Communication method and apparatus

Abstract

This application discloses a communication method and apparatus, relating to the field of communication technology, for reducing access latency of RedCap terminals. The method includes: obtaining a first cell list; determining the cell order of the first cell list based on cell information; and performing cell search or cell reselection based on the cell order. The first cell list is either a cell search list or a cell reselection list, and the cell information includes at least one of energy, signal-to-noise ratio (SNR), RedCap capability, bandwidth, or cell type. Compared to simply sorting cells in the first cell list based on energy and SNR, this solution additionally considers RedCap capability, bandwidth, and cell type during the cell sorting process. The RedCap terminal can use RedCap capability, bandwidth, and cell type to prioritize cells in the first cell list that are eligible for access, thereby enabling it to use cells at the top of the first cell list to complete access during cell search or reselection, thus reducing cell access latency.

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 variant of 5G technology defined by the 3rd Generation Partnership Project (3GPP) standardization organization, also known as lightweight 5G. This technology aims to provide a cost-effective solution for specific scenarios and applications while retaining the core advantages of 5G technology.

[0003] RedCap technology, while meeting application requirements and performance standards, reduces the performance requirements of terminal devices by decreasing bandwidth, the number of transceiver antennas, lowering data transmission rates, adjusting modulation schemes, and adopting half-duplex mode, thereby simplifying device complexity. This helps reduce terminal costs, lower energy consumption, and extend device lifespan. This technology is particularly suitable for Internet of Things (IoT) devices with lower data transmission rate requirements and certain specific industrial applications. The introduction of RedCap technology is expected to promote the wider deployment of 5G networks and enhance the commercial application potential of 5G technology.

[0004] However, it should be noted that RedCap terminals may experience significant latency when accessing the network, which could impact application scenarios with high real-time requirements. Summary of the Invention

[0005] This application provides a communication method and apparatus for reducing the access latency of RedCap terminals. 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, the method comprising: obtaining a first cell list; determining the cell order of the first cell list based on cell information; and performing cell search or cell reselection based on the cell order. The first cell list includes frequency division duplex (FDD) cells and / or time division duplex (TDD) cells, the first cell list is a cell search list or a cell reselection list, the cell information includes at least one of energy, signal-to-noise ratio, RedCap capability, bandwidth, or cell type, and the cell order is the cell search order or the cell reselection order.

[0007] Compared to traditional methods that sort cells in the first cell list solely based on energy and signal-to-noise ratio, the scheme proposed in this application incorporates three additional factors—RedCap capability, bandwidth, and cell type—when sorting cells. By comprehensively evaluating these factors, the RedCap terminal can prioritize cells with higher RedCap capability, greater bandwidth, and more suitable cell types in the first cell list. Therefore, during cell search or reselection, the RedCap terminal can preferentially select cells ranked higher in the first cell list to complete the access operation. This scheme effectively reduces cell access latency and improves network access efficiency.

[0008] In some implementations, the cell information includes energy, signal-to-noise ratio, RedCap capability, bandwidth, and cell type. In the cell order, cells supporting RedCap capability are ranked higher than target bandwidth cells that do not support RedCap capability. Target bandwidth cells that do not support RedCap capability are ranked higher than non-target bandwidth FDD cells that do not support RedCap capability. Non-target bandwidth FDD cells that do not support RedCap capability are ranked higher than non-target bandwidth TDD cells that do not support RedCap capability. The target bandwidth cell is a cell with bandwidth less than or equal to a bandwidth threshold.

[0009] Understandably, based on the characteristics of RedCap technology, this solution can divide cells into two main categories: cells with RedCap technology capabilities and cells without RedCap technology capabilities. Given that cells with RedCap technology capabilities have a significant advantage in accessing RedCap terminals, these cells should be given priority when ranking cells, ensuring they are placed in the first cell list before cells without RedCap technology capabilities.

[0010] For cells lacking RedCap technical capabilities, this solution can further subdivide them based on their bandwidth. Specifically, these cells can be divided into two categories: one is non-target bandwidth cells with bandwidth exceeding a certain threshold, and the other is target bandwidth cells with bandwidth less than or equal to that threshold. Since cells with smaller bandwidth are more suitable for accessing RedCap terminals, target bandwidth cells should be prioritized over non-target bandwidth cells in the first cell list.

[0011] Furthermore, non-target bandwidth cells within cells lacking RedCap capability can be further categorized based on cell type. Specifically, these cells can be divided into non-target bandwidth FDD cells and non-target bandwidth TDD cells. Typically, FDD cells have smaller bandwidths, while TDD cells have larger bandwidths. Given that smaller bandwidth cells are more suitable for RedCap terminal access, non-target bandwidth FDD cells lacking RedCap capability should be listed before non-target bandwidth TDD cells lacking RedCap capability in the first cell list.

[0012] In some implementations, if a first type of cell is found during the reselection evaluation process and the first type of cell does not exist in the first cell list, the first type of cell can be added to the first cell list. The first type of cell includes cells that support RedCap capability, target bandwidth cells that do not support RedCap capability, and non-target bandwidth FDD cells that do not support RedCap capability.

