Communication control method, electronic device and system

Abstract

Disclosed in the embodiments of the present application are a communication control method, an electronic device and a system. The method is applied to a communication system comprising a terminal device, a network device and a server. The method comprises: a terminal device receiving a system message of a cell a that is sent by a network device, wherein the system message comprises indication information of whether the cell a supports RedCap; the terminal device recording cell information of RedCap cells and non-RedCap cells in the cell a, so as to obtain a list A; the terminal device uploading the list A and the position of the terminal device to a server; on the basis of the position of the terminal device, downloading, from the server, cell information of RedCap cells and / or non-RedCap cells in a cell b, so as to obtain a list B; and on the basis of the list A and the list B, the terminal device obtaining a list C, such that a RedCap terminal disables the non-RedCap cells on the basis of the list C. Therefore, it is ensured that the RedCap terminal does not access the non-RedCap cells, thereby improving the data service experience of a user.

Description

A communication control method, electronic device and system

[0001] This application claims priority to Chinese Patent Application No. 202411181226.6, filed with the State Intellectual Property Office of China on August 26, 2024, entitled "A Communication Control Method, Electronic Device and System", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication technology, and in particular to a communication control method, electronic device and system. Background Technology

[0003] New Radio (NR) networks offer advantages such as high bandwidth, high speed, wide connectivity, and low latency. However, in some application scenarios, they can suffer from capacity overflow and excessive costs. The 3GPP wireless communication standard, in Release 17, proposed a fifth-generation mobile communication technology (the 5G...). th Generation 5G (reduced capability, RedCap) terminals can balance terminal hardware cost, design complexity, power consumption and performance requirements.

[0004] According to the provisions of existing communication protocols such as 3GPP TS38.331, RedCap terminals can only camp on NR cells that support RedCap (i.e., RedCap cells), and cannot camp on ordinary NR cells that do not support RedCap (i.e., non-RedCap cells). However, because the protocol version corresponding to RedCap is relatively high, and network deployment and coverage are still in their early stages, networks with different version capabilities include both RedCap and non-RedCap cells. RedCap terminals may access non-RedCap cells, resulting in a poor data service experience for users. Therefore, ensuring that RedCap terminals do not access non-RedCap cells is particularly important. Summary of the Invention

[0005] This application provides a communication control method, electronic device, and system. The method can be applied to a communication system including a terminal device, a network device, and a server. During cell search, the terminal device can receive a system message for cell a sent by the network device. This system message includes an indication of whether cell a supports RedCap. Then, the terminal device can record the cell information of cells in cell a that support RedCap and those that do not, obtaining a list A. Next, the terminal device can upload list A and its location to the server, and download the cell information of cells in cell b that support RedCap and / or those that do not, based on the terminal device's location, obtaining a list B. Finally, the terminal device can obtain a list C based on lists A and B, enabling RedCap terminals to disable non-RedCap cells according to list C, thereby ensuring that RedCap terminals do not access non-RedCap cells and improving the user's data service experience.

[0006] In a first aspect, this application provides a communication control method applied to a first terminal device, the first terminal device being a RedCap-reduced terminal device. The method includes: receiving a measurement configuration sent by a first network device, the measurement configuration being used to instruct the first terminal device to measure the signal quality of candidate cells; determining whether there are any cells among the candidate cells that do not support RedCap, and if so, not measuring the signal quality of cells that do not support RedCap; the cells that do not support RedCap are cells that the first terminal device has never accessed.

[0007] The first terminal device can be a terminal device 500 that supports RedCap, and the first network device can be a network device 300.

[0008] By implementing the method provided in the first aspect, the first terminal device can avoid measuring the signal quality of cells that do not support RedCap based on prior information, thereby avoiding the first terminal device from switching to cells that do not support RedCap, and eliminating the need for a RedCap terminal to have accessed a non-RedCap cell before disabling the non-RedCap cell, thus improving the user's data service experience.

[0009] In conjunction with the first aspect, in some embodiments, determining whether there are cells among the candidate cells that do not support RedCap specifically includes: determining whether there are cells among the candidate cells that do not support RedCap based on a first list, wherein the first list is used to record cells that do not support RedCap.

[0010] The first list can be list C, list A, or list B.

[0011] It is understood that the first terminal device can not only obtain cell information of cells that support RedCap and / or cells that do not support RedCap through the first list, and then determine whether there are cells that do not support RedCap among the candidate cells based on the first list, but also obtain cell information of cells that support RedCap and / or cells that do not support RedCap through databases, cloud servers, etc. This application embodiment does not limit this.

[0012] In conjunction with the first aspect, in some embodiments, the method further includes: receiving system messages from one or more candidate cells, wherein a system message from a candidate cell includes first indication information as to whether a candidate cell supports RedCap; and updating a first list based on the first indication information.

[0013] For example, during cell search by the first terminal device, the first terminal device can receive system messages of one or more candidate cells sent by the first network device. A system message for a candidate cell may include first indication information regarding whether the candidate cell supports RedCap. After receiving the system messages of one or more candidate cells sent by the first network device, the first terminal device can identify whether the candidate cell supports RedCap through the RedCap-related information elements in the system messages, and record the cell information of cells supporting RedCap and cells not supporting RedCap among the one or more candidate cells, updating the first list. As another example, during interoperation (e.g., cell handover, cell reselection, cell redirection) to the target cell by the first terminal device, the first terminal device can receive system messages of one or more candidate cells sent by the first network device. A system message for a candidate cell may include first indication information regarding whether the candidate cell supports RedCap. After receiving the system messages of one or more candidate cells sent by the first network device, the first terminal device can add the cell information, such as the first indication information regarding whether RedCap is supported, from the received system messages of one or more candidate cells to the first list, thereby updating the first list.

[0014] In conjunction with the first aspect, in some embodiments, the measurement configuration includes second indication information as to whether the candidate cell supports RedCap; the method further includes updating the first list based on the second indication information.

[0015] For example, if the first network device adds a cell message indicating whether RedCap is supported to the neighbor cell relationship of the measurement configuration when sending the measurement configuration to the first terminal device, the first terminal device can add cell information such as the cell message indicating whether RedCap is supported in the neighbor cell relationship of the received measurement configuration to the first list to update the first list.

[0016] In conjunction with the first aspect, in some embodiments, the method further includes uploading a first list to a first server.

[0017] The first server can be server 400.

[0018] For example, when an update to the first list is detected, the first terminal device can upload the updated first list to the first server.

[0019] In conjunction with the first aspect, in some embodiments, the first list is downloaded from a first server, and the first list is extracted by the first server from a second list based on the location of the first terminal device. The second list is generated based on cell information of cells that do not support RedCap uploaded by terminal devices at multiple locations.

[0020] In conjunction with the first aspect, in some embodiments, the method further includes: measuring the signal quality of a RedCap-supporting cell among candidate cells; returning a measurement report to a first network device, the measurement report being used to provide feedback on the signal quality of the RedCap-supporting cell; and receiving a cell handover signaling sent by the first network device, the cell handover signaling being used to instruct the first terminal device to hand over to a target cell, the target cell being a RedCap-supporting cell.

[0021] In conjunction with the first aspect, in some embodiments, the method further includes: during the cell search process, determining whether the candidate cell obtained through the cell search is a cell that does not support RedCap; if so, then not deciphering the system message of the cell that does not support RedCap.

[0022] For example, the first terminal device can match the cell information obtained through cell search with the cell information of cells that do not support RedCap in the first list. If the match is successful, the first terminal device can ignore the system messages of cells that do not support RedCap, so that the first terminal device does not camp on cells that do not support RedCap. It is understood that the first terminal device can not only obtain cell information of cells that support RedCap and / or cells that do not support RedCap through the first list, and then determine whether the candidate cells obtained through cell search are cells that do not support RedCap based on the first list, but also obtain cell information of cells that support RedCap and / or cells that do not support RedCap through databases, cloud servers, etc. This application embodiment does not limit this.

[0023] Secondly, this application provides a communication control method applied to a second terminal device, which is a non-RedCap terminal device. The method includes: when a service lag is detected, determining whether the serving cell where the second terminal device is located is a RedCap-supporting cell according to a first list; if so, performing cell reselection based on the RedCap-unsupporting cells recorded in the first list. The first list is used to record RedCap-supporting cells and RedCap-unsupporting cells.

[0024] The second terminal device can be a terminal device 600 that does not support RedCap, and the first list can be list C, list A, or list B.

[0025] By implementing the method provided in the second aspect, if multiple (e.g., 5) service interruptions are identified (e.g., the service resource scheduling rate is less than 80%) and the currently camped cell is determined to be a RedCap-supporting cell according to the first list, the second terminal device can perform cell reselection based on the RedCap-unsupporting cells recorded in the first list.

[0026] For example, the second terminal device can match the cell information of the serving cell where the second terminal device is located with the cell information of the cells that support RedCap in the first list. If the match is successful, the second terminal device can perform cell reselection based on the cells that do not support RedCap recorded in the first list, so that the second terminal device can camp on the cells that do not support RedCap.

[0027] In conjunction with the second aspect, in some embodiments, cell reselection is performed based on cells that do not support RedCap as recorded in the first list. Specifically, this includes: scoring the cells that do not support RedCap as recorded in the first list; the more bandwidth resources a cell that does not support RedCap has, the higher its score; and accessing the cell that does not support RedCap with the highest score.

