Communication method and apparatus

Abstract

The application discloses a communication method and device, which can improve the security of a communication system. The communication method comprises the following steps: determining whether a first user plane function (UPF) entity is attacked; and sending abnormal indication information to a first session management function (SMF) entity in the case that the first UPF entity is attacked, wherein the first SMF entity is connected with the first UPF entity, and the abnormal indication information is used for indicating that the first UPF entity is attacked.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a communication method and apparatus. Background Technology

[0002] Edge computing refers to an open platform that integrates network, computing, storage, and application capabilities, located close to the source of objects or data, to provide services at the nearest point in time. Edge computing enables the provision of a differentiated service network from the center to the edge.

[0003] In edge computing scenarios within a park, edge computing platforms (or edge computing servers) and user plane function network elements (such as user plane function (UPF) entities) in mobile communication networks are deployed in a distributed manner within the park. However, the security management capabilities of the data centers within the park are relatively weak and may be compromised, thus posing a risk to the communication system. Summary of the Invention

[0004] This application provides a communication method and apparatus that can improve the security of a communication system.

[0005] In a first aspect, a communication method is provided, comprising: determining whether a first user plane function (UPF) entity has been attacked; and, if the first UPF entity has been attacked, sending an anomaly indication message to a first session management function (SMF) entity, wherein the anomaly indication message is used to indicate that the first UPF entity has been attacked, and the first SMF entity is connected to the first UPF entity.

[0006] In the event that the first UPF entity is attacked, an anomaly indication message can be sent to the first SMF entity connected to the first UPF entity to indicate that the first UPF entity has been attacked. In this way, the first SMF entity can perform session reconstruction or user plane path adjustment for the sessions associated with the first UPF entity, thereby improving the security of the communication system.

[0007] In conjunction with the first aspect, in some possible implementations, the method further includes: obtaining connection information, the connection information being used to indicate at least one UPF entity connected to each SMF entity in at least one SMF entity, the at least one SMF entity including the first SMF entity.

[0008] The connection information is obtained, and the first SMF entity connected to the first UPF entity is determined based on the connection information, making the determination of the first SMF entity simpler.

[0009] In conjunction with the first aspect, in some possible implementations, determining whether the first user plane function UPF entity has been attacked includes: determining whether the first interface of the first UPF entity is abnormal, and if the first interface is abnormal, the first UPF entity is attacked.

[0010] In the event of an interface anomaly in the first UPF entity, it can be determined that the first UPF entity has been attacked, making the determination of whether the first UPF entity has been attacked easier.

[0011] In conjunction with the first aspect, in some possible implementations, the connection information may also include the identifier of each interface in at least one interface of the first UPF entity, wherein at least one interface of the first UPF entity includes the first interface.

[0012] If the first UPF entity is determined to be under attack based on the abnormality of its interface, the connection information includes the identifier of each interface in the first UPF entity, so that the first UPF entity to which the abnormal interface belongs can be determined based on the identifier of the abnormal interface.

[0013] In conjunction with the first aspect, in some possible implementations, obtaining connection information includes: receiving connection indication information sent by the first SMF entity, the connection indication information being used to indicate at least one of the UPF entities to which the first SMF entity is connected.

[0014] Connection information can be determined based on the connection indication information sent by each SMF entity, making the acquisition of connection information much simpler.

[0015] In conjunction with the first aspect, in some possible implementations, the connection indication information includes the identifier of the second interface of the first SMF entity; sending the exception indication information to the session management function SMF entity includes: sending the exception indication information according to the identifier of the second interface.

[0016] The second interface of the first SMF entity may be an interface used by the first SMF entity to communicate with the apparatus performing the communication method of the first aspect. Thus, the apparatus performing the communication method of the first aspect can address according to the identifier of the second interface of the first SMF entity and send an exception indication message to the address of the addressing result, so that the exception indication message is sent to the first SMF entity.

[0017] In conjunction with the first aspect, in some possible implementations, the connection indication information further includes the identifier of the fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect with the first SMF entity, and the exception indication information including the identifier of the fourth interface.

[0018] The error indication information includes the identifier of the fourth interface used by the first UPF entity to connect with the first SMF entity, facilitating subsequent processing by the first SMF entity. For example, the first SMF entity can disconnect from the first UPF entity based on the identifier of the fourth interface in the error indication information.

[0019] In conjunction with the first aspect, in some possible implementations, the connection information includes an identifier of a third interface of the first SMF entity, the third interface being used for connection between the first SMF entity and the first UPF entity. The method further includes: in the event of an anomaly in the first UPF entity, sending a first request message to a Network Storage Function (NRF) entity, the first request message including the identifier of the third interface; receiving a first response message from the NRF entity, the first response message including the identifier of a second interface of the first SMF entity; and sending an anomaly indication message to the first Session Management Function (SMF) entity, including sending the anomaly indication message according to the identifier of the second interface.

[0020] In the event of an anomaly in the first UPF entity, after identifying the first SMF entity, the identifier of the second interface of the first SMF entity can be requested from the NRF entity based on the identifier of the third interface of the first SMF entity. Then, an anomaly indication message is sent to the first SMF entity according to the identifier of the second interface.

[0021] In conjunction with the first aspect, in some possible implementations, the connection information is determined based on the interaction information between the at least one UPF entity and the at least one SMF entity, wherein the first interaction information between the first UPF entity and the first SMF entity includes the identifier of the third interface and the identifier of each of the at least one interface of the first UPF entity.

[0022] If the first interface of the first UPF entity is determined to be abnormal, the identifier of the third interface of the first SMF can be determined based on the connection information and the identifier of the first interface. Therefore, the identifier of the second interface of the first SMF can be requested from the NRF entity.

[0023] In conjunction with the first aspect, in some possible implementations, at least one interface of the first UPF entity includes a fourth interface, the fourth interface being used for the first UPF entity to connect to the first SMF entity, and the exception indication information including an identifier of the fourth interface.

[0024] The error indication information includes the identifier of the fourth interface used by the first UPF entity to connect with the first SMF entity, which facilitates subsequent processing by the first SMF entity.

[0025] In conjunction with the first aspect, in some possible implementations, the method further includes: in the event of an anomaly in the first UPF entity, sending a second request message to a unified database UDR entity, the second request message including the identifier of the first UPF entity; and receiving a second response message sent by the UDR entity, the second response message including the identifier of the first SMF entity.

[0026] By sending a request message to the Unified Database UDR entity, the identifier of the first SMF entity connected to the first UPF entity to which the abnormal interface belongs is obtained, and then the abnormal indication information is sent to the first SMF entity, without the need to store the connection relationship between the UPF entity and the SMF entity.

[0027] In conjunction with the first aspect, in some possible implementations, determining whether the first user plane function UPF entity has been attacked includes: determining whether the first interface of the first UPF entity is abnormal; if the first interface is abnormal, the first UPF entity is attacked; the identifier of the first UPF entity includes the identifier of the abnormal first interface in the first UPF entity.

[0028] In the event of an interface anomaly in the first UPF entity, it can be determined that the first UPF entity has been attacked, making the determination of whether the first UPF entity has been attacked easier.

[0029] If the first interface of the first UPF entity is determined to be abnormal, the first request message sent to the UDR entity uses the identifier of the first interface as the identifier of the first UPF entity. There is no need to determine the UPF entity to which the first interface belongs; the UDR entity can determine the first SMF entity connected to the first UPF entity based on the identifier of the first interface. This simplifies the method of determining the first SMF entity.

[0030] In conjunction with the first aspect, in some possible implementations, the identifier of the first SMF entity includes the identifier of the second interface of the first SMF entity, and sending the exception indication information to the first session management function SMF entity includes: sending the exception indication information according to the identifier of the second interface.

[0031] The UDR entity can determine the second interface of the first SMF entity connected to the first UPF entity based on the identifier of the first interface in the first UPF entity. The second interface of the first SMF entity may be an interface used by the first SMF entity to communicate with the apparatus performing the communication method of the first aspect. Therefore, the apparatus performing the communication method of the first aspect can perform addressing according to the identifier of the second interface of the first SMF entity and send an exception indication message to the address of the addressing result, so that the exception indication message is sent to the first SMF entity.

[0032] In conjunction with the first aspect, in some possible implementations, the second response information also includes the identifier of the fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect with the first SMF entity, and the exception indication information including the identifier of the fourth interface.

[0033] The error indication information includes the identifier of the fourth interface used by the first UPF entity to connect with the first SMF entity, which facilitates subsequent processing by the first SMF entity.

[0034] In a second aspect, a communication device is provided, comprising: a processing module and a transceiver module; the processing module is configured to determine whether a first user plane function (UPF) entity is under attack; the transceiver module is configured to, in the event that the first UPF entity is under attack, send an anomaly indication message to a first session management function (SMF) entity, the anomaly indication message being used to indicate that the first UPF entity is under attack, and the first SMF entity being connected to the first UPF entity.

[0035] In conjunction with the second aspect, in some possible implementations, the apparatus further includes an acquisition module for acquiring connection information, the connection information being used to indicate at least one UPF entity connected to each of at least one SMF entities, the at least one SMF entity including the first SMF entity.

[0036] In conjunction with the second aspect, in some possible implementations, the processing module is specifically used to determine whether the first interface of the first UPF entity is abnormal, and if the first interface is abnormal, the first UPF entity is attacked.

[0037] In conjunction with the second aspect, in some possible implementations, the connection information further includes the identifier of each interface in at least one interface of the first UPF entity, wherein at least one interface of the first UPF entity includes the first interface.

[0038] In conjunction with the second aspect, in some possible implementations, the acquisition module is specifically used to receive connection indication information sent by the first SMF entity, the connection indication information being used to indicate at least one of the UPF entities to which the first SMF entity is connected.

[0039] In conjunction with the second aspect, in some possible implementations, the connection indication information includes the identifier of the second interface of the first SMF entity; the transceiver module is specifically used to send the exception indication information according to the identifier of the second interface.

[0040] In conjunction with the second aspect, in some possible implementations, the connection indication information further includes the identifier of the fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect with the first SMF entity, and the exception indication information including the identifier of the fourth interface.

[0041] In conjunction with the second aspect, in some possible implementations, the connection information includes the identifier of a third interface of the first SMF entity, the third interface being used for connection between the first SMF entity and the first UPF entity. The transceiver module is further configured to, in the event of an anomaly in the first UPF entity, send a first request message to a Network Storage Function (NRF) entity, the first request message including the identifier of the third interface; the transceiver module is further configured to receive a first response message from the NRF entity, the first response message including the identifier of a second interface of the first SMF entity; specifically, the transceiver module is configured to send the anomaly indication information according to the identifier of the second interface.

[0042] In conjunction with the second aspect, in some possible implementations, the connection information is determined based on the interaction information between the at least one UPF entity and the at least one SMF entity, wherein the first interaction information between the first UPF entity and the first SMF entity includes the identifier of the third interface and the identifier of each of the at least one interface of the first UPF entity.

[0043] In conjunction with the second aspect, in some possible implementations, the transceiver module is further configured to, in the event of an anomaly in the first UPF entity, send a second request message to the unified database UDR entity, the second request message including the identifier of the first UPF entity; the transceiver module is further configured to, receive a second response message sent by the UDR entity, the second response message including the identifier of the first SMF entity.

[0044] In conjunction with the second aspect, in some possible implementations, the processing module is specifically used to determine whether the first interface of the first UPF entity is abnormal, and if the first interface is abnormal, the first UPF entity is attacked; the identifier of the first UPF entity includes the identifier of the abnormal first interface in the first UPF entity.

[0045] In conjunction with the second aspect, in some possible implementations, the identifier of the first SMF entity includes the identifier of the second interface of the first SMF entity, and the transceiver module is specifically used to send the exception indication information according to the identifier of the second interface.

