Communication method and related device

By re-registering or re-dialing after receiving a service denial message in the terminal device, the problem of unsuccessful call calls by the terminal device is solved, and the success rate and user experience of the call calls are improved.

CN120263776APending Publication Date: 2025-07-04HONOR DEVICE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311833598.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-12-27
Publication Date
2025-07-04

AI Technical Summary

Technical Problem

Terminal devices are prone to unsuccessful situations when calling, which affects the user experience.

Method used

Re-registration or domain redialing after receiving the service denial message is received to re-establish the communication link with the network device, and the success rate of call calls is improved.

Benefits of technology

Improves the success rate and user experience of call calls, and successfully establishes communication links after multiple attempts to re-register or re-dialize the domain.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120263776A_ABST
    Figure CN120263776A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a communication method and a related device, and is applied to the technical field of terminals. The method comprises: in response to an operation of making a call by a user, a terminal device switches from an idle state to a service state, and sends a first service request message to a first network device to request to establish a communication link with the first network device, the first network device being a device registered by the terminal device. A first network device receives a first service request message, since the state of a terminal device is updated to be logout through an implicit separation mode, a first service rejection message is sent to the terminal device, and the first service rejection message carries a rejection reason. And after receiving the first service rejection message, the terminal equipment registers on the first network equipment again. Thus, conversation can be realized through the first network equipment, and the call conversation success rate is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the technical field of terminals, and in particular, to a communication method and related devices. Background Art

[0002] A terminal device is installed with a subscriber identity module (SIM) or an embedded SIM card (eSIM), and can support functions such as voice calls, video calls, and Internet access. Currently, the phenomenon that a call on the terminal device fails easily occurs, affecting the user experience. Summary of the Invention

[0003] Embodiments of this application provide a communication method and related devices, which are applied to the technical field of terminals. In the embodiments of this application, it is beneficial to improve the success rate of call communication on the terminal device.

[0004] In a first aspect, embodiments of this application provide a communication method, which can be applied to a terminal device. The method includes: sending a first message, where the first message includes REGISTER information; receiving a second message, where the second message includes REGISTER / 200OK information, and the second message is used to respond to the first message; in response to an operation of a user making a call, sending a third message, where the third message includes SERVICE REQUEST information; receiving a fourth message, where the fourth message includes SERVICE REJECT information and #10IMPLICITLY DETACHED information, and the fourth message is used to respond to the third message; in response to the fourth message, sending a fifth message, where the fifth message includes ATTACH REQUEST information; where, before sending the fifth message, a sixth message including ACCESS REQUEST information is not sent.

[0005] The REGISTER information can also be described as Register information, the SERVICE REQUEST information can also be described as Service request information, and the SERVICE REJECT information, IMPLICITLY DETACHED information, ATTACH REQUEST information, and ACCESS REQUEST information are similar, and will not be elaborated here.

[0006] The terminal device sends a first message and receives a second message, which can indicate that the terminal device has successfully registered on the network device. The terminal device can communicate with the network device. In response to an operation of a user making a call, the terminal device switches from the idle state to the service state and can send a third message to establish a communication link with the network device.

[0007] The terminal device receives the fourth message, which indicates that the terminal device is deregistered on the network device, and the terminal device can send the fifth message to request re-registration. Before the terminal device sends the fifth message, it does not send the sixth message, which means that it does not request to access other network devices before sending the fifth message.

[0008] In the embodiment of the present application, the third message can refer to Figure 7 The first service request message in the fourth message can refer to Figure 7 The first service rejection message in the fifth message can refer to Figure 7 The attachment request message in the sixth message can refer to Figure 5 The access request message in.

[0009] In this way, by re-registering and re-establishing the communication link with the network device to realize the call, it is helpful to improve the success rate of the call, and compared with realizing the call by accessing other network devices, it is helpful to improve the efficiency of the call.

[0010] In one possible implementation, the method also includes: receiving a seventh message, the seventh message including ATTACHACCEPT information and IMS MODE SUPPORTED information, the seventh message is used to respond to the fifth message; sending an eighth message, the eighth message including REGISTER information; receiving a ninth message, the ninth message including REGISTER / 200OK information, the ninth message is used to respond to the eighth message; and in response to the ninth message, initiating a first call.

[0011] The ATTACH ACCEPT information may be described as Attach accept information, and the IMS MODE SUPPORTED information may be described as IMS mode supported information, which is not limited in the embodiments of the present application.

[0012] The seventh message is used to indicate that the access is successful and IMS registration can be performed. The terminal device can perform IMS registration, that is, send the eighth message, and the eighth message is used to indicate a registration request. If the ninth message is received, it means that the re-registration is successful, a communication link is established between the terminal device and the network device, and the terminal device can initiate a call.

[0013] In the embodiment of the present application, the seventh message can refer to Figure 7 The eighth message can refer to the attachment acceptance message in Figure 7 The ninth message can refer to the registration request message in Figure 7 The registration acceptance message in .

[0014] In this way, initiating a call when the re-registration is successful is helpful to improve the success rate of the call.

[0015] Optionally, after sending the eighth message, the terminal device may receive a reply message in response to the eighth message, where the reply message is used to indicate that authentication is required for registration. Then the terminal device may send a registration request carrying authentication. If the terminal device receives a registration acceptance message, i.e., the ninth message, in response to the registration request carrying authentication, it may determine that the re-registration is successful. Among them, the reply message may include UNAUTHORIZED (401) information. The registration request carrying authentication may include IMS SIP REGISTER information. The registration acceptance message in response to the registration request carrying authentication may include OK (200) information.

[0016] In this way, there may also be other interaction messages between the eighth message and the ninth message to implement re-registration.

[0017] In a possible implementation, initiating a first call in response to the ninth message includes: initiating a first call in response to the ninth message and the fourth message.

[0018] When the terminal device receives the fourth message, it may indicate that the request of the third message is rejected. When it receives the ninth message, it can indicate that the re-registration is successful. In the case where the request of the third message is rejected and the re-registration is successful, a first call is initiated.

[0019] In the embodiments of the present application, initiating a first call in response to the ninth message and the fourth message may refer to Figure 7 sending a call establishment request in the case where the call is unsuccessful and the re-registration is successful.

[0020] In this way, it is equivalent to that in response to the user's operation of making a call, the first attempt is rejected, and then the second attempt is made. In the case where the first attempt is rejected and the second attempt is successful, a first call is initiated. In this way, multiple attempts are made, which is beneficial to improving the success rate of the call.

[0021] In a possible implementation, the method further includes: sending a sixth message when the first call is unsuccessful.

[0022] If the first call is unsuccessful, it may indicate that the network device that has been accessed cannot implement a call. Then, a sixth message may be sent to access other network devices to implement a call. In the embodiments of the present application, this method may refer to Figure 7 S715 to S717 in

[0023] In this way, in the case where the call is unsuccessful, other network devices are accessed to facilitate subsequent re-calling, which is beneficial to improving the success rate of the call.

[0024] In a possible implementation, the method further includes: receiving a tenth message, where the tenth message includes REJECT information, and the tenth message is used to respond to the fifth message; in response to the tenth message, sending a sixth message.

[0025] Receiving the tenth message indicates that the registration is rejected, so the re-registration fails. In the case of re-registration failure, the terminal device can access other network devices by sending a sixth message to implement a call. In the embodiments of the present application, this method can refer to Figure 7 S718 to S720 in

[0026] In this way, in the case of failure to establish a communication link with a previously registered network device, accessing other network devices to facilitate call implementation is beneficial to improving the success rate of call.

[0027] In a possible implementation, the method further includes: receiving an eleventh message, where the eleventh message includes ATTACHACCEPT information, and the eleventh message is used to respond to the sixth message; in response to the eleventh message, initiating a second call.

[0028] Receiving the eleventh message can indicate successful access to other network devices. The terminal device can implement a call through other network devices, so a second call is initiated.

[0029] In the embodiments of the present application, the eleventh message can refer to Figure 5 the access acceptance message in

[0030] In this way, implementing a call through other network devices is beneficial to improving the success rate of call.

[0031] In a possible implementation, the above REGISTER information is IMSSIPREGISTER information. If the REGISTER information is IMS SIP REGISTER information, it can indicate that the terminal device performs IMS registration, which is beneficial to establishing a communication link with the network device.

[0032] In a possible implementation, before sending the first message, the method further includes: sending a twelfth message, where the twelfth message includes ATTACH REQUEST information; receiving a thirteenth message, where the thirteenth message includes ATTACH ACCEPT information and IMS MODE SUPPORTED information, and the thirteenth message is used to respond to the twelfth message.

[0033] Before the terminal device performs IMS registration, it can first perform an attachment, that is, send a twelfth message, which is used to request an attachment. If the thirteenth message is received, it indicates that the attachment is successful. After the attachment, registration can be performed. In this way, it is beneficial to realize the communication between the terminal device and the network device.

[0034] In a possible implementation manner, the method further includes: in response to the second message, displaying an icon including HD information.

[0035] When the terminal device receives the second message, it can indicate that the registration is successful, and the terminal device can display an icon including HD information on the interface. In the embodiments of the present application, the icon including HD information can be as shown in Figure 6 interface a.

[0036] In this way, indicating that the registration is successful through the icon including HD information is convenient for observation.

[0037] In a possible implementation manner, the method further includes: in response to the second message, setting the registration status of the Internet Protocol Multimedia Subsystem (IMS) to IMS registered.

[0038] When the terminal device receives the second message, it can indicate that the IMS registration is successful, and the terminal device can set the registration status of the IMS to IMS registered, which is convenient for monitoring the IMS registration status.

[0039] In a possible implementation manner, the fifth message is used to request registration on the first network device; the sixth message is used to request access to the second network device. The first network device is the device registered through the first message, and the first network device is different from the second network device.

[0040] In a possible implementation manner, the first message is used to request registration on the first network device; the second message is used to indicate acceptance of the request of the first message; the third message is used to request to establish a communication link with the first network device; the fourth message is used to indicate implicit separation.