[0028] For example, the second terminal device can score the cell that does not support RedCap recorded in the first list in the cell search results higher than the cell that supports RedCap, and the more bandwidth resources the cell that does not support RedCap has, the higher its score; the second terminal device can access the cell that does not support RedCap with the highest score.

[0029] Thirdly, this application provides a communication control method applied to a first network device. The method includes: during the process of a first terminal device accessing the first network device, learning that the first terminal device supports RedCap; filtering out neighboring cell relationships that do not support RedCap from the neighboring cells of the serving cell where the first terminal device is located; and sending a measurement configuration to the first terminal device based on the filtered neighboring cell relationships, wherein the measurement configuration is used to instruct the first terminal device to measure the signal quality of the cell that supports RedCap.

[0030] The first terminal device can be a terminal device 500 that supports RedCap, and the first network device can be a network device 300.

[0031] By implementing the method provided in the third aspect, the first network device can avoid sending measurement configurations for cells that do not support RedCap to the first terminal device, thereby preventing the first terminal device from measuring cells that do not support RedCap and thus preventing the first terminal device from switching to cells that do not support RedCap.

[0032] In conjunction with the third aspect, in some embodiments, the method further includes: receiving a measurement report sent by a first terminal device, the measurement report being used to provide feedback on the signal quality of a cell supporting RedCap; making a decision based on the measurement report, selecting the cell supporting RedCap with the best signal quality in the measurement report as the target cell; and sending a cell handover signaling to the first terminal device, the cell handover signaling being used to instruct the first terminal device to hand over to the target cell.

[0033] Fourthly, this application provides a communication system, which includes a terminal device and a network device; wherein, there is a communication connection between the terminal device and the network device; the terminal device is an electronic device as described in any one of the first or second aspects above, and the network device is an electronic device as described in any one of the third aspects above.

[0034] Fifthly, this application provides a terminal device, which includes a processor and a memory; wherein the memory is coupled to the processor and is used to store a computer program, and when the processor executes the computer program, the terminal device performs the method of either the first or second aspect described above.

[0035] Sixthly, this application provides a network device, which includes a processor and a memory; wherein the memory is coupled to the processor and is used to store a computer program, and when the processor executes the computer program, the network device performs the method described in any of the third aspects above.

[0036] In a seventh aspect, this application provides a computer-readable storage medium storing a computer program that is executed by a processor to implement the method described in any one of the first to third aspects.

[0037] Eighthly, this application provides a computer program product that, when executed by a processor, implements the method described in any one of the first to third aspects described above.

[0038] Ninthly, this application provides a chip including a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, causing the chip to perform the method described in any one of the first to third aspects above.

[0039] The solutions provided in aspects four through nine above are used to implement or cooperate with the methods provided in aspect one above. Therefore, they can achieve the same or corresponding beneficial effects as the methods in aspects one through three above, which will not be elaborated here. Attached Figure Description

[0040] Figure 1A is a schematic diagram of a wireless communication system 100 provided in an embodiment of this application;

[0041] Figure 1B is a schematic diagram of the system architecture of a terminal device 200 provided in an embodiment of this application;

[0042] Figure 2A is a structural schematic diagram of a terminal device 200 provided in an embodiment of this application;

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

[0044] Figure 2C is a schematic diagram of the structure of a server 400 provided in an embodiment of this application;

[0045] Figure 3 is a flowchart illustrating a list acquisition method provided in an embodiment of this application;

[0046] Figure 4 is a flowchart illustrating a method for a RedCap terminal to avoid camping on a non-RedCap cell according to a list, provided in an embodiment of this application.

[0047] Figure 5 is a flowchart illustrating a method for preventing a RedCap terminal from switching to a non-RedCap cell, provided in an embodiment of this application.

[0048] Figure 6 is a flowchart illustrating a method for a non-RedCap terminal to select non-RedCap cells based on a list, according to an embodiment of this application.

[0049] Figure 7 is a flowchart illustrating a method for preventing RedCap terminals from switching to non-RedCap cells on the network side, as provided in an embodiment of this application.

[0050] Figure 8 is a flowchart illustrating a communication control method applied to a terminal device 500 according to an embodiment of this application;

[0051] Figure 9 is a flowchart illustrating a communication control method applied to a terminal device 600 according to an embodiment of this application;

[0052] Figure 10 is a flowchart illustrating a communication control method applied to a network device 300 according to an embodiment of this application. Detailed Implementation

[0053] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be a limitation of this application.

[0054] New Radio (NR) networks offer advantages such as high bandwidth, high speed, wide connectivity, and low latency. However, in some application scenarios, they can suffer from capacity overflow and excessive costs. The 3GPP wireless communication standard, in Release 17, proposed a fifth-generation mobile communication technology (the 5G...). th Generation 5G (reduced capability, RedCap) terminals can balance terminal hardware cost, design complexity, power consumption and performance requirements.

[0055] According to the provisions of existing communication protocols such as 3GPP TS38.331, RedCap terminals can only camp on NR cells that support RedCap (i.e., RedCap cells), and cannot camp on ordinary NR cells that do not support RedCap (i.e., non-RedCap cells). However, because the protocol version corresponding to RedCap is relatively high, and network deployment and coverage are still in their early stages, networks with different version capabilities include both RedCap and non-RedCap cells. RedCap terminals may access non-RedCap cells, resulting in a poor data service experience for users. Therefore, ensuring that RedCap terminals do not access non-RedCap cells is particularly important.

[0056] Currently, during interoperation (e.g., cell handover, cell reselection, cell redirection) between a RedCap terminal and any NR cell, if the RedCap terminal identifies that the cell does not support RedCap, it can add the cell to a locally maintained prohibited access list. If the target cell is subsequently identified as being on this prohibited access list, the RedCap terminal can disable that cell. For example, during cell handover, cell reselection, or cell redirection, the RedCap terminal can avoid interoperating with non-RedCap cells by not reporting measurement reports of disabled cells.

[0057] However, the above method has the following drawbacks: 1. The cell can only be disabled after the RedCap terminal fails to interoperate with a non-RedCap cell once; 2. According to the 3GPP protocol, the terminal identifies whether the cell supports RedCap by using RedCap-related information elements (such as redCap-ConfigCommon-r17) in the cell's system message SIB1. During cell handover, the terminal first camps on the target cell and can only subsequently decode the target cell's system message. Therefore, it is possible that the target cell does not support RedCap, but the RedCap terminal can only confirm that the target cell is a non-RedCap cell after camping on the target cell; 3. When the terminal initially accesses the source cell, it will report to the network whether it supports RedCap (i.e., whether it is a RedCap terminal). After the terminal interoperates with the target cell, due to the network capability transfer problem, the target cell may not be aware of whether the terminal supports RedCap, and therefore may interoperate the RedCap terminal with a non-RedCap cell.

[0058] To address the aforementioned issues, this application provides a communication control method, electronic device, and system. This method can be applied to a communication system including a terminal device, a network device, and a server. During cell search, the terminal device receives a system message for cell a from the network device. This system message includes an indication of whether cell a supports RedCap. Then, the terminal device records the cell information of cells in cell a that support RedCap and those that do not, obtaining a list A. Next, the terminal device uploads list A and its location to the server, and downloads the cell information of cells in cell b that support RedCap and / or do not support RedCap from the server based on its location, obtaining a list B. Finally, the terminal device obtains a list C based on lists A and B, enabling RedCap-supporting terminal devices to disable cells that do not support RedCap based on list C. These non-RedCap cells are cells that RedCap-supporting terminal devices have not previously accessed, thus ensuring that RedCap terminals can avoid accessing non-RedCap cells based on prior information, without requiring RedCap terminals to have accessed a non-RedCap cell before disabling it, thereby improving the user's data service experience.

[0059] In this embodiment, cell a can be one or more candidate cells searched by the terminal device in the network device, and cell b can be a cell stored in the server whose location corresponds to the terminal device's current location. The cell information recorded in list C can include the cell information recorded in list A and list B. In some embodiments, when the terminal device moves within an area, the location of cell a obtained through cell search is the same as the location of the terminal device. In this case, cell b can include cell a; or, cell b can be equivalent to cell a. In other embodiments, when the terminal device moves from one area to another, cells a and cell b may overlap, meaning that some cells in cell a and some cells in cell b may be the same; or, cell a can include cell b. For example, if the terminal device moves from location 1 to location 2, where location 1 and location 2 are adjacent areas, the location of cell a includes both location 1 and location 2, and the terminal device is located at location 2, then the location of cell b is also location 2. It is easy to understand that cells a and cell b overlap, and this overlapping portion is the cell in cell a located at location 2.

[0060] In some embodiments, if the terminal device supports RedCap, the terminal device can download cell information of cells that do not support RedCap from the server according to the location of the terminal device, and obtain list B. Further, the terminal device can obtain list C based on the aforementioned list A and list B, so that the terminal device supporting RedCap can disable cells that do not support RedCap according to list C which records cell information of cells that do not support RedCap, thereby ensuring that the terminal device supporting RedCap does not access cells that do not support RedCap.