[0013] Understandably, Type 1 cells are more suitable for RedCap terminal access because their specific configurations and characteristics allow them to better meet the access requirements of RedCap terminals. If a Type 1 cell is not currently in the list of Type 1 cells, it may indicate that the cells in the list are not entirely suitable for RedCap terminal access. Therefore, during the reselection evaluation process, once a more suitable Type 1 cell for RedCap terminal access is found, it should be added to the list of Type 1 cells. This allows RedCap terminals to access the newly discovered Type 1 cell, thereby improving network performance and user experience.

[0014] In some implementations, the cell information includes energy, signal-to-noise ratio, RedCap capability, and cell type. In the cell order, cells supporting RedCap capability are ranked higher than FDD cells that do not support RedCap capability, and FDD cells that do not support RedCap capability are ranked higher than TDD cells that do not support RedCap capability.

[0015] Understandably, based on the characteristics of RedCap technology, this solution can classify cells into those with RedCap technology capabilities and those without. Cells with RedCap technology capabilities are more suitable for RedCap terminal access; therefore, when ranking cells, those supporting RedCap technology should be given priority, and their ranking in the first cell list should be higher than that of cells lacking RedCap technology capabilities.

[0016] For cells lacking RedCap technology capabilities, this solution can be further subdivided according to cell type, specifically into FDD cells that do not support RedCap technology and TDD cells that do not support RedCap technology. Typically, FDD cells have smaller bandwidth, while TDD cells have larger bandwidth. Since cells with smaller bandwidth have certain advantages in accessing RedCap terminals, when ranking cells, non-target bandwidth FDD cells lacking RedCap technology capabilities should be ranked higher, and their order in the first cell list should be higher than that of non-target bandwidth TDD cells lacking RedCap technology capabilities.

[0017] In some implementations, if a second type of cell is found during the reselection evaluation process and the second type of cell does not exist in the first cell list, the second type of cell can be added to the first cell list. The second type of cell includes cells that support RedCap capability and FDD cells that do not support RedCap capability.

[0018] Understandably, the second type of cell is more suitable for RedCap terminal access because its specific configuration and characteristics better meet the needs of RedCap terminals. The absence of a second type of cell in the first cell list indicates that the cells currently in the first cell list are not suitable for RedCap terminal access. Therefore, during the reselection evaluation process, once a second type of cell more suitable for RedCap terminal access is found, it should be added to the first cell list. This ensures that RedCap terminals can access the newly found second type of cell, thereby improving network efficiency and terminal performance.

[0019] In some implementations, the cell information mentioned above includes energy, signal-to-noise ratio, and cell type, and the order of FDD cells is higher than that of TDD cells in the cell order.

[0020] Understandably, this scheme categorizes cells into two main types based on their type: FDD cells and TDD cells. Typically, FDD cells are designed with smaller bandwidths, while TDD cells tend to use larger bandwidths. This bandwidth difference leads to an interesting phenomenon: RedCap terminal access is smoother and more efficient in FDD cells with lower bandwidth. Therefore, this scheme should take this into account when compiling the initial cell list, prioritizing FDD cells over TDD cells to ensure the rational allocation and maximization of network resource utilization efficiency.

[0021] In some implementations, if a third type of cell is found during the reselection evaluation process and the third type of cell does not exist in the first cell list, the third type of cell can be added to the first cell list. The third type of cell includes FDD cells.

[0022] Understandably, third-type cells are more suitable for RedCap terminal access because they possess specific network characteristics that better meet their access requirements. When a third-type cell is missing from the first cell list, it indicates that the cells currently in the first cell list are not suitable for RedCap terminal access. Therefore, during the reselection evaluation process, if a more suitable third-type cell for RedCap terminal access is found, it can be added to the first cell list. This allows the RedCap terminal to utilize the newly found access point, i.e., the third-type cell, for more efficient network access.

[0023] In some implementations, a second cell list can be obtained, which includes FDD cells and TDD cells; and a first cell list can be generated based on the second cell list, which includes FDD cells in the second cell list.

[0024] Understandably, FDD cells typically have smaller bandwidths, while TDD cells generally have larger bandwidths. Given that smaller bandwidth cells are more suitable for RedCap terminal access compared to larger bandwidth cells, by retaining only FDD cells from the second cell list, TDD cells can be effectively excluded from the candidate cell pool. This ensures a higher success rate for RedCap terminals accessing the network after cell reselection, improving network efficiency and performance, by using only FDD cells as candidate cells.

[0025] In some implementations, if a TDD cell that does not support RedCap capability is found during cell search or cell reselection, the aforementioned TDD cell that does not support RedCap capability can be added to the prohibited bar list.

[0026] Understandably, TDD cells typically have large bandwidth, making them less suitable for RedCap terminals. Therefore, to ensure RedCap terminals can effectively camp on cells that support their capabilities, it is recommended to add TDD cells that do not support RedCap capabilities to the prohibited camping list. This measure effectively prevents RedCap terminals from mistakenly selecting TDD cells that do not support their specific functions during cell reselection or access, thereby ensuring terminal performance and network stability.

[0027] In some implementations, system messages can be received; the RedCap capabilities mentioned above can be determined based on these system messages.

