WO2006133624A1 - Procédé d’enregistrement dans un sous-système ip multimédia - Google Patents

Procédé d’enregistrement dans un sous-système ip multimédia Download PDF

Info

Publication number
WO2006133624A1
WO2006133624A1 PCT/CN2006/001143 CN2006001143W WO2006133624A1 WO 2006133624 A1 WO2006133624 A1 WO 2006133624A1 CN 2006001143 W CN2006001143 W CN 2006001143W WO 2006133624 A1 WO2006133624 A1 WO 2006133624A1
Authority
WO
WIPO (PCT)
Prior art keywords
cscf
capability
authentication
type
supported
Prior art date
Application number
PCT/CN2006/001143
Other languages
English (en)
Chinese (zh)
Inventor
Fenqin Zhu
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2006133624A1 publication Critical patent/WO2006133624A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H04L63/205—Network architectures or network communication protocols for network security for managing network security; network security policies in general involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H04L65/1095—Inter-network session transfer or sharing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]

Definitions

  • the invention relates to the field of mobile communication technologies, in particular to an IP multimedia subsystem
  • Mobile communications are not limited to traditional voice communications, through the combination of data services such as presence, messaging, web browsing, location information, push services (PUSH), and file sharing.
  • data services such as presence, messaging, web browsing, location information, push services (PUSH), and file sharing.
  • PUSH push services
  • Mobile communication enables a variety of media types such as audio, video, pictures and text to meet the diverse needs of users.
  • IP-based Multimedia Subsystem IMS
  • 3GPP 3rd Generation Mobile Communications Standardization Partnership Project
  • 3GPP2 3rd Generation Mobile Communications Standardization Partnership Project 2
  • IMS IP-based Multimedia Subsystem
  • the IMS architecture is superimposed on a packet domain network (PS-Domain) in which the authentication-related entities include a Call State Control Function (CSCF) entity and a Home Subscriber Server (HSS) functional entity.
  • PS-Domain packet domain network
  • the authentication-related entities include a Call State Control Function (CSCF) entity and a Home Subscriber Server (HSS) functional entity.
  • CSCF Call State Control Function
  • HSS Home Subscriber Server
  • the CSCF can be divided into three logical entities: service CSCF (S-CSCF), proxy CSCF (P-CSCF), and query CSCF (I-CSCF). These three logical entities may be different physical devices or the same physical device. Different functional modules in the device.
  • the S-CSCF is a service control center of the IMS, which is used to perform session control, maintain session state, manage user information, and generate charging information.
  • the P-CSCF is an access point for the terminal user to access the IMS, and is used to complete user registration. Quality of Service (QoS) control and security management; I-CSCF is responsible for interworking between IMS domains, managing the allocation of S-CSCFs, hiding network topology and configuration information, and Generate billing data, etc.
  • the HSS is a very important user database that is used to support the processing of calls and sessions by various network entities.
  • IMS was only considered for use in third-generation mobile communication networks when it was initially introduced (R5 version protocol). Due to the abundance of services on the IMS, there is a need for operators to use IMS on 2G networks. However, in 2G networks, security-related functions of IMS based on 3G networks cannot be supported, such as quintuple authentication/network authentication. In order to solve the problem of user authentication faced by 2G users using IMS networks, 3GPP proposes a transitional authentication. Early IMS, which provides certain security functions for IMS services on 2G. When the user supports the 3G authentication scheme, the complete 3G-based authentication scheme is used to authenticate the access user.
  • the entity supporting the 2G transition authentication mode is referred to as an entity supporting Early IMS authentication
  • the entity supporting the 3G authentication mode is referred to as an entity supporting Full 3GPP IMS authentication. Since there are entities in the network that support different authentication methods, the following situations are inevitable: For example, in the home network domain of the user, there are both S-CSCFs that support and do not support Early IMS. If only the Early IMS authentication mode is supported.
  • the P-CSCF sends the received SIP registration request from the UE that supports only the Early IMS authentication mode to the S-CSCF that supports only the Full 3GPP IMS authentication mode.
  • the S-CSCF must follow the Full 3GPP IMS authentication mode. Checking the receipt of the registration request. At this time, the S-CSCF finds that the related header field is missing from the received SIP message, and considers the message to be an illegal message, thus returning a failure response message to the user, but if it is selected at this time Another S-CSCF that supports Early IMS authentication, the user may register successfully.
  • the user authentication failure in the above situation is caused by the UE not supporting the authentication mode supported by the S-CSCF, not because the UE is not legal, and this is unfair to the legitimate user. Will inevitably reduce user satisfaction.
  • some operators of the 3GPP at the current stage stipulate that both the P-CSCF and the S-CSCF are placed in the home network, and support the same type of authentication mode, thereby avoiding the P-CSCF and the S-CSCF. Supporting different types of authentication methods, that is, avoiding the case where the UE and the S-CSCF support different types of authentication methods.
  • One method is to configure the authentication capability data supported by the S-CSCF in the network in the P-CSCF.
  • the configuration data process will inevitably be complicated and not feasible.
  • the P/S-CSCF is upgraded to support both ways to avoid the complication of the configuration data, there are also successive upgrades, which may cause the network to support different authentication capability types for a period of time.
  • Another method is to combine the P/S-CSCFs in the same network entity, so that as long as the UE is compatible with the authentication capability type of the P-CSCF, it can be guaranteed to be compatible with the S-CSCF authentication capability type.
  • the logical functions of the P/S-CSCF are bound to be distributed on different physical entities. In this case, this method cannot be used any more.
  • the main object of the present invention is to provide an IP multimedia subsystem.
  • the method of implementing registration in (IMS) avoids authentication failure caused by mismatch of authentication capability types.
  • the technical solution of the present invention is implemented by pre-setting and preserving the correspondence between the S-CSCF and the type of authentication capability supported by the S-CSCF, and the method includes the following steps:
  • the I-CSCF After receiving the registration request from the user equipment UE, the I-CSCF obtains S-CSCF capability set information that can provide services for the UE.
  • the I-CSCF determines the type of the authentication capability supported by the UE, and obtains the requirement of the UE according to the correspondence between the S-CSCF and the type of the authentication capability supported by the S-CSCF and the S-CSCF capability set information.
  • the I-CSCF sends a registration request to the obtained S-CSCF, and continues the subsequent registration processing.
  • step b of the foregoing method the step of determining, by the I-CSCF, the type of authentication capability supported by the UE includes:
  • the I-CSCF determines whether the acquired S-CSCF capability set information includes the authentication capability type data required by the user, and if yes, determines the authentication supported by the UE according to the authentication capability type data required by the user.
  • the capability type otherwise, the type of authentication capability supported by the UE is determined according to the registration request initiated by the UE.
  • the manner in which the I-CSCF determines the type of the authentication capability according to the registration request initiated by the UE includes:
  • the I-CSCF determines, according to the received registration request of the UE, whether to include an authorized Authorization header field or according to a preset feature that supports different types of authentication capabilities, determining an authentication capability type supported by the UE;
  • determining, according to whether the registration request includes an Authorization header field determining a UE branch
  • the step of the authentication capability type includes: if the registration request includes an Authorization header field, and the header field usage conforms to the current 3GPP requirements, determining that the UE supports the Full IMS authentication mode; if the registration request does not include the Authorization header field, It is determined that the UE supports the Early IMS authentication mode.
  • step b of the foregoing method the step of the I-CSCF acquiring an S-CSCF that satisfies the service capability required by the UE and supports the authentication capability type of the UE includes:
  • the I-CSCF determines whether the acquired S-CSCF capability set information includes the authentication capability type data required by the user, and if so, the I-CSCF and the supported authentication capability type of the S-CSCF
  • the corresponding relationship and the authentication capability type data in the acquired S-CSCF capability set information directly obtain an S-CSCF that satisfies the service capability required by the UE and supports the UE's authentication capability type; otherwise, the I-CSCF
  • the S-CSCF capability set that satisfies the service capability of the UE is obtained from the obtained S-CSCF capability set information, and then the authentication capability type supported by the UE is determined according to the registration request initiated by the UE, and then the content is satisfied according to the
  • the S-CSCF capability set of the UE's service capability, the determined authentication capability type, and the correspondence between the S-CSCF and the type of authentication capability supported by the UE obtain the service capability that satisfies the UE and supports the authentication of the UE.
  • the step b further includes: when the acquired S-CSCF capability set information includes the authentication capability type data required by the user set in advance, but the I-CSCF cannot directly obtain the data according to the authentication capability type data.
  • the I-CSCF obtains the S-CSCF capability that satisfies the service capability of the UE from the acquired S-CSCF capability set information.
  • the step of saving the correspondence between the S-CSCF and the type of authentication capability supported by the S-CSCF includes: saving, in the form of a data table, the S-CSCF identifier and the supported template in the I-CSCF. Type of power.
  • the method further includes: when the I-CSCF cannot obtain the UE that satisfies the registration request according to the correspondence between the S-CSCF and the type of the authentication capability supported by the S-CSCF and the S-CSCF capability set information.
  • the I-CSCF returns a response message of the registration failure to the UE through the P-CSCF, or the I-CSCF randomly selects an S-CSCF, and then The S-CSCF sends a registration request and performs subsequent registration processing according to a normal procedure.
  • the S-CSCF if the S-CSCF arbitrarily selected by the I-CSCF satisfies the service capability requirement of the UE and matches the authentication capability type supported by the UE, the S-CSCF sends the UE to the UE through the I-CSCF and the P-CSCF. Returning the response information of the registration success; if the S-CSCF arbitrarily selected by the I-CSCF satisfies the service capability requirement of the UE and/or does not match the authentication capability type supported by the UE that initiated the registration request, the S-CSCF passes the I- The CSCF and the P-CSCF return response information of the registration failure to the UE.
  • the response information of the registration failure further includes the sender information of the information and the reason for the failure, and the failure reason is that the S-CSCF whose matching capability type matches is not found.
  • step b of the foregoing method when the S-CSCF that satisfies the service capability required by the UE and supports the UE's authentication capability type is more than one, an S-CSCF is arbitrarily selected from the S-CSCF.
  • the technical solution of the present invention mainly includes: pre-setting and saving a correspondence between an S-CSCF and an authentication capability type supported by the S-CSCF; and after receiving the registration request of the UE, the I-CSCF acquires the S of the UE. -CSCF capability set information; then determine the support supported by the UE The capability type, and the S-CSCF that satisfies the service capability of the UE and supports the UE's authentication capability type according to the correspondence between the S-CSCF and the authentication capability type supported by the S-CSCF and the S-CSCF capability set information. Then, a registration request is sent to the acquired S-CSCF to continue the subsequent processing.
  • the method of the present invention further includes providing a reason for the failure in the response message of the registration failure, thereby assisting the UE to perform the related operation. Since the present invention is less modified to the prior art solution, the existing configuration data method changes brought by the network size adjustment are minimized, so that the existing network has good compatibility.
  • Figure 1 shows the flow chart for user registration using the Early IMS authentication method. Mode for carrying out the invention
  • the correspondence between the S-CSCF and the type of authentication capability supported by the S-CSCF needs to be set and saved in advance, and the corresponding relationship may be saved in the form of a data table in the I-CSCF.
  • the S-CSCF identifier is implemented by the type of authentication capability it supports.
  • the form of the data table can be as shown in Table 1 below: S-CSCF identifies the authentication capabilities supported by the S-CSCF
  • the above S-CSCF data table for indicating the type of authentication capability supported by the S-CSCF is usually set in the I-CSCF.
  • Figure 1 shows the flow chart for user registration using the Early IMS authentication method.
  • the UE matches the authentication mode of the P-CSCF, and the UE initiates the registration request by using the SIP message.
  • the process mainly includes the following steps:
  • Step 101 The UE initiates a new IMS registration request message. Because the P-CSCF that receives the user registration request message matches the authentication capability type supported by the UE that initiated the request, the P-CSCF can correctly forward the registration request of the UE. Message.
  • the registration request message includes the identifier of the UE.
  • Step 102 103 The identifier of the P-CSCF in the UE determines its home domain, and determines the IP address of the entry point I-CSCF of the home domain by querying data in the Address Resolution Server (DNS).
  • DNS Address Resolution Server
  • Step 104 The P-CSCF forwards the registration request to the I-CSCF.
  • Steps 105 - 106 the I-CSCF sends a query location message to the HSS, where the query location message includes the identifier of the UE. Since the user is initially registered, the HSS finds the user subscription data of the UE according to the UE identifier in the query message, and obtains the S-CSCF capability set information according to the capability required by the subscription data, and then sets the S-CSCF capability set.
  • the I-CSCF Information returned to The I-CSCF, at the same time, if the authentication capability type data indicating the type of authentication capability supported by the UE is pre-configured according to the user subscription data in the HSS, the type of authentication capability indicating the type of authentication capability supported by the UE The data will be returned to the I-CSCF as part of the SC SCF capability set information.
  • Step 107 The I-CSCF selects, from the received S-CSCF capability set information, an S-CSCF set that can satisfy the service capability required by the UE and supports the UE's authentication capability type.
  • the specific selection process is as follows:
  • the I-CSCF determines, according to the authentication capability type data, the authentication supported by the UE that initiated the request.
  • the capability type according to the correspondence between the S-CSCF identifier in the set data table and the type of authentication capability supported by the S-CSCF, and the acquired S-CSCF capability set information, directly select a service that can meet the requirements of the UE.
  • the S-CSCF set may have one or more S-CSCFs, and if the S-CSCF set includes multiple S-CSCFs, the I-CSCF may be from the middle Pick an S-CSCF.
  • the I-CSCF first selects from the S-CSCF capability set information returned by the HSS.
  • the S-CSCF capability set that satisfies the UE service capability, and then determines the authentication capability type supported by the UE according to the registration request initiated by the UE, and then according to the S-CSCF identifier in the set data table and the supported profile thereof Corresponding relationship of the capability type, and the selected S-CSCF capability set capable of satisfying the UE service capability, selecting an S-CSCF set capable of satisfying the service capability required by the UE and supporting the UE's authentication capability type There may be one or more S-CSCFs in the S-CSCF set. If the S-CSCF set contains multiple S-CSCFs, the I-CSCF may select one S-CSCF from it.
  • the foregoing I-CSCF determines, according to the received registration request, the UE supported by the requesting request.
  • the method of the authentication capability type is: determining, according to whether an authorization (Authorization) header field exists in the registration request, the type of authentication capability supported by the UE that initiated the request, that is, if the registration request includes an Authorization header field and the header field usage is consistent Currently, the 3GPP requires that the UE that initiates the request supports the Full IMS authentication capability type. If the registration request does not include the Authorization header field, the UE that initiated the request supports the Early IMS authentication mode.
  • an authorization Authorization
  • the type of authentication capability supported by the UE that initiates the registration request may be determined according to a feature set by the operator that supports different types of authentication capabilities.
  • the UE that initiates the registration request in this embodiment only supports the Early IMS authentication capability type. According to the data in Table 1, only the S-CSCF1 and/or S may be included in the S-CSCF set selected by the I-CSCF. -CSCF2, but not S-CSCF3.
  • Step 108 The I-CSCF sends a registration request message to the selected S-CSCF.
  • Steps 109 ⁇ 110 the S-CSCF requests the authentication parameter from the HSS, and obtains the required parameters from the response information of the HSS.
  • Steps 111 to 112 the S-CSCF performs authentication according to the authentication parameters obtained by the HSS, and returns an authentication result to the HSS. It is assumed here that the S-CSCF adopts Early IMS authentication, and the specific authentication process is the same as the prior art, and will not be described in detail herein.
  • Steps 113 ⁇ 115 the S-CSCF returns a registration response message to the user.
  • the registration is successful, and the S-CSCF returns a registration success message to the UE through the P-CSCF.
  • the above embodiment is described by the registration process of the user who authenticates with Early IMS.
  • the difference between the registration process and the existing registration process is that it is preset to represent S.
  • the S-CSCF data table of the authentication capability type supported by the CSCF, the data table containing the correspondence between the S-CSCF identifier and the type of authentication capability supported by it, and the S-CSCF capability received from the HSS at the I-CSCF After the information is collected, determining the type of authentication capability supported by the UE that initiated the request, and according to the correspondence between the identifier of the S-CSCF in the set data table and the type of authentication capability supported by the set, And obtaining the S-CSCF capability set information, selecting an S-CSCF set capable of satisfying the service capability required by the UE that initiates the registration request, and supporting the UE's authentication capability type, and then selecting an S-CSCF from the set, Follow the normal process to continue the subsequent registration process.
  • the I-CSCF can be processed as follows: The S-CSCF capability set information returned from the HSS is selected to meet the UE service capability. The S-CSCF capability set is determined according to the registration request initiated by the UE, and then the type of the authentication capability supported by the UE is determined, and then the correspondence between the S-CSCF identifier and the supported authentication capability type in the set data table is determined.
  • the selected S-CSCF capability set capable of satisfying the service capability of the user and selecting an S-CSCF set capable of supporting the authentication capability type supported by the UE that initiates the registration request. That is, when the authentication capability type data supported by the UE is pre-configured in the HSS, but the I-CSCF cannot find the matching S-CSCF according to the S-CSCF capability set information returned by the HSS, the I-CSCF can The method is determined by a method for determining the type of authentication capability of the UE according to the registration request of the UE. Alternatively, you can follow the failure method described below.
  • the I-CSCF does not configure the above S-CSCF data table; or the I-CSCF determines the user's authentication capability.
  • the type is matched with the pre-configured S-CSCF data table, and no related entries are found.
  • the abnormal situation is not limited to this, and the I-CSCF cannot select the service that satisfies the UE from the acquired S-CSCF capability set.
  • the I-CSCF has the following two methods: Method 1: The I-CSCF returns a response message of registration failure to the UE through the P-CSCF.
  • the initiator information and the reason for the failure may be included in the response message of the registration failure.
  • the initiator information indicates that the failure response message is initiated by the I-CSCF, instead of the authentication failure at the P-CSCF; the failure reason indicates that the S-CSCF whose matching capability type matches is not found, for example, using 400 messages.
  • Method 2 The I-CSCF randomly selects an S-CSCF, sends a registration request to the selected S-CSCF, and continues the subsequent processing according to a normal procedure. At this point, there will be two more cases:
  • the S-CSCF selected by the I-CSCF matches the type of authentication capability supported by the UE that initiated the request.
  • the S-CSCF returns to the authentication result after normal processing, that is, through the I-CSCF and the P-CSCF.
  • the UE returns a response message indicating that the registration is successful.
  • the reason for this may be that the data in the S-CSCF data table that is pre-configured to indicate the type of authentication capability supported by the S-CSCF is incorrect or imperfect.
  • the S-CSCF selected by the I-CSCF does not match the authentication capability type supported by the UE that initiated the request, and the S-CSCF returns the response information of the registration failure to the UE through the I-CSCF and the P-CSCF, and the registration fails.
  • the response information may further include initiator information and the reason for the failure.
  • the initiator information indicates that the failure response message is initiated by the S-CSCF, which can be distinguished from the failure response message initiated by the P-CSCF. In the failure reason, it is indicated that the S-CSCF whose matching capability type matches is not found, for example.
  • the 400 message, that is, the Bad Request indicates that the UE that initiated the request supports the Early IMS, and the S-CSCF only supports the Full 3GPP IMS.
  • the 420 message that is, the Bad Extension, indicates that the UE that initiated the request supports Full 3GPP IMS and the S-CSCF only Support for Early IMS. By giving the reason for the failure in the response message of the registration failure, the UE can be assisted to perform subsequent related operations.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention concerne un procédé d’enregistrement dans un sous-système IP (Internet Protocol) multimédia (IMS). Le procédé comprend les étapes suivantes : prédéfinition et stockage de la relation correspondante entre la fonction S-CSCF et sa fonction d’authentification associée ; à réception de la demande d’enregistrement, obtention des informations définies sur la fonction de la S-CSCF du dispositif utilisateur (UE), détermination du type de fonction d’authentification prise en charge par l’UE, obtention de la S-CSCF répondant à la fonction de service de l’UE et gérant la fonction d’authentification de l’UE selon la relation correspondante entre la S-CSCF et sa fonction d’authentification associée et des informations définies sur la fonction de la S-CSCF, puis envoi de la demande d’enregistrement à la S-CSCF obtenue et poursuite du processus de fond. Ainsi, la fonction d’authentification prise en charge par l’UE correspond à celle associée à la S-CSCF.
