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

Abstract

The embodiment of the present application provides a communication method, terminal device and chip system in a wireless network, the method comprising: the terminal device receives an 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 the configuration information currently required to be activated configured by the first cell for the terminal device; when a first condition is met, an RRC reconfiguration completion message in response to the RRC reconfiguration message is sent to the first cell, the first condition comprising that the first configuration information does not have an abnormality and the second configuration information has an abnormality; after sending the RRC reconfiguration completion message to the first cell, if the first message sent by the first cell is received, RRC random access is re-initiated to the first cell based on the configuration parameters of the initial BWP in the SIB1 message, the first message is used to instruct the terminal device to switch from the first configuration information to the second configuration information with an abnormality. This improves the success rate of terminal services in wireless networks.

Description

Technical Field

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

[0002] At present, the fifth generation mobile communication network (5G network) is gradually being commercialized. When using terminal devices, users can not only surf the Internet through the 5G network, but also make calls through the 5G network. For example, the 5G network uses a new air interface to carry voice (voice over new radio, VONR) to realize call services, which greatly improves the user experience; but at the same time, compared with the mature 4G long term evolution (LTE) network, 5G VONR has some network compatibility issues, which may cause the terminal device to fail to perform services.

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

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

[0005] In a first aspect, a communication method in a wireless network is provided, including: a terminal device receives a radio resource control (RRC) reconfiguration message sent by a first cell belonging to a first wireless network, the RRC reconfiguration message carries first configuration information and second configuration information, wherein the first configuration information is configuration information corresponding to a first part of the bandwidth BWP, the second configuration information is configuration information corresponding to a second BWP, the first BWP is a BWP that is currently required to be activated and configured by the first cell for the terminal device, the first BWP includes one or more BWPs, and the second BWP is a BWP that is not currently required to be activated and configured by the first cell for the terminal device, the second BWP includes one or more BWPs; when a first condition is met, the terminal device sends an RRC reconfiguration completion message in response to the RRC reconfiguration message to the first cell, the first condition includes that the first BWP does not have an abnormality and the second BWP has an abnormality; after the terminal device sends the RRC reconfiguration completion message to the first cell, if the terminal device receives the first message sent by the first cell, the terminal device re-initiates RRC random access to the first cell based on the configuration parameters of the initial BWP in the system information block 1 SIB1 message, and the first message is used to instruct the terminal device to switch from the first BWP to the second BWP with an abnormality.

[0006] According to the above RRC reconfiguration message, the terminal device will actually use the first BWP instead of the second BWP. If the first BWP does not have an abnormality but the second BWP has an abnormality, it does not affect the normal communication process of the terminal device. Therefore, during the reconfiguration verification, the terminal device can judge the verification result as passed, and it is not necessary to judge the verification result of the RRC reconfiguration message as failed due to the abnormality of the second BWP. This can ensure that the current communication service is carried out normally and improve the success rate of the communication service. In addition, after the terminal device sends the RRC reconfiguration completion message to the first cell, if the first cell sends the first message to the terminal device again, instructing the terminal device to switch from the first BWP to the second BWP with an abnormality, if the terminal device switches, it is likely to result in the failure of subsequent services. Therefore, the terminal device does not switch the configuration information at this time, but re-initiates RRC random access to the first cell based on the configuration parameters of the initial BWP in the SIB1 message with normal configuration, so that the terminal device continues to use the correct configuration parameters of the initial BWP for resource synchronization. In this way, it is ensured that subsequent communication services are also carried out normally.

[0007] In some implementations, the terminal device re-initiates RRC random access to the first cell based on the configuration parameters of the initial BWP in the system information block 1 SIB1 message, including: within a first time period, the terminal device re-initiates RRC random access to the first cell based on the configuration parameters of the initial BWP in the SIB1 message, and the first time period is the BWP switching delay set when the first cell sends a first message to the terminal device.

[0008] Among them, the first duration can be the duration of the timer set by the first cell (i.e., the switching delay). When the first cell sends an indication message of switching BWP to the terminal device, it can determine a switching delay, i.e., the first duration, so that the terminal device replies with a confirmation message from the first cell within the duration to avoid long waiting in the cell. Therefore, after the terminal device receives the first message, if the first message indicates switching to a second BWP with an abnormal configuration, the terminal device can re-initiate RRC random access to the first cell based on the configuration parameters of the initial BWP in the SIB1 message within the first duration, without switching the abnormal configuration information, so that subsequent business processes proceed normally. In some implementations, the BWP ID of the initial BWP = 0.

[0009] In some implementations, the method further includes: when the terminal device does not reply to the first cell within the first time period, the terminal device receives a radio link failure RLF message sent by the first cell.

[0010] Because the first cell sets a switching delay (i.e., the first time duration) for the terminal device, the terminal device should reply to the message within this time duration. If the first cell does not receive any message from the terminal device within the first time duration, the first cell may no longer wait, but trigger RLF or execute other instructions (such as actively instructing the terminal device to switch to the initial BWP) on its own.

[0011] In some implementations, after the terminal device receives a radio resource control RRC reconfiguration message sent by a first cell belonging to a first wireless network, the method further includes: when an abnormality occurs in the first BWP, the terminal device triggers an RLF process.

