A communication method, a terminal device and a chip system under a wireless network

Abstract

Embodiments of the present application provide a communication method, a terminal device and a chip system under a wireless network. The method comprises: receiving, by the terminal device, a radio resource control (RRC) reconfiguration message sent by a first cell belonging to a first wireless network, the RRC reconfiguration message carrying first configuration information and second configuration information, wherein the first configuration information is configuration information currently required to be activated by the first cell for the terminal device, and the second configuration information is configuration information not currently required to be activated by the first cell for the terminal device; triggering, by the terminal device, a radio link failure (RLF) process in the case that the first configuration information is abnormal; and sending, by the terminal device, an RRC reconfiguration complete message in response to the RRC reconfiguration message to the first cell in the case that a first condition is met, the first condition comprising that the first configuration information is not abnormal and the second configuration information is abnormal. The method can improve the success rate of terminal services under a wireless network.

Description

[0001] This application is a divisional application of a Chinese patent application filed with the State Intellectual Property Office on October 24, 2023, with application number 202311391334.1 and entitled “A Communication Method, Terminal Device, and Chip System in a Wireless Network.” This application claims priority to a Chinese patent application filed with the State Intellectual Property Office on September 26, 2023, with application number 202311273311.0 and entitled “A Communication Method, Terminal Device, and Chip System in a 5G Network,” the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present application relates to the field of terminal device communications, and specifically to a communication method, terminal device, and chip system in a wireless network. Background Art

[0003] Currently, fifth-generation mobile communication networks (5G networks) are gradually entering commercial use. Users can use 5G devices not only to access the Internet but also to make calls. For example, 5G networks utilize a new air interface for voice over new radio (VONR) services, significantly improving user experience. However, compared to the mature 4G Long Term Evolution (LTE) network, 5G VONR has some network compatibility issues, which may cause service failures on terminal devices.

[0004] For example, taking the call service as an example, terminal devices that support 5G networks (such as mobile phones) often have problems with calls not being connected. For example, when the calling terminal calls the called terminal, the calling terminal will broadcast a prompt: This call cannot be connected temporarily. If the called side has turned on the leakage SMS reminder service, there will be a leakage SMS reminder). Summary of the Invention

[0005] The present application provides a communication method, terminal device and chip system in a wireless network to improve the success rate of terminal services in the wireless network.

[0006] In a first aspect, a communication method in a wireless network is provided, including: a terminal device receives a radio resource control (RRC) reconfiguration message sent by a first cell belonging to a first wireless network, the RRC reconfiguration message carries first configuration information and second configuration information, wherein the first configuration information is configuration information that is currently required to be activated and configured by the first cell for the terminal device, and the second configuration information is configuration information that is not currently required to be activated and configured by the first cell for the terminal device; when there is an abnormality in the first configuration information, the terminal device triggers a radio link failure (RLF) process; when a first condition is met, the terminal device sends an RRC reconfiguration completion message in response to the RRC reconfiguration message to the first cell, the first condition including that there is no abnormality in the first configuration information and that there is an abnormality in the second configuration information.

[0007] According to the aforementioned RRC reconfiguration message, the terminal device actually uses the first configuration information instead of the second configuration information. If there is an anomaly in the first configuration information, the terminal device can trigger the RLF process. If there is no anomaly in the first configuration information but there is an anomaly in the second configuration information, the terminal device can determine the verification result as passed during the reconfiguration verification, and does not need to determine the verification result of the RRC reconfiguration message as failed due to the anomaly in the second configuration information. This can ensure the normal operation of the current communication service and improve the success rate of the communication service.

[0008] In some implementations, the first configuration information is the configuration information corresponding to the first part of the bandwidth BWP, and the second configuration information is the configuration information corresponding to the second BWP. The first BWP is the BWP that the first cell configures for the terminal device and currently needs to be activated. The first BWP includes one or more BWPs. The second BWP is the BWP that the first cell configures for the terminal device and does not currently need to be activated. The second BWP includes one or more BWPs.

[0009] In some implementations, the first wireless network is a 5G network, and the first cell is a 5G cell. In one possible implementation, when the first BWP includes only one BWP (such as BWP1), the first BWP is the BWP currently required to be activated configured for the 5G cell, and it can be that firstActiveDownlinkBWP and firstActiveUplinkBWP in the RRC reconfiguration message are both configured as BWP1. When the first BWP includes two BWPs (such as BWP-1 and BWP-2), the first BWP is the BWP currently required to be activated configured for the 5G cell, and it can be that firstActiveDownlinkBWP is configured as BWP-1 and firstActiveUplinkBWP is configured as BWP-2 in the RRC reconfiguration message.

[0010] The second BWP is a BWP configured for the 5G cell that does not currently need to be activated. It can be understood that the BWP configured for firstActiveDownlinkBWP and firstActiveUplinkBWP in the RRC reconfiguration message is not the second BWP.

[0011] In this way, if there is no abnormality in the first BWP but there is an abnormality in the second BWP, the terminal device can judge the verification result as passed during the reconfiguration verification, and there is no need to judge the verification result of the RRC reconfiguration message as failed due to the abnormality in the second BWP. This can ensure that the current communication service is carried out normally and improve the success rate of the communication service.

[0012] In some implementations, the first condition also includes that the terminal device is currently in the process of establishing a call.

[0013] Among them, when the terminal device is in the process of establishing a call, the terminal device determines the verification result as passed, which can improve the success rate of the call service.

[0014] In some implementations, the above method further includes: when there is no abnormality in the first configuration information, there is an abnormality in the second configuration information, and the terminal device is not currently in the call establishment process, the terminal device triggers the RLF process.

[0015] In some implementations, after the terminal device sends an RRC reconfiguration completion message in response to the RRC reconfiguration message to the first cell, the above method also includes: the terminal device receives a first message sent by the first cell, the first message being used to instruct the terminal device to switch from the first configuration information to the second configuration information; after the terminal device receives the first message sent by the first cell, the terminal device triggers the RLF process.

[0016] Since the first configuration information used by the terminal device is configured normally, the subsequent communication services of the terminal device will proceed normally if the configuration information is not switched. However, if the cell instructs the terminal device to switch to the second configuration information containing an abnormal configuration, the terminal device will determine that the parameter configuration corresponding to the configuration information is abnormal, and further communication services will most likely fail. Therefore, the terminal device can trigger the RLF process at this time.

[0017] In some implementations, after the terminal device sends an RRC reconfiguration completion message in response to the RRC reconfiguration message to the first cell, the above method also includes: the terminal device sends a first registration request to the first cell, the type of the first registration request is mobile registration update MRU, and the value of the subsequent request FOR field in the first registration request is 0; the terminal device receives a capability query request sent by the first cell after receiving the first registration request; the terminal device sends first capability information to the first cell in response to the capability query request, and the first capability information indicates that the terminal device does not support dynamic configuration information switching.

[0018] The FOR field is 1 bit long. When the bit is 0, it indicates a nofollow-on request pending. When the bit is 1, it indicates a follow-on request pending. If a cell receives a registration request with a FOR field value of 0, it will trigger a query on the terminal device's capabilities.

[0019] In this implementation, after the current service is successfully established, the terminal device can proactively and temporarily turn off the ability to dynamically switch configuration information and synchronize it to the network side. As a result, the network side will not subsequently issue instructions for switching configuration information, thus avoiding the problem of possible failure of the communication service and greatly improving the success rate of the communication service.

[0020] In some implementations, the first capability information indicates that the terminal device does not support dynamic configuration information switching, specifically: the first capability information does not carry the bwp-SwitchingDelay field and the bwp-SameNumerology field.

[0021] In some implementations, before the terminal device sends the first capability information to the first cell, the method further includes: the terminal device disabling the capability of dynamically switching configuration information.

[0022] The terminal device may be configured with a parameter that indicates whether the terminal device has the capability to dynamically switch configuration information enabled. The terminal device may modify the value of this parameter to indicate that the capability to dynamically switch configuration information is disabled. For example, a value of 1 indicates that the terminal device has the capability to dynamically switch configuration information enabled, while a value of 0 indicates that the terminal device has the capability to dynamically switch configuration information disabled.

[0023] In some implementations, after the terminal device sends an RRC reconfiguration completion message in response to the RRC reconfiguration message to the first cell, the above method also includes: the terminal device receives a first message sent by the first cell, the first message is used to instruct the terminal to switch from the first configuration information to the second configuration information; after the terminal device receives the first message sent by the first cell, it disenables the first function corresponding to the second configuration information and switches from the first configuration information to the second configuration information, the first function being the function corresponding to the first parameter item with an abnormality in the second configuration information.

[0024] In this implementation, after the current service is successfully established, if the cell instructs the terminal device to switch to a BWP ID with a configuration abnormality, the terminal device can not configure the abnormal configuration item and disable the corresponding function, which can also ensure that subsequent services proceed normally and improve the success rate of communication services.

[0025] In some implementations, the first parameter item with the exception is the startingPRB field with a configuration exception. The startingPRB field with the configuration exception is the startingPRB field corresponding to the first value of the pucch resource Id in the second configuration information. When the pucch resource Id used for CSI (channel status information) is the first value, the first function is CSI.

