Ims registration method, apparatus, terminal and medium

Abstract

The present disclosure provides an IMS registration method, device, terminal and medium, and belongs to the technical field of communication. The method comprises the following steps: when registering IMS for a terminal, obtaining device information of the terminal and a network identifier used for indicating a network allowed to be used by the terminal; based on the network identifier of the terminal, obtaining format information of a UA used for registering IMS in the network corresponding to the network identifier; based on the obtained device information, constructing a target UA conforming to the format information, so that the format of the target UA can meet the UA format required by network registration; and based on the constructed target UA, performing IMS registration, so as to improve the success rate of IMS registration.

Description

Technical Field

[0001] This disclosure relates to the field of computer communication technology, and in particular to an IMS registration method, apparatus, terminal and medium. Background Technology

[0002] In recent years, Voice Over Long-Term Evolution (VOLTE) technology has seen its application expand rapidly as a technology capable of improving the quality and effectiveness of voice and video calls. However, before using VoLTE, the terminal's User Agent (UA) needs to register with the IP Multimedia Subsystem (IMS) so that the terminal can enable VoLTE-based calls.

[0003] In related technologies, the terminal typically sends a Session Initialization Protocol (SIP) signaling message, including a UA field, to the network equipment on the operator's side. The UA field contains a string representing the UA, so that the network equipment on the operator's side can register the terminal based on the UA included in the UA field.

[0004] However, many operators have strict requirements for the UA format. If the UA format does not meet the operator's requirements, the terminal cannot register with IMS, resulting in a low IMS registration success rate. Summary of the Invention

[0005] In view of this, this disclosure provides an IMS registration method, apparatus, terminal and medium, which can effectively improve the IMS registration success rate.

[0006] According to a first aspect of the present disclosure, an IMS registration method is provided, the method comprising:

[0007] In response to a registration command for the IP Multimedia Subsystem (IMS), the device information and network identifier of the terminal are obtained. The network identifier is used to indicate the networks that the terminal is allowed to use.

[0008] Based on this network identifier, obtain the format information of the UA used to register for IMS;

[0009] Based on this device information, construct a target User Agent (UA) that conforms to this format.

[0010] IMS registration is performed based on the target UA.

[0011] In some embodiments, based on the network identifier, the format information of the UA used for registering IMS is obtained, including:

[0012] Obtain the format identifier corresponding to the network identifier;

[0013] Obtain the format information corresponding to this format identifier, which will be used as the format information for the UA to register IMS.

[0014] In some embodiments, the method further includes: pre-storing the format identifier and the network identifier;

[0015] The storage process for the format identifier and the network identifier includes:

[0016] Obtain at least one network identifier and at least one candidate format information;

[0017] Set a format identifier for each of the at least one candidate format information;

[0018] The format identifier and its corresponding network identifier are uploaded to the cloud for storage.

[0019] In some embodiments, the device information corresponds to at least one information type, and the format information is used to indicate the information type of the device information included in each field of the target UA to be constructed;

[0020] Based on this device information, construct a target User Agent (UA) that conforms to this format, including:

[0021] Based on the information type of the device information, the device information is added to the corresponding field to obtain the target UA.

[0022] In some embodiments, after performing IMS registration based on the target UA, the method further includes:

[0023] If the terminal successfully registers with IMS, the target UA and / or the format information, along with the network identifier, are stored in the terminal's local storage.

[0024] In some embodiments, storing at least one of the target UA and the format information, corresponding to the network identifier, in the local storage of the terminal includes:

[0025] The target UA and / or the format identifier corresponding to the format information, along with the network identifier, are stored in the local storage of the terminal.

[0026] In some embodiments, the device information includes at least one of the following: manufacturer identifier, device identifier, software system identifier, software system version number, and software system version information.

[0027] In some embodiments, the network identifier includes at least one of the Mobile Country Code (MCC) and the Mobile Network Code (MNC);

[0028] In response to a registration instruction for the IP Multimedia Subsystem (IMS), the network identifier of the terminal is obtained, including at least one of the following:

[0029] In response to the registration command for the IP Multimedia Subsystem (IMS), the MCC of the user identity SIM card carried by the terminal is obtained as the network identifier of the terminal;

[0030] In response to the registration command for the IP Multimedia Subsystem (IMS), the MNC of the SIM card mounted on the terminal is obtained as the network identifier of the terminal.

[0031] In some embodiments, in response to a registration instruction for the IP Multimedia Subsystem (IMS), obtaining device information of the terminal includes:

[0032] In response to the registration command for IMS, obtain the first UA for the terminal;

[0033] If the first UA does not meet the target conditions, the device information is obtained from the first UA.

[0034] In some embodiments, after obtaining the first UA of the terminal in response to a registration instruction for IMS, the method further includes:

[0035] IMS registration is performed based on this first UA;

