Cell selection strategy configuration method, device, equipment, storage medium and program product

Abstract

The application discloses a cell selection strategy configuration method and device, equipment, a storage medium and a program product, relates to the technical field of communication, and is used for avoiding triggering a RedCap terminal device to perform cell selection on a cell that does not support RedCap. Applied to a terminal device, the above method comprises the following steps: receiving a configuration message from a base station; the configuration message comprises a cell selection strategy; the terminal device is a reduced capability RedCap terminal device and / or an enhanced reduced capability eRedCap terminal device; the cell selection strategy is used for limiting the terminal device to access a target cell; and the target cell is a cell that does not support RedCap and / or eRedCap. The application is applied to a scene of configuring a cell selection strategy.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a cell selection strategy configuration method, apparatus, device, storage medium, and program product. Background Technology

[0002] Reduced capability (RedCap) is a low-cost, low-speed fifth-generation mobile communication technology (5G). Currently, RedCap terminal devices can access fourth-generation mobile communication technology (4G) cells and 5G cells that support RedCap, but they cannot access 5G cells that do not support RedCap.

[0003] However, when a RedCap terminal device moves to the boundary area between a 4G cell and a 5G cell that does not support RedCap, it will trigger the RedCap terminal device to perform cell measurement and selection (reselection or handover). Since the RedCap terminal device cannot access a 5G cell that does not support RedCap, it will trigger the RedCap terminal device to perform cell selection, which will affect the service continuity of the RedCap terminal device. Summary of the Invention

[0004] This application provides a cell selection strategy configuration method, apparatus, device, storage medium, and program product to solve the technical problem that when a RedCap terminal device moves to the boundary area of ​​a 5G cell that does not support RedCap, it will trigger the RedCap terminal device to perform cell selection, which will affect the service continuity of the RedCap terminal device.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] In a first aspect, a cell selection strategy configuration method is provided, applied to a terminal device. The method includes: receiving a configuration message from a base station; the configuration message includes a cell selection strategy; the terminal device is a RedCap degraded terminal device and / or an eRedCap enhanced terminal device; the cell selection strategy is used to restrict the terminal device from accessing a target cell; the target cell is a cell that does not support RedCap and / or eRedCap.

[0007] In one possible implementation, the cell selection strategy is configured by the base station's network management system and / or core network equipment.

[0008] In one possible implementation, the cell selection strategy is used to indicate the access priority of multiple frequency bands; the multiple frequency bands include the frequency band of the target cell; the access priority of the target cell's frequency band is lower than the access priority of other frequency bands; the other frequency bands are frequency bands other than the target cell's frequency band among the multiple frequency bands; or, the cell selection strategy is used to indicate cell information that prohibits terminal devices from handing over or reselecting; the cell information includes the target cell; or, the cell selection strategy is used to indicate area information of allowed access areas and / or disallowed access areas; the target cell is located in a disallowed access area.

[0009] In one possible implementation, before receiving the configuration message from the base station, the method further includes: sending a terminal device capability message to the base station; the terminal device capability message includes a target field; the target field is used to characterize the capability information of the terminal device.

[0010] In one possible implementation, the target field is carried in the terminal device's capability information in the form of a container string under different network standards.

[0011] In one possible implementation, the target field is the RedCap capability field and / or the eRedCap capability field.

[0012] In one possible implementation, the method further includes: receiving a terminal device capability query message from a base station; the terminal device capability query message is used to instruct the terminal device to report its terminal capabilities.

[0013] In one possible implementation, the terminal device capability query message includes a RedCap capability acquisition field and / or an eRedCap capability acquisition field.

[0014] In one possible implementation, the cell accessed by the terminal device is a 4G cell of the fourth generation mobile communication system.

[0015] In one possible implementation, the terminal device capability message is parsed by the base station or core network equipment.

[0016] Secondly, a cell selection strategy configuration method is provided, applied to a base station. The method includes: sending a configuration message to a terminal device; the configuration message includes a cell selection strategy; the terminal device is a RedCap degraded terminal device and / or an eRedCap enhanced terminal device; the cell selection strategy is used to restrict the terminal device from accessing a target cell; the target cell is a cell that does not support RedCap and / or eRedCap.

[0017] In one possible implementation, before sending the configuration message to the terminal device, the method further includes configuring the cell selection strategy through the network management system.

[0018] In one possible implementation, before sending the configuration message to the terminal device, the method further includes: receiving a terminal device capability message from the terminal device; the terminal device capability message includes a target field; the target field is used to characterize the capability information of the terminal device.

[0019] In one possible implementation, the method further includes: sending a terminal device capability query message to the terminal device; the terminal device capability query message is used to instruct the terminal device to report its terminal capabilities.

[0020] Thirdly, a cell selection strategy configuration apparatus is provided, comprising: a receiving unit; the receiving unit being configured to receive a configuration message from a base station; the configuration message including a cell selection strategy; the terminal device being a RedCap degraded terminal device and / or an eRedCap enhanced terminal device; the cell selection strategy being used to restrict the terminal device from accessing a target cell; the target cell being a cell that does not support RedCap and / or eRedCap.

[0021] In one possible implementation, the cell selection strategy is configured by the base station's network management system and / or core network equipment.

[0022] In one possible implementation, the cell selection strategy is used to indicate the access priority of the frequency band of each of the multiple cells; the multiple cells include a target cell; the access priority of the frequency band of the target cell is lower than the access priority of the frequency bands of the other cells; the other cells are cells other than the target cell among the multiple cells; or, the cell selection strategy is used to indicate cell information that prohibits the terminal device from handing over or reselecting; the cell information includes the target cell; or, the cell selection strategy is used to indicate area information of the allowed access area and / or the disallowed access area; the target cell is located in the disallowed access area.

[0023] In one possible implementation, the cell selection strategy configuration device further includes: a sending unit; the sending unit is used to send a terminal equipment capability message to the base station; the terminal equipment capability message includes a target field; the target field is used to characterize the capability information of the terminal equipment.

[0024] In one possible implementation, the target field is carried in the terminal device's capability information in the form of a container string under different network standards.

[0025] In one possible implementation, the target field is the RedCap capability field and / or the eRedCap capability field.

[0026] In one possible implementation, the receiving unit is further configured to receive a terminal device capability query message from the base station; the terminal device capability query message is used to instruct the terminal device to report its terminal capabilities.