[0061] In other embodiments, if the terminal device does not support RedCap, the terminal device can download information about RedCap-supporting and RedCap-non-supporting cells from the server based on its location, thus obtaining List B. Further, the terminal device can obtain List C based on List A and List B, so that if a terminal device that does not support RedCap identifies multiple (e.g., 5) service interruptions (e.g., the service resource scheduling rate is below 80%) and determines that the currently camped cell is a RedCap-supporting cell based on List C, it can preferentially re-access a RedCap-non-supporting cell based on List C, which records information about RedCap-supporting and RedCap-non-supporting cells, thereby ensuring that a terminal device that does not support RedCap can access a RedCap-non-supporting cell.

[0062] It is understood that terminal devices can obtain cell information of RedCap-supporting cells and / or cells that do not support RedCap not only through the aforementioned List C, but also through databases, cloud servers, and other means. This application embodiment does not limit this.

[0063] First, we will introduce a communication system and related equipment provided in the embodiments of this application.

[0064] Figure 1A illustrates an exemplary wireless communication system 100 provided in an embodiment of this application.

[0065] As shown in Figure 1A, the wireless communication system 100 may include: a terminal device 200, a network device 300, and a server 400. The network device 300 is also referred to as the first network device, and the server 400 is also referred to as the first server.

[0066] In the wireless communication system 100, the terminal device 200 can establish a communication connection with the network device 300 or with the server 400.

[0067] The terminal device 200 can be any type of smart terminal device, and this application embodiment does not limit the specific type of the terminal device 200. For example, the terminal device 200 can be a mobile phone, a mobile tablet computer, an in-vehicle tablet computer, a watch, etc. In this application embodiment, the terminal device 200 can obtain List C, which can be used to record cell information of cells that support RedCap and / or cells that do not support RedCap, so that the terminal device that supports RedCap can disable cells that do not support RedCap according to List C, which are cells that the terminal device that supports RedCap has never accessed; or, so that the terminal device that does not support RedCap can preferentially re-access cells that do not support RedCap according to List C when it identifies multiple (e.g., 5 times) service delays (e.g., the service resource scheduling rate is less than 80%) and determines that the currently camped cell is a cell that supports RedCap according to List C. Specifically, during the cell search process, terminal device 200 can receive a system message for cell a sent by network device 300. This system message includes an indication of whether cell a supports RedCap. Cell a can be one or more candidate cells searched by terminal device 200 in network device 300. Then, terminal device 200 can record the cell information of cells in cell a that support RedCap and those that do not, obtaining list A. Next, terminal device 200 can upload list A and its location to server 400, and download the cell information of cells in cell b that support RedCap and / or those that do not support RedCap from server 400 according to its location, obtaining list B. Cell b can be used for services... The location stored in device 400 is the cell where terminal device 200 is located. Finally, terminal device 200 can obtain list C based on list A and list B, so that RedCap-enabled terminal devices can disable RedCap-unsupported cells according to list C. These RedCap-unsupported cells are cells that RedCap-enabled terminal devices have never accessed. Alternatively, if a RedCap-unsupported terminal device identifies multiple (e.g., 5) service interruptions (e.g., the service resource scheduling rate is below 80%) and determines that the currently camped cell is a RedCap-enabled cell according to list C, it can preferentially re-access a RedCap-unsupported cell according to list C. The cell information recorded in list C can include the cell information recorded in list A and list B.

[0068] In this embodiment, the terminal device 200 may include a terminal device 500 that supports RedCap and a terminal device 600 that does not support RedCap. Terminal device 500 is also referred to as a first terminal device, and terminal device 600 is also referred to as a second terminal device.

[0069] In some embodiments, the terminal device 500 can avoid camping on cells that do not support RedCap according to List C. Specifically, during the cell search process, the terminal device 500 can determine whether the cell obtained through the cell search is a cell that does not support RedCap according to List C. If so, the terminal device 500 can avoid deciphering the system message of the cell that does not support RedCap, thereby avoiding camping on the cell that does not support RedCap.

[0070] In some embodiments, terminal device 500 can avoid measuring the signal quality of cells that do not support RedCap according to Listing C, thereby avoiding handover to cells that do not support RedCap. Specifically, terminal device 500 can receive a measurement configuration sent by network device 300, which can be used to instruct terminal device 500 to measure the signal quality of candidate cells; then, terminal device 500 can determine whether there are any cells that do not support RedCap among the candidate cells according to Listing C. If so, terminal device 500 can choose not to measure the signal quality of the cells that do not support RedCap, which are cells that terminal device 500 has not accessed before; next, terminal device 500 can measure the signal quality of cells that support RedCap among the candidate cells, and after measuring the signal quality of the cells that support RedCap, can return a measurement report to network device 300, which can be used to provide feedback on the signal quality of the cells that support RedCap; finally, terminal device 500 can receive cell handover signaling sent by network device 300, which can be used to instruct terminal device 500 to handover to a target cell, which is a cell that supports RedCap. In other embodiments, network device 300 may not send measurement configurations for cells that do not support RedCap to terminal device 500, thereby avoiding terminal device 500 measuring cells that do not support RedCap and thus avoiding terminal device 500 handing over to cells that do not support RedCap. Specifically, during the access process of network device 300, terminal device 500 may send a report to network device 300, which may contain indication information that terminal device 500 supports RedCap; then, terminal device 500 may receive measurement configurations sent by network device 300, which can be used to instruct terminal device 500 to measure the signal quality of candidate cells that support RedCap; next, terminal device 500 may measure the signal quality of cells that support RedCap, and after measuring the signal quality of cells that support RedCap, may return a measurement report to network device 300, which can be used to provide feedback on the signal quality of candidate cells that support RedCap; finally, terminal device 500 may receive cell handover signaling sent by network device 300, which can be used to instruct terminal device 500 to hand over to a target cell, which is a cell that supports RedCap.

[0071] In some embodiments, if multiple service interruptions are detected and the currently serving cell is determined to be a RedCap-supporting cell according to List C, the terminal device 600 can perform cell reselection according to List C to serve a cell that does not support RedCap. Specifically, if multiple (e.g., 5 times) service interruptions are detected (e.g., the service resource scheduling rate is below 80%), the terminal device 600 can determine whether the serving cell where the terminal device 600 is located is a RedCap-supporting cell according to List C. If so, the terminal device 600 can perform cell reselection based on the cells that do not support RedCap recorded in List C, so that the terminal device 600 serves a cell that does not support RedCap.

[0072] In this embodiment, network device 300 may be an NR network. During the process of terminal device 200 obtaining list C, network device 300 may send a system message for cell a to terminal device 200 during cell search. This system message includes indication information on whether cell a supports RedCap. Cell a may be one or more candidate cells searched by terminal device 200 in network device 300.

[0073] In some embodiments, terminal device 500 may avoid measuring the signal quality of cells that do not support RedCap, according to Listing C, thereby avoiding handover of terminal device 500 to cells that do not support RedCap. Specifically, network device 300 may send a measurement configuration to terminal device 500, which can be used to instruct terminal device 500 to measure the signal quality of candidate cells; then, network device 300 may receive a measurement report returned by terminal device 500, which can be used to provide feedback on the signal quality of cells that support RedCap; next, network device 300 may make a decision based on the measurement report and select the RedCap-supporting cell with the best signal quality as the target cell; finally, network device 300 may send cell handover signaling to terminal device 500, which can be used to instruct terminal device 500 to handover to the target cell. In other embodiments, network device 300 may not send a measurement configuration for cells that do not support RedCap to terminal device 500, thereby avoiding terminal device 500 measuring cells that do not support RedCap, and thus avoiding handover of terminal device 500 to cells that do not support RedCap. Specifically, network device 300 can receive a report sent by terminal device 500, which may contain indication information that terminal device 500 supports RedCap; secondly, network device 300 can filter out neighboring cells that do not support RedCap from the neighboring cells of the serving cell where terminal device 500 is located; then, network device 300 can send a measurement configuration to terminal device 500 based on the filtered neighboring cell relationships, which can be used to instruct terminal device 500 to measure the signal quality of RedCap-supporting cells among candidate cells; next, network device 300 can receive a measurement report returned by terminal device 500, which can be used to provide feedback on the signal quality of RedCap-supporting cells among candidate cells, and make a decision based on the measurement report, selecting the RedCap-supporting cell with the best signal quality as the target cell; finally, network device 300 can send cell handover signaling to terminal device 500, which can be used to instruct terminal device 500 to hand over to the target cell.

[0074] In this embodiment, server 400 can be a cloud server. During the process of terminal device 200 obtaining list C, server 400 can receive list A uploaded by terminal device 200 and the location of terminal device 200. List A can be used to record cell information of cells supporting RedCap and cells not supporting RedCap in cell a. Cell a can be one or more candidate cells searched by terminal device 200 in network device 300. Then, server 400 can aggregate the cell information of all cells in server 400 based on the location of terminal device 200. Finally, server 400 can send list B, which records cell information of cells supporting RedCap and / or cells not supporting RedCap in cell b, to terminal device 200 based on the location of terminal device 200. Cell b can be a cell stored in server 400 at the location of terminal device 200.

[0075] Figure 1B illustrates, exemplarily, the system architecture of a terminal device 200 provided in an embodiment of this application.

