Information processing method, terminal device, and chip system

Abstract

The present application relates to the technical field of communications, and discloses an information processing method, a terminal device, and a chip system. The method comprises: receiving a first message which is sent by a network side and carries a quality of service classification identifier and first indication information, the first message being used for instructing to create a first bearer, and the first indication information being used for indicating that target bearer configuration information exists in the bearer to be created; sending a first response message to the network side; receiving a second message which is sent by the network side and carries the quality of service classification identifier, the second message further carrying second indication information or not carrying the first indication information and the second indication information, the second message being used for instructing to delete the first bearer, and the second indication information being used for indicating that the target bearer configuration information does not exist in the bearer to be deleted; and in response to the second message, deleting the target bearer configuration information of the first bearer. In this way, the influence on a terminal service when a network experiences an abnormality can be reduced, thereby improving the stability and reliability of the terminal service.

Description

Information processing method, terminal device and chip system

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on September 28, 2023, with application number 202311290534.8 and application name “Information Processing Method, Terminal Device and Chip System”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to an information processing method, terminal equipment, and chip system. Background Art

[0003] Currently, when a user equipment (UE) needs to conduct a data service such as a voice call or video call, the network can instruct the UE to create a bearer for data transmission and configure bearer configuration information such as relevant rules for the created bearer. In addition, after the UE ends the data service, the network can also instruct the UE to delete the created bearer and its bearer configuration information.

[0004] However, when deleting a bearer on the network side, an abnormality may occur, resulting in the inability to instruct the UE to delete the bearer configuration information. For example, when the UE needs to perform a data service, the network side instructs the UE to create a bearer by sending a create bearer message carrying first indication information to the UE, and the first indication information is used to indicate that the bearer to be created has target bearer configuration information. However, when the UE needs to end the data service, due to abnormal reasons such as network abnormality or network element abnormality, the network side may instruct the UE to delete the created bearer by sending a delete bearer message that does not carry the first indication information to the UE. For example, the delete bearer message carries the second indication information for indicating that the target bearer configuration information does not exist for the bearer to be deleted, or carries neither the first indication information nor the second indication information. This abnormal situation will result in the UE not deleting the local target bearer configuration information after receiving the delete bearer message, and the UE will also keep resending a deletion request to the network side requesting to delete the target bearer configuration information. However, the UE's repeated resending of the deletion request may affect the UE's data service.

[0005] Summary of the Invention

[0006] This application provides an information processing method, terminal device, and chip system that can reduce the impact of network anomalies on terminal services. The technical solution is as follows:

[0007] In the first aspect, an information processing method is provided, which can be applied to a UE, and the method includes: the UE receives a first message sent by the network side that carries a service quality classification identifier and first indication information, the first message is used to indicate the creation of a first bearer corresponding to the service quality classification identifier, and the first indication information is used to indicate that the bearer to be created has target bearer configuration information. In response to the first message, a first response message is sent to the network side to indicate acceptance of the creation of the first bearer. Afterwards, a second message sent by the network side that carries the service quality classification identifier but does not carry the first indication information is received, and the second message is used to indicate the deletion of the first bearer with the service quality classification identifier. For example, the second message carries the second indication information, or carries neither the first indication information nor the second indication information, and the second indication information is used to indicate that the bearer to be deleted does not have the target bearer configuration information. In response to the second message, the target bearer configuration information of the first bearer is deleted.

[0008] Normally, the first message sent by the network side when creating a bearer for the UE's data service carries the first indication information, so the second message sent when deleting the bearer should also carry the first indication information. However, in the event of an abnormality such as a network abnormality or a network element abnormality on the network side, the second message sent by the network side to the UE when deleting the bearer may not carry the first indication information, such as carrying the second indication information, or carrying neither the first indication information nor the second indication information. In this case, the UE may not delete the locally stored target bearer configuration information after receiving the second message, and may continue to send the first deletion request to the network side for requesting the deletion of the target bearer configuration information. However, if the UE continues to resend the deletion request, it may affect the UE's data service, such as causing the bearer of the next data service to be abnormally deleted, and then causing the next data service to end abnormally.

[0009] In an embodiment of the present application, in order to reduce the impact of network anomalies on terminal services, after the UE receives a first message sent by the network side that carries first indication information and is used to indicate the creation of a bearer, if a second message is received that indicates the deletion of the created bearer, even if the second message does not carry the first indication information, it is considered that the second message carries the first indication information, and the target bearer configuration information of the created bearer is deleted, such as deleting the locally stored target bearer configuration information of the created bearer. For example, after receiving the second message that indicates the deletion of the created bearer, even if the second message carries the second indication information, it is considered that the second message carries the first indication information, and the target bearer configuration information of the created bearer is deleted. Alternatively, even if the second message carries neither the first indication information nor the second indication information, it is considered that the second message carries the first indication information, and the target bearer configuration information of the created bearer is deleted.

[0010] In this way, when the network side is unable to instruct the UE to delete the target bearer configuration information due to an abnormality, the UE can be prevented from repeatedly resending the first deletion request to delete the target bearer configuration information, thereby preventing the network side from mistakenly deleting the bearer of the next data service due to the UE's repeated deletion request, thereby avoiding the impact of the abnormal situation that the network side is unable to instruct the UE to delete the bearer configuration information due to an abnormality on the next data service, ensuring the normal progress of the next data service, reducing the impact of network abnormalities on the UE service, improving the stability and reliability of the service, and thus improving the user experience.

[0011] The target bearer configuration information may be any configuration information related to the bearer. For example, the target bearer configuration information may include one or more of the following information: QoS rules, EPS bearer context mapping information, and QoS flow description information. Of course, the target bearer configuration information may also include other bearer configuration information, which is not limited in this embodiment of the present application.

[0012] Among them, QoS rules are used to indicate the QoS transmission mechanism rules of the corresponding QoS flow. QoS transmission mechanism rules can provide high-quality network services for different types of data transmission through intelligent management. For example, QoS rules can include one or more of priority rules, bandwidth guarantee rules, delay control rules, and packet loss control rules. Priority rules are used to intelligently manage data transmission by setting priority rules based on the importance of different types of data. For example, for video data with high real-time requirements, its priority can be set to high so that it is transmitted first. Bandwidth guarantee rules are used to avoid network overload by limiting the bandwidth usage ratio of each data type and ensure the rational use of network bandwidth. Delay control rules are used to ensure the timeliness of data transmission by managing the delay of data transmission to meet the requirements of some delay-sensitive applications. Packet loss control rules are used to ensure the integrity of data transmission by managing the packet loss of data transmission and avoid data packet loss during network transmission.

[0013] The EPS bearer context mapping information is used to indicate the mapping relationship between the EPS bearer and the QoS flow. The QoS flow description information is used to define the QoS flow corresponding to the corresponding bearer.

[0014] In one embodiment of the present application, for the first message indicating the creation of a bearer and the second message indicating the deletion of a bearer, the two messages can indicate whether the corresponding bearer is configured with target bearer configuration information by carrying different indication information (first indication information and second indication information). For example, both the first message and the second message carry a bearer configuration identifier, and the bearer configuration identifier is used to indicate whether the corresponding bearer has target bearer configuration information. The bearer configuration identifier can be pre-configured with different identification values. For example, the identification value of the bearer configuration identifier may include a first identification value and a second identification value, and the first identification value is used to indicate that the corresponding bearer has target bearer configuration information, and the second identification value is used to indicate that the corresponding bearer does not have target bearer configuration information. For example, the first identification value and the second identification value are 1 and 0, respectively. Of course, the first identification value and the second identification value can also be in other forms, and the embodiment of the present application does not limit this.

[0015] In this case, the first indication information refers to the bearer configuration identifier with the first identification value, and the second indication information refers to the bearer configuration identifier with the second identification value. For example, if the first indication information is qos_rules_incl=1, it indicates that the corresponding bearer is configured with QoS rules; if the second indication information is qos_rules_incl=0, it indicates that the corresponding bearer is not configured with QoS rules.

[0016] In another embodiment of the present application, these two messages can also indicate whether the corresponding bearer is configured with the target bearer configuration information by whether they carry the first indication information. For example, for these two messages, if the message carries the first indication information, it indicates that the corresponding bearer is configured with the target bearer configuration information. If the message does not carry the first indication information, it indicates that the corresponding bearer is not configured with the target bearer configuration information. The first indication message can be a configuration identifier of the target bearer configuration information, such as a configuration ID or number of the target bearer configuration information. For example, the first indication message can be id=28.

[0017] Among them, the service quality classification identifier corresponding to different network standards is represented differently. For example, the service quality classification identifier under the LTE network can be represented by QCI, and the service quality classification identifier under the 5G network can be represented by 5QI. Among them, different service quality classification identifier values ​​are used to indicate different service types, which can include voice calls, video calls, web surfing, etc. For example, QCI=1 and 5QI=1 correspond to voice call services, QCI=2 and 5QI=2 correspond to video call services, etc.

[0018] In the embodiments of the present application, the quality of service classification identifier value carried in the create bearer message and delete bearer message can be any of the available quality of service classification identifier values. That is, the service type corresponding to the quality of service classification identifier can be any service type within the range of service types permitted by the protocol. For example, the QCI value and 5QI can be any value from 1, 2, ..., 9. Of course, 5QI can also be a value greater than 9, which is not limited in the embodiments of the present application.

[0019] Among them, the bearer identifier is used to indicate the bearer to be created or deleted. The forms of bearers created under different network standards are different, and the corresponding bearer identifiers are expressed differently. For example, the bearer created under the LTE network can be a QoS flow, and the corresponding bearer identifier can be a QoS flow ID (QoS flow ID, QFI). The bearer created under the 5G network can be an EPS bearer, and the corresponding bearer identifier can be an EPS bearer ID (EPS Bearer ID, EBI).

[0020] In addition, the first message and the second message may also carry an identifier of the target bearer configuration information, such as an ID or number of the target bearer configuration information, etc. Of course, the first message and the second message may also carry other information, which is not limited in the embodiment of the present application.

[0021] In one embodiment of the present application, the UE may delete the locally stored target bearer configuration information in response to the second message, and send a second response message to the network side, where the second response message is used to indicate acceptance of deletion of the first bearer.

[0022] That is, after receiving the second message, the UE immediately deletes the locally stored target bearer configuration information and sends a response message to the network side.

[0023] In another embodiment of the present application, the UE may first send a second response message to the network side in response to the second message; send a first deletion request to the network side once or multiple times, and if no first deletion indication information is received for the first deletion request, delete the locally stored bearer configuration information of the first bearer, and the first deletion indication information is used to indicate the target bearer configuration information for deleting the first bearer.

[0024] That is, after receiving the second message, the UE first sends a response message to the network side, and then sends one or more first deletion requests to the network side requesting to delete the target bearer configuration information, so as to try to negotiate with the network side to delete the target bearer configuration information. In addition, if the UE does not receive the first deletion indication information for the first deletion request after sending one or more first deletion requests to the network side, it can also actively delete the locally stored bearer configuration information of the first bearer without the consent of the network side, and no longer resend the first deletion request. This can avoid the situation where the UE keeps resending the first deletion request after being rejected by the network side.

[0025] Among them, the first deletion indication information can be a third message, the third message includes a service quality classification identifier, a bearer identifier and the first indication information, and the third message is used to indicate the deletion of the first bearer corresponding to the service quality classification identifier and the target bearer configuration information of the first bearer.

[0026] In another embodiment of the present application, the number of times the UE resends the first deletion request can be controlled to prevent the UE from repeatedly resending the first deletion request. For example, after sending a preset number of deletion requests to the network side, if no first deletion indication information is received in response to the first deletion request, the locally stored bearer configuration information of the first bearer is deleted.