[0026] In some implementations, the first value is 40.

[0027] CSI is a function that allows a terminal device to measure various qualities of the wireless channel and report them to the network. If the field configuration corresponding to this function is abnormal, the terminal device can no longer configure pucch resource ID 40 and disable the corresponding CSI function. The terminal device then switches to the second configuration information for service. This means that the terminal device no longer measures and reports various qualities of the wireless channel during service, but service can continue normally.

[0028] In some implementations, when there is an abnormality in the second configuration information, the above method further includes: marking an abnormality on an identifier of the second configuration information.

[0029] If the terminal device marks the second configuration information, if the cell subsequently instructs the terminal device to switch to the marked configuration information, it means that the terminal device is instructed to switch to the configuration information with abnormal configuration, and the terminal device can execute the corresponding processing flow.

[0030] According to a second aspect, a communication method in a wireless network is provided, including: a terminal device receives multiple RRC reconfiguration messages sent by a 5G cell, and the multiple RRC reconfiguration messages carry at least first configuration information, wherein the first configuration information includes configuration information corresponding to a first BWP, and the first BWP includes one or more BWPs; when the number of abnormalities in the first configuration information in the multiple RRC reconfiguration messages exceeds a preset threshold, the terminal device triggers an RLF process and prohibits selecting the 5G cell as a serving cell within a preset time period.

[0031] In this implementation, when the terminal device receives a BWP containing an abnormal configuration in the cell configuration, the number of abnormalities in the cell can be counted. If the number of times the cell sends configuration abnormalities exceeds a preset threshold within a preset time, the terminal device can BAR the cell for a period of time, so that the terminal device selects a new cell to reside in. The probability of configuration abnormalities occurring in the new cell is lower, thereby improving the success rate of subsequent communication services.

[0032] According to a third aspect, a communication method in a wireless network is provided, including: a terminal device receives multiple RRC reconfiguration messages sent by a 5G cell, the multiple RRC reconfiguration messages carry at least first configuration information, wherein the first configuration information includes configuration information corresponding to a first BWP, the first BWP includes one or more BWPs, and the first BWP is a BWP that is configured by the 5G cell for the terminal device and is not currently required to be activated; when the number of times that the first configuration information in the multiple RRC reconfiguration messages is abnormal exceeds a preset threshold, the terminal device turns off the ability to dynamically switch the BWP for a preset first time.

[0033] In this implementation, when the terminal device receives a configured BWP containing an abnormal configuration, the number of abnormalities in the cell can be counted. If the number of times the cell sends configuration abnormalities exceeds a preset threshold within a preset time, the terminal device can temporarily turn off the dynamic switching BWP capability for a period of time. As a result, the network side will not subsequently send a BWP switching instruction, so that the terminal device will not switch to the first BWP with the abnormal configuration, thereby avoiding the problem of further failure of the communication service and greatly improving the success rate of the communication service.

[0034] In some implementations, the situation where the number of times that anomalies exist in the first configuration information in multiple RRC reconfiguration messages exceeds a preset threshold includes: the situation where the number of times that anomalies exist in the first configuration information in multiple RRC reconfiguration messages received within a preset second time exceeds a preset threshold, or the situation where the number of times that anomalies exist in the first configuration information in multiple RRC reconfiguration messages in a preset number of RRC reconfiguration messages received continuously exceeds a preset threshold.

[0035] In some implementations, the above method also includes: when the number of times that the first configuration information in multiple RRC reconfiguration messages is abnormal does not exceed a preset threshold, the terminal device triggers the RLF process.

[0036] In some implementations, when the terminal device turns off the capability of dynamic BWP switching for a preset first time, the above method also includes: the terminal device receives a capability query request sent by the 5G cell; the terminal device responds to the capability query request and sends first capability information to the 5G cell, and the first capability information indicates that the terminal device does not support dynamic BWP switching.

[0037] Among them, after the terminal device turns off the dynamic switching BWP capability, the terminal device can feedback capability information to the cell, indicating that the terminal device does not support BWP dynamic switching. The cell will then no longer dynamically switch BWP, ensuring that subsequent services will proceed normally.

[0038] In a fourth aspect, a terminal device is provided, the terminal device comprising:

[0039] a memory for storing instructions;

[0040] The processor is used to call and execute instructions in the memory so that the terminal device executes any one of the methods described in the first to third aspects above.

[0041] In the fifth aspect, a chip system is provided, which includes: a processing circuit, a receiving pin and a transmitting pin; wherein the receiving pin, the transmitting pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes any one of the methods described in the first to third aspects above to control the receiving pin to receive signals and control the transmitting pin to send signals.

[0042] In a sixth aspect, a chip system is provided, which includes a processor for supporting a terminal device to implement the wireless communication method described in any one of the first to third aspects above.

[0043] In some implementations, the chip system may be a modem chip. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 This is a schematic diagram of relevant cell parameters in an example of BWP configuration provided in an embodiment of the present application;

[0045] Figure 2 This is a schematic diagram of an example of Initial DL / UL BWP parameters provided in an embodiment of the present application;

[0046] Figure 3This is a schematic diagram of the configuration parameters of a ServingCellConfig provided in an embodiment of the present application;

[0047] Figure 4 This is a schematic diagram of the corresponding relationship between LocationAndBandwidth and the length of the starting virtual resource block and the continuously allocated resource blocks provided in an embodiment of the present application;

[0048] Figure 5 It is a signaling interaction flow chart for call services in related technologies;

[0049] Figure 6 This is a schematic diagram of an example of BWP configuration parameter anomaly provided in an embodiment of the present application;

[0050] Figure 7 This is a signaling interaction flow chart of a communication method in a wireless network provided by an embodiment of the present application;

[0051] Figure 8 This is a signaling interaction flow chart of another example of a communication method in a wireless network provided by an embodiment of the present application;

[0052] Figure 9 This is a signaling interaction flow chart of another example of a communication method in a wireless network provided in an embodiment of the present application;

[0053] Figure 10 This is a schematic diagram of the definition of the bwp-SwitchingDelay field and the bwp-SameNumerology field provided in an embodiment of the present application;

[0054] Figure 11 This is a signaling interaction flow chart of another example of a communication method in a wireless network provided in an embodiment of the present application;

[0055] Figure 12 This is a signaling interaction flow chart of another example of a communication method in a wireless network provided in an embodiment of the present application;

[0056] Figure 13 This is a signaling interaction flow chart of another example of a communication method in a wireless network provided in an embodiment of the present application;

[0057] Figure 14 This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

[0058] Figure 15 This is a software structure block diagram of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0059] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships can exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0060] In the following, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the quantity of the technical features indicated. Therefore, a feature specified as "first," "second," or "third" may explicitly or implicitly include one or more of the features.

[0061] At present, 5G networks are gradually being used commercially, and terminal devices can also realize communication services such as surfing the Internet and making phone calls under the 5G network. Therefore, the terminal device (such as a mobile phone, also referred to as UE in the embodiment of this application) must first access the 5G network to establish a 5G session.

[0062] After the user turns on the 5G network function on the UE, the UE can automatically connect to the 5G network and establish a communication connection. The process may include:

[0063] 1. Cell search and selection: The UE can scan the surrounding 5G frequency bands, obtain available cell information, and select the best cell for access based on the preset cell selection algorithm.

[0064] 2. Cell Access: The UE sends an access request to the best cell. Upon receiving the request, the cell can determine access authorization. If the UE meets the access requirements, the cell will assign a temporary mobile subscriber identity (TMSI) to the UE. After receiving the cell's access authorization, the UE can confirm the access request and send a confirmation message to the cell. Upon receiving the confirmation message, the cell completes the access process and assigns the UE an international mobile subscriber identity (IMSI).

[0065] 3. Security Negotiation and Establishment: After a UE accesses a cell, it can send a security negotiation request to the core network to ensure the security of subsequent communications. Upon receiving the security negotiation request, the core network selects an appropriate security protocol based on the UE's identity information and network policy, and sends a negotiation response to the UE. If the UE confirms the negotiation request, it sends a negotiation confirmation message to the core network. Upon receiving the negotiation confirmation message, the core network completes the security negotiation and establishment process and generates the relevant keys for the UE.

[0066] 4. Service Request and Establishment: If the UE wishes to perform a communication service, it may send a service request to the core network, informing it of the desired service. Upon receiving the service request, the core network selects an appropriate service policy based on the UE's needs and network resources, and sends a service response to the UE. Upon receiving the service response and confirming the service request, the UE sends a service confirmation message to the core network. Upon receipt of the service confirmation message, the core network completes the service request and establishment process and can allocate the appropriate service resources to the UE.

[0067] However, during the research and development of 5G network connectivity, researchers discovered that while 5G network bandwidth has increased significantly compared to 4G, some communication services performed by UEs (such as IoT services) do not require high bandwidth. Forcing all services or all terminal devices (including those other than mobile phones) to support high bandwidth would result in resource waste. Therefore, the concept of a bandwidth part (BWP) has been introduced in 5G networks. A BWP is a collection of contiguous common resource blocks (CRBs) with subcarrier spacing within a portion of the bandwidth of a carrier (e.g., a 100 MHz cell). A BWP is a continuous section of bandwidth allocated by the network (core network) to a UE, enabling flexible data transmission between the network and the UE. Each BWP corresponds to a specific Numerology (system parameter) and is a required configuration for UE access to the 5G network. Different UEs can be configured with different BWPs, and different communication services within a UE can be configured with different BWPs.

