ACL configuration method, ACL configuration device, computer program, and communication system

Abstract

This application discloses an ACL configuration method and apparatus. A first base station may include the user plane IP address of the first base station in signaling such as a handover request message, a configuration update message, or a secondary station addition request message, so that a target base station can obtain the user plane IP address of the first base station without performing a TNL address discovery procedure. Then, an ACL may be configured based on the obtained IP address. Therefore, the case in which a packet transmitted by the first base station is discarded by the second base station in a base station handover scenario may be efficiently avoided, and the reliability of data transmission may be improved.

Description

[Technical Field]

[0001] The present application relates to the field of communication technology, and in particular to an ACL configuration method and apparatus. [Background technology]

[0002] For security purposes in communication networks, a packet filtering function is configured for a base station. That is, an Access Control List (ACL) is pre-configured on the base station, and the base station performs access control on received packets through the pre-configured ACL. Specifically, the base station processes only packets whose source Internet Protocol (IP) address and destination IP address are within the ACL.

[0003] In a scenario in which a terminal device performs base station handover, the terminal device moves from one base station (source base station) to another base station (target base station). There is a time lag between the handover on the core network side and the air interface handover on the terminal device side. Therefore, after the air interface handover on the terminal device side is completed, the core network may still transmit data to be transmitted to the terminal device to the source base station. As a result, the source base station needs to forward the data to the target base station (data forwarding) after receiving the data. In this case, if a packet filtering function is enabled in the target base station, the target base station determines whether to process a packet received from the source base station based on an ACL. However, in existing base station handover scenarios, the target base station often discards packets transmitted by the source base station, resulting in poor reliability of data transmission. Summary of the Invention

[0004] The present application provides an ACL configuration method and apparatus for improving the reliability of data transmission in a base station handover process.

[0005] According to a first aspect, there is provided an access control list (ACL) configuration method, the method including: a second base station receiving a handover request message or a configuration update message from a first base station, where the handover request message or the configuration update message carries a user plane Internet Protocol (IP) address of the first base station; and the second base station configuring an ACL based on the user plane IP address.

[0006] In this embodiment of the present application, the first base station may retain the user plane IP address of the first base station in the handover request message, so that the second base station can obtain the user plane IP address of the first base station in the handover procedure and then configure the ACL. In this way, in the process of handing over a terminal from the first base station to the second base station, the second base station may not discard packets transmitted by the first base station. In addition, when the configuration of the first base station is updated (for example, but not limited to, in the present application, the user plane IP address of the first base station is updated, a neighbor cell is updated, or another update is performed), the first base station may retain the user plane IP address of the first base station in the configuration update message, so that the second base station can obtain the user plane IP address of the first base station. Thereafter, when the terminal device is handed over from the first base station to the second base station, the second base station may not discard packets transmitted by the first base station in the handover process. This is because the second base station has pre-configured an ACL based on the user plane IP address of the first base station.

[0007] In one possible design, after the second base station configures the ACL based on the user plane IP address, the second base station further receives a packet from the first base station. The second base station determines whether the source IP address of the packet is within the ACL. If the source IP address of the packet is within the ACL, the second base station processes the packet. If the source IP address of the packet is not within the ACL, the second base station discards the packet.

[0008] The user plane IP address of the first base station is configured in the ACL of the second base station, so the second base station will not discard packets, which improves the reliability of data transmission.

[0009] In a possible design, the second base station receiving the handover request message may be the second base station receiving the handover request message directly from the first base station based on an interface between the second base station and the first base station, or the second base station receiving the handover request message from the first base station via a core network element.

[0010] This embodiment of the present application provides two different ways to transmit the handover request message, which may improve the flexibility of the solution.

[0011] According to a second aspect, there is provided an ACL configuration method, the method including:

[0012] A step of a first base station generating a handover request message or a configuration update message, wherein the handover request message or the configuration update message carries a user plane IP address of the first base station; and a step of the first base station transmitting the handover request message or the configuration update message to a second base station.

[0013] In a possible design, the first base station may send a handover request message to the second base station via a core network element.

[0014] In one possible design, after the first base station sends the handover request message or the configuration update message to the second base station, the first base station further receives data from the core network; or the first base station further receives data from the terminal device. Furthermore, the first base station generates a packet based on the data and sends the packet to the second base station. The packet carries a source IP address, where the source IP address is the user plane IP address of the first base station.

[0015] In one possible design, the packet may be transmitted over an interface between the first base station and the second base station.

[0016] For the beneficial effects of the second aspect and the design of the second aspect, please refer to the beneficial effects of the first aspect and the design of the first aspect, and details will not be described in this specification.

[0017] According to a third aspect, there is provided an ACL configuration method, the method including: a step of receiving a secondary station addition request message from a master base station by a target secondary base station, wherein the secondary station addition request message carries a user plane IP address of a source secondary base station; and a step of the target secondary base station configuring an ACL based on the user plane IP address.

[0018] In this embodiment of the present application, in the SN change procedure, the user plane IP address of the S-SN is retained in the secondary station addition request message, so that the T-SN can obtain the user plane IP address of the S-SN without performing the TNL address discovery procedure. Then, the ACL can be configured based on the obtained S-SN. Therefore, in the SN handover scenario, the case where packets sent by the S-SN are discarded by the T-SN can be effectively avoided, and the reliability of data transmission can be improved.

[0019] In one possible design, after the target secondary base station configures the ACL based on the user plane IP address, the target secondary base station further receives a packet from the source secondary base station. The target secondary base station determines whether the source IP address of the packet is within the ACL. If the source IP address of the packet is within the ACL, the target secondary base station processes the packet. If the source IP address of the packet is not within the ACL, the target secondary base station discards the packet.

[0020] The user plane IP address of the S-SN is configured in the ACL of the T-SN, so the T-SN will not discard packets, which improves the reliability of data transmission.

[0021] In a possible design, the source secondary base station and the target secondary base station may correspond to different master base stations. Specifically, the source secondary base station corresponds to the source master base station, and the target secondary base station corresponds to the target master base station. Correspondingly, the target secondary base station receives a secondary station addition request message from the target master base station.

[0022] In another possible design, both the target secondary base station and the source secondary base station correspond to a master base station, i.e., the target secondary base station and the source secondary base station correspond to the same master base station.

[0023] This embodiment of the present application provides two different ways of transmitting the secondary station addition request message to improve the flexibility of the solution.

[0024] According to a fourth aspect, there is provided an ACL configuration method, the method including: a step of a master base station generating a secondary station addition request message, wherein the secondary station addition request message carries a user plane IP address of a source secondary base station; and a step of the master base station transmitting the secondary station addition request message to a target secondary base station.

[0025] In a possible design, the source secondary base station and the target secondary base station correspond to different master base stations. Specifically, the source secondary base station corresponds to the source master base station, and the target secondary base station corresponds to the target master base station. Correspondingly, before generating the secondary station addition request message, the target master base station further receives a handover request message from the source master base station. The handover request message carries the user plane IP address of the source secondary base station.

[0026] In this embodiment of the present application, an ACL may be configured for both the target master base station and the target secondary base station, which may further improve the reliability of data transmission.

[0027] In a possible design, the handover request message further carries the user plane IP address of the source master base station, and the target master base station further configures an ACL based on the user plane IP address of the source master base station.

[0028] In a possible design, both the target secondary base station and the source secondary base station correspond to the master base station, i.e., the target secondary base station and the source secondary base station correspond to the same master base station.

[0029] For the beneficial effects of the fourth aspect and the design of the fourth aspect, please refer to the beneficial effects of the third aspect and the design of the third aspect, and details will not be described in this specification.

[0030] According to a fifth aspect, there is provided an ACL configuration apparatus, the apparatus being located in a second base station, which may be, for example, a second base station or a chip disposed inside a network device, the apparatus including a module configured to perform a method according to the first aspect or any one of the possible implementations of the first aspect.

[0031] For example, the apparatus includes: a transceiver unit configured to receive a handover request message or a configuration update message from a first base station, where the handover request message or the configuration update message carries a user plane IP address of the first base station; and a processing unit configured to configure an ACL based on the user plane IP address.

[0032] According to a sixth aspect, there is provided an ACL configuration apparatus, the apparatus being located in a first base station, which may be, for example, the first base station or a chip disposed in a network device, the apparatus including a module configured to perform a method according to the second aspect or any one of the possible implementations of the second aspect.

[0033] For example, an apparatus may include: a processing unit configured to generate a handover request message or a configuration update message, where the handover request message or the configuration update message carries a user plane IP address of the first base station; and a transceiver unit configured to transmit the handover request message or the configuration update message to a second base station.

[0034] According to a seventh aspect, there is provided an ACL configuration device, the device being located in a target secondary base station, and may be, for example, a target secondary base station or a chip disposed within the target secondary base station, the device including a module configured to perform a method according to the third aspect or any one of the possible implementations of the third aspect.

[0035] For example, the apparatus may include: a transceiver unit configured to receive a secondary station addition request message from a master base station, where the secondary station addition request message carries a user plane IP address of a source secondary base station; and a processing unit configured to configure an ACL based on the user plane IP address.

[0036] According to an eighth aspect, there is provided an ACL configuration device. The device is located in a master base station, and may be, for example, a master base station or a chip disposed within the master base station. The device includes a module configured to perform a method according to the fourth aspect or any one of the possible implementations of the fourth aspect.

[0037] For example, the apparatus may include: a processing unit configured to generate a secondary station addition request message, wherein the secondary station addition request message carries a user plane IP address of a source secondary base station; and a transceiver unit configured to transmit the secondary station addition request message to a target secondary base station.

[0038] According to a ninth aspect, there is provided a communications device including a processor and a memory, the memory configured to store computer-executable instructions, and the processor configured to execute the computer-executable instructions stored in the memory, such that the communications device performs a method according to any one of the first aspect, possible designs of the first aspect, the second aspect, possible designs of the second aspect, the third aspect, possible designs of the third aspect, the fourth aspect, or possible designs of the fourth aspect.

[0039] According to a tenth aspect, there is provided a communications device including a processor and an interface circuit, the interface circuit configured to receive code instructions and transmit the code instructions to the processor, the processor executing the code instructions to perform a method according to any one of the first aspect, possible designs of the first aspect, the second aspect, possible designs of the second aspect, the third aspect, possible designs of the third aspect, the fourth aspect, or possible designs of the fourth aspect.

[0040] According to an eleventh aspect, there is provided a computer-readable storage medium configured to store instructions that, when executed, implement a method according to any one of the first aspect, possible designs of the first aspect, the second aspect, possible designs of the second aspect, the third aspect, possible designs of the third aspect, the fourth aspect, or possible designs of the fourth aspect.

