Communication method and device

Abstract

The embodiment of the invention discloses a communication method, relates to the technical field of communication, and is used for preventing RedCap terminal equipment from moving to an NR cell which does not support the RedCap technology. The method comprises the following steps: acquiring prior information; and under the condition that the priori information indicates that the target cell is an NR cell which does not support the Red Cap technology or the eRed Cap technology, forbidding moving to the target cell or leaving the target cell. According to the scheme provided by the embodiment of the invention, before the RedCap terminal equipment moves to the NR cell from the non-NR cell, whether the target cell supports the RedCap technology can be predicted in advance through the prior information, and under the condition that the target cell is the NR cell not supporting the RedCap technology, the RedCap terminal equipment is forbidden to move to the target cell, so that the RedCap terminal equipment is prevented from moving to the NR cell not supporting the RedCap technology.

Description

Technical Field

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

[0002] 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.

[0003] RedCap reduces the capabilities of terminal devices 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 terminal devices and aims to reduce costs, power consumption, and extend lifespan. RedCap is more conducive to the popularization and commercialization of 5G networks.

[0004] RedCap terminal devices can only function normally in New Radio (NR) cells or non-NR cells (such as Long Term Evolution (LTE) cells) that support RedCap technology. When a RedCap terminal device moves from a non-NR cell (e.g., during cell handover, cell reselection, redirection, or blind handover) to an NR cell, at least some network devices in the non-NR cell will treat the RedCap terminal device as a regular 5G terminal device. This may cause the RedCap terminal device to move to an NR cell that does not support RedCap technology, thus preventing the RedCap terminal device from functioning properly. Summary of the Invention

[0005] This application provides a communication method and apparatus to prevent RedCap terminal devices from moving to NR cells that do not support RedCap technology. To achieve the above objective, this application adopts the following technical solution:

[0006] In a first aspect, embodiments of this application provide a communication method applied to a terminal device with RedCap or enhanced reduced cap ability (eRedCap). The method includes: obtaining prior information; and prohibiting movement to or leaving the target cell when the prior information indicates that the target cell is an NR cell that does not support RedCap or eRedCap technology.

[0007] The solution provided in this application embodiment allows RedCap terminal devices to predict whether a target cell supports RedCap technology in advance through prior information before moving from a non-NR cell to an NR cell. If the target cell is an NR cell that does not support RedCap technology, the RedCap terminal device is prohibited from moving to the target cell, thereby preventing the RedCap terminal device from moving to an NR cell that does not support RedCap technology.

[0008] In addition, in the solution provided in this application embodiment, after the RedCap terminal device camps on an NR cell, it can determine whether the camped NR cell supports RedCap technology through prior information. If the camped NR cell is an NR cell that does not support RedCap technology, the RedCap terminal device will leave the NR cell, thereby avoiding the RedCap terminal device from camping on an NR cell that does not support RedCap technology for a long time, which would cause the RedCap terminal device to malfunction.

[0009] In one possible implementation, the target cell can be moved to if prior information indicates that the target cell is an NR cell that supports RedCap or eRedCap technology.

[0010] The solution provided in this application embodiment allows RedCap terminal devices to predict in advance whether a target cell supports RedCap technology before moving from a non-NR cell to an NR cell. If the target cell is an NR cell that supports RedCap technology, the device can move to the target cell through cell handover, cell reselection, or redirection, thereby ensuring that the RedCap terminal device works normally.

[0011] In one possible implementation, system messages can be received; prior information can be determined based on the system messages.

[0012] As can be seen, in the solution provided by the embodiments of this application, the RedCap terminal device can obtain prior information through system messages. After obtaining the prior information, the RedCap terminal device can predict in advance whether the target cell supports RedCap technology.

[0013] Optionally, prohibiting movement to the target cell includes prohibiting at least one of the following: measuring the target cell, reporting the measurement results of the target cell, conducting cell assessment of the target cell, conducting cell search of the target cell, or selecting the target cell.

