Patent Description:
When a control plane and a user plane (control plane and user plane, CU) are separated, as a centralized control plane for user access management, a virtual broadband remote access server control plane (virtual broadband remote access server control plane, vBRAS-CP) device interacts with a control device, such as a remote authentication dial in user service (remote authentication dial in user service, RADIUS) server, to complete authentication, authorization, and accounting for an access user.

When the control device expects to delete data of user equipment from an entry of a virtual broadband remote access server user plane (virtual broadband remote access server user plane, vBRAS-UP) device, the control device sends a delete instruction for deleting the user equipment to the vBRAS-CP device, and the vBRAS-CP device instructs the vBRAS-UP device to delete the entry of the user equipment. This can reclaim an address and a related resource allocated to the user equipment.

When user equipment with some attributes needs to be deleted, the control device expects to send a delete instruction to the vBRAS-CP device for each user equipment with the attributes. In other words, a quantity of delete instructions is equal to that of the deleted user equipments. <CIT> describes dynamic switching of user equipment between a hardware forwarding plane and a software forwarding plane in a BRAS scenario. <CIT> describes a message forwarding method reducing the need for forwarding packets received from the network side across the VM to ensure the forwarding performance of the vBNG. <CIT> describes a traffic scheduling method, device, server, and storage medium implementing self-scheduling when a broadband access device is overloaded avoiding network anomalies and improving user network quality. The IETF Document "Simple Control and User Plane Separation Protocol (S-CUSP)", draft-chz-simple-cu-separation-bng-protocol-<NUM>. txt specifies the Simple CU Separation BNG control channel Protocol (S-CUSP) for communications between a BNG Control Plane (CP)and a set of User Planes (UPs) including deletion of sessions.

Embodiments of this application provide a method for deleting user equipment, to delete a plurality of user equipments at the same time.

A first aspect of embodiments of this application provides a method for deleting user equipment. The method includes:.

A vBRAS-CP device receives a delete instruction sent by a control device, where the delete instruction carries a target attribute. At least two user equipments managed by the control device meet the target attribute, and the user equipments meeting the target attribute are to be deleted. The vBRAS-CP device sends a delete entry operation to a vBRAS-UP device according to the delete instruction, to instruct the vBRAS-UP device to delete an entry of the user equipment corresponding to the target attribute, and release an address and a related resource of the user equipments. The delete entry operation sent by the vBRAS-CP carries the target attribute.

When user equipment carrying the target attribute needs to be deleted, the control device only needs to send one delete instruction including the target attribute to the vBRAS-CP device, and the vBRAS-CP device instructs the vBRAS-UP device to delete all entries of the user equipments carrying the target attribute according to the delete instruction. This can reduce packet interaction between the control device and the vBRAS-CP device when there are a plurality of user equipments carrying the target attribute.

According to the first aspect of the embodiments of this application, in a first implementation of the first aspect of the embodiments of this application, after the vBRAS-CP device receives the delete instruction sent by the control device, the vBRAS-CP device may send a go-offline packet to the user equipments meeting the target attribute based on the target attribute carried in the delete instruction. The go-offline packet instructs the user equipment corresponding to the target attribute to go offline.

In this embodiment of this application, when the control device needs to delete the user equipments meeting the target attribute, the vBRAS-CP device may instruct the user equipments meeting the target attribute to go offline. After receiving the go-offline packet, the user equipments meeting the target attribute may determine that the user equipments are beyond a management scope of the control device.

According to the first aspect or the first implementation of the first aspect of the embodiments of this application, in a second implementation of the first aspect of the embodiments of this application, the vBRAS-CP device may receive a user attribute sent by the user equipment, and store the user attribute. It may be understood that the target attribute belongs to the user attribute.

This embodiment of this application provides a method for obtaining the user attribute of the user equipment by using the vBRAS-CP device.

According to any one of the first aspect to the second implementation of the first aspect of the embodiments of this application, in a third implementation of the first aspect of the embodiments of this application, the target attribute may include at least one of a user plane identity (UP-ID) and a domain (domain).

