WO2008049300A1 - Procédé, terminal, dispositif et système pour obtenir les informations d'identification d'un serveur d'application - Google Patents
Procédé, terminal, dispositif et système pour obtenir les informations d'identification d'un serveur d'application Download PDFInfo
- Publication number
- WO2008049300A1 WO2008049300A1 PCT/CN2007/002191 CN2007002191W WO2008049300A1 WO 2008049300 A1 WO2008049300 A1 WO 2008049300A1 CN 2007002191 W CN2007002191 W CN 2007002191W WO 2008049300 A1 WO2008049300 A1 WO 2008049300A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application server
- information
- identifier
- identification information
- module
- Prior art date
Links
Classifications
-
- 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/1063—Application servers providing network services
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Definitions
- the present invention relates to the field of network communication technologies, and in particular, to a method, a terminal, a device, and a system for acquiring application server identification information. Background technique
- IMS Internet protocol Multimedia Subsystem
- PoC PTT over Cellular
- the terminal user when an end user experiences a service that needs to provide corresponding server identification information, the terminal user often obtains the identification information of the corresponding application server from the website provided by the operator through the PortaK portal website, and then manually inputs the identification information of the corresponding application server as a program. A configuration message at runtime.
- the inventor has found that after obtaining the identification information of the application server by using the above technical solution, the terminal user needs to manually input the identification information of the application server, which may make the terminal user feel inconvenient.
- the format of the application server identification information is quite specialized, for example: sip:[email protected], this will make the terminal user difficult to understand the format, and thus the terminal user needs to accurately input the identification information of the application server.
- the identification information of the application server is changed, the terminal cannot correctly experience the multimedia service.
- the present invention provides a method, a terminal, a device, and a system for acquiring application server identification information, which are used to solve the problem that the terminal cannot automatically obtain the target application server identification information in the prior art.
- the present invention provides a method for obtaining application server identification information, including the following steps:
- the first device sends an identification request to the second device
- the second device returns the identification information of the target application server to the first device.
- the present invention also provides a system for acquiring application server identification information, including a first device and a second device.
- the first device includes an identifier requesting module, configured to send an identifier request to the second device, where the second device includes a processing module, configured to return, to the first device, identifier information of the target application server.
- the present invention also provides a terminal, comprising a module for running an application, the terminal further comprising an identification requesting module, configured to send an identification request according to the application.
- the present invention further provides a device, comprising a second receiving module for receiving information, the device further comprising a processing module, configured to send the identification information of the target application server according to the identifier request received by the second receiving module.
- the first device can automatically obtain the target application server identification information by sending the identification request to the second device, so that the user does not need to manually input the complicated and difficult application when experiencing the service that needs to provide the corresponding application server identification information.
- Server identification information which improves user experience satisfaction.
- FIG. 1 is a flowchart of acquiring application server identification information by a user terminal according to Embodiment 1 of the present invention
- FIG. 2 is a flowchart of confirming identification information of an application server obtained by a user terminal to a target application server according to Embodiment 1 of the present invention
- FIG. 3 is a flowchart of acquiring application server identifier information by a user terminal according to Embodiment 2 of the present invention
- FIG. 4 is a flowchart of acquiring user server identifier information by a user terminal according to Embodiment 3 of the present invention
- FIG. 5 is a flowchart of the identification information of the application server obtained by the user terminal to the centralized server according to the third embodiment of the present invention
- FIG. 6 is a flowchart of acquiring application server identification information by a user terminal according to Embodiment 4 of the present invention
- FIG. 7 is a system block diagram for acquiring application server identification information according to an embodiment of the present invention
- FIG. 8 is a second embodiment of the present invention.
- the first device sends an identification request to the second device; the second device returns the identification information of the target application server to the first device.
- the user terminal that is the first device obtains the target application server identification information by sending an identifier request to the application server corresponding to the application type that is requested by the application server, in this embodiment, in the embodiment, the target application The server acts as the second device.
- the process for the user terminal to obtain the application server identification information is as shown in FIG. 1, and includes the following steps:
- Step S101 The user terminal sends an identifier request message to the application server proxy, where the identifier request message carries information of an application type corresponding to the application.
- Step S102 After receiving the identifier request message, the application server proxy forwards the identifier request message to the application server corresponding to the application type, that is, the target application server, according to the information of the application type carried in the identifier request message;
- the application server proxy may proxy the application server corresponding to the different application type, and after receiving the identifier request message, the application server proxy may determine the application server corresponding to the application type according to the information of the application type carried in the identifier request message, and The identifier request message is forwarded to an application server corresponding to the application type.
- Step S103 The target application server returns an identifier request response message to the application server proxy, where the response message carries the identifier information of the target application server.
- Step S104 The application server agent forwards the response message to the user terminal.
- Step S105 After receiving the response message, the user terminal parses and saves the identifier information of the application server.
- the foregoing process may also be performed when the user terminal initiates the first service request after the application is started.
- the identifier request message may be the service request message or an independent identifier request message.
- the user terminal After obtaining the application server identifier information, the user terminal may be used as the correct identifier information of the application server corresponding to the application type requested by the user terminal, or may obtain the application server to ensure the correctness of the application server identifier information obtained by the user terminal. After the identification information, confirm to the target application server whether the identification information is correct.
- the process for the user terminal to confirm the identification information of the application server obtained by the user terminal to the target application server is as shown in FIG. 2, and includes the following steps:
- Step S201 The user terminal sends an acknowledgement request message to the application server proxy, where the acknowledgement request message carries the identifier information of the application server parsed by the user terminal and the application type information corresponding to the application;
- Step S202 After receiving the confirmation request message, the application server agent forwards the confirmation request message to the target application server according to the information of the application type carried in the confirmation request message.
- Step S203 after receiving the confirmation request message, the target application server parses and determines whether the identification information carried in the confirmation request message is the identification information of the application server, and if yes, proceeds to step S207; otherwise, proceeds to step S204;
- Step S204 The target application server returns a conflict response to the application server proxy, where the conflicting response carries the identifier information of the application server.
- Step S205 The application server proxy forwards the conflict response to the user terminal.
- Step S206 The user terminal parses and saves the identifier information of the application server carried in the conflict response, and resends the confirmation request message to the application server proxy, where the confirmation request message carries the identifier information of the application server parsed by the user terminal and the application. Information about the application type corresponding to the program, Returning to step S202;
- Step S207 The target application server returns a correct response to the application server proxy.
- Step S208 The application server proxy forwards the correct response to the user terminal.
- Step S209 The user terminal uses the currently saved identification information of the application server as the identification information of the target application server.
- the user terminal will continuously send a confirmation request to the application server.
- the number of times the user terminal initiates the confirmation request may be limited, for example, 3 times, if the user The terminal sends the acknowledgment request to the application server three times, and the correct response is not obtained.
- the user terminal can consider that the application server proxy, the application server, or the network transmission error occurs at this time, and can temporarily suspend the identification information to the target application server, or directly It is considered that the application server identification information saved locally is correct.
- the conflicting response may not carry the identifier information of the application server, and the conflict response is only used to notify the user terminal that the identifier information of the application server carried in the confirmation request message is incorrect, and the confirmation process is not looped. Ends after the terminal receives a conflict response or a correct response. After the user terminal knows whether the identification information of the application server carried in the confirmation request message is correct, the user terminal may determine whether to send the identification request to the target application server to obtain the identification information again according to the requirement.
- the user terminal as the first device when acquiring the target application server identification information as the second device, carries the application server identification information suggested by the user terminal in its identification request message.
- the process for the user terminal to obtain the application server identification information in this embodiment is as shown in FIG. 3, and includes the following steps:
- Step S301 The user terminal sends an identifier request message to the application server proxy, where the identifier request message carries the information of the application type corresponding to the application and the application server identifier information suggested by the user terminal;
- the suggested application server identifier information such as sip: [email protected], can It is the identification information of the application server obtained by the user terminal when the application is last run or the identification information of the initial application server of the user terminal.
- the identification information of the initial application server may be automatically generated by the user terminal.
- Step S302 After receiving the identifier request message, the application server proxy forwards the identifier request message to the application server corresponding to the application type, that is, the target application server;
- Step S303 After receiving the identifier request message, the target application server parses and determines whether the application server identifier information recommended by the terminal carried in the identifier request message is the identifier information of the target application server, and if yes, proceeds to step S307; otherwise, Going to step S304;
- the target application server determines whether the identifier information of the target application server is carried in the identifier request message.
- the judgment method whether the identification request carries the identification information of the application server suggested by the terminal, the judgment can be made.
- the target application server identifier information is sip: [email protected]
- the application server identifier information recommended by the user terminal carried in the identifier request message received by the application server is sip:[email protected]
- the application is The server can determine that the parsed identification information is inconsistent with the identification information of the application server, that is, the identification information carried in the identifier request message is not the identification information of the application server.
- Step S304 the target application server returns the identifier information of the target application server to the application server proxy.
- Step S305 The application server proxy forwards the identifier information to the user terminal.
- Step S306 the user terminal receives and saves the identifier information, and ends.
- Step S307 The target application server returns a correct response to the application server proxy.
- Step S308 the application server proxy forwards the correct response to the user terminal.
- Step S309 the user terminal uses the recommended application server identification information as the identification information of the target application server.
- the target application server may return to the terminal. It is correct response, for example, the target application server returns identification information that may be the target application server to the terminal.
- the focus of the process is that when the application server identifier information recommended by the terminal in the identifier request message is not the identifier information of the target application server, the target application server needs to return the identifier information of the target application server to the terminal.
- the user terminal After receiving the identification information of the target application server, the user terminal can use it as the identification information of the correct target application server, and can also confirm the correctness of the identification information to the target application server, and receive the correct response of the target application server. Then, the identification information of the application server is used as the identification information of the correct target application server.
- the process of the user terminal confirming the identification information of the application server obtained by the user terminal to the application server may be the same as that in the first embodiment.
- the operator maintains a centralized server as the second device, where the mapping table indicating the mapping relationship between the application type information and the application server identification information is saved, and the user terminal as the first device can obtain the application from the centralized server.
- Server identification information The process for the user terminal to obtain the application server identification information is as shown in FIG. 4, and includes the following steps:
- Step S401 The user terminal sends an identifier request message to the proxy device, where the identifier request message carries information of an application type corresponding to the application.
- Step S402 After receiving the identifier request message, the proxy device forwards the identifier request message to the centralized server.
- Step S403 After receiving the identifier request message, the centralized server parses the information of the application type carried therein, and searches the mapping table to obtain the identifier information of the application server corresponding to the information of the application type.
- Step S404 The centralized server returns an identifier request response message to the proxy device, where the response message carries the identifier information of the application server.
- Step S405 The proxy device forwards the response message to the user terminal.
- Step S406 After receiving the response message, the user terminal parses and saves the identifier information of the application server.
- the function of the proxy device is only the forwarding identifier request message and the identifier request response message. Therefore, in a specific implementation, the proxy device may not exist.
- the user terminal may be used as the correct identifier information of the application server corresponding to the application type requested by the user terminal, or may confirm the application server identifier to the centralized server to ensure the application server identifier information obtained by the user terminal.
- the correctness of the method of confirmation is shown in Figure 5, including the following steps:
- Step S501 The user terminal sends an acknowledgement request message to the proxy device, where the acknowledgement request message carries the identifier information of the application server received by the user terminal and the information about the application type corresponding to the application;
- Step S502 After receiving the confirmation request message, the proxy device forwards the confirmation request message to the centralized server.
- Step S503 After receiving the confirmation request message, the centralized server parses and determines whether the information of the application type carried in the application and the identification information of the application server are consistent with those recorded in the mapping table. If yes, go to step S507; otherwise, go to step S504. ;
- Step S504 The centralized server returns a conflict response to the proxy device, where the conflict response carries the identifier information of the target application server.
- the centralized server learns the identification information of the target application server by searching the mapping table according to the information of the application type.
- Step S505 The proxy device forwards the conflict response to the user terminal.
- Step S506 After receiving the conflict response, the user terminal parses and saves the identifier information of the application server, and resends the confirmation request message to the proxy device, where the confirmation request message carries the identifier information of the application server parsed by the user terminal, and the The information of the application type corresponding to the application returns to step S502;
- Step S507 The centralized server returns a correct response to the proxy device.
- Step S508 the proxy device forwards the correct response to the user terminal.
- Step S509 the user terminal uses the recommended application server identification information as the target application server. Identification information.
- the number of times the user terminal initiates the confirmation request may also be limited.
- the user terminal that is the first device obtains the identification information of the target application server from the centralized server that is the second device, and when the target application server identification information is acquired, the user request is carried in the identification request message.
- Application server identification information The process for the user terminal to obtain the application server identification information in this embodiment is as shown in FIG. 6, and includes the following steps:
- Step S601 The user terminal sends an identifier request message to the proxy device, where the identifier request message carries the information of the application type corresponding to the application and the application server identifier information suggested by the user terminal;
- Step S602 After receiving the identifier request message, the proxy device forwards the identifier request message to the centralized server.
- Step S603 After receiving the identifier request message, the centralized server parses and determines whether the application server identifier information and the application type information recommended by the terminal carried in the identifier request message are consistent with those recorded in the mapping table, and if yes, perform the steps. S607, otherwise, proceeding to step S604;
- Step S604 The centralized server returns the identification information of the target application server to the proxy device.
- the centralized server obtains the identification information of the target application server by searching the mapping table according to the information of the application type.
- Step S605 The proxy device forwards the identifier information to the user terminal.
- Step S606 The user terminal receives and saves the identifier information of the application server, and ends.
- Step S607 The centralized server returns a correct response to the proxy device.
- Step S608 The proxy device forwards the correct response to the user terminal.
- Step S609 The user terminal uses the recommended application server identification information as the identification information of the target application server.
- the user terminal may identify the identifier of the application server carried therein.
- the application server identifier may be confirmed to the centralized server to ensure the correctness of the application server identification information obtained by the user terminal, and the confirmation method may be the same as in the third embodiment.
- the confirmation method is the same.
- a system for acquiring application server identification information is as shown in FIG. 7, and includes a first device 100 and a second device 300, where:
- the first device 100 includes an identification requesting module 101 for transmitting an identification request to the second device 300.
- the second device 300 includes a processing module 301 for returning the target application server identification information to the first device 100.
- the system can also include a proxy device 200 for forwarding the identification request and the identification information of the application server between the first device 100 and the second device 300.
- the first device 100 includes:
- a program running module 102 configured to run an application
- the identifier requesting module 101 sends an identifier request according to the application running by the program running module 102.
- the first receiving module 103 is configured to receive the application server identifier information.
- the first storage module 104 is configured to save the application server identification information received by the first receiving module 103.
- the identifier requesting module 101 may obtain the saved application server identifier information from the first storage module 104, and carry it in the identifier request.
- the application server identification information may be obtained from the first storage module 104.
- the first device 100 may confirm to the application server whether the identification information is correct. Therefore, in this embodiment, the first The device 100 further includes an acknowledgment request module 105, configured to send a confirmation request to the second device 300 after the first receiving module 103 receives the identification information.
- the second device 300 includes:
- the second receiving module 302 is configured to receive information.
- the processing module 301 is configured to send the identifier information of the target application server according to the identifier request received by the second receiving module 302.
- the second device 300 may further determine whether the target application server identifier information is carried in the identifier request that is received by the second device 300 to determine whether to return the target application server identifier information to the first device 100. Therefore, in this embodiment, the second device 300 further The first determining module 303 is configured to determine whether the target application server identifier information is carried in the identifier request received by the second receiving module 302. When the identifier request does not carry the target application server identifier information, the notification processing module 301 sends the target application server. Identification information.
- the second device 300 in this embodiment may further include a second determination module 304 and a confirmation module 305, where:
- the second judging module 304 is configured to determine whether the acknowledgment request received by the second receiving module 302 carries the target application server identification information, and notifies the confirmation module 305;
- the confirmation module 305 sends a conflict response, otherwise, the confirmation module 305 sends a correct response.
- the second device 300 may be a target application server or a centralized server.
- the second device 300 may be as shown in FIG.
- the second storage module 306 is configured to save a mapping table that identifies a mapping relationship between the application type information and the application server identification information.
- the searching module 307 is configured to: according to the identifier request lookup mapping table received by the second receiving module 302, obtain and output the identifier information of the target application server.
- the processing module 301, the first determining module 303, the second determining module 304, and the confirming module 305 can all know the target application server identification information from the searching module 307.
- the first device sends an identifier request to the second device; the second device returns the identifier information of the target application server to the first device.
- the technology provided by the embodiment of the present invention is used.
- the first device sends the identification request to the second device, and the target application server identification information is automatically obtained, so that the user does not need to manually input the complicated and difficult application server identification information when experiencing the service that needs to provide the corresponding application server identification information. , to improve user experience satisfaction.
- the spirit and scope of the Ming Thus, it is intended that the present invention cover the modifications and the modifications of the invention
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Transfer Between Computers (AREA)
Description
获取应用服务器标识信息的方法、 终端、 设备和*** 技术领域
本发明涉及网络通信技术领域, 尤其涉及获取应用服务器标识信息的方法、 终端、 设备和***。 背景技术
IMS ( Internet protocol Multimedia Subsystem, 因特网协议多媒体子***) 作为下一代融合网络, 以业务创新为驱动, 使运营商能快速高效地部署各种融 合多媒体业务; 在终端用户体验某些多媒体业务的时候, 需要终端用户填写应 用服务器的标识信息, 例如, 用户在开展 PoC ( PTT over Cellular, —键通)业 务、 Message (消息)业务和 Conference (会议) 业务的时候均需要提供相应应 用服务器的标识信息。
目前, 终端用户在体验某种需要提供相应服务器标识信息的业务时, 往往 从运营商提供的网站上通过 PortaK门户网站)获取相应应用服务器的标识信息, 然后手工输入相应应用服务器的标识信息作为程序运行时的一个配置信息。
发明人在实现本发明时发现, 釆用上述技术方案获取应用服务器的标识信 息后, 需要由终端用户手工输入应用服务器的标识信息, 这会令终端用户感觉 不方便。 且由于应用服务器标识信息的格式专业化程度相当高, 例如: sip:[email protected], 这将使得终端用户对该格式不易理解, 从而导致 终端用户要准确地输入应用服务器的标识信息是存在困难的, 这将令终端用户 感觉更加地不方便。 并且, 如果应用服务器的标识信息发生变更, 则终端就不 能正确体验该多媒体业务, 此时就需要用户重新从运营商提供的网站上通过 Portal获取相应应用服务器的标识信息, 然后再次手工输入相应应用服务器的标 识信息作为程序运行时的一个配置信息, 这对于终端用户来说是极其麻烦的, 终端用户的体验很差。 发明内容
本发明提供获取应用服务器标识信息的方法、 终端、 设备和***, 用以解 决现有技术中存在终端无法自动获取目标应用服务器标识信息的问题。
为了解决上述技术问题, 本发明提供了一种获取应用服务器标识信息的方 法, 包括以下步骤:
第一设备向第二设备发送标识请求;
第二设备向第一设备返回目标应用服务器的标识信息。
本发明还提供了一种获取应用服务器标识信息的***, 包括第一设备和第 二设备,
所述第一设备包括标识请求模块, 用于向所述第二设备发送标识请求; 所述第二设备包括处理模块, 用于向所述第一设备返回目标应用服务器的 标识信息。
本发明还提供了一种终端, 包括用于运行应用程序的模块, 所述终端还包 括标识请求模块, 用于根据所述应用程序发送标识请求。
本发明还提供了一种设备, 包括用于接收信息的第二接收模块, 所述设备 还包括处理模块, 用于根据所述第二接收模块接收到的标识请求发送目标应用 服务器的标识信息。
在本发明中, 第一设备通过向第二设备发送标识请求, 可以自动获取目标 应用服务器标识信息, 使得用户在体验需要提供相应应用服务器标识信息的业 务时, 不需要手工输入复杂难懂的应用服务器标识信息, 使用户的体验满意度 提高。 附图说明
图 1为本发明实施例一中用户终端获取应用服务器标识信息的流程图; 图 2 为本发明实施例一中用户终端向目标应用服务器确认其获得的应用服 务器的标识信息的流程图;
图 3为本发明实施例二中用户终端获取应用服务器标识信息的流程图; 图 4为本发明实施例三中用户终端获取应用服务器标识信息的流程图;
图 5 为本发明实施例三中用户终端向集中服务器确认其获得的应用服务器 的标识信息的流程图;
图 6为本发明实施例四中用户终端获取应用服务器标识信息的流程图; 图 7为本发明一个实施例中获取应用服务器标识信息的***框图; 图 8为本发明一个实施例中作为第二设备的集中服务器的示意框图。 具体实施方式
在本发明中, 第一设备向第二设备发送标识请求; 第二设备向第一设备返 回目标应用服务器的标识信息。
下面结合附图和实施例对本发明作进一步地说明。
实施例一
本实施例中, 作为第一设备的用户终端通过向其请求的应用类型所对应的 应用服务器, 即目标应用服务器, 发送标识请求来获取目标应用服务器标识信 息, 在本实施例中, 该目标应用服务器作为第二设备。 当用户开启一个需要相 应应用服务器的标识信息才能正确实现的应用程序时, 用户终端获取应用服务 器标识信息的流程如图 1所示, 包括以下步骤:
步骤 S101 , 用户终端发送标识请求消息给应用服务器代理, 该标识请求消 息中携带该应用程序对应的应用类型的信息;
步骤 S102, 应用服务器代理接收到该标识请求消息后, 根据该标识请求消 息中携带的应用类型的信息将该标识请求消息转发给该应用类型对应的应用服 务器, 即目标应用服务器;
应用服务器代理可以代理对应于不同应用类型的应用服务器, 当应用服务 器代理接收到该标识请求消息后, 可以根据该标识请求消息中携带的应用类型 的信息确定该应用类型对应的应用服务器, 并将该标识请求消息转发给该应用 类型对应的应用服务器。
步骤 S103 ,目标应用服务器向应用服务器代理返回一个标识请求响应消息, 该响应消息中携带目标应用服务器的标识信息;
步骤 S104 , 应用服务器代理将该响应消息转发给该用户终端; 步骤 S105 , 用户终端接收到该响应消息后, 解析并保存该应用服务器的标 识信息。
上述流程也可以在该应用程序开启后, 用户终端发起第一次业务请求时进 行, 在这种情况下, 上述标识请求消息可以是该次业务请求消息, 也可以是独 立的标识请求消息。 在用户终端获得该应用服务器的标识信息后, 在进行后续 的业务时, 可以直接与该应用服务器进行交互。
用户终端在获得应用服务器标识信息后, 可以将其作为用户终端所请求的 应用类型对应的应用服务器正确的标识信息, 也可以为了确保用户终端获得的 应用服务器标识信息的正确性, 在获得应用服务器的标识信息后, 向目标应用 服务器确认该标识信息是否正确。 本实施例中, 用户终端向目标应用服务器确 认其获得的应用服务器的标识信息的流程如图 2所示, 包括以下步骤:
步骤 S201 , 用户终端向应用服务器代理发送确认请求消息, 该确认请求消 息中携带用户终端解析出的应用服务器的标识信息以及该应用程序对应的应用 类型的信息;
步骤 S202 , 应用服务器代理接收到该确认请求消息后, 根据该确认请求消 息中携带的应用类型的信息将该确认请求消息转发给目标应用服务器;
步骤 S203 , 目标应用服务器接收到该确认请求消息后, 解析并判断该确认 请求消息中携带的是否是该应用服务器的标识信息, 如果是, 进行步骤 S207; 否则进行步骤 S204;
步骤 S204 , 目标应用服务器向应用服务器代理返回冲突响应, 在该冲突响 应中携带该应用服务器的标识信息;
步骤 S205 , 应用服务器代理向用户终端转发该冲突响应;
步骤 S206 , 用户终端解析并保存该冲突响应中携带的应用服务器的标识信 息, 并向应用服务器代理重新发送确认请求消息, 该确认请求消息中携带用户 终端解析出的应用服务器的标识信息以及该应用程序对应的应用类型的信息,
返回步骤 S202;
步骤 S207 , 目标应用服务器向应用服务器代理返回正确响应;
步骤 S208, 应用服务器代理向用户终端转发该正确响应;
步骤 S209, 用户终端将当前保存的应用服务器的标识信息作为目标应用服 务器的标识信息。
根据上述确认流程, 如果目标应用服务器不向用户终端返回正确响应, 用 户终端将不断地向应用服务器发送确认请求, 在具体实现时, 可以限定用户终 端发起确认请求的次数, 如 3次, 如果用户终端向应用服务器发送了 3次确认 请求, 还得不到正确响应, 则用户终端可以认为此时应用服务器代理、 应用服 务器或者网络传输出错, 可以进行暂停向目标应用服务器请求其标识信息, 或 者直接认为此时本地保存的应用服务器标识信息为正确等操作。
在具体实现时, 该冲突响应中可以不携带应用服务器的标识信息, 则冲突 响应只用于通知用户终端其确认请求消息中携带的应用服务器的标识信息不正 确 , 而确认流程也不进行循环且在终端接收到冲突响应或者正确响应后结束。 在用户终端获知其确认请求消息中携带的应用服务器的标识信息是否正确后, 用户终端可以根据需要确定是否再次向目标应用服务器发送标识请求来获取其 标识信息。
实施例二
本实施例中, 作为第一设备的用户终端在获取作为第二设备的目标应用服 务器标识信息时, 在其标识请求消息中携带用户终端建议的应用服务器标识信 息。 则本实施例中用户终端获取应用服务器标识信息的流程如图 3 所示, 包括 以下步骤:
步骤 S301 , 用户终端发送标识请求消息给应用服务器代理, 该标识请求消 息中携带该应用程序对应的应用类型的信息以及用户终端建议的应用服务器标 识信息;
该建议的应用月良务器标识信息, 例如 sip: [email protected], 可以
是用户终端保存的上一次运行该应用程序时获得的应用服务器的标识信息或者 用户终端初始的应用服务器的标识信息, 该初始的应用服务器的标识信息可以 是用户终端自动生成的。
步骤 S302, 应用服务器代理接收到该标识请求消息后, 将该标识请求消息 转发给该应用类型对应的应用服务器, 即目标应用服务器;
步骤 S303 , 目标应用服务器接收到该标识请求消息后, 解析并判断该标识 请求消息中携带的该终端建议的应用服务器标识信息是否是该目标应用服务器 的标识信息, 如果是, 进行步骤 S307 , 否则, 进行步骤 S304;
在本步骤中, 目标应用服务器判断的可以是, 该标识请求消息中是否携带 了该目标应用服务器的标识信息。 釆用这种判断方式时, 不论该标识请求中是 否携带终端建议的应用服务器的标识信息, 都可以进行判断。
在一个实例中 , 目标应用服务器标识信息为 sip: [email protected], 而应用服务器接收到的标识请求消息中携带的用户终端建议的应用服务器标识 信息为 sip:[email protected],则应用月良务器可以判断出该解析出的标识 信息与该应用服务器的标识信息不一致, 即该标识请求消息中携带的不是该应 用服务器的标识信息。
步骤 S304, 目标应用服务器向应用服务器代理返回目标应用服务器的标识 信息;
步骤 S305 , 应用服务器代理将该标识信息转发给该用户终端;
步骤 S306, 用户终端接收并保存该标识信息, 结束;
步骤 S307 , 目标应用服务器向应用服务器代理返回正确响应;
步骤 S308, 应用服务器代理向用户终端转发该正确响应。
步骤 S309, 用户终端将其建议的应用服务器标识信息作为目标应用服务器 的标识信息。
在本实施例中, 当该标识请求消息中携带的该终端建议的应用服务器标识 信息是该目标应用服务器的标识信息时, 目标应用服务器向终端返回的可以不
是正确响应, 例如目标应用服务器向终端返回可以是目标应用服务器的标识信 息。 本流程中的重点是当该标识请求消息中携带的该终端建议的应用服务器标 识信息不是该目标应用服务器的标识信息时, 目标应用服务器需要向终端返回 目标应用服务器的标识信息。
用户终端在接收到目标应用服务器的标识信息后, 可以将其作为正确的目 标应用服务器的标识信息, 也可以再向目标应用服务器确认该标识信息的正确 性, 在接收到目标应用服务器的正确响应后, 再将该应用服务器的标识信息作 为正确的目标应用服务器的标识信息。 在本实施例中, 用户终端向应用服务器 确认其获得的应用服务器的标识信息的流程可以和实施例一相同。
实施例三
本实施例中, 运营商维护一个集中服务器作为第二设备, 其中保存了标明 应用类型的信息和应用服务器标识信息间映射关系的映射表, 作为第一设备的 用户终端可以从该集中服务器获取应用服务器标识信息。 用户终端获取应用服 务器标识信息的流程如图 4所示, 包括以下步骤:
步骤 S401 , 用户终端发送标识请求消息给代理设备, 该标识请求消息中携 带该应用程序对应的应用类型的信息;
步骤 S402 , 代理设备接收到该标识请求消息后, 将该标识请求消息转发给 集中服务器;
步骤 S403 , 集中服务器接收到该标识请求消息后, 解析出其中携带的应用 类型的信息, 查找映射表, 获得该应用类型的信息对应的应用服务器的标识信 息;
步骤 S404 , 集中服务器向代理设备返回一个标识请求响应消息, 该响应消 息中携带应用服务器的标识信息;
步骤 S405 , 代理设备将该响应消息转发给该用户终端;
步骤 S406 , 用户终端接收到该响应消息后, 解析并保存该应用服务器的标 识信息。
在本实施例中, 代理设备的功能仅仅是转发标识请求消息和标识请求响应 消息, 因此, 在具体实现时, 可以不存在该代理设备。
用户终端在获得应用服务器标识信息后, 可以将其作为用户终端所请求的 应用类型对应的应用服务器正确的标识信息, 也可以向集中服务器确认该应用 服务器标识从而确保用户终端获得的应用服务器标识信息的正确性, 该确认方 法的流程如图 5所示, 包括以下步骤:
步骤 S501 , 用户终端发送确认请求消息给代理设备, 该确认请求消息中携 带用户终端接收到的应用服务器的标识信息以及该应用程序对应的应用类型的 信息;
步骤 S502 , 代理设备接收到该确认请求消息后, 将该确认请求消息转发给 集中服务器;
步骤 S503 , 集中服务器接收到该确认请求消息后, 解析并判断其中携带的 应用类型的信息和应用服务器的标识信息是否和映射表中记录的一致, 如果是, 进行步骤 S507 , 否则, 进行步骤 S504;
步骤 S504 , 集中服务器向代理设备返回冲突响应, 该冲突响应中携带目标 应用服务器的标识信息;
集中服务器通过根据应用类型的信息查找映射表来获知目标应用服务器的 标识信息。
步骤 S505 , 代理设备将该冲突响应转发给该用户终端;
步骤 S506 , 用户终端接收到该冲突响应后, 解析并保存该应用服务器的标 识信息, 并向代理设备重新发送确认请求消息, 该确认请求消息中携带用户终 端解析出的应用服务器的标识信息以及该应用程序对应的应用类型的信息, 返 回步骤 S502;
步骤 S507 , 集中服务器向代理设备返回正确响应;
步骤 S508 , 代理设备向用户终端转发该正确响应;
步骤 S509 , 用户终端将其建议的应用服务器标识信息作为目标应用服务器
的标识信息。
与实施例一类似, 在本实施例中, 也可以限定用户终端发起确认请求的次 数。
实施例四
本实施例中, 作为第一设备的用户终端从作为第二设备的集中服务器获取 目标应用服务器的标识信息, 并且, 在获取目标应用服务器标识信息时, 在其 标识请求消息中携带用户终端建议的应用服务器标识信息。 则本实施例中用户 终端获取应用服务器标识信息的流程如图 6所示, 包括以下步骤:
步骤 S601 , 用户终端发送标识请求消息给代理设备, 该标识请求消息中携 带该应用程序对应的应用类型的信息以及用户终端建议的应用服务器标识信 息;
步骤 S602 , 代理设备接收到该标识请求消息后, 将该标识请求消息转发给 集中服务器;
步骤 S603 , 集中服务器接收到该标识请求消息后, 解析并判断该标识请求 消息中携带的该终端建议的应用服务器标识信息和应用类型的信息是否和映射 表中记录的一致, 如果是, 进行步骤 S607 , 否则, 进行步骤 S604;
步骤 S604 , 集中服务器向代理设备返回目标应用服务器的标识信息; 集中服务器通过根据应用类型的信息查找映射表来获知目标应用服务器的 标识信息。
步骤 S605 , 代理设备将该标识信息转发给该用户终端;
步骤 S606 , 用户终端接收并保存该应用服务器的标识信息, 结束; 步骤 S607 , 集中服务器向代理设备返回正确响应;
步骤 S608 , 代理设备向用户终端转发该正确响应;
步骤 S609 , 用户终端将其建议的应用服务器标识信息作为目标应用服务器 的标识信息。
用户终端在接收到冲突响应后, 可以将其中携带的应用服务器的标识信息
作为其所请求的应用类型对应的应用服务器正确的标识信息, 也可以向集中服 务器确认该应用服务器标识从而确保用户终端获得的应用服务器标识信息的正 确性, 该确认方法可以与实施例三中的确认方法相同。
在本发明的一个实施例中, 获取应用服务器标识信息的***如图 7 所示, 包括第一设备 100和第二设备 300 , 其中:
第一设备 100包括标识请求模块 101 , 用于向第二设备 300发送标识请求; 第二设备 300包括处理模块 301 ,用于向第一设备 100返回目标应用服务器 标识信息。
该***还可以包括代理设备 200,用于在第一设备 100和第二设备 300之间 转发标识请求和应用服务器的标识信息。
其中, 第一设备 100包括:
程序运行模块 102, 用于运行应用程序;
标识请求模块 101 , 根据程序运行模块 102运行的应用程序发送标识请求; 第一接收模块 103 , 用于接收应用服务器标识信息;
第一存储模块 104,用于保存第一接收模块 103接收到的应用服务器标识信 息。
在具体实施时, 标识请求模块 101 可以从第一存储模块 104获取其保存的 应用服务器标识信息, 携带在标识请求中发送。
当程序运行模块 102需要体验某业务时, 可以从第一存储模块 104中获取 应用服务器标识信息。
为了确保第一设备 100获得的应用服务器标识信息的正确性, 在获得应用 服务器的标识信息后, 第一设备 100可以向应用服务器确认该标识信息是否正 确, 因此, 在本实施例中, 第一设备 100还包括确认请求模块 105 , 用于在第一 接收模块 103接收到标识信息后, 向第二设备 300发送确认请求。
第二设备 300包括:
第二接收模块 302, 用于接收信息;
处理模块 301,用于根据第二接收模块 302接收到的标识请求发送目标应用 服务器的标识信息。
由于第二设备 300可以先判断其接收到的标识请求中是否携带目标应用服 务器标识信息来决定是否向第一设备 100返回目标应用服务器标识信息, 因此, 在本实施例中, 第二设备 300还包括第一判断模块 303 , 用于判断第二接收模块 302接收到的标识请求中是否携带目标应用服务器标识信息,当标识请求中没有 携带目标应用服务器标识信息时, 通知处理模块 301 发送目标应用服务器的标 识信息。
对应于第一设备 100的确认请求模块 105 ,本实施例中的第二设备 300还可 以包括第二判断模块 304和确认模块 305 , 其中:
第二判断模块 304 ,用于判断第二接收模块 302接收到的确认请求中是否携 带目标应用服务器标识信息, 并通知确认模块 305;
当该通知为确认请求中没有携带目标应用服务器标识信息时,确认模块 305 发送冲突响应, 否则, 确认模块 305发送正确响应。
在具体实现时, 上述第二设备 300 可以是目标应用服务器, 也可以是集中 服务器, 当第二设备 300为集中服务器时, 第二设备可以如图 8所示, 还应当 包括:
第二存储模块 306 ,用于保存标识应用类型的信息和应用服务器标识信息间 映射关系的映射表;
查找模块 307 , 用于根据第二接收模块 302接收到的标识请求查找映射表, 获取并输出目标应用服务器的标识信息。
当第二设备 300是集中服务器时, 其处理模块 301、 第一判断模块 303、 第 二判断模块 304和确认模块 305都可以从查找模块 307获知目标应用服务器标 识信息。
综上所述, 本发明实施例中, 第一设备向第二设备发送标识请求; 第二设 备向第一设备返回目标应用服务器的标识信息。 釆用本发明实施例提供的技术
方案, 第一设备通过向第二设备发送标识请求, 可以自动获取目标应用服务器 标识信息, 使得用户在体验需要提供相应应用服务器标识信息的业务时, 不需 要手工输入复杂难懂的应用服务器标识信息, 使用户的体验满意度提高。 明的精神和范围。 这样, 倘若对本发明的这些修改和变型属于本发明权利要求 及其等同技术的范围之内, 则本发明也意图包含这些改动和变型在内。
Claims
1、 一种获取应用服务器标识信息的方法, 其特征在于, 包括以下步骤: 第一设备向第二设备发送标识请求;
第二设备向第一设备返回目标应用服务器的标识信息。
2、 如权利要求 1所述的方法, 其特征在于, 所述标识请求中携带第一设备 建议的应用服务器的标识信息;
第二设备接收到所述标识请求后, 先判断所述建议的标识信息是否为所述 目标应用服务器的标识信息, 当所述建议的标识信息不是所述目标应用服务器 的标识信息时, 向第一设备返回所述目标应用服务器的标识信息;
第一设备接收并保存所述目标应用服务器的标识信息。
3、 如权利要求 2所述的方法, 其特征在于, 所述建议的标识信息为第一设 备本地保存的或者其初始的应用服务器的标识信息。
4、 如权利要求 1所述的方法, 其特征在于, 第二设备接收到所述标识请求 后, 直接向第一设备返回目标应用服务器的标识信息。
5、 如权利要求 1、 2或 4所述的方法, 其特征在于, 第一设备接收到所述 标识信息后, 向第二设备发送确认请求, 所述确认请求中携带所述接收到的标 识信息;
第二设备判断所述确认请求中携带的标识信息是否正确, 如果是, 向第一 设备返回正确响应, 否则向第一设备返回冲突响应。
6、 如权利要求 5所述的方法, 其特征在于, 所述冲突响应中携带目标应用 服务器的标识信息, 第一设备接收到所述冲突响应后, 解析并保存所述标识信 息, 并重新向第二设备发送确认请求。
7、 如权利要求 1或 2所述的方法, 其特征在于, 所述标识请求中携带第一 设备所请求的应用类型的信息。
8、 如权利要求 7所述的方法, 其特征在于, 第一设备和第二设备之间通过 代理设备转发所述标识请求和所述应用服务器的标识信息。
9、 如权利要求 8所述的方法, 其特征在于, 所述代理设备根据所述标识请 求中携带的应用类型的信息将所述请求转发给第二设备, 所述第二设备为所述 应用类型对应的目标应用服务器。
10、 如权利要求 7 所述的方法, 其特征在于, 所述第二设备本地保存了应 用类型的信息和应用服务器标识信息间的映射关系;
所述第二设备接收到所述标识请求后, 根据所述应用类型的信息及所述映 射关系获知所述目标应用服务器的标识信息。
11、 一种获取应用服务器标识信息的***, 包括第一设备和第二设备, 其 特征在于,
所述第一设备包括标识请求模块, 用于向所述第二设备发送标识请求; 所述第二设备包括处理模块, 用于向所述第一设备返回目标应用服务器的 标识信息。
12、 如权利要求 11所述的***, 其特征在于, 所述第二设备还包括第一判 断模块, 用于判断所述标识请求中是否携带所述目标应用服务器标识信息, 当 所述标识请求中没有携带所述目标应用服务器标识信息时, 通知所述处理模块 向第一设备返回目标应用服务器标识信息。
13、 如权利要求 11所述的***, 其特征在于, 所述第一设备还包括: 第一接收模块, 用于接收所述第二设备返回的应用服务器标识信息; 第一存储模块, 用于保存所述第一接收模块接收到的应用服务器标识信息。
14、 如权利要求 13所述的***, 其特征在于, 所述第一设备还包括确认请 求模块, 用于在所述第一接收模块接收到所述标识信息后, 向第二设备发送确 认请求。
15、 如权利要求 14所述的***, 其特征在于, 所述第二设备还包括第二判 断模块和确认模块, 其中: 器标识信息, 并通知所述确认模块;
当所述通知为所述确认请求中没有携带所述目标应用服务器标识信息时, 所述确认模块向所述第一设备发送冲突响应, 否则, 所述确认模块向所述第一 设备发送正确响应。
16、 如权利要求 11所述的***, 其特征在于, 所述***还包括代理设备, 用于在所述第一设备和所述第二设备之间转发所述标识请求和所述应用服务器 的标识信息。
17、 如权利要求 16所述的***, 其特征在于, 所述第二设备为所述目标应 用服务器;
所述标识请求模块将对应所述目标应用服务器的应用类型的信息携带在所 述标识请求中发送给所述代理设备, 所述代理设备根据所述应用类型的信息将 所述请求转发给所述第二设备。
18、 如权利要求 11或 16所述的***, 其特征在于, 所述第二设备还包括: 第二存储模块, 用于保存标识应用类型的信息和应用服务器标识信息间映 射关系的映射表;
查找模块, 用于根据所述标识请求查找所述映射表, 获取并输出所述目标 应用服务器的标识信息。
19、 一种终端, 包括用于运行应用程序的模块, 其特征在于, 所述终端还 包括标识请求模块, 用于根据所述应用程序发送标识请求。
20、 如权利要求 19所述的终端, 其特征在于, 所述终端还包括:
第一接收模块, 用于接收应用服务器的标识信息;
第一存储模块, 用于保存所述第一接收模块接收到的应用服务器标识信息。
21、 如权利要求 20所述的终端, 其特征在于, 所述终端还包括确认请求模 块, 用于在所述第一接收模块接收到所述标识信息后, 发送确认请求。
22、 一种设备, 包括用于接收信息的第二接收模块, 其特征在于, 所述设 备还包括处理模块, 用于根据所述第二接收模块接收到的标识请求发送目标应 用服务器的标识信息。
23、 如权利要求 22所述的设备, 其特征在于, 所述设备还包括第一判断模 块, 用于判断所述第二接收模块接收到的标识请求中是否携带所述目标应用服 务器标识信息, 当所述标识请求中没有携带所述目标应用服务器标识信息时, 通知所述处理模块发送目标应用服务器的标识信息。
24、 如权利要求 22所述的设备, 其特征在于, 所述设备还包括第二判断模 块和确认模块, 其中:
所述第二判断模块, 用于判断所述第二接收模块接收到的确认请求中是否 携带所述目标应用服务器的标识信息, 并通知所述确认模块;
当所述通知为所述确认请求中没有携带所述目标应用服务器标识信息时, 所述确认模块发送冲突响应, 否则, 所述确认模块发送正确响应。
25、 如权利要求 22、 23或 24所述的设备, 其特征在于, 所述设备为所述 目标应用服务器。
26、 如权利要求 22、 23或 24所述的设备, 其特征在于, 所述设备还包括: 第二存储模块, 用于保存标识应用类型的信息和应用服务器标识信息间映 射关系的映射表;
查找模块, 用于根据所述第二接收模块接收到的标识请求查找所述映射表, 获取并输出所述目标应用服务器的标识信息。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP07785133A EP1993235A4 (en) | 2006-10-20 | 2007-07-18 | METHOD, DEVICE, DEVICE AND SYSTEM FOR OBTAINING IDENTIFICATION INFORMATION OF AN APPLICATION SERVER |
US12/326,215 US20090077242A1 (en) | 2006-10-20 | 2008-12-02 | Method, terminal, device and system for obtaining id information of application service |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNA2006101402799A CN101166129A (zh) | 2006-10-20 | 2006-10-20 | 获取应用服务器标识信息的方法、终端、设备和*** |
CN200610140279.9 | 2006-10-20 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/326,215 Continuation US20090077242A1 (en) | 2006-10-20 | 2008-12-02 | Method, terminal, device and system for obtaining id information of application service |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008049300A1 true WO2008049300A1 (fr) | 2008-05-02 |
Family
ID=39324115
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2007/002191 WO2008049300A1 (fr) | 2006-10-20 | 2007-07-18 | Procédé, terminal, dispositif et système pour obtenir les informations d'identification d'un serveur d'application |
Country Status (4)
Country | Link |
---|---|
US (1) | US20090077242A1 (zh) |
EP (1) | EP1993235A4 (zh) |
CN (1) | CN101166129A (zh) |
WO (1) | WO2008049300A1 (zh) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9179485B2 (en) * | 2012-07-17 | 2015-11-03 | Qualcomm Incorporated | Methods and apparatus for associating user equipment electronic identifiers with users |
CN104135504B (zh) * | 2014-02-11 | 2015-12-30 | 腾讯科技(深圳)有限公司 | 一种基于应用的服务提供方法、装置及*** |
CN108834130B (zh) * | 2018-05-31 | 2022-09-02 | 深圳市宏电技术股份有限公司 | 标识分配方法、装置、终端及计算机可读存储介质 |
CN111382774B (zh) * | 2018-12-31 | 2024-06-04 | 华为技术有限公司 | 一种数据处理方法及装置 |
CN113064753B (zh) * | 2019-12-30 | 2023-03-14 | 深圳Tcl新技术有限公司 | 一种主机状态获取方法、***、智能终端及存储介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1319814A (zh) * | 2000-01-28 | 2001-10-31 | 韩尼克公司 | 双字节域名服务器*** |
US20030108000A1 (en) | 2001-12-07 | 2003-06-12 | Telefonaktiebolaget Lm Ericsson (Pub1) | Service access system and method in a telecommunications network |
US20050027869A1 (en) * | 2003-07-31 | 2005-02-03 | International Business Machines Corporation | Method, system and program product for asynchronously processing requests |
WO2005064896A1 (en) | 2003-12-19 | 2005-07-14 | Nokia Corporation | Application server adressing |
DE102004038646A1 (de) | 2004-08-09 | 2006-02-23 | Siemens Ag | Bereitstellung zumindest einer Adresse eines Applikationsservers |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040249949A1 (en) * | 2003-03-27 | 2004-12-09 | Christophe Gourraud | Voice and multimedia distribution using Push-To-Talk (PTT) subscribers' group |
FI20045138A0 (fi) * | 2004-04-16 | 2004-04-16 | Nokia Corp | Ryhmätiedon hallinta |
FI20040577A0 (fi) * | 2004-04-23 | 2004-04-23 | Nokia Corp | Tiedon toimittaminen tietoliikennejärjestelmän resurssista |
JP4331090B2 (ja) * | 2004-11-05 | 2009-09-16 | パナソニック株式会社 | 通信システム、情報処理装置、仲介サーバ、識別情報送信サーバ、通信方法及びプログラム |
US8473617B2 (en) * | 2004-12-31 | 2013-06-25 | Sony Corporation | Media client architecture for networked communication devices |
EP1905208B1 (en) * | 2005-07-19 | 2009-10-07 | Telefonaktiebolaget LM Ericsson (publ) | Method and apparatus for allocating application servers in an ims |
-
2006
- 2006-10-20 CN CNA2006101402799A patent/CN101166129A/zh active Pending
-
2007
- 2007-07-18 WO PCT/CN2007/002191 patent/WO2008049300A1/zh active Application Filing
- 2007-07-18 EP EP07785133A patent/EP1993235A4/en not_active Withdrawn
-
2008
- 2008-12-02 US US12/326,215 patent/US20090077242A1/en not_active Abandoned
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1319814A (zh) * | 2000-01-28 | 2001-10-31 | 韩尼克公司 | 双字节域名服务器*** |
US20030108000A1 (en) | 2001-12-07 | 2003-06-12 | Telefonaktiebolaget Lm Ericsson (Pub1) | Service access system and method in a telecommunications network |
US20050027869A1 (en) * | 2003-07-31 | 2005-02-03 | International Business Machines Corporation | Method, system and program product for asynchronously processing requests |
WO2005064896A1 (en) | 2003-12-19 | 2005-07-14 | Nokia Corporation | Application server adressing |
DE102004038646A1 (de) | 2004-08-09 | 2006-02-23 | Siemens Ag | Bereitstellung zumindest einer Adresse eines Applikationsservers |
Non-Patent Citations (1)
Title |
---|
See also references of EP1993235A4 |
Also Published As
Publication number | Publication date |
---|---|
EP1993235A1 (en) | 2008-11-19 |
EP1993235A4 (en) | 2009-09-23 |
US20090077242A1 (en) | 2009-03-19 |
CN101166129A (zh) | 2008-04-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10536490B2 (en) | Apparatus and method for communications involving a legacy device | |
US9667674B2 (en) | Method, device, and system for connecting to a communication device | |
JP5032338B2 (ja) | パケット交換無線アクセス網において緊急呼出を処理する方法及び装置 | |
CA2784453C (en) | System and method for detecting and processing stale messages | |
US9407775B2 (en) | Method and apparatus for managing calls | |
US7773584B2 (en) | Method and apparatus for processing session initiation protocol messages associated with a voice over IP terminal | |
KR100770861B1 (ko) | 아이피 멀티미디어 서브시스템망에서 회선교환 서비스정보를 획득하기 위한 방법 및 장치 | |
WO2004112351A1 (en) | Service registration, subscription and notification across local service discovery domains | |
US10462294B2 (en) | Method and apparatus for processing a communication request from a roaming voice over IP terminal | |
WO2008084911A1 (en) | Session update using management of capability of terminal | |
WO2008049300A1 (fr) | Procédé, terminal, dispositif et système pour obtenir les informations d'identification d'un serveur d'application | |
WO2015117442A1 (zh) | 融合通信终端发现以及能力探测的处理方法及装置 | |
US20090063697A1 (en) | File transfer system and method for same | |
KR101447297B1 (ko) | 세션 통합 방법 및 시스템 | |
JP2008546308A (ja) | Sipベース移動管理のための方法およびシステム | |
JP2009245397A (ja) | サーバ補助装置とそのプログラム | |
CN103152495A (zh) | 一种媒体转移的方法、装置及*** | |
JP2009246410A (ja) | プロトコル変換装置、およびこれを含む通信システム | |
JP2008113381A (ja) | 通信システム | |
KR20080093725A (ko) | 세션 설정 프로토콜 기반의 ip 멀티미디어 서비스를제공하는 단말장치, 호 세션 제어 기능 장치 및 이를이용한 서비스 요청 송/수신 방법 | |
KR101630621B1 (ko) | 통합 메시징 서비스 방법, 기계로 읽을 수 있는 저장 매체 및 장치 | |
WO2009107465A1 (ja) | サービストリガ制御システム、サーバ、方法およびプログラム | |
JP2011083039A (ja) | 通信システム及びサーバ装置 | |
WO2010045770A1 (zh) | 消息处理方法/***、融合业务*** | |
JP2005151009A (ja) | 通信端末 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07785133 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007785133 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |