CN119095173A

CN119095173A - A communication method, terminal device and chip system in wireless network

Info

Publication number: CN119095173A
Application number: CN202411170127.8A
Authority: CN
Inventors: 李海波; 王莎
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2023-09-26
Filing date: 2023-10-24
Publication date: 2024-12-06
Also published as: CN117651285B; CN117651285A

Abstract

The embodiment of the application provides a communication method, terminal equipment and a chip system under a wireless network, wherein the method comprises the steps that the terminal equipment 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, the first configuration information is configuration information which is configured by the first cell for the terminal equipment and needs to be activated currently, the second configuration information is configuration information which is configured by the first cell for the terminal equipment and needs to be activated not currently, under the condition that the first configuration information is abnormal, the terminal equipment triggers a Radio Link Failure (RLF) process, under the condition that the first configuration information is met, the terminal equipment sends an RRC reconfiguration completion message responding to the RRC reconfiguration message to the first cell, and the first condition comprises that the first configuration information is not abnormal and the second configuration information is abnormal. The method can improve the success rate of terminal service under the wireless network.

Description

Communication method, terminal equipment and chip system under wireless network

The application discloses a split application of China patent application, which is submitted to the national intellectual property agency, the application number is 202311391334.1, and the application name is 'a communication method, terminal equipment and chip system under a wireless network' at the 10 th month of 2023. The present application claims priority from the chinese patent application filed at 26, 09, 2023, filed with the national intellectual property office under application number 202311273311.0, application name "communication method under 5G network, terminal device and chip system", the entire contents of which are incorporated herein by reference.

Technical Field

The present application relates to the field of terminal device communication, and in particular, to a communication method, a terminal device, and a chip system in a wireless network.

Background

Currently, the fifth generation mobile communication network (5G network) is gradually in commercial use. When the user uses the terminal equipment, the user can not only surf the internet through the 5G network, but also call through the 5G network, for example, the 5G network adopts a new air interface to bear voice (voice over new radio, VONR) to realize the call service, so that the user experience is greatly improved, but meanwhile, compared with a mature 4G long-term evolution (long term evolution, LTE) network, the VONR of the 5G network has some network compatibility problems, which can cause the terminal equipment to fail to execute the service.

For example, taking a call service as an example, a problem that a terminal device (such as a mobile phone) supporting a 5G network is not always called can occur, for example, when a calling terminal dials the called terminal, the calling terminal can broadcast a prompt that the call cannot be switched on temporarily, and if a called side starts a leakage short message reminding service, a leakage short message reminding is generated.

Disclosure of Invention

The application provides a communication method, terminal equipment and a chip system under a wireless network, so as to improve the success rate of terminal service under the wireless network.

In a first aspect, a communication method in a wireless network is provided, where a terminal device receives a radio resource control RRC reconfiguration message sent by a first cell belonging to a first wireless network, where the RRC reconfiguration message carries first configuration information and second configuration information, where the first configuration information is configuration information that is configured by the first cell for the terminal device and that needs to be activated currently, the second configuration information is configuration information that is configured by the first cell for the terminal device and that needs to be activated not currently, the terminal device triggers a radio link failure RLF procedure if the first configuration information is abnormal, and sends an RRC reconfiguration complete message in response to the RRC reconfiguration message to the first cell if a first condition is met, where the first condition includes that the first configuration information is not abnormal and the second configuration information is abnormal.

According to the RRC reconfiguration message, the terminal device actually uses the first configuration information instead of the second configuration information, and if the first configuration information is abnormal, the terminal device may trigger the RLF procedure. If the first configuration information is not abnormal but the second configuration information is abnormal, the terminal equipment can judge the verification result as passing the verification when the reconfiguration verification is performed, and the verification result of the RRC reconfiguration message is not judged as failing the verification because the second configuration information is abnormal, so that the normal operation of the current communication service can be ensured, and the success rate of the communication service is improved.

In some implementations, the first configuration information is configuration information corresponding to a first part of bandwidth BWP, the second configuration information is configuration information corresponding to a second BWP, the first BWP is a BWP configured by the first cell for the terminal device and currently requiring activation, the first BWP includes one or more BWP, the second BWP is a BWP configured by the first cell for the terminal device and not currently requiring activation, and the second BWP includes one or more BWP.

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 (e.g., BWP 1), the first BWP is the BWP that is currently required to be activated for the 5G cell configuration, and may be both firstActiveDownlinkBWP and firstActiveUplinkBWP in the RRC reconfiguration message are configured as BWP1. When the first BWP includes two BWP (e.g., BWP-1 and BWP-2), the first BWP is the BWP currently required to be activated for the 5G cell configuration, and may be configured as BWP-1 and firstActiveUplinkBWP in the RRC reconfiguration message firstActiveDownlinkBWP.

The second BWP is a BWP configured by the 5G cell that is not currently required to be activated, and it can be understood that neither of the BWP configured by firstActiveDownlinkBWP and firstActiveUplinkBWP in the RRC reconfiguration message is the second BWP.

Thus, if the first BWP is not abnormal but the second BWP is abnormal, the terminal device can determine that the verification result is passed when the terminal device reconfigures and verifies, and the verification result of the RRC reconfiguration message is not required to be determined as not passed when the second BWP is abnormal, thereby ensuring that the current communication service is normally performed and improving the success rate of the communication service.

In some implementations, the first condition further includes that the terminal device is currently in the call setup process.

Under the condition that the terminal equipment is in the process of establishing the call, the terminal equipment judges the verification result to pass the verification, so that the success rate of the call service can be improved.

In some implementations, the method further includes triggering the RLF procedure by the terminal device if the first configuration information is not abnormal, the second configuration information is abnormal, and the terminal device is not currently in the call setup process.

In some implementations, after the terminal device sends the RRC reconfiguration complete message responding to the RRC reconfiguration message to the first cell, the method further includes the terminal device receiving a first message sent by the first cell, the first message being used for indicating the terminal device to switch from the first configuration information to the second configuration information, and triggering the RLF procedure after the terminal device receives the first message sent by the first cell.

Since the first configuration information used by the terminal device is configured normally, if the configuration information is not switched, the subsequent communication service of the terminal device is performed normally. However, if the cell instructs the terminal device to switch to the second configuration information including the abnormal configuration, the terminal device may determine that the parameter configuration corresponding to the configuration information is abnormal, and then the communication service may fail with a high probability, so that the terminal device may trigger the RLF procedure at this time.

In some implementations, after the terminal device sends the RRC reconfiguration complete message responding to the RRC reconfiguration message to the first cell, the method further comprises the step that the terminal device sends a first registration request to the first cell, the type of the first registration request is mobile registration update MRU, the value of a follow-up 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 responds to the capability query request and sends first capability information to the first cell, and the first capability information indicates that the terminal device does not support dynamic configuration information switching.

The size of the FOR field is 1bit, when the bit is 0, the following no-pending (no-slow-on request pending) is not needed, and when the bit is 1, the following request pending (slow-on request pending) is indicated. Then, if the cell receives a registration request with a value of 0 in the FOR field, the cell triggers the capability of querying the terminal device.

In the implementation mode, after the current service is successfully established, the terminal equipment can actively and temporarily close the capability of dynamically switching configuration information and synchronize the capability to the network side, so that the subsequent network side does not issue a command for switching the configuration information, the problem that the communication service is likely to fail again is avoided, and the success rate of the communication service is improved to a greater extent.

In some implementations, the first capability information indicates that the terminal device does not support dynamic configuration information handover, specifically, the first capability information does not carry bwp-SWITCHINGDELAY fields and bwp-SameNumerology fields.

In some implementations, before the terminal device sends the first capability information to the first cell, the method further includes the terminal device turning off the capability of the dynamic handover configuration information.

Wherein, a parameter can be set in the terminal device, and the parameter characterizes whether the terminal device starts the capability of dynamically switching configuration information. The terminal device may modify the value of the parameter to characterize the ability to shut down the dynamic handover configuration information. For example, the parameter value is 1, which indicates that the terminal device is capable of starting the dynamic switching configuration information, and the parameter value is 0, which indicates that the terminal device is capable of closing the dynamic switching configuration information.

In some implementations, after the terminal equipment sends the RRC reconfiguration complete message responding to the RRC reconfiguration message to the first cell, the method further comprises the steps that the terminal equipment receives a first message sent by the first cell, the first message is used for indicating the terminal to switch from the first configuration information to the second configuration information, after the terminal equipment receives the first message sent by the first cell, a first function corresponding to the second configuration information is enabled, and the terminal equipment switches from the first configuration information to the second configuration information, wherein the first function is a function corresponding to a first parameter item with abnormality in the second configuration information.

