WO2007009344A1 - Méthode d’inscription/annulation et système d’inscription/annulation - Google Patents

Méthode d’inscription/annulation et système d’inscription/annulation Download PDF

Info

Publication number
WO2007009344A1
WO2007009344A1 PCT/CN2006/001518 CN2006001518W WO2007009344A1 WO 2007009344 A1 WO2007009344 A1 WO 2007009344A1 CN 2006001518 W CN2006001518 W CN 2006001518W WO 2007009344 A1 WO2007009344 A1 WO 2007009344A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
registration
information
client
request information
Prior art date
Application number
PCT/CN2006/001518
Other languages
English (en)
French (fr)
Inventor
Lei Yuan
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.
Priority to AT06753078T priority Critical patent/ATE472919T1/de
Priority to DE602006015147T priority patent/DE602006015147D1/de
Priority to CNA200680011509XA priority patent/CN101156363A/zh
Priority to US11/664,652 priority patent/US20080091835A1/en
Priority to EP06753078A priority patent/EP1791297B1/en
Publication of WO2007009344A1 publication Critical patent/WO2007009344A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/18—Delegation of network management function, e.g. customer network management [CNM]
    • 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
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload

Definitions

  • the present invention relates to a network communication technology, and more particularly to a registration/logout system and a registration/logout method.
  • Background Art In modern communication systems, such as NGN (Next Generation Network), many new services are constantly emerging, and these new services bring a rich experience to users. Therefore, users are likely to need to apply for multiple services in order to get services for multiple services.
  • SIP Intelligent Session Protocol
  • NGN Next Generation Network
  • SIP Initial Session Protocol
  • NGN In order to use these multiple services that have been applied, only one service can be registered/deregistered at a time, and therefore, in order to simultaneously use multiple services, the user must separately— - Register/deregister each business required. Therefore, it takes time to register/log off the business.
  • the present invention is achieved by the following technical solutions.
  • the present invention provides a registration/logout system, including:
  • a client configured to send service request information to the service management server, and send each service registration/deregistration request information to the service registration/logout server according to the predetermined rule and each service registration/deregistration information returned by the service management server;
  • a service management server configured to store user information, where the user information includes each service information, and send each service registration/deregistration information to the client;
  • the service registration/logout server is used to register/deregister the service according to each service registration/logout request information.
  • the client further includes: an encryption device, configured to encrypt the service request information.
  • the service management server further includes: a decryption device, configured to decrypt the encrypted service request information.
  • the service management server further includes: an authentication device, configured to authenticate the service request information.
  • the registration/logout system further includes: a communication network including a next generation network and an Internet for connecting a client, a service management server, and a service registration/logout server, and implementing communication therebetween.
  • the invention also provides a registration/logout method, comprising:
  • the client sends service request information to the service management server;
  • the service management server obtains multiple service information according to the service request information, and sends multiple service information to the client;
  • the client generates a plurality of service registration/deregistration request information according to the plurality of service information, and issues a plurality of service registration/deregistration debt request information to the service registration/deregistration server by using a predetermined rule;
  • the service registration/logout server registers/deregisters multiple services based on multiple service registration/logout request information.
  • the method further includes: when the client encrypts the service request information.
  • the step of the service management server obtaining the plurality of service information according to the service request information, and before sending the plurality of service information to the client, the method further includes: the service management server decrypting the encrypted service request information.
  • the service information includes a service account number, a service password, and a service registration/deregistration server address.
  • the predetermined rules include: random registration/logout, registration/deregistration by priority.
  • the service management server obtains a plurality of service information according to the service request information, and executes the plurality of service information before sending the service information to the client:
  • the service management server performs authentication according to the service request information.
  • . 1 shows a schematic diagram of a registration/logout system of the present invention
  • Figure 2 is a flow chart showing the registration/logout method of the present invention
  • Figure 3 illustrates an embodiment of the registration method of the present invention
  • FIG. 4 illustrates an embodiment of the logout method of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS In order to facilitate the understanding and implementation of the present invention, the embodiments of the present invention are described in conjunction with the drawings.
  • the present invention provides a registration/logout system.
  • the registration/logout system includes: a communication network, a client, a service management server, a service registration/logout server, and an application server.
  • the registration/logout system of the present invention will be described in detail below.
  • the communication network includes an NGN network and/or an Internet (Internet) network for connecting a client, an application server, a service registration/logout server, and a service management server, and can enable a client, an application server, a service registration/logout server, and
  • the business management servers communicate with each other.
  • SIP can be used for communication.
  • HTTP Hyperlink Transmission Protocol
  • other protocols can be used for communication.
  • the client is connected to the service management server through the communication network, and is configured to generate service request information, send the generated service request information to the service management server, and according to the predetermined rule and the service registration/deregistration information returned by the service management server.
  • the service registration/deregistration server issues individual service registration/deregistration request information.
  • the service request information includes a username and a user password.
  • the client includes encryption means for encrypting service request information and/or service registration/logout information.
  • the service management server is configured to store user information.
  • the user information includes a user name, a user password, and various service information corresponding to the user.
  • the service information includes information such as a service account number, a service password, a service registration/deregistration server address, a registration mode information, and an encryption method.
  • the service management server further includes: a decryption device, configured to decrypt the service request information; The device is configured to authenticate the service request information according to the user information.
  • the service registration/deregistration server is configured to register/deregister each service according to each service registration/deregistration request information, and whether the user is allowed to use the requested service according to the registration status of the customer.
  • the service registration/logout server may be an application server (AS), a softswitch, or another server on a physical entity.
  • the application server is used to run various services.
  • the present invention also provides a registration/deregistration method for registering/deregistering a plurality of services at a time, and the registration/deregistration method described above is described in detail below.
  • the user can open a plurality of services in the business hall or through the communication network, obtain relevant business information, and then store the business information in the user information table of the business management server.
  • the client sends service request information to the service management server, where the service request information includes a user name and a user password.
  • the service request information may be encrypted at the client, for example, using DES (Data Encryption Standard) to encrypt the service request information.
  • DES Data Encryption Standard
  • the client can send service request information to the service management server at various times. For example: After the client receives the user registration/logout request, it sends the service request information, and sends the service request information according to the preset time, and sends it at regular intervals. Business request information, etc.
  • the client may send the service request information to the service management server in various manners.
  • the service request information is sent to the service management server through the NGN through a protocol such as HTTP or through a protocol such as SIP.
  • the service management server first decrypts the encrypted service request information, and then authenticates the service request information according to the user information, that is, whether the user name and the user password are consistent. If they are consistent, the authentication is passed. Otherwise, Authentication failed.
  • step 23 it is judged whether the authentication is passed, and if yes, step 24 is performed, otherwise, step 27 is performed.
  • the service management server takes out the service information of the user, and sends the service information to the client.
  • the service information includes a plurality of service information.
  • the client generates service registration/logout request information according to the service information sent by the service management server, and sends the service registration/logout request information to the service registration/logout server according to the predetermined rule.
  • step 26 the service registration/logout server registers/deregisters the service based on the service registration/logout request information.
  • step 27 error processing is performed, and the client name and password may be prompted to be inconsistent, and the user is required to resubmit the service request information, and then perform steps 21 to 23 again until the authentication is passed, or the submission is reached a predetermined number of times (eg, 5 times). At the time, the authentication still fails, and the user's registration/logout request can be rejected. In the present invention, the registration/deregistration request is submitted 5 times, the authentication still fails, the user's registration/deregistration is rejected, and the user is prompted to reset the user password with the valid certificate to the business hall.
  • a predetermined number of times eg, 5 times
  • the predetermined rule refers to a registration/deregistration order, for example, may be applied for registration/deregistration in accordance with a prioritized priority order, or randomly to the service registration/logout server.
  • the client can return the registration/deregistration success message to the user after all the business registration/deregistration is completed, or return the registration/logout success message to the user after the key service registration/logout is completed, so as to enable The user is informed that certain services are registered/logged out successfully.
  • the registration/deregistration method of each service can be determined at the time of service application, and is configured when the service is allocated.
  • the service registration/deregistration method can be configured as a standard SIP registration/deregistration process, and the website HTTP/HTTPS registration/deregistration Process or any custom registration/logout process.
  • service registration/logout servers corresponding to each service may be different or the same.
  • the NGN service is used as an example to describe the process of registering multiple services at a time. Assume that there is a user in the NGN whose user name is Ray and the user password is RayPwd. The three NGN services have been applied for: Service A, Service B, Service C, client address is Ray@192.0.2.4, service registration/deregistration server The information is shown in Table 1.
  • ARS1 ARSl.com 5060 Account Registration Server Business Registration / Logout Server
  • Table 3 shows the business information
  • step 301 the user Ray inputs the username Ray and the password RayPwd through the client interface, and then clicks the button to submit the service request information;
  • step 302 the client encapsulates information such as the username Ray and the password RayPwd into a message and sends it to the AMS1.
  • user information such as user name and password may be encrypted, and then the encrypted user information is sent to AMS1.
  • the following is an example of a message from the client to AMS1 to send service request information.
  • S2 REGISTER Client->AMS1 5 message is as follows:
  • step 303 after receiving the HTTP packet sent by the client, the AMS1 parses the packet to obtain the username and password. If the message has been encrypted, a decryption operation is also required. AMS1 verifies the authentication of the username and password sent by the client with the user information stored in AMS1 (see Table 2 User Information Table).
  • step 304 the service management server takes out the stored service information corresponding to the user (see Table 3 user service information table); the service management server sends the service information corresponding to the user to the client;
  • ⁇ / registrar> The client registers all services according to the service information according to the predefined priority level. Since the service A has the highest priority, the service A is processed first.
  • step 305 since the registration mode of the service B is the standard SIP mode, the client requests 4 megabytes of words from the ARS1, so that the client encrypts the service A registration request according to the challenge word, and the challenge word functions as a key. .
  • step 306 ARS1 issues a challenge word to the client.
  • step 307 the client encrypts the service A registration request information according to the challenge word and sends it to ASR1. That is, AMS1 cooperates with ARS1 to complete the registration of service A.
  • the following is an example of a message from the Business A registration process.
  • step 308 after the registration of the service A is completed, according to the registration status of the service A, the ARS1 returns the registration success or failure information to the client.
  • the service B Since the service has a higher priority because of the service B, the service B should be processed.
  • step 309 since the registration mode of the service B is the standard SIP mode, the client requests the challenge word from the A S1, so that the client encrypts the service B registration request according to the challenge word, where the challenge word is The effect is equivalent to the key.
  • step 310 A S1 issues a challenge word to the client.
  • step 311 the client encrypts the service B registration request information according to the challenge word and sends it to ASR1.
  • ASR1 ASR1
  • SI 1 REGISTER Client -> A S1 5 message example is as follows:
  • S12200 OK ARSl-> Client the information example is as follows: SIP/2.0 200 OK
  • step 312 after the registration of the service B is completed, according to the registration status of the service B, A S1 returns the registration success or failure information to the client.
  • step 313 since the registration mode of the service C is HTTP, the client sends the service registration request information to the ASR2.
  • the ARS2 will register the success or failure according to the registration status of the service C. Return to the client.
  • the following is an example of a message for the Business C registration process.
  • JSESSIOinD 87D42196E7BB95A3F45D19FAF31AB62F
  • step 315 since the three services corresponding to the user are all required to be registered, if all the services are successfully registered, the registration success information is returned, otherwise the registration failure information is returned.
  • step 401 the user Ray enters the username Ray and the password RayPwd through the client interface, and then clicks the button to submit the service request;
  • the client encapsulates information such as the username Ray and the password RayPwd into a message and sends it to AMS1.
  • user information such as user name and password can be encrypted, and then the encrypted user information is sent to AMS1.
  • the following is an example of a message from the client to AMS1 to send a service request.
  • User-Agent Mozilla/4 . 0 ( compatible ; MSIE 6. 0 ; Windows NT 5. 1 ) Content-Length: 40
  • step 403 after receiving the HTTP packet sent by the client, the AMS1 parses the packet to obtain the username and password. If the message has been encrypted, a decryption operation is also required. AMS1 verifies the authentication of the username and password sent by the client with the user information stored in AMS1 (see Table 2 User Information Table).
  • step 404 the service management server retrieves the stored service information corresponding to the user (see Table 3 user service information table); the service management server sends the service information corresponding to the user to the client;
  • ⁇ / registrar> The client logs out all services according to the service information according to the predefined priority level. Because service A has the highest priority, the service A is processed first.
  • step 405 the client issues a logout request for service A to ARS1.
  • the only difference between the client's logout request message and the registration request message is that the Expires field has a value of 0.
  • step 406 after the transaction A is cancelled, the ARS1 will be injected according to the cancellation status of the service A.
  • the pin success or failure message is returned to the client.
  • step bare 407 the client sends a logout request for service B to ARS1.
  • the only difference between the client's logout request message and the registration request message is that the Expires field has a value of 0.
  • step 408 after the service B is deregistered, according to the cancellation status of the service B, the ARS1 returns the cancellation success or failure information to the client.
  • step 409 the client issues a logout request for service C to ARS2.
  • step 410 after the transaction C is cancelled, the ARS2 returns the logout success or failure information to the client according to the cancellation status of the service C.
  • step 411 since the three services corresponding to the user are all required to be logged out, if all services are successfully logged off, the logout success information is returned, otherwise the logout failure information is returned.
  • each service corresponds to the same user name and user password, and may also correspond to different user names and user passwords.
  • the service request information sent by the client to the service management server should be included.
  • multiple services can be registered/deregistered at one time, thereby avoiding the need for the user to apply for multiple services and registering/deregistering each service. Therefore, the user's time is saved and the user is provided with a good experience. , bringing benefits to the integration of the business.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)
  • Computer And Data Communications (AREA)
  • Hardware Redundancy (AREA)
  • Preparation Of Compounds By Using Micro-Organisms (AREA)