[0014] For example, measurements of a target cell can be disabled.

[0015] Understandably, cell measurement is an important step in cell handover, cell reselection, and redirection. By prohibiting measurement of target cells that do not support RedCap technology, RedCap terminal devices can be prevented from moving to target cells that do not support RedCap technology due to cell handover, cell reselection, or redirection.

[0016] As another example, the reporting of measurement results for the target cell can be prohibited.

[0017] It is understandable that reporting cell measurement results is an important step in cell handover and redirection. By prohibiting the reporting of measurement results for target cells that do not support RedCap technology, RedCap terminal devices can be prevented from moving to target cells that do not support RedCap technology due to cell handover or redirection.

[0018] As another example, community assessments for the target community can be prohibited.

[0019] Understandably, cell assessment is an important step in cell reselection. By prohibiting cell assessment of target cells that do not support RedCap technology, RedCap terminal devices can be prevented from moving to target cells that do not support RedCap technology due to cell reselection.

[0020] For example, cell searches for a target cell can be disabled.

[0021] Understandably, cell search is a crucial step in initial access and network reconnection. By prohibiting cell search of target cells that do not support RedCap technology, RedCap terminal devices can be prevented from moving to target cells that do not support RedCap technology due to initial access or network reconnection.

[0022] In one possible implementation, radio resource control (RRC) reconstruction can be performed if prior information indicates that the target cell is an NR cell that does not support RedCap or eRedCap technology.

[0023] In the solution provided in this application embodiment, if a RedCap terminal device is camped in an NR cell that does not support RedCap technology due to blind handover or other reasons, it can reselect the camped cell by performing RRC reconstruction to leave the NR cell. This avoids the RedCap terminal device being camped in an NR cell that does not support RedCap technology for a long time, which would cause the RedCap terminal device to malfunction.

[0024] Secondly, embodiments of this application provide a communication device, which may be a RedCap terminal device or an eRedCap terminal device, or a module (e.g., processor, chip, or chip system) applied to a RedCap terminal device or an eRedCap terminal device, or a logical node, logical module, or software capable of implementing all or part of the functions of a RedCap terminal device or an eRedCap terminal device. The device includes a transceiver unit and a processing unit. The transceiver unit is used to acquire prior information. The processing unit is used to prohibit movement to or leaving the target cell when the prior information indicates that the target cell is an NR cell that does not support RedCap or eRedCap technology.

[0025] In one possible implementation, the processing unit is further configured to: move to the target cell if prior information indicates that the target cell is an NR cell supporting RedCap technology or eRedCap technology.

[0026] In one possible implementation, the transceiver unit is specifically used to: receive system messages; and determine prior information based on the system messages.

[0027] In one possible implementation, prohibiting movement to the target cell includes prohibiting at least one of the following: performing cell measurements on the target cell, reporting measurement results of the target cell, performing cell assessments on the target cell, performing cell searches on the target cell, or performing cell selection on the target cell.

[0028] In one possible implementation, the processing unit is specifically used to perform RRC reconstruction.

[0029] Thirdly, embodiments of this application also provide a communication device (e.g., the communication device may be a chip or a chip system), the device comprising: 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.

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

[0031] 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.

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

[0033] 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.

[0034] 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.

[0035] 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

[0036] 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.

[0037] Figure 1 This application provides a schematic diagram of the structure of a communication system according to an embodiment of the present application.

[0038] Figure 2 This application provides a schematic diagram of the structure of a network device according to an embodiment of the present application.

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

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

[0041] Figure 5 This application provides a schematic diagram illustrating the prohibition of movement to the target cell in its embodiments.

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

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

[0044] Figure 8 This 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 future evolution communication systems, etc., without limitation. The following only uses... Figure 1 Taking the communication system 100 shown as an example, the method provided in the embodiments of this application will be described.

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

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