[0041] In a possible implementation, the terminal device includes a connection management (CM) module and a network attached storage (NAS) module; in response to a user's operation of making a call, a third message is sent, including: in response to the user's operation of making a call, the CM module transmits the third message to the NAS module; the NAS module sends the third message; a fourth message is received, including: the NAS module receives the fourth message; the NAS module transmits a fourteenth message to the CM module, and the fourteenth message is used to indicate the rejection of the third message; a ninth message is received, including: the NAS module receives the ninth message; the NAS module transmits the ninth message to the CM module; in response to the ninth message and the fourth message, a first call is initiated, including: the CM module, in response to the ninth message and the fourteenth message, instructs the NAS module to initiate the first call; the NAS module initiates the first call.

[0042] For the terminal device to send the third message, reference can be made to Figure 7 S703 and S704 in. For the terminal device to receive the fourth message, reference can be made to Figure 7 S705 and S706 in. The fourteenth message can refer to the first service rejection message in S706. It should be noted that the fourteenth message may be the same as or different from the fourth message, and the embodiments of the present application do not limit this.

[0043] For initiating the first call in response to the ninth message and the fourth message, reference can be made to Figure 7 S713 and S714 in.

[0044] In this way, the CM module can initiate a call when the third message is rejected and the registration is successful, and achieve the call through multiple attempts, which is beneficial to improving the success rate of the call.

[0045] In a possible implementation, the terminal device includes a connection management CM module and a network attached storage NAS module; in response to a user's operation of making a call, a third message is sent, including: in response to the user's operation of making a call, the CM module transmits the third message to the NAS module; the NAS module sends the third message; a fourth message is received, including: the NAS module receives the fourth message; a ninth message is received, including: the NAS module receives the ninth message; in response to the ninth message, a first call is initiated, including: the NAS module, in response to the ninth message, transmits a fifteenth message to the CM module, and the fifteenth message is used to indicate the acceptance of the third message; the CM module, in response to the fifteenth message, instructs the NAS module to initiate the first call; the NAS module initiates the first call.

[0046] For the terminal device to send the third message, reference can be made to Figure 9S903 and S904 in. The terminal device receives the fourth message and can refer to Figure 9 S905 in. The terminal device receives the ninth message and can refer to Figure 9 The successful re-registration in.

[0047] In response to the ninth message, initiate the first call and can refer to Figure 9 S907 and S909 in. The fifteenth message can refer to Figure 9 The first service acceptance message in.

[0048] The CM module can initiate a call when the third message is received. In this way, without replacing the network device to implement a call, the CM module does not need to know that re-registration has been performed, reducing unnecessary steps and facilitating the improvement of processing efficiency.

[0049] In a second aspect, an embodiment of the present application provides a communication device, which may be a terminal device, or a chip or a chip system in the terminal device. The communication device may include a sending unit and a receiving unit. The sending unit is used to perform the sending step, and the transceiver unit is used to perform the receiving step, so that the communication device implements a communication method described in the first aspect or any one of the possible implementation manners of the first aspect. When the communication device is a terminal device, the sending unit and the receiving unit may be communication interfaces. The communication device may further include a storage unit, and the storage unit may be a memory. The storage unit is used to store instructions, and the sending unit and the receiving unit execute the instructions stored in the storage unit, so that the communication device implements a communication method described in the first aspect or any one of the possible implementation manners of the first aspect. The communication device may also be a chip or a chip system in the terminal device to implement a communication method described in the first aspect or any one of the possible implementation manners of the first aspect.

[0050] Exemplarily, the sending unit is used to send a first message, and the first message includes REGISTER information; the receiving unit is used to: receive a second message, and the second message includes REGISTER / 200OK information, and the second message is used to respond to the first message; the sending unit is further used to: in response to the operation of the user making a call, send a third message, and the third message includes SERVICEREQUEST information; the receiving unit is further used to: receive a fourth message, and the fourth message includes SERVICE REJECT information and #10IMPLICITLY DETACHED information, and the fourth message is used to respond to the third message; the sending unit is further used to: in response to the fourth message, send a fifth message, and the fifth message includes ATTACH REQUEST information; wherein, before sending the fifth message, a sixth message including ACCESS REQUEST information is not sent.

[0051] In a possible implementation, the receiving unit is further configured to: receive a seventh message, where the seventh message includes ATTACH ACCEPT information and IMS MODE SUPPORTED information, and the seventh message is used to respond to the fifth message; the sending unit is further configured to: send an eighth message, where the eighth message includes REGISTER information; the receiving unit is further configured to: receive a ninth message, where the ninth message includes REGISTER / 200OK information, and the ninth message is used to respond to the eighth message; the sending unit is further configured to: in response to the ninth message, initiate a first call.

[0052] In a possible implementation, the sending unit is further configured to: in response to the ninth message and the fourth message, initiate a first call.

[0053] In a possible implementation, the sending unit is further configured to: in the case where the first call is unsuccessful, send a sixth message.

[0054] In a possible implementation, the receiving unit is further configured to: receive a tenth message, where the tenth message includes REJECT information, and the tenth message is used to respond to the fifth message; the sending unit is further configured to: in response to the tenth message, send a sixth message.

[0055] In a possible implementation, the receiving unit is further configured to: receive an eleventh message, where the eleventh message includes ATTACH ACCEPT information, and the eleventh message is used to respond to the sixth message; the sending unit is further configured to: in response to the eleventh message, initiate a second call.

[0056] In a possible implementation, the above REGISTER information is IMSSIPREGISTER information.

[0057] In a possible implementation, the sending unit is further configured to: send a twelfth message, where the twelfth message includes ATTACH REQUEST information; the receiving unit is further configured to: receive a thirteenth message, where the thirteenth message includes ATTACH ACCEPT information and IMS MODE SUPPORTED information, and the thirteenth message is used to respond to the twelfth message.

[0058] In a possible implementation, the communication device further includes a display unit, and the display unit is configured to: in response to the second message, display an icon including HD information.

[0059] In a possible implementation, the method further includes: in response to the second message, set the registration status of IMS to IMS registered.

[0060] In a possible implementation, the fifth message is used to request registration on the first network device; the sixth message is used to request access to the second network device. The first network device is the device registered through the first message, and the first network device is different from the second network device.

[0061] In a possible implementation, the first message is used to request registration on the first network device; the second message is used to indicate acceptance of the request of the first message; the third message is used to request to establish a communication link with the first network device; the fourth message is used to indicate implicit separation.

[0062] In a possible implementation, the communication device further includes a processing unit; the processing unit is configured to: in response to a user's operation of making a call, transmit the third message to the sending unit; the sending unit is further configured to: after receiving the transmitted third message, send the third message; the receiving unit is configured to: when receiving the fourth message; transmit the fourteenth message to the processing unit, and the fourteenth message is used to indicate rejection of the third message; when the receiving unit receives the ninth message, the receiving unit is further configured to: transmit the ninth message to the processing unit; the processing unit is further configured to: in response to the ninth message and the fourteenth message, instruct the sending unit to initiate a first call; the sending unit is further configured to: initiate the first call.

[0063] In a possible implementation, the communication device further includes a processing unit; the processing unit is configured to: in response to a user's operation of making a call, transmit the third message to the sending unit; the sending unit is further configured to: after receiving the transmitted third message, send the third message; the receiving unit is configured to: receive the fourth message; the receiving unit is further configured to: receive the ninth message; and in response to the ninth message, send the fifteenth message to the processing unit, and the fifteenth message is used to indicate acceptance of the third message; the processing unit is further configured to: in response to the fifteenth message, instruct the sending unit to initiate a first call; the sending unit is further configured to: initiate the first call.

[0064] In a third aspect, an embodiment of the present application provides a terminal device, including a processor and a memory. The memory is used to store code instructions, and the processor is used to run the code instructions to execute the method described in the first aspect or any possible implementation manner of the first aspect.

[0065] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction runs on a computer, the computer is caused to execute the method described in the first aspect or any possible implementation manner of the first aspect.

[0066] Fifth aspect, an embodiment of the present application provides a computer program product including a computer program. When the computer program runs on a computer, it causes the computer to execute the method described in the first aspect or any possible implementation manner of the first aspect.

[0067] Sixth aspect, the present application provides a chip or a chip system. The chip or the chip system includes at least one processor and a communication interface. The communication interface and the at least one processor are interconnected by a line. The at least one processor is configured to run a computer program or instruction to execute the method described in the first aspect or any possible implementation manner of the first aspect. Among them, the communication interface in the chip can be an input / output interface, a pin, a circuit, etc.

[0068] In a possible implementation, the chip or the chip system described above in the present application further includes at least one memory, and instructions are stored in the at least one memory. The memory can be a storage unit inside the chip, such as a register, a cache, etc., or it can be a storage unit of the chip (such as a read-only memory, a random access memory, etc.).

[0069] Seventh aspect, an embodiment of the present application provides a communication system, including a terminal device and a network device. The terminal device and the network device communicate with each other to execute the method described in the first aspect or any possible implementation manner of the first aspect. Among them, the network device can include one or more terminal devices.

[0070] It should be understood that the second aspect to the seventh aspect of the present application correspond to the technical solutions of the first aspect of the present application. The beneficial effects obtained by each aspect and the corresponding feasible implementation manners are similar and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] Figure 1 is a schematic diagram of a communication system applicable to an embodiment of the present application;

[0072] Figure 2 is a schematic diagram of the hardware structure of a terminal device provided by an embodiment of the present application;

[0073] Figure 3 is a schematic diagram of the hardware structure of a SoC provided by an embodiment of the present application;

[0074] Figure 4 is a schematic diagram of the software architecture of a terminal device provided by an embodiment of the present application;

[0075] Figure 5 is a schematic diagram of the module interaction of a communication method provided by an embodiment of the present application;

[0076] Figure 6It is a schematic diagram of an interface for making a call provided by an embodiment of the present application;

[0077] Figure 7 It is a schematic diagram of module interaction of another communication method provided by an embodiment of the present application;

[0078] Figure 8 It is another schematic diagram of an interface for making a call provided by an embodiment of the present application;

[0079] Figure 9 It is a schematic diagram of module interaction of yet another communication method provided by an embodiment of the present application;

