CN110351110B

CN110351110B - Method, equipment and system for configuring terminal parameters

Info

Publication number: CN110351110B
Application number: CN201810302368.1A
Authority: CN
Inventors: 叶婉玲; 时书锋; 郭晓龙; 陈铠
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-04-04
Filing date: 2018-04-04
Publication date: 2021-07-16
Anticipated expiration: 2038-04-04
Also published as: CN110351110A

Abstract

The embodiment of the application discloses a method, equipment and a system for configuring terminal parameters, relates to the technical field of communication, and aims to solve the problem that the existing method for configuring the terminal parameters consumes time and cost. The method comprises the following steps: the configuration server receives an IMS registration request which is sent by the terminal and used for requesting IMS registration of the terminal, and sends configuration parameters used for supporting IMS services to the terminal. The method provided by the embodiment of the application is mainly used for realizing the configuration of the terminal parameters through the IMS registration process.

Description

Method, equipment and system for configuring terminal parameters

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a method, equipment and a system for configuring terminal parameters.

Background

In the existing third Generation Partnership Project (3 GPP) Protocol TS 24.167, a method for configuring service parameters of an Internet Protocol (IP) Multimedia Subsystem (IMS) is defined, and the method is compatible with an Open Mobile Alliance (OMA) DM1.2 Protocol. However, due to the complexity of the OMA DM1.2 protocol, not too many terminals can support the OMA DM protocol, and thus the configuration method defined by the 3GPP protocol TS 24.167 is not widely used. A method for configuring IMS service parameters is also defined in mobile telecommunications asian conference (GSMA) PRD rcc.14, but this method is also rarely used.

At present, before a terminal enters a communication market for circulation, the following method is generally adopted to configure IMS service parameters of the terminal: a Mobile operator (MNO) issues a "parameter setting list" of the MNO to each Original Equipment Manufacturer (OEM) (or chip manufacturer), and after receiving the "parameter setting list" issued by the MNO, the OEM performs a targeted adaptation and interoperability test on each configuration value corresponding to an IMS service parameter, and determines an IMS service parameter supported by a terminal from the test result, so as to ensure that a terminal circulating in the market completely meets a communication standard executed by the operator, where the "parameter setting list" includes the IMS service parameter and its corresponding configuration value. Since the parameter setting lists owned by different operators in different countries are different, IMS service parameters supported by different terminals may be different, such as: there are M × N parameter configurations between M different operators and N different terminals, which is very time consuming, and the same OEM needs to perform parameter configuration work for many operators, which undoubtedly increases its working cost.

Disclosure of Invention

The embodiment of the application provides a method, equipment and a system for configuring terminal parameters, and aims to solve the problem of time consumption and cost of the conventional terminal parameter configuration.

In order to achieve the above purpose, the following technical solutions are adopted in the embodiments of the present application.

In a first aspect, an embodiment of the present application provides a method for configuring a terminal parameter, where a configuration server receives an IMS registration request of a terminal for requesting IMS registration for the terminal, and sends a configuration parameter for supporting an IMS service to the terminal according to the IMS registration request. Based on the technical scheme provided by the embodiment of the application, the configuration parameters of the terminal can be sent to the terminal when the terminal initiates IMS registration, the configuration of the terminal parameters can be realized while the IMS registration is realized, the OEM of the terminal and an operator do not need to carry out parameter negotiation and docking, namely, the network side equipment sends the configuration parameters to the terminal through a control plane signaling, and the time and the cost are saved. Meanwhile, the server storing the configuration parameters of the terminal is deployed at the network side, so that different OEM equipment can directly access the server to obtain the configuration parameters of the terminal, and the centralized configuration of the configuration parameters of the terminal is realized.

In a possible design, in combination with the first aspect, the configuration parameters of the terminal are stored on the configuration server. Therefore, the configuration parameters of the terminal stored by the terminal can be directly issued to the terminal after the IMS registration request is received, and the configuration parameters of the terminal do not need to be acquired by other functional entities and then issued to the terminal, so that the design complexity of the configuration server is reduced.

In a possible design, with reference to the first aspect, the configuration parameters of the terminal are stored in an Application Server (AS), and before the configuration Server sends the configuration parameters of the terminal to the terminal, the configuration Server sends a third-party registration request to the AS, and waits for and receives a 200OK carrying the configuration parameters of the terminal, which is returned by the AS and corresponds to the third-party registration request. Therefore, the configuration parameters of the terminal can be acquired through the third-party registration process and are issued to the terminal.

In one possible design, in combination with the first aspect, the configuration parameters of the terminal are stored in a Home Subscriber Server (HSS); before the configuration Server sends the configuration parameters of the terminal to the terminal, the configuration Server sends a Server Assignment Request (SAR) to the HSS, and receives a Server Assignment Answer (SAA) carrying the configuration parameters of the terminal, which is sent by the HSS. Therefore, the HSS can manage the configuration parameters of the terminal in a centralized way, and the configuration parameters of the terminal are acquired from the HSS and are issued to the terminal.

In a possible design, with reference to the first aspect or any one of the above possible designs, the server is configured as a Serving Call Session Control Function (S-CSCF) or a Proxy Call Session Control Function (P-CSCF). Therefore, the technical scheme provided by the embodiment of the application can be executed by different functional entities, and the flexibility of the scheme execution is increased.

In a possible design, with reference to the first aspect or any one of the above possible designs, the sending, by the configuration server, the configuration parameters of the terminal to the terminal includes: and the configuration server carries the configuration parameters of the terminal in 200OK corresponding to the IMS registration request and sends the configuration parameters to the terminal, wherein the 200OK is used for indicating the success of the IMS registration of the terminal. Therefore, the configuration parameters of the terminal can be sent to the terminal through the signaling in the existing IMS registration process, no new signaling needs to be added, the complexity of network design is reduced, and meanwhile, the method is compatible with the existing IMS registration process.

In another possible design, with reference to the first aspect, before the configuration server sends the configuration parameter of the terminal to the terminal, the configuration server receives SIP MESSAGE carrying the configuration parameter of the terminal sent by the AS, and the sending, by the configuration server, the configuration parameter of the terminal to the terminal includes: the configuration server sends SIP MESSAGE to the terminal carrying the configuration parameters of the terminal. Therefore, the configuration parameters can be issued to the terminal through the newly added signaling, and the signaling in the existing IMS registration process is not occupied.

In another possible design, with reference to the first aspect or any one of the above possible designs, the IMS registration request includes indication information for indicating that the terminal supports a network element in the IMS to issue configuration parameters, and the configuration server sends the configuration parameters of the terminal to the terminal according to the IMS registration request, including: and the configuration server sends the configuration parameters of the terminal to the terminal according to the indication information. Therefore, the configuration parameters of the terminal can be sent to the terminal under the condition that the terminal supports the network element in the IMS to issue the configuration parameters, and the problem that the configuration parameters of the terminal are issued to cause the failure of the configuration of the terminal under the condition that the terminal does not support the network element in the IMS to issue the configuration parameters is solved.

In yet another possible design, with reference to the first aspect or any one of the above possible designs, the method further includes: the method comprises the steps that a configuration server receives a re-registration request which is sent by a terminal and used for requesting the re-IMS registration of the terminal, and when the configuration parameters of the terminal are updated, the configuration server carries the updated configuration parameters of the terminal in a re-registration response which is used for indicating the successful re-registration of the terminal IMS and sends the re-registration response to the terminal. Therefore, the updated configuration parameters of the terminal can be issued to the terminal through the IMS registration process initiated by the terminal again, and the configuration parameters on the terminal can be updated in time.

In yet another possible design, with reference to the first aspect or any one of the above possible designs, the method further includes: the configuration server receives a subscription request which is sent by the terminal and used for requesting the configuration server to send a notification to the terminal when the configuration parameters of the terminal are updated, and when the configuration parameters of the terminal are updated, the configuration server sends an event notification carrying the updated configuration parameters of the terminal to the terminal. Therefore, the updated configuration parameters of the terminal can be issued to the terminal in an active subscription mode of the terminal, and the configuration parameters on the terminal can be updated in time.

In yet another possible design, with reference to the first aspect or any one of the above possible designs, the method further includes: and the configuration server detects that the configuration parameters of the terminal are updated, carries the updated configuration parameters of the terminal in SIP MESSAGE and sends the configuration parameters to the terminal. Therefore, when the configuration server detects that the configuration parameters of the terminal are updated, the updated configuration parameters can be actively issued to the terminal, and the configuration parameters on the terminal can be updated in time.

In yet another possible design, with reference to the first aspect or any one of the above possible designs, the method further includes: and the configuration server receives the configuration parameters updated by the terminal and sends the configuration parameters updated by the terminal to the terminal. Therefore, under the condition that the configuration server does not store the configuration parameters of the terminal, the updated configuration parameters are received from other functional entities storing the configuration parameters of the terminal, and the received updated configuration parameters are issued to the terminal, so that the configuration parameters on the terminal are updated in time.

In a second aspect, an embodiment of the present application provides a method for configuring a terminal parameter, where a terminal sends an IMS registration request for requesting IMS registration for the terminal to a configuration server, and receives a configuration parameter for supporting an IMS service sent by the configuration server. Based on the technical scheme provided by the embodiment of the application, the configuration parameters of the terminal sent by the configuration server can be received when the terminal initiates the IMS registration, so that the configuration of the terminal parameters is realized, the OEM of the terminal and an operator are not required to carry out negotiation and butt joint of the parameters, and the time and the cost are saved. Meanwhile, the server storing the configuration parameters of the terminal is deployed at the network side, so that different OEM equipment can directly access the server to obtain the configuration parameters of the terminal, and the centralized configuration of the configuration parameters of the terminal is realized.

In a possible design, in combination with the second aspect, the configuration parameters of the terminal are stored at an S-CSCF, or a P-CSCF, or an AS, or an HSS. In this way, the configuration parameters of the terminal are stored in the network side functional entity, so that the operator can manage the configuration parameters of the terminal in a centralized manner.