[0036] If IMS registration based on the first UA fails, obtain the network identifier of the terminal;

[0037] Based on this network identifier, obtain the format information of the UA used to register for IMS;

[0038] Based on this device information, construct a target User Agent (UA) that conforms to this format.

[0039] Re-register with IMS based on the target UA.

[0040] According to a second aspect of the present disclosure, an IMS registration apparatus is provided, the apparatus comprising:

[0041] The acquisition module is used to acquire the terminal's device information and network identifier in response to the registration instruction of the IP Multimedia Subsystem (IMS). The network identifier is used to indicate the networks that the terminal is allowed to use.

[0042] This acquisition module is also used to obtain the format information of the UA used to register for IMS based on the network identifier;

[0043] The building module is used to construct a target User Agent (UA) that conforms to the specified format based on the device information.

[0044] The registration module is used to register the IMS based on the target UA.

[0045] In some embodiments, the acquisition module, when used to acquire format information of the UA used for registering IMS based on the network identifier, includes a first acquisition unit and a second acquisition unit;

[0046] The first acquisition unit is used to acquire the format identifier corresponding to the network identifier;

[0047] The second acquisition unit is used to acquire the format information corresponding to the format identifier, which is used as the format information of the UA for registering IMS.

[0048] In some embodiments, the device further includes:

[0049] The first storage module is used to pre-store the corresponding format identifier and the network identifier;

[0050] The storage process for the format identifier and the network identifier includes:

[0051] Obtain at least one network identifier and at least one candidate format information;

[0052] Set a format identifier for each of the at least one candidate format information;

[0053] The format identifier and its corresponding network identifier are uploaded to the cloud for storage.

[0054] In some embodiments, the device information corresponds to at least one information type, and the format information is used to indicate the information type of the device information included in each field of the target UA to be constructed;

[0055] This building module, when used to construct a target User Agent (UA) conforming to this format based on the device information, is specifically used for:

[0056] Based on the information type of the device information, the device information is added to the corresponding field to obtain the target UA.

[0057] In some embodiments, the device further includes:

[0058] The second storage module is used to store the target UA and / or the format information, along with the network identifier, in the local storage of the terminal when the terminal successfully registers IMS.

[0059] In some embodiments, the second storage module, when used to store at least one of the target UA and the format information in the local storage of the terminal corresponding to the network identifier, is specifically used for:

[0060] The target UA and / or the format identifier corresponding to the format information, along with the network identifier, are stored in the local storage of the terminal.

[0061] In some embodiments, the device information includes at least one of the following: manufacturer identifier, device identifier, software system identifier, software system version number, and software system version information.

[0062] In some embodiments, the network identifier includes at least one of the Mobile Country Code (MCC) and the Mobile Network Code (MNC);

[0063] When the acquisition module acquires the network identifier of the terminal in response to a registration instruction for the IP Multimedia Subsystem (IMS), it is specifically used for at least one of the following:

[0064] In response to the registration command for the IP Multimedia Subsystem (IMS), the MCC of the user identity SIM card carried by the terminal is obtained as the network identifier of the terminal;

[0065] In response to the registration command for the IP Multimedia Subsystem (IMS), the MNC of the SIM card mounted on the terminal is obtained as the network identifier of the terminal.

[0066] In some embodiments, when the acquisition module acquires device information of the terminal in response to a registration instruction for the IP Multimedia Subsystem (IMS), it is specifically used for:

[0067] In response to the registration command for IMS, obtain the first UA for the terminal;

[0068] If the first UA does not meet the target conditions, the device information is obtained from the first UA.

[0069] In some embodiments, the registration module is further configured to register an IMS based on the first UA;

[0070] The acquisition module is also used to acquire the network identifier of the terminal in the event that IMS registration based on the first UA fails.

[0071] This acquisition module is also used to obtain the format information of the UA used to register for IMS based on the network identifier;

[0072] This building module is also used to construct a target User Agent (UA) that conforms to the specified format based on the device information.

[0073] This registration module is also used to re-register the IMS based on the target UA.

[0074] According to a third aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the IMS registration method provided in any of the embodiments of the first aspect described above.

[0075] According to a fourth aspect of the present disclosure, a terminal is provided, the terminal comprising:

[0076] processor;

[0077] Memory used to store processor-executable instructions;

[0078] The processor is configured as follows:

[0079] In response to a registration command for the IP Multimedia Subsystem (IMS), the device information and network identifier of the terminal are obtained. The network identifier is used to indicate the networks that the terminal is allowed to use.

[0080] Based on this network identifier, obtain the format information of the UA used to register for IMS;

[0081] Based on this device information, construct a target User Agent (UA) that conforms to this format.

[0082] IMS registration is performed based on the target UA.

[0083] The technical solutions provided in this disclosure may have the following beneficial effects:

