WO2007085164A1 - Procédé et système pour rapporter les informations de renouvellement de la propriété client - Google Patents

Procédé et système pour rapporter les informations de renouvellement de la propriété client Download PDF

Info

Publication number
WO2007085164A1
WO2007085164A1 PCT/CN2006/003118 CN2006003118W WO2007085164A1 WO 2007085164 A1 WO2007085164 A1 WO 2007085164A1 CN 2006003118 W CN2006003118 W CN 2006003118W WO 2007085164 A1 WO2007085164 A1 WO 2007085164A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
server
attribute
subscription
information
Prior art date
Application number
PCT/CN2006/003118
Other languages
English (en)
French (fr)
Inventor
Xueping Zhong
Linyi Tian
Chong Gu
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 DE602006008356T priority Critical patent/DE602006008356D1/de
Priority to AT06817856T priority patent/ATE438992T1/de
Priority to EP06817856A priority patent/EP1983707B1/en
Priority to CN200680013178.3A priority patent/CN101164305A/zh
Publication of WO2007085164A1 publication Critical patent/WO2007085164A1/zh
Priority to US12/179,021 priority patent/US20080281965A1/en

Links

Classifications

    • 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/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/303—Terminal profiles
    • 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/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • 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/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users

Definitions

  • the present invention relates to communication technologies, and in particular, to a method and system for reporting client attribute update information.
  • the UE may be a mobile phone, a notebook computer with a mobile terminal, or a mobile communication device installed on a vehicle, and these devices can perform various wireless services with the wireless access network.
  • the system structure in which the wireless network provides services for the UE is as shown in FIG. 1 or FIG. 2.
  • the client is a device that includes a User Agent Profile (UAP) or a Personal Digital Assistant (PDA);
  • the server is a service application server that supports UAP (such as PUSH server, WEB). Server, etc.).
  • UAP Wireless Application Protocol
  • WAP gateway is added to implement different protocol stacks and content format conversion, such as the conversion of the WAP protocol stack and the WWW protocol stack. Conversion from Wireless Markup Language (WML) to Hypertext Markup Language (HTML).
  • WML Wireless Markup Language
  • HTML Hypertext Markup Language
  • UAP is mainly used to adapt the content of the client and the server. For example, if the client wants to browse a certain webpage, the client needs to send the capability information of the device to the server.
  • the UAP attribute information of the user agent file includes: hardware platform information, software platform information, browser client, network characteristics. And WAP features, etc.
  • the hardware platform information refers to the hardware features of the terminal, including the terminal type, device model, display screen size, input and output modes, and so on. For example, specify screen size, bit per pixel, color, support for text input capability, support for image capabilities, and keyboard.
  • Software platform information refers to the software operating environment of the terminal, including the operating system, whether it supports video, audio codec, and user. Language selection, etc. For example, indicate whether support for receiving downloadable software, supported character sets, etc.
  • the information browser client refers to a set of features that describe the HTML browsing application.
  • Network characteristics refer to information describing the structure and environment of the network, such as network bearers.
  • the WAP feature refers to the WAP-related information that the client supports, such as the capabilities and features of WML Browse.
  • the client When the client initiates a session to the network, it will include its own UAP-related information in the request message and send it to the WAP gateway or server. After receiving the request message, if the server can process the request including the UAP information, the server obtains the UAP information of the client according to the UAP related information included in the request message, and reduces the content requested by the client according to the information. Send it to the client again.
  • a method for UAP representation and interaction between a client and a server When a client capability changes, the client reports a change to the server's own capabilities, and the server provides content according to the new client capability (as shown in FIG. 3). Enables the server to tailor the content provided based on client capabilities to best match the user The way to provide content to the user. ⁇
  • step 410 the client initiates a request to the server, at which point the client establishes a session with the server.
  • the client includes the UAP information in the session request, which is usually the Uniform Resource Locator (URL) of the UAP.
  • the server initiates a UAP request to the UAP storage server according to the UAP URL information, thereby obtaining the UAP.
  • URL Uniform Resource Locator
  • step 420 the server returns a response message to the client. If the server can correctly process the UAP information, it returns a UAP message OK. If not, an error code is returned.
  • This process only occurs when the client connects to the server.
  • the server maintains a session with the client until the server or client closes the connection.
  • the server caches the UAP information of the client.
  • the UAP update process is shown in Figure 5.
  • the client sends a capability change message to notify the server of the change.
  • the server updates the locally cached client capability information according to the information contained in the capability update notification reported by the client, and returns a response message to the client.
  • the client's capability update process is shown in Figure 6. It can be divided into three phases: the web browsing phase, the client capability update phase, and the web browsing phase after the client capability update.
  • the user initiates a web browsing and is browsing certain content of interest.
  • the server has obtained the client capability information of the user, and can tailor the content according to the actual capability of the client, so that the content best matches the capabilities of the client, as in step 610.
  • the user replaces the displayed font size with a small font, causing the client to change its capabilities, and the client notifies the server of the change.
  • the server updates the locally cached client capability information according to the information contained in the capability update notification reported by the client, and returns a response message to the client, as in steps 620 to 640.
  • the user continues to browse other webpages, and the client initiates a new webpage browsing request to the server, and the server sends the content to the client according to the modified client capability information, as in step 650. 680.
  • unnecessary communication traffic exists between the client and the server, which increases the processing load on the server side.
  • the main purpose of the present invention is to provide a method and system for reporting client attribute update information, so that the client device can selectively update the reporting capability to reduce the communication traffic between the client and the server and the processing load on the server.
  • the method for reporting client attribute update information provided by the embodiment of the present invention includes: determining, by the server, related client attributes according to the provided service, and sending a request for subscribing to the attribute to the client;
  • the client responds to the subscription request and sends an update notification message to the server when it detects that the attribute of the server-side subscription changes.
  • the update notification message sent by the client includes information about the attribute change, and the method further includes:
  • the server updates the client attribute information according to the attribute change related information of the client.
  • the attributes are user agent profile attributes or/and capability attributes of the user terminal.
  • the embodiment of the present invention further provides a reporting system for updating client attribute information, and a subscription decision unit is configured on the server side for determining related client attributes according to the provided service, and subscribing the attributes to the client;
  • the client includes a subscription management unit, and the subscription content is detected, and the related attribute changes are detected, and the attribute change information subscribed by the server is fed back to the server.
  • the service provided by the subscription decision unit on the server side occurs When changing, the client is re-subscribed to the client attributes related to the changed business.
  • An embodiment of the present invention provides a server, including:
  • a subscription decision unit is configured to determine related client attributes according to the provided services, and subscribe the attributes to the client.
  • a subscription management unit configured to manage the subscription content from the server, detect related attributes, and feed back the attribute change information of the server-side subscription to the server.
  • the technical solution provided by the embodiment of the present invention adds a subscription/notification mechanism to the update of the device capability, and the server only subscribes to the client user agent profile UAP attribute related to the provided service.
  • the client only needs to report the part of the UAP update subscribed by the server, and a large number of unsubscribed UAP updates can be used without the H, thereby reducing the communication traffic between the client and the server.
  • the server only needs to process UAP changes that may affect its own services, and does not have to deal with a large number of unrelated UAP requests, thereby reducing the processing load on the server side and improving the performance of the server-side processing service.
  • the client has a management function for the subscription content, so that one client can accept subscriptions from multiple servers at the same time, and each server can have one or more subscriptions.
  • FIG. 1 is a system structural diagram of a wireless network providing service in the prior art
  • FIG. 2 is a structural diagram of a system for adding a WAP gateway in a wireless network providing service process in the prior art
  • FIG. 3 is a schematic diagram of a client reporting a change in its own attributes in the prior art
  • FIG. 4 is a flow chart of establishing a connection request between a client and a server in the prior art
  • FIG. 5 is a flowchart of an update initiated when a client capability attribute is changed in the prior art
  • 6 is a flowchart of a method for initiating attribute change in a process of browsing a webpage by a client in the prior art
  • FIG. 7 is a schematic diagram of a method for reporting a client capability attribute update information in an embodiment of the present invention; The client capability attribute update information is reported to the system structure diagram;
  • FIG. 9 is a flowchart of a method for reporting client capability attribute update information in the first embodiment of the present invention.
  • FIG. 10 is a flowchart of a method for reporting client capability attribute update information in a second embodiment of the present invention. detailed description
  • the client capability attribute update is taken as an example for description. Other attribute updates can also be reported by this method.
  • the specific steps of the client capability attribute update information reporting method are as follows:
  • Step 701 The user initiates a service request, that is, the client where the user is located sends a message to the server, requesting the server to provide a service for the server.
  • Step 702 After receiving the service request initiated by the user, the server returns a response message to the client of the user.
  • Step 703 The server determines related client capability attributes according to the provided service, and subscribes the related attributes to the client.
  • Step 704 the client receives and manages the subscription request from the server, and returns a response message to the server.
  • steps 701 to 704 are stages of establishing a connection between the client and the server.
  • the client detects that its own attribute has changed, it first determines whether the attributes that caused the change are subscribed by the server, and if not, ignores the changes; if it has been subscribed, it proceeds to step 705.
  • Step 705 Send a notification message to the server that subscribes to the attribute, where the change is included Property value.
  • Step 706 The server updates the locally cached client capability information according to the information included in the update notification message reported by the client, and returns a response message to the client.
  • Steps 705 to 706 are the attribute update process of the client.
  • the UAP attribute information including: the hardware platform information, the software platform information, the browser client, the network feature, and the WAP feature, can also be reported by the method provided by the present invention, and the specific steps are similar to the foregoing embodiment. , will not repeat them here.
  • a subscription/notification mechanism is added to the device update attribute reporting (e.g., user agent profile UAP attribute) information, and the server only subscribes to the client user agent profile UAP attribute associated with the provided service.
  • the client only needs to report the part of the UAP update subscribed by the server.
  • a large number of unsubscribed UAP updates can be reported without any report, thereby reducing the communication traffic between the client and the server.
  • the server only needs to process UAP changes that may affect its own services, and does not have to deal with a large number of unrelated UAP requests, thereby reducing the processing load on the server side and improving the performance of the server-side processing service.
  • the client capability update reporting system in the embodiment of the present invention includes two parts: a client and a server.
  • the server side further includes a subscription decision unit; the client further includes a subscription management unit. '
  • the server-side subscription decision unit is configured to determine related client capability attributes according to the provided services, and subscribe the attributes to the client. Specifically, the server-side subscription decision unit is responsible for determining which services and setting parameters of the UE are related to the services provided by the server, and initiating a subscription request for the related attributes to the client, and requesting the client to report the changes to the attributes when the attributes are changed. Server, so that the server sends the content to the client correctly.
  • the subscription management unit of the client is configured to manage the subscription content from the server, and notify the server when the attribute subscribed by the server changes.
  • the client's subscription management unit is responsible for processing the subscription request from the server, requesting to distinguish sessions from different servers, maintaining subscription requests for each session, and being able to change based on device attributes detected by other modules or changes in user preferences. Initiate a property update notification message, Reported to the server.
  • An embodiment of the present invention provides a server, including:
  • a subscription decision unit is configured to determine related client attributes according to the provided services, and subscribe the attributes to the client.
  • a terminal device is further provided in the embodiment of the present invention, including:
  • a subscription management unit configured to: forward the subscription content from the server, detect related attributes, and feed back the attribute change information of the server-side subscription to the server.
  • the specific steps of the method for reporting client capability attribute update information are as follows:
  • Step 901 The client initiates a connection request. Specifically, when a user of a client needs to implement a certain service, the client where the client is located sends a connection request message, requesting the server to provide a service for it. For example, if the user wants to browse the webpage, the client where the user is located sends a browsing request to the server.
  • the client in this embodiment may be a mobile terminal, a fixed terminal, a PC or other occasions requiring reporting update capability.
  • Step 902 The server returns a response and determines a related attribute to generate a subscription request according to the request message.
  • the server After receiving the request message for establishing a connection, the server first determines whether the request message carries information about a client-related attribute, such as related information of the UAP. If the request message does not carry the information about the UAP, the client does not support the UAP, and the server directly returns the response. If the information about the UAP is carried, the client supports the UAP, and then the server requests the message according to the request. Get UAP information. If the acquisition is unsuccessful, the server returns a response that does not support UAP.
  • a client-related attribute such as related information of the UAP.
  • the server-side subscription decision unit determines the relevant UAP attribute according to the provided service, that is, determines Which properties of the client are related to the service they are requesting, and a subscription request is generated.
  • the service provided by the server is only related to the screen size, pixel per bit and color of the client.
  • the server-side subscription decision unit generates a subscription request for the screen size, pixel bits and color of the subscribing client.
  • Step 903 The subscription decision unit of the server side initiates a subscription request. Specifically, the server-side subscription decision unit sends the subscription request generated in step 902 to the client, and requests the client to report to the server when the subscribed attributes change, so that the server correctly sends the content to the client. end.
  • the client responds to the subscription request. Specifically, after the client receives the subscription request from the server, the client's subscription management unit stores and processes the subscription request. If the processing is successful, a response message that the subscription request succeeds is sent to the subscription decision unit of the server; if the processing fails, a message that the subscription request fails is sent to the subscription decision unit of the server. Since the client may have established connections to multiple servers or multiple connections to one server, the subscription management unit is required to be able to distinguish and maintain subscription requests from different servers and different subscription requests from the same server. It is not difficult to find that steps 901 to 904 correspond to steps 701 to 704 and belong to the connection establishment phase.
  • step 905 the client detects whether its capability has changed. Specifically, the client's subscription management unit detects whether its device capabilities or user preferences have changed at any time through other modules of the client. If some attributes of the client are changed due to the state of the device or the settings of the user, Then, proceed to step 906 to check whether there is a server that subscribes to the change attribute; if the attribute of the client does not change, return to step 905 to continue detecting the attribute change of the client itself.
  • Step 906 the client's subscription management unit checks to see if there is a server that subscribes to the change. If yes, go to step 907; if not, go back to step 905 and continue to detect the client's own property changes. For example, the client detects that the screen size, the number of bits per pixel, and the keyboard attributes have changed in step 905. For the above case, the server side subscribes to the client's screen size, per pixel bit, and color subscription. The request, therefore, the client's subscription management unit can view the server with the subscribed screen size, bits per pixel, and proceeds to step 907.
  • the client initiates an update notification message. Specifically, the client informs the server that subscribes to the attribute by the update notification message through the update notification message, so that the server can correctly deliver the content to the client. For the above case, the client sends the screen size to the server, An update notification message per pixel bit. If the changed client capability attribute is subscribed by multiple servers, the client needs to send an update notification message to each server that subscribes to the attribute. ,
  • step 908 the server returns a response. Specifically, after receiving the update notification message, the server updates the attribute information of the locally cached client according to the information contained in the update notification message reported by the client, and returns a response message to the client, and thereafter, according to the modified The client capability information reduces the content and sends it to the client.
  • the above steps 905 to 908 correspond to steps 705 to 706 and belong to the client capability attribute update phase.
  • the client can access the server side of the network side through the WAP gateway.
  • the server-side subscription decision unit and the client's subscription management unit can communicate using a Session Initiation Protocol (SIP) or other interactive protocol.
  • SIP Session Initiation Protocol
  • the server end subscribes to the attributes related to the service currently being performed by the client, and when a large number of attributes that are not related to the ongoing service change, the client does not need to report to the server, thereby greatly reducing the client and the server. Communication traffic between.
  • the server side only needs to process UAP changes that may affect its own services, and does not have to deal with a large number of unrelated UAP requests, thereby reducing the processing load on the server side, improving the performance of the server-side processing service, and reducing the information that the WAP gateway needs to process. Increased the number of clients that the WAP gateway can access simultaneously.
  • the second embodiment of the present embodiment increases the situation in which the service provided by the server changes.
  • the specific steps of the client capability attribute update information reporting method are as follows:
  • Step 1001 to step 1006 corresponds to step 701 to step 706.
  • Step 1007 When the service provided by the server changes, the server needs to initiate a synchronization client capability attribute request to the client.
  • Step 1008 The client reports the update attribute of the client, that is, sends the related attribute of the changed service to the server.
  • the server initiates a subscription request.
  • the server-side subscription decision unit root determines the relevant attribute according to the changed service, and re-initiates the subscription request. For example Said that the server-side service is only related to the client's screen size, bit per pixel and color, but the changed service is only related to the client's support for text input and image support capabilities.
  • the server-side subscription decision unit Initiate a new subscription request, request subscription to the client's support text input capabilities and support image capability attributes.
  • the client returns a subscription response. Specifically, after receiving the newly initiated subscription request from the server-side subscription decision unit, the subscription management unit of the client overwrites the previous subscription request to the same connection and returns a response to the server-side subscription decision unit. For the above case, the client's subscription management unit overwrites the subscription request of the original subscription screen size, per-pixel bit and color attribute with the subscription-supported text input capability and the support image capability attribute new subscription request, and returns a response to the server-side subscription decision unit. . After that, the client sends an update notification message to the server only when it supports changes in text input capabilities and support image capabilities.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
  • Computer And Data Communications (AREA)
  • Debugging And Monitoring (AREA)