[0028] Understandably, System Information Blocks (SIBs) play a crucial role in communication systems. System messages ensure that terminals can correctly access the network and provide necessary system configuration information, thereby guaranteeing the normal operation of the terminal and the realization of communication functions. Therefore, RedCap terminals can use system messages (such as SIB1) to determine whether a cell has RedCap capability, which is a crucial step. Only when the terminal recognizes that the cell supports RedCap technology can it perform the corresponding configuration and optimization to adapt to the network environment and ensure the efficiency and stability of data transmission.

[0029] 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, etc.), or a logical node, logical module or software that can realize all or part of the terminal functions. The device includes: a transceiver unit and a processing unit.

[0030] The transceiver unit is used to obtain a first cell list, which includes FDD cells and / or TDD cells, and the first cell list is a cell search list or a cell reselection list.

[0031] The processing unit is configured to determine the cell order of the first cell list based on cell information, wherein the cell information includes at least one of energy, signal-to-noise ratio, RedCap capability, bandwidth, or cell type, and the cell order is either the cell search order or the cell reselection order.

[0032] The aforementioned processing unit is also used to perform cell search or cell reselection according to the aforementioned cell order.

[0033] In some implementations, the cell information includes energy, signal-to-noise ratio, RedCap capability, bandwidth, and cell type. In the cell order, cells supporting RedCap capability are ranked higher than target bandwidth cells that do not support RedCap capability. Target bandwidth cells that do not support RedCap capability are ranked higher than non-target bandwidth FDD cells that do not support RedCap capability. Non-target bandwidth FDD cells that do not support RedCap capability are ranked higher than non-target bandwidth TDD cells that do not support RedCap capability. The target bandwidth cell is a cell with bandwidth less than or equal to a bandwidth threshold.

[0034] In some implementations, the processing unit is further configured to: add the first type of cell to the first cell list when a first type of cell is found during the reselection evaluation process and the first type of cell does not exist in the first cell list. The first type of cell includes cells that support RedCap capability, target bandwidth cells that do not support RedCap capability, and non-target bandwidth FDD cells that do not support RedCap capability.

[0035] In some implementations, the cell information includes energy, signal-to-noise ratio, RedCap capability, and cell type. In the cell order, cells supporting RedCap capability are ranked higher than FDD cells that do not support RedCap capability, and FDD cells that do not support RedCap capability are ranked higher than TDD cells that do not support RedCap capability.

[0036] In some implementations, the processing unit is further configured to: add the second type of cell to the first cell list when a second type of cell is found during the reselection evaluation process and the second type of cell does not exist in the first cell list; the second type of cell includes cells that support RedCap capability and FDD cells that do not support RedCap capability.

[0037] In some implementations, the cell information mentioned above includes energy, signal-to-noise ratio, and cell type, and the order of FDD cells is higher than that of TDD cells in the cell order.

[0038] In some implementations, the processing unit is further configured to: add the third type of cell to the first cell list when a third type of cell is found during the reselection evaluation process and the third type of cell does not exist in the first cell list, wherein the third type of cell includes FDD cells.

[0039] In some implementations, the transceiver unit is further configured to: obtain a second cell list, the second cell list including FDD cells and TDD cells; generate the first cell list based on the second cell list, the first cell list including FDD cells in the second cell list.

[0040] In some implementations, the processing unit is also used to add the TDD cell that does not support RedCap capability to the prohibited bar list when the cell search or cell reselection is performed on a TDD cell that does not support RedCap capability.

[0041] In some implementations, the aforementioned transceiver unit is also used to: receive system messages; and determine the aforementioned RedCap capability based on the system messages.

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

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

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

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

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

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

[0048] In some implementations, the computer-readable storage medium can be a non-transitory computer-readable storage medium.

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

[0050] The communication device, computer-readable 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

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

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

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

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

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

[0056] Figure 5 A schematic diagram illustrating a cell classification method provided in an embodiment of this application;

[0057] Figure 6 A schematic diagram illustrating another cell classification method provided in this application embodiment;

[0058] Figure 7 A schematic diagram illustrating yet another cell classification method provided in this application embodiment;

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

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

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

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

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

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

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

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

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

[0068] 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 terminals 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.

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

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

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

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

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

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

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

[0076] 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:

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

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

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

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

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

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

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

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

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

[0086] Apart from Figure 3 The transmitter 306 and receiver 305 shown may be accompanied by other communication components in the terminal 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 300 may also support other wireless communication signals, such as satellite signals, shortwave signals, etc. In addition to wireless communication, the terminal 300 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.

[0087] The aforementioned input / output modules are 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.

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

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

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

[0091] It should be noted that, Figure 3 The terminal 300 shown is merely 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.

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

[0093] S401, Get the first list of cells.

[0094] Taking the RedCap terminal as an example, it can obtain the first cell list.

[0095] Specifically, the RedCap terminal is able to obtain the first cell list, which includes FDD cells.

[0096] Furthermore, RedCap terminals are also able to obtain a first cell list that includes both FDD and TDD cells.

[0097] Taking the eRedCap terminal as an example, it can obtain the first cell list.

[0098] Specifically, the eRedCap terminal can obtain the first cell list, which includes FDD cells.

[0099] Furthermore, the enhanced redcap terminal is also able to obtain a first cell list that includes both FDD and TDD cells.