[0084] When registering an IMS for a terminal, the system obtains the terminal's device information and the network identifier indicating the networks the terminal is allowed to use. Based on the terminal's network identifier, it obtains the format information of the User Agent (UA) used to register the IMS under the network corresponding to that network identifier. Based on the obtained device information, it constructs a target UA that conforms to the format information, ensuring that the target UA's format meets the UA format requirements for network registration. Finally, based on the constructed target UA, it performs IMS registration, thereby improving the IMS registration success rate.

[0085] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0086] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0087] Figure 1 This is a schematic diagram illustrating an implementation environment of an IMS registration method according to an exemplary embodiment of the present disclosure;

[0088] Figure 2 This is a flowchart illustrating an IMS registration method according to an exemplary embodiment of this specification;

[0089] Figure 3 This disclosure provides a simplified flow of an IMS registration method according to an exemplary embodiment;

[0090] Figure 4 This disclosure is a flowchart illustrating an IMS registration method according to an exemplary embodiment;

[0091] Figure 5 This is a block diagram illustrating an IMS registration apparatus according to an exemplary embodiment of the present disclosure;

[0092] Figure 6 This is a schematic diagram of the structure of a terminal 600 according to an exemplary embodiment. Detailed Implementation

[0093] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0094] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The singular forms “a,” “the,” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0095] It should be understood that although the terms first, second, third, etc., may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0096] This disclosure provides an IMS registration method for registering a terminal with IMS, enabling the terminal to perform VoLTE-based voice and video calls. In one possible implementation, the implementation environment for this IMS registration method can be found in [link to relevant documentation]. Figure 1 , Figure 1 This is a schematic diagram illustrating an implementation environment of an IMS registration method according to an exemplary embodiment of the present disclosure. The implementation environment of the IMS registration method may include a terminal 101 and a network device 102.

[0097] Terminal 101 can be a smartphone, smartwatch, tablet, laptop, etc., and this disclosure does not limit the specific device type of the terminal. Terminal 101 can be equipped with a SIM card to enable SIM card-based calls. Terminal 101 can connect to network device 102 via wired or wireless connection so that terminal 101 can communicate with network device 102.

[0098] Network device 102 can be a single server, multiple servers, a server cluster, etc. For example, network device 102 can be a Home Subscriber Server (HSS). Optionally, network device 102 can also be other types of servers. This disclosure does not limit the number or specific type of network device. Network device 102 can connect to terminal 101 via wired or wireless connection so that network device 102 can communicate with terminal 101.

[0099] Based on the terminal 101 and network device 102 described above, when registering IMS for terminal 101, terminal 101 can obtain its own device information, thereby determining the User Agent (UA) for IMS registration based on the obtained device information, and then sending a registration request carrying the UA to network device 102. In response to receiving the registration request, network device 102 registers in the IMS system according to the UA carried in the received registration request, so that terminal 101 can realize VoLTE-based voice and video calls after successful IMS registration.

[0100] The above is a description of the implementation environment of this disclosure. Next, the IMS registration method provided by this disclosure will be described in detail with reference to the embodiments of this specification.

[0101] like Figure 2 As shown, Figure 2 This is a flowchart illustrating an IMS registration method according to an exemplary embodiment, the method comprising the following steps:

[0102] Step 201: In response to the registration instruction for the IP Multimedia Subsystem (IMS), obtain the terminal's device information and network identifier. The network identifier is used to indicate the networks that the terminal is allowed to use.

[0103] Optionally, the registration instruction can be triggered automatically after the SIM card is inserted into the terminal, or the registration instruction can be triggered automatically after the terminal is powered on for the first time with the SIM card already inserted, or the registration instruction can be triggered by the user's registration operation on the terminal, with the terminal generating the registration instruction in response to the user's registration operation, or the registration instruction can be triggered in other ways. This disclosure does not limit the specific method of triggering the registration instruction.

[0104] The terminal's device information can be of various types. For example, it may include device information indicating the terminal's manufacturer, device information indicating the terminal's model, and device information indicating the software system installed on the terminal. The device information indicating the terminal's manufacturer can be a manufacturer identifier; the device information indicating the terminal's model can be a device identifier (such as a device model identifier); and the device information indicating the software system installed on the terminal can include a software system identifier, a software system version number, and software system version information. Therefore, the terminal's device information can include at least one of the following: manufacturer identifier, device identifier, software system identifier, software system version number, and software system version information.

[0105] It should be noted that the network identifier indicates the networks that the terminal is allowed to use, that is, the networks that the SIM card installed in the terminal is allowed to use. Optionally, the network identifier of the terminal can be the Mobile Country Code (MCC) of the SIM card installed in the terminal, or it can be the Mobile Network Code (MCC) of the SIM card installed in the terminal, or it can be a combination of MCC and MNC. This disclosure does not limit this.

[0106] Step 202: Based on the network identifier, obtain the format information of the UA used to register IMS.