[0068] Generally, BWP can be divided into initial BWP, dedicated BWP, active BWP and default BWP. Initial BWP: The BWP used by the UE during the initial access phase. The initial BWP is divided into downlink initial BWP and uplink initial BWP. Dedicated BWP: The BWP configured by the UE in the radio resource control (RRC) connected state. Activated BWP: The BWP activated by the UE at a certain moment in the RRC connected state. It is one of the dedicated BWPs. The protocol stipulates that the UE can only activate one configured dedicated BWP as its active BWP at a time in the RRC connected state. Default BWP: The BWP that the UE works with after its BWP inactivity timer expires in the RRC connected state. It is also one of the dedicated BWPs. RRC signaling is used to instruct the UE which configured dedicated BWP to use as the default BWP.

[0069] As can be seen from the description, when the UE accesses a cell, the network side can configure the BWP for the UE through RRC signaling. Then, by configuring different BWPs for the UE on the network side, the purpose of variable uplink and downlink bandwidth used by the UE can be achieved. In addition to the different bandwidth sizes of different BWPs, the configuration parameters of other physical layer channels or signals are also independently configured for each BWP. Therefore, the network side can switch the UE's BWP to a large bandwidth based on the current business volume, such as when large amounts of data need to be transmitted. In addition, the network side will also switch the UE to a BWP with better channel quality based on the measurement values ​​of each frequency domain channel.

[0070] For example, at a certain moment, the UE is playing an 8K high-definition video, which requires the support of 5G large bandwidth. The network side can configure the UE to access a large BWP. After watching the video, the user starts using the UE to send messages. At this time, the network side can allocate a small BWP to the UE. The UE and the network side can communicate with a smaller transmission power to save resources.

[0071] In some implementations, the relevant cell parameters in the BWP configuration can be found in Figure 1, wherein the downlink BWP (downlink BWP) may include the BWP identifier (BWP ID), the frequency domain location and bandwidth of the bandwidth part (LocationAndBandwidth), the cell-specific parameters of the physical downlink control channel (PDCCH) (pdcch-CommonConfig), the cell-specific parameters of the physical downlink shared channel (PDSCH) (pdsch-CommonConfig), the UE-specific PDCCH configuration (pdcch-Config) and the UE-specific PDSCH configuration (pdsch-Config), etc., and the uplink BWP (uplink BWP) may include the BWP identifier (bwp id), the frequency domain location and bandwidth of the bandwidth part (LocationAndBandwidth), the cell-specific parameters of the physical uplink control channel (PUCCH) (pucch-CommonConfig), the physical uplink shared channel (physical uplink channel, PUSCH) cell-specific parameters (pusch-CommonConfig), UE-specific PUCCH configuration (pucch-Config), UE-specific PUSCH configuration (pusch-Config), profile class (srs-Config), etc. Exemplarily, the BWP configuration process may include:

[0072] First, the network side configures an initial downlink / uplink BWP (Initial DL / UL BWP) in the system information block 1 (SIB1), and its BWP ID = 0. It can be understood that the SIB1 message of the 5G network can carry the basic information required for the UE to access the wireless cell, random access parameters, and the availability and scheduling period of other SIBs. For example, the description of Initial DL / UL BWP in the standard protocol 38.331 can be found in Figure 2As shown, ServingCellConfigCommonSIB is used to configure the cell-specific parameters of the UE's serving cell in SIB1. Downlink parameters (DownlinkConfigCommonSIB) and uplink parameters (UplinkConfigCommonSIB) are defined in ServingCellConfigCommonSIB. The initial uplink BWP: initialUplinkBWP (used to provide the initial uplink BWP parameters of the cell) is defined in UplinkConfigCommonSIB, and the initial downlink BWP: initialDownlinkBWP (used to provide the initial downlink BWP parameters of the cell) is defined in DownlinkConfigCommonSIB.

[0073] The process of the UE obtaining the Initial DL / UL BWP in the initial access process includes: 1. decoding the master information block (MIB) to obtain Coreset#0 information, 2. monitoring the SIB1 information in Coreset#0, 3. decoding SIB1, and obtaining the Initial DL / UL BWP.

[0074] Secondly, before entering the connected state, the UE can only transmit and receive on the Initial BWP. Before receiving MSG4, for downlink, the UE can also work only on Coreset#0, and the network side only schedules on Coreset#0. After the UE enters the connected state, in the configuration of the connected state, such as the serving cell configuration (ServingCellConfig) of the downlink configuration, up to 4 BWPs can be configured. Therefore, the UE side needs to store up to 5 BWP configurations. However, at the same time, the UE has at most one BWP in effect. After entering the connected state, the first effective BWP is determined by the identifier of the first effective downlink BWP (firstActiveDownlinkBWP-Id).

[0075] For example, the configuration parameters of ServingCellConfig can be found in Figure 3 As shown in the figure, the maxNorfBWPs configuration parameter represents the maximum number of configured BWPs (for example, 4), and the firstActiveDownlinkBWP-Id is the first effective BWP. The protocol interprets firstActiveDownlinkBWP-Id as follows: the BWP-Id contained in this field is the BWP to be activated when performing RRC reconfiguration (if this field is not defined, RRC reconfiguration will not force BWP switching).

[0076] In actual applications, the network side can also perform BWP switching for the UE based on different communication services or other requirements. The switching process can include the following methods:

[0077] 1. The network side instructs the UE to perform BWP switching through downlink control information (DCI).

[0078] DCI format 0-1 / 1-1 contains a Bandwidth Part Indicator field. If the BWP indicated by this field is inconsistent with the current BWP, the UE needs to switch BWPs. Since this field is a maximum of 2 bits, and according to the previous description, the UE can be configured with a maximum of 5 BWPs, it is clear that 2 bits cannot represent all 5 BWPs. Therefore, two situations are distinguished.

[0079] 1.1) Initial BWP+3BWP

[0080] Taking the description of DCI format 0-1 in standard 38.212 as an example, the Bandwidth part indicator indicates the position index when BWP-Id is used as the ascending order.

[0081] 1.2) Initial BWP+4BWP

[0082] At this time, the UE cannot switch to the Initial BWP through DCI and can only switch among the four other configured BWPs.

[0083] 2. There is no random access resource on the currently activated non-initial BWP, so switch to the Initial BWP.

[0084] If random access needs to be sent on the currently activated BWP due to, for example, timing advance (TA) timer expiration, but there is no PRACH configuration on the current BWP configuration, then the BWP needs to be switched to the Initial UL BWP for random access. It can be assumed that the PRACH configuration must exist on the Initial UL BWP.

[0085] 3. The BWP inactivity timer times out and switches to the default BWP.

[0086] When the BWP inactivity timer expires, if the default downlink BWP identifier (defaultDownlinkBWP-Id) is configured, the UE will switch to the BWP; if not configured, the UE will switch to the initial downlink BWP (initialDownlinkBWP).

[0087] 4. RRC reconfigures BWP switching.

[0088] That is, firstDownlinkActiveBWP-Id or firstUplinkActiveBWP-Id is directly changed.

[0089] However, whether configuring or switching BWP, the UE needs to know which part of the overall bandwidth is allocated. Figure 1 It can be seen that among the relevant information element parameters of the BWP configuration, there is a parameter for the frequency domain location and bandwidth (LocationAndBandwidth) of the bandwidth part. According to this parameter, the UE can obtain two parameters: the starting virtual resource block (Offset) and the length of the continuously allocated resource block (ie, the bandwidth size).

[0090] According to the calculation method specified in the protocol, the resource allocation method of BWP generally adopts the RIV (resource indication value) method. RIV (i.e. LocationAndBandwidth) corresponds to the length of the starting virtual resource block and the length of the continuous allocated resource blocks. For example, the corresponding relationship between LocationAndBandwidth and the length of the starting virtual resource block and the continuous allocated resource blocks is as follows: Figure 4 As shown, the BWP parameter includes the LocationAndBandwidth parameter, which ranges from (0,37949). According to the formula in protocol 38.214 L can be calculated RBs and RB start , where RIV is the value of LocationAndBandwidth, L RBs Indicates the length of the continuous resource block allocated in the cell bandwidth (BWP Bandwidth), RB start Represents the starting virtual resource block, and the protocol also sets If the starting virtual resource block is offset relative to the starting point, the offset of the starting virtual resource block offsetToCarrier may also be defined in the parameter SCS-SpecificCarrier.

[0091] Under normal circumstances, when the network configures multiple BWPs to the UE, if the BWP parameters are normal, the UE can reply to the network with a reconfiguration completion message to complete the configuration process, and the UE can subsequently perform communication services on the activated BWP. However, after research, it was found that in some scenarios, due to a problem with a parameter configuration of the BWP of the PUCCH channel in the RRC reconfiguration message sent by the network to the UE, the UE fails to pass the RRC reconfiguration message verification, and then the UE will not send an RRC reconfiguration completion message to the network (that is, the UE will not respond to the RRC reconfiguration message), which in turn causes the UE to be unable to establish a data radio bearer (DRB) and the network to fail to initialize the UE context, which will eventually lead to problems such as the caller and the called party being unable to connect in the call service scenario or the data service being unavailable in the data service scenario.