[0012] If there is an abnormality in the first BWP that needs to be activated in the configuration information sent by the first cell to the terminal device, the terminal device may not be able to perform new services normally, and the RLF process may be triggered.

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

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

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

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

[0017] Among them, when the terminal device is in the process of establishing a call, that is, when the conditions are met that there is no abnormality in the first BWP, there is an abnormality in the second BWP, and the terminal device is in the process of establishing a call, the terminal device will judge the verification result as passed, which can improve the success rate of the call service.

[0018] In some implementations, the method further includes: when there is no abnormality in the first BWP, there is an abnormality in the second BWP, and the terminal device is not currently in the process of establishing a call, the terminal device triggering the RLF process.

[0019] That is to say, if there is no abnormality in the configuration of the first BWP to be used by the terminal device, it will further determine whether it is currently in the process of establishing a call. If it is not in the process of establishing a call, it can be considered that the RRC reconfiguration has failed, triggering the RLF process, and no subsequent steps will be executed, thereby ensuring the success rate of the call service.

[0020] In some implementations, a terminal device receives a radio resource control (RRC) reconfiguration message sent by a first cell belonging to a first wireless network, including: after receiving a paging message sent by the first cell, the terminal device receives an RRC reconfiguration message sent by the first cell, and the Paging message is used to page the terminal device when there is an incoming call.

[0021] In which, when the terminal device is in the scenario of establishing a call, the first cell will send a service request to the terminal device, that is, send a Paging message, which is used to page the terminal device for an incoming call. After that, the terminal device can establish an RRC connection with the first cell and receive the RRC reconfiguration message sent by the first cell.

[0022] In some implementations, the abnormality in the second BWP includes: the configuration parameters of the second BWP include a first parameter item with a configuration abnormality, the first parameter item with a configuration 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 the pucch resource Id in the second configuration information.

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

[0024] Among them, when pucch resource Id is the first value, it can be used to implement the CSI function. CSI is a function in which the terminal device measures various qualities of the wireless channel and sends it to the network in the form of a report. If the field configuration corresponding to this function is abnormal, the terminal device may not be able to measure and report various qualities of the wireless channel normally when performing services. However, if the terminal device does not use the second BWP during the communication service, it will not affect the terminal device's communication service. At this time, the terminal device can determine the verification result as passed and normally reply to the first cell with an RRC reconfiguration completion message to improve the success rate of the communication service.

[0025] In some implementations, when there is an abnormality in the second BWP, the method further includes: marking an abnormality on an identifier of the second BWP.

[0026] If the terminal device marks the second BWP, if the first cell subsequently instructs the terminal device to switch to the marked configuration information, it means that the terminal device is instructed to switch to the BWP with abnormal configuration. The terminal device can re-initiate RRC random access to the first cell based on the initial BWP in the SIB1 message.

[0027] In a second aspect, a terminal device is provided, the terminal device comprising:

[0028] A memory for storing instructions;

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

[0030] In a third aspect, a chip system is provided, comprising: a processing circuit, a receiving pin and a transmitting pin; wherein the receiving pin, the transmitting pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes any method described in the first to third aspects above to control the receiving pin to receive a signal and control the transmitting pin to send a signal.

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

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

[0033] Figure 1 is a schematic diagram of broadband resources corresponding to different BWPs provided in an embodiment of the present application;

[0034] Figure 2It is a schematic diagram of relevant cell parameters in an example of BWP configuration provided in an embodiment of the present application;

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

[0036] Figure 4 is a schematic diagram of configuration parameters of an example of ServingCellConfig provided in an embodiment of the present application;

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

[0038] Figure 6 It is a signaling interaction flow chart for call services in the related technology;

[0039] Figure 7 It is a schematic diagram of an example of BWP configuration parameter abnormality provided in an embodiment of the present application;

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

[0041] Fig. 9 is a signaling interaction flow chart of another communication method in a wireless network provided in an embodiment of the present application;

[0042] Fig.10 This is a signaling interaction flow chart of another example of a communication method in a wireless network provided in an embodiment of the present application;

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

[0044] Fig.12 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

[0045] Fig.13 This is a software structure block diagram of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0047] In the following, the terms "first", "second", and "third" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first", "second", and "third" may explicitly or implicitly include one or more of the features.

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

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

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

[0051] 2. Cell access: The UE sends an access request to the best cell. After receiving the request, the cell can make an access authorization judgment. If the UE meets the access conditions, the cell will allocate a temporary mobile subscriber identity (TMSI) to the UE. After the UE receives the access authorization from the cell, it can confirm the access request and send a confirmation message to the cell. When the cell receives the confirmation message, the access process is completed and an international mobile subscriber identity (IMSI) is allocated to the UE.

[0052] 3. Security negotiation and establishment: After the UE accesses the cell, the UE can send a security negotiation request to the core network to ensure the security of subsequent communication services. After receiving the security negotiation request, the core network can select an appropriate security protocol based on the UE's identity information and network policy, and send a negotiation response to the UE. After the UE receives the negotiation response, if it confirms the negotiation request, it sends a negotiation confirmation message to the core network. After the core network receives the negotiation confirmation message, the security negotiation and establishment process is completed and the relevant keys are generated for the UE.