[0107] The obtained format information can be the UA format required for IMS registration on the network corresponding to the network identifier. Therefore, by obtaining the format information, it is possible to determine the required UA format for registering IMS on the network corresponding to the network identifier.

[0108] Step 203: Based on the device information, construct the target UA that conforms to the specified format.

[0109] Step 204: Register the IMS based on the target UA.

[0110] The solution provided in this disclosure obtains the terminal's device information and the network identifier used to indicate the networks that the terminal is allowed to use when registering an IMS for the terminal. Based on the terminal's network identifier, it obtains the format information of the UA used to register the IMS under the network corresponding to that network identifier. Based on the obtained device information, it constructs a target UA that conforms to the format information, so that the format of the target UA can meet the UA format required for network registration. Then, based on the constructed target UA, it performs IMS registration, thereby improving the IMS registration success rate.

[0111] After introducing the basic implementation process of this disclosure, various non-limiting embodiments of this disclosure will be described in detail below.

[0112] In some embodiments, when obtaining terminal device information in response to the registration instruction to the IMS system in step 201 above, the terminal device information can be obtained directly from the terminal's local storage, or it can be obtained in the following ways:

[0113] In one possible implementation, in response to a registration instruction to IMS, the first User Agent (UA) of the terminal is obtained. If the first UA does not meet the target conditions, device information is obtained based on the first UA.

[0114] The terminal may pre-store a first User Agent (UA) in a preset format, which may include various types of device information. For example, the first UA may include at least one of the following: manufacturer identifier, device identifier, software system identifier, software system version number, and software system version information. Optionally, the first UA may also include other types of device information, which is not limited in this disclosure.

[0115] The first User Agent (UA) meeting the target condition can mean that the first UA meets the UA requirements of the network equipment on the operator's side. For example, the first UA meeting the target condition can mean that the first UA includes preset type device information (for ease of explanation, preset type device information is referred to as preset device information). The preset device information can be a device identifier, or optionally, other types of device information. The device identifier can be the device model name.

[0116] For example, a carrier's requirements for a User Agent (UA) may include:

[0117] 1. The User Agent (UA) must include the device identifier, and the device identifier must not be changed in subsequent Measurement Reports (MRs);

[0118] 2. The firmware version must also be included in the User Agent (UA);

[0119] 3. The Android version should not appear in the User Agent (UA). The UA should include the version of the third-party operating system (such as MIUI).

[0120] Based on the above requirements, for this operator, the User Agent (UA) that meets the target conditions can be as follows, or in other words, the UA that meets the requirements of this operator can be as follows:

[0121] Xiaomi_Mi MIX 2S_Miui_10_Global_8.9.20_Beta

[0122] Optionally, different operators may have the same or different requirements for the User Agent (UA), and this disclosure does not limit this.

[0123] The above describes the process of obtaining the terminal's device information. The following describes the process of obtaining the terminal's network identifier.

[0124] It should be noted that, since the network identifier can be MCC, MNC, or a combination of MCC and MNC, or in other words, the network identifier can include at least one of MCC and MNC, based on this, in some embodiments, for step 201 above, when obtaining the terminal's network identifier in response to the registration instruction to the IMS system, there are three possible implementation methods:

[0125] In one possible implementation, in response to a registration command to the IP Multimedia Subsystem (IMS), the MCC of the SIM card mounted on the terminal is obtained as the network identifier of the terminal.

[0126] The MCC (Multi-Choice Code) consists of three digits and is used to uniquely identify a country, but a country can have multiple MCCs. For example, China's MCC is 460, while the United States has MCCs 310, 311, and 316.

[0127] In another possible implementation, if the first UA includes product information, the MNC of the SIM card carried by the terminal is obtained as the network identifier of the terminal.

[0128] The MNC (Mobile Number) consists of two or three digits and is used to uniquely identify an operator. For example, China Mobile's Global System for Mobile Communications (GSM) MNC is 01, and China Unicom's GSM MNC is 02.

[0129] In another possible implementation, if the first UA includes product information, the MCC and MNC of the SIM card carried by the terminal are obtained as the network identifier of the terminal.

[0130] When using MCC and MNC as the network identifier of a terminal, the MCC and MNC can be concatenated together, and the result can be used as the terminal's network identifier. For example, the MCC of China and the MNC of China Mobile's GSM system can be concatenated together, and the result is 460-01. This result can be used as the terminal's network identifier to indicate that the terminal is using the network provided by China Mobile's GSM system.

[0131] In some embodiments, a format identifier can be used as a marker for format information, with different format information corresponding to different format identifiers, so that the corresponding format information can be obtained through the format identifier. Furthermore, the cloud can pre-store the correspondence between format identifiers and network identifiers, so that the format identifier corresponding to a network identifier can be obtained based on the correspondence, and the corresponding format information can be obtained subsequently based on the format identifier. It should be noted that one network identifier corresponds to one format identifier, and different network identifiers may correspond to the same or different format identifiers.