[0027] That is, the UE is only allowed to send a maximum of a preset number of first deletion requests to the network. If the UE does not receive the first deletion indication information for the first deletion request after sending the first deletion request a preset number of times, the UE can proactively delete the locally stored target bearer configuration information without the network's consent. This can avoid the situation where the UE repeatedly sends the first deletion request after being rejected by the network.

[0028] In another embodiment of the present application, a timer duration can be set for the UE to resend the first deletion request to prevent the UE from repeatedly resending the first deletion request. For example, after receiving the second message, a first timer is started; within the timer duration of the first timer, one or more first deletion requests are sent to the network side; if no first deletion indication information for the first deletion request is received within the timer duration of the first timer, the locally stored bearer configuration information of the first bearer is deleted.

[0029] That is, the UE is only allowed to send the first deletion request within the timer duration of the first timer. If the UE does not receive the first deletion indication information in response to the first deletion request within the timer duration, the UE can proactively delete the locally stored target bearer configuration information without the consent of the network side. This can avoid the situation where the UE repeatedly sends the first deletion request after being rejected by the network side.

[0030] It is understandable that starting the first timer after receiving the second message may include any of the following implementations: starting the first timer in response to receiving the second message, that is, starting the first timer immediately after receiving the second message; starting the first timer when sending the second response message to the network side; starting the first timer after sending the second response message to the network side; starting the first timer when sending the first deletion request to the network side for the first time; starting the first timer after sending the first deletion request to the network side for the first time. Of course, the first timer can also be started at other appropriate times after receiving the second message, and this embodiment of the present application is not limited to this.

[0031] In one embodiment of the present application, failure to receive first deletion indication information in response to a first deletion request includes: receiving a deletion rejection message sent by the network, the deletion rejection message being used to indicate a rejection of deleting the target bearer configuration information of the first bearer; and failure to receive first deletion indication information in response to the first deletion request sent by the network. That is, after receiving the deletion rejection message sent by the network, the first deletion indication information sent by the network has not yet been received.

[0032] In one embodiment of the present application, when the terminal device resides on a fifth-generation 5G network, the service quality classification identifier is the service quality classification identifier 5QI of the 5G network, the first message and the second message are protocol data unit PDU session modification command messages, and the first response message is a PDU session modification completion message. When the terminal device resides on a long-term evolution LTE network, the service quality classification identifier is the service quality classification identifier QCI of the LTE network, the first message is an activation dedicated evolved packet system EPS bearer context request message, the first response message is an activation dedicated EPS bearer context accept message, and the second message is a deactivation dedicated EPS bearer context request message.

[0033] In one embodiment of the present application, when the terminal device resides on a 5G network, the second response message is a PDU session modification complete message, and the first deletion request is a PDU session modification request message. When the terminal device resides on an LTE network, the second response message is a deactivate dedicated EPS bearer context accept message, and the first deletion request is a modify EPS bearer context request message.

[0034] In one embodiment of the present application, when the terminal device resides in a 5G network, the first message and the second message also include a PDU session identifier, and the PDU session modification request message includes the PDU session identifier, which is used to identify the session corresponding to the first bearer.

[0035] In one embodiment of the present application, when the terminal device resides on a 5G network, the delete reject message is a PDU session modification reject message, and the third message is a PDU session modification command message. When the terminal device resides on an LTE network, the delete reject message is a bearer resource modification reject message, and the third message is a deactivate dedicated EPS bearer context request message.

[0036] In one embodiment of the present application, the service type indicated by the service quality classification identifier is a voice call service or a video call service. Before the UE receives the first message sent by the network side, it can also initiate a call or receive an incoming call through the network side.

[0037] For example, the UE may send a first Invite message to the network, then receive a first provisional response message from the network, and then receive a first session-in-progress message from the network. Alternatively, the UE may receive a second Invite message from the network, respond to the second Invite message, and then send a second provisional response message to the network. Thereafter, the UE may send a second session-in-progress message to the network. The provisional response message may be a 100Tying message, and the session-in-progress message may be a 183 message.

[0038] In a second aspect, an information processing device is provided, wherein the information processing device has the function of implementing the information processing method of the first aspect. The information processing device includes at least one module, wherein the at least one module is used to implement the information processing method of the first aspect.

[0039] In a third aspect, an information processing device is provided, wherein the structure of the information processing device includes a processor and a memory, wherein the memory is used to store a program that supports the information processing device in executing the information processing method provided in the first aspect, and to store data involved in implementing the information processing method described in the first aspect. The processor is configured to execute the program stored in the memory. The information processing device may also include a communication bus for establishing a connection between the processor and the memory.

[0040] In a fourth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer executes the information processing method described in the first aspect.

[0041] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the information processing method described in the first aspect.

[0042] In the sixth aspect, a chip system is provided, which includes one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected through lines; the chip system is applied to a terminal device including a communication module and a memory; the interface circuit is used to receive a signal from the memory and send the signal to the processor, the signal including computer instructions stored in the memory; when the processor executes the computer instructions, the terminal device executes the information processing method described in the first aspect above.

[0043] The technical effects obtained by the above-mentioned second, third, fourth, fifth and sixth aspects are similar to the technical effects obtained by the corresponding technical means in the above-mentioned first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] FIG1 is a schematic diagram of a communication system to which the technical solution provided in an embodiment of the present application is applicable;

[0045] FIG2 is a schematic diagram of another communication system to which the technical solution provided in an embodiment of the present application is applicable;

[0046] FIG3 is a schematic structural diagram of a terminal device provided in an embodiment of the present application;

[0047] FIG4 is a schematic diagram of a paging process provided in the related art;

[0048] FIG5 is a schematic diagram of a paging process provided in an embodiment of the present application;

[0049] FIG6 is a schematic diagram of another paging process provided in an embodiment of the present application;

[0050] FIG7 is a software structure block diagram of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0051] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0052] It should be understood that the “multiple” mentioned in this application refers to two or more. In the description of this application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; “and / or” in this article is merely a description of the association relationship of associated objects, indicating that 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 order to facilitate the clear description of the technical solution of this application, words such as “first” and “second” are used to distinguish between identical or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as “first” and “second” do not limit the quantity and execution order, and words such as “first” and “second” do not necessarily limit them to be different.

[0053] The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The application scenarios of the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0054] The information processing method provided in the embodiment of the present application can be applied to a communication system, which may be a Long Term Evolution (LTE) communication system, a fifth generation (5G) communication system, or a new communication system that will emerge in the future development of wireless communications, etc., and the embodiment of the present application does not limit this. The communication system may include terminal equipment, access network equipment, core network equipment, and an Internet-protocol Multimedia Subsystem (IMS). The access network equipment, core network equipment, and IMS may be collectively referred to as a network (Network, NW).

[0055] FIG1 is a schematic diagram of a communication system to which the technical solution provided in an embodiment of the present application is applicable. As shown in FIG1 , the communication system may include UE 101, UE 102, and a 5G NW. The 5G NW is deployed in a standalone (SA) network. The 5G NW may include a 5G base station 201, a 5G base station 202, a 5G core network (5GC) 203, and an IMS 204. The 5G base stations 201 and 202 are connected to the 5G core network 203, and the 5G core network 203 is connected to the IMS 204.

[0056] Among them, UE101 and UE102 are terminal devices, and the terminal devices may include smart phones (such as mobile phones equipped with Android systems or iOS systems, etc.), tablet computers, laptops, PDAs, mobile Internet devices (mobile internet devices, MIDs), wearable devices (such as smart watches, smart bracelets, etc.) or other devices that can access the Internet. In the embodiment of the present application, the terminal device can be a terminal sold independently or a chip in the terminal. In the technical solution provided in the embodiment of the present application, the technical solution provided in the embodiment of the present application is described by taking the device for realizing the function of the terminal as an example, which is a terminal device.

[0057] As an example, user information is stored in a terminal device. This user information may include an International Mobile Subscriber Identification Number (IMSI). The IMSI may be stored in the subscriber identity module (SIM) card of the terminal device. The terminal device can use this user information as an identity to initiate or receive calls through various voice solutions.

[0058] 5G base station 201 and 5G base station 202 can be next generation NodeBs (gNBs). 5G base station 201 can be connected to UE 101 and communicate with UE 101 using 5G new radio (NR) access technology, that is, 5G base station 201 and UE 101 communicate via an NR link. 5G base station 202 can be connected to UE 102 and communicate with UE 102 using 5G NR access technology, that is, 5G base station 202 and UE 102 communicate via an NR link.

[0059] The 5G core network 203 is used to exchange, forward, connect, and route data. The network elements in the 5G core network 203 are functional virtual units, which may include but are not limited to: access and mobility management function (AMF), user plane function (UPF), and session management function (SMF). The AMF can perform registration, connection, reachability, and mobility management, provide a session management message transmission channel for the UE and SMF, and provide authentication and authorization functions for the UE when accessing. The SMF is responsible for tunnel maintenance, Internet protocol (IP) address allocation and management, policy implementation and quality of service (QoS) control, billing data collection, roaming, etc. For example, the SMF can be used to manage UE sessions through the UPF and perform the establishment, modification, and release of each session. The UPF is mainly responsible for the routing and forwarding related functions of user plane data packets.

[0060] IMS 204 may include a call session control function (CSCF) and a home subscriber server (HSS). The CSCF controls signaling and authentication during multimedia call sessions, and coordinates with other network entities to control the session. The HSS manages user data, storing all user and service-related data, such as user identity, subscription information, and access information.

[0061] Among them, CSCF can include Proxy-Call Session Control Function (P-CSCF) entity, Interrogating-Call Session Control Function (I-CSCF) entity, and Serving-Call Session Control Function (S-CSCF) entity. The P-CSCF entity is the first connection point between the access network and the IMS. All session messages initiated from and terminated at UEs that support IMS must be forwarded through the P-CSCF entity. The I-CSCF entity can connect the S-CSCF entity and the P-CSCF entity to provide the UE with an entry to the home network. During the call process, the call message to the IMS network is first routed to the I-CSCF entity. The I-CSCF entity can query the address information of the S-CSCF entity where the user is registered for the UE through the HSS in the IMS, and then route the message to the S-CSCF. The S-CSCF entity is the control core of the IMS and provides UE with functions such as session control and registration.

[0062] As an example, UE101 serves as a calling UE and UE102 serves as a called UE, and both can implement a voice call service or a video call service through the 5G NW.

[0063] FIG2 is a schematic diagram of another communication system to which the technical solution provided in an embodiment of the present application is applicable. As shown in FIG2 , the communication system may include UE 103, UE 104, and a 4G NW. The 4G NW may include a 4G base station 301, a 4G base station 302, a 4G core network (evolved packet core, EPC) 303, and an IMS 304. 4G base stations 301 and 302 are connected to a 4G core network 303, which is connected to an IMS 304.

[0064] Among them, UE103 and UE104 are terminal devices and will not be described in detail here.

[0065] The 4G base station 301 may be an evolved Node B (eNB). The 4G base station 301 may be connected to the UE 103 and communicate with the UE 103. The 4G base station 302 may be connected to the UE 104 and communicate with the UE 104.

[0066] The 4G core network 303 mainly includes the following network elements: mobility management entity (MME), serving gateway (SGW), packet data network gateway (PGW), home subscriber server (HSS) and application server (AS). The main functions of MME include access control, mobility management, attachment and detachment, session management (such as bearer establishment, modification and release), etc. The main function of SGW is to route and forward data packets. The main functions of PGW include user-based packet filtering, lawful interception, IP address allocation, etc. The HSS is used to store user subscription information, user subscription data and mobile user location information.

[0067] The functions of IMS 304 are similar to those of the aforementioned IMS 204 and will not be further described in detail in this embodiment of the present application.

[0068] As an example, UE 103 serves as a calling UE and UE 104 serves as a called UE, and both can implement a voice call service or a video call service through the 4G NW.