This embodiment of this application provides a plurality of possible forms of the target attribute.

According to any one of the first aspect to the third implementation of the first aspect of the embodiments of this application, in a fourth implementation of the first aspect of the embodiments of this application, a specific manner of receiving the delete instruction from the control device by the vBRAS-CP device may be: The vBRAS-CP device receives the delete instruction sent by the control device by using a disconnect message (disconnect message, DM) packet.

According to any one of the first aspect to the third implementation of the first aspect of the embodiments of this application, in the fourth implementation of the first aspect of the embodiments of this application, the control device may be any one of a RADIUS server and an equipment management system (equipment management system, EMS) server.

A second aspect of embodiments of this application provides a method for deleting user equipment. The method includes:.

A vBRAS-UP device receives a delete entry operation sent by a vBRAS-CP device, where the delete entry operation carries a target attribute. The vBRAS-UP device deletes an entry of user equipment meeting the target attribute according to the delete entry operation, and releases an address and a related resource that are occupied by the user equipment.

When user equipment carrying the target attribute needs to be deleted, a control device only needs to send one delete instruction including the target attribute to the vBRAS-CP device, and the vBRAS-CP device instructs the vBRAS-UP device to delete the entry of the user equipment carrying the target attribute according to the delete instruction. When there are a plurality of user equipments carrying the target attribute, packet interaction between the control device and the vBRAS-CP device may be reduced.

According to the second aspect of the embodiments of this application, in a first implementation of the second aspect of the embodiments of this application, the target attribute may include at least one of a user plane identity (UP-ID) and a domain (domain).

A third aspect of embodiments of this application provides a method for deleting user equipment. The method includes:.

A control device sends a delete instruction to a vBRAS-CP device, where the delete instruction includes a target attribute, the target attribute corresponds to at least two user equipments. The delete instruction is used to instruct the vBRAS-CP device to send a delete entry operation that carries the target attribute to a vBRAS-UP device.

When user equipment carrying the target attribute needs to be deleted, the control device only needs to send one delete instruction including the target attribute to the vBRAS-CP device, and the vBRAS-CP device instructs the vBRAS-UP device to delete an entry of the user equipment carrying the target attribute according to the delete instruction. This can reduce packet interaction between the control device and the vBRAS-CP device when there are a plurality of user equipments carrying the target attribute.

According to the third aspect, in a first implementation of the third aspect of the embodiments of this application, the target attribute may include at least one of a user plane identity (UP-ID) and a domain (domain).

According to the third aspect or the first implementation of the third aspect of the embodiments of this application, in a second implementation of the third aspect of the embodiments of this application, a specific manner of sending the delete instruction to the vBRAS-CP device by the control device may be: The control device sends the delete instruction to the vBRAS-CP device by using a disconnect message (DM) packet.

According to the first aspect to the second implementation of the first aspect of the embodiments of this application, in a third implementation of the first aspect of the embodiments of this application, the control device may be any one of a RADIUS server and an EMS server.

A fourth aspect of embodiments of this application provides a vBRAS-CP device. The vBRAS-CP device performs the method according to the first aspect.

A fifth aspect of embodiments of this application provides a vBRAS-UP device. The vBRAS-UP device performs the method according to the second aspect.

A sixth aspect of embodiments of this application provides a control device. The control device performs the method according to the third aspect.

A seventh aspect of this application provides a vBRAS-CP device. The vBRAS-CP device has functions of implementing the method according to the first aspect and the implementations of the first aspect. The vBRAS-CP device includes a processor and a transmission interface. The transmission interface is configured to receive or send data. The processor is configured to call software instructions stored in a memory, to perform an information transmission method according to the first aspect and the implementations of the first aspect.

An eighth aspect of this application provides a vBRAS-UP device. The vBRAS-UP device has functions of implementing the method according to the second aspect and the implementations of the second aspect. The vBRAS-UP device includes a processor and a transmission interface. The transmission interface is configured to receive or send data. The processor is configured to call software instructions stored in a memory, to perform the information transmission method according to the second aspect and the implementations of the second aspect.

