WO2023284366A1 - Dbng-cp的备份方法及装置 - Google Patents

Dbng-cp的备份方法及装置 Download PDF

Info

Publication number
WO2023284366A1
WO2023284366A1 PCT/CN2022/089582 CN2022089582W WO2023284366A1 WO 2023284366 A1 WO2023284366 A1 WO 2023284366A1 CN 2022089582 W CN2022089582 W CN 2022089582W WO 2023284366 A1 WO2023284366 A1 WO 2023284366A1
Authority
WO
WIPO (PCT)
Prior art keywords
dbng
backup
backup group
negotiation
group
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.)
Ceased
Application number
PCT/CN2022/089582
Other languages
English (en)
French (fr)
Inventor
宋雪雁
陈勇
李志军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to EP22841007.2A priority Critical patent/EP4373039A4/en
Publication of WO2023284366A1 publication Critical patent/WO2023284366A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/12—Arrangements for remote connection or disconnection of substations or of equipment thereof
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • 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/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/22—Alternate routing

Definitions

  • Embodiments of the present invention relate to the communication field, and in particular, relate to a backup method and device for a Disaggregated Broadband Network Gateway-Control Plane (DBNG-CP) network function.
  • DBNG-CP Disaggregated Broadband Network Gateway-Control Plane
  • the traditional MAN service gateway that is, Broadband Access Server (BRAS) equipment mainly implements the access control and management functions of fixed-line broadband users.
  • BRAS Broadband Access Server
  • the vBRAS virtual Broadband Access Server
  • the vBRAS with separation of transfer and control realizes centralized management and traffic forwarding of fixed broadband users, improving equipment resource utilization; at the same time, it realizes redundant backup through forwarding plane pooling and control plane cloudification, improving network reliability. Realized by technologies such as load sharing and active/standby backup, the flexibility of business deployment and the reliability of business operation can be improved.
  • DBNG-CP1 and DBNG-CP2 are configured as the same backup group instance, where the backup group instance information may include: backup group members, priority of backup group members, switching strategy, etc.
  • Possible CP failure locations include: link communication between CP-UP, link failure between active and standby CPs, and CP instance failure.
  • BBF WT-459 specifies that the DBNG control plane interface protocol is implemented by Packet Forwarding Control Protocol (PFCP). , but for the important scenario of CP protection, the WT-459 project does not yet have a standard specification supported by the protocol.
  • PFCP Packet Forwarding Control Protocol
  • Embodiments of the present invention provide a DBNG-CP backup method and device to at least solve the problem of backup capability negotiation of DBNG-CP backup group instances in the related art.
  • a DBNG-CP backup method including: a first DBNG-CP sends a backup negotiation request to a second DBNG-CP belonging to the same backup group instance, so as to perform backup capability negotiation; The first DBNG-CP receives a backup negotiation response from the second DBNG-CP in response to the backup negotiation request, thereby completing the master/backup election between the first DBNG-CP and the second DBNG-CP.
  • the master/standby election between the first DBNG-CP and the second DBNG-CP after the master/standby election between the first DBNG-CP and the second DBNG-CP is completed, it further includes: after detecting that the first DBNG-CP of the master member fails, reporting the fault information to the second DBNG-CP, and trigger backup group switching to switch the second DBNG-CP as the primary member.
  • the first DBNG-CP after the first DBNG-CP switches over the backup group due to a failure, it further includes: triggering the switching of all DBNG-UPs managed by the first DBNG-CP in the backup group instance, to Switch to the management of all DBNG-UPs in the backup group instance by the second DBNG-CP.
  • the DBNG-UP reports the fault information carried in the first PFCP protocol message to the second DBNG-CP.
  • the backup group switching after the backup group switching is triggered to switch the second DBNG-CP as the primary member, it further includes: the second DBNG-CP notifies the backup group switching result to the Describe DBNG-UP.
  • the failure of the first DBNG-CP is one of the following: when the first DBNG-CP is active, the failure detected by the first DBNG-CP; the first DBNG-CP is In the offline state, the DBNG-UP detects a failure of the first DBNG-CP through the connection with the first DBNG-CP.
  • the first DBNG-CP and the second DBNG-CP extend the backup capability negotiation message through a private protocol to complete the CP backup capability negotiation.
  • a PFCP node reporting mechanism is used to report the fault information of the first DBNG-CP and notify the backup group switchover.
  • the failure information of the first DBNG-CP is reported through a PFCP node report request message, and the backup group switching notification is performed through a PFCP node report response message.
  • the first DBNG-CP reports the fault information by extending the information element of the PFCP node report request message.
  • the extended information element in the PFCP node report request message includes: a control plane path failure information element and a CP backup group identification information element.
  • the first PFCP protocol message or the second protocol message includes a DBNG-CP backup group identification information element and/or a DBNG-CP fault reporting information element.
  • the encapsulation format of the DBNG-CP backup group identification cell includes at least one of the following: cell type information, cell field length information, DBNG-CP backup group identification information, DBNG-CP Backup group member information, DBNG-CP backup group type information, DBNG-CP backup group policy information.
  • the encapsulation format of the control plane fault reporting cell includes at least one of the following: cell type information, cell field length information, local logical interface IP address information, and remote logical interface IP address information.
  • the first DBNG-CP before the first DBNG-CP sends the backup negotiation request to the second DBNG-CP, it further includes: configuring multiple backup group instances of the first DBNG-CP; for each backup group For example, configure multiple DBNG-UPs managed by the first DBNG-CP, and the active-standby switching strategy of the first DBNG-CP backup group instance.
  • the first DBNG-CP is an active member in the first backup group instance, and a backup member in the second backup group instance.
  • a DBNG-CP backup device including: a sending module configured to send a backup negotiation request to a second DBNG-CP belonging to the same backup group instance, so as to perform backup capability negotiation a receiving module, configured to receive a backup negotiation response from the second DBNG-CP in response to the backup negotiation request, so as to complete the master/backup election between the first DBNG-CP and the second DBNG-CP.
  • a computer-readable storage medium is also provided, and a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to perform any one of the above methods when running Steps in the examples.
  • an electronic device including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to perform any of the above Steps in the method examples.
  • the primary and secondary elections are completed through backup negotiation between the first DBNG-CP and the second DBNG-CP, thereby solving the problem of backup capability negotiation of DBNG-CP backup group instances, and adding DBNG-CP Flexibility of CP backup protection.
  • Fig. 1 is the block diagram of the hardware structure of the computer terminal of the operation DBNG-CP backup method according to the embodiment of the invention
  • Fig. 2 is the flowchart of the DBNG-CP backup method according to the embodiment of the present invention.
  • Fig. 3 is a structural block diagram of a DBNG-CP backup device according to an embodiment of the present invention.
  • Fig. 4 is the schematic diagram according to the DBNG-CP backup processing mechanism of the embodiment of the present invention.
  • Fig. 5 is a flow chart of a BNG-CP backup group instance configuration method according to an embodiment of the present invention.
  • Fig. 6 is a flow chart of fault information reporting processing according to an embodiment of the present invention.
  • FIG. 1 is a block diagram of the hardware structure of the computer terminal running the DBNG-CP backup method according to an embodiment of the present invention.
  • the computer terminal may include one or more (only one is shown in Figure 1) processors 102 (processors 102 may include but not limited to processing devices such as microprocessor MCU or programmable logic device FPGA, etc.) and a memory 104 for storing data, wherein the above-mentioned computer terminal may also include a transmission device 106 and an input and output device 108 for communication functions.
  • FIG. 1 is only for illustration, and it does not limit the structure of the above computer terminal.
  • the computer terminal may also include more or fewer components than shown in FIG. 1 , or have a different configuration than that shown in FIG. 1 .
  • Memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the backup method of the separated broadband network gateway control plane network function DBNG-CP in the embodiment of the present invention, processor 102 by running
  • the computer program stored in the memory 104 executes various functional applications and data processing, that is, implements the above-mentioned methods.
  • the memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include a memory that is remotely located relative to the processor 102, and these remote memories may be connected to a computer terminal through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the transmission device 106 is used to receive or transmit data via a network.
  • the specific example of the above-mentioned network may include a wireless network provided by the communication provider of the computer terminal.
  • the transmission device 106 includes a network interface controller (NIC for short), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, referred to as RF) module, which is used to communicate with the Internet in a wireless manner.
  • RF Radio Frequency
  • FIG. 2 is the flow chart of the backup method of a kind of DBNG-CP according to the embodiment of the present invention, as shown in Fig. 2, this flow process includes the following steps:
  • Step S202 the first DBNG-CP sends a backup negotiation request to the second DBNG-CP belonging to the same backup group instance, to perform backup capability negotiation;
  • Step S204 the first DBNG-CP receives a backup negotiation response from the second DBNG-CP in response to the backup negotiation request, thereby completing the master/backup election between the first DBNG-CP and the second DBNG-CP.
  • step S204 of this embodiment it may further include: after the first DBNG-CP of the active member fails, the first DBNG-CP reports the failure information to the The second DBNG-CP, or the DBNG-UP managed by the first DBNG-CP reports fault information to the second DBNG-CP.
  • after reporting the fault information to the second DBNG-CP it may further include: after the second DBNG-CP detects the reported fault information, triggering a backup group switchover to switch the second DBNG-CP The CP switches to the master member.
  • the DBNG-UP may report the fault information carried in the first PFCP protocol message to the second DBNG-CP.
  • the first DBNG-CP may also include: triggering the switching of all DBNG-UPs managed by the first DBNG-CP in the backup group instance to switch Until the second DBNG-CP manages all DBNG-UPs in the backup group instance.
  • the backup group switching after the backup group switching is triggered to switch the second DBNG-CP as the primary member, it may further include: the second DBNG-CP notifies the backup group switching result to the DBNG-UP.
  • the failure of the first DBNG-CP can be one of the following: when the first DBNG-CP is active, the first DBNG-CP detects a failure; the first DBNG-CP is offline state, the DBNG-UP detects a failure of the first DBNG-CP through the connection with the first DBNG-CP.
  • the first DBNG-CP and the second DBNG-CP extend the backup capability negotiation message through a private protocol to complete the CP backup capability negotiation.
  • a PFCP node reporting mechanism is used to report the failure information of the first DBNG-CP and notify the backup group switchover.
  • the failure information of the first DBNG-CP is reported through the PFCP node reporting request message, and the backup group switching notification is performed through the PFCP node reporting response message.
  • the first DBNG-CP reports the fault information by extending the information element of the PFCP node report request message.
  • the extended information elements in the PFCP node report request message include: a control plane path fault information element and a CP backup group identification information element.
  • step S202 it may also include: configuring multiple backup group instances of the first DBNG-CP; for each backup group instance, configuring multiple DBNG-UP managed by the first DBNG-CP , and the active-standby switching strategy of the first DBNG-CP backup group instance.
  • the first DBNG-CP may be an active member in the first backup group instance, and a backup member in the second backup group instance.
  • the primary and secondary elections can be completed through backup capability negotiation between the first DBNG-CP and the second DBNG-CP, and DBNG-CP fault detection and backup group switching mechanisms are provided, adding DBNG-CP
  • the flexibility of backup protection realizes the management of DBNG-CP master or backup based on the granularity of DBNG-UP.
  • the IE extension of the PFCP protocol meets the requirements of DBNG. -Requirements for CP backup capability negotiation.
  • a DBNG-CP backup device is also provided, which is used to implement the above embodiments and preferred implementation modes, and what has already been described will not be repeated.
  • the term "module” may be a combination of software and/or hardware that realizes a predetermined function.
  • the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
  • FIG. 3 is a structural block diagram of a backup device 100 for a separate broadband network gateway control plane network function DBNG-CP according to an embodiment of the present invention. As shown in FIG. 3 , the device includes a sending module 10 and a receiving module 20 .
  • the sending module 10 is configured to send a backup negotiation request to a second DBNG-CP belonging to the same backup group instance, so as to perform backup capability negotiation.
  • the receiving module 20 is configured to receive a backup negotiation response from the second DBNG-CP in response to the backup negotiation request, so as to complete the master/backup election between the first DBNG-CP and the second DBNG-CP.
  • the above-mentioned modules can be realized by software or hardware. For the latter, it can be realized by the following methods, but not limited to this: the above-mentioned modules are all located in the same processor; or, the above-mentioned modules can be combined in any combination The forms of are located in different processors.
  • the control interface between the DBNG-CP and the DBNG-UP is described using the PFCP protocol as an example. But the present invention is not limited to the PFCP protocol, no matter which protocol the control interface adopts, the given information of the information element (Information Element, IE) type and TLV (Type Length Value) encapsulation can be general.
  • Information Element Information Element
  • TLV Type Length Value
  • a DBNG-CP backup (Redundancy) processing mechanism is provided.
  • DBNG-CP1 and DBNG-CP2 are configured in the same backup group instance, and DBNG-CP1 and DBNG-CP2 pass The heartbeat line between nodes notifies the CP backup (Redundancy) capability, and the heartbeat line communication is completed on the interface between DBNG-CP, and cannot be realized through the control plane interface protocol of DBNG-CP and DBNG-UP.
  • It can be done with a private protocol. In terms of protocol extension requirements, it is necessary to expand the support for Redundancy Group (Redundancy Group) capability IE, and carry out backup (Redundancy) capability negotiation.
  • Fig. 4 is a DBNG-CP backup processing mechanism flowchart, as shown in Fig. 4, the method comprises the steps:
  • Step S401 DBNG-CP1 sends a backup negotiation request (Redundancy Association Request) to DBNG-CP2.
  • Step S402 DBNG-CP1 sends a backup negotiation response (Redundancy Association Response) to DBNG-CP2.
  • DBNG-CP1 and DBNG-CP2 complete the Redundancy capability negotiation, require the heartbeat line between the CPs to carry backup information for notification of backup capabilities, and complete the primary and backup of the first DBNG-CP and the second DBNG-CP election.
  • Step S403 after DBNG-CP1 fails, DBNG-CP1 reports the failure to DBNG-CP2 through the heartbeat line.
  • the DBNG-UP may also report the failure information to DBNG-CP2 through the control plane interface. If the failure of the primary DBNG-CP1 is reported through DBNG-UP, the control plane interface protocol between DBNG-CP and DBNG-UP needs to be extended, for example, protocol extension processing needs to be performed on the PFCP protocol.
  • Step S404 the standby member DBNG-CP2 detects the fault information, triggers DBNG-CP Redundancy instance switching, switches itself as the primary member, and notifies user information to its corresponding user plane network function DBNG-UP, and synchronizes user information entries to DBNG-CP2.
  • This embodiment mainly provides a method for configuring a BNG-CP backup group instance.
  • One DBNG-CP instance in the fixed network may manage hundreds of DBNG-UPs.
  • this embodiment proposes that when configuring a BNG-CP backup group instance, it is necessary to increase the number of DBNG-UP members managed by it.
  • the method includes the following steps:
  • Step S501 configure DBNG-CP1 backup group instance 1;
  • Step S502 configuring DBNG-UP members managed by DBNG-CP1, for example, including DBNG-UPn+1, DBNG-UPn+2, etc.;
  • Step S503 configuring the priority, switching strategy, etc. of the DBNG-CP1 backup group instance
  • Step S504 configure DBNG-CP2 backup group instance 2;
  • Step S505 configuring DBNG-UP members managed by DBNG-CP2, for example, including DBNG-UPm+1, DBNG-UPm+2, etc.;
  • Step S506 configuring the priority, switching strategy, etc. of the DBNG-CP2 backup group instance
  • Step S507 on another network function DBNG-CP2 of the DBNG-CP1 backup group, configure a backup instance group with the same id, namely: add DBNG-UPn+1, and DBNG-UPn+2 is the DBNG-UPn+2 of the backup instance group 1.
  • Step S508 according to the backup algorithm mechanism, the backup instance 1 where DBNG-CP1 is located elects DBNG-CP1 as the master DBNG-CP, and the backup instance 2 where DBNG-CP1 is located elects DBNG-CP1 as the standby DBNG-CP.
  • DBNG-UP is configured as a member of the DBNG-CP backup group instance, and balanced management of DBNG-UP in the network is realized by configuring and managing backup group switching policies of different DBNG-UP groups.
  • This embodiment mainly relates to the processing of reporting Redundancy fault information supported by the PFCP protocol. As described in step S406 of the above embodiment, if the DBNG-CP backup failure information is reported through DBNG-UP, it needs to be supported by the control interface protocol between DBNG-CP and DBNG-UP.
  • FIG. 6 is a flow chart of the PFCP protocol supporting backup fault information reporting process, as shown in Figure 6, mainly including the following steps:
  • step S601 DBNG-CP1 detects a fault as an active CP, and the fault information includes detection of a DBNG-UP connection fault managed by it, or DBNG-CP1 is offline, and DBNG-UP detects the connection of DBNG-CP1 through the connection with DBNG-CP1. Fault.
  • step S602 the DBNG-UP reports the fault information to the standby (standby) DBNG-CP2, and carries the fault information through a PFCP node report request (PFCP Node Report Request).
  • Step S603 DBNG-CP2 triggers local backup group switching according to the backup algorithm mechanism, and switches itself as the master DBNG-CP, and notifies the switching result to DBNG-UP through PFCP Node Report Response.
  • PFCP node report includes PFCP node report request (PFCP Node Report Request) and PFCP Node Report Response (PFCP Node Report Response) two message types.
  • PFCP node report request contains the Alternative SMF IP Address IE, which is used to specify the SMF backup address.
  • the SMF of the 3GPP core network is the control plane network function of the UPF, and the UPF is the user plane network function, corresponding to
  • DBNG-CP is the network function of DBNG control plane
  • DBNG-UP is the network function of DBNG user plane.
  • the backup protection of DBNG-CP is similar to that of SMF. Different from the core network 29.244, the backup protection of DBNG-CP is a dynamic policy configuration, and the master and backup are not manually specified. Therefore, in terms of protocol extension implementation, a new IE implementation needs to be added.
  • the PFCP protocol is used to meet the requirements of DBNG-CP protection flexibility through the existing Node ID IE and Alternative SMF IP Address IE, but the Node ID of DBNG-CP needs to be clarified when PFCP is applied Information, increase the designation of DBNG-UP members, CP Redundancy protection mode, and CP Redundancy priority policy. As shown in Table 1, the CP Redundancy Group IE needs to be added
  • CP backup group identification (Redundancy Group ID) IE encapsulation format is shown in Table 2:
  • the IEs in Table 2 are used to deliver the configuration information of the CP backup group, and their encapsulation is as follows:
  • the 1-2 bytes are used for IE type information encapsulation, and the IE type information is CP Redundancy Group ID (CP Redundancy Group ID) IE.
  • CP Redundancy Group ID CP Redundancy Group ID
  • the 3-4 bytes are used for IE field length information encapsulation.
  • the fifth byte is used for the ID information encapsulation of the CP backup group (CP redundancy Group), representing information such as the name and identifier of the Group group.
  • CP redundancy Group representing information such as the name and identifier of the Group group.
  • the CP backup group member refers to the UP information managed by the CP.
  • the 6th and 7th bytes are used for CP backup group member (CP Redundancy Group Member) information encapsulation, including CP and user side physical interface name (name) or identification (id), or virtual interface name or id, etc.
  • CP backup group member CP Redundancy Group Member
  • the 8th-9th bytes are used for CP backup group type (CP Redundancy Group Type) information encapsulation, used to indicate whether it is hot backup, cold backup or warm backup, etc.
  • CP backup group type CP Redundancy Group Type
  • the 10th-11th bytes are used for CP backup group policy (CP Redundancy Group Policy) information encapsulation, used to describe the CP switching strategy, such as priority, switching strategy, etc.
  • CP backup group policy CP Redundancy Group Policy
  • the node report request includes the control plane path failure report (CP Path Failure Report) IE
  • CP Path Failure Report IE
  • the CP Path Failure Report IE type defined by 3GPP needs to be extended to support Port, Logical Port (such as tunnel, PW) and Node.
  • the Logical Port IE has been added in Chapter 6.6.2 of BBF TR-459. The corresponding type is 32769. For the problem of Node instance failure, it can be understood as based on the port interface, so IE extension is not required.
  • Control Plane Path Failure Report (Control Plane Path Failure Report) is shown in Table 3.
  • This IE is used to report the path failure of the CP instance. If there is a path unreachable failure on the backup group interface, DBNG-UP will report the Node Report Request (Node Report Request) information to DBNG-CP.
  • Node Report Request Node Report Request
  • the specific encapsulation format of the IE is as follows:
  • the 1-2 bytes are used for IE type information encapsulation, and the IE type information is Control Plane Path Failure (Control Plane Path Failure) IE.
  • the 3-4 bytes are used for IE field length information encapsulation.
  • the 5th and 6th bytes are used to carry the IP address information of the local logical interface and the address reachability detection information.
  • the 7th to 8th bytes are used to carry the IP address information of the remote logical interface and the address reachability detection information.
  • IE extension is used to meet the requirements for negotiation of control plane backup (CP Redundancy) capabilities.
  • the extension of the backup negotiation message can be completed through protocol interaction between DBNG-CP1 and DBNG-CP2, and the negotiation interaction process increases the fault detection capability and redundancy processing capability of Redundancy.
  • the IE used in the interactive message can be a newly added Fixed Redundancy IE, or an extension of an existing IE.
  • PFCP Node Report Use the PFCP Node Report (PFCP Node Report) implementation mechanism to complete the CP fault detection and protection group switching process.
  • PFCP Node Report Processing flow, using PFCP Node Report Request (PFCP Node Report Request) and PFCP Node Report Request Response (PFCP Node Report Response) mechanism to carry DBNG-CP fault detection information and protection group switching notification .
  • PFCP Node Report Request PFCP Node Report Request
  • PFCP Node Report Response PFCP Node Report Response
  • IE extension of PFCP Node Report Request PFCP Node Report Request
  • This IE can be a new fixed backup (Fixed Redundancy) IE, or an extension of an existing IE.
  • the IE extension of the PFCP Node Report Response (PFCP Node Report Response) information is used for the new active CP to notify the user flow table to the user plane network function DBNG-UP.
  • Embodiments of the present invention also provide a computer-readable storage medium, in which a computer program is stored, wherein the computer program is set to execute the steps in any one of the above method embodiments when running.
  • the above-mentioned computer-readable storage medium may include but not limited to: U disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM) , mobile hard disk, magnetic disk or optical disk and other media that can store computer programs.
  • ROM read-only memory
  • RAM random access memory
  • mobile hard disk magnetic disk or optical disk and other media that can store computer programs.
  • An embodiment of the present invention also provides an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments.
  • the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.
  • each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices In fact, they can be implemented in program code executable by a computing device, and thus, they can be stored in a storage device to be executed by a computing device, and in some cases, can be executed in an order different from that shown here. Or described steps, or they are fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present invention is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例提供了一种DBNG-CP的备份方法及装置。该方法包括：第一DBNG-CP向属于同一个备份组实例的第二DBNG-CP发送备份协商请求，以进行备份能力协商；所述第一DBNG-CP接收第二DBNG-CP针对所述备份协商请求回复的备份协商响应，从而完成所述第一DBNG-CP与第二DBNG-CP之间的主备选举。通过本发明，解决了DBNG-CP备份组实例的备份能力协商的问题，增加了DBNG-CP备份保护的灵活性。