[0069] As another example, a UE in a 4G communication system may also implement a voice call service or a video call service with a UE in a 5G communication system. For example, UE 101 implements a voice call service or a video call service with UE 103 through a 4G NW and a 5G NW where UE 103 is located.

[0070] It can be understood that the units shown in Figures 1 and 2 do not constitute a specific limitation on the wireless communication system. The wireless communication system may also include more or fewer units than shown in the figure, or combine certain units, or split certain units, or arrange the units differently. This application does not limit this.

[0071] Next, the terminal device involved in the embodiment of the present application is described.

[0072] FIG3 is a schematic diagram of the structure of a terminal device 100 provided in an embodiment of the present application. The terminal 100 may be UE 101 and UE 102 in FIG1 , or UE 103 and UE 104 in FIG2 . Referring to FIG3 , 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 jack 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195. Among them, the sensor module 180 can 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.

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

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

[0075] The controller may be the nerve center and command center of the terminal device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

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

[0077] In some embodiments, the processor 110 may include one or more interfaces, such as an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0078] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the terminal device 100. While charging the battery 142, the charging management module 140 can also provide power to the terminal device 100 via the power management module 141.

[0079] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0080] 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.

[0081] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0082] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the terminal device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

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

[0084] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the terminal device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0085] In some embodiments, antenna 1 of terminal device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that terminal device 100 can communicate with a network and other devices via wireless communication technology. Wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, 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).

[0086] The terminal device 100 implements display functions through a GPU, display screen 194, and an application processor. The GPU is a microprocessor for image processing and is connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or change display information. The terminal device 100 can implement a camera function through the ISP, camera 193, video codec, GPU, display screen 194, and application processor.

[0087] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