[0053] Network device 200 is located on the network side of the aforementioned communication system, used to help terminal devices achieve wireless access, and is a device with wireless transceiver capabilities or a chip or chip system that can be installed in the device. 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), next-generation base stations in sixth-generation (6G) mobile communication systems, 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, 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 remote control 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 equipment 300 is a device, equipment, module, chip or chip system with transceiver functions. It can also be referred to as user equipment (UE), 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 terminal devices in the embodiments of this application may 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, and smart grids. Wireless terminals in various applications include those related to grids, transportation safety, smart cities, and smart homes; vehicle-mounted terminals; vehicle-mounted screens; vehicle-mounted audio systems; car keys; roadside units (RSUs) with terminal functions; and flying equipment (e.g., intelligent robots, hot air balloons, drones, and airplanes). The terminal equipment in this application can also be an onboard module, onboard unit, onboard component, onboard chip, or onboard unit integrated into a vehicle as one or more components or units. The terminal equipment 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 device. The device used to implement the function of the terminal device can be the terminal device itself; it can also be a device that supports the terminal device in implementing the function, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete components.

[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 needs to be explained that, Figure 1 The communication system 100 shown is merely one implementation of the embodiments of this application. In actual applications, the communication system 100 may include more or fewer components, which is not limited here.

[0059] refer to Figure 2 , Figure 2 The network device 200 provided in some embodiments of this application is illustrated. For example... Figure 2 As shown, 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 can be connected via bus 204 or other means. Figure 2 Taking a bus connection as an example:

[0060] The communication interface 203 can be used by the network device 200 to communicate with other communication devices, such as terminal devices 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 another network device 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, RT Linux, 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 terminal devices, or one or more network devices.

[0063] Processor 201 can be used for radio channel management, establishing and dismantling call and communication links, and providing cell handover control for users within the control area. Specifically, processor 201 may include: an administration / communication module (AM / CM) (for central 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 needs to be explained that, Figure 2 The network device 200 shown is merely one implementation of the embodiments of this application. In actual applications, the network device 200 may include more or fewer components, which is not limited here.

[0066] refer to Figure 3 , Figure 3 The present application illustrates a terminal device 300 provided in some embodiments. For example... Figure 3As shown, the terminal device 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 Taking a bus connection as an example:

[0067] The communication interface 303 can be used by the terminal device 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 device 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 device 300, the number of transmitters 306 and receivers 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] Apart from Figure 3 The transmitter 306 and receiver 305 shown may be accompanied by other communication components in the terminal device 300, such as a global positioning system (GPS) module, a Bluetooth module, or a wireless fidelity (Wi-Fi) module. Not limited to the wireless communication signals described above, the terminal device 300 may also support other wireless communication signals, such as satellite signals, shortwave signals, etc. In addition to wireless communication, the terminal device 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 device 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 terminal devices, 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 by one or more embodiments of this application on the terminal device 300 side. For the implementation of the resource allocation method provided by 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 device 300 side, and execute the instructions contained in the program.

[0074] It needs to be explained that, Figure 3 The terminal device 300 shown is merely one implementation of the embodiments of this application. In actual applications, the terminal device 300 may include more or fewer components, which is not limited here.

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

[0076] S401, Obtain prior information.

[0077] In one possible implementation, the terminal device can receive system messages and determine prior information based on the system messages.

[0078] For example, a terminal device can receive a system information block (SIB) sent by a network device and determine prior information based on the SIB.

[0079] For example, after a RedCap terminal device camps on an NR cell, it can receive SIB4 sent by the network equipment of the NR cell and determine whether each frequency point supports RedCap technology based on whether a specific field (such as redCapAccessAllowed-r17) is carried in the inter-frequency measurement configuration of each frequency point in SIB4. For frequency points that do not support RedCap technology, it can measure to determine which cells are under that frequency point and determine that the cells under that frequency point are NR cells that do not support RedCap technology. Based on the cell information of NR cells that do not support RedCap technology (such as cell unique code (IdentityDocument, ID), cell identifier, etc.), it can determine prior information.

[0080] For example, after the eRedCap terminal device camps on an NR cell, it can receive SIB4 sent by the network equipment of the NR cell and determine whether each frequency point supports eRedCap technology based on whether the inter-frequency measurement configuration of each frequency point in the SIB4 carries a specific field (such as eRedCapAccessAllowed-r18). For frequency points that do not support eRedCap technology, it performs measurements to determine which cells are under that frequency point and determines that the cells under that frequency point are NR cells that do not support eRedCap technology. Based on the cell information of NR cells that do not support eRedCap technology, it determines prior information.

[0081] As can be seen, in the solution provided by the embodiments of this application, the RedCap terminal device can obtain prior information through system messages. After obtaining the prior information, the RedCap terminal device can predict in advance whether the target cell supports RedCap technology.

[0082] In one possible implementation, the prior information may include cell information of NR cells that do not support RedCap technology and / or cell information of NR cells that do not support eRedCap technology.

[0083] For example, prior information may include cell information of NR cells that do not support RedCap technology.

[0084] For example, prior information may include cell information of NR cells that do not support eRedCap technology.

[0085] In one possible implementation, prior information sent by other devices can be received.

[0086] For example, a RedCap terminal device can receive prior information sent by a server or other RedCap terminal devices.

[0087] For example, in some scenarios, a server can be set up to store prior information. RedCap terminal devices can request prior information from the server and receive prior information sent by the server.

[0088] As another example, the eRedCap terminal device can receive prior information sent by the server or other eRedCap terminal devices.

[0089] S402. If prior information indicates that the target cell is an NR cell that does not support RedCap technology or eRedCap technology, moving to or leaving the target cell is prohibited.

[0090] Optionally, prohibiting movement to the target cell includes prohibiting at least one of the following: measuring the target cell, reporting the measurement results of the target cell, conducting cell assessment of the target cell, conducting cell search of the target cell, or selecting the target cell.

[0091] For example, such as Figure 5 As shown, prohibiting movement to the target cell can include prohibiting measurement of the target cell, prohibiting reporting of measurement results of the target cell, prohibiting cell assessment of the target cell, prohibiting cell search of the target cell, and prohibiting cell selection of the target cell.

[0092] In one possible implementation, a RedCap terminal can prevent the terminal from moving to the target cell if it has not moved to the target cell and prior information indicates that the target cell is an NR cell that does not support RedCap technology.

[0093] For example, after a RedCap terminal camps on an LTE cell, if the RedCap terminal needs to move to an NR cell through cell handover, cell reselection, or redirection, then during the cell measurement process, if the RedCap terminal finds that the target cell is an NR cell that does not support RedCap technology, it can choose not to measure the target cell.

[0094] For example, after a RedCap terminal camps on an LTE cell, if it needs to move to an NR cell via cell handover or redirection, the RedCap terminal enters connected mode and initiates LTE-to-NR cell measurement. During this measurement process, if the RedCap terminal discovers that the target cell is an NR cell that does not support RedCap technology, it may choose not to measure the target cell. Without measuring the target cell, the RedCap terminal cannot obtain a measurement report for the target cell and therefore cannot report this report to the network equipment in the LTE cell where it camps. Consequently, the network equipment in the LTE cell where the RedCap terminal camps cannot instruct the RedCap terminal to move to a target cell that does not support RedCap technology via cell handover or redirection based on the target cell's measurement report.

[0095] For example, after a RedCap terminal camps on an LTE cell, if it needs to move to an NR cell via cell reselection, it initiates an idle-state cell measurement from LTE to NR. During this measurement, if the RedCap terminal discovers that the target cell is an NR cell that does not support RedCap technology, it can choose not to measure the target cell. Without measuring the target cell, the RedCap terminal cannot obtain a measurement report for the target cell, nor can it perform cell evaluation based on the report. Consequently, it will not perform cell reselection to a target cell that does not support RedCap technology.

[0096] Understandably, cell measurement is an important step in cell handover, cell reselection, and redirection. By prohibiting measurement of target cells that do not support RedCap technology, RedCap terminal devices can be prevented from moving to target cells that do not support RedCap technology due to cell handover, cell reselection, or redirection.

[0097] For example, after a RedCap terminal camps on an LTE cell, if the RedCap terminal needs to move to an NR cell via cell handover or redirection, then during the cell measurement process, if the RedCap terminal finds that the target cell is an NR cell that does not support RedCap technology, it may not report the measurement results of the target cell.

[0098] For example, after a RedCap terminal camps on an LTE cell, if it needs to move to an NR cell via cell handover or redirection, the RedCap terminal enters connected state and initiates LTE-to-NR cell measurement. During the cell measurement process, if the RedCap terminal discovers that the target cell is an NR cell that does not support RedCap technology, the RedCap terminal may choose not to report the target cell's measurement report to the network equipment in the LTE cell where it is camped. Consequently, the network equipment in the LTE cell where the RedCap terminal is camped cannot instruct the RedCap terminal to move to the target cell via cell handover or redirection based on the target cell's measurement report.

[0099] It is understandable that reporting cell measurement results is an important step in cell handover and redirection. By prohibiting the reporting of measurement results for target cells that do not support RedCap technology, RedCap terminal devices can be prevented from moving to target cells that do not support RedCap technology due to cell handover or redirection.

[0100] For example, after a RedCap terminal camps on an LTE cell, if the RedCap terminal needs to reselect to an NR cell, then during the cell measurement process, if the RedCap terminal finds that the target cell is an NR cell that does not support RedCap technology, it can choose not to perform cell evaluation on the target cell.

[0101] For example, after a RedCap terminal camps on an LTE cell, if it needs to move to an NR cell via cell reselection, the RedCap terminal initiates an idle-state cell measurement from LTE to NR. During the cell measurement process, if the RedCap terminal discovers that the target cell is an NR cell that does not support RedCap technology, the RedCap terminal can choose not to perform cell evaluation on the target cell, thus avoiding cell reselection to a target cell that does not support RedCap technology due to cell evaluation.

[0102] Understandably, cell assessment is an important step in cell reselection. By prohibiting cell assessment of target cells that do not support RedCap technology, RedCap terminal devices can be prevented from moving to target cells that do not support RedCap technology due to cell reselection.

[0103] For example, after a RedCap terminal is powered on or disconnected from the network, it can move to an NR cell through initial access or reconnection. If the RedCap terminal finds that the target cell is an NR cell that does not support RedCap technology during the cell search process, it can choose not to perform a cell search on the target cell.

[0104] Understandably, cell search is a crucial step in initial access and network reconnection. By prohibiting cell search of target cells that do not support RedCap technology, RedCap terminal devices can be prevented from moving to target cells that do not support RedCap technology due to initial access or network reconnection.

[0105] As can be seen, the solution provided in this application embodiment allows the RedCap terminal device to predict in advance whether the target cell supports RedCap technology before moving from a non-NR cell to an NR cell. If the target cell is an NR cell that does not support RedCap technology, the RedCap terminal device is prohibited from moving to the target cell, thereby preventing the RedCap terminal device from moving to an NR cell that does not support RedCap technology.

[0106] In another possible implementation, the eRedCap terminal can prevent the terminal from moving to the target cell if it has not moved to the target cell and prior information indicates that the target cell is an NR cell that does not support eRedCap technology.

[0107] As can be seen, the solution provided in this application allows the eRedCap terminal device to predict in advance whether the target cell supports eRedCap technology before moving from a non-NR cell to an NR cell. If the target cell is an NR cell that does not support eRedCap technology, the eRedCap terminal device is prohibited from moving to the target cell, thereby preventing the eRedCap terminal device from moving to an NR cell that does not support eRedCap technology.

[0108] In one possible implementation, a RedCap terminal can leave a target cell even if it has moved to the target cell and prior information indicates that the target cell is an NR cell that does not support RedCap technology.

[0109] For example, after a RedCap terminal device camps on an NR cell due to blind handover or other reasons, the RedCap terminal device can determine whether the currently camped NR cell supports RedCap technology through prior information. If the prior information indicates that the target cell is an NR cell that does not support RedCap technology, the RedCap terminal device can leave the target cell.

[0110] For example, after a RedCap terminal device camps on an NR cell due to blind handover or other reasons, the RedCap terminal device can determine whether the currently camped NR cell supports RedCap technology through prior information. If the prior information indicates that the target cell is an NR cell that does not support RedCap technology, the RedCap terminal device can perform RRC reconstruction to reselect the camped cell and leave the NR cell.

[0111] As can be seen, in the solution provided by the embodiments of this application, after the RedCap terminal device camps on an NR cell, it can determine whether the NR cell it camps on supports RedCap technology through prior information. If the NR cell it camps on is not an NR cell that does not support RedCap technology, the RedCap terminal device leaves the NR cell, thereby avoiding the RedCap terminal device from camping on an NR cell that does not support RedCap technology for a long time, which would cause the RedCap terminal device to malfunction.

[0112] In another possible implementation, the eRedCap terminal can leave the target cell even if it has moved to the target cell and prior information indicates that the target cell is an NR cell that does not support eRedCap technology.

[0113] As can be seen, in the solution provided by the embodiments of this application, after the eRedCap terminal device camps on an NR cell, it can determine whether the camped NR cell supports eRedCap technology through prior information. If the camped NR cell is an NR cell that does not support eRedCap technology, the eRedCap terminal device leaves the NR cell, thereby avoiding the eRedCap terminal device from camping on an NR cell that does not support eRedCap technology for a long time, which would cause the eRedCap terminal device to malfunction.

[0114] The specific implementation method for leaving the target cell can be any method that can be conceived by those skilled in the art, and the embodiments of this application do not limit it.

[0115] For example, a RedCap terminal device or an eRedCap terminal device can perform an RRC reconstruction.

[0116] For example, if a RedCap terminal device is camped on an NR cell that does not support RedCap technology due to blind handover or other reasons, the RedCap terminal device can perform RRC reconstruction to reselect the camped cell and leave the NR cell.

[0117] As can be seen, in the solution provided by the embodiments of this application, if the RedCap terminal device is camped in an NR cell that does not support RedCap technology due to blind handover or other reasons, it can perform RRC reconstruction to reselect the camped cell and leave the NR cell. This avoids the RedCap terminal device from camping in an NR cell that does not support RedCap technology for a long time, which would cause the RedCap terminal device to malfunction.

[0118] For example, if an eRedCap terminal device is camped on an NR cell that does not support eRedCap technology due to blind handover or other reasons, the eRedCap terminal device can perform RRC reconstruction to reselect the camped cell and leave the NR cell.

[0119] As can be seen, in the solution provided by the embodiments of this application, when the eRedCap terminal device is camped in an NR cell that does not support eRedCap technology due to blind handover or other reasons, it can reselect the camped cell by performing RRC reconstruction to leave the NR cell. This avoids the eRedCap terminal device being camped in an NR cell that does not support eRedCap technology for a long time, which would cause the eRedCap terminal device to malfunction.

[0120] In one possible implementation, the target cell can be moved to if prior information indicates that the target cell is an NR cell that supports RedCap or eRedCap technology.

[0121] For example, a RedCap terminal device can move to a target cell if prior information indicates that the target cell is an NR cell that supports RedCap technology.

[0122] As can be seen, the solution provided in this application embodiment allows the RedCap terminal device to predict in advance whether the target cell supports RedCap technology before moving from a non-NR cell to an NR cell. If the target cell is an NR cell that supports RedCap technology, the device can move to the target cell through cell handover, cell reselection, or relocation, thereby ensuring that the RedCap terminal device works normally.

[0123] As another example, the eRedCap terminal device can move to the target cell if prior information indicates that the target cell is an NR cell that supports eRedCap technology.

[0124] As can be seen, the solution provided in this application embodiment allows the eRedCap terminal device to predict in advance whether the target cell supports eRedCap technology before moving from a non-NR cell to an NR cell. If the target cell is an NR cell that supports eRedCap technology, the device can move to the target cell through cell handover, cell reselection, or relocation, thereby ensuring that the eRedCap terminal device works normally.

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

[0126] 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.

[0127] 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.

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

[0129] Figure 6 The diagram illustrates a possible configuration of the communication device involved in the above embodiments. This device can be a RedCap terminal device or an eRedCap terminal device, or a module (e.g., processor, chip, or chip system) applied to a RedCap terminal device or an eRedCap terminal device, or a logical node, logical module, or software capable of implementing all or part of the functions of a RedCap terminal device or an eRedCap terminal device. Figure 6 As shown, the communication device 600 may include a transceiver unit 601 and a processing unit 602.

[0130] The transceiver unit 601 is used to acquire prior information.

[0131] The processing unit 602 is used to prohibit moving to or leaving the target cell when prior information indicates that the target cell is an NR cell that does not support RedCap technology or eRedCap technology.

[0132] In one possible implementation, the processing unit is further configured to: move to the target cell if prior information indicates that the target cell is an NR cell supporting RedCap technology or eRedCap technology.

[0133] In one possible implementation, the transceiver unit 601 is specifically used to: receive system messages; and determine prior information based on the system messages.

[0134] In one possible implementation, prohibiting movement to the target cell includes prohibiting at least one of the following: performing cell measurements on the target cell, reporting measurement results of the target cell, performing cell assessments on the target cell, performing cell searches on the target cell, or performing cell selection on the target cell.

[0135] In one possible implementation, the processing unit 602 is specifically used to: perform RRC reconstruction.

[0136] This application also provides a chip, which can be the chip of the above-mentioned communication device. Figure 7 A schematic diagram of a chip 700 is shown. The chip 700 includes one or more processors 701 and interface circuitry 702. Optionally, the chip 700 may also include a bus 703.

[0137] The processor 701 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the aforementioned communication method can be completed through integrated logic circuits in the processor 701 or through software instructions.

[0138] Optionally, the processor 701 described above can 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 can be a microprocessor or any conventional processor, etc.

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

[0140] 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).