[0053] 4. Service request and establishment: After that, if the UE wants to perform communication services, it can send a service request to the core network to inform the core network of the communication services it needs to perform. After receiving the service request, the core network can select an appropriate service strategy based on the UE's needs and network resources, and send a service response to the UE. After receiving the service response, if the UE confirms the service request, it can send a service confirmation message to the core network. After receiving the service confirmation message, the core network completes the service request and establishment process and can allocate corresponding service resources to the UE.

[0054] However, in the process of research and development of 5G network connection, researchers found that compared with 4G, the bandwidth of 5G network has increased significantly, but some communication services (such as IoT services) performed by UE do not require large bandwidth. If all services or all terminal devices (including devices other than mobile phones) are forced to support large bandwidth, it will cause resource waste. Therefore, in 5G network, the concept of bandwidth part (BWP) is proposed. BWP is a set of continuous common resource blocks (CRBs) under subcarrier spacing in a part of the bandwidth of a carrier (such as a cell of 100MHZ). BWP is a continuous bandwidth resource allocated to UE by the network side (core network), which can realize flexible data transmission between the network side and UE. Each BWP corresponds to a specific Numerology (system parameter) and is a necessary configuration for UE to access 5G network. Among them, different UEs can be configured with different BWPs, and different communication services of a UE can be configured with different BWPs.

[0055] For example, the broadband resources corresponding to different BWPs can be found in Figure 1 , where the lowest RB position in the full bandwidth on the network side can be recorded as PointA(CRB0), and the starting position of the first BWP0 is The number of RBs (i.e., the BWP0 bandwidth size) is The starting position of the second BWP1 is The number of RBs (i.e., the BWP1 bandwidth size) is The starting position of the third BWP2 is The number of RBs (i.e., the BWP2 bandwidth size) is The starting position of the fourth BWP3 is The number of RBs (i.e., the BWP3 bandwidth size) is And so on.

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

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

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

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

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

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

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

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

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

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

[0066] Among them, DCI format 0-1 / 1-1 has a BWP indication field (Bandwidth part indicator field). If the BWP indicated by this field (field, or field) is inconsistent with the current BWP, the UE needs to switch the BWP. Since this field is at most 2 bits, and according to the previous description, the UE is configured with at most 5 BWPs, it is obvious that 2 bits cannot represent 5 BWPs, so two situations are distinguished.

[0067] 1.1) Initial BWP+3BWP

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

[0069] 1.2) Initial BWP+4BWP

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

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

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

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

[0074] When the BWPinactivity timer times out, if the default downlink BWP identifier (defaultDownlinkBWP-Id) is configured, the UE will switch to the BWP. If not configured, the UE will switch to the initial downlink BWP (initialDownlinkBWP).

[0075] 4. RRC reconfiguration for BWP switching

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

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

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

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

[0080] For example, Figure 6 As shown, it is a signaling interaction flow chart for call services in the relevant technology. When the UE resides on cell B and is in an idle state (IDLE state), and the UE has a service demand (for example, the UE receives a Paging message for calling the UE, or other data services, etc.), the UE establishes an RRC connection with the network side (core network); the core network sends an RRC reconfiguration message through cell B, and some parameters corresponding to BWP in the RRC reconfiguration message are abnormally configured (such as BWP1 is normal, BWP2 is abnormal); the UE identifies the BWP configuration abnormality, triggers the radio link failure (RLF) process, and does not send an RRC reconfiguration completion message to the network side. Since the core network has not received the reconfiguration completion message replied by the UE, it is impossible to initialize the UE context, that is, the initialization of the UE context fails, and the invitation message of the calling party cannot be sent, resulting in the problem that the called party cannot be connected. Assuming that the UE reselects a cell later, if cell B has the highest priority or the best signal, the UE will still choose cell B to reside. If the BWP parameter configuration in the RRC reconfiguration message sent by cell B is still abnormal, the UE will enter a process of continuous call failure or data service failure.

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

[0082] Therefore, the reasons for the failure of RRC reconfiguration in the above related technologies are: 1. According to the protocol formula, if the starting PRB configured by the network side exceeds the theoretically calculated L RBs This is unreasonable. If the network side switches the UE to this BWP ID during subsequent data transmission, problems will occur. 2. For this incorrect configuration item (i.e., startingPRB), there may be problems with the UE's use in the future. Therefore, the modem in the UE will determine that the RRC reconfiguration message verification fails in this case, so the UE does not reply with a reconfiguration completion message.

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

[0084] Embodiment 1

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

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

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

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

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

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

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

[0092] The service request received by the UE may be, for example, a Paging message for calling the UE. The Paging message may be a message generated by the network side after receiving an Invite message from the caller. The UE then requests to establish an RRC connection with the network side so that the network side can initialize the context.

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

[0094] S105, the UE verifies the RRC reconfiguration message (the verification may also be referred to as identification or inspection), and identifies that an abnormally configured BWP exists in the RRC reconfiguration message.

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

[0096] Among them, the UE can verify the RRC reconfiguration message according to the calculation method specified in the above protocol, and then identify the BWP with abnormal configuration.

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