In the implementation manner, after the current service is established successfully, if the cell indicates that the terminal equipment is switched to the BWP ID with abnormal configuration, the terminal equipment can not configure the abnormal configuration item and enable the corresponding function, so that the subsequent service can be ensured to be normally performed, and the success rate of the communication service is improved.

In some implementations, the first parameter item with the exception is a startingPRB field with the configuration exception, the startingPRB field with the configuration exception is a startingPRB field corresponding to when pucch resource Id in the second configuration information is the first value, and the first function is CSI when pucch resource Id for CSI (channel status information) is the first value.

In some implementations, the first value is 40.

The CSI is a function that the terminal device measures various qualities of the wireless channel and sends the quality to the network in a report form, and if the field configuration corresponding to the function is abnormal, the terminal device may not configure pucch resource Id to 40 any more, and close the corresponding CSI function. And then the terminal equipment is switched to the second configuration information to carry out service, namely the terminal equipment does not measure and report various qualities of the wireless channel any more when carrying out service, but the service can be normally carried out.

In some implementations, in the case that the second configuration information is abnormal, the method further includes performing abnormal marking on the identification of the second configuration information.

If the terminal device marks the second configuration information, the terminal device can execute corresponding processing flow if the cell indicates that the terminal device is switched to the marked configuration information, namely, the configuration information which characterizes that the terminal device is switched to the configuration abnormality.

In a second aspect, a communication method in a wireless network is provided, where the terminal device receives a plurality of RRC reconfiguration messages sent by a 5G cell, where the plurality of RRC reconfiguration messages carry at least first configuration information, where the first configuration information includes configuration information corresponding to a first BWP, the first BWP includes one or more BWP, and the terminal device triggers an RLF procedure when a number of times that the first configuration information is abnormal in the plurality of RRC reconfiguration messages exceeds a preset threshold, and prohibits selection of the 5G cell as a serving cell within a preset duration.

In the implementation manner, when the terminal equipment receives the BWP configured by the cell and including the abnormal configuration, the abnormal times of the cell can be counted, if the abnormal times of the cell issued by the cell exceeds a preset threshold value in a preset time, the terminal equipment can BAR the cell for a period of time, so that the terminal equipment selects a new cell to reside, the probability of the abnormal configuration occurring on the new cell is smaller, and the success rate of the subsequent communication service is improved.

In a third aspect, a communication method in a wireless network is provided, where the terminal device receives multiple RRC reconfiguration messages sent by a 5G cell, where the multiple RRC reconfiguration messages at least carry first configuration information, where the first configuration information includes configuration information corresponding to a first BWP, the first BWP includes one or multiple BWP, the first BWP is a BWP configured by the 5G cell for non-current activation, and in the multiple RRC reconfiguration messages, the terminal device closes a capability preset for dynamically switching BWP for a first time when a number of abnormalities exists in the first configuration information exceeds a preset threshold.

In this implementation manner, when the terminal device receives the configured BWP including the abnormal configuration, the number of abnormal times of the cell may be counted, if the number of times of issuing the configuration abnormality by the cell exceeds a preset threshold in a preset time, the terminal device may temporarily close the dynamic BWP switching capability for a period of time, so that the subsequent network side will not issue a BWP switching instruction, so that the terminal device will not switch to the first BWP having the abnormal configuration, thereby avoiding the problem of re-failure of the communication service, and greatly improving the success rate of the communication service.

In some implementations, the case that the number of times of abnormality of the first configuration information in the plurality of RRC reconfiguration messages exceeds a preset threshold includes the case that the number of times of abnormality of the first configuration information in the plurality of RRC reconfiguration messages received within a preset second time exceeds the preset threshold, or the case that the number of times of abnormality of the first configuration information in the plurality of RRC reconfiguration messages exceeds the preset threshold in a preset number of RRC reconfiguration messages continuously received.

In some implementations, the method further includes triggering the RLF procedure by the terminal device if the number of times of abnormality in the first configuration information in the plurality of RRC reconfiguration messages does not exceed a preset threshold.

In some implementations, in the case that the terminal device closes the capability of the dynamic BWP to switch for a preset first time, the method further includes the terminal device receiving a capability query request sent by the 5G cell, and the terminal device sending first capability information to the 5G cell in response to the capability query request, the first capability information indicating that the terminal device does not support the dynamic BWP switch.

After the terminal device closes the BWP capability, the terminal device may feed back capability information to the cell, indicating that the terminal device does not support BWP dynamic switching, and the cell will not dynamically switch BWP any more, so as to ensure that the subsequent service will be performed normally.

In a fourth aspect, there is provided a terminal device comprising:

a memory for storing instructions;

a processor for invoking and executing instructions in the memory to cause the terminal device to perform the method of any of the first to third aspects above.

In a fifth aspect, a chip system is provided, where the chip system includes a processing circuit, a receiving pin, and a transmitting pin, where the receiving pin, the transmitting pin, and the processing circuit communicate with each other through an internal connection path, and the processing circuit performs the method of any one of the first to third aspects to control the receiving pin to receive a signal, and control the transmitting pin to transmit a signal.

In a sixth aspect, a chip system is provided, where the chip system includes a processor, and is configured to support a terminal device to implement the wireless communication method according to any one of the first to third aspects.

In some implementations, the system-on-chip may be a modem chip.

Drawings

Fig. 1 is a schematic diagram illustrating relevant cell parameters in a BWP configuration according to an embodiment of the present application;

Fig. 2 is a diagram illustrating an example INITIAL DL/UL BWP parameter according to an embodiment of the present application;

FIG. 3 is a schematic diagram illustrating exemplary configuration parameters ServingCellConfig according to one embodiment of the present application;

Fig. 4 is a schematic diagram of a correspondence relationship between an example LocationAndBandwidth provided in an embodiment of the present application and a length of a starting virtual resource block and a continuously allocated resource block;

FIG. 5 is a signaling interaction flow diagram for a telephony service in accordance with the related art;

FIG. 6 is a schematic diagram illustrating an example of abnormality of BWP configuration parameters according to an embodiment of the present application;

fig. 7 is a signaling interaction flow chart of an example of a communication method under a wireless network according to an embodiment of the present application;

Fig. 8 is a signaling interaction flow chart of another example of a communication method under a wireless network according to an embodiment of the present application;

Fig. 9 is a signaling interaction flow chart of a communication method under a wireless network according to another embodiment of the present application;

FIG. 10 is a schematic diagram illustrating an exemplary definition of bwp-SWITCHINGDELAY fields and bwp-SameNumerology fields according to an embodiment of the present application;

fig. 11 is a signaling interaction flow chart of a communication method under a wireless network according to another embodiment of the present application;

fig. 12 is a signaling interaction flow chart of a communication method under a wireless network according to another embodiment of the present application;

Fig. 13 is a signaling interaction flow chart of a communication method under a wireless network according to another embodiment of the present application;

fig. 14 is a schematic structural diagram of an example of a terminal device according to an embodiment of the present application;

Fig. 15 is a block diagram of a software structure of an example terminal device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the embodiment of the present application, unless otherwise indicated, "/" means or, for example, a/B may represent a or B, and "and/or" herein is merely an association relationship describing an association object, which means that three relationships may exist, for example, a and/or B, and that three cases, i.e., a alone, a and B together, and B alone, exist. In addition, in the description of the embodiments of the present application, "plurality" means two or more than two.

The terms "first," "second," "third," and the like, are used below for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first", "a second", or a third "may explicitly or implicitly include one or more such feature.

Currently, in commercial use, a terminal device may also realize communication services such as internet surfing and call making under the 5G network, and then the terminal device (e.g. a mobile phone, also referred to as UE in the embodiment of the present application) needs to perform 5G network access to establish a 5G session.

Wherein, after the user opens the function of the 5G network on the UE, the UE may automatically connect to the 5G network and establish a communication connection, and the process may include:

1. And (3) cell searching and selecting, namely the UE can scan the surrounding 5G frequency bands, acquire available cell information and select an optimal cell to access based on a preset cell selection algorithm.

2. And (3) cell access, namely, the UE sends an access request to the optimal cell, after receiving the request, the cell can carry out access authorization judgment, and if the UE meets the access condition, the cell can allocate a temporary mobile user identifier (temporary mobile subscriber identity, TMSI) for the UE. After receiving the access authorization of the cell, the UE may perform a confirmation access request and send a confirmation message to the cell. The cell receives the confirmation message, i.e. completes the access procedure, and assigns an international mobile subscriber identity (international mobile subscriber identity, IMSI) to the UE.

