A communication method, apparatus, program product, and storage medium

Abstract

This application provides a communication method, apparatus, program product, and storage medium. The method includes: determining that IMS registration has failed; and sending first indication information, which at least indicates the reason for the IMS registration failure. Thus, the terminal device can report the reason for the IMS registration failure to the network side through the first indication information, solving the problem in the prior art where the network side cannot obtain the reason for IMS registration. This allows the network side to make targeted adjustments to the IMS registration process based on the specific reason for the IMS registration failure, thereby resolving the IMS registration failure problem and improving the IMS registration success rate.

Description

Technical Field

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

[0002] With the development of communication technologies, various communication methods can be used, such as Voice over Long Term Evolution (VOLTE), Evolved Packet System Fallback (EPSfallback), and Voice over New Radio (VONR). Regardless of the method used, successful registration with the Internet Protocol Multimedia Subsystem (IMS) is a prerequisite. Therefore, improving the IMS registration success rate has become a pressing technical problem. Summary of the Invention

[0003] This application provides a communication method, device, program product, and storage medium, with the aim of improving the IMS registration success rate.

[0004] To achieve the above objectives, this application provides the following technical solution:

[0005] Firstly, this application provides a communication method. This method can be applied to a terminal device. Unless otherwise specified, the "terminal device" in this application can refer to the terminal device itself, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. The method includes: determining that IMS registration has failed; and sending first indication information, which at least indicates the reason for the IMS registration failure.

[0006] In the method provided by this application, the terminal device can report the reason for IMS registration failure to the network side through the first indication information. This solves the problem that the network side cannot obtain the reason for IMS registration failure in the prior art. It enables the network side to make targeted adjustments to the IMS registration process based on the specific reason for IMS registration failure, thereby solving the problem of IMS registration failure, improving the IMS registration success rate, and facilitating the timely recovery of related services.

[0007] In conjunction with the first aspect, in one possible implementation, the first indication information is carried in the User Equipment Assistance Information (UAI). This allows for the indication of the reason for IMS registration failure by modifying the existing UAI, without needing to design and define new messages, simplifying implementation and saving power to some extent by eliminating the need to send new messages. Furthermore, once the terminal device determines the reason for the IMS registration failure, it can promptly report the reason via the UAI, enabling the network side to resolve the IMS registration failure issue in a timely manner, thereby improving the IMS registration success rate.

[0008] In conjunction with the first aspect, in one possible implementation of the first aspect, the first indication information is carried in a Radio Resource Control (RRC) message. This facilitates reporting the reason for IMS registration failure.

[0009] In conjunction with the first aspect, in one possible implementation of the first aspect, the first indication information further indicates cell information associated with the IMS registration failure. This cell information includes at least one of the following: Physical Cell Identity (PCI) or Cell Global Identity (CGI). This also allows the specific cell information to be sent to the network side, enabling the network side to more accurately locate the fault that may be causing the IMS registration failure, conduct more precise troubleshooting, resolve the IMS registration failure issue, and prevent further IMS registration failures, thereby improving the IMS registration success rate.

[0010] In conjunction with the first aspect, in one possible implementation of the first aspect, sending first indication information includes: sending second indication information, the second indication information indicating the reason for IMS registration failure and cell information; receiving request information, the request information requesting the reporting of the reason for IMS registration failure and cell information; and sending a response message, the response message including the first indication information. Thus, through information interaction between the terminal device and the network side, the terminal device can be triggered to report the reason for IMS registration failure and cell information, facilitating the network side to resolve the IMS registration failure problem and improving the IMS registration success rate.

[0011] In conjunction with the first aspect, in one possible implementation of the first aspect, the second indication information is carried in the Radio Resource Control Connection Setup Complete (RRCConnection Setup Complete) message. This allows for the indication of the reason for IMS registration failure and cell information to the terminal device by modifying the existing RRC Connection SetupComplete message, without requiring the design and definition of a new message, thus simplifying implementation.

[0012] In conjunction with the first aspect, in one possible implementation of the first aspect, the reasons for IMS registration failure include at least one of the following: Internet Protocol (IP) type mismatch, inability to obtain routing announcement messages, or inability to obtain Internet Protocol version 6 (IPv6) prefix information. This allows the terminal device to report specific reasons for IMS registration failure, enabling the network side to make targeted adjustments to the IMS registration process, such as adjusting the IP type of the IMS network element, sending routing announcement messages, or configuring a valid subscribed IPv6 prefix, thereby resolving the IMS registration failure problem and improving the IMS registration success rate.

[0013] Secondly, this application provides a communication method that can be applied to a base station. Unless otherwise specified, the "base station" in this application can refer to the base station itself, a component within the base station (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the base station's functions. The method includes: receiving first indication information indicating the reason for IMS registration failure; and sending third indication information indicating the reason for IMS registration failure.

[0014] In the method provided in this application, the base station continues to send the reason for the IMS registration failure to the IMS network element. In this way, the IMS network element can make targeted adjustments to the IMS registration process based on the specific reason for the IMS registration failure, solve the problem of IMS registration failure, and improve the IMS registration success rate.

[0015] In conjunction with the second aspect, in one possible implementation, the first indication information is carried in the UAI. This allows for the indication of the reason for IMS registration failure by modifying the existing UAI, without needing to design and define new messages, simplifying implementation and saving power to some extent by eliminating the need to send new messages. Furthermore, once the terminal device determines the reason for the IMS registration failure, it can promptly report the reason via the UAI, allowing the base station to obtain the reason for the IMS registration failure in a timely manner.

[0016] In conjunction with the second aspect, in one possible implementation of the second aspect, the first indication information is carried in the RRC message. This facilitates reporting the reason for IMS registration failure.

[0017] In conjunction with the second aspect, in one possible implementation of the second aspect, the first indication information further indicates cell information associated with the IMS registration failure, the cell information including at least one of the following: PCI or CGI. This allows the base station to obtain specific cell information, facilitating more accurate location of the fault that may be causing the IMS registration failure, enabling more precise fault diagnosis and resolution of the IMS registration failure problem.

[0018] In conjunction with the second aspect, in one possible implementation of the second aspect, receiving the first indication information includes: receiving the second indication information, which indicates the reason for the IMS registration failure and cell information; sending the request information, which requests the reporting of the reason for the IMS registration failure and cell information; and receiving the response message, which includes the first indication information. In this way, through information interaction between the terminal device and the network side, the terminal device can be triggered to report the reason for the IMS registration failure and cell information, facilitating the network side to resolve the IMS registration failure problem and improving the IMS registration success rate.

[0019] Thirdly, this application provides a communication method. This method can be applied to IMS network elements. Unless otherwise specified, the "IMS network element" in this application can refer to the IMS network element itself, a component within the IMS network element (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the IMS network element's functions. The method includes: receiving third indication information, which indicates the reason for IMS registration failure; and adjusting the IMS registration process based on the reason for the IMS registration failure.

[0020] In the method provided by this application, the IMS network element can obtain the specific reason for the IMS registration failure. In this way, the IMS registration process can be adjusted in a targeted manner based on the specific reason for the IMS registration failure, so as to solve the problem of IMS registration failure and improve the IMS registration success rate.

[0021] In conjunction with the third aspect, in one possible implementation, adjusting the IMS registration process based on the reasons for IMS registration failure includes: if the IMS registration failure is due to an IP type mismatch, adjusting the IP type of the IMS network element; or, if the IMS registration failure is due to the inability to obtain a routing advertisement message, sending a routing advertisement message; or, if the IMS registration failure is due to the inability to obtain IPv6 prefix information, sending configuration information indicating valid subscribed IPv6 prefix information. This allows for targeted adjustments to the IMS registration process, resolving IMS registration failure issues and thereby improving the IMS registration success rate.

[0022] Fourthly, this application provides a communication method. This method can be applied to a Mobile Management Entity (MME). Unless otherwise specified, "MME" in this application can refer to the MME itself, a component within the MME (e.g., a processor, chip, or chip system), or a logical module or software capable of implementing all or part of the MME's functions. The method includes: receiving third indication information, which indicates the reason for IMS registration failure and cell information associated with the IMS registration failure; and determining the problematic cell where the IMS registration failure occurred based on the reason for the IMS registration failure and the cell information.

[0023] In the method provided in this application, the MME can obtain the reason for the IMS registration failure and the cell information associated with the IMS registration failure. This can identify the specific problematic cell, which facilitates subsequent troubleshooting of the problematic cell and resolves the IMS registration failure problem, thereby improving the IMS registration success rate.

[0024] In conjunction with the fourth aspect, in one possible implementation of the fourth aspect, the cell information includes at least one of the following: PCI or CGI. This allows the MME to obtain specific cell information, enabling more accurate location of potential faults, more precise fault diagnosis, and resolution of IMS registration failures, thereby improving the IMS registration success rate.

[0025] Fifthly, embodiments of this application provide a communication device that can be applied to a terminal device. Unless otherwise specified, "terminal device" in embodiments of this application can refer to the terminal device itself, or a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. Alternatively, the device can also be applied to a base station. Unless otherwise specified, "base station" in embodiments of this application can refer to the base station itself, or a component within the base station (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the base station's functions. The device can be applied to an IMS network element. Unless otherwise specified, "IMS network element" in this embodiment can refer to the IMS network element itself, a component within the IMS network element (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the IMS network element's functions. Alternatively, the device can be applied to an MME. Unless otherwise specified, "MME" in this embodiment can refer to the MME itself, a component within the MME (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the MME's functions. The device includes a module for executing the communication method in the first aspect or any optional embodiment of the first aspect, or a module for executing the communication method in the second aspect or any optional embodiment of the second aspect, or a module for executing the communication method in the third aspect or any optional embodiment of the third aspect, or a module for executing the communication method in the fourth aspect or any optional embodiment of the fourth aspect.

[0026] In a sixth aspect, embodiments of this application provide a communication device that can be applied to a terminal device or its internal circuits, chips, chip systems, etc., or to a network device or its internal circuits, chips, chip systems, etc. The device may include at least one processor, which is configured to call computer instructions in a memory to cause the communication device to execute the communication method in the first aspect or any optional embodiment of the first aspect, or execute the communication method in the second aspect or any optional embodiment of the second aspect, or execute the communication method in the third aspect or any optional embodiment of the third aspect, or execute the communication method in the fourth aspect or any optional embodiment of the fourth aspect.

[0027] In conjunction with the sixth aspect, in one possible implementation of the sixth aspect, the communication device may further include a memory.

[0028] In a seventh aspect, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform the communication method in the first aspect or any optional embodiment of the first aspect, or to perform the communication method in the second aspect or any optional embodiment of the second aspect, or to perform the communication method in the third aspect or any optional embodiment of the third aspect, or to perform the communication method in the fourth aspect or any optional embodiment of the fourth aspect.

[0029] Eighthly, embodiments of this application provide a computer-readable storage medium for storing a computer program that, when the computer program is run on a computer, causes the computer to execute the communication method in the first aspect or any optional embodiment of the first aspect, or execute the communication method in the second aspect or any optional embodiment of the second aspect, or execute the communication method in the third aspect or any optional embodiment of the third aspect, or execute the communication method in the fourth aspect or any optional embodiment of the fourth aspect.

[0030] Ninthly, embodiments of this application provide a chip system including a processor for supporting a device in implementing the functions involved in the foregoing aspects, such as transmitting or processing data and / or information involved in the foregoing methods. In one possible design, the chip system further includes a memory for storing program instructions and data necessary for the device. This chip system may be composed of chips or may include chips and other discrete devices.

[0031] In a tenth aspect, embodiments of this application provide a chip including one or more interface circuits and one or more processors; the interface circuits are configured to receive signals from the memory of an electronic device and send signals to the processors, the signals including computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device performs a communication method in the first aspect or any optional embodiment of the first aspect, or performs a communication method in the second aspect or any optional embodiment of the second aspect, or performs a communication method in the third aspect or any optional embodiment of the third aspect, or performs a communication method in the fourth aspect or any optional embodiment of the fourth aspect. Attached Figure Description

[0032] Figure 1 A flowchart illustrating a communication method provided in an embodiment of this application;

[0033] Figure 2 A flowchart illustrating another communication method provided in an embodiment of this application;

[0034] Figure 3A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0035] Figure 4 A flowchart illustrating the process of recording the reasons for IMS registration failure and cell information is provided in this embodiment of the application.

[0036] Figure 5 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0037] Figure 6 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0038] Figure 7 This is a schematic diagram of another communication device provided in an embodiment of this application;

[0039] Figure 8 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0040] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions "a," "an," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, "one or more" refers to one, two, or more; "and / or" describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0041] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0042] The "multiple" mentioned in the embodiments of this application refers to two or more. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order.

[0043] The embodiments of this application are applied to communication systems, which can be second-generation (2G) communication systems, third-generation (3G) communication systems, long-term evolution (LTE) systems, fifth-generation (5G) communication systems, LTE and 5G hybrid architectures, 5G New Radio (5G NR) systems, and new communication systems that will emerge in the future development of communication.

[0044] A communication system includes a first device and a second device. The first device can be a network-side device used to provide network communication functions; in some cases, it is also called a network device or network element. A network device can typically be a base station (including functional units of a base station, or a combination of functional units of base stations) or a core network unit. The core network unit can be a functional unit within the core network, including but not limited to the MME, Access and Mobility Management Function (AMF) unit, or Session Management Function (SMF) unit. The second device can be a device accessing the network, typically a terminal.

[0045] In the embodiments provided in this application, the base station can be any device with wireless transceiver capabilities, including but not limited to: evolved Node B (NodeB or eNB or e-NodeB) in LTE, base station (gNodeB or gNB) or transmission receiving point / transmission reception point (TRP) in new radio (NR), base stations evolved from 3GPP, access nodes in Wi-Fi systems, wireless relay nodes, wireless backhaul nodes, etc. The base station can be: macro base station, micro base station, pico base station, satellite base station, small cell, relay station, or balloon station, etc. The base station can include one or more co-located or non-co-located transmission reception points (TRPs). The base station can also be a radio controller, centralized unit (CU), and / or distributed unit (DU) in a cloud radio access network (CRAN) scenario. The base station can communicate with the terminal, or it can communicate with the terminal through a relay station. The terminal can communicate with multiple base stations using different technologies. For example, the terminal can communicate with base stations that support LTE networks, base stations that support 5G networks, and can also establish dual connections with both LTE and 5G base stations.

[0046] In the embodiments provided in this application, the terminal can take various forms, such as a mobile phone, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, vehicle-mounted terminal device, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, wearable terminal device, etc. The terminal may also be referred to as terminal equipment, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal equipment, mobile device, UE terminal equipment, terminal equipment, wireless communication equipment, UE agent, or UE device, etc. The terminal can also be a fixed terminal or a mobile terminal.

[0047] To more clearly illustrate the technical solutions of the embodiments of this application, the relevant concepts involved in the embodiments of this application are explained below.

[0048] (1) IMS is a multimedia service based on IP networks, aiming to provide end customers with a more novel and diversified multimedia service experience through IP networks. It is considered a core technology of next-generation networks and is of great significance for realizing the convergence of mobile and fixed networks, as well as introducing differentiated services such as the triple convergence of voice, data, and video. Among them, IMS uses the Session Initiation Protocol (SIP) as the call control protocol, realizing the separation of call control and service control, and enhancing multimedia support capabilities. It supports multiple access methods, including fixed telephone networks, mobile phone networks, and the Internet, allowing users to enjoy a converged communication experience across different networks and using multiple terminals.

[0049] IMS registration is the process by which terminal devices authenticate and register within the IMS network in order to use the services provided by IMS.

[0050] (2) Router Advertisement (ROI) messages are a type of ICMPv6 message used in IPv6 networks to announce the existence of routers and provide network configuration information. The main functions of RUI messages include: announcing the existence of routers, providing network configuration parameters, announcing prefix information, announcing the default router, etc.

[0051] (3) IPv6 prefix information is a fixed number of bits in an IPv6 address used to identify the network portion, which can be used for IPv6 address allocation and management.

[0052] (4) UAI is a new Radio Resource Control (RRC) message defined in the 5G R16 specification. Through UAI, the UE can notify the network of its various internal states so that the network can schedule resources to better match the specific state of the UE.

[0053] (5)MDT is a method in which operators use the commercial terminals or test terminals of contracted users to measure and report data, which partially replaces the traditional drive test work and realizes the automatic collection of terminal measurement data to detect and optimize problems and faults in the wireless network.

[0054] (6) IPv6 only means that in a part or the entire network, only the IPv6 protocol is used for data transmission, and the IPv4 protocol is not used.

[0055] IPv4v6 refers to the technology that uses both IPv4 and IPv6 protocols in a network to achieve the transition from IPv4 to IPv6.

[0056] (7) Proxy-Call Session Control Function (P-CSCF) is an important network element in IMS. As the first entity that users come into contact with in the IMS system, it is the unified entry point for IMS to visit the network.

[0057] (8) PCI is a physical layer identifier used to uniquely identify a cell in a communication system.

[0058] CGI is used to identify the area covered by a cell, uniquely identifying a cell worldwide.

[0059] Standard information refers to the communication standards and protocols between different mobile communication networks. Different standards can support different frequency bands, data rates, and quality of service. Common standards include LTE, Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), and so on.

[0060] Globally, 4G / 5G networks are gradually replacing 2G / 3G networks. Under 4G / 5G networks, call methods include VoLTE, EPS fallback, and VoNR. Regardless of the communication method, successful IMS registration is a prerequisite for use.

[0061] Currently, there are various IMS registration failure issues. For example, during the IMS registration process, when a terminal device initiates an IMS Public Data Networks (PDN) / Protocol Data Unit (PDU) request, it carries an IPv6-only or IPv4v6 IP type. The network assigns an IPv6-type Proxy-Call Session Control Function (PCSCCF) address and Interface Identifier (IID). The terminal device then initiates a Router Solicitation message, but fails to receive Router Advertisement messages from the network. As a result, it cannot obtain IPv6 prefix information from the Router Advertisement, and the terminal device cannot form an IPv6 address, thus failing to initiate IMS registration. Ultimately, IMS registration fails, impacting user experience.

[0062] However, the network side is currently unable to obtain the reason for the IMS registration failure, which prevents it from handling the IMS registration failure accordingly.

[0063] To address this, embodiments of this application provide a communication method, apparatus, program product, and storage medium. After determining that IMS registration has failed, the terminal reports the reason for the IMS registration failure to the network side through a first indication message. This solves the problem in the prior art that the network side cannot obtain the reason for the IMS registration failure, enabling the network side to make targeted adjustments to the IMS registration process based on the specific reason for the IMS registration failure, thereby resolving the IMS registration failure problem and improving the IMS registration success rate.