[0027] In one possible implementation, the terminal device capability query message includes a RedCap capability acquisition field and / or an eRedCap capability acquisition field.

[0028] In one possible implementation, the cell accessed by the terminal device is a 4G cell of the fourth generation mobile communication system.

[0029] In one possible implementation, the terminal device capability message is parsed by the base station or core network equipment.

[0030] Fourthly, a cell selection policy configuration apparatus is provided, comprising: a sending unit; the sending unit being configured to send a configuration message to a terminal device; the configuration message including a cell selection policy; the terminal device being a RedCap degraded terminal device and / or an eRedCap enhanced terminal device; the cell selection policy being used to restrict the terminal device from accessing a target cell; the target cell being a cell that does not support RedCap and / or eRedCap.

[0031] In one possible implementation, the cell selection strategy configuration device further includes: a processing unit; the processing unit is used to configure the cell selection strategy through the network management system.

[0032] In one possible implementation, the cell selection strategy configuration device further includes: a receiving unit; the receiving unit is configured to receive a terminal device capability message from a terminal device; the terminal device capability message includes a target field; the target field is used to characterize the capability information of the terminal device.

[0033] In one possible implementation, the sending unit is further configured to send a terminal device capability query message to the terminal device; the terminal device capability query message is used to instruct the terminal device to report its terminal capabilities.

[0034] Fifthly, an electronic device includes: a processor and a memory; wherein the memory is used to store one or more programs, the one or more programs including computer-executable instructions, and when the electronic device is running, the processor executes the computer-executable instructions stored in the memory to cause the electronic device to perform a cell selection strategy configuration method as described in the first aspect.

[0035] In a sixth aspect, a computer-readable storage medium is provided for storing one or more programs, the one or more programs including instructions that, when executed by a computer, cause the computer to perform a cell selection strategy configuration method as described in the first aspect.

[0036] In a seventh aspect, a computer program product is provided, wherein when computer instructions are executed on an electronic device, the electronic device performs a cell selection strategy configuration method as described in the first aspect.

[0037] This application provides a cell selection policy configuration method, apparatus, device, storage medium, and program product, applied in scenarios involving cell selection policy configuration. When cell selection policy configuration is required, RedCap terminal devices and / or eRedCap terminal devices can receive configuration messages including cell selection policies from base stations. Cell selection policies are used to restrict corresponding terminal devices from accessing cells that do not support RedCap. That is, after informing RedCap terminal devices and / or eRedCap terminal devices of cells that do not support RedCap and / or eRedCap, terminal devices can avoid triggering cell reselection or handover upon detecting the corresponding cell. This solves the problem in related technologies where RedCap terminal devices and / or eRedCap terminal devices trigger cell reselection or handover when detecting cells that do not support RedCap.

[0038] Using the above method, RedCap terminal devices and / or eRedCap terminal devices can receive information from the base station about cells that do not support RedCap and / or eRedCap, thereby restricting the corresponding terminal devices from accessing cells that do not support RedCap and / or eRedCap. This solves the technical problem of RedCap terminal devices triggering cell selection when moving to the boundary area of ​​a 5G cell that does not support RedCap, thus affecting the service continuity of RedCap terminal devices. Attached Figure Description

[0039] Figure 1 A schematic diagram of the structure of a cell selection strategy configuration system provided for an embodiment of this application;

[0040] Figure 2 A flowchart illustrating a cell selection strategy configuration method provided for embodiments of this application. Figure 1 ;

[0041] Figure 3 A schematic diagram of a terminal device located in a boundary region, provided for an embodiment of this application;

[0042] Figure 4 A flowchart illustrating a cell selection strategy configuration method provided for embodiments of this application. Figure 2 ;

[0043] Figure 5 A flowchart illustrating a cell selection strategy configuration method provided for embodiments of this application. Figure 3 ;

[0044] Figure 6 A flowchart illustrating a cell selection strategy configuration method provided for embodiments of this application. Figure 4 ;

[0045] Figure 7 A schematic diagram of the structure of a cell selection strategy configuration device provided in an embodiment of this application. Figure 1 ;

[0046] Figure 8 A schematic diagram of the structure of a cell selection strategy configuration device provided in an embodiment of this application. Figure 2 ;

[0047] Figure 9 This is a schematic diagram of the structure of an electronic device provided as an embodiment of this application. Detailed Implementation

[0048] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0049] In the description of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" and "multiple" refer to two or more. The terms "first," "second," etc., do not limit the quantity or order of execution, and "first," "second," etc., do not necessarily imply differences.

[0050] RedCap is a low-cost, low-speed 5G technology based on commercial 5G networks. Through software upgrades, it can simultaneously support the access and operation of both 5G terminal devices and 5G RedCap terminal devices. Currently, RedCap terminal devices support dual-mode 4G and 5G RedCap networks, meaning they can access the network in either a 4G or a RedCap-enabled 5G network.

[0051] In the initial stages of RedCap deployment, the network construction investment cost of enabling RedCap functionality across all frequency bands of an existing 5G network is high. Therefore, operators typically consider deployment scenarios where RedCap functionality is enabled on demand within the existing 5G network. On-demand RedCap activation ensures RedCap network continuity within a certain 5G coverage area. At the boundaries of 5G networks, there are boundary areas between different systems and within the same system. The first type of boundary area is the boundary between a 4G network and a 5G network that has not enabled (i.e., does not support) RedCap. The second type of boundary area is the boundary between a 4G network and a 5G network that has enabled RedCap. The third type of boundary area is the boundary within a 5G system between a 5G network that has not enabled RedCap and a 5G network that has enabled RedCap.

[0052] For the first and third types of boundary areas, if a RedCap dual-mode terminal device (also known as a RedCap terminal device) accesses a 4G cell or a 5G cell with RedCap enabled, the RedCap dual-mode terminal device will report its terminal capabilities through the corresponding 4G or 5G network. When the RedCap dual-mode terminal device moves to a 5G neighboring cell that does not have RedCap enabled, a ping-pong handover problem occurs. That is, because the 5G neighboring cell does not support RedCap, the RedCap dual-mode terminal device cannot handover or reselect to a 5G neighboring cell and will return to the 4G cell or a 5G cell with RedCap enabled, affecting the service continuity of the RedCap terminal device. Furthermore, this may repeatedly trigger the handover or reselection process, further affecting the service continuity of the RedCap terminal device and increasing its power consumption.