[0132] Based on the above, in some embodiments, when obtaining the format information of the UA used for IMS registration based on the network identifier in step 202, it can be implemented in the following way:

[0133] Obtain the format identifier corresponding to the network identifier; obtain the format information corresponding to the format identifier, which will be used as the format information for the UA to register IMS.

[0134] In the process of pre-storing the correspondence between format identifiers and network identifiers, the correspondence between network identifiers and their corresponding format identifiers can be obtained by pre-storing the network identifiers and their corresponding format identifiers.

[0135] In one possible implementation, storing the correspondence between the format identifier and the network identifier may include the following steps:

[0136] Step 1: Obtain at least one network identifier and at least one candidate format information.

[0137] It should be noted that there are generally about 10 commonly used UA formats in the IMS registration process. In one possible implementation, the format information of these 10 commonly used UA formats in the IMS registration process can be used as at least one candidate format information.

[0138] Some carrier networks may have their own required User Agent (UA) format; therefore, each candidate format will have a corresponding network identifier. It should be noted that different carrier networks may require the same UA format, meaning that one candidate format may correspond to multiple network identifiers.

[0139] Step 2: Set a format identifier for at least one candidate format information.

[0140] In one possible implementation, a label can be set for at least one candidate format information obtained, and then the set label can be used as the format identifier corresponding to the candidate format information.

[0141] For example, if there are 10 candidate format information, these 10 candidate format information can be randomly sorted, and then based on the sorting result, the 10 candidate format information can be assigned numbers 1 to 10 in order, thereby completing the setting of the format identifier.

[0142] The following are some examples of candidate format information, and the format identifiers corresponding to the candidate format information:

[0143] Generate manufacturer identifier + device identifier + software system identifier + software system version number + software system version information, with the format identifier being 1;

[0144] Generate a string containing the manufacturer identifier, device identifier, and Android version, with the format identifier being 2;

[0145] etc.

[0146] Step 3: Upload the format identifier and the corresponding network identifier to the cloud for storage.

[0147] It should be noted that the format information obtained through step 202 above can indicate the information type of the device information included in each field of the target UA to be constructed. The device information obtained through step 201 above can correspond to at least one information type. Therefore, for step 203 above, when constructing a target UA that conforms to the format information based on the device information, the following implementation methods can be used:

[0148] In one possible implementation, the device information is added to the corresponding field based on the information type of the device information to obtain the target UA.

[0149] For example, if the device information indicates that the fields of the target UA to be built include the manufacturer identifier, the device identifier, and the software system identifier in sequence, then the obtained manufacturer identifier can be added to the first field of the target UA to be built, the obtained device identifier can be added to the second field of the target UA to be built, and the obtained software system identifier can be added to the third field of the target UA to be built, thereby obtaining the constructed target UA.

[0150] In some embodiments, after constructing a target UA that conforms to the format information, IMS registration can be performed based on the target UA. For step 204 above, registration based on the target UA can be implemented in the following way:

[0151] In one possible implementation, a registration request carrying the target UA is sent to the network device. Upon receiving the registration request carrying the target UA, the network device stores the target UA if the target UA meets the UA format requirements for IMS registration, thereby achieving IMS registration based on the target UA.

[0152] The registration request can be an instruction generated based on the Session Initialization Protocol (SIP).

[0153] A brief flowchart of the IMS registration method provided in the above embodiments can be found in [reference needed]. Figure 3 , Figure 3 This disclosure provides a simplified flow of an IMS registration method according to an exemplary embodiment. Taking the cloud as an example, which stores a format identifier, MCC, and MNC, the method provided by this disclosure can determine the format information of the UA based on the format identifier, and can also map the UA to the format identifier according to the corresponding format information, thereby constructing the obtained terminal device information into a target UA that conforms to the format information, and thus initiating the IMS registration process based on the target UA.

[0154] Figure 3 The diagram shown is only the basic process of this disclosure. For a more detailed process and the specific implementation of each step, please refer to the above embodiments, which will not be repeated here.

[0155] In some embodiments, if the terminal successfully registers IMS, the target UA and / or format information, corresponding to the network identifier, are stored in the terminal's local storage.

[0156] In one possible implementation, when storing the target UA and / or format information, along with the network identifier, in the terminal's local storage, the format identifier corresponding to the target UA and / or format information, along with the network identifier, can be stored in the terminal's local storage.

[0157] In other words, when a terminal successfully registers with IMS, the target UA and network identifier can be stored in the terminal's local storage, the format identifier and network identifier can be stored in the terminal's local storage, and the target UA, format identifier and network identifier can be stored in the terminal's local storage.

[0158] It should be noted that the above embodiments are all illustrated using the application scenario of a terminal registering IMS on a network for the first time. In more possible implementations, the solution provided in this disclosure can also be used in the scenario of re-registering IMS.