[0064] For details, please refer to Figure 1 , Figure 1 This application provides a flowchart illustrating a communication method. This communication method can be executed by a communication system, which may include terminal equipment, a base station, and IMS network elements. Unless otherwise specified, in this application, "terminal equipment" can refer to the terminal equipment itself, a component within the terminal equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal equipment's functions. Similarly, "base station" can refer to the base station itself, a component within the base station (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the base station's functions. Likewise, "IMS network element" can refer to the IMS network element itself, a component within the IMS network element (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the IMS network element's functions. The communication method provided in this application may include the following steps:

[0065] 101. Terminal device determined that IMS registration failed.

[0066] In this embodiment, the terminal device can initiate SA registration in a standalone (SA) network and successfully establish an Internet Protocol Multimedia Subsystem Protocol Data Unit Session (IMS PDU Session). Afterward, the terminal device can detect and determine whether IMS registration has failed, and determine the reason for the failure. If IMS registration fails, the terminal device can report the reason for the failure.

[0067] 102. The terminal device sends the first instruction information to the base station.

[0068] The first indication information at least indicates the reason for the IMS registration failure. The reason for the IMS registration failure can be used to adjust the IMS registration process. The reason for the IMS registration failure may be IP type mismatch or inability to obtain routing announcement messages, etc.

[0069] It should be noted that there is currently no corresponding reporting mechanism for IMS registration failures, and the network side cannot perceive the specific reasons for the terminal device's IMS registration failure.

[0070] 103. The base station sends the third instruction information to the IMS network element.

[0071] In this embodiment, after the terminal device sends the first indication information, the base station can receive the first indication information, parse it to obtain the reason for the IMS registration failure, and thus the base station can know that the IMS registration failed. It needs to report the reason for the IMS registration failure to the IMS network element for further processing. Afterwards, the base station can send a third indication information to the IMS network element. The third indication information also indicates abnormal information.

[0072] 104. Based on the reasons for IMS registration failure, adjust the IMS registration process for IMS network elements.

[0073] In this embodiment of the application, after the base station sends the third indication information, the IMS network element can receive the third indication information, parse the third indication information to obtain the reason for the IMS registration failure, and adjust the IMS registration process accordingly based on the reason for the IMS registration failure to solve the problem of IMS registration failure and improve the IMS registration success rate.

[0074] As can be seen, in this embodiment of the application, the terminal device can report the reason for IMS registration failure to the network side through the first instruction information. This solves the problem that the network side cannot obtain the reason for IMS registration failure in the prior art, so that the network side can make targeted adjustments to the IMS registration process based on the specific reason for IMS registration failure, solve the problem of IMS registration failure, and improve the IMS registration success rate.

[0075] exist Figure 1 Based on the publicly available communication methods, this application provides two compatible solutions to address IMS registration failures. One solution is based on the UAI reporting the cause of the IMS registration failure. Upon receiving the specific cause, the network side can adjust the IMS registration process accordingly to resolve the issue promptly. The other solution is based on the MDT reporting the cause of the IMS registration failure and cell information. This allows the network side to identify cells with a high concentration of IMS registration failures, adjust the IMS registration process, and troubleshoot the problem. The following provides a detailed description of these two compatible solutions for IMS registration failures.

[0076] Please see Figure 2 , Figure 2 A flowchart illustrating another communication method for implementing this application is provided. Figure 2 exist Figure 1 Based on the provided communication methods, a more detailed explanation of the communication methods will be given. Figure 2 The communication method can be executed by a communication system, which may include terminal equipment, base stations, and IMS network elements. The definitions of terminal equipment, base stations, and IMS network elements are the same as those mentioned above. Figure 1The definitions of terminal equipment, base station, and IMS network element are the same and will not be repeated here. The communication method provided in this application embodiment may include the following steps:

[0077] 201. Terminal device determined that IMS registration failed.

[0078] In this embodiment, SA registration can be performed first. After successful SA registration, the terminal device can send a PDU Session Establishment Request to the base station, requesting the Data Network Name (DNN) as IMS. The network device can send a PDU Session Establishment Accept to the terminal device to complete the PDU session establishment. Afterwards, the terminal device detects IMS registration failure, i.e., detects a PDU session configuration error, and determines the IMS registration failure and its cause. The cause of IMS registration failure can include any of the following: IP type mismatch, inability to obtain routing advertisement messages, or inability to obtain IPv6 prefix information.

[0079] 202. The terminal device sends UAI to the base station.

[0080] In this embodiment, the first indication information is carried in the UAI, and the first indication information at least indicates the reason for the IMS registration failure.

[0081] In one possible implementation, the UAI in this application embodiment may include a newly added first information element. The first information element carries first indication information, which is an IMS registration failure reason value. This IMS registration failure reason value indicates the reason for the IMS registration failure. The first information element can be named an IMS Fail Indication information element, an IMS Fail-Assistance information element, etc., and this application embodiment does not impose any limitations on this. By adding an IMS registration failure reason value to the UAI, the purpose of indicating a specific IMS registration failure reason is achieved. This method adds less data to the UAI, does not require additional signaling to indicate the reason for the IMS registration failure, saves communication resources, and enables network devices to receive the UAI faster, determine the reason for the IMS registration failure more promptly, and resolve the IMS registration failure problem more quickly. Specific examples are given below.

[0082] For example: an IMS registration failure reason value of 1 indicates an IP type mismatch; an IMS registration failure reason value of 2 indicates that a routing advertisement message could not be obtained; an IMS registration failure value of 3 indicates that IPv6 prefix information could not be obtained. It is understood that the above is merely an illustrative example and should not be construed as a limitation on the embodiments of this application.

[0083] It should be noted that, in this embodiment of the application, if the reason for IMS registration failure is indicated by the IMS registration failure reason value, the terminal device and the network side need to align the IMS registration failure reasons indicated by different IMS registration failure reason values. The terminal device and the network side can save the mapping relationship between different IMS registration failure reason values ​​and different IMS registration failure reasons, such as saving a mapping table between different IMS registration failure reason values ​​and different IMS registration failure reasons, etc. In this way, the network side can determine the specific reason for IMS registration failure based on the mapping relationship.

[0084] 203. The base station sends the third instruction information to the IMS network element.

[0085] It is understood that 203 in this embodiment is the same as 103 in the above embodiment, so it will not be described again.

[0086] 204. Based on the reasons for IMS registration failure, the IMS network element adjusts the IMS registration process.

[0087] It should be noted that adjusting the IMS registration process in this embodiment may include adjusting the registration parameters of the terminal device's IMSPDU session, which can provide corresponding handling for different types of IMS registration failures.

[0088] In one possible implementation, step 204 in this embodiment may include: adjusting the IMS registration process based on the reason for IMS registration failure, including: if the IMS registration failure is due to an IP type mismatch, adjusting the IP type of the IMS network element; or, if the IMS registration failure is due to the inability to obtain a routing announcement message, sending a routing announcement message; or, if the IMS registration failure is due to the inability to obtain IPv6 prefix information, sending configuration information indicating valid subscribed IPv6 prefix information. This allows for targeted adjustments to the IMS registration process, resolving the IMS registration failure problem and thereby improving the IMS registration success rate.

[0089] It should be noted that, in this embodiment of the application, the IMS network element can send routing announcement messages to the base station, and the base station can then send the routing announcement messages to the terminal device; similarly, the IMS network element can send configuration information to the base station, and the base station can then send the configuration information to the terminal device.

[0090] As can be seen, the existing UAI can be used to indicate the reason for IMS registration failure in this embodiment of the application, without the need to design and define new messages, which is convenient for implementation. Moreover, after the terminal device determines the reason for IMS registration failure, it can report the reason for IMS registration failure to the network side in a timely manner through UAI. In this way, the IMS network element can make timely and targeted adjustments to the IMS registration process based on the specific reason for IMS registration failure, and resolve the IMS registration failure problem in a timely manner, thereby improving the IMS registration success rate.

[0091] Please see Figure 3 , Figure 3 A flowchart illustrating another communication method for implementing this application is provided. Figure 3 exist Figure 1 Based on the provided communication methods, a more detailed explanation of the communication methods will be given. Figure 3 The communication method can be executed by a communication system, which may include terminal equipment, base stations, IMS network elements, and MME. The definitions of terminal equipment, base stations, and IMS network elements are the same as those mentioned above. Figure 1 The definitions of terminal equipment, base station, and IMS network element are the same and will not be repeated here. In this application's embodiments, "MME" can refer to the MME itself, a component within the MME (e.g., a processor, chip, or chip system), or a logical module or software capable of implementing all or part of the MME's functions. The communication method provided in this application's embodiments may include the following steps:

[0092] 301. Terminal device determined that IMS registration failed.

[0093] It is understood that 301 in this embodiment is similar to 201 in the above embodiment, and the same parts will not be described again here.

[0094] Please see Figure 4 , Figure 4This application provides a schematic diagram of a process for recording the cause of IMS registration failure and cell information. The process for recording the cause of IMS registration failure and cell information may include: 401. Performing SA registration, and the SA registration is successful; 402. After successful SA registration, the terminal device can send a PDU session establishment request to the base station, with the requested DNN being IMS; 403. The base station can send a PDU session establishment acceptance to the terminal device, completing the PDU session establishment; 404. An IMSSIP signaling interaction error occurs, and IMS registration fails; 405. The terminal device detects the IMS registration failure, i.e., detects an abnormal PDU session configuration, determines and records the cause of the IMS registration failure, and records one or more of the following information of the current cell where the IMS registration failure occurred: PCI, CGI, standard information, cell identity (Cell Id), radio access technology (Rat), etc., and may also record the terminal device's location information, such as latitude and longitude. The recorded information can then be saved locally for subsequent data statistics reporting to the network side. The reasons for IMS registration failure can be at least one of the following: IP type mismatch, inability to obtain routing announcement messages, or inability to obtain IPv6 prefix information.

[0095] In one possible implementation, the recorded information can be first saved to a local variable, and then the abnormal information can be reported to the network side when the reporting conditions are met. The reporting conditions may include establishing an RRC connection between the terminal device and the base station, etc. The local variable can be named something like "IMS Failure Report Storage (VarFailIMS-Report)" variable, etc., and this embodiment of the application does not impose any limitations on this.

[0096] 302. The terminal device sends a second instruction message to the base station.

[0097] The second indication information indicates the reason for the IMS registration failure and / or cell information.

[0098] In one possible implementation, the second indication information is carried in the RRC Connection Setup Complete message. In this way, by modifying the existing RRC Connection Setup Complete message, the reason for the terminal device's IMS registration failure and the failure to report cell information can be indicated without designing and defining a new message, which is convenient for implementation.

[0099] It should be noted that if the second indication information is carried in the RRC Connection Setup Complete message, an RRC connection needs to be established first. That is, before executing 302, the terminal device needs to send a Radio Resource Control Connection Request (RRC Connection Request) message to the base station, and the base station needs to send an RRC Connection Setup (RRC Connection Setup) message to the terminal device to establish an RRC connection.

[0100] In one possible implementation, the RRC Connection Setup Complete message may include a newly added third information element carrying second indication information. This third information element can be named something like the IMS FailIms-InfoAvailable information element; this embodiment does not impose any limitations on this. The second indication information being true indicates the presence of an anomaly.

[0101] 303. The base station sends a request message to the terminal device.

[0102] Among them, the request information requests the reporting of the reason for the IMS registration failure and / or cell information.

[0103] In this embodiment of the application, after the terminal device sends the second indication information, the base station will receive the second indication information. The base station can parse the second indication information to determine the reason and / or cell information of the IMS registration failure that the terminal device has not yet reported. The base station can send a request information to request the terminal device to report the reason and / or cell information of the IMS registration failure.

[0104] In one possible implementation, the request information can be carried in an RRC message. This RRC message can be a User Equipment Information Request (UEInformationRequest) message, which may include a newly added fourth information element to carry the request information. This fourth information element could be named something like an IMS anomaly report request (failIms-ReportReq) element; this embodiment does not impose such limitations. A request value of true indicates that the reason for the IMS registration failure and / or cell information should be reported. After authentication, security activation, and other processes, the base station can request the terminal device to report the reason for the IMS registration failure and / or cell information via the UEInformationRequest message.

[0105] In this embodiment of the application, the information interaction between the terminal device and the base station can trigger the terminal device to report the reason for the IMS registration failure and / or cell information, which facilitates the subsequent resolution of the IMS registration failure problem.

[0106] 304. The terminal device sends the first instruction information to the base station.

[0107] In this embodiment of the application, after the base station sends the request information, the terminal device will receive the request information. The terminal device can parse the request information to determine the reason for the IMS registration failure and / or cell information that needs to be reported. The terminal device can send the first indication information to indicate the reason for the IMS registration failure and / or cell information.

[0108] The cell information includes at least one of the following: PCI or CGI.

[0109] In one possible implementation, the first indication information is carried in the RRC message, which facilitates the reporting of anomaly information. The RRC message carrying the first indication information can be a UE Information Response message. This UE Information Response message may include a newly added second information element, which carries the first indication information. This second information element can be named an IMS anomaly report (failIms-Report) information element, etc., and this application embodiment does not impose any limitations on this. The content of the failIms-Report information element can come from the aforementioned VarFailIMS-Report variable, that is, the MDT mode of the failIms-Report information element can be added to record relevant data of IMS registration failure, summarize the problem cell information, and report it to the network through the MDT method, promoting timely network configuration optimization.

[0110] In one possible implementation, the first indication information in this embodiment is an IMS registration failure reason value, which indicates the reason for the IMS registration failure. Thus, by only carrying the IMS registration failure reason value, the specific reason for the IMS registration failure can be indicated, thereby reducing the amount of data carried by the UAI and saving communication resources.

[0111] It should be noted that the same base station can receive multiple different first indication messages sent by multiple different terminal devices. Then, one first indication message can correspond to one third indication message to report the reason for IMS registration failure and / or cell information to the MME one by one. Alternatively, multiple first indication messages can correspond to one third indication message to report the reasons for multiple IMS registration failures and / or multiple cell information to the MME together, etc. This application embodiment does not limit this.

[0112] 305. The base station sends a third instruction message to the IMS network element.

[0113] It is understood that 305 in this embodiment is similar to 103 in the above embodiment, and the same parts will not be described again here.

[0114] In this embodiment, the third indication information can at least indicate the reason for the IMS registration failure.

[0115] 306. Based on the reasons for IMS registration failure, the IMS network element adjusts the IMS registration process.

[0116] It is understood that 306 in this embodiment is the same as 204 in the above embodiment, and will not be described again here.

[0117] 307. The base station sends a third instruction message to the MME.

[0118] In this embodiment, after the terminal device sends the first indication information, the base station can receive the first indication information, parse it to obtain the reason for the IMS registration failure and the cell information. Thus, the base station can know that the IMS registration has failed and needs to continue reporting the reason for the IMS registration failure and the cell information to the MME for processing. Afterwards, the base station can send a third indication information to the MME. The third indication information indicates the reason for the IMS registration failure and the cell information.

[0119] 308. Based on the reason for the IMS registration failure and the cell information, the MME determines the problematic cell where the IMS registration failure occurred.

[0120] In this embodiment of the application, after the base station sends the third indication information, the MME can receive the third indication information, parse the third indication information, obtain the reason for the IMS registration failure and the cell information, locate the cell with a relatively concentrated fault based on the reason for the IMS registration failure and determine the problem cell where the IMS registration failure occurred, so as to carry out corresponding fault investigation on the problem cell.

[0121] In this embodiment, troubleshooting can be performed on problematic cells, such as checking for anomalies in related links based on PCI or CGI. It should be noted that the MME can receive IMS registration failure reasons and cell information reported by multiple different terminal devices. Therefore, based on multiple IMS registration failure reasons and cell information, the cell with the most concentrated faults can be located; this cell with the most concentrated faults is the problematic cell where IMS registration failure occurred.

[0122] In one possible implementation, the number of times a cell ID is reported can be used to determine whether a cell has a cluster of problems, or the number of times PCI or CGI reports can be used to determine whether a cell has a cluster of problems, and so on.

[0123] As can be seen, in this application implementation, the terminal device sends a second indication message to the base station indicating the reason for the IMS registration failure and cell information. The base station can then request the terminal device to report the reason for the IMS registration failure and cell information. After the terminal device reports the reason for the IMS registration failure and cell information, the base station will continue to report the reason for the IMS registration failure and cell information to the IMS network element and MME. Thus, the IMS network element can adjust the IMS registration process based on the specific reason for the IMS registration failure, and the MME can be aware of the IMS registration failure and locate the problematic cell, facilitating subsequent troubleshooting of the problematic cell. This allows for dynamic and timely resolution of the IMS registration failure problem, improving the IMS registration success rate.

[0124] Please see Figure 5 , Figure 5 This is a flowchart illustrating another communication method provided in an embodiment of this application. This communication method can be executed by a communication system, which may include a terminal device, a base station, and an MME. The definitions of the terminal device, base station, and MME are the same as described above. Figure 3 The definitions of terminal equipment, base station, and MME are the same and will not be repeated here. The communication method provided in the embodiments of this application may include the following steps:

[0125] 501. The terminal device sends a Radio Resource Control Connection Request message to the base station.

[0126] In this embodiment, when IMS registration fails, the terminal device can first record the reason for the failure and cell information locally. Then, when the terminal device has the opportunity to initiate an RRC connection, it can inform the network side of the reason for the IMS registration failure and the corresponding cell information via an RRCConnection Setup Complete message.

[0127] It is understood that the reasons for registration failure and cell information in this embodiment are the same as those for IMS registration failure in the above embodiments, so they will not be repeated here.

[0128] 502. The network device sends a wireless resource control connection setting message to the terminal device.

[0129] 503. The terminal device sends a wireless resource control connection setup completion message to the base station.

[0130] It is understood that 503 in this application embodiment is similar to 302 in the above embodiment, and therefore will not be described again.

[0131] 504. The base station sends a request message to the terminal device.

[0132] It is understood that 504 in this application embodiment is similar to 303 in the above embodiment, and the same parts will not be described again here.

[0133] In this embodiment of the application, the base station can send request information to the terminal device after authentication and security activation.

[0134] 505. The terminal device sends a response message to the base station.

[0135] It is understood that 505 of this application embodiment is similar to 304 of the above embodiment, and the same parts will not be described again here.

[0136] The response message in this embodiment is an RRC message, which includes first indication information indicating abnormal information.

[0137] 506. The base station sends a message to the MME indicating the reason for the registration failure and cell information.

[0138] The message indicating the reason for the registration failure and the cell information can be an S1-AP message.

[0139] Understandably, the base station can also send a message to the MME including the reason for the registration failure and cell information, such as the reason for the IMS registration failure and cell information can be carried in the S1-AP message.

[0140] 507. MME executes the fault determination process.

[0141] The MME processing flow in this application embodiment can also be directly based on existing technology solutions.

[0142] It should be noted that, Figure 5 The communication method shown can also be used independently based on existing technologies.

[0143] As can be seen, in this embodiment of the application, the terminal device can first record the reason for the IMS registration failure and the corresponding cell information locally, and then report the reason for the IMS registration failure and the corresponding cell information to the network side after reconnecting, so that the network side can perform corresponding processing to solve the problem of IMS registration failure and improve the IMS registration success rate.

[0144] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0145] To facilitate better implementation of the above-described solutions in the embodiments of this application, related apparatus for implementing the above-described solutions is also provided below.