[0076] As shown in Figure 1B, the system architecture may include: an application processor (AP) layer and a modem layer.

[0077] The AP layer can be used by terminal device 200 to download list B from server 400. In some embodiments, terminal device 200 can periodically (e.g., every 30 minutes) download list B from server 400 via the AP layer to update list C. In other embodiments, when a change in the location of terminal device 200 is detected, terminal device 200 can download list B from server 400 via the AP layer to update list C. It is readily understood that the new list B downloaded by terminal device 200 from server 400 can replace the old list B to update list C. The AP layer can also be used by terminal device 200 to update list A. For example, during the interoperation process of terminal device 200 (e.g., cell handover, cell reselection, cell redirection) to the target cell, terminal device 200 can receive system messages from one or more candidate cells. A system message from a candidate cell includes indication information about whether the candidate cell supports RedCap. Terminal device 200 can then update list A through the AP layer based on this indication information. Alternatively, if network device 300 adds a cell indicating whether RedCap is supported to the neighbor cell relationship in the measurement configuration when sending measurement configuration to terminal device 200, terminal device 200 can update list A through the AP layer based on this cell information. The AP layer can also be used by terminal device 200 to upload list A to server 400. For example, terminal device 200 can upload list A to server 400 periodically (e.g., every 60 minutes) through the AP layer. Or, when an update to list A is detected, terminal device 200 can upload the updated list A to server 400 through the AP layer. The AP layer can also be used to send List A and List B to the Modem layer via AT commands, so that the Modem layer can obtain List C based on List A and List B.

[0078] The Modem layer can provide cellular communication capabilities to the terminal device 200, ensuring that data can be transmitted effectively and accurately between the terminal device 200 and the network device 300. The Modem layer can also receive lists A and B from the AP layer and derive list C based on lists A and B. This allows RedCap-enabled terminal devices to disable RedCap-unsupported cells (cells the RedCap-enabled terminal device has never accessed) according to list C; or, if a RedCap-unsupported terminal device identifies multiple (e.g., 5) service interruptions (e.g., a service resource scheduling rate below 80%) and determines that its current camped cell is a RedCap-enabled cell according to list C, it can preferentially re-access a RedCap-unsupported cell according to list C. The cell information recorded in list C can include the cell information recorded in list A and list B.

[0079] Figure 2A illustrates the structure of a terminal device 200 provided in an embodiment of this application.

[0080] As shown in Figure 2A, the terminal device 200 may include: input / output modules (including an audio input / output module 210, a key input module 209, and a display 211, etc.), a user interface 202, one or more terminal processors 203, a transmitter 204, a receiver 205, a coupler 206, an antenna 208, and a memory 207. These components can be connected via a bus or other means; Figure 2A illustrates a bus connection as an example.

[0081] The communication interface 201 can be used by the terminal device 200 to communicate with other communication devices, such as a base station. Specifically, the base station can be the network device 300 shown in Figure 2B. The communication interface 201 refers to the interface between the terminal processor 203 and the transceiver system (composed of a transmitter 204 and a receiver 205), such as the X1 interface in Long Term Evolution (LTE). In specific implementations, the communication interface 201 may include one or more of the following: Global System for Mobile Communication (GSM) (2G) communication interface, Wideband Code Division Multiple Access (WCDMA) (3G) communication interface, and Long Term Evolution (LTE) (4G) communication interface, or it can be a 4.5G, 5G, or future New Radio communication interface. Not limited to wireless communication interfaces, the terminal device 200 can also be configured with a wired communication interface 201, such as a Local Access Network (LAN) interface.

[0082] 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 206 is used to split the mobile communication signal received by antenna 208 into multiple paths and distribute them to multiple receivers 205.

[0083] Transmitter 204 can be used to transmit signals output by terminal processor 203, such as modulating the signal on a licensed frequency band or on an unlicensed frequency band.

[0084] Receiver 205 can be used to process mobile communication signals received by antenna 208. For example, receiver 205 can demodulate received signals modulated on unlicensed frequency bands or received signals modulated on licensed frequency bands.

[0085] In some embodiments of this application, the transmitter 204 and the receiver 205 can be considered as a wireless modem. In the terminal device 200, there can be one or more transmitters 204 and receivers 205.

[0086] In addition to the transmitter 204 and receiver 205 shown in Figure 2A, the terminal device 200 may also include other communication components, such as a Global Positioning System (GPS) module, a Bluetooth module, and a Wireless Fidelity (Wi-Fi) module. Not limited to the wireless communication signals described above, the terminal device 200 may also support other wireless communication signals, such as satellite signals, shortwave signals, etc. Not limited to wireless communication, the terminal device 200 may also be configured with a wired network interface (such as a LAN interface) to support wired communication.

[0087] The input / output module is used to realize the interaction between the terminal device 200 and the user / external environment, and may mainly include an audio input / output module 210, a key input module 209, and a display 211. In specific implementations, the input / output module may also include a camera, a touch screen, and sensors, etc. All input / output modules communicate with the terminal processor 203 through the user interface 202.

[0088] Memory 207 is coupled to terminal processor 203 and is used to store various software programs and / or multiple sets of instructions. In specific implementations, memory 207 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 207 may store an operating system (hereinafter referred to as the system), such as embedded operating systems like Android, iOS, Windows, or Linux. Memory 207 may also store network communication programs, which can be used to communicate with one or more auxiliary devices, one or more terminal devices, or one or more network devices. Memory 207 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 207 may be used to store the implementation program of the communication control method provided in one or more embodiments of this application on the terminal device 200 side. For the implementation of the communication control method provided in one or more embodiments of this application, please refer to the following embodiments.

[0090] The terminal processor 203 can be used to read and execute computer-readable instructions. Specifically, the terminal processor 203 can be used to call a program stored in the memory 207, such as the implementation program of the communication control method provided in one or more embodiments of this application on the terminal device 200 side, and execute the instructions contained in the program.

[0091] The terminal processor 203 can be a modem processor, a module that implements the main functions of wireless communication standards such as 3GPP and ETSI. The modem can be a standalone chip or integrated with other chips or circuits to form a system-on-a-chip (SoC) or integrated circuit. These chips or integrated circuits can be used in all devices that implement wireless communication functions, including mobile phones, computers, laptops, tablets, routers, wearable devices, automobiles, and home appliances. It should be noted that in different implementations, the terminal processor 203 can be a standalone chip coupled to off-chip memory, meaning it does not contain internal memory; or the terminal processor 203 can be coupled to on-chip memory and integrated into the chip, meaning it contains internal memory.

[0092] Understandably, terminal device 200 can be the terminal device 200 in the wireless communication system 100 shown in FIG1A, and can be implemented as a mobile device, mobile station, mobile unit, wireless unit, remote unit, user agent, mobile client, etc.

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

[0094] The structure of terminal device 500 is the same as that of terminal device 600, so it will not be described again here.

[0095] Figure 2B illustrates the structure of a network device 300 provided in an embodiment of this application.

[0096] As shown in Figure 2B, the network device 300 may include: a communication interface 302, one or more network device processors 301, a transmitter 304, a receiver 305, a coupler 306, an antenna 307, and a memory 303. These components can be connected via a bus or other means; Figure 2B illustrates a bus connection as an example.

[0097] The communication interface 302 can be used by the network device 300 to communicate with other communication devices, such as terminal devices or other base stations. Specifically, the terminal device can be the terminal device 200 shown in FIG2A. The communication interface 302 refers to the interface between the network device processor 301 and the transceiver system (composed of a transmitter 304 and a receiver 305), such as the S1 interface in LTE. In specific implementations, the communication interface 302 may include one or more of the following: Global System for Mobile Communications (GSM) (2G) communication interface, Wideband Code Division Multiple Access (WCDMA) (3G) communication interface, and Long Term Evolution (LTE) (4G) communication interface, etc., or it can be a 4.5G, 5G, or future New Radio communication interface. Not limited to wireless communication interfaces, the network device 300 can also be configured with a wired communication interface 302 to support wired communication. For example, the backhaul link between one network device 300 and other network devices 300 can be a wired communication connection.

[0098] Antenna 307 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 306 can be used to split mobile communication signals into multiple paths and distribute them to multiple receivers 305.

[0099] Transmitter 304 can be used to transmit signals output by network device processor 301, such as modulating the signal on a licensed frequency band or on an unlicensed frequency band.

[0100] Receiver 305 can be used to process mobile communication signals received by antenna 307. For example, receiver 305 can demodulate received signals modulated on unlicensed frequency bands or received signals modulated on licensed frequency bands.

[0101] In some embodiments of this application, the transmitter 304 and receiver 305 can be considered as a wireless modem. In the network device 300, the number of transmitters 304 and receivers 305 can be one or more.

[0102] Memory 303 is coupled to network device processor 301 and is used to store various software programs and / or multiple sets of instructions. In specific implementations, memory 303 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 303 may store an operating system (hereinafter referred to as the system), such as uCOS, VxWorks, RTLinux, or other embedded operating systems. Memory 303 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.

[0103] The network device processor 301 can be used for wireless channel management, establishing and dismantling call and communication links, and controlling handover of user equipment within the control area. Specifically, the network device processor 301 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 SubMultiplexer (TCSM) (for multiplexing, demultiplexing, and code conversion functions), etc.