[0053] The main reason for the above problem is that during the handover or reselection process from a 4G cell or a 5G cell with RedCap enabled to a 5G cell without RedCap enabled, the RedCap terminal device first reads the System Information Block 1 (SIB1) message of the adjacent 5G cell. Based on the SIB1 message, it identifies that the 5G cell does not support RedCap, causing the RedCap terminal device to fail to redirect and return to the 4G cell or a 5G cell with RedCap enabled for reconnection. Furthermore, this process may be repeatedly triggered. To address this issue, the solution in related technologies is to enable a protection / penalty mechanism on the RedCap terminal device. This involves using a timer to set a time limit so that after a RedCap terminal device fails to redirect, it does not measure or report the corresponding 5G cell's measurement report for a certain period, thus avoiding repeated redirection failures.

[0054] However, enabling the protection / penalty mechanism on RedCap terminal devices has the following drawbacks: First, if the protection / penalty mechanism fails, the RedCap terminal device will re-trigger the measurement and reselection or handover process, failing to fundamentally solve the inter-system boundary problem. Second, enabling the protection / penalty mechanism requires a redirection failure when the RedCap terminal device moves from a 4G cell or a RedCap-enabled 5G cell to a non-RedCap-enabled 5G neighboring cell. If the RedCap terminal device accesses a new 4G cell or a RedCap-enabled 5G cell, or if the timer exceeds the set time, the measurement and reselection or handover process will be re-triggered, resulting in another redirection failure, which will affect the operator's key performance indicators (KPIs). Third, the duration of the protection / penalty mechanism needs to be set by the operator, and there is no reference value. An unreasonable configuration duration may negatively impact the user experience of the RedCap terminal device. Therefore, the relevant technology cannot completely solve the handover or reselection failure problem when the RedCap terminal device moves from a 4G cell or a RedCap-enabled 5G cell to a non-RedCap-enabled 5G cell.

[0055] The root cause of the aforementioned problems is that RedCap terminal devices access the 4G network as 4G terminals, supporting the 4G network's ability to acquire 5G terminal device capabilities, but how to acquire RedCap capabilities is not defined in detail. Furthermore, after acquiring the RedCap capabilities of the terminal device, it is also necessary to prevent the RedCap terminal device from switching to a 5G cell without RedCap enabled, which requires a corresponding solution. To solve the problem of repeated handover or reselection failures when RedCap terminal devices move from a 4G cell or a 5G cell with RedCap enabled to a 5G cell without RedCap enabled, this application provides a cell selection strategy configuration method. By acquiring the RedCap capabilities of the terminal device and configuring a cell selection strategy for the RedCap terminal device, the handover or reselection failure problem can be avoided.

[0056] The cell selection strategy configuration method provided in this application embodiment can be applied to a cell selection strategy configuration system. Figure 1 A schematic diagram of a cell selection strategy configuration system is shown. Figure 1 As shown, the cell selection strategy configuration system 10 includes: terminal equipment 11, base station 12, and core network equipment (also known as core network element) 13.

[0057] In this embodiment, terminal device 11 is connected to base station 12, and base station 12 is connected to core network device 13. The terminal device 11, base station 12, and core network device 13 can be connected via wired or wireless means, and this embodiment of the invention does not limit the connection.

[0058] It should be noted that, Figure 1 This application uses a terminal device 11 and a base station 12 as an example to introduce the solution proposed in this application. This application does not limit the number of terminal devices 11 and base stations 12 involved.

[0059] Terminal device 11 is used to receive terminal device capability query messages sent by base station 12, return terminal device capability messages to base station 12, and, when terminal device 11 is a RedCap terminal device and / or an eRedCap terminal device, receive configuration messages including cell selection strategies sent by base station 12, and perform cell selection based on the cell selection strategies included in the configuration messages.

[0060] Base station 12 sends a terminal device capability query message to terminal device 11, receives a terminal device capability message returned by terminal device 11, determines whether terminal device 11 is a RedCap terminal device and / or eRedCap terminal device by parsing the terminal device capability message, configures a cell selection policy through the network management system after determining that terminal device 11 is a RedCap terminal device and / or eRedCap terminal device, and sends a configuration message including the cell selection policy to terminal device 11.

[0061] The core network device 13 is used to send a terminal device capability information request to the base station 12, so as to send a terminal device capability query message to the terminal device 11 through the base station 12, and to receive the signaling parsing terminal device capability message including the terminal device capability message through the base station 12 to determine whether the terminal device 11 is a RedCap terminal device and / or an eRedCap terminal device. After determining that the terminal device 11 is a RedCap terminal device and / or an eRedCap terminal device, it configures a cell selection policy and sends a configuration message including the cell selection policy to the terminal device 11 through the base station.

[0062] For example, terminal device 11 can be a user-side entity used to receive or transmit signals, such as a mobile phone. Terminal device can also be called terminal equipment, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. Terminal device can be a RedCap terminal device (i.e., a terminal device supporting RedCap functionality), an eRedCap terminal device (i.e., a terminal device supporting eRedCap functionality), a car with communication capabilities, a smart car, wearable devices, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and so on. The embodiments disclosed herein do not limit the specific technology or device form used in the terminal device.

[0063] Base station 12 can be a base station in Long Term Evolution (LTE) or Long Term Evolution Advanced (LTEA) systems, or an evolved Node B (eNB or eNodeB) (i.e., a base station in a 4G network), a base station device (gNB) in a 5G network, a base station in a 2G network, a base station in a 3G network, or a base station in a future communication system, etc. Base stations can include various macro base stations, micro base stations, femtocell base stations, wireless remote extensions, reconfigurable intelligent surfaces (RISS), routers, relay stations, transmission and reception points (TRPs), receivers, access points, wireless fidelity (WIFI) devices, and other network-side equipment. A base station can sometimes also be referred to as a reader / writer used for communication with terminals.

[0064] Core network equipment 13 can be a mobility management entity (MME) network element in the core network.

[0065] The following description, in conjunction with the accompanying drawings, describes a cell selection strategy configuration method provided by an embodiment of this application. For example... Figure 2 As shown in the embodiment of this application, a cell selection strategy configuration method is provided, the method including S201:

[0066] S201. The base station sends a configuration message to the terminal device. Correspondingly, the terminal device receives the configuration message from the base station.

[0067] The configuration message includes a cell selection policy; the terminal device is a RedCap degraded terminal device and / or an eRedCap enhanced terminal device; the cell selection policy is used to restrict the terminal device from accessing the target cell; the target cell is a cell that does not support RedCap and / or eRedCap.