[0146] Please see Figure 6 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 600 may include a transceiver module 601 (sometimes also called a transceiver unit) and a processing module 602 (sometimes also called a processing unit). The transceiver module can implement sending and receiving functions. When the transceiver module implements the sending function, it can be called a sending module (sometimes also called a sending unit), and when the transceiver module implements the receiving function, it can be called a receiving module (sometimes also called a receiving unit). The sending module and the receiving module can be the same functional module, which is called the transceiver module and can implement both sending and receiving functions; or, the sending module and the receiving module can be different functional modules, and the transceiver module is a collective term for these functional modules.

[0147] In some possible implementations, the communication device 600 provided in the embodiments of this application further includes: a storage module (sometimes also called a storage unit) for storing any data, computer instructions and / or computer programs that may be involved in the embodiments of this application.

[0148] The transceiver module 601, processing module 602, and storage module in this application embodiment are used to enable the communication device 600 to perform the functions of the terminal device in the above method embodiment, or to enable the communication device 600 to perform the functions of the base station in the above method embodiment, or to enable the communication device 600 to perform the functions of the IMS network element in the above method embodiment. Alternatively, they are used to enable the communication device 600 to perform the functions of the MME in the above method embodiment.

[0149] The following describes each module in the communication device 600, which is used to implement the functions of the terminal device in the above method embodiments.