[0098] Among them, the current BWP is the BWP that the UE is going to use (or is called the BWP that is going to be activated). The UE determines whether the current BWP configuration is abnormal, that is, whether the configuration of the parameters corresponding to the BWP ID that the UE is going to use (the BWP ID to be used is firstDownlinkActiveBWP-Id and firstUplinkActiveBWP-Id) is abnormal. Here, the modem in the UE can determine whether the configuration of the parameters corresponding to the BWP ID that the UE is going to use is abnormal. For example, assuming that the BWP that the UE is going to use is configured as the aforementioned BWP1, as mentioned above, the parameter configuration corresponding to BWP1 is normal, then the UE can execute S108; the UE can switch to the BWP1 after receiving the RRC reconfiguration message. For another example, assuming that the BWP that the UE is going to use is configured as the aforementioned BWP2, and the parameter configuration corresponding to BWP2 is abnormal, then the UE can execute S107 to trigger the RLF process.

[0099] S107, the UE does not reply the RRC reconfiguration completion message to cell B, triggering the RLF process.

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

[0101] S108, UE replies to cell B with an RRC reconfiguration completion message.

[0102] S109, the network side responds to initialize context establishment.

[0103] S110: The network sends an Invite message to the UE, and the call service proceeds normally.

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

[0105] S111, cell B sends a BWP switching indication message to the UE.

[0106] Optionally, the indication message sent by cell B may be downlink control information (downlink control information, DCI).

[0107] S112, the UE determines whether to switch to a BWP ID with a configuration abnormality, and if so, executes S113, and if not, the subsequent process is normal.

[0108] S113, the UE re-initiates RRC random access to cell B, and carries the configuration parameters of the initial BWP in the SIB1 message during random access to perform uplink and downlink synchronization.

[0109] Since the parameters of the BWP (i.e., BWP1) currently used by the UE are configured normally, the subsequent communication services of the UE will proceed normally if the BWP switching is not performed. However, if cell B instructs the UE to perform BWP switching, and it needs to switch to the BWP (i.e., BWP2) containing the above-mentioned configuration abnormality, then the UE will determine that the parameter configuration corresponding to the BWP to be switched is abnormal, and the communication service will most likely fail. Therefore, the UE (or the modem in the UE) can not perform BWP switching, but re-initiate RRC random access to cell B. Here, when the UE re-initiates RRC random access to cell B, it can carry the configuration parameters of the initial BWP in the SIB1 message to inform the network side to use the RACH resources corresponding to the initial BWP in the SIB1 message for uplink and downlink synchronization. Among them, it can be seen from the above description that an initial downlink / uplink BWP (InitialDL / UL BWP) will be configured in SIB1, and BWP ID=0. Under normal circumstances, the UE can normally send and receive data for communication services on the initial BWP. In this way, the UE subsequently uses the normally configured initial BWP for communication services, which can make the subsequent business processes normal.

[0110] It can be understood that if cell B instructs the UE to perform BWP switching, it needs to switch to a normally configured BWP (such as another normal BWP3), then the UE can perform BWP switching, and the subsequent process is normal.

[0111] In some implementations, before step S108, the UE may further perform S114: marking the BWPID with abnormal configuration, wherein the modem may mark the BWP ID (e.g., marked as invalidBWP). Accordingly, if cell B instructs the UE to switch to the BWP ID marked as abnormal in S111, the UE performs step S113.

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

[0113] In the above implementation, when the UE receives a BWP with a configuration anomaly configured by the network side, during the reconfiguration check, the UE can judge the check result as passed if the BWP to be used (i.e., BWP1) is checked normally, and it is not necessary to judge the check result of the RRC reconfiguration message as failed due to the abnormality of BWP2, thereby ensuring the normal operation of the current communication service and improving the success rate of the communication service. In addition, if the cell instructs the UE to switch to the BWP with an abnormal configuration, the UE can re-initiate RRC random access to the cell and use the initial BWP in the SIB1 message for resource synchronization to ensure that subsequent communication services are also carried out normally.

[0114] Embodiment 2

[0115] In some scenarios, when the cell instructs the UE to perform BWP switching, a timer is usually set, and the UE is required to reply to the message within the timer to complete the BWP switching. Therefore, the UE can re-initiate RRC random access to cell B within the timer to avoid the network side performing other operations after the timer expires.

[0116] Specifically, Fig. 9 As shown, the signaling interaction process of a communication method in a wireless network provided in an embodiment of the present application may include:

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

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

[0119] S202, UE receives a service request sent by cell B.

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

[0121] The service request received by the UE may be, for example, a Paging message for calling the UE. The Paging message may be a message generated by the network side after receiving an Invite message from the caller. The UE then requests to establish an RRC connection with the network side so that the network side can initialize the context.

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

[0123] S205, the UE verifies the RRC reconfiguration message (the verification may also be referred to as identification or inspection), and identifies that an abnormally configured BWP exists in the RRC reconfiguration message.

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

[0125] Among them, the UE can verify the RRC reconfiguration message according to the calculation method specified in the above protocol, and then identify the BWP with abnormal configuration.

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