[0068] In one possible implementation, the terminal device accesses a 4G cell.

[0069] Optionally, the configuration message sent by the base station to the terminal device can be a configuration message from the core network (i.e., the configuration message can be configured by the core network) or a configuration message sent by the base station itself to the terminal device (i.e., the configuration message can also be configured by the operator's network management system). That is, when the core network device sends a configuration message to the terminal device, the base station needs to forward the configuration message to the terminal device. Furthermore, the terminal device can receive configuration messages from the base station. The base station can be the base station of the cell currently accessed by the terminal device. The cell currently accessed by the terminal device can be a 4G cell, or a 5G cell supporting RedCap and / or eRedCap. The target cell can be a 5G cell adjacent to the cell currently accessed by the terminal device. This way, the terminal device is likely to move to the boundary area of ​​the 5G cell and detect its signal. Furthermore, when the terminal device detects the signal of the 5G cell, it can determine not to execute a handover or reselection process based on the cell selection strategy, thereby avoiding handover or reselection failure. The cell selection strategy only includes information about adjacent cells, which can reduce the data packet size of the configuration message, reduce transmission pressure, and reduce the pressure on the terminal device to process and parse the information included in the cell selection strategy.

[0070] For example, such as Figure 3As shown, when the RedCap terminal device is currently connected to the base station of the 4G cell, when the RedCap terminal device moves to the boundary area between the 4G cell and the 5G cell, and the RedCap terminal device detects the signal of the 5G cell, it can know from the cell selection policy that the adjacent 5G cell does not support RedCap, and therefore does not perform the handover or reselection process. Figure 3 This application is not intended to limit the scope of the application, but is merely an example.

[0071] It should be noted that if the terminal device is a RedCap terminal device, then the target cell must be a cell that does not support RedCap. If the terminal device is an eRedCap terminal device, then the target cell must be a cell that does not support eRedCap.

[0072] This application employs a cell selection strategy to enable RedCap and / or eRedCap terminal devices to identify cells that do not support RedCap and / or eRedCap. This allows the terminal devices to avoid triggering cell reselection or handover upon detecting a corresponding cell. This solves the problem in related technologies where RedCap and / or eRedCap terminal devices trigger cell reselection or handover when detecting a cell that does not support RedCap, thereby preventing handover or reselection failures, ensuring service continuity for RedCap terminal devices, and reducing power consumption of the terminal devices.

[0073] In a design, such as Figure 4 As shown in the embodiment of this application, a cell selection strategy configuration method is provided. Before step S201 above, the method further includes step S301:

[0074] S301. The base station configures the cell selection strategy through the network management system, and / or the core network equipment configures the cell selection strategy.

[0075] Optionally, the base station's network management system typically stores detailed information about all cells under that base station and all cells under neighboring base stations. This information includes whether the cells have RedCap and / or eRedCap functionality enabled, as well as the enabling status of RedCap and / or eRedCap functionality in certain specific areas and frequency bands. Thus, when the terminal device is a RedCap terminal device and / or an eRedCap terminal device, the base station's network management system can configure a cell selection policy based on the detailed information of all cells under that base station and all cells under neighboring base stations. Furthermore, the base station can send configuration information, including the cell selection policy, to the terminal device.

[0076] Core network equipment typically stores information about areas where RedCap and / or eRedCap functionality is enabled, as well as information about areas where RedCap and / or eRedCap functionality is not enabled. This allows the core network equipment to configure cell selection policies based on the information about areas with and without RedCap and / or eRedCap functionality when the terminal device is a RedCap terminal device and / or an eRedCap terminal device. Furthermore, the core network equipment can send configuration information, including the cell selection policy, to the base station, which then forwards this information to the terminal device.

[0077] This application allows for the configuration of cell selection strategies through both the base station's network management system and core network equipment, thereby improving the flexibility of cell selection strategy configuration.

[0078] In one possible implementation, the cell selection strategy is used to indicate the access priority of multiple frequency bands; the multiple frequency bands include the frequency band of the target cell; the access priority of the target cell's frequency band is lower than the access priority of other frequency bands; the other frequency bands are frequency bands other than the target cell's frequency band among the multiple frequency bands; or, the cell selection strategy is used to indicate cell information that prohibits terminal devices from handing over or reselecting; the cell information includes the target cell; or, the cell selection strategy is used to indicate area information of allowed access areas and / or disallowed access areas; the target cell is located in a disallowed access area.

[0079] Optionally, the cell selection strategy can be an adjusted mobility priority list. That is, typically, multiple frequency bands can be detected in the area where the terminal device is located, and the 5G network mobility priority list can include the access priorities of multiple frequency bands. The access priorities of these multiple frequency bands can be configured by the operator based on the coverage and network load of different frequency bands. In the adjusted priority list, the access priority of frequency bands of cells that do not support RedCap and / or eRedCap is set lower than the access priority of other frequency bands.

[0080] When the terminal device is a RedCap terminal device and / or an eRedCap terminal device, the base station issues a mobility priority list applicable to RedCap and / or eRedCap terminal devices. This mobility priority list may differ from the mobility priority list for ordinary terminals (i.e., non-RedCap or non-eRedCap terminal devices). This prevents the terminal device from accessing cells that do not support RedCap and / or eRedCap, thereby avoiding handover or reselection of the terminal device.

[0081] For example, assume that the area where the terminal device is located can detect the frequency bands of cells A, B, and C. Cell A operates on the 2.1GHz band. Cell B operates on the 3.5GHz band. Cell C operates on the 900MHz band. In the 5G network mobility priority list, the access priority from highest to lowest is 3.5GHz, 2.1GHz, and 900MHz. In this area, RedCap / eRedCap is enabled on the 2.1GHz band, while RedCap / eRedCap is not enabled on the 3.5GHz and 900MHz bands. The adjusted mobility priority list then shows the access priority from highest to lowest as 2.1GHz, 3.5GHz, and 900MHz.

[0082] It should be noted that one cell corresponds to one frequency band, and one base station corresponds to multiple cells.

[0083] Optionally, the cell information can be a cell identifier, such as cell C, which does not support RedCap. This application can prevent the terminal device from triggering a handover or reselection of cells that do not support RedCap by sending a message to the terminal device prohibiting the terminal device from switching or reselecting.

[0084] When the terminal device is a RedCap terminal device and / or an eRedCap terminal device, the base station's network management system can be configured with a cell selection policy to indicate cell information that prohibits the terminal device from handing over or reselecting.

[0085] Optionally, the area information can be an area identifier (e.g., area A). The cell selection strategy can be a mobility restriction list. The mobility restriction list includes area information for allowed areas (i.e., allowed access areas in this application) and / or non-allowed areas (i.e., non-allowed access areas in this application) within Service Area Restrictions. The target cell is not located in an allowed access area. This application can avoid the terminal device triggering a handover or reselection for cells that do not support RedCap by sending area information to the terminal device, including allowed access areas (excluding cells that do not support RedCap) and / or non-allowed access areas (including cells that do not support RedCap).

[0086] When the terminal device is a RedCap terminal device and / or an eRedCap terminal device, the core network device can configure a cell selection policy to indicate area information for allowed and / or disallowed access areas.

[0087] It should be noted that service area restrictions in 5G networks define which areas terminal devices can communicate with the network and which areas they cannot. Terminal devices within a permitted area are allowed to conduct normal service communication with the network. Terminal devices within a prohibited area are not allowed to conduct normal service communication with the network and cannot trigger network selection or cell reselection.

[0088] The prohibited zones specified in related technologies are consistent with the tracking area identity (TA) zone range, meaning that reselection is restricted for specific TA zones. TA zones are primarily used in communication networks to track the location of terminal equipment. In LTE networks, the configuration unit in the mobility restriction list is the TA zone, which supports mobility management of terminal equipment, such as reselection operations, and is also used for paging user equipment.

[0089] Optionally, the disallowed zone can be configured on a per-cell basis. For example, the disallowed zone can be cell C, which allows for fine-grained configuration of neighboring cells.

[0090] In a design, such as Figure 5 As shown in the embodiment of this application, a cell selection strategy configuration method is provided. Before step S201 above, the method further includes step S401:

[0091] S401. The terminal device sends a terminal device capability message to the base station. Correspondingly, the base station receives the terminal device capability message from the terminal device.

[0092] The terminal device capability message includes a target field; the target field is used to characterize the capability information of the terminal device.

[0093] Optionally, the terminal device's capability information may include processor performance, storage capacity, operating system, network access method, whether it supports RedCap, and whether it supports eRedCap, among other capabilities possessed by the terminal device. This allows the base station to parse the terminal device's capability information to determine whether the terminal device is a RedCap terminal device and / or an eRedCap terminal device. This facilitates the subsequent configuration of cell selection policies when the terminal device is a RedCap terminal device and / or an eRedCap terminal device, preventing the terminal device from triggering handover or reselection failures.

[0094] In one possible implementation, the target field is carried in the terminal device's capability information in the form of a container string under different network standards.

[0095] Optionally, the target field can be reported using a container. That is, the terminal device capability message is a container string containing the terminal device's capability information under different network standards, including the radio access technology-type (RAT-type) (i.e., network standard) and the container string. This allows determination of whether the terminal device is a RedCap and / or eRedCap terminal device based on the terminal device capability message. This facilitates subsequent configuration of cell selection policies when the terminal device is a RedCap and / or eRedCap terminal device, preventing the terminal device from triggering handover or reselection failures.

[0096] For example, the capability information of a terminal device in the form of a container string under different network standards can be UE-Capability RAT-Container List IE. UE-Capability RAT-Container List IE is used to transmit the capability information of the terminal device and contains multiple parameters to describe the terminal's capabilities.

[0097] For example, the current data structure of the UE-Capability RAT-Container List IE is as follows:

[0098] UE-CapabilityRAT-ContainerList IE

[0099] --ASN1START (Data Structure Start Marker)

[0100] --TAG-UE-CAPABILITYRAT-CONTAINERLIST-START

[0101] UE-CapabilityRAT-ContainerList::=

[0102] SEQUENCE(SIZE(0..maxRAT-CapabilityContainers))OF UE-CapabilityRAT-Container

[0103] UE-CapabilityRAT-Container::=

[0104] SEQUENCE{

[0105] rat-Type

[0106] RAT-Type,

[0107] ue-CapabilityRAT-Container

[0108] OCTET STRING

[0109] }

[0110] --TAG-UE-CAPABILITYRAT-CONTAINERLIST-STOP

[0111] --ASN1STOP (End marker for data structure)

[0112] It should be noted that, as shown in the above data structure, the UE-Capability RAT-Container List IE can report the capabilities of the terminal device in the form of a container string, which can distinguish different network standards. The capabilities of the terminal device include the terminal device's RedCap capability and / or eRedCap capability. Thus, the base station can determine whether the terminal device has RedCap capability and / or eRedCap capability by parsing the UE-Capability RAT-Container List IE.

[0113] Optionally, the base station can parse terminal device capability messages reported via containers. During parsing at the base station, the base station needs to support parsing the terminal device capability container list reported by the terminal device, parsing the terminal device capabilities corresponding to the NR RAT (5G NR standard), and extracting RedCap and / or eRedCap capability information.

[0114] This application can parse terminal device capability messages reported via containers using a base station approach.

[0115] In one possible implementation, the target field is the RedCap capability field and / or the eRedCap capability field.

[0116] This application can determine whether a terminal device is a RedCap terminal device and / or an eRedCap terminal device based on the RedCap capability field or the eRedCap capability field, which facilitates the subsequent configuration of cell selection policies when the terminal device is a RedCap terminal device and / or an eRedCap terminal device, and avoids the terminal device triggering handover or reselection failure.

[0117] In a design, such as Figure 6 As shown in the embodiment of this application, a cell selection strategy configuration method is provided. Before step S401 above, the method further includes step S501:

[0118] S501. The base station sends a terminal device capability query message to the terminal device. Correspondingly, the terminal device receives the terminal device capability query message from the base station.

[0119] Among them, the terminal device capability query message is used to instruct the terminal device to report its terminal capabilities.

[0120] Optionally, the base station can trigger the acquisition of terminal device capabilities. That is, when a terminal device accesses the base station, the base station can send a terminal device capability query message to the terminal device.

[0121] Terminal devices can receive requested Capability NR messages from base stations. Furthermore, terminal devices can send terminal capability messages to the base station. In this way, the base station or core network equipment can configure cell selection strategies based on the terminal capability messages, preventing the terminal device from triggering handover or reselection failures.

[0122] For example, a terminal device capability query message can be a requested Capability NR information element (IE). The requested Capability NR IE includes terminal device capability acquisition filtering information. For instance, this terminal device capability acquisition filtering information can be a UE-Capability Request Filter NRIE.

[0123] In this context, Requested Capability NR IE can be resolved to UE-Capability RequestFilter NR IE. UE-Capability Request Filter NR IE omits the domain band list filter.

[0124] For example, the current data structure of the UE-Capability Request Filter NR IE is as follows:

[0125] UE-Capability Request Filter NR IE

[0126] --ASN1START (Data Structure Start Marker)

[0127] --TAG-UE-CAPABILITYREQUESTFILTERNR-START

[0128] UE-Capability Request Filter NR::=

[0129] SEQUENCE{

[0130] frequencyBandListFilter

[0131] FreqBandList

[0132] OPTIONAL,--Need N

[0133] nonCriticalExtension

[0134] UE-CapabilityRequestFilterNR-v1540

[0135] OPTIONAL

[0136] }

[0137] UE-CapabilityRequestFilterNR-v1540::=

[0138] SEQUENCE{

[0139] srs-SwitchingTimeRequest

[0140] ENUMERATED{true}

[0141] OPTIONAL,--Need N

[0142] nonCriticalExtension

[0143] UE-CapabilityRequestFilterNR-v1710

[0144] OPTIONAL

[0145] }

[0146] UE-CapabilityRequestFilterNR-v1710::=

[0147] SEQUENCE{

[0148] sidelinkRequest-r17

[0149] ENUMERATED{true}

[0150] OPTIONAL,--Need N

[0151] nonCriticalExtension

[0152] SEQUENCE{}

[0153] OPTIONAL

[0154] }

[0155] --TAG-UE-CAPABILITYREQUESTFILTERNR-STOP

[0156] --ASN1STOP (End marker for data structure)

[0157] As can be seen from the above data structure, the current UE-Capability Request Filter NR IE does not include fields related to RedCap capability and eRedCap capability. Therefore, the base station cannot instruct the terminal to report its RedCap capability and eRedCap capability.

[0158] In one possible implementation, the terminal device capability query message provided in this application embodiment may include a RedCap capability acquisition field and / or an eRedCap capability acquisition field.

[0159] It should be understood that this application achieves explicit presentation of the aforementioned capability acquisition fields by adding a RedCap capability acquisition field and / or an eRedCap capability acquisition field to the terminal device capability query message. In this way, the terminal device can report to the base station whether it possesses RedCap capability and / or eRedCap capability based on the terminal device capability query message.

[0160] For example, the data structure of the UE-Capability Request Filter NR IE provided in this application embodiment is as follows:

[0161] UE-Capability Request Filter NR IE-xxxx::=

[0162] SEQUENCE{

[0163] RedCapRequest-r17***RedCap Cap Capability Acquisition Fields

[0164] ENUMERATED{true}

[0165] OPTIONAL, --Need N

[0166] nonCriticalExtension

[0167] SEQUENCE{}

[0168] OPTIONAL

[0169] }

[0170] UE-Capability Request Filter NR IE-xxxx::=

[0171] SEQUENCE{

[0172] eRedCapRequest-r17***eRedCap Cap Capability Acquisition Fields

[0173] ENUMERATED{true}

[0174] OPTIONAL, --Need N

[0175] nonCriticalExtension

[0176] SEQUENCE{}

[0177] OPTIONAL

[0178] RedCapRequest-r17 and eRedCapRequest-r17 are the newly added RedCap capability acquisition fields and eRedCap capability acquisition fields, respectively. Therefore, the UE-Capability RequestFilter NR IE provided in this application embodiment includes RedCap capability acquisition fields and eRedCap capability acquisition fields. Thus, the base station can instruct the terminal to report its RedCap and eRedCap capabilities.

[0179] Optionally, the base station can parse the terminal device capability message reported via UE-Capability Request Filter NR IE. During parsing at the base station, no modification to the interface signaling between the base station and the core network equipment is required.

[0180] In one possible implementation, the core network equipment can trigger the acquisition of terminal device capabilities. Specifically, when the terminal device accesses the core network equipment through a base station, the core network equipment can use the UE Capability Info Indication function of the next-generation (NG) interface to include a UE Capability Info Request IE in a downlink Non-Access Stratum (NAS) message, setting it to "requested". Furthermore, if the base station receives the UE Capability Info Request from the core network equipment, it can send a terminal device capability query message to the terminal device.

[0181] In one possible implementation, the core network device can parse the terminal device capability message reported via UE-Capability RequestFilter NR IE. This requires modification of the interface signaling between the base station and the core network device (i.e., the signaling in this application). The base station can send the terminal device capability message to the core network device via the interface signaling (e.g., S1 interface signaling). The interface signaling can carry the terminal device capability message, which includes the terminal device's NR capability from its radio-side capabilities. The terminal device's NR capability includes a RedCap capability field and / or an eRedCap capability field. The core network device (such as the MME) can associate the corresponding terminal device radio-side capability information with the terminal device (e.g., UE registration information) for subsequent operations.

[0182] This application can parse terminal device capability messages reported via UE-Capability RequestFilter NR IE through both core network equipment and base stations, making the parsing of terminal device capability messages more flexible.

[0183] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0184] This application embodiment can divide a cell selection strategy configuration method into functional modules based on the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0185] Figure 7 This is a schematic diagram of a cell selection strategy configuration device provided in an embodiment of this application. Figure 7 As shown, a cell selection strategy configuration device 90 is used to prevent RedCap terminal devices from performing cell selection on cells that do not support RedCap, for example, for executing... Figure 2 The illustration shows a cell selection strategy configuration method. The cell selection strategy configuration device 90 includes a receiving unit 901.