[0150] In some possible implementations, in the communication device 600 provided in this application embodiment, the processing module 602 is used to determine that IMS registration has failed;

[0151] The transceiver module 601 is used to send first indication information, which at least indicates the reason for the IMS registration failure.

[0152] In some possible implementations, in the communication device 600 provided in this application embodiment, the first instruction information is carried in the UAI.

[0153] In some possible implementations, in the communication device 600 provided in this application embodiment, the first indication information is carried in the RRC message.

[0154] In some possible implementations, in the communication device 600 provided in this application embodiment, the first indication information also indicates cell information associated with IMS registration failure, and the cell information includes at least one of the following: PCI or CGI.

[0155] In some possible implementations, in the communication device 600 provided in this application embodiment, the transceiver module 601 is specifically used to send second indication information, the second indication information indicating the reason for IMS registration failure and cell information; receive request information, the request information requesting the reporting of the reason for IMS registration failure and cell information; and send a response message, the response message including the first indication information.

[0156] In some possible implementations, in the communication device 600 provided in this application embodiment, the second indication information is carried in the RRC Connection Setup Complete message.

[0157] In some possible implementations, the reason for IMS registration failure in the communication device 600 provided in this application embodiment is any of the following: IP type mismatch, inability to obtain routing announcement messages, or inability to obtain IPv6 prefix information.