[0100] The first list of cells mentioned above includes FDD cells and / or TDD cells.

[0101] The first cell list can be a cell search list or a cell reselection list.

[0102] FDD, or Frequency Division Duplex, is a technology that achieves full-duplex communication by allocating uplink and downlink frequencies to two different frequencies. The core of this technology lies in maintaining a specific frequency interval between the two frequencies, typically a pair of symmetrical frequency bands. FDD technology is well-suited for wireless communication systems that require a separate radio frequency channel for each user. In FDD mode, uplink and downlink signals are transmitted using different frequencies; the uplink uses a specific frequency, while the downlink uses a different frequency. This unique frequency allocation method effectively avoids mutual interference between uplink and downlink communications, thus significantly improving the stability and reliability of the entire communication system.

[0103] TDD, or Time Division Duplex, is a technology that achieves bidirectional communication by dividing time. In TDD mode, mobile communication systems utilize different time slots on the same frequency channel (carrier) for both receiving and transmitting, distinguishing between the receiving and transmitting channels by ensuring time separation. In a TDD mobile communication system, communication between network devices and terminals occurs on the same frequency channel, but reception and transmission are differentiated by different time slots. Specifically, during a specific time period, the network device sends signals to the terminal, while during a different time period, the terminal sends signals to the network device. This alternating transmission and reception pattern enables effective bidirectional communication between the two devices on the same channel, thereby improving communication efficiency and quality.

[0104] In some implementations, a second cell list can be obtained, which includes FDD cells and TDD cells; and a first cell list can be generated based on the second cell list, which includes FDD cells in the second cell list.

[0105] For example, the second cell list includes cells 1 to 10, where cells 5 and 8 in the second cell list are TDD cells, and the remaining cells in the second cell list (i.e., cells 1, 2, 3, 4, 6, 7, 9, and 10) are FDD cells. Then, the first cell list generated based on the second cell list includes cells 1, 2, 3, 4, 6, 7, 9, and 10.

[0106] Understandably, FDD cells typically have smaller bandwidths, while TDD cells generally have larger bandwidths. Given that smaller bandwidth cells are more suitable for RedCap terminal access compared to larger bandwidth cells, by retaining only FDD cells from the second cell list, TDD cells can be effectively excluded from the candidate cell pool. This ensures a higher success rate for RedCap terminals accessing the network after cell reselection, improving network efficiency and performance, by using only FDD cells as candidate cells.

[0107] S402. Determine the order of the first community list based on the community information.

[0108] In some implementations, the aforementioned cell information includes at least one of energy, signal-to-noise ratio, RedCap capability, bandwidth, or cell type.

[0109] In other implementations, the aforementioned cell information includes at least one of energy, signal-to-noise ratio, eRedCap capability, bandwidth, or cell type.

[0110] The cell order mentioned above refers to the cell search order or cell reselection order.

[0111] In some implementations, the aforementioned cell information includes energy, signal-to-noise ratio, RedCap capability, bandwidth, and cell type.

[0112] In cell ordering, cells that support RedCap capability are prioritized over cells that do not support RedCap capability but have a target bandwidth.

[0113] Cells that do not support RedCap capability but have target bandwidth are prioritized over non-target bandwidth FDD cells that do not support RedCap capability.

[0114] Non-target bandwidth FDD cells that do not support RedCap capability are prioritized over non-target bandwidth TDD cells that do not support RedCap capability.

[0115] The target bandwidth cell refers to a cell whose bandwidth is less than or equal to the set bandwidth threshold.

[0116] The target bandwidth can be set to 20 MHz.

[0117] For example, the first cell list includes cells 1 to 4. Cell 1 supports RedCap capability, while cells 2 to 4 do not support RedCap capability. The bandwidth of cell 2 is less than the target bandwidth, while the bandwidth of cells 3 and 4 is greater than the target bandwidth. Cell 3 is an FDD cell, and cell 4 is a TDD cell.

[0118] Since cells supporting RedCap capabilities should be prioritized over those that do not support RedCap capabilities but have target bandwidth, cell 1 should be placed before cells 2 to 4, meaning cell 1 should be at the top of the first cell list.

[0119] Meanwhile, cells that do not support RedCap capability but have target bandwidth should be prioritized over FDD cells that do not support RedCap capability and whose bandwidth is not target. Therefore, cell 2 should be ranked before cell 3 and cell 4, that is, cell 2 should be the second cell in the first cell list.

[0120] Finally, FDD cells that do not support RedCap capability and whose bandwidth is not the target should be prioritized over TDD cells that do not support RedCap capability and have non-target bandwidth. Therefore, cell 3 should be ranked before cell 4, that is, cell 3 should be the third cell in the first cell list, while cell 4 should be the fourth cell.

[0121] like Figure 5 As shown, based on the characteristics of RedCap technology, this solution can divide cells into two main categories: cells with RedCap technology capabilities and cells without RedCap technology capabilities. Given that cells with RedCap technology capabilities have a significant advantage in accessing RedCap terminals, these cells should be given priority when ranking cells, ensuring they are placed in the first cell list before cells without RedCap technology capabilities.