[0186] The receiving unit 901 is used to receive a configuration message from the base station; the configuration message includes a cell selection policy; the terminal device is a RedCap degraded terminal device and / or an eRedCap enhanced terminal device; the cell selection policy is used to restrict the terminal device from accessing the target cell; the target cell is a cell that does not support RedCap and / or eRedCap.

[0187] In one possible implementation, the cell selection strategy is configured by the base station's network management system and / or core network equipment.

[0188] In one possible implementation, the cell selection strategy is used to indicate the access priority of multiple frequency bands; the multiple frequency bands include the frequency band of the target cell; the access priority of the target cell's frequency band is lower than the access priority of other frequency bands; the other frequency bands are frequency bands other than the target cell's frequency band among the multiple frequency bands; or, the cell selection strategy is used to indicate cell information that prohibits terminal devices from handing over or reselecting; the cell information includes the target cell; or, the cell selection strategy is used to indicate area information of allowed access areas and / or disallowed access areas; the target cell is located in a disallowed access area.

[0189] In one possible implementation, the cell selection strategy configuration device 90 further includes: a sending unit 902; the sending unit 902 is used to send a terminal equipment capability message to the base station; the terminal equipment capability message includes a target field; the target field is used to characterize the capability information of the terminal equipment.

[0190] In one possible implementation, the target field is carried in the terminal device's capability information in the form of a container string under different network standards.