[0046] Thirdly, a communication method is provided for use with a Session Management Function (SMF) entity, the method comprising: receiving an anomaly indication information sent by a Security Policy Control Function (SPCF) entity, the anomaly indication information being used to indicate that a first UPF entity has been attacked; and disconnecting the connection with the first UPF entity.

[0047] The Session Management Function (SMF) entity disconnects from the first UPF entity upon receiving an anomaly indication message from the SPCF entity, thus providing security for the communication system.

[0048] In conjunction with the third aspect, in some possible implementations, the method further includes: sending interface indication information to a Network Storage Function (NRF) entity, the interface indication information including an identifier of a second interface of the SMF entity and an identifier of a third interface of the SMF entity, the third interface being used for connection between the SMF entity and the first UPF entity; the anomaly indication information is sent by the SPCF entity based on a first response information sent by the NRF entity, the first response information including the identifier of the third interface, the first response information being sent by the NRF entity based on a first request information, the first request information including the identifier of the second interface, the first request information being sent by the SPCF entity upon determining that the first UPF entity has been attacked.

[0049] The SMF entity registers the identifiers of its second and third interfaces with the NRF entity by sending interface indication information. Therefore, if the first UPF entity is found to be faulty, the SPCF entity, after identifying the SMF entity connected to the first UPF entity, can request the identifier of the SMF entity's second interface from the NRF entity based on the identifier of the first SMF entity's third interface. Subsequently, the SPCF entity can send fault indication information to the SMF entity according to the identifier of the second interface.

[0050] In conjunction with the third aspect, in some possible implementations, the method further includes: sending first connection indication information to the SPCF entity, the first connection indication information being used to indicate at least one UPF entity to which the SMF entity is connected, the at least one UPF entity including the first UPF entity.

[0051] Therefore, the SPCF entity can determine the SMF entity to which the first UPF entity being attacked is connected based on the first connection indication information.

[0052] In conjunction with the third aspect, in some possible implementations, the first connection indication information includes the identifier of the second interface of the first SMF entity, and the exception indication information is sent by the SPCF entity according to the identifier of the second interface.

[0053] The second interface of the SMF entity can be the interface used by the SMF entity to communicate with the SPCF entity. Thus, the SPCF entity can address according to the identifier of the second interface and send an exception indication message to the address obtained from the addressing, thereby sending the exception indication message to the SMF entity.

[0054] In conjunction with the third aspect, in some possible implementations, the method further includes: sending a second connection indication message to a unified database UDR entity, the second connection indication message indicating that the SMF entity is connected to at least one UPF entity, the at least one UPF entity including the first UPF entity; the anomaly indication message is sent by the SPCF entity according to second response information, the second response information including the identifier of the SMF entity; the second response information is sent by the UDR entity according to second request information, the second request information including the identifier of the first UPF entity; the second request information is sent by the SPCF entity when it is determined that the first UPF entity has been attacked.

[0055] The SMF entity registers at least one UPF entity with the UDR entity by sending a second connection indication message to the UDR entity. The second connection indication message may include the identifier of the SMF entity and the identifier of each UPF entity within the at least one UPF entity.

[0056] Therefore, the SPCF entity can send a request message to the Unified Database UDR entity to obtain the identifier of the SMF entity connected to the first UPF entity to which the abnormal interface belongs, and send an abnormal indication message to the SMF entity according to the identifier of the SMF entity.

[0057] In conjunction with the third aspect, in some possible implementations, the second connection indication information includes the identifier of the SMF entity, the identifier of the SMF entity includes the identifier of the second interface of the SMF entity, and the exception indication information is sent by the SPCF entity according to the identifier of the second interface.

[0058] The second connection indication information includes the identifier of the second interface of the SMF entity, so that the UDR entity can determine the second interface of the first SMF entity connected to the first UPF entity based on the identifier of the first interface in the first UPF entity. The second interface of the SMF entity may be the interface used by the first SMF entity to communicate with the apparatus performing the communication method of the first aspect. Therefore, the SPCF entity can perform addressing according to the identifier of the second interface of the SMF entity and send exception indication information to the address of the addressing result, so that the exception indication information is sent to the SMF entity.

[0059] In conjunction with the third aspect, in some possible implementations, the second connection indication information includes the identifier of the fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect with the SMF entity, the second response information also includes the identifier of the fourth interface, and the exception indication information includes the identifier of the fourth interface.

[0060] The second connection indication information includes the identifier of the fourth interface used by the first UPF entity to connect with the first SMF entity, so that the exception indication information can be sent to the identifier of the fourth interface, which facilitates the first SMF entity to perform subsequent processing.

[0061] Fourthly, a communication method is provided, comprising: receiving interface indication information sent by a first SMF entity, the interface indication information including an identifier of a second interface of the first SMF entity and an identifier of a third interface of the first SMF entity, the third interface being used for connection between the first SMF entity and a first UPF entity; receiving first request information sent by an SPCF entity, the first request information including the identifier of the second interface, the first request information being sent by the SPCF entity when it is determined that the first UPF entity is under attack; and sending first response information to the SPCF entity, the first response information including the identifier of the third interface, the identifier of the third interface being used by the first SMF entity to send an anomaly indication information to the first SMF entity, the anomaly indication information being used to indicate that the first UPF entity is under attack.

[0062] Fifthly, a communication method is provided, comprising: receiving second connection indication information sent by a first SMF entity, the second connection indication information being used to indicate that the first SMF entity is connected to at least one UPF entity, the at least one UPF entity including the first UPF entity; receiving second request information sent by an SPCF entity, the second request information being sent by the SPCF entity when it determines that the first UPF entity has been attacked, the second request information including an identifier of the first UPF entity; and sending second response information to the SPCF entity, the second response information including an identifier of the first SMF entity, the identifier of the first SMF entity being used by the first SMF entity to send an anomaly indication information to the first SMF entity, the anomaly indication information being used to indicate that the first UPF entity has been attacked.

[0063] In conjunction with the fifth aspect, in some possible implementations, the second connection indication information includes the identifier of the SMF entity, the identifier of the SMF entity includes the identifier of the second interface of the SMF entity, and the exception indication information is sent by the SPCF entity according to the identifier of the second interface.

[0064] In conjunction with the fifth aspect, in some possible implementations, the second connection indication information includes the identifier of the fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect with the SMF entity, the second response information also includes the identifier of the fourth interface, and the exception indication information includes the identifier of the fourth interface.

[0065] A sixth aspect provides a communication apparatus comprising modules for performing the methods in any one of the fourth to sixth aspects.

[0066] A seventh aspect provides a communication device, including a processor and a communication interface, the communication interface being used for the communication device to interact with other communication devices, and when program instructions are executed in the at least one processor, causing the communication device to perform a method in any one of the first, fourth to sixth aspects.

[0067] Eighthly, a computer-readable medium is provided that stores program code for execution by a device, the program code including methods for performing any one of the first, fourth to sixth aspects.

[0068] Ninth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method in any one of the implementations of the first, fourth to sixth aspects described above.

[0069] In a tenth aspect, a chip is provided, the chip including a processor and a data interface, wherein the processor reads instructions stored in a memory through the data interface and executes the method in any one of the implementations of the first, fourth to sixth aspects described above.

[0070] Optionally, as one implementation, the chip may further include a memory storing instructions, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to perform the method in any one of the first or fourth to sixth aspects of the implementation.

[0071] The aforementioned chip can be a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC).

[0072] It should be understood that, in this application, the method of the first aspect can specifically refer to the first aspect and the method in any of the various implementations of the first aspect.

[0073] The technical effects that can be achieved by any possible implementation of any of the second to tenth aspects mentioned above can be described with reference to the technical effects that can be achieved by any possible implementation of any of the first aspects mentioned above, and the repetitions will not be discussed. Attached Figure Description

[0074] Figure 1 This is a schematic diagram of a possible network architecture according to an embodiment of this application.

[0075] Figure 2 This is a schematic diagram of another possible network architecture according to an embodiment of this application.

[0076] Figure 3 This is a schematic flowchart of a communication method provided in an embodiment of this application.

[0077] Figure 4 This is a schematic flowchart illustrating another communication method provided in an embodiment of this application.

[0078] Figure 5 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application.

[0079] Figure 6 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application.

[0080] Figure 7 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application.

[0081] Figure 8 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application.

[0082] Figure 9 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application.

[0083] Figure 10 This is a schematic structural diagram of a communication device provided in an embodiment of this application.

[0084] Figure 11 This is a schematic structural diagram of another communication device provided in the embodiments of this application. Detailed Implementation

[0085] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0086] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, future 5th generation (5G) systems, or new radio (NR), etc.

[0087] To facilitate understanding of the embodiments of this application, firstly, in conjunction with Figure 1 and Figure 2 The application scenarios of the embodiments of this application are described in detail.

[0088] Figure 1 This is a schematic diagram of a network architecture applicable to the communication method provided in the embodiments of this application. Figure 1 The network architecture 100 shown may specifically include one or more of the following network elements:

[0089] 1. User Equipment (UE): This can be referred to as terminal equipment, terminal, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent, or user device. UE can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal equipment in future 5G networks, or terminal equipment in future evolved public land mobile networks (PLMNs), etc. It can also be an end device, logical entity, smart device, such as a mobile phone, smart terminal, or other terminal equipment; or a server, gateway, base station, controller, or other communication equipment; or an Internet of Things (IoT) device, such as a sensor, electricity meter, water meter, etc. UE can also be a wired device, such as a computer, laptop, etc. This application's embodiments do not limit this.

[0090] 2. Access Network (AN): Provides network access functionality for authorized users in a specific area and can use transmission tunnels of different quality depending on the user's level and service requirements. Access networks can employ different access technologies. Currently, there are two types of radio access technologies: 3rd Generation Partnership Project (3GPP) access technologies (such as those used in 3G, 4G, or 5G systems) and non-3GPP access technologies. 3GPP access technologies refer to access technologies that conform to 3GPP standards and specifications. Access networks using 3GPP access technologies are called Radio Access Networks (RANs). In 5G systems, access network equipment is called next-generation node base stations (gNBs). Non-3GPP access technologies refer to access technologies that do not conform to 3GPP standards and specifications, such as air interface technologies represented by access points (APs) in Wi-Fi.

[0091] An access network that uses wired communication technology to implement network access functions can be called a wired access network.

[0092] An access network that uses wireless communication technology to implement access network functions can be called a radio access network (RAN). A RAN manages radio resources, provides access services to terminals, and facilitates the forwarding of control signals and user data between terminals and the core network.