[0080] Figure 10 It is a schematic flowchart of a communication method provided by an embodiment of the present application;

[0081] Figure 11 It is a schematic block diagram of a chip system provided by an embodiment of the present application. Detailed implementation manners

[0082] For the convenience of clearly describing the technical solutions of the embodiments of the present application, the following explanations are made first:

[0083] In the embodiments of the present application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and roles. For example, the first service rejection message and the second service rejection message are only used to distinguish different service rejection messages, and do not limit their sequence. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and terms such as "first" and "second" do not necessarily mean different.

[0084] It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly, using words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.

[0085] In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the relationship between associated objects and indicates that three relationships may exist. For example, A and / or B may represent the cases of A alone, A and B existing simultaneously, and B alone, where A and B may be singular or plural. The character " / " generally indicates an "or" relationship between the associated objects before and after. "At least one (item)" or a similar expression thereof refers to any combination of these items, including any combination of a single item or multiple items. For example, at least one (item) of a, b, or c may represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c may be single or multiple.

[0086] It should be noted that in the embodiments of the present application, "when..." may be at the instant when a certain situation occurs or within a period of time before and after the occurrence of a certain situation. The embodiments of the present application do not make specific limitations in this regard. In addition, the display interface provided in the embodiments of the present application is only an example, and the display interface may also include more or less content.

[0087] It should be noted that the explanations of the signaling and terms in the embodiments of the present application may also refer to the explanations in the standards and protocols of the 3rd generation partnership project (3GPP), such as 24.229, RFC3261, RFC3262, and 23.401. The capitalization and spaces of the letters in the signaling in the present application are only for example, and the specific regulations shall be subject to the standards and protocols.

[0088] The terminal device involved in the embodiments of this application can be a terminal device with transceiver functions, or a chip or chip system that can be set in the terminal device. The terminal device can also be referred to as a user equipment (UE), access terminal, subscriber unit, user station, mobile station (MS), mobile phone, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in the embodiments of this application can be a mobile phone, cellular phone, smart phone, tablet computer (Pad), wireless data card, personal digital assistant (PDA), wireless modem, handset, laptop computer, machine type communication (MTC) terminal, computer with wireless transceiver function, virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self-driving, etc. The terminal device in the embodiments of this application can also be an in-vehicle module, in-vehicle module group, in-vehicle component, in-vehicle chip, or in-vehicle unit built into a vehicle as one or more components or units. In some examples, the terminal device can also be simply referred to as a terminal.

[0089] The network device involved in the embodiments of this application may also be referred to as a network apparatus, and the embodiments of this application do not make any limitations thereto. In some examples, the network device may be an access network (AN) device, or may be referred to as a radio access network (RAN) device. The RAN device may provide an access function for the terminal device and is responsible for functions such as radio resource management, quality of service (QoS) management, data compression, and encryption on the air interface side. The RAN device may include 5G, such as the gNB in the NR system, or one or a group (including multiple antenna panels) of antenna panels of the base station in 5G, or may also be a network node constituting the gNB, transmission and reception point (TRP or transmission point, TP), or transmission measurement function (TMF), such as a building base band unit (BBU), or a centralized unit (CU) or a distributed unit (DU), an RSU with base station functions, or a wired access gateway, or a core network element of 5G. Or, the RAN device may also include an access point (AP) in a wireless fidelity (WiFi) system, a wireless relay node, a wireless backhaul node, various forms of macro base stations, micro base stations (also referred to as small stations), relay stations, access points, wearable devices, vehicle-mounted devices, and so on. Or, the RAN device may also include an access network device for the next-generation mobile communication system, such as a 6G base station. Or, in the next-generation mobile communication system, the network device may also have other naming methods, all of which are covered within the protection scope of the embodiments of this application, and this application does not make any limitations thereto.

[0090] To better understand the embodiments of this application, the terms involved in the embodiments of this application will be introduced first.

[0091] 1. Long Term Evolution (LTE) network registration and New Radio (NR) network registration

[0092] LTE network registration means that a terminal device (such as a mobile phone, a tablet computer, etc.) connects to the network device of the operator through the LTE network.

[0093] NR network registration means that a terminal device connects to the network device of the operator through the NR network.

[0094] Among them, both LTE camping on network and NR camping on network include a series of actions including cell selection and registration.

[0095] 2. Domain switching

[0096] In the embodiments of the present application, domain switching may refer to a terminal device changing the mobile communication technology. For example, changing from the sixth-generation mobile communication technology (6G) to the fifth-generation mobile communication technology (5G), from 5G to the fourth-generation mobile communication technology (4G), from the second-generation mobile communication technology (2G) to the third-generation mobile communication technology (3G), etc.

[0097] In the embodiments of the present application, domain switching may also refer to a terminal device switching from the Internet Protocol Multimedia Subsystem (IMS) to the Circuit Switched (CS) domain, or from the CS domain to the IMS domain, or from the Packet Switched (PS) domain to the CS domain, or from the CS domain to the PS domain. Among them, the IMS domain mainly serves multimedia communication, the CS domain mainly serves traditional voice communication and SMS services, and the PS domain mainly serves voice communication.

[0098] The domain switching in the embodiments of the present application may also refer to the terminal device changing the communication mode. For example, switching from an NR network to an LTE network, or from an LTE network to an NR network, or from an LTE network to a universal mobile telecommunications system (UMTS) network, or switching from a UMTS network to an LTE network, or from a UMTS network to a global system for mobile communications (GSM) network, or from a GSM network to a UMTS network. Among them, the LTE network can meet the standards of a 4G network, the NR network can meet the standards of a 5G network, the UMTS network can meet the standards of a 3G network, and the GSM network can meet the standards of a 2G network.

[0099] It can be understood that domain switching is only an example name and can also be called changing the communication mode, or changing the frequency. The embodiments of the present application do not limit this. In some cases, the implementation method of domain switching can be that a network device, such as an access network device, according to the current actual communication situation, instructs the terminal device to switch from the currently camped network to another network, so as to facilitate the terminal device to obtain better communication quality. Among them, the switching and camping of the network can include the switching between different system networks. For example, the LTE network and the NR network are networks of different systems. In specific implementation, the access network device can instruct the terminal device to switch and camp to a new network through any one of the schemes such as network blind redirection, measurement-based redirection, or measurement-based cell handover.

[0100] 3. Cell

[0101] A cell may refer to the area within the wireless coverage of a network device. Within this area, the terminal device can communicate with the network device reliably through wireless signals. It can be understood that the coverage of each network device can be divided into one or more cells, and each cell can correspond to one or more frequency points. It can also be understood that each cell is the area formed by the coverage of one or more frequency points.

[0102] In some embodiments of the present application, different cells may correspond to the same network device. That is to say, the network device to which the first cell belongs and the network device to which the second cell belongs may be the same network device. For example, the first cell and the second cell may be managed by the same base station. In this case, it can be called that the first cell and the second cell share a station.

[0103] In some embodiments of the present application, different cells may correspond to different network devices. That is to say, the network device to which the first cell belongs and the network device to which the second cell belongs may be different network devices. For example, the first cell and the second cell may be managed by different network devices.

[0104] 4. Cell Handover (HO)

[0105] Cell handover may refer to the process of migrating the communication link between the terminal device and the current network device to another network device. In a wireless communication system, when the terminal device moves or approaches from one cell to another cell, in order to keep the communication of the terminal device uninterrupted, handover is required.

[0106] In some examples, the terminal device may repeatedly handover between different cells.

[0107] Exemplarily, Figure 1 shows a schematic diagram of a communication system that repeatedly handovers between different cells. As Figure 1 shown, taking the terminal device as a mobile phone and the network device as a base station as an example. The current location of the terminal device can be covered by the first cell, the second cell, and the third cell at the same time. When the terminal device needs to perform wireless communication, it can select one of the first cell, the second cell, and the third cell to camp on to achieve access to the network (such as an LTE network or an NR network). In some implementations, the first cell may correspond to the first network device, the second cell may correspond to the second network device, and the third cell may correspond to the third network device. In the embodiments of the present application, the cell where the terminal device currently camps may be referred to as the serving cell. The cell adjacent to the serving cell and whose coverage range includes the current location of the terminal device is called the neighbor cell. The terminal device may repeatedly handover between the serving cell and the neighbor cell, that is, repeatedly handover between the first cell, the second cell, and the third cell.

[0108] It can be understood that Figure 1 is only a simplified schematic diagram for easy understanding. Other network devices and / or other terminal devices may also be included in this communication system, Figure 1 which are not drawn in the figure.

[0109] In some embodiments, the terminal device in the above communication system may access the communication network (such as a 5G network) corresponding to the network device through the network device. In this way, the terminal device may enable various communication services based on the accessed communication network. Exemplarily, the communication services may include call services. Among them, the call service may be a call based on a 5G communication system, such as a VoNR call, or a call based on a 4G communication system, or a call based on a future communication system (such as a 6G communication system).

[0110] After the terminal device detects a SIM card or an eSIM card, it can camp on the network, such as camping on an LTE network or an NR network. After successful network camping, the terminal device can support functions such as voice calls, video calls, and using mobile data. In some scenarios, the terminal device may experience unsuccessful calls, affecting the user experience.

[0111] When the network signal of the terminal device is poor, the terminal device has a temporary fault, or repeatedly switches between different cells, the terminal device and the network device cannot interact normally, and the network device may use the Implicitly Detached method to update the status of the terminal device in the network device to De-Registered or Unregistered. Among them, Implicit Detachment can refer to the network device separating from the terminal device without notifying the terminal device. Implicit Detachment can occur when the network device assumes that it cannot communicate with the terminal device. Among them, the separation between the network device and the terminal device can refer to the disconnection of the communication link between the network device and the terminal device.

[0112] In some implementations, when the terminal device is at the edge of the coverage area of the network device, there may be a poor network signal. The terminal device may not respond to the message sent by the network device due to the poor network signal, and the network device may use the Implicitly Detached method to update the status of the terminal device to De-Registered.

[0113] Exemplarily, in the above Figure 1 shown communication system, the serving cell of the terminal device is the first cell. When the terminal device is at the edge of the first cell, there may be a poor network signal. The terminal device may not respond to the message sent by the first network device due to the poor network signal, and the first network device may use the Implicitly Detached method to update the status of the terminal device to De-Registered.