Description

客户端属性更新信息的上报方法及系统 本申请要求于 2006 年 01 月 24 曰提交中国专利局、 申请号为 200610023602.4,发明名称为 "客户端能力更新上报系统及其方法"的中 国专利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信技术，特别涉及客户端属性更新信息的上报方法及 系统。
背景技术
随着科技的迅猛发展， 给人类的生活和工作带来了十分重大的变 革。 通信等领域作出的贡献尤为突出。 从十九世纪发明的电报， 逐渐发 展现在的第三代移动通信（3G， The Third Generation ), 使人类对移动 性与信息的需求急剧上升， 人们希望无论何时、 何地， 当需要的时候， 就能高速访问互联网或企业内部网， 收发电子邮件， 进行电子商务， 交 换文件、 传真和其他的数据， 从而提高自己在社会生活中的竟争优势， 获得一个更加灵活的生活方式。
为了满足人类对无线网络提出的各种无线业务要求，近年来用户设 备（UE, User Equipment ) 的能力也随着无线网络不断推出的新业务而 变得越来越强。 其中， UE可以是手机， 也可以是带有移动终端的笔记 本电脑， 或者是安装在车辆上的移动通信设备， 这些设备能够同无线接 入网进行各种无线业务。
无线网络为 UE提供服务的系统结构如图 1或图 2所示。在图 1中， 客户端为包含支持用户代理档案 （UAP, User Agent Profile )或个人数 字助理（PDA, Personal Digital Assistant ) 的设备； 服务器端为包含支 持 UAP的业务应用服务器（如 PUSH服务器， WEB服务器等）的设备。 图 2 与图 1 的区别仅在于增加了无线应用协议 ( WAP , Wireless Application Protocol ) 网关， 用于实现不同协议堆栈以及内容格式的转 化，如 WAP十办议堆 4戋与 WWW协议堆栈的转化、无线标记语言（ WML， Wireless Markup Language ) 到超文本标记语言 （HTML , Hypertext Markup Language ) 的转换。 其中， UAP 主要用于对客户端与服务器端的内容进行适配。 比如 说， 客户端希望浏览某一网页， 该客户端则需要把自身设备的能力信息 发送给服务器端， 用户代理档案 UAP属性信息包括： 硬件平台信息、 软件平台信息、 浏览器客户端、 网络特征以及 WAP特征等。
硬件平台信息指终端的硬件特征， 包括终端种类， 设备型号， 显示 屏幕大小， 输入、 输出方式等。 比如说， 指明屏幕尺寸、 每象素比特、 颜色、 支持文本输入能力、 支持图像能力和键盘等信息， 软件平台信息 指终端的软件操作环境， 包括操作系统， 是否支持视频、 音频编解码， 用户语言选择等。 比如说， 指明是否支持接收可下载的软件， 支持的字 符集等信息浏览器客户端指一组描述 HTML浏览应用程序的特性。
网络特征指描述网络相关的结构和环境， 如网络承载等信息。
WAP特征指描述客户端支持的 WAP相关信息， 如 WML Browse 的能力和特性等。
客户端向网络发起会话时 , 会把自身的 UAP相关信息包含到请求 消息中， 发给 WAP网关或者服务器端。 服务器端接收到请求消息后， 如果该服务器能够处理包含有 UAP信息的请求， 则根据请求消息中包 含的 UAP相关信息， 取得客户端的 UAP信息， 并根据此信息对客户端 申请的内容进行裁减， 再发给该客户端。
目前， 市场上客户端的选择多不胜数， 虽然极大地满足了用户的个 性化需求。 然而， 客户端的多样性也导致了能力上的极大差别， 如屏幕 尺寸大小，颜色，字体，甚至同一个客户端间的能力上也是动态变换的， 如摄像头的插入， 蓝牙电话的选择等， 而且， 根据用户的喜好也会发生 动态的变化， 如设置不同的字体， 是否接收网页上的图片等。 为了使客 户端能正确显示网络所提供的服务， 如所浏宽的网页， 多媒体消息业务 ( MMS, Multimedia Message Services )等内容， 也为了使服务器能够 最有效地使用客户端提供的能力， 提供了一种客户端和服务器间 UAP 表示和交互的方法： 当客户端能力发生变换时， 该客户端上报给服务器 自身能力的变化， 服务器按照新的客户端能力提供内容（如图 3所示）， 使得服务器能够根据客户端能力对提供的内容进行裁减， 以最符合用户 的方式提供内容给用户。 ■
客户端与服务器建立连接的流程如图 4所示。 在步骤 410中， 客户 端向服务器发起请求， 此时客户端与服务器会建立一个会话。 客户端在 会话请求中包含 UAP 的相关信息， 通常是 UAP 的统一资源定位器 (URL, Uniform Resource Locator), 服务器根据 UAP的 URL信息， 向 UAP的存储服务器发起取得 UAP的请求， 从而获得 UAP。
在步驟 420中， 服务器向客户端返回响应信息， 如果服务器能够正 确处理 UAP信息， 则返回 UAP信息 OK, 如果不能， 则返回错误代码。
本流程只在客户端连接服务器时发生。服务器与客户端保持一个会 话， 直到服务器或客户端关闭连接， 这个过程中服务器会缓存客户端的 UAP信息。
当客户端的能力发生变化时， UAP的更新流程如图 5所示。 在步 骤 510中， 客户端发送能力变更消息， 通知服务器所发生的变化。 在步 骤 520中，服务器根据客户端上报的能力更新通知中包含的信息更新本 地緩存的客户端能力信息， 并返回响应消息给客户端。
以客户端浏览网页为例， 客户端的能力更新流程如图 6所示， 可分 为三个阶段： 网页浏览阶段、 客户端能力更新阶段以及客户端能力更新 后网页浏览阶段。
在网页浏览阶段中， 用户发起网页浏览， 正在浏笕某些感兴趣的内 容。 此时服务器已经取得该用户的客户端能力信息， 能够根据该客户端 的实际能力对内容进行裁减， 以使得内容最符合客户端的能力， 如步骤 610。
在客户端能力更新阶段中， 用户把显示的字体大小换成小字体， 使 客户端发生了能力变化， 客户端把这种变化通知服务器。 服务器根据该 客户端上报的能力更新通知中包含的信息更新本地缓存的客户端能力 信息， 并返回响应消息给客户端， 如步骤 620至 640。
在客户端能力更新后网页浏览阶段中， 用户继续浏览其它网页， 客 户端发起新的网页浏览请求给服务器，服务器根据修改后的客户端能力 信息对内容裁减后发送给客户端， 如步骤 650至 680。 在实际应用中， 客户端与服务器间存在不必要的通信流量， 增加了 服务器端的处理负担。
在现有技术的 UAP更新流程中， 无论客户端发生任何变化， 都需 向服务器端上报， 服务器端在接收客户端的能力更新通知后， 根据能力 更新通知中包含的信息更新本地缓存的客户端能力信息，并返回响应消 息给客户端。 发明人在发明过程中发现： 在实际应用中， 客户端发生的 许多能力变化其实并不影响用户目前所进行的操作，上报这些变化只是 无谓地增加了网络流量； 并且， 服务器端或 WAP网关也会由于处理这 些无关的能力更新请求而导致对本身性能的影响。 发明内容
本发明的主要目的在于提供一种客户端属性更新信息的上报方法 及系统， 使得客户端设备可以有选择地更新上报能力， 以减少客户端与 服务器端之间的通信流量和服务器端的处理负担。
本发明实施例提供的一种客户端属性更新信息的上报方法， 包括： 服务器端根据所提供的业务确定相关的客户端属性， 并向客户端 发送订阅所述属性的请求；
所述客户端响应所述订阅请求并在检测到所述服务器端订阅的属 性发生变化时， 发送更新通知消息给所述 务器端。
所述客户端发送的更新通知消息中包含属性变化相关信息， 该方 法进一步包括：
所述服务器根据所述客户端的属性变化相关信息更新客户端属性 信息。
所述属性为用户代理档案属性或 /和用户终端的能力属性。
本发明实施例还提供一种客户端属性更新信息的上报系统， 在服 务器端设置有订阅决策单元， 用于根据所提供的业务确定相关的客户 端属性， 并向客户端订阅所述属性；
所述客户端中包括订阅管理单元， 居所述订阅内容， 检测相关 属性变化， 并将所述服务器端订阅的属性变化信息反馈给服务器端。
更适宜地， 所述订阅决策单元在所述服务器端所提供的业务发生 变化时， 重新向所述客户端订阅与变化后的业务相关的客户端属性。 本发明实施例提供一种服务器， 包括：
订阅决策单元， 用于根据所提供的业务确定相关的客户端属性， 并向客户端订阅所述属性。
本发明实施例提供的一种终端设备， 包括： ,
订阅管理单元， 用于管理来自所述服务器端的订阅内容， 检测相关 属性， 并将所述月良务器端订阅的属性变化信息反馈给服务器端。
与现有技术相比，本发明实施例提供的技术方案对于设备能力的更 新上报增加了订阅 /通知机制， 而且服务器端只订阅与所提供的业务相 关的客户端用户代理档案 UAP属性。 这样客户端只需要上报服务器端 所订阅的那部分 UAP更新， 大量未被订阅的 UAP更新可以不用上才 H， 从而降低了客户端与服务器端之间的通信流量。而服务器端只需处理可 能影响自身业务的 UAP变化， 而不必处理大量无关的 UAP请求， 从而 减轻了服务器端的处理负担， 提高了服务器端处理业务的性能。 由于客 户端上报的 UAP更新少了， WAP网关需要处理的信息也相应减少， 提 高了 WAP网关可同时接入的客户端数目。对于客户端 UAP变化频繁的 场合， 本发明的上述效果更为显著。
客户端具有对订阅内容的管理功能，使得一个客户端可以同时接受 多个服务器的订阅， 每个服务器可以有一个或多个订阅。
服务器端提供的业务发生变化时， 重新发起订阅流程， 客户端可以 及时更新需要上报的 UAP属性种类， 从而可以更好地应对客户的各种 业务需求。 附图说明
图 1是现有技术中无线网络提供服务的系统结构图；
图 2是现有技术中无线网络提供服务过程中增加 WAP网关的系统 结构图；
图 3是现有技术中客户端上报自身属性变化的示意图；
图 4是现有技术中客户端与服务器端建立连接请求的流程图； 图 5是现有技术中客户端能力属性变更时发起的更新流程图； 图 6是现有技术中客户端浏览网页过程中发起属性变更的流程图； 图 7是本发明实施例中的客户端能力属性更新信息上报方法的原 理图； - 图 8 是本发明实施例中的客户端能力属性更新信息上报系统结构 图；
图 9是本发明第一实施例中的客户端能力属性更新信息上报方法 流程图；
图 10是本发明第二实施例中的客户端能力属性更新信息上报方法 流程图。 具体实施方式
为使本发明的目的、 技术方案和优点更加清楚， 下面将结合附图对 本发明作进一步地详细描述。
下述实施例中， 以客户端能力属性更新为例进行说明。 其他属性更 新的情况也可通过该方法进行上报。
如图 7所示， 本实施例中， 客户端能力属性更新信息上报方法的具 体步骤如下：
步骤 701， 用户发起业务请求， 即用户所在的客户端向服务器端发 送消息， 请求服务器为其提供业务。
步驟 702, 服务器接收到该用户发起的业务请求后， 向该用户的客 户端返回响应消息。
步骤 703， 服务器根据所提供的服务确定相关的客户端能力属性， 并向客户端订阅其相关属性。
步骤 704, 客户端接收并管理来自服务器的订阅请求， 并向该服务 器返回响应消息。
上述步骤 701至步骤 704为客户端与服务器的连接建立阶段。 当客户端检测到自身的属性发生变化后，首先判断产生变化的这些 属性是否被服务器订阅， 如果没有， 则忽略这些变化； 如果已被订阅， 则进入步骤 705。
步驟 705， 向订阅该属性的服务器发送通知消息， 其中包含变化后 的属性值。
步骤 706, 服务器根据客户端上报的更新通知消息中包含的信息更 新本地緩存的客户端能力信息， 并返回响应消息给客户端。 步骤 705至 步骤 706为客户端的属性更新流程。
可以理解， 对于用户代理档案 UAP属性信息， 包括： 硬件平台信 息、 软件平台信息、 浏览器客户端、 网络特征以及 WAP特征， 也可通 过本发明提供的方法进行上报， 具体步驟与上述实施例类似， 在此不 再赘述。
本发明的具体实施方案中， 对于设备的属性（如用户代理档案 UAP 属性）信息更新上报增加了订阅 /通知机制， 而且服务器端只订阅与所 提供的业务相关的客户端用户代理档案 UAP属性。这样客户端只需要上 报服务器端所订阅的那部分 UAP更新，大量未被订阅的 UAP更新可以不 用上报， 从而降低了客户端与服务器端之间的通信流量。 而服务器端只 需处理可能影响自身业务的 UAP变化，而不必处理大量无关的 UAP请求， 从而减轻了服务器端的处理负担， 提高了服务器端处理业务的性能。
如图 8所示，本发明实施例中的客户端能力更新上报系统包含客户 端与服务器端两部分。 服务器端进一步包含订阅决策单元； 客户端进一 步包含订阅管理单元。 '
其中， 服务器端的订阅决策单元， 用于根据所提供的业务确定相关 的客户端能力属性， 并向客户端订阅这些属性。 具体地说， 服务器端的 订阅决策单元负责确定服务器提供的服务与 UE的哪些能力和设置参数 相关， 并向客户端发起这些相关属性的订阅请求， 要求客户端在这些属 性发生变化时， 能够上报给服务器， 以便服务器正确的把内容发给客户 端。
客户端的订阅管理单元， 用于管理来自所述服务器端的订阅内容， 在该服务器端所订阅的属性发生变化时通知该服务器端。 具体地说， 客 户端的订阅管理单元负责处理来自服务器端的订阅请求，要求区分来自 不同服务器的会话， 维护各会话的订阅请求， 并能够根据其它模块检测 到的设备属性发生变化或用户的偏好发生变化发起属性更新通知消息， 上报给服务器。
本发明实施例提供一种服务器， 包括：
订阅决策单元， 用于根据所提供的业务确定相关的客户端属性， 并向客户端订阅所述属性。
本发明的实施例中还提供了一种终端设备， 包括：
订阅管理单元， 用于； f理来自所述服务器端的订阅内容， 检测相关 属性， 并将所述服务器端订阅的属性变化信息反馈给服务器端。
以上对本发明的原理及其系统进行了说明，下面对基于上述系统的 本发明第一实施例进行详细描述。
如图 9所示， 本发明第一实施例中， 客户端能力属性更新信息的上 报方法的具体步骤如下：
步骤 901 , 客户端发起连接请求。 具体地说， 当客户端的用户需要 实现某项业务时， 其所在的客户端发送连接请求消息， 请求服务器为其 提供业务。 比如说， 用户想要浏览网页， 则该用户所在的客户端向服务 器发送浏览请求。 本实施方式中的客户端可以是移动终端， 固定终端， PC机或其他需要上报更新能力的场合。
步骤 902, 服务器端返回响应并根据请求消息确定相关属性生成订 阅请求。
具体地说， 服务器端在接收到建立连接的请求消息后， 首先判断该 请求消息是否携带客户端相关属性的信息， 如 UAP的相关信息。 如果 请求消息中不携带 UAP的相关信息， 则说明该客户端不支持 UAP, 月良 务器直接返回响应； 如果携带 UAP的相关信息， 则说明该客户端支持 UAP, 那么， 服务器端根据请求消息获取 UAP信息。 如果获取不成功， 则服务器返回不支持 UAP的响应； 如果获取成功， 则说明服务器支持 UAP, 向客户端返回响应， 并且， 服务器端的订阅决策单元根据所提供 的服务确定相关的 UAP属性， 即确定客户端的哪些属性与其请求的服 务相关， 并生成订阅请求。 比如说， 服务器端所提供的服务仅与客户端 的屏幕尺寸、 每象素比特和颜色相关， 那么， 服务器端的订阅决策单元 生成订阅客户端的屏幕尺寸、 每象素比特和颜色的订阅请求。 步骤 903 , 服务器端的订阅决策单元发起订阅请求。 具体地说， 服 务器端的订阅决策单元将在步骤 902中生成的订阅请求发送给客户端， 要求客户端在被订阅的这些属性发生变化时， 能够上报给服务器， 以便 服务器正确的把内容发给客户端。
步骤 904， 客户端响应订阅请求。 具体地说， 当客户端接收到来自 服务器端的订阅请求后，客户端的订阅管理单元对该订阅请求进行存储 及处理。 如果处理成功， 则向服务器端的订阅决策单元发送订阅请求成 功的响应消息； 如果处理失败， 则向服务器端的订阅决策单元发送订阅 请求失败的消息。 由于客户端可能与多个服务器建立了连接， 或者与一 个服务器建立了多种连接， 因此， 订阅管理单元要求能够区分和维护来 自不同服务器端的订阅请求， 以及来自同一个服务器端的不同订阅请 求。 不难发现， 步骤 901至步驟 904对应于步驟 701至步驟 704， 属于 连接建立阶段。
步骤 905， 客户端检测自身的能力是否发生变化。 具体地说， 客户 端的订阅管理单元通过该客户端的其他模块随时检测自身的设备能力 或用户喜好是否发生了变化，如果由于设备的状态或用户的设置而导致 了客户端的某些属性发生了改变， 则进入步骤 906, 查看是否有订阅该 变化属性的服务器；如果客户端的属性没有发生变化，则回到步驟 905 , 继续检测客户端自身的属性变化。
步骤 906，客户端的订阅管理单元查看是否有订阅该变化的服务器。 如果有， 则进入步骤 907; 如果没有， 则回到步骤 905 , 继续检测客户 端自身的属性变化。 比如说， 客户端在步骤 905中检测到屏幕尺寸、 每 象素比特以及键盘属性发生了改变， 针对上述案例， 服务器端向客户端 订阅的是客户端的屏幕尺寸、 每象素比特和颜色的订阅请求， 因此， 客 户端的订阅管理单元可以查看到有订阅屏幕尺寸、 每象素比特的服务 器， 进入步驟 907。
步骤 907, 客户端发起更新通知消息。 具体地说， 客户端将变化的 属性通过更新通知消息告知订阅该属性的服务器， 以便服务器能够正确 地把内容发给客户端。 针对上述案例， 客户端向服务器发送屏幕尺寸、 每象素比特的更新通知消息。如果所变化的客户端能力属性被多个服务 器订阅， 则该客户端需将更新通知消息发送给每个订阅该属性的服务 器。 ，
步骤 908， 服务器返回响应。 具体地说， 服务器在接收到更新通知 消息后，根据该客户端上报的更新通知消息中包含的信息更新本地緩存 的客户端的属性信息， 并返回响应消息给客户端， 并在此后根据修改后 的客户端能力信息对内容进行裁减， 发送给客户端。 上述步骤 905至步 骤 908对应于步骤 705至步骤 706, 属于客户端能力属性更新阶段。
在此， 客户端可以通过 WAP网关接入网络侧的服务器端。 服务器 端的订阅决策单元与客户端的订阅管理单元之间可以使用会话发起协 议（SIP, Session Initiation Protocol )或其他交互协议进行通信。 在本实 施方式中， 服务器端订阅了与客户端目前正在进行的业务相关的属性， 大量的与正在进行的业务无关的属性变化时， 客户端无需上报给服务 器， 大大减少了客户端与服务器端之间的通信流量。 使得服务器端只需 处理可能影响自身业务的 UAP变化，而不必处理大量无关的 UAP请求， 从而减轻了服务器端的处理负担， 提高了服务器端处理业务的性能， 并 且减少了 WAP网关需要处理的信息，提高了 WAP网关可同时接入的客 户端数目。
与前述第一实施例类似，本实施第二实施例中增加了服务器所提供 的服务发生变化的情况。
如图 10所示， 本发明第二实施例中， 客户端能力属性更新信息上 报方法的具体步骤如下：
步骤 1001至步骤 1006对应于步驟 701至步骤 706。
步驟 1007， 当服务器所提供的服务发生变化时， 服务器端需要向 客户端发起同步客户端能力属性请求。
步骤 1008, 客户端上报客户端的更新属性， 也就是将变化后业务 的相关属性发送给服务器端。
步骤 1009, 服务器端发起订阅请求。 具体地说， 服务器端的订阅 决策单元根'据变化后的业务确定相关属性， 并重新发起订阅请求。 比如 说， 服务器端原本所提供的服务仅与客户端的屏幕尺寸、每象素比特和 颜色相关，但是变化后的业务仅与客户端的支持文本输入能力和支持图 像能力相关， 那么， 服务器端的订阅决策单元发起新的订阅请求， 请求 订阅客户端的支持文本输入能力和支持图像能力属性。
步驟 1001 , 客户端返回订阅响应。 具体地说， 客户端的订阅管理 单元在接收到服务器端的订阅决策单元新发起的订阅请求后，将该新的 订阅请求覆盖之前对同一个连接的订阅请求，并对服务器端的订阅决策 单元返回响应。 针对上述案例， 客户端的订阅管理单元用订阅支持文本 输入能力和支持图像能力属性新的订阅请求覆盖原来订阅屏幕尺寸、每 象素比特和颜色属性的订阅请求，并向服务器端的订阅决策单元返回响 应。之后，客户端仅在其支持文本输入能力和支持图像能力发生变化时， 向服务器端发送更新通知消息。
虽然通过参照本发明 '的某些优选实施方式， 已经对本发明进行了图 示和描述， 但本领域的普通技术人员应该明白， 可以在形式上和细节上 对其作各种改变， 而不偏离本发明的精神和范围。