[0041] According to a twelfth aspect, there is provided a chip, coupled to a memory and configured to read and execute program instructions stored in the memory to implement a method according to any one of the first aspect, possible designs of the first aspect, the second aspect, possible designs of the second aspect, the third aspect, possible designs of the third aspect, the fourth aspect, or possible designs of the fourth aspect.

[0042] According to a thirteenth aspect, there is provided a computer program product comprising instructions, the computer program product storing the instructions which, when executed on a computer, cause the computer to perform a method according to any one of the first aspect, possible designs of the first aspect, the second aspect, possible designs of the second aspect, the third aspect, possible designs of the third aspect, the fourth aspect, or possible designs of the fourth aspect.

[0043] According to a fourteenth aspect, there is provided a communication system comprising a first base station and a second base station, wherein the second base station is configured to perform a method according to the first aspect or any one of its possible designs, and the first base station is configured to perform a method according to the second aspect or any one of its possible designs.

[0044] According to a fifteenth aspect, there is provided a communication system including a target secondary base station and a master base station, wherein the target secondary base station is configured to perform a method according to the third aspect or any one of its possible designs, and the master base station is configured to perform a method according to the fourth aspect or any one of its possible designs. [Brief explanation of the drawings]

[0045] [Figure 1] 1 is a schematic diagram of a network architecture of a possible cellular network to which the present application can be applied;

[0046] [Figure 2] 1 is a schematic diagram of a TNL address discovery procedure and an Xn interface handover procedure.

[0047] [Figure 3] FIG. 1 is a schematic diagram of a multi-operator sharing scenario.

[0048] [Figure 4] 1 is a flowchart of a secondary node change triggered by an SN.

[0049] [Figure 5] 1 is a schematic flowchart of an ACL configuration method according to an embodiment of the present application;

[0050] [Figure 6] 1 is a schematic flowchart of a base station handover in an X2-based inter-base station handover scenario;

[0051] [Figure 7] 1 is a schematic flowchart of a base station handover in an Xn-based inter-base station handover scenario;

[0052] [Figure 8] 1 is a schematic flowchart of an NG-based base station handover.

[0053] [Figure 9] 1 is a schematic flowchart of another ACL configuration method according to an embodiment of the present application;

[0054] [Figure 10A] 1 is a schematic flowchart of a base station handover in an S-SN triggered inter-SN base station handover scenario; [Figure 10B] 1 is a schematic flowchart of a base station handover in an S-SN triggered inter-SN base station handover scenario;

[0055] [Figure 11A] 1 is a schematic flowchart of a base station handover in an MN-triggered inter-SN base station handover scenario; [Figure 11B] 1 is a schematic flowchart of a base station handover in an MN-triggered inter-SN base station handover scenario;

[0056] [Figure 12A] 10 is a schematic flowchart of a base station handover in a scenario where an MN inter-base station handover and an SN inter-base station handover are performed simultaneously. [Figure 12B] 10 is a schematic flowchart of a base station handover in a scenario where an MN inter-base station handover and an SN inter-base station handover are performed simultaneously.

[0057] [Figure 13A]1 is a schematic flowchart of a base station handover in a scenario where an eNodeB / gNodeB is changed to a master station. [Figure 13B] 1 is a schematic flowchart of a base station handover in a scenario where an eNodeB / gNodeB is changed to a master station.

[0058] [Figure 14A] 1 is a schematic flowchart of a base station handover in a scenario where the master station is changed to an eNodeB / gNodeB. [Figure 14B] 1 is a schematic flowchart of a base station handover in a scenario where the master station is changed to an eNodeB / gNodeB.

[0059] [Figure 15] 1 is a schematic diagram of the structure of an ACL configuration device according to the present application;

[0060] [Figure 16] 1 is a schematic diagram of the structure of a communication device according to the present application;

[0061] [Figure 17] 1 is a schematic diagram of the structure of another communication device according to the present application; DETAILED DESCRIPTION OF THE INVENTION

[0062] The technical solutions in the embodiments of the present application may be applicable to 5th Generation (5G) systems, and may also be applicable to other wireless communication systems, such as Long Term Evolution (LTE) systems, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access (CDMA) systems, and new network device systems.

[0063] To facilitate understanding of the embodiments of the present application, the application scenario used in the embodiments of the present application is described by using the network architecture shown in Figure 1. The network architecture can be applied to various communication systems mentioned above.

[0064] As shown in FIG. 1, the communication system includes a first base station, a second base station, and a terminal device. When the terminal device is located within the coverage area of ​​the first base station, the terminal device may be connected to and communicate with the first base station. When the terminal device is located within the coverage area of ​​the second base station, the terminal device may be connected to and communicate with the second base station. When the terminal device moves from the coverage area of ​​the first base station to the coverage area of ​​the second base station, the first base station is a source base station for base station handover of the terminal device, and the second base station is a target base station for base station handover of the terminal device. When the terminal device moves from the coverage area of ​​the second base station to the coverage area of ​​the first base station, the second base station is a source base station for base station handover of the terminal device, and the first base station is a target base station for base station handover of the terminal device. For example, FIG. 1 uses an example in which the first base station is a source base station and the second base station is a target base station.

[0065] Herein, a terminal device may also be referred to as a terminal and may include a device that provides voice and / or data connectivity to a user, such as a handheld device with wireless connectivity or a processing device connected to a wireless modem. The terminal device may communicate with the core network through a radio access network (RAN) and exchange voice and / or data with the RAN. A terminal device may include a user equipment (UE), a wireless terminal device, a mobile terminal device, a device-to-device (D2D) communication terminal device, a V2X terminal device, a machine-to-machine / machine-type communications (M2M / MTC) terminal device, an internet of things (IoT) terminal device, a subscriber unit, a subscriber station, a mobile station, a remote station, an access point (AP), a remote terminal, an access terminal, a user terminal, a user agent, or a user device, etc. For example, a terminal device may include a mobile phone (also referred to as a "morphic" phone), a computer with a mobile terminal device, or a portable, pocket-sized, handheld, or computer-equipped mobile device. For example, the terminal device may be a device such as a personal communications service (PCS) telephone, a cordless telephone, a session initiation protocol (SIP) telephone, a wireless local loop (WLL) station, or a personal digital assistant (PDA).The terminal device further includes a limited device, such as a device with low power consumption, a device with limited storage capacity, or a device with limited computing power, for example, a terminal device includes an information sensing device such as a barcode, a radio frequency identification (RFID), a sensor, a global positioning system (GPS), or a laser scanner.

[0066] By way of example and not limitation, in embodiments of the present application, the terminal device may alternatively be a wearable device. A wearable device, which may also be referred to as a wearable intelligent device, an intelligent wearable device, etc., is a general term for wearable devices, such as glasses, gloves, watches, clothes, and shoes, that are intelligently designed and developed to be worn daily using wearable technology. A wearable device is a portable device that can be worn directly on the body or integrated into a user's clothing or accessories. A wearable device is not only a hardware device, but also implements powerful functions through software support, data exchange, and cloud interaction. In a broad sense, a wearable intelligent device includes a large, fully functional device, such as a smart watch or smart glasses, that can implement all or part of its functions without relying on a smartphone, and also includes a device that is dedicated to only one type of application function and needs to work in cooperation with other devices, such as a smartphone, such as various smart bands, smart helmets, or smart jewelry for monitoring physical symptoms.

[0067] When the above various terminal devices are located in a vehicle (for example, placed in the vehicle or mounted in the vehicle), all of the terminal devices may be considered as in-vehicle terminal devices, for example, the in-vehicle terminal devices may also be referred to as on-board units (OBUs).

[0068] As used herein, a base station may be a device that communicates with wireless terminal devices over the air interface in an access network by using one or more cells. The base station may be configured to convert received over-the-air frames to and from Internet Protocol (IP) packets and act as a router between the terminal devices and the rest of the access network, which may include an IP network. The base station may be an evolved NodeB (eNB or eNodeB) in a long term evolution (LTE) system or a long term evolution advanced (LTE-A) system; a next generation NodeB (gNB), a next generation evolved NodeB (ng-eNB), or an enhanced next generation NodeB (en-gNB) in a new radio (NR) system of the 5th generation (5G) mobile communication technology; a central unit (CU) and a distributed unit (DU) in a cloud radio access network (Cloud RAN) system; or a relay device. The embodiments of the present application are not limited thereto.

[0069] In the embodiment of the present application, the source base station (the first base station shown in FIG. 1) and the target base station (the second base station shown in FIG. 1) may be the same type of base station (for example, both are base stations in the LTE system, or both are base stations in the 5G system), or may be different (for example, the source base station is a base station in the LTE system and the target base station is a base station in the 5G system; or the source base station is a base station in the 5G system and the target base station is a base station in the LTE system). This is not limited in the present application.

[0070] Due to the mobility of the terminal device, the terminal device moves from the coverage area of ​​the source base station to the coverage area of ​​the target base station (the dashed arrow in FIG. 1 indicates the moving direction), and the terminal device triggers an inter-base station handover procedure. The inter-base station handover procedure includes the following steps: first, the terminal device performs an air interface handover to hand over the air interface connected to the terminal device from the air interface provided by the source base station to the air interface provided by the target base station; then, the source base station reports handover information to the core network device for the handover; and the core network device performs a core network-related handover after receiving the handover information. There is a time difference between the handover on the core network side and the air interface handover on the terminal device side (the handover on the core network side is later than the air interface handover on the terminal device side). Therefore, after the terminal device hands over the air interface to the target base station, the core network may possibly transmit data to be transmitted to the terminal device to the source base station. In this case, the source base station needs to forward the data to the target base station (data forwarding) after receiving the data, and then the target base station transmits the data to the terminal device.

[0071] Forged packets may exist in a communication network. For security purposes, a packet filtering function is configured for a base station. That is, an ACL is pre-configured on the base station, so that the base station performs access control on received packets through the ACL. Specifically, an IP address is configured in the ACL. After receiving a packet, before continuing to process the packet, the base station needs to determine that both the source IP address and the destination IP address of the packet are within the ACL. Otherwise, the base station will discard the packet.

[0072] However, in a base station handover scenario such as that shown in Figure 1, if the packet filtering function of the target base station is enabled, the target base station needs to obtain the user plane IP address of the source base station in advance and pre-configure an ACL based on the IP address so that the target base station does not discard packets sent by the source base station.

[0073] If the control plane transmission link of the X2 / Xn interface between the source base station and the target base station has not been established, the source base station and the target base station can obtain the IP address (including the control plane IP address and the user plane IP address) of the peer end by using the TNL address discovery procedure to establish the X2 / Xn transmission link (including the control plane transmission link and the user plane transmission link) and configure the IP address of the peer base station in the ACL of the source base station and the target base station.

[0074] For example, FIG. 2 is a schematic diagram of the TNL address discovery procedure and the Xn interface handover procedure.

[0075] Step 1: Perform the TNL address discovery procedure.