[0114] In some implementations, a temporary fault of the terminal device can mean that the terminal device is not successfully awakened when it is in the sleep state, or uses the wrong decoding method to decode the received message. The terminal device may not be able to respond to the message sent by the network device due to the temporary fault, and the network device may use the Implicitly Detached method to update the status of the terminal device to De-Registered.

[0115] Exemplarily, in the above Figure 1 shown communication system, the serving cell of the terminal device is the first cell. After the terminal device receives a message from the first network device, the terminal device uses the wrong decoding method to decode the received message, resulting in not obtaining the content in the message, and thus not responding to the message sent by the first network device in a timely manner. The first network device may use the Implicitly Detached method to update the status of the terminal device to De-Registered.

[0116] In some implementations, when the terminal device repeatedly switches between different cells, the network device repeatedly changes the state of the terminal device to deregistered. In some cases, the state of the terminal device may be updated to deregistered using the method of implicit detachment.

[0117] Exemplarily, in the communication system shown above Figure 1 The serving cell of the terminal device is the first cell. The terminal device switches from the first cell to the second cell, then from the second cell back to the first cell, then from the first cell to the third cell, and then from the third cell back to the first cell. The first network device corresponding to the first cell repeatedly changes the state of the terminal device to deregistered. In some cases, the state of the terminal device may be updated to deregistered using the method of implicit detachment.

[0118] In the case of implicit detachment, since the network device does not notify the terminal device that it has been detached from the network device, the terminal device cannot know that it is in a deregistered state with the network device. Therefore, in some implementations, when the terminal device detects that the user has a call requirement, the terminal device may send a Service request message to the network device to establish a link with the network device, but will receive a Service reject message from the network device, and the message carries the rejection reason as #10 Implicitly detached, ultimately resulting in an unsuccessful call by the terminal device.

[0119] When the terminal device encounters an unsuccessful call situation, it will cause a low success rate of the terminal device's call. To solve this problem, the embodiments of the present application provide the following one or more communication methods:

[0120] 1) When receiving a service reject message and the service reject message carries the rejection reason as #10 Implicitly detached, the terminal device can perform a domain switch, for example, switch from the IMS domain to the CS domain, and make a new call on the new domain, which is beneficial to improving the success rate of the call and enhancing the user experience.

[0121] 2) When receiving a service reject message and the service reject message carries the rejection reason as #10 Implicitly detached, the terminal device can perform re-registration. In the case of successful re-registration, make a call, which is beneficial to improving the success rate of the call and enhancing the user experience.

[0122] The communication methods provided by the embodiments of the present application can be applied to terminal devices, such as devices like mobile phones or tablets. For the sake of easy understanding, the terminal devices provided by the embodiments of the present application will be introduced first.

[0123] Figure 2 This is a schematic diagram of the hardware structure of a terminal device provided by an embodiment of the present application. As Figure 2 shown, the terminal device 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 (MIC) 170C, a headphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0124] Optionally, the above-mentioned sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric 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.

[0125] It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the terminal device. In other embodiments of the present application, the terminal device may include more or fewer components than shown, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

[0127] The operating system running on the AP can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. The layered architecture can adopt the Android system, the iOS system, or other operating systems, which are not limited in the embodiments of the present application.

[0128] The Modem can also be referred to as a baseband processor (BP). The Modem can include modules such as a protocol stack for cellular communication and a physical layer for cellular communication, and can implement functions such as modulation and demodulation, channel encoding and decoding, and source encoding and decoding. Among them, the cellular protocol stack can include a connection management (CM) module, a call control (CC) module, and a network attached storage (NAS) module. The CM module can dynamically establish, modify, and release connections in the communication network, and can mainly process call-related data, such as routing, resource allocation, and session management. The CM module can dynamically adjust the call path according to the real-time network status and user requirements to ensure the best communication quality and performance. The CC module is mainly responsible for establishing, maintaining, and releasing call connections during the communication process, and can involve the processing of various protocols and signaling to ensure the stability and reliability of the communication link. The NAS module can perform operations such as network registration to achieve communication with network devices. It should be noted that the NAS module is only an example name, which is not limited in the embodiments of the present application.

[0129] The Modem in the embodiments of the present application can provide cellular communication capabilities. The Modem runs on a baseband chip and a coprocessor, and the terminal device can implement a series of cellular communication functions such as sending and receiving text messages, 5G-related functions, making calls, and answering calls through the Modem.

[0130] The SIM card interface 195 is used to insert a SIM card. The SIM card described in the embodiments of the present application can be understood as a module that provides user information in the cellular network or uses the mobile cellular network. For example, a terminal device with a SIM card slot and a card reader can register the mobile cellular network by inserting a SIM card. Among them, the SIM card can be a physical card (or called a hard card), or a virtual SIM card (or called a soft card), such as an eSIM, etc. The specific form of the SIM card is not limited in the embodiments of the present application.

[0131] The IMS described in the embodiments of the present application is a general term for the logical function entities in the network core layer that control IP multimedia services. The IMS services can include: IMS information services, IMS call services, etc.

[0132] In some implementations, the AP and the Modem can be integrated on a system on chip (SoC). The SoC can use the user information provided by the SIM card to implement cellular communication through radio frequency (RF) components and antennas (such as the Figure 2 antenna 1 shown above). Among them, the SoC is also called a system-level chip, which integrates the chips required for the operation of the operating system of the terminal device on one chip.

[0133] Exemplarily, Figure 3 shows a schematic structural diagram of an SoC. As Figure 3 shown, the SoC includes the capabilities of the AP and the Modem. Among them, the AP is used to process the internal data of the terminal device, excluding the part related to external communication. The Modem is used to process the part related to external communication, including handling services such as making calls, sending text messages, and accessing the Internet.

[0134] Moreover, a physical channel such as a shared memory or a bus is established between the AP and the Modem to achieve data transmission between the AP and the Modem, such as the transmission of data such as call content and text message content.

[0135] In Figure 3 the example, the Modem is integrated in the SoC. However, in actual implementation, the Modem can also exist in the form of an independent chip and be soldered to the main board of the terminal device together with the SoC. In the following text, mainly Figure 3 the form shown, that is, the Modem is integrated in the SoC, is taken as an example for illustration.

[0136] RF represents the electromagnetic frequency that can be radiated into space. The RF components are mainly used for the processing of receiving and transmitting signals in the wireless communication process.

[0137] The RF components can communicate with the cellular physical layer in the Modem, be used to receive the cellular baseband digital signal, perform digital-to-analog conversion processing on it and then transmit it through the antenna, and perform analog-to-digital conversion processing on the radio electromagnetic wave signal received by the antenna and then send it to the cellular baseband.

[0138] Taking the operating system running on the AP as the Android system as an example, the software architecture of the terminal device is exemplarily described below.

[0139] Figure 4 shows a schematic diagram of the software architecture of a terminal device. As Figure 4As shown, the Android system is a layered architecture, which divides the AP of the terminal device into several layers, each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system can be divided into multiple layers, from top to bottom, the application layer (applications), the application framework layer (application framework), the hardware abstraction layer (HAL), the kernel layer (kernel), and the Modem.

[0140] The application layer can include a series of application packages. The application layer runs applications by calling the application programming interface (API) provided by the application framework layer. Figure 4 As shown, the application package may include system UI, browser, phone, video and other applications.

[0141] The application framework layer provides API and programming framework for the applications in the application layer. The application framework layer includes some predefined functions. Figure 4 As shown, the application framework layer may include telephone / IMS services, CS phone (Phone) and PS Phone, etc.

[0142] Among them, the telephone / IMS service is used to call the modem to send and receive messages during the establishment of a media session and after the media session is established, that is, during the call, such as a call request message (such as INVITE), a confirmation message (such as ACK) received from the call request message, and a response message (such as 200OK) in response to the call request message.

[0143] Among them, CS Phone is used for calls on CS network. When IMS service is unavailable (terminal device resides in 2G / 3G or IMS registration is unsuccessful), calls can be made through CS calls. It can also be used for domain change and redialing when IMS call is unsuccessful (commonly known as CS redial).

[0144] Among them, PS Phone is used for calls on the PS network. When IMS services are available, IMS calls (VOLTE, VONR) can be made through the PS domain.

[0145] It should be understood that the above description is merely an example listed for a better understanding of the technical solution of this embodiment, and is not intended to be the sole limitation to this embodiment.

[0146] The purpose of the hardware abstraction layer (HAL) is to abstract the hardware, which can provide a unified interface for upper-layer applications to query hardware devices, or can also provide data storage services for upper-layer applications. As Figure 4 shown, the HAL layer may include a display driver module and a sensor hardware abstraction. The HAL layer can transmit information from the application framework layer to the kernel layer, or transmit information from the kernel layer to the application framework layer.

[0147] The kernel layer is the layer between hardware and software. In the technical solution provided by the embodiments of the present application, the kernel layer may include a transmission control protocol / internet protocol (TCP / IP) protocol stack.

[0148] Among them, TCP / IP may refer to a protocol suite capable of implementing information transmission between multiple different networks. In the embodiments of the present application, the TCP / IP STACK in the kernel layer can serve the Internet access service and can also provide services for data processing related to video during a call service.

[0149] The Modem may include a CM module, a CC module, and a NAS module. In the embodiments of the present application, when a phone application in the application layer responds to an operation of a user making a call, a call command can be received, and the phone application can transmit the call command to the Modem. The embodiments of the present application do not limit the specific transmission path of the call command. The CM module in the Modem can receive the call command and, based on the call command, can send a service request message to a network device through an antenna.

[0150] In some examples, if the NAS module receives a service rejection message from a network device through an antenna, and the service rejection message carries a rejection reason of #10 Implicitly detached, the NAS module can transmit the service rejection message to the CM module. Based on the service rejection message, the CM module can instruct the CC module to make a call, and the CC module can redial in a different domain to improve the success rate of the call.