[0088] The internal memory 121 can be used to store computer executable program codes, which 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. The program storage area may 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 may store data created by the terminal device 100 during use (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.

[0089] The terminal device 100 can implement audio functions, such as music playback, recording, etc., through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D and the application processor.

[0090] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to and disconnected from the terminal device 100 by inserting or removing it from the SIM card interface 195. The terminal device 100 can support one or N SIM card interfaces, where N is an integer greater than one. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The terminal device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the terminal device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the terminal device 100 and cannot be separated from the terminal device 100.

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

[0092] The methods in the following embodiments can all be implemented in the terminal device 100 having the above hardware structure. Next, the terminal device 100 is taken as a UE as an example for description.

[0093] Currently, when a UE needs to conduct data services such as voice calls, video calls, or web surfing, the network can instruct the UE to create a bearer for data transmission and configure bearer configuration information, such as relevant rules, for the created bearer. Furthermore, after the UE terminates the data service, the network can also instruct the UE to delete the created bearer and its bearer configuration information. However, when the network deletes a bearer, an exception may occur, preventing the UE from being instructed to delete the bearer configuration information, thereby impacting the UE's data service. For example, this could affect the UE's next data service, causing the UE's next data service to terminate abnormally.

[0094] Next, taking the data service as a voice call service, and the UE residing on the 5G network and being the called UE as an example, the following figures will be used to describe in detail the situation in the related art where the network side is unable to instruct the UE to delete the bearer configuration information, resulting in an abnormal paging process. Please refer to Figure 4, which is a schematic diagram of a paging process provided in the related art. As shown in Figure 4, the paging process includes the following steps:

[0095] Step 401: The network sends an Invite message 1 to the UE.

[0096] The network side refers to the 5G network in which the UE is located. The Invite message is a commonly used Session Initiation Protocol (SIP) request message used to establish a conversation for media exchange with a user agent. SIP is an application layer protocol that can establish, modify, and release multimedia sessions in IP networks. SIP's main applications include, but are not limited to, voice, messaging, video, and call control.

[0097] In response to the user operation, the calling UE can initiate a call. The calling UE can send a call request message (for example, Invite message 1) through the calling side network (the network where the calling UE is registered). After the Invite message 1 arrives at the called side network (network side), it is sent by the called side network to the called UE.

[0098] Step 402: The UE sends a 100Trying message to the network side.

[0099] The 100Trying message is a temporary response message used to indicate that the UE on the network side has received the Invite message 1 and the message is being processed.

[0100] After the called UE receives the Invite message 1, it can send a 100Trying message through the network side (called side network). After the 100Trying message reaches the calling side network, it is sent to the calling UE by the host side network.

[0101] Step 403: The UE sends a 183 message to the network side.

[0102] Among them, the 183 message is used to indicate that the call connection is in progress.

[0103] Step 404: The network side sends a PDU session modification command message 1 to the UE. The PDU session modification command message 1 carries the PDU session identity document (ID) 1, 5QI=1, QFI1, qos_rules_incl=1, QoS rule ID1, and the corresponding QoS rule.

[0104] After receiving the 183 message fed back by the called UE, the network side can create a bearer 1 for carrying voice call data for the UE by sending a PDU session modification command message to the UE.

[0105] Among them, PDU session ID1 is used to identify the session corresponding to the created bearer 1. 5QI (5G QoS class identifier) ​​is the 5G quality level classification identifier. Different 5QI values ​​correspond to different resource types, priorities, delays and packet loss rates. In addition, different 5QI values ​​correspond to different service types. For example, 5QI=1 corresponds to voice call services. qos_rules_incl is the QoS rule configuration identifier in the bearer configuration identifier, which is used to indicate whether the corresponding bearer (i.e., bearer 1) is configured with QoS rules. QFI1 is the bearer identifier of bearer 1, which is used to indicate bearer 1. QoS flow identifier (QoS flow ID, QFI) is used to identify QoS flow. In the 5G network, QoS flow can be configured as a bearer for the UE, so the QoS flow indicated by QFI1 can be called bearer 1. qos_rules_incl=1 indicates that the corresponding bearer (i.e., bearer 1) is configured with QoS rules. QoS rule ID1 can include one or more QoS rule IDs, each of which is used to indicate a QoS rule. The QoS rule corresponding to QoS rule ID1 is the QoS rule configured for bearer 1. In addition, the PDU session modification command message 1 may also carry an operation code 1, where the operation code 1 is used to indicate the creation of a bearer.

[0106] The PDU session modification command message 1 is used to instruct the creation of a bearer 1 with 5QI=1, that is, a bearer 1 used to carry voice call data. Moreover, the created bearer 1 with 5QI=1 is configured with a QoS rule.

[0107] Step 405: The UE sends a PDU session modification complete message 1 to the network side.

[0108] After receiving the PDU session modification command message 1 from the network side, the UE can locally store the PDU session ID1, 5QI=1, QFI1, QoS rule ID1, and the QoS rule corresponding to the QoS rule ID1, and return the session modification completion message 1 to the network side.

[0109] It should be noted that QoS rule ID1 and the corresponding QoS rule have a corresponding relationship with QFI1. This corresponding relationship is used to indicate that the first two are configured for QFI1, that is, QoS rule ID1 is the ID of the QoS rule configured for bearer 1 indicated by QFI1, and the QoS rule corresponding to QoS rule ID1 is the QoS rule configured for bearer 1 indicated by QFI1.

[0110] Step 406: The network side and the UE perform a call cancellation process.

[0111] Before a call is successfully established, the network may cancel the call process due to an exception.

[0112] For example, the network side may send a CANCEL message to the UE to cancel the call process. The CANCEL message is used to close a session for which a final response has not been received.

[0113] Step 407: The network side sends a PDU session modification command message 2 to the UE. The PDU session modification command message 2 carries the PDU session ID 1, QFI 1, and qos_rules_incl=0.

[0114] After canceling the call, the network can delete the created bearer 1 with 5QI=1 by sending a PDU Session Modify Command message 2 to the UE. qos_rules_incl=0 indicates that no QoS rules are configured for the corresponding bearer (i.e., bearer 1). In addition, the PDU Session Modify Command message 2 can also carry an operation code 2, which is used to indicate the deletion of the corresponding bearer (i.e., bearer 1).

[0115] Normally, if the PDU session modification command message sent when creating a bearer carries qos_rules_incl=1, the PDU session modification command message sent when deleting the bearer should also carry qos_rules_incl=1. In this way, after the UE receives the PDU session modification command message indicating the deletion of the bearer, it can recognize that the bearer to be deleted is configured with QoS rules and delete the QoS rules corresponding to the bearer stored locally. However, due to abnormal conditions such as network abnormalities or network element abnormalities on the network side, in such abnormal conditions, the PDU session modification command message 2 sent by the network side to the UE may carry qos_rules_incl=0 instead of qos_rules_incl=1.

[0116] Step 408: The UE sends a PDU session modification completion message 2 to the network side.

[0117] After the UE receives the PDU session modification command message 2, since the PDU session modification command message 2 carries qos_rules_incl = 0, the UE will assume that the bearer 1 to be deleted is not configured with QoS rules. Therefore, after deleting bearer 1, the UE will not delete the locally stored QoS rules corresponding to bearer 1. That is, in response to the PDU session modification command message 2, the UE will return the PDU session modification complete message 2 to the network side without deleting the locally stored QoS rules corresponding to bearer 1.

[0118] Step 409: The UE sends a PDU session modification request message to the network side for the first time. The PDU session modification request message carries PDU session ID1 and QoS rule ID1, and is used to request deletion of the QoS rule corresponding to QoS rule ID1.

[0119] Since the UE still stores the QoS rule of bearer 1 locally, the UE will request to delete the QoS rule by sending a PDU session modification request message carrying QoS rule ID 1 indicating the QoS rule of bearer 1 to the network side.

[0120] Step 410: The network sends a PDU session modification reject message to the UE. The PDU session modification reject message carries a rejection cause value of 31.

[0121] The PDU Session Modification Reject message is used to indicate the rejection of the UE's PDU Session Modification request, that is, the rejection of the deletion of the QoS rule for Bearer 1. The rejection reason value 31 "cause=31" is used to indicate an unclear reason. Due to an abnormality on the network side, it may believe that the UE has been instructed to delete the QoS rule for Bearer 1 via PDU Session Modification Command Message 2. After receiving the PDU Session Modification Request message for requesting the deletion of the QoS rule, the PDU Session Modification Request message is rejected.

[0122] Step 411: The UE sends a PDU session modification request message to the network side for the second time.

[0123] After the PDU session modification request message sent by the UE for the first time is rejected, the UE will resend the PDU session modification request message to the network to request to delete the QoS rule again.

[0124] Step 412: The network sends a PDU session modification reject message to the UE, where the PDU session modification reject message carries a rejection cause value of 31.

[0125] After the network side receives the PDU session modification request message sent by the UE for the second time, it will reject the received PDU session modification request message again and return a PDU session modification rejection message to the UE, similar to rejecting the PDU session modification request message sent by the UE for the first time.

[0126] Step 413: The UE sends a PDU session modification request message to the network side for the third time.

[0127] Step 414: The network sends a PDU session modification reject message to the UE, where the PDU session modification reject message carries a rejection cause value of 31.

[0128] Similarly, after the network side receives the PDU session modification request message sent by the UE for the third time, it will reject the received PDU session modification request message again and return a PDU session modification reject message to the UE.

[0129] Step 415: The network sends an Invite message 2 to the UE.

[0130] During the process of the UE resending the PDU Session Modification Request message to the network, the called UE may receive an incoming call again, i.e., be called again. In this case, the network can receive the Invite message 2 sent by the calling UE through the calling side network and the called side network.

[0131] Step 416: The UE sends a 100Trying message to the network side.

[0132] Step 417: The UE sends a 183 message to the network side.

[0133] Step 418: The network side sends a PDU session modification command message 3 to the UE. The PDU session modification command message 3 carries PDU session ID1, 5QI=1, QFI1, qos_rules_incl=1, QoS rule ID1 and corresponding QoS rules.

[0134] The network can create a bearer for the UE to carry voice call data by sending a PDU Session Modify Command message 3 to the UE. The PDU Session Modify Command message 1 is used to instruct the creation of Bearer 2 with 5QI = 1 to carry voice call data. The Bearer Identifier of Bearer 2 is QFI1. Furthermore, the created Bearer 2 with 5QI = 1 is configured with QoS rules.

[0135] It should be noted that after deleting the aforementioned bearer 1, the network side can reclaim the PDU session ID 1, QFI 1, and QoS rule ID 1. Therefore, when creating bearer 2, the reclaimed PDU session ID 1 can be reallocated to the PDU session corresponding to bearer 2, the reclaimed QFI 1 can be reallocated to the QoS flow corresponding to bearer 2, and the QoS rule ID 1 can be reallocated to the QoS rule configured for bearer 2. This results in the PDU session modification command message 3 carrying the same PDU session ID, QFI, and QoS rule ID as the aforementioned PDU session modification command message 1.

[0136] Step 419: The UE sends a PDU session modification completion message 3 to the network side.

[0137] Step 420: The UE sends a 200 OK message to the network side.

[0138] The 200 OK message is the final response to the Invite message 2, indicating that the content of the Session Description Protocol (SDP) has been exchanged. After that, the UE can communicate with the calling UE through the network.

[0139] Step 421: The UE communicates with the calling UE through the network side.

[0140] Step 422: The UE sends a PDU session modification request message to the network side for the fourth time.

[0141] Since the PDU session modification request message sent by the UE to request deletion of the QoS rule corresponding to bearer 1 has been rejected by the network side, the UE will continue to resend the PDU session modification request message to the network side during the process of the UE talking to the calling UE through the network side.

[0142] Step 423: The network side sends a PDU session modification command message 4 to the UE. The PDU session modification command message 4 carries the PDU session ID1, QFI1, qos_rules_incl=1, and QoS rule ID1.

[0143] In response to receiving the PDU session modification request message, the network side sends a PDU session modification command message 4 to the UE.

[0144] The PDU session modification command message 4 is used to instruct deletion of the bearer 2 corresponding to the QFI1 and the QoS rule of the bearer 2 (ie, the QoS rule ID1).

[0145] After receiving the fourth PDU session modification request message sent by the UE, since the PDU session ID1 and QoS rule ID1 carried in the PDU session modification request message are the same as the PDU session ID1 and QoS rule ID1 corresponding to bearer 2, the network side may mistakenly believe that the UE requests to delete the QoS rules of bearer 2, and deletes bearer 2 and the QoS rules of bearer 2 stored on the network side according to the PDU session modification request message, and then instructs the UE to delete the QoS rules of bearer 2 stored on the UE side by sending a PDU session modification command message 4 to the UE.

[0146] Step 424: The UE sends a PDU session modification completion message 4 to the network side.

[0147] Since the PDU session modification command message 4 carries qos_rules_incl=1, in response to the PDU session modification command message 4, the UE can delete the QoS rules corresponding to the locally stored PDU session ID1 (i.e., the QoS rules corresponding to bearer 2) and return the PDU session modification completion message 4 to the network side.

[0148] Step 425: The network sends a BYE message to the UE. The BYE message carries abnormality cause information, including insufficient bearer resources.

[0149] The BYE message is used to end a call. Usually, a call starts with an Invite message and ends with a BYE message.

[0150] After bearer 2 is deleted, the call will lose the bearer used to transmit voice call data, causing the call to end due to insufficient bearer resources, that is, causing the call to be abnormally dropped.

[0151] Currently, after the network sends a PDU Session Modify Command message 1 with qos_rules_incl = 1 to the UE, instructing the UE to create Bearer 1 corresponding to the first voice call service, the network may delete the created Bearer 1 by sending a PDU Session Modify Command message 2 with qos_rules_incl = 0 to the UE due to abnormal reasons such as network abnormalities or network element abnormalities. This will cause the UE to be unable to delete the locally stored QoS rules according to PDU Session Modify Command message 2, and will cause it to repeatedly send PDU Session Modify Request messages to the network to request the deletion of local QoS rules. During the process of UE resending the PDU session modification request message, if the UE needs to make a voice call again, the network side will create the corresponding bearer 2 for the second voice call service by sending a PDU session modification command message 3 to the UE. After creating the corresponding bearer 2 for the second voice call service, if the network side receives the PDU session modification request message resent by the UE to request to delete the QoS of bearer 1, since the PDU session ID and QoS rule ID corresponding to bearer 1 and bearer 2 are the same, the network side may mistakenly believe that the UE is requesting to delete the QoS rule of bearer 2 corresponding to the second voice call service, and mistakenly delete bearer 2 corresponding to the second voice call service, resulting in the second voice call service being terminated due to insufficient bearer resources.

[0152] That is, when the network side deletes the bearer of the last voice call service, it may be unable to instruct the UE to delete the bearer configuration information due to an abnormality, causing the UE to repeatedly resend the deletion request to delete the bearer configuration information. The UE's repeated deletion request may affect the UE's next voice call. For example, during the next voice call, the bearer of the voice call service is abnormally deleted, which in turn causes the voice call to be abnormally disconnected.

[0153] As can be seen from Figure 4 above, after the network side sends a create bearer message carrying first indication information to the UE to instruct the UE to create the bearer corresponding to the first data service, when the bearer needs to be deleted, the network side may send an abnormal delete bearer message carrying second indication information to the UE to instruct the UE to delete the created bearer due to abnormal reasons such as network abnormality or network element abnormality (for example, an abnormality occurs in the network element in the core network on the network side). The first indication information is used to indicate that the corresponding bearer has target bearer configuration information, and the second indication information is used to indicate that the corresponding bearer does not have target bearer configuration information. After receiving the create bearer message carrying the first indication information, the UE can store the target bearer configuration information locally. Afterwards, if it receives the abnormal delete bearer message carrying the second indication information, since the second indication information is used to indicate that the corresponding bearer does not have target bearer configuration information, the UE will assume that the bearer to be deleted also does not have target bearer configuration information, and will not delete the locally stored target bearer configuration information after deleting the bearer. Since the UE still has the target bearer configuration information stored locally, the UE will send a deletion request to the network side to delete the target bearer configuration information. However, due to an anomaly, the network may believe that it has instructed the UE to delete the target bearer configuration information through the abnormal bearer deletion message, and therefore reject the UE's deletion request. After being rejected, the UE will continue to resend the deletion request to the network. During this process, if the UE needs to perform a second data service, the network will recreate the bearer corresponding to the second data service for the UE by sending a create bearer message to the UE. Afterwards, if the network receives the deletion request resent by the UE, it may mistakenly delete the bearer corresponding to the second data service in response to the deletion request, causing the second data service to end due to insufficient bearer resources.

[0154] In an embodiment of the present application, in order to reduce the impact of network abnormalities on UE services, an information processing method is proposed. In this method, after the UE receives a first message sent by the network side and carrying first indication information for indicating the creation of a bearer, if a second message is received for indicating the deletion of the created bearer, even if the second message does not carry the first indication information, it is considered that the second message carries the first indication information, and the target bearer configuration information of the created bearer is deleted, such as deleting the locally stored target bearer configuration information of the created bearer.

[0155] For example, after receiving a second message indicating deletion of an established bearer, even if the second message carries the second indication information, the second message is considered to carry the first indication information, and the target bearer configuration information of the established bearer is deleted. Alternatively, even if the second message carries neither the first indication information nor the second indication information, the second message is considered to carry the first indication information, and the target bearer configuration information of the established bearer is deleted.

[0156] In this way, when the network side is unable to instruct the UE to delete the bearer configuration information due to an abnormality, the UE can be prevented from repeatedly resending the deletion request to delete the target bearer configuration information, thereby preventing the network side from mistakenly deleting the bearer of the next data service due to the UE's repeated deletion request, thereby avoiding the impact of the abnormal situation that the network side is unable to instruct the UE to delete the bearer configuration information due to an abnormality on the next data service, ensuring the normal progress of the next data service, reducing the impact of network abnormalities on the UE service, improving the stability and reliability of the service, and thus improving the user experience.

[0157] It can be understood that the second message carrying the second indication information may include: the second message carrying the second indication information but not carrying the first indication message.

[0158] It should be noted that, when the network side is a 5G network, the network side can create a bearer for the UE by establishing a PDU session with the UE. The PDU session may include a QoS flow, which is the finest granularity of QoS distinction in the PDU session, that is, the bearer it creates is a QoS flow. A QoS flow refers to an IP flow that meets a certain QoS. When the network side is a 4G network (such as an LTE network), the network side can create a bearer for the UE by establishing a public data network (PDN) connection with the UE. The PDN connection may include an evolved packet system (EPS) bearer, that is, the bearer it creates is an EPS bearer. The EPS bearer of the PDN connection has a mapping relationship with the QoS flow of the PDU session. When the network standard is switched, the two can be mapped to each other. For example, if the UE switches from a 5G network to a 4G network, the QoS flow of the PDU session can be mapped to the EPS bearer of the PDN connection, and data transmission is based on the mapped EPS bearer. If the UE switches from a 4G network to a 5G network, the EPS bearer of the PDN connection can be mapped to the QoS flow of the PDU session, and data transmission is based on the mapped QoS flow.

[0159] In the embodiments of the present application, the target bearer configuration information may be any configuration information related to the bearer. For example, the target bearer configuration information may include one or more of the following information: QoS rules, EPS bearer context mapping information, and QoS flow descriptions. Of course, the target bearer configuration information may also include other bearer configuration information, which is not limited in the embodiments of the present application.

[0160] Among them, QoS rules are used to indicate the QoS transmission mechanism rules of the corresponding QoS flow. QoS transmission mechanism rules can provide high-quality network services for different types of data transmission through intelligent management. For example, QoS rules can include one or more of priority rules, bandwidth guarantee rules, delay control rules, and packet loss control rules. Priority rules are used to intelligently manage data transmission by setting priority rules based on the importance of different types of data. For example, for video data with high real-time requirements, its priority can be set to high so that it is transmitted first. Bandwidth guarantee rules are used to avoid network overload by limiting the bandwidth usage ratio of each data type and ensure the rational use of network bandwidth. Delay control rules are used to ensure the timeliness of data transmission by managing the delay of data transmission to meet the requirements of some delay-sensitive applications. Packet loss control rules are used to ensure the integrity of data transmission by managing the packet loss of data transmission and avoid data packet loss during network transmission.

[0161] The EPS bearer context mapping information is used to indicate the mapping relationship between the EPS bearer and the QoS flow. The QoS flow description information is used to define the QoS flow corresponding to the corresponding bearer.

[0162] In one example, for the first message indicating the creation of a bearer and the second message indicating the deletion of a bearer, the two messages can indicate whether the corresponding bearer is configured with target bearer configuration information by carrying different indication information (first indication information and second indication information). For example, both the first message and the second message carry a bearer configuration identifier, and the bearer configuration identifier is used to indicate whether the corresponding bearer has target bearer configuration information. The bearer configuration identifier can be pre-configured with different identification values. For example, the identification value of the bearer configuration identifier may include a first identification value and a second identification value, and the first identification value is used to indicate that the corresponding bearer has target bearer configuration information, and the second identification value is used to indicate that the corresponding bearer does not have target bearer configuration information. For example, the first identification value and the second identification value are 1 and 0, respectively. Of course, the first identification value and the second identification value may also be in other forms, which are not limited in the embodiments of the present application.

[0163] In this case, the first indication information refers to the bearer configuration identifier with the first identification value, and the second indication information refers to the bearer configuration identifier with the second identification value. For example, if the first indication information is qos_rules_incl=1, it indicates that the corresponding bearer is configured with QoS rules; if the second indication information is qos_rules_incl=0, it indicates that the corresponding bearer is not configured with QoS rules.

[0164] In another example, these two messages can also indicate whether the corresponding bearer is configured with the target bearer configuration information by whether they carry the first indication information. For example, for these two messages, if the message carries the first indication information, it indicates that the corresponding bearer is configured with the target bearer configuration information. If the message does not carry the first indication information, it indicates that the corresponding bearer is not configured with the target bearer configuration information. The first indication message can be a configuration identifier of the target bearer configuration information, such as a configuration ID or number of the target bearer configuration information. For example, the first indication message can be id=28.

[0165] In addition, the first message and the second message may further include a quality of service classification identifier to indicate the bearer to be created or deleted corresponding to the quality of service classification identifier, that is, the bearer that meets the service type indicated by the quality of service classification identifier. The quality of service classification identifiers corresponding to different network standards are represented differently. For example, the quality of service classification identifier under the LTE network can be represented by QCI (QoS class identifier), and the quality of service classification identifier under the 5G network can be represented by 5QI (5G QoS class identifier). Among them, different quality of service classification identifier values ​​are used to indicate different service types, and service types may include voice calls, video calls, web surfing, etc. For example, QCI=1 and 5QI=1 correspond to voice call services, QCI=2 and 5QI=2 correspond to video call services, etc.

[0166] In the embodiments of the present application, the quality of service classification identifier value carried in the create bearer message and delete bearer message can be any of the available quality of service classification identifier values. That is, the service type corresponding to the quality of service classification identifier can be any service type within the range of service types permitted by the protocol. For example, the QCI value and 5QI can be any value from 1, 2, ..., 9. Of course, 5QI can also be a value greater than 9, which is not limited in the embodiments of the present application.

[0167] In addition, the first message and the second message may also carry a bearer identifier, which is used to indicate the bearer to be created or deleted. The forms of the bearers created under different network standards are different, and the corresponding bearer identifiers are expressed differently. For example, the bearer created under the LTE network may be a QoS flow, and the corresponding bearer identifier may be a QoS flow ID (QoS flow ID, QFI). The bearer created under the 5G network may be an EPS bearer, and the corresponding bearer identifier may be an EPS bearer ID (EPS Bearer ID, EBI).

[0168] In addition, the first message and the second message may also carry an identifier of the target bearer configuration information, such as an ID or number of the target bearer configuration information, etc. Of course, the first message and the second message may also carry other information, which is not limited in the embodiment of the present application.

[0169] As an example, the UE may receive a first message sent by the network side, the first message carrying a service quality classification identifier, a bearer identifier, and first indication information, the first message being used to indicate the creation of a first bearer corresponding to the service quality classification identifier, the bearer identifier being used to identify the first bearer, and the first indication information being used to indicate that the bearer to be created has target bearer configuration information. In response to the first message, a first response message is sent to the network side, the first response message being used to indicate acceptance of the creation of the first bearer. A second message sent by the network side is received, the second message carrying a service quality classification identifier and a bearer identifier, and the second message also carrying the second indication information, or the second message does not carry the first indication information and the second indication information, the second message being used to indicate the deletion of the first bearer corresponding to the service quality classification identifier, and the second indication information being used to indicate that the bearer to be deleted does not have target bearer configuration information. In response to the second message, the target bearer configuration information of the first bearer is deleted.

[0170] In the embodiment of the present application, in response to the second message, deleting the target bearer configuration information of the first bearer may include the following two implementation methods:

[0171] A first implementation manner: in response to the second message, the locally stored target bearer configuration information is deleted, and a second response message is sent to the network side, where the second response message is used to indicate acceptance of deletion of the first bearer.

[0172] That is, after receiving the second message, the UE immediately deletes the locally stored target bearer configuration information and sends a response message to the network side.

[0173] The second implementation method: in response to the second message, send a second response message to the network side; send one or more first deletion requests to the network side, if no first deletion indication information is received for the first deletion request, delete the locally stored bearer configuration information of the first bearer, and the first deletion indication information is used to indicate the target bearer configuration information for deleting the first bearer.

[0174] That is, after receiving the second message, the UE first sends a response message to the network side, and then sends one or more first deletion requests to the network side requesting to delete the target bearer configuration information, in an attempt to negotiate with the network side to delete the target bearer configuration information. In addition, after sending one or more first deletion requests, if the UE does not receive the first deletion indication information for the first deletion request, it can also proactively delete the locally stored bearer configuration information of the first bearer without the consent of the network side, and no longer resend the first deletion request. This can avoid the situation where the UE keeps resending the first deletion request after being rejected by the network side.

[0175] Among them, the first deletion indication information can be a third message, the third message includes a service quality classification identifier, a bearer identifier and the first indication information, and the third message is used to indicate the deletion of the first bearer corresponding to the service quality classification identifier and the target bearer configuration information of the first bearer.

[0176] In an example, the second implementation may include the following two possible implementations:

[0177] 1) By controlling the number of times the UE resends the first deletion request, the UE is prevented from constantly resending the first deletion request.