A ninth aspect of this application provides a control device. The control device has functions of implementing the method according to the third aspect and the implementations of the third aspect. The control device includes a processor and a transmission interface. The transmission interface is configured to receive or send data. The processor is configured to call software instructions stored in a memory, to perform the information transmission method according to the third aspect and the implementations of the third aspect.

A tenth aspect of embodiments of this application provides a computer storage medium. The computer storage medium stores instructions. When the instructions are executed on a computer, the computer is enabled to perform the method according to any one of the first aspect to the third aspect.

An eleventh aspect of embodiments of this application provides a computer software product. When a computer program product runs on a computer, the computer is enabled to perform the method according to any one of the first aspect to the third aspect.

Refer to <FIG>. A network architecture in an embodiment of this application includes:
a control device <NUM>, a vBRAS-CP device <NUM>, vBRAS-UP devices <NUM> and <NUM>, and user equipments <NUM> to <NUM>.

The control device <NUM> is configured to manage devices or perform authentication, authorization, and accounting for a user. In this embodiment of this application, the control device <NUM> may be a RADIUS server, or another device such as an equipment management system (equipment management system, EMS) server. This is not specifically limited herein.

The vBRAS-CP device <NUM> receives a delete instruction from the control device, and instructs the vBRAS-UP devices <NUM> and <NUM> to delete indicated user equipment according to the delete instruction.

The user equipments <NUM> to <NUM> may be connected to the vBRAS-UP devices <NUM> and <NUM> by using optical line terminals (optical line terminals, OLTs) <NUM> to <NUM>. In practice, one OLT may be connected to one user equipment, or may be connected to the plurality of user equipments. The one vBRAS-UP device may be connected to the one OLT, or may be connected to a plurality of OLTs. This is not specifically limited herein.

This embodiment of this application describes a network architecture including the one control device <NUM>, the one vBRAS-CP device <NUM>, the two vBRAS-UP devices <NUM> and <NUM>, and the five user equipments <NUM> to <NUM> as an example. In practice, a quantity of devices may be another value not less than <NUM>. For example, one control device, two vBRAS-CP devices, one vBRAS-UP device, and four user equipments. This is not specifically limited herein.

Refer to <FIG>. An embodiment of a method for deleting user equipment in an embodiment includes the following steps.

Step <NUM>: A vBRAS-CP obtains a user attribute of user equipment.

After accessing a network, the user equipment sends the user attribute to the vBRAS-CP device. The user attribute may include either a user plane identity (user plane identity, UP-ID) or a domain (domain). It may be understood that the user attribute may alternatively be a physical or a software attribute of another user equipment. This is not specifically limited herein.

In an actual application, a manner of obtaining the user attribute of the user equipment by the vBRAS-CP device is not limited to receiving from the user equipment, or obtaining from another third-party device. For example, if the user attribute is online duration of the user equipment, the vBRAS-CP device may obtain the user attribute from a timer.

Step <NUM>: A control device sends a delete instruction to the vBRAS-CP device.

The delete instruction includes a target attribute. In this embodiment, the target attribute corresponds to two or more user equipments, and the target attribute belongs to the user attribute. It may be understood that the user attribute may include a plurality of types, and the target attribute may also include a plurality of types, for example, including two types of the UP-ID and the domain.

After obtaining the user attribute of the user equipment, the vBRAS-CP device may report the user attribute to the control device. The control device may manage the user equipment based on the user attribute. It may be understood that the control device may further obtain the user attribute of the user equipment in another manner, for example, obtain from configuration instructions of a network administrator. If the user attribute is the online duration of the user equipment, the control device may obtain the user attribute from the timer of the online duration of a user.

In this example, if the user attribute is the UP-ID within a range of <NUM> to FFFF, the target attribute may be that the UP-ID is within the range of <NUM> to 0FFF, or the UP-ID is within the range of <NUM> to <NUM>. This is not specifically limited herein.

In this example, if the control device is a RADIUS server, the delete instruction may be a DM packet. The DM packet carries the target attribute, that is, the range of the UP-ID.