In a possible design, in combination with the second aspect or any possible design of the second aspect, the IMS registration request includes indication information for indicating that the terminal supports the network element in the IMS to issue the configuration parameter, so that the configuration server sends the configuration parameter of the terminal to the terminal when the terminal supports the network element in the IMS to issue the configuration parameter, thereby avoiding a problem that the configuration parameter of the terminal is issued to cause a failure in the configuration of the terminal when the terminal does not support the network element in the IMS to issue the configuration parameter.

In a possible design, in combination with the second aspect or any one of the possible designs of the second aspect, the receiving, by the terminal, the configuration parameter of the terminal sent by the configuration server includes: and the terminal receives a 200OK which is sent by the configuration server and carries the configuration parameters of the terminal, wherein the 200OK is a response message corresponding to the IMS registration request, and the 200OK is used for indicating the success of the IMS registration of the terminal. Therefore, the configuration parameters of the terminal can be received through the signaling in the existing IMS registration process, no new signaling needs to be added, the complexity of network design is reduced, and meanwhile, the method is compatible with the existing IMS registration process.

In a possible design, in combination with the second aspect or any one of the possible designs of the second aspect, the receiving, by the terminal, the configuration parameter of the terminal sent by the configuration server includes: the terminal receives the session initiation protocol message SIP MESSAGE carrying the configuration parameters of the terminal sent by the configuration server. Therefore, the configuration parameters of the terminal can be received through the newly added signaling, and the signaling in the existing IMS registration process is not occupied.

In a further possible design, in combination with the second aspect or any one of the possible designs of the second aspect, the configuration server is an S-CSCF, or a P-CSCF. Therefore, different functional entities can issue configuration parameters to the terminal, and the flexibility of the implementation of the scheme is increased.

In yet another possible design, in combination with the second aspect or any one of the possible designs of the second aspect, the method further includes: the terminal sends a re-registration request for requesting the re-IMS registration of the terminal to the configuration server, and receives a re-registration response which is sent by the configuration server and carries the updated configuration parameters of the terminal. Therefore, the updated configuration parameters of the terminal can be issued to the terminal through the IMS registration process initiated by the terminal again, and the configuration parameters on the terminal can be updated in time.

In yet another possible design, in combination with the second aspect or any one of the possible designs of the second aspect, the method further includes: the terminal sends a subscription request for requesting the configuration server to send a notification to the terminal when the configuration parameters of the terminal are updated to the configuration server, and receives an event notification which is sent by the configuration server and carries the updated configuration parameters of the terminal. Therefore, the updated configuration parameters of the terminal can be issued to the terminal in an active subscription mode of the terminal, and the configuration parameters on the terminal can be updated in time.

In a third aspect, an embodiment of the present application provides a configuration server, where the configuration server may implement the functions performed by the configuration server in the above aspects or possible designs, where the functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions. Such as: the configuration server may include: a receiving unit, a transmitting unit;

a receiving unit, configured to receive an IMS registration request of the terminal for requesting IMS registration for the terminal, and a sending unit, configured to send a configuration parameter for supporting an IMS service to the terminal according to the IMS registration request.

For a specific implementation manner of the configuration server, reference may be made to the behavior function of the configuration server in the method for configuring the terminal parameter provided in the third aspect, the fourth aspect, or any one of the possible designs of the foregoing aspects, and details are not repeated here. Thus, the configuration server provided may achieve the same benefits as the first aspect or any of the possible designs of the above aspects.

In a fourth aspect, a configuration server is provided, comprising: a processor and a memory; the memory is configured to store computer executable instructions, and when the configuration server is running, the processor executes the computer executable instructions stored in the memory to cause the configuration server to perform the method for configuring terminal parameters according to the first aspect or any one of the possible designs of the above aspects.

In a fifth aspect, there is provided a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform the method for configuring terminal parameters according to the first aspect or any one of the above possible designs.

A sixth aspect provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of configuring terminal parameters of the first aspect or any of the possible designs of the above aspect.

In a seventh aspect, a chip system is provided, where the chip system includes a processor and a communication interface, and is configured to support a configuration server to implement the functions in the foregoing aspects, for example, the support processor receives an IMS registration request of a terminal through the communication interface, the IMS registration request requesting for IMS registration of the terminal, and sends configuration parameters for supporting an IMS service to the terminal according to the IMS registration request. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary for configuring the server. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

For technical effects brought by any design manner in the third aspect to the seventh aspect, reference may be made to the technical effects brought by the first aspect or any possible design manner in the foregoing aspect, and details are not repeated.

In an eighth aspect, an embodiment of the present application provides a terminal, where the terminal may implement the functions performed by the terminal in the above aspects or possible designs, and the functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions. Such as: the terminal may include: a transmitting unit and a receiving unit;

a sending unit, configured to send an IMS registration request for requesting IMS registration for the terminal to the configuration server, and a receiving unit, configured to receive a configuration parameter that is sent by the configuration server and supports IMS services.

The specific implementation manner of the terminal may refer to the behavior function of the terminal in the method for configuring the terminal parameter provided in the fifth aspect or any one of the possible designs of the foregoing aspects, and details are not repeated here. Thus, the terminal provided can achieve the same advantageous effects as the second aspect or any one of the possible designs of the above aspects.

In a ninth aspect, there is provided a terminal comprising: a processor and a memory; the memory is configured to store computer executable instructions, and when the terminal is running, the processor executes the computer executable instructions stored in the memory to cause the terminal to perform the method for configuring terminal parameters as set forth in the second aspect or any one of the above possible designs.

In a tenth aspect, there is provided a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform the method for configuring terminal parameters according to the second aspect or any one of the above possible designs.

In an eleventh aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method for configuring terminal parameters according to the second aspect or any one of the above possible designs.

In a twelfth aspect, a chip system is provided, where the chip system includes a processor and a communication interface, and is configured to support a terminal to implement the functions recited in the foregoing aspects, for example, the support processor sends an IMS registration request for requesting IMS registration for the terminal to a configuration server through the communication interface, and receives configuration parameters of the terminal sent by the configuration server. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary for the terminal. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

For technical effects brought by any design manner in the eighth aspect to the twelfth aspect, reference may be made to the technical effects brought by the second aspect or any possible design manner in the foregoing aspects, and details are not repeated.

In a thirteenth aspect, a system for configuring parameters of a terminal is provided, which includes the configuration server according to any design form of the third aspect to the seventh aspect, and the terminal according to any design form of the eighth aspect to the twelfth aspect.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

Drawings

Fig. 1 is a flowchart of a method for configuring a terminal parameter according to an embodiment of the present disclosure;

FIG. 2 is an IMS architecture diagram provided by an embodiment of the present application;

fig. 3 is a schematic diagram of an IMS registration flow;

fig. 4 is a block diagram of a communication device according to an embodiment of the present application;

fig. 5 is a flowchart of a method for configuring a terminal parameter according to an embodiment of the present disclosure;

fig. 6 is a flowchart of another method for configuring terminal parameters according to an embodiment of the present application;

fig. 7 is a flowchart of another method for configuring parameters of a terminal according to an embodiment of the present application;

fig. 8 is a flowchart of another method for configuring terminal parameters according to an embodiment of the present application;

fig. 9 is a flowchart of another method for configuring terminal parameters according to an embodiment of the present application;

fig. 10 is a flowchart of a method for updating configuration parameters of a terminal according to an embodiment of the present application;

fig. 11 is a flowchart of another method for updating configuration parameters of a terminal according to an embodiment of the present application;

fig. 12 is a flowchart of a method for updating configuration parameters of a terminal according to an embodiment of the present application;

fig. 13 is a block diagram of a configuration server according to an embodiment of the present application;

fig. 14 is a structural diagram of a terminal according to an embodiment of the present application.

Detailed Description

The main idea of the embodiment of the application is as follows: the configuration parameters of the terminal are pre-stored in a certain functional entity in the IMS, and when the terminal performs IMS registration, the configuration server in the IMS carries the configuration parameters of the terminal in a certain Session Initiation Protocol (SIP) signaling (e.g., 200OK) in the IMS registration flow and issues the configuration parameters to the terminal. The configuration parameters of the terminal related in the embodiments of the present application mainly refer to configuration parameters of a Service Level (Service Level), and may be referred to as IMS Service parameters of the terminal, where the configuration parameters of the terminal may be used to support IMS services, for example: the configuration parameters of the terminal may include parameters such as an Address (Address) of an IMS Proxy Session Control Function (P-CSCF), an SIP timer (SIP Timers), and a Pre-Cons support, and may also include other configuration parameters that can be delivered to the terminal through the scheme provided in the embodiment of the present application, without limitation. For example, fig. 1 is a flowchart of a method for configuring a terminal parameter according to an embodiment of the present disclosure, and as shown in fig. 1, the method may include steps 101 to 102:

step 101: the terminal sends an IMS registration request to the configuration server.

Step 102: the method comprises the steps that a configuration server receives an IMS registration request of a terminal and sends configuration parameters of the terminal to the terminal according to the IMS registration request, wherein the configuration parameters of the terminal are used for supporting IMS services; and the terminal receives the configuration parameters of the terminal sent by the configuration server to realize the configuration of the terminal parameters.

Wherein, the sending, by the configuration server, the configuration parameter of the terminal to the terminal according to the IMS registration request may include: the IMS registration request is used as a trigger condition for sending the configuration parameters of the terminal to the terminal by the configuration server, when the configuration server receives the IMS registration request, the configuration server is triggered to send the configuration parameters of the terminal to the terminal, or the IMS registration request comprises indication information used for indicating that the terminal supports a network element in the IMS to send the configuration parameters of the terminal, and the configuration server sends the configuration parameters of the terminal to the terminal according to the indication information.

The terminal may be a User Equipment (UE), such as: cell phones, computers, and may also be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, smart phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), computers, laptops, handheld communication devices, handheld computing devices, satellite radios, Wireless modem cards, Set Top Boxes (STBs), Customer Premises Equipment (CPE), and/or other devices used to communicate over a Wireless system.