[0076] Before performing the Xn interface handover procedure, the source base station and the target base station first perform a TNL address discovery procedure to obtain the IP address of the peer end and configure the ACL in advance. Specifically, the TNL address discovery procedure includes S1.1 to S1.6.

[0077] S1.1: A source base station (e.g., Next Generation Radio Access Network (NG-RAN) node 1) sends an Uplink RAN ​​Configuration Transfer message to a core network device (in FIG. 2, the Access and Mobility Management Function (AMF) is used as an example). The message carries the control plane IP address and user plane IP address of the source base station.

[0078] S1.2: The AMF sends a Downlink RAN ​​Configuration Transfer message to the target base station (e.g., NG-execution node 2). The message carries the control plane IP address and user plane IP address of the source base station.

[0079] S1.3: After receiving the downlink RAN ​​configuration transfer message, the target base station uses the control plane IP address and user plane IP address of the source base station to create a transmission link of the Xn interface and pre-configure the ACL of the target base station.

[0080] S1.4: The target base station sends an uplink RAN ​​configuration transfer message to the core network device, the message carrying the control plane IP address and user plane IP address of the target base station.

[0081] S1.5: The core network device sends a downlink RAN ​​configuration transfer message to the source base station, the message carrying the control plane IP address and user plane IP address of the target base station.

[0082] S1.6: After receiving the downlink RAN ​​configuration transfer message, the source base station uses the control plane IP address and user plane IP address of the target base station to create a transmission link and pre-configure the ACL of the source base station.

[0083] Step 2: Perform the Xn interface setup procedure.

[0084] Step 3: The source base station sends a Handover Request message to the target base station.

[0085] Step 4: The target base station sends a Handover Request Acknowledge message to the source base station.

[0086] Step 5: After the air interface connection of the terminal device is handed over from the source base station to the target base station, the core network still transmits data to be transmitted to the terminal device to the source base station before the core network handover is completed. After receiving the data, the source base station encapsulates the data into packets and forwards the packets to the target base station.

[0087] Step 6: After receiving the packet forwarded by the source base station, the target base station determines that the source IP address (i.e., the IP address of the source base station) and destination IP address (i.e., the IP address of the target base station) of the packet are within the ACL and continues processing the packet.

[0088] As shown in Figure 2, when a control plane transmission link between the source base station and the target base station has not been established, the source base station and the target base station pre-configure an ACL by using a TNL address discovery procedure.

[0089] However, in some scenarios, the source base station and the target base station do not support the TNL procedure, and the target base station cannot pre-configure the user plane IP address of the source base station in the ACL. Therefore, in the process of handing over the terminal device from the source base station to the target base station, the target base station discards packets sent by the source base station.

[0090] Below we provide two possible example scenarios.

[0091] Example 1: Multi-operator sharing scenario

[0092] As shown in FIG. 3, operator A is first introduced to base stations 1 and 2. When a terminal device operated by operator A performs an inter-base station handover, base stations 1 and 2 are triggered to perform a TNL address discovery procedure via the Xn interface, create an Xn transmission link, and pre-configure an ACL corresponding to operator A. The Xn interface operates normally, and data transfer is normal. Then, operator B is introduced. For security purposes, operator A and operator B may share a control plane IP address but not a user plane IP address. Therefore, when a terminal device operated by operator B performs an Xn-based inter-base station handover, operator B's Xn interface control plane transmission link (i.e., operator A's Xn interface control plane transmission link) operates normally. Therefore, when a terminal device operated by operator B performs an inter-base station handover, base stations 1 and 2 are not triggered to perform a TNL address discovery procedure via the Xn interface. As a result, base station 2 cannot obtain the user plane IP address configured by operator B for base station 1 and cannot automatically pre-configure an ACL corresponding to operator B. In a base station handover scenario, when base station 1 forwards a packet corresponding to operator B to base station 2, base station 2 discards the packet and the data transmission fails.

[0093] Example 2: Secondary node change scenario

[0094] First, let us briefly explain the LTE / NR dual connectivity scenario. In a non-standalone (NSA) network based on the Evolved Packet Core (EPC), a terminal device with NSA dual connectivity capability is connected to both an LTE base station and an NR base station. The terminal device transmits by using the radio resources of the two base stations. Data from the terminal device can be divided and transmitted between the two base stations. Dual connectivity is achieved when the carriers on the eNodeB side and the gNodeB side are aggregated separately. One of the two base stations connected to the terminal device is the master base station (also referred to as the master node or master station, etc.), and the other is the secondary base station (also referred to as the secondary node or secondary station, etc.).

[0095] In a secondary node (SN) change procedure in a non-standalone (NSA) network, signaling between a source secondary node (S-SN) and a target secondary node (T-SN) is forwarded by a master node (MN). There is no X2 interface between the S-SN and the T-SN. Therefore, there is no TNL address discovery, and the T-SN cannot obtain the user plane IP address of the S-SN. However, when a terminal device is handed over between the S-SN and the T-SN, the S-SN also forwards data to the T-SN. However, the T-SN cannot obtain the user plane IP address of the S-SN and cannot pre-configure the user plane IP address of the S-SN in the ACL. As a result, the data forwarded by the S-SN is discarded by the T-SN, and data transmission fails.

[0096] It should be understood that a secondary node in this specification may also be referred to as a secondary base station (SgNB) or secondary station, etc., and a master node may also be referred to as a master base station (MgNB) or master station, etc.

[0097] Figure 4 shows the secondary node change procedure triggered by the SN. The procedure includes the following steps:

[0098] S3.1: The S-SN sends an SgNB Change Required message to the MN.

[0099] S3.2: The MN sends an SgNB Change Request message to the T-SN.

[0100] S3.3: The T-SN sends an SgNB Change Request Acknowledge message to the MN.

[0101] S3.4: The MN sends an SgNB Change Confirm message to the S-SN, and the secondary station change confirmation is completed.

[0102] S3.5: After the air interface connection of the terminal device is handed over from the S-SN to the T-SN, if the handover of the Serving Gateway (SGW) is not completed, the SGW still sends the data to be sent to the terminal device to the S-SN, and the S-SN encapsulates the data into packets and forwards the packets to the T-SN after receiving the data.

[0103] S3.6: The T-SN discards the packet forwarded by the S-SN to the T-SN because the source IP address of the packet (i.e., the user plane IP address of the S-SN) is not within the ACL of the T-SN.

[0104] Example 3: Base Station User Plane IP Address Update Scenario

[0105] Using FIG. 1 as an example, the first base station and the second base station exchange IP addresses and pre-configure an ACL based on the TNL address discovery procedure. After a certain period of time, the user plane IP address of the first base station is updated. In this case, the terminal device triggers a base station handover procedure. The terminal device is handed over from the first base station to the second base station. The second base station does not know that the user plane IP address of the first base station has been updated, and the ACL of the second base station still stores only the user plane IP address of the first base station before the update. In this case, if the source base station sends a packet to the target base station using the updated user plane IP address, the target base station will consider that the IP address in the packet does not match the packet in the ACL, and thus the packet sent by the source base station will be discarded.

[0106] From the foregoing description, it can be understood that in some data forwarding scenarios, the target base station cannot pre-configure the ACL by using the TNL procedure, resulting in packets sent by the source base station being discarded by the target base station, resulting in unreliable data transmission.

[0107] To solve the above technical problems, the embodiments of the present application provide an ACL configuration method and apparatus. The source base station may include its user plane IP address in signaling, such as a handover request message, a configuration update message, or a secondary station addition request message, so that the target base station can obtain the user plane IP address of the source base station without performing a TNL address discovery procedure. An ACL may then be configured based on the obtained IP address. Therefore, in a base station handover scenario, a case in which packets transmitted by the source base station are discarded by the target base station may be efficiently avoided, and the reliability of data transmission may be improved.

[0108] In order to make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the following further describes the technical solutions of the embodiments of the present application in detail with reference to the accompanying drawings.

[0109] It should be noted that the terms "system" and "network" may be used interchangeably in embodiments of the present application, and "at least one" refers to one or more, and "multiple" refers to two or more. The term "and / or" is a relational relationship for describing related objects and may indicate that three relationships may exist. For example, A and / or B may indicate the following cases: only A is present, both A and B are present, and only B is present, where A and B may be singular or plural. The character " / " typically indicates an "or" relationship between related objects. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of singular items or plural items. For example, at least one of a, b, or c may refer to a, b, c, a and b, a and c, b and c, or a, b, and c.

[0110] Additionally, unless otherwise specified, ordinal numbers such as "first" and "second" in the embodiments of the present application are used to distinguish between multiple objects and are not intended to limit the order, chronology, priority, or importance of the multiple objects. For example, a first priority criterion and a second priority criterion are merely used to distinguish between different criteria and do not indicate different content, priority, or importance of the two criteria.

[0111] In addition, the terms "comprise" and "have" in the embodiments, claims, and accompanying drawings of the present application are not exclusive. For example, a process, method, system, product, or device that includes a series of steps or modules is not limited to the listed steps or modules and may include additional steps or modules that are not listed.

[0112] With reference to FIGS. 5 to 9, the following describes in detail the solution of ACL configuration in an X2 / Xn-based inter-base station handover scenario.

[0113] 5 shows an ACL configuration method provided in an embodiment of the present application, which includes the following steps:

[0114] S501: A first base station sends a handover request message or a configuration update message to a second base station, and the second base station receives the handover request message or the configuration update message from the first base station. The handover request message or the configuration update message carries a user plane IP address of the first base station.

[0115] An interface for direct communication exists between the first base station and the second base station, for example, an X2 interface or an Xn interface. This is not specifically limited in the present application. When the interface between the first base station and the second base station is an X2 interface, both the first base station and the second base station are evolved NodeBs (eNBs) in a long term evolution (LTE) system or a long term evolution advanced (LTE-A) system. When the interface between the first base station and the second base station is an Xn interface, both the first base station and the second base station are next generation NodeBs (gNBs), next generation evolved NodeBs (ng-eNBs), or enhanced next generation NodeBs (en-gNBs) in a new radio (NR) system of the 5th generation (5G) mobile communication technology.

[0116] S502: The second base station configures an ACL based on the user plane IP address of the first base station.

[0117] Specifically, if an ACL is configured on the second base station, the user plane IP address of the first base station may be added to the ACL as a source IP address, and the IP address of the second base station may be further added as a destination IP address. If an ACL is not configured on the second base station, an ACL is generated. The user plane IP address of the first base station may be added to the generated ACL as a source IP address, and the IP address of the second base station may be further added as a destination IP address.

[0118] In this embodiment of the present application, the first base station may retain the user plane IP address of the first base station in the handover request message, so that the second base station can obtain the user plane IP address of the first base station in the handover procedure and then configure the ACL. In this way, in the process of the terminal being handed over from the first base station to the second base station, the second base station may not discard packets sent by the first base station.