Step <NUM>: The vBRAS-CP device replies an acknowledge message to the control device.

The vBRAS-CP device may reply the acknowledge message to the control device after receiving the delete instruction. After receiving the acknowledge message, the control device confirms that the vBRAS-CP device has received the delete instruction.

In this example, if the control device is the RADIUS server, the acknowledge message may be a disconnect message acknowledge character (disconnect message acknowledge character, DM ACK).

It may be understood that the step <NUM> may not be performed in the actual application. After the vBRAS-CP device receives the delete instruction, step <NUM> and subsequent steps may be directly performed. For example, if the control device is an EMS server, the EMS server may send the delete instruction to the vBRAS-CP device through the simple network management protocol (simple network management protocol, SNMP), the netconf protocol (network configuration protocol), or the YANG (yet another next generation) protocol.

Step <NUM>: The vBRAS-CP sends a go-offline packet to the user equipment.

After receiving the delete instruction, the vBRAS-CP device may send the go-offline packet to user equipment indicated by the delete instruction, that is, the user equipment meeting the target attribute, to instruct the user equipment to go offline.

Step <NUM>: The vBRAS-CP device sends a delete entry operation to the vBRAS-UP device.

After receiving the delete instruction, the vBRAS-CP device may send the delete entry operation that carries the target attribute to the vBRAS-UP device. The delete entry operation instructs the vBRAS-UP device to delete an entry of the user equipment meeting the target attribute.

Step <NUM>: The vBRAS-UP deletes the entry of the user equipment.

The vBRAS-UP device deletes the entry of the user equipment meeting the target attribute according to the delete entry operation sent by the vBRAS-CP device, and reclaims an address and a related resource of the user equipment.

An execution sequence of the foregoing steps is merely an example. There may be different execution sequences in another design. For example, the step <NUM> may alternatively be performed after the step <NUM>. For another example, a sequence of the step <NUM> and the step <NUM> may be exchanged.

It may be understood that in the actual application, there may be a plurality of target attributes carried in the delete entry operation. For example, if the target attribute includes the UP-ID and the domain, it may be specified that the vBRAS-UP device deletes user equipment whose UP-ID is within a preset range and whose domain meets a preset condition. In other words, the vBRAS-UP device deletes the user equipment that meets both target attributes of the UP-ID and the domain. Alternatively, it may be specified that the vBRAS-UP device deletes user equipment whose UP-ID is within the preset range or whose domain meets the preset condition. In other words, the vBRAS-UP device deletes the user equipment that meets one of the two target attributes of the UP-ID and the domain. This is not specifically limited herein.

The above describes the method for deleting the user equipment in the embodiments of this application, and the following describes a device in the embodiments of this application.

Refer to <FIG>. An embodiment of a vBRAS-CP device <NUM> in an embodiment of this application includes:.

In this embodiment, operations performed by the units in the vBRAS-CP device <NUM> are similar to those described in the embodiment shown in <FIG>. This is not described herein again.

Refer to <FIG>. An embodiment of a vBRAS-UP device <NUM> in an embodiment of this application includes:.

In this embodiment, operations performed by the units in the vBRAS-UP device <NUM> are similar to those described in the embodiment shown in <FIG>. This is not described herein again.

Refer to <FIG>. An embodiment of a control device <NUM> in an embodiment of this application includes:
a sending unit <NUM>, configured to send a delete instruction to a vBRAS-CP device, and specifically configured to send the delete instruction to the vBRAS-CP device by using a DM packet.

In this embodiment, operations performed by the units in the control device <NUM> are similar to those described in the embodiment shown in <FIG>. This is not described herein again.

Refer to <FIG>. An embodiment of this application provides a vBRAS-CP device <NUM>. The vBRAS-CP device <NUM> may include one or more processors <NUM> and a memory <NUM>. The memory <NUM> stores program code. Further, the memory <NUM> may store data.