[0151] In some other examples, if the NAS module receives a service rejection message from a network device via an antenna, and the service rejection message carries the rejection reason as #10 Implicitly detached, the NAS module can perform re-registration. After successful re-registration, it can transmit a message indicating successful re-registration to the CM module. Based on the message indicating successful re-registration, the CM module can make a call. If the re-registration fails, the NAS module can transmit a message indicating failed re-registration to the CM module. Based on the message indicating failed re-registration, the CM module can instruct the CC module to make a call, and the CC module can redial across domains to improve the success rate of the call.

[0152] It should be understood that in some embodiments, layers that perform the same function may be referred to by other names, or a layer that can perform the functions of multiple layers may be regarded as one layer, or a layer that can perform the functions of multiple layers may be divided into multiple layers. The embodiments of the present application do not limit this.

[0153] To better understand the method provided by the embodiments of the present application, the communication method provided by the embodiments of the present application will be described below.

[0154] The communication method provided by the embodiments of the present application can improve the success rate of call conversations by redialing across domains.

[0155] Exemplarily, Figure 5 shows a module interaction diagram of a communication method provided by the embodiments of the present application. This method can be applied to the communication system shown above Figure 1 but the embodiments of the present application are not limited thereto. As Figure 5 shown, the software architecture of the terminal device can be as shown above Figure 4 shown. The terminal device may include a phone application and a Modem. The Modem includes a CM module, a CC module, and a NAS module.

[0156] As Figure 5 shown, the method may include the following steps:

[0157] S501. The terminal device detects an operation of the user making a call.

[0158] Optionally, the terminal device may provide a control for the user to make a call. The user can trigger the control for making a call to make a call. For example, the phone application in the terminal device may be provided with a control for making a call. When the user triggers the control for making a call, the phone application in the terminal device can detect the operation of the user making a call.

[0159] The terminal device may include a first SIM card and / or a second SIM card. The first SIM card may correspond to a first telephone number, and the second SIM card may correspond to a second telephone number. In response to the user's operation of making a call, the terminal device may use the telephone number of the first SIM card or the second SIM card to make a call. The SIM card used by the terminal device for making a call may be the default one or set by the user, and the embodiments of the present application do not limit this. S502. In response to the user's operation of making a call, the phone application may transmit a call command to the CM module in the Modem.

[0160] The call command may be understood as indication information for making a call. In some examples, the call command may carry information such as the called party's call number and call domain. Among them, the call domain is used to indicate the domain used for making a call. The call domain may be the PS domain, the CS domain, or AUTO, where AUTO is used to indicate free selection without restricting the domain used for the call.

[0161] In the above Figure 4 In the software architecture shown, in response to the user's operation of making a call, when the IMS service is available, the phone application may instruct the PS phone to make a call. The PS phone may transmit a call command to the CM module in the Modem. Or, in response to the user's operation of making a call, when the IMS service is unavailable, the phone application may instruct the CS phone to make a call. The CS phone may transmit a call command to the CM module in the Modem.

[0162] Correspondingly, the CM module may receive the call command.

[0163] S503. After the CM module receives the call command, the CM module transmits a first service request message to the NAS module.

[0164] Optionally, the CM module sends a first service request message to the NAS module based on the call command.

[0165] The NAS module may have a pass-through function and may send the received first service request message to other devices.

[0166] Among them, the first service request message may include information of Service request. The first service request message may be a message sent by the terminal device when transitioning from the idle state to having a service requirement (such as a call service), and may be used to request the establishment of an uplink to send a signaling message (such as a call request message). It can be understood that the scenario where the terminal device is located is that it is idle for a period of time and the first service executed after ending the idle state is a phone call.

[0167] In some examples, if the call domain included in the call command is the PS domain, the CM module can, based on the call command, determine whether the network registered by the terminal device is an LTE network or an NR network. If the registered network is an LTE network or an NR network, it can instruct the NAS module to send a first service request message to the first network device in the PS domain.

[0168] In other examples, if the call domain included in the call command is the CS domain, the CM module can, based on the call command, determine whether the network registered by the terminal device is a UMTS network or a GSM network. If the registered network is a UMTS network or a GSM network, it can instruct the NAS module to send a first service request message to the first network device in the CS domain.

[0169] In still other examples, if the call domain included in the call command is AUTO, the CM module can, based on the call command, instruct the NAS module to preferentially send the first service request message on the network capable of transmitting at a higher frequency. When the terminal device supports a 6G or higher-level network, it can preferentially send the first service request message on the 6G or higher-level network. This is conducive to improving the communication rate and shortening the information transmission duration.

[0170] Correspondingly, the NAS module can receive the first service request message.

[0171] S504. After the NAS module receives the first service request message, the terminal device sends the first service request message to the first network device.

[0172] Optionally, the NAS module in the terminal device sends the first service request message to the first network device. For example, the NAS module in the terminal device sends the first service request message to the first network device based on the first service request message.

[0173] In the above Figure 1 In the communication system shown, the resident cell of the terminal device can be the first cell, and the terminal device can communicate with the first network device.

[0174] It should be noted that in the embodiments of the present application, the terminal device can include a first SIM card and / or a second SIM card, and the network used by the terminal device in the resident cell refers to the network currently registered by the terminal device based on the first SIM card and / or the second SIM card.

[0175] Correspondingly, the first network device receives the first service request message.

[0176] S505. After the first network device receives the first service request message, the first network device can send a first service rejection message to the terminal device, and the first service rejection message carries the information of #10 implicit detachment.

[0177] Since the status of the terminal device with respect to the first network device is logged out or unregistered, after receiving the first service request message, the first network device may send a first service rejection message to the terminal device, and the first service rejection message carries information about implicit detachment #10.

[0178] Optionally, based on the first service request message, the first network device may send a first service rejection message to the terminal device.

[0179] Among them, the first service rejection message may include information about "Service reject". The first service rejection message may carry the rejection reason: implicit detachment #10. The first service rejection message is used to reject the "Service request".

[0180] Optionally, the first service rejection message may carry information about "Service reject" and "cause_value = 10(0xa)(Implicitly detached)".

[0181] Correspondingly, the terminal device may receive the first service rejection message. Optionally, the NAS module in the terminal device may receive the first service rejection message.

[0182] S506. After the NAS module in the terminal device receives the first service rejection message, the NAS module may transmit the first service rejection message to the CM module.

[0183] Optionally, based on the first service rejection message, the NAS module may transmit the first service rejection message to the CM module.

[0184] The NAS module transmitting the first service rejection message to the CM module is used to indicate that the first service request message has been rejected.

[0185] In one example, the NAS module may have a pass-through function and may forward the received first service rejection message to the CM module.

[0186] S507. After the CM module receives the first service rejection message, the CM module transmits a call indication message to the CC module.

[0187] Optionally, based on the first service rejection message, the CM module transmits a call indication message to the CC module.

[0188] Based on the first service rejection message, the CM module determines that the call is unsuccessful and may transmit a call indication message to the CC module. The call indication information is used to instruct the CC module to make a call.

[0189] In some examples, after the CM module receives the first service rejection message, it can set a preset identifier to 0. When it detects that the preset identifier is 0, it can determine that the call is unsuccessful.

[0190] Correspondingly, the CC module receives an indication message for the call.

[0191] S508. After the CC module receives the indication message for the call, the CC module transmits indication information for network search to the NAS module. The indication information for network search is used to indicate searching for available network devices different from the first network device nearby.

[0192] Optionally, based on the indication message for the call, the CC module transmits indication information for network search to the NAS module.

[0193] The indication information for network search is used to indicate domain switching. For example, from NR to LTE, or from LTE to GSM.

[0194] Correspondingly, the NAS module can receive the indication information for network search.

[0195] S509. After the NAS module receives the indication information for network search, it performs a network search action.

[0196] Optionally, based on the indication information for network search, the NAS module performs a network search action.

[0197] S510. When the NAS module of the terminal device searches for a second network device, the terminal device sends an access request message to the second network device.

[0198] Optionally, the NAS module in the terminal device sends an access request message to the second network device.

[0199] Among them, the access request message is used to request access to the second network device. The access request message may include AccessRequest information. Optionally, the access request message may also carry information such as the identity identifier of the terminal device.

[0200] S511. After the second network device receives the access request message, it sends an access acceptance message to the terminal device.

[0201] Optionally, the second network device sends an access acceptance message to the terminal device based on the received access request message.

[0202] The access acceptance message may include an Access accept message, which is used to indicate successful access.

[0203] S512. After the NAS module in the terminal device receives the access acceptance message, it transmits indication information for accessing the second network device to the CC module.

[0204] Correspondingly, the CC module receives the indication information for accessing the second network device.

[0205] S513. After the CC module receives the indication information for accessing the second network device, the CC module sends a call establishment request message to the NAS module.

[0206] Optionally, based on the indication information for accessing the second network device, the CC module sends a call establishment request message to the NAS module.

[0207] Among them, the call establishment request message is used to initiate a call. Optionally, the call establishment request message may carry information such as the called party's phone number, voice coding format, and voice coding type.

[0208] Correspondingly, the NAS module receives the call establishment request message.

[0209] S514. After the NAS module receives the call establishment request message, the terminal device sends a call establishment request message to the second network device.

[0210] Optionally, based on the call establishment request message, the NAS module may send a call establishment request message to the second network device.

[0211] The NAS module may have a transparent transmission function and can send the received call establishment request message to the second network device.

[0212] Correspondingly, the second network device receives the call establishment request message.

[0213] After the second network device receives the call establishment request message, it can call the called party. If the call is successful, it can send a call success response message to the terminal device. If the call is not successful, it can send a response message carrying the error reason to the terminal device, or not send a response message to the terminal device.

[0214] If the terminal device receives the call success response message, it can determine that the call is successful. If the terminal device receives the response message carrying the error reason, or does not receive a response message within a certain period of time, it can determine that the call is not successful.

[0215] The process shown in the above S508 to S514 can be understood as cross-domain redialing. In the case where the terminal device fails to establish a link with the first network device through the first service request message, the terminal device can achieve a call through cross-domain redialing.

[0216] It should be noted that in the scenario where the terminal device includes a first SIM card and / or a second SIM card, when the terminal device makes a call using the first SIM card or the second SIM card, the SIM card will not be switched during the cross-domain redialing process.