[0178] For example, after sending a preset number of deletion requests to the network side, if no first deletion indication information for the first deletion request is received, the locally stored bearer configuration information of the first bearer is deleted.

[0179] Among them, the preset number of times can be set in advance according to needs, for example, the preset number of times can be 2 times or 3 times, etc., and the embodiment of the present application does not limit this.

[0180] That is, the UE is only allowed to send a maximum of a preset number of first deletion requests to the network. If the UE does not receive the first deletion indication information for the first deletion request after sending the first deletion request a preset number of times, the UE can proactively delete the locally stored target bearer configuration information without the network's consent. This can avoid the situation where the UE repeatedly sends the first deletion request after being rejected by the network.

[0181] 2) By setting a timer duration for the UE to resend the first deletion request, the UE is prevented from constantly resending the first deletion request.

[0182] Specifically, after receiving the second message, the first timer is started; one or more first deletion requests are sent to the network side within the timing duration of the first timer; if the first deletion indication information for the first deletion request is not received within the timing duration of the first timer, the bearer configuration information of the locally stored first bearer is deleted.

[0183] The timing duration can be set in advance according to needs, for example, it can be set to 5 seconds, 10 seconds or 30 seconds.

[0184] That is, the UE is only allowed to send the first deletion request within the timer duration of the first timer. If the UE does not receive the first deletion indication information in response to the first deletion request within the timer duration, the UE can proactively delete the locally stored target bearer configuration information without the consent of the network side. This can avoid the situation where the UE repeatedly sends the first deletion request after being rejected by the network side.

[0185] It is understandable that starting the first timer after receiving the second message may include any of the following implementations: starting the first timer in response to receiving the second message, that is, starting the first timer immediately after receiving the second message; starting the first timer when sending the second response message to the network side; starting the first timer after sending the second response message to the network side; starting the first timer when sending the first deletion request to the network side for the first time; starting the first timer after sending the first deletion request to the network side for the first time. Of course, the first timer can also be started at other appropriate times after receiving the second message, and this embodiment of the present application is not limited to this.

[0186] It can also be understood that the embodiments of the present application only illustrate the above-mentioned second implementation method by using the above-mentioned two possible implementation methods. Of course, the above-mentioned second implementation method can also be implemented through other possible implementation methods, and the embodiments of the present application do not limit this.

[0187] In one example, not receiving the first deletion indication information from the network side for the first deletion request may include: receiving a deletion rejection message sent by the network side, the deletion rejection message being used to indicate a rejection of deleting the target bearer configuration information of the first bearer; and not receiving the first deletion indication information sent by the network side.

[0188] That is, after receiving the deletion rejection message sent by the network side, the first deletion indication information sent by the network side has not yet been received.

[0189] It should be noted that the message format used by the network to instruct the UE to create or delete a bearer may vary across different network standards. For example, in a 5G network, the network can instruct the UE to create or delete a bearer by sending a PDU Session Modify Command message to the UE. In a 4G network such as an LTE network, the network can instruct the UE to create or delete a bearer by sending an Activate Dedicated EPS Bearer Context Request message or a Deactivate Dedicated EPS Bearer Context Request message, respectively.

[0190] Next, the information processing method provided in the embodiment of the present application will be illustrated with reference to the accompanying drawings, taking the case where the data service is a voice call service and the UE resides in a 5G network and is a called UE as an example.

[0191] FIG5 is a schematic diagram of a paging process provided in an embodiment of the present application. As shown in FIG5 , the paging process includes the following contents:

[0192] Step 501: After receiving the Invite message 1, the IMS sends the Invite message 1 to the 5G core network.

[0193] The Invite message is a commonly used SIP request message used to establish a dialogue for media exchange with a user agent.

[0194] It is understandable that in response to the user operation, the calling UE can initiate a call, and the calling UE can send a call request message (for example, Invite message 1) through the calling-side network (the network where the calling UE is registered). The Invite message 1 can reach the I-CSCF entity in the IMS, and the I-CSCF entity can query the address information of the S-CSCF entity where the user is registered for the UE through the HSS in the IMS, and then route the Invite message 1 to the S-CSCF, which forwards the Invite message 1 through the P-CSCF entity to the 5G core network where the called UE is registered.

[0195] Step 502: The 5G core network sends an Invite message 1 to the UE through the 5G base station.

[0196] The 5G core network determines the 5G base station corresponding to the called UE, sends NVITE message 1 to the 5G base station, and then the 5G base station sends NVITE message 1 to the UE.

[0197] Step 503: The UE sends a 100Trying message to the IMS through the 5G base station and the 5G core network.

[0198] The 100Trying message is a temporary response message used to indicate that the UE on the network side has received the Invite message 1 and the message is being processed.

[0199] The UE sends a 100Trying message to the 5G base station, which then sends it to the 5G core network. The 5G core network then sends it to the IMS. After receiving the 100Trying message, the IMS can forward it to the calling UE.

[0200] In addition, if the UE is in idle state, after receiving NVITE message 1, the UE can first establish a radio resource control (RRC) connection with the 5G base station. After establishing the RRC connection with the 5G base station, the UE sends a 100Trying message to the IMS through the 5G base station and the 5G core network.

[0201] Step 504: The UE sends a 183 message to the IMS through the 5G base station and the 5G core network.

[0202] Among them, the 183 message is used to indicate that the call connection is in progress.

[0203] After receiving the 183 message, the IMS may forward the 183 message to the calling UE, for example, by forwarding the 183 message to the calling UE through a core network and a base station in the calling side network.

[0204] Step 505: The 5G core network sends a PDU session modification command message 1 to the UE through the 5G base station. The PDU session modification command message 1 carries PDU session ID1, 5QI=1, QFI1, qos_rules_incl=1, QoS rule ID1 and corresponding QoS rules.

[0205] PDU session ID 1 is used to identify the session corresponding to bearer 1 to be created. 5QI = 1 corresponds to voice call service. QFI1 is used to identify bearer 1 to be created, specifically the QoS flow corresponding to bearer 1 to be created. qos_rules_incl = 1 indicates that QoS rules are configured for bearer 1 to be created. QoS rule ID 1 includes one or more QoS rule IDs, each of which identifies a QoS rule configured for bearer 1.

[0206] The PDU session modification command message 1 is used to instruct the creation of a bearer 1 with 5QI=1, and the created bearer 1 with 5QI=1 is configured with a QoS rule.

[0207] For example, the SMF in the 5G core network establishes a PDU session modification command message 1, sends the PDU session modification command message 1 to the AMF in the 5G core network, and the AMF sends the PDU session modification command message 1 to the called UE through the 5G base station.

[0208] Step 506: The UE sends a PDU session modification completion message 1 to the 5G core network through the 5G base station.

[0209] The PDU session modification complete message 1 is a response message to the PDU session modification command message 1, used to indicate the acceptance of the creation of bearer 1 with 5QI=1. In response to receiving the PDU session modification complete message 1, the UE can first store the QoS rules, such as storing the PDU session ID 1, 5QI=1, QFI1, QoS rule ID 1 and the corresponding QoS rules, and then send the PDU session modification complete message 1 to the 5G base station, which is then forwarded by the 5G base station to the 5G core network. For example, the PDU session modification complete message 1 is sent to the AMF in the 5G core network, and then forwarded by the AMF to the SMF.