[0093] The wireless access network can be, for example, a base station (NodeB), an evolved NodeB (eNB or eNodeB), a base station (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access point (AP) in a WiFi system. It can also be a wireless controller in a cloud radio access network (CRAN) scenario. Alternatively, the access network device can be a relay station, access point, vehicle-mounted equipment, wearable devices, or network equipment in a future 5G network or a future evolved PLMN network. The embodiments of this application do not limit the specific technology or device form used in the wireless access network device.

[0094] 3. Access and Mobility Management Function (AMF) Entity: Primarily used for mobility management and access management, such as user location updates, user registration with the network, and user handover; it can also be used to implement other functions of the Mobility Management Entity (MME) besides session management, such as lawful interception or access authorization (or authentication). In the embodiments of this application, it can be used to implement the functions of the access and mobility management network element.

[0095] 4. Session Management Function (SMF) Entity: Primarily used for session management (such as session establishment, modification, and release), UE Internet Protocol (IP) address allocation and management, selection of manageable user plane functions, policy control, or terminal points for charging function interfaces, and downlink data notification. In the embodiments of this application, it can be used to implement the functions of the session management network element.

[0096] 5. User plane function (UPF) entity: i.e., data plane gateway. It can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, etc. User data can access the data network (DN) through this network element. In the embodiments of this application, it can be used to implement the functions of a user plane gateway.

[0097] 6. Data Network (DN): A network used to provide data transmission. Examples include carrier service networks, the Internet, third-party service networks, and IP Multimedia Service (IMS) networks. In 5G networks, DNs are identified by their data network name (DNN).

[0098] 7. Authentication Server Function (AUSF) entity: mainly used for user authentication, i.e., authorizing the UE to access the 5G network.

[0099] 8. Network Exposure Function (NEF) entity: Used to securely expose services and capabilities provided by 5G network functions to the outside world.

[0100] 9. Network function (NF) repository function (NRF) entity: used to store network function entities and their description information, as well as support service discovery, network element entity discovery and registration, etc.

[0101] 10. Policy control function (PCF) entity: A unified policy framework used to guide network behavior, providing policy rule information to control plane functional network elements (such as AMF, SMF, etc.).

[0102] 11. Unified Data Management (UDM) entity: Used to handle user identification, access authentication, registration, or mobility management, etc.

[0103] 12. Application function (AF) entity: Used for data routing affected by applications, accessing network open function elements, or interacting with the policy framework for policy control, etc.

[0104] 13. Unified Data Repository (UDR) Entity: Provides storage capabilities for contracted data, policy data, and capability-related data.

[0105] In this network architecture, Nausf is the service-based interface presented by AUSF, Namf is the service-based interface presented by AMF, Nsmf is the service-based interface presented by SMF, Nnef is the service-based interface presented by NEF, Nnrf is the service-based interface presented by NRF, Npcf is the service-based interface presented by PCF, Nudm is the service-based interface presented by UDM, and Nudr is the service-based interface presented by UDR. The N1 interface is the reference point between the terminal and the AMF entity; the N2 interface is the reference point between the AN and AMF entities, used for sending non-access stratum (NAS) messages, etc.; the N3 interface is the reference point between the (R)AN and the UPF entity, used for transmitting user plane data, etc.; the N4 interface is the reference point between the SMF entity and the UPF entity, used for transmitting information such as tunnel identification information for N3 connections, data buffer indication information, and downlink data notification messages, etc.; the N6 interface is the reference point between the UPF entity and the DN, used for transmitting user plane data, etc.

[0106] Figure 1 The interface names between the various network elements are merely examples; in actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0107] It should be understood that the network architecture described above in the embodiments of this application is merely an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture. The network architecture applicable to the embodiments of this application is not limited to this, and any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0108] Figure 2 This is a schematic diagram of a network architecture applicable to the communication method provided in the embodiments of this application.

[0109] Network architecture 200 is based on point-to-point interfaces. Interface N13 is the reference point between the UDM entity and the AUSF entity; interface N35 is the reference point between the UDM entity and the UDR entity; interface N12 is the reference point between the AUSF entity and the AMF entity; interface N8 is the reference point between the UDM entity and the AMF entity; interface N10 is the reference point between the UDM entity and the SMF entity; interface N36 is the reference point between the UDR entity and the PCF entity; interface N5 is the reference point between the PCF entity and the AF entity; and interface N15 is the reference point between the PCF entity and the AMF entity.

[0110] Figure 1 and Figure 2The AMF, SMF, UPF, UDR, NEF, AUSF, NRF, PCF, and UDM network elements shown can all be understood as network elements in the core network used to implement different functions, such as being combined into network slices as needed. These core network elements can be independent devices or integrated into the same device to implement different functions; this application does not limit this. The device that performs the functions of the core network elements can also be called a core network device or a network device.

[0111] The naming conventions described above are solely for distinguishing different functions and do not imply that these network elements are independent physical devices. This application does not limit the specific form of these network elements; for example, they may be integrated into the same physical device or they may be separate physical devices. Furthermore, the naming conventions described above are only for distinguishing different functions and should not constitute any limitation on this application. This application does not exclude the possibility of using other naming conventions in 5G networks and other future networks. For example, in 6G networks, some or all of the aforementioned network elements may use the terminology from 5G, or they may use other names, etc. This is a unified explanation provided here and will not be repeated below.

[0112] Edge computing provides differentiated service networks from the center to the edge. The migration of content, applications, and computing to the edge drives the development of edge computing. Centralized deployment of the core network cannot meet the needs of new business, and the migration of the network to the edge along with business flows is an industry trend. Edge computing, combined with smart campuses, enables rapid deployment, achieving local business closed loops, and saving transmission costs for campus users while ensuring a better experience through a more optimized network.

[0113] However, in campus edge computing scenarios, the edge computing platform (or edge computing server) and user plane function network elements (such as UPF) in the mobile communication network are deployed inside the campus. The security management capabilities of the data centers within the campus are relatively weak, posing a risk of breach. Attackers can hijack the UPF (e.g., physically infiltrate the corresponding data center) to attack the user plane and control plane of the mobile communication network, leading to risks to the communication network.

[0114] To address the aforementioned issues, this application provides a communication method.

[0115] Figure 3 This is a schematic flowchart of a communication method provided in an embodiment of this application.

[0116] Method 300 can be performed by a security policy control function (SPCF) entity or other network elements. Method 300 includes steps S310 to S320.

[0117] In S310, determine whether the first UPF entity has been attacked.

[0118] In S320, if the first UPF entity is attacked, an anomaly indication message is sent to the first session management function (SMF) entity. The first SMF entity is connected to the first UPF entity, and the anomaly indication message is used to indicate that the first UPF entity has been attacked.

[0119] In the event that the first UPF entity is attacked, method 300 can send an anomaly indication message to the first SMF entity connected to the first UPF entity to indicate that the first UPF entity has been attacked. This allows the first SMF entity to perform session reconstruction or user plane path adjustment for sessions related to the first UPF entity, thereby improving the security of the communication system.

[0120] In some embodiments, before performing S310, connection information may be obtained, which is used to indicate at least one UPF entity to which each SMF entity in at least one SMF entity is connected, the at least one SMF entity including a first SMF entity.

[0121] In other words, before S320, if it is determined that the first UPF entity has been attacked, the first SMF entity connected to the first UPF entity can be identified based on the connection information, so that an anomaly indication message can be sent to the first SMF entity in S320.

[0122] Specifically, in S310, it can be determined whether the first interface of the first UPF entity is abnormal, and if the first interface is abnormal, the first UPF entity is attacked.

[0123] In other words, by inspecting the interfaces of the first UPF entity, if any of the interfaces of the first UPF entity is abnormal, it can be determined that the first UPF entity has been attacked.

[0124] Optionally, the connection information may also include the identifier of each interface in at least one interface of the first UPF entity, wherein at least one interface of the first UPF entity includes the first interface.

[0125] It should be understood that the first interface can be any interface in the first UPF entity.

[0126] In other words, prior to S310, it is also possible to obtain the identifier of each interface in at least one interface of the first UPF entity. In the event of an anomaly in the first interface of the first UPF entity, it can be determined that the first UPF entity has been attacked based on the identifier of the first interface.

[0127] Connection information can be determined based on connection indication information sent by each SMF entity, or it can be determined based on the interaction information between each UPF entity and the connected SMF entity.

[0128] If the connection information is determined based on the connection indication information sent by each SMF entity, before S310, the connection indication information sent by the first SMF entity can be received. The connection indication information sent by the first SMF entity is used to indicate at least one UPF entity connected to the first SMF entity.

[0129] After receiving the connection indication information sent by each SMF entity, the connection information can be determined based on the connection indication information sent by at least one SMF entity.

[0130] The connection indication information sent by the first SMF entity also includes the identifier of the second interface of the first SMF entity. In S320, the exception indication information can be sent to the first SMF entity according to the identifier of the second interface.

[0131] In other words, the second interface of the first SMF entity can be the interface used by the first SMF entity to communicate with the SPCF entity. Therefore, in S320, the exception indication information can be sent according to the identifier of the second interface of the first SMF entity.

[0132] The connection indication information sent by the first SMF entity may also include the identifier of the fourth interface of the first UPF entity. The fourth interface of the first UPF entity may be, for example, an N4 interface, used for connection between the first UPF entity and the first SMF entity. Error indication information may include the identifier of the fourth interface of the first UPF entity.

[0133] The error indication information includes the identifier of the fourth interface used by the first UPF entity to connect with the first SMF entity, facilitating subsequent processing by the first SMF entity. For example, the first SMF entity can disconnect from the first UPF entity based on the identifier of the fourth interface in the error indication information.

[0134] When the connection information is determined based on the interaction information between each UPF entity and the connected SMF entity, the connection information may include the identifier of the third interface of the first SMF entity, which is used for the connection between the first SMF entity and the first UPF entity.

[0135] In the event of an anomaly in the first UPF entity, a first request message may be sent to the NRF entity before S320. The first request message includes the identifier of the third interface.

[0136] Then, the first response information can be received from the NRF entity. The first response information includes the identifier of the second interface of the first SMF entity.

[0137] In S320, an error indication message can be sent according to the identifier of the second interface.

[0138] The third interface used by the first SMF entity to connect to the first UPF entity can be the N4 interface of the first SMF entity. The second interface of the first SMF entity can be the interface used by the first SMF entity to connect to the SPCF entity, for example, it can be the service interface of the first SMF entity.

[0139] In other words, if the first UPF entity is abnormal, after identifying the first SMF entity, the identifier of the second interface of the first SMF entity can be requested from the NRF entity based on the identifier of the N4 interface of the first SMF entity. Then, an abnormality indication message is sent to the first SMF entity according to the identifier of the second interface.

[0140] Optionally, the connection information may be determined based on the interaction information between the at least one UPF entity and the at least one SMF entity. The first interaction information between the first UPF entity in the at least one UPF entity and the first SMF entity in the at least one SMF entity may include the identifier of the third interface, and may include the identifier of each interface in at least one interface of the first UPF entity.

[0141] Therefore, if it is determined that the first interface of the first UPF entity is abnormal, the identifier of the third interface of the first SMF can be determined based on the connection information and the identifier of the first interface. Thus, the identifier of the second interface of the first SMF can be requested from the NRF entity.

[0142] For example, the security policy enhancement function (SPEF) can acquire information received or sent by at least one UPF entity. The interaction information between the UPF entity and the SMF entity may include the identifiers of each interface in the UPF entity and the identifiers of the interfaces used by the SMF entity to connect to the UPF entity. Based on the interaction information between the UPF entity and the SMF entity, the SPEF entity can send to the SPEF the identifiers of the interfaces used by the SMF entity to connect to the UPF entity, as well as the identifiers of each interface of the UPF entity to which the SMF entity is connected.

[0143] Specifically, SPEF can obtain the first interaction information and send the identifier of the third interface and the identifier of each interface in at least one interface of the first UPF entity to the SPCF entity.

[0144] Therefore, the SPCF entity can determine the connection information based on the information sent by SPEF.

[0145] At least one interface of the first UPF entity includes a fourth interface, which is used for the first UPF entity to connect with the first SMF entity, and the exception indication information includes the identifier of the fourth interface.

[0146] The first interaction information between the first UPF entity and the first SMF entity may include the identifier of the third interface and the identifier of the fourth interface. Therefore, the exception indication information may include the identifier of the fourth interface.

[0147] The fourth interface of the first UPF entity is used for connection between the first UPF entity and the first SMF entity; for example, it could be the N4 interface of the first UPF entity. The identifier of the fourth interface in the exception indication information can be used to indicate the first UPF entity. The exception indication information includes the identifier of the fourth interface used by the first UPF entity to connect with the first SMF entity, facilitating subsequent processing by the first SMF entity. For example, the first SMF entity can disconnect from the first UPF entity based on the identifier of the fourth interface in the exception indication information. That is, when the first SMF entity disconnects from the fourth interface indicated by the identifier of the fourth interface, it disconnects from the first UPF entity.

[0148] In other embodiments, in the event of an anomaly in the first UPF entity, a second request message can be sent to the UDR entity. The second request message includes the identifier of the first UPF entity.