[0092] For example, Figure 5 As shown, it is a signaling interaction flow chart for call services in the relevant technology. When the UE resides on cell B and is in idle state (IDLE state), and the UE has a service demand (for example, the UE receives a Paging message for calling the UE), the UE establishes an RRC connection with the network side (core network); the core network sends an RRC reconfiguration message through cell B. In the RRC reconfiguration message, some parameters corresponding to the BWP are abnormally configured (for example, BWP1 is normal, BWP2 is abnormal); the UE identifies the BWP configuration abnormality and triggers the radio link failure (RLF) process. Since the core network has not received the reconfiguration completion message replied by the UE, it is unable to initialize the UE context, that is, the initialization of the UE context fails, and the caller's invite message cannot be sent, resulting in the problem of the called party not being able to connect. Assuming that the UE reselects the cell later, if cell B has the highest priority or the best signal, the UE will still choose cell B to reside. The BWP parameter configuration in the RRC reconfiguration message sent by cell B is still abnormal, and the UE enters a loop of disconnection.

[0093] To solve this problem, we analyze the configuration parameters of BWP2. Assuming that the RRC reconfiguration message sent by the network side carries two BWPs, BWP1 and BWP2, and the configuration of BWP2 is abnormal, we find that the value of LocationAndBandwidth is configured as 17325 (such as Figure 6 As shown in Figure (a), if according to the formula The calculation result is 17325=275×(64-1)+0, which is RB start =0,L RBs=64, the maximum length of the continuously allocated resource block is 64. However, in the configuration parameters of BWP2, the starting PRB corresponding to the resource block with pucch resource ID 40 is configured as 110 (e.g. Figure 6 (b) and (c) in the figure), exceeding L RBs range, obviously Figure 6 The configuration in Figure (c) is abnormal, so the UE fails to verify the RRC reconfiguration message, resulting in unreachable calls or unavailable data services.

[0094] Therefore, the reasons for the failure of RRC reconfiguration in the above related technologies are: 1. According to the protocol formula, if the starting PRB configured on the network side exceeds the theoretically calculated L RBs This is unreasonable. If the network switches the UE to this BWP ID during subsequent data transmission, problems will arise. 2. This incorrect configuration item (i.e., starting PRB) may cause problems for the UE in the future. Therefore, the UE modem will determine that the RRC reconfiguration message verification has failed in this case, and the UE will not reply with a reconfiguration complete message.

[0095] Based on this, some embodiments of the present application provide a communication method in a wireless network to improve the success rate of terminal services in the wireless network.

[0096] Example 1

[0097] In one scenario, the network side configures two BWPs for the UE through an RRC reconfiguration message, for example, two BWPs with BWP ID=1 and BWP ID=2, and in the RRC reconfiguration message, firstActiveDownlinkBWP and firstActiveUplinkBWP are both configured as BWP1, that is, the RRC reconfiguration message carries firstActiveDownlinkBWP-Id 1 and firstActiveUplinkBWP-Id 1, that is, the network side instructs the UE to use BWP1 as the currently activated uplink or downlink BWP through the RRC reconfiguration message, while BWP2 is not used as the currently activated BWP. It is assumed that the network side's configuration of BWP1 in the RRC reconfiguration message is normal, and there is an abnormality in the configuration of BWP2 in the RRC reconfiguration message (for example, the above Figure 6 Abnormal configuration shown in (c)).

[0098] According to the RRC reconfiguration message, the BWP (i.e., firstActiveDownlinkBWP and firstActiveUplinkBWP) that the UE will actually use is the normal BWP1 instead of the BWP2 with the abnormal problem. Although the network side has configured two BWP IDs for the UE, the UE may not switch BWP in the future (i.e., it may not use the BWP2 with the abnormal problem in the future). Therefore, during the reconfiguration verification, the modem in the UE can judge the verification result as passed if the BWP1 verification is normal. There is no need to judge the verification result of the RRC reconfiguration message as failed due to the abnormality of BWP2. Later, when the UE really needs to switch to the BWP ID with the abnormal problem (i.e., BWP2), it can be decided whether to report an error based on the situation.

[0099] Specifically, if Figure 7 As shown, the signaling interaction process of a communication method in a wireless network provided in an embodiment of the present application may include:

[0100] S101, UE resides in cell B and is in IDLE state.

[0101] The UE can camp on the cell B through cell search and access. It can be understood that if the UE is not currently performing any communication service, it is in the IDLE state.

[0102] S102, the UE receives a service request sent by cell B.

[0103] S103, the UE requests to establish an RRC connection with the network side (core network).

[0104] The service request received by the UE may be a Paging message (paging message) for calling the UE. The Paging message may be a message generated by the network side after receiving the Invite message from the caller. The UE then requests to establish an RRC connection with the network side so that the network side initializes the context.

[0105] S104, cell B sends an RRC reconfiguration message to the UE.

[0106] S105: The UE identifies the RRC reconfiguration message (the identification may also be referred to as verification), and identifies that an abnormal BWP configuration exists in the RRC reconfiguration message.

[0107] For example, the RRC reconfiguration message configures two BWPs for the UE, namely BWP1 and BWP2. It is assumed here that some parameter configurations corresponding to BWP IDs in the RRC reconfiguration message are abnormal, for example, the parameter configuration corresponding to BWP2 is abnormal.

[0108] The UE may identify the RRC reconfiguration message according to the calculation method specified in the above protocol, and further identify the abnormally configured BWP.

[0109] S106, the UE determines whether the current BWP configuration is abnormal. If the current BWP configuration is abnormal, S107 is executed. If the current BWP configuration is normal, S108 is executed.

[0110] The current BWP is the BWP that the UE will use (or is called the BWP that will be activated). The UE determines whether the current BWP configuration is abnormal, that is, whether the configuration of the parameters corresponding to the BWP ID that the UE will use (the BWP ID to be used, namely, firstDownlinkActiveBWP-Id and firstUplinkActiveBWP-Id) is abnormal. Here, the modem in the UE can determine whether the configuration of the parameters corresponding to the BWP ID that the UE will use is abnormal. For example, assuming that the BWP that the UE will use is configured as the aforementioned BWP1, as described above, the parameter configuration corresponding to BWP1 is normal, then the UE can execute S108; after receiving the RRC reconfiguration message, the UE can switch to the BWP1.

[0111] S107: The UE does not reply an RRC reconfiguration complete message to cell B, triggering an RLF procedure.

[0112] That is, if the configuration of the parameters corresponding to the BWP ID to be used by the UE is abnormal, the modem may consider that the RRC reconfiguration has failed and will not reply the RRC reconfiguration completion message to cell B (network side). Then the modem triggers the RLF process and will not execute subsequent steps.

[0113] S108, the UE replies to cell B with an RRC reconfiguration complete message.

[0114] S109: The network side responds and initiates context establishment.

[0115] S110: The network sends the caller's Invite message to the UE, and the call service proceeds normally.

[0116] That is, if the configuration of the parameters corresponding to the BWP ID to be used by the UE is normal, the modem can normally reply with an RRC reconfiguration completion message after performing RRC reconfiguration, and finally successfully establish the service (ie, the call service corresponding to the above call).

[0117] S111 , cell B instructs the UE to switch to a BWP ID with abnormal configuration.

[0118] S112: The UE triggers an RLF procedure.

[0119] Since the parameters of the BWP currently used by the UE (i.e., BWP1) are configured correctly, the UE's subsequent communication services will proceed normally if no BWP switching is performed. However, if cell B instructs the UE to switch to a BWP with an abnormal configuration (i.e., BWP2), the UE will determine that the parameters corresponding to the BWP are configured abnormally, and further communication services will most likely fail. Therefore, the UE (or the modem in the UE) can trigger the RLF process at this time.

[0120] In some implementations, before step S108, the UE may further perform S112: marking a BWP ID with an abnormal configuration, wherein the modem may mark the BWP ID. Accordingly, if cell B instructs the UE to switch to a BWP ID marked as abnormal in S111, the UE triggers an RLF procedure. It is understood that cell B instructing the UE to switch to the marked BWP ID may be by cell B sending a message (e.g., an RRC reconfiguration message) instructing the UE to switch to the BWP ID with the abnormal configuration.

[0121] It can be understood that this embodiment can be applied not only to call service scenarios but also to other data service scenarios such as Internet access, and is suitable for any scenario that requires the UE to verify the RRC reconfiguration message.

[0122] In the above implementation, when the UE receives a BWP with an abnormal configuration configured by the network side, during the reconfiguration verification, the UE can judge the verification result as passed if the BWP to be used (i.e., BWP1) is verified normally. There is no need to judge the verification result of the RRC reconfiguration message as failed due to the abnormality of BWP2. This can ensure that the current communication service is carried out normally and improve the success rate of the communication service.

[0123] Example 2

[0124] Since the main problem in the related art is that the UE cannot be connected when being called by the called party, in order to ensure the success rate of the call service, this embodiment can also further execute different processing strategies according to whether the call is currently being established during the reconfiguration check.

[0125] Specifically, if Figure 8 As shown, the signaling interaction process of another example of a communication method in a wireless network provided in an embodiment of the present application may include:

[0126] S201, the UE resides in cell B and is in IDLE state.

[0127] S202: UE receives a service request sent by cell B.

[0128] S203, the UE requests to establish an RRC connection with the network side (core network).

[0129] The service request received by the UE may be a Paging message (paging message) for calling the UE. The Paging message may be a message generated by the network side after receiving the Invite message from the caller. The UE then requests to establish an RRC connection with the network side so that the network side initializes the context.

[0130] S204, cell B sends an RRC reconfiguration message to the UE.

[0131] S205: The UE identifies the RRC reconfiguration message and identifies that the RRC reconfiguration message contains an abnormally configured BWP configuration.

[0132] For example, the RRC reconfiguration message configures two BWPs for the UE, namely BWP1 and BWP2. It is assumed here that some parameters corresponding to BWP IDs in the RRC reconfiguration message are abnormally configured, for example, parameters corresponding to BWP2 are abnormally configured.

[0133] The UE may identify the RRC reconfiguration message according to the calculation method specified in the above protocol, and further identify the abnormally configured BWP.

[0134] S206, the UE determines whether the current BWP configuration is abnormal. If the current BWP configuration is abnormal, S207 is executed; if the current BWP configuration is normal, S208 is executed.

[0135] The current BWP is the BWP that the UE will use (or is called the BWP that will be activated). The UE determines whether the current BWP configuration is abnormal, that is, whether the configuration of the parameters corresponding to the BWP ID to be used by the UE (the BWP ID to be used, namely, firstDownlinkActiveBWP-Id and firstUplinkActiveBWP-Id) is abnormal. For example, assuming that the BWP to be used by the UE is configured as the aforementioned BWP1, as described above, the parameter configuration corresponding to BWP1 is normal, then the UE can execute S208; after receiving the RRC reconfiguration message, the UE can switch to the BWP1.

[0136] S207: The UE does not reply an RRC reconfiguration complete message to cell B, triggering an RLF process.

[0137] That is, if the configuration of the parameters corresponding to the BWP ID to be used by the UE is abnormal, the modem may consider that the RRC reconfiguration has failed and will not reply the RRC reconfiguration completion message to cell B (network side). Then the modem triggers the RLF process and will not execute subsequent steps.

[0138] S208, determining whether the call is currently being established. If so, execute S209; otherwise, execute S207.

[0139] S209, the UE replies to cell B with an RRC reconfiguration complete message.

[0140] In other words, if the configuration of the parameters corresponding to the BWP ID to be used by the UE is normal, the UE further determines whether it is currently in the call establishment process. If so, the UE responds with an RRC reconfiguration complete message as normal. If not, the UE considers the RRC reconfiguration to have failed, triggering the RLF procedure and discontinuing subsequent steps. In some implementations, the UE may determine whether the received service request is a call service request based on the above-mentioned request, and if so, determine that the UE is currently in the call establishment process.

[0141] S210: The network side responds and initiates context establishment.

[0142] S211: The network sends the caller's Invite message to the UE, and the call service proceeds normally.

[0143] At this point, the call service is successfully established and the UE can talk to the caller normally.

[0144] S212 , cell B instructs the UE to switch to the BWP ID with abnormal configuration.

[0145] S213: The UE triggers the RLF procedure.

[0146] Since the parameters of the BWP currently used by the UE (i.e., BWP1) are configured correctly, the UE's subsequent call services will proceed normally if no BWP switching is performed. However, if cell B instructs the UE to switch to a BWP with an abnormal configuration (i.e., BWP2), the UE will determine that the parameters corresponding to the BWP are configured abnormally, and further call services will likely fail. Therefore, the UE (or the modem in the UE) can trigger the RLF process at this time.

[0147] In some implementations, before step S209, the UE may further perform S213: marking the BWPID with abnormal configuration, wherein the modem may mark the BWP ID.

[0148] In the above implementation, when the UE receives a BWP with an abnormal configuration configured by the network side, during the reconfiguration verification, the UE can judge the verification result as passed if the BWP to be used (i.e., BWP1) is verified normally and the call is currently in the process of being established. There is no need to judge the verification result of the RRC reconfiguration message as failed due to the abnormality of BWP2. This can ensure that the current call service proceeds normally, thereby improving the success rate of the call service.

[0149] Example 3

[0150] It can be seen from the above-mentioned embodiments 1 and 2 that after the current service is carried out normally, if the network side does not instruct the UE to switch the BWP, the service will not be abnormal. If after a period of time, the network side instructs the UE to switch to a BWP ID with a configuration abnormality, the UE will trigger the RLF process, and the service may still be interrupted (after the service is successfully established, the interruption does not necessarily mean the service fails), or the service may fail when a new communication service is carried out. Therefore, this embodiment takes into account that after the communication service is successfully established, the UE can actively and temporarily turn off the ability to dynamically switch BWP and synchronize it to the network side. As a result, the network side will not subsequently issue a BWP switching instruction, thereby avoiding the problem that the communication service may fail again, and further improving the success rate of the communication service.

[0151] Specifically, if Figure 9 As shown, the signaling interaction process of another example of a communication method in a wireless network provided in an embodiment of the present application may include:

[0152] S301, the UE resides in cell B and is in IDLE state.

[0153] S302: UE receives a service request sent by cell B.

[0154] S303, the UE requests to establish an RRC connection with the network side (core network).

[0155] The service request received by the UE may be a Paging message (paging message) for calling the UE. The Paging message may be a message generated by the network side after receiving the Invite message from the caller. The UE then requests to establish an RRC connection with the network side so that the network side initializes the context.

[0156] S304, cell B sends an RRC reconfiguration message to the UE.

[0157] Among them, the parameter configurations corresponding to some BWP IDs in the RRC reconfiguration message are abnormal, for example, the parameter configuration corresponding to the non-currently activated BWP2 is abnormal.

[0158] S305: The UE identifies the RRC reconfiguration message and identifies that the RRC reconfiguration message contains an abnormally configured BWP configuration.

[0159] For example, the RRC reconfiguration message configures two BWPs for the UE, namely BWP1 and BWP2. It is assumed here that some parameter configurations corresponding to BWP IDs in the RRC reconfiguration message are abnormal, for example, the parameter configuration corresponding to BWP2 is abnormal.

[0160] The UE may identify the RRC reconfiguration message according to the calculation method specified in the above protocol, and further identify the abnormally configured BWP.

[0161] S306, the UE determines whether the current BWP configuration is abnormal. If the current BWP configuration is abnormal, S307 is executed. If the current BWP configuration is normal, S308 is executed.

[0162] The current BWP is the BWP that the UE will use (or is called the BWP that will be activated). The UE determines whether the current BWP configuration is abnormal and whether the configuration of the parameters corresponding to the BWP ID to be used (the BWP ID to be used, namely, firstDownlinkActiveBWP-Id and firstUplinkActiveBWP-Id) is abnormal. For example, assuming that the BWP to be used by the UE is configured as the aforementioned BWP1, as described above, the parameter configuration corresponding to BWP1 is normal, then the UE can execute S208; after receiving the RRC reconfiguration message, the UE can switch to the BWP1.

[0163] S307: The UE does not reply an RRC reconfiguration complete message to cell B, triggering an RLF process.

[0164] That is, if the configuration of the parameters corresponding to the BWP ID to be used by the UE is abnormal, the modem may consider that the RRC reconfiguration has failed and will not reply the RRC reconfiguration completion message to cell B (network side). Then the modem triggers the RLF process and will not execute subsequent steps.

[0165] S308, determining whether the call is currently being established. If so, execute S309; ​​otherwise, execute S307.

[0166] S309, the UE replies to cell B with an RRC reconfiguration complete message.

[0167] If the configuration of the parameters corresponding to the BWP ID to be used by the UE is normal, it can be further determined whether it is currently in the call establishment process. If it is, the RRC reconfiguration complete message is normally replied. If it is not in the call establishment process, the RRC reconfiguration is considered to have failed, the RLF process is triggered, and no further steps are executed.

[0168] In some implementations, the above step S308 is optional, that is, if it is determined in S306 that there is no abnormality in the configuration of the parameters corresponding to the BWP ID to be used by the UE, the UE can directly execute the process of replying the RRC reconfiguration completion message to cell B in S309.

[0169] S310: The network side responds and initiates context establishment.

[0170] S311: The network sends the caller's Invite message to the UE, and the call service proceeds normally.

[0171] At this point, the call service is successfully established, and the UE can talk to the caller normally. In some implementations, the call service is successfully established and the UE rings normally.

[0172] S312: The UE temporarily disables the dynamic BWP switching capability.

[0173] The UE may be configured with a parameter that indicates whether the UE has enabled the dynamic BWP switching capability. The UE may modify the value of this parameter to indicate that the dynamic BWP switching capability is disabled. For example, a value of 1 indicates that the UE has enabled the dynamic BWP switching capability, while a value of 0 indicates that the UE has disabled the dynamic BWP switching capability.

[0174] S313: The UE sends a first registration request to cell B.

[0175] S314, cell B queries the UE's capability information.

[0176] It can be understood that the first registration request is used to trigger cell B to query the UE capabilities. In this embodiment, the type of the first registration request can be mobility registration updating (MRU), and the value of the follow-on request (FOR) field carried in the first registration request is 0.

[0177] The FOR field is 1 bit in size. When the bit value is 0, it indicates that no subsequent processing is required (nofollow-on request pending). When the bit value is 1, it indicates that a subsequent request is pending (follow-on request pending). Generally, if cell B receives a registration request with a FOR field value of 1, it will not trigger a query of the UE's capabilities. However, if cell B receives a registration request with a FOR field value of 0, it will trigger a query of the UE's capabilities.

[0178] S315, the UE feeds back the UE capability information to cell B.

[0179] S316 , cell B returns a first registration acceptance to the UE.

[0180] When the UE's capabilities are fed back to cell B, the UE reports that the UE does not support dynamic BWP switching. After obtaining the capability that the UE does not support dynamic BWP switching, cell B may return a registration acceptance for the first registration request to the UE, and will not subsequently configure multiple BWPs for the UE, or will not instruct the UE to dynamically switch the BWP, thereby preventing the UE from being instructed to switch to a BWP with a configuration problem.

[0181] Under normal circumstances, after the UE temporarily turns off the dynamic switching BWP function, when the UE reports its capabilities to cell B, it will not carry the two information elements bwp-SwitchingDelay (BWP switching delay) and bwp-SameNumerology. The bwp-SameNumerology field indicates the maximum number of BWPs with the same sub-carrier spacing (SCS) supported by the UE. Among them, if the capability information sent by the UE to cell B does not carry the bwp-SwitchingDelay field and the bwp-SameNumerology field, it indicates that the UE indicates to cell B that the UE does not support dynamic BWP switching. It can be understood that if the capability information sent by the UE to cell B carries the bwp-SwitchingDelay field and the bwp-SameNumerology field, it indicates that the UE indicates to cell B that the UE supports dynamic BWP switching.

[0182] For example, the definition of the bwp-SwitchingDelay field and the bwp-SameNumerology field can be found in Figure 10 If the capability information sent by the UE to cell B does not carry these two fields, cell B will not obtain the values ​​corresponding to the two fields, and will not subsequently configure multiple BWPs for the UE, or instruct the UE to dynamically switch BWPs.

[0183] In some implementations, before step S309, the UE may further perform S317: marking the BWPID with abnormal configuration, wherein the modem may mark the BWP ID.

[0184] In the above implementation, when the UE receives a BWP configured by the network that contains an abnormal configuration, during the reconfiguration verification, the UE can determine the verification result as passed if the BWP to be used (i.e., BWP1) is verified normally and the call is currently being established. There is no need to determine the verification result of the RRC reconfiguration message as failed due to the abnormality of BWP2, thereby ensuring the normal operation of the current call service. At the same time, after the current service is successfully established, the UE can proactively and temporarily disable the ability to dynamically switch BWPs and synchronize this to the network side. As a result, the network side will not subsequently issue BWP switching instructions, thereby avoiding the problem of possible failure of the communication service and greatly improving the success rate of the communication service.

[0185] Example 4

[0186] It can be seen from the above examples 1 and 2 that after the current service is running normally, if the network side does not instruct the UE to switch to BWP, the service will not be abnormal. If after a period of time, the network side instructs the UE to switch to a BWP ID with an abnormal configuration, the UE will trigger the RLF process, and the subsequent service may still be interrupted, or the service may fail when performing a new communication service. However, through research, it was found that although some configuration items in the BWP configuration are abnormal (such as the above Figure 6 Figure (c) shows that only the resource block with pucchresouce ID 40 is configured abnormally), but these abnormal configuration items will only make the corresponding functions unusable and will not cause communication service interruption. Therefore, when the network side instructs the UE to switch to the BWP ID with abnormal configuration, the UE can not configure the abnormal configuration items (also called parameter items) (which can be understood as not taking effect on the configuration items), and disable the corresponding functions, and then switch to the corresponding BWP ID normally to perform services. In this way, the communication service is likely to be able to proceed normally.

[0187] Specifically, if Figure 11 As shown, the signaling interaction process of another example of a communication method in a wireless network provided in an embodiment of the present application may include:

[0188] S401, the UE resides in cell B and is in IDLE state.

[0189] S402: UE receives a service request sent by cell B.

[0190] S403, the UE requests to establish an RRC connection with the network side (core network).

[0191] The service request received by the UE may be a Paging message (paging message) for calling the UE. The Paging message may be a message generated by the network side after receiving the Invite message from the caller. The UE then requests to establish an RRC connection with the network side so that the network side initializes the context.

[0192] S404, cell B sends an RRC reconfiguration message to the UE.

[0193] Among them, the parameter configurations corresponding to some BWP IDs in the RRC reconfiguration message are abnormal, for example, the parameter configuration corresponding to the non-currently activated BWP2 is abnormal.

[0194] S405: The UE identifies the RRC reconfiguration message and identifies that the RRC reconfiguration message contains an abnormally configured BWP configuration.

[0195] The UE may identify the RRC reconfiguration message according to the calculation method specified in the above protocol, and further identify the abnormally configured BWP.

[0196] S406, the UE determines whether the current BWP configuration is abnormal. If the current BWP configuration is abnormal, S407 is executed; if the current BWP configuration is normal, S408 is executed.

[0197] The current BWP is the BWP that the UE will use (or is called the BWP that will be activated). The UE determines whether the current BWP configuration is abnormal, that is, whether the configuration of the parameters corresponding to the BWP ID to be used is abnormal.

[0198] S407: The UE does not reply an RRC reconfiguration complete message to cell B, triggering an RLF procedure.

[0199] That is, if the configuration of the parameters corresponding to the BWP ID to be used by the UE is abnormal, the modem may consider that the RRC reconfiguration has failed and will not reply the RRC reconfiguration completion message to cell B (network side). Then the modem triggers the RLF process and will not execute subsequent steps.

[0200] S408, determining whether the call is currently being established. If so, execute S409; otherwise, execute S407.

[0201] S409, the UE replies to cell B with an RRC reconfiguration complete message.

[0202] If the configuration of the parameters corresponding to the BWP ID to be used by the UE is normal, the UE will further determine whether it is currently in the call establishment process. If it is, it will respond with an RRC reconfiguration complete message. If it is not in the call establishment process, it will be considered that the RRC reconfiguration has failed, triggering the RLF process, and no further steps will be executed.

[0203] Similarly, the above step S408 is also optional, and the UE may not determine whether it is in the call establishment process.

[0204] S410: The network side responds and initiates context establishment.

[0205] S411: The network sends the caller's Invite message to the UE, and the call service proceeds normally.

[0206] At this point, the call service is successfully established, and the UE can talk to the caller normally. In some implementations, the call service is successfully established and the UE rings normally.

[0207] S412 , cell B instructs the UE to switch to the BWP ID with abnormal configuration.

[0208] S413: The UE does not configure the abnormal configuration item and disables the function corresponding to the abnormal configuration item.

[0209] S414: The UE switches to the corresponding BWP ID to perform services.

[0210] Among them, if the abnormal configuration item in the configuration corresponding to the BWP ID to be switched to is A configuration, the UE does not configure the A configuration and disables the function corresponding to the A configuration. Exemplarily, the A configuration can be the configuration of the startingPRB of the pucch resource Id 40 as in the above example. There is an abnormality in the configuration, and the pucch resource Id 40 is used for CSI (channel status information) (CSI is a function for the UE to measure various qualities of the wireless channel and send it to the network side in the form of a report), then the UE no longer configures the pucch resource Id 40 and turns off the corresponding CSI function. The UE then switches to the corresponding BWP ID (that is, the BWP ID containing the abnormal configuration) to perform the service, that is, when performing the service, the UE no longer measures the various qualities of the wireless channel and reports them to the network side, but the service can proceed normally.

[0211] S415: The network side identifies an abnormality and instructs the UE to switch cells.

[0212] Because the UE no longer feeds back the function corresponding to the A configuration to the network side (for example, the UE no longer reports the various qualities of the measured wireless channel to the network side), the network side may recognize this abnormal situation, and the network side can instruct the UE to switch from the current cell (the cell corresponding to the BWP ID with the network configuration abnormality, that is, cell B) to the new cell, thereby avoiding the abnormal problem in the current cell (cell B).

[0213] In some implementations, before step S409, the UE may further perform S416: marking the BWPID with abnormal configuration, wherein the modem may mark the BWP ID.

[0214] In the above implementation, when the UE receives a BWP configured by the network side that contains an abnormal configuration, during the reconfiguration verification, the UE can determine the verification result as passed if the BWP to be used (i.e., BWP1) is verified normally and the call is currently being established. There is no need to determine the verification result of the RRC reconfiguration message as failed due to the abnormality of BWP2, thereby ensuring the normal operation of the current call service. At the same time, after the current service is successfully established, if the network side instructs the UE to switch to the BWP ID with the abnormal configuration, the UE can not configure the abnormal configuration items and disable the functions corresponding to the abnormal configuration items, which can also ensure the normal operation of subsequent services and improve the success rate of communication services.

[0215] Example 5

[0216] Different from the previous embodiment, when this embodiment detects that there is a configuration abnormality in the RRC reconfiguration message sent by the cell to the UE (such as an abnormality in the configuration of the BWP), it does not determine whether to go through the RLF process or reply normally to the RRC reconfiguration completion message based on the verification result. Instead, the number of abnormalities of the cell is counted. If the number of configuration abnormalities sent by the cell exceeds a preset threshold within a preset time, the UE (or modem) can BAR the cell and select a new cell.

[0217] Specifically, if Figure 12 As shown, the signaling interaction process of another example of a communication method in a wireless network provided in an embodiment of the present application may include:

[0218] S501, the UE resides in cell B and is in IDLE state.

[0219] S502: UE receives a service request sent by cell B.

[0220] S503, the UE requests to establish an RRC connection with the network side (core network).

[0221] The service request received by the UE may be a Paging message (paging message) for calling the UE. The Paging message may be a message generated by the network side after receiving the Invite message from the caller. The UE then requests to establish an RRC connection with the network side so that the network side initializes the context.

[0222] S504, cell B sends an RRC reconfiguration message to the UE.

[0223] Among them, some parameters corresponding to BWP IDs in the RRC reconfiguration message are configured abnormally.

[0224] S505: The UE identifies the RRC reconfiguration message and identifies that the RRC reconfiguration message contains an abnormally configured BWP configuration.

[0225] S506: If the UE identifies that the BWP configuration is abnormal, the number of abnormalities corresponding to cell B is increased by 1.

[0226] Among them, the BWP configuration abnormality identified by the UE here can be a BWP configuration abnormality to be used or a BWP configuration abnormality not to be used. That is to say, as long as the UE recognizes that there are abnormal configuration parameters of the BWP, the UE will increase the number of abnormalities corresponding to cell B by 1.

[0227] S507: Determine whether the number of abnormalities corresponding to cell B within a preset time exceeds a preset threshold. If so, execute S508; otherwise, execute S509.

[0228] The preset time may be a set unit time, such as 1 minute, and the preset threshold may be a set maximum number of times, such as 3 times.

[0229] S508, the UE temporarily BARs the cell B for a preset duration, and then executes S509.

[0230] If the number of exceptions corresponding to cell B exceeds a preset threshold within a preset time, it indicates that the configuration issue of cell B has not been corrected. Subsequent camping on cell B will still result in service failure. Therefore, the UE can BAR the cell (i.e., cell B with the configuration issue) for a period of time (preset duration), allowing the UE to subsequently camp on other cells. In some implementations, the preset duration can be 5 minutes. UE BARing the cell may mean prohibiting the UE from accessing the cell during cell selection, cell reselection, and / or cell handover.

[0231] S509: The UE triggers the RLF procedure and reselects a cell.

[0232] If the number of anomalies associated with cell B does not exceed a preset threshold within a preset time period, the UE does not temporarily bar the cell with the configuration anomaly. At this point, the UE can trigger an RLF procedure, citing RRC reconfiguration failure as the cause, and reselect a cell. Furthermore, after the UE temporarily barges to cell B, it can also trigger an RLF procedure and reselect a cell.

[0233] It can be understood that when the number of abnormalities corresponding to cell B does not exceed the preset threshold, since there is no BAR cell B, when the UE reselects a cell, it may still select cell B until the number of abnormalities corresponding to cell B exceeds the preset threshold. The UE will BAR cell B, and then select the new cell when reselecting the cell. After successful access to the new cell, there is a high probability that there will be no configuration abnormality problem in the new cell, so subsequent services will proceed normally.

[0234] In some implementations, after 5 minutes of BARing cell B, the UE will release the BAR operation and restore cell B to normal (i.e., cell B is restored to the unbarred state). If the UE subsequently camps on cell B and the configuration of cell B is still abnormal, the UE can BAR cell B again. In this case, the BAR time can be increased, for example, to 10 minutes for cell B, and so on.

[0235] In the above implementation, when the UE receives a BWP configured by the network side that contains an abnormal configuration, the number of abnormalities in the cell can be counted. If the number of times the cell sends configuration abnormalities exceeds a preset threshold within a preset time, the UE can BAR the cell for a period of time, so that the UE selects a new cell to reside in. The probability of configuration abnormalities occurring in the new cell is lower, thereby improving the success rate of subsequent communication services.

[0236] Example 6

[0237] Different from the previous embodiment, when this embodiment detects that there is a configuration abnormality in the RRC reconfiguration message sent by the cell to the UE (such as an abnormality in the configuration of the BWP), it does not determine whether to perform the RLF process or reply normally to the RRC reconfiguration completion message based on the verification result, but counts the number of abnormalities in the cell. If the number of configuration abnormalities sent by the cell exceeds a preset threshold within a preset time, the UE (or modem) can turn off the UE's dynamic switching BWP capability for a period of time, so that the UE continues to use the normally configured BWP.

[0238] Specifically, if Figure 13 As shown, the signaling interaction process of another example of a communication method in a wireless network provided in an embodiment of the present application may include:

[0239] S601: UE resides in cell B and is in IDLE state.

[0240] S602: UE receives a service request sent by cell B.

[0241] S603, the UE requests to establish an RRC connection with the network side (core network).

[0242] The service request received by the UE may be a Paging message (paging message) for calling the UE. The Paging message may be a message generated by the network side after receiving the Invite message from the caller. The UE then requests to establish an RRC connection with the network side so that the network side initializes the context.

[0243] S604, cell B sends an RRC reconfiguration message to the UE.

[0244] Among them, the parameter configurations corresponding to some BWP IDs in the RRC reconfiguration message are abnormal, for example, the parameter configuration corresponding to the non-currently activated BWP2 is abnormal.

[0245] S605: The UE identifies the RRC reconfiguration message and identifies that the RRC reconfiguration message contains an abnormally configured BWP configuration.

[0246] S606: If the UE identifies that the BWP configuration is abnormal, the number of abnormalities corresponding to cell B is increased by 1.

[0247] The BWP configuration anomaly identified by the UE here may be an unused BWP configuration anomaly, that is, upon identifying the presence of configuration anomaly parameters in BWP2, the UE increases the number of anomalies corresponding to cell B by 1.

[0248] S607: Determine whether the number of abnormalities corresponding to cell B within a preset time exceeds a preset threshold. If so, execute S608; otherwise, execute S609.

[0249] The preset time may be a set unit time, such as 1 minute, and the preset threshold may be a set maximum number of times, such as 3 times.

[0250] S608: The UE temporarily disables the dynamic BWP switching capability for a preset duration, and executes S609.

[0251] If the number of anomalies corresponding to cell B exceeds the preset threshold within the preset time, it means that the configuration problem of cell B has not been fixed, and the UE can turn off the dynamic switching BWP capability for a period of time (preset duration). Therefore, when the network side subsequently queries the UE's capability information, the capability information reported by the UE does not support BWP dynamic switching. The network side will not configure multiple BWPs for the UE, or will not instruct the UE to dynamically switch BWP, thereby avoiding the UE being instructed to switch to a BWP with a configuration problem.

[0252] S609: The UE triggers the RLF procedure and reselects a cell.

[0253] If the number of exceptions associated with cell B does not exceed a preset threshold within a preset time period, the UE does not need to temporarily disable the dynamic BWP capability. At this point, the UE can trigger an RLF procedure, citing RRC reconfiguration failure as the cause, and reselect a new cell for access. Furthermore, even after temporarily disabling the dynamic BWP capability, the UE can still trigger an RLF procedure and reselect a new cell. Understandably, if cell B has the best signal quality or the highest priority, it will likely still be selected.

[0254] S610: When a new service request is received, cell B queries the UE's capability information.

[0255] S611, the UE feeds back the UE capability information to cell B.

[0256] After the UE reconnects to the cell, if there is a service request, the cell will query the UE for capability information. At this time, the UE will feedback the UE's capabilities to cell B and report that the UE does not support dynamic BWP switching. After cell B obtains the UE's capability to support dynamic BWP switching, it will not configure multiple BWPs or dynamically switch BWPs, and subsequent communication services will be normal.

[0257] It is understandable that if the number of exceptions corresponding to cell B does not exceed the preset threshold, the UE may still select cell B when reselecting a cell. When a new service request comes in, cell B will also query the UE's capability information. Since the UE has not disabled the dynamic BWP switching capability at this time, the capability information fed back by the UE to cell B indicates that it supports BWP dynamic switching, and the communication service may still fail. Until the number of exceptions corresponding to cell B exceeds the preset threshold, the UE disables the dynamic BWP switching capability, and the capability information fed back by the UE to cell B indicates that the UE does not support BWP dynamic switching, then cell B will no longer dynamically switch BWP, so subsequent services will proceed normally.

[0258] Generally, if the UE does not disable the dynamic switching BWP capability, the capability information sent by the UE to cell B can carry the bwp-SwitchingDelay field and the bwp-SameNumerology field. After the UE disables the dynamic switching BWP capability, the capability information sent by the UE to cell B does not carry the bwp-SwitchingDelay field and the bwp-SameNumerology field.

[0259] In the above implementation, when the UE receives a BWP with an abnormal configuration configured by the network side, the number of abnormalities in the cell can be counted. If the number of times the cell sends configuration abnormalities exceeds a preset threshold within a preset time, the UE can temporarily turn off the dynamic switching BWP capability for a period of time. As a result, the network side will not subsequently send BWP switching instructions, thereby avoiding the problem of further failure of communication services and greatly improving the success rate of communication services.

[0260] It is understood that the processes for interacting with the cell or network side in the above embodiments can all be executed by the modem in the UE. Therefore, the communication method under the wireless network provided in the embodiments of the present application can be applied to terminal devices with wireless network communication capabilities, such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, ultra-mobile personal computers (UMPCs), netbooks, and personal digital assistants (PDAs). The embodiments of the present application do not impose any restrictions on the specific type of terminal devices.

[0261] For example, Figure 14 1 is a schematic diagram of the structure of an example terminal device 100 provided in an embodiment of the present application. Taking the terminal device 100 as a mobile phone as an example, the terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0262] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0263] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly retrieve it from the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0264] The wireless communication function of the terminal device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0265] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0266] In some embodiments, antenna 1 of terminal device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that terminal device 100 can communicate with a network and other devices via wireless communication technology. Wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. GNSS may include the global positioning system (GPS), the global navigation satellite system (GLONASS), the Beidou navigation satellite system (BDS), the quasi-zenith satellite system (QZSS) and / or the satellite based augmentation system (SBAS).