Claims

权 利 要 求
1. 一种客户端属性更新信息的上报方法， 其特征在于， 包括： 服务器端根据所提供的业务确定相关的客户端属性， 并向客户端 发送订阅所述属性的请求；
所述客户端响应所述订阅请求并在检测到所述服务器端订阅的属 性发生变化时， 发送更新通知消息给所述服务器端。
2. 根据权利要求 1所述的方法， 其特征在于， 所述客户端发送的 更新通知消息中包含属性变化相关信息， 该方法进一步包括：
所述服务器根据所述客户端的属性变化相关信息更新客户端属性 信息。 '
3. 才艮据权利要求 1所述的方法， 其特征在于， 所述属性为用户代 理档案属性或 /和用户终端的能力属性。
4. 根据权利要求 1、 2或 3所述的方法， 其特征在于，
当所述服务器端所提供的业务发生变化时， 所述服务器端重新向 所述客户端订阅与变化后的业务相关的客户端属性。
5. 一种客户端属性更新信息的上报系统， 其特征在于， 在服务器 端设置有订阅决策单元， 用于^^据所提供的业务确定相关的客户端属 性， 并向客户端订阅所述属性；
所述客户端中包括订阅管理单元， 根据所述订阅内容， 检测相关 属性变化， 并将所述服务器端订阅的属性变化信息反馈给服务器端。
6. 根据权利要求 5所述的系统， 其特征在于， 所述属性为用户代 理档案属性或 /和用户终端的能力属性。
7. 根据权利要求 5所述的系统， 其特征在于， 所述订阅管理单元 管理的订阅内容来自一个或多个服务器， 每个服务器分别有一个或多 个订阅。
8. 根据权利要求 5至 7中任一项所述的系统， 其特征在于， 所述 订阅决策单元在所述服务器端所提供的业务发生变化时， 重新向所述 客户端订阅与变化后的业务相关的客户端属性。
•
9. 一种服务器， 其特征在于， 包括：
订阅决策单元， 用于根据所提供的业务确定相关的客户端属性， 并向客户端订阅所述属性。
10. 一种终端设备， 其特征在于， 包括：
订阅管理单元， 用于管理来自所述服务器端的订阅内容， 检测相 关属性， 并将所述服务器端订阅的属性变化信息反馈给服务器端。
PCT/CN2006/003118 2006-01-24 2006-11-20 Procédé et système pour rapporter les informations de renouvellement de la propriété client WO2007085164A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
DE602006008356T DE602006008356D1 (de) 2006-01-24 2006-11-20 Verfahren und System zur Meldung von Aktualisierungsinformationen der Fähigkeiten eines Gerätes
AT06817856T ATE438992T1 (de) 2006-01-24 2006-11-20 Verfahren und system zur meldung von aktualisierungsinformationen der fähigkeiten eines gerätes
EP06817856A EP1983707B1 (en) 2006-01-24 2006-11-20 A method and a system for reporting device capability update information
CN200680013178.3A CN101164305A (zh) 2006-01-24 2006-11-20 客户端属性更新信息的上报方法及系统
US12/179,021 US20080281965A1 (en) 2006-01-24 2008-07-24 Method and system for reporting device capability update information

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610023602.4A CN100563169C (zh) 2006-01-24 2006-01-24 客户端能力更新上报系统、方法、服务器和终端设备
CN200610023602.4 2006-01-24

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/179,021 Continuation US20080281965A1 (en) 2006-01-24 2008-07-24 Method and system for reporting device capability update information