The configuration server may be a certain functional entity deployed in the IMS shown in fig. 2, and the configuration server may interact with other functional entities in the IMS to perform the process of configuring the terminal parameters provided in the embodiment of the present application.

AS shown in fig. 2, the IMS may be deployed by a certain MNO, and may include a P-CSCF, an inquiry Session Control Function (I-CSCF), an S-CSCF, an HSS, and an AS, where in this embodiment, the configuration server may specifically be the S-CSCF or the P-CSCF, or may be an independently deployed device. Specifically, the HSS or S-CSCF or P-CSCF or AS in fig. 2 may store configuration parameters of the terminal, such AS: before executing the scheme provided by the embodiment of the present application, an operator may configure configuration parameters of a terminal on these functional entities in advance through an Operation Support System (OSS). The P-CSCF is equivalent to a boundary proxy server defined by SIP, and may be a first step of the terminal contacting the IMS, and is a point that the terminal first needs to access in a visited domain (or when roaming), and Session Initiation Protocol (SIP) MESSAGEs entering and exiting the IMS all pass through the P-CSCF. The I-CSCF essentially provides an entry to the home network, hides the topology of the home network from other networks, and finds out for a particular user, via the HSS, the corresponding S-CSCF, which is the point of contact for terminal roaming or foreign tasks into the local service provider network, and when it receives a request, it will route the request to the corresponding S-CSCF. The S-CSCF is mainly used to provide the user with the services subscribed to by the user. The HSS is mainly used to store S-CSCF capability sets associated with a user and corresponding user profiles, or other information, which the HSS can know the user' S current location and the services specified by the user, and which the various CSCFs in the IMS can query for. The AS refers to a server providing an application service to the terminal.

It should be noted that the terminal shown in fig. 2 may pass through the fourth generation (4)^thGeneration, 4G) network access to IMS, also via fifth Generation (5)^thGeneration, 5G) network access to IMS, without limitation. Furthermore, fig. 2 is only an exemplary framework diagram of the IMS, and the IMS may include other functional entities besides the functional entities shown in fig. 2, without limitation. Such as: the IMS may further include an independently deployed functional entity, which performs the function of the configuration server shown in fig. 1, that is, the configuration server may also be the independently deployed functional entity in fig. 2; the independent functional entity can interact with HSS, S-CSCF, P-CSCF and AS through undefined interfaces, so AS to realize the scheme for configuring the terminal parameters provided by the embodiment of the application.

Specifically, step 101 shown in fig. 1 may be a combination of some procedures in the existing IMS registration procedure, and the configuration parameters of the terminal in step 102 may be carried in some signaling in the existing IMS registration procedure and sent to the terminal. The existing IMS registration procedure, as shown in fig. 3, may include:

first, initial registration

The initial registration may include the processes shown in FIGS. 3 at 1-10: the terminal sends a REGISTER (REGISTER) request including the identifier of the terminal and the domain name (such as the address of the I-CSCF) of the terminal belonging to the found P-CSCF; the P-CSCF analyzes an Internet Protocol (IP) address of the I-CSCF by using the region name included in the registration request, and sends the registration request to the I-CSCF according to the address of the I-CSCF; I-CSCF receives the register Request, sends User Authorization Request (UAR) to HSS, receives User Authorization Answer (UAA) carrying S-CSCF capability set from HSS, selects one S-CSCF from S-CSCF capability set, and sends the register Request to S-CSCF; the method comprises the steps that S-CSCF receives a registration Request, sends a Multimedia Authentication Request (MAR) to HSS, and obtains a Multimedia authentication response (MAA) carrying an authentication vector set from HSS, if the S-CSCF finds that a terminal is not authorized according to the MAA, the S-CSCF sends a '401 Unauthorized' response to challenge the terminal, and then the registration authentication process shown in FIG. 3 is executed; otherwise, if the S-CSCF finds that the terminal is authorized according to the MAA, steps 16 to 20 shown in fig. 3 are executed, and the IMS registration of the terminal is successful.

Second, registration authentication

The registration authentication may include the processes 11-20 shown in FIG. 3: the terminal receives a response of '401 Unauthorized (Unauthorized)' and sends a REGISTER (REGISTER) request carrying the response of '401 Unauthorized (Unauthorized)' to the P-CSCF; the P-CSCF sends the registration request to the I-CSCF; the I-CSCF finds out the S-CSCF through interaction with the HSS, and sends a registration request comprising a '401 Unauthorized (Unauuthorized)' response to the S-CSCF; the S-CSCF checks the response, and if it is correct, sends the SAR to the HSS, obtains from the HSS an SAA carrying user service subscription data (Server Profile) and an Initial Filter Criteria (iFC) for instructing the S-CSCF to trigger the service, and sends a "200 OK" indicating that the registration request is accepted, that is, the IMS registration of the terminal is successful, and the terminal is successfully authorized. If the subsequent terminal needs to initiate a service application related to registration (e.g., a prompt tone and a prompt page for entering a multimedia service), i.e., service registration, steps 16 to 17 in the process may be executed, otherwise, steps 16 to 17 may not be executed.

Third, service registration

The service registration can also be called third party registration, and can comprise the processes 21-22 shown in FIG. 3: the S-CSCF sends a third party registration request to an AS serving for the user according to the obtained iFC, and informs the AS that the user is registered and can reach; if the AS agrees to provide the service for the terminal, then a '200 OK' is returned to the S-CSCF to indicate that the third party registration request is accepted, and the terminal can use the service provided by the AS.

In a possible design, the configuration server is a P-CSCF, the configuration parameters of the terminal are stored in the P-CSCF, the IMS registration request is the registration request in step 11 in fig. 3, and step 102 is implemented by step 20 in fig. 3, and includes: and the P-CSCF carries the configuration parameters of the terminal in the received 200OK and sends the configuration parameters to the terminal. In particular, this possible design may be referred to the scheme shown in fig. 5.

In yet another possible design, the configuration server is an S-CSCF in fig. 2, and the IMS registration request is a registration request in the authentication registration process in fig. 3; step 102 is realized through steps 18-20 shown in fig. 3, such as: and the S-CSCF carries the configuration parameters of the terminal in the 200OK and sends the configuration parameters to the terminal through the I-CSCF and the P-CSCF in sequence. In the method, the configuration parameters of the terminal are stored in the S-CSCF, or the S-CSCF acquires the configuration parameters from the HSS or the S-CSCF acquires the configuration parameters from the AS. In particular, this possible design can be referred to the solutions shown in fig. 6 to 9.

As can be seen from the above, when the terminal initiates the IMS registration process, the configuration server in the IMS can carry the configuration parameters of the terminal in the signaling in the IMS registration process with the aid of the existing IMS registration process and issue the configuration parameters to the terminal, and the configuration of the terminal parameters is also implemented while the IMS registration is implemented, so that the parameters are configured when the terminal is registered on the network side, and the OEM of the terminal and the operator do not need to perform negotiation and docking of the parameters, which saves time and cost. Meanwhile, the server storing the configuration parameters of the terminal is deployed at the network side, so that the terminal configuration parameters can be updated in time by an operator, and equipment of different OEMs can directly access the server to obtain the latest configuration parameters.

In order to implement the technical solution provided by the embodiment of the present application, the functional entities include: the HSS, S-CSCF, P-CSCF, AS, etc. may include the components shown in fig. 4. As shown in fig. 4, a block diagram of a communication device according to an embodiment of the present invention is provided, and the communication device 400 includes at least one processor 401, a communication line 402, a memory 403, and at least one communication interface 404. The processor 401, the memory 403 and the communication interface 404 may be connected by a communication line 402.

Processor 401 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement embodiments of the present Application, such as: one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs).

The communication link 402 may include a path for communicating information between the aforementioned components.

The communication interface 404 is used for communicating with other devices or a communication Network, and may use any transceiver or the like, such as ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), and the like.

The Memory 403 may be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory 403, which may be separate, is coupled to the processor 401 via a communication line 402. The memory 403 may also be integrated with the processor 401. The memory 403 is used for storing computer-executable instructions or application program codes for executing the scheme of the present application, and is controlled by the processor 401 to execute, so as to implement the method for configuring the terminal parameters provided in the following embodiments of the present application.

As one implementation, the processor 401 may include one or more CPUs such as CPU0 and CPU1 in fig. 4. As another implementation, the communication device 400 may include multiple processors, such as the processor 401 and the processor 407 in fig. 4. As yet another implementable manner, the communication device 400 may also include an output device 405 and an input device 406.

It should be noted that the communication device 400 may be a general-purpose device or a special-purpose device. For example, the communication device 400 may be a desktop computer, a laptop computer, a web server, a PDA, a mobile phone, a tablet computer, a wireless terminal, an embedded device, or a device having a similar structure as in fig. 4. The embodiment of the present application does not limit the type of the communication apparatus 400.

The method for configuring the terminal parameter provided in the embodiment of the present application may be applied to the IMS shown in fig. 2, and a description is made below on a scheme for configuring the terminal parameter provided in the embodiment of the present application, by taking a configuration server as a P-CSCF or an S-CSCF in fig. 2 as an example, in combination with the IMS shown in fig. 2. It should be noted that different MNOs may all deploy the IMS shown in fig. 2, and implement the scheme provided in the embodiment of the present application in combination with the deployed IMS, so as to implement parameter configuration for the terminal.

Assuming that the configuration server in fig. 1 is a P-CSCF, fig. 5 is a flowchart of a method for configuring parameters of a terminal according to an embodiment of the present application, in which the configuration parameters of the terminal are stored in the P-CSCF. As shown in fig. 5, the method may include steps 501 to 506:

step 501: the terminal sends a register request to the P-CSCF, and the P-CSCF sends the register request to the S-CSCF to execute initial register.

The registration request may be used to indicate IMS registration for the terminal, and specifically, the registration request may carry information of the terminal (such as an identifier of the terminal, or a serial number of the terminal, or a type of the terminal, and the like).