[0217] During the execution of Figure 5 the method shown, the interface of the terminal device can be as Figure 6 shown. In response to the user's operation of opening the phone application, the terminal device can display a phone interface, as shown in Figure 6 interface a in Figure 6 In interface a in Figure 6 interface a, the phone interface includes a phone keypad, call information, and three controls. Among them, the call information includes the call date and the name of the caller. For example, a call is made with An'an on October 14th and a call is made with A Fa on October 9th. The three controls can include a phone control, a contacts control, and a favorites control. In Figure 6 interface a in

[0218] When the user triggers the An'an option, the terminal device can detect the user's operation of making a call. In response to the user's operation of making a call, it can display a dialing interface, as shown in Figure 6 interface b in Figure 6 In interface b in

[0219] During the process of the terminal device displaying Figure 6 interface b in Figure 6 it can execute the above S502 to S510. If it successfully accesses the second network device, it can display a 4G network on the interface, as shown in Figure 6 interface c in

[0220] When the terminal device receives a call success response message from the second network device, it will display that the other party is ringing on the interface, as shown in Figure 6 interface d in Figure 6 In interface d in

[0221] For the communication method provided by the embodiments of the present application, when receiving a first service rejection message and the first service rejection message carries a rejection reason of #10 implicit detachment, the terminal device can perform a call through cross-domain redialing, which is beneficial to improving the success rate of call communication and enhancing the user experience.

[0222] The above S506 is an example. In another example, after the NAS module receives the first service rejection message, it can analyze the rejection reason carried in the first service rejection message, so as to transmit different messages to the CM module according to different rejection reasons.

[0223] Exemplarily, if the rejection reason carried in the first service rejection message is #10 implicit separation, the NAS module can transmit a message with an identifier of 1 to the CM. After receiving the message with an identifier of 1, the CM module executes S507 based on the identifier 1. If the rejection reason carried in the first service rejection message is a reason other than #10 implicit separation, the NAS module can transmit a message with an identifier of 0 to the CM. After receiving the message with an identifier of 0, the CM module executes other processing methods based on the identifier 0.

[0224] In this way, the CM module can execute different processing methods in different scenarios, with stronger flexibility.

[0225] The above Figure 5 In the method shown above, when the terminal device receives the first service rejection message and the rejection reason carried in the first service rejection message is #10 implicit separation, it performs a cross-domain redial. The embodiment of the present application also provides a communication method, which can perform re-registration before the cross-domain redial, so that the state of the terminal device on the network device side is updated to registered. In this way, after the re-registration is successful, a re-call is made, which is beneficial to improving the success rate of the call.

[0226] In one possible implementation manner, Figure 7 shows a module interaction diagram of a communication method provided by an embodiment of the present application. This method can be applied to the above Figure 1 shown communication system, but the embodiment of the present application is not limited thereto. As Figure 7 shown, the software architecture of the terminal device can be as above Figure 4 shown.

[0227] As Figure 7 shown, this method may include the following steps:

[0228] S701 to S706 can refer to the above S501 to S506, and will not be elaborated here.

[0229] S707. After the CM module receives the first service rejection message, the CM module can determine that the call is unsuccessful.

[0230] Optionally, based on the first service rejection message, the CM module can determine that the call is unsuccessful. It should be noted that the unsuccessful call here can be understood as the rejection of the transmitted first service request message. The unsuccessful call can also be referred to as an unsuccessful request or a rejected request. The embodiment of the present application does not make any limitations in this regard.

[0231] In some examples, after the CM module receives the first service rejection message, it may set a preset identifier to 0. When detecting that the preset identifier is 0, it may determine that the call is unsuccessful.

[0232] S708. After the NAS module receives the first service rejection message, the NAS module may send an attach request message to the first network device, and the attach request message is used for attachment.

[0233] Among them, the attach request message may include the message of Attach request. Optionally, the attach request message may carry information of the attach request type (combined EPS / IMSI attach). In some examples, the attach request message may request to perform NR or LTE registration.

[0234] Correspondingly, the first network device may receive the attach request message.

[0235] S709. After the first network device receives the attach request message, the first network device may send an attach accept message to the terminal device.

[0236] Optionally, based on the attach request message, the first network device may send an attach accept message to the terminal device.

[0237] Among them, the attach accept message may include Attach accept information and IMS mode Suppoted information. In some examples, the attach accept message may include Attach accept information and IMS Vo PS Session in Simode Suppoted information. The attach accept message is used to indicate acceptance of the attach request message and support for IMS registration.

[0238] S710. After the terminal device receives the attach accept message, it may send a registration request message to the first network device, and the registration request message is used to request IMS registration on the first network device.

[0239] Optionally, after the NAS module in the terminal device receives the attach accept message, it may send a registration request message to the first network device. In some examples, the NAS module sends a registration request message to the first network device based on the attach accept message.

[0240] When the terminal device receives the attach accept message, it can indicate that the attachment is successful, and the terminal device can continue the registration process, that is, it can send a registration request message to the first network device.

[0241] The registration request message may include Register information. In some examples, the registration request message may include IMS_SIP_REGISTER information.

[0242] S711. After the first network device receives the registration request message, the first network device may send a registration acceptance message to the terminal device.

[0243] Optionally, based on the registration request message, the first network device sends a registration acceptance message to the terminal device.

[0244] The registration acceptance message may include Register / OK(200) information. This registration acceptance message is used to indicate successful registration. When the terminal device receives the registration acceptance message, it can determine that the registration is successful. Among them, OK(200) can also be expressed as OK200, (200)OK, or 200OK, etc. The embodiments of the present application do not limit this.

[0245] Other steps may or may not be included between S710 and S711. The embodiments of the present application do not limit this.

[0246] In some examples, after S710, the terminal device receives a reply message in response to the registration request message, and this reply message in response to the registration request message is used to indicate that authentication is required for registration. Then the terminal device may send a registration request carrying authentication to the first network device. If the terminal device receives a registration acceptance message in response to the registration request carrying authentication, it can determine that the re-registration is successful.

[0247] Among them, the reply message in response to the registration request message may include UNAUTHORIZED(401) information. The registration request carrying authentication may include IMS_SIP_REGISTER information. The registration acceptance message in response to the registration request carrying authentication may include OK(200) information.

[0248] The above S708 to S710 can be understood as the terminal device performing re-registration.

[0249] It can be understood that the terminal device may send a first service request message to the first network device, which can indicate that the terminal device has been registered. After the NAS module in the terminal device receives the first service rejection message and then performs registration again, it can be called re-registration, that is, re-registration is used to indicate that it has been registered before and needs to be registered again. The steps executed by the NAS module are the same as those for previous registration.

[0250] Exemplarily, for the registration previously performed by the NAS module using the LTE network, after receiving the first service rejection message, the NAS module may use the LTE network to perform re-registration. Alternatively, for the registration previously performed by the NAS module using the NR network, after receiving the first service rejection message, the NAS module may use the NR network to perform re-registration. If the re-registration is successful, the NAS module may execute S709. If the re-registration fails, the NAS module may execute S718.

[0251] Optionally, based on the first service rejection message, the NAS module may perform re-registration, that is, execute S708 to S710 described above.

[0252] S706 and S708 may be executed simultaneously or sequentially. The embodiments of the present application do not make any limitation in this regard.

[0253] S712. After receiving the registration acceptance message, the NAS module in the terminal device may transmit a message indicating successful re-registration to the CM module.

[0254] Among them, the message indicating successful re-registration is used to indicate that the re-registration is successful. Optionally, the message indicating successful re-registration may include information on the current network registration status. For example, the message indicating successful re-registration includes service rat = NR / LTE / GSM / UMTS, which is used to indicate that the current network registration status is the registered NR network, LTE network, GSM network, or UMTS.

[0255] When the call is unsuccessful and the NAS module receives the message indicating successful re-registration, it may execute S713.

[0256] Correspondingly, the CM module receives the message indicating successful re-registration.

[0257] S713. After the CM module receives the message indicating successful re-registration, the CM module transmits a call establishment request message to the NAS module.

[0258] The call establishment request message may refer to S513 described above and will not be elaborated here.

[0259] S714. After the NAS module receives the call establishment request message, the terminal device sends a call establishment request message to the first network device, and this call establishment request message is used to initiate a call.

[0260] Optionally, based on the call establishment request message, the NAS module may send a call establishment request message to the first network device.

[0261] Correspondingly, the first network device receives the call establishment request message.

[0262] S715. In the case of a call failure, the NAS module transmits a call failure message to the CM module.

[0263] S716. After receiving the call failure message, the terminal device performs cross-domain redialing, which can refer to the above S508 to S514 and will not be elaborated here.

[0264] S718. If the re-registration fails, the NAS module transmits a re-registration failure message to the CM module.

[0265] The re-registration failure message is used to indicate that the re-registration fails. If the terminal device does not receive the above registration acceptance message, the re-registration fails.

[0266] Optionally, the re-registration failure message may include limit unknown information, which is used to indicate that the registration is not successful.

[0267] The NAS module executes S719 when the call is unsuccessful and the re-registration failure message is received.

[0268] Correspondingly, the CM module receives the re-registration failure message.

[0269] S719 and S720 can refer to S507 to S514 shown above Figure 5 and will not be elaborated here.

[0270] It should be noted that in the scenario where the terminal device includes the first SIM card and / or the second SIM card, when the terminal device makes a call using the first SIM card or the second SIM card, the SIM card will not be switched during the re-registration and cross-domain redialing processes.

[0271] During the execution of Figure 7 the method shown, the interface change of the terminal device can be as shown in Figure 8 When the terminal device responds to the user's operation of opening the phone application, it can display a phone interface, as shown in interface a in Figure 8 In interface a in Figure 8 the terminal device displays an HD icon and a 5G network 801, which can indicate that the terminal device can communicate with the first network device through the 5G network using the SIM card. When the terminal device responds to the user's operation of making a call, it can display a dialing interface, as shown in interface b in Figure 8 During the process of the terminal device displaying interface b in