[0149] Then, a second response message can be received from the UDR entity. The second response message includes the identifier of the first SMF entity. After receiving the second response message, the UDR entity can send a second request message. The second response message can be understood as a response to the second request message.

[0150] In S310, it can be determined whether the first interface of the first UPF entity is abnormal. An abnormal first interface of the first UPF entity can be understood as the first UPF entity being attacked.

[0151] The identifier of the first UPF entity includes the identifier of the first interface that is abnormal in the first UPF entity.

[0152] In other words, the second request information may include the identifier of the first interface in the first UPF entity. Based on the identifier of the first interface, the UDR entity can determine the first SMF entity connected to the first UPF entity.

[0153] The identifier of the first SMF entity may include the identifier of the second interface of the first SMF entity. In S320, an exception indication message can be sent according to the identifier of the second interface of the first SMF entity.

[0154] The UDR entity can determine the second interface of the first SMF entity connected to the first UPF entity based on the identifier of the first interface in the first UPF entity. The second interface of the first SMF entity is used for connection between the first SMF entity and the SPCF entity; for example, the second interface of the first SMF entity can be a service interface of the first SMF entity. The second response information sent by the UDR entity may include the identifier of the second interface of the first SMF entity. Therefore, in S320, sending the exception indication information according to the identifier of the second interface of the first SMF entity allows the exception indication information to be sent to the first SMF entity.

[0155] The second response information may also include the identifier of the fourth interface of the first UPF entity. The fourth interface of the first UPF entity is used for the connection between the first UPF entity and the first SMF entity, and the exception indication information includes the identifier of the fourth interface of the first UPF entity.

[0156] The fourth interface of the first UPF entity is used for connection between the first UPF entity and the first SMF entity; for example, it could be the N4 interface of the first UPF entity. The identifier of the fourth interface in the exception indication information can be used to indicate the first UPF entity. The exception indication information includes the identifier of the fourth interface of the first UPF entity, facilitating subsequent processing by the first SMF entity. For example, the first SMF entity can disconnect from the first UPF entity based on the identifier of the fourth interface in the exception indication information. In other words, when the first SMF entity disconnects from the fourth interface indicated by the identifier, it disconnects from the first UPF entity.

[0157] If the first interface that causes the exception in the first UPF entity is not the fourth interface of the first UPF entity, the exception indication information may include the identifier of the fourth interface. If the first interface that causes the exception in the first UPF entity is the fourth interface of the first UPF entity, the exception indication information may or may not include the identifier of the fourth interface.

[0158] Figure 4 This is a schematic flowchart of a communication method provided in an embodiment of this application. Method 400 includes steps S401 to S413.

[0159] In S401, the first SMF entity sends network function registration information to the NRF entity.

[0160] For network architecture 100, network function registration information may include the network function (NF) type of the first SMF entity, the NF instance identifier (ID) of the first SMF entity, the service interface identifier of the first SMF entity, and the identifier of the N4 interface of the first SMF entity.

[0161] For network architecture 200, network function registration information may include network function (NF) type, NF instance identification (ID), the identifier of the N4 interface of the SMF entity, and the identifier of the interface used by the SMF entity to communicate with other network elements in network architecture 200. The identifier of the N4 interface of the SMF entity and the identifiers of other interfaces may be the same or different.

[0162] The NF type of the first SMF entity indicates the type of network element sending the network function registration information, i.e., it indicates that the type of the first SMF entity is SMF. The NF instance ID of the first SMF entity indicates the first SMF entity itself. The service interface identifier of the first SMF entity can be the fully qualified domain name (FQDN) or IP address of the service interface of the first SMF entity, used to indicate the service interface of the first SMF entity. The identifier of the N4 interface of the first SMF entity can be the FQDN or IP address of the N4 interface of the first SMF entity, used to indicate the N4 interface of the first SMF entity.

[0163] Method 400 is illustrated using network architecture 100 as an example.

[0164] In S402, the NRF entity sends a registration response message to the first SMF entity.

[0165] The registration response message indicates that the network function registration was successful.

[0166] In S403, the SPEF entity detects information related to establishing an N4 coupling between the first SMF entity and the first UPF entity.

[0167] The SPEF entity can obtain interaction information between each UPF entity and the SMF entity in at least one UPF entity. The at least one UPF entity includes a first UPF entity. The SMF entity that establishes an N4 coupling with the first UPF entity is the first SMF entity. The first UPF entity can be any one of the at least one UPF entity.

[0168] During the process of establishing a connection between the UPF entity and the SMF entity (which can also be understood as establishing an N4 association), the messages exchanged between the UPF entity and the SMF entity contain the identifiers of the N4 interfaces of the SMF entity and the UPF entity.

[0169] Therefore, the SPEF entity can determine the correspondence information 1 based on the information exchanged between each UPF entity and the SMF entity in at least one UPF entity. In the correspondence information 1, the identifier of the N4 interface of each SMF entity corresponds to the identifier of the N4 interface of at least one UPF entity, and there is an N4 coupling between the UPF entity and the SMF entity, that is, the N4 interface of the UPF entity is connected to the N4 interface of the SMF entity.

[0170] In S404, the SPEF entity sends correspondence information 1 to the SPCF.

[0171] In S405, the SPEF entity detects information related to session establishment and session modification between the first SMF entity and the first UPF entity.

[0172] During the message transmission between the UPF entity and the SMF entity related to session establishment, session modification, etc., the interaction information between the SMF entity and the UPF entity carries the N3 interface identifier and N9 interface identifier of the UPF entity, which are used to configure the N3 interface and N9 interface of the UPF entity.

[0173] The SPEF entity can determine the correspondence information 2 based on the information exchanged between each UPF entity and the SMF entity in at least one UPF entity. The correspondence information 2 is used to represent the correspondence between the identifier of the N4 interface of each UPF entity and the identifiers of the N3 interface and N9 interface of that UPF.

[0174] In S406, the SPEF entity sends the corresponding relationship information 2 to the SPCF.

[0175] In S407, the SPEF entity determines whether the interface of the first UPF entity is abnormal.

[0176] A SPEF entity can inspect each interface of each UPF entity in at least one UPF entity to determine if there are any abnormal interfaces.

[0177] It should be understood that S407 can be performed multiple times. For example, S407 can be performed periodically.

[0178] In the event of an interface failure in the first UPF entity, S408 can be executed. The first UPF entity can be any one of the at least one UPF entities.

[0179] In S408, the SPEF entity sends an exception interface message to the SPCF entity.

[0180] The abnormal interface information includes the identifier of the abnormal interface in the first UPF entity.

[0181] Based on the anomaly indication information, the SPCF entity can determine that the first UPF entity is untrusted, meaning that the first UPF entity has been attacked.

[0182] If the identifier of the abnormal interface in the abnormal interface information is the identifier of the N4 interface of the first UPF entity, the SPCF entity can determine the identifier of the N4 interface of the SMF entity corresponding to the identifier of the abnormal interface in the UPF entity according to the correspondence information 1.

[0183] If the identifier of the abnormal interface in the abnormal interface information is the N3 or N9 interface of the first UPF entity, the SPCF entity can determine the identifier of the N4 interface of the first UPF entity according to the correspondence information 2, and determine the identifier of the N4 interface of the first SMF entity connected to the N4 interface of the first UPF entity according to the correspondence information 1.

[0184] In S409, the SPCF entity sends an interface query message to the NRF entity.

[0185] The interface query information may include the identifier of the N4 interface of the first SMF entity.

[0186] In S410, the NRF entity sends interface response information to the SPCF entity.

[0187] The interface response information includes the identifier of the service interface of the first SMF entity.

[0188] After power-on, each SMF entity can send network function registration information to the NRF entity. Based on the network function registration information sent by each SMF entity, the NRF entity can determine the correspondence between the identifier of the N4 interface and the identifier of the service interface in that SMF entity.

[0189] In S411, the SPCF entity sends an exception indication message according to the identifier of the service interface of the first SMF entity.

[0190] The SPCF entity can address the identifier of the service interface of the first SMF entity and send an exception indication message to the address indicated by the addressing result. Thus, the exception indication message can be sent to the first SMF entity.

[0191] The exception indication information is used to indicate an interface exception of the first UPF entity.

[0192] The first SMF entity can process the business related to the first UPF entity based on the anomaly indication information.

[0193] For example, the first SMF entity can perform S412 and S413.

[0194] In S412, the first SMF entity disconnects the N4 coupling with the N4 interface of the first UPF entity.

[0195] The anomaly indication information may also include the identifier of the N4 interface in the first UPF entity.

[0196] The first SMF entity can disconnect from the abnormal indication information identifier, thereby disconnecting the N4 association with the first UPF entity.

[0197] In S413, the first SMF entity can perform session reconstruction or user plane path adjustment of the session if a session exists with the first UPF entity.

[0198] The first SMF entity can re-establish the session after disconnecting the N4 coupling with the first UPF entity's N4 interface. Alternatively, the first SMF entity can determine whether to re-establish the session based on the role of the first UPF entity in the session after disconnecting the N4 coupling with the first UPF entity's N4 interface. It should be understood that the session can be a protocol data unit (PDU) session.

[0199] If the first SMF entity determines that the first UPF entity is the relay UPF (intermediate UPF, I-UPF) of the session, it can adjust the user plane path of the session, thereby treating other UPF entities other than the first UPF entity as I-UPFs.

[0200] If the first SMF entity determines that the first UPF entity is the PDU session anchor (PSA-UPF) of the session, the session can be reconstructed, thereby using other UPF entities other than the first UPF entity as PSA-UPF.

[0201] In method 400, the NRF entity provides network function registration and query services. The SPEF entity reports the detected correspondence information 1 and correspondence information 2 to the SPCF entity. Correspondence information 1 represents the correspondence between the N4 interfaces of a UPF entity and an SMF entity with N4 coupling, respectively. Correspondence information 2 represents the correspondence between the N4 interface and the N3 and N9 interfaces in the UPF entity. When the SPEF entity detects an interface anomaly in the first UPF entity, the SPCF entity determines the identifier of the N4 interface of the first SMF entity with N4 coupling to the first UPF entity based on correspondence information 1 and correspondence information 2. Using the identifier of the N4 interface of the first SMF entity, the SPCF entity queries the NRF entity to obtain the identifier of the service interface of the first SMF. Then, the SPCF entity can send anomaly indication information according to the identifier of the service interface of the first SMF to indicate to the first SMF entity that the first UPF entity has been attacked. Thus, the first SMF entity can take appropriate action to ensure communication security.

[0202] When the N4 coupling between the first SMF entity and the first UPF entity's N4 interface is broken, the SPEF entity can detect the interaction information related to the disconnection between the first SMF entity and the first UPF entity. The SPEF entity can send a connection disconnection indication message to the SPCF. The connection disconnection indication message indicates that the identifier of the N4 interface of the first SMF entity and the identifier of the N4 interface of the first UPF entity do not have a corresponding relationship, that is, the N4 interface of the first SMF entity and the N4 interface of the first UPF entity have been disconnected. The connection disconnection indication message may include the identifier of the N4 interface of the first SMF entity and the identifier of the N4 interface of the first UPF entity. Therefore, the SPCF entity can update the correspondence information 1.

[0203] Alternatively, after the SPCF entity sends an exception indication message according to the identifier of the service interface of the first SMF entity, the SPCF entity can update the correspondence information 1. In the updated correspondence information 1, the identifier of the N4 interface of the first SMF entity does not correspond to the identifier of the N4 interface of the first UPF entity.

[0204] Alternatively, after the SPCF entity sends the exception indication information according to the identifier of the service interface of the first SMF entity, the SPCF entity can mark it in the corresponding relationship information 1 to indicate that the exception indication information has been sent to the first SMF entity.

[0205] Figure 5 This is a schematic flowchart of a communication method provided in an embodiment of this application. Method 500 includes steps S501 to S509.

[0206] In S501, the first SMF entity establishes an N4 coupling with the first UPF entity.