[0210] Step 507: The 5G core network cancels the call process with the UE through the 5G base station.

[0211] Before a call is successfully established, the network may cancel the call due to an exception. For example, the 5G core network may send a CANCEL message to the UE via the 5G base station to cancel the call. The CANCEL message is used to close a session that has not received a final response.

[0212] Step 508: The 5G core network sends a PDU session modification command message 2 to the UE through the 5G base station. The PDU session modification command message 2 carries PDU session ID1, QFI1 and qos_rules_incl=0.

[0213] Among them, PDU session modification command message 2 is used to indicate the deletion of bearer 1 corresponding to QFI1, and qos_rules_incl = 0 is used to indicate that no QoS rules are configured for bearer 1 to be deleted. The 5G core network may experience abnormal conditions such as network abnormalities or network element abnormalities. In such abnormal conditions, the PDU session modification command message 2 sent by the 5G core network to the UE may carry qos_rules_incl = 0 instead of qos_rules_incl = 1.

[0214] For example, the SMF in the 5G core network establishes a PDU session modification command message 2, sends the PDU session modification command message 2 to the AMF in the 5G core network, and the AMF sends the PDU session modification command message 2 to the called UE through the 5G base station.

[0215] In an embodiment of the present application, in order to solve the problem that when the network side deletes the bearer of a data service, it is unable to instruct the UE to delete the bearer configuration information due to an exception, which affects the UE's next data service, such as causing the UE's next voice call service to be abnormally dropped, after receiving the PDU session modification command message 2 for deleting the bearer carrying qos_rules_incl=0, it is also considered that qos_rules_incl=1, and the locally stored QoS rules are deleted to avoid the situation where the UE keeps resending the PDU session modification request to delete the QoS rules.

[0216] After receiving the PDU session modification command message 2, the UE may immediately delete the locally stored QoS rules of bearer 1. In addition, after receiving the PDU session modification command message 2, the UE may also first send a PDU session modification request message to the network side. After sending one or more PDU session modification request messages, if no first deletion response to the PDU session modification request message is received, the locally stored QoS rules of bearer 1 are deleted.

[0217] In the embodiments of the present application, any one of the following three implementation methods (method 1, method 2, and method 3) will be used as an example to illustrate how to solve the above problem.

[0218] Method 1:

[0219] Step 509: The UE deletes the locally stored QoS rule of bearer 1.

[0220] Step 510: The UE sends a PDU session modification completion message 2 to the 5G core network through the 5G base station.

[0221] Among them, the PDU session modification completion message 2 is a response message to the PDU session modification command message 2, used to indicate acceptance of deletion of bearer 1.

[0222] That is, after receiving the PDU session modification command message 2, the UE can immediately delete the locally stored QoS rule of the bearer 1 and return a PDU session modification completion message to the network side.

[0223] For example, the UE sends a PDU session modification complete message 2 to the 5G base station, which is then forwarded by the 5G base station to the 5G core network. For example, the PDU session modification complete message 2 is sent to the AMF in the 5G core network, which is then forwarded by the AMF to the SMF.

[0224] Method 2:

[0225] Step 511: The UE sends a PDU session modification completion message 2 to the 5G core network through the 5G base station.

[0226] Step 512: The UE sends a PDU session modification request message to the 5G core network through the 5G base station for the first time. The PDU session modification request message carries PDU session ID1 and QoS rule ID1.

[0227] The PDU session modification request message is used to request deletion of the QoS rule corresponding to QoS rule ID1, that is, the QoS rule of bearer 1.

[0228] That is, after receiving the PDU session modification command message 2, the UE first sends the PDU session modification completion message 2 to the network side, and sends the first PDU session modification request message to the network side. By sending the PDU session modification request message, it tries to negotiate with the network side to delete the QoS rules of bearer 1.

[0229] For example, a PDU session modification request message is sent to the AMF in the 5G core network, and then forwarded by the AMF to the SMF.

[0230] Step 513: The 5G core network sends a PDU session modification reject message to the UE through the 5G base station. The PDU session modification reject message carries a rejection reason value = 31.

[0231] The PDU Session Modification Reject message is used to indicate the rejection of the UE's PDU Session Modification request. The rejection reason value 31 ("cause=31") is used to indicate an ambiguous reason. Due to an anomaly, the network may believe that the UE has been instructed to delete the QoS rule for Bearer 1 via PDU Session Modification Command Message 2 and reject the UE's PDU Session Modification request.

[0232] For example, the SMF in the 5G core network sends a PDU session modification reject message to the UE through the AMF.

[0233] Step 514: The UE sends a PDU session modification request message to the 5G core network through the 5G base station for the second time.

[0234] After being rejected by the network side, the UE can resend the PDU session modification request message to the 5G core network.

[0235] Step 515: The 5G core network sends a PDU session modification reject message to the UE through the 5G base station.

[0236] Step 516: The UE deletes the locally stored QoS rule of bearer 1.

[0237] In an embodiment of the present application, after sending a preset number of (i.e., 2) PDU session modification request messages to the network side, if no first deletion indication information for the PDU session modification rejection message is received, such as no PDU session modification command message 3 from the 5G core network, the locally stored QoS rules of bearer 1 are deleted. PDU session modification command message 3 carries ID1, 5QI=1, QFI1, qos_rules_incl=1, QoS rule 1, and the corresponding QoS rule, and is used to indicate the deletion of bearer 1 with 5QI=1.

[0238] It should be noted that the above-mentioned method 2 is only illustrated by taking the preset number of times as 2 times, and in other embodiments, the preset number of times can also be set to other values, and the embodiments of the present application do not limit this.

[0239] Method 3:

[0240] Step 517: The UE sends a PDU session modification completion message 2 to the 5G core network through the 5G base station.

[0241] Step 518: After sending the PDU session modification completion message 2, the UE starts timer 1, and timer 1 begins timing.

[0242] Step 519: The UE sends a PDU session modification request message to the 5G core network through the 5G base station for the first time. The PDU session modification request message carries PDU session ID1 and QoS rule ID1.

[0243] Step 520: The 5G core network sends a PDU session modification reject message to the UE through the 5G base station. The PDU session modification reject message carries a rejection reason value = 31.

[0244] Step 521: If the timing duration of timer 1 reaches the timing duration of timer 1, the UE deletes the QoS rule of bearer 1 stored locally.

[0245] It should be noted that the embodiment of the present application is only illustrated by taking the example of the UE starting timer 1 after sending the PDU session modification completion message 2 to the network side. It should be understood that the UE can also start timer 1 at other times after receiving the PDU session modification command message 2, such as starting timer 1 after step 508 and before step 517, or starting timer 1 after step 519. The embodiment of the present application does not limit this.

[0246] Step 522: After receiving Invite message 2, the IMS sends Invite message 2 to the 5G core network.

[0247] After the UE deletes the locally stored QoS rule for bearer 1 with 5QI=1, the called UE may receive an incoming call again, i.e., be called again. In this case, the IMS can receive the Invite message 2 sent by the calling UE through the calling side network. After receiving the Invite message 2, the IMS can send the Invite message 2 to the 5G core network.

[0248] It should be noted that the calling UEs of the first voice call service and the second voice call service may be the same UE or different UEs, and this embodiment of the present application does not limit this.

[0249] Step 523: The 5G core network sends an Invite message 2 to the UE through the 5G base station.

[0250] Step 524: The UE sends a 100Trying message to the IMS through the 5G base station and the 5G core network.

[0251] In addition, after the UE receives the NVITE message 2, if the UE is in the idle state, the UE can also first establish an RRC connection with the 5G base station. After establishing the RRC connection with the 5G base station, the 100Trying message is sent to the IMS through the 5G base station and the 5G core network. After receiving the 100Trying message, the IMS can forward the 100Trying message to the calling UE, for example, through the core network and base station in the calling side network to forward the 100Trying message to the calling UE.

[0252] Step 525: The UE sends a 183 message to the IMS through the 5G base station and the 5G core network.

[0253] After receiving the 183 message, the IMS may forward the 183 message to the calling UE, for example, by forwarding the 183 message to the calling UE through a core network and a base station in the calling side network.

[0254] Step 526: The 5G core network sends a PDU session modification command message 4 to the UE through the 5G base station. The PDU session modification command message 4 carries PDU session ID1, 5QI=1, QFI1, qos_rules_incl=1, QoS rule ID1 and corresponding QoS rules.

[0255] Among them, the PDU session modification command message 4 is used to instruct the creation of bearer 2 with 5QI=1, that is, bearer 2 used to carry the voice call data of the second voice call service. PDU session ID1 is used to identify the session corresponding to bearer 2 to be created. 5QI=1 corresponds to the voice call service. QFI1 is used to identify bearer 2 to be created, specifically to identify the QoS flow corresponding to bearer 2 to be created. qos_rules_incl=1 indicates that bearer 2 to be created is configured with QoS rules. QoS rule ID1 includes one or more QoS rule IDs, each QoS rule ID is used to identify a QoS rule configured for bearer 2.

[0256] For example, the SMF in the 5G core network establishes a PDU session modification command message 4, sends the PDU session modification command message 4 to the AMF in the 5G core network, and the AMF sends the PDU session modification command message 4 to the called UE through the 5G base station.

[0257] Step 527: The UE sends a PDU session modification completion message 3 to the 5G core network through the 5G base station.

[0258] The PDU session modification complete message 3 is a response message to the PDU session modification command message 4, indicating acceptance of the creation of bearer 2. In response to receiving the PDU session modification complete message 4, the UE may first store the QoS rules of bearer 2, such as PDU session ID1, QFI1, QoS rule ID1, and the corresponding QoS rules, and then send the PDU session modification complete message 3 to the 5G base station, which is then forwarded by the 5G base station to the 5G core network. For example, the PDU session modification complete message 3 is sent to the AMF in the 5G core network, which is then forwarded by the AMF to the SMF.

[0259] Step 528: After receiving the update message, the IMS sends the update message to the UE through the 5G core network and the 5G base station.

[0260] The UPDATE message is used to instruct execution of resource reservation, and the UPDATE message may carry resource reservation status.

[0261] The calling UE can send an UPDATE message to the called UE through the calling side network. After the UPDATE message reaches the IMS, the IMS can send the UPDATE message to the 5G core network, and then the 5G core network sends it to the called UE through the 5G base station.

[0262] Step 529: The UE sends a 180Ringing message to the IMS through the 5G base station and the 5G core network.

[0263] 180Ringing is used to indicate that the called UE is ringing, indicating that the Invite message 2 has been sent to the called UE and the called UE is ringing.

[0264] After receiving the UPDATE message, the UE can ring and send a 180Ringing message to the IMS through the 5G base station and 5G core network. After receiving the 180Ringing message, the IMS can forward the 180Ringing message to the calling UE, for example, through the core network and base station in the calling side network.

[0265] Step 530: The UE sends a 200OK message to the IMS through the 5G base station and the 5G core network.

[0266] The 200OK message is the final response to the Invite message 2, indicating that the SDP content has been exchanged. After that, the UE can communicate with the calling UE through the network side, that is, through the 5G base station, 5G core network, and IMS.

[0267] It should be noted that the embodiment of the present application is only explained by taking the example of the network side sending an abnormal PDU session modification command message 2 to the UE after the call is canceled due to an abnormality before the first voice call service is successfully established. It should be understood that the network side can also send an abnormal PDU session modification command message 2 to the UE after the first voice call service successfully establishes the call and ends the call according to the user's end call operation. The embodiment of the present application does not limit the scenario in which the network side sends an abnormal PDU session modification command message 2 to the UE.