[0272] the terminal device can execute the above S702 to S706. If it performs re-registration based on the first service rejection message, during the re-registration process, the 5G network 801 does not display and no service 802 is shown, as shown in Figure 8 In Figure 8as shown in the c interface in

[0273] If the re-registration is successful, the terminal device redisplays the 5G network 801, as Figure 8 shown in the d interface in Figure 6 and executes the above S712 to S714. It can be understood that if the re-call is successful, it is shown on the interface that the other party is ringing. If the re-registration fails, the terminal device can execute the above S718 to S720 and display the

[0274] c interface in

[0275] In another possible implementation, Figure 9 FIG. shows a module interaction diagram of another communication method provided by an embodiment of the present application. This method can be applied to the above Figure 1 shown communication system, but the embodiments of the present application are not limited thereto. As Figure 9 shown, the software architecture of the terminal device can be as shown in the above Figure 4 shown. The terminal device includes a phone application and a Modem. The Modem includes a CM module, a CC module, and a NAS module.

[0276] As Figure 9 shown, this method may include the following steps:

[0277] The implementation manners of S901 to S905 can refer to the above S501 to S505 and will not be elaborated here.

[0278] S906 can refer to the above S708 to S710 and will not be elaborated here.

[0279] S907. If the re-registration is successful, the NAS module transmits a first service acceptance message to the CM module.

[0280] The first service acceptance message is used to respond to the first service request message and is used to indicate acceptance of the first service request message, that is, it indicates that a link has been established with the first network device.

[0281] Correspondingly, the CM module receives the first service acceptance message.

[0282] After the CM module receives the first service acceptance message, the terminal device can execute S908 and S909. Among them, S908 and S909 are used to initiate a call, which can be understood as the first call based on a call command. S908 and S909 can refer to S713 and S714 shown above Figure 7 and will not be elaborated here.

[0283] If the call fails, the terminal device can execute S910 to S912 for a second call. S910 to S912 can refer to S715 and S717 shown above Figure 7 and will not be elaborated here.

[0284] S913. If the re-registration fails, the NAS module transmits a second service rejection message to the CM module.

[0285] The second service acceptance message is used to respond to the first service request message and indicates the rejection of the first service request message, that is, it indicates that no link is established with the first network device.

[0286] Correspondingly, the CM module receives the second service rejection message.

[0287] After the CM module receives the second service rejection message, the terminal device can execute S914 and S915. Among them, S914 and S915 can refer to S507 and S514 shown above Figure 5 and will not be elaborated here.

[0288] It should be noted that in the scenario where the terminal device includes a first SIM card and / or a second SIM card, when the terminal device makes a call using the first SIM card or the second SIM card, the SIM card will not be switched during the re-registration and cross-domain redialing processes.

[0289] During the execution of Figure 9 the method shown above, the interface change of the terminal device can be as shown above Figure 8 and will not be elaborated here.

[0290] For the communication method provided by the embodiments of the present application, when receiving the first service rejection message and the rejection reason carried in the first service rejection message is #10 implicit detachment, the terminal device can perform re-registration. In the case of successful re-registration, a call is made, which is beneficial to improving the success rate of the call and enhancing the user experience. In addition, in the case of failed re-registration, cross-domain redialing is performed and multiple attempts are made, which is beneficial to increasing the probability of call success.

[0291] The method provided by the embodiments of the present application can also be applied to the Internet access scenario.

[0292] Exemplarily, in response to the user's operation of querying a web page, the browser application can receive an Internet access command. The browser application can transmit the Internet access command to the Modem. The CM module in the Modem can receive the Internet access command and, based on the Internet access command, send a first service request message to the first network device.

[0293] In some examples, if the NAS module in the Modem receives a first service rejection message from the first network device, and the first service rejection message carries the rejection reason as #10Implicitly detached, the NAS module can transmit the first service rejection message to the CM module. Based on the first service rejection message, the CM module can instruct the CC module to access the Internet. The CC module can change the domain and send a message requesting Internet access to the second network device to improve the success rate of Internet access.

[0294] In other examples, if the NAS module in the Modem receives a service rejection message from the first network device, and the first service rejection message carries the rejection reason as #10Implicitly detached, the NAS module can perform re-registration. After the re-registration is successful, it can send a message requesting Internet access to the first network device. If the re-registration fails, the NAS module can transmit the first service rejection message to the CM module. Based on the first service rejection message, the CM module can instruct the CC module to access the Internet. The CC module can change the domain and send a message requesting Internet access to the second network device to improve the success rate of Internet access.

[0295] In this way, it is beneficial to improve the success rate of Internet access when the user triggers an Internet access operation once.

[0296] The method provided by the embodiments of the present application is described in detail above. Next, the method provided by the embodiments of the present application is summarized.

[0297] In a call scenario, before the user triggers a call, the user is in the idle state. Since the user triggers a call, the terminal device switches from the idle state to the service state. Therefore, the terminal device sends a first service request message to the network device to establish a communication link. At this time, since the network device changes the state of the terminal device to logged out through implicit detachment, it cannot provide services to the terminal device, so it rejects the request of the terminal device, resulting in an unsuccessful call. In this scenario, the probability that the user triggers a call and the terminal device switches from the idle state to the service state is small, so it is not easy to find that the call is unsuccessful because of implicit detachment.

[0298] The above Figure 5 In the method shown, in the case of implicit detachment, the terminal device changes the network device by means of re-dialing after changing the domain to improve the success rate of the call. The above Figure 7 and Figure 9In the method shown, an implicit separation occurs, and the terminal device re-registers, re-creates a communication link with the first network device, and continues to attempt to make a call through the first network device. Compared with changing the domain, that is, switching to the second network device with a smaller communication frequency, it is beneficial to improve the call efficiency.

[0299] The above Figure 7 and Figure 9 The difference lies in that: in the method shown in Figure 7 , when the CM module of the terminal device has the first service request message rejected and the registration is successful, it instructs the NAS module to initiate a call. While in the method shown in Figure 9 , when the CM module of the terminal device has the first service request message accepted, it instructs the NAS module to initiate a call.

[0300] Figure 7 In the method shown in Figure 9 , the CM module can determine that the first request fails and then makes a call after successful registration. By making multiple attempts to achieve a call, it is beneficial to improve the success rate of the call.

[0301] In the Internet access scenario, the solution is the same as the above call scenario and will not be elaborated here.

[0302] The above summarizes the method provided by the embodiments of the present application. Next, the method provided by the embodiments of the present application will be specifically introduced in combination with the step flow.

[0303] Exemplarily, Figure 10 shows a schematic flowchart of a communication method provided by an embodiment of the present application. As shown in Figure 10 , the method may include the following steps:

[0304] S1001. Send a first message, where the first message includes REGISTER information.

[0305] S1002. Receive a second message, where the second message includes REGISTER / 200OK information, and the second message is used to respond to the first message.

[0306] S1003. In response to the operation of the user making a call, send a third message, where the third message includes SERVICEREQUEST information.

[0307] S1004. Receive a fourth message, which includes SERVICE REJECT information and #10IMPLICITLY DETACHED information, and the fourth message is used to respond to the third message.

[0308] S1005. In response to the fourth message, send a fifth message, which includes ATTACH REQUEST information. Among them, before sending the fifth message, a sixth message is not sent, and the sixth message includes ACCESS REQUEST information.

[0309] The terminal device sends a first message and receives a second message, which indicates that the terminal device has been successfully registered on the network device. The terminal device can communicate with the network device. In response to the operation of the user making a call, the terminal device switches from the idle state to the service state and can send a third message to establish a communication link with the network device.

[0310] The terminal device receives the fourth message, which indicates that the status of the terminal device on the network device is logged out. The terminal device can send a fifth message to request re-registration. Before the terminal device sends the fifth message, a sixth message is not sent, which means that before sending the fifth message, there is no request to access other network devices.

[0311] In this way, by re-registering and re-establishing the communication link with the network device to achieve a call, it is beneficial to improve the success rate of the call, and compared with achieving a call by accessing other network devices, it is beneficial to improve the efficiency of the call.

[0312] Optionally, the method further includes: receiving a seventh message, which includes ATTACH ACCEPT information and IMS MODE SUPPORTED information, and the seventh message is used to respond to the fifth message; sending an eighth message, which includes REGISTER information; receiving a ninth message, which includes REGISTER / 200OK information, and the ninth message is used to respond to the eighth message; in response to the ninth message, initiate a first call.

[0313] In this way, initiating a call when the re-registration is successful is beneficial to improve the success rate of the call.

[0314] Optionally, in response to the ninth message, initiating a first call includes: in response to the ninth message and the fourth message, initiating a first call.

[0315] The terminal device receives the fourth message, which can indicate that the request of the third message is rejected. Receiving the ninth message can indicate that the re-registration is successful. When the request of the third message is rejected and the re-registration is successful, initiate a first call.

[0316] In this way, it is equivalent to making a second attempt in response to the user's operation of making a call when the first attempt is rejected. When the first attempt is rejected and the second attempt is successful, a first call is initiated. In this way, making multiple attempts is beneficial to improving the success rate of call connection.

[0317] Optionally, the method further includes: sending a sixth message when the first call is unsuccessful.

[0318] In this way, when the call is unsuccessful, other network devices are accessed to facilitate subsequent re - calling, which is beneficial to improving the success rate of call connection.

[0319] Optionally, the method further includes: receiving a tenth message, where the tenth message includes REJECT information and is used to respond to the fifth message; in response to the tenth message, sending a sixth message.

[0320] In this way, when the establishment of a communication link with a previously registered network device fails, other network devices are accessed to facilitate call connection, which is beneficial to improving the success rate of call connection.

[0321] Optionally, the method further includes: receiving an eleventh message, where the eleventh message includes ATTACH ACCEPT information and is used to respond to the sixth message; in response to the eleventh message, initiating a second call.

[0322] In this way, calls are made through other network devices, which is beneficial to improving the success rate of call connection.

[0323] Optionally, the above REGISTER information is IMSSIPREGISTER information. If the REGISTER information is IMS SIPREGISTER information, it can indicate that the terminal device performs IMS registration, which is beneficial to establishing a communication link with the network device.