3. And after the UE accesses the cell, the UE can send a security negotiation request to the core network so as to ensure the security of the subsequent communication service. After receiving the security negotiation request, the core network may select an appropriate security protocol according to the identity information of the UE and the network policy, and send a negotiation response to the UE. The UE receives the negotiation response, and if the negotiation request is confirmed, a negotiation confirmation message is sent to the core network. After receiving the negotiation confirmation message, the core network completes the security negotiation and establishment process, and generates a relevant key for the UE.

4. And after the service request and the establishment, if the UE is to carry out the communication service, the service request can be sent to the core network to inform the core network of the communication service required to be carried out. The core network receives the service request, can select a proper service strategy according to the requirement of the UE and the condition of network resources, and sends a service response to the UE. The UE receives the service response and may send a service confirmation message to the core network if the service request is confirmed. The core network receives the service confirmation message, completes the service request and establishment process, and can allocate corresponding service resources for the UE.

However, in the related development process of the 5G network connection, researchers find that the bandwidth of the 5G network is greatly increased compared with that of the 4G network, but some communication services (such as the internet of things service) performed by the UE do not need a large bandwidth, and if all services or all terminal devices (including devices other than the mobile phone) are forced to support the large bandwidth, resource waste is caused. Thus, in a 5G network, the concept of fractional Bandwidth (BWP) is proposed, i.e. a set of consecutive common resource blocks (common resource blocks, CRB) at subcarrier intervals in a fractional bandwidth in one carrier, e.g. a certain cell at 100 MHZ. The BWP is a continuous bandwidth resource allocated to the UE by the network side (core network), so that flexible data transmission between the network side and the UE can be realized, and each BWP corresponds to a specific Numerology (system parameter) and is a necessary configuration for the UE to access the 5G network. Wherein different UEs may configure different BWPs, and different communication services of one UE may configure different BWPs.

In general, BWP can be divided into initial BWP (initial BWP), dedicated BWP (dedicated BWP), active BWP (active BWP), and default BWP (default BWP). Initial BWP-BWP used in the UE initial access stage, the initial BWP is divided into a downlink initial BWP and an uplink initial BWP. Dedicated BWP-BWP configured by the UE in the radio resource control (radio resource control, RRC) connected state. The active BWP is that the UE activates 1 of the dedicated BWPs at a certain moment in the RRC-connected state, and the protocol specifies that the UE can activate only 1 configured dedicated BWP as its active BWP at the current moment in the RRC-connected state. Default BWP-the BWP the UE works when its BWP inactivity timer (INACTIVITY TIMER) expires while in RRC connected state, is also 1 of the dedicated bwrps, indicating which configured dedicated bwrp the UE uses as default bwrp through RRC signaling.

As can be seen from the description, the network side may perform BWP configuration to the UE through RRC signaling when the UE accesses the cell. Then, the purpose of uplink and downlink bandwidth variation used by the UE can be achieved by configuring different BWP to the UE through the network side, and besides the inconsistent bandwidth, the configuration parameters of other physical layer channels or signals are configured independently by the different BWP. Therefore, the network side can switch the BWP of the UE to a large bandwidth according to the current traffic, for example, when a large data volume transmission is required. In addition, the network side also switches the UE to BWP with better channel quality according to the measured value of each frequency domain channel.

The UE is playing the high-definition video of 8K at a certain moment, and the network side can configure the UE to access the large BWP when the UE needs the support of the large bandwidth of 5G, and after the UE finishes viewing the video, the user starts to send a message by using the UE, and the network side only needs to allocate the small BWP to the UE when the UE and the network side can communicate with each other with the small transmission power, so as to achieve the purpose of saving resources.

In some implementations, the relevant cell parameters in the BWP configuration may be seen in fig. 1, where the downlink BWP (downlink BWP) may include BWP identification (BWP ID), frequency domain location and bandwidth of the bandwidth part (LocationAndBandwidth), cell specific parameters of the physical downlink control channel (physical downlink control channel, PDCCH) (PDCCH-CommonConfig), cell specific parameters of the physical downlink shared channel (physical downlink SHARED CHANNEL, PDSCH) (PDSCH-CommonConfig), UE specific PDCCH configuration (PDCCH-Config), and UE specific PDSCH configuration (PDSCH-Config), etc., and the uplink BWP (uplink BWP) may include BWP identification (BWP ID), frequency domain location and bandwidth of the bandwidth part (LocationAndBandwidth), cell specific parameters of the physical uplink control channel (physical uplink control channel, PUCCH) (PUCCH-CommonConfig), cell specific parameters of the physical uplink shared channel (physical uplink SHARED CHANNEL, PUSCH) (PUSCH-CommonConfig), UE specific configuration (PUCCH-Config), UE specific configuration (PUSCH-Config), and the like. Illustratively, the process of BWP configuration may include:

First, the network side configures an initial downlink/uplink BWP (INITIAL DL/UL BWP) in the system information block 1 (systeminformation block, sib1), whose BWP id=0. It can be appreciated that the SIB1 message of the 5G network may carry basic information required for the UE to access the radio cell, random access parameters, and availability and scheduling periods of other SIBs. For example, as described in the standard protocol 38.331 with respect to INITIAL DL/UL BWP, as shown in fig. 2, servingCellConfigCommonSIB is used to configure cell-specific parameters of a UE's serving cell in SIB1, and downlink parameters (DownlinkConfigCommonSIB) and uplink parameters (UplinkConfigCommonSIB) are defined in ServingCellConfigCommonSIB. An initial uplink BWP: initialUplinkBWP (for providing initial uplink BWP parameters of the cell) is defined in UplinkConfigCommonSIB, and an initial downlink BWP: initialDownlinkBWP (for providing initial downlink BWP parameters of the cell) is defined in DownlinkConfigCommonSIB.

The UE acquires INITIAL DL/UL BWP in the initial access procedure, which includes 1. Decoding the main system information block (master information block, MIB), acquiring Coreset #0 information, 2. Listening to SIB1 information in Coreset #0, 3. Decoding SIB1, acquiring INITIAL DL/UL BWP.

Second, before entering the connected state, the UE can only transmit and receive on the Initial BWP (Initial BWP), and before receiving the MSG4, the UE can also only operate on Coreset #0 for downlink, and the network side only schedules on Coreset #0. After the UE enters the connected state, a maximum of 4 BWP may be reconfigured in the configuration of the connected state, e.g., in the serving cell configuration (ServingCellConfig) of the downlink configuration. Therefore, the UE side needs to store 5 BWP configurations at maximum. At the same time, however, at most one BWP is active by the UE, and after entering the connected state, the first active BWP is determined by the identity (firstActiveDownlinkBWP-Id) of the first active downlink BWP.

Illustratively, the configuration parameters ServingCellConfig may be seen in FIG. 3, with maxNorfBWPs of the configuration parameters characterizing the maximum number of BWPs configured (e.g., 4), firstActiveDownlinkBWP-Id being the first BWP to be effected. The explanation of firstActiveDownlinkBWP-Id in the protocol is that this field contains the BWP-Id, i.e. the BWP to be activated when performing the RRC reconfiguration (if this field is undefined, the RRC reconfiguration does not force a BWP handover).

In practical applications, the network side may also perform BWP handover on the UE according to different communication services or other requirements, and the handover process may include the following modes:

1. the network side instructs the UE to perform BWP handover through downlink control information (downlink control information, DCI).

Wherein, the DCI format 0-1/1-1 has a BWP indication field (Bandwidth part indicator field) therein, and if the BWP indicated by the field (field, or referred to as field) is inconsistent with the current BWP, the UE needs to perform BWP handover. Since the field is at most 2 bits and the UE is configured with at most 5 BWP according to the foregoing description, it is apparent that 2 bits cannot represent 5 BWP, thus distinguishing the two cases.

1.1)Initial BWP+3BWP

Taking the description of DCI formats 0-1 in standard 38.212 as an example, bandwidth part indicator indicates that BWP-Id is used as the position index in ascending order.

1.2)Initial BWP+4BWP

At this time, the UE cannot switch to the Initial BWP through DCI, but can switch among the 4 BWP configured otherwise.

2. There is no random access resource on the currently active non-Initial BWP and a switch is made to the Initial BWP.

If random access needs to be sent on the currently active BWP due to, for example, timing advance (TIMING ADVANCE, TA) Timer timeout, but no PRACH configuration is on the current BWP configuration, then the BWP needs to be switched to the Initial UL BWP for random access, and the PRACH configuration may be considered to exist on the Initial UL BWP.

3. The BWP inactivity timer (INACTIVITY TIMER) times out, switching to the default BWP.