Optionally, the registration request further indicates, in an explicit manner, that the terminal supports the configuration parameter of the network element issuing terminal in the IMS, for example, the registration request may further carry indication information for indicating that the terminal supports the configuration parameter of the network element issuing terminal in the IMS, so as to explicitly indicate that the terminal supports the configuration parameter of the network element issuing terminal in the IMS; or, the registration request is further used to indicate, in an implicit manner, that the terminal supports the configuration parameter of the network element issuing terminal in the IMS, for example, the network element in the IMS stores description information of a plurality of terminals in advance, the description information of the terminal may be used to describe whether the terminal supports the configuration parameter of the network element issuing terminal in the IMS, the registration request carries information of the terminal, and after the network element in the IMS receives the information of the terminal, it may be determined whether the terminal corresponding to the information of the terminal supports the configuration parameter of the network element issuing terminal in the IMS according to the description information of the terminal stored in the network element in the IMS, where: a network side device (such as a configuration server) configures configuration parameters of a network element issuing terminal in an IMS supported by a terminal with a terminal type of 1, and then determines that the terminal sending the registration request supports the configuration parameters of the network element issuing terminal in the IMS when the type of the terminal carried in the registration request is 1.

Specifically, the step can refer to steps 1 to 5 in the initial registration process shown in fig. 3, and is not described again.

It should be noted that, in this embodiment of the present application, information (or parameters) carried in a registration request sent by a terminal to a P-CSCF, a registration request sent by the P-CSCF to an I-CSCF, and a registration request sent by the I-CSCF to an S-CSCF may be the same or different, and is not limited. However, in the process of sending the registration request, if the terminal sends the registration request to the P-CSCF, the registration request carries the terminal information and the indication information, where the indication information is used to indicate that the terminal supports the network element in the IMS to issue the configuration parameters of the terminal, and in the process of sending the registration request to the S-CSCF, the registration request may always carry the terminal information and the indication information.

Step 502: the S-CSCF receives the registration request, determines that the terminal is not authorized, and sends a "401 Unauthorized" response to the terminal, i.e., the terminal is not authorized.

Specifically, the step 502 can be described with reference to steps 6 to 10 in fig. 3, and is not described again.

Step 503: the terminal sends an IMS registration request to the P-CSCF.

The IMS registration request may be the registration request in step 11 shown in fig. 3. The IMS registration request may carry information of the terminal, and may also carry indication information or other information for indicating that the terminal supports the network element in the IMS to issue the configuration parameter of the terminal. Specifically, step 503 can be described with reference to step 11 in fig. 3, and is not described again.

Step 504: and the P-CSCF receives the IMS registration request, sends the IMS registration request to the S-CSCF, and the S-CSCF receives the IMS registration request.

Wherein, the sending, by the P-CSCF, the IMS registration request to the S-CSCF may include: and the P-CSCF sends an IMS registration request to the I-CSCF, the I-CSCF receives the IMS registration request, interacts with the HSS to select the S-CSCF, and sends the IMS registration request to the S-CSCF. Specifically, the step 504 can be described with reference to steps 12 to 15 in fig. 3, and is not described again.

It should be noted that, in this embodiment of the present application, information (or parameters) carried in an IMS registration request sent by a terminal to a P-CSCF, an IMS registration request sent by the P-CSCF to an I-CSCF, and an IMS registration request sent by the I-CSCF to an S-CSCF may be the same or different, and is not limited. However, in the process of sending the IMS registration request, if the terminal sends the IMS registration request to the P-CSCF, the IMS registration request may always carry the terminal information and the indication information, if the terminal carries the terminal information and the indication information for indicating that the terminal supports the network element in the IMS to issue the configuration parameters of the terminal.

Step 505: the S-CSCF sends a 200OK to the P-CSCF.

The 200OK corresponds to the IMS registration request and is used to indicate that IMS registration of the terminal is successful, and the S-CSCF may send the 200OK to the I-CSCF in the SAA received from the HSS, and the I-CSCF sends the 200OK to the P-CSCF. Specifically, step 505 can be described with reference to steps 16 to 19 in fig. 3, and is not described again.

Step 506: and the P-CSCF receives the 200OK, carries the configuration parameters of the terminal in the 200OK and sends the configuration parameters to the terminal.

When the IMS registration request carries indication information for indicating that the terminal supports the network element in the IMS to issue the configuration parameter of the terminal, the P-CSCF may, according to the indication information, carry the configuration parameter of the terminal stored in the P-CSCF in 200OK and issue the configuration parameter to the terminal after receiving the 200 OK; otherwise, once the P-CSCF receives the 200OK, it is triggered to carry the configuration parameters of the terminal stored by itself in the 200OK and send them to the terminal.

Specifically, the process of the P-CSCF sending the 200OK to the terminal may be described with reference to step 20 in fig. 3, and is not described again.

It should be noted that, if the S-CSCF determines that the terminal is authorized in step 502, in the scheme shown in fig. 5, after the S-CSCF determines that the terminal is authorized, step 505 and step 506 may be directly performed to implement issuing the configuration parameters of the terminal without performing step 503 and step 504, where in this possible scheme, the 200OK sent by the S-CSCF to the P-CSCF is the 200OK corresponding to the registration request in step 501.

Compared with the prior art, in the scheme shown in fig. 5, the configuration parameters of the terminal are stored in the P-CSCF, and when the terminal performs IMS registration, the configuration parameters of the terminal are carried in 200OK and sent to the terminal, and the terminal parameters are not required to be configured through negotiation between an OEM of the terminal and an operator, which saves time and cost. Meanwhile, the P-CSCF in which the configuration parameters of the terminal are stored is deployed at the network side, so that the terminal configuration parameters can be updated in time by an operator, and equipment of different OEMs can be directly accessed to the P-CSCF to obtain the latest configuration parameters.

Assuming that the configuration server in fig. 1 is an S-CSCF, fig. 6 is a flowchart of a method for configuring parameters of a terminal according to an embodiment of the present application, in which the configuration parameters of the terminal are stored in the S-CSCF, as shown in fig. 6, the method may include steps 601 to 605:

step 601: the terminal sends a register request to the P-CSCF, and the P-CSCF sends the register request to the S-CSCF to execute initial register.

The registration request and the execution process in this step may refer to those in step 501, and are not described again.

Step 602: the S-CSCF receives the registration request, determines that the terminal is not authorized, and sends a "401 Unauthorized" response to the terminal, i.e., the terminal is not authorized.

Specifically, the step 602 can be described with reference to steps 6 to 10 in fig. 3, and is not described again.

Step 603: the terminal sends an IMS registration request to the P-CSCF, the P-CSCF receives the IMS registration request, the S-CSCF sends the IMS registration request to the S-CSCF, and the S-CSCF receives the IMS registration request.

The description of the IMS registration request in step 603 may refer to step 503, and step 503 may refer to steps 11 to 15 shown in fig. 3, which is not described again.

In the process, the S-CSCF may select the S-CSCF, which stores the configuration parameters of the terminal, for the I-CSCF. In a possible design, an operator prestores configuration parameters of a terminal in each S-CSCF in an IMS system, and in step 14, an I-CSCF selects one S-CSCF from a set of S-CSCF capabilities acquired by an HSS according to the prior art or a random mode, and sends an IMS registration request to the S-CSCF; or, in another possible design, part of S-CSCFs in the IMS store configuration parameters of the terminal, when the HSS issues an S-CSCF capability set to the I-CSCF in step 15, the S-CSCF capability set includes a tag of the S-CSCF, where the tag of the S-CSCF is used to indicate whether the S-CSCF stores the configuration parameters of the terminal, and after the I-CSCF obtains the S-CSCF capability set from the HSS, the I-CSCF selects an S-CSCF stored with the configuration parameters of the terminal according to the tag of the S-CSCF, and sends an IMS registration request to the S-CSCF.

Step 604: S-CSCF sends SAR to HSS, HSS receives SAR, sends SAA to S-CSCF, and S-CSCF receives SAA.

Step 604 can be described with reference to steps 16 to 17 in fig. 3, and is not described again.

So far, the S-CSCF determines that the IMS registration of the terminal is successful.

Step 605: and the S-CSCF carries the configuration parameters of the terminal in the 200OK and sends the 200OK to the terminal.

The description of the 200OK can be referred to in step 505. The manner in which the S-CSCF sends the 200OK to the terminal may refer to the processes shown in steps 18 to 20 of fig. 3, and will not be described again.

Specifically, when the IMS registration request carries indication information for indicating that the terminal supports the network element in the IMS to issue the configuration parameter of the terminal, the S-CSCF may, according to the indication information, after determining that the IMS registration of the terminal is successful, carry the configuration parameter of the terminal stored therein in 200OK, and issue the configuration parameter to the terminal; otherwise, when the IMS registration request does not carry the indication information, the S-CSCF may trigger the terminal to carry the configuration parameters of the terminal stored in itself in 200OK and issue the configuration parameters to the terminal after determining that the IMS registration of the terminal is successful.

It should be noted that, if the S-CSCF determines that the terminal is authorized in step 602, in the scheme shown in fig. 6, after the S-CSCF determines that the terminal is authorized, step 605, or step 604 and step 605 may be directly performed, so as to implement issuing the configuration parameters of the terminal without performing step 603, where in this possible scheme, the 200OK sent by the S-CSCF to the P-CSCF is the 200OK corresponding to the registration request in step 601.

Compared with the prior art, in the scheme shown in fig. 6, the configuration parameters of the terminal are stored in the S-CSCF, and when the terminal performs IMS registration, the configuration parameters of the terminal are carried in 200OK and issued to the terminal, and the terminal parameters do not need to be configured through negotiation between the OEM of the terminal and the operator, which saves time and cost. Meanwhile, the S-CSCF in which the configuration parameters of the terminal are stored is deployed at the network side, so that the terminal configuration parameters can be updated in time by an operator, and equipment of different OEMs can be directly accessed to the S-CSCF to obtain the latest configuration parameters.