Description

DBNG-CP的备份方法及装置 技术领域
本发明实施例涉及通信领域，具体而言，涉及一种分离的宽带网络网关控制面网络功能(Disaggregated Broadband Network Gateway-Control Plane,DBNG-CP)的备份方法及装置。
背景技术
传统城域网业务网关，即宽带接入服务(Broadband Access Server，BRAS)设备主要实现固网宽带用户的接入控制与管理功能。
转控分离的vBRAS(virtual Broadband Access Server)实现固定宽带用户的集中管理与流量转发，提升设备资源利用率；同时，通过转发面池化与控制面云化实现冗余备份，提高网络可靠性。通过负荷分担、主备备份等技术实现，可提升业务部署的灵活性及业务运行的可靠性。
为保障DBNG-CP的高可靠性，一般将部署在不同数据中心(Data Center，DC)(可能部署在不同城市，不同机房等)的两个CP配置为同一备份组，主备CP可能位于不同的网络域。如：配置DBNG-CP1和DBNG-CP2为同一备份组实例，这里的备份组实例信息可能包括：备份组成员，备份组成员的优先级，切换策略等。CP可能发生故障位置包括：CP-UP之间链路通信，主备CP之间链路故障，及CP实例故障。
为支持CP的可靠性，需要使用DBNG-CP与DBNG-UP之间的控制面接口协议支持，BBF WT-459指定DBNG控制面接口协议采用报文转发控制协议(Packet Forwarding Control Protocol，PFCP)实现，但是对于CP保护这一重要场景，WT-459项目尚未有协议支持的标准规范。
发明内容
本发明实施例提供了一种DBNG-CP的备份方法及装置，以至少解决相关技术中DBNG-CP备份组实例的备份能力协商的问题。
根据本发明的一个实施例，提供了一种DBNG-CP的备份方法，包括：第一DBNG-CP向属于同一个备份组实例的第二DBNG-CP发送备份协商请求，以进行备份能力协商；所述第一DBNG-CP接收第二DBNG-CP针对所述备份协商请求回复的备份协商响应，从而完成所述第一DBNG-CP与第二DBNG-CP之间的主备选举。
在一个示例性实施例中，完成所述第一DBNG-CP与第二DBNG-CP之间的主备选举之后，还包括：在检测到主成员第一DBNG-CP发生故障后，上报故障信息至所述第二DBNG-CP，并触发备份组切换以将第二DBNG-CP切换为主成员。
在一个示例性实施例中，在第一DBNG-CP因故障发生备份组切换后，还包括：触发所述备份组实例内由所述第一DBNG-CP管理的所有DBNG-UP的切换，以切换至由所述第二DBNG-CP管理所述备份组实例内所有DBNG-UP。
在一示例性实施例中，所述DBNG-UP通过第一PFCP协议消息将携带的所述故障信息上报至所述第二DBNG-CP。
在一示例性实施例中，在触发备份组切换以将第二DBNG-CP切换为主成员之后，还包括：所述第二DBNG-CP通过第二PFCP协议消息将备份组切换结果通告至所述DBNG-UP。
在一示例性实施例中，所述第一DBNG-CP的故障为以下之一：第一DBNG-CP为活动状态下，所述第一DBNG-CP检测到的故障；第一DBNG-CP为离线状态下，所述DBNG-UP通过与所述第一DBNG-CP的连接检测到的第一DBNG-CP的故障。
在一示例性实施例中，所述第一DBNG-CP与第二DBNG-CP之间通过私有协议对备份能力协商消息进行扩展以完成CP备份能力协商。
在一示例性实施例中，采用PFCP节点上报机制，以进行所述第一DBNG-CP的故障信息的上报，以及备份组切换通告。
在一示例性实施例中，通过PFCP节点上报请求消息上报所述第一DBNG-CP的故障信息，以及通过PFCP节点上报响应消息进行备份组切换通告。
在一示例性实施例中，通过对PFCP节点上报请求消息的信元进行扩展以进行所述第一DBNG-CP的故障信息上报。
在一示例性实施例中，PFCP节点上报请求消息中的扩展信元包括：控制面路径故障信元和CP备份组标识信元。
在一示例性实施例中，所述第一PFCP协议消息或所述第二协议消息中包括DBNG-CP备份组标识信元和/或DBNG-CP故障上报信元。
在一示例性实施例中，所述DBNG-CP备份组标识信元的封装格式中包括以下至少之一：信元类型信息、信元字段长度信息、DBNG-CP备份组标识信息、DBNG-CP备份组成员信息、DBNG-CP备份组类型信息、DBNG-CP备份组策略信息。
在一示例性实施例中，控制面故障上报信元的封装格式中包括以下至少之一：信元类型信息、信元字段长度信息、本地逻辑接口IP地址信息、远端逻辑接口IP地址信息。
在一示例性实施例中，所述第一DBNG-CP向第二DBNG-CP发送备份协商请求之前，还包括：配置所述第一DBNG-CP的多个备份组实例；对于每个备份组实例，配置第一DBNG-CP管理的多个DBNG-UP，以及第一DBNG-CP备份组实例的主备切换策略。
在一示例性实施例中，所述第一DBNG-CP在第一备份组实例中为主成员，在第二备份组实例中为备成员。
根据本发明的另一个实施例，提供了一种DBNG-CP的备份装置，包括：发送模块，设置为向属于同一个备份组实例的第二DBNG-CP发送备份协商请求，以进行备份能力协商；接收模块，设置为接收第二DBNG-CP针对所述备份协商请求回复的备份协商响应，从而完成所述第一DBNG-CP与第二DBNG-CP之间的主备选举。
根据本发明的又一个实施例，还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本发明的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
在本发明的上述实施例中，第一DBNG-CP与第二DBNG-CP之间通过备份协商完成主备选举，从而解决了DBNG-CP备份组实例的备份能力协商的问题，增加了DBNG-CP备份保护的灵活性。
附图说明
图1是根据本发明实施例的运行DBNG-CP备份方法的计算机终端的硬件结构框图；
图2是根据本发明实施例的DBNG-CP备份方法的流程图；
图3是根据本发明实施例的DBNG-CP备份装置的结构框图；
图4是根据本发明实施例的DBNG-CP备份处理机制的示意图；
图5是根据本发明实施例的BNG-CP备份组实例配置方法流程图；
图6是根据本发明实施例的故障信息上报处理的流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明的实施例。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请实施例中所提供的方法实施例可以在移动终端、计算机终端、服务器或者类似的运算装置中执行。以运行在网络侧的计算机终端上为例，图1是根据本发明实施例的运行DBNG-CP的备份方法的计算机终端的硬件结构框图。如图1所示，计算机终端可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和用于存储数据的存储器104，其中，上述计算机终端还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述计算机终端的结构造成限定。例如，计算机终端还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可用于存储计算机程序，例如，应用软件的软件程序以及模块，如本发明实施例中的分离的宽带网络网关控制面网络功能DBNG-CP的备份方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至计算机终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106用于经由一个网络接收或者发送数据。上述的网络具体实例可包括计算机终端的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，简称为RF)模块，其用于通过无线方式与互联网进行通讯。
本实施例中提供了一种DBNG-CP的备份方法。图2是根据本发明实施例的一种DBNG-CP的备份方法的流程图，如图2所示，该流程包括可如下步骤：
步骤S202，第一DBNG-CP向属于同一个备份组实例的第二DBNG-CP发送备份协商请求，以进行备份能力协商；
步骤S204，所述第一DBNG-CP接收第二DBNG-CP针对所述备份协商请求回复的备份协商响应，从而完成所述第一DBNG-CP与第二DBNG-CP之间的主备选举。
在本实施例的步骤S204之后，还可包括：在主成员第一DBNG-CP发生故障后，所述第一DBNG-CP通过与备成员第二DBNG-CP之间的心跳线上报故障信息至所述第二DBNG-CP，或通过第一DBNG-CP管理的DBNG-UP上报故障信息至第二DBNG-CP。
在本实施例中，将故障信息上报至所述第二DBNG-CP之后，还可包括：在第二DBNG-CP检测到上报的所述故障信息后，触发备份组切换以将第二DBNG-CP切换为主成员。
在本实施例中，所述DBNG-UP可通过第一PFCP协议消息将携带的所述故障信息上报至所述第二DBNG-CP。
在本实施例中，在第一DBNG-CP因故障发生备份组切换后，还可包括：触发所述备份组实例内由所述第一DBNG-CP管理的所有DBNG-UP的切换，以切换至由所述第二DBNG-CP管理所述备份组实例内所有DBNG-UP。
在本实施例中，在触发备份组切换以将第二DBNG-CP切换为主成员之后，还可包括：所述第二DBNG-CP通过第二PFCP协议消息将备份组切换结果通告至所述DBNG-UP。
在本实施例中，所述第一DBNG-CP的故障可以为以下之一：第一DBNG-CP为活动状态下，所述第一DBNG-CP检测到的故障；第一DBNG-CP为离线状态下，所述DBNG-UP通过与所述第一DBNG-CP的连接检测到的第一DBNG-CP的故障。
在本实施例中，所述第一DBNG-CP与第二DBNG-CP之间通过私有协议对备份能力协商消息进行扩展以完成CP备份能力协商。
在本实施例中，采用PFCP节点上报机制，以进行所述第一DBNG-CP的故障信息的上报，以及备份组切换通告。
在本实施例中，通过PFCP节点上报请求消息上报所述第一DBNG-CP的故障信息，以及通过PFCP节点上报响应消息进行备份组切换通告。
在本实施例中，通过对PFCP节点上报请求消息的信元进行扩展以进行所述第一DBNG-CP的故障信息上报。
在本实施例中，PFCP节点上报请求消息中的扩展信元包括：控制面路径故障信元和CP备份组标识信元。
在本实施例中，在步骤S202之前，还可包括：配置所述第一DBNG-CP的多个备份组实例；对于每个备份组实例，配置第一DBNG-CP管理的多个DBNG-UP，以及第一DBNG-CP备份组实例的主备切换策略。
在本实施例中，所述第一DBNG-CP在第一备份组实例中可以为主成员，而在第二备份组实例中为备成员。
通过本实施的上述步骤，第一DBNG-CP与第二DBNG-CP之间可通过备份能力协商完成主备选举，并且提供了DBNG-CP的故障检测及备份组切换机制，增加了DBNG-CP备份保护的灵活性，实现基于DBNG-UP粒度的DBNG-CP主或备的管理，另外，在备份组成员DBNG-CP与DBNG-UP控制面接口上，对PFCP协议的IE进行扩展满足了DBNG-CP备份能力协商的要求。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种DBNG-CP的备份装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的分离的宽带网络网关控制面网络功能DBNG-CP的备份装置100的结构框图，如图3所示，该装置包括发送模块10和接收模块20。
发送模块10，设置为向属于同一个备份组实例的第二DBNG-CP发送备份协商请求，以进行备份能力协商。
接收模块20，设置为接收第二DBNG-CP针对所述备份协商请求回复的备份协商响应，从而完成所述第一DBNG-CP与第二DBNG-CP之间的主备选举。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
为了便于对本发明所提供的技术方案的理解，下面将结合具体场景的实施例进行详细描述。
需要说明的是，在本发明的实施例中，在DBNG-CP与DBNG-UP之间控制接口，使用PFCP协议为例进行了扩展说明。但本发明不局限于PFCP协议，无论控制接口采用何种协议，给出的信元(Information Element,IE)类型和TLV(Type Length Value)封装信息可以是通用的。
实施例一
在本实施例中，提供了一种DBNG-CP的备份(Redundancy)处理机制，在本实施例中，配置DBNG-CP1和DBNG-CP2在同一个备份组实例，DBNG-CP1和DBNG-CP2通过节点间的心跳线通告CP备份(Redundancy)能力，心跳线通信为运行在DBNG-CP之间的接口上完成，不能通过DBNG-CP与DBNG-UP的控制面接口协议实现，在本实施例中可以采用私有协议完成。协议扩展需求方面，需要扩展支持备份组(Redundancy Group)能力IE，进行备份(Redundancy)能力协商。
图4是DBNG-CP备份处理机制流程图，如图4所示，该方法包括如下步骤：
步骤S401,DBNG-CP1向DBNG-CP2发送备份协商请求(Redundancy Association Request)。
步骤S402，DBNG-CP1向DBNG-CP2发送备份协商响应(Redundancy Association Response)。
通过上述步骤S401-S402，DBNG-CP1与DBNG-CP2完成Redundancy能力协商，要求CP间的心跳线携带备份信息用于备份能力的通告，完成第一DBNG-CP和第二DBNG-CP的主备选举。
步骤S403，在DBNG-CP1发生故障后，DBNG-CP1通过心跳线上报故障到DBNG-CP2。在本实施例中，在DBNG-CP1故障后，也可以通过DBNG-UP通过控制面接口将故障信息上报到DBNG-CP2。如果通过DBNG-UP上报主DBNG-CP1的故障，则需要对DBNG-CP与DBNG-UP之间的控制面接口协议进行扩展，例如，对PFCP协议需要进行协议扩展处理。
步骤S404，备成员DBNG-CP2检测到故障信息，触发DBNG-CP Redundancy实例切换，切换自己为主成员，并通告用户信息到其对应的用户面网络功能DBNG-UP，及同步用户信息表项到DBNG-CP2。
实施例二
本实施例主要提供了一种BNG-CP备份组实例配置方法。固网网络一个DBNG-CP实例可能管理几百个DBNG-UP，存在一个DBNG-CP可以为某些DBNG-UP的主用DBNG-CP，也可以同时作为其他一些DBNG-UP的备用DBNG-CP的情况，为此，本实施例提出，在进行BNG-CP备份组实例配置时，需要增加对其管理的DBNG-UP成员。
如图5所示，该方法包括如下步骤：
步骤S501，配置DBNG-CP1备份组实例1；
步骤S502，配置DBNG-CP1管理的DBNG-UP成员，例如，包括DBNG-UPn+1，DBNG-UPn+2等；
步骤S503，配置DBNG-CP1备份组实例的优先级、切换策略等；
步骤S504，配置DBNG-CP2备份组实例2；
步骤S505，配置DBNG-CP2管理的DBNG-UP成员，例如，包括DBNG-UPm+1，DBNG-UPm+2等；
步骤S506，配置DBNG-CP2备份组实例的优先级、切换策略等；
步骤S507，在DBNG-CP1备份组的另一个网络功能DBNG-CP2上，进行相同id的备份实例组配置，即：增加DBNG-UPn+1，DBNG-UPn+2为备份实例组1的DBNG-UP成员；增加DBNG-UPm+1，DBNG-UPm+2为备份实例组2的DBNG-UP成员。
步骤S508，根据备份算法机制，DBNG-CP1所在的备份实例1选举DBNG-CP1为主DBNG-CP，而DBNG-CP1所在的备份实例2选举DBNG-CP1为备DBNG-CP。
本实施例中，DBNG-CP备份组实例配置的成员是DBNG-UP，通过对不同DBNG-UP组的备份组切换策略配置管理，实现对网络中DBNG-UP的均衡管理。
实施例三
本实施例主要涉及PFCP协议支持的Redundancy故障信息上报处理。如在上述实施例的步骤S406中所描述的，如果DBNG-CP备份故障信息通过DBNG-UP上报，则需要通过DBNG-CP与DBNG-UP间的控制接口协议支持。
在本实施例中，以采用PFCP协议进行备份故障信息上报处理为例，通过采用PFCP节点上报(PFCP Node Report)信息协商来完成。图6是PFCP协议支持备份故障信息上报处理的流程图，如图6所示，主要包括如下步骤：
步骤S601，DBNG-CP1作为active CP检测到故障，此故障信息包括检测到其管理的DBNG-UP连接故障，或DBNG-CP1离线，DBNG-UP通过与DBNG-CP1的连接检测到 DBNG-CP1的故障。
步骤S602，DBNG-UP上报故障信息到备用(standby)DBNG-CP2，通过PFCP节点上报请求(PFCP Node Report Request)携带故障信息。
步骤S603，DBNG-CP2根据备份算法机制，触发本地备份组切换，并切换自己为主DBNG-CP，通过PFCP节点上报响应(PFCP Node Report Response)通告切换结果到DBNG-UP。
实施例四
本实施例提供了一种PFCP备份组(Redundancy Group)支持扩展方案，根据3GPP TS29.244的7.4.5章节描述，PFCP节点上报(PFCP Node Report)包括PFCP节点上报请求(PFCP Node Report Request)和PFCP节点上报响应(PFCP Node Report Response)两种报文类型。其中，PFCP节点上报请求(PFCP Node Report Request)包含了Alternative SMF IP Address IE，用于SMF备份地址的指定，3GPP核心网的SMF为UPF的控制面网络功能，UPF为用户面网络功能，对应到固网网络，DBNG-CP为DBNG控制面网络功能，DBNG-UP为DBNG用户面网络功能。DBNG-CP的备份保护类似于SMF的备份保护。与核心网29.244不同的是，DBNG-CP的备份保护是动态策略配置，非手动指定主备，因此，在协议扩展实现方面，需要增加新的IE实现。在进行BNG-CP备份组实例配置时，需要增加对其管理的DBNG-UP成员，同时，增加主备选择策略配置用于主备DBNG-CP的选举。
在本实施例中，采用PFCP协议，通过已有的Node ID IE及结合Alternative SMF IP Address IE可以满足DBNG-CP保护灵活性的需求，只是在进行PFCP应用时，需要明确DBNG-CP的Node ID信息，增加对DBNG-UP成员，CP Redundancy保护模式，及CP Redundancy优先级策略等的指定。如表1所示，需要新增CP备份组标识(CP Redundancy Group)IE
表1
Figure PCTCN2022089582-appb-000001
其中，CP备份组标识(Redundancy Group ID)IE封装格式如表2所示：
表2
Figure PCTCN2022089582-appb-000002
表2中的IE用于CP备份组的配置信息下发，其封装情况如下：
第1-2字节用于IE类型信息封装，IE类型信息为CP备份组标识(CP Redundancy Group  ID)IE。
第3-4字节用于IE字段长度信息封装。
第5字节用于CP备份组(CP redundancy Group)的ID信息封装，表征Group组的name，identifier等信息。
在本实施例中，CP备份组成员(CP Group member)指的是CP管理的UP信息。
第6-7字节用于CP备份组成员(CP Redundancy Group Member)信息封装，包括CP与用户侧物理接口名称(name)或标识(id)，或虚拟接口name或id等。
第8-9字节用于CP备份组类型(CP Redundancy Group Type)信息封装，用于说明是热备、冷备或温备等。
第10-11字节用于CP备份组策略(CP Redundancy Group Policy)信息封装，用于说明CP倒换的策略，如优先级、切换策略等。
实施例五
本实施例提供一种PFCP Redundancy故障信息上报协议扩展方案，根据3GPP TS29.244的7.4.5章节描述，节点上报请求(Node Report Request)包括了控制面路径故障上报(CP Path Failure Report)IE，但是3GPP定义的控制面路径故障上报(CP Path Failure Report)IE类型，需要扩展IE类型支持Port及Logical Port(如tunnel,PW)及Node。在BBF TR-459 6.6.2章节已经增加了逻辑端口(Logical Port)IE。对应type是32769。对于Node实例故障问题，可以理解为基于port接口的，因此，不需要再进行IE扩展。
在本实施例中，控制面路径故障上报(Control Plane Path Failure Report)IE封装格式如表3所示。
表3
Figure PCTCN2022089582-appb-000003
该IE用于CP实例路径故障上报，如果备份组接口存在路径不可达故障，则DBNG-UP上报节点上报请求(Node Report Request)信息到DBNG-CP。该IE的具体封装格式如下：
第1-2字节用于IE类型信息封装，IE类型信息为控制面路径故障(Control Plane Path Failure)IE。
第3-4字节用于IE字段长度信息封装。
第5-6字节用于本地逻辑接口IP地址信息携带，及地址可达性检测信息。
第7-8字节用于远端逻辑接口IP地址信息携带，及地址可达性检测信息。
在本发明的上述实施例中，1)为增加DBNG-CP备份保护的灵活性，实现基于UP粒度的DBNG-CP主或备的管理。2)采用备份组成员DBNG-CP1、DBNG-CP2与用户面网络功能DBNG-UP控制面接口上，采用IE扩展满足对控制面备份(CP Redundancy)能力协商的要求。3)DBNG-CP1与DBNG-CP2间可通过协议交互完成对备份协商消息(Redundancy association message)扩展，协商交互流程增加Redundancy的故障检测能力及Redundancy处 理能力。交互消息中所采用的IE可以是新增Fixed Redundancy IE，也可以是已有IE的扩展。
在本发明上述实施例中，还提供了如下的PFCP协议实现机制处理。4)采用PFCP节点上报(PFCP Node Report)实现机制，完成CP的故障检测及保护组切换流程。5)PFCP节点上报(PFCP Node Report)处理流程，采用PFCP节点上报请求(PFCP Node Report Request)及PFCP节点上报请求响应(PFCP Node Report Response)机制携带DBNG-CP的故障检测信息及保护组切换通告。6)PFCP节点上报请求(PFCP Node Report Request)信息的IE扩展，主要用于CP故障点上报请求。此IE可以是新增固定备份(Fixed Redundancy)IE，也可以是已有IE的扩展。7)PFCP节点上报响应(PFCP Node Report Response)信息的IE扩展，用于新active CP对用户流表等通告到用户面网络功能DBNG-UP。
本发明的实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本发明的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (16)

  1. 一种分离的宽带网络网关控制面网络功能DBNG-CP的备份方法，包括：
    第一DBNG-CP向属于同一个备份组实例的第二DBNG-CP发送备份协商请求，以进行备份能力协商；
    所述第一DBNG-CP接收第二DBNG-CP针对所述备份协商请求回复的备份协商响应，从而完成所述第一DBNG-CP与第二DBNG-CP之间的主备选举。
    所述DBNG-CP备份组管理了一组DBNG-UP。
  2. 根据权利要求1所述的方法，其中，完成所述第一DBNG-CP与第二DBNG-CP之间的主备选举之后，还包括：
    在检测到主成员第一DBNG-CP发生故障后，上报故障信息至所述第二DBNG-CP，并触发备份组切换以将第二DBNG-CP切换为主成员。
  3. 根据权利要求2所述的方法，其中，在第一DBNG-CP因故障发生备份组切换后，还包括：
    触发所述备份组实例内由所述第一DBNG-CP管理的所有DBNG-UP的切换，以切换至由所述第二DBNG-CP管理所述备份组实例内所有DBNG-UP。
  4. 根据权利要求2所述的方法，其中，所述DBNG-UP通过第一PFCP协议消息将携带的所述故障信息上报至所述第二DBNG-CP。
  5. 根据权利要求4所述的方法，其中，在触发备份组切换以将第二DBNG-CP切换为主成员之后，还包括：
    所述第二DBNG-CP通过第二PFCP协议消息将备份组切换结果通告至所述DBNG-UP。
  6. 根据权利要求2所述的方法，其中，所述第一DBNG-CP的故障为以下之一：
    第一DBNG-CP为活动状态下，所述第一DBNG-CP检测到的故障；
    第一DBNG-CP为离线状态下，所述DBNG-UP通过与所述第一DBNG-CP的连接检测到的第一DBNG-CP的故障。
  7. 根据权利要求2所述的方法，其中，所述第一DBNG-CP与第二DBNG-CP之间通过私有协议对备份能力协商消息进行扩展以完成CP备份能力协商。
  8. 根据权利要求5所述的方法，其中，采用PFCP节点上报机制以进行所述第一DBNG-CP的故障信息的上报，以及备份组切换通告。
  9. 根据权利要求8所述的方法，其中，通过PFCP节点上报请求消息上报所述第一DBNG-CP的故障信息，以及通过PFCP节点上报响应消息进行备份组切换通告。
  10. 根据权利要求9所述的方法，其中，通过对PFCP节点上报请求消息的信元进行扩展以进行所述第一DBNG-CP的故障信息上报。
  11. 根据权利要求10所述的方法，其中，PFCP节点上报请求消息中的扩展信元包括：控制面路径故障信元和CP备份组标识信元。
  12. 根据权利要求1所述的方法，其中，所述第一DBNG-CP向第二DBNG-CP发送备份协商请求之前，还包括：
    配置所述第一DBNG-CP的多个备份组实例；
    对于每个备份组实例，配置第一DBNG-CP管理的多个DBNG-UP，以及第一DBNG-CP备份组实例的主备切换策略。
  13. 根据权利要求12所述的方法，其中，所述第一DBNG-CP在第一备份组实例中为主成员，在第二备份组实例中为备成员。
  14. 一种分离的宽带网络网关控制面节点DBNG-CP的备份装置，位于第一DBNG-CP中，包括：
    发送模块，设置为向属于同一个备份组实例的第二DBNG-CP发送备份协商请求，以进行备份能力协商；
    接收模块，设置为接收第二DBNG-CP针对所述备份协商请求回复的备份协商响应，从而完成所述第一DBNG-CP与第二DBNG-CP之间的主备选举。
  15. 一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被处理器执行时实现所述权利要求1至13任一项中所述的方法的步骤。
  16. 一种电子装置，包括存储器、处理器以及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现所述权利要求1至13任一项中所述的方法的步骤。