[0122] For cells lacking RedCap technical capabilities, this solution can further subdivide them based on their bandwidth. Specifically, these cells can be divided into two categories: one is non-target bandwidth cells with bandwidth exceeding a certain threshold, and the other is target bandwidth cells with bandwidth less than or equal to that threshold. Since cells with smaller bandwidth are more suitable for accessing RedCap terminals, target bandwidth cells should be prioritized over non-target bandwidth cells in the first cell list.

[0123] Furthermore, non-target bandwidth cells within cells lacking RedCap capability can be further categorized based on cell type. Specifically, these cells can be divided into non-target bandwidth FDD cells and non-target bandwidth TDD cells. Typically, FDD cells have smaller bandwidths, while TDD cells have larger bandwidths. Given that smaller bandwidth cells are more suitable for RedCap terminal access, non-target bandwidth FDD cells lacking RedCap capability should be listed before non-target bandwidth TDD cells lacking RedCap capability in the first cell list.

[0124] In other implementations, the aforementioned cell information includes energy, signal-to-noise ratio, eRedCap capability, bandwidth, and cell type.

[0125] In cell ordering, cells that support eRedCap capability are prioritized over cells that do not support eRedCap capability but have a target bandwidth.

[0126] Cells that do not support eRedCap capability but have target bandwidth are prioritized over non-target bandwidth FDD cells that do not support eRedCap capability.

[0127] Non-target bandwidth FDD cells that do not support eRedCap capability are prioritized over non-target bandwidth TDD cells that do not support eRedCap capability.

[0128] In some implementations, the aforementioned cell information includes energy, signal-to-noise ratio, RedCap capability, and cell type.

[0129] In the above cell order, cells supporting RedCap capability are ranked higher than FDD cells that do not support RedCap capability.

[0130] The order of FDD cells that do not support RedCap capability is higher than that of TDD cells that do not support RedCap capability.

[0131] like Figure 6 As shown, based on the characteristics of RedCap technology, this scheme can classify cells into cells with RedCap technology capabilities and cells without RedCap technology capabilities. Cells with RedCap technology capabilities are more suitable for RedCap terminal access due to their characteristics. Therefore, when ranking cells, those cells that support RedCap technology should be given priority, and their ranking in the first cell list should be higher than that of cells without RedCap technology capabilities.

[0132] For cells lacking RedCap technology capabilities, this solution can be further subdivided according to cell type, specifically into FDD cells that do not support RedCap technology and TDD cells that do not support RedCap technology. Typically, FDD cells have smaller bandwidth, while TDD cells have larger bandwidth. Since cells with smaller bandwidth have certain advantages in accessing RedCap terminals, when ranking cells, non-target bandwidth FDD cells lacking RedCap technology capabilities should be ranked higher, and their order in the first cell list should be higher than that of non-target bandwidth TDD cells lacking RedCap technology capabilities.

[0133] In some implementations, the aforementioned cell information includes energy, signal-to-noise ratio, eRedCap capability, and cell type.

[0134] In the above cell order, cells that support eRedCap capability are ranked higher than FDD cells that do not support eRedCap capability.

[0135] The order of FDD cells that do not support eRedCap capability is higher than that of TDD cells that do not support eRedCap capability.

[0136] In some implementations, the cell information mentioned above includes energy, signal-to-noise ratio, and cell type, and the order of FDD cells is higher than that of TDD cells in the cell order.

[0137] like Figure 7 As shown, based on cell type, this scheme can classify cells into two main categories: FDD cells and TDD cells. Typically, FDD cells are designed with smaller bandwidths, while TDD cells tend to use larger bandwidths. This bandwidth difference leads to an interesting phenomenon: in FDD cells with smaller bandwidths, RedCap terminal access is smoother and more efficient. Therefore, when formulating the first cell list, this scheme should take this into account, setting a higher priority for FDD cells than for TDD cells to ensure the rational allocation of network resources and maximize their utilization efficiency.

[0138] In some implementations, system messages can be received; the RedCap capabilities mentioned above can be determined based on these system messages.

[0139] Taking a RedCap terminal as an example, it can receive SIB4 messages from the network equipment corresponding to the cell. Once the SIB4 is obtained, the terminal will analyze its content in detail to assess whether the cell supports RedCap technology. Specifically, the terminal will search the SIB4 message for specific field identifiers, such as "redCapAccessAllowed-r17". If this field exists, it can be confirmed that the cell supports RedCap technology and has the corresponding network functions. If it does not exist, it indicates that the cell does not support RedCap technology and lacks the corresponding network capabilities.

[0140] In some other implementations, system messages can be received; the eRedCap capability can be determined based on these system messages.

[0141] Taking an eRedCap terminal as an example, it can receive SIB4 messages from the network equipment corresponding to the cell. Once the SIB4 is obtained, the terminal will analyze its content in detail to assess whether the cell supports RedCap technology. Specifically, the terminal will search the SIB4 message for specific field identifiers, such as "eRedCapAccessAllowed-r18". If this field exists, it can be confirmed that the cell supports RedCap technology and has the corresponding network functions. If it does not exist, it indicates that the cell does not support RedCap technology and lacks the corresponding network capabilities.