[0267] The internal memory 121 can be used to store computer executable program codes, and the executable program codes include instructions. The processor 110 executes various functional applications and data processing of the terminal device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created during the use of the terminal device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0268] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0269] The software system of the terminal device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present application, the Android system with a layered architecture is used as an example to illustrate the software structure of the terminal device 100.

[0270] Figure 15 This is a software structure diagram of the terminal device 100 in an embodiment of the present application. The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer. The application layer can include a series of application packages.

[0271] like Figure 15 As shown, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

[0272] The application framework layer provides an application programming interface (API) and programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0273] like Figure 15 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

[0274] The window manager is used to manage window programs. The window manager can obtain the size of the display screen, determine whether there is a status bar, lock the screen, take screenshots, etc. The content provider is used to store and obtain data and make this data accessible to applications. The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, etc. The phone manager is used to provide communication functions for the terminal device 100. For example, the management of call status (including answering, hanging up, etc.). The resource manager provides various resources for applications, such as localized strings, icons, pictures, layout files, video files, etc. The notification manager enables applications to display notification information in the status bar, which can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction.

[0275] The Android runtime includes the core library and the virtual machine. The Android runtime is responsible for scheduling and management of the Android system.

[0276] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0277] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0278] The system library can include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (such as OpenGL ES), and a 2D graphics engine (such as SGL).