[0119] It may be understood that when a terminal device is handed over between base stations, i.e., when a first base station sends a handover request message to a second base station, the first base station may also be referred to as a source base station, and the second base station may also be referred to as a target base station.

[0120] In this embodiment of the present application, when the configuration of the first base station is updated (for example, but not limited to, when the user plane IP address of the first base station is updated, a neighbor cell is updated, or another update is performed), the first base station may retain the user plane IP address of the first base station in a configuration update message (if it is triggered by an update of the user plane IP address of the first base station, the configuration update message retains the updated user plane IP address of the first base station), so that the second base station can obtain the user plane IP address of the first base station. In this way, when the terminal device is subsequently handed over from the first base station to the second base station, the second base station may not discard packets sent by the first base station in the handover process. This is because the second base station has pre-configured an ACL based on the user plane IP address of the first base station.

[0121] Optionally, after the first base station sends a handover request message or a configuration update message to the second base station, or after the first base station sends a change required message to the core network element, the first base station further receives data to be transmitted to the terminal device from the core network. Alternatively, the first base station further receives data to be transmitted to the core network from the terminal device. In this case, since the terminal device is handed over to the second base station, the first base station generates a packet based on the received data, adds a source IP address and a destination IP address to the packet, and then transmits the packet to the second base station. The source IP address is the user plane IP address of the first base station, and the destination IP address is the user plane IP address of the second base station. Correspondingly, after receiving the packet transmitted by the first base station, the second base station determines whether the source IP address of the packet is within the ACL. If the source IP address of the packet is within the ACL, the second base station processes the packet. If the source IP address of the packet is not within the ACL, the second base station discards the packet.

[0122] The user plane IP address of the first base station is configured in the ACL of the second base station, so the second base station will not discard packets, which improves the reliability of data transmission.

[0123] Optionally, in step S501, the first base station sends a handover request message to the second base station, including but not limited to the following two manners:

[0124] Manner 1: The first base station sends a handover request message to the second base station through the interface between the first base station and the second base station.

[0125] For example, the first base station and the second base station are both base stations in an LTE system, and the first base station sends the handover request message to the second base station through the X2 interface. Alternatively, for example, the first base station and the second base station are both base stations in a 5G system, and the first base station sends the handover request message to the second base station through the Xn interface.

[0126] Manner 2: The first base station sends a handover request message to the second base station via a core network element.

[0127] For example, a first base station generates a change required message, where the change required message carries the user plane IP address of the first base station. The first base station sends the change required message to a core network element. After receiving the change required message, the core network element generates a handover request message, where the handover request message carries the user plane IP address of the first base station. The core network element sends the handover request message to a second base station.

[0128] It should be understood that the core network element may be any network element, such as an AMF, that can communicate with the first base station and the second base station, which is not limited in this embodiment of the present application.

[0129] It should be noted that in the inter-base station handover process, a necessary condition for the first base station to retain its user plane IP address in the change required message is that there is a direct forwarding path between the first base station and the second base station. In other words, when the first base station subsequently sends a packet (in which data from the core network or data from the device is encapsulated) to the second base station, the packet is sent directly through the interface between the first base station and the second base station.

[0130] In this way, for the second base station, if the first base station does not directly transmit packets to the second base station (e.g., there is no direct forwarding path between the first base station and the second base station, and the packets need to be forwarded by the core network to reach the second base station), the second base station will not perform unnecessary ACL configuration, thereby improving the utilization of system resources.

[0131] In order to better understand the technical solution shown in FIG. 5, the following further provides some complete embodiments with reference to some specific inter-base station handover scenarios. Embodiment 1

[0132] As shown in Figure 6, an X2-based inter-base station handover scenario (ie, the interface between the source base station and the target base station is an X2 interface) is used as an example. The solution includes the following steps:

[0133] S601: When a UE is handed over from a source eNodeB to a target eNodeB, the source eNodeB sends a Handover Request message to the target eNodeB, where the Handover Request message carries the X2 interface user plane IP address of the source eNodeB.

[0134] S602: The target eNodeB sends a Handover Request Acknowledge message to the source eNodeB.

[0135] S603: The target eNodeB configures an ACL based on the user plane IP address of the source eNodeB (i.e., the source node of the data forwarding) and the user plane IP address of the target eNodeB (the target eNodeB is the destination node of the data forwarding) carried in the handover request message.

[0136] It can be understood that in Figure 6, the target eNodeB starts configuring the ACL after the target eNodeB sends a handover request acknowledgement message to the source eNodeB as an example. In practice, the ACL may be configured earlier or later. This is not a limitation in the present application.

[0137] S604: The source eNodeB sends an RRC Connection Reconfiguration to the UE.

[0138] S605: The source eNodeB sends an SN Status Transfer message to the target eNodeB.

[0139] S606: The source eNodeB forwards data from the core network or data from the terminal device to the target eNodeB, and the data is specifically sent to the target eNodeB in the form of a packet. The packet carries a source IP address (i.e., the user plane IP address of the source eNodeB) and a destination IP address (i.e., the user plane IP address of the target eNodeB).

[0140] S607: The target eNodeB determines, based on the configured ACL, whether the source IP address (i.e., the user plane IP address of the source eNodeB) and the destination IP address (the user plane IP address of the target eNodeB) carried in the packet are within the ACL. If the source IP address and the destination IP address carried in the packet are within the ACL, the target eNodeB continues to process the packet. If the source IP address and the destination IP address carried in the packet are not within the ACL, the target eNodeB discards the packet.

[0141] It should be understood that the target eNodeB adds the user plane IP address of the source eNodeB and the user plane IP address of the target eNodeB to the ACL in S603. Therefore, the target eNodeB determines that the ACL contains the source IP address and destination IP address of the packet, and does not discard the packet, but continues to process the packet.

[0142] S608: The UE and the target eNodeB perform a random access procedure.

[0143] S609: The UE sends an RRC Connection Reconfiguration Complete message.

[0144] S610: The target eNodeB and a mobility management entity (MME) perform a path switch procedure.

[0145] S611: The target eNodeB sends a UE Context release message to the source eNodeB.

[0146] According to S601-S611, the target eNodeB discovers the user plane IP address of the source eNodeB in the base station handover process, and then configures the ACL.

[0147] It should be noted that in the above-mentioned inter-base station handover process, the source eNodeB may not retain the user plane IP address of the source eNodeB, but may inform the target eNodeB of the X2 interface user plane IP address of the source eNodeB by using an evolved NodeB Configuration Update (eNB Configuration Update) message of the X2 interface of the source eNodeB. The target eNodeB may pre-configure an ACL based on the user plane IP address. When the handover process is performed, the target base station may perform access control on received packets based on the pre-configured ACL. In this case, the handover procedure differs only in that the handover request message in S601 may not retain the X2 interface user plane IP address of the source eNodeB, and the step of configuring the ACL (S603) may be performed at any time before data transfer (S606), for example, before S601. This is not specifically limited in the present application.

[0148] It should be understood that the eNB Configuration Update message may be triggered when the configuration of the source eNodeB is updated, for example, when the user plane IP address of the source eNodeB is changed or when a neighbor cell is changed. This is not a limitation in this application. In any scenario where a Configuration Update message needs to be sent, the user plane IP address of the sender (e.g., source eNodeB) may be carried in the message.

[0149] In embodiment 1, when the packet filtering function is enabled, the target eNodeB obtains the IP address of the data forwarding source through X2 signaling, and then automatically pre-configures the ACL. There is no need to manually configure the ACL. Therefore, the reliability of data transmission can be improved. Embodiment 2

[0150] As shown in Figure 7, an Xn-based inter-base station handover scenario (ie, the interface between the source base station and the target base station is an Xn interface) is used as an example. The solution includes the following steps:

[0151] S701: The source gNB sends a Handover Request message to the target gNB, where the message carries the user plane IP address of the source gNB.

[0152] S702: The target gNB sends a Handover Request Acknowledge message to the source gNB.

[0153] It can be understood that after receiving the handover request message sent by the source gNB, the target gNB configures the ACL based on the user plane IP address of the source gNB. In Figure 7, it is used as an example that the target gNB starts configuring the ACL after the target gNB sends a handover request acknowledgement message to the source gNB. In practice, the ACL may be configured earlier or later. This is not a limitation in the present application.

[0154] S703: The UE and the source gNB perform a handover initiation procedure.

[0155] S704: The source gNB sends an SN status transfer message to the target gNB.

[0156] As shown in Figure 7, the target gNB receives a packet sent by the source gNB, and the target gNB determines whether both the source IP address and the destination IP address of the packet are within the ACL. If both the source IP address and the destination IP address of the packet are within the ACL, the target gNB continues processing the packet. If both the source IP address and the destination IP address of the packet are not within the ACL, the target gNB discards the packet.

[0157] S705: The UE and the source gNB perform a Handover Completion procedure.

[0158] S706: The target gNB and AMF perform a Path Switch procedure.

[0159] S707: The target gNB sends a UE context release message to the source gNB, causing the source gNB to release the UE context.

[0160] It should be noted that in the aforementioned inter-base station handover process, the source gNB may not retain its user plane IP address, but may inform the target gNB of its Xn interface user plane IP address by using an NG-RAN Node Configuration Update message of the Xn interface of the source gNB. The target gNB may pre-configure an ACL based on the user plane IP address. When the handover process is performed, the target base station may perform access control on received packets based on the pre-configured ACL. In this case, the handover procedure differs only in that the handover request message in S701 may not retain the Xn interface user plane IP address of the source gNB, and the step of configuring the ACL by the target gNB may be performed at any time before data transfer, for example, before S701. This is not specifically limited in the present application.

[0161] It should be understood that the NG-Execute Node Configuration Update message may be triggered when the configuration of the source gNB is updated, for example, when the user plane IP address of the source gNB is changed or when a neighboring cell is changed. This is not a limitation in this application. In any scenario where a Configuration Update message needs to be sent, the user plane IP address of the sender (e.g., source gNB) may be carried in the message.

[0162] In embodiment 2, when the packet filtering function is enabled, the target gNB obtains the IP address of the data forwarding source through Xn signaling, and then automatically pre-configures the ACL, eliminating the need to manually configure the ACL, thereby improving the reliability of data transmission. Embodiment 3

[0163] In the above embodiment 1 and embodiment 2, an example is used in which the source base station directly sends the handover request message to the target base station. In practical application, the handover request message can alternatively be sent by the source base station to the target base station through a core network.

[0164] As shown in Figure 8, the NG handover scenario is used as an example, and the following steps are specifically included:

[0165] S801: The source gNB sends a change required message to the current serving AMF. If the source gNB detects that there is a direct forwarding path between the source gNB and the target gNB, the user plane IP address of the source gNB is retained in the message.