[0268] It is understandable that the embodiment of the present application is only illustrated by taking the case where the UE is the called party as an example. In the case where the UE is the calling UE, the network side may also send an abnormal PDU session modification command message 2 to the UE. In this process, the information processing method provided in the example of the present application can also be used to solve the above problem. For example, the above steps 501-504 can also be replaced with the following steps: the UE sends an Invite message 1 to the IMS through the 5G base station and the 5G core network. After the IMS receives the 100Trying message, it sends a 100Trying message to the UE through the 5G core network and the 5G base station. Accordingly, the above steps 522-530 can also be replaced with the following steps: the UE sends an Invite message 2 to the IMS through the 5G base station and the 5G core network. After the IMS receives the 100Trying message, it sends a 100Trying message to the UE through the 5G core network and the 5G base station. After the IMS receives the 183 message, it sends the 183 message to the UE through the 5G core network and the 5G base station. The 5G core network sends a PDU session modification command message 4 to the UE through the 5G base station. The UE sends a PDU Session Modification Complete message 3 to the 5G core network via the 5G base station. The UE sends an UPDATE message to the IMS via the 5G base station and the 5G core network. After receiving the 180Ringing message, the IMS sends a 180Ringing message to the UE via the 5G core network and the 5G base station. After receiving the 200OK message, the IMS sends a 200OK message to the UE via the 5G core network and the 5G base station. After receiving the 200OK message, the UE can communicate with the called UE through the network side, that is, through the 5G base station, the 5G core network, and the IMS.

[0269] In an embodiment of the present application, after the UE receives a PDU session modification command message 1 sent by the network side and carrying qos_rules_incl=1 to indicate the creation of a bearer, if it receives a PDU session modification command message 2 to indicate the deletion of the bearer, even if the PDU session modification command message 2 carries qos_rules_incl=0, the UE also considers that qos_rules_incl=1 and deletes the locally stored QoS rules. In this way, when the network side is unable to instruct the UE to delete the QoS rules due to an abnormality, it can avoid the situation where the UE repeatedly resends the PDU session modification request message requesting the deletion of the QoS rules, thereby avoiding the problem that the network side mistakenly deletes the bearer of the next voice call service due to the retransmission of the PDU session modification request message by the UE, causing the next voice call service to be abnormally dropped. In this way, the normal operation of the next voice call service can be guaranteed, the impact of network abnormalities on the UE service can be reduced, the stability and reliability of the voice call service can be improved, and the user experience can be improved.

[0270] It should be noted that under different network standards, the message format of the network side instructing the UE to create and delete a bearer may be different. Next, the information processing method provided in the embodiment of the present application will be illustrated with reference to the accompanying drawings, taking the data service as a voice call service, the UE residing on a 4G network such as an LTE network, and being a calling UE as an example.

[0271] FIG6 is a schematic diagram of another paging process provided in an embodiment of the present application. As shown in FIG6 , the paging process includes the following contents:

[0272] Step 601: After receiving the Invite message 1, the IMS sends the Invite message 1 to the 4G core network.

[0273] Step 602: The 4G core network sends an Invite message 1 to the UE through the 4G base station.

[0274] Step 603: The UE sends a 100Trying message to the IMS via the 4G base station and the 4G core network.

[0275] Step 604: The UE sends a 183 message to the IMS via the 4G base station and the 4G core network.

[0276] Among them, the implementation method of steps 601 to 604 is the same as that of steps 501 to 504 in the embodiment of Figure 5 above, and will not be repeated here in this embodiment of the present application.

[0277] Step 605: The 4G core network sends an active dedicated EPS bearer context request message 1 to the UE through the 4G base station. The active dedicated EPS bearer context request message 1 carries QCI=1, EBI1, id=28, QoS rule ID1 and corresponding QoS rule.

[0278] Activate Dedicated EPS Bearer Context Request Message 1 indicates the creation of EPS Bearer 1 with QCI = 1, i.e., EPS Bearer 1 used to carry voice call service data. EBI1 identifies EPS Bearer 1. id = 28 indicates that QoS rules are configured for EPS Bearer 1. QoS Rule ID 1 can include one or more QoS Rule IDs, each of which identifies a QoS rule configured for EPS Bearer 1.

[0279] The MME in the 4G core network may create an activation dedicated EPS bearer context request message 1 and send the dedicated EPS bearer context request message 1 to the 4G base station through the SGW and the PGW, so as to be sent to the UE through the 4G base station.

[0280] Step 606: The UE sends an active dedicated EPS bearer context accept message 1 to the 4G core network via the 4G base station.

[0281] The Activate Dedicated EPS Bearer Context Accept message 1 is a response message to the Activate Dedicated EPS Bearer Context Request message 1, indicating acceptance of the creation of EPS Bearer 1. The UE can send the EPS Bearer Context Request message 1 to the 4G core network via a 4G base station. The EPS Bearer Context Accept message 1 can reach the PGW of the 4G core network, which forwards the EPS Bearer Context Accept message 1 to the SGW, which then sends it to the MME.

[0282] Step 607: The 4G core network cancels the call process with the UE through the 4G base station.

[0283] Step 608: The 4G core network sends a deactivate dedicated EPS bearer context request message 1 to the UE through the 4G base station. The deactivate dedicated EPS bearer context request message 1 carries QCI=1 and EBI1.

[0284] The dedicated EPS bearer context deactivation request message 1 is used to instruct deletion of EPS bearer 1. Furthermore, the dedicated EPS bearer context deactivation request message 1 does not carry id=28, which may indicate that no QoS rule is configured for EPS bearer 1. Furthermore, the dedicated EPS bearer context deactivation request message 1 may not carry QCI=1, which is not limited in this embodiment of the present application.

[0285] For example, the MME in the 4G core network establishes a deactivation dedicated EPS bearer context request message 1, sends the deactivation dedicated EPS bearer context request message 1 to the SGW in the 5G core network, and then the SGW sends it to the 5G base station through the PGW, and then sends it to the called UE through the 5G base station.

[0286] Under normal circumstances, the dedicated EPS bearer context activation request message 1 carries ID = 28 and the corresponding QoS rule ID 1. The corresponding dedicated EPS bearer context deactivation request message 1 should also carry ID = 28 and the corresponding QoS rule ID 1. However, the 4G core network may experience abnormalities such as network anomalies or network element abnormalities. In such abnormalities, the dedicated EPS bearer context deactivation request message 1 sent by the 4G core network to the UE may not carry ID = 28 and the corresponding QoS rule ID 1.

[0287] In an embodiment of the present application, in order to solve the problem that when the network side deletes the bearer of a data service, it is unable to instruct the UE to delete the bearer configuration information due to an abnormality, which affects the UE's next data service, such as causing the UE's next voice call service to be abnormally dropped, after the UE receives the dedicated EPS bearer context deactivation request message 1 that does not carry id=28 and the corresponding QoS rule ID1 for indicating the deletion of the bearer, it is also considered that the dedicated EPS bearer context deactivation request message 1 carries id=28 and the corresponding QoS rule ID1, and deletes the locally stored QoS rules of the EPS bearer 1, so as to avoid the situation where the UE keeps resending the deletion request for deleting the QoS rule.

[0288] After receiving the Deactivate Dedicated EPS Bearer Context Request message 1, the UE may immediately delete the locally stored QoS rules of EPS Bearer 1. In addition, after receiving the Activate Dedicated EPS Bearer Context Request message 1, the UE may first send a Bearer Resource Modification Request message to the network to request deletion of the QoS rules of EPS Bearer 1. After sending one or more Bearer Resource Modification Request messages, if no first Delete Response to the PDU Session Modification Request message is received, the UE deletes the locally stored QoS rules of EPS Bearer 1.

[0289] In the embodiments of the present application, the following three implementation methods (method 1, method 2, and method 3) are used as examples to illustrate how to solve the above problems.

[0290] Method 1:

[0291] Step 609: The UE deletes the locally stored QoS rule of EPS bearer 1.

[0292] Step 610: The UE sends a deactivate dedicated EPS bearer context accept message 1 to the 4G core network via the 4G base station.

[0293] The dedicated EPS bearer context deactivation accept message 1 is a response message to the dedicated EPS bearer context deactivation request message 1, and is used to indicate acceptance of deletion of EPS bearer 1. The dedicated EPS bearer context deactivation accept message 1 may be established and sent by an MME in the 4G core network. The sending path of the dedicated EPS bearer context deactivation accept message 1 is the same as the sending path of the dedicated EPS bearer context activation accept message 1, and is not further described in detail in the embodiments of the present application.

[0294] That is, after receiving the dedicated EPS bearer context deactivation request message 1, the UE immediately deletes the locally stored QoS rule of the EPS bearer 1 and returns a dedicated EPS bearer context deactivation accept message to the network side.

[0295] Method 2:

[0296] Step 611: The UE sends a deactivation dedicated EPS bearer context accept message 1 to the 4G core network through the 4G base station.

[0297] Step 612: The UE sends a bearer resource modification request message to the 4G core network through the 4G base station for the first time. The bearer resource modification request message carries EBI1 and QoS rule ID1.

[0298] The bearer resource modification request message is used to request deletion of the QoS rule of EPS bearer 1. In addition, the bearer resource modification request message may also carry QCI=1, which is not limited in the embodiment of the present application.

[0299] Step 613: The 4G core network sends a bearer resource modification reject message to the UE through the 4G base station.

[0300] The bearer resource modification reject message is a rejection response to the bearer resource modification request message, and is used to indicate that deletion of the QoS rule of EPS bearer 1 is rejected.

[0301] In addition, the bearer resource modification reject message may also carry reject reason indication information, which is used to indicate an unclear reason. For example, the reject reason indication information may be a reject reason value, which is used to indicate an unclear reason, such as reject reason value=31.

[0302] Step 614: The UE sends a modify EPS bearer context request message to the 4G core network through the 4G base station for the second time.

[0303] Step 615: The 4G core network sends a bearer resource modification rejection message to the UE through the 4G base station.

[0304] Step 616: The UE deletes the locally stored QoS rule of EPS bearer 1.

[0305] It should be noted that after sending a preset number of bearer resource modification request messages to the network side (i.e., 2 times), if no first deletion indication information for the bearer resource modification request is received, such as no deactivation dedicated EPS bearer context request message 2 is received from the 4G core network, the locally stored QoS rules of EPS bearer 1 may be deleted. Deactivation dedicated EPS bearer context request message 2 carries QCI=1, EBI1, id=28, and the corresponding QoS rule ID 1. Deactivation dedicated EPS bearer context request message 2 is used to indicate the deletion of EPS bearer 1 and the QoS rules of EPS bearer 1.

[0306] It can be understood that the above-mentioned method 2 is the same as the method 2 in the embodiment of Figure 5. The specific implementation principle can refer to the relevant description of method 2 in the embodiment of Figure 5, and the embodiment of this application will not be repeated here.

[0307] Method 3:

[0308] Step 617: The UE sends a deactivation dedicated EPS bearer context accept message 1 to the 4G core network through the 4G base station.

[0309] Step 618: The UE starts timer 2, and timer 2 begins timing.

[0310] Step 619: The UE sends a bearer resource modification request to the 4G core network through the 4G base station for the first time. The bearer resource modification request message carries EBI1, id=28, and QoS rule ID1.

[0311] Step 620: The 4G core network sends a bearer resource modification rejection message to the UE through the 4G base station.

[0312] Step 621: If the timing duration of timer 2 reaches the timing duration of timer 2, the UE deletes the locally stored QoS rule of EPS bearer 1.

[0313] It should be noted that the embodiment of the present application is only illustrated by taking the example of the UE starting timer 2 after sending a deactivation dedicated EPS bearer context acceptance message to the network side. It should be understood that the UE can also start timer 2 at other times after receiving the deactivation dedicated EPS bearer context request message 1, such as starting timer 2 after step 608 and before step 617, or starting timer 2 after step 619. The embodiment of the present application is not limited to this.