[0159] In one possible implementation, the terminal may pre-store a first UA, which includes various device information of the terminal. In response to the IMS registration command, the terminal may directly obtain the stored first UA and then register the IMS based on the first UA. If the IMS registration based on the first UA fails, the terminal may obtain the format information of the UA used for IMS registration, and construct a target UA that conforms to the format information based on the device information, and then re-register the IMS based on the target UA.

[0160] This disclosure does not specify which types of device information the first UA includes. Furthermore, the above process is merely a procedural description; for specific implementation methods, please refer to the various embodiments described above, which will not be repeated here.

[0161] When applying the IMS registration method provided in this disclosure to a re-registration scenario, the process of this IMS registration method can be found in [reference needed]. Figure 4 , Figure 4 This is a flowchart illustrating an IMS registration method according to an exemplary embodiment. The cloud pre-stores a combination of format identifiers and MCC / MNC. The IMS registration method provided by this disclosure can detect whether a terminal has failed to register for IMS. If registration fails, it checks whether the UA (i.e., the first UA) used by the terminal during the initial IMS registration meets the target conditions, specifically whether it meets the operator's IMS registration requirements (e.g., whether the first UA includes a device identifier). If the first UA does not meet the target conditions, it retrieves the format identifier corresponding to the operator's network to be registered from the cloud. Based on the format identifier, it determines the format information and, based on the format information, determines the composition of the target UA (e.g., device identifier + software version information). Based on the terminal's device information, it constructs a target UA that conforms to the format information and re-initiates IMS registration. After successful IMS registration, the target UA's format information is updated to local storage so that subsequent IMS registrations can be initiated directly using the target UA.

[0162] For the foregoing method embodiments, in order to simplify the description, they are all described as a series of actions. However, those skilled in the art should know that this disclosure is not limited to the described order of actions, because according to this disclosure, some steps may be performed in other orders or simultaneously.

[0163] Secondly, those skilled in the art should also know that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by this disclosure.

[0164] Corresponding to the aforementioned application function implementation method embodiments, this disclosure also provides embodiments of application function implementation apparatus and corresponding terminals.

[0165] See Figure 5 , Figure 5 This is a block diagram illustrating an IMS registration apparatus according to an exemplary embodiment of the present disclosure, the apparatus including:

[0166] The acquisition module 501 is used to acquire the terminal's device information and network identifier in response to the registration instruction for the IP Multimedia Subsystem (IMS). The network identifier is used to indicate the networks that the terminal is allowed to use.

[0167] The acquisition module 501 is also used to acquire the format information of the UA used to register IMS based on the network identifier;

[0168] The building module is used to construct the target User Agent (UA) based on device information and in a conforming format.

[0169] The registration module is used for IMS registration based on the target UA.

[0170] In some embodiments, the acquisition module, when used to acquire format information of the UA used for registering IMS based on the network identifier, includes a first acquisition unit and a second acquisition unit.

[0171] The first acquisition unit is used to acquire the format identifier corresponding to the network identifier;

[0172] The second acquisition unit is used to acquire the format information corresponding to the format identifier, which is used as the format information of the UA for registering IMS.

[0173] In some embodiments, the device further includes:

[0174] The first storage module is used to pre-store the corresponding format identifier and network identifier;

[0175] The stored procedures for format identifiers and network identifiers include:

[0176] Obtain at least one network identifier and at least one candidate format information;

[0177] Set a format identifier for at least one candidate format information;

[0178] Upload the format identifier and the corresponding network identifier to the cloud for storage.

[0179] In some embodiments, the device information corresponds to at least one information type, and the format information is used to indicate the information type of the device information included in each field of the target UA to be constructed;

[0180] This building module, when used to construct a target User Agent (UA) that conforms to a specific format based on device information, is specifically used for:

[0181] Based on the information type of the device information, the device information is added to the corresponding field to obtain the target User Agent (UA).

[0182] In some embodiments, the device further includes:

[0183] The second storage module is used to store the target UA and / or format information, along with the network identifier, in the terminal's local storage when the terminal successfully registers IMS.

[0184] In some embodiments, the second storage module, when used to store at least one of the target UA and format information, corresponding to the network identifier, in the local storage of the terminal, is specifically used for:

[0185] Store the target UA and / or the format identifier corresponding to the format information, along with the network identifier, in the terminal's local storage.

[0186] In some embodiments, the device information includes at least one of the following: manufacturer identifier, device identifier, software system identifier, software system version number, and software system version information.

[0187] In some embodiments, the network identifier includes at least one of the Mobile Country Code (MCC) and the Mobile Network Code (MNC);

[0188] When the acquisition module acquires the network identifier of the terminal in response to a registration instruction for the IP Multimedia Subsystem (IMS), it is specifically used for at least one of the following:

[0189] In response to the registration command for the IP Multimedia Subsystem (IMS), the MCC of the user identity SIM card carried by the terminal is obtained as the network identifier of the terminal;

[0190] If the first UA includes product information, the MNC of the SIM card installed in the terminal is obtained as the network identifier of the terminal.

[0191] In some embodiments, when the acquisition module acquires device information of the terminal in response to a registration instruction for the IP Multimedia Subsystem (IMS), it is specifically used for:

[0192] In response to the registration command for IMS, obtain the terminal's first UA;

[0193] If the target conditions are not met by the first UA, obtain device information from the first UA.

[0194] In some embodiments, the registration module is further configured to register an IMS based on a first User Agent (UA).

[0195] This acquisition module is also used to acquire the terminal's network identifier in the event that IMS registration based on the first UA fails.

[0196] This acquisition module is also used to acquire the format information of the UA used to register IMS based on the network identifier;

[0197] This building module is also used to construct a target User Agent (UA) that conforms to a specific format based on device information;

[0198] This registration module is also used to re-register the IMS based on the target UA.

[0199] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative, wherein the modules or units described as separate components may or may not be physically separate, and the components shown as modules or units may or may not be physical modules or physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules or units can be selected to achieve the purpose of this disclosure according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0200] Accordingly, this disclosure provides a terminal, which includes: a processor and a memory for storing processor-executable instructions; wherein the processor is configured to perform the following steps:

[0201] In response to the registration command for the IP Multimedia Subsystem (IMS), the device information and network identifier of the terminal are obtained. The network identifier is used to indicate the networks that the terminal is allowed to use.

[0202] Based on the network identifier, obtain the format information of the UA used to register IMS;

[0203] Based on device information, construct a target user agent (UA) that conforms to the specified format.

[0204] IMS registration is performed based on the target UA.

[0205] Figure 6This is a schematic diagram illustrating the structure of a terminal 600 according to an exemplary embodiment. For example, the terminal 600 can be a user device, specifically a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, wearable device such as smartwatch, smart glasses, smart bracelet, smart running shoes, etc.

[0206] Reference Figure 6 The terminal 600 may include one or more of the following components: a processing component 602, a memory 604, a power supply component 606, a multimedia component 608, an audio component 610, an input / output (I / O) interface 612, a sensor component 614, and a communication component 616.

[0207] Processing component 602 typically controls the overall operation of terminal 600, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 602 may include one or more processors 620 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 602 may include one or more modules to facilitate interaction between processing component 602 and other components. For example, processing component 602 may include a multimedia module to facilitate interaction between multimedia component 608 and processing component 602.

[0208] Memory 604 is configured to store various types of data to support operation on terminal 600. Examples of this data include instructions for any application or method operating on terminal 600, contact data, phonebook data, messages, pictures, videos, etc. Memory 604 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0209] Power supply component 606 provides power to various components of terminal 600. Power supply component 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to terminal 600.

[0210] Multimedia component 608 includes a screen that provides an output interface between the terminal 600 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 608 includes a front-facing camera and / or a rear-facing camera. When the terminal 600 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0211] Audio component 610 is configured to output and / or input audio signals. For example, audio component 610 includes a microphone (MIC) configured to receive external audio signals when terminal 600 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 604 or transmitted via communication component 616. In some embodiments, audio component 610 also includes a speaker for outputting audio signals.

[0212] I / O interface 612 provides an interface between processing component 602 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0213] Sensor assembly 614 includes one or more sensors for providing state assessments of various aspects of terminal 600. For example, sensor assembly 614 can detect the on / off state of terminal 600, the relative positioning of components such as the display and keypad of terminal 600, changes in the position of terminal 600 or one of its components, the presence or absence of user contact with terminal 600, orientation or acceleration / deceleration of terminal 600, and temperature changes of terminal 600. Sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 614 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0214] Communication component 616 is configured to facilitate wired or wireless communication between terminal 600 and other devices. Terminal 600 can access wireless networks based on communication standards, such as WiFi, 2G or 3G, 4G LTE, 5G NR, or combinations thereof. In one exemplary embodiment, communication component 616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the aforementioned communication component 616 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0215] In an exemplary embodiment, terminal 600 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0216] In an exemplary embodiment, a non-transitory computer-readable storage medium is also provided, such as a memory 604 including instructions. When the instructions in the storage medium are executed by the processor 620 of the terminal 600, the terminal 600 is enabled to execute an IMS registration method, which includes:

[0217] In response to the registration command for the IP Multimedia Subsystem (IMS), the device information and network identifier of the terminal are obtained. The network identifier is used to indicate the networks that the terminal is allowed to use.

[0218] Based on the network identifier, obtain the format information of the UA used to register IMS;

[0219] Based on device information, construct a target user agent (UA) that conforms to the specified format.

[0220] IMS registration is performed based on the target UA.