Publications (1)

Publication Number Publication Date
WO2007085164A1 true WO2007085164A1 (fr) 2007-08-02

Family

ID=37954808

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/003118 WO2007085164A1 (fr) 2006-01-24 2006-11-20 Procédé et système pour rapporter les informations de renouvellement de la propriété client

Country Status (7)

Country Link
US (1) US20080281965A1 (zh)
EP (1) EP1983707B1 (zh)
CN (2) CN100563169C (zh)
AT (1) ATE438992T1 (zh)
DE (1) DE602006008356D1 (zh)
ES (1) ES2327782T3 (zh)
WO (1) WO2007085164A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080046858A (ko) * 2006-11-23 2008-05-28 엘지전자 주식회사 미디어 싱크 기기, 미이어 소스 기기 및 미디어 싱크기기의 제어 방법
JP2009212550A (ja) * 2008-02-29 2009-09-17 Ntt Docomo Inc 端末機能管理サーバ、通信システム及び通信方法
CN101996206B (zh) 2009-08-11 2013-07-03 阿里巴巴集团控股有限公司 一种呈现网页页面的方法、装置及系统
CA2715362A1 (en) * 2009-09-22 2011-03-22 Thwapr, Inc. Interoperable mobile media sharing
US8825962B1 (en) 2010-04-20 2014-09-02 Facebook, Inc. Push-based cache invalidation notification
US9559906B2 (en) 2013-01-11 2017-01-31 Microsoft Technology Licensing, Llc Server load management
US9225768B2 (en) * 2013-02-06 2015-12-29 Sap Portals Israel Ltd Providing network-applicable content
CN104812006B (zh) * 2014-01-24 2019-11-01 北京三星通信技术研究有限公司 基于缓存的数据传输方法及装置
US11068905B2 (en) * 2014-03-31 2021-07-20 Red Hat, Inc. Behavior adjustment based on capabilities of a downstream server

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1201944A (zh) * 1997-03-24 1998-12-16 格维康姆公司 对因特网无线访问的方法和结构
US20030162540A1 (en) * 2000-07-14 2003-08-28 Nielsen Peter Dam Device for use as a client in a client -server system
WO2005027536A2 (en) * 2003-09-17 2005-03-24 Cellglide Ltd. Packet transport over general packet radio service (gprs) networks

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6816895B2 (en) * 2001-03-26 2004-11-09 Motorola, Inc. Updating the capability negotiation information of a mobile station with an editing application downloaded from a service provider
SE0104080D0 (sv) * 2001-12-05 2001-12-05 Ericsson Telefon Ab L M A method and apparatus for negotiating mobile services
AU2002236125A1 (en) * 2002-03-04 2003-09-16 Nokia Corporation Method, network device and system for providing profile data applicable to hypertext transfer protocol (http)
US7113776B2 (en) * 2002-08-30 2006-09-26 Qualcomm Inc. System and method for application and application metadata filtering based on wireless device capabilities
US7685315B2 (en) * 2002-10-28 2010-03-23 Nokia Corporation System and method for conveying terminal capability and user preferences-dependent content characteristics for content adaptation
EP1593249A1 (en) * 2003-02-03 2005-11-09 Koninklijke KPN N.V. Message data transmission in mobile communication systems taking into account capabilities of sending and receiving devices
US7406696B2 (en) * 2004-02-24 2008-07-29 Dialogic Corporation System and method for providing user input information to multiple independent, concurrent applications
US7512401B2 (en) * 2005-04-04 2009-03-31 Nokia Corporation Method and system for updating capabilities of a device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1201944A (zh) * 1997-03-24 1998-12-16 格维康姆公司 对因特网无线访问的方法和结构
US20030162540A1 (en) * 2000-07-14 2003-08-28 Nielsen Peter Dam Device for use as a client in a client -server system
WO2005027536A2 (en) * 2003-09-17 2005-03-24 Cellglide Ltd. Packet transport over general packet radio service (gprs) networks