[0191] In one possible implementation, the target field is the RedCap capability field and / or the eRedCap capability field.

[0192] In one possible implementation, the receiving unit 901 is further configured to receive a terminal device capability query message from the base station; the terminal device capability query message is used to instruct the terminal device to report its terminal capabilities.

[0193] In one possible implementation, the terminal device capability query message includes a RedCap capability acquisition field and / or an eRedCap capability acquisition field.

[0194] In one possible implementation, the cell accessed by the terminal device is a 4G cell of the fourth generation mobile communication system.

[0195] In one possible implementation, the terminal device capability message is parsed by the base station or core network equipment.

[0196] Figure 8 This is a schematic diagram of a cell selection strategy configuration device provided in an embodiment of this application. Figure 8 As shown, a cell selection strategy configuration device 100 is used to prevent RedCap terminal devices from performing cell selection on cells that do not support RedCap, for example, for executing... Figure 2 The illustration shows a cell selection strategy configuration method. The cell selection strategy configuration device 100 includes: a transmission unit 1001.

[0197] The sending unit 1001 is used to send a configuration message to the terminal device; the configuration message includes a cell selection policy; the terminal device is a RedCap degraded terminal device and / or an eRedCap enhanced terminal device; the cell selection policy is used to restrict the terminal device from accessing the target cell; the target cell is a cell that does not support RedCap and / or eRedCap.