Assuming that the configuration server in fig. 1 is an S-CSCF, fig. 7 is a flowchart of a method for configuring parameters of a terminal according to an embodiment of the present application, in which the configuration parameters of the terminal are stored in an HSS, as shown in fig. 7, the method may include steps 701 to 705:

step 701: the terminal sends a register request to the P-CSCF, and the P-CSCF sends the register request to the S-CSCF to execute initial register.

Step 702: the S-CSCF receives the registration request, determines that the terminal is not authorized, and sends a "401 Unauthorized" response to the terminal, i.e., the terminal is not authorized.

Specifically, the step 702 can be described with reference to steps 6 to 10 in fig. 3, and is not described again.

Step 703: the terminal sends an IMS registration request to the P-CSCF, the P-CSCF receives the IMS registration request, the S-CSCF sends the IMS registration request to the S-CSCF, and the S-CSCF receives the IMS registration request.

The relevant description of the IMS registration request in step 703 may refer to step 503, and step 703 may refer to steps 11 to 15 shown in fig. 3, which is not described again.

Step 704: S-CSCF sends SAR to HSS, HSS receives SAR, sends SAA to S-CSCF, and S-CSCF receives SAA.

The SAR may include information of the terminal, or information of the terminal and indication information for indicating that the terminal supports the network element in the IMS to issue the configuration parameter of the terminal. The SAA may include configuration parameters of the terminal.

Specifically, the S-CSCF may carry information and indication information of the terminal in the IMS registration request in the SAR and send the information to the HSS, and the HSS may carry configuration parameters of the terminal stored by the HSS in the SAA according to the indication information and send the configuration parameters to the S-CSCF; otherwise, when the HSS receives the SAR, the HSS is triggered to carry the configuration parameters of the terminal stored by the HSS in the SAA and send the configuration parameters to the S-CSCF.

Step 705: and the S-CSCF carries the received configuration parameters of the terminal in the SAA on 200OK and sends the 200OK to the terminal.

Compared with the prior art, in the scheme shown in fig. 7, the configuration parameters of the terminal are stored in the HSS, and when the terminal performs IMS registration, the configuration parameters of the terminal are carried in 200OK and are issued to the terminal, and the terminal parameters are not required to be configured through negotiation between an OEM of the terminal and an operator, so that time and cost are saved. Meanwhile, the HSS in which the configuration parameters of the terminal are stored is deployed at the network side, so that the terminal configuration parameters can be updated in time by an operator, and equipment of different OEMs can be directly accessed to the HSS to obtain the latest configuration parameters.

Assuming that the configuration server in fig. 1 is an S-CSCF, fig. 8 is a flowchart of a method for configuring parameters of a terminal according to an embodiment of the present application, in which the configuration parameters of the terminal are stored in an AS. As shown in fig. 8, the method may include steps 801 to 807:

step 801: the terminal sends a register request to the P-CSCF, and the P-CSCF sends the register request to the S-CSCF to execute initial register.

Step 802: the S-CSCF receives the registration request, determines that the terminal is not authorized, and sends a "401 Unauthorized" response to the terminal, i.e., the terminal is not authorized.

Specifically, step 802 can be described with reference to steps 6 to 10 in fig. 3, and is not described again.

Step 803: the terminal sends an IMS registration request to the P-CSCF, the P-CSCF receives the IMS registration request, the S-CSCF sends the IMS registration request to the S-CSCF, and the S-CSCF receives the IMS registration request.

The description of the IMS registration request in step 803 may refer to step 503, and step 803 may refer to steps 11 to 15 shown in fig. 3, which are not described again.

Step 804: S-CSCF sends SAR to HSS, HSS receives SAR, sends SAA to S-CSCF, and S-CSCF receives SAA.

The SAA may include an iFC, and the iFC may be used to instruct an S-CSCF to trigger a service.

Specifically, step 804 can be described with reference to steps 16 to 17 in fig. 3, and is not described again.

Step 805: and the S-CSCF sends a third party registration request to the AS according to the iFC.

Step 805 can refer to step 21 shown in fig. 3, and is not described again.

Step 806: and the S-CSCF waits for and receives the 200OK corresponding to the third party registration request returned by the AS.

The 200OK corresponding to the third registration request may carry configuration parameters of the terminal.

Specifically, the S-CSCF may wait and receive a 200OK corresponding to the third party registration request returned by the AS according to the waiting indication. The waiting indication may be preconfigured on the S-CSCF by the operator through local configuration in advance, or the waiting indication may be carried in the iFC in step 804.

The waiting indication may be used to indicate that the S-CSCF issues a 200OK corresponding to the IMS registration request to the terminal after receiving a response message corresponding to the third-party registration request returned by the AS, where the response message is the 200OK corresponding to the third-party registration request, or a failed response message, or the like, that is, after the S-CSCF determines that the IMS registration of the terminal is successful, the S-CSCF does not immediately return the 200OK corresponding to the IMS registration request to the terminal, but first sends the third-party registration request to the AS, then waits for a response message (200OK or a failed response message) returned by the AS, and returns the 200OK corresponding to the registration request to the terminal after waiting for the response message returned by the AS or exceeding a preset time (the response message returned by the AS is still not received).

Specifically, in order to avoid that the S-CSCF waits indefinitely for a response message returned by the AS, a timer may be set on the S-CSCF, where the timer is used to limit a duration for the S-CSCF to wait for the response message returned by the AS, and if the timer is overtime and the S-CSCF does not yet receive the response message returned by the AS, the S-CSCF directly sends a 200OK to the terminal, where the 200OK does not carry configuration parameters of the terminal.

Step 807: and the S-CSCF carries the configuration parameters of the terminal in a 200OK corresponding to the IMS registration request and sends the 200OK to the terminal.

The manner in which the S-CSCF sends the 200OK to the terminal may refer to the processes shown in steps 18 to 20 in fig. 3, and will not be described again.

It should be noted that, if the S-CSCF waits for and receives the response message returned by the AS and indicating that the response message is a failure in step 806, the S-CSCF may also execute step 807, except that the 200OK sent by the S-CSCF does not carry the configuration parameters of the terminal at this time. In addition, if the S-CSCF determines that the terminal is authorized in step 802, the scheme shown in fig. 8 may not perform step 803, but directly perform step 804 to step 807 to implement issuing the configuration parameters of the terminal, where in the possible scheme, the 200OK issued by the S-CSCF to the P-CSCF is the 200OK corresponding to the registration request in step 801.

Compared with the prior art, in the scheme shown in fig. 8, the configuration parameters of the terminal are stored in the AS, and when the terminal performs IMS registration, the configuration parameters of the terminal are carried in 200OK and sent to the terminal, and the terminal parameters are not required to be configured through negotiation between an OEM of the terminal and an operator, so that time and cost are saved. Meanwhile, the AS stored with the configuration parameters of the terminal is deployed at the network side, so that the terminal configuration parameters can be updated in time by an operator, and equipment of different OEMs can be directly accessed to the AS to acquire the latest configuration parameters.

Optionally, in the solutions shown in fig. 5 to fig. 8, the configuration parameters of the terminal may be carried in a 200OK in the form of Extensible Markup Language (XML), where the 200OK may be a User Datagram Protocol (UDP) packet. When a 200OK cannot carry configuration parameters of a terminal, for example: the 200OK has 8 bytes of idle payload that can carry some information, and the configuration parameter of the terminal occupies 16 bytes, and a TCP packet can be sent instead in a Transmission Control Protocol (TCP) layer, that is, the 200OK carrying the configuration parameter of the terminal is sent through the TCP packet.

The above-mentioned solutions shown in fig. 5 to fig. 8 only take the example of issuing the configuration parameters of the terminal to the terminal through 200OK corresponding to the IMS registration request as an example, and describe the technical solution provided in the embodiment of the present application, in yet another feasible solution, after the third registration of the terminal is successful, the configuration parameters of the terminal may also be issued to the terminal through a newly added signaling (e.g. SIP MESSAGE, or a notification message, etc.), and specifically, the feasible solution is shown in fig. 9.

Fig. 9 is a flowchart of a method for configuring parameters of a terminal according to an embodiment of the present application, where in the method, the configuration parameters of the terminal are stored in an AS, and the AS may be a first AS preferentially triggered by an S-CSCF according to an iFC, or may be any one of multiple ASs triggered by the S-CSCF according to the iFC, without limitation. As shown in fig. 9, the method may include steps 901 to 908:

step 901: the terminal sends a register request to the P-CSCF, and the P-CSCF sends the register request to the S-CSCF to execute initial register.

Step 902: the S-CSCF receives the registration request, determines that the terminal is not authorized, and sends a "401 Unauthorized" response to the terminal, i.e., the terminal is not authorized.

Specifically, the step 902 can be described with reference to steps 6 to 10 in fig. 3, and is not described again.

Step 903: the terminal sends an IMS registration request to the P-CSCF, the P-CSCF receives the IMS registration request, the S-CSCF sends the IMS registration request to the S-CSCF, and the S-CSCF receives the IMS registration request.

The description of the IMS registration request in step 903 may refer to step 503, and step 903 may refer to steps 11 to 15 shown in fig. 3, which is not described again.

Step 904: S-CSCF sends SAR to HSS, HSS receives SAR, sends SAA to S-CSCF, S-CSCF receives SAA, and sends 200OK to terminal.

Specifically, step 904 can be described with reference to steps 16 to 20 in fig. 3, and is not described again.

Step 905: and the S-CSCF sends a third party registration request to the AS according to the iFC.

Step 905 can refer to step 21 shown in fig. 3, and is not described again.

Step 906: and the AS receives the third party registration request, determines that the third party registration of the terminal is successful, and sends 200OK to the S-CSCF.

Step 906 can refer to step 22 shown in fig. 3, and is not described again.

Step 907: the AS sends SIP MESSAGE to the S-CSCF.

SIP MESSAGE carries the configuration parameters of the terminal.

Step 908: the S-CSCF sends SIP MESSAGE to the terminal.

Wherein the S-CSCF sending SIP MESSAGE to the terminal may include: the S-CSCF sends SIP MESSAGE to the I-CSCF, the I-CSCF receives the SIP MESSAGE, sends SIP MESSAGE to the P-CSCF, and the P-CSCF sends SIP MESSAGE to the terminal.