[0221] The aforementioned non-transitory computer-readable storage media may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage devices, etc.

[0222] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0223] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. An IMS registration method, characterized in that, The method includes: In response to a registration command for the IP Multimedia Subsystem (IMS), the first User Agent (UA) of the terminal is obtained, wherein the first UA is pre-stored by the terminal. IMS registration is performed based on the first UA; In the event that IMS registration fails based on the first UA, the network identifier of the terminal is obtained, and device information is obtained from the first UA. The network identifier is used to indicate the networks that the terminal is allowed to use, wherein different format information is pre-configured for different network identifiers. Obtain the format information of the UA used for registering IMS corresponding to the network identifier, wherein the format information indicates the type of device information required for the UA used for registering IMS; The device information is assembled based on the device information type indicated by the format information to construct a target UA that conforms to the format information; Re-register with IMS based on the target UA.

2. The method according to claim 1, characterized in that, The step of obtaining the format information of the User Agent (UA) used for IMS registration based on the network identifier includes: Obtain the format identifier corresponding to the network identifier; Obtain the format information corresponding to the format identifier, and use it as the format information for the UA used to register IMS.

3. The method according to claim 2, characterized in that, The method further includes: pre-storing the corresponding format identifier and the network identifier; The storage process for the format identifier and the network identifier includes: Obtain at least one network identifier and at least one candidate format information; Set a format identifier for each of the at least one candidate format information; The format identifier and the corresponding network identifier are uploaded to the cloud for storage.

4. The method of claim 1, wherein, The device information corresponds to at least one information type, and the format information is used to indicate the information type of the device information included in each field of the target UA to be constructed; The step of constructing a target User Agent (UA) conforming to the specified format information based on the device information includes: Based on the information type of the device information, the device information is added to the corresponding field to obtain the target UA.

5. The method of claim 1, wherein, After performing IMS registration based on the target UA, the method further includes: If the terminal successfully registers IMS, the target UA and / or the format information, along with the network identifier, are stored in the terminal's local storage.

6. The method according to claim 5, characterized in that, The step of storing at least one of the target UA and the format information, corresponding to the network identifier, in the local storage of the terminal includes: The target UA and / or the format identifier corresponding to the format information are stored in the local storage of the terminal along with the network identifier.

7. The method according to claim 1, characterized in that, The device information includes at least one of the following: manufacturer identifier, device identifier, software system identifier, software system version number, and software system version information.

8. The method of claim 1, wherein, The network identifier includes at least one of the Mobile Country Code (MCC) and the Mobile Network Code (MNC); In response to a registration instruction for the IP Multimedia Subsystem (IMS), the network identifier of the terminal is obtained, including at least one of the following: In response to a registration command for the IP Multimedia Subsystem (IMS), the MCC of the user identity SIM card mounted on the terminal is obtained as the network identifier of the terminal; In response to a registration command for the IP Multimedia Subsystem (IMS), the MNC of the SIM card mounted on the terminal is obtained and used as the network identifier of the terminal.

9. An IMS registration device, characterized in that, The device includes: The acquisition module is used to acquire the first User Agent (UA) of the terminal in response to the registration instruction of the IP Multimedia Subsystem (IMS), wherein the first UA is pre-stored by the terminal; The registration module is used to register the IMS based on the first UA; The acquisition module is further configured to acquire the network identifier of the terminal and acquire device information from the first UA in the event that IMS registration based on the first UA fails. The network identifier is used to indicate the network that the terminal is allowed to use, wherein different format information is pre-configured for different network identifiers. The acquisition module is further configured to acquire the format information of the UA used for registering IMS corresponding to the network identifier, wherein the format information indicates the type of device information required for the UA used for registering IMS; A construction module is used to assemble the device information based on the device information type indicated by the format information to construct a target UA that conforms to the format information; The registration module is also used to re-register the IMS based on the target UA.

10. A terminal, characterized in that, The terminal includes: processor; Memory used to store processor-executable instructions; The processor is configured as follows: In response to a registration command for the IP Multimedia Subsystem (IMS), the first User Agent (UA) of the terminal is obtained, wherein the first UA is pre-stored by the terminal. Register the IMS based on the first UA; In the event that IMS registration fails based on the first UA, the network identifier of the terminal is obtained, and device information is obtained from the first UA. The network identifier is used to indicate the networks that the terminal is allowed to use, wherein different network identifiers correspond to different format information. Obtain the format information of the UA used for registering IMS corresponding to the network identifier, wherein the format information indicates the type of device information required for the UA used for registering IMS; The device information is assembled based on the device information type indicated by the format information to construct a target UA that conforms to the format information; Re-register with IMS based on the target UA.

11. A non-transitory computer-readable storage medium having stored thereon a computer program, characterized in that, When the program is executed by the processor, it implements the steps of the IMS registration method as described in any one of claims 1 to 8.

Images