[0141] 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).

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

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

[0144] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device can be a communication device, a chip within the communication device, or a functional module. For example... Figure 8 As shown, the electronic device 800 includes a processor 801, a transceiver 802, and a communication line 803.

[0145] The processor 801 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 may choose to call the transceiver 802 and the communication line 803 to complete the corresponding operation.

[0146] Furthermore, the electronic device 800 may also include a memory 804. The processor 801, the memory 804, and the transceiver 802 can be connected via a communication line 803.

[0147] The processor 801 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 801 can also be other devices with processing capabilities, such as circuits, devices, or software modules, without limitation.

[0148] Transceiver 802 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 802 can be a module, circuit, transceiver, or any device capable of enabling communication.

[0149] The transceiver 802 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.

[0150] Communication line 803 is used to transmit information between the various components included in electronic device 800.

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

[0152] The memory 804 is used to store instructions. These instructions can be computer programs.

[0153] The memory 804 can be volatile memory or non-volatile memory, or 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 DRAM (DRRAM). Memory 804 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.

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

[0155] In one example, processor 801 may include one or more processor cores, for example Figure 8 The processor cores are 0 and 1.

[0156] As an optional implementation, the electronic device 800 includes multiple processors, for example, besides Figure 8 In addition to processor 801, it may also include processor 807.