[0127] Among them, the current BWP is the BWP that the UE is going to use (or is called the BWP that is going to be activated). The UE determines whether the current BWP configuration is abnormal, that is, whether the configuration of the parameters corresponding to the BWP ID that the UE is going to use (the BWP ID to be used is firstDownlinkActiveBWP-Id and firstUplinkActiveBWP-Id) is abnormal. Here, the modem in the UE can determine whether the configuration of the parameters corresponding to the BWP ID that the UE is going to use is abnormal. For example, assuming that the BWP that the UE is going to use is configured as the aforementioned BWP1, as mentioned above, the parameter configuration corresponding to BWP1 is normal, then the UE can execute S208; the UE can switch to the BWP1 after receiving the RRC reconfiguration message. For another example, assuming that the BWP that the UE is going to use is configured as the aforementioned BWP2, and the parameter configuration corresponding to BWP2 is abnormal, then the UE can execute S207 to trigger the RLF process.

[0128] S207, the UE does not reply the RRC reconfiguration completion message to cell B, triggering the RLF process.

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

[0130] S208, UE replies to cell B with an RRC reconfiguration completion message.

[0131] S209, the network side responds to initialize context establishment.

[0132] S210: The network sends an Invite message to the UE, and the call service proceeds normally.

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

[0134] S211, cell B sends a BWP switching instruction message to the UE.

[0135] S212, the UE determines whether it needs to switch to the BWP ID with the configuration abnormality, and if so, executes S213, otherwise, the subsequent process is normal.

[0136] S213, within the first duration, the UE re-initiates RRC random access to cell B, and carries the configuration parameters of the initial BWP in the SIB1 message during random access to perform uplink and downlink synchronization.

[0137] The first duration may be the duration of the timer set by cell B. In some implementations, when cell B sends an indication message for switching BWP to the UE, it may determine a switching delay (i.e., the first duration) based on the capabilities and subcarrier spacing (SCS) reported by the UE when the cell was previously accessed. For example, for a UE reporting Type 1, the switching delay determined by cell B is T1, and for a UE reporting Type 2, the switching delay determined by cell B is T2. Exemplarily, the values ​​of T1 and T2 may be in the range of [10, 25] milliseconds. In addition, if the subcarrier spacing of the BWP before and after the switching is different, the switching delay may be determined based on the delay corresponding to the BWP with the larger delay.

[0138] If cell B instructs the UE to perform BWP switching, and it needs to switch to the BWP (i.e., BWP2) containing the above-mentioned configuration anomaly, then the UE will determine that the parameter configuration corresponding to the BWP to be switched is abnormal, and the communication service will most likely fail. Therefore, the UE (or the modem in the UE) may not perform BWP switching, but re-initiate RRC random access to cell B within the first duration. Here, when the UE re-initiates RRC random access to cell B, it may carry the configuration parameters of the initial BWP in the SIB1 message to inform the network side to use the RACH resources corresponding to the initial BWP in the SIB1 message for uplink and downlink synchronization. Among them, it can be seen from the above description that an initial downlink / uplink BWP (Initial DL / UL BWP) will be configured in SIB1, and BWP ID = 0. Under normal circumstances, the UE can normally send and receive data for communication services on the initial BWP. In this way, the UE subsequently uses the normally configured initial BWP for communication services, which can make the subsequent business processes normal.

[0139] S214: If cell B does not receive any message from the UE within the first duration, cell B triggers RLF or executes other instructions on its own.

[0140] Because cell B sets a switching delay (i.e., the first duration) for the UE, the UE should reply to the message within this duration. If cell B does not receive any message from the UE within the first duration, cell B may no longer wait, but trigger RLF or execute other instructions (e.g., actively instruct the UE to switch to the initial BWP) on its own.

[0141] In some implementations, before step S208, the UE may further perform S215: marking the BWPID with abnormal configuration, wherein the modem may mark the BWP ID (e.g., marked as invalidBWP). Accordingly, if cell B instructs the UE to switch to the BWP ID marked as abnormal in S211, the UE performs step S213.

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

[0143] In the above implementation, when the UE receives a BWP with a configuration anomaly configured by the network side, during the reconfiguration check, the UE can judge the check result as passed if the BWP to be used (i.e., BWP1) is checked normally, and it is not necessary to judge the check result of the RRC reconfiguration message as failed due to the abnormality of BWP2, thereby ensuring that the current communication service is carried out normally and improving the success rate of the communication service. In addition, if the cell instructs the UE to switch to the BWP with an abnormal configuration, the UE can re-initiate RRC random access to the cell within the first duration, and use the initial BWP in the SIB1 message for resource synchronization to ensure that subsequent communication services are also carried out normally.

[0144] Embodiment 3

[0145] Because the main problem in the related technology is that the UE cannot be connected when the called party makes a call, in order to ensure the success rate of the call service, this embodiment can also further execute different processing strategies according to whether it is currently in the call establishment process (or in the call process) during the reconfiguration check.

[0146] Specifically, Fig.10 As shown, the signaling interaction process of another example of a communication method in a wireless network provided in an embodiment of the present application may include:

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

[0148] S302, UE receives a service request sent by cell B.

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

[0150] The service request received by the UE may be, for example, a Paging message for calling the UE. The Paging message may be a message generated by the network side after receiving an Invite message from the caller. The UE then requests to establish an RRC connection with the network side so that the network side can initialize the context.

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