PCT/CN2022/089582 2021-07-16 2022-04-27 Dbng-cp的备份方法及装置 Ceased WO2023284366A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22841007.2A EP4373039A4 (en) 2021-07-16 2022-04-27 METHOD AND APPARATUS FOR BACKING UP DBNG-CP

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110809209.2A CN115701040A (zh) 2021-07-16 2021-07-16 Dbng-cp的备份方法及装置
CN202110809209.2 2021-07-16

Publications (1)

Publication Number Publication Date
WO2023284366A1 true WO2023284366A1 (zh) 2023-01-19

Family

ID=84919005

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/089582 Ceased WO2023284366A1 (zh) 2021-07-16 2022-04-27 Dbng-cp的备份方法及装置

Country Status (3)

Country Link
EP (1) EP4373039A4 (zh)
CN (1) CN115701040A (zh)
WO (1) WO2023284366A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4412162A1 (en) * 2023-02-03 2024-08-07 Juniper Networks, Inc. Control plane initiated switchover for subscriber group

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102137021A (zh) * 2011-03-31 2011-07-27 北京傲天动联技术有限公司 接入控制器的异地冗余备份方法
CN109039680A (zh) * 2017-06-08 2018-12-18 华为技术有限公司 一种切换主宽带网络网关bng和备bng的方法、系统和bng
CN110650077A (zh) * 2018-06-27 2020-01-03 中兴通讯股份有限公司 一种l2tp协议控制与转发分离的方法及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2536068B1 (en) * 2011-06-18 2014-08-13 Deutsche Telekom AG Virtual subscriber management
US9985875B1 (en) * 2015-03-31 2018-05-29 Juniper Networks, Inc. Route signalling based resilient application overlay network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102137021A (zh) * 2011-03-31 2011-07-27 北京傲天动联技术有限公司 接入控制器的异地冗余备份方法
CN109039680A (zh) * 2017-06-08 2018-12-18 华为技术有限公司 一种切换主宽带网络网关bng和备bng的方法、系统和bng
CN110650077A (zh) * 2018-06-27 2020-01-03 中兴通讯股份有限公司 一种l2tp协议控制与转发分离的方法及系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP TS29.244
BROADBAND FORUM: "TR-459 Control and User Plane Separation for a disaggregated BNG", 3GPP DRAFT; C4-203064, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. DEFAULT_VALUE ;20200401, 14 May 2020 (2020-05-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051882750 *
See also references of EP4373039A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4412162A1 (en) * 2023-02-03 2024-08-07 Juniper Networks, Inc. Control plane initiated switchover for subscriber group

Also Published As

Publication number Publication date
CN115701040A (zh) 2023-02-07
EP4373039A4 (en) 2024-10-09
EP4373039A1 (en) 2024-05-22

Similar Documents

Publication Publication Date Title
JP6988004B2 (ja) 集中型ユニットと分散型ユニットのアーキテクチャにおける通信方法および通信デバイス
JP5759024B2 (ja) 地理的冗長ゲートウェイでセッションを復元するシステムおよび方法
US10051527B2 (en) Systems and methods for evolved packet core cluster and session handling
WO2023280166A1 (zh) 跨区域通信方法及设备、计算机可读存储介质
CN113472646B (zh) 一种数据传输方法、节点、网络管理器及系统
US20190273650A1 (en) Method and System for Processing NF Component Exception, and Device
CN106657330B (zh) 用户数据迁移方法和用户数据备份方法、装置及系统
CN112217649B (zh) 终端设备管理方法、服务器及终端设备
WO2023284367A1 (zh) Dbng-up的备份方法及装置
CN113891374B (zh) 故障网元识别方法、装置及设备
CN105704042A (zh) 报文处理方法、bng及bng集群系统
WO2020057445A1 (zh) 一种通信系统、方法及装置
CN112218342A (zh) 一种实现核心网子切片容灾的方法、装置和系统
CN104703165A (zh) 一种处理无线接入的方法、转发设备及网络控制器
WO2022267688A1 (zh) 备用smf发现方法、装置、电子设备和介质
CN104243304B (zh) 非全连通拓扑结构的数据处理方法、设备和系统
EP3896572B1 (en) Server computer, method for providing an application, mobile communication network and method for providing access to a server computer
US8849270B2 (en) System and method for providing geographic redundancy for mobile wireless data network components
WO2021169291A1 (zh) 发布路由的方法、网元、系统及设备
WO2023284366A1 (zh) Dbng-cp的备份方法及装置
CN109120556B (zh) 一种云主机访问对象存储服务器的方法及系统
WO2022044546A1 (ja) 通信システムおよびその障害復旧方法
CN101132357A (zh) 一种无线接入网络重组方法、系统及重组控制器
CN102572903B (zh) 接入支持节点的选择及容灾方法、系统及接入控制设备
CN117009135A (zh) 用户数据备份、用户数据恢复方法及数据库服务器设备

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: 22841007

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022841007

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022841007

Country of ref document: EP

Effective date: 20240216