PCT/CN2006/001143 2005-06-17 2006-05-29 Procédé d’enregistrement dans un sous-système ip multimédia WO2006133624A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2005100776047A CN100433913C (zh) 2005-06-17 2005-06-17 在ip多媒体子系统中实现注册的方法
CN200510077604.7 2005-06-17

Publications (1)

Publication Number Publication Date
WO2006133624A1 true WO2006133624A1 (fr) 2006-12-21

Family

ID=37134019

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/001143 WO2006133624A1 (fr) 2005-06-17 2006-05-29 Procédé d’enregistrement dans un sous-système ip multimédia

Country Status (2)

Country Link
CN (1) CN100433913C (fr)
WO (1) WO2006133624A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108076452A (zh) * 2016-11-18 2018-05-25 大唐移动通信设备有限公司 一种通知业务能力的方法、装置和系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102984164B (zh) * 2012-12-06 2015-06-17 大唐移动通信设备有限公司 一种ims注册方法及装置
CN103701780A (zh) * 2013-12-13 2014-04-02 大唐移动通信设备有限公司 一种鉴权方法和系统
CN110493773B (zh) * 2019-08-23 2022-09-02 中国联合网络通信集团有限公司 移动设备鉴权能力的获取方法及其设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004061543A2 (fr) * 2003-01-03 2004-07-22 Nokia Corporation Procede et appareil de resolution de schema indifferents au type de protocole dans un sous-systeme ip multimedia
US20050071679A1 (en) * 2003-02-04 2005-03-31 Krisztian Kiss Method and system for authorizing access to user information in a network

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10116547A1 (de) * 2001-04-03 2002-10-10 Nokia Corp Registrierung eines Endgeräts in einem Datennetz
ATE306776T1 (de) * 2002-10-22 2005-10-15 Verfahren und system zur authentifizierung von benutzern in einem telekommunikationssystem
US20040187021A1 (en) * 2003-02-10 2004-09-23 Rasanen Juha A. Mobile network having IP multimedia subsystem (IMS) entities and solutions for providing simplification of operations and compatibility between different IMS entities

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004061543A2 (fr) * 2003-01-03 2004-07-22 Nokia Corporation Procede et appareil de resolution de schema indifferents au type de protocole dans un sous-systeme ip multimedia
US20050071679A1 (en) * 2003-02-04 2005-03-31 Krisztian Kiss Method and system for authorizing access to user information in a network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"IP multimedia subsystem and its service frame in the UMTS", CHINA DATA COMMUNICATION, February 2004 (2004-02-01), XP008073589 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108076452A (zh) * 2016-11-18 2018-05-25 大唐移动通信设备有限公司 一种通知业务能力的方法、装置和系统

