CN103188311B - Client Agent navigation system and method - Google Patents
Client Agent navigation system and method Download PDFInfo
- Publication number
- CN103188311B CN103188311B CN201110457179.XA CN201110457179A CN103188311B CN 103188311 B CN103188311 B CN 103188311B CN 201110457179 A CN201110457179 A CN 201110457179A CN 103188311 B CN103188311 B CN 103188311B
- Authority
- CN
- China
- Prior art keywords
- pid
- client
- service
- client agent
- core
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 29
- 230000011664 signaling Effects 0.000 claims abstract description 112
- 238000001824 photoionisation detection Methods 0.000 claims description 192
- 230000004044 response Effects 0.000 abstract description 12
- 239000003795 chemical substances by application Substances 0.000 description 91
- 230000008569 process Effects 0.000 description 9
- 238000013507 mapping Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000006866 deterioration Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a kind of Client Agent navigation system and method, can effectively reduce the pressure of global index's service, improve the response performance of system. A kind of Client Agent navigation system that the embodiment of the present invention provides comprises: kernel service, from local cache or obtain the PID of client from the request from client, this PID comprises access service address and Client Agent address designation, this Client Agent address designation is indicated Client Agent side-play amount with respect to first address in access service, and, know access service according to the access service address in obtained PID, be sent to this access service after PID is added in signaling; Access service, obtains Client Agent according to the Client Agent address designation location of PID in described signaling, starts the Client Agent navigating to and removes the PID in signaling; The Client Agent navigating to, is forwarded to client by the signaling of removing after PID.
Description
Technical Field
The invention relates to the technical field of internet communication, in particular to a client proxy positioning system and a client proxy positioning method.
Background
In many applications of the internet, in order to facilitate processing of a client's request, a client agent is generally provided at an access layer of a service, and interaction between the client and a core service on a server is realized through the client agent.
In a large-scale internet system, in order to avoid single point of failure and offload of service pressure, multiple access services are set in an access layer, and each access service may generate multiple client proxies. Under the structure, after a client logs in an access service and the access service generates a client agent of the client, the client registers on a global index service to generate a mapping relation between the client and the access service. When the core service wants to send the signaling to the client, the client agent of the client needs to be found, and the specific method is as follows:
the core service acquires the address of the access service where the client agent is located according to the mapping relation stored in the global index service, and sends a signaling to the access service under the address; then, the access service finds out the client agent of the client in the mapping list of the access service, the client agent issues a signaling to the client, and the client is informed of corresponding information through the signaling.
The existing client proxy query scheme has at least the following defects:
when the access amount is large, the core service needs to frequently send requests to the global index service, so that the system burden is overlarge, and the response speed of the system is reduced; moreover, when the access service searches the client agent in its own mapping list, it adopts a mode of sequentially searching in the mapping list item by item through the client Identification (ID), so that the query efficiency is low, and the deterioration of the system response performance is aggravated.
Disclosure of Invention
The invention provides a client agent positioning system and a client agent positioning method, which aim to solve the problems of low query efficiency and poor system performance in the existing scheme.
In order to achieve the purpose, the embodiment of the invention adopts the following technical scheme:
the embodiment of the invention provides a client agent positioning system, which comprises an access service, a client agent and a core service,
the core service acquires the PID of the client from a local cache or a request from the client, wherein the PID comprises an access service address and a client agent address identifier, the client agent address identifier indicates the offset of the client agent in the access service relative to a head address, and the core service acquires the access service according to the access service address in the acquired PID, adds the PID to a signaling and then sends the signaling to the access service;
the access service is used for positioning according to the client agent address identifier of the PID in the signaling to obtain a client agent, starting the positioned client agent and removing the PID in the signaling;
and the positioned client agent forwards the signaling with the PID removed to the client.
The embodiment of the invention also provides a client agent positioning method, which comprises the following steps:
obtaining a user login identity unique identification PID of the client from a local cache of the core service or from a request from the client, wherein the PID comprises an access service address and a client agent address identification, the client agent address identification indicates an offset of the client agent in the access service relative to a first address,
acquiring an access service according to an access service address in the acquired PID, adding the PID to a signaling, and then sending the signaling from the core service to the access service;
positioning according to the client agent address identifier of the PID in the signaling to obtain a client agent, starting the positioned client agent by using the access service and removing the PID in the signaling;
and forwarding the signaling with the PID removed to the client through the positioned client agent.
The embodiment of the invention has the beneficial effects that:
the embodiment of the invention obviously reduces the access request to the global index service by setting the unique identification PID of the user login identity and maintaining the PID in the local cache of the core service or obtaining the PID from the client request; in addition, the embodiment of the invention directly sets the address offset of the client agent in the PID, thereby improving the information query efficiency.
The embodiment of the invention provides a method for quickly positioning a user agent, which can effectively reduce the pressure of global index service and improve the response performance of a system.
Drawings
Fig. 1 is a flowchart illustrating a working process of a client-side proxy location system according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating a working process of another client-side proxy location system according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a working procedure of a client-side proxy location system according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating a working procedure of a client-side proxy location system according to an embodiment of the present invention;
fig. 5 is a flowchart of a client agent location method according to a second embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
An embodiment of the present invention provides a client agent positioning system, referring to fig. 1, where the system includes an access service, a client agent, and a core service, and the specific workflow is as follows:
1: the core service obtains a user login identity unique identifier (PID) of the client.
According to different core service types, the specific manner of acquiring the PID by the core service is different, and may include the following two operations:
1 a: and the core service, such as the core service with the state, acquires the PID of the client from the local cache.
In step 1a, the stateful core service searches for a PID in the local cache according to the client identifier (UserId), and before searching, the core service may obtain the UserId through a request from the client. The stateful core service maintains a correspondence between the client identifier and the PID, which may be a hash mapping relationship.
1 b: a core service, such as a stateless core service, obtains the client's PID from a request from the client.
The state of the core service can be judged by whether two requests from the same initiator have a context relationship at the server side. In the case of stateful core services, the server typically stores information about the requests, and each request may use the information of the previous request by default. While the stateless core service cannot store the relevant information, the processing information that the server can process must be all from the information carried by the request and the common information that is stored by other servers and can be used by all requests. Therefore, in this embodiment, different PID acquisition manners are set for different types of core services.
The PID includes an access service address and a client agent address identifier indicating an offset of the client agent in the access service with respect to the head address. The first address is the first address of the client agent stored in the access service. Further, the PID may further include timestamp information.
2: the core service acquires the access service according to the access service address in the acquired PID, adds the PID to the signaling and then sends the signaling to the access service.
3: and the access service locates according to the address identifier of the client agent of the PID in the signaling to obtain the client agent.
4: the access service initiates or invokes the located client agent and removes the PID in the signaling.
5: the client agent forwards the signaling to the client.
And the positioned client agent forwards the signaling with the PID removed to the client.
The following describes a specific interaction manner of each device or function in this embodiment in detail with reference to fig. 2.
Fig. 2 mainly illustrates a scenario in which the core service is a stateful core service, which includes a registration process of the client and a process in which the core service issues a signaling to the client.
1: the client sends a login request to the access service.
2: the access service generates a client agent and PID for the client.
Each login of the access service to each client generates a client agent and a PID corresponding to the client, wherein the PID comprises an access service address, a client agent address Identifier (ID) and timestamp information, and the timestamp information indicates the creation time of the PID, namely the login time of the client.
The access service also adds timestamp information to the client agent, and the timestamp information of the client agent and the timestamp information in the PID are kept consistent in one login of one client.
Further, in this embodiment, the access service stores the generated PID in the form of an array, where an array element in the array represents a PID, and the client proxy address identifier in the PID is formed by a label of the array element. Namely, the client agent address identifier in the PID indicates address offset information relative to the initial address, and the client agent can be directly positioned by utilizing the offset information, so that the query efficiency is improved; and the embodiment is realized by adopting an array and an array label, and the operation is simple and convenient.
3: the access service sends a registration request to the global index service.
The access service adds the PID in the registration request and sends the registration request to the global index service, and the global index service receives and stores the PID of the client.
After the registration is successful, the global index service returns a registration success message to the access service, and the access service returns a login success message to the client.
4: the access service sends the PID to the core service (stateful core service).
5: the core service saves the PID in a local cache.
For the core service with the state, a local cache container is arranged on the core service and used for storing the PID of the client, so that the access frequency of the core service to the global index service is reduced, the pressure of the global index service is reduced, and the performance of the system is improved.
The registration process of the client under the stateful core service is completed through the above steps 1 to 5. For the scenario of stateless core services, the difference is that steps 4 and 5 need not be performed compared to the registration procedure of the client under the stateful core services.
6: the core service looks up the PID from the local cache.
When the core service needs to send signaling to the client, the core service first finds the PID from the local cache.
Further, the core service obtains the PID of the client from the local cache according to the learned client identifier (UserId). When the core service executes different services, the specific way of acquiring the UserId is also different, for example, for a friend adding service in instant messaging, the core service can acquire the UserId of the client from a friend list stored by the server; for the interactive service of two clients, the core service can acquire the UserId of the other client from the message of the one client, and send a signaling to the other client by using the UserId.
7: the core service sends signaling to the access service.
The core service obtains the access service address in the searched PID, obtains the currently used access service, adds the searched PID in a signaling (such as a service request signaling), and then sends the signaling to the access service.
Further, in this embodiment, the core service adds the PID to the signaling header of the signaling.
8: a client agent on the access service forwards the signaling to the client.
After receiving the signaling sent by the core service, the access service searches the used client agent according to the client agent address ID in the PID in the signaling. The access service removes the PID in the signaling, e.g., in the access service removal signaling header, and the signaling is forwarded by the client agent to the client.
After receiving the signaling, the client returns response information to the access service through the client agent, and the access service sends the response information to the core service to inform the core service that the signaling is successfully issued.
The signaling issuing process from the stateful core service to the client is completed through the above steps 6 to 8. For the stateless core service, the difference is mainly that, in step 6, the stateless core service does not look up the PID from the local cache, but obtains the PID from the request sent by the client. The client needs to receive a request from the client before signaling is sent, and when the client sends the request to the core service through a client agent on the access service, the access service adds the PID into the request, so that the core service can acquire the PID when receiving the request.
Referring to fig. 3, another flow chart of the core service issuing the signaling to the client is shown.
Fig. 3 is still illustrated by taking a scenario in which the core service is a stateful core service as an example, and the registration process of the client is omitted here. For stateless core services, since the PID is reported to the core service along with the request of the client, and the PID is an effective PID used in the current operation, the processing manner shown in fig. 3 is not generally needed.
1: the core service looks up the PID from the local cache.
When the core service needs to send signaling to the client, the core service first finds the PID from the local cache.
Further, the core service obtains the PID of the client from the local cache according to the learned client identifier (UserId). When the core service executes different services, the specific way of acquiring the UserId is also different, for example, for a friend addition service in instant messaging, the core service can acquire the UserId of the client from a friend list in a request sent by the client; for the interactive service of two clients, the core service can acquire the UserId of the other client from the request message of the one client, and send a signaling to the other client by using the UserId.
2: the core service sends signaling to the access service.
The core service obtains the access service address in the searched PID, obtains the currently used access service, adds the searched PID in a signaling (such as a service request signaling), and then sends the signaling to the access service.
Further, in this embodiment, the core service adds the PID to the signaling header of the signaling.
3: the access service determines whether the PID is valid.
In one case, if the client logs in the same access service for multiple times within a period of time, the PID of the client stored in the access service is inconsistent with the PID of the client stored in the core service, and at this time, the timestamp information in the PID is used to determine whether the PID is valid, that is, whether the PID is a PID that should be used in the current operation. And when the access service finds the client agent according to the client agent address identifier of the PID in the signaling, comparing whether the timestamp information in the PID is consistent with the timestamp information of the found client agent, if so, taking the found client agent as the positioned client agent, and if not, executing the step 4.
In another case, the client logs in the access service 1, exits from the access service 1 after a period of time, and logs in the access service 2, and the core service stores the PID of the client when logging in the access service 1, and the access service 1 does not have a client agent generated for the client, and if the client agent cannot be found according to the client agent address identifier of the PID in the signaling, it is determined that the PID is invalid, and step 4 is performed.
4: the access service sends an acquisition request to the core service, requesting the core service to reacquire the PID.
5: and the core service acquires a new PID from the global index service according to the acquisition request.
6: the global index service returns the new PID to the core service.
7: the core service adds the new PID into the signaling, such as the service request signaling, and sends the signaling to the access service.
8: a client agent on the access service forwards the signaling to the client.
After receiving the signaling sent by the core service, the access service searches the used client agent according to the client agent address ID in the PID in the signaling. The access service removes the PID in the signaling, e.g., in the access service removal signaling header, and the signaling is forwarded by the client agent to the client.
After receiving the signaling, the client returns response information to the access service through the client agent, and the access service sends the response information to the core service to inform the core service that the signaling is successfully issued.
Referring to fig. 4, another flow chart of the core service issuing the signaling to the client is shown.
Fig. 4 is still illustrated by taking a scenario in which the core service is a stateful core service as an example, and the registration process of the client is omitted here. For stateless core services, since the PID is reported to the core service along with the request of the client, and the PID is an effective PID used in the current operation, the processing manner shown in fig. 4 is not generally needed.
1: the core service looks up the PID from the local cache.
When the core service needs to send signaling to the client, the core service first finds the PID from the local cache.
Further, the core service obtains the PID of the client from the local cache according to the learned client identifier (UserId).
2: the access service sends an acquisition request to the core service, requesting the core service to reacquire the PID.
And when the core service cannot find the PID, sending a request to the global index service.
When the core service cannot find the PID in the local cache, for example, if the current core service is inconsistent with the core service associated with the client login, the current core service cannot find the PID of the client in the local cache, and at this time, the PID is obtained from the global index service.
3: and the core service acquires a new PID from the global index service according to the acquisition request.
4: the core service sends signaling to the access service.
The core service obtains an access service address in the newly acquired PID, acquires the currently used access service, adds the searched PID in a signaling (such as a service request signaling), and then sends the signaling to the access service.
Further, in this embodiment, the core service adds the PID to the signaling header of the signaling.
5: a client agent on the access service forwards the signaling to the client.
After receiving the signaling sent by the core service, the access service searches the used client agent according to the client agent address ID in the PID in the signaling. The access service removes the PID in the signaling, e.g., in the access service removal signaling header, and the signaling is forwarded by the client agent to the client.
After receiving the signaling, the client returns response information to the access service through the client agent, and the access service sends the response information to the core service to inform the core service that the signaling is successfully issued.
In the embodiment of the invention, the unique identification PID of the user login identity is set, and the PID is maintained in the local cache of the core service or is obtained from the client request, so that the access request to the global index service is obviously reduced; in addition, the embodiment of the invention directly sets the address offset of the client agent in the PID, thereby improving the information query efficiency.
The embodiment of the invention provides a method for quickly positioning a user agent, which can effectively reduce the pressure of global index service and improve the response performance of a system.
An embodiment of the present invention provides a client-side proxy location method, referring to fig. 5, where the method includes:
51: acquiring a user login identity unique identifier (PID) of a client from a local cache of a core service or a request from the client, wherein the PID comprises an access service address and a client agent address identifier, and the client agent address identifier indicates an offset of a client agent in the access service relative to a head address;
52: acquiring an access service according to an access service address in the acquired PID, adding the PID to a signaling, and then sending the signaling from the core service to the access service;
53: positioning according to the client agent address identifier of the PID in the signaling to obtain a client agent, starting the positioned client agent by using the access service and removing the PID in the signaling;
54: and forwarding the signaling with the PID removed to the client through the positioned client agent.
Further, storing all the PIDs of all the clients in the system, which log in each time, in the global index service, wherein the PIDs also include timestamp information, and the obtaining of the client proxy according to the client proxy address identifier of the PID in the signaling includes: when the client agent is found according to the client agent address identification of the PID in the signaling, comparing whether the timestamp information in the PID is consistent with the timestamp information of the found client agent, if so, taking the found client agent as the positioned client agent, if not, sending an acquisition request to a core service by using an access service, and acquiring a new PID from a global index service by the core service according to the acquisition request; or,
and when the client agent cannot be found according to the client agent address identifier of the PID in the signaling, sending an acquisition request to the core service, and acquiring a new PID from the global index service by the core service according to the acquisition request.
Further, a PID is generated for each logged-in client by using the access service, and the system further includes:
transmitting the generated PID to a global index service using the access service; the generated PID is sent to a stateful core service by utilizing the access service, and the stateful core service stores the PID in a local cache; the generated PID is added to the client's request with the access service, which is forwarded by the client agent to the stateless core service.
Further, the sending the PID from the core service to the access service after adding the PID to the signaling includes: the PID is added to a signaling header of the signaling and then is sent to the access service from a core service;
the initiating the located client agent and removing the PID in the signaling with the access service comprises: the PID in the signaling header is removed with the access service.
The core services include stateful core services and stateless core services, the stateful core services are provided with a local cache,
the stateful core service maintains the corresponding relation between the client identification and the PID, and acquires the PID of the client from a local cache according to the acquired client identification; and the stateless core service takes the PID carried in the received client request as the acquired client PID.
Further, the stateful core service acquires the client identifier through a request from the client, and acquires the PID of the client from the global index service according to the acquired client identifier when acquiring the PID of the client from the local cache fails.
Further, the access service stores the generated PID in an array form, wherein an array element in the array represents a PID;
the client proxy address identifier in the PID is formed by the label of the array element.
The specific implementation manner of each step in the second embodiment of the present invention can be referred to in the related content in the first embodiment of the present invention. In the embodiment of the invention, the unique identification PID of the user login identity is set, and the PID is maintained in the local cache of the core service or is obtained from the client request, so that the access request to the global index service is obviously reduced; in addition, the embodiment of the invention directly sets the address offset of the client agent in the PID, thereby improving the information query efficiency.
The embodiment of the invention provides a method for quickly positioning a user agent, which can effectively reduce the pressure of global index service and improve the response performance of a system.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (10)
1. A client agent location system, comprising an access service, a client agent and a core service,
the core service acquires a unique user login identity (PID) of a client from a local cache or a request from the client, wherein the PID comprises an access service address and a client proxy address identifier, the client proxy address identifier indicates the offset of a client proxy in the access service relative to a head address, and the core service acquires the access service according to the access service address in the acquired PID, adds the PID to a signaling and then sends the signaling to the access service;
the access service is used for positioning according to the client agent address identifier of the PID in the signaling to obtain a client agent, starting the positioned client agent and removing the PID in the signaling;
and the positioned client agent forwards the signaling with the PID removed to the client.
2. The system of claim 1, further comprising a global index service that stores PIDs for each login of all clients in the system, the PIDs further comprising timestamp information,
when the client agent is found according to the client agent address identification of the PID in the signaling, the access service compares whether the timestamp information in the PID is consistent with the timestamp information of the found client agent, if so, the found client agent is used as the positioned client agent, if not, the access service sends an acquisition request to a core service, and the core service acquires a new PID from the global index service according to the acquisition request; and
and the access service sends an acquisition request to the core service when the client agent cannot be found according to the client agent address identifier of the PID in the signaling, and the core service acquires a new PID from the global index service according to the acquisition request.
3. The system according to claim 1 or 2, wherein the core services comprise stateful core services and stateless core services, the stateful core services being provided with a local cache,
the stateful core service maintains the corresponding relation between the client identification and the PID, and acquires the PID of the client from a local cache according to the acquired client identification;
and the stateless core service takes the PID carried in the received client request as the acquired client PID.
4. The system of claim 3,
the stateful core service acquires the client identifier through a request from the client, and acquires the PID of the client from the global index service according to the acquired client identifier when the PID of the client is failed to be acquired from the local cache.
5. The system of claim 4, wherein the access service generates and maintains a PID for each logged-on client, the system further comprising:
the access service sends the generated PID to a global index service;
the access service sends the generated PID to a stateful core service, and the stateful core service stores the PID in a local cache;
the access service adds the generated PID in the request of the client, and the client agent forwards the request of the client to the stateless core service;
wherein the core services include stateful core services and stateless core services.
6. The system of claim 5,
the access service stores the generated PID in an array form, wherein one array element in the array represents one PID;
the client proxy address identifier in the PID is formed by the label of the array element.
7. The system of claim 1,
the core service adding a PID to a signaling header of the signaling;
the access service removes the PID in the signaling header.
8. A client agent location method, the method comprising:
obtaining a user login identity unique identification PID of the client from a local cache of the core service or from a request from the client, wherein the PID comprises an access service address and a client agent address identification, the client agent address identification indicates an offset of the client agent in the access service relative to a first address,
acquiring an access service according to an access service address in the acquired PID, adding the PID to a signaling, and then sending the signaling from the core service to the access service;
positioning according to the client agent address identifier of the PID in the signaling to obtain a client agent, starting the positioned client agent by using the access service and removing the PID in the signaling;
and forwarding the signaling with the PID removed to the client through the positioned client agent.
9. The method of claim 8, wherein the PIDs of all clients in the system for each login are stored in the global index service, the PIDs further include timestamp information, and the locating the client agent according to the address of the client agent of the PID in the signaling comprises:
when the client agent is found according to the client agent address identification of the PID in the signaling, comparing whether the timestamp information in the PID is consistent with the timestamp information of the found client agent, if so, taking the found client agent as the positioned client agent, if not, sending an acquisition request to a core service by using an access service, and acquiring a new PID from a global index service by the core service according to the acquisition request; and the number of the first and second groups,
and when the client agent cannot be found according to the client agent address identifier of the PID in the signaling, sending an acquisition request to the core service, and acquiring a new PID from the global index service by the core service according to the acquisition request.
10. The method of claim 9, wherein a PID is generated for each logged-on client using an access service, and wherein the system further comprises:
transmitting the generated PID to a global index service using the access service;
the generated PID is sent to a stateful core service by utilizing the access service, and the stateful core service stores the PID in a local cache;
adding the generated PID to the client request by using the access service, and forwarding the client request to a stateless core service by a client agent;
wherein the core services include stateful core services and stateless core services.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110457179.XA CN103188311B (en) | 2011-12-30 | 2011-12-30 | Client Agent navigation system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110457179.XA CN103188311B (en) | 2011-12-30 | 2011-12-30 | Client Agent navigation system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103188311A CN103188311A (en) | 2013-07-03 |
| CN103188311B true CN103188311B (en) | 2016-05-25 |
Family
ID=48679276
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110457179.XA Active CN103188311B (en) | 2011-12-30 | 2011-12-30 | Client Agent navigation system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103188311B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104618517B (en) * | 2015-03-05 | 2018-08-07 | 国家电网公司 | A kind of method, system and device of PUSH message |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101010924A (en) * | 2004-08-25 | 2007-08-01 | 法国电信公司 | Method and system for localising users for services based on sip or h.323 protocols with dynamic ip address allocation |
| CN101374068A (en) * | 2007-08-25 | 2009-02-25 | 华为技术有限公司 | Method, apparatus and system for implementing packet transmission of multicast business |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB0106918D0 (en) * | 2001-03-20 | 2001-05-09 | Marconi Comm Ltd | VoIP SYSTEMS |
| US8041819B1 (en) * | 2002-03-19 | 2011-10-18 | Cisco Technology, Inc. | Method and system for providing network services |
-
2011
- 2011-12-30 CN CN201110457179.XA patent/CN103188311B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101010924A (en) * | 2004-08-25 | 2007-08-01 | 法国电信公司 | Method and system for localising users for services based on sip or h.323 protocols with dynamic ip address allocation |
| CN101374068A (en) * | 2007-08-25 | 2009-02-25 | 华为技术有限公司 | Method, apparatus and system for implementing packet transmission of multicast business |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103188311A (en) | 2013-07-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110247999B (en) | Domain name resolution method, domain name resolution device, household appliance and storage medium | |
| US9888089B2 (en) | Client side cache management | |
| CN104202360B (en) | The method of accessed web page, device and router | |
| US20110320522A1 (en) | Context-specific network resource addressing model for distributed services | |
| CN108494755B (en) | Method and device for transmitting Application Programming Interface (API) request | |
| RU2008106250A (en) | STORAGE AND RESOLUTION IN THE BRANCH DNS | |
| CN103036967A (en) | Data download system and device and method for download management | |
| JP2012533791A (en) | Download plug-ins in instant messaging client | |
| CN107682470B (en) | Method and device for detecting public network IP availability in NAT address pool | |
| RU2642833C2 (en) | Method and device for mediere resource support | |
| JP2007108905A (en) | File server, file providing method, and program | |
| WO2017166524A1 (en) | Domain name parsing method and apparatus | |
| CN104144223B (en) | A kind of data capture method and device | |
| CN108206776B (en) | Group history message query method and device | |
| CN103685168A (en) | Query request service method for DNS (Domain Name System) recursive server | |
| US20180293316A1 (en) | Method and system for second-degree friend query | |
| CN112929463A (en) | Traffic proxy method, server and system based on DNS (Domain name System) | |
| US9130938B2 (en) | Method, switch, and system for processing a message | |
| US8984100B2 (en) | Data downloading method, terminal, server, and system | |
| JP2002525749A (en) | Internet caching system, method and system configuration | |
| CN106155925A (en) | A kind of method and device obtaining data | |
| CN107992489B (en) | Data processing method and server | |
| US20150156259A1 (en) | Load balancing apparatus, information processing system, method and medium | |
| JP2008113384A (en) | Communication system | |
| CN103188311B (en) | Client Agent navigation system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP02 | Change in the address of a patent holder |
Address after: Room 810, 8 / F, 34 Haidian Street, Haidian District, Beijing 100080 Patentee after: BEIJING D-MEDIA COMMUNICATION TECHNOLOGY Co.,Ltd. Address before: 100089 Beijing city Haidian District wanquanzhuang Road No. 28 Wanliu new building 6 storey block A room 602 Patentee before: BEIJING D-MEDIA COMMUNICATION TECHNOLOGY Co.,Ltd. |
|
| CP02 | Change in the address of a patent holder |