The memory <NUM> may be a volatile memory, a nonvolatile memory, or a persistent storage device. The program code stored in the memory <NUM> may include one or more modules, and each module may include a series of instruction operations for the vBRAS-CP device. Further, the processor <NUM> may be configured to communicate with the memory <NUM>, and perform the series of instruction operations in the memory <NUM> on the vBRAS-CP device <NUM>.

The vBRAS-CP device <NUM> may further include one or more power supplies <NUM>, one or more wired or wireless network interfaces <NUM>, one or more input/output interfaces <NUM>, and/or one or more operating systems, such as Windows, Android, Mac OS, iOS, Unix, Linux, and FreeBSD.

The processor <NUM> may perform the operations performed by the vBRAS-CP device in the embodiment shown in <FIG>. This is not specifically described herein again.

Refer to <FIG>. An embodiment of this application provides a vBRAS-UP device <NUM>. The vBRAS-UP device <NUM> may include one or more processors <NUM> and a memory <NUM>. The memory <NUM> stores program code. Further, the memory <NUM> may store data.

The memory <NUM> may be a volatile memory, a nonvolatile memory, or a persistent storage device. The program code stored in the memory <NUM> may include one or more modules, and each module may include a series of instruction operations for the vBRAS-UP device. Further, the processor <NUM> may be configured to communicate with the memory <NUM>, and perform the series of instruction operations in the memory <NUM> on the vBRAS-UP device <NUM>.

The vBRAS-UP device <NUM> may further include one or more power supplies <NUM>, one or more wired or wireless network interfaces <NUM>, one or more input/output interfaces <NUM>, and/or one or more operating systems, such as Windows, Android, Mac OS, iOS, Unix, Linux, and FreeBSD.

The processor <NUM> may perform the operations performed by the vBRAS-UP device in the embodiment shown in <FIG>. This is not specifically described herein again.

Refer to <FIG>. An embodiment of this application provides a control device <NUM>. The control device <NUM> may include one or more processors <NUM> and a memory <NUM>. The memory <NUM> stores program code. Further, the memory <NUM> may store data.

The memory <NUM> may be a volatile memory, a nonvolatile memory, or a persistent storage device. The program code stored in the memory <NUM> may include one or more modules, and each module may include a series of instruction operations for the control device. Further, the processor <NUM> may be configured to communicate with the memory <NUM>, and perform the series of instruction operations in the memory <NUM> on the control device <NUM>.

The control device <NUM> may further include one or more power supplies <NUM>, one or more wired or wireless network interfaces <NUM>, one or more input/output interfaces <NUM>, and/or one or more operating systems, such as Windows, Android, Mac OS, iOS, Unix, Linux, and FreeBSD.

The processor <NUM> may perform the operations performed by the control device in the embodiment shown in <FIG>. This is not specifically described herein again.

An embodiment of this application further provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. When the computer program is executed by a computer, a method procedure related to a control device, a vBRAS-CP device, or a vBRAS-UP device in any one of the foregoing method embodiments is implemented. Correspondingly, the computer may be the control device, the vBRAS-CP device, or the vBRAS-UP device.

It should be understood that a processor mentioned in the control device, the vBRAS-CP device, or the vBRAS-UP device in the embodiments of this application, or the processor provided in the embodiments of this application may be a central processing unit (central processing unit, CPU), or may be another general-purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or another programmable logic device, a discrete gate or a transistor logical device, a discrete hardware assembly, or the like. The general-purpose processor may be a microprocessor, any conventional processor, or the like.

It should be further understood that there may be one or more processors in the control device, the vBRAS-CP device, or the vBRAS-UP in the embodiments of this application. The quantity may be adjusted based on an actual application scenario. This is merely an example for description herein, and is not limited. There may be one or more memories in the embodiments of this application. The quantity may be adjusted based on an actual application scenario. This is merely an example for description herein, and is not limited.