Also Published As

Publication number Publication date
CN100563169C (zh) 2009-11-25
EP1983707B1 (en) 2009-08-05
ES2327782T3 (es) 2009-11-03
EP1983707A4 (en) 2009-03-04
CN1937522A (zh) 2007-03-28
CN101164305A (zh) 2008-04-16
DE602006008356D1 (de) 2009-09-17
US20080281965A1 (en) 2008-11-13
EP1983707A1 (en) 2008-10-22
ATE438992T1 (de) 2009-08-15

Similar Documents

Publication Publication Date Title
WO2007085164A1 (fr) Procédé et système pour rapporter les informations de renouvellement de la propriété client
US9984172B2 (en) Accessing really simple syndication (RSS) enabled content using session initiation protocol (SIP) signaling
US7685315B2 (en) System and method for conveying terminal capability and user preferences-dependent content characteristics for content adaptation
US20030195964A1 (en) Managing multicast sessions
US9430581B2 (en) Method and system for detecting slow page load
US20030236892A1 (en) System for adaptation of SIP messages based on recipient's terminal capabilities and preferences
KR101424261B1 (ko) 모바일 웹 서비스를 제공하는 단말기 및 상기 단말기의동작 방법
US20140149534A1 (en) Methods and arrangements for caching static information for packet data applications in wireless communication systems
JP2009009595A (ja) 部分的プレゼンス通知を行うシステムおよび方法
US20040267900A1 (en) Dynamic mobile device characterization
GB2391420A (en) Method for serving audio and image communication in web browser using session initiation protocol
US20060136554A1 (en) Information server in a communication system
US7076523B2 (en) Interaction interface for a composite device computing environment
WO2007112636A1 (en) A method for reporting the user agent profile,the server, and the user terminal thereof
US20030163517A1 (en) Method and apparatus for decreasing bandwidth for wireless data interchange
KR100365137B1 (ko) 무선 인터넷 연결 유지 시스템 및 그 방법
KR100463836B1 (ko) 무선 단말기 특성의 그룹화를 통한 컨텐츠 변환 및 캐슁시스템과 방법
KR20070087168A (ko) 통신 시스템 내의 이동 정보 서버로의 액세스 모니터링
Suryanarayana et al. CC/PP for content negotiation and contextualization
KR100925644B1 (ko) 오브젝트 전송 시스템 및 그 제어방법
TW591911B (en) World Wide Web connection switching method
JP2005267015A (ja) サーバ装置
WO2009107465A1 (ja) サービストリガ制御システム、サーバ、方法およびプログラム
JP2005277526A (ja) 移動体通信システム及びサーバ装置

Legal Events

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

Ref document number: 200680013178.3

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2006817856

Country of ref document: EP