It should be noted that, in this embodiment of the present application, the S-CSCF sends SIP MESSAGE to the I-CSCF, the I-CSCF receives the SIP MESSAGE, and sends SIP MESSAGE to the P-CSCF, and the information (or parameters) carried in the SIP MESSAGE sent by the P-CSCF to the terminal may be the same or different, which is not limited. However, in the process of sending SIP MESSAGE, the configuration parameters of the terminal in SIP MESSAGE must exist to ensure that the configuration parameters of the terminal are issued to the terminal.

The SIP MESSAGE can be replaced by a notification message or other types of messages, without limitation. Such as: the notification message carrying the configuration parameters of the terminal can be sent to the terminal in an implicit subscription mode.

Further, the scheme shown in fig. 9 may further include: after receiving SIP MESSAGE, the terminal returns 200OK corresponding to SIP MESSAGE to AS, for example: the terminal sends a 200OK corresponding to SIP MESSAGE to the P-CSCF, which sends the 200OK to the I-CSCF, which sends the 200OK to the S-CSCF, which sends the 200OK to the AS, indicating that the terminal successfully received SIP MESSAGE.

It should be noted that, in the scheme shown in fig. 9, when the length of the configuration parameter of the terminal is greater than the length of SIP MESSAGE, that is, one SIP MESSAGE cannot carry the configuration parameter of the terminal, the configuration parameter of the terminal may be carried by multiple pieces of SIP MESSAGE.

Compared with the prior art, in the scheme shown in fig. 9, the configuration parameters of the terminal are stored in the AS, and when the terminal performs IMS registration, the configuration parameters of the terminal are carried in SIP MESSAGE and sent to the terminal, so that the terminal parameters do not need to be configured through negotiation between the OEM of the terminal and the operator, and time and cost are saved. Meanwhile, the AS stored with the configuration parameters of the terminal is deployed at the network side, so that the terminal configuration parameters can be updated in time by an operator, and equipment of different OEMs can be directly accessed to the AS to acquire the latest configuration parameters.

Further, in order to realize timely update of the configuration parameters of the terminal, the embodiment of the application further provides an update process of the configuration parameters of the terminal. The following describes a configuration parameter update procedure of a terminal according to an embodiment of the present application, with reference to the scheme shown in fig. 10, or fig. 11, or fig. 12, by taking an example of updating a configuration parameter of a terminal stored in an S-CSCF.

In one feasible scheme, updated configuration parameters are sent to the terminal through a re-registration process of the terminal. As shown in fig. 10, a configuration parameter updating process for a terminal provided in the embodiment of the present application includes:

step 1001: the terminal sends a re-registration request to the P-CSCF.

Wherein, the re-registration request can be used to request the terminal to re-perform IMS registration. The re-registration request may include information of the terminal, or indication information for indicating that the terminal supports the network element in the IMS to issue the configuration parameters of the terminal, or information of the terminal and indication information for indicating that the terminal supports the network element in the IMS to issue the configuration parameters of the terminal, and the like. The related description of the information of the terminal can be referred to fig. 5, and is not repeated.

Specifically, the process of sending the re-registration request to the P-CSCF by the terminal is the same as the process of sending the IMS registration request to the P-CSCF by the terminal, and is not described again.

Step 1002: and the P-CSCF receives the re-registration request, sends the re-registration request to the S-CSCF, and the S-CSCF receives the re-registration request.

Wherein, the sending, by the P-CSCF, the re-registration request to the S-CSCF may include: and the P-CSCF sends a re-registration request to the I-CSCF, the I-CSCF receives the re-registration request, the I-CSCF interactively selects the S-CSCF with the HSS, and the re-registration request is sent to the S-CSCF. Specifically, the process of sending the IMS registration request to the S-CSCF by the P-CSCF in fig. 3 may be referred to when the P-CSCF sends the re-registration request to the S-CSCF, and details are not repeated.

It should be noted that, in the embodiment of the present application, information (or parameters) carried in a re-registration request sent by a terminal to a P-CSCF, a re-registration request sent by a P-CSCF to an I-CSCF, and a re-registration request sent by an I-CSCF to an S-CSCF may be the same or different, and is not limited. However, in the process of sending the re-registration request, if the re-registration request carries indication information for indicating that the terminal supports the network element in the IMS to issue the configuration parameters of the terminal, the re-registration request may always carry the indication information in the process of sending the re-registration request to the S-CSCF by the P-CSCF.

Step 1003: and the S-CSCF detects that the configuration parameters of the terminal stored by the S-CSCF are updated, and carries the updated configuration parameters of the terminal in the re-registration response to send the re-registration response to the terminal.

The re-registration response corresponds to the re-registration request and can be used for indicating that the IMS re-registration of the terminal is successful. The re-registration response may be 200 OK.

Specifically, the S-CSCF detecting that the configuration parameter of the terminal stored in the S-CSCF is updated may include: the re-registration request in step 1001 may further include a timestamp of the terminal receiving the configuration parameter last time, the S-CSCF obtains the timestamp of the terminal receiving the configuration parameter last time from the re-registration request, and the S-CSCF senses that the configuration parameter of the terminal stored by the S-CSCF is updated, and if the S-CSCF senses that the timestamp of the terminal stored by the S-CSCF is updated, it is determined that the configuration parameter of the terminal stored by the S-CSCF is updated; alternatively, the first and second electrodes may be,

the S-CSCF records a timestamp of the configuration parameter which is sent to the terminal last time by the S-CSCF and a timestamp which is used for perceiving that the configuration parameter of the terminal stored by the S-CSCF is updated, and if the timestamp which is used for perceiving that the configuration parameter of the terminal stored by the S-CSCF is updated is newer, the configuration parameter of the terminal stored by the S-CSCF is determined to be updated.

Specifically, once the S-CSCF detects that the configuration parameters of the terminal stored in the S-CSCF are updated, the S-CSCF is triggered to send the configuration parameters updated by the terminal to the terminal by carrying the configuration parameters in the re-registration response; or the re-registration request comprises indication information used for indicating the terminal to support the network element in the IMS to issue the configuration parameters of the terminal, and the S-CSCF carries the configuration parameters updated by the terminal in the re-registration response and sends the re-registration response to the terminal; or the S-CSCF records the indication information which is carried in the IMS registration request sent before the P-CSCF and used for indicating the terminal to support the network element in the IMS to send the configuration parameters of the terminal, and carries the configuration parameters updated by the terminal in the re-registration response according to the recorded indication information and sends the re-registration response to the terminal. The process of sending the re-registration response to the terminal by the S-CSCF may refer to the process of sending the 200OK to the terminal by the S-CSCF, which is not described again.

It should be noted that the S-CSCF in the scheme shown in fig. 10 may also be replaced with other functional entities storing the configuration parameters of the terminal, such AS an HSS, an AS, a P-CSCF, and the like, and the process of updating the configuration parameters of the terminal by these functional entities may refer to the scheme shown in fig. 10, for example: when the HSS stores the configuration parameters of the terminal, after step 1002 is executed, the S-CSCF sends the SAR to the HSS, the HSS receives the SAR, and when it detects that the configuration parameters of the terminal stored by the HSS are updated, the S-CSCF sends an SAA carrying the updated configuration parameters of the terminal to the S-CSCF, and the S-CSCF receives the SAA and sends a re-registration response carrying the updated configuration parameters of the terminal to the terminal.

When the configuration parameters of the terminal stored in the AS are stored, after step 1002 is executed, the S-CSCF may send an SAR to the HSS, the HSS receives the SAR, send an SAA to the S-CSCF, the S-CSCF receives the SAA, and sends a third party registration request to the AS, and when the AS detects that the configuration parameters of the terminal stored in itself are updated, the AS sends a response message (e.g., 200OK corresponding to the third party registration) carrying the updated configuration parameters of the terminal to the S-CSCF, and the S-CSCF receives the response message and sends a re-registration response carrying the updated configuration parameters of the terminal to the terminal.

When the configuration parameters of the terminal stored in the P-CSCF are stored, after step 1002 is executed, if the S-CSCF determines that the terminal re-registration is successful, the re-registration response is sent to the P-CSCF, and the P-CSCF receives the re-registration response.

The method for detecting the update of the configuration parameters of the terminal stored by the HSS, AS, and P-CSCF may refer to step 1003, and is not described again.

In another possible solution, the configuration parameters of the terminal are updated through a subscription mechanism. As shown in fig. 11, a process for updating configuration parameters of another terminal provided in the embodiment of the present application includes:

step 1101: the terminal sends a subscription request to the S-CSCF, and the S-CSCF receives the subscription request.

The subscription request is used for requesting the S-CSCF to send a notification to the terminal when the configuration parameters of the terminal are updated. The subscription request may carry information of the terminal or other information, and the information of the terminal may be described with reference to fig. 5, which is not described again.

Specifically, the sending, by the terminal, the subscription request to the S-CSCF may include: and the terminal sends a subscription request to the P-CSCF, and the P-CSCF sends the subscription request to the S-CSCF.

It should be noted that, in the embodiment of the present application, information (or parameters) carried in the subscription request sent by the terminal to the P-CSCF and the subscription request sent by the P-CSCF to the S-CSCF may be the same or different, and is not limited.

Step 1102: and the S-CSCF detects that the configuration parameters of the terminal are updated, and the S-CSCF sends an event notification to the terminal.

Wherein, the event notification carries the configuration parameters updated by the terminal.

Specifically, the S-CSCF may send the event notification to the terminal when detecting that the configuration parameter of the terminal stored in the S-CSCF is updated, where the step 1003 is referred to for detecting that the configuration parameter of the terminal stored in the S-CSCF is updated, and no further description is given, or receive, from the HSS, Data Update information (Cx-Update _ Subscr _ Data) carrying the updated configuration parameter of the terminal, detect that the configuration parameter of the terminal is updated according to the Data Update information, and send the event notification to the terminal.