[0207] In other words, the N4 interface of the first SMF entity establishes a connection with the N4 interface of the first UPF entity.

[0208] During the process of establishing an N4 association between the first SMF entity and the first UPF entity, the information exchanged between the first SMF entity and the first UPF entity carries the identifier of the N4 interface of the first UPF entity.

[0209] In S502, the first SMF entity sends association information 1 to the SPCF entity.

[0210] The associated information 1 includes the service interface identifier of the first SMF entity, the identifier of the N4 interface of the first SMF entity, and the identifier of the N4 interface of the first UPF entity.

[0211] In S503, the first SMF entity establishes or modifies a session with the first UPF entity.

[0212] During the process of establishing or modifying a session between the first SMF entity and the first UPF entity, the information exchanged between the first UPF entity and the first SMF entity carries the identifier of the N3 interface and / or the identifier of the N9 interface of the first UPF entity, which is used to configure the N3 interface and / or the N9 interface of the first UPF entity.

[0213] In S504, the first SMF entity sends association information 2 to the SPCF entity.

[0214] The associated information 2 includes the identifier of the N4 interface of the first UPF entity, as well as the identifier of the N3 interface and / or the identifier of the N9 interface of the first UPF entity.

[0215] It should be understood that an SPCF entity can receive association information 1 and association information 2 sent by at least one SMF entity. The at least one SMF entity includes a first SMF entity.

[0216] Then S505 to S506 can be performed.

[0217] In S505, the SPEF entity can determine whether the interface of the first UPF entity is abnormal.

[0218] The SPEF entity can inspect the interfaces of at least one UPF entity. Specifically, the SPEF entity can obtain information about the communication between each interface of each UPF entity and other network elements, and determine whether each interface is abnormal based on this information.

[0219] The information that allows any interface in each UPF entity to communicate with other network elements may include the identifier of that interface.

[0220] The at least one UPF entity includes the first UPF entity.

[0221] S505 can be performed multiple times. For example, S505 can be performed periodically.

[0222] In the event of an interface failure in the first UPF entity, S506 can be performed.

[0223] In S506, the SPEF entity can send exception interface information to the SPCF entity.

[0224] The SPCF entity can determine the SMF service interface associated with the abnormal interface in the first UPF entity based on the association information 1.

[0225] The abnormal interface information includes the identifier of the abnormal interface in the first UPF entity.

[0226] If the abnormal interface in the first UPF entity is the N4 interface of the first UPF entity, the SPCF entity can determine the identifier of the service interface of the first SMF that is associated with the first UPF entity by N4 according to the association information 1.

[0227] When the abnormal interface in the first UPF entity is either the N3 or N9 interface of the first UPF entity, the SPCF entity can determine the identifier of the N4 interface of the first SMF that is associated with the first UPF entity based on association information 1 and association information 2. For example, the SPCF entity can determine the identifier of the N4 interface of the first UPF entity based on association information 2; and the SPCF entity can determine the identifier of the service interface of the first SMF that is associated with the first UPF entity based on association information 1.

[0228] After that, S507 to S509 can be performed.

[0229] In S507, the SPCF entity sends an exception indication message according to the identifier of the service interface of the first SMF entity.

[0230] In S508, the first SMF entity disconnects the N4 coupling with the N4 interface of the first UPF entity.

[0231] In S509, the first SMF entity can perform session reconstruction or user plane path adjustment of the session if a session exists with the first UPF entity.

[0232] It should be understood that S507 to S509 can be similar to S411 to S413; see details below. Figure 4The description of S411 to S413.

[0233] In method 500, the first SMF entity sends association information 1 and association information 2 to the SPCF entity. Association information 1 indicates the association between the service interface of the first SMF entity and the N4 interface of the first UPF entity, and association information 2 indicates the association between the N4 interface of the first UPF entity and its N3 and N9 interfaces. Based on association information 1 and association information 2, the SPCF entity determines the service interface of the first SMF entity that has an N4 association with the first UPF entity to which the interface reported by the SPCF entity as having an anomaly belongs. The SPCF entity sends an anomaly indication message according to the service interface to notify the first SMF entity that the first UPF entity has been attacked and is untrusted. Thus, the first SMF entity can take appropriate action to ensure communication security. For example, the first SMF entity can release the N4 association with the first UPF entity based on the anomaly indication message, and can perform session reconstruction or user plane path adjustment according to session requirements.

[0234] For example, when the N4 coupling between the first SMF entity and the first UPF entity's N4 interface is disconnected, the SPEF entity can detect the interaction information related to the disconnection between the first SMF entity and the first UPF entity. The SPEF entity can send a connection disconnection indication message to the SPCF. The connection disconnection indication message indicates that the identifier of the N4 interface of the first SMF entity and the identifier of the N4 interface of the first UPF entity do not have a corresponding relationship, that is, the N4 interface of the first SMF entity and the N4 interface of the first UPF entity have been disconnected. The connection disconnection indication message may include the identifier of the N4 interface of the first SMF entity and the identifier of the N4 interface of the first UPF entity. Therefore, the SPCF entity can update the correspondence information 1.

[0235] For example, after the first SMF entity disconnects the N4 coupling with the N4 interface of the first UPF entity, the first SMF entity can send a connection disconnection indication message to the SPCF entity. The connection disconnection indication message indicates that the identifier of the N4 interface of the first SMF entity and the identifier of the N4 interface of the first UPF entity do not correspond, that is, the N4 interface of the first SMF entity and the N4 interface of the first UPF entity have been disconnected. Therefore, the SPCF entity can update the correspondence information 1.

[0236] For example, after the SPCF entity sends an exception indication message according to the identifier of the service interface of the first SMF entity, the SPCF entity can update the correspondence information 1. In the updated correspondence information 1, the identifier of the N4 interface of the first SMF entity and the identifier of the N4 interface of the first UPF entity do not have a correspondence.

[0237] For example, after the SPCF entity sends the exception indication information according to the identifier of the service interface of the first SMF entity, the SPCF entity can mark it in the corresponding relationship information 1 to indicate that the exception indication information has been sent to the first SMF entity.

[0238] Figure 6 This is a schematic flowchart of a communication method provided in an embodiment of this application. Method 600 includes steps S601 to S611.

[0239] In S601, the first SMF entity and the first UPF entity establish an N4 coupling.

[0240] During the process of establishing an N4 association between the first SMF entity and the first UPF entity, the information exchanged between the first SMF entity and the first UPF entity carries the identifier of the N4 interface of the first UPF entity.

[0241] In S602, the first SMF entity sends association information 1 to the UDR entity.

[0242] The associated information 1 includes the service interface identifier of the first SMF entity, the identifier of the N4 interface of the first SMF entity, and the identifier of the N4 interface of the first UPF entity.

[0243] In S603, the first SMF entity establishes or modifies a session with the first UPF entity.

[0244] During the process of establishing or modifying a session between the first SMF entity and the first UPF entity, the information exchanged between the first UPF entity and the first SMF entity carries the identifier of the N3 interface and / or the identifier of the N9 interface of the first UPF entity.

[0245] In S604, the first SMF entity sends association information 2 to the UDR entity.

[0246] The associated information 2 includes the identifier of the N4 interface of the first UPF entity, as well as the identifier of the N3 interface and / or the identifier of the N9 interface of the first UPF entity.

[0247] It should be understood that an SPCF entity can receive association information 1 and association information 2 sent by at least one SMF entity. The at least one SMF entity includes a first SMF entity.

[0248] Then S605 to S606 can be performed.

[0249] In S605, the SPEF entity can determine whether the interface of the first UPF entity is abnormal.

[0250] The SPEF entity can inspect the interfaces of at least one UPF entity. Specifically, the SPEF entity can obtain information about the communication between each interface of each UPF entity and other network elements, and determine whether each interface is abnormal based on this information.

[0251] The information that allows any interface in each UPF entity to communicate with other network elements may include the identifier of that interface.

[0252] The at least one UPF entity includes the first UPF entity.

[0253] S605 can be performed multiple times. For example, S605 can be performed periodically.

[0254] In the event of an interface malfunction in the first UPF entity, S606 can be executed.

[0255] In S606, the SPEF entity can send exception interface information to the SPCF entity.

[0256] The abnormal interface information includes the identifier of the abnormal interface in the first UPF entity.

[0257] After that, S607 and S608 can be performed.

[0258] In S607, the SPCF entity sends network element query information to the UDR entity.

[0259] The network element query information includes the identifiers of the abnormal interfaces in the first UPF entity.

[0260] The network element query information may also include a target entity type identifier, which indicates that the type of the entity being queried is SMF.

[0261] The UDR entity can determine the SMF service interface associated with the abnormal interface in the first UPF entity based on the association information 1.

[0262] If the abnormal interface in the first UPF entity is the N4 interface of the first UPF entity, the SPCF entity can determine the identifier of the service interface of the first SMF that is associated with the first UPF entity by N4 according to the association information 1.

[0263] When the abnormal interface in the first UPF entity is either the N3 or N9 interface of the first UPF entity, the SPCF entity can determine the identifier of the N4 interface of the first SMF that is associated with the first UPF entity based on association information 1 and association information 2. For example, the SPCF entity can determine the identifier of the N4 interface of the first UPF entity based on association information 2; and the SPCF entity can determine the identifier of the service interface of the first SMF that is associated with the first UPF entity based on association information 1.

[0264] In S608, the UDR entity sends network element response information to the SPCF entity.

[0265] The network element response information includes the identifier of the service interface of the first SMF.

[0266] The network element response information may also include the identifier of the N4 interface of the first UPF entity.

[0267] For example, if the UDR entity determines that the abnormal interface is not the N4 interface of the first UPF entity, the network element response information sent by the UDR entity includes the identifier of the N4 interface of the first UPF entity; if the UDR entity determines that the abnormal interface in the first UPF entity in the received network element query information is the N4 interface of the first UPF entity, the network element response information sent by the UDR entity may or may not include the identifier of the N4 interface of the first UPF entity.

[0268] After that, S609 to S611 can be performed.

[0269] In S609, the SPCF entity sends an exception indication message according to the identifier of the service interface of the first SMF entity.

[0270] In S610, the first SMF entity disconnects the N4 coupling with the N4 interface of the first UPF entity.

[0271] In S611, the first SMF entity can perform session reconstruction or user plane path adjustment of the session if a session exists with the first UPF entity.

[0272] It should be understood that S609 to S611 can be similar to S411 to S413, as detailed in the following documents. Figure 4 The description of S411 to S413.

[0273] In method 600, the first SMF entity registers association information 1 and association information 2 in the UDR entity. Association information 1 indicates the association between the service interface of the first SMF entity and the N4 interface of the first UPF entity, and association information 2 indicates the association between the N4 interface of the first UPF entity and its N3 and N9 interfaces. The SPCF entity sends the identifier of the interface with an anomaly reported by the SPEF entity to the UDR entity. Based on association information 1 and association information 2, the UDR entity sends the identifier of the service interface of the first SMF entity that is associated with the first UPF entity via N4. The SPCF entity sends anomaly indication information according to the identifier of the service interface to notify the first SMF entity that the first UPF entity has been attacked and is untrusted. Thus, the first SMF entity can take appropriate action to ensure communication security.

[0274] After the first SMF entity disconnects the N4 coupling with the first UPF entity's N4 interface, the first SMF entity can send a connection disconnection indication message to the UDR entity. The connection disconnection indication message may include the identifiers of the first SMF entity's N4 interface and the first UPF entity's N4 interface, and is used to instruct the first SMF entity to disconnect the N4 coupling with the first UPF entity. The UDR entity can delete association information 1 based on the connection disconnection indication message.

[0275] Alternatively, after the SPCF entity sends an exception indication message according to the identifier of the service interface of the first SMF entity, the SPCF entity may send a connection disconnection indication message to the UDR entity to instruct the UDR entity to delete the associated information 1.