[0166] S802: The AMF selects an AMF and a User Plane Function (UPF) to be used by the terminal device to perform a base station handover.

[0167] S803: The AMF sends a handover request message to the target gNB, where the message carries the user plane IP address of the source gNB.

[0168] S804: The target gNB sends a handover request acknowledgement message to the AMF.

[0169] It should be understood that after receiving the handover request message, the target gNB may configure an ACL based on the user plane IP address of the source gNB.

[0170] S805: The AMF sends a handover command to the source gNB.

[0171] S806: The source gNB sends a handover command to the UE.

[0172] S807: The source gNB sends an Uplink RAN ​​Status Transfer message to the AMF.

[0173] S808: The AMF sends a Downlink RAN ​​Status Transfer message to the target gNB.

[0174] S809: Perform a data forwarding procedure. Specifically, the UPF sends downlink user plane data to the source gNB, and the source gNB forwards the data directly to the target gNB (i.e., S809a), or the source gNB forwards the data to the target gNB through the UPF (i.e., S809b).

[0175] If the source gNB forwards data directly to the target gNB (i.e., S809a), the target gNB decides whether to continue processing the packet or discard the packet based on the ACL after receiving the packet.

[0176] S810: The UE sends a handover confirmation message to the target gNB.

[0177] S811: The target gNB sends a handover notification message to the AMF.

[0178] S812: Release the UE context. Specifically, the AMF sends a UE context release command message to the source gNB. The UE releases the context and sends a UE context release complete message to the AMF.

[0179] Note that in step S801, if the source gNB detects that there is no direct forwarding path between the source gNB and the target gNB, the user plane IP address of the source gNB does not need to be retained in the message, because the data needs to be forwarded through the NG interface of the core network in indirect forwarding. The target gNB may obtain the IP address of the UPF by using the NG interface user plane setup procedure.

[0180] In embodiment 3, when the packet filtering function is enabled, in a direct forwarding scenario of NG handover, the target base station may obtain the IP address of the data forwarding source through NG signaling and automatically pre-configure the ACL, eliminating the need to manually configure the ACL. Therefore, the reliability of data transmission may be improved.

[0181] Figures 5 to 8 illustrate solutions for ACL configuration in an X2 / Xn-based inter-base station handover scenario. Below, with reference to Figures 9, 10A, and 10B, solutions for ACL configuration in an SN inter-base station handover scenario in an LTE / NR dual connectivity scenario will be described.

[0182] 9 shows an ACL configuration method provided in an embodiment of the present application, which includes the following steps:

[0183] S901: The master base station (MN) sends a secondary station addition request message to the target secondary base station (T-SN), and the target secondary base station receives the secondary station addition request message from the master base station, where the secondary station addition request message carries the user plane IP address of the source secondary base station (S-SN).

[0184] In this embodiment of the present application, the SN-to-SN base station handover may be triggered by the MN or may be triggered by the S-SN, which is not limited in the present application.

[0185] S902: The target secondary base station configures an ACL based on the user plane IP address of the source secondary base station.

[0186] Specifically, if the user plane IP address of the source secondary base station and the user plane IP address of the target secondary base station (i.e., the target secondary base station) are not in the ACL of the target secondary base station, the user plane IP address of the source secondary base station and the user plane IP address of the target secondary base station are added to the ACL. The user plane IP address of the source secondary base station is used as the source IP address, and the user plane IP address of the target secondary base station is used as the destination IP address.

[0187] In this embodiment of the present application, during the SN change procedure, the MN retains the user plane IP address of the S-SN in the secondary station addition request message, so that the T-SN can obtain the user plane IP address of the S-SN without performing the TNL address discovery procedure. Then, an ACL can be configured based on the obtained S-SN. Therefore, in an SN handover scenario, the case where packets sent by the S-SN are discarded by the T-SN can be effectively avoided, and the reliability of data transmission can be improved.

[0188] Optionally, after the MN sends a secondary station addition request message to the T-SN, the S-SN further receives data to be transmitted to the terminal device from the core network. Alternatively, the S-SN further receives data to be transmitted to the core network from the terminal device. In this case, since the terminal device is handed over to the T-SN, the S-SN generates a packet based on the received data, adds a source IP address and a destination IP address to the packet, and then transmits the packet to the T-SN. The source IP address is the user plane IP address of the S-SN, and the destination IP address is the user plane IP address of the T-SN. Correspondingly, after receiving the packet transmitted by the S-SN, the T-SN determines whether the source IP address of the packet is within the ACL. If the source IP address of the packet is within the ACL, the T-SN processes the packet. If the source IP address of the packet is not within the ACL, the T-SN discards the packet.

[0189] The user plane IP address of the S-SN is configured in the ACL of the T-SN, so the T-SN will not discard packets, which improves the reliability of data transmission.

[0190] Optionally, in step S501, the MN sends a secondary station addition request message to the T-SN, including but not limited to the following two ways:

[0191] Scheme 1: The S-SN and the T-SN correspond to the same MN. In this case, the MN directly generates a secondary station addition request message and sends the secondary station addition request message to the T-SN.

[0192] For example, the coverage area of ​​the MN is relatively large, the coverage area of ​​the S-SN and that of the T-SN are relatively small, and the S-SN and T-SN are within the coverage area of ​​the same MN. In this case, the S-SN and T-SN correspond to the same MN.

[0193] Scheme 2: The S-SN and the T-SN correspond to different MNs. For example, the S-SN corresponds to the source master base station (S-MN) and the T-SN corresponds to the target master base station (T-MN). In this case, the S-MN sends a handover request message to the T-MN, and then the T-MN sends a secondary station addition request message to the T-SN.

[0194] For example, if the S-MN and S-SN are in the same coverage area and the T-MN and T-SN are in the same coverage area, the S-SN and T-SN may correspond to different MNs.

[0195] For example, the S-MN first sends a handover request message (the handover request message carries the user plane IP address of the S-SN) to the T-MN. After receiving the handover request message, the T-MN generates a secondary station addition request message and sends the secondary station addition request message to the T-SN.

[0196] Note that in this example, the UE's service bearer is established only on the S-SN. Therefore, the handover request message and the secondary station addition request message only carry the user plane IP address of the S-SN, and only the T-SN configures the ACL. However, in practical applications, the UE's service bearer may be established on both the S-SN and the S-MN.

[0197] If the service bearer of the UE is only established on the S-MN, please refer to the embodiment shown in Figure 5 for the actual handover process. Specifically, the S-MN sends a handover request message to the T-MN, and the message carries the user plane IP address of the S-MN, and the T-MN configures an ACL based on the user plane IP address of the S-MN.

[0198] When the UE's service bearer has been established in both the S-MN and the S-MN, the actual handover process is as follows: The S-MN sends a handover request message to the T-MN, where the message carries the user plane IP address of the S-MN and the user plane IP address of the S-SN. The T-MN configures an ACL based on the user plane IP address of the S-MN. The T-MN sends a secondary station addition request message to the S-SN, where the message carries the user plane IP address of the S-SN. The T-SN configures an ACL based on the user plane IP address of the S-SN.

[0199] In order to better understand the technical solution shown in FIG. 9, the following further provides several complete embodiments with reference to several specific LTE / NR dual connectivity scenarios. Embodiment 4

[0200] 10A and 10B, an example is used in which the S-SN triggers the inter-SN base station handover procedure, and the S-SN and T-SN correspond to the same MN. The inter-SN base station handover procedure includes the following steps:

[0201] S1001: The S-SN sends an SgNB Change Required message to the MN.

[0202] S1002: The MN sends an SgNB Addition Request message to the T-SN, and the message carries the user plane IP address of the S-SN.

[0203] S1003: The T-SN sends an SgNB Addition Request Acknowledge message to the MN.

[0204] It should be understood that after receiving the SgNB addition request message, the T-SN configures an ACL based on the user plane IP address of the S-SN.

[0205] S1004: The MN sends an RRC Connection Reconfiguration message to the UE.

[0206] S1005: The UE sends an RRC Connection Reconfiguration Complete message to the MN.

[0207] S1006: The MN sends an SgNB Change Confirm message to the S-SN.

[0208] S1007: The MN sends an SgNB Reconfiguration Complete message to the T-SN.

[0209] S1008: The UE initiates a random access procedure for the T-SN.

[0210] S1009: The S-SN sends an SN Status Transfer message to the T-SN.

[0211] S1009 includes S1009a and S1009b. S1009a: The S-SN sends an SN status transfer message to the MN. S1009b: The MN sends an SN status transfer message to the T-SN.

[0212] It should be understood that when the T-SN receives a packet from the S-SN, the T-SN determines whether to continue processing the packet or discard the packet based on the ACL.

[0213] S1010: The MN sends a Secondary RAT Data Usage Report to the S-SN.

[0214] S1011: The MN transmits an E-RAB Marker modification indication to the SGW.

[0215] S1012: The SGW and the MME perform bearer modification for the UE.

[0216] S1013: The SGW sends an end marker packet to the S-SN via the MN.

[0217] S1014: The SGW sends a New Path message to the T-SN.

[0218] S1015: The MME sends an E-RAB Marker modification Confirm message to the MN.

[0219] S1016: The MN instructs the S-SN to release the context of the UE.

[0220] It should be noted that before S1001, if the MN does not have a user plane IP address configuration of the S-SN, the MN may initiate a secondary station change procedure triggered by the MN to obtain the configuration of the S-SN, and then obtain the user plane IP address of the S-SN.

[0221] In embodiment 4, when the packet filtering function is enabled, the T-SN obtains the IP address of the data transmission source through X2 signaling and automatically pre-configures the ACL, eliminating the need to manually configure the ACL, thereby improving the reliability of data transmission. Embodiment 5

[0222] 11A and 11B, an example is used in which an MN triggers an inter-SN base station handover procedure, and the S-SN and T-SN correspond to the same MN. The inter-SN base station handover procedure includes the following steps:

[0223] S1101: MN sends an SgNB Addition Request message to S-SN, and the message carries the user plane IP address of the S-SN.

[0224] S1102: The T-SN sends an SgNB Addition Request Acknowledge message to the MN.

[0225] It should be understood that after receiving the SgNB addition request message, the T-SN may configure an ACL based on the user plane IP address of the S-SN.

[0226] S1103: MN releases S-SN.

[0227] S1103 includes: S1103a: MN sends an SgNB Release Request message to S-SN; and S1103b: S-SN sends an SgNB Release Request Acknowledge message to MN.

[0228] S1104: The MN sends an RRC Connection Reconfiguration message to the UE.

[0229] S1105: The UE sends an RRC Connection Reconfiguration Complete message to the MN.

[0230] S1106: The MN sends an SgNB Reconfiguration Complete message to the T-SN.

[0231] S1107: The UE initiates a random access procedure for the T-SN.

[0232] S1108: The S-SN sends an SN Status Transfer message to the T-SN.