[0142] Understandably, System Information Blocks (SIBs) play a crucial role in communication systems. System messages ensure that terminals can correctly access the network and provide necessary system configuration information, thereby guaranteeing the normal operation of the terminal and the realization of communication functions. Therefore, RedCap terminals can use system messages (such as SIB1) to determine whether a cell has RedCap capability, which is a crucial step. Only when the terminal recognizes that the cell supports RedCap technology can it perform the corresponding configuration and optimization to adapt to the network environment and ensure the efficiency and stability of data transmission.

[0143] S403. Perform cell search or cell reselection according to the cell order in the first cell list.

[0144] In some implementations, if a first type of cell is found during the reselection evaluation process and the first type of cell does not exist in the first cell list, the first type of cell can be added to the first cell list. The first type of cell includes cells that support RedCap capability, target bandwidth cells that do not support RedCap capability, and non-target bandwidth FDD cells that do not support RedCap capability.

[0145] Understandably, Type 1 cells are more suitable for RedCap terminal access because their specific configurations and characteristics allow them to better meet the access requirements of RedCap terminals. If a Type 1 cell is not currently in the list of Type 1 cells, it may indicate that the cells in the list are not entirely suitable for RedCap terminal access. Therefore, during the reselection evaluation process, once a more suitable Type 1 cell for RedCap terminal access is found, it should be added to the list of Type 1 cells. This allows RedCap terminals to access the newly discovered Type 1 cell, thereby improving network performance and user experience.

[0146] In some implementations, if a second type of cell is found during the reselection evaluation process and the second type of cell does not exist in the first cell list, the second type of cell can be added to the first cell list. The second type of cell includes cells that support RedCap capability and FDD cells that do not support RedCap capability.

[0147] Understandably, the second type of cell is more suitable for RedCap terminal access because its specific configuration and characteristics better meet the needs of RedCap terminals. The absence of a second type of cell in the first cell list indicates that the cells currently in the first cell list are not suitable for RedCap terminal access. Therefore, during the reselection evaluation process, once a second type of cell more suitable for RedCap terminal access is found, it should be added to the first cell list. This ensures that RedCap terminals can access the newly found second type of cell, thereby improving network efficiency and terminal performance.

[0148] In some implementations, if a third type of cell is found during the reselection evaluation process and the third type of cell does not exist in the first cell list, the third type of cell can be added to the first cell list. The third type of cell includes FDD cells.

[0149] Understandably, third-type cells are more suitable for RedCap terminal access because they possess specific network characteristics that better meet their access requirements. When a third-type cell is missing from the first cell list, it indicates that the cells currently in the first cell list are not suitable for RedCap terminal access. Therefore, during the reselection evaluation process, if a more suitable third-type cell for RedCap terminal access is found, it can be added to the first cell list. This allows the RedCap terminal to utilize the newly found access point, i.e., the third-type cell, for more efficient network access.

[0150] In some implementations, if a TDD cell that does not support RedCap capability is found during cell search or cell reselection, the aforementioned TDD cell that does not support RedCap capability can be added to the prohibited bar list.

[0151] Understandably, TDD cells typically have large bandwidth, making them less suitable for RedCap terminals. Therefore, to ensure RedCap terminals can effectively camp on cells that support their capabilities, it is recommended to add TDD cells that do not support RedCap capabilities to the prohibited camping list. This measure effectively prevents RedCap terminals from mistakenly selecting TDD cells that do not support their specific functions during cell reselection or access, thereby ensuring terminal performance and network stability.

[0152] As can be seen from S401 to S403, compared to the traditional method of sorting cells in the first cell list solely based on energy and signal-to-noise ratio, the scheme proposed in this application further incorporates three additional factors—RedCap capability, bandwidth, and cell type—when sorting cells. By comprehensively evaluating these factors, the RedCap terminal can prioritize cells with higher RedCap capability, larger bandwidth, and more suitable cell types in the first cell list. Therefore, during cell search or reselection, the RedCap terminal can preferentially select cells ranked higher in the first cell list to complete the access operation. The implementation of this scheme effectively reduces cell access latency and improves network access efficiency.

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

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

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

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

[0157] Figure 8 The diagram illustrates a possible configuration of the communication device involved in the above embodiments. This device can 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. Figure 8 As shown, the communication device 800 may include a transceiver unit 801 and a processing unit 802.

[0158] The transceiver unit 801 is used to obtain a first cell list, which includes FDD cells and / or TDD cells, and is a cell search list or a cell reselection list.

[0159] The processing unit 802 is configured to determine the cell order of the first cell list based on cell information, wherein the cell information includes at least one of energy, signal-to-noise ratio, RedCap capability, bandwidth or cell type, and the cell order is either the cell search order or the cell reselection order.

[0160] The aforementioned processing unit 802 is also used to perform cell search or cell reselection according to the aforementioned cell order.

[0161] In some implementations, the cell information includes energy, signal-to-noise ratio, RedCap capability, bandwidth, and cell type. In the cell order, cells supporting RedCap capability are ranked higher than target bandwidth cells that do not support RedCap capability. Target bandwidth cells that do not support RedCap capability are ranked higher than non-target bandwidth FDD cells that do not support RedCap capability. Non-target bandwidth FDD cells that do not support RedCap capability are ranked higher than non-target bandwidth TDD cells that do not support RedCap capability. The target bandwidth cell is a cell with bandwidth less than or equal to a bandwidth threshold.