In case of a BWP INACTIVITY TIMER timeout, if the identity (defaultDownlinkBWP-Id) of the default downlink BWP is configured, the UE will switch to the BWP, and if not configured, the UE switches to the initial downlink BWP (initialDownlinkBWP).

4. The RRC reconfiguration performs BWP handover.

I.e. directly changing firstDownlinkActiveBWP-Id or firstUplinkActiveBWP-Id.

However, whether BWP is configured or BWP is switched, it is necessary for the UE to know which part of bandwidth resources in the overall bandwidth is specifically allocated. As can be seen from fig. 1, among the relevant cell parameters of the BWP configuration, one parameter is the frequency domain position of the bandwidth portion and the bandwidth (LocationAndBandwidth), and the UE can obtain two parameters of the starting virtual resource block (Offset) and the length of the continuously allocated resource block (i.e. the bandwidth size) according to the parameters.

The BWP resource allocation method generally adopts RIV (resource indication value) method according to the calculation method specified by the protocol, and the RIV (i.e. LocationAndBandwidth) corresponds to the length of the starting virtual resource block and the continuously allocated resource block. Exemplary correspondence of LocationAndBandwidth to the length of the starting virtual resource block, the consecutive allocated resource blocks is shown in FIG. 4, wherein the BWP parameters include LocationAndBandwidth parameters in the range (0,37949), according to the formula of protocol 38.214L _RBs and RB _start can be calculated, wherein RIV is LocationAndBandwidth, L _RBs represents the length of continuously allocated resource blocks in cell Bandwidth (BWP Bandwidth), RB _start represents the initial virtual resource block, and the protocol is setThe offset offsetToCarrier of the starting virtual resource block may also be defined in parameter SCS-SPECIFICCARRIER if the starting virtual resource block is offset from the starting point.

Normally, when the network side configures the plurality of BWP to the UE, if the BWP parameters are normal, the UE may reply to the network side with a reconfiguration complete message to complete the configuration procedure, and the subsequent UE may perform communication traffic on the activated BWP. However, it is found through research that in some scenarios, because a certain parameter configuration of BWP of a PUCCH channel in an RRC reconfiguration message sent to a UE by a network side has a problem, the UE does not pass the verification of the RRC reconfiguration message, and then the UE does not send an RRC reconfiguration complete message to the network side (i.e. the UE does not respond to the RRC reconfiguration message), and further the UE cannot establish a data radio bearer (data radio bearer, DRB) and the network initiates a UE context failure, which eventually results in a problem that a calling party is not passed in a call service scenario or a data service is not available in a data service scenario.

Illustratively, as shown in fig. 5, it is a signaling interaction flow chart for call traffic in the related art. When the UE resides in the cell B and is in an IDLE state (IDLE state), the UE has a service requirement (e.g., the UE receives a Paging message for calling the UE), and the UE establishes an RRC connection with a network side (core network), the core network issues an RRC reconfiguration message through the cell B, and the core network issues an RRC reconfiguration message with a parameter configuration abnormality (e.g., BWP1 normal, BWP2 abnormality) corresponding to a part of BWP in the RRC reconfiguration message, and the UE recognizes the BWP configuration abnormality and triggers a radio link failure (radio link failure, RLF) procedure. Since the core network does not receive the reconfiguration complete message replied by the UE, the UE context cannot be initialized, that is, the UE context cannot be initialized, and the invite (invite) message of the calling terminal cannot be issued, which results in the problem that the called party cannot be connected. If the priority of the cell B is highest or the signal is best, the UE can select the cell B to reside, and if the configuration of the RRC reconfiguration message sent by the cell B is abnormal, the UE enters a circulation failure process.

To solve this problem, we analyze the configuration parameters of BWP2, and if the configuration exception of BWP1 and BWP2 is carried in the RRC reconfiguration message issued by the network side, the value of LocationAndBandwidth is configured to 17325 (as shown in (a) of fig. 6) according to the formula17325=275× (64-1) +0, I.e. RB _start＝0,L_RBs =64 should be calculated, the length of the consecutive allocated resource blocks is maximally 64. However, in the configuration parameters of BWP2, starting PRB corresponding to the pucch resource Id resource block is configured to 110 (as shown in (b) and (c) of fig. 6), and exceeds the range of L _RBs, and obviously, the configuration of (c) of fig. 6 is abnormal, so that the UE checks that the RRC reconfiguration message does not pass, resulting in called failure or unavailable data service.

Therefore, the reason for the failure of RRC reconfiguration in the above related art is that 1, calculated according to the protocol formula, if the starting PRB configured by the network side exceeds the range of L _RBs calculated theoretically, it is unreasonable, and if the network side causes the UE to switch to the BWP ID during the subsequent data transmission, a problem will occur. 2. For this misconfiguration term (i.e., startingPRB), future UE usage may be problematic, so the modem in the UE will determine in this case that the RRC reconfiguration message check fails and the UE does not reply to the reconfiguration complete message.

Based on this, some embodiments of the present application provide a communication method under a wireless network, so as to improve the success rate of terminal services under the wireless network.

Example 1

In one scenario, the network side configures two BWP for the UE through one RRC reconfiguration message, e.g., BWP id=1 and BWP id=2, and both of firstActiveDownlinkBWP and firstActiveUplinkBWP in the RRC reconfiguration message are configured as BWP1, i.e., firstActiveDownlinkBWP-ID 1 and firstActiveUplinkBWP-ID 1 are carried in the RRC reconfiguration message, that is, the network side instructs the UE to use BWP1 as the currently active BWP of the uplink or the downlink through the RRC reconfiguration message, and BWP2 is not used as the currently active BWP. It is assumed that the configuration of BWP1 is normal in the RRC reconfiguration message, and that the configuration of BWP2 is abnormal in the RRC reconfiguration message (e.g., abnormal configuration shown in (c) of fig. 6).

According to the RRC reconfiguration message, the BWP actually used by the UE (i.e., firstActiveDownlinkBWP and firstActiveUplinkBWP) is normal BWP1 instead of BWP2 having an abnormal problem, and the network side configures two BWP IDs for the UE, but the UE will not necessarily perform BWP handover in the future (i.e., will not necessarily use BWP2 having an abnormal problem), so that during reconfiguration check, the modem in the UE may determine that the check result is checked as passing when BWP1 is checked as normal, and may not determine that the check result of the RRC reconfiguration message is checked as not passing when BWP2 is abnormal, and then determine whether to report an error according to circumstances when the UE really needs to switch to the BWP ID having an abnormal problem (i.e., BWP 2).

Specifically, as shown in fig. 7, a signaling interaction flow of an exemplary communication method under a wireless network according to an embodiment of the present application may include:

s101, the UE resides in the cell B and is in an IDLE state.

The UE may camp on cell B by cell search and access. It can be appreciated that if the UE is not currently doing any traffic, it is in IDLE state.

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

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

The service request received by the UE may be a Paging message (Paging message) for calling the UE, which may be a message generated after the Invite message of the calling party is received at the network side, and then the UE requests establishment of an RRC connection with the network side to initialize a context at the network side.

S104, the cell B issues RRC reconfiguration information to the UE.

S105, the UE identifies the RRC reconfiguration message (the identification may also be referred to as checking), and identifies that the BWP configuration with the configuration abnormality exists in the RRC reconfiguration message.

For example, the RRC reconfiguration message configures two BWP, BWP1 and BWP2, for the UE. Here, it is assumed that there is an abnormality in the parameter configuration corresponding to a part of BWP ID in the RRC reconfiguration message, for example, there is an abnormality in the parameter configuration corresponding to BWP2.

The UE may identify the RRC reconfiguration message according to the calculation mode specified by the above protocol, and may further identify BWP with abnormal configuration.

S106, the UE determines whether the current BWP configuration is abnormal, if so, S107 is performed, and if not, S108 is performed.

Wherein the current BWP, i.e. the BWP to be used by the UE (or called to be activated), the UE determines whether the current BWP configuration is abnormal, i.e. whether the configuration of the parameters corresponding to the BWP IDs to be used by the UE (BWP IDs to be used, i.e. firstDownlinkActiveBWP-ID and firstUplinkActiveBWP-ID) is abnormal. Here, it may be determined by the modem in the UE whether the configuration of the parameter corresponding to the BWP ID to be used by the UE is abnormal. For example, assuming that BWP to be used by the UE is configured as the aforementioned BWP1, the configuration of parameters corresponding to BWP1 is normal as described above, the UE may perform S108 and the UE may switch to the BWP1 after receiving the RRC reconfiguration message.