[0233] S1108 includes: S1108a: S-SN sends an SN status transfer message to MN; and S1108b: MN sends an SN status transfer message to T-SN.

[0234] It should be understood that when the T-SN receives a packet from the S-SN, the T-SN determines whether to continue processing the packet or discard the packet based on the ACL.

[0235] S1109: The MN transmits a Secondary RAT Data Usage Report to the S-SN.

[0236] S1110: The MN transmits an E-RAB Marker modification indication to the SGW.

[0237] S1111: The SGW and MME perform bearer modification for the UE.

[0238] S1112: The SGW sends an End Marker Packet to the S-SN by using the MN.

[0239] S1113: The SGW sends a New Path message to the T-SN.

[0240] S1114: The MME sends an E-RAB Marker modification Confirm message to the MN.

[0241] S1115: The MN instructs the S-SN to release the context of the UE.

[0242] It should be noted that before S1101, if the MN does not have a user plane IP address configuration of the S-SN, the MN may initiate a secondary station change procedure triggered by the MN to obtain the configuration of the S-SN, and then obtain the user plane IP address of the S-SN.

[0243] In embodiment 5, T-SN obtains the IP address of the data transmission source through X2 signaling and automatically pre-configures the ACL, eliminating the need to manually configure the ACL, thereby improving the reliability of data transmission. Embodiment 6

[0244] 12A and 12B, the procedure of simultaneous handover between MN base stations and handover between SN base stations is used as an example. The handover procedure includes the following steps:

[0245] S1201: The S-MN sends a Handover Request message to the T-MN, where the message carries the user plane IP address of the S-SN and / or the user plane IP address of the S-MN.

[0246] Bearers of dual connectivity services carry the address of the S-SN, and bearers of non-dual connectivity services carry the address of the S-MN.

[0247] The T-MN may configure an ACL based on the user plane IP address of the S-MN and the IP address of the T-MN in the handover request message.

[0248] S1202: The T-MN sends an SgNB Addition Request message to the T-SN, and the message carries the user plane IP address of the S-SN.

[0249] The source user plane IP address of the data transfer carried on the dual connection bearer for handover to the T-SN is obtained from the handover request message.

[0250] The T-SN may configure an ACL based on the user plane IP address and the T-SN's IP address in the SgNB addition request message.

[0251] S1203: The T-SN sends an SgNB Addition Request Acknowledge message to the T-MN.

[0252] S1204: The T-MN sends a Handover Request Acknowledge message to the S-MN.

[0253] S1205: S-MN releases S-SN.

[0254] S1205 includes: S1205a: S-MN sends an SbNB release request message to S-SN; and S1205b: S-SN sends an SgNB release request acknowledgement message to S-MN.

[0255] S1206: The S-MN sends an RRC Connection Reconfiguration message to the UE, and the S-MN sends an SgNB Change Confirmation message to the S-SN.

[0256] S1207: The UE initiates a random access procedure to the T-MN.

[0257] S1208: The UE sends an RRC Connection Reconfiguration Complete message to the T-SN.

[0258] S1209: The UE initiates a random access procedure for the T-SN.

[0259] S1210: The T-SN sends an SgNB Reconfiguration Complete message to the T-MN.

[0260] S1211: The S-SN sends a Secondary RAT Data Usage Report to the MME by using the S-MN (including S1211a and S1211b).

[0261] S1212: An SN status transfer message is transmitted.

[0262] Specifically, the following steps are included: S1212a: S-SN sends an SN status transfer message to S-MN; S1212b: S-MN sends an SN status transfer message to T-MN; and S1212c: T-MN sends an SN status transfer message to T-SN.

[0263] It should be understood that when a T-SN receives a packet from an S-SN, the T-SN determines whether to continue processing the packet or to discard the packet based on the ACL configured on the T-SN. When a T-MN receives a packet from an S-MN, the T-MN determines whether to continue processing the packet or to discard the packet based on the ACL configured on the T-MN.

[0264] S1213: MME and T-SN perform a path switching procedure.

[0265] S1214: The S-MN instructs the T-MN to release the context of the UE.

[0266] S1215: The S-MN instructs the S-SN to release the context of the UE.

[0267] It should be noted that before S1101, if the MN does not have a user plane IP address configuration of the S-SN, the MN may initiate a secondary station change procedure triggered by the MN to obtain the configuration of the S-SN, and then obtain the user plane IP address of the S-SN.

[0268] In embodiment 6, the T-SN and T-MN obtain the IP address of the data transmission source through X2 signaling, and automatically pre-configure the ACL, eliminating the need to manually configure the ACL, thereby improving the reliability of data transmission. Embodiment 7

[0269] An example of a scenario in which an eNodeB / gNodeB is changed to a master station is used, as shown in Figures 13A and 13B. The handover procedure includes the following steps:

[0270] S1301: A source base station S-eNB sends a Handover Request message to a T-MN, where the message carries an S-SN and / or a user plane IP address of the S-eNB.

[0271] The T-MN may configure an ACL based on the user plane IP address of the S-eNB and the IP address of the T-MN in the handover request message.

[0272] S1302: The T-MN sends an SgNB Addition Request message to the T-SN, where the message carries the user plane IP address of the S-eNB.

[0273] The source IP address of the data transfer of the dual connection bearer is obtained from the handover request message.

[0274] The T-SN may configure an ACL based on the user plane IP address of the S-eNB and the IP address of the T-SN in the SgNB addition request message.

[0275] S1303: The T-SN sends an SgNB Addition Request Acknowledge message to the T-MN.

[0276] S1304: The T-MN sends a Handover Request Acknowledge message to the S-eNB.

[0277] S1305: The S-eNB sends an RRC Connection Reconfiguration message to the UE.

[0278] S1306: The UE initiates a random access procedure to the T-MN.

[0279] S1307: The UE sends an RRC Connection Reconfiguration Complete message to the T-SN.

[0280] S1308: The UE initiates a random access procedure for the T-SN.

[0281] S1309: The T-MN sends an SgNB Reconfiguration Complete message to the T-SN.

[0282] S1310: An SN status transfer message is transmitted.

[0283] S1310 includes: S1310a: The S-eNB sends an SN status transfer message to the T-MN; and S1310b: The T-MN sends an SN status transfer message to the T-SN.

[0284] S1311: Data transfer is performed.

[0285] When a T-SN receives a packet from an S-eNB, the T-SN determines whether to continue processing the packet or discard the packet based on the ACL configured on the T-SN. When a T-MN receives a packet from an S-eNB, the T-MN determines whether to continue processing the packet or discard the packet based on the ACL configured on the T-MN.

[0286] S1312: The T-MN and the MME perform a route switching procedure.

[0287] S1313: The T-MN instructs the S-eNB to release the context of the UE.

[0288] In embodiment 7, when the packet filtering function is enabled, in the scenario where the eNodeB / gNodeB changes to a master station, the T-MN and T-SN obtain the IP address of the data forwarding source through X2 signaling and automatically pre-configure the ACL, eliminating the need to manually configure the ACL, thereby improving the reliability of data transmission. Embodiment 8

[0289] 14A and 14B, the following diagrams are used as an example of a scenario in which the master station is changed to an eNodeB / gNodeB. The handover procedure includes the following steps:

[0290] S1401: The S-MN sends a handover request message to a target base station T-eNB, where the message carries the user plane IP address of the S-SN and / or the user plane IP address of the S-MN.

[0291] Bearers of dual connectivity services carry the address of the S-SN, and bearers of non-dual connectivity services carry the address of the S-MN.

[0292] The T-eNB may configure the ACL based on the user plane IP address of the S-SN and / or S-MN in the handover request message and the IP address of the T-eNB.

[0293] S1402: The T-eNB sends a Handover Request Acknowledge message to the T-MN.

[0294] S1403: S-MN releases S-SN.

[0295] S1403 includes: S1403a: S-MN sends an SbNB release request message to S-SN; and S1403b: S-SN sends an SgNB release request acknowledgement message to S-MN.

[0296] S1404: The S-MN sends an RRC Connection Reconfiguration message to the UE.

[0297] S1405: The UE initiates a random access procedure to the T-eNB.

[0298] S1406: The UE transmits an RRC Connection Reconfiguration Complete message to the T-eNB.

[0299] S1407: An SN status transfer message is transmitted.

[0300] Specifically, the following steps are included: S1407a: S-SN sends an SN status transfer message to S-MN; and S1407b: S-MN sends an SN status transfer message to T-eNB.

[0301] S1408: Data transfer is performed.

[0302] It should be understood that when the T-eNB receives a packet from the S-SN, the T-eNB determines whether to continue processing the packet or to discard the packet based on the ACL configured on the T-eNB. When the T-eNB receives a packet from the S-MN, the T-eNB determines whether to continue processing the packet or to discard the packet based on the ACL configured on the T-eNB.

[0303] S1409: The S-SN sends a Secondary RAT Data Usage Report to the MME by using the S-MN (including S1409a and S1409b).

[0304] S1410: The T-eNB and the MME perform a path switching procedure.

[0305] S1411: The T-eNB instructs the T-MN to release the context of the UE.

[0306] S1412: The T-MN instructs the S-SN to release the context of the UE.

[0307] In embodiment 8, when the packet filtering function is enabled, in a scenario where the master station is changed to an eNodeB / gNodeB, the T-eNB obtains the IP address of the data forwarding source through X2 signaling and automatically pre-configures the ACL, eliminating the need to manually configure the ACL. Therefore, the reliability of data transmission can be improved.

[0308] It should be understood that the embodiments herein can be combined with each other to achieve different technical effects.

[0309] The foregoing describes various methods provided in the embodiments of the present application, and the following describes apparatuses provided in the embodiments of the present application.

[0310] Based on the same technical concept, an embodiment of the present application further provides an ACL configuration device. The device may be, for example, a base station or a chip disposed inside the base station. The device has functions implemented by any of the base stations in FIGS. 5 to 14A and 14B. For example, the device 800 includes corresponding modules, units, or means for performing steps performed by any of the base stations in the embodiments shown in FIGS. 5 to 14A and 14B. The functions, units, or means may be implemented by software, or by hardware, or by hardware executing corresponding software.

[0311] For example, as shown in FIG. 15, the apparatus includes a transceiver unit 1501 and a processing unit 1502.

[0312] When the device is located in the second base station shown in FIG. 5, the functions of the modules of the device are as follows.

[0313] The transceiver unit 1501 is configured to receive a handover request message or a configuration update message from a first base station, where the handover request message or the configuration update message carries a user plane IP address of the first base station.

[0314] The processing unit 1502 is configured to configure an ACL based on a user plane IP address.

[0315] Optionally, the transceiver unit 1501 is further configured to receive a packet from the first base station after the processing unit 1502 configures an ACL based on the user plane IP address. The processing unit 1502 is further configured to determine whether a source IP address of the packet is within the ACL. If the source IP address of the packet is within the ACL, the processing unit 1502 processes the packet. If the source IP address of the packet is not within the ACL, the processing unit 1502 discards the packet.