[0279] The surface manager manages the display subsystem and provides fusion of 2D and 3D layers for multiple applications. The media library supports playback and recording of various common audio and video formats, as well as static image files. The media library supports a variety of audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG. The 3D graphics processing library implements 3D graphics drawing, image rendering, compositing, and layer processing. The 2D graphics engine is the drawing engine for 2D drawing.

[0280] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0281] The above describes in detail an example of a communication method under a wireless network provided by an embodiment of the present application. It is understandable that, in order to implement the above functions, the terminal device includes hardware and / or software modules corresponding to the execution of each function. Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of the present application.

[0282] The present application provides a terminal device that implements the behavior of the terminal device described in any of the above-described method embodiments. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to each sub-function of the above-described functionality. Specifically, the terminal device can be a user equipment device, such as a mobile phone.

[0283] An embodiment of the present application also provides a communication system, which includes the network device and terminal device described in any of the above embodiments.

[0284] The present application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer, implements the method flow related to the terminal device in any of the above method embodiments. Specifically, the computer may be the above terminal device.

[0285] The present application also provides a computer program or a computer program product including a computer program, which, when executed on a computer, enables the computer to implement the method flow related to the terminal device in any of the above method embodiments. Specifically, the computer can be the above terminal device.

[0286] The present application also provides a computer program or a computer program product including the computer program, which, when executed on a computer, enables the computer to implement the method flow related to the network device in any of the above method embodiments. Specifically, the computer can be the above network device.

