WO2010145428A1 - Method and system for implementing disaster recovery switch - Google Patents
Method and system for implementing disaster recovery switch Download PDFInfo
- Publication number
- WO2010145428A1 WO2010145428A1 PCT/CN2010/073261 CN2010073261W WO2010145428A1 WO 2010145428 A1 WO2010145428 A1 WO 2010145428A1 CN 2010073261 W CN2010073261 W CN 2010073261W WO 2010145428 A1 WO2010145428 A1 WO 2010145428A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- same
- synchronization
- performance
- average
- decision
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
Definitions
- the distribution R has the following characteristics: (1) the front end of the responsibility (Fo E d, FE) and the user-storage (Bac d, BE).
- FE and BE can be deployed in the same geographical station, or can be deployed in Different geographic stations (2)
- FE and BE can be configured separately, you or non-you deploy, and, in the case of non-deployment, FE and BE are not equal, and can be stored centrally.
- FE can be used for all BEs, but it can be effective for rabbit FE needs and BE.
- the R scheme of the distribution R and the system have the following R schemes provided by the following R schemes, which are provided to the other 0 stations, Hugh, in the main direction, including each FE to FE, and teach BE to BE and the distribution R, FE and BE can be respectively, that is, FE has a barrier, and only need to be connected to each FE, and no BE synchronization is required. Same, BE Need, does not require FE synchronization.
- the R 401 is synchronized to R 402 in the way of storage, or use, and is connected to (sg a g a s e po , ST ) 01 102
- R is from 601 to 801, pointing to R402.
- STP 01 102 sends all of them to R401.
- F 01 BE301 completes each.
- F 01, each F 02, BE301, and each BE302 can be deployed in different geographical locations.
- each FE 201 barrier each to each FE 202, each FE 202 can
- FE and BE are allowed to be deployed on different geographical stations, FE and BE are the same, which limits the performance of FE BE. Because of the different performance characteristics of FE and BE, such as FE, the BE can be optimally ideal. For example, in the system shown in Figure 2, FE may have the best performance in BE, and each BE The performance is poor. If the FE is out, the BEs are not synchronized, so that the BE FEs are very different, the performance is degraded, and the performance cannot meet the requirements. The same reason, in the case of BE sheep, the same occurs.
- each storage of each other for example, including, ( he ca o A hoTza o Acco, AAA, user
- the methods provided are distributed, distributed, and stored separately.
- the method includes the front end of each of the front and the side, or each of the unfamiliar customers, in the case that the result satisfies the synchronization, the synchronization rules are not synchronized with the front end or the front end.
- the method can include the front end of each of the friends or each
- results, and/or each of the unoccupied or front ends each yields a result.
- each of the results includes the following at least the same within the same predetermined
- the same is the same as the same number of the same value, the same average within the same.
- the synchronization synchronization rule may include the front end or establish a new one, if the same number of the same number in the same period as the synchronization is greater than the same value, and the same average within the same time is greater than the average, and the same within the predetermined same size. Or front end first.
- each can force the following, each, each
- the distributed, distributed deployment, and each storage system may include performance monitoring, decision making, and control.
- each result is determined to receive the results of the performance monitoring, each or the front end Whether the same number satisfies the synchronization
- each result may include at least the following Same as the same inside
- the decision can satisfy the synchronization
- Each of the following registers can be used for each of the register and user registers.
- the FE BE is controlled by the same (performance) line, the synchronization of FE BE, the unnecessary FE and BE of the rabbit, the self-synchronization performance of FE and BE, and the manual Each of the same. Description
- each storage for example, may include R SS AA, ER, etc.
- the FE can be established by BE first, so that the FE of the FE main FE FE is similar to that of the FE.
- the BE can be established by the FE first, so that the BE is the BE of the BE BE. You can put the rules table, as shown in Table 1.
- F 01 can be any one of the deployment shown in 2, F 01 can be any one of the deployment shown in 2, F 01 can be any one of the deployment shown in 2, F 01 can be any one of the deployment shown in 2, F 01 can be any one of the deployment shown in 2, F 01 can be any one of the deployment shown in 2, F 01 can be any one of the deployment shown in 2, F 01 can be any one of the deployment shown in 2, F 01 can be any one of the deployment shown in 2, F 01 can be
- BE301 is the same as the same, BE301 can also be the same as 01, each BE 302 can also be the same as each FE 202, and the necessary FE BE can be the same.
- the method of this includes
- Step S302 in each of the FE and the BE,
- the synchronization may have a multi-god situation, for example, each of the roads may not satisfy the requirements.
- Synchronization step 5304 in the case that the result satisfies the synchronization, the synchronization rule (the rule can be pre-configured) synchronizes the BE or FE of each non-guest.
- step S302 each FE or BE customer, each of the customer's FE or BE needs to obtain each And each of the unexposed BE or FE each obtained each result.
- the results of may include at least the same within the same predetermined
- the force cannot satisfy the ratio of the predetermined value of each demand, the proportion of the predetermined value, and the average of the same average.
- the sheep can be used or combined. For example, in each of the requirements, you can refer to the above.
- the BE301 is not synchronized. Otherwise, it is necessary to combine BE301 to each BE302, and each of the F 02 and each BE302.
- the method is similar, and it is no longer.
- each of the self-strategies that specify FE and BE is higher than BE302 at 1001 F 01 BE301, so the performance of F 01 BE302 is lower than (the requirements cannot be met, ie , to meet the synchronization), control from the BE301 Force master, on the contrary, is not allowed to configure 1003, FE 201 BE 301 performance is higher than 02 BE301, therefore, the performance of F 02 BE301 is lower than
- control will be F 01 force master, but not allowed.
- each storage for example, including SS ER, etc.
- the system includes performance monitoring, decision making, and control.
- each result of each customer's FE or BE does not have a customer BE or FE, whether each meets the pre-configured synchronization control, in the case that the result of the decision meets the synchronization, the pre-configured synchronization rules are not the raw BE or FE synchronization.
- each of the results may include the following at least the same
- Each of the following registers can be used for each of the register registers. System.
- each of the main F 01 and each F 02, the number of storage in the different geographical distribution R is stored by the main BE301 and each BE302, deployed in different geographical locations, and BE301 and each BE 302 can 01.
- Each F 02 is not in the same geographical location.
- performance monitoring is deployed on the FE, that is, as shown in FIG. 4, the performance monitoring 101 is deployed on the main F 01, the performance monitoring 102 is deployed on each F 02, and the performance monitoring 101 is monitored on the FE 201 BE 301. 102 monitors each F 02 and BE302.
- the decision 401 and the control 501 can be deployed on the same or separately, and the decision 401 and the control 501 can be deployed in the same geographical location.
- Performance monitoring 102 can monitor the same as F02 BE301 and make decisions 401 on a regular basis.
- the performance monitoring 102 can be pre-configured with the same T, so that the information of the upper decision 401 can include the same, the same and the same as the same T.
- Decision 401 collects performance on performance monitoring 102 and analyzes the performance of all performance monitoring of pre-configured FE 202 within T2.
- Decision 401 uses pre-configured performance to determine if BE is required.
- the performance may include an average of the same T3 and the ratio T4. If the ratio is the same as T3 in the same T2, or the ratio of the same T is greater than the ratio T4, the decision 401 requires BE self, and the control system 501.
- Control 501 receives an indication of decision 401, whether or not to allow BE to be self-contained, and to introduce a new BE. If the fruit distribution is allowed, and each BE302 is in a row, the control 501 first controls each of the FE 301, and then controls each FE 302.
- the BE301 barrier requires each BE302 to be the master, while the STP still sends all of them to 01, 01 and only the BE302 users can complete each.
- Performance Monitoring 101 monitors FE 201 BE 302 in the same way as decision-making 401.
- the performance monitoring 101 can be pre-configured with the same T, so that the information of the upper decision 401 can include the same, the same and the same as the same T.
- Decision 401 collects performance on performance monitoring 101 and analyzes the performance of all performance monitoring of pre-configured FE 201 within T2. Decision 401 Use pre-configured performance Undetermined if FE is required. Performance can include averages with T3 and
- Ratio T4 if it is within the same T2, the average is the same as T3, or the ratio of the same is greater than the same T is greater than
- the decision 401 requires FE self-control and 501 control.
- Control 501 receives an indication of decision 401, whether FE is required to be configured, and FE is the new FE. 2, the fruit distribution configuration is allowed, and each F 02 line is always (and the same amount of FE202 BE302 can meet the requirements), then control 501 first FE 202 command, then control FE 201 command, STP will send all to F 02, F 02 BE302 complete each.
- Control 501 from FE or BE can use the first table shown in 1.
- Each of the 1s specifies the self-policy of FE and BE, for example, In 1001, F 01 BE301 is higher than BE302 first. Therefore, if the performance of FE 201 BE 302 is lower than that of BE BE 301, the opposite is not allowed to configure 1003. The performance of FE 201 BE 301 is higher than F 02 BE301. Therefore, the performance of F 02 BE301 is lower than
- control can be either stipulated, established or SCTP, and BE, and the way of Hugh is in this field, and this article is no longer.
- the FE BE has the same performance line monitoring, FE BE synchronization, rabbit unnecessary FE and BE, near FE and BE self-conformity performance And the rabbits are handmade.
- the above is better than the limit, and any modifications, equivalents, etc. made within this spirit and principle are included in this document.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
A method and system for implementing disaster recovery switch are disclosed. The method includes: for a network equipment whose disaster recovery switch occurs in one party of a front end (FE) and a back end (BE), judging whether the condition of the synchronization switch is satisfied, according to the detection result of quality of service (QoS) of the data access link between FE or BE after the disaster recovery switch and BE or FE of the network equipment in which the disaster recovery switch does not occur; if satisfying the condition of the synchronization switch, synchronously switching BE or FE of the network equipment in which the disaster recovery switch does not occur, according to the rule of the synchronization switch. It is possible to harmonize the synchronization switch of FE and BE and ensure the capability of the system service by monitoring QoS between FE and BE.
Description
的 方法和 統 木領域 Method and system
本 涉及通信領域, 尤其涉及 的 方法和 統。 背景 木 This relates to the field of communications, and in particular to methods and systems. Background
5 位置寄存器 (ho e oca o Tegse ) 于存儲 全 約用戶的 , 看 各的高速 、 以及 安全性和 各 融合需求的 增 , 使 R 羊的 1+1 各和 + 各容 方案 力分布 R 5 location register (ho e oca o Tegse ) for storing all the users, see the high speed, and the increase of security and integration requirements, so that R 1 1 + and + each program force distribution R
目前, 分布 R具有以下 特性 (1) 責 各 理的前端 (Fo E d, FE)和 責用戶 存儲的 (Bac d, BE)彼此 FE和BE既可以部署在同 介地理站 , 也可以部署在不同的地理站 (2)FE和BE可以分別配置各自的 方案, 你或非 你部署, 且, 在非 你部署的情況下, FE和BE的 不相等, 可以 的集 中存儲。 At present, the distribution R has the following characteristics: (1) the front end of the responsibility (Fo E d, FE) and the user-storage (Bac d, BE). FE and BE can be deployed in the same geographical station, or can be deployed in Different geographic stations (2) FE and BE can be configured separately, you or non-you deploy, and, in the case of non-deployment, FE and BE are not equal, and can be stored centrally.
5 通常, 在 統的 各 R 方案中, 是 , 近是 5 Usually, in the various R schemes, yes, near
,都需要部署FE和BE, 且FE只能 本 的BE。而在分布 R 中, FE可以 所有的BE, 而能 有效 兔 FE需要和BE Both need to deploy FE and BE, and FE can only have this BE. In the distribution R, FE can be used for all BEs, but it can be effective for rabbit FE needs and BE.
未的限制。 就 使得分布 R和 統的 R 方案在 統 換上存在以下 統的 R 方案所提供的是 介 向另外0 介站 的 , 休 , 在主 向 的 中, 包括了 各 FE 到 FE,以及教 BE 到 BE 而 于分布 R, FE和BE可以分別 , 即, FE出現 障, 只 需要將 各 到各 FE, 不需要BE 同步 。 同 的, BE
需要 , 不要求FE 同步 。Unrestricted. So that the R scheme of the distribution R and the system have the following R schemes provided by the following R schemes, which are provided to the other 0 stations, Hugh, in the main direction, including each FE to FE, and teach BE to BE and the distribution R, FE and BE can be respectively, that is, FE has a barrier, and only need to be connected to each FE, and no BE synchronization is required. Same, BE Need, does not require FE synchronization.
1 了 +1 各容 統的部署 。 1所示, R 401 的 于存儲、 或 用的 方式同步到 R 402, 同 , 在 令特接 (sg a g a s e po , ST ) 01 102 1 +1 deployment of each system. As shown in Fig. 1, the R 401 is synchronized to R 402 in the way of storage, or use, and is connected to (sg a g a s e po , ST ) 01 102
R 由 801的各 由 601, 指向 R402。 在 到 R402前, STP 01 102將所有 各 送到 R401, 在 主 R401中, F 01 BE301完成 各 的 。 R is from 601 to 801, pointing to R402. Before reaching R402, STP 01 102 sends all of them to R401. In the main R401, F 01 BE301 completes each.
F 01或 BE301 障 , 到 R402 ,停止 BE301 和 BE302的 , 且 STP 01 102和 F 01的信令 , 所有 各 自 送到各 R402 F 01 or BE301 barrier, to R402, stop BE301 and BE302, and STP 01 102 and F 01 signaling, all sent to each R402
2 了分布 R的部署 。 2所示, F 01、各 F 02、 BE301、各 BE302均可以部署在不同的地理位置。 2 Distribution R deployment. As shown in Figure 2, F 01, each F 02, BE301, and each BE302 can be deployed in different geographical locations.
FE 201 障 , 各將 到各 FE 202, 各 FE 202可以 FE 201 barriers, each to each FE 202, each FE 202 can
BE301完成 各 的 。 BE301 completes each.
由于FE和BE允許部署在不同的地理站 上, 因此, FE和BE 同的 各 , 就 制約FE BE 性能的因素。 由于不同的FE和BE 同存在地理 近差別等 性能的因素, FE 某 介BE 可以 得最理想的 "。 例 , 在 2所示的 統部署中, FE可 能在 BE 的 性能最好, 而 各 BE 的 性能較差。 果 FE 了 , BE不 同步 , 使得 BE FE 同 的 各 很 , 性能降低, 性能不能 滿足 各需求 , 各的 同理, 在BE羊 的情況下, 同 出現 。 同理, 除了分布式部署的 R 外, 其他" 分布式部署、 且 各 存儲彼此 的 各 (例 , 包括 、 、 ( he ca o A hoTza o Acco , AAA 各 、 用戶
各 ( o eS bsc be Se Ve , SS 、 各 寄存器 ( q p e de y Regse ER)), 均存在由于FE和BE不 同步 而 各 Since FE and BE are allowed to be deployed on different geographical stations, FE and BE are the same, which limits the performance of FE BE. Because of the different performance characteristics of FE and BE, such as FE, the BE can be optimally ideal. For example, in the system shown in Figure 2, FE may have the best performance in BE, and each BE The performance is poor. If the FE is out, the BEs are not synchronized, so that the BE FEs are very different, the performance is degraded, and the performance cannot meet the requirements. The same reason, in the case of BE sheep, the same occurs. Similarly, except distributed Outside the deployment of R, other "distributed deployments, and each storage of each other (for example, including, , ( he ca o A hoTza o Acco, AAA, user Each (o eS bsc be Se Ve , SS, each register (qpe de y Regse ER)) exists because each of the FE and BE are not synchronized.
的 。 of .
相 木中分布式部署的 各中由于BE和FE 非同步 而 的BE FE 同 性能不能得到 、 甚至 降低 性能 而 各 常 的 , 目前尚未提出有效的解決 。 In the distributed deployment of the phase, the BE FE with the non-synchronization of the BE and the FE cannot be obtained or even reduced in performance, and no effective solution has been proposed yet.
內容 Content
相 木中分布式部署的 各中由于FE和BE 非同步 而 的FE BE 同 性能不能得到 、 甚至 In the distributed deployment of the phase, the performance of the FE BE due to the unsynchronized FE and BE cannot be obtained, or even
性能的降低而 各 常 的 , 本 提出 Performance is reduced and often
的 , FE BE 同的數 性能。 , FE BE with the same number of performance.
本 的 木 是 的 The wood of this is
本 的 介方面, 提供了 的 方法, 于 分 布式部署、 且 各 存儲 的 各 。 In this aspect, the methods provided are distributed, distributed, and stored separately.
本 的方法包括 吋于前端和 中的 方 生客 的 各, 的前端或 各未 生客 的 在 結果 滿足同步 的情況下, 同步 規則 各未 生客 的 或前端 同步 。 The method includes the front end of each of the front and the side, or each of the unfamiliar customers, in the case that the result satisfies the synchronization, the synchronization rules are not synchronized with the front end or the front end.
在 各的前端或 生客 , 方法可 步包括 友 生客 的前端或 的 各 得到 各 At each front end or a customer, the method can include the front end of each of the friends or each
結果、 和/或 各未 生客 的 或前端 的 各 得到 各 結果。 The results, and/or each of the unoccupied or front ends each yields a result.
, 的 各 結果包括以下至少 預定 同 內 的 同的 、 預定 同 內
的 同的 同大于 同 值的 數量、 預定 同 內 的 同的平均 同。 , each of the results includes the following at least the same within the same predetermined The same is the same as the same number of the same value, the same average within the same.
且, 在 各 結果滿足以下至少 的情況下, And, if each result satisfies at least the following,
滿足同步 預定 同 內 的 同的 同大于 同 值的 數量 的數量 、 預定 同 內 的 同的平均 同大于平均 同 、 預定 同 內 的 同的 同大于 的第 , 同步 規則可以包括 的前端或 建立新的 的 或前端的 先 。 The synchronization synchronization rule may include the front end or establish a new one, if the same number of the same number in the same period as the synchronization is greater than the same value, and the same average within the same time is greater than the average, and the same within the predetermined same size. Or front end first.
, 各可以力以下 荃枚、 、 各 , each can force the following, each, each
位置寄存器 各 寄存器 用戶 各 。 Location register Each register user.
本 的另 方面, 提供了 的 統, 于 分 布式部署、 且 各 存儲 的 各 , 統 可以包括性能監控 、 決策 、 以及 控制 。 In another aspect of the present invention, the distributed, distributed deployment, and each storage system may include performance monitoring, decision making, and control.
休 , 性能監控 于 各的前端、 和/或 于 各的 , 于 性能監控 所在的前端或 通信的 或前端 同的數 的 各 , 得到 各 結果 決策 于接收未自性能監控 的 各 結果, 各 或前端 同的數 的 各 是否滿足同步 Hugh, performance monitoring at each front end, and/or each of the front end of the performance monitoring or the number of the communication or front end, each result is determined to receive the results of the performance monitoring, each or the front end Whether the same number satisfies the synchronization
控制 于在 決策 的 結果 滿足同步 的情況下, 同步 規則 各未 生客 的 或前端 同步 。 It is controlled that the synchronization rules are not synchronized with each other or the front end is synchronized when the result of the decision meets the synchronization.
其中, 的 各 結果可以包括以下至少
同 內 的 同的 、 預定 同 內 Wherein, each result may include at least the following Same as the same inside
的 同的 同大于 同 值的 、 預定 同 內 的 同的平均 同。 The same as the same value of the same value, the same as the same within the same.
, 在 各 結果滿足以下至少 的情況下, 決策 可以 滿足同步 預定 同 內 In the case where the results satisfy at least the following, the decision can satisfy the synchronization
的 同的 同大于 同 值的 的 、 預定 同 內 的 同的平均 同大于 平均 同 、 預定 同 內 的 同的 The same average of the same and greater than the same value, which is greater than the average, and the same within the same
同大于 的第 同 值的 在 求量中所占的比例 Proportion of the same value of greater than the same
的比例 。 proportion .
, 各可以力以下 荃枚、 、 各 位置寄存器 各 寄存器 用戶 各 。 Each of the following registers can be used for each of the register and user registers.
借助于本 的上 木 , 通 FE BE 同的 各 ( 性能) 行監控, FE BE的同步 , 不 兔不必要的FE 和BE , 近 FE和BE的自 同步 統 各性能, 且自 也 兔了手工 的 各中 同。 說明 With the help of this board, the FE BE is controlled by the same (performance) line, the synchronization of FE BE, the unnecessary FE and BE of the rabbit, the self-synchronization performance of FE and BE, and the manual Each of the same. Description
1是 相 木的 +1 各容 統的部署 1 is the deployment of +1 each system
2是 相 木的分布 R的部署 2 is the distribution of the wood R deployment
3是 本 方法 的 的 方法的流程 3 is the flow of the method of the method
4是 本 明 統 的 的 統的流程 。 休 方式 4 is the unified process of this system. Hugh way
相 木中分布式部署、 且 各 存儲 的 各 (例 , R、 各 、 SS ER等)上FE和BE中的 方
另 方不 同步 而 的FE BE 同的 性能 得到 的 , 本 考慮到 然分布 統中的 FE和BE 可以 , 但是在某些情況下, FE和BE中的 方 , 另 方 果 同步 可以使 統 得更佳的 性能, 因此, 本 提出 各 FE 各 BE 同的 各 在FE或BE中的 是 否 另 方 同步 , 果 了 , FE BE 同的 The distributed deployment in the phase, and the parties in the FE and BE on each storage (for example, R, each, SS ER, etc.) The same performance of the FE BE that is not synchronized, this considers that FE and BE in the distribution system can be, but in some cases, the parties in FE and BE can be made more synchronized. Good performance, therefore, it is proposed that each FE of each FE is synchronized with each other in FE or BE, and if so, FE BE is the same
性能較差, 則 FE和BE中未 的 方 同步 。 Poor performance, then FE and BE are not synchronized.
下面將結合 , 本 的 。 The following will be combined with this one.
方法 Method
在本 中, 提供了 的 方法, 于 分布式部署、 且 各 存儲 的 各 (例 , 可以包括 R SS AA 各 、 ER等 各) 。 In this paper, methods are provided for distributed deployment, and each storage (for example, may include R SS AA, ER, etc.).
在 本 的 中, 首先需要 中的通信狀況配置 規則。 休 , 于FE而言, 可以 FE可以 先 BE建立 , 以 在 FE 力主 FE FE 最 的BE 矣似 , 于BE而言, 可以 BE可以 先 FE建立 , 以 在 BE 力主 BE BE 最 的 FE , 可 , 可以將 規則 表格 , 例 , 表 1 所示。 In this section, you first need the communication status configuration rule. In the case of FE, the FE can be established by BE first, so that the FE of the FE main FE FE is similar to that of the FE. For the BE, the BE can be established by the FE first, so that the BE is the BE of the BE BE. You can put the rules table, as shown in Table 1.
1 1
休 休 坊間 的性能排序 Performance sequencing between lounges
1001 FE201 BE301 BE302 1001 FE201 BE301 BE302
1002 FE202 BE302 BE301 1002 FE202 BE302 BE301
1003 BE301 FE201 FE202 1003 BE301 FE201 FE202
1004 BE302 FE202 FE201 規則可在 預先配置好, 其配置結果 各 FE BE
的地理位置 等因素相 , 本文不再 。 1004 BE302 FE202 FE201 rules can be pre-configured, and the configuration results are FE BE The geographical location and other factors, this article is no longer.
此 , 需要 所有 各的 前端和/或 配置監控 前端和/ 或 相 的數 的 各 量的功能。 This requires all of the front ends and/or the ability to configure the number of monitor front ends and/or phases.
例 , 在 2所示的 部署 中, F 01可以 For example, in the deployment shown in 2, F 01 can
BE301 同的 各 同 的, BE301也可以 01 同的 各 , 各 BE 302也可以 各 FE 202 同的 各 , 且, 在必要的 FE BE 同可以 向 。 BE301 is the same as the same, BE301 can also be the same as 01, each BE 302 can also be the same as each FE 202, and the necessary FE BE can be the same.
在 行服各 , 可以 很多 方法, 比較 羊而且有 效的方式就是 /。向 的方式, 即, FE和/或BE中向 等到 返 的 , 的 同 各 。 In the service, there are many ways to compare sheep and the effective way is /. The way to the right, that is, FE and / or BE in the same to return to the same.
在 結果 , 于 FE BE, 可以 汞 同 定 同 內 的 、 平均 同、 同 值的 數量等信息。 In the result, in FE BE, information such as the same amount, the same amount, and the same value of mercury can be determined.
下面將結合 , 本 的 。 The following will be combined with this one.
3所示, 本 的 的 方法包括 As shown in Figure 3, the method of this includes
步驟S302, 于FE和BE中的 方 生客 的 各, Step S302, in each of the FE and the BE,
的FE或BE 各未 生客 的BE或FE 同的數 (即, , 新建立的數 ) 的 各 結果 是否滿足同步 , 同步 可以具有多神情況, 例 , 可以 在 路上的 各 不能滿足 各需求 滿足同步 步驟 5304, 在 結果 滿足同步 的情況下, 同步 規則 ( 規則可以 預先配置得到) 各未 生客 的BE或 FE 同步 。 Whether the results of the same number of BE or FE of the FE or BE (ie, the newly established number) satisfy the synchronization, the synchronization may have a multi-god situation, for example, each of the roads may not satisfy the requirements. Synchronization step 5304, in the case that the result satisfies the synchronization, the synchronization rule (the rule can be pre-configured) synchronizes the BE or FE of each non-guest.
在步驟S302中, 在 各的 FE或BE 生客 , 生客 的FE或BE需要 的 各 得到 各
、和 各未 生客 的BE或FE 的 各 得到 各 結果。 In step S302, each FE or BE customer, each of the customer's FE or BE needs to obtain each And each of the unexposed BE or FE each obtained each result.
, 的 各 結果可以包括以下至少 預定吋同 內 的 同的 、 預定 同 內 The results of , may include at least the same within the same predetermined
的 同的 同大于 同 值的 、 預定 同 內 的 同的平均 同。 The same as the same value of the same value, the same as the same within the same.
在 是否滿足 各需求的 , 果滿足以下 中的至少 介, 則 力不能滿足 各需求 預定 同 值的 的 定 、 預定 同 值的 的 在 中占有的比例 定比例 、 平均 同 的平均 同 。 If the demand is met, if at least the following is satisfied, the force cannot satisfy the ratio of the predetermined value of each demand, the proportion of the predetermined value, and the average of the same average.
由于不同的 各 各 量的要求不 所以可以將上 羊 使用或組合使用。 例 , 于 各 要求不 格的 各, 可以 以上 中的 介 。 Due to the different requirements of different quantities, the sheep can be used or combined. For example, in each of the requirements, you can refer to the above.
例 , 在 2所示的 部署 果 01 至 各 FE 202, 此 就需要 的各 FE 202 未 的 BE301 同的 的 各 是否能 滿足 各需求 果 結果 是 (即, 不滿足同步 ), 則不 BE301 同步 , 否則需要將 BE301 至各 BE302, 由各 F 02 各 BE302 的 各。 For example, in the deployment result 01 to the FE 202 shown in FIG. 2, if each of the FEs 202 that are required by each FE 202 does not satisfy the respective requirements, that is, the result is (ie, the synchronization is not satisfied), then the BE301 is not synchronized. Otherwise, it is necessary to combine BE301 to each BE302, and each of the F 02 and each BE302.
于BE首先 、 FE是否 同步 的情況, 理方式 矣似, 里不再 。 In the case where the BE first and FE are synchronized, the method is similar, and it is no longer.
在 同步 的 , 表1所示, 每 介 指定了 FE和BE 的自 策略, 例 , 在 1001 F 01 BE301的 先 高 于BE302, 因此, 果F 01 BE302的性能低于 (不能滿 足 各需求, 即, 滿足同步 ) , 控制 自 將BE301
力主 , 相反則不允許 配置 1003, FE 201 BE 301的性能高 于 02 BE301, 因此, 果F 02 BE301的性能低于 In the synchronization, as shown in Table 1, each of the self-strategies that specify FE and BE, for example, is higher than BE302 at 1001 F 01 BE301, so the performance of F 01 BE302 is lower than (the requirements cannot be met, ie , to meet the synchronization), control from the BE301 Force master, on the contrary, is not allowed to configure 1003, FE 201 BE 301 performance is higher than 02 BE301, therefore, the performance of F 02 BE301 is lower than
, 控制 自 將F 01 力主 , 相反則不允許。 , control will be F 01 force master, but not allowed.
上 , 自 決策和控制FE和BE的同步 , 使得 統始終 行于最佳性能下, 特別是 于FE和BE的非 你部署, 兔由于手工 換所戶生的 各中 同。 On, self-decision and control of the synchronization of FE and BE, so that the system is always in the best performance, especially for the non-deployment of FE and BE, rabbits are the same because of the manual exchange of households.
統 System
在本 中, 提供了 的 統, 于 分布式部署、 且 各 存儲 的 各(例 , 包括 SS ER 各 等) 。 In this paper, the system is provided in a distributed deployment, and each storage (for example, including SS ER, etc.).
本 的 的 統包括性能監控 、 決策 、 以及 控制 , 休 The system includes performance monitoring, decision making, and control.
性能監控 于 各的FE、和/或 于 各的 BE, 于 性能監控 所在的FE或BE 同 所在的FE或BE 的BE或FE 同的 各 , 得到 各 結果 決策 于接收未自性能監控 的 各 結果, 各 結果 各 生客 的FE或BE 未 生客 BE或FE 同 的 的 各 是否滿足預先配置的同步 控制 于在 決策 的 結果 滿足同步 的情況下, 預先配置的同步 規則 各未 生客 的BE或FE 同步 。 The performance is monitored in each FE, and/or in each BE, and the FE or BE where the performance monitoring is located is the same as the BE or FE of the FE or BE where the performance is monitored, and each result is determined to receive the results of the performance monitoring. , each result of each customer's FE or BE does not have a customer BE or FE, whether each meets the pre-configured synchronization control, in the case that the result of the decision meets the synchronization, the pre-configured synchronization rules are not the raw BE or FE synchronization.
其中, 的 各 結果可以包括以下至少 預 定吋同 內 的 同的 、 預定 同 內 Wherein, each of the results may include the following at least the same
的 同的 同大于 同 值的 、 預定 同 內 的 同的平均 同。
, 在 各 結果滿足以下至少 的情況下, 決策 可以 滿足同步 預定 同 內 The same is the same as the same average of the same value. In the case that each result satisfies at least the following, the decision can satisfy the synchronization
的 同的 同大于 同 值的 數量 的數 平均 同 、 預定 同 內 的 同的 The same number of the same number greater than the same value, the same as the same
同大于 的第 同 值的 數量在 求量中所占的比例 The proportion of the same number of values greater than the sum of the quantities
的比例 。 proportion .
, 各可以力以下 荃枚, , 各 位置寄存器 各 寄存器 用戶 各 。 的 統。 Each of the following registers can be used for each of the register registers. System.
4是 本 的 的 統的 。 4 is the unit of this.
4所示,分布 的 各 各由主 F 01和各 F 02 ,部署在不同的地理位置 分布 R的數 存儲 各由主 BE301 和各 BE302 , 部署在不同的地理位置, 且 BE301和各 BE 302可以 01、 各 F 02不在同 地理位置。 4, the distribution of each of the main F 01 and each F 02, the number of storage in the different geographical distribution R is stored by the main BE301 and each BE302, deployed in different geographical locations, and BE301 and each BE 302 can 01. Each F 02 is not in the same geographical location.
在本 中, 在FE上部署性能監控 , 即, 4所示, 性 能監控 101部署在主 F 01上,性能監控 102部署在各 F 02 上, 性能監控 101 于監控 FE 201 BE 301的 同, 監控 102 于監控各 F 02 同BE302的 同。 In this example, performance monitoring is deployed on the FE, that is, as shown in FIG. 4, the performance monitoring 101 is deployed on the main F 01, the performance monitoring 102 is deployed on each F 02, and the performance monitoring 101 is monitored on the FE 201 BE 301. 102 monitors each F 02 and BE302.
決策 401和 控制 501可以部署在相同的 上, 也 可以分別部署在不同的 上, , 可以將 決策 401 和 控制 501部署在同 地理位置。 The decision 401 and the control 501 can be deployed on the same or separately, and the decision 401 and the control 501 can be deployed in the same geographical location.
下面以 F 01 障 , 休說明 本 的 Below is the F 01 barrier.
統中在FE 障 , FE BE的性能 FE和BE的
。In the FE barrier, FE BE performance FE and BE .
F 01 障 , STP和 F 01的信令 路中 , 各 由 , STP將所有 各 送到各 F 02。 由于 BE301 未 障, 因此, F 02 BE301的用戶 完成 各 的 。 性能監控 102可以 監控F 02 BE301的 同, 以定期上 的方式 決策 401。性能監控 102可以預先 配置 同 T , 使得上 決策 401的信息可以包括 本 同 內的 、 平均 同和 同大于 同 T 的 。 In the signaling path of F 01 , STP and F 01 , each and every STP will be sent to each F 02 . Since the BE301 is unobstructed, the users of the F 02 BE301 complete each. Performance monitoring 102 can monitor the same as F02 BE301 and make decisions 401 on a regular basis. The performance monitoring 102 can be pre-configured with the same T, so that the information of the upper decision 401 can include the same, the same and the same as the same T.
決策 401收集性能監控 102上 的性能 , 且 和分析預先配置的 同 T2內 FE 202的所有性能監控 的性能 。 Decision 401 collects performance on performance monitoring 102 and analyzes the performance of all performance monitoring of pre-configured FE 202 within T2.
決策 401使用預先配置的性能 未 定是否需要 BE自 。性能 可以包括平均 同 T3和 比率 T4, 果在 同 T2內, 平均 同 T3, 或者 同大于 同 T 的 的比率大于 比 率 T4, 決策 401 需要 BE自 , 通 控 制 501 。 Decision 401 uses pre-configured performance to determine if BE is required. The performance may include an average of the same T3 and the ratio T4. If the ratio is the same as T3 in the same T2, or the ratio of the same T is greater than the ratio T4, the decision 401 requires BE self, and the control system 501.
控制 501收到 決策 401 的指示 , 需要 是否允 許BE自 , 且 介 BE作力新的 BE。 果分布 允許自 , 且各 BE302 行狀 常, 則 控制 501首先 控制 FE 301 各 , 然 控制各 FE 302 力主 , Control 501 receives an indication of decision 401, whether or not to allow BE to be self-contained, and to introduce a new BE. If the fruit distribution is allowed, and each BE302 is in a row, the control 501 first controls each of the FE 301, and then controls each FE 302.
BE302 到BE301, F 02 BE302完成 各 的 。 BE302 to BE301, F 02 BE302 complete each.
下面將以 BE301 障 , 休說明 本 的 統 中在BE 障 , FE BE的性能 FE和BE的 The following will be the BE301 barrier, the rest of the system in the BE barrier, FE BE performance FE and BE
步驟。
BE301 障 , 需要各 BE302 力主 , 而 STP仍然將所 有 各 送到 01, 01只能 BE302的用戶 完成 各 的 。 step. The BE301 barrier requires each BE302 to be the master, while the STP still sends all of them to 01, 01 and only the BE302 users can complete each.
性能監控 101監控 FE 201 BE 302的 同, 以定期 上 的方式, 決策 401。 性能監控 101可以預先配置 同 T , 使得上 決策 401的信息可以包括本 同 內的 、平均 同和 同大于 同 T 的 。 Performance Monitoring 101 monitors FE 201 BE 302 in the same way as decision-making 401. The performance monitoring 101 can be pre-configured with the same T, so that the information of the upper decision 401 can include the same, the same and the same as the same T.
決策 401收集性能監控 101上 的性能 , 且 和分析預先配置的 同 T2內 FE 201的所有性能監控 的性能 。 決策 401 使用預先配置的性能 未 定是否需要 FE自 。 性能 可以包括平均 同 T3和 Decision 401 collects performance on performance monitoring 101 and analyzes the performance of all performance monitoring of pre-configured FE 201 within T2. Decision 401 Use pre-configured performance Undetermined if FE is required. Performance can include averages with T3 and
比率 T4, 果在 同 T2內, 平均 同 T3, 或 者 同大于 同 T 的 的比率大于 Ratio T4, if it is within the same T2, the average is the same as T3, or the ratio of the same is greater than the same T is greater than
比率 T4, 決策 401 需要 FE自 , 通 控制 501 。 For the ratio T4, the decision 401 requires FE self-control and 501 control.
控制 501收到 決策 401 的指示 , 需要 是否配 置 FE自 , 且 介 FE作力新的 FE。 2中, 果分布 配置 允許自 , 且各 F 02 行狀 常(且FE202 BE302 同的 各 量能 滿足 各需求),則 控制 501 首先 FE 202 令 , 然 控制 FE 201 令 , STP 將所有 各 送到F 02, F 02 BE302完成 各 的 。 Control 501 receives an indication of decision 401, whether FE is required to be configured, and FE is the new FE. 2, the fruit distribution configuration is allowed, and each F 02 line is always (and the same amount of FE202 BE302 can meet the requirements), then control 501 first FE 202 command, then control FE 201 command, STP will send all to F 02, F 02 BE302 complete each.
, 控制 501 自 FE或 BE 可以 使用 1所示的 先 表格。 , Control 501 from FE or BE can use the first table shown in 1.
1中的每 介 先 指定了 FE和BE的自 策略, 例 ,
在 1001中, F 01 BE301的 先 高于BE302, 因此, 果FE 201 BE 302的性能低于 , 控制 自 將BE 301 力主 , 相反則不允許 配置 1003, FE 201 BE 301的性能高 于F 02 BE301, 因此, 果F 02 BE301的性能低于 Each of the 1s specifies the self-policy of FE and BE, for example, In 1001, F 01 BE301 is higher than BE302 first. Therefore, if the performance of FE 201 BE 302 is lower than that of BE BE 301, the opposite is not allowed to configure 1003. The performance of FE 201 BE 301 is higher than F 02 BE301. Therefore, the performance of F 02 BE301 is lower than
控制 自 將F 01 力主 , 相反則不允許。 Control self-pressing F 01 force master, but not allowed.
于 統中存在 以上的FE和BE的情況, 同 可以按照上 方法 , 休 前所 的 似, 里不再 。 此 , 除了 4中所示的在FE上 性能監控 的情況 外, 也可 以在BE 性能監控 , 而監控FE的 , 且,在必要的情況下, 可以在FE和BE上 性能監控 , 而 到相互 測的目的。 In the case of the above FE and BE in the system, the same can be done according to the above method, before the break, no longer. Therefore, in addition to the performance monitoring on the FE shown in 4, it is also possible to monitor the FE performance, and monitor the FE, and, if necessary, the performance monitoring on the FE and BE, and to the mutual measurement. the goal of.
此外, 在本 明中, 控制 可以 或 令 、 建立或 SCTP 等手段 和BE的 , 休的 方式是本 領域 木 的, 本文不再 。 In addition, in the present invention, the control can be either stipulated, established or SCTP, and BE, and the way of Hugh is in this field, and this article is no longer.
上 統, 自 決策和控制FE和BE的同步 , 使得 統始終 行于最佳性能下, 特別是 于FE和BE的非 你部署, 兔由于手工 換所戶生的 各中 同。 Up-to-date, self-determination and control of the synchronization of FE and BE, so that the system always performs at the best performance, especially for the non-deployment of FE and BE, the rabbits are replaced by the manual exchange of households.
上 , 借助于本 的上 木 , 在FE和BE的 障自 上,通 FE BE 同的 性能 行監控, FE BE的同 步 , 兔不必要的FE和BE ,近 FE和BE的自 同 統 各性能, 且 兔手工 的 各中 同。 以上 力本 的較佳 而已, 不用以限制本 , 凡在 本 的精神和原則 內, 所作的任何修改、 等同替換、 等, 包 含在本 的 內。
With the help of the above-mentioned wood, in the FE and BE barriers, the FE BE has the same performance line monitoring, FE BE synchronization, rabbit unnecessary FE and BE, near FE and BE self-conformity performance And the rabbits are handmade. The above is better than the limit, and any modifications, equivalents, etc. made within this spirit and principle are included in this document.
Claims
1. 的 方法, 于 分布式部署、 且 各 1. Method for distributed deployment, and each
存儲 的 各 , 其特 在于, 方法包括 Each of the stored items, the method includes
在 結果 滿足所述同步 的情況下, 同步 規則 各未 生客 的 或前端 同步 。 In the case where the result satisfies the synchronization, the synchronization rules are not synchronized with each other or the front end.
2. 要求 1所述的方法, 其特 在于, 在所 各的前端 或 生客 , 方法 步包括 2. The method of claim 1 is characterized in that, in each of the front ends or the customer, the method step comprises
友生客 的 前端或 The front end of the friend
到 各 結果、 和/或 各未 生客 的 或前 To each result, and/or to each
3. 要求 1所述的方法, 其特 在于, 的 各 結果包括以下至少 預定吋同 內 的 同的 、 預定 同 內 的 同的 同大于 同 值的 數量、 預定 同 內 的 同的平均 同。 3. The method of claim 1 is characterized in that each of the results includes at least the same, the same within the same predetermined, the same number greater than the same value, and the same average within the predetermined same.
4. 要求 3所述的方法, 其特 在于, 在所 各 4. The method of claim 3, characterized in that
滿足以下至少 的情況下, 滿足 同步 預定 同 內 的 同的 同大于 If at least the following conditions are met, the same and greater than the same within the synchronization schedule are satisfied.
同 值的 數量 的數量 、 預定 同 內 The number of the same value, the same as
的 同的平均 同大于平均 同 、 預定 同 內 的 同的 同大于 的第
The same average is greater than the average, the same as the same within the same
5. 要求 1所述的方法, 其特 在于, 同步 規則包括 先 。 5. The method of claim 1 is characterized in that the synchronization rule comprises first.
6. 要求 1至5 中任 項 的方法, 其特 在于, 各力以下 荃枚、 、 各 位置寄存器 各 寄存器 用戶 各 。 6. The method of any one of the items 1 to 5 is characterized in that each of the following registers and each register of each position register is used.
7. 的 統, 于 分布式部署、 且 各 7. System, distributed deployment, and
存儲 的 各 , 其特 在于, 統包括性能監控 、 決策 、 以及 控制 , 其中, Each of the storage includes a performance monitoring, a decision, and a control, wherein
性能監控 于 各的前端、 和/或 于 各的 , 于 性能監控 所在的前端或 通信的 或前端 同的數 的 各 , 得到 各 結果 Performance is monitored at each front end, and/or each of the front ends of the performance monitoring or the same number of communications or front ends.
滿足同步 Satisfy synchronization
控制 于在所 決策 的 結果 滿足 同 步 的情況下, 同步 規則 各未 生客 的 或前端 同步 。 It is controlled that the synchronization rules are not synchronized with the front end or the front end when the result of the decision is satisfied.
8. 要求 7所述的 統, 其特 在于, 的 各 結果包括以下至少 預定吋同 內 的 同的 、 預定 同 內 的 同的 同大于 同 值的 數量、 預定 同 內 的 同的平均 同。
8. The system of claim 7 is characterized in that each of the following results includes at least the same, the same and the same within the predetermined same size, the same number of the same value, and the same average within the same time.
9. 要求 8 的 統, 其特 在于, 在所 各 結 果滿足以下至少 的情況下, 決策 9. The requirement of 8 is that the decision is made when the results satisfy at least the following
滿足所述同步 Satisfy the synchronization
預定 同 內 的 同的 同大于 The same and the same within
同 值的 數量 的數量 、 預定 同 內 The number of the same value, the same as
的 同的平均 同大于平均 同 、 預定 同 內所述 的 同的 同大于 的第 The same average is greater than the average and the same as the same as stated in the same
同 值的 數量在 求量中所占的比例 的比例 。 The ratio of the proportion of the same value to the proportion of the quantity.
10. 要求7至9中任 項 的 統, 其特 在于, 各力以下 荃枚、 、 各 位置寄存器 各 寄存器 用戶 各 。
10. The system of any one of the items 7 to 9 is required, and each of the registers of the respective registers is different from each other.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910236738.7A CN102056207B (en) | 2009-10-29 | 2009-10-29 | Method and system for realizing disaster recovery and switching |
CN200910236738.7 | 2009-10-29 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010145428A1 true WO2010145428A1 (en) | 2010-12-23 |
Family
ID=43355813
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2010/073261 WO2010145428A1 (en) | 2009-10-29 | 2010-05-26 | Method and system for implementing disaster recovery switch |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102056207B (en) |
WO (1) | WO2010145428A1 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109242414A (en) * | 2018-08-16 | 2019-01-18 | 深圳前海启航供应链管理有限公司 | A kind of contract management system |
CN116193384A (en) * | 2021-11-26 | 2023-05-30 | 中兴通讯股份有限公司 | Disaster recovery switching method, system, electronic equipment and storage medium |
CN115225467A (en) * | 2022-07-05 | 2022-10-21 | 中国铁道科学研究院集团有限公司 | 5G-EIR disaster recovery backup, fault detection and service recovery method for railway 5G private network system |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1447606A (en) * | 2002-03-22 | 2003-10-08 | 华为技术有限公司 | Redundant disaster method for realizing adscription of location registers throuth mobile communication operating system |
CN1946058A (en) * | 2006-10-28 | 2007-04-11 | 武汉市中光通信公司 | Soft exchange device allopatric disaster recovery solution system and its method for software exchange network |
CN101247568A (en) * | 2008-03-12 | 2008-08-20 | 中兴通讯股份有限公司 | Data fault-tolerance system and method and intermediate equipment |
CN101426306A (en) * | 2008-10-24 | 2009-05-06 | 中国移动通信集团山东有限公司 | A disaster tolerance switching method, system and apparatus |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6434713B1 (en) * | 1998-09-03 | 2002-08-13 | Lg Information & Communications, Ltd. | Processor management method of mobile communication home location register (HLR) system |
CN100372302C (en) * | 2004-09-23 | 2008-02-27 | 华为技术有限公司 | Remote disaster allowable system and method |
CN101365182B (en) * | 2008-09-23 | 2012-07-04 | 中兴通讯股份有限公司 | Method, system and media gateway implementing relay gateway disaster tolerated uninterrupted call |
-
2009
- 2009-10-29 CN CN200910236738.7A patent/CN102056207B/en active Active
-
2010
- 2010-05-26 WO PCT/CN2010/073261 patent/WO2010145428A1/en active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1447606A (en) * | 2002-03-22 | 2003-10-08 | 华为技术有限公司 | Redundant disaster method for realizing adscription of location registers throuth mobile communication operating system |
CN1946058A (en) * | 2006-10-28 | 2007-04-11 | 武汉市中光通信公司 | Soft exchange device allopatric disaster recovery solution system and its method for software exchange network |
CN101247568A (en) * | 2008-03-12 | 2008-08-20 | 中兴通讯股份有限公司 | Data fault-tolerance system and method and intermediate equipment |
CN101426306A (en) * | 2008-10-24 | 2009-05-06 | 中国移动通信集团山东有限公司 | A disaster tolerance switching method, system and apparatus |
Also Published As
Publication number | Publication date |
---|---|
CN102056207A (en) | 2011-05-11 |
CN102056207B (en) | 2015-04-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3614632B1 (en) | Large-scale real-time multimedia communications | |
JP5550792B2 (en) | Method for finding a set of routes in a network | |
CN101438541B (en) | Relay transmission device and relay transmission method | |
CN102014458B (en) | Method and apparatus for admission control of data in a mesh network | |
US10075892B2 (en) | Mobile device for use in a dynamic and stochastic asynchronously updated wireless ad-hoc network | |
CN111669418B (en) | Data communication method, data synchronization method, system, device, gateway equipment, server and base station equipment | |
CN101145930B (en) | Method, system and device for guaranteeing reliable transmission of multicast service | |
EP2874354B1 (en) | A network element and a controller for managing the network element | |
CN103986651A (en) | SDN controller and control method thereof | |
US20120099425A1 (en) | Network device and method for establishing path data | |
CN101466158B (en) | Communication method in a network comprising a primary network and a secondary network | |
US11197177B2 (en) | Outdoor lighting network as a contingency connectivity infrastructure | |
WO2010145428A1 (en) | Method and system for implementing disaster recovery switch | |
EP3504902B1 (en) | Outdoor lighting network as a contingency connectivity infrastructure | |
US20130064134A1 (en) | Rapid deployment devices in wireless self-organizing networks and methods for same | |
CN100403731C (en) | Method for controlling communication transmission path in stacked equipment domain | |
JP2007329549A (en) | Network system and routing selection apparatus thereof | |
CN100496023C (en) | Method for transmitting link-state information | |
WO2015096432A1 (en) | Method and system for controlling network topology structure | |
CN103312612A (en) | Optimizing method and system for multi-constrain quality-of-service routing | |
CN102447611A (en) | Method and system for establishing bidirectional point-to-multipoint label switched path as well as method and system for removing bidirectional point-to-multipoint label switched path | |
del Pilar Salamanca et al. | A survey on IEEE 802.11-based MANETs and DTNs for survivor communication in disaster scenarios | |
CN101287270B (en) | Method and apparatus for service transmission | |
US20060209683A1 (en) | Packet transmission method and station in packet ring telecommunications network | |
JP3550349B2 (en) | Broadcast communication system and method for feeding back statistical information |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10788824 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10788824 Country of ref document: EP Kind code of ref document: A1 |