[0314] It can be understood that the above-mentioned method 3 is the same as the method 3 in the embodiment of Figure 5. The specific implementation principle can refer to the relevant description of method 3 in the embodiment of Figure 5, and the embodiment of this application will not be repeated here.

[0315] Step 622: After receiving the Invite message 2, the IMS sends the Invite message 2 to the 4G core network.

[0316] Step 623: The 4G core network sends an Invite message 2 to the UE through the 4G base station.

[0317] Step 624: The UE sends a 100Trying message to the IMS via the 4G base station and the 4G core network.

[0318] Step 625: The UE sends a 183 message to the IMS via the 4G base station and the 4G core network.

[0319] Step 626: The 4G core network sends a dedicated EPS bearer context activation request message 2 to the UE through the 4G base station. The dedicated EPS bearer context activation request message 2 carries QCI=1, EBI1, id=28, QoS rule ID1 and corresponding QoS rules.

[0320] Activate Dedicated EPS Bearer Context Request Message 2 indicates the creation of EPS Bearer 2 with QCI = 1, i.e., EPS Bearer 2 used to carry the second voice call service data. EBI1 identifies EPS Bearer 2. id = 28 indicates that QoS rules are configured for EPS Bearer 2. QoS Rule ID 1 can include one or more QoS Rule IDs, each of which identifies a QoS rule configured for EPS Bearer 2.

[0321] Step 627: The UE sends an activation dedicated EPS bearer context accept message 2 to the 4G core network through the 4G base station.

[0322] The dedicated EPS bearer context activation accept message 2 is a response message to the dedicated EPS bearer context activation request message 2 , and is used to indicate acceptance of the creation of the EPS bearer 2 .

[0323] Step 628: After receiving the UPDATE message, the IMS sends the UPDATE message to the UE through the 4G core network and the 4G base station.

[0324] Step 629: The UE sends a 180 Ringing message to the IMS via the 4G base station and the 4G core network.

[0325] Step 630: The UE sends a 200 OK message to the IMS via the 4G base station and the 4G core network.

[0326] After that, the UE can talk to the calling UE through the network side, that is, through the 4G base station, 4G core network and IMS.

[0327] It can be understood that the embodiment of the present application is only illustrated by taking the case where the UE is the called party as an example. In the case where the UE is the calling UE, the network side may send an abnormal deactivation dedicated EPS bearer context request message 1 to the UE. In this process, the information processing method provided in the example of the present application can also be used to solve the above problem. For example, the above steps 601-604 can also be replaced by the following steps: the UE sends an Invite message 1 to the IMS through the 4G base station and the 4G core network. After the IMS receives the 100Trying message, it sends a 100Trying message to the UE through the 4G core network and the 4G base station. Correspondingly, the above steps 622-630 can also be replaced by the following steps: the UE sends an Invite message 2 to the IMS through the 4G base station and the 4G core network. After the IMS receives the 100Trying message, it sends a 100Trying message to the UE through the 4G core network and the 4G base station. After the IMS receives the 183 message, it sends the 183 message to the UE through the 4G core network and the 4G base station. The 4G core network sends a PDU Session Modification Command message 4 to the UE via the 4G base station. The UE sends a PDU Session Modification Complete message 3 to the 4G core network via the 4G base station. The UE sends an UPDATE message to the IMS via the 4G base station and the 4G core network. After receiving the 180Ringing message, the IMS sends a 180Ringing message to the UE via the 4G core network and the 4G base station. After receiving the 200OK message, the IMS sends a 200OK message to the UE via the 4G core network and the 4G base station. After receiving the 200OK message, the UE can communicate with the called UE through the network side, that is, through the 4G base station, the 4G core network, and the IMS.

[0328] In addition, an operating system runs on the terminal devices, such as the terminal device shown in FIG3 , such as the iOS operating system developed by Apple, the Android open source operating system developed by Google, and the Windows operating system developed by Microsoft.

[0329] The operating system of the terminal device can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present application takes the Android system with a layered architecture as an example to illustrate the hardware and software structure of the terminal device. It should be noted that although the embodiment of the present application is described using the Android system as an example, its basic principles are also applicable to terminal devices based on operating systems such as iOS or Windows.

[0330] Figure 7 is a block diagram of the software structure of a terminal device provided in an embodiment of the present application. The software structure adopts a layered architecture, which divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. Taking the Android system, the Android system running on the AP as an example, in some embodiments, the Android system is divided into five layers, from top to bottom, namely the application layer, the application framework layer (Framework), the Android runtime (Android runtime) and the system library, the hardware abstraction layer (HAL) and the system kernel layer (Kernel).

[0331] The application layer can include a series of application packages. Application packages may include apps such as camera, gallery, calendar, call, map, WLAN, Bluetooth, music, video, and short message. The application layer may also include system UI (system UI), which is used to display the terminal device interface, such as displaying the signal icon corresponding to the SIM card and the call interface. The application framework layer provides the application programming interface (API) and programming framework for the applications in the application layer. The application framework layer includes some predefined functions. For example, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc. The phone manager is used to provide call functions for the terminal device, such as call status management (including connecting and hanging up). The application framework layer may also include RIL (Radio Interface Layer), and the modem processor (modem) can exchange information with the telephony through the RIL.

[0332] The modem may include a NAS (Non-Access Stratum) layer, an RRC (Radio Resource Control) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. Each of the aforementioned layers may be a software module. The modem may interact with a base station via an antenna. The methods provided in the embodiments of the present application may be implemented by a modem.

[0333] In addition, some embodiments of the present application provide a terminal device, which includes: one or more processors and a memory; the memory is used to store computer program code, and the computer program code includes computer instructions. When one or more processors execute the computer instructions, the terminal device executes the above-mentioned information processing method.

[0334] Some embodiments of the present application provide a chip system for use in a terminal device. The chip system includes at least one processor and an interface, wherein the interface is configured to receive instructions and transmit them to the at least one processor; the at least one processor executes the instructions, causing the terminal device to execute the paging message processing method described above. The chip system may be a modem, or a system on chip (SoC) including a modem, and the method described above may be implemented by a modem.

[0335] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center via a wired (such as a coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access, or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0336] The above are optional embodiments provided for this application and are not intended to limit this application. Any modifications, equivalent replacements, improvements, etc. made within the technical scope disclosed in this application should be included in the scope of protection of this application.

Claims

1. An information processing method, characterized in that: Applied in a terminal device, the method comprises: receiving a first message sent by a network side, the first message carrying a service quality classification identifier, a bearer identifier, and first indication information, the first message being used to indicate creation of a first bearer corresponding to the service quality classification identifier, the bearer identifier being used to identify the first bearer, and the first indication information being used to indicate that the bearer to be created has target bearer configuration information; In response to the first message, sending a first response message to the network side, where the first response message is used to indicate acceptance of establishing the first bearer; receiving a second message sent by the network side, the second message carrying the quality of service classification identifier and the bearer identifier, and the second message also carrying second indication information, or the second message does not carry the first indication information and the second indication information, the second message is used to indicate deletion of the first bearer corresponding to the quality of service classification identifier, and the second indication information is used to indicate that the bearer to be deleted does not have the target bearer configuration information; In response to the second message, the target bearer configuration information of the first bearer is deleted.

2. The method according to claim 1, characterized in that The deleting the bearer configuration information of the first bearer in response to the second message includes: In response to the second message, the locally stored target bearer configuration information of the first bearer is deleted, and a second response message is sent to the network side, where the second response message is used to indicate acceptance of deletion of the first bearer.

3. The method according to claim 1, characterized in that The deleting the bearer configuration information of the first bearer in response to the second message includes: In response to the second message, sending a second response message to the network side, where the second response message is used to indicate acceptance of deleting the first bearer; After sending one or more first deletion requests to the network side, if no first deletion indication information is received for the first deletion request, the target bearer configuration information of the first bearer stored locally is deleted, and the first deletion indication information is used to indicate the deletion of the target bearer configuration information of the first bearer.

4. The method according to claim 3, characterized in that The sending the first deletion request to the network side once or multiple times includes sending a preset number of first deletion request messages to the network side.

5. The method according to claim 3, characterized in that The method further comprises: After receiving the second message, starting a first timer; The sending one or more first deletion requests to the network side includes: Sending the first deletion request to the network side once or multiple times within the timing duration of the first timer; The first deletion indication information for the first deletion request is not received, including: If the first deletion indication information for the first deletion request is not received within the timing duration of the first timer, the locally stored target bearer configuration information of the first bearer is deleted.

6. The method according to any one of claims 3 to 5, characterized in that: The first deletion indication information that the first deletion request is not received includes: A deletion rejection message is received from the network side, wherein the deletion rejection message is used to indicate a rejection of deleting the the target bearer configuration information of the first bearer; The first deletion indication information sent by the network side in response to the first deletion request is not received.

7. The method according to any one of claims 1 to 6, characterized in that: In the case where the terminal device resides in a fifth generation 5G network, the service quality classification identifier is a service quality classification identifier 5QI of the 5G network, the first message and the second message are protocol data unit PDU session modification command messages, and the first response message is a PDU session modification completion message; In the case where the terminal device resides in a Long Term Evolution LTE network, the service quality classification identifier is the service quality classification identifier QCI of the LTE network, the first message is an activation dedicated evolved packet system EPS bearer context request message, the first response message is an activation dedicated EPS bearer context acceptance message, and the second message is a deactivation dedicated EPS bearer context request message.

8. The method according to any one of claims 3 to 5, characterized in that: In the case where the terminal device resides in a 5G network, the second response message is a PDU session modification completion message, and the first deletion request is a PDU session modification request message; In the case where the terminal device resides in an LTE network, the second response message is a deactivation dedicated EPS bearer context acceptance message, and the first deletion request is a modification EPS bearer context request message.

9. The method according to claim 8, characterized in that In the case where the terminal device resides in a 5G network, the first message and the second message also include a PDU session identifier, the PDU session modification request message includes the PDU session identifier, and the PDU session identifier is used to identify the session corresponding to the first bearer.

10. The method according to claim 6, characterized in that In the case where the terminal device resides in a 5G network, the deletion rejection message is a PDU session modification rejection message, and the first deletion indication information is a PDU session modification command message; In the case where the terminal device resides in an LTE network, the deletion rejection message is a bearer resource modification rejection message, and the first deletion indication information is a deactivation dedicated EPS bearer context request message.

11. The method according to any one of claims 1 to 10, characterized in that: The target bearer configuration information includes one or more of the following information: quality of service QoS rules, EPS bearer context mapping information and QoS flow description information.

12. The method according to any one of claims 1 to 11, characterized in that: The first indication information is a bearer configuration identifier whose identification value is a first identification value, and the second indication information is a bearer configuration identifier whose identification value is a second identification value. The bearer configuration identifier is used to indicate whether the target bearer configuration information exists in the corresponding bearer.

13. The method according to any one of claims 1 to 12, characterized in that: The service type indicated by the service quality classification identifier is a voice call service or a video call service, and before receiving the first message sent by the network side, the method further includes any one of the following methods: Sending a first invitation Invite message to the network side; receiving a first temporary response message sent by the network side; receiving a first session in progress message sent by the network side, wherein the first session in progress message is used to indicate that a call connection is in progress; Receive a second Invite message sent by the network side; send a second temporary response message to the network side in response to the second Invite message; and send a second session in progress message to the network side.

14. A terminal device, characterized in that: The terminal device comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the method according to any one of claims 1 to 13 when executed by the processor.

15. A chip system, characterized in that: The chip system includes one or more interface circuits and one or more processors; the interface circuits and the processors are interconnected via lines; The chip system is applied to a terminal device including a communication module and a memory; the interface circuit is used to receive a signal from the memory and send the signal to the processor, the signal including computer instructions stored in the memory; when the processor executes the computer instructions, the terminal device executes the method described in any one of claims 1-13.

Images