CN113037815A - Method for operating EIP (extended Access Point) under BWS (broadband remote Access Server) service interruption or EIP service interruption scene - Google Patents
Method for operating EIP (extended Access Point) under BWS (broadband remote Access Server) service interruption or EIP service interruption scene Download PDFInfo
- Publication number
- CN113037815A CN113037815A CN202110212416.XA CN202110212416A CN113037815A CN 113037815 A CN113037815 A CN 113037815A CN 202110212416 A CN202110212416 A CN 202110212416A CN 113037815 A CN113037815 A CN 113037815A
- Authority
- CN
- China
- Prior art keywords
- eip
- bws
- service
- bound
- nat
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 21
- 239000000725 suspension Substances 0.000 claims abstract description 18
- 230000008878 coupling Effects 0.000 abstract description 4
- 238000010168 coupling process Methods 0.000 abstract description 4
- 238000005859 coupling reaction Methods 0.000 abstract description 4
- 238000013507 mapping Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/32—Specific management aspects for broadband networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Beans For Foods Or Fodder (AREA)
Abstract
The invention provides an operation method for an EIP (enhanced Internet protocol) under a BWS (broadband remote Access Server) outage scene or an EIP outage scene, which comprises the following steps of: s1: listing a plurality of scenes of BWS or EIP service suspension, including adding EIP into BWS, starting EIP service, stopping EIP service and moving EIP out of BWS; s2: adding EIP into BWS, starting EIP service, stopping EIP service, and moving EIP out of BWS for operation, respectively, comprising the following steps; s21: adding EIP into BWS, and suspending EIP operation; s22: EIP service is stopped, EIP operation is suspended; s23: the EIP is moved out of the BWS, and the EIP operation is started; s24: and (5) opening the EIP service and starting EIP operation. The invention discloses an operation method for EIP under a BWS (broadband remote Access Server) outage scene or an EIP outage scene, which solves the problems that when the EIP is added into the BWS, the EIP and the BWS generate a coupling relation, and the outage and the start of a product can influence each other.
Description
Technical Field
The invention belongs to the technical field of communication, and particularly relates to an EIP operation method in a BWS (broadband remote Access Server) outage scene or an EIP outage scene.
Background
An Elastic IP Address (EIP) is a public IP Address resource that can be purchased and held independently. The Shared Bandwidth (BWS) can provide the Bandwidth multiplexing capability of multiple IP addresses at a geographic level, and can share the same Bandwidth for the instances of ECS, load balancing, NAT gateway, etc. that bind EIP. When the EIP is added to the BWS, the bandwidth information of the EIP itself will be invalid and the EIP therein will not be clocked any more, but with the passage of time, the BWS or the EIP may cause the product to be out of service due to expiration or defaulting. If BWS is out of service, all EIPs in BWS will halt nat mapping function blocking their traffic, and if EIP is not out of service in BWS, will likewise halt nat mapping function and will stop EIP timing. As long as EIP is added to BWS, the EIP is coupled with BWS, and the stop and start of any product can affect each other.
Disclosure of Invention
In view of the above, the present invention provides an operation method for EIP in BWS outage or EIP outage scenarios to solve the problems that when EIP is added into BWS, it will generate a coupling relationship with BWS, and the outage and the start of the product will affect each other.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a method for operating an EIP (enhanced IP platform) in a BWS (broadband remote Access service) outage scene comprises the following steps of:
s1: listing a plurality of scenes of BWS or EIP service suspension, including adding EIP into BWS, starting EIP service, stopping EIP service and moving EIP out of BWS;
s2: adding EIP into BWS, starting EIP service, stopping EIP service, and moving EIP out of BWS for operation, respectively, comprising the following steps;
s21: adding EIP into BWS, and suspending EIP operation;
s22: EIP service is stopped, EIP operation is suspended;
s23: the EIP is moved out of the BWS, and the EIP operation is started;
s24: and (5) opening the EIP service and starting EIP operation.
Further, the EIP used in step S21 is added to BWS, and suspending EIP operation includes the following steps:
a1, judging whether the EIP is bound with the instance, if so, executing the step A2;
a2, judging whether the EIP is bound with the NAT product, if so, executing the pause operation of the NAT product, otherwise, executing the pause operation of the EIP.
Further, the EIP used in step a2 is added to BWS, and EIP operations are suspended without modifying the current state of the EIP.
Further, the EIP service suspension used in step S22, and the suspension of EIP operation includes the following steps:
b1, judging whether EIP binds the example, if not, modifying EIP state to be the pause state of the unbound example;
b2, if the instance is bound, modifying the state of the EIP to be the suspended state of the bound instance, and then judging whether the EIP is in the out-of-service BWS;
b3, if the EIP is not in the BWS, judging whether the EIP is bound with the NAT product, if the EIP is bound with the NAT, executing the pause operation of the NAT product, if the EIP is not bound with the NAT, executing the pause operation of the EIP;
b4. if the EIP is in the out-of-service BWS, the pause operation of step B3 need not be performed;
b5, judging whether the EIP is in BWS, if yes, not needing to do EIP end timing operation, otherwise executing end timing operation.
Further, the EIP used in step S23 is shifted out of BWS, and the starting EIP operation includes the following steps:
c1: judging whether the EIP binds the instance, if so, performing the step C2;
c2: and judging whether the EIP is bound with the NAT product, if the EIP is bound with the NAT product, executing the opening operation of the NAT product, and if the EIP is not bound with the NAT product, executing the opening operation of the EIP.
Further, the EIP used in step C2 moves out of BWS, starting EIP operation, and does not modify the current state of EIP.
Further, the EIP opening is performed in step S24, and the EIP opening operation includes the following steps:
d1: judging the current state of the EIP, and if the EIP is in the suspended state of the unbound instance, modifying the state of the EIP into the unbound instance state;
d2: if the binding instance is in the suspended state, modifying the EIP state into the binding instance state, and then judging whether the EIP is in the suspended BWS;
d3: if the EIP is not in the service-suspended BWS, judging whether the EIP is bound with an NAT product, if the EIP is bound with the NAT product, executing the opening operation of the NAT product, and if the EIP is not bound with the NAT product, executing the opening operation of the EIP;
d4: if the EIP is in the out-of-service BWS, the suspend operation of step D3 need not be performed;
d5: and judging whether the EIP is in the BWS, if so, not needing to perform the EIP timing starting operation, otherwise, executing the timing starting operation.
Compared with the prior art, the invention has the following beneficial effects: the invention provides an operation method for EIP under BWS (broadband Access Server) outage scenes or EIP outage scenes, wherein the EIP is added into the BWS and generates a coupling relation with the BWS, and the outage and the start of any product can influence each other.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate an embodiment of the invention and, together with the description, serve to explain the invention and not to limit the invention. In the drawings:
FIG. 1 is a schematic diagram illustrating an operation flow of suspending an EIP when the EIP is added to a BWS according to an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating the operation flow of EIP service suspension and EIP pause according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating an EIP operation of moving out of BWS and starting the EIP according to an embodiment of the present invention;
fig. 4 is a schematic diagram of an operation flow of the EIP service and the EIP startup according to the embodiment of the present invention.
Detailed Description
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict.
In the description of the present invention, it is to be understood that the terms "center", "longitudinal", "lateral", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", and the like, indicate orientations or positional relationships based on those shown in the drawings, and are used only for convenience in describing the present invention and for simplicity in description, and do not indicate or imply that the referenced devices or elements must have a particular orientation, be constructed and operated in a particular orientation, and thus, are not to be construed as limiting the present invention. Furthermore, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first," "second," etc. may explicitly or implicitly include one or more of that feature. In the description of the present invention, "a plurality" means two or more unless otherwise specified.
In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meaning of the above terms in the present invention can be understood by those of ordinary skill in the art through specific situations.
The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.
When the EIP is added into the BWS, the EIP and the BWS are coupled, the stop and the start of any product can affect each other, and the following specific scenes are listed:
in a specific scene:
1. stopping taking the product:
(1) in the scene, because the EIP is already in the BWS, the suspension timing operation is not needed, and only the EIP is required to be modified into a suspension state and suspend a nat mapping function to block the flow;
(2) in the scene, because the EIP is already in the BWS, the pause timing operation is not needed, and because the BWS is in the shutdown state and the nat mapping function of the EIP is paused, the EIP only needs to be modified into the pause state;
(3) in the scene, due to the fact that the BWS where the EIP is located is out of service, only the nat mapping function needs to be paused to block the flow;
(4) in the EIP service suspension state, the BWS where the EIP is located is suspended, in the scene, the EIP is already in the service suspension state, the nat mapping function is suspended, the BWS where the EIP is located is suspended, and the EIP does not need to do other operations.
2. The product is taken orally:
(1) in the scene, the nat mapping function is already suspended in the EIP service suspension state, and the BWS service does not change the service suspension state of the EIP per se, so that the EIP does not need to do other operations;
(2) in the scene, the nat mapping function is suspended in the BWS service suspension state, and the EIP service does not change the service suspension state of the BWS, so that the EIP only needs to change the suspended state to the normal state;
(3) in the scene, as the EIP is not stopped, when the BWS is started, the nat mapping function of the EIP needs to be recovered to remove the flow blockage;
(4) in the scene, as the BWS where the EIP is located is not stopped, when the EIP is started, the nat mapping function of the EIP needs to be recovered, the flow blockage is relieved, and the suspension state of the EIP is changed into the normal state;
3. EIP moves out of BWS:
(1) in the scene, the EIP is always out of service, and does not need to do other operations;
(2) the non-stop EIP is moved out from the stop BWS, under the scene, the EIP is not stopped, the EIP is moved out from the stop BWS and is not bound by the BWS, the EIP starts to time and recovers the nat mapping function, and the flow blockage is relieved;
(3) the un-serviced EIP is removed from the un-serviced BWS,
in this scenario, the EIP is not suspended, and the normal function of the un-suspended BWS can be maintained, and the un-suspended BWS is removed from the BWS, and only the EIP needs to be timed.
As shown in fig. 1 to 4, a method for operating an EIP in a BWS outage or EIP outage scenario includes the following steps:
s1: listing a plurality of scenes of BWS or EIP service suspension, including adding EIP into BWS, starting EIP service, stopping EIP service and moving EIP out of BWS;
s2: adding EIP into BWS, starting EIP service, stopping EIP service, and moving EIP out of BWS for operation, respectively, comprising the following steps;
s21: adding EIP into BWS, and suspending EIP operation;
s22: EIP service is stopped, EIP operation is suspended;
s23: the EIP is moved out of the BWS, and the EIP operation is started;
s24: and (5) opening the EIP service and starting EIP operation.
As shown in fig. 1, the EIP used in step S21 is added to BWS, and suspending EIP operation includes the following steps:
a1, judging whether the EIP is bound with the instance, if so, executing the step A2;
a2, judging whether the EIP is bound with the NAT product, if so, executing the pause operation of the NAT product, otherwise, executing the pause operation of the EIP.
As shown in FIG. 1, EIP used in step A2 is added to BWS, and EIP operations are suspended without modifying the current state of EIP.
As shown in fig. 2, the EIP service suspension used in step S22 includes the following steps:
b1, judging whether EIP binds the example, if not, modifying EIP state to be the pause state of the unbound example;
b2, if the instance is bound, modifying the state of the EIP to be the suspended state of the bound instance, and then judging whether the EIP is in the out-of-service BWS;
b3, if the EIP is not in the BWS, judging whether the EIP is bound with the NAT product, if the EIP is bound with the NAT, executing the pause operation of the NAT product, if the EIP is not bound with the NAT, executing the pause operation of the EIP;
b4. if the EIP is in the out-of-service BWS, the pause operation of step B3 need not be performed;
b5, judging whether the EIP is in BWS, if yes, not needing to do EIP end timing operation, otherwise executing end timing operation.
As shown in FIG. 3, the EIP used in step S23 is shifted out of BWS, and the EIP start operation comprises the following steps:
c1: judging whether the EIP binds the instance, if so, performing the step C2;
c2: and judging whether the EIP is bound with the NAT product, if the EIP is bound with the NAT product, executing the opening operation of the NAT product, and if the EIP is not bound with the NAT product, executing the opening operation of the EIP.
As shown in FIG. 3, the EIP used in step C2 is shifted out of BWS, and EIP operations are started without modifying the current state of EIP.
As shown in fig. 4, the EIP open at step S24 includes the following steps:
d1: judging the current state of the EIP, and if the EIP is in the suspended state of the unbound instance, modifying the state of the EIP into the unbound instance state;
d2: if the binding instance is in the suspended state, modifying the EIP state into the binding instance state, and then judging whether the EIP is in the suspended BWS;
d3: if the EIP is not in the service-suspended BWS, judging whether the EIP is bound with an NAT product, if the EIP is bound with the NAT product, executing the opening operation of the NAT product, and if the EIP is not bound with the NAT product, executing the opening operation of the EIP;
d4: if the EIP is in the out-of-service BWS, the suspend operation of step D3 need not be performed;
d5: and judging whether the EIP is in the BWS, if so, not needing to perform the EIP timing starting operation, otherwise, executing the timing starting operation.
The invention provides an operation method for EIP under BWS (broadband Access Server) outage scenes or EIP outage scenes, wherein the EIP is added into the BWS and generates a coupling relation with the BWS, and the outage and the start of any product can influence each other.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (7)
1. A method for operating an EIP (enhanced IP protection) under a BWS (broadband remote Server) outage scene or an EIP outage scene, which is characterized by comprising the following steps:
s1: listing a plurality of scenes of BWS or EIP service suspension, including adding EIP into BWS, starting EIP service, stopping EIP service and moving EIP out of BWS;
s2: adding EIP into BWS, starting EIP service, stopping EIP service, and moving EIP out of BWS for operation, respectively, comprising the following steps;
s21: adding EIP into BWS, and suspending EIP operation;
s22: EIP service is stopped, EIP operation is suspended;
s23: the EIP is moved out of the BWS, and the EIP operation is started;
s24: and (5) opening the EIP service and starting EIP operation.
2. The method of claim 1, wherein the EIP operation method is performed in a BWS outage scene or an EIP outage scene, and comprises: the EIP used in step S21 is added to BWS, and suspending EIP operation includes the following steps:
a1, judging whether the EIP is bound with the instance, if so, executing the step A2;
a2, judging whether the EIP is bound with the NAT product, if so, executing the pause operation of the NAT product, otherwise, executing the pause operation of the EIP.
3. The method of claim 2, wherein the EIP is operated in a BWS outage scene or an EIP outage scene, and wherein the EIP comprises: the EIP used in step a2 is added to BWS, and EIP operations are suspended without modifying the current state of the EIP.
4. The method of claim 1, wherein the EIP operation method is performed in a BWS outage scene or an EIP outage scene, and comprises: the EIP service suspension utilized in step S22, suspending EIP operations comprising the steps of:
b1, judging whether EIP binds the example, if not, modifying EIP state to be the pause state of the unbound example;
b2, if the instance is bound, modifying the state of the EIP to be the suspended state of the bound instance, and then judging whether the EIP is in the out-of-service BWS;
b3, if the EIP is not in the BWS, judging whether the EIP is bound with the NAT product, if the EIP is bound with the NAT, executing the pause operation of the NAT product, if the EIP is not bound with the NAT, executing the pause operation of the EIP;
b4. if the EIP is in the out-of-service BWS, the pause operation of step B3 need not be performed;
b5, judging whether the EIP is in BWS, if yes, not needing to do EIP end timing operation, otherwise executing end timing operation.
5. The method of claim 1, wherein the EIP operation method is performed in a BWS outage scene or an EIP outage scene, and comprises: the EIP used in step S23 moves out of BWS, and the EIP starting operation comprises the following steps:
c1: judging whether the EIP binds the instance, if so, performing the step C2;
c2: and judging whether the EIP is bound with the NAT product, if the EIP is bound with the NAT product, executing the opening operation of the NAT product, and if the EIP is not bound with the NAT product, executing the opening operation of the EIP.
6. The method of claim 5, wherein the EIP operation is performed in a BWS outage scene or an EIP outage scene, and comprises: step C2 uses EIP to move out of BWS, starting EIP operation, without modifying the current state of EIP.
7. The method of claim 1, wherein the EIP operation method is performed in a BWS outage scene or an EIP outage scene, and comprises: the EIP opening operation used in step S24 includes the following steps:
d1: judging the current state of the EIP, and if the EIP is in the suspended state of the unbound instance, modifying the state of the EIP into the unbound instance state;
d2: if the binding instance is in the suspended state, modifying the EIP state into the binding instance state, and then judging whether the EIP is in the suspended BWS;
d3: if the EIP is not in the service-suspended BWS, judging whether the EIP is bound with an NAT product, if the EIP is bound with the NAT product, executing the opening operation of the NAT product, and if the EIP is not bound with the NAT product, executing the opening operation of the EIP;
d4: if the EIP is in the out-of-service BWS, the suspend operation of step D3 need not be performed;
d5: and judging whether the EIP is in the BWS, if so, not needing to perform the EIP timing starting operation, otherwise, executing the timing starting operation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110212416.XA CN113037815A (en) | 2021-02-25 | 2021-02-25 | Method for operating EIP (extended Access Point) under BWS (broadband remote Access Server) service interruption or EIP service interruption scene |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110212416.XA CN113037815A (en) | 2021-02-25 | 2021-02-25 | Method for operating EIP (extended Access Point) under BWS (broadband remote Access Server) service interruption or EIP service interruption scene |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113037815A true CN113037815A (en) | 2021-06-25 |
Family
ID=76462288
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110212416.XA Pending CN113037815A (en) | 2021-02-25 | 2021-02-25 | Method for operating EIP (extended Access Point) under BWS (broadband remote Access Server) service interruption or EIP service interruption scene |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113037815A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1398720A2 (en) * | 2002-08-30 | 2004-03-17 | NTT DoCoMo, Inc. | Suspended service recovery system, method and computer program product |
| CN111314368A (en) * | 2020-02-27 | 2020-06-19 | 紫光云技术有限公司 | Method for realizing tube renting intercommunication by using load balancer |
| CN111641513A (en) * | 2020-05-11 | 2020-09-08 | 紫光云技术有限公司 | Method for measuring time of elastic public network IP |
| CN112118327A (en) * | 2020-08-04 | 2020-12-22 | 紫光云(南京)数字技术有限公司 | Method and system for conveniently and quickly modifying IP (Internet protocol) of elastic network card under public cloud |
-
2021
- 2021-02-25 CN CN202110212416.XA patent/CN113037815A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1398720A2 (en) * | 2002-08-30 | 2004-03-17 | NTT DoCoMo, Inc. | Suspended service recovery system, method and computer program product |
| CN111314368A (en) * | 2020-02-27 | 2020-06-19 | 紫光云技术有限公司 | Method for realizing tube renting intercommunication by using load balancer |
| CN111641513A (en) * | 2020-05-11 | 2020-09-08 | 紫光云技术有限公司 | Method for measuring time of elastic public network IP |
| CN112118327A (en) * | 2020-08-04 | 2020-12-22 | 紫光云(南京)数字技术有限公司 | Method and system for conveniently and quickly modifying IP (Internet protocol) of elastic network card under public cloud |
Non-Patent Citations (4)
| Title |
|---|
| 华为云: "弹性公网IP共享带宽介绍-华为云", 《HTTPS://WWW.HUAWEICLOUD.COM/ZHISHI/1585010404372.HTML》 * |
| 开发者中心: "欠费说明_使用指南_云主机", 《HTTPS://DEVELOPER.QINIU.COM/QVM/6330/OWE-THE-INSTRUCTIONS》 * |
| 星速运小编: "阿里云NAT网关绑定EIP", 《HTTPS://WWW.XINGSUYUN58.COM/16352.HTML》 * |
| 阿里云: "当阿里云ECS实例EIP到期或欠费时的缴费或充值说明", 《HTTPS://WWW.JOELLED.COM/COMBLEM/1192.HTML》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220131740A1 (en) | Method and system of a dynamic high-availability mode based on current wide area network connectivity | |
| JP5227776B2 (en) | Method and system for executing service reception control | |
| CN102413046B (en) | Method for forwarding flow by means of virtual router redundancy protocol backup set and equipment | |
| US8826265B2 (en) | Data concentrator initiated multicast firmware upgrade | |
| US20100267390A1 (en) | Fault-tolerant, multi-network detour router system for text messages, data, and voice | |
| WO2014059844A1 (en) | Method and device for dynamically switching gateway of distributed resilient network interconnect | |
| CN104320494A (en) | Intelligent home doorbell system based on cloud technology and Internet of Things technology | |
| TW200306736A (en) | Flexible and scalable integrated access device | |
| CN103117946B (en) | Traffic sharing method based on isolating device with isolation gateway connected applications | |
| CN103124290B (en) | Based on the load-balancing method of reverse isolation device with isolation gateway connected applications | |
| CN102239670B (en) | A kind of load sharing method and device | |
| JP2009532948A (en) | System and method for active geographical redundancy | |
| CN101547198A (en) | Method and device for controlling connections of network security equipment | |
| CN103108416A (en) | Ip Multimedia Subsystem (IMS) equipment and data processing method thereof | |
| CN101917491A (en) | Method and terminal for improving domain name resolution efficiency | |
| CN113037815A (en) | Method for operating EIP (extended Access Point) under BWS (broadband remote Access Server) service interruption or EIP service interruption scene | |
| CN113824594A (en) | Message sending method and equipment | |
| CN103051484B (en) | Session service processing method, system and Session Border Controll | |
| CN203057286U (en) | All-IP soft switch technology-based service integration access controller | |
| JP2009278297A (en) | Gateway device, communication system including the same, and communication method | |
| RU2560817C2 (en) | Method, system and associated device for transmission of information like service | |
| CN113438159B (en) | Transmission method and device of segmented routing strategy and network transmission system | |
| CN103782563A (en) | Event-based keep alive times in communication networks | |
| JP2013239884A (en) | Ims service system, ims terminal, and method of detecting ims service server from internet line | |
| JP6259622B2 (en) | COMMUNICATION DEVICE, RADIO NETWORK SYSTEM, RADIO NETWORK CONTROL METHOD, AND RADIO NETWORK CONTROL PROGRAM |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210625 |