[0276] Alternatively, after the SPCF entity sends the exception indication information according to the identifier of the service interface of the first SMF entity, the SPCF entity can send a notification indication information to the UDR entity. The notification indication information is used to indicate that the SPCF entity has sent the exception indication information to the first SMF entity.

[0277] Figure 7 This is a schematic flowchart illustrating a communication method provided in the application embodiment. Method 700 includes steps S710 to S720. Method 700 can be executed by a first SMF entity.

[0278] In S710, an anomaly indication message is received from the Security Policy Control Function (SPCF) entity, which indicates that the first UPF entity has been attacked.

[0279] In S710, the connection with the first UPF entity is disconnected.

[0280] Upon receiving an anomaly indication message from the SPCF entity, the first SMF entity disconnects from the first UPF entity, thus providing security for the communication system.

[0281] In other words, prior to S710, there was a connection between the first SMF entity and the first UPF entity. This connection could be an N4 association between the first SMF entity and the first UPF entity.

[0282] In some embodiments, prior to S710, the first SMF entity may send interface indication information to the NRF entity. The interface indication information includes the identifier of the second interface of the first SMF entity and the identifier of the third interface of the first SMF entity. The third interface is used for connection between the first SMF entity and the first UPF entity.

[0283] The anomaly indication information is sent by the SPCF entity based on the first response information sent by the NRF entity. The first response information includes the identifier of the third interface. The first response information is also sent by the NRF entity based on the first request information. The first request information includes the identifier of the second interface. The first request information is sent by the SPCF entity when the first UPF entity is attacked.

[0284] In other words, if the first UPF entity is attacked, the SPCF entity can determine the third interface of the first SMF entity connected to the first UPF entity. Then, the SPCF entity can send a first request message to the NRF entity, the first request message including the identifier of the third interface. The SPCF entity can receive a first response message from the NRF entity, the first response message including the identifier of the second interface of the first SMF entity. Therefore, the SPCF entity can send an anomaly indication message according to the identifier of the second interface, so that the anomaly indication message is sent to the first SMF entity.

[0285] Specifically, see Figure 3 and Figure 4 The explanation is as follows. Interface instruction information can be carried in... Figure 4 The network function registration information. The first request information can be... Figure 4 The interface query information. The second response information can be... Figure 4 The query response information.

[0286] In other embodiments, prior to S710, the first SMF entity may send first connection indication information to the SPCF entity, the first connection indication information being used to indicate at least one UPF entity to which the first SMF entity is connected, the at least one UPF entity including the first UPF entity.

[0287] The SPCF entity can receive first connection indication information sent by at least one SMF entity. This at least one SMF entity includes a first SMF entity. Therefore, the SPCF entity can determine that the SMF entity to which the first UPF entity is connected is the first SMF entity.

[0288] The first connection indication information may include the identifier of the second interface of the first SMF entity, and the exception indication information is sent by the SPCF entity according to the identifier of the second interface.

[0289] Specifically, see Figure 3 and Figure 5 The description. The first connection indication information may include... Figure 5 The associated information 1 and associated information 2 are shown.

[0290] In some other embodiments, prior to S710, the first SMF entity may send a second connection indication message to the UDR entity, the second connection indication message being used to indicate at least one UPF entity to which the first SMF entity is connected, the at least one UPF entity including the first UPF entity.

[0291] The anomaly indication information is sent by the SPCF entity based on the second response information, which includes the identifier of the first SMF entity. The second response information is also sent by the UDR entity based on the second request information, which includes the identifier of the first UPF entity. The second request information is sent by the SPCF entity when it determines that the first UPF entity has been attacked.

[0292] In other words, if the first UPF entity is attacked, the SPCF entity can send a second request message to the UDR entity, which includes the identifier of the first UPF entity. The SPCF entity can receive a second response message from the UDR entity, which also includes the identifier of the first SMF entity. Therefore, the SPCF entity can send anomaly indication information to the first SMF entity.

[0293] For example, the second connection indication information may include the identifier of the first SMF entity, which includes the identifier of the second interface of the first SMF entity. The exception indication information may be sent by the SPCF entity according to the identifier of the second interface.

[0294] For example, the second connection indication information may include an identifier of a fourth interface of the first UPF entity, which is used for connection between the first UPF entity and the first SMF entity. The second response information may also include an identifier of the fourth interface, and the exception indication information may include the identifier of the fourth interface.

[0295] For example, the identifier of the first UPF entity may include the identifier of a first interface in the first UPF entity. The first interface may be an interface in the first UPF entity that is experiencing an anomaly. The second connection indication information may include the identifiers of each interface of each UPF entity to which the first SMF entity is connected.

[0296] An SPCF entity can determine that the first UPF entity has been attacked if there is an abnormal interface in the first UPF entity.

[0297] Specifically, see Figure 3 and Figure 6 The description. The second connection indication information may include... Figure 6 The associated information 1 and associated information 2 are shown. The second request information can be... Figure 6 The network element query information. The second response information can be... Figure 6 The network element response information.

[0298] Figure 8 This is a schematic flowchart illustrating a communication method provided in an embodiment of this application. Method 800 includes steps S810 to S830. Method 800 can be executed by an NRF entity.

[0299] In S810, interface indication information sent by the first SMF entity is received. The interface indication information includes the identifier of the second interface of the first SMF entity and the identifier of the third interface of the first SMF entity. The third interface is used for the connection between the first SMF entity and the first UPF entity.

[0300] In S820, a first request message sent by an SPCF entity is received. The first request message includes the identifier of the second interface. The first request message is sent by the SPCF entity when it determines that the first UPF entity has been attacked.

[0301] In S830, a first response message is sent to the SPCF entity. The first response message includes the identifier of the third interface. The identifier of the third interface is used by the first SMF entity to send an anomaly indication message to the first SMF entity. The anomaly indication message is used to indicate that the first UPF entity has been attacked.

[0302] Method 800 provides a query function to the SPCF entity. Upon receiving the identifier of the second interface of the first SMF entity sent by the SPCF entity, the SPCF entity sends the identifier of the third interface of the first SMF entity to the SPCF entity. This enables the SPCF entity to send anomaly indication information to the first SMF entity connected to the first UPF entity when it determines that the first UPF entity has been attacked, thereby improving the security of the communication system.

[0303] Specifically, see Figure 3 and Figure 5 Explanation.

[0304] Figure 9 This is a schematic flowchart illustrating a communication method provided in an embodiment of this application. Method 900 includes steps S910 to S930. Method 900 can be executed by a UDR entity.

[0305] In S910, a second connection indication information sent by a first SMF entity is received. The second connection indication information is used to indicate at least one UPF entity connected to by the first SMF entity, and the at least one UPF entity includes the first UPF entity.

[0306] In S910, a second request message is received from an SPCF entity. The second request message is sent by the SPCF entity when it determines that the first UPF entity has been attacked. The second request message includes the identifier of the first UPF entity.

[0307] In S910, a second response message is sent to the SPCF entity. The second response message includes the identifier of the first SMF entity. The identifier of the first SMF entity is used by the first SMF entity to send an anomaly indication message to the first SMF entity. The anomaly indication message is used to indicate that the first UPF entity has been attacked.

[0308] Method 900 provides a query function to the SPCF entity. Upon receiving the identifier of the first UPF entity sent by the SPCF entity, the SPCF entity sends the identifier of the first SMF entity connected to the first UPF entity to the SPCF entity. This enables the SPCF entity to send anomaly indication information to the first SMF entity when it determines that the first UPF entity has been attacked, thereby improving the security of the communication system.

[0309] For example, the second connection indication information may include the identifier of the first SMF entity, which may include the identifier of the second interface of the first SMF entity, and the exception indication information is sent by the SPCF entity according to the identifier of the second interface.

[0310] For example, the second connection indication information may include an identifier of the fourth interface of the first UPF entity, which is used for the first UPF entity to connect to the SMF entity.

[0311] The second response information may also include the identifier of the fourth interface. The exception indication information may include the identifier of the fourth interface.

[0312] For example, the second connection indication information may include the identifier of at least one interface in each connected UPF entity. The second request information may include the identifier of a first interface in the first UPF entity. The identifier of at least one interface in the first UPF entity includes the identifier of the first interface. The first interface may be an interface in the first UPF entity that exhibits an anomaly.

[0313] Specifically, see Figure 3 and Figure 5 Explanation.

[0314] The above text combined Figures 1 to 9 The method embodiments of this application are described below, in conjunction with the following. Figures 10 to 11 This section describes the apparatus embodiments of the present application. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be found in the foregoing method embodiments.

[0315] Figure 10 This is a schematic structural diagram of a data processing device provided in an embodiment of this application.

[0316] The communication device 2000 includes a processing module 2010 and a transceiver module 2020.

[0317] In some embodiments, the communication device 2000 can be used to implement the functions of the SPCF entity mentioned above.

[0318] The processing module 2010 is used to determine whether the first user plane function UPF entity has been attacked.

[0319] The transceiver module 2020 is used to send an anomaly indication message to the first session management function (SMF) entity when the first UPF entity is attacked. The anomaly indication message is used to indicate that the first UPF entity has been attacked and that the first SMF entity is connected to the first UPF entity.

[0320] Optionally, the communication device 2000 further includes an acquisition module. The acquisition module is used to acquire connection information, the connection information being used to indicate at least one UPF entity connected to each of the at least one SMF entities, the at least one SMF entity including the first SMF entity.

[0321] Optionally, the processing module 2010 is specifically used to determine whether the first interface of the first UPF entity is abnormal, and if the first interface is abnormal, the first UPF entity is attacked.

[0322] Optionally, the connection information may also include the identifier of each interface in at least one interface of the first UPF entity, wherein at least one interface of the first UPF entity includes the first interface.

[0323] Optionally, the acquisition module is configured to receive connection indication information sent by the first SMF entity, the connection indication information being used to indicate at least one of the UPF entities to which the first SMF entity is connected.

[0324] Optionally, the connection indication information includes the identifier of the second interface of the first SMF entity.

[0325] The transceiver module 2020 is specifically used to send the abnormal indication information according to the identifier of the second interface.

[0326] Optionally, the connection indication information may further include the identifier of the fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect with the first SMF entity, and the exception indication information may include the identifier of the fourth interface.

[0327] Optionally, the connection information includes an identifier of a third interface of the first SMF entity, the third interface being used for connection between the first SMF entity and the first UPF entity.

[0328] The transceiver module 2020 is also used to send a first request message to the Network Storage Function (NRF) entity in the event of an anomaly in the first UPF entity, wherein the first request message includes the identifier of the third interface.

[0329] The transceiver module 2020 is also configured to receive first response information sent by the NRF entity, wherein the first response information includes the identifier of the second interface of the first SMF entity;

[0330] The transceiver module 2020 is specifically used to send the abnormal indication information according to the identifier of the second interface.

[0331] Optionally, the connection information is determined based on the interaction information between the at least one UPF entity and the at least one SMF entity, wherein the first interaction information between the first UPF entity and the first SMF entity includes the identifier of the third interface and the identifier of each interface among the at least one interface of the first UPF entity.

[0332] Optionally, at least one interface of the first UPF entity includes a fourth interface, the fourth interface being used for the first UPF entity to connect to the first SMF entity, and the exception indication information including the identifier of the fourth interface.

[0333] Optionally, the transceiver module 2020 is further configured to send a second request message to the unified database UDR entity in the event that the first UPF entity is abnormal, the second request message including the identifier of the first UPF entity.

[0334] The transceiver module 2020 is also configured to receive second response information sent by the UDR entity, the second response information including the identifier of the first SMF entity.

[0335] Optionally, the processing module 2010 is specifically used to determine whether the first interface of the first UPF entity is abnormal, and if the first interface is abnormal, the first UPF entity is attacked.

[0336] The identifier of the first UPF entity includes the identifier of the first abnormal interface in the first UPF entity.

