WO2005096550A1 - Procede de creation d'une petite fenetre du cote client dans le reseau intelligent de donnees a large bande - Google Patents
Procede de creation d'une petite fenetre du cote client dans le reseau intelligent de donnees a large bande Download PDFInfo
- Publication number
- WO2005096550A1 WO2005096550A1 PCT/CN2005/000374 CN2005000374W WO2005096550A1 WO 2005096550 A1 WO2005096550 A1 WO 2005096550A1 CN 2005000374 W CN2005000374 W CN 2005000374W WO 2005096550 A1 WO2005096550 A1 WO 2005096550A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- module
- portal server
- handshake
- message
- Prior art date
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/50—Network services
- H04L67/75—Indicating network or usage conditions on the user display
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2869—Operational details of access network equipments
- H04L12/2878—Access multiplexer, e.g. DSLAM
- H04L12/2879—Access multiplexer, e.g. DSLAM characterised by the network type on the uplink side, i.e. towards the service provider network
- H04L12/2881—IP/Ethernet DSLAM
Definitions
- the present invention relates to a broadband data intelligent network technology, and in particular, to a method for implementing a small client window in a broadband data intelligent network.
- broadband data intelligent networks can provide users with rich services, such as broadband Internet access services, portal services, and so on.
- FIG. 1 shows the basic structure of the existing broadband data intelligent network.
- the broadband data intelligent network includes an integrated service control center (ISCC), a broadband service access device (BRAS) s portal server, a database, and so on.
- the BRAS is connected to both the ISCC and the portal server, and the portal server is connected to the database.
- the BRAS is used to establish a data link between the user client and the portal server.
- the ISCC is equivalent to a service control point in the intelligent network, which is used to control user authentication, accounting, and authorization operations.
- the database is used to store the portal server. The data needed.
- a small window is set on the human-computer interaction interface of the user, for example, a small window is set on the computer display screen.
- the user's access information is displayed in a small window, such as the user's online time and access user name.
- operation buttons for users to access the broadband data network or disconnect the broadband data network that is, operation buttons such as login or offline.
- the user can control the use of their own data services by operating the buttons in the small window.
- the timing handshake between the portal server and the small window is generally used.
- Mechanism to proceed When the user cannot use the data service due to the abnormal network interruption, because the browser timing window cannot send a handshake message, the portal server can set the user's online status to offline and send a offline message to the BRAS after detecting the handshake timeout. This can avoid the problem that the network side still charges the user due to the network interruption that prevents the user from using the data service.
- the handshake mechanism between the small window and the portal server is also implemented through the heartbeat function of the browser.
- the small window of the client is often closed on the display or replaced by another page due to the abnormal operation of the browser.
- the user cannot see the small window, and therefore cannot take the initiative to go offline. If the user wants to go offline actively, he must log in to the portal server again and be authenticated, so that a small window will appear again on the client, and then the user can click the offline button to actively disconnect from the broadband network. Obviously, this will cause great inconvenience to users.
- the existing portal server uses some inherent mechanisms of the browser. This process is complicated and the function is unstable. In addition, when there are many browser versions, the processing of the portal server is also prone to errors.
- the main object of the present invention is to provide an implementation in a broadband data intelligent network.
- a method of a small window on a client side which can solve the problem of inconvenience of a user in using data services in the prior art.
- a method for implementing a small window of a client in a broadband data intelligent network includes: a. Setting a first module and a second module in a client in advance;
- the first module obtains the IP address of the client, and sends it to the portal server along with the authentication information entered by the user;
- the first module After receiving the authentication pass message from the portal server, the first module starts the operation of the second module;
- the second module generates a small window for displaying user access information and providing user operation buttons.
- the method further includes establishing a shared memory on the client side where both the first module and the second module can perform read and write operations.
- the first module writes information related to the user's use of data services into the shared memory
- the second module retrieves the information related to the user's use of data services from the shared memory.
- the user access information is read from the information, and the user access information is displayed in a small window.
- step b further includes the first module sending the obtained local IP address to the integrated service control center ISCC through the portal server to request user information. If the ISCC judges that the user has not been successfully authenticated, the portal server generates a user name and password for the user to enter Authentication page, otherwise the first module directly starts the operation of the second module.
- step d a step of using a small window to control the user's use of data services is further included.
- This step includes:
- the second module periodically sends a handshake message to the portal server
- the portal server checks whether the user logout reason in the user record in the database is null, and if so, returns a handshake response message indicating success to the second module; otherwise returns a handshake response message indicating failure to the second module; After receiving the handshake response message, the second module continues to periodically send a handshake message to the portal server for the handshake response message indicating success; for the handshake response message indicating failure, the second module stops the user from using the data service, and in a small window Displays the reason why the user is offline.
- the method further comprises, after receiving the forced offline from the ISCC or receiving a message from the client that the user has taken the initiative to offline, setting the user offline reason in the user record in the database to a non-null value.
- the method further includes re-sending the handshake message after the second module does not receive a handshake response message from the portal server within a preset time, if the handshake message is not received after resending the handshake message a predetermined number of times In response to the message, the second module displays a network connection exception in a small window.
- the method further includes that the portal server looks up the user record in the online user linked list after receiving the handshake message from the client, and if the user record is found, further checking whether the reason why the user of the user record in the database is offline is If no user record is found, a message to create user information is returned to the second module. After receiving the message, the second module sends a handshake message to create the user information to the current portal server.
- the method further comprises: before sending the handshake message, determining whether the data service is accessed through web authentication, and if so, performing the step of sending the handshake message, otherwise displaying the information directly in a small window.
- the method further comprises: the portal server scans the online user data linked list at a fixed time, and if the handshake message from the client is not received, the user information is put into the special delete queue; then the queue to be deleted is traversed to the user Send an offline request, and then delete the current user data from the online user data list.
- the method may further include setting the number of handshake failures in advance, and further changing the number of handshake failures if no handshake message is received from the client.
- the number of handshake failures is equal to a preset maximum value, the user information is placed in a queue to be deleted. And sending to the user Before the offline request can be further judged whether it is necessary to send a offline request to the user, if yes, perform the step of sending the offline request; otherwise, the current user data is directly deleted from the online user data list.
- the judgment of whether the offline request is required to be sent to the user is to compare whether the IP address of the portal server of the user information in the database is the same as its own IP address.
- the present invention first provides a first module and a second module.
- the first module After the IP address successfully authenticates the user, the first module starts the operation of the second module, and then the second module generates a small window, and displays the user access information and provides the user operation button in the small window.
- the present invention implements a small client window by means of the first module and the second module working in a cooperative manner. This implementation is independent of the operating system and the existing browser software, thus avoiding the use of a browser in the prior art. It is easy to generate a small window. The small window is closed or covered abnormally, which avoids causing trouble to the user.
- a shared memory that can be read and written by the first module and the second module is set on the client, and all information related to the user's access to the data intelligent network is written into the shared memory. Since the information in the shared memory does not exist in the form of a file, it can avoid staff loss caused by user's misoperation, and effectively prevent attacks by network hackers, etc., and greatly improve the security of data use.
- the first module of the present invention After the first module of the present invention obtains the local IP address, it sends the obtained IP address to the ISCC through the portal server to request user information. If the ISCC judges that the user has not been successfully authenticated, the portal server generates an authentication page for the user to enter a username and password Otherwise, the first module directly starts the operation of the second module. This can effectively ensure that only one user can log in to the portal server at a time, and the implementation method is simple and stable.
- the present invention adds a processing flow for the cluster service in a fine-grained manner to the processing flow of the client and the portal server, for example, when traversing the queue to be deleted, the portal server can compare the portal server IP address of the user information in the database Is it the same The IP address is the same to determine whether to send offline messages.
- the portal server finds that it has not received a handshake message from the client, it is found in the database shared by multiple portal servers that the client is sending a handshake message to another portal server.
- Send a offline message to the BRAS but directly delete the user information in its own queue to be deleted. In this way, since no offline message is received from the portal server, the user client can normally use the data service through another portal server.
- these special processing procedures ensure that the present invention can well support cluster services.
- Figure 1 is the basic structure diagram of the existing broadband data intelligent network.
- Fig. 2 is an overall flowchart of the present invention.
- FIG. 3 is a flowchart of controlling a user to use a data service through a small window.
- FIG. 4 is the processing flow of the portal server when the network connection is abnormal.
- a first module and a second module are set on the client, where the first module is configured to obtain a local IP address when a user accesses the portal server, and start the second module after the portal server is successfully authenticated. Operation of the module; the second module is used to pop up a small window on the client and display the user's access information in the small window, such as the user's access status, Internet time, access type and access user name, etc.
- a user operation button is provided in a small window, which can specifically include "login to the portal server with an access user name", "login to the portal server with another account", and "offline” .
- a first module and a second module are first set on a user client.
- the first module is configured to obtain a local IP address when a user accesses the portal server, and start the second module after the portal server is successfully authenticated.
- Module operation The second module is used to pop up a small window on the client, and display the user's access information in the small window, while providing user operation buttons in the small window.
- step 202 when the monthly household wants to access the broadband data intelligent network, it accesses the corresponding address of the portal server, starts the first module, and obtains the IP address of the client by the first module. After obtaining the IP address correctly, the portal monthly server is on the client Push an authentication page. The user enters the user name and password on the authentication page, and then clicks Connect to the network to request that the user be a legitimate user.
- the username and password here can be collectively referred to as-eyelid identification information.
- the portal server sends an authentication request to the BRAS, which contains the user name and password information of the user and the IP address information of the client.
- BRAS then reports the authentication request to ISCC.
- step 204 the ISCC verifies whether the user is a legal user according to the user name, password, and IP address, and if it is a legal user, sends an authentication success response to the BRAS. BRAS then sends a successful authentication response to the portal server. The portal server sends a message indicating that the user authentication is successful to the first module of the user client.
- step 205 after receiving the authentication success response from the portal server, the first module starts the operation of the second module, and sends a message that the user has successfully logged in to the second module.
- the second module In step 206, the second module generates a small window and displays it on the display screen of the client. At the same time, the user access information is displayed in a small window, and a user operation button is provided in the small window. So far, the present invention successfully implements a small window on the user client, and this implementation manner is implemented through the cooperative work of the first module and the second module. Since the implementation manner of the present invention is independent of the operating system and the existing browser software, it avoids the situation that the small window that is easily generated by the browser in the prior art is prone to be closed or covered abnormally. Users go online to cause trouble.
- the first module and the second module in the present invention may be implemented in the form of a circuit, or may be implemented in the form of software.
- the first module can be a control, such as an ActiveX control
- the second module can be a client application.
- the software implementing the first module may be stored on the portal server, and the user downloads and runs the software from the portal server when the user accesses the broadband data network for the first time.
- the small client window can have the function of automatically checking for the updated version, for example, writing the corresponding version information in a configuration file of the portal server, obtaining the version information as a control of the first module, and comparing the version with the client. If the version of the client is not the latest version, go to the portal server to download the latest program again.
- a shared memory for information related to the use of the data service by the user may be further set in the memory of the user client.
- the first module and the second module of the present invention may both Shared memory for read and write operations.
- the relevant information here includes information such as user name, local IP address, Internet time, and access method.
- the authentication page may not be displayed directly when the user logs in to the portal server.
- the first module sends the obtained local IP address to the ISCC through the portal server.
- the ISCC judges that the J3 ⁇ 4 user has been successfully authenticated
- the user can log in to the portal server directly; if the ISCC judges that the user is not authenticated If successful, then an authentication page is generated as described in step 202.
- the client will not generate an authenticated page, and in particular, the user will not be authenticated again, thereby ensuring that only one user at the same time can successfully authenticate.
- the second module determines whether the user accesses the Internet through web authentication.
- the message indicating that the user authentication succeeds is sent by the portal server to the first module, and includes information about a user's Internet access mode. This information is stored in the shared memory by the first module, so the second module can determine the user's Internet access mode by reading the information in the shared memory.
- the small window will display basic information about Internet access, such as the length of time spent on the Internet, but will not provide a "Login to the portal server with an access user name” button, and it will display "Offline” that is different from web authentication. "Button” to exit, button.
- step 316 display the information corresponding to the access method in a small window, and then follow the steps The existing processing flow corresponding to the access method is processed.
- the second module sends a handshake message. If it is started for the first time, a message to create user information is sent. It is not the first time to start. If the return code of the ordinary handshake message is a message that needs to send user information, it will also send a message that creates user information.
- the handshake message contains information of the message type, and the message type can indicate that the handshake message is a normal handshake message, a message to create user information, or an offline message.
- step 303 after receiving the handshake message, the portal server determines whether the handshake message is a message indicating creation of user information. If so, in step 304, the database Add the record of the user to the user, and add the record of the user to the online user list of the portal server, and then execute step 309. If it is a normal handshake message, in step 305, the user is looked up in the online user list, and it is determined whether the user is found. If the user is not found, a message requiring creation of user information is returned to the second module of the user client in step 306. If the user is found, go to step 307.
- step 307 the portal server determines whether the reason why the user is offline is empty. If so, step 308 is performed, otherwise step 309 is performed. The reason why the user is offline is recorded in the corresponding record of the user in the online user list. If the portal server receives a message from the BRAS that the user has been forcibly offline, set the reason for the user to be offline forcibly, otherwise leave the initial null value.
- step 308 the portal server clears the user record in the data bank and sends a handshake response message indicating the failure to the user to the second module.
- the portal server clears the number of user handshake failures to zero, and then returns a successful handshake response message to the second module.
- the number of handshake failures is recorded in the portal server's memory, and its initial value is zero. If the portal server does not receive a turbulent handshake message from the user client when it arrives at a specified time, the handshake failure times are incremented by one.
- step 310 the second module determines whether a handshake response message is received from the portal server within a predetermined time, and if so, executes step 311, otherwise executes step 314.
- the second module clears the failure times.
- the number of failures here is used to indicate the number of times that the second module has not received the handshake response message within a specified time, and its initial value is zero. As will be explained in detail later, each time it is judged that no handshake response message is received, the number of failures will increase by one.
- step 312 the second module determines whether the handshake response message indicates success, and if so, executes step 302 again after a predetermined time interval, that is, re-sends to the portal server.
- a handshake message If the handshake response message is a message requiring user information creation, a special handshake message indicating the creation of user information is sent again in step 302. If the second module judges that the handshake response message indicates success, but there is a reason to go offline (indicating that the user has been forced to go offline), or the second module does not receive a handshake response message from the portal server within a preset time, the second The module stops sending the handshake message in step 313, displays the reason for the user offline in a small window, and closes the small window after the user determines.
- the handshake response message contains a response result value, such as a value indicating success or failure, and when it indicates failure, it may further include the reason for the failure.
- step 314 if it is determined that the handshake response message is not received within a predetermined time, the second module sets a waiting day t for sending the next handshake message.
- the waiting time here is longer than the interval between sending handshake messages under normal circumstances. short.
- the second module increments the number of handshake failures by one.
- step 315 the second module determines whether the number of failures is greater than a preset maximum number of failures. If so, step 313 is performed, that is, the user stops using the data service and informs the user of the reason for offline in a small window. If the maximum number of failures has not been reached, step 302 is performed again, and a handshake message is sent to the portal server again after a short waiting time.
- the above process includes processing when the network terminates the user's use of the data service, processing when the user is actively offline, and processing when the network is interrupted and the user is offline.
- the ISCC on the network side finds that the user cannot continue to use the data service for some reason, the ISCC sends a message to the BRAS, and then the BRAS sends a message to the portal server, and the portal server takes the user in the user record offline.
- the reason is set to a non-null value, so that when the next handshake message arrives, the portal server returns a response message indicating failure to the client after detecting the non-null value, and carries the reason for offline, so that the client application side receives After the handshake response message, it is determined that the response is a failure in step 312, so that the user uses the data service in step 313 and closes the small window.
- the second module sends a special handshake message, that is, the message type is set to indicate a "online message”
- the portal server interacts with the BRAS, and returns the offline success message.
- the client application determines that the user does not continue to access the Internet in step 312, and then terminates the user's use of the data service in step 313 and closes the small window.
- the second module determines in step 310 that the handshake response message from the portal server is not received within a predetermined time, it indicates that the network connection is faulty, and the second module may perform step 313 at this time. This will take the user offline and close the small window. Of course, it is also possible to set the maximum number of failures and resend the handshake message as shown in the figure. In actual situations, this process can be added to delete as needed.
- FIG. 4 shows the processing flow of the portal server when the network connection is abnormal.
- the portal server scans the online user data linked list in the memory every other time interval;
- step 402 the portal server determines whether the number of handshake failures of the user is less than the maximum. If yes, go to step 403; otherwise, go to step 404. As mentioned before, if the portal server normally receives the user's handshake message, it will clear the number of handshake failures, so step 403 will not be performed in this case. In other words, the purpose of this judgment is to check whether there is an abnormal network connection.
- step 403 increase the number of handshake failures of the user by one.
- step 404 the user information is placed in a queue to be deleted.
- step 405 it is determined whether the scan is completed, that is, whether the entire online user data link list is traversed. If so, step 406 is performed, otherwise step 401 is performed again, that is, the next user information is searched.
- step 406 the portal server traverses the queue to be deleted.
- the portal server determines whether an offline message needs to be sent. This step is In order to support the cluster business, in the cluster business, multiple portal servers can provide data services to the same user, so it is possible that the current portal server judges that it has not received the user's handshake message for a long time, but the user may pass another Portal server to connect data services. In this way, the current portal server determines whether there is another portal server providing services to users by searching for records in the database. If so, step 408 is not performed, that is, no offline request is sent to the user, and step 409 is directly performed, that is, The current user data is deleted from the online user list.
- step 408 is performed, that is, a offline request is sent to the BRAS, and then step 409 is performed.
- it is specifically determined whether another portal server provides services to the user by comparing whether the IP address of the portal server of the user information in the database is the same as its own IP address. If they are the same, it is considered that there is no other portal server providing services to the user, and if they are not the same, it is considered that there is another portal server providing services to the user.
- step 410 it is determined whether the traversal of the queue to be deleted is completed. If yes, end this process. Otherwise, step 406 is performed again, that is, it is determined whether the next user information needs to send an offline message.
- the portal server in FIG. 3 returns a message that needs to create user information and a small window sends a message to the portal server to create user information that can well support cluster services .
- the portal server in FIG. 3 returns a message that needs to create user information and a small window sends a message to the portal server to create user information that can well support cluster services .
- the second portal server will find its own memory There is no record of the user in the online user linked list saved in, so a message to the client that needs to create user information is returned.
- the small window of the client After receiving the message, the small window of the client sends a create user information message to the second portal server. In this way, the second portal server can continue to provide data access services to users.
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP05738138A EP1732267B1 (en) | 2004-03-24 | 2005-03-24 | Method and system for achieving a small window at a client-side in a broadband intelligent network |
AT05738138T ATE456888T1 (de) | 2004-03-24 | 2005-03-24 | Verfahren und system zur erlangung eines kleinen fensters auf kundenseite in einem intelligenten breitbanddatennetz |
DE602005019141T DE602005019141D1 (de) | 2004-03-24 | 2005-03-24 | Verfahren und System zur Erlangung eines kleinen Fensters auf Kundenseite in einem intelligenten Breitbanddatennetz |
US11/510,177 US7788320B2 (en) | 2004-03-24 | 2006-08-25 | Method, device and system for producing small window at client in broadband data intelligent network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB2004100303941A CN100344099C (zh) | 2004-03-24 | 2004-03-24 | 一种在宽带数据智能网中实现客户端小窗口的方法 |
CN200410030394.1 | 2004-03-24 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/510,177 Continuation US7788320B2 (en) | 2004-03-24 | 2006-08-25 | Method, device and system for producing small window at client in broadband data intelligent network |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005096550A1 true WO2005096550A1 (fr) | 2005-10-13 |
Family
ID=35046804
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2005/000374 WO2005096550A1 (fr) | 2004-03-24 | 2005-03-24 | Procede de creation d'une petite fenetre du cote client dans le reseau intelligent de donnees a large bande |
Country Status (6)
Country | Link |
---|---|
US (1) | US7788320B2 (zh) |
EP (1) | EP1732267B1 (zh) |
CN (1) | CN100344099C (zh) |
AT (1) | ATE456888T1 (zh) |
DE (1) | DE602005019141D1 (zh) |
WO (1) | WO2005096550A1 (zh) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB0420675D0 (en) * | 2004-09-17 | 2004-10-20 | Ibm | Method and software tool for installation of portlets into a client platform |
KR101079592B1 (ko) * | 2006-11-03 | 2011-11-04 | 삼성전자주식회사 | 디스플레이장치 및 그 정보갱신방법 |
US20080177869A1 (en) * | 2007-01-24 | 2008-07-24 | Christopher Jensen Read | System and method for configuring consumer electronics device for home network using the internet |
US20080229370A1 (en) * | 2007-03-13 | 2008-09-18 | Zustak Frederick J | TV-centric system |
US20090055534A1 (en) * | 2007-08-22 | 2009-02-26 | Sony Corporation | Tiered network structure for large ce device populations |
CN107517236B (zh) | 2016-06-17 | 2021-06-15 | 斑马智行网络(香港)有限公司 | 一种用于物联网的事件处理方法、装置和设备 |
CN107517238A (zh) * | 2016-06-17 | 2017-12-26 | 阿里巴巴集团控股有限公司 | 一种用于物联网的智能设备控制方法、装置和设备 |
CN107147643A (zh) * | 2017-05-10 | 2017-09-08 | 武汉票据交易中心有限公司 | 一种客户端登录方法 |
CN112714123A (zh) * | 2020-12-27 | 2021-04-27 | 杭州迪普科技股份有限公司 | 上网方法、装置及电子设备 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6240091B1 (en) | 1997-07-14 | 2001-05-29 | Nokia Telecommunications Oy | Implementation of access service |
US20020152242A1 (en) * | 2001-04-12 | 2002-10-17 | Meyer Kristin S. | System for monitoring the usage of intranet portal modules |
KR20030043055A (ko) * | 2001-11-26 | 2003-06-02 | 삼성전자주식회사 | 디지털 가입자 회선 망에서 공지사항 안내 서비스 시스템 |
JP2003219197A (ja) * | 2002-01-18 | 2003-07-31 | Sega Toys:Kk | 画像生成装置、画像生成方法及びプログラム |
EP1349062A2 (en) * | 2002-03-28 | 2003-10-01 | Seiko Epson Corporation | Download management system |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
SE9900710L (sv) * | 1999-02-25 | 2000-08-26 | Ericsson Telefon Ab L M | Metod och anordning som avser kommunikationsnätverk för mobiltelefoner |
US7111060B2 (en) * | 2000-03-14 | 2006-09-19 | Aep Networks, Inc. | Apparatus and accompanying methods for providing, through a centralized server site, a secure, cost-effective, web-enabled, integrated virtual office environment remotely accessible through a network-connected web browser |
US20020129096A1 (en) * | 2001-02-14 | 2002-09-12 | Mansour Peter M. | Platform-independent distributed user interface client architecture |
CN1180594C (zh) * | 2001-09-29 | 2004-12-15 | 华为技术有限公司 | 互联网个人号码业务中的认证与计费方法 |
CN1152333C (zh) * | 2002-07-31 | 2004-06-02 | 华为技术有限公司 | 基于认证、计费、授权协议的门户认证实现方法 |
US8321584B2 (en) * | 2003-04-04 | 2012-11-27 | Ellacoya Networks, Inc. | Method and apparatus for offering preferred transport within a broadband subscriber network |
-
2004
- 2004-03-24 CN CNB2004100303941A patent/CN100344099C/zh not_active Expired - Lifetime
-
2005
- 2005-03-24 EP EP05738138A patent/EP1732267B1/en active Active
- 2005-03-24 AT AT05738138T patent/ATE456888T1/de not_active IP Right Cessation
- 2005-03-24 WO PCT/CN2005/000374 patent/WO2005096550A1/zh active Application Filing
- 2005-03-24 DE DE602005019141T patent/DE602005019141D1/de active Active
-
2006
- 2006-08-25 US US11/510,177 patent/US7788320B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6240091B1 (en) | 1997-07-14 | 2001-05-29 | Nokia Telecommunications Oy | Implementation of access service |
US20020152242A1 (en) * | 2001-04-12 | 2002-10-17 | Meyer Kristin S. | System for monitoring the usage of intranet portal modules |
KR20030043055A (ko) * | 2001-11-26 | 2003-06-02 | 삼성전자주식회사 | 디지털 가입자 회선 망에서 공지사항 안내 서비스 시스템 |
JP2003219197A (ja) * | 2002-01-18 | 2003-07-31 | Sega Toys:Kk | 画像生成装置、画像生成方法及びプログラム |
EP1349062A2 (en) * | 2002-03-28 | 2003-10-01 | Seiko Epson Corporation | Download management system |
Also Published As
Publication number | Publication date |
---|---|
DE602005019141D1 (de) | 2010-03-18 |
ATE456888T1 (de) | 2010-02-15 |
US7788320B2 (en) | 2010-08-31 |
EP1732267B1 (en) | 2010-01-27 |
EP1732267A4 (en) | 2007-03-14 |
US20070055750A1 (en) | 2007-03-08 |
CN1674522A (zh) | 2005-09-28 |
EP1732267A1 (en) | 2006-12-13 |
CN100344099C (zh) | 2007-10-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2005096550A1 (fr) | Procede de creation d'une petite fenetre du cote client dans le reseau intelligent de donnees a large bande | |
US20030069848A1 (en) | A User interface for computer network management | |
US6081508A (en) | Remote computer communication | |
EP1700230B1 (en) | Dynamic timeout in a client-server system | |
KR101099238B1 (ko) | 외부 컴퓨터를 내부 컴퓨터에 원격으로 접속하기 위한 시스템 및 방법 | |
JP4734592B2 (ja) | クライアントリダイレクトによるプライベートネットワークへの安全なアクセス提供方法およびシステム | |
US6799147B1 (en) | Enterprise integrated testing and performance monitoring software | |
US8291268B2 (en) | Apparatus, system, and method to provide alert notification with reconcile actions | |
US7257741B1 (en) | Methods and systems for communications device troubleshooting | |
US20110138446A1 (en) | System and method for providing user authentication and identity management | |
CN101841537A (zh) | 一种基于协议代理实现对文件共享访问控制方法及系统 | |
CA2415868A1 (en) | Systems and methods for authenticating a user to a web server | |
US20010042202A1 (en) | Dynamically extendible firewall | |
US20070180126A1 (en) | Systems and methods for establishing and validating secure network sessions | |
US6959392B1 (en) | Information providing system and method for providing information | |
US7281027B2 (en) | Distributed processing system and network monitoring system | |
US7392540B1 (en) | Methods and systems for customer premises remote collaboration facility | |
US7426727B2 (en) | Delayed uploading of user registration data | |
Cisco | Release Notes for the PIX Firewall Manager Version 4.3(2)g | |
Cisco | Release Notes for the PIX Firewall Manager Version 4.3(2)f | |
Cisco | Release Notes for the PIX Firewall Manager Version 4.3(2)h | |
Cisco | CiscoSecure ACS 2.2(3) for UNIX Release Notes | |
Cisco | CiscoSecure ACS 2.2(3) for UNIX Release Notes | |
Cisco | PIX Firewall Manager Version 4.2(3) Release Notes | |
Cisco | Release Notes for CiscoSecure ACS 2.2.2 for UNIX |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005738138 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2005738138 Country of ref document: EP |