[0152] S305: The UE verifies the RRC reconfiguration message and identifies that an abnormally configured BWP exists in the RRC reconfiguration message.

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

[0154] Among them, the UE can identify the RRC reconfiguration message according to the calculation method specified in the above protocol, and then identify the BWP with abnormal configuration.

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

[0156] Among them, the current BWP is the BWP that the UE is going to use (or is called the BWP that is going to be activated), and the UE determines whether the current BWP configuration is abnormal, that is, whether the configuration of the parameters corresponding to the BWP ID that the UE is going to use (the BWP ID to be used is firstDownlinkActiveBWP-Id and firstUplinkActiveBWP-Id) is abnormal. For example, assuming that the BWP that the UE is going to use is configured as the aforementioned BWP1, as described above, the parameter configuration corresponding to BWP1 is normal, then the UE can execute S308.

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

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

[0159] S308, determining whether a call is currently being established, if so, executing S309, and if not, executing S307.

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

[0161] That is to say, if there is no abnormality in the configuration of the parameters corresponding to the BWP ID to be used by the UE, it is further determined whether it is currently in the call establishment process (or in the call process), and if it is in the call establishment process, the RRC reconfiguration completion message is normally replied. If it is not in the call establishment process, it can be considered that the RRC reconfiguration has failed, triggering the RLF process, and no subsequent steps will be performed. In some implementations, the UE can determine whether it is a call service request based on the above-mentioned received service request, and if so, it is determined to be in the call establishment process.

[0162] S310, the network side responds to initiate context establishment.

[0163] S311: The network sends an Invite message to the UE, and the call service proceeds normally.

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

[0165] S312, cell B sends a BWP switching instruction message to the UE.

[0166] S313, the UE determines whether it needs to switch to the BWP ID with the configuration abnormality, and if so, executes S314, otherwise, the subsequent process is normal.

[0167] S314, the UE re-initiates RRC random access to cell B, and carries the configuration parameters of the initial BWP in the SIB1 message during random access to perform uplink and downlink synchronization.

[0168] Since the parameters of the BWP (i.e., BWP1) currently used by the UE are configured normally, the subsequent communication services of the UE will proceed normally if the BWP switching is not performed. However, if cell B instructs the UE to perform BWP switching, and it needs to switch to the BWP (i.e., BWP2) containing the above-mentioned configuration abnormality, then the UE will determine that the parameter configuration corresponding to the BWP to be switched is abnormal, and the communication service will most likely fail. Therefore, the UE (or the modem in the UE) can not perform BWP switching, but re-initiate RRC random access to cell B. Here, when the UE re-initiates RRC random access to cell B, it can carry the configuration parameters of the initial BWP in the SIB1 message to inform the network side to use the RACH resources corresponding to the initial BWP in the SIB1 message for uplink and downlink synchronization. Among them, it can be seen from the above description that an initial downlink / uplink BWP (InitialDL / UL BWP) will be configured in SIB1, and BWP ID=0. Under normal circumstances, the UE can normally send and receive data for communication services on the initial BWP. In this way, the UE subsequently uses the normally configured initial BWP for communication services, which can make the subsequent business processes normal.

[0169] In some implementations, before step S309, the UE may further perform S315: marking the BWPID with abnormal configuration, wherein the BWP ID may be marked by the modem. Accordingly, if cell B instructs the UE to switch to the BWP ID marked as abnormal in S312, the UE performs step S314.

[0170] In the above implementation, when the UE receives a BWP with a configuration anomaly configured from the network side, during the reconfiguration check, the UE can judge the check result as passed if the BWP to be used (i.e., BWP1) is checked normally and the call is currently being established, and it is not necessary to judge the check result of the RRC reconfiguration message as failed due to the abnormality of BWP2, thereby ensuring that the current call service is carried out normally and improving the success rate of the call service. In addition, if the cell instructs the UE to switch to the BWP with an abnormal configuration, the UE can re-initiate RRC random access to the cell and use the initial BWP in the SIB1 message for resource synchronization to ensure that subsequent communication services are also carried out normally.

[0171] Embodiment 4

[0172] On the basis of the third embodiment, when the cell instructs the UE to perform BWP switching, a timer is usually set, and the UE is required to reply to the message within the timing range of the timer to complete the BWP switching. Therefore, the UE can re-initiate RRC random access to cell B within the timing range of the timer to avoid the network side performing other operations after the timer expires.

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

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

[0175] S402, UE receives a service request sent by cell B.

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

[0177] The service request received by the UE may be, for example, a Paging message for calling the UE. The Paging message may be a message generated by the network side after receiving an Invite message from the caller. The UE then requests to establish an RRC connection with the network side so that the network side can initialize the context.

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

[0179] S405: The UE identifies the RRC reconfiguration message, and identifies that an abnormally configured BWP exists in the RRC reconfiguration message.

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

[0181] Among them, the UE can identify the RRC reconfiguration message according to the calculation method specified in the above protocol, and then identify the BWP with abnormal configuration.

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

[0183] Among them, the current BWP is the BWP that the UE is going to use (or is called the BWP that is going to be activated), and the UE determines whether the current BWP configuration is abnormal, that is, whether the configuration of the parameters corresponding to the BWP ID that the UE is going to use (the BWP ID to be used is firstDownlinkActiveBWP-Id and firstUplinkActiveBWP-Id) is abnormal. For example, assuming that the BWP that the UE is going to use is configured as the aforementioned BWP1, as described above, the parameter configuration corresponding to BWP1 is normal, then the UE can execute S408.