[0158] The following describes each module in the communication device 600, which is used to implement the functions of the base station in the above method embodiment.

[0159] In some possible implementations, in the communication device 600 provided in this application embodiment, the transceiver module 601 is used to receive first indication information, the first indication information indicating the reason for IMS registration failure;

[0160] The transceiver module 601 is also used to send third indication information, which indicates the reason for the IMS registration failure.

[0161] In some possible implementations, in the communication device 600 provided in this application embodiment, the first instruction information is carried in the UAI.

[0162] In some possible implementations, in the communication device 600 provided in this application embodiment, the first indication information is carried in the RRC message.

[0163] In some possible implementations, in the communication device 600 provided in this application embodiment, the first indication information also indicates cell information associated with IMS registration failure, and the cell information includes at least one of the following: PCI or CGI.

[0164] In some possible implementations, in the communication device 600 provided in this application embodiment, the transceiver module 601 is specifically used to receive second indication information, the second indication information indicating the reason for IMS registration failure and cell information; send request information, the request information requesting the reporting of the reason for IMS registration failure and cell information; and receive a response message, the response message including the first indication information.

[0165] The following describes each module in the communication device 600, which is used to implement the functions of the IMS network element in the above method embodiment.

[0166] In some possible implementations, in the communication device 600 provided in this application embodiment, the transceiver module 601 is used to receive third indication information, which indicates the reason for IMS registration failure;

[0167] Processing module 602 is used to adjust the IMS registration process based on the reasons for IMS registration failure.

[0168] In some possible implementations, in the communication device 600 provided in this application embodiment, the processing module 602 is specifically used to adjust the IP type of the IMS network element when the reason for IMS registration failure is that the Internet Protocol IP type does not match.

[0169] The transceiver module 601 is also used to send routing announcement messages when IMS registration fails because the reason is that the routing announcement message cannot be obtained.

[0170] The transceiver module 601 is also used to send configuration information when IMS registration fails because the IPv6 prefix information cannot be obtained. The configuration information indicates valid subscribed IPv6 prefix information.

[0171] The following describes each module in the communication device 600, which is used to implement the function of the MME in the above method embodiment.

[0172] In some possible implementations, in the communication device 600 provided in this application embodiment, the transceiver module 601 is used to receive third indication information, the third indication information indicating the reason for IMS registration failure and cell information associated with IMS registration failure;

[0173] The processing module 602 is used to determine the problematic cell where IMS registration failed, based on the reason for the IMS registration failure and the cell information.

[0174] In some possible implementations, the cell information in the communication device 600 provided in this application embodiment includes at least one of the following: PCI or CGI.

[0175] It should be noted that the physical device corresponding to the transceiver module can be a transceiver, and the physical device corresponding to the processing module can be a processor. The information interaction and execution processes between the modules of the above-mentioned device are based on the same concept as the method embodiments of this application, and the resulting technical effects are the same. For details, please refer to the descriptions in the foregoing method embodiments of this application, which will not be repeated here.

[0176] Figure 7 This application provides another example of the composition of a communication device. The communication device 700 may be a first device, including but not limited to a base station and a core network unit. Figure 7 A simplified schematic diagram of a base station structure is shown. The base station includes sections 710, 720, and 730. Section 710 is mainly used for baseband processing and base station control; section 710 is typically the control center of the base station, often referred to as a processor, used to control the base station to perform the processing operations on the first device side in the above method embodiments. Section 720 is mainly used to store computer program code and data. Section 730 is mainly used for the transmission and reception of radio frequency signals and the conversion between radio frequency signals and baseband signals; section 730 is often referred to as a transceiver module, transceiver, transceiver circuit, or transceiver unit. The transceiver module of section 730, also referred to as a transceiver or transceiver unit, includes an antenna 733 and radio frequency circuitry (…). Figure 7 (Not shown in the diagram), where the radio frequency circuitry is primarily used for radio frequency processing. Optionally, the device in section 730 used to implement the receiving function can be considered a receiver, and the device used to implement the transmitting function can be considered a transmitter; that is, section 730 includes receiver 732 and transmitter 731. A receiver can also be called a receiving module, receiver circuit, or receiving circuit, etc., and a transmitter can be called a transmitting module, transmitter, or transmitting circuit, etc.

[0177] Sections 710 and 720 may include one or more circuit boards, each of which may include one or more processors and one or more memories. The processors are used to read and execute programs from the memories to implement baseband processing functions and control the base station. If multiple circuit boards exist, they can be interconnected to enhance processing capabilities. As an alternative implementation, multiple circuit boards may share one or more processors, multiple circuit boards may share one or more memories, or multiple circuit boards may simultaneously share one or more processors.

[0178] For example, in one implementation, the transceiver module in section 730 is used to execute the transceiver-related processes performed by the base station (first device) in the aforementioned method embodiments. The processor in section 710 is used to execute the processing-related processes performed by the base station in the aforementioned method embodiments.

[0179] It should be understood that Figure 7This is for illustrative purposes only and not as a limitation. The network devices mentioned above, including processors, memory, and transceivers, may be independent of... Figure 7 The structure shown.

[0180] Figure 8 This application provides another example of the composition of a communication device. The communication device can be a second device, including but not limited to mobile phones, smart wearable devices (such as smartwatches), and other electronic devices. Taking a mobile phone as an example, the communication device may include a processor 310, an external memory interface 320, an internal memory 321, a display screen 330, a camera 340, an antenna 100, an antenna 200, a cellular communication module 350, and a short-range communication module 360, etc.