It should also be understood that the memory or the readable storage medium mentioned in the control device, the vBRAS-CP device, or the vBRAS-UP device in the embodiments of this application may be a volatile memory or a non-volatile memory, or both the volatile memory and the non-volatile memory. The nonvolatile memory may be a read-only memory (read-only memory, ROM), a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (random access memory, RAM) that is used as a cache. Through example but not limitative descriptions, many forms of RAMs are available, for example, a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), a synchronous dynamic random access memory (synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and a direct rambus random access memory (direct rambus RAM, DR RAM).

It should be further noted that when the control device, the vBRAS-CP device, or the vBRAS-UP device includes the processor (or a processing unit) and the memory, the processor in this application may be integrated with the memory, or may be connected to the memory by using an interface. This may be adjusted based on an actual application scenario, and is not limited.

An embodiment of this application further provides a computer program or a computer program product including the computer program. When the computer program is executed on a computer, the computer is enabled to implement a method procedure related to the control device, the vBRAS-CP device or the vBRAS-UP device in any one of the foregoing method embodiments. Correspondingly, the computer may be the control device, the vBRAS-CP device, or the vBRAS-UP device.

All or some of the foregoing embodiments shown in <FIG> may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or some of the embodiments may be implemented in a form of a computer program product.

The computer program product includes one or more computer instructions. When computer program instructions are loaded and executed on the computer, all or some of procedures or functions according to the embodiments of this application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable apparatus. The computer instructions may be stored in the computer-readable storage medium or may be transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, a computer, a server, or a data center to another website, another computer, another server, or another data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by the computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid state disk Solid State Disk (SSD)), or the like.

In the embodiments provided in this application, it should be understood that the system, the apparatus, and the method disclosed in this application may be implemented in other manners. For example, the foregoing apparatus embodiments are merely examples. For example, division of the units is merely logical function division and may be other division during actual implementation. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces.

Some or all of the units may be selected depending on actual requirements to achieve the objectives of the solutions in the embodiments.

When the integrated unit is implemented in the form of a software function unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of this application essentially, or the part contributing to the conventional technology, or all or some of the technical solutions may be implemented in the form of a software product. The computer software product is stored in one storage medium and includes several instructions for instructing a computer device (which may be a personal computer, the server, or another network device) to perform all or some of the steps of the methods described in the embodiment in <FIG> of this application. The storage medium includes various media that can store the program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk, or an optical disc.

In the specification, claims, and the accompanying drawings of this application, the terms "first", "second", and the like are intended to distinguish similar objects but do not necessarily indicate a specific order or sequence. It should be understood that the terms used in such a way are interchangeable in proper circumstances, and this is merely a discrimination manner for describing objects having a same attribute in embodiments of this application. In addition, the terms "include", "have" and any other variants mean to cover the non-exclusive inclusion, so that a process, method, system, product, or device that includes a series of units is not necessarily limited to those units, but may include other units not expressly listed or inherent to such a process, method, product, or device.

Names of messages/frames/information, modules, units, or the like provided in the embodiments of this application are merely examples, and other names may be used provided that the messages/frames/information, modules, units, or the like have same functions.

The terms used in embodiments of this application are merely for the purpose of illustrating specific embodiments, and are not intended to limit the present invention. The terms "a", "the", and "this" of singular forms used in embodiments and the appended claims of this application are also intended to include plural forms, unless otherwise specified in a context clearly. In the descriptions of this application, "/" represents an "or" relationship between associated objects unless otherwise specified. For example, A/B may represent A or B. The term "and/or" in this application is merely an association relationship for describing associated objects, and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists, where A and B each may be singular or plural.

Claim 1:
A method for deleting user equipment (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>), comprising:
receiving (<NUM>), by a virtual broadband remote access server control plane vBRAS-CP device (<NUM>), a delete instruction from a control device (<NUM>), wherein the delete instruction comprises a target attribute, and the target attribute corresponds to at least two user equipments (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>); and
sending (<NUM>), by the vBRAS-CP device (<NUM>), a delete entry operation to a virtual broadband remote access server user plane vBRAS-UP device (<NUM>, <NUM>), to instruct the vBRAS-UP device (<NUM>, <NUM>) to delete entries of the user equipments (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) corresponding to the target attribute; and the delete entry operation comprises the target attribute.