CN106612299B - Access request processing method and device - Google Patents
Access request processing method and device Download PDFInfo
- Publication number
- CN106612299B CN106612299B CN201510691188.3A CN201510691188A CN106612299B CN 106612299 B CN106612299 B CN 106612299B CN 201510691188 A CN201510691188 A CN 201510691188A CN 106612299 B CN106612299 B CN 106612299B
- Authority
- CN
- China
- Prior art keywords
- user
- area
- server
- access request
- module
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 10
- 238000000034 method Methods 0.000 claims abstract description 30
- 230000008569 process Effects 0.000 claims description 7
- 230000000977 initiatory effect Effects 0.000 claims description 5
- 238000012217 deletion Methods 0.000 claims 1
- 230000037430 deletion Effects 0.000 claims 1
- 230000008901 benefit Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000015654 memory Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- 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/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Computer And Data Communications (AREA)
Abstract
The application provides a processing method and a device of an access request, wherein the processing method of the access request comprises the following steps: receiving an access request sent by a user, wherein the access request comprises a user identifier of the user; acquiring a registration address of the user according to the user identifier, and acquiring an address currently used by the user according to the access request; and determining a server for processing the access request according to the registered address of the user and the address currently used by the user. According to the method and the device, the writing operation can be ensured to only occur on the server in one region, the dirty data generated by writing competition is avoided, and the server closest to the user is used for processing the access request of the user every time, so that the access speed can be improved, the global deployment of application is realized, and the user experience is improved.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for processing an access request.
Background
The globalization trend of internet application is increasingly obvious, and corresponding technical schemes are needed for websites to be accessible to users all over the world. At present, two common technical schemes are provided, one is that servers in the same area are accessed globally, the scheme has the advantages of simple implementation and the disadvantage that other areas are accessed slowly; the other is to establish a plurality of substations, which has the advantage that the access speed can be guaranteed, but when the write operation is involved, in order to guarantee the data consistency, the data is always only allowed to be written at the master station, and the access speed at the time cannot be guaranteed.
In summary, in the prior art, when accessing a website in different areas, the access speed cannot be guaranteed, especially the access of a write operation, such as: drop order or log in, etc., resulting in a poor user experience.
Disclosure of Invention
The present application aims to solve at least one of the technical problems in the related art to some extent.
To this end, a first object of the present application is to propose a method for processing an access request. The method can ensure that the write operation only occurs on the server in one area, avoid dirty data generated by write competition, and the server closest to the user is used for processing the access request of the user each time, thereby improving the access speed, realizing the global deployment of the application and improving the user experience.
A second object of the present application is to provide an access request processing apparatus.
In order to achieve the above object, a method for processing an access request according to an embodiment of the first aspect of the present application includes: receiving an access request sent by a user, wherein the access request comprises a user identifier of the user; acquiring a registration address of the user according to the user identifier, and acquiring an address currently used by the user according to the access request; and determining a server for processing the access request according to the registered address of the user and the address currently used by the user.
In the method for processing the access request, after the access request sent by the user is received, the registered address of the user is obtained according to the user identifier of the user, the address currently used by the user is obtained according to the access request, and the server for processing the access request is determined according to the registered address of the user and the address currently used by the user, so that the writing operation can be ensured to be only performed on the server in one area, dirty data caused by writing competition is avoided, the server closest to the user is used for processing the access request of the user every time, the access speed can be improved, global deployment of applications is realized, and the user experience is improved.
In order to achieve the above object, an apparatus for processing an access request according to an embodiment of the second aspect of the present application includes: the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving an access request sent by a user, and the access request comprises a user identifier of the user; an obtaining module, configured to obtain a registration address of the user according to the user identifier, and obtain an address currently used by the user according to the access request received by the receiving module; and the determining module is used for determining a server for processing the access request according to the registered address of the user and the address currently used by the user.
In the access request processing device in the embodiment of the application, after the receiving module receives an access request sent by a user, the obtaining module obtains a registration address of the user according to a user identifier of the user, obtains an address currently used by the user according to the access request, and then the determining module determines a server for processing the access request according to the registration address of the user and the address currently used by the user, so that it is ensured that write operation only occurs on servers in one area, dirty data generated by write competition is avoided, and the server closest to the user is used for processing the access request of the user each time, thereby improving access speed, realizing global deployment of applications, and improving user experience.
Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
FIG. 1 is a flow chart of one embodiment of a method for processing an access request according to the present application;
FIG. 2 is a flow chart of another embodiment of a method for processing an access request according to the present application;
FIG. 3 is a schematic structural diagram of an embodiment of a device for processing an access request according to the present application;
fig. 4 is a schematic structural diagram of another embodiment of the access request processing apparatus according to the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application. On the contrary, the embodiments of the application include all changes, modifications and equivalents coming within the spirit and terms of the claims appended hereto.
Fig. 1 is a flowchart of an embodiment of a processing method of an access request according to the present application, and as shown in fig. 1, the processing method of the access request may include:
And 102, acquiring the registered address of the user according to the user identification, and acquiring the current address used by the user according to the access request.
In this embodiment, the server that processes the access request is determined according to the registered address of the user and the address currently used by the user, so that it can be ensured that the write operation only occurs on one server, thereby avoiding dirty data caused by write contention, and each access is the server closest to the user.
In the method for processing the access request, after the access request sent by the user is received, the registered address of the user is obtained according to the user identification of the user, the address currently used by the user is obtained according to the access request, and the server for processing the access request is determined according to the registered address of the user and the address currently used by the user, so that the writing operation can be ensured to be only performed on the server in one area, the dirty data generated by writing competition is avoided, the server closest to the user is used for processing the access request of the user every time, the access speed can be improved, the global deployment of the application is realized, and the user experience is improved.
Fig. 2 is a flowchart of another embodiment of the access request processing method of the present application, and as shown in fig. 2, step 103 may be:
step 201, obtaining a first area to which the registered address of the user belongs and a second area to which the address currently used by the user belongs.
That is, if the first area is the same as the second area, the access to the first area, i.e., the server of the area to which the registered address of the user described above belongs, is continued.
That is, if the first area is different from the second area, which indicates that the user has roamed to a new area, such as a business trip or a tour, the server that handles the access request is determined to be the server of the second area.
Further, after step 204, the method may further include:
In this embodiment, after the roaming information of the user is added to the server in the second area, if the user accesses the second area again next time, the user is the same as the user registered in the second area.
In this embodiment, step 205 and step 206 may be executed in parallel or sequentially, the execution order of step 205 and step 206 is not limited in this embodiment, and step 205 is executed before step 206 in fig. 2 as an example.
Further, if it is detected that the user roams from the second area to the third area, the roaming information of the user is added to the server in the third area to identify that the user roams to the third area.
When the access request is a read operation request, copying the data of the user from the server of the second area to a server of a third area, and updating the roaming information of the user on the server of the first area to identify that the user currently roams to the third area.
Further, after the data of the user is copied from the server in the second area to the server in the third area, the data of the user and the roaming information of the user may be deleted from the server in the second area, so that the latest data of the user may be guaranteed to be on the server that is used by the user most recently.
Further, after detecting that the user finishes roaming back to the first area, deleting the roaming information of the user on a server of the area to which the user roaming place belongs; and if the data of the user is updated, copying the data of the user back to the server in the first area, and deleting the roaming information of the user on the server in the first area.
That is, after the user finishes roaming back to the first area, if the user returns from the second area to the first area, the roaming information of the user is deleted from the server of the second area, and if the data of the user is updated, the data of the user is copied back to the server of the first area from the server of the second area, and the roaming information of the user is deleted from the server of the first area.
If the user returns from the third area to the first area, the roaming information of the user on the server of the third area is deleted, if the data of the user is updated, the data of the user is copied from the server of the third area to the server of the first area, and the roaming information of the user on the server of the first area is deleted.
The access request processing method provided by the application mainly establishes a roaming list of global users of the website by means of offline analysis and near real-time processing (within 10 s) by means of the user information which is the global unique roaming identifier. And adopting a memory isolation technology to standardize non-heap storage (off-heap) to locally store the roaming table. When the roaming information of the user is changed, a reliable coordination system (such as Zookeeper) of the distributed system monitors the version node of the routing table, local storage is changed in a pull mode, and a change result is reported. The change of the whole user roaming information is atomic operation, in order to ensure the consistency of all the application roaming list external memories, a bolt lock is reliably held by a coordination system globally, and when an application fails to update or fails due to network reasons, the global consistency of the final roaming list is ensured through idempotent and overtime strategies. Of course, this is only an example scheme for implementing the processing method of the access request provided in the present application, and the present application is not limited to this scheme.
Fig. 3 is a schematic structural diagram of an embodiment of an access request processing apparatus according to the present application, where the access request processing apparatus in the present embodiment may be used as a general server in a distributed system to implement the flows of the embodiments shown in fig. 1 and fig. 2 in the present application. As shown in fig. 3, the apparatus for processing the access request may include: a receiving module 31, an obtaining module 32 and a determining module 33;
the receiving module 31 is configured to receive an access request sent by a user, where the access request includes a user identifier of the user;
an obtaining module 32, configured to obtain a registration address of the user according to the user identifier, and obtain an address currently used by the user according to the access request received by the receiving module 31;
a determining module 33, configured to determine a server for processing the access request according to the registered address of the user and the address currently used by the user.
In this embodiment, the determining module 33 determines the server that processes the access request according to the registered address of the user and the address currently used by the user, so that it can be ensured that the write operation only occurs on one server, thereby avoiding the dirty data generated by write contention, and each access is the server closest to the user.
Fig. 4 is a schematic structural diagram of another embodiment of the access request processing apparatus according to the present application, and compared with the access request processing apparatus shown in fig. 3, the difference is that in the access request processing apparatus shown in fig. 4, the determining module 33 may include: an obtaining sub-module 331, a judging sub-module 332 and a determining sub-module 333;
the obtaining sub-module 331 is configured to obtain a first area to which the registered address of the user belongs and a second area to which the address currently used by the user belongs;
a determining submodule 332, configured to determine whether the first area is the same as the second area;
a determining submodule 333 configured to determine, when the determining submodule 332 determines that the first area is the same as the second area, that the server which processes the access request is a server of the first area; when the determination submodule 332 determines that the first area is different from the second area, it determines that the server that processes the access request is the server of the second area. That is, if the first area is the same as the second area, the server continues to access the first area, which is the area to which the registered address of the user belongs; if the first area is different from the second area, indicating that the user has roamed into a new area, such as a business trip or a tour, the determination sub-module 333 determines the server handling the access request to be the server for the second area.
Further, the processing device of the access request may further include: an add module 34;
an adding module 34, configured to add roaming information of the user to the server in the second area after the determining module 33 determines that the server processing the access request is the server in the second area, where the roaming information of the user is used to identify that the user roams to the second area.
In this embodiment, after the adding module 34 adds the roaming information of the user to the server in the second area, if the user accesses the second area next time, the same is the same as the user registered in the second area.
Further, the processing device of the access request may further include: an initiating module 35 and an adding module 34;
the initiating module 35 is configured to initiate a data roaming request to the server in the first area after the determining module 33 determines that the server processing the access request is the server in the second area;
an adding module 34, configured to add the roaming information of the user on the server in the first area to identify that the user currently roams to a second area.
Further, the processing device of the access request may further include:
a judging module 36, configured to judge a type of the access request;
a copy module 37, configured to copy the user data from the server in the first area to the server in the second area when the access request is a read operation request;
and a writing module 38, configured to write data of the write operation request into the server in the second area when the access request is a write operation request.
Further, the processing device of the access request may further include: an update module 39;
an adding module 34, further configured to add roaming information of the user to a server in a third area to identify that the user roams to the third area when it is detected that the user roams from a second area to the third area;
a copy module 37, further configured to copy the user data from the server in the second area to the server in the third area when the access request is a read operation request;
an updating module 39, configured to update the roaming information of the user on the server in the first area to identify that the user currently roams to the third area.
Further, the processing device of the access request may further include:
a deleting module 310, configured to delete the user data and the user roaming information from the server in the second area after the copying module 37 copies the user data from the server in the second area to the server in the third area, so as to ensure that the latest data of the user is on the server that is latest used by the user.
Further, the processing device of the access request may further include: a delete module 310 and a copy module 37;
a deleting module 310, configured to delete the roaming information of the user on the server in the area to which the roaming destination of the user belongs after detecting that the user finishes roaming back to the first area;
a copy module 37, configured to copy the user data back to the server in the first area when the user data is updated;
the deleting module 310 is further configured to delete the roaming information of the user on the server in the first area.
In the apparatus for processing the access request, after the receiving module 31 receives the access request sent by the user, the obtaining module 32 obtains the registered address of the user according to the user identifier of the user, obtains the address currently used by the user according to the access request, and then the determining module 33 determines the server for processing the access request according to the registered address of the user and the address currently used by the user, so that it can be ensured that the write operation only occurs on the server in one area, thereby avoiding the dirty data generated by write competition, and the server closest to the user is used for processing the access request of the user each time, thereby improving the access speed, realizing the global deployment of the application, and improving the user experience.
It should be noted that, in the description of the present application, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In addition, in the description of the present application, "a plurality" means two or more unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic Gate circuit for implementing a logic function on a data signal, an asic having an appropriate combinational logic Gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), and the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.
Claims (16)
1. An access request processing method applied to an overall server includes:
receiving an access request sent by a user, wherein the access request comprises a user identifier of the user;
acquiring a registration address of the user according to the user identifier, and acquiring an address currently used by the user according to the access request;
determining a server for processing the access request according to the registration address of the user and the address currently used by the user; the method comprises the following steps: acquiring a first area to which a registered address of the user belongs and a second area to which an address currently used by the user belongs; judging whether the first area is the same as the second area; if the access requests are the same, determining that the server processing the access requests is the server of the first area; and if the access requests are different, determining that the server processing the access requests is the server of the second area.
2. The method of claim 1, wherein after determining that the server processing the access request is the server of the second area, further comprising:
and adding the roaming information of the user on the server of the second area, wherein the roaming information of the user is used for identifying that the user roams to the second area.
3. The method of claim 1, wherein after determining that the server processing the access request is the server of the second area, further comprising:
and initiating a data roaming request to a server of the first area, and adding roaming information of the user on the server of the first area to identify that the user currently roams to the second area.
4. The method of claim 3, further comprising:
judging the type of the access request;
copying the user's data from the server of the first area to the server of the second area if the access request is a read operation request;
and if the access request is a write operation request, writing the data of the write operation request into the server of the second area.
5. The method of claim 4, further comprising:
if the user is detected to roam from the second area to a third area, roaming information of the user is added on a server of the third area to identify that the user roams to the third area.
6. The method of claim 5, further comprising:
when the access request is a read operation request, copying the data of the user from the server of the second area to the server of the third area, and updating the roaming information of the user on the server of the first area to identify that the user currently roams to the third area.
7. The method of claim 6, wherein after copying the user's data from the server of the second area to the server of the third area, further comprising:
and deleting the data of the user and the roaming information of the user from the server of the second area.
8. The method of any one of claims 2-7, further comprising:
after the fact that the user finishes roaming back to the first area is detected, the roaming information of the user on a server of the area where the user roaming place belongs is deleted; and if the data of the user is updated, copying the data of the user back to the server of the first area, and deleting the roaming information of the user on the server of the first area.
9. An apparatus for processing an access request, comprising:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving an access request sent by a user, and the access request comprises a user identifier of the user;
an obtaining module, configured to obtain a registration address of the user according to the user identifier, and obtain an address currently used by the user according to the access request received by the receiving module;
the determining module is used for determining a server for processing the access request according to the registered address of the user and the address currently used by the user; the determining module comprises: the obtaining submodule is used for obtaining a first area to which the registered address of the user belongs and a second area to which the address currently used by the user belongs; the judgment submodule is used for judging whether the first area is the same as the second area or not; a determining submodule, configured to determine, when the determining submodule determines that the first area is the same as the second area, that the server which processes the access request is the server of the first area; and when the judging submodule determines that the first area is different from the second area, determining that the server for processing the access request is the server of the second area.
10. The apparatus of claim 9, further comprising:
and an adding module, configured to add, after the determining module determines that the server processing the access request is the server in the second area, roaming information of the user on the server in the second area, where the roaming information of the user is used to identify that the user roams to the second area.
11. The apparatus of claim 9, further comprising:
an initiating module, configured to initiate a data roaming request to the server in the first area after the determining module determines that the server processing the access request is the server in the second area;
an adding module, configured to add the roaming information of the user on the server in the first area to identify that the user currently roams to the second area.
12. The apparatus of claim 11, further comprising:
the judging module is used for judging the type of the access request;
a copy module for copying the user's data from the server of the first area to the server of the second area when the access request is a read operation request;
and the writing module is used for writing the data of the write operation request into the server of the second area when the access request is the write operation request.
13. The apparatus of claim 12,
the adding module is further configured to add roaming information of the user on a server in a third area when it is detected that the user roams from the second area to the third area, so as to identify that the user roams to the third area.
14. The apparatus of claim 13, further comprising: an update module;
the copy module is further used for copying the data of the user from the server of the second area to the server of the third area when the access request is a read operation request;
the updating module is used for updating the roaming information of the user on the server of the first area so as to identify that the user currently roams to the third area.
15. The apparatus of claim 14, further comprising:
a deleting module, configured to delete the data of the user and the roaming information of the user from the server in the second area after the copying module copies the data of the user from the server in the second area to the server in the third area.
16. The apparatus of any one of claims 10-15, further comprising: a deletion module and a copy module;
the deleting module is configured to delete the roaming information of the user on the server in the area to which the roaming destination of the user belongs after detecting that the user finishes roaming back to the first area;
the copying module is used for copying the data of the user back to the server of the first area when the data of the user is updated;
the deleting module is further configured to delete the roaming information of the user on the server in the first area.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510691188.3A CN106612299B (en) | 2015-10-22 | 2015-10-22 | Access request processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510691188.3A CN106612299B (en) | 2015-10-22 | 2015-10-22 | Access request processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106612299A CN106612299A (en) | 2017-05-03 |
| CN106612299B true CN106612299B (en) | 2020-07-10 |
Family
ID=58611776
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510691188.3A Active CN106612299B (en) | 2015-10-22 | 2015-10-22 | Access request processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106612299B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107404527B (en) * | 2017-07-26 | 2020-05-29 | 郑州云海信息技术有限公司 | Resource access and control method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB0223855D0 (en) * | 2002-10-12 | 2002-11-20 | Motorola Inc | Communication system,serving communication unit and method of routing information |
| US7042864B1 (en) * | 2000-08-01 | 2006-05-09 | Cisco Technology, Inc. | Enabling push technologies for mobile IP |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2005084065A1 (en) * | 2004-02-18 | 2005-09-09 | Megasoft, Ltd. | Network-based system and method for global roaming |
| US7778229B2 (en) * | 2005-07-29 | 2010-08-17 | Cisco Technology, Inc. | Optimized IP address use in a mobile IP environment |
| CN100531435C (en) * | 2006-01-26 | 2009-08-19 | 中兴通讯股份有限公司 | System and method for realizing communication positioning based on R4 protocol |
| CN1859412B (en) * | 2006-03-28 | 2012-06-20 | 华为技术有限公司 | Registrating roaming custom IP address in evolution network and service using method |
| CN100466846C (en) * | 2007-01-08 | 2009-03-04 | 华为技术有限公司 | The method and system for access to the home packet data network |
| CN101771995B (en) * | 2008-12-31 | 2013-02-27 | 华为技术有限公司 | Service roaming method, device and system |
| CN102647334B (en) * | 2011-02-22 | 2015-07-29 | ***通信集团公司 | A kind of data routing method and device |
-
2015
- 2015-10-22 CN CN201510691188.3A patent/CN106612299B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7042864B1 (en) * | 2000-08-01 | 2006-05-09 | Cisco Technology, Inc. | Enabling push technologies for mobile IP |
| GB0223855D0 (en) * | 2002-10-12 | 2002-11-20 | Motorola Inc | Communication system,serving communication unit and method of routing information |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106612299A (en) | 2017-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106911524B (en) | HA implementation method and device | |
| US11509522B2 (en) | Synchronization of logical network state between global and local managers | |
| US10831612B2 (en) | Primary node-standby node data transmission method, control node, and database system | |
| US7165083B2 (en) | File management method in a distributed storage system | |
| US11368407B2 (en) | Failover management using availability groups | |
| CN106933548B (en) | Global information obtaining, processing and updating method, device and system | |
| CN109714239B (en) | Management message issuing method, VNFM (virtual network management frequency) equipment and server | |
| US10673694B2 (en) | Private network mirroring | |
| US8880549B2 (en) | Concurrent database access by production and prototype applications | |
| US10078655B2 (en) | Reconciling sensor data in a database | |
| JP2019502186A (en) | System and method for obtaining, processing and updating global information | |
| US20180089297A1 (en) | Data Copy Method and Device | |
| WO2018000653A1 (en) | Information processing method for m2m application, cse and ae | |
| CN108810166A (en) | Route management method, system, computer equipment and computer readable storage medium | |
| CN106612299B (en) | Access request processing method and device | |
| KR101846778B1 (en) | Method for ID Resolution Service and M2M System applying the same | |
| CN113301173A (en) | Domain name updating system and method, message forwarding method and server | |
| US11205049B2 (en) | Method for managing semantic information on M2M/IoT platform | |
| CN110807185A (en) | System access method, device and server | |
| CN108156203B (en) | Storage system and storage node management method | |
| US9380109B2 (en) | Resource synchronization control method, device, and system | |
| CN113615146B (en) | Reselection of network function instances based on data consistency | |
| CN114764403A (en) | Data migration method, device, equipment and storage medium | |
| CN109947727B (en) | Data processing method, device, computer equipment and storage medium | |
| CN107704462B (en) | Resource metadata maintenance method, equipment and storage device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240221 Address after: # 01-21, Lai Zan Da Building 1, 51 Belarusian Road, Singapore Patentee after: Alibaba Singapore Holdings Ltd. Country or region after: Singapore Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: ALIBABA GROUP HOLDING Ltd. Country or region before: Cayman Islands |