[0157] As an optional implementation, the electronic device 800 also includes an output device 805 and an input device 806. For example, the input device 806 is a device such as a keyboard, mouse, microphone, or joystick, and the output device 805 is a device such as a display screen or speaker.

[0158] It should be noted that the electronic device 800 can be a chip system or... Figure 8 Devices with similar structures. The chip system can be composed of chips or include chips and other discrete components. Actions, terminology, 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 can be used in specific implementations without limitation. Furthermore, Figure 8 The structural composition shown does not constitute a limitation on the electronic device 800, except... Figure 8 In addition to the components shown, the electronic device 800 may include more than Figure 8 This may indicate more or fewer components, or combinations of certain components, or different component arrangements.

[0159] 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-type metal oxide semiconductors (NMOS), p-type metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0160] 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.

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

[0162] 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.

[0163] 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.

[0164] 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.

[0165] 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.

[0166] 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.

[0167] 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.

[0168] 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.

[0169] 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.

[0170] 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.

[0171] 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 embodiment, 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.

[0172] 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 by comprising: A terminal device applied to a reduced capability RedCap or an enhanced reduced capability eRedCap, comprising: acquiring prior information; in a case where the prior information indicates that a target cell is a new radio, NR, cell that does not support a RedCap technology or an eRedCap technology, prohibiting moving to the target cell or leaving the target cell.