S107, the UE does not reply the RRC reconfiguration complete message to the cell B, and triggers the RLF flow.

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 fails, and does not reply to the cell B (network side) with an RRC reconfiguration complete message, and further the modem triggers the RLF procedure, and does not execute subsequent steps.

S108, the UE replies an RRC reconfiguration complete message to the cell B.

S109, the network side responds to the initialization context establishment.

S110, the network side sends Invite message of calling party to the UE, and the call service is normally carried out.

That is, if the configuration of the parameters corresponding to the BWP ID to be used by the UE is not abnormal, the modem may normally reply to the RRC reconfiguration complete message after performing RRC reconfiguration, and finally, the service (i.e., the call service corresponding to the call) is successfully established.

S111, cell B instructs the UE to switch to BWP ID with abnormal configuration.

S112, the UE triggers the RLF flow.

Since the parameters of the BWP (i.e., BWP 1) currently used by the UE are normally configured, if the BWP handover is not performed, the subsequent communication traffic of the UE is normally performed. However, if the cell B instructs the UE to switch to BWP (i.e. BWP 2) containing abnormal configuration, the UE may determine that the configuration of the parameters corresponding to the BWP is abnormal, and then the UE may fail to perform the communication service with a high probability, so that the UE (or a modem in the UE) may trigger the RLF procedure at this time.

In some implementations, prior to step S108, the UE may also perform S112, marking the BWP ID for which there is an abnormal configuration, which may be marked by the modem. Then, correspondingly, if cell B instructs the UE to switch to the BWP ID marked as abnormal in S111, the UE triggers the RLF procedure. It is understood that the BWP ID that cell B instructs the UE to switch to the flag may be a cell B transmission message (e.g., RRC reconfiguration message) that instructs the UE to switch to the BWP ID configured with the abnormality.

It can be appreciated that the embodiment can be applied to other data service scenarios such as internet surfing, besides the session service scenario, so long as the scenario that the UE needs to check the RRC reconfiguration message is suitable.

In the implementation manner, when the UE receives the BWP configured on the network side and including the configuration with exception, during reconfiguration check, the UE may determine that the check result passes under the condition that the BWP to be used (i.e., BWP 1) is checked normally, and it is not necessary to determine that the check result of the RRC reconfiguration message does not pass due to the presence of exception in BWP2, thereby ensuring that the current communication service is performed normally, and improving the success rate of the communication service.

Example two

Because the related art mainly has the problem that the UE cannot be connected when the called party makes a call, in order to ensure the success rate of the call service, the embodiment can further execute different processing strategies according to whether the call is currently established or not during reconfiguration verification.

Specifically, as shown in fig. 8, a signaling interaction flow of a communication method under another wireless network provided by an embodiment of the present application may include:

S201, the UE camps on cell B and is in IDLE state.

S202, the UE receives a service request sent by the cell B.

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

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

S205, the UE identifies the RRC reconfiguration message, and identifies that the BWP configuration with the configuration abnormality exists in the RRC reconfiguration message.

For example, the RRC reconfiguration message configures two BWP, BWP1 and BWP2, for the UE. Here, it is assumed that there is a parameter configuration abnormality corresponding to a part of BWP ID in the RRC reconfiguration message, for example, a parameter configuration abnormality corresponding to BWP2.

S206, the UE determines whether the current BWP configuration is abnormal, if so, S207 is performed, and if not, S208 is performed.

Wherein the current BWP, i.e. the BWP to be used by the UE (or called to be activated), the UE determines whether the current BWP configuration is abnormal, i.e. whether the configuration of the parameters corresponding to the BWP IDs to be used by the UE (BWP IDs to be used, i.e. firstDownlinkActiveBWP-ID and firstUplinkActiveBWP-ID) is abnormal. For example, assuming that BWP to be used by the UE is configured as the aforementioned BWP1, the configuration of parameters corresponding to BWP1 is normal as described above, the UE may perform S208 and the UE may switch to the BWP1 after receiving the RRC reconfiguration message.

S207, the UE does not reply the RRC reconfiguration complete message to the cell B, and triggers the RLF flow.

S208, it is determined whether or not the call is currently being established, S209 is performed if the call is being established, and S207 is performed if the call is not being established.

S209, the UE replies an RRC reconfiguration complete message to the cell B.

That is, if the configuration of the parameters corresponding to the BWP ID to be used by the UE is not abnormal, it is further determined whether the current session is established, and if so, the RRC reconfiguration complete message is normally replied. If the RRC reconfiguration fails in the call establishment process, the RLF flow is triggered, and the subsequent steps are not executed. In some implementations, the UE may determine whether it is a call service request according to the received service request, and if so, determine that it is in the call setup process.

S210, the network side responds to the initialization context establishment.

S211, the network side sends Invite message of the calling party to the UE, and the call service is normally carried out.

At this time, the call service is successfully established, and the UE can talk with the caller normally.

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

S213, the UE triggers the RLF flow.

Since the parameters of the BWP (i.e., BWP 1) currently used by the UE are normally configured, if the BWP handover is not performed, the subsequent call traffic of the UE is normally performed. However, if the cell B instructs the UE to switch to BWP (i.e. BWP 2) containing abnormal configuration, the UE may determine that the configuration of the parameters corresponding to the BWP is abnormal, and then the UE may fail to perform the call service with a high probability, so that the UE (or the modem in the UE) may trigger the RLF procedure at this time.

In some implementations, before step S209, the UE may also perform S213, marking a BWP ID for which there is an abnormal configuration, where the BWP ID may be marked by a modem.

In the implementation manner, when the UE receives the BWP configured on the network side and including the configuration having the abnormality, during reconfiguration check, the UE may determine that the check result is passed when the BWP to be used (i.e., BWP 1) is checked normally and when the BWP is currently in the call establishment process, and does not need to determine that the check result of the RRC reconfiguration message is not passed due to the abnormality of BWP2, thereby ensuring that the current call service is performed normally and improving the success rate of the call service.

Example III

As can be seen from the above embodiments and the second embodiment, after the current service is normally performed, if the network side does not instruct the UE to perform BWP switching, the service will not be abnormal, if after a period of time, the network side instructs the UE to switch to the BWP ID with abnormal configuration, the UE will trigger the RLF procedure, and the subsequent service may still be interrupted (after the service is successfully established, the interruption may not necessarily fail), or the service fails when the new communication service is performed. Therefore, in this embodiment, after the communication service is successfully established, the UE may actively and temporarily close the capability of dynamically switching BWP and synchronize the BWP to the network side, so that the subsequent network side will not issue an instruction for BWP switching, thereby avoiding the problem that the communication service may fail again, and further improving the success rate of the communication service.

Specifically, as shown in fig. 9, a signaling interaction flow of a communication method under a wireless network provided by an embodiment of the present application may include:

s301, the UE resides in the cell B and is in an IDLE state.

S302, the UE receives a service request sent by a cell B.

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

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

The RRC reconfiguration message includes a parameter configuration exception corresponding to a part of BWP IDs, for example, a parameter configuration exception corresponding to non-currently activated BWP 2.

S305, the UE identifies the RRC reconfiguration message, and identifies the BWP configuration with abnormal configuration in the RRC reconfiguration message.

S306, the UE determines whether the current BWP configuration is abnormal, if so, S307 is performed, and if not, S308 is performed.

Wherein the current BWP, i.e. the BWP to be used by the UE (or called to be activated), the UE determines whether the current BWP configuration is abnormal, i.e. whether the configuration of the parameters corresponding to the BWP IDs to be used (BWP IDs to be used, i.e. firstDownlinkActiveBWP-ID and firstUplinkActiveBWP-ID) is abnormal. For example, assuming that BWP to be used by the UE is configured as the aforementioned BWP1, the configuration of parameters corresponding to BWP1 is normal as described above, the UE may perform S208 and the UE may switch to the BWP1 after receiving the RRC reconfiguration message.

S307, the UE does not reply the RRC reconfiguration complete message to the cell B, and triggers the RLF flow.

S308, it is determined whether or not the call is currently being established, S309 is executed if the call is being established, and S307 is executed if the call is not being established.

S309, the UE replies an RRC reconfiguration complete message to cell B.

If the configuration of the parameters corresponding to the BWP ID to be used by the UE is not abnormal, it may be further determined whether the current session is established, and if so, an RRC reconfiguration complete message is normally replied. If the RRC reconfiguration fails in the call establishment process, the RLF flow is triggered, and the subsequent steps are not executed.

In some implementations, the step of S308 is optional, that is, if it is determined in S306 that the configuration of the parameters corresponding to the BWP ID to be used by the UE is not abnormal, the UE may directly perform the procedure of replying to the RRC reconfiguration complete message to the cell B in S309.