[0162] In some implementations, the processing unit 802 is further configured to: add the first type of cell to the first cell list when a first type of cell is found during the reselection evaluation process and the first type of cell does not exist in the first cell list. The first type of cell includes cells that support RedCap capability, target bandwidth cells that do not support RedCap capability, and non-target bandwidth FDD cells that do not support RedCap capability.

[0163] In some implementations, the cell information includes energy, signal-to-noise ratio, RedCap capability, and cell type. In the cell order, cells supporting RedCap capability are ranked higher than FDD cells that do not support RedCap capability, and FDD cells that do not support RedCap capability are ranked higher than TDD cells that do not support RedCap capability.

[0164] In some implementations, the processing unit 802 is further configured to: add the second type of cell to the first cell list when a second type of cell is found during the reselection evaluation process and the second type of cell does not exist in the first cell list; the second type of cell includes cells that support RedCap capability and FDD cells that do not support RedCap capability.

[0165] In some implementations, the cell information mentioned above includes energy, signal-to-noise ratio, and cell type, and the order of FDD cells is higher than that of TDD cells in the cell order.

[0166] In some implementations, the processing unit 802 is further configured to: add the third type of cell to the first cell list when a third type of cell is found during the reselection evaluation process and the third type of cell does not exist in the first cell list, wherein the third type of cell includes FDD cells.

[0167] In some implementations, the transceiver unit 801 is further configured to: obtain a second cell list, the second cell list including FDD cells and TDD cells; generate the first cell list based on the second cell list, the first cell list including FDD cells in the second cell list.

[0168] In some implementations, the processing unit 802 is further configured to: add the TDD cell that does not support RedCap capability to the prohibited bar list when the cell search or cell reselection is performed on a TDD cell that does not support RedCap capability.

[0169] In some implementations, the transceiver unit 801 is further configured to: receive system messages; and determine the RedCap capability based on the system messages.

[0170] This application also provides a chip, which can be the chip of the above-mentioned communication device. Figure 9 A schematic diagram of a chip 900 is shown. The chip 900 includes one or more processors 901 and interface circuitry 902. Optionally, the chip 900 may also include a bus 903.

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

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

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

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

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

[0176] Optionally, the chip can be used in the communication device or communication device involved in the embodiments of this application. Optionally, the interface circuit 902 can be used to output the execution result of the processor 901. 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.

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

[0178] Figure 10 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 10 As shown, the electronic device 1000 includes a processor 1001, a transceiver 1002, and a communication line 1003.

[0179] The processor 1001 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 1002 and the communication line 1003 to complete the corresponding operation.

[0180] Furthermore, the electronic device 1000 may also include a memory 1004. The processor 1001, the memory 1004, and the transceiver 1002 can be connected via a communication line 1003.

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

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

[0183] The transceiver 1002 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.

[0184] Communication line 1003 is used to transmit information between the various components included in electronic device 1000.

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

[0186] Memory 1004 is used to store instructions. These instructions can be computer programs.

[0187] The memory 1004 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 (DRRAM). Memory 1004 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.

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

[0189] In one example, processor 1001 may include one or more processor cores, for example Figure 10 The processor cores are 0 and 1.

[0190] As an optional implementation, the electronic device 1000 includes multiple processors, for example, besides Figure 10 In addition to processor 1001, it may also include processor 1007.

[0191] As an optional implementation, the electronic device 1000 also includes an output device 1005 and an input device 1006. For example, the input device 1006 is a device such as a keyboard, mouse, microphone, or joystick, and the output device 1005 is a device such as a display screen or speaker.

[0192] It should be noted that the electronic device 1000 can be a chip system or... Figure 10 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 10 The structural composition shown herein does not constitute a limitation on the electronic device 1000, except... Figure 10 In addition to the components shown, the electronic device 1000 may include more than Figure 10 This may indicate more or fewer components, or combinations of certain components, or different component arrangements.

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

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

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

[0196] This application also provides a computer-readable 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.

[0197] In some implementations, the aforementioned computer-readable storage medium can be a non-transitory computer-readable storage medium, which may include non-volatile media such as ROM, or certain volatile media such as some RAM.

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

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

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

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

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

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

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

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

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

[0207] 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: Obtain a first cell list, which includes frequency division duplex (FDD) cells and / or time division duplex (TDD) cells. The first cell list is a cell search list or a cell reselection list. The cell order of the first cell list is determined based on cell information, which includes at least one of energy, signal-to-noise ratio, RedCap capability, bandwidth, or cell type. The cell order is either the cell search order or the cell reselection order. Cell search or cell reselection is performed according to the cell order.

2. The method according to claim 1, characterized in that, The cell information includes energy, signal-to-noise ratio, RedCap capability, bandwidth, and cell type. In the cell order, cells supporting RedCap capability are ranked higher than target bandwidth cells that do not support RedCap capability. Target bandwidth cells that do not support RedCap capability are ranked higher than non-target bandwidth FDD cells that do not support RedCap capability. Non-target bandwidth FDD cells that do not support RedCap capability are ranked higher than non-target bandwidth TDD cells that do not support RedCap capability. The target bandwidth cell is a cell with bandwidth less than or equal to a bandwidth threshold.