[0316] Optionally, when receiving a handover request message from the first base station, the transceiver unit 1501 is specifically configured to receive the handover request message from the first base station via a core network element.

[0317] When the device is located in the first base station shown in FIG. 5, the functions of the modules of the device are as follows.

[0318] The processing unit 1502 is configured to generate a handover request message or a configuration update message, where the handover request message or the configuration update message carries a user plane IP address of the first base station. The transceiver unit 1501 is configured to transmit the handover request message or the configuration update message to the second base station.

[0319] Optionally, the transceiver unit 1501 is specifically configured to send a handover request message to the second base station via a core network element.

[0320] Optionally, the transceiver unit 1501 is further configured to receive data from the core network or receive data from the terminal device after sending the handover request message or the configuration update message to the second base station. The processing unit 1502 is further configured to generate a packet based on the data. The transceiver unit 1501 is further configured to send the packet to the second base station, where the packet carries a source IP address, and the source IP address is a user plane IP address of the first base station.

[0321] Optionally, the packet is transmitted over an interface between the first base station and the second base station.

[0322] When the device is located in the target secondary base station shown in FIG. 9, the functions of the modules of the device are as follows.

[0323] The transceiver unit 1501 is configured to receive a secondary station addition request message from the master base station, where the secondary station addition request message carries a user plane IP address of the source secondary base station.

[0324] The processing unit 1502 is configured to configure an ACL based on a user plane IP address.

[0325] Optionally, the transceiver unit 1501 is further configured to receive a packet from the source secondary base station after the processing unit 1502 configures an ACL based on the user plane IP address. The processing unit 1502 is further configured to determine whether a source IP address of the packet is within the ACL. If the source IP address of the packet is within the ACL, the processing unit 1502 processes the packet. If the source IP address of the packet is not within the ACL, the processing unit 1502 discards the packet.

[0326] Optionally, the source secondary base station and the target secondary base station correspond to different master base stations. For example, the master base station is the target master base station, and the source secondary base station corresponds to the source master base station. When receiving a secondary station addition request message from the master base station, the transceiver unit 1501 is particularly configured to receive a secondary station addition request message from the target master base station.

[0327] Optionally, both the target secondary base station and the source secondary base station correspond to a master base station, ie the target secondary base station and the source secondary base station correspond to the same master base station.

[0328] When the device is located in the master base station shown in FIG. 9, the functions of the modules of the device are as follows:

[0329] The processing unit 1502 is configured to generate a secondary station addition request message, where the secondary station addition request message carries a user plane IP address of the source secondary base station.

[0330] The transceiver unit 1501 is configured to transmit a secondary station addition request message to the target secondary base station.

[0331] Optionally, the source secondary base station and the target secondary base station correspond to different master base stations. For example, the source secondary base station corresponds to the source master base station and the target secondary base station corresponds to the target master base station. Before generating the secondary station addition request message, the processing unit 1502 is further configured to receive a handover request message from the source master base station, where the handover request message carries a user plane IP address of the source secondary base station.

[0332] Optionally, the handover request message further carries a user plane IP address of the source master base station, and the processing unit 1502 is further configured to configure an ACL based on the user plane IP address of the source master base station.

[0333] Optionally, the target secondary base station and the source secondary base station correspond to a master base station, ie the target secondary base station and the source secondary base station correspond to the same master base station.

[0334] Based on the same technical concept, an embodiment of the present application further provides a communication device. As shown in Fig. 16, the device includes a processor 1601 and a memory 1602. The memory 1602 is configured to store computer-executable instructions. The processor 1601 is configured to execute the computer-executable instructions stored in the memory 1602, thereby causing the communication device to perform the method performed by any of the base stations in the embodiments shown in Figs. 5 to 14A and 14B.

[0335] The processor 1601 and the memory 1602 may be coupled by using an interface circuit or may be integrated together, which is not a limitation herein.

[0336] In this embodiment of the present application, the specific connection medium between the processor 1601 and the memory 1602 is not limited. In this embodiment of the present application, the processor 1601 and the memory 1602 are connected through a bus in FIG. 16, and the bus is represented by a thick line in FIG. 16. The connection manner between other components is only described schematically and is not limited thereto. The bus may be classified into an address bus, a data bus, a control bus, etc. For ease of representation, there is only one thick line in FIG. 16 to represent the bus, but this does not mean that there is only one bus or only one type of bus.

[0337] It should be understood that the processors mentioned in the embodiments of the present application may be implemented by hardware or software. When the processor is implemented by hardware, the processor may be a logic circuit or an integrated circuit, etc. When the processor is implemented by software, the processor may be a general-purpose processor and is implemented by reading software code stored in a memory.

[0338] For example, a processor may be a Central Processing Unit (CPU), or may be another general-purpose processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), another programmable logic device, a discrete gate, a transistor logic device, or a discrete hardware component, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like.

[0339] It can be understood that the memory referred to in the embodiments of the present application can be volatile memory or nonvolatile memory, or can include volatile memory and nonvolatile memory. Nonvolatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM) and is used as an external cache. By way of example and not limitation, many forms of RAM may be used, such as static random access memory (Static RAM, SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct Rambus random access memory (Direct Rambus RAM, DR RAM).

[0340] It should be noted that if the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (storage module) may be integrated into the processor.

[0341] Note that memory as described herein is intended to include, without being limited to, these and any other suitable types of memory.

[0342] Based on the same technical concept, an embodiment of the present application further provides a communication device. As shown in Fig. 17, the device includes a processor 1701 and an interface circuit 1702. The interface circuit 1702 is configured to receive code instructions and transmit the code instructions to the processor 1701. The processor 1701 executes the code instructions to perform the method performed by any of the base stations in the embodiments shown in Figs. 5 to 14A and 14B.

[0343] Based on the same technical concept, an embodiment of the present application further provides a computer-readable storage medium configured to store instructions that, when executed, implement the methods performed by any of the base stations in the embodiments shown in Figures 5 to 14A and 14B.

[0344] Based on the same technical concept, an embodiment of the present application further provides a chip, coupled to a memory, configured to read and execute program instructions stored in the memory to implement the methods performed by any of the base stations in the embodiments shown in Figures 5 to 14A and 14B.

[0345] Based on the same technical concept, an embodiment of the present application further provides a computer program product including instructions, which, when executed on a computer, cause the computer to perform the method performed by any of the base stations in the embodiments shown in Figures 5 to 14A and 14B.

[0346] Those skilled in the art will appreciate that the embodiments of the present application may be provided as a method, a system, or a computer program product. Therefore, the present application may take the form of a hardware-only embodiment, a software-only embodiment, or an embodiment that combines software and hardware. In addition, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROM, optical memory, etc.) that contain computer-usable program code.

[0347] The present application will be described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present application. It is worth noting that computer program instructions can be used to implement each process and / or each block in the flowcharts and / or block diagrams, and combinations of processes and / or blocks in the flowcharts and / or block diagrams. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or a processor of another programmable data processing device to create a machine, such that the instructions, executed by a processor of a computer or another programmable data processing device, create an apparatus for implementing the specific functions in one or more processes in the flowcharts and / or one or more blocks in the block diagrams.

[0348] These computer program instructions may be stored in a computer-readable memory that can instruct a computer or another programmable data processing device to act in a specific manner, such that the instructions stored in the computer-readable memory can create an artifact that includes an instruction apparatus that implements a particular function in one or more processes of the flowcharts and / or in one or more blocks of the block diagrams.

[0349] These computer program instructions may be loaded into a computer or other programmable data processing device such that a sequence of operations and steps are performed on the computer or other programmable device to generate a computer-implemented process. Thus, the instructions that execute on the computer or other programmable device provide steps for implementing particular functions in one or more processes of the flowcharts and / or in one or more blocks of the block diagrams.