[0104] In this application, the network device processor 301 can be used to read and execute computer-readable instructions. Specifically, the network device processor 301 can be used to call a program stored in the memory 303, such as the implementation program of the communication control method provided in one or more embodiments of this application on the network device 300 side, and execute the instructions contained in the program.

[0105] The network device processor 301 can be a modem processor, a module that implements the main functions of wireless communication standards such as 3GPP and ETSI. The modem can be a standalone chip or integrated with other chips or circuits to form a system-on-a-chip (SoC) or integrated circuit. These chips or integrated circuits can be applied to all network-side devices that implement wireless communication functions. For example, in LTE networks, it is called an evolved Node B (eNB or eNodeB); in third-generation (3G) networks, it is called a Node B; and in 5G networks, it is called a 5G base station (NR NodeB, gNB). It should be noted that in different implementations, the network device processor 301 can be a standalone chip coupled to off-chip memory, meaning it does not contain internal memory; or the network device processor 301 can be coupled to on-chip memory and integrated into the chip, meaning it contains internal memory.

[0106] Understandably, network device 300 can be the network device 300 in the wireless communication system 100 shown in Figure 1A, and can be implemented as a base transceiver station, a wireless transceiver, a basic service set (BSS), an extended service set (ESS), a NodeB, an eNodeB, etc. Network device 300 can be implemented as several different types of base stations, such as macro base stations, micro base stations, etc. Network device 300 can apply different wireless technologies, such as cellular wireless access technology, or wireless local area network (WLAN) wireless access technology.

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

[0108] Figure 2C illustrates the structure of the server 400 provided in an embodiment of this application.

[0109] As shown in Figure 2C, server 400 may include processor 410 and memory 420. The components in server 400 are connected to each other via a bus and communicate with each other based on the bus.

[0110] Processor 410 may include one or more processing units, such as application processors, modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0111] Memory 420 is coupled to processor 410 and is used to store various software programs and / or multiple sets of instructions. Memory 420 can be used to store computer executable program code, which includes instructions. Processor 410 executes various functional applications and data processing of server 400 by running the instructions stored in memory 420. Memory may also be provided in processor 410 for storing instructions and data.

[0112] The memory 420 may include one or more random access memory (RAM) and one or more non-volatile memory (NVM). The RAM can be directly read and written by the processor 410. The RAM can be used to store executable programs (e.g., machine instructions) of the operating system or other running programs. The NVM can also store executable programs and user and application data. Executable programs, i.e., user data, stored in the NVM can be pre-loaded into the RAM for direct reading and writing by the processor 410.

[0113] It should be understood that the server 400 shown in Figure 2C is merely an example, and the server 400 may have more or fewer components than those shown in Figure 2C, may combine two or more components, or may have different component configurations. The various components shown in Figure 2C may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0114] The following is a detailed flowchart illustrating a list acquisition method provided in an embodiment of this application.

[0115] Figure 3 illustrates the specific flow of a list acquisition method provided in an embodiment of this application. This method can be applied to the wireless communication system 100 shown in Figure 1A.

[0116] As shown in Figure 3, the method may include:

[0117] S101. During the cell search process, network device 300 sends a system message for cell a to terminal device 200.

[0118] S102, Terminal device 200 records the cell information of cell a and obtains list A.

[0119] Specifically, during the cell search process of terminal device 200, network device 300 can send a system message for cell a to terminal device 200. This system message may include indication information on whether cell a supports RedCap. Cell a may be one or more candidate cells searched by terminal device 200 in network device 300.

[0120] Specifically, after receiving the system message for cell a sent by network device 300, terminal device 200 can identify whether cell a supports RedCap through the RedCap-related information elements (e.g., redCap-ConfigCommon-r17) in the system message SIB1 of cell a, and record the cell information of cells in cell a that support RedCap and those that do not, obtaining list A, which can be stored locally. List A can record not only the indication information of whether cell a supports RedCap, but also the cell ID and location information of cell a. The cell ID can be used to uniquely identify each cell, the tracking area code (TAC) can be used to identify the location of the cell, and the geographic location (e.g., city) can also be used to identify the location of the cell; this embodiment does not limit this. It is understood that list A can also record cell information of cell a other than the indication information of whether RedCap is supported, the cell ID, and the location information; this embodiment does not limit this.

[0121] In this embodiment of the application, the terminal device 200 may include a terminal device 500 that supports RedCap and a terminal device 600 that does not support RedCap. Specifically, the terminal device 500 may record the cell information of cells in cell a that do not support RedCap in list A, and the terminal device 600 may record the cell information of cells in cell a that support RedCap in list A.

[0122] S103, Terminal device 200 uploads List A and the location of terminal device 200 to server 400.

[0123] S104, Server 400 aggregates the cell information of all cells in Server 400 based on the location of Terminal Device 200.

[0124] Specifically, after obtaining List A, terminal device 200 can upload List A and its location to server 400. In some embodiments, terminal device 200 can upload List A to server 400 periodically (e.g., every 60 minutes). In other embodiments, when an update to List A is detected, terminal device 200 can upload the updated List A to server 400. For example, during the process of terminal device 200 interoperating (e.g., cell handover, cell reselection, cell redirection) to a target cell, terminal device 200 can receive system messages from one or more candidate cells. A system message from a candidate cell includes indication information on whether a candidate cell supports RedCap. Then, terminal device 200 can update List A according to the indication information. Updating List A according to the indication information may include, but is not limited to, terminal device 200 adding the indication information on whether RedCap is supported and the corresponding cell information such as the CELL ID and location information of the candidate cell from the received system messages of one or more candidate cells to List A. In this scenario, terminal device 200 can detect that list A has been updated, and then terminal device 200 can upload the updated list A to server 400. For example, if network device 300 adds a cell message indicating whether RedCap is supported to the neighbor cell relationship in the measurement configuration when sending the measurement configuration to terminal device 200, then terminal device 200 can update list A based on this cell message. Specifically, updating list A based on the cell message indicating whether RedCap is supported in the neighbor cell relationship of the measurement configuration may include, but is not limited to, the terminal device 200 adding the received cell message indicating whether RedCap is supported, along with cell information such as the CELL ID and location information of the corresponding candidate cell, to list A. In this scenario, terminal device 200 can detect that list A has been updated, and then terminal device 200 can upload the updated list A to server 400.

[0125] Specifically, after receiving list A uploaded by terminal device 200, server 400 can obtain cell information of cells supporting RedCap and cells not supporting RedCap from list A. It is easy to understand that server 400 stores cell information of cells supporting RedCap and cells not supporting RedCap uploaded by terminal devices at multiple locations. This cell information can be displayed in the form of, for example, a database table, which may specifically contain cell information such as the cell ID, location information, and indications of whether RedCap is supported. It is understood that the cell information can also be displayed in the form of a structure in server 400, and this embodiment of the application does not limit this.

[0126] Then, server 400 can aggregate the cell information of all cells in server 400 (i.e., cell information of cells supporting RedCap and cells not supporting RedCap uploaded by terminal devices at multiple locations) based on the location of terminal device 200, so that terminal device 200 can download and use it. The location of terminal device 200 can be a frequently used location of terminal device 200, which can be identified by terminal device 200 based on its historical login information.

[0127] S105. Terminal device 200 downloads cell information of cell b from server 400 according to the location of terminal device 200, and obtains list B.

[0128] Specifically, after server 400 aggregates the cell information of all cells in server 400 based on the location of terminal device 200, terminal device 200 can download cell information of cell b from server 400 according to its location, obtaining list B. Cell b can be a cell stored on server 400 at the location of terminal device 200. List B can record whether cell b supports RedCap indication information, cell ID of cell b, and location information. It is understood that list B can also record cell information of cell b other than RedCap indication information, cell ID, and location information; this application embodiment does not limit this. In some embodiments, terminal device 200 can download list B from server 400 periodically (e.g., every 30 minutes). In other embodiments, terminal device 200 can download list B from server 400 when a change in the location of terminal device 200 is detected. It is readily understood that the new list B downloaded by terminal device 200 from server 400 can replace the old list B to update list C.

[0129] In some embodiments, when the terminal device 200 moves within a region, the location of cell a obtained through cell search is the same as the location of the terminal device 200. In this case, cell b may include cell a; or, cell b may be equivalent to cell a. In other embodiments, when the terminal device 200 moves from one region to another, cells a and cell b may overlap, meaning that some cells in cell a and some cells in cell b may be the same; or, cell a may include cell b. For example, when the terminal device 200 moves from position 1 to position 2, where positions 1 and 2 are adjacent regions, the location of cell a includes both positions 1 and 2, and the terminal device 200 is located at position 2, then the location of cell b is also at position 2. It is easy to understand that cells a and cell b overlap, and this overlapping portion is the cell in cell a located at position 2.

[0130] In some embodiments, if the terminal device 200 supports RedCap, the terminal device 200 can download cell information of cells that do not support RedCap from the server 400 according to the location of the terminal device 200, and obtain list B. Further, the terminal device 200 can obtain list C based on the aforementioned list A and list B, so that the terminal device supporting RedCap can disable cells that do not support RedCap according to list C which records cell information of cells that do not support RedCap, thereby ensuring that the terminal device supporting RedCap does not access cells that do not support RedCap.