3. The method according to claim 2, characterized in that, The method further includes: If a cell of the first type is found during the reselection evaluation process and the cell of the first type does not exist in the cell list, the cell of the first type is added to the cell list. The cell of the first type includes cells that support RedCap capability, target bandwidth cells that do not support RedCap capability, and non-target bandwidth FDD cells that do not support RedCap capability.

4. The method according to claim 1, characterized in that, The cell information includes energy, signal-to-noise ratio, RedCap capability, and cell type. In the cell order, cells that support RedCap capability are ranked higher than FDD cells that do not support RedCap capability, and FDD cells that do not support RedCap capability are ranked higher than TDD cells that do not support RedCap capability.

5. The method according to claim 4, characterized in that, The method further includes: If a second type of cell is found during the reselection evaluation process and the second type of cell does not exist in the first cell list, the second type of cell is added to the first cell list. The second type of cell includes cells that support RedCap capability and FDD cells that do not support RedCap capability.

6. The method according to claim 1, characterized in that, The cell information includes energy, signal-to-noise ratio, and cell type, and the cell order is FDD cells in higher order than TDD cells.

7. The method according to claim 6, characterized in that, The method further includes: If a third type of cell is found during the reselection evaluation process and the third type of cell does not exist in the first cell list, the third type of cell is added to the first cell list. The third type of cell includes FDD cells.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Obtain the second cell list, which includes FDD cells and TDD cells; The first cell list is generated based on the second cell list, and the first cell list includes FDD cells in the second cell list.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: If a TDD cell that does not support RedCap capability is found during cell search or cell reselection, the TDD cell that does not support RedCap capability will be added to the prohibited bar list.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: Receive system messages; The RedCap capability is determined based on the system message.

11. A communication device, characterized in that, include: Transceiver unit and processing unit; The transceiver unit is used to obtain a first cell list, which includes FDD cells and / or TDD cells. The first cell list is a cell search list or a cell reselection list. The processing unit is configured to determine the cell order of the first cell list based on cell information, wherein the cell information includes at least one of energy, signal-to-noise ratio, RedCap capability, bandwidth, or cell type, and the cell order is either the cell search order or the cell reselection order. The processing unit is also used to perform cell search or cell reselection according to the cell order.

12. The apparatus according to claim 11, characterized in that, The cell information includes energy, signal-to-noise ratio, RedCap capability, bandwidth, and cell type. In the cell order, cells supporting RedCap capability are ranked higher than target bandwidth cells that do not support RedCap capability. Target bandwidth cells that do not support RedCap capability are ranked higher than non-target bandwidth FDD cells that do not support RedCap capability. Non-target bandwidth FDD cells that do not support RedCap capability are ranked higher than non-target bandwidth TDD cells that do not support RedCap capability. The target bandwidth cell is a cell with bandwidth less than or equal to a bandwidth threshold.

13. The apparatus according to claim 12, characterized in that, The processing unit is also used for: If a cell of the first type is found during the reselection evaluation process and the cell of the first type does not exist in the cell list, the cell of the first type is added to the cell list. The cell of the first type includes cells that support RedCap capability, target bandwidth cells that do not support RedCap capability, and non-target bandwidth FDD cells that do not support RedCap capability.

14. The apparatus according to claim 11, characterized in that, The cell information includes energy, signal-to-noise ratio, RedCap capability, and cell type. In the cell order, cells that support RedCap capability are ranked higher than FDD cells that do not support RedCap capability, and FDD cells that do not support RedCap capability are ranked higher than TDD cells that do not support RedCap capability.

15. The apparatus according to claim 14, characterized in that, The processing unit is also used for: If a second type of cell is found during the reselection evaluation process and the second type of cell does not exist in the first cell list, the second type of cell is added to the first cell list. The second type of cell includes cells that support RedCap capability and FDD cells that do not support RedCap capability.

16. The apparatus according to claim 11, characterized in that, The cell information includes energy, signal-to-noise ratio, and cell type, and the cell order is FDD cells in higher order than TDD cells.

17. The apparatus according to claim 16, characterized in that, The processing unit is also used for: If a third type of cell is found during the reselection evaluation process and the third type of cell does not exist in the first cell list, the third type of cell is added to the first cell list. The third type of cell includes FDD cells.

18. The apparatus according to any one of claims 11 to 17, characterized in that, The transceiver unit is also used for: Obtain the second cell list, which includes FDD cells and TDD cells; The first cell list is generated based on the second cell list, and the first cell list includes FDD cells in the second cell list.

19. The apparatus according to any one of claims 11 to 18, characterized in that, The processing unit is also used for: If a TDD cell that does not support RedCap capability is found during cell search or cell reselection, the TDD cell that does not support RedCap capability will be added to the prohibited bar list.

20. The apparatus according to any one of claims 11 to 19, characterized in that, The transceiver unit is also used for: Receive system messages; The RedCap capability is determined based on the system message.

21. 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 10.

22. 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 10.

23. 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 10.

Images