Also Published As

Publication number Publication date
CN1852556A (zh) 2006-10-25
CN100433913C (zh) 2008-11-12

Similar Documents

Publication Publication Date Title
US7822407B2 (en) Method for selecting the authentication manner at the network side
EP1816825A1 (fr) Procede et systeme d'authentification de terminal d'usager
EP2137931B1 (fr) Procédé et arrangement de gestion de profils dans un réseau de services multimédia
EP1864522B1 (fr) Procede permettant d'etablir des communications reposant sur un systeme ims
JP5091569B2 (ja) サービス毎通信制御装置、システム及び方法
EP2084882B1 (fr) Authentification dans un réseau de communication
EP1994707B1 (fr) Commande d'accès dans un réseau de communication
US20070055874A1 (en) Bundled subscriber authentication in next generation communication networks
WO2006136097A1 (fr) Procédé pour traiter une anomalie lors de la procédure d'inscription d'un utilisateur
US20120096162A1 (en) Methods and apparatuses for initiating provisioning of subscriber data in a hss of an ip multimedia subsystem network
WO2006125359A1 (fr) Procede d'implementation de la securite de domaine d'acces d'un sous-systeme multimedia ip
US20110246624A1 (en) Service Node, Control Method Thereof, User Node, and Control Method Thereof
US20110173687A1 (en) Methods and Arrangements for an Internet Multimedia Subsystem (IMS)
WO2008025280A1 (fr) Procédé et système d'authentification
WO2006072209A1 (fr) Procede de negociation d'une cle dans un sous-systeme multimedia ip
WO2006111078A1 (fr) Procede d’obtention des informations d’acces utilisateur dans le reseau de prochaine generation
EP4059247A1 (fr) Procédé de prise en charge d'authentification d'un équipement d'utilisateur
WO2006133624A1 (fr) Procédé d’enregistrement dans un sous-système ip multimédia
EP2449743B1 (fr) Procédé et appareil destinés à être utilisés dans un sous-système multimédia ip
WO2008089699A1 (fr) Procédé et système d'authentification d'un terminal utilisateur dans un réseau ims
CN101001145B (zh) 支持非ip多媒体业务子系统终端漫游的认证方法
WO2011029342A1 (fr) Procédé, dispositif et système d'identification d'un type d'identité d´utilisateur public (pui)
WO2010108357A1 (fr) Procédé et système de commande de politique
WO2007045181A1 (fr) Procede, systeme et dispositif d’obtention d’informations d’acces
KR101016641B1 (ko) 단말에 대한 인증 제어 장치 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06742031

Country of ref document: EP

Kind code of ref document: A1