[0198] In one possible implementation, the cell selection strategy configuration device 100 further includes: a processing unit 1002; the processing unit 1002 is used to configure the cell selection strategy through the network management system.

[0199] In one possible implementation, the cell selection strategy configuration device 100 further includes: a receiving unit 1003; the receiving unit 1003 is used to receive a terminal device capability message from a terminal device; the terminal device capability message includes a target field; the target field is used to characterize the capability information of the terminal device.

[0200] In one possible implementation, the sending unit 1001 is further configured to send a terminal device capability query message to the terminal device; the terminal device capability query message is used to instruct the terminal device to report its terminal capabilities.

[0201] In the case where the functions of the integrated modules described above are implemented in hardware, this application provides a possible structural schematic diagram of the electronic device involved in the above embodiments. For example... Figure 9 As shown, an electronic device 120 is used to prevent RedCap terminal devices from performing cell selection on cells that do not support RedCap, for example, for performing... Figure 2 The illustration shows a cell selection strategy configuration method. The electronic device 120 includes a processor 1201, a memory 1202, and a bus 1203. The processor 1201 and the memory 1202 can be connected via the bus 1203.

[0202] Processor 1201 is the control center of the communication device. It can be a single processor or a collective term for multiple processing elements. For example, processor 1201 can be a general-purpose central processing unit (CPU) or other general-purpose processors. Among them, the general-purpose processor can be a microprocessor or any conventional processor.

[0203] As one embodiment, processor 1201 may include one or more CPUs, for example Figure 9 CPU 0 and CPU 1 are shown in the diagram.

[0204] The memory 1202 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0205] As one possible implementation, the memory 1202 can exist independently of the processor 1201. The memory 1202 can be connected to the processor 1201 via the bus 1203 and is used to store instructions or program code. When the processor 1201 calls and executes the instructions or program code stored in the memory 1202, it can implement the cell selection strategy configuration method provided in this application embodiment.

[0206] In another possible implementation, the memory 1202 can also be integrated with the processor 1201.

[0207] Bus 1203 can be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 9 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0208] It should be pointed out that, Figure 9 The structure shown does not constitute a limitation on the electronic device 120. Except... Figure 9 In addition to the components shown, the electronic device 120 may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0209] As an example, combined Figure 7 The functions implemented by the receiving unit 901 and the transmitting unit 902 in the cell selection strategy configuration device 90 are the same as those of the receiving unit 901 and the transmitting unit 902. Figure 9 The processor 1201 in it has the same function.

[0210] Optional, such as Figure 9 As shown, the electronic device 120 provided in this application embodiment may also include a communication interface 1204.

[0211] The communication interface 1204 is used to connect with other devices via a communication network. This communication network can be Ethernet, a wireless access network, a wireless local area network (WLAN), etc. The communication interface 1204 may include a receiving unit for receiving data and a transmitting unit for transmitting data.

[0212] In one design, the communication interface in the electronic device provided in this application embodiment can also be integrated into the processor.

[0213] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional units is used as an example. In practical applications, the above functions can be assigned to different functional units as needed, that is, the internal structure of the device can be divided into different functional units to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0214] This application also provides a computer-readable storage medium storing instructions. When a computer executes these instructions, the computer performs each step of the method flow shown in the above method embodiments.

[0215] The embodiments of this application provide a computer program product in which, when computer instructions are run on an electronic device, the electronic device executes a cell selection strategy configuration method described in the above method embodiments.

[0216] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), registers, hard disks, optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing, or any other form of computer-readable storage medium in the art.

[0217] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside within an application-specific integrated circuit (ASIC).

[0218] In the embodiments of this application, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0219] Since the electronic devices, computer-readable storage media, and computer program products in the embodiments of this application can be applied to the above methods, the technical effects they can achieve can also be referred to the above method embodiments. The embodiments of this application will not be repeated here.

[0220] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be covered within the scope of protection of this application.

Claims