[0337] Optionally, the identifier of the first SMF entity includes the identifier of the second interface of the first SMF entity.

[0338] The transceiver module 2020 is specifically used to send the abnormal indication information according to the identifier of the second interface.

[0339] Optionally, the second response information may also include an identifier of a fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect to the first SMF entity.

[0340] The anomaly indication information includes the identifier of the fourth interface.

[0341] In other embodiments, the communication device 2000 may be used to implement the functions of the first SMF entity mentioned above.

[0342] The transceiver module 2020 is used to receive anomaly indication information sent by the security policy control function entity, the anomaly indication information being used to indicate that the first UPF entity has been attacked.

[0343] The processing module 2010 is used to disconnect the connection with the first UPF entity.

[0344] Optionally, the transceiver module 2020 is further configured to send interface indication information to the NRF entity, the interface indication information including the identifier of the second interface of the device 2000 and the identifier of the third interface of the device 2000, the third interface being used for the connection between the device 2000 and the first UPF entity.

[0345] The anomaly indication information is sent by the security policy control function entity based on the first response information sent by the NRF entity, and the first response information includes the identifier of the third interface.

[0346] The first response information is sent by the NRF entity based on the first request information, which includes the identifier of the second interface. The first request information is sent by the security policy control function entity when the first UPF entity is attacked.

[0347] Optionally, the transceiver module 2020 is further configured to send first connection indication information to the security policy control function entity, the first connection indication information being used to indicate at least one UPF entity connected to the device 2000, the at least one UPF entity including the first UPF entity.

[0348] Optionally, the first connection indication information includes the identifier of the second interface of the device 2000, and the anomaly indication information is sent by the security policy control function entity according to the identifier of the second interface.

[0349] Optionally, the transceiver module 2020 is further configured to send a second connection indication information to the UDR entity, the second connection indication information being used to indicate at least one UPF entity connected to the device 2000, the at least one UPF entity including the first UPF entity.

[0350] The anomaly indication information is sent by the security policy control function entity based on the second response information, which includes the identifier of the device 2000.

[0351] The second response information is sent by the UDR entity based on the second request information, which includes the identifier of the first UPF entity.

[0352] The second request information is sent by the security policy control function entity when the first UPF entity is attacked.

[0353] Optionally, the second connection indication information includes the identifier of device 2000, the identifier of device 2000 includes the identifier of the second interface of device 2000, and the anomaly indication information is sent by the security policy control function entity according to the identifier of the second interface.

[0354] Optionally, the second connection indication information includes an identifier of a fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect to the device 2000.

[0355] The second response information also includes the identifier of the fourth interface, and the exception indication information includes the identifier of the fourth interface.

[0356] In some other embodiments, the communication device 2000 may be used to implement the functionality of the NRF entity described above.

[0357] The transceiver module 2020 is also used to receive interface indication information sent by the first SMF entity, the interface indication information including the identifier of the second interface of the first SMF entity and the identifier of the third interface of the first SMF entity, the third interface being used for the connection between the first SMF entity and the first UPF entity;

[0358] The transceiver module 2020 is also used to receive first request information sent by the security policy control function entity, the first request information including the identifier of the second interface, and the first request information is sent by the security policy control function entity when the first UPF entity is attacked;

[0359] The transceiver module 2020 is also used to send a first response message to the security policy control function entity. The first response message includes the identifier of the third interface. The identifier of the third interface is used by the first SMF entity to send an anomaly indication message to the first SMF entity. The anomaly indication message is used to indicate that the first UPF entity has been attacked.

[0360] The processing module 2010 can be used to control the transceiver module 2020 so that the transceiver module 2020 can perform the above functions.

[0361] In some other embodiments, the communication device 2000 may be a UDR entity, or may be used to implement the functions of the UDR entity described above.

[0362] The transceiver module 2020 is used to receive second connection indication information sent by a first SMF entity, the second connection indication information being used to indicate at least one UPF entity connected to the first SMF entity, the at least one UPF entity including the first UPF entity.

[0363] The transceiver module 2020 is also used to receive a second request message sent by the security policy control function entity, the second request message being sent by the security policy control function entity in the event that the first UPF entity is attacked, and the second request message including the identifier of the first UPF entity.

[0364] The transceiver module 2020 is also used to send a second response message to the security policy control function entity. The second response message includes the identifier of the first SMF entity. The identifier of the first SMF entity is used by the first SMF entity to send an anomaly indication message to the first SMF entity. The anomaly indication message is used to indicate that the first UPF entity has been attacked.

[0365] Optionally, the second connection indication information includes the identifier of the first SMF entity, the identifier of the first SMF entity includes the identifier of the second interface of the first SMF entity, and the anomaly indication information is sent by the security policy control function entity according to the identifier of the second interface.

[0366] Optionally, the second connection indication information includes the identifier of the fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect with the SMF entity, the second response information also includes the identifier of the fourth interface, and the exception indication information includes the identifier of the fourth interface.

[0367] The processing module 2010 can be used to control the transceiver module 2020 so that the transceiver module 2020 can perform the above functions.

[0368] Figure 8 This is a schematic structural diagram of a data processing device provided in an embodiment of this application.

[0369] The communication device 3000 includes at least one processor 3010 and a communication interface 3020.

[0370] The communication interface 3020 is used for communication device 3000 to exchange information with other communication devices.

[0371] When program instructions are executed in at least one processor 3010, at least one processor 3010 is used to perform the method described above.

[0372] In some embodiments, the communication device 3000 can be used to implement the functions of the SPCF entity mentioned above.

[0373] The processor 3010 is used to determine whether the first user plane function UPF entity has been attacked.

[0374] The communication interface 3020 is used to send an anomaly indication message to the first session management function (SMF) entity when the first UPF entity is attacked. The anomaly indication message is used to indicate that the first UPF entity has been attacked and the first SMF entity is connected to the first UPF entity.

[0375] Optionally, the communication interface 3020 is further configured to acquire connection information, the connection information being used to indicate at least one UPF entity connected to each of the at least one SMF entities, the at least one SMF entity including the first SMF entity.

[0376] Optionally, the processor 3010 is specifically configured to determine whether the first interface of the first UPF entity is abnormal, and if the first interface is abnormal, the first UPF entity is attacked.

[0377] Optionally, the connection information may also include the identifier of each interface in at least one interface of the first UPF entity, wherein at least one interface of the first UPF entity includes the first interface.

[0378] Optionally, the communication interface 3020 is further configured to receive connection indication information sent by the first SMF entity, the connection indication information being used to indicate at least one of the UPF entities to which the first SMF entity is connected.

[0379] Optionally, the connection indication information includes the identifier of the second interface of the first SMF entity.

[0380] The communication interface 3020 is also used to send the abnormal indication information according to the identifier of the second interface.

[0381] Optionally, the connection indication information may further include the identifier of the fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect with the first SMF entity, and the exception indication information may include the identifier of the fourth interface.

[0382] Optionally, the connection information includes an identifier of a third interface of the first SMF entity, the third interface being used for connection between the first SMF entity and the first UPF entity.

[0383] The communication interface 3020 is also used to send a first request message to the Network Storage Function (NRF) entity in the event of an anomaly in the first UPF entity, the first request message including the identifier of the third interface.

[0384] The communication interface 3020 is also used to receive first response information sent by the NRF entity, the first response information including the identifier of the second interface of the first SMF entity.

[0385] The communication interface 3020 is also used to send the abnormal indication information according to the identifier of the second interface.

[0386] Optionally, the connection information is determined based on the interaction information between the at least one UPF entity and the at least one SMF entity, wherein the first interaction information between the first UPF entity and the first SMF entity includes the identifier of the third interface and the identifier of each interface among the at least one interface of the first UPF entity.

[0387] Optionally, at least one interface of the first UPF entity includes a fourth interface, the fourth interface being used for the first UPF entity to connect to the first SMF entity, and the exception indication information including the identifier of the fourth interface.

[0388] Optionally, the communication interface 3020 is further configured to send a second request message to the unified database UDR entity in the event of an anomaly of the first UPF entity, the second request message including the identifier of the first UPF entity.

[0389] The communication interface 3020 is also used to receive second response information sent by the UDR entity, the second response information including the identifier of the first SMF entity.

[0390] Optionally, the processor 3010 is specifically configured to determine whether the first interface of the first UPF entity is abnormal, and if the first interface is abnormal, the first UPF entity is attacked.

[0391] The identifier of the first UPF entity includes the identifier of the first abnormal interface in the first UPF entity.

[0392] Optionally, the identifier of the first SMF entity includes the identifier of the second interface of the first SMF entity.

[0393] The communication interface 3020 is also used to send the abnormal indication information according to the identifier of the second interface.

[0394] Optionally, the second response information may also include an identifier of a fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect to the first SMF entity.

[0395] The anomaly indication information includes the identifier of the fourth interface.

[0396] In other embodiments, the communication device 3000 may be used to implement the functions of the first SMF entity mentioned above.

[0397] The communication interface 3020 is used to receive anomaly indication information sent by the security policy control function entity, the anomaly indication information being used to indicate that the first UPF entity has been attacked.

[0398] The processor 3010 is used to disconnect the connection with the first UPF entity.

[0399] Optionally, the communication interface 3020 is further configured to send interface indication information to the NRF entity, the interface indication information including the identifier of the second interface of the device 3000 and the identifier of the third interface of the device 3000, the third interface being used for the connection between the device 3000 and the first UPF entity.

[0400] The anomaly indication information is sent by the security policy control function entity based on the first response information sent by the NRF entity, and the first response information includes the identifier of the third interface.

[0401] The first response information is sent by the NRF entity based on the first request information, which includes the identifier of the second interface. The first request information is sent by the security policy control function entity when the first UPF entity is attacked.

[0402] Optionally, the communication interface 3020 is further configured to send a first connection indication message to the security policy control function entity, the first connection indication message being used to indicate at least one UPF entity connected to the device 3000, the at least one UPF entity including the first UPF entity.

[0403] Optionally, the first connection indication information includes the identifier of the second interface of the device 3000, and the anomaly indication information is sent by the security policy control function entity according to the identifier of the second interface.

[0404] Optionally, the communication interface 3020 is further configured to send a second connection indication information to the UDR entity, the second connection indication information being used to indicate at least one UPF entity connected to the device 3000, the at least one UPF entity including the first UPF entity.

[0405] The anomaly indication information is sent by the security policy control function entity based on the second response information, which includes the identifier of device 3000.

[0406] The second response information is sent by the UDR entity based on the second request information, which includes the identifier of the first UPF entity.

[0407] The second request information is sent by the security policy control function entity when the first UPF entity is attacked.

[0408] Optionally, the second connection indication information includes the identifier of device 3000, the identifier of device 3000 includes the identifier of the second interface of device 3000, and the anomaly indication information is sent by the security policy control function entity according to the identifier of the second interface.

[0409] Optionally, the second connection indication information includes an identifier of a fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect to the device 3000.

[0410] The second response information also includes the identifier of the fourth interface, and the exception indication information includes the identifier of the fourth interface.

[0411] In some other embodiments, the communication device 3000 may be used to implement the functionality of the NRF entity described above.

[0412] The communication interface 3020 is also used to receive interface indication information sent by the first SMF entity, the interface indication information including the identifier of the second interface of the first SMF entity and the identifier of the third interface of the first SMF entity, the third interface being used for the connection between the first SMF entity and the first UPF entity;

[0413] The communication interface 3020 is also used to receive first request information sent by the security policy control function entity, the first request information including the identifier of the second interface, and the first request information is sent by the security policy control function entity when the first UPF entity is attacked;

[0414] The communication interface 3020 is also used to send a first response message to the security policy control function entity. The first response message includes the identifier of the third interface. The identifier of the third interface is used by the first SMF entity to send an anomaly indication message to the first SMF entity. The anomaly indication message is used to indicate that the first UPF entity has been attacked.