[0131] In other embodiments, if the terminal device 200 does not support RedCap, the terminal device 200 can download information about cells supporting RedCap and cells not supporting RedCap from the server 400 based on its location, thus obtaining a list B. Further, the terminal device 200 can obtain a list C based on the aforementioned lists A and B, so that if a terminal device that does not support RedCap identifies multiple (e.g., 5) service interruptions (e.g., the service resource scheduling rate is below 80%) and determines from list C that the currently camped cell is a cell supporting RedCap, it can preferentially re-access a cell that does not support RedCap based on list C, which records information about cells supporting RedCap and cells not supporting RedCap, thereby ensuring that a terminal device that does not support RedCap can access a cell that does not support RedCap.

[0132] S106. Terminal device 200 obtains list C based on list A and list B.

[0133] In some embodiments, after obtaining List B, terminal device 200 can obtain List C based on List A and List B, so that RedCap-enabled terminal devices (terminal device 500) can disable cells that do not support RedCap according to List C. These unsupported cells are cells that the RedCap-enabled terminal devices have never accessed, thus ensuring that RedCap terminals can avoid accessing non-RedCap cells based on prior information, without requiring the RedCap terminal to have accessed the non-RedCap cell before disabling it, thereby improving the user's data service experience. List C may include cell information recorded in List A and List B. In other embodiments, after obtaining List B, terminal device 500 can directly disable cells that do not support RedCap according to List B. In other embodiments, after obtaining List A, terminal device 500 can directly disable cells that do not support RedCap according to List A.

[0134] It is understood that the terminal device 200 can obtain cell information of cells that support RedCap and / or cells that do not support RedCap not only through the aforementioned list, but also through databases, cloud servers, etc. This application embodiment does not limit this.

[0135] In this embodiment, a terminal device 500 supporting RedCap can disable cells that do not support RedCap according to List C. In some embodiments, the terminal device 500 can avoid camping on cells that do not support RedCap according to List C; that is, during cell search, the terminal device 500 can avoid decoding system messages of cells that do not support RedCap according to List C. In other embodiments, the terminal device 500 can avoid measuring the signal quality of cells that do not support RedCap according to List C, thereby avoiding interoperation (e.g., cell handover) to cells that do not support RedCap. In other embodiments, when multiple service interruptions are detected and the currently camped cell is determined to be a RedCap-supporting cell according to List C, a terminal device 600 that does not support RedCap can determine whether the serving cell where the terminal device 600 is located is a RedCap-supporting cell according to List C. If so, the terminal device 600 can perform cell reselection based on the cells that do not support RedCap recorded in List C, so that the terminal device 600 camps on a cell that does not support RedCap.

[0136] The following is a flowchart illustrating a method for a RedCap terminal to avoid camping on non-RedCap cells based on a list, according to an embodiment of this application.

[0137] Figure 4 illustrates, exemplarily, the specific process of a method for a RedCap terminal to avoid camping on non-RedCap cells according to a list, as provided in an embodiment of this application. This method can be applied to a RedCap-enabled terminal device 500.

[0138] As shown in Figure 4, the method may include:

[0139] S201. During the cell search process, the terminal device 500 determines, according to List C, whether the cell obtained through the cell search is a cell that does not support RedCap.

[0140] S202, Terminal device 500 does not understand system messages for cells that do not support RedCap.

[0141] In some embodiments, the terminal device 500 can avoid camping on cells that do not support RedCap according to List C. Specifically, during cell search, the terminal device 500 can determine whether a cell obtained through the cell search does not support RedCap according to List C. If so, the terminal device 500 can avoid decrypting the system messages of the cell that does not support RedCap, thereby avoiding camping on the cell that does not support RedCap. For example, the terminal device 500 can match the cell information (e.g., CELL ID) of the cell obtained through the cell search with the cell information (e.g., CELL ID) of the cell that does not support RedCap in List C. If the match is successful, the terminal device 500 can avoid decrypting the system messages of the cell that does not support RedCap.

[0142] In cell handover scenarios, to prevent RedCap-enabled terminal device 500 from switching to a cell that does not support RedCap, in some embodiments, terminal device 500 can avoid measuring the signal quality of a cell that does not support RedCap according to Listing C.

[0143] The following is a flowchart illustrating a method for preventing a RedCap terminal from switching to a non-RedCap cell, provided by an embodiment of this application.

[0144] Figure 5 illustrates, exemplarily, the specific process of a method for preventing a RedCap terminal from switching to a non-RedCap cell according to an embodiment of this application. This method can be applied to RedCap-enabled terminal devices 500 and network devices 300.

[0145] As shown in Figure 5, the method may include:

[0146] S301, Network device 300 sends measurement configuration to terminal device 500.

[0147] S302, Terminal device 500 determines whether there are any candidate cells that do not support RedCap based on list C.

[0148] S303, Terminal Equipment 500 does not measure the signal quality of cells that do not support RedCap.

[0149] In some embodiments, terminal device 500 may avoid measuring the signal quality of cells that do not support RedCap according to Listing C, thereby avoiding terminal device 500 switching to cells that do not support RedCap.

[0150] Specifically, network device 300 can send a measurement configuration to terminal device 500, which can be used to instruct terminal device 500 to measure the signal quality of candidate cells.

[0151] Specifically, after receiving the measurement configuration sent by network device 300, terminal device 500 can determine whether there are any cells that do not support RedCap among the candidate cells in the measurement configuration according to List C. If so, terminal device 500 can choose not to measure the signal quality of the cells that do not support RedCap. These cells that do not support RedCap are ones that terminal device 500 has not previously accessed. For example, terminal device 500 can match the cell information (e.g., CELL ID) of the candidate cells in the measurement configuration with the cell information (e.g., CELL ID) of the cells that do not support RedCap in List C. If the match is successful, terminal device 500 can choose not to measure the signal quality of the cells that do not support RedCap, thereby avoiding switching to cells that do not support RedCap.

[0152] S304, Terminal Equipment 500 measures the signal quality of RedCap-supporting cells among candidate cells.

[0153] S305, Terminal device 500 returns a measurement report to network device 300.

[0154] S306 and network equipment 300 make decisions.

[0155] S307, network device 300 sends cell handover signaling to terminal device 500.

[0156] Specifically, terminal device 500 can measure the signal quality of candidate cells that support RedCap. After measuring the signal quality of RedCap-supporting cells, terminal device 500 can return a measurement report to network device 300, which can be used to provide feedback on the signal quality of RedCap-supporting cells.

[0157] Specifically, after receiving the measurement report returned by the terminal device 500, the network device 300 can make a decision based on the measurement report and select the cell supporting RedCap with the best signal quality as the target cell. Then, the network device 300 can send cell handover signaling to the terminal device 500, which can be used to instruct the terminal device 500 to hand over to the target cell. After receiving the cell handover signaling sent by the network device 300, the terminal device 500 can hand over to the target cell.

[0158] To prevent a RedCap-enabled terminal device 500 from switching to a RedCap-unsupported cell, in some embodiments, the terminal device 500 can also be directly controlled not to switch to a RedCap-unsupported cell. Specifically, after receiving the measurement configuration sent by the network device 300, the terminal device 500 can measure the signal quality of all candidate cells in the measurement configuration and return a measurement report to the network device 300. After receiving the cell handover signaling sent by the network device 300, the terminal device 500 can determine whether the target cell is a RedCap-unsupported cell according to List C. If so, it controls the terminal device 500 not to switch to the target cell and sends a notification to the network device 300 to reselect the target cell. In addition, after measuring the signal quality of all candidate cells in the measurement configuration, the terminal device 500 can also, according to List C, not return a measurement report of a RedCap-unsupported cell to the network device 300. This application embodiment does not limit the method by which the terminal side avoids the RedCap-enabled terminal device 500 switching to a RedCap-unsupported cell.

[0159] Terminal devices that do not support RedCap can camp on both RedCap-supporting and non-RedCap-supporting cells. However, RedCap-supporting cells reuse the frequency domain resources of the Enhanced Mobile Broadband (eMBB) Physical Random Access Channel (PRACH) to provide dedicated Bandwidth Part (BWP) resources for RedCap-supporting terminal devices. RedCap-supporting terminal devices are preferentially camped on BWPs with fewer users. Theoretically, a RedCap-supporting cell can be configured with a maximum of five dedicated BWPs for RedCap-supporting terminal devices. In other words, RedCap-supporting cells allocate most of their bandwidth resources to RedCap-supporting terminal devices, resulting in less available bandwidth for non-RedCap-supporting terminal devices. Therefore, if a non-RedCap-supporting terminal device camps on a RedCap-supporting cell, it is prone to resource shortages and service interruptions.

[0160] The following is a flowchart illustrating a method for a non-RedCap terminal to select non-RedCap cells based on a list, according to an embodiment of this application.

[0161] Figure 6 illustrates, exemplarily, the specific flow of a method for a non-RedCap terminal to select non-RedCap cells based on a list, according to an embodiment of this application. This method can be applied to a terminal device 600 that does not support RedCap.

[0162] As shown in Figure 6, the method may include:

[0163] S401. Terminal device 600 determines, according to List C, whether the serving cell where terminal device 600 is located is a cell that supports RedCap.