[0181] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the communication device. In other embodiments, the communication device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0182] Processor 310 may include one or more processing units, such as application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0183] It is understood that the interface connection relationships between the modules illustrated in this embodiment are merely illustrative and do not constitute a structural limitation on the communication device. In other embodiments of this application, the communication device may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0184] The external storage interface 320 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the communication device. The external storage card communicates with the processor 310 through the external storage interface 320 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.

[0185] Internal memory 321 can be used to store computer executable program code, which includes instructions. Processor 310 executes various functional applications and data processing of the communication device by running the instructions stored in internal memory 321, thereby implementing the communication method described in the above embodiments. Internal memory 321 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the communication device (such as audio data, phonebook, etc.). Furthermore, internal memory 321 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 310 executes various functional applications and data processing of the communication device by running instructions stored in internal memory 321 and / or instructions stored in memory located within the processor.

[0186] The wireless communication function of the communication device can be realized through antenna 100, antenna 200, cellular communication module 350, short-range communication module 360, modem processor and baseband processor, etc.

[0187] Antennas 100 and 200 are used to transmit and receive electromagnetic wave signals. Each antenna in the communication device can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 100 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0188] The cellular communication module 350 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G in communication devices. The cellular communication module 350 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The cellular communication module 350 can receive electromagnetic waves through the antenna 100, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The cellular communication module 350 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation through the antenna 100. In some embodiments, at least some functional modules of the cellular communication module 350 may be housed in the processor 310. In some embodiments, at least some functional modules of the cellular communication module 350 and at least some modules of the processor 310 may be housed in the same device.

[0189] In some embodiments, the communication device initiates or receives call requests via cellular communication module 350 and antenna 100.

[0190] Furthermore, an operating system runs on the aforementioned components. Examples include iOS, Android, and Windows operating systems. Applications can be installed and run on this operating system. Those skilled in the art will understand that, for the sake of convenience and brevity, explanations and beneficial effects of the relevant content in any of the communication devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0191] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or modules may be electrical, mechanical, or other forms.

[0192] The modules described as separate components may or may not be physically separate. Similarly, the components shown as modules may or may not be physical modules; they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0193] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0194] If the integrated modules are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the essential contribution of the technical solution of this application, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the processes of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

[0195] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method includes: The Internet Protocol Multimedia Subsystem (IMS) registration has failed. Send a first indication message, which at least indicates the reason for the IMS registration failure.

2. The method according to claim 1, characterized in that, The first indication information is carried in the User Equipment Assistance Information (UAI).

3. The method according to claim 1, characterized in that, The first indication information is carried in the Radio Resource Control (RRC) message.

4. The method according to claim 3, characterized in that, The first indication information also indicates cell information associated with IMS registration failure, the cell information including at least one of the following: Physical Cell Identifier (PCI) or Cell Global Identifier (CGI).

5. The method according to any one of claims 4, characterized in that, The sending of the first indication information includes: Send a second indication message, which indicates the reason for the IMS registration failure and the cell information; Receive a request message, which requests the reporting of the reason for the IMS registration failure and the cell information; Send a response message, the response message including the first indication information.

6. The method according to claim 5, characterized in that, The second indication information is carried in the Radio Resource Control Connection Setup Complete (RRC) message.

7. The method according to any one of claims 1 to 6, characterized in that, The reason for the IMS registration failure is any of the following: Internet Protocol IP type mismatch, inability to obtain routing announcement messages, or inability to obtain IPv6 prefix information.

8. A communication method, characterized in that, The method includes: Receive a first indication message, which indicates the reason for the failure of Internet Protocol Multimedia Subsystem (IMS) registration; Send a third indication message, which indicates the reason for the IMS registration failure.

9. The method according to claim 8, characterized in that, The first indication information is carried in the User Equipment Assistance Information (UAI).

10. The method according to claim 8, characterized in that, The first indication information is carried in the Radio Resource Control (RRC) message.

11. The method according to claim 10, characterized in that, The first indication information also indicates cell information associated with IMS registration failure, the cell information including at least one of the following: Physical Cell Identifier (PCI) or Cell Global Identifier (CGI).

12. The method according to claim 11, characterized in that, The receiving of the first indication information includes: Receive a second indication message, which indicates the reason for the IMS registration failure and the cell information; Send a request message, which requests the reporting of the reason for the IMS registration failure and the cell information; A response message is received, the response message including the first indication information.

13. A communication method, characterized in that, The method includes: Receive a third indication message, which indicates the reason for the IMS registration failure; Based on the reasons for the IMS registration failure, the IMS registration process has been adjusted.

14. The method according to claim 13, characterized in that, The adjustment of the IMS registration process based on the reasons for the IMS registration failure includes: The reason for the IMS registration failure is that the Internet Protocol IP type does not match. Adjust the IP type of the IMS network element. Alternatively, the IMS registration failure may be due to the inability to obtain the routing announcement message and send the routing announcement message. Alternatively, the IMS registration may fail because it cannot obtain IPv6 prefix information and send configuration information, which indicates valid subscribed IPv6 prefix information.

15. A communication method, characterized in that, The method includes: Receive third indication information, which indicates the reason for the IMS registration failure and the cell information associated with the IMS registration failure; Based on the reason for the IMS registration failure and the cell information, the problematic cell where the IMS registration failure occurred is identified.

16. The method according to claim 15, characterized in that, The cell information includes at least one of the following: Physical Cell Identifier (PCI) or Cell Global Identifier (CGI).

17. A communication device, characterized in that, It includes modules for performing the communication method as described in any one of claims 1 to 7, or for performing the communication method as described in any one of claims 8 to 12, or for performing the communication method as described in any one of claims 13 to 14, or for performing the communication method as described in any one of claims 15 to 16.

18. A communication device, characterized in that, The device includes at least one processor configured to invoke computer instructions in memory to cause the communication device to perform the communication method as described in any one of claims 1 to 7, or the communication method as described in any one of claims 8 to 12, or the communication method as described in any one of claims 13 to 14, or the communication method as described in any one of claims 15 to 16.

19. A computer program product, characterized in that, The instruction includes instructions that, when executed on a computer, cause the computer to perform the communication method as described in any one of claims 1 to 7, or the communication method as described in any one of claims 8 to 12, or the communication method as described in any one of claims 13 to 14, or the communication method as described in any one of claims 15 to 16.

20. A computer storage medium, characterized in that, Used to store a computer program that, when the computer program is run on a computer, causes the computer to perform the communication method as described in any one of claims 1 to 7, or the communication method as described in any one of claims 8 to 12, or the communication method as described in any one of claims 13 to 14, or the communication method as described in any one of claims 15 to 16.

Images