S310, the network side responds to the initialization context establishment.

S311, the network side sends Invite message of calling party to the UE, and the call service is normally carried out.

At this time, the call service is successfully established, and the UE can talk with the caller normally. In some implementations, the success of the call service establishment may also be that the UE rings normally.

S312, the UE temporarily turns off the dynamic handoff BWP capability.

Wherein, a parameter may be set in the UE, and the parameter characterizes whether the UE starts the dynamic handover BWP capability. The UE may modify the value of this parameter to characterize the off dynamic handoff BWP capability. For example, a value of 1 characterizes the UE to turn on the dynamic switching BWP capability, and a value of 0 characterizes the UE to turn off the dynamic switching BWP capability.

S313, the UE sends a first registration request to cell B.

S314, cell B queries the capability information of the UE.

It is appreciated that the first registration request (registration request) is used to trigger cell B to query UE capabilities. In this embodiment, the type (type) of the first registration request may be mobile registration update (mobility registration updating, MRU), and a value of a follow-up request (FOR) field carried in the first registration request is 0.

The size of the FOR field is 1bit, when the bit is 0, the following no-pending (no-slow-on request pending) is not needed, and when the bit is 1, the following request pending (slow-on request pending) is indicated. In general, if the cell B receives a registration request with a value of 1 in the FOR field, it will not trigger the capability of querying the UE, and if the cell B receives a registration request with a value of 0in the FOR field, it will trigger the capability of querying the UE.

S315, the UE feeds back capability information of the UE to the cell B.

S316, cell B returns the first registration acceptance to the UE.

Wherein the feedback UE does not support dynamic BWP handover when feeding back the UE's capability to cell B. After obtaining the capability that the UE does not support dynamic BWP switching, the cell B may return a registration accept for the first registration request to the UE, and may not configure multiple BWP for the UE later, or may not instruct the UE to dynamically switch BWP, so that the UE may be prevented from being instructed to switch to the BWP with a problem configuration.

In general, after the UE temporarily turns off the dynamic BWP function, two cells BWP-SWITCHINGDELAY (BWP switching delay) and BWP-SameNumerology are not carried when the UE reports the capability to the cell B, and the BWP-SameNumerology field indicates the maximum BWP number with the same subcarrier spacing (sub-CARRIER SPACE, SCS) supported by the UE. Wherein, if the capability information does not carry BWP-SWITCHINGDELAY field and BWP-SameNumerology field when the UE sends the capability information to cell B, the UE is characterized to indicate to cell B that the UE does not support dynamic BWP handover. It can be appreciated that if the capability information sent by the UE to cell B carries the BWP-SWITCHINGDELAY field and the BWP-SameNumerology field, then characterizing the UE to cell B indicates that the UE is supporting dynamic BWP handover.

For example, the definition of the BWP-SWITCHINGDELAY field and the BWP-SameNumerology field may be referred to in fig. 10, if the capability information sent by the UE to the cell B does not carry the two fields, the cell B may not obtain the values corresponding to the two fields, and may not configure multiple BWP for the UE, or may not instruct the UE to dynamically switch BWP.

In some implementations, prior to step S309, the UE may also perform S317 of tagging the BWP ID for which the abnormal configuration exists, which may be tagged by the modem.

In the above implementation manner, when the UE receives the BWP configured on the network side and including the configuration having the abnormality, during the reconfiguration check, the UE may determine that the check result is passed when the BWP to be used (i.e., BWP 1) is checked normally and when the call is currently established, and may not determine that the check result of the RRC reconfiguration message is not passed due to the abnormality of BWP2, thereby ensuring that the current call service is performed normally. Meanwhile, after the current service is established successfully, the UE can actively and temporarily close the capacity of dynamically switching BWP and synchronize the capacity to the network side, so that the subsequent network side does not issue a BWP switching instruction, the problem that the communication service is likely to fail is avoided, and the success rate of the communication service is improved to a greater extent.

Example IV

As can be seen from the above embodiments and the second embodiment, after the current service is normally performed, if the network side does not instruct the UE to perform BWP handover, the service will not be abnormal, and if after a period of time, the network side instructs the UE to switch to the BWP ID with abnormal configuration, the UE will trigger the RLF procedure, and the service may still be interrupted or fail when performing the new communication service. However, it is found through research that, although some configuration items in the BWP configuration are abnormal (for example, the configuration items of the resource block with the number of pucch resouce Id being 40 in the (c) diagram in fig. 6 are abnormal), these abnormal configuration items only cause the corresponding functions to be disabled and do not cause the interruption of the communication service. Therefore, when the network side instructs the UE to switch to the BWP ID with abnormal configuration, the UE may not configure (may be understood as not validating) the configuration item with abnormal configuration (also referred as a parameter item), disable (disable) the corresponding function, and then switch to the corresponding BWP ID normally for service, so that the communication service can still be performed normally with high probability.

Specifically, as shown in fig. 11, a signaling interaction flow of a communication method under a wireless network provided in an embodiment of the present application may include:

S401, the UE camps on cell B and is in IDLE state.

S402, the UE receives a service request sent by the cell B.

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

S404, the cell B issues an RRC reconfiguration message to the UE.

S405, the UE identifies the RRC reconfiguration message, and identifies that the BWP configuration with the configuration abnormality exists in the RRC reconfiguration message.

S406, the UE determines whether the current BWP configuration is abnormal, if so, S407 is performed, and if not, S408 is performed.

Wherein the current BWP, i.e. the BWP to be used by the UE (or called to be activated), the UE determines whether the configuration of the current BWP is abnormal, i.e. whether the configuration of the parameters corresponding to the BWP ID to be used is abnormal.

S407, the UE does not reply the RRC reconfiguration complete message to the cell B, and triggers the RLF flow.

S408, judging whether the call is in the process of establishing the call, if so, executing S409, and if not, executing S407.

S409, the UE replies RRC reconfiguration complete message to the cell B.

If the configuration of the parameters corresponding to the BWP ID to be used by the UE is not abnormal, further judging whether the current process is in the call establishment process, and if so, normally replying an RRC reconfiguration complete message. If the RRC reconfiguration fails in the call establishment process, the RLF flow is triggered, and the subsequent steps are not executed.

Similarly, the step of S408 is also optional, and the UE may not make a determination as to whether or not the call is being established.

S410, the network side responds to the initialization context establishment.

S411, the network side sends Invite message of calling party to the UE, and the call service is normally carried out.

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

S413, the UE does not configure the configuration item with the abnormality and disables the function corresponding to the configuration item with the abnormality.

S414, the UE switches to the corresponding BWP ID for service.

If the configuration item having abnormality in the configuration corresponding to the BWP ID to be switched to is the a configuration, the UE does not configure the a configuration and disables the function corresponding to the a configuration. Illustratively, the a configuration may be the startingPRB configuration of pucch resource Id, which is an anomaly in the configuration of pucch resource Id, as in the above example, and pucch resource Id is for CSI (channel status information) (CSI is a function that the UE measures various qualities of a radio channel and reports to the network side), then the UE no longer configures pucch resource Id 40 and turns off the corresponding CSI function. The UE then switches to the corresponding BWP ID (i.e. the BWP ID containing the abnormal configuration) to perform the service, that is, the UE does not measure various qualities of the radio channel and reports them to the network side when performing the service, but the service can be performed normally.

S415, the network side identifies abnormality and instructs the UE to switch cells.

Because the UE does not feed back the function corresponding to the configuration a to the network side (e.g., the UE does not report the measured quality of the wireless channel to the network side), the network side may recognize the abnormal situation, and the network side may instruct the UE to switch from the current cell (the cell corresponding to the BWP ID with abnormal network configuration, i.e., the cell B) to the new cell, thereby avoiding the abnormal problem existing in the current cell (the cell B).

In some implementations, before step S409, the UE may also perform S416, marking the BWP ID for which there is an abnormal configuration, which may be marked by the modem.

In the above implementation manner, when the UE receives the BWP configured on the network side and including the configuration having the abnormality, during the reconfiguration check, the UE may determine that the check result is passed when the BWP to be used (i.e., BWP 1) is checked normally and when the call is currently established, and may not determine that the check result of the RRC reconfiguration message is not passed due to the abnormality of BWP2, thereby ensuring that the current call service is performed normally. Meanwhile, after the current service is established successfully, if the network side indicates that the UE is switched to the BWP ID with abnormal configuration, the UE can not configure the abnormal configuration item and enable the function corresponding to the abnormal configuration item, so that the subsequent service can be ensured to be normally performed, and the success rate of the communication service is improved.

Example five