[0164] S402, Terminal device 600 performs cell reselection based on cells that do not support RedCap as recorded in List C.

[0165] In some embodiments, upon detecting multiple (e.g., 5) instances of service lag (e.g., service resource scheduling rate below 80%), terminal device 600 may release its connection with the serving cell. After releasing the connection, terminal device 600 may re-perform a cell search. Then, terminal device 600 can determine, according to List C, whether the serving cell it is in is a RedCap-supporting cell. If so, terminal device 600 can perform cell reselection based on the RedCap-unsupporting cells recorded in List C, so that terminal device 600 camps on the RedCap-unsupporting cell. For example, terminal device 600 can match the cell information (e.g., CELL ID) of the serving cell it is in with the cell information (e.g., CELL ID) of RedCap-supporting cells in List C. If a match is successful, terminal device 600 can perform cell reselection based on the RedCap-unsupporting cells recorded in List C, so that terminal device 600 camps on the RedCap-unsupporting cell.

[0166] In some embodiments, the terminal device 600 can match the cell information (e.g., CELL ID) of the cell search results with the cell information (e.g., CELL ID) of cells that do not support RedCap recorded in List C. If a match is successful, the terminal device 600 can camp on the cell that does not support RedCap. In other embodiments, the terminal device 600 can score the cell search results based on the cells that do not support RedCap recorded in List C and access the cell that does not support RedCap with the highest score. For example, the terminal device 600 can score the cells that do not support RedCap recorded in List C in the cell search results higher than the cells that support RedCap, and the more bandwidth resources a cell that does not support RedCap has, the higher its score; the terminal device 600 can access the cell that does not support RedCap with the highest score.

[0167] In cell handover scenarios, to prevent RedCap-enabled terminal device 500 from switching to a cell that does not support RedCap, in some embodiments, network device 300 may not send measurement configurations for cells that do not support RedCap to terminal device 500, thereby preventing terminal device 500 from measuring cells that do not support RedCap and thus preventing terminal device 500 from switching to cells that do not support RedCap.

[0168] The following is a flowchart illustrating a method for preventing RedCap terminals from switching to non-RedCap cells on the network side, provided by an embodiment of this application.

[0169] Figure 7 illustrates, exemplarily, the specific process of a network-side method for preventing RedCap terminals from switching to non-RedCap cells according to an embodiment of this application. This method can be applied to RedCap-enabled terminal devices 500 and network devices 300.

[0170] As shown in Figure 7, the method may include:

[0171] S501. During the process of accessing network device 300, terminal device 500 sends a report to network device 300.

[0172] S502, Network device 300 filters out neighboring cell relationships that do not support RedCap from the neighboring cells of the serving cell where terminal device 500 is located.

[0173] S503, network device 300 sends measurement configuration to terminal device 500 based on the filtered neighbor cell relationship.

[0174] Specifically, during the access process to network device 300, terminal device 500 can send a report to network device 300. This report may contain indication information that terminal device 500 supports RedCap (e.g., the report may contain the capability element RedCapParameters-r17), so that network device 300 can know that terminal device 500 supports RedCap through this indication information. Before accessing network device 300, terminal device 500 can perform cell search. During the cell search process, terminal device 500 can receive system messages of each cell in the cell search results sent by network device 300. These system messages may include indication information of whether each cell supports RedCap. It is understood that the embodiments of this application do not limit the way in which the network device learns whether the terminal device supports RedCap. For example, network device 300 can also learn that terminal device 500 supports RedCap by accessing RedCap radio frequency air interface resources during random access.

[0175] Specifically, after learning that terminal device 500 supports RedCap, network device 300 can filter out neighboring cells that do not support RedCap from the neighboring cells of the serving cell where terminal device 500 is located. Then, network device 300 can send a measurement configuration to terminal device 500 based on the filtered neighboring cell relationships. This measurement configuration can be used to instruct terminal device 500 to measure the signal quality of candidate cells, all of which are RedCap-supporting cells.

[0176] S504, Terminal Equipment 500 measures the signal quality of cells that support RedCap.

[0177] S505, terminal device 500 returns a measurement report to network device 300.

[0178] S506 and network equipment 300 make decisions.

[0179] S507, network device 300 sends cell handover signaling to terminal device 500.

[0180] Specifically, after receiving the measurement configuration sent by the network device 300, the terminal device 500 can measure the signal quality of the RedCap-supporting cell and return a measurement report to the network device 300 after measuring the signal quality of the RedCap-supporting cell. This measurement report can be used to provide feedback on the signal quality of the RedCap-supporting cell.

[0181] Specifically, after receiving the measurement report returned by the terminal device 500, the network device 300 can make a decision based on the measurement report and select the cell supporting RedCap with the best signal quality as the target cell. Then, the network device 300 can send cell handover signaling to the terminal device 500, which can be used to instruct the terminal device 500 to hand over to the target cell. After receiving the cell handover signaling sent by the network device 300, the terminal device 500 can hand over to the target cell.

[0182] To prevent RedCap-enabled terminal devices 500 from switching to cells that do not support RedCap, in some embodiments, after receiving measurement reports from all candidate cells (including RedCap-enabled and RedCap-unsupported cells) returned by terminal devices 500, network devices 300 may also filter out measurement reports from cells that do not support RedCap. This application embodiment does not limit the method by which the network side avoids RedCap-enabled terminal devices 500 switching to cells that do not support RedCap.

[0183] The following is a flowchart illustrating a communication control method applied to a terminal device 500 provided in an embodiment of this application.

[0184] Figure 8 illustrates, exemplarily, a specific flow of a communication control method applied to a terminal device 500 according to an embodiment of this application. This method can be applied to a first terminal device, which may be a RedCap-enabled terminal device 500.

[0185] As shown in Figure 8, the method may include:

[0186] S601, Receive the measurement configuration sent by the first network device.

[0187] S602. Determine whether there are any candidate cells that do not support RedCap.

[0188] S603. Do not measure the signal quality of cells that do not support RedCap.

[0189] In this embodiment, the first terminal device can receive a measurement configuration sent by the first network device. This measurement configuration can be used to instruct the first terminal device to measure the signal quality of candidate cells. Then, the first terminal device can determine whether there are any cells among the candidate cells that do not support RedCap. If so, the first terminal device may choose not to measure the signal quality of the cells that do not support RedCap, as these are cells that the first terminal device has never accessed. The first network device can be network device 300.

[0190] In some embodiments, the first terminal device can determine whether there are any cells that do not support RedCap among the candidate cells based on a first list. This first list can be used to record cells that do not support RedCap. The first list can be the aforementioned list C, list A, or list B. It is understood that the first terminal device can obtain cell information for RedCap-supporting and / or RedCap-unsupporting cells not only through the first list, but also through databases, cloud servers, etc. This application embodiment does not impose any limitations on this.

[0191] In some embodiments, the first terminal device may receive system messages from one or more candidate cells. A system message from a candidate cell may include first indication information regarding whether a candidate cell supports RedCap. After receiving system messages from one or more candidate cells, the first terminal device may update a first list based on the first indication information. For example, during cell search, the first terminal device may receive system messages from one or more candidate cells sent by a first network device. A system message from a candidate cell may include first indication information regarding whether a candidate cell supports RedCap. After receiving system messages from one or more candidate cells sent by the first network device, the first terminal device may identify whether a candidate cell supports RedCap using RedCap-related information elements in the system messages, and record cell information for cells supporting RedCap and cells not supporting RedCap among the one or more candidate cells, thus updating the first list. As another example, during interoperation (e.g., cell handover, cell reselection, cell redirection) to a target cell, the first terminal device may receive system messages from one or more candidate cells sent by the first network device. A system message from a candidate cell may include first indication information regarding whether a candidate cell supports RedCap. After receiving system messages from one or more candidate cells sent by the first network device, the first terminal device can add cell information, such as whether RedCap is supported, from the system messages of the one or more candidate cells to the first list to update the first list.

[0192] In some embodiments, the measurement configuration may include second indication information regarding whether a candidate cell supports RedCap, and the first terminal device may update the first list based on this second indication information. For example, if the first network device adds a cell message indicating whether RedCap is supported to the neighbor cell relationship of the measurement configuration when sending the measurement configuration to the first terminal device, the first terminal device may add cell information such as the cell message indicating whether RedCap is supported from the neighbor cell relationship of the received measurement configuration to the first list to update the first list.

[0193] In some embodiments, after updating the first list, the first terminal device can upload the updated first list to a first server, which may be server 400. For example, when an update to the first list is detected, the first terminal device can upload the updated first list to the first server.

[0194] In some embodiments, the first list may be downloaded from a first server, and the first list may be extracted by the first server from a second list based on the location of the first terminal device. The second list may be generated based on cell information of cells that do not support RedCap uploaded by terminal devices at multiple locations.

[0195] In some embodiments, after determining whether there are any candidate cells that do not support RedCap, the first terminal device can measure the signal quality of the candidate cells that support RedCap. After measuring the signal quality of the candidate cells that support RedCap, the first terminal device can return a measurement report to the first network device, which can be used to provide feedback on the signal quality of the RedCap-supporting cells. Then, the first terminal device can receive cell handover signaling sent by the first network device, which can be used to instruct the first terminal device to hand over to a target cell, wherein the target cell may be a RedCap-supporting cell.