2. The method of claim 1, wherein, The method further comprises: in a case where the prior information indicates that the target cell is an NR cell that supports the RedCap technology or the eRedCap technology, moving to the target cell.

3. The method according to claim 1 or 2, characterized in that, The acquiring of the prior information comprises: receiving a system message; determining the prior information according to the system message.

4. The method according to any one of claims 1 to 3, characterized in that, The prohibiting of moving to the target cell comprises prohibiting at least one of the following: performing cell measurement on the target cell, reporting a measurement result of the target cell, performing cell evaluation on the target cell, performing cell search on the target cell, or performing cell selection on the target cell.

5. The method according to any one of claims 1 to 4, characterized in that, The leaving of the target cell comprises: performing radio resource control, RRC, reestablishment.

6. A communication device, characterized by comprising: a transceiver and a processing unit; The transceiver is configured to acquire prior information. The processing unit is configured to, in a case where the prior information indicates that a target cell is a new radio, NR, cell that does not support a RedCap technology or an eRedCap technology, prohibit moving to the target cell or leaving the target cell.

7. The apparatus of claim 6, wherein, The processing unit is further configured to: in a case where the prior information indicates that the target cell is an NR cell that supports the RedCap technology or the eRedCap technology, move to the target cell.

8. The apparatus of claim 6 or 7, wherein, The transceiver is specifically configured to: receive a system message; determine the prior information according to the system message.

9. The apparatus of any one of claims 6-8, wherein, The prohibiting of moving to the target cell comprises prohibiting at least one of the following: performing cell measurement on the target cell, reporting a measurement result of the target cell, performing cell evaluation on the target cell, performing cell search on the target cell, or performing cell selection on the target cell.

10. The apparatus of any one of claims 6 to 9, wherein, The processing unit is specifically configured to: perform radio resource control, RRC, reestablishment.

11. A communications device comprising at least one processor and a memory, wherein the processor is configured to: The at least one processor executes programs or instructions stored in the memory, so that the communication device implements the method of any one of claims 1-5.

12. A computer readable storage medium for storing a computer program, characterized in that, When the computer program runs on the computer or the processor, the computer or the processor implements the method of any one of claims 1-5.

13. A computer program product, the computer program product comprising instructions embodied therein, wherein: When the instructions run on the computer or the processor, the computer or the processor implements the method of any one of claims 1-5.

Images