Specifically, the sending, by the S-CSCF, the event notification to the terminal may include: and the S-CSCF sends an event notification to the P-CSCF, and the P-CSCF sends the event notification to the terminal.

It should be noted that, in this embodiment of the present application, the S-CSCF sends the event notification to the P-CSCF, and information (or parameters) carried in the event notification sent by the P-CSCF to the terminal may be the same or different, which is not limited. However, during the sending process, the updated configuration parameters of the terminal must be included in the event notification.

In addition, the S-CSCF in the solution shown in fig. 11 may also be replaced with other functional entities storing configuration parameters of the terminal, such AS an AS, a P-CSCF, and the like, except that, when the S-CSCF in the solution shown in fig. 11 is replaced with an AS, the sending, by the terminal, the subscription request to the AS may include: the terminal sends a subscription request to the P-CSCF, the P-CSCF sends a subscription request to the S-CSCF, and the S-CSCF sends a subscription request to the AS. The AS transmitting the event notification to the terminal may include: and the AS sends an event notification to the S-CSCF, the S-CSCF sends the event notification to the P-CSCF, and the P-CSCF sends the event notification to the terminal. And, when the S-CSCF in the scheme illustrated in fig. 11 is replaced by an AS, the scheme may further include: and after receiving the event notification, the terminal returns a response message (ACK) to the P-CSCF, and after receiving the ACK, the P-CSCF sends 200OK to the AS to indicate that the terminal successfully receives the event notification.

In another feasible scheme, when the S-CSCF detects that the configuration parameters of the terminal stored in the S-CSCF are updated, the S-CSCF actively issues the updated configuration parameters of the terminal through SIP MESSAGE. As shown in fig. 12, a configuration parameter updating process for another terminal provided in the embodiment of the present application includes:

step 1201: and the S-CSCF detects that the configuration parameters of the terminal are updated.

The method for detecting that the configuration parameter of the terminal is updated by the S-CSCF may refer to step 1003, which is not described herein again.

Step 1202: and the S-CSCF carries the updated configuration parameters of the terminal in SIP MESSAGE and sends the configuration parameters to the terminal.

Specifically, once the S-CSCF detects that the configuration parameters of the terminal stored in the S-CSCF are updated, the S-CSCF is triggered to carry the updated configuration parameters of the terminal in SIP MESSAGE and send the parameters to the terminal; or the S-CSCF records the indication information which is carried in the IMS registration request sent before the P-CSCF and used for indicating the terminal to support the network element in the IMS to send the configuration parameters of the terminal, and carries the configuration parameters updated by the terminal in SIP MESSAGE according to the recorded indication information and sends the configuration parameters to the terminal. The process of sending SIP MESSAGE to the terminal by the S-CSCF is described with reference to step 908 and will not be described in detail.

Further, the scheme shown in fig. 12 may further include: and the terminal sends 200OK corresponding to SIP MESSAGE to the S-CSCF through the P-CSCF and the I-CSCF to indicate that the terminal successfully receives SIP MESSAGE carrying the updated configuration parameters of the terminal.

It should be noted that, the S-CSCF in the solution shown in fig. 12 may also be replaced with other functional entities storing the configuration parameters of the terminal, such AS an HSS, an AS, a P-CSCF, and the like, and the process of updating the configuration parameters of the terminal by these functional entities may refer to the solution shown in fig. 12, for example: the configuration parameters of the terminal are stored in the HSS, when the HSS detects that the stored configuration parameters of the terminal are updated, the HSS sends Data Update information (Cx-Update _ subsccr _ Data) carrying the updated configuration parameters of the terminal to the S-CSCF, and after receiving the Data Update information, the S-CSCF sends SIP MESSAGE carrying the updated configuration parameters of the terminal to the terminal, wherein the manner of sending SIP MESSAGE to the terminal by the S-CSCF is as described in step 1202; and, after the S-CSCF receives the 200OK corresponding to SIP MESSAGE returned by the terminal, the S-CSCF returns a Data Update response (Cx-Update _ subsccr _ Data Resp) to the HSS; or after the S-CSCF sends SIP MESSAGE carrying the updated configuration parameters of the terminal to the terminal, the S-CSCF may return a data update response to the HSS, and does not need to send the data update response to the HSS after receiving the 200OK corresponding to SIP MESSAGE.

And once the AS detects that the stored configuration parameters of the terminal are updated, the AS is triggered to send SIP MESSAGE carrying the updated configuration parameters of the terminal to the S-CSCF, and the S-CSCF sends the SIP MESSAGE to the terminal, or the AS detects that the stored configuration parameters of the terminal are updated and sends SIP MESSAGE carrying the updated configuration parameters of the terminal to the S-CSCF after receiving a third party registration request sent by the S-CSCF, and the S-CSCF sends the SIP MESSAGE to the terminal. The way in which the S-CSCF sends SIP MESSAGE to the terminal is as described in step 1202. In this implementation manner, the terminal may further return a 200OK corresponding to SIP MESSAGE to the AS through the P-CSCS and the S-CSCF after receiving the configuration parameter carrying the updated terminal.

The parameters of the terminal are stored in the P-CSCF, and when the P-CSCF detects that the stored configuration parameters of the terminal are updated, the P-CSCF sends SIP MESSAGE carrying the updated configuration parameters of the terminal to the terminal.

The method for detecting the update of the configuration parameters of the terminal stored by the HSS, AS, and P-CSCF may refer to step 1201, and is not described again.

Optionally, in the processes shown in fig. 10 to 12, when part of the parameters of the terminal are updated, the configuration parameters of the whole terminal may be issued to the terminal, or only the updated configuration parameters in the configuration parameters of the terminal may be issued to the terminal, without limitation. Such as: assuming that the configuration parameters of the terminal include 10 parameters, wherein 5 parameters are updated, at this time, all the configuration parameters including the 5 updates may be packaged and sent to the terminal, or only the 5 updated parameters may be sent to the terminal, so as to reduce redundancy when sending a message.

The above-mentioned scheme provided by the embodiments of the present application is mainly introduced from the perspective of interaction between the nodes. It is understood that each node, for example, a configuration server, a terminal, etc., contains corresponding hardware structures and/or software modules for performing each function in order to realize the functions. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the configuration server and the terminal may be divided into the functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

In the case of dividing the function modules by corresponding functions, fig. 13 shows a schematic diagram of a possible configuration server, which may be used to execute the functions of the S-CSCF or the P-CSCF in the above embodiments. As shown in fig. 13, the configuration server may include: a receiving unit 130, a transmitting unit 131;

a receiving unit 130, configured to receive an IMS registration request of the terminal for requesting IMS registration for the terminal, and a sending unit 131, configured to send a configuration parameter for supporting an IMS service to the terminal according to the IMS registration request.

Further, the configuration server shown in fig. 13 further includes a detecting unit 132 configured to detect that the configuration parameter of the terminal is updated, and a sending unit 131, further configured to carry the updated configuration parameter of the terminal in SIP MESSAGE to send the updated configuration parameter to the terminal.

Further, the receiving unit 130 is further configured to receive a re-registration request that is sent by the terminal and used for requesting to re-perform IMS registration on the terminal, and the sending unit 131 is further configured to, when the configuration parameter of the terminal stored in the configuration server is updated, carry the updated configuration parameter of the terminal in a re-registration response for indicating that IMS re-registration of the terminal is successful, and send the re-registration response to the terminal.

Further, the receiving unit 130 is further configured to receive a subscription request sent by the terminal and used for requesting the configuration server to send a notification to the terminal when the configuration parameter of the terminal is updated, and the sending unit 131 is further configured to send an event notification to the terminal carrying the updated configuration parameter of the terminal when the configuration parameter of the terminal stored in the configuration server is updated.

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again. The configuration server provided by the embodiment of the application is used for executing the method for configuring the terminal parameters, so that the same effect as the method for configuring the terminal parameters can be achieved.

In the case of using an integrated unit, an embodiment of the present application provides a communication device, which may exist in a product form of a chip, and is configured to perform the function of configuring a server in the foregoing embodiment, and the apparatus may include: a processing module and a communication module. The processing module is used to control and manage the actions of the device, e.g., the processing module is used to support the device to perform other processes of the techniques described herein. The communication module is used to support communication between the apparatus and other network entities, for example, the functional module or the network entity shown in fig. 2. The apparatus may also include a storage module to store the program code and data for the apparatus.

The processing module may be a processor or a controller. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, a DSP and a microprocessor, or the like. The communication module may be a transceiver circuit or a communication interface, etc. The storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the apparatus according to the embodiment of the present application may be the communication device shown in fig. 4.

Fig. 14 shows a schematic diagram of a possible composition of a terminal, which may be used to perform the functions of the terminal referred to in the above embodiments. As shown in fig. 14, the terminal may include: a transmitting unit 140 and a receiving unit 141;

a sending unit 140, configured to send an IMS registration request for requesting IMS registration for the terminal to the configuration server; a receiving unit 141, configured to receive the configuration parameters for supporting the IMS service sent by the configuration server.

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again. The terminal provided by the embodiment of the application is used for executing the method for configuring the terminal parameters, so that the same effect as the method for configuring the terminal parameters can be achieved.

In the case of using an integrated unit, an embodiment of the present application provides a communication device, which exists in a product form of a chip and is used for performing the functions of the terminal in the foregoing embodiments, and the device may include: a processing module and a communication module. The processing module is used to control and manage the actions of the device, e.g., the processing module is used to support the device to perform other processes of the techniques described herein. The communication module is used to support communication between the apparatus and other network entities, for example, the functional module or the network entity shown in fig. 2. The apparatus may also include a storage module to store the program code and data for the apparatus.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip microcomputer, a chip, or the like) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for configuring terminal parameters, the method comprising:

the method comprises the steps that a configuration server receives an IMS registration request of a network interconnection protocol multimedia subsystem of a terminal, wherein the IMS registration request is used for requesting IMS registration of the terminal;

and the configuration server sends the configuration parameters of the terminal to the terminal according to the IMS registration request, wherein the configuration parameters of the terminal are used for supporting IMS services.