[0196] In some embodiments, during cell search, the first terminal device can determine whether the candidate cells obtained through cell search are cells that do not support RedCap. If so, the first terminal device can ignore the system messages of cells that do not support RedCap, so that the first terminal device does not camp on cells that do not support RedCap. For example, the first terminal device can match the cell information of cells obtained through cell search with the cell information of cells that do not support RedCap in a first list. If the match is successful, the first terminal device can ignore the system messages of cells that do not support RedCap, so that the first terminal device does not camp on cells that do not support RedCap. It is understood that the first terminal device can not only obtain cell information of cells that support RedCap and / or cells that do not support RedCap through a first list, and then determine whether the candidate cells obtained through cell search are cells that do not support RedCap based on the first list, but also obtain cell information of cells that support RedCap and / or cells that do not support RedCap through databases, cloud servers, etc. This application embodiment does not limit this.

[0197] The following is a flowchart illustrating a communication control method applied to a terminal device 600 provided in an embodiment of this application.

[0198] Figure 9 illustrates, exemplarily, a specific flow of a communication control method applied to a terminal device 600 according to an embodiment of this application. This method can be applied to a second terminal device, which may be a terminal device 600 that does not support RedCap.

[0199] As shown in Figure 9, the method may include:

[0200] S701. Determine whether the serving cell where the second terminal device is located is a cell that supports RedCap based on the first list.

[0201] S702. Perform cell reselection based on cells that do not support RedCap as recorded in the first list.

[0202] In this embodiment, when service lag is detected, the second terminal device can determine whether its serving cell supports RedCap based on a first list. If so, the second terminal device can perform cell reselection based on cells that do not support RedCap recorded in the first list, allowing it to camp on a RedCap-free cell. The first list can record RedCap-supporting and RedCap-non-supporting cells; it can be the aforementioned list C, list A, or list B. For example, the second terminal device can match the cell information of its serving cell with the cell information of RedCap-supporting cells in the first list. If a match is successful, the second terminal device can perform cell reselection based on cells that do not support RedCap recorded in the first list, allowing it to camp on a RedCap-non-supporting cell. In some embodiments, the second terminal device can score the RedCap-non-supporting cells recorded in the first list; the more bandwidth resources a RedCap-non-supporting cell has, the higher its score. Finally, the second terminal device can access the RedCap-non-supporting cell with the highest score.

[0203] The following is a flowchart illustrating a communication control method applied to a network device 300 provided in an embodiment of this application.

[0204] Figure 10 illustrates, exemplarily, a specific flow of a communication control method applied to a network device 300 according to an embodiment of this application. This method can be applied to a first network device, which may be network device 300.

[0205] As shown in Figure 10, the method may include:

[0206] S801. During the process of the first terminal device accessing the first network device, it is learned that the first terminal device supports RedCap.

[0207] S802. Filter out neighboring cell relationships that do not support RedCap from the neighboring cells of the serving cell where the first terminal device is located.

[0208] S803, based on the filtered neighbor cell relationships, send the measurement configuration to the first terminal device.

[0209] In this embodiment of the application, during the process of the first terminal device accessing the first network device, the first network device can learn that the first terminal device supports RedCap. After learning that the first terminal device supports RedCap, the first network device can filter out neighboring cells that do not support RedCap from the neighboring cells of the serving cell where the first terminal device is located, and send a measurement configuration to the first terminal device based on the filtered neighboring cell relationships. This measurement configuration can be used to instruct the first terminal device to measure the signal quality of cells that support RedCap.

[0210] In some embodiments, after sending a measurement configuration to the first terminal device based on the filtered neighbor cell relationships, the first network device can receive a measurement report sent by the first terminal device. This measurement report can be used to provide feedback on the signal quality of cells supporting RedCap. Then, the first network device can make a decision based on the measurement report, selecting the RedCap-supporting cell with the best signal quality in the measurement report as the target cell. Finally, the first network device can send cell handover signaling to the first terminal device, which can be used to instruct the first terminal device to hand over to the target cell.

[0211] This application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it can implement the steps performed by the electronic device in the above method embodiments, or the steps performed by the human-computer interaction module and the computing module.

[0212] This application also provides a computer program product that, when run on a terminal device, enables the terminal device to perform the steps executed by the electronic device in the above method embodiments.

[0213] This application also provides a chip system, which includes a processor coupled to a memory. The processor executes a computer program stored in the memory to implement the steps performed by the electronic device in any of the method embodiments of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0214] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

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

[0216] As used in the above embodiments, depending on the context, the term "when..." can be interpreted as meaning "if...", "after...", "in response to determining...", or "in response to detecting...". Similarly, depending on the context, the phrase "when determining..." or "if (the stated condition or event) is interpreted as meaning "if determining...", "in response to determining...", "when (the stated condition or event) is detected", or "in response to detecting (the stated condition or event)".

[0217] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.

[0218] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A communication control method, applied to a first terminal device, characterized in that, The first terminal device is a RedCap degraded terminal device, and the method includes: The device receives a measurement configuration sent by a first network device, the measurement configuration being used to instruct the first terminal device to measure the signal quality of a candidate cell; Determine whether there are any candidate cells that do not support RedCap. If so, do not measure the signal quality of the cell that does not support RedCap. The cell that does not support RedCap is one that the first terminal device has never accessed.

2. The method according to claim 1, characterized in that, The determination of whether any candidate cells do not support RedCap specifically includes: The candidate cells are determined based on a first list, which records cells that do not support RedCap.

3. The method according to claim 2, characterized in that, The method further includes: Receive system messages from one or more of the candidate cells, wherein the system message of one candidate cell includes first indication information as to whether the candidate cell supports RedCap; Update the first list according to the first instruction information.

4. The method according to claim 2 or 3, characterized in that, The measurement configuration includes second indication information on whether the candidate cell supports RedCap; the method further includes: Update the first list according to the second instruction information.

5. The method according to claim 3 or 4, characterized in that, The method further includes: Upload the first list to the first server.

6. The method according to claim 2, characterized in that, The first list is downloaded from the first server. The first list is extracted by the first server from the second list based on the location of the first terminal device. The second list is generated based on the cell information of the cells that do not support RedCap uploaded by terminal devices at multiple locations.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Measure the signal quality of the candidate cells that support RedCap; A measurement report is returned to the first network device, the measurement report being used to provide feedback on the signal quality of the RedCap-supporting cell; The first terminal device receives a cell handover signaling message sent by the first network device. The cell handover signaling message is used to instruct the first terminal device to hand over to a target cell, which is a cell that supports RedCap.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: During the cell search process, it is determined whether the candidate cells obtained through the cell search are cells that do not support RedCap. If so, the system messages of the cells that do not support RedCap are not parsed.

9. A communication control method applied to a second terminal device, characterized in that, The second terminal device is a non-RedCap terminal device, and the method includes: If a service interruption is detected, the system determines whether the serving cell where the second terminal device is located is a RedCap-supporting cell based on a first list. If so, cell reselection is performed based on the RedCap-unsupporting cells recorded in the first list. The first list is used to record the RedCap-supporting cells and the RedCap-unsupporting cells.

10. The method according to claim 9, characterized in that, The cell reselection based on the cells that do not support RedCap recorded in the first list specifically includes: The cells that do not support RedCap recorded in the first list are scored. The more bandwidth resources a cell has, the higher its score. The cell with the highest access score is the one that does not support RedCap.

11. A communication control method, applied to a first network device, characterized in that, The method includes: During the process of the first terminal device accessing the first network device, it is learned that the first terminal device supports RedCap; Filter out neighboring cell relationships that do not support RedCap from the neighboring cells of the serving cell where the first terminal device is located; Based on the filtered neighbor cell relationships, a measurement configuration is sent to the first terminal device, which instructs the first terminal device to measure the signal quality of cells supporting RedCap.

12. The method according to claim 11, characterized in that, The method further includes: Receive a measurement report sent by the first terminal device, the measurement report being used to provide feedback on the signal quality of the RedCap-supporting cell; Based on the measurement report, a decision is made to select the RedCap-supporting cell with the best signal quality in the measurement report as the target cell; A cell handover signaling message is sent to the first terminal device, the cell handover signaling message being used to instruct the first terminal device to hand over to the target cell.

13. A communication system, characterized in that, It includes a terminal device and a network device; wherein, there is a communication connection between the terminal device and the network device; the terminal device is the electronic device according to any one of claims 1-10, and the network device is the electronic device according to any one of claims 11-12.

14. A terminal device, characterized in that, The terminal device includes a processor and a memory; wherein the memory is coupled to the processor and is used to store a computer program, which, when executed by the processor, causes the terminal device to perform the method as described in any one of claims 1-10.

15. A network device, characterized in that, The network device includes a processor and a memory; wherein the memory is coupled to the processor and is used to store a computer program that, when executed by the processor, causes the network device to perform the method as described in any one of claims 11-12.

16. A computer storage medium, characterized in that, The computer storage medium stores a computer program that, when executed by a processor, causes the electronic device to perform the method as described in any one of claims 1-12.

17. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it causes the electronic device to perform the method as described in any one of claims 1-12.

Images