Unlike the foregoing embodiment, in this embodiment, in the case where it is detected that there is a configuration abnormality in an RRC reconfiguration message sent by a cell to a UE (e.g., there is an abnormality in configuration of BWP), it is not determined according to the check result whether to go through an RLF procedure or normally reply to an RRC reconfiguration complete message, but counting the number of abnormalities in the cell, and if the number of abnormalities in configuration sent by the cell exceeds a preset threshold in a preset time, the UE (or modem) may BAR the cell and select a new cell.

Specifically, as shown in fig. 12, a signaling interaction procedure of a communication method under a wireless network provided by an embodiment of the present application may include:

s501, the UE camps on cell B and is in IDLE state.

S502, the UE receives a service request sent by a cell B.

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

S504, the cell B issues an RRC reconfiguration message to the UE.

The RRC reconfiguration message includes a parameter configuration exception corresponding to a part of BWP ID.

S505, the UE identifies the RRC reconfiguration message, and identifies the BWP configuration with abnormal configuration in the RRC reconfiguration message.

S506, if the UE identifies that the BWP configuration is abnormal, the number of abnormalities corresponding to the cell B is increased by 1.

Here, the BWP configuration anomaly identified by the UE may be a BWP configuration anomaly to be used or a BWP configuration anomaly not to be used, that is, the UE adds 1 to the number of anomalies corresponding to the cell B as long as the BWP is identified that there is a parameter of the configuration anomaly.

S507, judging whether the number of abnormal times corresponding to the cell B in the preset time exceeds a preset threshold, executing S508 if the number of abnormal times exceeds the preset threshold, and executing S509 if the number of abnormal times does not exceed the preset threshold.

The preset time may be a set unit time, for example, 1 minute, and the preset threshold may be a set maximum number of times, for example, 3 times.

S508, the UE temporarily BARs the preset duration of cell B, and performs S509.

If the number of anomalies corresponding to the cell B exceeds the preset threshold value within the preset time, it is indicated that the configuration problem of the cell B is not repaired, and the subsequent residence on the cell B still results in service failure, so that the UE can BAR the cell (i.e., the cell B configured with the problem) for a period of time (preset duration) to enable the UE to select and reside from other cells subsequently. In some implementations, the preset duration may be 5 minutes. The UE BAR may refer to prohibiting the UE from accessing the cell during cell selection, cell reselection, and/or cell handover.

S509, the UE triggers the RLF procedure and reselects the cell.

If the number of anomalies corresponding to the cell B within the preset time does not exceed the preset threshold, the UE does not need to have the configured anomalous cell by the temporary BAR. At this point the UE may trigger the RLF procedure because the RRC reconfiguration failed and reselect the cell. And after the UE temporarily BARs the cell B, the RLF procedure can also be triggered and the cell is reselected.

It can be understood that, under the condition that the number of anomalies corresponding to the cell B does not exceed the preset threshold, since there is no BAR cell B, when the UE reselects the cell, the UE may select the cell B until the number of anomalies corresponding to the cell B exceeds the preset threshold, the UE will BAR cell B, when reselecting the cell, a new cell will be selected, after the new cell is successfully accessed, there is no configuration anomaly problem in the new cell with a high probability, so that the subsequent service will be performed normally.

In some implementations, after 5 minutes of BAR cell B, the UE will deactivate the BAR operation, returning cell B to normal (i.e., cell B returns to an unaddressed state). If the subsequent UE camps again on cell B and the configuration of cell B is still abnormal, the UE may also re-BAR cell B, at which point the time of BAR may be increased, e.g. BAR cell B time is 10 minutes, and so on.

In the implementation manner, when the UE receives the BWP configured by the network side and including the configuration abnormality, the UE may count the number of abnormalities in the cell, and if the number of times of issuing the configuration abnormality by the cell exceeds the preset threshold in the preset time, the UE may BAR the cell for a period of time, so that the UE selects a new cell to camp, and the probability of occurrence of the configuration abnormality in the new cell is smaller, thereby improving the success rate of the subsequent communication service.

Example six

Unlike the foregoing embodiment, in this embodiment, in the case where it is detected that there is a configuration abnormality in an RRC reconfiguration message sent by a cell to a UE (e.g., there is an abnormality in configuration of BWP), it is not determined according to the check result whether to go through an RLF procedure or to normally reply to an RRC reconfiguration complete message, but the number of abnormalities is counted for the cell, and if the number of times of issuing configuration abnormalities by the cell exceeds a preset threshold in a preset time, the UE (or modem) may close the dynamic BWP capability of the UE for a period of time, so that the UE continuously uses the BWP with normal configuration.

Specifically, as shown in fig. 13, a signaling interaction flow of a communication method under a wireless network provided in an embodiment of the present application may include:

s601, the UE camps on cell B and is in IDLE state.

S602, the UE receives a service request sent by a cell B.

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

S604, the cell B issues an RRC reconfiguration message to the UE.

S605, the UE identifies the RRC reconfiguration message, and identifies that the BWP configuration with the configuration abnormality exists in the RRC reconfiguration message.

S606, if the UE identifies that the BWP configuration is abnormal, the number of abnormalities corresponding to the cell B is increased by 1.

Here, the BWP configuration anomaly identified by the UE may be an unused BWP configuration anomaly, that is, the UE identifies that there is a parameter of the configuration anomaly in BWP2, and adds 1 to the number of anomalies corresponding to cell B.

S607, judging whether the number of abnormal times corresponding to the cell B in the preset time exceeds a preset threshold, executing S608 if the number of abnormal times exceeds the preset threshold, and executing S609 if the number of abnormal times does not exceed the preset threshold.

S608, the UE temporarily turns off the dynamic handoff BWP capability preset time period, and performs S609.

If the number of anomalies corresponding to the cell B exceeds the preset threshold in the preset time, which indicates that the configuration problem of the cell B is not repaired, the UE may close the capability of dynamically switching BWP for a period of time (preset duration), so that when the subsequent network side queries the capability information of the UE, the network side does not configure a plurality of BWP for the UE, or does not instruct the UE to dynamically switch BWP, and further, it may be avoided that the UE is instructed to switch to the BWP with the problem.

S609, the UE triggers the RLF procedure and reselects the cell.

If the number of anomalies corresponding to the cell B within the preset time does not exceed the preset threshold, the UE does not need to temporarily close the dynamic BWP switching capability. At this time, the UE may trigger the RLF procedure because the RRC reconfiguration fails and reselects the cell for access. And after the UE temporarily turns off the dynamic handoff BWP capability, the RLF procedure may also be triggered and the cell reselected. It will be appreciated that if the signal quality of cell B is best or highest priority, here the cell B is selected with a high probability.

S610, when there is a new service request, cell B queries capability information of the UE.

S611, the UE feeds back capability information of the UE to the cell B.

After the UE re-accesses the cell, if there is a service request, the cell queries the UE for capability information, and when the UE feeds back the capability of the UE to the cell B, the feedback UE does not support BWP dynamic handover. After the cell B acquires the capability that the UE does not support dynamic BWP switching, multiple BWP will not be configured, or BWP will not be dynamically switched, and the subsequent communication service is normal.

It can be understood that, if the number of anomalies corresponding to the cell B does not exceed the preset threshold, when the UE reselects the cell, the cell B may select the cell B, and when a new service request is made, the cell B may query the capability information of the UE, and since the UE does not close the capability of dynamically switching BWP at this time, the capability information fed back by the UE to the cell B indicates that the BWP is supported for dynamic switching, and the communication service may also fail. Until the abnormal times corresponding to the cell B exceeds a preset threshold, the UE closes the dynamic BWP switching capability, the capability information fed back to the cell B by the UE indicates that the UE does not support the BWP dynamic switching, and the cell B does not dynamically switch the BWP any more, so that the subsequent service can be normally performed.

In general, the capability information that the UE sends to cell B may carry BWP-SWITCHINGDELAY fields and BWP-SameNumerology fields in the case where the UE does not turn off the dynamic handoff BWP capability. After the UE turns off the dynamic handoff BWP capability, the capability information sent by the UE to cell B does not carry the BWP-SWITCHINGDELAY field and the BWP-SameNumerology field.

In the implementation manner, when the UE receives the BWP configured by the network side and including the configuration with exception, the UE may count the number of exceptions in the cell, and if the number of times that the cell issues the configuration exception exceeds a preset threshold in a preset time, the UE may temporarily close the capability of dynamically switching BWP for a period of time, so that the subsequent network side will not issue an instruction for switching BWP, thereby avoiding the problem of re-failure of the communication service, and greatly improving the success rate of the communication service.