[0324] Optionally, before sending the first message, the method further includes: sending a twelfth message, where the twelfth message includes ATTACH REQUEST information; receiving a thirteenth message, where the thirteenth message includes ATTACH ACCEPT information and IMS MODESUPPORTED information and is used to respond to the twelfth message.

[0325] Before the terminal device performs IMS registration, it can first perform attachment, that is, send the twelfth message, which is used to request attachment. If the thirteenth message is received, it indicates that the attachment is successful. After attachment, registration can be performed. In this way, it is beneficial to realize the communication between the terminal device and the network device.

[0326] Optionally, the method further includes: in response to the second message, displaying an icon including HD information. In this way, it is indicated that the registration is successful through the icon including HD information, which is convenient for observation.

[0327] Optionally, the method further includes: in response to the second message, setting the registration status of the IMS to IMS registered.

[0328] When the terminal device receives the second message, it can indicate that the IMS registration is successful. The terminal device can set the registration status of the IMS to IMS registered, which is convenient for monitoring the IMS registration status.

[0329] In a possible implementation, the fifth message is used to request registration on the first network device; the sixth message is used to request access to the second network device. The first network device is the device registered through the first message, and the first network device is different from the second network device.

[0330] In a possible implementation, the first message is used to request registration on the first network device; the second message is used to indicate acceptance of the request of the first message; the third message is used to request to establish a communication link with the first network device; the fourth message is used to indicate implicit separation.

[0331] In a possible implementation, the terminal device includes a CM module and a NAS module; in response to the operation of the user making a call, sending the third message includes: in response to the operation of the user making a call, the CM module transmits the third message to the NAS module; the NAS module sends the third message; receiving the fourth message includes: the NAS module receives the fourth message; the NAS module transmits the fourteenth message to the CM module, and the fourteenth message is used to indicate rejection of the third message; receiving the ninth message includes: the NAS module receives the ninth message; the NAS module transmits the ninth message to the CM module; in response to the ninth message and the fourth message, initiating the first call includes: the CM module, in response to the ninth message and the fourteenth message, instructs the NAS module to initiate the first call; the NAS module initiates the first call.

[0332] In this way, the CM module can initiate a call when the third message is rejected and the registration is successful, and realize the call through multiple attempts, which is beneficial to improving the success rate of the call.

[0333] In a possible implementation, the terminal device includes a CM module and a NAS module; in response to a user's operation of making a call, a third message is sent, including: in response to the user's operation of making a call, the CM module transmits the third message to the NAS module; the NAS module sends the third message; a fourth message is received, including: the NAS module receives the fourth message; a ninth message is received, including: the NAS module receives the ninth message; in response to the ninth message, a first call is initiated, including: the NAS module, in response to the ninth message, transmits a fifteenth message to the CM module, and the fifteenth message is used to indicate acceptance of the third message; the CM module, in response to the fifteenth message, instructs the NAS module to initiate the first call; the NAS module initiates the first call.

[0334] In this way, the CM module can initiate a call when the third message is received. In this way, without replacing network devices to implement a call, the CM module does not need to know that re-registration has been performed, reducing unnecessary steps and facilitating the improvement of processing efficiency.

[0335] The embodiment of the present application also provides a chip system, as Figure 11 shown. The chip system 1100 includes at least one processor (such as an application processor AP and a baseband processor Modem) 1101 and at least one interface circuit 1102. The processor 1101 and the interface circuit 1102 can be interconnected by lines. For example, the interface circuit 1102 can be used to receive signals from other devices (such as the memory of the terminal). For another example, the interface circuit 1102 can be used to send signals to other devices (such as the processor 1101). Exemplarily, the interface circuit 1102 can read the instructions stored in the memory and send the instructions to the processor 1101. When the instructions are executed by the processor 1101, the terminal device can execute each step in the above embodiment. Of course, the chip system can also include other discrete devices, and the embodiment of the present application does not make specific limitations on this.

[0336] The communication method provided by the embodiment of the present application can be applied to an electronic device with communication functions. The electronic device includes a terminal device, and the specific device form of the terminal device and the like can refer to the above relevant description, which will not be elaborated here.

[0337] The embodiment of the present application provides a terminal device, which includes: a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, so that the terminal device executes the above method.

[0338] Embodiments of the present application further provide a computer program product including one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from a website, a computer, a server, or a data center to another website, a computer, a server, or a data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or a wireless manner (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server or a data center integrating one or more available media. For example, the available medium may include magnetic media (such as floppy disks, hard disks, or magnetic tapes), optical media (such as digital versatile discs (DVDs)), or semiconductor media (such as solid state disks (SSDs)).

[0339] Embodiments of the present application further provide a computer-readable storage medium. The methods described in the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. The computer-readable storage medium may include a computer storage medium and a communication medium, and may also include any medium that can transmit a computer program from one place to another. The storage medium may be any target medium accessible by a computer.

[0340] As a possible design, the computer-readable storage medium may include a compact disc read-only memory (CD-ROM), RAM, ROM, EEPROM, or other optical disc memories; the computer-readable storage medium may include a disk memory or other disk storage devices. Moreover, any connection line may also be appropriately referred to as a computer-readable storage medium. For example, if software is transmitted from a website, a server, or other remote sources using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies (such as infrared, radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used herein, disks and optical discs include optical discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks usually reproduce data magnetically, while optical discs reproduce data optically using lasers.

[0341] Embodiments of the present application are described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to embodiments of the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processing unit of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, such that the instructions executed by the processing unit of the computer or other programmable data processing device generate means for implementing the specified functions in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or in multiple blocks or the specified functions of multiple blocks.

Claims

1. A communication method, characterized in that, Applied to a terminal device, including: Sending a first message, the first message including REGISTER information; Receiving a second message, the second message including REGISTER / 200OK information, the second message being used to respond to the first message; In response to a user's operation of making a call, sending a third message, the third message including SERVICE REQUEST information; Receiving a fourth message, the fourth message including SERVICE REJECT information and #10IMPLICITLY DETACHED information, the fourth message being used to respond to the third message; In response to the fourth message, sending a fifth message, the fifth message including ATTACH REQUEST information; Wherein, before sending the fifth message, no sixth message is sent, the sixth message including ACCESSREQUEST information.

2. The method according to claim 1, wherein The method further includes: Receiving a seventh message, the seventh message including ATTACH ACCEPT information and IMS MODE SUPPORTED information, the seventh message being used to respond to the fifth message; Sending an eighth message, the eighth message including REGISTER information; Receiving a ninth message, the ninth message including REGISTER / 200OK information, the ninth message being used to respond to the eighth message; In response to the ninth message, initiating a first call.

3. The method according to claim 2, characterized in that, The initiating the first call in response to the ninth message includes: In response to the ninth message and the fourth message, initiating the first call.

4. The method according to claim 2 or 3, characterized in that, The method further includes: In the case where the first call is unsuccessful, sending the sixth message.

5. The method according to claim 1, characterized in that, The method further includes: Receiving a tenth message, the tenth message including REJECT information, the tenth message being used to respond to the fifth message; In response to the tenth message, sending the sixth message.

6. The method according to claim 4 or 5, characterized in that, The method further includes: Receiving an eleventh message, the eleventh message including ATTACH ACCEPT information, the eleventh message being used to respond to the sixth message; In response to the eleventh message, initiating a second call.

7. The method according to any one of claims 1 to 6, characterized in that The REGISTER information is IMS SIPREGISTER information.

8. The method according to any one of claims 1 to 7, characterized in that, Before sending the first message, the method further includes: Sending a twelfth message, the twelfth message including ATTACH REQUEST information; Receiving a thirteenth message, the thirteenth message including ATTACH ACCEPT information and IMS MODE SUPPORTED information, the thirteenth message being used to respond to the twelfth message.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: In response to the second message, displaying an icon including HD information.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: In response to the second message, setting the registration status of the Internet Protocol Multimedia Subsystem IMS to IMS registered.

11. The method according to any one of claims 1 to 10, characterized in that, The fifth message is used to request registration on the first network device; the sixth message is used to request access to the second network device, where the first network device is the device registered through the first message, and the first network device is different from the second network device.

12. The method according to any one of claims 1 to 11, characterized in that, The first message is used to request registration on the first network device; the second message is used to indicate acceptance of the request of the first message; the third message is used to request to establish a communication link with the first network device; the fourth message is used to indicate implicit separation.

13. The method according to claim 3, characterized in that, The terminal device includes a connection management (CM) module and a network attached storage (NAS) module; The sending of the third message in response to the user's operation of making a call includes: In response to the user's operation of making a call, the CM module transmits the third message to the NAS module; The NAS module sends the third message; The receiving of the fourth message includes: The NAS module receives the fourth message; The NAS module transmits a fourteenth message to the CM module, and the fourteenth message is used to indicate rejection of the third message; The receiving of the ninth message includes: The NAS module receives the ninth message; The NAS module transmits the ninth message to the CM module; The initiating of the first call in response to the ninth message and the fourth message includes: The CM module, in response to the ninth message and the fourteenth message, instructs the NAS module to initiate the first call; The NAS module initiates the first call.

14. The method according to claim 2, wherein The terminal device includes a connection management (CM) module and a network attached storage (NAS) module; The sending of the third message in response to the user's operation of making a call includes: In response to the user's operation of making a call, the CM module transmits the third message to the NAS module; The NAS module sends the third message; The receiving of the fourth message includes: The NAS module receives the fourth message; The receiving of the ninth message includes: The NAS module receives the ninth message; The initiating of the first call in response to the ninth message includes: The NAS module, in response to the ninth message, transmits a fifteenth message to the CM module, and the fifteenth message is used to indicate acceptance of the third message; The CM module, in response to the fifteenth message, instructs the NAS module to initiate the first call; The NAS module initiates the first call.

15. A terminal device, characterized in that, Includes: A processor and a memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the terminal device executes the method according to any one of claims 1-14.

16. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the method according to any one of claims 1-14.

17. A chip system, characterized in that, Includes at least one processor and a communication interface, the communication interface and the at least one processor are interconnected by a line, and the at least one processor is used to run a computer program or instruction to execute the method according to any one of claims 1-14.