2. The method of claim 1, wherein the configuration parameters of the terminal are stored on the configuration server.

3. The method according to claim 1, characterized in that the configuration parameters of the terminal are saved on an application server AS; before the configuration server sends the configuration parameters of the terminal to the terminal, the method further includes:

the configuration server sends a third party registration request to the AS;

the configuration server waits for and receives 200OK corresponding to the third party registration request returned by the AS; and the 200OK corresponding to the third party registration request carries the configuration parameters of the terminal.

4. The method according to claim 1, characterized in that the configuration parameters of the terminal are saved on a home server HSS; before the configuration server sends the configuration parameters of the terminal to the terminal, the method further includes:

the configuration server sends a server allocation request SAR to the HSS,

and the configuration server receives a server allocation response (SAA) sent by the HSS, wherein the SAA carries the configuration parameters of the terminal.

5. The method according to any one of claims 1 to 4,

the configuration server is a service session control entity S-CSCF or a proxy session control entity P-CSCF.

6. The method according to any of claims 1-4, wherein the configuration server sends the configuration parameters of the terminal to the terminal, comprising:

and the configuration server carries the configuration parameters of the terminal in 200OK and sends the configuration parameters to the terminal, wherein the 200OK is used for indicating the success of IMS registration of the terminal.

7. The method of claim 1, wherein before the configuration server sends the configuration parameters of the terminal to the terminal, the method further comprises:

the configuration server receives a session initiation protocol message SIP MESSAGE sent by an AS, wherein the SIP MESSAGE carries configuration parameters of the terminal;

the configuration server sends the configuration parameters of the terminal to the terminal, and the configuration parameters comprise:

and the configuration server sends SIP MESSAGE carrying the configuration parameters of the terminal to the terminal.

8. The method according to any one of claims 1 to 4 and 7, wherein the IMS registration request includes indication information for indicating that the terminal supports issuing configuration parameters by a network element in the IMS, and the configuration server sends the configuration parameters of the terminal to the terminal according to the IMS registration request, including:

and the configuration server sends the configuration parameters of the terminal to the terminal according to the indication information.

9. The method according to any one of claims 1-4, 7, further comprising:

the configuration server receives a re-registration request sent by the terminal, wherein the re-registration request is used for requesting the terminal to perform IMS registration again;

and when the configuration parameters of the terminal are updated, the configuration server carries the updated configuration parameters of the terminal in a re-registration response and sends the re-registration response to the terminal, wherein the re-registration response is used for indicating that the IMS re-registration of the terminal is successful.

10. The method according to any one of claims 1-4, 7, further comprising:

the configuration server receives a subscription request sent by the terminal; the subscription request is used for requesting the configuration server to send a notification to the terminal when the configuration parameters of the terminal are updated;

and when the configuration parameters of the terminal are updated, the configuration server sends an event notification to the terminal, wherein the event notification carries the updated configuration parameters of the terminal.

11. The method according to any one of claims 1-4, 7, further comprising:

the configuration server detects that the configuration parameters of the terminal are updated;

and the configuration server carries the updated configuration parameters of the terminal in SIP MESSAGE and sends the parameters to the terminal.

12. The method according to any one of claims 1-4, 7, further comprising:

the configuration server receives the updated configuration parameters of the terminal;

and the configuration server sends the updated configuration parameters of the terminal to the terminal.

13. A method for configuring terminal parameters, the method comprising:

a terminal sends an IMS registration request to a configuration server, wherein the IMS registration request is used for requesting IMS registration of the terminal;

and the terminal receives the configuration parameters of the terminal sent by the configuration server, wherein the configuration parameters of the terminal are used for supporting the IMS service.

14. The method of claim 13,

the IMS registration request comprises indication information used for indicating the terminal to support the network element in the IMS to issue the configuration parameters.

15. The method according to claim 13 or 14, wherein the terminal receives the configuration parameters of the terminal sent by the configuration server, and comprises:

and the terminal receives a 200OK sent by the configuration server, wherein the 200OK carries the configuration parameters of the terminal, and the 200OK is used for indicating that the IMS registration of the terminal is successful.

16. The method according to claim 13 or 14, wherein the terminal receives the configuration parameters of the terminal sent by the configuration server, and comprises:

the terminal receives a session initiation protocol message SIP MESSAGE sent by the configuration server, wherein the SIP MESSAGE carries configuration parameters of the terminal.

17. The method according to claim 13-or 14,

the configuration server is S-CSCF or P-CSCF.

18. The method according to claim 13-or 14,

the terminal sends a re-registration request to the configuration server, wherein the re-registration request is used for requesting the terminal to perform IMS registration again;

and the terminal receives a re-registration response sent by the configuration server, wherein the re-registration response carries the updated configuration parameters of the terminal.

19. The method according to claim 13 or 14, characterized in that the method further comprises:

the terminal sends a subscription request to the configuration server; the subscription request is used for requesting the configuration server to send a notification to the terminal when the configuration parameters of the terminal are updated;

and the terminal receives an event notification sent by the configuration server, wherein the event notification carries the updated configuration parameters of the terminal.

20. A configuration server, characterized in that the configuration server comprises:

a receiving unit, configured to receive an IMS registration request of a network interconnection protocol multimedia subsystem of a terminal, where the IMS registration request is used to request IMS registration of the terminal;

a sending unit, configured to send a configuration parameter of the terminal to the terminal according to the IMS registration request, where the configuration parameter of the terminal is used to support an IMS service.

21. The configuration server according to claim 20, wherein the configuration parameters of the terminal are stored on the configuration server.

22. The configuration server according to claim 20, wherein the configuration parameters of the terminal are stored on an application server AS; the sending unit is further configured to send a third party registration request to the AS before the configuration server sends the configuration parameters of the terminal to the terminal;

the receiving unit is further configured to wait for and receive a 200OK corresponding to the third party registration request returned by the AS; and the 200OK corresponding to the third party registration request carries the configuration parameters of the terminal.

23. A configuration server according to claim 20, characterized in that the configuration parameters of said terminal are stored on a home server HSS; the sending unit is further configured to send a server allocation request SAR to the HSS before the configuration server sends the configuration parameters of the terminal to the terminal,

the receiving unit is further configured to receive a server allocation response SAA sent by the HSS, where the SAA carries the configuration parameter of the terminal.

24. The configuration server according to any of claims 20-23,

25. The configuration server according to any of claims 20-23, wherein the configuration server sends the configuration parameters of the terminal to the terminal, comprising:

26. The configuration server of claim 20,

the receiving unit is further configured to receive a session initiation protocol message SIP MESSAGE sent by an AS before the configuration server sends the configuration parameters of the terminal to the terminal, where the configuration parameters of the terminal are carried in the message SIP MESSAGE;

the sending unit is specifically configured to send SIP MESSAGE carrying the configuration parameters of the terminal to the terminal.

27. The configuration server according to any one of claims 20 to 23 and 26, wherein the IMS registration request includes indication information for indicating that the terminal supports a network element in an IMS to issue configuration parameters, and the sending unit is specifically configured to send the configuration parameters of the terminal to the terminal according to the indication information.

28. The configuration server according to any of claims 20-23, 26,

the receiving unit is further configured to receive a re-registration request sent by the terminal, where the re-registration request is used to request that IMS registration is performed again on the terminal;

the sending unit is further configured to, when the configuration parameter of the terminal is updated, carry the updated configuration parameter of the terminal in a re-registration response and send the re-registration response to the terminal, where the re-registration response is used to indicate that IMS re-registration of the terminal is successful.

29. The configuration server according to any of claims 20-23, 26,

the receiving unit is further configured to receive a subscription request sent by the terminal; the subscription request is used for requesting the configuration server to send a notification to the terminal when the configuration parameters of the terminal are updated;

the sending unit is further configured to send, by the configuration server, an event notification to the terminal when the configuration parameter of the terminal is updated, where the event notification carries the updated configuration parameter of the terminal.

30. A configuration server according to any of claims 20-23, 26, characterised in that the configuration server comprises:

the detection unit is used for detecting that the configuration parameters of the terminal are updated;

the sending unit is further configured to send the updated configuration parameters carried in SIP MESSAGE to the terminal.

31. The configuration server according to any of claims 20-23, 26,

the receiving unit is further configured to receive the updated configuration parameters of the terminal;

the sending unit is further configured to send the updated configuration parameters of the terminal to the terminal.

32. A terminal, characterized in that the terminal comprises:

a sending unit, configured to send an IMS registration request to a configuration server, where the IMS registration request is used to request IMS registration for the terminal;

a receiving unit, configured to receive a configuration parameter of the terminal sent by the configuration server, where the configuration parameter of the terminal is used to support an IMS service.

33. The terminal of claim 32,

34. The terminal according to claim 32 or 33, wherein the receiving unit is specifically configured to:

and receiving a 200OK message sent by the configuration server, wherein the 200OK carries the configuration parameters of the terminal, and the 200OK is used for indicating that the IMS registration of the terminal is successful.

35. The terminal according to claim 32 or 33, wherein the receiving unit is specifically configured to:

receiving a session initiation protocol message SIP MESSAGE sent by the configuration server, wherein the SIP MESSAGE carries configuration parameters of the terminal.

36. The terminal according to claim 32 or 33,

the configuration server is S-CSCF or P-CSCF.

37. The terminal according to claim 32 or 33,

the sending unit is further configured to send a re-registration request to the configuration server, where the re-registration request is used to request that IMS registration is performed again on the terminal;

the receiving unit is further configured to receive a re-registration response sent by the configuration server, where the re-registration response carries the updated configuration parameters of the terminal.

38. The terminal according to claim 32 or 33, characterized in that the terminal further comprises:

the sending unit is further configured to send a subscription request to the configuration server; the subscription request is used for requesting the configuration server to send a notification to the terminal when the configuration parameters of the terminal are updated;

the receiving unit is further configured to receive an event notification sent by the configuration server, where the event notification carries the updated configuration parameters of the terminal.