[0287] The present application also provides an apparatus for use in a terminal device, wherein the apparatus is coupled to a memory and configured to read and execute instructions stored in the memory, so that the terminal device can perform the method flow associated with the terminal device in any of the above method embodiments. The memory may be integrated into the processor or independent of the processor. The apparatus may be a chip (e.g., a system on a chip (SoC)) on the terminal device.

[0288] It should also be understood that the memory mentioned in the embodiments of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0289] It should be noted that the memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.

[0290] In this application, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, "at least one of a, b, or c", or "at least one of a, b, and c" can all mean: a, b, c, ab (i.e., a and b), ac, bc, or abc, where a, b, and c can be single or multiple.

[0291] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. Some or all of the steps can be executed in parallel or sequentially. 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 the present application.

[0292] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel 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.

[0293] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0295] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0296] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, server, network device, or terminal device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application.

[0297] The device structure diagrams provided in the various device embodiments of the present invention only illustrate simplified designs of the corresponding devices. In actual applications, the device may include any number of transmitters, receivers, processors, memories, etc. to implement the functions or operations performed by the device in the various device embodiments of the present invention, and all devices that can implement the present application are within the scope of protection of this application.

[0298] The terms used in the embodiments of the present invention are for the purpose of describing specific embodiments only and are not intended to limit the present invention. The singular forms "a", "the" and "the" used in the embodiments of the present invention and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items. The character " / " herein generally indicates that the objects associated before and after are in an "or" relationship.