1. A method for configuring a cell selection strategy, characterized in that, Applied to a terminal device, the method includes: Send a terminal device capability message to the base station; the terminal device capability message includes a target field; the target field is carried in the terminal device's capability information in container string form under different network standards; the target field is a RedCap capability field and / or an eRedCap capability field. Receive a terminal device capability query message from the base station; the terminal device capability query message includes a RedCap capability acquisition field and / or an eRedCap capability acquisition field; The system receives a configuration message from a base station; the configuration message includes a cell selection policy; the terminal device is a RedCap degraded terminal device and / or an eRedCap enhanced terminal device; the cell selection policy restricts the terminal device from accessing a target cell; the target cell is a cell that does not support RedCap and / or eRedCap; the cell selection policy indicates the access priority of multiple frequency bands corresponding to the multiple cells; the multiple frequency bands include the frequency band of the target cell; the access priority of the frequency band of the target cell is lower than the access priority of other frequency bands; the other frequency bands are frequency bands other than the frequency band of the target cell; the multiple cells are all cells under the base station and all cells under the base stations adjacent to the base station; one cell in the multiple cells corresponds to one frequency band; the cell selection policy also indicates area information of an area where access is not permitted; the target cell is located in the area where access is not permitted; the area where access is not permitted can be configured at the cell granularity.

2. The method according to claim 1, characterized in that, The cell selection strategy is configured by the base station's network management system and / or core network equipment.

3. The method according to claim 2, characterized in that, The cell selection strategy is used to indicate cell information that the terminal device is prohibited from switching or reselecting; the cell information includes the target cell.

4. The method according to claim 1, characterized in that, The target field is used to characterize the capability information of the terminal device.

5. The method according to claim 4, characterized in that, The terminal device capability query message is used to instruct the terminal device to report its terminal capabilities.

6. The method according to claim 1, characterized in that, The cell accessed by the terminal device is a 4G cell of the fourth generation mobile communication system.

7. The method according to claim 4, characterized in that, The terminal device capability message is parsed by the base station or core network equipment.

8. A method for configuring a cell selection strategy, characterized in that, Applied to a base station, the method includes: The terminal device capability message sent by the receiving terminal includes a target field; the target field is carried in the terminal device's capability information in container string format under different network standards; the target field is a RedCap capability field and / or an eRedCap capability field. Send a terminal device capability query message to the terminal; the terminal device capability query message includes a RedCap capability acquisition field and / or an eRedCap capability acquisition field; A configuration message is sent to a terminal device; the configuration message includes a cell selection policy; the terminal device is a RedCap degraded terminal device and / or an eRedCap enhanced terminal device; the cell selection policy is used to restrict the terminal device from accessing a target cell; the target cell is a cell that does not support RedCap and / or eRedCap; the cell selection policy is used to indicate the access priority of multiple frequency bands corresponding to the multiple cells; the multiple frequency bands include the frequency band of the target cell; the access priority of the frequency band of the target cell is lower than the access priority of other frequency bands; the other frequency bands are frequency bands other than the frequency band of the target cell among the multiple frequency bands; the multiple cells are all cells under the base station and all cells under the base stations adjacent to the base station; one cell in the multiple cells corresponds to one frequency band; the cell selection policy is also used to indicate area information of the disallowed access area; the target cell is located in the disallowed access area; the disallowed access area can be configured at the cell granularity.

9. The method according to claim 8, characterized in that, Before sending the configuration message to the terminal device, the method further includes: Configure the cell selection strategy through the network management system.

10. The method according to claim 8, characterized in that, The target field is used to characterize the capability information of the terminal device.

11. The method according to claim 10, characterized in that, The terminal device capability query message is used to instruct the terminal device to report its terminal capabilities.

12. A cell selection strategy configuration device, characterized in that, Applied to terminal equipment, the cell selection strategy configuration device includes: a receiving unit; The receiving unit is configured to send a terminal device capability message to the base station; the terminal device capability message includes a target field; the target field is carried in the terminal device's capability information in container string form under different network standards; the target field is a RedCap capability field and / or an eRedCap capability field; receive a terminal device capability query message from the base station; the terminal device capability query message includes a RedCap capability acquisition field and / or an eRedCap capability acquisition field; receive a configuration message from the base station; the configuration message includes a cell selection policy; the terminal device is a RedCap capability-reduced terminal device and / or an enhanced RedCap capability-reduced terminal device; the cell selection policy is used to restrict the terminal device's access to target networks. The target cell is a cell that does not support RedCap and / or eRedCap. The cell selection strategy is used to indicate the access priority of multiple frequency bands corresponding to the multiple cells. The multiple frequency bands include the frequency band of the target cell. The access priority of the frequency band of the target cell is lower than the access priority of other frequency bands. The other frequency bands are frequency bands other than the frequency band of the target cell. The multiple cells are all cells under the base station and all cells under the base stations adjacent to the base station. Each cell in the multiple cells corresponds to one frequency band. The cell selection strategy is also used to indicate the area information of the disallowed access area. The target cell is located in the disallowed access area. The disallowed access area can be configured at the cell granularity.

13. A cell selection strategy configuration device, characterized in that, Applied to base stations, the cell selection strategy configuration device includes: a transmission unit; The sending unit is configured to receive a terminal device capability message sent by a terminal; the terminal device capability message includes a target field; the target field is carried in the terminal device's capability information in the form of a container string under different network standards; the target field is a RedCap capability field and / or an eRedCap capability field; and send a terminal device capability query message to the terminal; the terminal device capability query message includes a RedCap capability acquisition field and / or an eRedCap capability acquisition field. A configuration message is sent to the terminal device; the configuration message includes a cell selection policy; the terminal device is a RedCap degraded terminal device and / or an eRedCap enhanced terminal device; the cell selection policy is used to restrict the terminal device from accessing a target cell; the target cell is a cell that does not support RedCap and / or eRedCap; the cell selection policy is used to indicate the access priority of multiple frequency bands corresponding to the multiple cells; the multiple frequency bands include the frequency band of the target cell; the access priority of the frequency band of the target cell is lower than the access priority of other frequency bands; the other frequency bands are frequency bands other than the frequency band of the target cell among the multiple frequency bands; the multiple cells are all cells under the base station and all cells under the base stations adjacent to the base station; one cell in the multiple cells corresponds to one frequency band.

14. An electronic device, characterized in that, include: Processor and memory; The memory is used to store one or more programs, the one or more programs including computer execution instructions. When the electronic device is running, the processor executes the computer execution instructions stored in the memory to cause the electronic device to perform the method of any one of claims 1-7 or 8-11.

15. A computer-readable storage medium storing one or more programs, characterized in that, The one or more programs include instructions that, when executed by a computer, cause the computer to perform the method as claimed in any one of claims 1-7 or 8-11.

16. A computer program product, characterized in that, The computer program product includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as claimed in any one of claims 1-7 or 8-11.

Images