Description

一种注册 /注销系统和注册 /注销方法 技术领域 本发明涉及一种网络通信技术， 尤其涉及一种注册 /注销系统和注册 /注销 方法。 背景技术 在现代通信系统中， 如在 NGN (下一代网络) 中， 许多新业务在不断地 出现， 这些新业务为用户带来了丰富体验。 因此， 用户很可能需要申请多个 业务， 以便得到多个业务的服务。 然而， 在诸如 NGN的 SIP (初始会话协议) 的现有技术中， 为了使用这些已申请的多个业务， 一次只能注册 /注销一个业 务， 因此， 用户为了同时使用多个业务, 必须分别——注册 /注销每一个所需 要使用业务。 因此， 使得注册 /注销业务比较耗费时间。 发明内容 针对现有技术的上述缺陷， 本发明的目的是提供一种注册 /注销系统和注 册 /注销方法， 可一次注册 /注销多个业务， 从而节省了注册 /注销时间。
本发明是通过下述技术方案实现的， 本发明提供了一种注册 /注销系统， 包括：
客户端， 用于向业务管理服务器发出业务请求信息， 并根据预定规则和 业务管理服务器返回的各个业务注册 /注销信息向业务注册 /注销服务器发出 各个业务注册 /注销请求信息；
业务管理^^务器， 用于存储用户信息， 所述用户信息包括各个业务信息， 并向客户端发送各个业务注册 /注销信息；
业务注册 /注销服务器， 用于根据各个业务注册 /注销请求信息对业务进行 注册 /注销。
所述的客户端还包括： 加密装置， 用于对业务请求信息进行加密。 所述的业务管理服务器还包括： 解密装置， 用于对加密的业务请求信息 进行解密。
所述的业务管理服务器还包括： 鉴权装置， 用于对业务请求信息进行鉴 权。
所述的注册 /注销系统还包括： 通信网络， 所述通信网络包括下一代网絡 和互联网， 用于连接客户端、 业务管理服务器和业务注册 /注销服务器， 并实 现它们之间的通信。
本发明还提供了一种注册 /注销方法， 包括：
客户端向业务管理服务器发出业务请求信息；
业务管理服务器根据业务请求信息获得多个业务信息， 并将多个业务信 息发给客户端；
客户端根据多个业务信息生成多个业务注册 /注销请求信息， 并以预定规 则向业务注册 /注销服务器发出多个业务注册 /注销債求信息；
业务注册 /注销服务器根据多个业务注册 /注销请求信息对多个业务进行 注册 /注销。
当所述的步骤客户端向业务管理服务器发出业务请求信息之前还包括： 客户端对业务请求信息进行加密时。 所述的步骤业务管理服务器根据业务请 求信息获得多个业务信息， 并将多个业务信息发给客户端之前还包括： 业务 管理服务器对加密的业务请求信息进行解密。
所述业务信息包括业务帐号、 业务密码、 业务注册 /注销服务器地址。 所述预定规则包括： 随机注册 /注销、 按优先级注册 /注销。
在执行步骤业务管理服务器根据业务请求信息获得多个业务信息， 并将 多个业务信息发给客户端之前还执行： 业务管理服务器根据业务请求信息进 行鉴权。
根据本发明， 可一次注册 /注销多个业务， 从而避免了用户申请多个业务 后在使用时需要——注册 /注销每一个业务， 因此， 节省了用户的时间， 给用 户带来良好的体验。 说明 图 1示出了本发明的注册 /注销系统的示意图；
图 2示出了本发明的注册 /注销方法的流程图；
图 3示出了本发明的注册方法的一个实施例；
图 4示出了本发明的注销方法的一个实施例。 具体实施方式 为了便于本领域一般技术人员理解和实现本发明， 现结合附图描绘本发 明的实施例。
本发明提供了一种注册 /注销系统， 如图 1所示， 所述注册 /注销系统包括： 通信网絡、 客户端、 业务管理服务器、 业务注册 /注销服务器和应用服务器。 下面将详细说明本发明的注册 /注销系统。
所述的通信网络包括 NGN网络和 /或 Internet (互连网） 网絡， 用于连接客 户端、 应用服务器、 业务注册 /注销服务器和业务管理服务器， 可使客户端、 应用服务器、 业务注册 /注销服务器和业务管理服务器之间进行互相通信。 当 上述设备通过 NGN相连时， 可采用 SIP进行通信， 当上述设备通过 Internet网络 相连时， 可采 HTTP (超链接传输协议）等协议进行通信。
所述的客户端通过通信网络与业务管理服务器相连， 用于生成业务请求 信息， 将生成的业务请求信息发给业务管理服务器， 并根据预定规则和业务 管理服务器返回的各个业务注册 /注销信息向业务注册 /注销服务器发出各个 业务注册 /注销请求信息。 所述业务请求信息包括用户名和用户密码。 所述客 户端包括加密装置， 用于对业务请求信息和 /或业务注册 /注销信息进行加密。
所述的业务管理服务器用于存储用户信息。 所述用户信息包括用户名、 用户密码及该用户所对应的各个业务信息。 所述业务信息包括业务帐号、 业 务密码、 业务注册 /注销服务器地址、 注册方式信息以及加密方式等信息。 所 述业务管理服务器还包括： 解密装置， 用于对业务请求信息进行解密； 鉴权 装置， 用于根据用户信息对业务请求信息进行鉴权。
所述的业务注册 /注销服务器用于根据各个业务注册 /注销请求信息对各 个业务进行注册 /注销， 并可根据客户的注册情况是否允许用户使用所请求的 业务。 所述业务注册 /注销服务器在物理实体上可以是应用服务器（AS ) 、 软 交换或者其他服务器。
所述的应用服务器用于运行各种业务。
本发明还提供了一种可一次注册 /注销多个业务的注册 /注销方法， 下面详 细描述所述的注册 /注销方法。
首先， 用户可在营业厅或通过通信网络开通多项业务, 并获得相关的业 务信息， 然后将业务信息存储到业务管理服务器的用户信息表中。
如图 2所示， 在步骤 21中， 客户端向业务管理服务器发出业务请求信息， 所述业务请求信息包括用户名、 用户密码。 为了保证用户信息的安全性， 可 在客户端对业务请求信息进行加密， 例如使用 DES (数据加密标准）等方法对 业务请求信息进行加密。
客户端向业务管理服务器发出业务请求信息可以有多种时机， 例如： 在 客户端接收到用户注册 /注销请求后发出业务请 信息， 按照事先设定的时间 发出业务请求信息， 按固定时间间隔发出业务请求信息等。
客户端向业务管理服务器发出业务请求信息可以有多种方式， 例如， 以 HTTP等协议通过 Internet网络、 或者以 SIP等协议通过 NGN向业务管理服务器 发出业务请求信息。
在步骤 22中， 业务管理服务器首先对加密的业务请求信息进行解密， 然 后根据用户信息对业务请求信息进行鉴权， 即验证用户名与用户密码是否一 致， 若一致， 则鉴权通过， 否则， 鉴权失败。
在步骤 23中， 判断鉴权是否通过， 若通过， 执行步骤 24, 否则， 执行步 骤 27。
在步骤 24中， 鉴权通过以后， 业务管理服务器取出该用户的业务信息， 并将业务信息发给客户端。 所述业务信息包括多项业务信息。 在步驟 25中， 客户端根据业务管理服务器发来的业务信息生成业务注册 / 注销请求信息， 并按照预定规则将业务注册 /注销请求信息发给业务注册 /注销 服务器。
在步骤 26中， 业务注册 /注销服务器根据业务注册 /注销请求信息对业务进 行注册 /注销。
在步骤 27中， 进行错误处理， 可以提示客户端用户名与密码不一致， 要 求用户重新提交业务请求信息， 重新执行步骤 21至 23 , 直至鉴权通过， 或者 提交次达到预定次数（如 5次） 时， 鉴权仍未通过， 可以拒绝该用户的注册 / 注销请求。 在本发明中， 采用提交注册 /注销请求次达到 5次， 鉴权仍未通过， 拒绝该用户的注册 /注销倩求， 提示用户带着有效证件到营业厅重新设置用户 密码。
所述预定规则是指注册 /注销顺序，例如可以按照事先配置的优先級顺序， 或者随机的一一向业务注册 /注销服务器申请注册 /注销。
为了让用户获知注册 /注销情况，客户端可以在全部业务注册 /注销完成后 返回注册 /注销成功消息给用户， 也可以在关键业务注册 /注销完成后返回注册 /注销成功消息给用户， 以便使用户得知某些业务是否注册 /注销成功。
各个业务的注册 /注销方式可在业务申请时确定，在分配业务时进行配置， 根据申请时方式不同， 可以将业务注册 /注销方式配置为标准 SIP注册 /注销流 程、 网站 HTTP/HTTPS注册 /注销流程或任何自定义的注册 /注销流程。
应该注意到， 各个业务对应的业务注册 /注销服务器可以是不同的， 也可 以是相同的。
如图 3所示， 下面以 NGN业务为实例说明一次注册多个业务的流程。 假设 NGN中有一用户， 其用户名为 Ray， 用户密码为 RayPwd, 已经申请开通三种 NGN业务： 业务 A, 业务 B, 业务 C, 客户端地址为 Ray@192.0.2.4, 业务注册 /注销服务器的信息如表 1所示。
表 1 业务注册 /注销服务器信息表 服务器名 服务器地址 服务器类型 备注
AMS1 www.AMS 1.com:8001/resistrar.do Account Management Server 业务管理服务器
ARS1 ARSl.com:5060 Account Registration Server 业务注册 /注销服务器
ARS2 www.ARS2.com:8002/registrar.do Account Registration Server 业务注册 /注销服务器 表 2示出了用户信息。
表 2 用户信息表
Figure imgf000008_0001
表 3示出了业务信息
表 3 业务信息表
Figure imgf000008_0002
在步骤 301中， 用户 Ray通过客户端界面输入用户名 Ray和密码 RayPwd, 然后点击按鈕提交业务请求信息； 在步骤 302中， 客户端将用户名 Ray和密码 RayPwd等信息封装为报文发送 给 AMS1。 为了保证用户信息的安全性， 可对用户名、 密码等用户信息进行加 密后， 然后将加密的用户信息发送到 AMS1。 下面是客户端到 AMS1发送业务 请求信息的消息示例。
S2 REGISTER Client->AMS15 消息示例如下：
POST http : //www . AMSl . coiu : 80Ql/reqistrar■ do HTTP/1♦ 1
Content-Type： application/x-ww -form-url encoded
Accept - Encoding : gzip, deflate
Content-Length： 40
Connection： Keep-Alive
Cache-Control： no-cache narae ay&password RayPwd&clientaddr-RayglSS , 0 . 2 . 4 &me :hod=login & s ubmi t s ubmi t
在步骤 303中， AMS1接收到客户端发送的 HTTP报文后， 解析报文得到用 户名， 密码。 如果报文已被加密， 则还需要进行解密操作。 AMS1将客户端发 送的用户名和密码， 与 AMS1存储的用户信息（见 2表用户信息表）核实鉴权。
在步骤 304中， 鉴权通过则业务管理服务器取出存储的该用户对应的业务 信息（见表 3用户业务信息表）； 业务管理服务器将该用户对应的业务信息发 给客户端；
S4 200 OKAMSl->Client, 消息示例如下：
HTTP/1 . 1 200 0K
Set-Cookie : JSESSIONID=87D42196E7BB95A3F45D19FQE31CD62F
Content- Type : text/html ; charset=gb2312
Content -Length : 20
Connection : close
<registrar>
<accourrtVectorInf o>
<accountinfo>
<username>Ray</userName>
<serviceName>Service A<serviceName>
<account>SA000001</response>
<pass ord>SA000001Pwd</password>
<registServer>ARSl</registSe3:ver>
<£"egistMethod>SIP</registi iethod>
<registDecode>MD5<registDecode>
<loginPriority>High</loginPriority>
<loginMust>Yes</login ust>
<logoutPriority>High</logoutPriority>
<logoutMust>Yes</logoutMust>
</accountinf o>
<accountinf o> <username>Ray</userNaine>
<serviceName>Service B<serviceName>
<account>SB00000K/response>
<password>SB000001Pwd</password>
<regist Server>ARSK/regist Server >
<o:egistMethod>SIP</:t:eg:LstMethod>
<registDecode>MD5<registDecode>
<loginPriority>Mid</loginPriority>
<loginMust>Yes</loginMust>
<logoutPriority> id< /logout Priori y>
<logoutMust>Yes</logoutMust>
</accountinf o>
<accountinf o>
<username>Ray</userName>
<serviceName>Service C<serviceName>
<account>SC00000K/response>
<pass ord>SC000001Pwd</password>
<registServer>ARS2</regi s Server >
<regist ethod>HTTP</registMethod>
<registDecode>NO<registDecode>
<loginPriority>Low</loginPriority>
<loginMust>Yes</loginMust>
<logoutPriority>Low< /logou Prior it y>
<logoutMust>Yes</logout ust>
</ accountinf o>
<accountVectorInf o>
</ registrar> 客户端按照事先定义的优先级别根据业务信息对所有的业务进行注册； 由于业务 A的优先级最高， 所以最先处理业务 A。
在步骤 305中， 由于业务 B的注册方式为标准 SIP方式， 客户端向 ARS1请 求4兆战字， 以便客户端根据挑战字对业务 A注册请求进行加密， 所述挑战字的 作用相当于密钥。 在步骤 306中， ARS1向客户端发出挑战字。 在步骤 307中， 客户端根据挑战字对业务 A注册请求信息进行加密后发给 ASR1。 即， AMS1 与 ARS1配合完成业务 A的注册。 下面是业务 A注册过程的消息示例。
S5 REGISTER Client->ARS1 , 消息示例如下：
REGISTER sip: ARS1. com SIP/2.0
Via: SIP/2.0/UDP temp. ARS1. com: 5080
Max-Forwards： 70
To： Ray<sip： RaygARSJ . com>;
From: Ray<sip： RayQARSl . coiT!>;tag=456248
Call- ID: 843817637684230@temp.ARSl.com
CSeq: 1 REGISTER
Contact: <sip:Ray@192.0.2.4>
User-Agent： Service A/1.0
Expires： 72000
Content-Length： 0
S6401 with Authorization ARSl->Client, 信息示例如下: SIP/2.0 401 Unauthorized
Allow: 工 ISIVITE, ACK, BYE, CANCEL, OPTIONS, REGISTER
Via: SIP/2.0/UDP temp. ARS1. com: 5080
To： Ray<sip： ay^ARSl . com>r- tag=2493k59kci
From: Ray<sip： Ray@AKSl . οοπΐ>; tag=456248
Call- ID: 843817637684230@temp.ARSl.com
CSeq: 1 REGISTER
Contact： <sip： ARS1. com>
Expires: 72000
Content-Length： 0
www-Authenticate： Digest
qop="auth/' , nonce=/B JbQ .001,', algor ithm^^mdS " , realm="A Sl · com"
S7 REGISTER Client->ARS1 , 消息示例如下:
REGISTER sip: ARSl . com SIP/2.0
Via; SIP/2.0/UDP temp .ARSl . com: 5080
Max-Forwards： 70
To: Ray<si ： Ray^ARSl . com>； t ag=2493 k59 kd
From: Ray<sip: Ray @ ARSl . com>; tag=456248
Call -工 D: 843817637684230@temp. ARSl. com
CSeq: 2 REGISTER
Contact； <sip： Ray@ 192.0.2.4>
User-Agent： Service A/1.0
Expires: 72000
Content-Length; 0
Authorization： Digest a 1 g o r i t hm= "md 5 " ,
cnonce=//51f308670-0972-809d-3409a-4a091dld09 '/
nc^OOOOOOOl, nonce^^BJbQ.001", qop^^'auth", realm^^A Sl . com
response=//lacl7228a5e400a99f378eeedf87aa2c"/
uri="sip: A S2. us ername=SA000001 Q ARS 1. com
S8200 OK ARSl»>Client? 信息示例如下:
SIP/2.0 200 OK
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, REGISTER, SUBSCRIBE NOTIFY, INFO
Via: SIP/2.0/UDP temp .ARSl . com: 5080
To: Ray<sip： Ray@A Sl · cora>; tag=2493k59kd
From： Ray < si ： RayQA Sl . com>； tag= 56248
Call -工 D: 843817637684230@temp.ARSl.com
CSeq: 2 REGISTER
Contact： <s±p:ARSl . com>
User-Agent： Service A/1.0
Expires： 72000
Content-Length： 0 在步骤 308中， 当业务 A注册完成后， 根据业务 A的注册情况， ARS1将注 册成功或失败信息返回客户端。
由于业务由于业务 B的优先级较高， 所以应处理业务 B。
在步骤 309中， 由于业务 B的注册方式为标准 SIP方式， 客户端向 A S1请 求挑战字， 以便客户端根据挑战字对业务 B注册请求进行加密， 所述挑战字的 作用相当于密钥。 在步骤 310中， A S1向客户端发出挑战字。 在步骤 311中， 客户端根据挑战字对业务 B注册请求信息进行加密后发给 ASR1。下面是业务 B 注册过程的消息示例。
S9 REGISTER Client->ARS1, 消息示例如下：
REGISTER sip: ARSl . com SIP/2.0
Via: SIP/2.0/UDP t emp. ARSl . com: 5080
Max-Forwards： 70
To: Ray<sip： Ray@ARS2. com>;
From: Ray<sip： RayQ ARSl . com>;tag=4562 8
Call-ID: 843817637684230@temp.ARSl.com
CSeq: 1 REGISTER
Contact: <sip:Ray@192.0.2.4>
User-Agen ： Service B/1.0
Expires： 72000
Content-Length： 0
S 10401 with Authorization ARS 1 -> Client , 信息示例如下：
SIP/2.0 401 Unauthorized
Allow: INVITE, AC , BYE, CANCEL, OPTIONS, REGISTER
Via: SIP/2.0/UDP temp. ARSl . com: 5080
To: Ray<sip:Ray§Ai?S2. coin>;tag=2493k59kd
From: Ray<sip： RayOA Sl . com>;tag=456248
Call- ID: 843817637684230@temp.ARSl.com
CSeq: 1 REGISTER
Contact： <si : ARSl . com>
Expires: 72000
Content-Length： 0
www-Authenticate： Digest
qop="auth" , nonce="B JbQ .001", algor ithm="md5 " , realm="A S2. com-
SI 1 REGISTER Client ->A S15 消息示例如下:
REGISTER sip: ARSl . com SIP/2.0
Via: SIP/2.0/UDP temp. ARSl . com: 5080
Max-Forwards : 70
To: Ray< s ip： Ray . com>; tag=2493k59kd
From: Ray<si ： RayQ ARSl . coi«>; tag=456248
Call -工 D: 843817637684230@temp.ARSl.com
CSeq: 2 REGISTER
Contac ： <si ： Ray@192.0.2.4>
User-Agen ： Service B/1.0
Expires： 72000
Content-Length; 0
Authorization： Digest algorithm=/md5' /
cnonce=//51f308670-0972-809d-3409a-4a091dld09/',
nc=00000001,nonce="BJbQ.001/,,qop=,auth/ /realm=/'A 51. com
response=/lacl7228a5e400a99f378eeedf87aa2c/',
uri= sip： ARSl . com'', usernarue=SB000001@AR51 , com
S12200 OK ARSl-> Client, 信息示例如下: SIP/2.0 200 OK
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, REGISTER, SUBSCRIBE NOTIFY, INFO
Via: SIP/2.0/UDP temp.ARSl . com: 5080
To： Ray<sip： RayQARSl . com>; tag=2493k59kd
From: Ray<sip： Ray@ ARS2. com>; tag=4562 8
Call-ID: 843817637684230@temp.ARSl.com
CSeq: 2 REGISTER
Contact： <sip : ARS1. com>
User-Agent： Service B/1.0
Expires： 72000
Content-Length： 0 在步骤 312中， 当业务 B注册完成后， 根据业务 B的注册情况， A S1将注 册成功或失败信息返回客户端。
最后只剩下业务 C, 客户端对业务 C进行处理。
在步骤 313中， 由于业务 C的注册方式为 HTTP, 客户端向 ASR2发出业务 注册请求信息， 在步骤 314中， 当业务 C注册完成后， 根据业务 C的注册情况， ARS2将注册成功或失败信息返回客户端。下面是业务 C注册过程的消息示例。
S13 REGISTER Client ->ARS2, 消息示例如下：
POST http://www.ARS2. com: 8002/registrar . do HTTP/1.
Content-Type： application/x- ww-f orm-urlencoded
Content-Length： 140
Connection： Keep- Alive
Cache-Control： no-cache
<registrar>
<method>login</methol>
<serviceinf o>
<servicename>Service C</servicename>
</ serviceinf o>
<acco ntinf o>
<account>SC00000K/response>
<password>SC000001Pwd</password>
</ account info>
<clientinf o>
<clientaddr>Ray@192.0.2.4</clientaddr>
</ clientinf o>
</ registrar>
S14200 OK A S2-> Client, 消息示例如下 ·,
HTTP/1.1 200 OK
Set-Cookie: JSESSIOinD=87D42196E7BB95A3F45D19FAF31AB62F
Content-Type： text /html; charset=gb2312
Content-Length： 104
Connection: close
<registrar>
<response>
<rspcode>l</rspcode>
Figure imgf000014_0001
在步骤 315中， 由于该用户对应的三个业务都是必须注册的， 如果所有业 务注册成功则返回注册成功信息， 否则返回注册失败信息。
如图 4所示， 下面描述注销过程。
在步骤 401中， 用户 Ray通过客户端界面输入用户名 Ray和密码 RayPwd, 然后点击按钮提交业务请求；
在步骤 402中， 客户端将用户名 Ray和密码 RayPwd等信息封装为报文发送 给 AMS1。 为了保证用户信息的安全性， 可对用户名、 密码等用户信息进行加 密后， 然后将加密的用户信息发送到 AMS1。 下面是客户端到 AMS1发送业务 请求的消息示例。
S2 REGISTER Client->AMS 1 , 消息示例如下：
~ POST http : //www. AMS1 . com: 8001/registrar . do HTTP/1 . 1
Content-Type： application/x-w w-f orm-urlencoded
Accept— Encoding : gzip, deflate
User-Agent : Mozilla/4 . 0 ( compatible ; MSIE 6. 0 ; Windows NT 5 . 1 ) Content-Length： 40
Connection : Keep -Alive
Cache-Control： no-cache
Cookie： JSESSIONID=87D42196E7BB95A3F45D19FQE31CD62F
naine=Kay&passwo;i:d=SayiVd&clieritacid:r=Ray@ 192 . 0. 2 . 4 &method=logout &submit=submit
在步骤 403中， AMS1接收到客户端发送的 HTTP报文后， 解析报文得到用 户名和密码。 如果报文已被加密， 则还需要进行解密操作。 AMS1将客户端发 送的用户名和密码， 与 AMS1存储的用户信息（见 2表用户信息表）核实鉴权。
在步骤 404中， 鉴权通过则业务管理服务器取出存储的该用户对应的业务 信息（见表 3用户业务信息表）； 业务管理服务器将该用户对应的业务信息发 给客户端；
S4 200 OK AMSl->Client, 消息示例如下： HTTP/1 . 1 200 OK
Set-Cookie : JSESSI0NID 87D42196E7BB95A3F45D19FQE31CD62F
Content-Type： text /html; charset=gb2312
Content-Length： 20
Connection : close
<registrar>
<accourrtVecto:rInf o>
<accountinf o>
< u s e rname >Ray</userN ame >
<serviceName>Service A<serviceName>
<account>SA00000K/response>
<password>SA000001Pwd</password>
<registServer>ARSK/registServer>
<registMeth〇d>SIP</registMethod>
<registDecode> D5<registDecode>
<loginPrio;t:ity>Higli</loginPriority〉
<loginMust>Yes</logixiMust〉
<logoutPriority>High</ logout Priority>
<logoutMust>Yes</logoutMust>
< /accoun info>
<accountinf o>
<username>Ray</userName>
<serviceName>Service B<serviceName>
<account>SB00000K/response>
<password>SB000001Pwd</pass ord>
<r egist Server >ARSK/regist Server >
<registMethod>SIP</registMethod>
<registDecode>MD5<registDecode>
<loginPriority>Mid</loginPriority>
<loginMust>Yes</loginMust> .
<logoutPriority>Mid</logoutPriority>
<logoutMust>Yes</logoutMust>
</accountinf o>
<accountinf o>
<username>Ray</userName>
<serviceName>Service C<serviceName>
<account>SC00000K/response>
<password>SC000001Pwd</pass ord>
<registServer〉ARS2</:regist Served
<regxstMethod〉HTTP</registMethod>
<registDecode>NO<registDecode>
<loginPriority>Low</loginPriority>
<login ust>Yes</loginMust>
<logoutPriority>Low</logoutPriority>
<logoutMust>Yes</logoutMust>
</accountinf o>
<accountVectorInf o>
</ registrar> 客户端按照事先定义的优先级别根据业务信息对所有的业务进行注销； 由于业务 A的优先级最高， 所以最先处理业务 A。
在步骤 405中， 客户端向 ARS1发出业务 A的注销请求。 客户端发出的注销 请求消息与注册请求消息的唯一区别是 Expires字段取值为 0。
在步骤 406中， 当业务 A注销完成后， 根据业务 A的注销情况， ARS1将注 销成功或失败信息返回客户端。
S4 REGISTER Client->ARS1 , 消息示例如下:
REGISTER sip: ARS1. com SIP/2.0
Via: SIP/2.0/UDP temp. A S1. com: 5080
Max-Forwards： 70
To: Ray< s i : Ray @ AKS2. co >；
From: Ray<sip： Ray@ ARS1. com>； ag=456248
Call-ID: 843817637684230@temp.ARSl.com
CSeq: 3 REGISTER
Contact： <sip:Ray@192.0.2.4>
User-Agent： Service A/1.0
Expires： 0
Content-Length： 0
S5200 OK ARSl->Client， 信息示例如下:
SIP/2.0 200 OK
Allow: INVITE, ACKr BYE, CANCEL, OPTIONS, REGISTER
Via: SIP/2.0/UDP temp. ARS1. com: 5080
To: Ray<sip： Ray@ARSl . com>
From: Ray<sip： Ray@Ai?Sl . com> ; tag= 562 8
Call-工 D: 843817637684230@temp.ARSl.com
CSeq: 3 REGISTER
Contac ： <si ： ARS1. com>
User-Agen ： Service A/1.0
ESxpires： 0
Content-Length： 0 由于业务由于业务 B的优先级较高， 所以应处理业务；8。
在步裸 407中， 客户端向 ARS1发出业务 B的注销请求。 客户端发出的注销 请求消息与注册请求消息的唯一区别是 Expires字段取值为 0。
在步骤 408中， 当业务 B注销完成后， 根据业务 B的注销情况， ARS1将注 销成功或失败信息返回客户端。
S6 REGISTER Client->ARS1 , 消息示例如下：
REGISTER sip: ARS1. com SIP/2.0
Via: SIP/2,0/UDP temp. ARS1. com: 5080
Max- Forwards： 70
To: Ray<si ： Ray@ ARS1. com>；
From: Ray<sip： Ray@ARS2. com>; tag=456248
Call - ID: 843817637684230@temp.ARSl.com
CSeq: 3 REGISTER
Contact: <sip:Ray@192.0.2.4>
User-Agen ： Service A/1.0
Expires： 0
Content-Length： 0
S7200OKARSl->Client, 信息示例如下: SIP/2.0 200 OK
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, REGISTER
Via: SIP/2.0/UDP temp. ARS1. com: 5080
To: Ray<sip： Ray@ AKS2. com>
From: Ray<si ： RayQ ARS1. com>; tag=456248
Call- ID: 843817637684230@temp.ARSl.com
CSeq: 3 REGISTER
Contact： <sip : ARS1. com>
User-Agent： Service A/1.0
Expires： 0
Content-Length： 0 最后处理业务 c。
在步骤 409中， 客户端向 ARS2发出业务 C的注销请求。 在步驟 410中， 当 业务 C注销完成后，根据业务 C的注销情况， ARS2将注销成功或失败信息返回 客户端。
S8 REGISTER Client->ARS2? 消息示例如下：
POST i t^>: / /www. ARS2.com: 8002/ registrar .do HTTP/1.1
Content-Type： application/x-w w-f orm-urlencoded
Content-Length： 140
Connection： Keep— Alive
Cache-Control： no-cache
Cookie: JSESSION工 D=87D42196E7BB95A3F45D19FAF31AB62F
<registrar>
<method>logout</method>
<serviceinf o>
<servicename>Service C</servicename>
</serviceinf o>
<accountinf o>
<account>SC000001</response>
<pass orci>SC000001Pwd</pass ord>
</accountinf o>
<clientinf o>
<clientaddr>Ray@192.0.2.4</clientaddr>
</ client info>
</ registrar>
S9200OKARS2->Client, 消息示例如下:
HTTP/1.1 200 OK
Content-Type： text /html; charset=gb2312
Content-Length: 104
Connection: close
<registrar>
<response>
<rspcode>K/rspcode>
</ response>
</ egis trar> 在步骤 411中， 由于该用户对应的三个业务都是必须注销的， 如果所有业 务注销成功则返回注销成功信息， 否则返回注销失败信息。
应该注意的是， 在业务管理服务器的用户信息中， 各个业务对应同一个 用户名和用户密码， 也可以对应不同的用户名和用户密码， 这时客户端向业 务管理服务器发出的业务请求信息中应包括与各个业务相对应的用户名和用 户密码。
根据本发明， 可一次注册 /注销多个业务， 从而避免了用户申请多个业务 后在使用时需要——注册 /注销每一个业务， 因此， 节省了用户的时间， 给用 户带来良好的体验， 给业务的集成带来好处。
虽然通过实施例描绘了本发明， 但本领域普通技术人员知道， 在不脱离 本发明的精神和实质的情况下， 就可使本发明有许多变形和变化， 本发明的 范围由所附的权利要求来限定。

Claims

权利要求
1、 一种注册 /注销系统， 其特征在于， 包括：
客户端， 用于向业务管理服务器发出业务请求信息， 并根据预定规则和 业务管理服务器返回的各个业务信息向业务注册 /注销服务器发出各个业务注 册 /注销请求信息；
业务管理服务器， 用于存储用户信息， 所述用户信息包括各个业务信息， 并向客户端发送各个业务信息；
业务注册 /注销服务器， 用于根据各个业务注册 /注销请求信息对业务进行 注册 /注销。
2、 根据权利要求 1所述的注册 /注销系统， 其特征在于， 所述的客户端还 包括： 加密装置， 用于对业务请求信息进行加密。
3、 根据权利要求 2所述的注册 /注销系统， 其特征在于， 所述的业务管理 服务器还包括： 解密装置， 用于对加密的业务请求信息进行解密。
4、 根据权利要求 1所述的注册 /注销系统， 其特征在于， 所述的业务管理 服务器还包括： 鉴权装置， 用于对业务请求信息进行鉴权。
5、 根据权利要求 1所述的注册 /注销系统， 其特征在于， 所述的注册 /注销 系统还包括： 通信网络， 所述通信网络包括下一代网络和互联网， 用于连接 客户端、 业务管理服务器和业务注册 /注销服务器， 并实现它们之间的通信。
6、 一种注册 /注销方法， 其特征在于， 包括：
客户端向业务管理服务器发出业务请求信息；
业务管理服务器根据业务请求信息获得多个业务信息， 并将多个业务信 息发给客户端；
客户端根据多个业务信息生成多个业务注册 /注销请求信息， 并以预定规 则向业务注册 /注销服务器发出多个业务注册 /注销请求信息；
业务注册 /注销服务器根据多个业务注册 /注销请求信息对多个业务进行 注册 /注销。
7、 根据权利要求 6所述的注册 /注销方法， 其特征在于， 所述的步骤客户 端向业务管理服务器发出业务请求信息之前还包括： 客户端对业务请求信息 进行加密。
8、 根据权利要求 7所述的注册 /注销方法， 其特征在于， 所述的步骤业务 管理服务器根据业务请求信息获得多个业务信息， 并将多个业务信息发给客 户端之前还包括： 业务管理服务器对加密的业务请求信息进行解密。
9、 根据权利要求 6所述的注册 /注销方法， 其特征在于， 所述业务信息包 括业务帐号、 业务密码、 业务注册 /注销服务器地址。
10、根据权利要求 6所述的注册 /注销方法， 其特征在于， 所述预定规则包 括： 随机注册 /注销、 按优先级注册 /注销。.
11、 根据权利要求 6所述的注册 /注销方法， 其特征在于， 在执行步驟业 务管理服务器根据业务请求信息获得多个业务信息 , 并将多个业务信息发给 客户端之前还执行： 业务管理服务器根据业务请求信息进行鉴权。
PCT/CN2006/001518 2005-07-19 2006-06-30 Méthode d’inscription/annulation et système d’inscription/annulation WO2007009344A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
AT06753078T ATE472919T1 (de) 2005-07-19 2006-06-30 Ein registrierungs-/löschungsverfahren und registrierungs-/löschungssystem
DE602006015147T DE602006015147D1 (de) 2005-07-19 2006-06-30 Ein registrierungs-/löschungsverfahren und registrierungs-/löschungssystem
CNA200680011509XA CN101156363A (zh) 2005-07-19 2006-06-30 一种注册/注销系统和注册/注销方法
US11/664,652 US20080091835A1 (en) 2005-07-19 2006-06-30 Register/Unregister System And A Register/Unregister Method
EP06753078A EP1791297B1 (en) 2005-07-19 2006-06-30 A registration/cancel method and a registration/cancel system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510085028.0 2005-07-19
CNA2005100850280A CN1852136A (zh) 2005-07-19 2005-07-19 一种注册/注销系统和注册/注销方法

Publications (1)

Publication Number Publication Date
WO2007009344A1 true WO2007009344A1 (fr) 2007-01-25

Family

ID=37133606

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/001518 WO2007009344A1 (fr) 2005-07-19 2006-06-30 Méthode d’inscription/annulation et système d’inscription/annulation

Country Status (6)

Country Link
US (1) US20080091835A1 (zh)
EP (1) EP1791297B1 (zh)
CN (2) CN1852136A (zh)
AT (1) ATE472919T1 (zh)
DE (1) DE602006015147D1 (zh)
WO (1) WO2007009344A1 (zh)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101197671B (zh) * 2006-12-08 2012-10-10 中兴通讯股份有限公司 通信系统中的鉴权方法
CN101127769B (zh) * 2007-08-20 2012-04-04 华为技术有限公司 基于会话发起协议的用户注册的方法、系统及终端、服务器
US8561055B2 (en) * 2009-10-15 2013-10-15 Blackberry Limited Method, system and apparatus for management of push content
EP2320376A1 (en) * 2009-11-06 2011-05-11 Research In Motion Limited Method, system and apparatus for management of push content when changing computing devices
EP2365677B1 (en) * 2010-03-03 2020-04-08 BlackBerry Limited Method, system and apparatus for configuring a device for interaction with a server
EP2363998B1 (en) * 2010-03-03 2015-01-07 BlackBerry Limited Method, system and apparatus for managing push data transfers
CN102594782B (zh) * 2011-01-14 2016-03-02 中国移动通信集团公司 Ip多媒体子系统鉴权方法、系统及服务器
CN102694770A (zh) * 2011-03-22 2012-09-26 中兴通讯股份有限公司 一种业务平台中多类型资源管理的系统及方法
JP6296324B2 (ja) 2013-07-12 2018-03-20 ブラザー工業株式会社 登録サーバのプログラム、情報機器、情報機器のプログラム、及びネットワークシステム
CN103888288A (zh) * 2014-02-20 2014-06-25 北京优联实科信息科技有限公司 一种注册方法、管理器、注册器与系统
CN106375102B (zh) * 2015-07-22 2019-08-27 华为技术有限公司 一种服务注册方法、使用方法及相关装置
CN106101293A (zh) * 2016-08-30 2016-11-09 北京小米移动软件有限公司 账号管理方法及装置
JP6910894B2 (ja) 2017-09-01 2021-07-28 キヤノン株式会社 情報処理装置、制御方法、およびプログラム
CN113630273A (zh) * 2021-08-06 2021-11-09 百果园技术(新加坡)有限公司 账号注销系统、方法、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030169695A1 (en) * 1999-11-10 2003-09-11 Qualcomm, Inc. Data center for providing subscriber access to data maintained on an enterprise network
CN1543167A (zh) * 2002-12-02 2004-11-03 ���ǵ�����ʽ���� 利用会话发起协议的终端注册方法
US20040236633A1 (en) 2003-05-05 2004-11-25 Knauerhase Robert C. Management and arbitration of mobile service discovery
CN1617498A (zh) * 2003-11-11 2005-05-18 华为技术有限公司 下一代网络终端的孵化方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7272636B2 (en) * 2001-04-24 2007-09-18 Sun Microsystems, Inc. Peer group name server
US6981263B1 (en) * 2001-06-29 2005-12-27 Bellsouth Intellectual Property Corp. Methods and systems for converged service creation and execution environment applications
US6885861B2 (en) * 2001-08-24 2005-04-26 Nokia Corporation Service mobility and recovery in communication networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030169695A1 (en) * 1999-11-10 2003-09-11 Qualcomm, Inc. Data center for providing subscriber access to data maintained on an enterprise network
CN1543167A (zh) * 2002-12-02 2004-11-03 ���ǵ�����ʽ���� 利用会话发起协议的终端注册方法
US20040236633A1 (en) 2003-05-05 2004-11-25 Knauerhase Robert C. Management and arbitration of mobile service discovery
CN1617498A (zh) * 2003-11-11 2005-05-18 华为技术有限公司 下一代网络终端的孵化方法

Also Published As

Publication number Publication date
EP1791297A4 (en) 2008-03-12
EP1791297A1 (en) 2007-05-30
ATE472919T1 (de) 2010-07-15
EP1791297B1 (en) 2010-06-30
DE602006015147D1 (de) 2010-08-12
CN101156363A (zh) 2008-04-02
US20080091835A1 (en) 2008-04-17
CN1852136A (zh) 2006-10-25

Similar Documents

Publication Publication Date Title
WO2007009344A1 (fr) Méthode d’inscription/annulation et système d’inscription/annulation
US10104068B2 (en) Service provider invocation
US10277577B2 (en) Password-less authentication system and method
US10136315B2 (en) Password-less authentication system, method and device
JP5651313B2 (ja) 連続する再認証を必要としないｓｉｐシグナリング
US9264420B2 (en) Single sign-on for network applications
KR101475981B1 (ko) 만료된 패스워드 처리
EP3328023B1 (en) Authentication of users in a computer network
WO2003091891A1 (en) Authentication and protection for ip application protocols based on 3gpp ims procedures
CN112261022A (zh) 一种基于api网关的安全认证方法
JP2009290329A (ja) Ｉｐ通信システム、サーバユニット、端末デバイスおよび認証方法
US20160269382A1 (en) Secure Distribution of Non-Privileged Authentication Credentials
EP2809042A1 (en) Method for authenticate a user associated to a user agent implemented over SIP protocol
US8453229B2 (en) Push type communications system
US20080065776A1 (en) Method of connecting a first device and a second device
JP2006270431A (ja) 呼制御装置、端末、これらのプログラム、及び通信チャネル確立方法
JP4945591B2 (ja) 認証システム、認証方法、および仮パスワード発行装置
EP4207682A1 (en) Device, method and system of handling access control
Sengul et al. RFC 9431 Message Queuing Telemetry Transport (MQTT) and Transport Layer Security (TLS) Profile of Authentication and Authorization for Constrained Environments (ACE) Framework
Gustafson et al. Securely Available Credentials (SACRED)-Credential Server Framework
Alvarez‐Bermejo et al. Blind signatures using light variations in CCD sensors as a pattern to avoid identity forging
Gustafson et al. RFC3760: Securely Available Credentials (SACRED)-Credential Server Framework
Nystrom et al. Network Working Group D. Gustafson Request for Comments: 3760 Future Foundation Category: Informational M. Just Treasury Board of Canada

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2006753078

Country of ref document: EP

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWP Wipo information: published in national office

Ref document number: 2006753078

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 200680011509.X

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 11664652

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

WWP Wipo information: published in national office

Ref document number: 11664652

Country of ref document: US