[0184] S407, the UE does not reply the RRC reconfiguration completion message to cell B, triggering the RLF process.

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

[0186] S408, determining whether a call is currently being established, if so, executing S409, and if not, executing S407.

[0187] S409, UE replies to cell B with an RRC reconfiguration completion message.

[0188] That is to say, if there is no abnormality in the configuration of the parameters corresponding to the BWP ID to be used by the UE, it is further determined whether it is currently in the call establishment process (or in the call process), and if it is in the call establishment process, the RRC reconfiguration completion message is normally replied. If it is not in the call establishment process, it can be considered that the RRC reconfiguration has failed, triggering the RLF process, and no subsequent steps will be performed. In some implementations, the UE can determine whether it is a call service request based on the above-mentioned received service request, and if so, it is determined to be in the call establishment process.

[0189] S410, the network side responds to initiate context establishment.

[0190] S411: The network sends an Invite message to the UE, and the call service proceeds normally.

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

[0192] S412, cell B sends a BWP switching instruction message to the UE.

[0193] S413, the UE determines whether it needs to switch to the BWP ID with the configuration abnormality, and if so, executes S414, otherwise, the subsequent process is normal.

[0194] S414: Within the first duration, the UE re-initiates RRC random access to cell B, and carries the configuration parameters of the initial BWP in the SIB1 message during random access to perform uplink and downlink synchronization.

[0195] The first duration may be the duration of the timer set by cell B. In some implementations, when cell B sends an indication message for switching BWP to the UE, it may determine a switching delay (i.e., the first duration) based on the capabilities and subcarrier spacing (SCS) reported by the UE when the cell was previously accessed. For example, for a UE reporting Type 1, the switching delay determined by cell B is T1, and for a UE reporting Type 2, the switching delay determined by cell B is T2. In addition, if the subcarrier spacing of the BWP before the switch and the BWP after the switch are different, the switching delay may be determined based on the delay corresponding to the BWP with the larger delay. Exemplarily, the values ​​of T1 and T2 may be in the range of [10, 25] milliseconds.

[0196] If cell B instructs the UE to perform BWP switching, and it needs to switch to the BWP (i.e., BWP2) containing the above-mentioned configuration anomaly, then the UE will determine that the parameter configuration corresponding to the BWP to be switched is abnormal, and the communication service will most likely fail. Therefore, the UE (or the modem in the UE) may not perform BWP switching, but re-initiate RRC random access to cell B within the first duration. Here, when the UE re-initiates RRC random access to cell B, it may carry the configuration parameters of the initial BWP in the SIB1 message to inform the network side to use the RACH resources corresponding to the initial BWP in the SIB1 message for uplink and downlink synchronization. Among them, it can be seen from the above description that an initial downlink / uplink BWP (Initial DL / UL BWP) will be configured in SIB1, and BWP ID = 0. Under normal circumstances, the UE can normally send and receive data for communication services on the initial BWP. In this way, the UE subsequently uses the normally configured initial BWP for communication services, which can make the subsequent business processes normal.

[0197] S415: If cell B does not receive any message from the UE within the first duration, cell B triggers RLF or executes other instructions on its own.

[0198] Because cell B sets a switching delay (i.e., the first duration) for the UE, the UE should reply to the message within this duration. If cell B does not receive any message from the UE within the first duration, cell B may no longer wait, but trigger RLF or execute other instructions (e.g., actively instruct the UE to switch to the initial BWP) on its own.

[0199] In some implementations, before step S409, the UE may further perform step S416: marking the BWPID with abnormal configuration, wherein the BWP ID may be marked by the modem. Accordingly, if cell B instructs the UE to switch to the BWP ID marked as abnormal in step S412, the UE performs step S414.

[0200] In the above implementation, when the UE receives a BWP with a configuration anomaly configured from the network side, during the reconfiguration check, the UE can judge the check result as passed if the BWP to be used (i.e., BWP1) is checked normally and the call is currently being established, and it is not necessary to judge the check result of the RRC reconfiguration message as failed due to the abnormality of BWP2, thereby ensuring that the current call service is carried out normally and improving the success rate of the call service. In addition, if the cell instructs the UE to switch to the BWP with an abnormal configuration, the UE can re-initiate RRC random access to the cell and use the initial BWP in the SIB1 message for resource synchronization to ensure that subsequent communication services are also carried out normally.

[0201] It can be understood that the processes of interacting with the cell or the network side in the above embodiments can all be executed by the modem in the UE. Then, the communication method under the wireless network provided in the embodiment of the present application can be applied to mobile phones, tablet computers, wearable devices, vehicle-mounted devices, ultra-mobile personal computers (ultra-mobile personal computers, UMPC), netbooks, personal digital assistants (personal digital assistants, PDA) and other terminal devices with wireless network communication capabilities. The embodiment of the present application does not impose any restrictions on the specific type of terminal devices.

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

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

[0204] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

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

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

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

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