[0299] As used herein, the words “if” or “if” may be interpreted as “at the time of” or “when” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrases “if it is determined” or “if (stated condition or event) is detected” may be interpreted as “when it is determined” or “in response to the determination” or “when detecting (stated condition or event)” or “in response to detecting (stated condition or event),” depending on the context.

[0300] Those skilled in the art will understand that all or part of the steps in the above-mentioned embodiment method can be implemented by instructing related hardware through a program, and the program can be stored in a readable storage medium of a device. When the program is executed, it includes all or part of the above-mentioned steps, and the storage medium, such as FLASH, EEPROM, etc.

[0301] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that different embodiments can be combined. The above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any combination, modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A communication method in a wireless network, characterized in that: include: The terminal device receives multiple RRC reconfiguration messages sent by a first cell belonging to a first wireless network, where the multiple RRC reconfiguration messages carry at least first configuration information, wherein the first configuration information includes configuration information corresponding to a first BWP, the first BWP includes one or more BWPs, and the first BWP is a BWP configured by the first cell for the terminal device that does not currently need to be activated; When the number of times that the first configuration information in the multiple RRC reconfiguration messages is abnormal exceeds a preset threshold, the terminal device turns off the ability to dynamically switch BWP for a preset first time, wherein the abnormality in the first configuration information includes: a first parameter item with an abnormality in the first configuration information, the first parameter item with an abnormality is a startingPRB field with a configuration abnormality, and the startingPRB field with a configuration abnormality is the startingPRB field corresponding to the pucch resource Id in the first configuration information when it is a first value; The terminal device triggers the RLF process and reselects a cell; The terminal device continues to select the first cell as the serving cell; When there is a new service request, the terminal device receives a capability query request sent by the first cell; The terminal device sends first capability information to the first cell in response to the capability query request, where the first capability information indicates that the terminal device does not support dynamic BWP switching. After obtaining the first capability information, the first cell does not configure multiple BWPs for the terminal device or does not instruct the terminal device to dynamically switch the BWP. The first capability information indicating that the terminal device does not support BWP switching includes: the first capability information does not carry the bwp-SwitchingDelay field and the bwp-SameNumerology field.

2. The method according to claim 1, wherein The situation where the number of times that abnormalities exist in the first configuration information in the multiple RRC reconfiguration messages exceeds a preset threshold includes: the situation where the number of times that abnormalities exist in the first configuration information in the multiple RRC reconfiguration messages received within a preset second time exceeds a preset threshold, or the situation where the number of times that abnormalities exist in the first configuration information in the multiple RRC reconfiguration messages received in a preset number of consecutive times exceeds a preset threshold.

3. The method according to claim 1 or 2, wherein: The method also includes: when the number of times that the first configuration information in the multiple RRC reconfiguration messages is abnormal does not exceed a preset threshold, the terminal device triggers the RLF process.

4. The method according to any one of claims 1 to 3, characterized in that The first value is 40.

5. The method according to any one of claims 1 to 4, characterized in that The first wireless network is a 5G network.

6. A terminal device, characterized in that: The terminal device includes: a memory for storing instructions; A processor is configured to call and execute instructions in the memory so that the terminal device executes the method according to any one of claims 1 to 5.

7. A chip system, characterized in that: The chip system includes a processor for supporting a terminal device to implement the method according to any one of claims 1 to 5.

Images