[0350] It is obvious that those skilled in the art can make various modifications and variations to the present application without departing from the scope of the present application. The present application is intended to cover these modifications and variations of the present application and their equivalent techniques as long as they fall within the scope of protection defined by the claims of the present application. [Other possible items] [Item 1] receiving, by a second base station, a handover request message or a configuration update message from a first base station, wherein the handover request message or the configuration update message carries a user plane Internet Protocol IP address of the first base station; and configuring, by the second base station, an ACL based on the user plane IP address; The access control list (ACL) configuration method includes: [Item 2] After the step of configuring, by the second base station, an ACL based on the user plane IP address, the method further comprises: receiving, by the second base station, a packet from the first base station; determining, by the second base station, whether a source IP address of the packet is within the ACL; and processing the packet by the second base station if the source IP address of the packet is within the ACL; or discarding the packet by the second base station if the source IP address of the packet is not within the ACL. The method of item 1, comprising: [Item 3] The step of receiving, by the second base station, a handover request message from the first base station includes: receiving, by the second base station, the handover request message from the first base station via a core network element; 3. The method according to item 1 or 2, comprising: [Item 4] generating, by a first base station, a handover request message or a configuration update message, wherein the handover request message or the configuration update message carries a user plane IP address of the first base station; and sending, by the first base station, the handover request message or the configuration update message to a second base station; The ACL configuration method includes: [Item 5] The step of transmitting the handover request message by the first base station to a second base station comprises: sending, by the first base station, the handover request message to the second base station via a core network element; Item 5. The method according to item 4, comprising: [Item 6] After the step of sending, by the first base station, the handover request message or the configuration update message to a second base station, the method further comprises: receiving data from a core network by the first base station; or receiving data from a terminal device by the first base station; and generating, by the first base station, a packet based on the data and transmitting the packet to the second base station, wherein the packet carries a source IP address, the source IP address being the user plane IP address of the first base station; 6. The method according to item 4 or 5, comprising: [Item 7] 6. The method according to claim 4 or 5, wherein the packet is transmitted through an interface between the first base station and the second base station. [Item 8] receiving, by the target secondary base station, a secondary station addition request message from the master base station, wherein the secondary station addition request message carries a user plane IP address of the source secondary base station; and configuring an ACL based on the user plane IP address by the target secondary base station; The ACL configuration method includes: [Item 9] After the step of configuring, by the target secondary base station, an ACL based on the user plane IP address, the method further comprises: receiving, by the target secondary base station, a packet from the source secondary base station; determining, by the target secondary base station, whether the source IP address of the packet is within the ACL; and processing the packet by the target secondary base station if the source IP address of the packet is within the ACL; or discarding the packet by the target secondary base station if the source IP address of the packet is not within the ACL. Item 9. The method of item 8, comprising: [Item 10] 10. The method according to item 8 or 9, wherein the master base station is a target master base station, the source secondary base station corresponds to a source master base station, and the target secondary base station corresponds to the target master base station. [Item 11] 10. The method of claim 8 or 9, wherein the target secondary base station and the source secondary base station correspond to the master base station. [Item 12] generating a secondary station addition request message by the master base station, wherein the secondary station addition request message carries a user plane IP address of the source secondary base station; and transmitting the secondary station addition request message to a target secondary base station by the master base station; The ACL configuration method includes: [Item 13] the master base station is a target master base station, The source secondary base station corresponds to a source master base station, and the target secondary base station corresponds to a target master base station; Prior to the step of generating a secondary station addition request message by the master base station, the method further comprises: receiving, by the target master base station, a handover request message from the source master base station, the handover request message carrying the user plane IP address of the source secondary base station; Item 13. The method according to item 12. [Item 14] the handover request message further carries a user plane IP address of the source master base station; The method further comprises: configuring an ACL by the target master base station based on the user plane IP address of the source master base station; Item 14. The method according to item 13. [Item 15] Item 13. The method of item 12, wherein the target secondary base station and the source secondary base station correspond to the master base station. [Item 16] an ACL configuration device, the device being located within a second base station; a transceiver unit configured to receive a handover request message or a configuration update message from a first base station, wherein the handover request message or the configuration update message carries a user plane IP address of the first base station; and a processing unit configured to configure an ACL based on the user plane IP address; An apparatus comprising: [Item 17] the transceiver unit is further configured to receive packets from the first base station after the processing unit configures the ACL based on the user plane IP address; The processing unit is further configured to determine whether a source IP address of the packet is within the ACL, and if the source IP address of the packet is within the ACL, the processing unit processes the packet; or if the source IP address of the packet is not within the ACL, the processing unit discards the packet. Item 17. The device according to item 16. [Item 18] Item 18. The apparatus according to item 16 or 17, wherein, when receiving the handover request message from a first base station, the transceiver unit is specifically configured to receive the handover request message from the first base station via a core network element. [Item 19] an ACL configuration device, the device being located within a first base station; a processing unit configured to generate a handover request message or a configuration update message, wherein the handover request message or the configuration update message carries a user plane IP address of the first base station; and a transceiver unit configured to transmit the handover request message or the configuration update message to a second base station. An apparatus comprising: [Item 20] 20. The apparatus of claim 19, wherein the transceiver unit is specifically configured to transmit the handover request message to the second base station via a core network element. [Item 21] the transceiver unit is further configured to receive data from a core network or receive data from a terminal device after sending the handover request message or the configuration update message to the second base station; the processing unit is further configured to generate a packet based on the data; The transceiver unit is further configured to transmit the packet to the second base station, the packet carrying a source IP address, the source IP address being the user plane IP address of the first base station. 21. The device according to item 19 or 20. [Item 22] 21. The apparatus according to claim 19 or 20, wherein the packet is transmitted over an interface between the first base station and the second base station. [Item 23] an ACL configuration device, the device being located within a target secondary base station; a transceiver unit configured to receive a secondary station addition request message from a master base station, wherein the secondary station addition request message carries a user plane IP address of a source secondary base station; and a processing unit configured to configure an ACL based on the user plane IP address; An apparatus comprising: [Item 24] The transceiver unit is further configured to receive packets from the source secondary base station after the processing unit configures the ACL based on the user plane IP address; The processing unit is further configured to determine whether a source IP address of the packet is within the ACL, and if the source IP address of the packet is within the ACL, the processing unit processes the packet; or if the source IP address of the packet is not within the ACL, the processing unit discards the packet. Item 24. The device according to item 23. [Item 25] 25. The apparatus of item 23 or 24, wherein the master base station is a target master base station, the source secondary base station corresponds to a source master base station, and the target secondary base station corresponds to the target master base station. [Item 26] 25. The apparatus of claim 23 or 24, wherein the target secondary base station and the source secondary base station correspond to the master base station. [Item 27] An ACL configuration device, the device being located in a master base station; a processing unit configured to generate a secondary station addition request message, wherein the secondary station addition request message carries a user plane IP address of the source secondary base station; and a transceiver unit configured to transmit the secondary station addition request message to a target secondary base station. An apparatus comprising: [Item 28] the master base station is a target master base station; The source secondary base station corresponds to the source master base station, and the target secondary base station corresponds to the target master base station; The transceiver unit is further configured to receive a handover request message from the source master base station before the processing unit generates the secondary station addition request message, the handover request message carrying the user plane IP address of the source secondary base station. Item 28. The device according to item 27. [Item 29] the handover request message further carries a user plane IP address of the source master base station; The processing unit is further configured to configure an ACL based on the user plane IP address of the source master base station. Item 29. The device according to item 28. [Item 30] 28. The apparatus of claim 27, wherein the target secondary base station and the source secondary base station correspond to the master base station. [Item 31] 16. A communications device comprising a processor and a memory, wherein the memory is configured to store computer-executable instructions, and wherein the processor is configured to execute the computer-executable instructions stored in the memory, thereby causing the communications device to perform the method of any one of items 1 to 3, 4 to 7, 8 to 11 or 12 to 15. [Item 32] 16. A communications device comprising a processor and an interface circuit, the interface circuit being configured to receive code instructions and transmit the code instructions to the processor, the processor executing the code instructions to perform the method of any one of items 1 to 3, 4 to 7, 8 to 11 or 12 to 15. [Item 33] 16. A computer-readable storage medium configured to store instructions that, when executed, implement the method of any one of items 1 to 3, 4 to 7, 8 to 11, or 12 to 15. [Item 34] 16. A chip coupled to a memory and configured to read and execute program instructions stored in the memory to implement the method of any one of items 1 to 3, 4 to 7, 8 to 11 or 12 to 15. [Item 35] 16. A computer program product comprising instructions, the computer program product storing the instructions, which when executed on a computer, enable the computer to perform the method of any one of items 1 to 3, 4 to 7, 8 to 11 or 12 to 15. [Item 36] A communication system comprising a first base station and a second base station, wherein the second base station is configured to perform the method according to any one of items 1 to 3, and the first base station is configured to perform the method according to any one of items 4 to 7. [Item 37] A communication system comprising a target secondary base station and a master base station, the target secondary base station being configured to perform the method described in any one of items 8 to 11, and the master base station being configured to perform the method described in any one of items 12 to 15.

Claims

1. receiving, by a second base station, a handover request message or a configuration update message from a first base station, wherein the handover request message or the configuration update message carries a user plane Internet Protocol (IP) address of the first base station; and configuring, by the second base station, an access control list (ACL) based on the user plane IP address; An ACL configuration method comprising:

2. The step of receiving, by the second base station, a handover request message from the first base station includes: receiving, by the second base station, the handover request message from the first base station via a core network element; The method of claim 1 , comprising:

3. The step of receiving, by the second base station, a handover request message from the first base station includes: receiving, by the second base station, the handover request message directly from the first base station based on an interface between the second base station and the first base station; The method of claim 1 , comprising:

4. An ACL configuration method, comprising: generating, by a first base station, a handover request message or a configuration update message, wherein the handover request message or the configuration update message carries a user plane IP address of the first base station; and sending, by the first base station, the handover request message or the configuration update message to a second base station; Equipped with The step of transmitting the handover request message by the first base station to a second base station comprises: sending, by the first base station, the handover request message to the second base station via a core network element; and After the step of sending the handover request message or the configuration update message to the second base station by the first base station, the ACL configuration method further comprises: receiving data from a core network by the first base station; or receiving data from a terminal device by the first base station; and generating, by the first base station, a packet based on the data and transmitting the packet to the second base station, wherein the packet carries a source IP address, the source IP address being the user plane IP address of the first base station; An ACL configuration method comprising:

5. receiving, by the target secondary base station, a secondary station addition request message from the master base station, wherein the secondary station addition request message carries a user plane IP address of the source secondary base station; and configuring an ACL based on the user plane IP address by the target secondary base station; An ACL configuration method comprising:

6. generating a secondary station addition request message by the master base station, wherein the secondary station addition request message carries a user plane IP address of the source secondary base station; and transmitting the secondary station addition request message to a target secondary base station by the master base station; An ACL configuration method comprising:

7. an ACL configuration device, the ACL configuration device being located within a second base station; a transceiver unit configured to receive a handover request message or a configuration update message from a first base station, wherein the handover request message or the configuration update message carries a user plane IP address of the first base station; and a processing unit configured to configure an ACL based on the user plane IP address; An ACL configuration device comprising:

8. 8. The ACL configuration device according to claim 7, wherein, when receiving the handover request message from a first base station, the transceiver unit is specifically configured to receive the handover request message from the first base station via a core network element.

9. 8. The ACL configuration device according to claim 7, wherein when receiving the handover request message from a first base station, the transceiver unit is specifically configured to receive the handover request message directly from the first base station based on an interface between the second base station and the first base station.

10. an ACL configuration device, the ACL configuration device being located within a first base station; a processing unit configured to generate a handover request message or a configuration update message, wherein the handover request message or the configuration update message carries a user plane IP address of the first base station; and a transceiver unit configured to transmit the handover request message or the configuration update message to a second base station. Equipped with the transceiver unit is particularly configured to transmit the handover request message to the second base station via a core network element; the transceiver unit is further configured to receive data from a core network or receive data from a terminal device after sending the handover request message or the configuration update message to the second base station; the processing unit is further configured to generate a packet based on the data; the transceiver unit is further configured to transmit the packet to the second base station, the packet carrying a source IP address, the source IP address being the user plane IP address of the first base station. ACL configuration device.

11. an ACL configuration device, the ACL configuration device being located in a target secondary base station; a transceiver unit configured to receive a secondary station addition request message from a master base station, wherein the secondary station addition request message carries a user plane IP address of a source secondary base station; and a processing unit configured to configure an ACL based on the user plane IP address; An ACL configuration device comprising:

12. An ACL configuration device, the ACL configuration device being located in a master base station; a processing unit configured to generate a secondary station addition request message, wherein the secondary station addition request message carries a user plane IP address of the source secondary base station; and a transceiver unit configured to transmit the secondary station addition request message to a target secondary base station. An ACL configuration device comprising:

13. A computer program product for causing a computer to execute the ACL configuration method according to any one of claims 1 to 3.

14. A computer program for causing a computer to execute the ACL configuration method according to claim 4.

15. A computer program for causing a computer to execute the ACL configuration method according to claim 5.

16. A computer program for causing a computer to execute the ACL configuration method according to claim 6.

17. A communication system comprising a first base station and a second base station, wherein the second base station is configured to perform the ACL configuration method set forth in claim 1, and the first base station is configured to perform the ACL configuration method set forth in claim 4.

18. A communication system comprising a target secondary base station and a master base station, wherein the target secondary base station is configured to perform the ACL configuration method described in claim 5, and the master base station is configured to perform the ACL configuration method described in claim 6.

Images