It is understood that the process of interacting with the cell or network side in the above embodiments may be performed by a modem in the UE. The communication method under the wireless network provided by the embodiment of the application can be applied to terminal equipment with wireless network communication capability such as mobile phones, tablet computers, wearable equipment, vehicle-mounted equipment, ultra-mobile personal computer (UMPC), netbooks, personal Digital Assistants (PDA) and the like, and the embodiment of the application does not limit the specific type of the terminal equipment.

Fig. 14 is a schematic structural diagram of an exemplary terminal device 100 according to an embodiment of the present application. Taking the example that the terminal device 100 is a mobile phone, the terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge 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 key 190, a motor 191, an indicator 192, a camera 193, a display 194, a subscriber identity module (subscriber identification module, SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (application processor, AP), a modem processor (modem), a graphics processor (graphics processing unit, GPU), an image signal processor (IMAGE SIGNAL processor, ISP), a controller, a memory, a video codec, a digital signal processor (DIGITAL SIGNAL processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it may be called directly from memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

The wireless communication function of the terminal device 100 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating 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. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

In some embodiments, antenna 1 and mobile communication module 150 of terminal device 100 are coupled, and antenna 2 and wireless communication module 160 are coupled, such that terminal device 100 may communicate with a network and other devices via wireless communication techniques. The wireless communication techniques can include a global system for mobile communications (global system for mobile communications, GSM), general packet radio service (GENERAL PACKET radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation SATELLITE SYSTEM, GLONASS), a beidou satellite navigation system (beidou navigation SATELLITE SYSTEM, BDS), a quasi zenith satellite system (quasi-zenith SATELLITE SYSTEM, QZSS) and/or a satellite based augmentation system (SATELLITE BASED AUGMENTATION SYSTEMS, SBAS).

The internal memory 121 may be used to store computer-executable program code that includes instructions. The processor 110 executes various functional applications of the terminal device 100 and data processing by executing instructions stored in the internal memory 121. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data (such as audio data, phonebook, etc.) created during use of the terminal device 100, and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like.

It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the terminal device 100. In other embodiments of the application, terminal device 100 may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The software system of the terminal device 100 may employ a layered architecture, an event driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the application, taking an Android system with a layered architecture as an example, a software structure of the terminal device 100 is illustrated.

Fig. 15 is a software configuration block diagram of the terminal device 100 of the embodiment of the present application. The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun rows (Android runtime) and system libraries, and a kernel layer, respectively. The application layer may include a series of application packages.

As shown in fig. 15, the application package may include applications for cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, etc.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for the application of the application layer. The application framework layer includes a number of predefined functions.

As shown in fig. 15, 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.

The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like. The content provider is used to store and retrieve data and make such data accessible to applications. The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The telephony manager is used to provide the communication functions of the terminal device 100. Such as the management of call status (including on, hung-up, etc.). The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like. The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction.

Android runtime include core libraries and virtual machines. Android runtime is responsible for scheduling and management of the android system.

The core library comprises two parts, wherein one part is a function required to be called by java language, and the other part is an android core library.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. Such as surface manager (surface manager), media library (media library), three-dimensional graphics processing library (e.g., openGL ES), 2D graphics engine (e.g., SGL), etc.

The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications. Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc. The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like. The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

Examples of the communication method under the wireless network provided by the embodiment of the present application are described in detail above. It will be appreciated that the terminal device, in order to achieve the above-described functions, comprises corresponding hardware and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application in conjunction with the embodiments, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The embodiment of the application provides terminal equipment, which has the function of realizing the behavior of the terminal equipment in any method embodiment. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to each of the above-described functions. In particular, the terminal device may be a user device, such as a mobile phone.

The embodiment of the application also provides a communication system which comprises the network equipment and the terminal equipment.

The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, 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-mentioned terminal device.

The embodiment of the application also provides a computer program or a computer program product comprising the computer program, and the computer program when executed on a certain computer can enable the computer to implement the method flow related to the terminal device in any of the method embodiments. Specifically, the computer may be the above-mentioned terminal device.

Embodiments of the present application also provide a computer program or a computer program product comprising a computer program, which when executed on a computer causes the computer to implement the method flows related to the network device in any of the above method embodiments. Specifically, the computer may be the above-mentioned network device.

The embodiment of the application also provides a device which is applied to the terminal equipment, and the device is coupled with the memory and used for reading and executing the instructions stored in the memory, so that the terminal equipment can execute the method flow related to the terminal equipment in any method embodiment. The memory may be integrated in the processor or may be separate from the processor. The means may be a chip on the terminal device (e.g., system on chip SoC (System on a Chip)).

It should also be understood that the memory referred to in embodiments of the present invention may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be read-nnly memory (ROM), programmable ROM (PROM), erasable programmable ROM (erasable PROM, EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory, among others. The volatile memory may be random access memory (random access memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (doubledata RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and direct memory bus random access memory (direct rambus RAM, DR RAM).

It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

In the present application, "at least one" means one or more, and "a plurality" means two or more. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, "at least one (a), b, or c)", or "at least one (a, b, and c)", may each represent a, b, c, a-b (i.e., a and b), a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple, respectively.

It should be understood that, in various embodiments of the present application, the sequence number of each process described above does not mean that the execution sequence of some or all of the steps may be executed in parallel or executed sequentially, and the execution sequence of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device or a terminal device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application.

The device configuration diagrams presented in the device embodiments of the present application only show a simplified design of the corresponding device. In practical applications, the apparatus may include any number of transmitters, receivers, processors, memories, etc. to implement the functions or operations performed by the apparatus in the embodiments of the present application, and all apparatuses that may implement the present application are within the scope of the present application.

The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items. The character "/" herein generally indicates that the associated object is an "or" relationship.

The words "if" or "if" as used herein may be interpreted as "at..once" or "when..once" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrase "if determined" or "if detected (stated condition or event)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event)" or "in response to detection (stated condition or event), depending on the context.

It will be appreciated by those of ordinary skill in the art that implementing all or part of the steps in the methods of the above embodiments may be accomplished by a program that instructs related hardware, where the program may be stored on a readable storage medium of a device, where the program, when executed, includes all or part of the steps described above, where the storage medium is, for example, FLASH, EEPROM, etc.

While the foregoing embodiments have been described in some detail for purposes of clarity of understanding, it will be appreciated that various embodiments of the invention may be practiced otherwise than as specifically described, and that no limitations are intended to the scope of the invention except as may be modified or practiced in any way within the spirit and principles of the invention.

Claims

1. A communication method in a wireless network, comprising:

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, and the first BWP includes one or more BWPs;

When the number of times that the first configuration information in the multiple RRC reconfiguration messages has anomalies exceeds a preset threshold, the terminal device triggers the RLF process and prohibits selecting the first cell as a serving cell within a preset time period.

2. A communication method in a wireless network, characterized by comprising:

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 that is configured by the first 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 of dynamically switching BWP for a preset first time.

3. The method as claimed in claim 1 or 2 is characterized in that the situation where the number of times the first configuration information has anomalies in the multiple RRC reconfiguration messages exceeds a preset threshold includes: the situation where the number of times the first configuration information has anomalies in the multiple RRC reconfiguration messages received within a preset second time exceeds a preset threshold, or, in a preset number of RRC reconfiguration messages received continuously, the number of times the first configuration information has anomalies in multiple RRC reconfiguration messages exceeds a preset threshold.

4. The method as described in any one of claims 1 to 3 is characterized in that the method also includes: when the number of abnormalities in the first configuration information in the multiple RRC reconfiguration messages does not exceed a preset threshold, the terminal device triggers the RLF process.

5. The method according to claim 2, wherein, when the terminal device turns off the ability of dynamically switching BWP for a preset first time, the method further comprises:

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.

6. The method as claimed in claim 5 is characterized in that the first capability information indicates that the terminal device does not support BWP switching, including: the first capability information does not carry a bwp-SwitchingDelay field and a bwp-SameNumerology field.

7. The method according to claim 6, characterized in that before the terminal device receives the capability query request sent by the first cell, the method further comprises:

The terminal device disables the capability of dynamically switching BWP.

8. The method according to any one of claims 1 to 7 is characterized in that 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 first value of pucch resource Id in the first configuration information.

9. The method of claim 8, wherein the first value is 40.

10. The method according to any one of claims 1 to 9, wherein the first wireless network is a 5G network.

11. A terminal device, characterized in that the terminal device comprises:

A memory for storing instructions;

A processor is used to call and execute instructions in the memory so that the terminal device executes the method described in any one of claims 1 to 10.

12. A chip system, characterized in that the chip system comprises a processor for supporting a terminal device to implement the method as described in any one of claims 1 to 10.