CN112492634B - Transmission PTN escape circuit implementation method and device based on mobile network - Google Patents
Transmission PTN escape circuit implementation method and device based on mobile network Download PDFInfo
- Publication number
- CN112492634B CN112492634B CN202011456463.0A CN202011456463A CN112492634B CN 112492634 B CN112492634 B CN 112492634B CN 202011456463 A CN202011456463 A CN 202011456463A CN 112492634 B CN112492634 B CN 112492634B
- Authority
- CN
- China
- Prior art keywords
- service
- circuit
- tunnel
- emergency plan
- escape
- 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
Images
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
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method and a device for realizing a transmission PTN escape circuit based on a mobile network, wherein the method comprises the following steps: calling an SC API (application program interface), receiving a circuit ID (identity) to be recovered and associated with service related information, associating the original service in-out tunnel topological connection, setting a tunnel without passing through a link and requesting a tunnel route, creating a tunnel, generating a plan, and calling an interface to feed back to an upper system; calling an SC API (application program interface), receiving the ID (identity) of the escape circuit, inquiring related information, deleting the original service, creating a new service through an escape circuit tunnel, updating after the emergency plan scheduling is finished, and calling the interface to feed back to an upper system; and calling an SC API (application program interface), receiving the ID (identity) of the circuit needing to be recovered and associated related information, deleting the service of the escape circuit, newly creating a service bound with the original tunnel, migrating and recovering the data of the emergency plan after the back-cut is finished, and feeding back the upper system by using the calling interface. The method and the device have the advantages that the guarantee capability of key users is greatly improved, and the customer satisfaction is improved.
Description
Technical Field
The invention relates to the field of PTN networks of mobile operators, in particular to a method and a device for realizing a transmission PTN escape circuit based on a mobile network.
Background
Various services carried in the PTN network of a mobile operator, including a customer service and a base station service, are often provided to important parties, major conference events and major enterprises and institutions, and some important circuits according to priorities are necessary to ensure that the services cannot be interrupted.
In practical application, a main path and a standby path are set for a service to ensure switching when the service is interrupted; and then setting a service rerouting to ensure that a new path is recalculated for switching or protecting after the service path is interrupted. However, in reality, various situations in the network vary widely, and it is impossible to exclude simultaneous interruption of the main and standby paths, and the situation that the network does not have a rerouting condition will cause interruption of the service to be unable to recover.
At present, under the condition that the method for adjusting the service cannot solve the problem, the method only can urge the outside line constructors to recover the fault. This time is often long and can lead to long interruptions of the restore circuit, which can create an undesirable impression on the customer, greatly reduce customer perception, and even have a significant impact on the customer.
Disclosure of Invention
In order to solve the problem that the service can not be rerouted and recovered after the main service and the standby service are simultaneously interrupted, the invention provides a method and a device for realizing a PTN (packet transport network) escape circuit based on mobile network, which can be used for rapidly recovering the service through the escape circuit when a reinsurance circuit configured with an emergency plan is subjected to a service interruption fault which can not be solved by the conventional network at the cost of occupying more network resources in advance and ensuring that the service interruption can not be normally recovered, thereby improving the user satisfaction.
In order to achieve the purpose, the invention adopts the following technical scheme:
in an embodiment of the present invention, a method for implementing a PTN-based escape circuit for transmission based on a mobile network is provided, where the PTN-based escape circuit is implemented by a transmission super controller based on an interface of "SPNPTN OMC northbound interface service configuration technical specification" of a mobile enterprise, and includes:
generating an emergency plan: calling an SC API (application program interface), receiving a circuit ID (identity) to be recovered and associated with service related information, associating the original service in and out of tunnel topological connection, setting a tunnel route without passing through a link and requesting a tunnel, creating a tunnel, generating a plan, and calling an upper system interface to feed back an upper system;
emergency plan scheduling: calling an SC API (application program interface), receiving an ID (identity) of the escape circuit, inquiring related information, deleting an original service, creating a new service through an escape circuit tunnel, updating after the emergency plan is scheduled, and calling an interface of an upper system to feed back the upper system;
and (3) recovering an emergency plan: and calling an SC API (application program interface), receiving the ID (identity) of the circuit needing to be recovered and associating related information, deleting the escape circuit service, newly creating a service bound with the original tunnel, migrating and recovering the emergency plan data after the backstepping is finished, and calling an upper system interface to feed back an upper system.
Further, the emergency plan generation specifically includes:
the upper-layer system calls an external API (application program interface) of the transmission super controller, provides circuit information of an escape circuit needing emergency plan generation and transmission side source and destination end information comprising a network element, a port and a VLAN (virtual local area network) of an AZ (asynchronous receiver/transmitter) end;
the transmission super controller associates the received transmission side source and destination information with the source and destination information of the full service stored by the transmission super controller, so as to realize the association between the circuit and the service;
the transmission super controller inquires corresponding service, tunnel, route and topology connection data through the associated service ID, searches a source node output port and a destination node input port of the original tunnel, and associates the corresponding topology connection;
using original parameters, adding two topological connections associated in the previous step as tunnel routes which are different from original tunnel routes without passing through links, and requesting the tunnel routes again;
using the result returned by the re-request route to establish a tunnel, marking the tunnel as an escape circuit tunnel of the appointed service by a name, and using the tunnel as an idle state without carrying any service;
the transmission super controller associates the newly-built escape circuit tunnel, tunnel route, and corresponding circuit, service, tunnel and route to generate an emergency plan;
and feeding back the detailed information support of the emergency plan to an upper-layer system through an interface according to the requirement.
Further, the emergency plan scheduling specifically includes:
the upper system calls an external API (application program interface) of the transmission super controller, transmits a circuit ID (identity) and applies for an interrupt circuit which cannot recover the service in a conventional mode to carry out emergency plan scheduling;
the transmission super controller receives a circuit ID needing to switch the escape circuit, associates the circuit ID with the generated emergency plan, and obtains the tunnel ID, the service source and destination end and other detailed information of the escape circuit;
the transmission super controller deletes the original service through the service ID, binds the existing escape circuit tunnel through the stored detailed information of the original service, and creates the service again, and after the creation is successful, the newly created service is the transmission service of the restored re-protection circuit, so that the switching of the escape circuit is realized;
the transmission super controller stores the circuit for switching and recovering the escape circuit and the newly-built service ID in the previous step into an emergency plan and changes the related state;
and returning the switched result to an upper-layer system through an interface for backup association.
Further, the emergency plan recovery specifically comprises:
when the upper-layer system judges that the fault of the reassurance circuit is recovered and needs to be switched back, an external API (application program interface) of a transmission super controller is called, and a circuit ID (identity) needing to be subjected to emergency plan recovery is transmitted;
the transmission super controller receives a circuit ID needing escape circuit switching, associates the circuit ID with an emergency plan in a changed state, and obtains detailed information of an original service, an ID of a newly-built service and an ID of an original tunnel;
the transmission super controller deletes the corresponding service through the ID of the newly-built service, then binds the original tunnel through the stored detailed information of the original service, and re-creates the service, wherein the newly-built service is the service after the original tunnel path is switched and the escape circuit tunnel is released, and the emergency plan recovery is completed at the moment;
the super controller is transmitted to migrate relevant data of the circuit after the switching back, the service newly built in the last step and the emergency circuit tunnel, the relevant data in the processes of scheduling the emergency plan and recovering the emergency plan to a history table, and meanwhile, the emergency plan is recovered to the original state which is not scheduled, and the relevant service is updated to be the latest service, namely the service newly built in the last step;
and returning the result of the recovery of the emergency plan and the ID of the latest service to an upper-layer system through an interface for backup association.
In an embodiment of the present invention, a device for implementing a PTN escape circuit based on mobile network is further provided, where the device is a transmission super controller and is implemented based on an interface of "SPNPTN OMC northbound interface service configuration technical specification" of a mobile enterprise, and the device includes:
the emergency plan generating module is used for calling an SC API (application program interface), receiving the ID of the circuit needing to be recovered, associating the relevant information of the service, associating the original service in and out of the tunnel topological connection, setting a tunnel route which is required to be requested without passing through a link, creating a tunnel, generating a plan, and calling an interface of an upper system to feed back the upper system;
the emergency plan scheduling module is used for calling an SC API (service provider interface), receiving the ID (identity) of the escape circuit, inquiring related information, deleting the original service, creating a new service through an escape circuit tunnel, updating after the emergency plan scheduling is finished, and calling an upper system interface to feed back an upper system;
and the emergency plan recovery module is used for calling the SC API, receiving the ID of the circuit needing to be recovered and related information, deleting the escape circuit service, newly creating a service bound with the original tunnel, migrating and recovering the emergency plan data after the back cut is finished, and calling the upper system interface to feed back the upper system.
Further, the emergency plan generating module is specifically configured to:
the upper layer system calls an external API (application program interface) of the transmission super controller, provides circuit information of an escape circuit needing to be generated in an emergency plan, and transmits source and destination end information of a side, wherein the source and destination end information comprises a network element, a port and a VLAN (virtual local area network) of an AZ (AZ) end;
the transmission super controller associates the received transmission side source and destination information with the source and destination information of the full service stored by the transmission super controller, so as to realize the association between the circuit and the service;
the transmission super controller inquires corresponding service, tunnel, route and topology connection data through the associated service ID, searches a source node output port and a destination node input port of the original tunnel, and associates the corresponding topology connection;
using original parameters, adding two topological connections associated in the previous step as tunnel routes which are different from original tunnel routes without passing through links, and requesting the tunnel routes again;
using the result returned by the re-request route to establish a tunnel, marking the tunnel as an escape circuit tunnel of the appointed service by a name, and using the tunnel as an idle state without carrying any service;
the transmission super controller associates the newly-built escape circuit tunnel and tunnel route with the corresponding circuit, service, tunnel and route to generate an emergency plan;
and feeding back the detailed information support of the emergency plan to an upper-layer system through an interface according to the requirement.
Further, the emergency plan scheduling module is specifically configured to:
the upper system calls an external API (application program interface) of the transmission super controller, transmits a circuit ID (identity) and applies for an interrupt circuit which cannot recover the service in a conventional mode to carry out emergency plan scheduling;
the transmission super controller receives a circuit ID of an escape circuit needing to be switched, associates the circuit ID with a generated emergency plan, and obtains an escape circuit tunnel ID, a service source and destination end and other detailed information;
the transmission super controller deletes the original service through the service ID, binds the existing escape circuit tunnel through the stored detailed information of the original service, and re-creates the service, wherein after the creation is successful, the newly created service is the transmission service of the restored re-protection circuit, so that the switching of the escape circuit is realized;
the transmission super controller stores the circuit for switching and recovering the escape circuit and the newly-built service ID in the previous step into an emergency plan and changes the related state;
and returning the switched result to an upper-layer system through an interface for backup association.
Further, the emergency plan recovery module is specifically configured to:
when judging that the failure of the reassurance circuit is recovered and the switching-back is needed, the upper layer system calls an external API (application program interface) of the transmission super controller and transmits a circuit ID (identity) needing to be subjected to emergency plan recovery;
the transmission super controller receives a circuit ID needing escape circuit switching, associates the circuit ID with an emergency plan in a changed state, and obtains detailed information of an original service, an ID of a newly-built service and an ID of an original tunnel;
the transmission super controller deletes corresponding services through the ID of the newly-built services, then binds the original tunnel through the stored detailed information of the original services, and re-creates the services, wherein the newly-built services are the services after the original tunnel path is switched and the escape circuit tunnel is released, and at the moment, the recovery of the emergency plan is completed;
the transmission super controller transfers relevant data of the circuit after being switched back, the service newly built in the last step and the emergency circuit tunnel, and relevant data in the processes of emergency plan scheduling and emergency plan recovery to a history table, simultaneously recovers the emergency plan to an unscheduled initial state, and updates the relevant service to be the latest service, namely the service newly built in the last step;
and returning the result of the recovery of the emergency plan and the ID of the latest service to an upper-layer system through an interface for backup association.
In an embodiment of the present invention, a computer device is further provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the PTN escape circuit implementation method based on mobile network transmission is implemented.
In an embodiment of the present invention, a computer-readable storage medium is further provided, where the computer-readable storage medium stores a computer program for executing the method for implementing the PTN escape circuit based on mobile network transmission.
Has the advantages that:
1. the invention is used for solving the problem that the rerouting and recovering service can not be carried out after the main service and the standby service are simultaneously interrupted, greatly improves the guarantee capability of the heavy-point user and improves the customer satisfaction.
2. The invention is realized based on the current group interface standard, the internal logic of the pure transmission super controller is realized, the interface is not required to be optimized and adjusted, the network management of manufacturers is not required to be more, the network management of each manufacturer is not required to be subjected to new function development and more interface adaptation, the feasibility of realizing the function is greatly improved, the cost investment of upgrading multiple manufacturers is reduced, and the time for realizing the function is reduced.
Drawings
Fig. 1 is a flow chart of an implementation method of a PTN escape circuit based on mobile network according to an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating a process of generating an emergency plan according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of an emergency plan scheduling process according to an embodiment of the present invention;
FIG. 4 is a schematic diagram illustrating an emergency plan recovery process according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an embodiment of an escape circuit implementation device for PTN transmission based on a mobile network;
fig. 6 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
Detailed Description
The principles and spirit of the present invention will be described below with reference to several exemplary embodiments, it being understood that these embodiments are presented only to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As will be appreciated by one skilled in the art, embodiments of the present invention may be embodied as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.
According to the embodiment of the invention, the invention provides a method and a device for realizing a transmission PTN escape circuit based on a mobile network, which mainly establish an emergency plan tunnel outside a main/standby service path for the PTN service of a protection circuit in the support range of the existing enterprise label interface; the tunnel is normally used as an idle state and does not bear any service; under the extreme condition that the existing main and standby tunnel protection and service path rerouting can not normally recover the service, the service bearing tunnel is switched to an idle emergency plan tunnel for recovering the service, the service path is recovered after the service fault is recovered, and the emergency plan tunnel is recovered to an idle state.
The principles and spirit of the present invention are explained in detail below with reference to several representative embodiments of the invention.
Fig. 1 is a flowchart of an implementation method of a PTN transmission escape circuit based on a mobile network according to an embodiment of the present invention. As shown in fig. 1, the method is implemented for a transmission super controller based on an interface of "SPNPTN OMC northbound interface service configuration technical specification" of a mobile enterprise, and includes:
s1, generating an emergency plan: calling an SC API (application program interface), receiving a circuit ID (identity) to be recovered and associated with service related information, associating the original service in and out of tunnel topological connection, setting a tunnel route without passing through a link and requesting a tunnel, creating a tunnel, generating a plan, and calling an upper system interface to feed back an upper system;
s2, emergency plan scheduling: calling an SC API (service center interface application program), receiving an ID (identity) of an escape circuit, inquiring related information, deleting an original service, creating a new service through an escape circuit tunnel, updating after an emergency plan is scheduled, and calling an interface of an upper system to feed back the upper system;
s3, emergency plan recovery: and calling an SC API (application program interface), receiving the ID (identity) of the circuit needing to be recovered and associating related information, deleting the escape circuit service, newly creating a service bound with the original tunnel, migrating and recovering the emergency plan data after the backstepping is finished, and calling an upper system interface to feed back an upper system.
It should be noted that although the operations of the method of the present invention have been described in the above embodiments and the accompanying drawings in a particular order, this does not require or imply that these operations must be performed in this particular order or that all of the illustrated operations must be performed to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.
For a clearer explanation of the implementation method of the PTN escape circuit based on mobile network transmission, a specific embodiment is described below, but it should be noted that the embodiment is only for better explaining the present invention and is not to be construed as an inappropriate limitation to the present invention.
The method is realized for a transmission Super Controller (SC) based on an interface of SPNPTN OMC northbound interface service configuration technical specification of a mobile enterprise logo.
Fig. 2 is a schematic diagram of an emergency plan generation process according to an embodiment of the present invention. As shown in fig. 2, the specific process of generating the emergency plan (setting the escape circuit) is as follows:
step 1: and the upper layer system calls an external API (application program interface) of the transmission super controller, provides circuit information of the escape circuit needing to be generated in an emergency plan, and transmits source and destination end information of the side, including information of a network element, a port, a VLAN (virtual local area network) and the like of the AZ end.
And 2, step: the transmission super controller associates the received transmission side source and destination terminal information with the basic information such as source and destination terminals of the total service stored by itself, so as to realize the association between the circuit and the service.
And step 3: and the transmission super controller inquires out corresponding service, tunnel, route and topological connection data through the associated service ID (service 1). And searching a source node output port and a sink node input port of the original tunnel, and associating the source node output port and the sink node input port with corresponding topological connections.
And 4, step 4: and (4) adding two topological connections associated in the last step into the original parameters to re-request the tunnel routing without passing through the link. The tunnel route is a tunnel route different from the original tunnel route path.
And 5: and using the result returned by the re-request route to establish a tunnel, marking the tunnel as an escape circuit tunnel of the designated service through a name, and using the tunnel as an idle state without carrying any service.
Step 6: and the transmission super controller system associates the newly-built escape circuit tunnel and tunnel route with information such as corresponding circuit, service, tunnel and route to generate an emergency plan.
And 7: and feeding back the detailed information support of the emergency plan to an upper-layer system through an interface according to the requirement.
Fig. 3 is a schematic diagram of an emergency plan scheduling process according to an embodiment of the present invention. As shown in fig. 3, the specific flow of emergency plan scheduling (using of the escape circuit) is as follows:
step 1: and the upper layer system calls an external API (application program interface) of the transmission super controller, transmits a circuit ID (identity) and applies for an interrupt circuit which cannot recover the service in a conventional mode to carry out emergency plan scheduling.
Step 2: and the transmission super controller receives the circuit ID of the circuit needing to be switched to the escape circuit, associates the circuit ID with the generated emergency plan, and obtains the ID of the escape circuit tunnel, the ID of the service (service 1), the service source and destination and other detailed information.
And 3, step 3: the transmission super controller deletes the original service through the service ID (service 1), and then binds the existing escape circuit tunnel through the stored detailed information of the original service to recreate the service (service 2). After the creation is successful, the newly-created service (service 2) is the transmission service of the restored reassuring circuit, so that the switching of the escape circuit is realized.
And 4, step 4: and the transmission super controller saves the circuit switched and recovered by the escape circuit and the newly-built service ID (service 2) into an emergency plan and changes the related state.
And 5: and returning the switched result to an upper-layer system through an interface for backup association.
Fig. 4 is a schematic diagram of an emergency plan recovery process according to an embodiment of the present invention. As shown in fig. 4, the specific process of emergency plan recovery (escape circuit rollback) is as follows:
step 1: and when the upper-layer system judges that the failure of the reassurance circuit is recovered and needs to perform the switching back, calling an external API (application program interface) of the transmission super controller, and transmitting a circuit ID (identity) which needs to perform emergency plan recovery.
Step 2: the transmission super controller receives a circuit ID needing escape circuit switching, associates the circuit ID with an emergency plan in a changed state, and obtains the detailed information of the original service (service 1), the ID of the newly-built service (service 2), the ID of the original tunnel and other information.
And step 3: the transmission super controller deletes the corresponding service through the ID of the newly created service (service 2), and then binds the original tunnel through the stored detailed information of the original service (service 1) to recreate the service (service 3). The newly-established service (service 3) is the service after the original tunnel path has been switched and the escape circuit tunnel is released. At this point, the emergency protocol recovery has been completed.
And 4, step 4: and (4) transferring relevant data of the circuit after the switching back, the service (service 3) newly established in the step (3), the emergency circuit tunnel and the like, and relevant data in the emergency plan scheduling and emergency plan recovery process to a history table by the transmission super controller. And meanwhile, the emergency plan is restored to the unscheduled initial state, and the associated service is updated to be the service (service 3) newly established in the step 3.
And 5: and returning the result of the recovery of the emergency plan and the service ID of the latest service back to the upper-layer system through the interface for backup association.
Based on the same inventive concept, the invention also provides a transmission PTN escape circuit implementation device based on the mobile network. The implementation of the device can be referred to the implementation of the method, and repeated details are not repeated. The term "module," as used below, may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 5 is a schematic structural diagram of an implementation device of a PTN transmission escape circuit based on a mobile network according to an embodiment of the present invention. As shown in fig. 5, the apparatus is a transmission Super Controller (SC), and is implemented based on an interface of "SPNPTN OMC northbound interface service configuration technical specification" of a mobile enterprise, and includes:
an emergency plan generating module 101, configured to call an SC API interface, receive a circuit ID that needs to be recovered and associate service-related information, associate an original service in and out of a tunnel topological connection, set a tunnel route that needs not to pass through a link and request a tunnel route, create a tunnel, generate a plan, and call an upper system interface to feed back an upper system; the method is specifically used for:
the upper layer system calls an external API (application program interface) of the transmission super controller, provides circuit information of an escape circuit needing to be generated in an emergency plan, and transmits source and destination end information of a side, wherein the source and destination end information comprises a network element, a port and a VLAN (virtual local area network) of an AZ (AZ) end;
the transmission super controller associates the received transmission side source and destination information with the source and destination information of the full service stored by the transmission super controller, so as to realize the association between the circuit and the service;
the transmission super controller inquires corresponding service, tunnel, route and topology connection data through the associated service ID, searches a source node output port and a sink node input port of the original tunnel and associates the corresponding topology connection;
using original parameters, adding two topological connections associated in the previous step into a new tunnel route which is not the same as the original tunnel route path without passing through a link;
using the result returned by the re-request route to establish a tunnel, marking the tunnel as an escape circuit tunnel of the appointed service through a name, and using the tunnel as an idle state without carrying any service;
the transmission super controller associates the newly-built escape circuit tunnel and tunnel route with the corresponding circuit, service, tunnel and route to generate an emergency plan;
and feeding back the detailed information support of the emergency plan to an upper-layer system through an interface according to the requirement.
The emergency plan scheduling module 102 is configured to call an SC API interface, receive an escape circuit ID and query related information, delete an original service and create a new service through an escape circuit tunnel, update after the emergency plan scheduling is completed, and call an upper system interface to feed back an upper system; the method is specifically used for:
the upper system calls an external API (application program interface) of the transmission super controller, transmits a circuit ID (identity) and applies for an interrupt circuit which cannot recover the service in a conventional mode to carry out emergency plan scheduling;
the transmission super controller receives a circuit ID of an escape circuit needing to be switched, associates the circuit ID with a generated emergency plan, and obtains an escape circuit tunnel ID, a service source and destination end and other detailed information;
the transmission super controller deletes the original service through the service ID, binds the existing escape circuit tunnel through the stored detailed information of the original service, and re-creates the service, wherein after the creation is successful, the newly created service is the transmission service of the restored re-protection circuit, so that the switching of the escape circuit is realized;
the transmission super controller stores the circuit for switching and recovering the escape circuit and the newly-built service ID in the previous step into an emergency plan and changes the related state;
and returning the switched result to an upper-layer system through an interface for backup association.
The emergency plan recovery module 103 is used for calling an SC API (application program interface), receiving a circuit ID (identity) to be recovered and related information, deleting an escape circuit service, creating a new service bound with an original tunnel, migrating and recovering emergency plan data after the back cut is completed, and calling an upper system interface to feed back an upper system; the method is specifically used for:
when the upper-layer system judges that the fault of the reassurance circuit is recovered and needs to be switched back, an external API (application program interface) of a transmission super controller is called, and a circuit ID (identity) needing to be subjected to emergency plan recovery is transmitted;
the transmission super controller receives a circuit ID needing escape circuit switching, associates the circuit ID with an emergency plan in a changed state, and obtains detailed information of an original service, an ID of a newly-built service and an ID of an original tunnel;
the transmission super controller deletes corresponding services through the ID of the newly-built services, then binds the original tunnel through the stored detailed information of the original services, and re-creates the services, wherein the newly-built services are the services after the original tunnel path is switched and the escape circuit tunnel is released, and at the moment, the recovery of the emergency plan is completed;
the super controller is transmitted to migrate relevant data of the circuit after the switching back, the service newly built in the last step and the emergency circuit tunnel, the relevant data in the processes of scheduling the emergency plan and recovering the emergency plan to a history table, and meanwhile, the emergency plan is recovered to the original state which is not scheduled, and the relevant service is updated to be the latest service, namely the service newly built in the last step;
and returning the result of the recovery of the emergency plan and the ID of the latest service to an upper-layer system through an interface for backup association.
It should be noted that although several modules of the mobile network based transport PTN escape circuit implementation are mentioned in the above detailed description, such partitioning is merely exemplary and not mandatory. Indeed, the features and functionality of two or more of the modules described above may be embodied in one module according to embodiments of the invention. Conversely, the features and functions of one module described above may be further divided into embodiments by a plurality of modules.
Based on the aforementioned inventive concept, as shown in fig. 6, the present invention further provides a computer device 200, which includes a memory 210, a processor 220, and a computer program 230 stored on the memory 210 and operable on the processor 220, wherein the processor 220 implements the aforementioned method for implementing the PTN escape circuit based on mobile network transmission when executing the computer program 230.
Based on the foregoing inventive concept, the present invention further provides a computer-readable storage medium storing a computer program for executing the foregoing method for implementing the PTN escape circuit based on mobile network.
The invention provides a method and a device for realizing a PTN (packet transport network) escape circuit based on mobile network transmission, which can reserve an emergency escape path for a key point guarantee circuit by using a resource real occupation mode of an appointed path under the condition that an OMC (operation management center) of a manufacturer does not support PTN resource occupation, and can ensure that when the main and standby service paths of the key point guarantee circuit are interrupted due to faults, the final path recovery guarantee is carried out when the rerouting recovery service cannot be carried out due to the shortage of network physical and network resources.
While the spirit and principles of the invention have been described with reference to several particular embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, nor is the division of aspects, which is for convenience only as the features in such aspects may not be combined to benefit. The invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
The limitation of the protection scope of the present invention is understood by those skilled in the art, and various modifications or changes which can be made by those skilled in the art without inventive efforts based on the technical solution of the present invention are still within the protection scope of the present invention.
Claims (10)
1. A PTN transmission escape circuit implementation method based on a mobile network is characterized in that the method is implemented for a transmission super controller based on an interface of SPNPTN OMC northbound interface service configuration technical specification of a mobile enterprise, and comprises the following steps:
generating an emergency plan: calling an SC API (application program interface), receiving a circuit ID (identity) to be recovered and associated with service related information, associating the original service in and out of tunnel topological connection, setting a tunnel route without passing through a link and requesting a tunnel, creating a tunnel, generating a plan, and calling an upper system interface to feed back an upper system;
emergency plan scheduling: calling an SC API (application program interface), receiving an ID (identity) of the escape circuit, inquiring related information, deleting an original service, creating a new service through an escape circuit tunnel, updating after the emergency plan is scheduled, and calling an interface of an upper system to feed back the upper system;
and (3) recovering an emergency plan: and calling an SC API (application program interface), receiving the ID (identity) of the circuit needing to be recovered and associating related information, deleting the escape circuit service, newly creating a service bound with the original tunnel, migrating and recovering the emergency plan data after the backstepping is finished, and calling an upper system interface to feed back an upper system.
2. The PTN transmission escape circuit implementation method based on the mobile network as claimed in claim 1, wherein the emergency plan generation specifically comprises:
the upper layer system calls an external API (application program interface) of the transmission super controller, provides circuit information of an escape circuit needing to be generated in an emergency plan, and transmits source and destination end information of a side, wherein the source and destination end information comprises a network element, a port and a VLAN (virtual local area network) of an AZ (AZ) end;
the transmission super controller associates the received transmission side source and destination information with the source and destination information of the full service stored by the transmission super controller, so as to realize the association between the circuit and the service;
the transmission super controller inquires corresponding service, tunnel, route and topology connection data through the associated service ID, searches a source node output port and a destination node input port of the original tunnel, and associates the corresponding topology connection;
using original parameters, adding two topological connections associated in the previous step into a new tunnel route which is not the same as the original tunnel route path without passing through a link;
using the result returned by the re-request route to establish a tunnel, marking the tunnel as an escape circuit tunnel of the appointed service through a name, and using the tunnel as an idle state without carrying any service;
the transmission super controller associates the newly-built escape circuit tunnel, tunnel route, and corresponding circuit, service, tunnel and route to generate an emergency plan;
and feeding back the detailed information support of the emergency plan to an upper-layer system through an interface according to the requirement.
3. The PTN transmission escape circuit implementation method based on the mobile network as claimed in claim 1, wherein the emergency plan scheduling specifically comprises:
the upper system calls an external API (application program interface) of the transmission super controller, transmits a circuit ID (identity) and applies for an interrupt circuit which cannot recover the service in a conventional mode to carry out emergency plan scheduling;
the transmission super controller receives a circuit ID needing to switch the escape circuit, associates the circuit ID with the generated emergency plan, and obtains the tunnel ID, the service source and destination end and other detailed information of the escape circuit;
the transmission super controller deletes the original service through the service ID, binds the existing escape circuit tunnel through the stored detailed information of the original service, and creates the service again, and after the creation is successful, the newly created service is the transmission service of the restored re-protection circuit, so that the switching of the escape circuit is realized;
the transmission super controller stores the circuit for switching and recovering the escape circuit and the newly-built service ID in the previous step into an emergency plan and changes the relevant state;
and returning the switched result to an upper-layer system through an interface for backup association.
4. The PTN transmission escape circuit implementation method based on the mobile network as claimed in claim 1, wherein the emergency plan recovery specifically comprises:
when the upper-layer system judges that the fault of the reassurance circuit is recovered and needs to be switched back, an external API (application program interface) of a transmission super controller is called, and a circuit ID (identity) needing to be subjected to emergency plan recovery is transmitted;
the transmission super controller receives a circuit ID needing escape circuit switching, associates the circuit ID with an emergency plan in a changed state, and obtains detailed information of an original service, an ID of a newly-built service and an ID of an original tunnel;
the transmission super controller deletes the corresponding service through the ID of the newly-built service, then binds the original tunnel through the stored detailed information of the original service, and re-creates the service, wherein the newly-built service is the service after the original tunnel path is switched and the escape circuit tunnel is released, and the emergency plan recovery is completed at the moment;
the transmission super controller transfers relevant data of the circuit after being switched back, the service newly built in the last step and the emergency circuit tunnel, and relevant data in the processes of emergency plan scheduling and emergency plan recovery to a history table, simultaneously recovers the emergency plan to an unscheduled initial state, and updates the relevant service to be the latest service, namely the service newly built in the last step;
and returning the result of the recovery of the emergency plan and the ID of the latest service to an upper-layer system through an interface for backup association.
5. A transmission PTN escape circuit implementation device based on a mobile network is characterized in that the device is a transmission super controller and is implemented based on an interface of a mobile enterprise label SPNPTN OMC northbound interface service configuration technical specification, and the device comprises:
the emergency plan generating module is used for calling an SC API (service provider interface), receiving a circuit ID (identity) to be recovered, associating service related information, associating the original service in and out of a tunnel topological connection, setting a tunnel route which is required to be requested without passing through a link, creating a tunnel, generating a plan, and calling an interface of an upper system to feed back the upper system;
the emergency plan scheduling module is used for calling an SC API (service provider interface), receiving the ID (identity) of the escape circuit, inquiring related information, deleting the original service, creating a new service through an escape circuit tunnel, updating after the emergency plan scheduling is finished, and calling an upper system interface to feed back an upper system;
and the emergency plan recovery module is used for calling the SC API (application program interface), receiving the ID of the circuit needing to be recovered and associating related information, deleting the service of the escape circuit, newly creating the service bound with the original tunnel, migrating and recovering the emergency plan data after the switchback is finished, and calling the interface of the upper system to feed back the upper system.
6. The PTN transmission escape circuit implementation device based on the mobile network as claimed in claim 5, wherein the emergency plan generation module is specifically configured to:
the upper-layer system calls an external API (application program interface) of the transmission super controller, provides circuit information of an escape circuit needing emergency plan generation and transmission side source and destination end information comprising a network element, a port and a VLAN (virtual local area network) of an AZ (asynchronous receiver/transmitter) end;
the transmission super controller associates the received transmission side source and destination information with the source and destination information of the full service stored by the transmission super controller, so as to realize the association between the circuit and the service;
the transmission super controller inquires corresponding service, tunnel, route and topology connection data through the associated service ID, searches a source node output port and a sink node input port of the original tunnel and associates the corresponding topology connection;
using original parameters, adding two topological connections associated in the previous step into a new tunnel route which is not the same as the original tunnel route path without passing through a link;
using the result returned by the re-request route to establish a tunnel, marking the tunnel as an escape circuit tunnel of the appointed service by a name, and using the tunnel as an idle state without carrying any service;
the transmission super controller associates the newly-built escape circuit tunnel and tunnel route with the corresponding circuit, service, tunnel and route to generate an emergency plan;
and feeding back the detailed information support of the emergency plan to an upper-layer system through an interface according to the requirement.
7. The PTN transmission escape circuit implementation device based on the mobile network as claimed in claim 5, wherein the emergency plan scheduling module is specifically configured to:
the upper system calls an external API (application program interface) of the transmission super controller, transmits a circuit ID (identity) and applies for an interrupt circuit which cannot recover the service in a conventional mode to carry out emergency plan scheduling;
the transmission super controller receives a circuit ID needing to switch the escape circuit, associates the circuit ID with the generated emergency plan, and obtains the tunnel ID, the service source and destination end and other detailed information of the escape circuit;
the transmission super controller deletes the original service through the service ID, binds the existing escape circuit tunnel through the stored detailed information of the original service, and re-creates the service, wherein after the creation is successful, the newly created service is the transmission service of the restored re-protection circuit, so that the switching of the escape circuit is realized;
the transmission super controller stores the circuit for switching and recovering the escape circuit and the newly-built service ID in the previous step into an emergency plan and changes the relevant state;
and returning the switched result to an upper-layer system through an interface for backup association.
8. The PTN transmission escape circuit implementation device based on the mobile network as claimed in claim 5, wherein the emergency plan recovery module is specifically configured to:
when the upper-layer system judges that the fault of the reassurance circuit is recovered and needs to be switched back, an external API (application program interface) of a transmission super controller is called, and a circuit ID (identity) needing to be subjected to emergency plan recovery is transmitted;
the transmission super controller receives a circuit ID needing escape circuit switching, associates the circuit ID with an emergency plan in a changed state, and obtains detailed information of an original service, an ID of a newly-built service and an ID of an original tunnel;
the transmission super controller deletes the corresponding service through the ID of the newly-built service, then binds the original tunnel through the stored detailed information of the original service, and re-creates the service, wherein the newly-built service is the service after the original tunnel path is switched and the escape circuit tunnel is released, and the emergency plan recovery is completed at the moment;
the super controller is transmitted to migrate relevant data of the circuit after the switching back, the service newly built in the last step and the emergency circuit tunnel, the relevant data in the processes of scheduling the emergency plan and recovering the emergency plan to a history table, and meanwhile, the emergency plan is recovered to the original state which is not scheduled, and the relevant service is updated to be the latest service, namely the service newly built in the last step;
and returning the result of the recovery of the emergency plan and the ID of the latest service to an upper-layer system through an interface for backup association.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1-4 when executing the computer program.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for performing the method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011456463.0A CN112492634B (en) | 2020-12-10 | 2020-12-10 | Transmission PTN escape circuit implementation method and device based on mobile network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011456463.0A CN112492634B (en) | 2020-12-10 | 2020-12-10 | Transmission PTN escape circuit implementation method and device based on mobile network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112492634A CN112492634A (en) | 2021-03-12 |
| CN112492634B true CN112492634B (en) | 2023-03-14 |
Family
ID=74917367
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011456463.0A Active CN112492634B (en) | 2020-12-10 | 2020-12-10 | Transmission PTN escape circuit implementation method and device based on mobile network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112492634B (en) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100531137C (en) * | 2006-08-25 | 2009-08-19 | 中兴通讯股份有限公司 | Method for establishing control side tunnel in mobile communication system multicast service |
| CN104065501A (en) * | 2013-03-22 | 2014-09-24 | 中兴通讯股份有限公司 | Method for positioning network fault in network management system and device thereof |
| CN107566266B (en) * | 2016-06-30 | 2019-09-27 | 中兴通讯股份有限公司 | The retransmission method and device, the network equipment of quick heavy-route |
| CN107666437A (en) * | 2016-07-27 | 2018-02-06 | 中兴通讯股份有限公司 | A kind of static tunnel restoration method, apparatus and network node |
| CN110912818A (en) * | 2019-11-26 | 2020-03-24 | 中盈优创资讯科技有限公司 | Method and system for judging same route of PTN (packet transport network) service |
-
2020
- 2020-12-10 CN CN202011456463.0A patent/CN112492634B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112492634A (en) | 2021-03-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP3974652B2 (en) | Hardware and data redundancy architecture for nodes in communication systems | |
| CN111586114A (en) | Business cooperative processing method and related equipment | |
| CN106878072B (en) | Message transmission method and device | |
| CN104869057A (en) | OpeFlow switch graceful restart processing method, device and OpeFlow controller | |
| CN111817869A (en) | Network configuration recovery method and related equipment thereof | |
| JP5869041B2 (en) | Method for mapping network topology request to physical network, computer program product, mobile communication system, and network configuration platform | |
| CN115022909B (en) | UPF network element, data transmission method, equipment and medium based on core network | |
| US20200403851A1 (en) | Network alarm method, device, system and terminal | |
| US20230132861A1 (en) | Switching method and apparatus, device, and storage medium | |
| CN101262528B (en) | A multi-gateway backup method for voice access of network call | |
| WO2010127625A2 (en) | Seats processing method, exchange and call center | |
| CN108900441B (en) | Network switching method, first electronic device and readable storage medium | |
| CN111371680B (en) | Route management method, device, equipment and storage medium for dual-computer hot standby | |
| CN112492634B (en) | Transmission PTN escape circuit implementation method and device based on mobile network | |
| CN113727221A (en) | Intelligent optical network control method, device and system | |
| JPH10502221A (en) | Mobility in telecommunications networks | |
| CN115314924A (en) | UPF pool intelligent balance system and implementation method | |
| CN111436162A (en) | Processing method and equipment | |
| WO2018014882A1 (en) | Method and device for acquiring router information, and router addressing apparatus and system | |
| CN111698142B (en) | Message forwarding method and device, electronic equipment and storage medium | |
| CN112073980B (en) | Service migration method and system for mobile edge computing | |
| CN101223722B (en) | Method for soft re-routing in optical network | |
| CN102164094B (en) | Multi-link traffic reallocation method and device | |
| CN113365165B (en) | Method and equipment for dynamically switching transport network rerouting service | |
| CN117499963A (en) | Service processing method, device and storage medium |
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 | ||
| CP02 | Change in the address of a patent holder |
Address after: 200000 room 702-2, No. 4811 Cao'an Road, Jiading District, Shanghai Patentee after: CHINA UNITECHS Address before: Room 1004-4, 10 / F, 1112 Hanggui Road, Anting Town, Jiading District, Shanghai Patentee before: CHINA UNITECHS |
|
| CP02 | Change in the address of a patent holder |