[0209] It is 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 present application, the terminal device 100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0210] The software system of the terminal device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The present application embodiment takes the Android system of the layered architecture as an example to exemplify the software structure of the terminal device 100.

[0211] Fig.13 1 is a software structure diagram of the terminal device 100 of the embodiment of the present application. The layered architecture divides the software into several layers, each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, namely, the application layer, the application framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer. The application layer can include a series of application packages.

[0212] like Fig.13 As shown, the application package may include camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

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

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

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

[0216] Android runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

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

[0218] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

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

[0220] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications. The media library supports playback and recording of multiple common audio and video formats, as well as static image files. The media library can support multiple audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc. The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis, and layer processing. The 2D graphics engine is a drawing engine for 2D drawing.

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

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

[0223] The embodiment of the present application provides a terminal device, which has the function of implementing the behavior of the terminal device in any of the above method embodiments. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to each sub-function in the above function. Specifically, the terminal device can be a user device, such as a mobile phone.

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

[0225] The present application also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a computer, the method flow related to the terminal device in any of the above method embodiments is implemented. Specifically, the computer can be the above terminal device.

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

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

[0228] The embodiment of the present application also provides a device, which is applied to a terminal device, and the device is coupled to a memory, and is used to read and execute instructions stored in the memory, so that the terminal device can execute the method flow related to the terminal device in any of the above method embodiments. The memory can be integrated in the processor or independent of the processor. The device can be a chip on the terminal device (such as a system on a chip SoC (System on a Chip)).

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

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

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

[0232] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution, some or all of the steps can be executed in parallel or sequentially, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0233] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

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

[0235] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple 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.

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

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

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

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

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

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

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

Claims

1. A communication method in a wireless network, characterized in that: include: The terminal device receives 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, wherein the first configuration information is configuration information corresponding to a first part of the bandwidth BWP, and the second configuration information is configuration information corresponding to a second BWP, the first BWP is a BWP that is currently required to be activated and configured by the first cell, and the first BWP includes one or more BWPs, and the second BWP is a BWP that is not currently required to be activated and configured by the first cell, and the second BWP includes one or more BWPs; When a first condition is met, the terminal device sends an RRC reconfiguration complete message in response to the RRC reconfiguration message to the first cell, the first condition including that there is no abnormality in the first BWP and there is an abnormality in the second BWP; After the terminal device sends the RRC reconfiguration completion message to the first cell, if the terminal device receives a first message sent by the first cell, the terminal device re-initiates RRC random access to the first cell based on the configuration parameters of the initial BWP in the system information block 1 SIB1 message, and the first message is used to instruct the terminal device to switch from the first BWP to the second BWP with an abnormality.

2. The method according to claim 1, characterized in that The terminal device re-initiates RRC random access to the first cell based on the configuration parameters of the initial BWP in the system information block 1 SIB1 message, including: Within a first time period, the terminal device re-initiates RRC random access to the first cell based on the configuration parameters of the initial BWP in the SIB1 message, and the first time period is the BWP switching delay set when the first cell sends the first message to the terminal device.

3. The method according to claim 2, characterized in that The initial BWP has BWPID=0.

4. The method according to claim 2 or 3, characterized in that The method further comprises: When the terminal device does not reply a message to the first cell within the first time period, the terminal device receives a radio link failure RLF message sent by the first cell.

5. The method according to any one of claims 1 to 4, characterized in that The first condition also includes that the terminal device is currently in the process of establishing a call.

6. The method according to claim 5, characterized in that The method further comprises: When there is no abnormality in the first BWP, there is an abnormality in the second BWP, and the terminal device is not currently in the call establishment process, the terminal device triggers the RLF process.

7. The method according to claim 5, characterized in that The terminal device receives a radio resource control RRC reconfiguration message sent by a first cell belonging to a first wireless network, including: After receiving the paging message sent from the first cell, the terminal device receives the RRC reconfiguration message sent by the first cell, where the paging message is used to page the terminal device when there is an incoming call.

8. The method according to any one of claims 1 to 7, characterized in that The abnormality of the second BWP includes: the configuration parameters of the second BWP include a first parameter item with abnormal configuration.

9. The method according to claim 8, characterized in that The first parameter item with the configuration abnormality is the startingPRB field with the configuration abnormality, and the startingPRB field with the configuration abnormality is the startingPRB field corresponding to the first value of the pucch resource Id in the configuration parameters of the second BWP.

10. The method according to any one of claims 1 to 9, characterized in that In the case that the second BWP is abnormal, the method further includes: The identification of the second BWP is marked as abnormal.

11. The method according to any one of claims 1 to 10, characterized in that After the terminal device receives a radio resource control RRC reconfiguration message sent by a first cell belonging to the first wireless network, the method further includes: When an abnormality occurs in the first BWP, the terminal device triggers the RLF process.

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

13. 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 12.

14. A chip system, characterized in that: The chip system includes: a processing circuit, a receiving pin and a transmitting pin; wherein the receiving pin, the transmitting pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the method as described in any one of claims 1 to 12 to control the receiving pin to receive a signal and control the transmitting pin to send a signal.

15. A chip system, characterized in that: The chip system includes a processor for supporting a terminal device to implement a method as described in any one of claims 1 to 12.

Images