[0415] The processor 3010 can be used to control the communication interface 3020 so that the communication interface 3020 can perform the above functions.

[0416] In some other embodiments, the communication device 3000 may be a UDR entity, or may be used to implement the functions of the UDR entity described above.

[0417] The communication interface 3020 is used to receive second connection indication information sent by a first SMF entity, the second connection indication information being used to indicate at least one UPF entity connected to the first SMF entity, the at least one UPF entity including the first UPF entity.

[0418] The communication interface 3020 is also used to receive a second request message sent by the security policy control function entity, the second request message being sent by the security policy control function entity in the event that the first UPF entity is attacked, and the second request message including the identifier of the first UPF entity.

[0419] The communication interface 3020 is also used to send a second response message to the security policy control function entity. The second response message includes the identifier of the first SMF entity. The identifier of the first SMF entity is used by the first SMF entity to send an anomaly indication message to the first SMF entity. The anomaly indication message is used to indicate that the first UPF entity has been attacked.

[0420] Optionally, the second connection indication information includes the identifier of the first SMF entity, the identifier of the first SMF entity includes the identifier of the second interface of the first SMF entity, and the anomaly indication information is sent by the security policy control function entity according to the identifier of the second interface.

[0421] Optionally, the second connection indication information includes the identifier of the fourth interface of the first UPF entity, the fourth interface being used for the first UPF entity to connect with the SMF entity, the second response information also includes the identifier of the fourth interface, and the exception indication information includes the identifier of the fourth interface.

[0422] The processor 3010 can be used to control the communication interface 3020 so that the communication interface 3020 can perform the above functions.

[0423] Furthermore, the units in the above devices can be integrated in whole or in part, or they can be implemented independently. In one implementation, these units are integrated together as a system-on-a-chip (SOC). The SOC may include at least one processor for implementing any of the above methods or implementing the functions of the units in the device. The at least one processor may be of different types, such as CPU and FPGA, CPU and artificial intelligence processor, CPU and graphics processing unit (GPU), etc.

[0424] This application also provides a computer program storage medium, characterized in that the computer program storage medium has program instructions, which, when executed, cause the method described above to be executed.

[0425] This application also provides a chip system, characterized in that the chip system includes at least one processor, and when program instructions are executed in the at least one processor, the method described above is executed.

[0426] This application also provides a program product, the computer program product including program instructions, which, when executed in a computer device, cause the aforementioned data processing method to be executed.

[0427] This application also provides a communication system, including at least one SMF entity, at least one UPF entity, and the communication device described above. The at least one SMF entity includes a first SMF entity, and the at least one UPF entity includes the first SMF entity.

[0428] The communication system may also include an NRF entity or a UDR entity.

[0429] It should be understood that the processor in the embodiments of this application can be a central processing unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0430] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile 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. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0431] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0432] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0433] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0434] In this application, prefixes such as "first" and "second" are used merely to distinguish different descriptive objects and do not limit the position, order, priority, quantity, or content of the described objects. For example, if the described object is an "interface," then the ordinal numbers before "interface" in "first interface" and "second interface" do not restrict the position, order, or priority of "interface"; similarly, if the described object is "request information," then the ordinal numbers before "request information" in "first request information" and "second request information" do not restrict the position, order, or priority of "request information."

[0435] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0436] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0437] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0438] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0439] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0440] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0441] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0442] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Entities applied to security policy control functions include: Determine whether the first user plane functional entity has been attacked; In the event that the first user plane functional entity is attacked, an anomaly indication message is sent to the first session management functional entity. The first session management functional entity is connected to the first user plane functional entity, and the anomaly indication message is used to indicate that the first user plane functional entity has been attacked. The method further includes: Obtaining connection information, the connection information including the identifier of the third interface of the first session management function entity, the third interface being used for connection between the first session management function entity and the first user plane function entity, the method further includes: In the event of an anomaly in the first user plane functional entity, a first request message is sent to the network storage functional entity, the first request message including the identifier of the third interface; The system receives a first response message from the network storage function entity, the first response message including the identifier of the second interface of the first session management function entity; Sending the exception indication information to the first session management function entity includes: sending the exception indication information according to the identifier of the second interface.

2. The method according to claim 1, characterized in that, The connection information is used to indicate at least one user plane function entity connected to each of the at least one session management function entities, the at least one session management function entity including the first session management function entity.

3. The method according to claim 2, characterized in that, Determining whether the first user plane functional entity has been attacked includes: determining whether the first interface of the first user plane functional entity is abnormal; if the first interface is abnormal, the first user plane functional entity has been attacked.

4. The method according to claim 3, characterized in that, The connection information also includes the identifier of each interface in at least one interface of the first user plane functional entity, wherein at least one interface of the first user plane functional entity includes the first interface.

5. The method according to any one of claims 1 to 4, characterized in that, The acquisition of connection information includes: Receive connection indication information sent by the first session management function entity, the connection indication information being used to indicate at least one of the user plane function entities to which the first session management function entity connects.

6. The method according to claim 5, characterized in that, The connection indication information includes the identifier of the second interface of the first session management function entity.

7. The method according to claim 5 or 6, characterized in that, The connection indication information also includes the identifier of the fourth interface of the first user plane functional entity, the fourth interface being used for the first user plane functional entity to connect with the first session management functional entity, and the exception indication information including the identifier of the fourth interface.

8. The method according to claim 1, characterized in that, The connection information is determined based on the interaction information between the at least one user plane functional entity and the at least one session management functional entity, wherein the first interaction information between the first user plane functional entity and the first session management functional entity includes the identifier of the third interface and the identifier of each of the at least one interface of the first user plane functional entity.

9. The method according to claim 8, characterized in that, At least one interface of the first user plane functional entity includes a fourth interface, which is used for the first user plane functional entity to connect with the first session management functional entity, and the exception indication information includes the identifier of the fourth interface.

10. The method according to claim 1, characterized in that, The method further includes: In the event of an anomaly in the first user plane functional entity, a second request message is sent to the unified database entity, the second request message including the identifier of the first user plane functional entity; The system receives a second response message sent by the unified database entity, the second response message including the identifier of the first session management function entity.

11. The method according to claim 10, characterized in that, Determining whether the first user plane functional entity has been attacked includes: determining whether the first interface of the first user plane functional entity is abnormal; if the first interface is abnormal, the first user plane functional entity has been attacked. The identifier of the first user plane functional entity includes the identifier of the first abnormal interface in the first user plane functional entity.

12. The method according to claim 10 or 11, characterized in that, The identifier of the first session management function entity includes the identifier of the second interface of the first session management function entity. Sending the exception indication information to the first session management function entity includes: sending the exception indication information according to the identifier of the second interface.

13. The method according to any one of claims 10 to 12, characterized in that, The second response information also includes the identifier of the fourth interface of the first user plane functional entity, the fourth interface being used for the first user plane functional entity to connect with the first session management functional entity. The anomaly indication information includes the identifier of the fourth interface.

14. A communication method, characterized in that, Applied to a session management function entity, the method includes: Receive an anomaly indication information sent by the security policy control function entity, the anomaly indication information being used to indicate that the first user plane function entity has been attacked; Disconnect from the first user plane functional entity; The method further includes: sending interface indication information to a network storage function entity, the interface indication information including the identifier of a second interface of the session management function entity and the identifier of a third interface of the session management function entity, the third interface being used for the connection between the session management function entity and the first user plane function entity; The anomaly indication information is sent by the security policy control function entity based on the first response information sent by the network storage function entity, and the first response information includes the identifier of the third interface. The first response information is sent by the network storage function entity based on the first request information, the first request information including the identifier of the second interface, and the first request information is sent by the security policy control function entity when the first user plane function entity is attacked.

15. The method according to claim 14, characterized in that, The method further includes: sending a first connection indication information to the security policy control function entity, the first connection indication information being used to indicate that the session management function entity connects to at least one user plane function entity, the at least one user plane function entity including the first user plane function entity.

16. The method according to claim 15, characterized in that, The first connection indication information includes the identifier of the second interface of the session management function entity, and the exception indication information is sent by the security policy control function entity according to the identifier of the second interface.

17. The method according to claim 14, characterized in that, The method further includes: sending a second connection indication information to a unified database entity, the second connection indication information being used to indicate at least one user plane function entity to which the session management function entity connects, the at least one user plane function entity including the first user plane function entity; The anomaly indication information is sent by the security policy control function entity based on the second response information, which includes the identifier of the session management function entity. The second response information is sent by the unified database entity based on the second request information, which includes the identifier of the first user plane function entity. The second request information is sent by the security policy control function entity when the first user plane function entity is attacked.

18. The method according to claim 17, characterized in that, The second connection indication information includes the identifier of the session management function entity, the identifier of the session management function entity includes the identifier of the second interface of the session management function entity, and the exception indication information is sent by the security policy control function entity according to the identifier of the second interface.

19. The method according to claim 17 or 18, characterized in that, The second connection indication information includes the identifier of the fourth interface of the first user plane functional entity, the fourth interface being used for the first user plane functional entity to connect with the session management functional entity. The second response information also includes the identifier of the fourth interface, and the exception indication information includes the identifier of the fourth interface.

20. A communication method, characterized in that, Entities applied to network storage functions include: The system receives interface indication information sent by the first session management function entity. The interface indication information includes the identifier of the second interface of the first session management function entity and the identifier of the third interface of the first session management function entity. The third interface is used for the connection between the first session management function entity and the first user plane function entity. The system receives a first request message sent by a security policy control function entity. The first request message includes the identifier of the second interface. The first request message is sent by the security policy control function entity when the first user plane function entity is attacked. The security policy control function entity sends a first response message, which includes the identifier of the third interface. The identifier of the third interface is used by the security policy control function entity to send an anomaly indication message to the first session management function entity. The anomaly indication message is used to indicate that the first user plane function entity has been attacked.

21. A communication method, characterized in that, Applied to unified database entities, including: Receive a second connection indication information sent by a first session management function entity, the second connection indication information being used to indicate at least one user plane function entity to which the first session management function entity is connected, the at least one user plane function entity including the first user plane function entity; Receive a second request message sent by the security policy control function entity, the second request message being sent by the security policy control function entity in the event that the first user plane function entity is attacked, the second request message including the identifier of the first user plane function entity; Send a second response message to the security policy control function entity. The second response message includes the identifier of the first session management function entity. The identifier of the first session management function entity is used by the security policy control function entity to send an anomaly indication message to the first session management function entity. The anomaly indication message is used to indicate that the first user plane function entity has been attacked.

22. The method according to claim 21, characterized in that, The second connection indication information includes the identifier of the first session management function entity, the identifier of the first session management function entity includes the identifier of the second interface of the first session management function entity, and the exception indication information is sent by the security policy control function entity according to the identifier of the second interface.

23. The method according to claim 21 or 22, characterized in that, The second connection indication information includes the identifier of the fourth interface of the first user plane functional entity, the fourth interface being used for the first user plane functional entity to connect with the session management functional entity. The second response information also includes the identifier of the fourth interface, and the exception indication information includes the identifier of the fourth interface.

24. A communication device, characterized in that, It includes various modules for performing the method according to any one of claims 1 to 23.

25. A communication device, characterized in that, It includes at least one processor and a communication interface, the communication interface being used for the communication device to interact with other communication devices, and when program instructions are executed in the at least one processor, causing the communication device to perform the method as described in any one of claims 1 to 23.

26. A computer program product, characterized in that, Includes program instructions, when which, when executed, the method as described in any one of claims 1 to 23, is performed.

27. A computer-readable storage medium, characterized in that, The computer-readable medium stores program instructions for execution by the device, which, when executed, perform the method as described in any one of claims 1 to 23.

28. A chip, characterized in that, The chip includes at least one processor, which, when program instructions are executed in the at least one processor, causes the method as described in any one of claims 1 to 23 to be performed.

Images