Communication method and network device

Abstract

The application provides a communication method and device, the method comprises: a session management function network element acquires an interface identifier; the session management function network element sends an address of a user plane function network element and the interface identifier to a first network element, the interface identifier is used for the first network element to determine an interface corresponding to the interface identifier, and the address of the user plane function network element and the interface corresponding to the interface identifier are used for the first network element to control the user plane function network element. In the communication method of the embodiment of the application, the UPF can realize that other types of control plane network elements of non-SMF type control the UPF network element, and the UPF network element can be isolated and operated based on different configurations of the SMF network element and other network elements, and the same message is processed in parallel, so that multiple types of controllers control the same UPF network element.

Description

Technical Field

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

[0002] Currently, in Service Based Architecture (SBA), only the Session Management Function (SMF) network element can control the User Plane Function (UPF) network element. For example, an SMF network element can control a UPF network element through the N4 interface, while other network elements need to go through the SMF network element to control the UPF network element.

[0003] With the evolution of fifth-generation (5G) networks, the functions of UPF (User Provider Function) have become increasingly powerful. For example, it can perform user service status analysis, including: whether traffic is abnormal, the severity of latency changes caused by network congestion, and whether latency meets service experience requirements, etc. These functions can meet the needs of Network Data Analysis Function (NWDAF) network elements and are real-time sensing capabilities, while current NWDAF network elements cannot directly control UPF network elements.

[0004] Therefore, the above-mentioned technologies can no longer adequately meet the requirements for realizing the functions of UPF network elements. How to enable non-SMF type network elements to control UPF network elements, and how UPF network elements can isolate the configurations of SMF network elements and other types of network elements, have become urgent problems to be solved. Summary of the Invention

[0005] This application provides a communication method and network device that enables other network elements (non-SMF type) to control UPF network elements. Moreover, the UPF network elements can operate in isolation based on different configurations of SMF network elements and other types of network elements, and process the same message in parallel, thereby enabling multiple types of controllers to control the same UPF network element.

[0006] In a first aspect, a communication method is provided, comprising: a session management function network element acquiring an interface identifier; the session management function network element sending the address of a user plane function network element and the interface identifier to a first network element, wherein the interface identifier is used by the first network element to determine the interface corresponding to the interface identifier, and the address of the user plane function network element and the interface corresponding to the interface identifier are used by the first network element to control the user plane function network element.

[0007] It should be understood that the interface corresponding to the interface identifier is the newly added message interface of the user plane function network element, including: message exit and / or message entry.

[0008] According to the solution provided in this application, the session management function network element can obtain the interface identifier and send the address of the user plane function network element and the interface identifier to the first network element. This enables the first network element to control the user plane function network element through the interface corresponding to the address and interface identifier of the user plane function network element. Simultaneously, the user plane function network element can operate in isolation based on different configurations of the session management function network element and other types of network elements, processing the same message in parallel, thereby enabling multiple types of controllers to control the user plane function network element.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the session management function network element sends first information to the user plane function network element, the first information being used to instruct the user plane function network element to allocate the interface identifier.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the session management function network element obtaining the interface identifier includes: the session management function network element receiving the interface identifier from the user plane function network element.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the session management function network element sends the interface identifier to the user plane function network element.

[0012] Optionally, the session management function network element receives capability indication information from the user plane function network element. The capability indication information is used to indicate that the user plane function network element can be controlled by a first type of network element, which is a network element other than the session management function type.

[0013] For example, the first type of network element may include different types of control plane function (CPF) network elements such as access and mobility management function (AMF), network data analysis function (NWDAF), policy control function (PCF), group management function (GMF), network expsorue function (NEF), unified data management (UDM), media function (MF), network repository function (NRF), authentication server function (AUSF), binding support function (BSF), and network data analysis (NWDA).

[0014] Optionally, the session management function network element receives a request message from the first network element, the request message being used to request control of the user plane function network element.

[0015] For example, the request message includes at least one of the following information: the identifier of the user plane function network element, the service area covered by the user plane function network element, and the session identifier of the user equipment.

[0016] Secondly, a communication method is provided, comprising: a user plane function network element receiving a message detection rule and a message processing rule corresponding to a first network element from a first network element, wherein the first network element is a non-session management function type network element; the user plane function network element receiving a message through an interface corresponding to the first network element; the user plane function network element detecting the message according to the message detection rule, and processing the message according to the message processing rule.

[0017] According to the solution provided in this application, the user plane function network element receives packet detection rules and packet processing rules corresponding to the first network element from the first network element, and performs packet detection and processing according to the packet detection rules and packet processing rules respectively. This enables the first network element to control the user plane function network element through the interface corresponding to the address and interface identifier of the user plane function network element. Simultaneously, the user plane function network element can operate in isolation based on different configurations of the session management function network element and other types of network elements, processing the same packet in parallel, thereby enabling multiple types of controllers to control the user plane function network element.

[0018] In conjunction with the second aspect, in some implementations of the second aspect, the user plane function network element receives first information from the session management function network element, the first information being used to instruct the user plane function network element to allocate an interface identifier for the interface.

[0019] In conjunction with the second aspect, in some implementations of the second aspect, the user plane function network element sends the interface identifier of the interface to the session management function network element.

[0020] In conjunction with the second aspect, in some implementations of the second aspect, the user plane function network element receives the interface identifier of the interface from the session management function network element.

[0021] Optionally, the user plane function network element sends capability indication information to the session management function network element. The capability indication information is used to indicate that the user plane function network element can be controlled by a first type of network element, where the first type of network element is a non-session management function type network element.

[0022] Thirdly, a communication method is provided, comprising: a first network element receiving an address and interface identifier of a user plane function network element from a session management function network element; the first network element determining an interface corresponding to the interface identifier based on the interface identifier; the first network element controlling the user plane function network element based on the address of the user plane function network element and the interface corresponding to the interface identifier; and the first network element sending a message detection rule and a message processing rule corresponding to the first network element to the user plane function network element, wherein the first network element is a non-session management function type network element.

[0023] According to the solution provided in this application, the first network element receives the address and interface identifier of the user plane function network element from the session management function network element, and sends the packet detection rules and packet processing rules corresponding to the first network element to the user plane function network element. This enables the first network element to control the user plane function network element through the interface corresponding to the address and interface identifier of the user plane function network element. Simultaneously, the user plane function network element can operate in isolation based on different configurations of the session management function network element and other types of network elements, processing the same packet in parallel, thereby enabling multiple types of controllers to control the user plane function network element.

[0024] In conjunction with the third aspect, in some implementations of the third aspect, the first network element sends a request message to the session management function network element, the request message being used to request the first network element to control the user plane function network element.

[0025] For example, the request message includes at least one of the following information: the identifier of the user plane function network element, the service area covered by the user plane function network element, and the session identifier of the user equipment.

[0026] Fourthly, a network device is provided, comprising: a processing unit for acquiring an interface identifier; and a transceiver unit for sending the address of a user plane function network element and the interface identifier to a first network element, wherein the address of the user plane function network element and the interface identifier are used by the first network element to control the user plane function network element through the interface corresponding to the interface identifier.

[0027] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to send first information to the user plane function network element, the first information being used to instruct the user plane function network element to allocate the interface identifier.

[0028] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the processing unit is used to receive the interface identifier from the user plane function network element through the transceiver unit.

[0029] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further configured to send the interface identifier to the user plane function network element.

[0030] Optionally, the transceiver unit is further configured to receive capability indication information from the user plane function network element, the capability indication information being used to indicate that the user plane function network element can be controlled by a first type of network element, the first type of network element being a non-session management function type network element.

[0031] Optionally, the transceiver unit is further configured to receive a request message from the first network element, the request message being used to request control of the user plane function network element.

[0032] For example, the request message includes at least one of the following information: the identifier of the user plane function network element, the service area covered by the user plane function network element, and the session identifier of the user equipment.

[0033] Fifthly, a network device is provided, comprising: a transceiver unit, configured to receive from a first network element a packet detection rule and a packet processing rule corresponding to the first network element, wherein the first network element is a non-session management function type network element; the transceiver unit is further configured to receive packets through an interface corresponding to the first network element; and a processing unit, configured to detect the packets according to the packet detection rule and process the packets according to the packet processing rule.

[0034] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to receive first information from the session management function network element, the first information being used to instruct the user plane function network element to allocate an interface identifier for the interface.

[0035] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to send the interface identifier of the interface to the session management function network element.

[0036] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to receive the interface identifier of the interface from the session management function network element.

[0037] Optionally, the transceiver unit is further configured to send capability indication information to the session management function network element, the capability indication information being used to indicate that the user plane function network element can be controlled by a first type of network element, the first type of network element being a non-session management function type network element.

[0038] In a sixth aspect, a network device is provided, comprising: a transceiver unit configured to receive an address and interface identifier of a user plane function network element from a session management function network element; a processing unit configured to determine an interface corresponding to the interface identifier based on the interface identifier; the processing unit is further configured to control the user plane function network element based on the address of the user plane function network element and the interface identifier; the transceiver unit is further configured to send a packet detection rule and a packet processing rule corresponding to a first network element to the user plane function network element, wherein the first network element is a non-session management function type network element.

[0039] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the transceiver unit is further configured to send a request message to the session management function network element, the request message being used to request the first network element to request control of the user plane function network element.

[0040] For example, the request message includes at least one of the following information: the identifier of the user plane function network element, the service area covered by the user plane function network element, and the session identifier of the user equipment.

[0041] In a seventh aspect, a network device is provided, including a transceiver, a processor, and a memory. The processor controls the transceiver to transmit and receive signals, the memory stores a computer program, and the processor calls and runs the computer program from the memory, causing the network device to perform the method in the first aspect or any possible implementation thereof, or the method in the second aspect or any possible implementation thereof, or the method in the third aspect or any possible implementation thereof.

[0042] Optionally, the processor may be one or more, and the memory may be one or more.

[0043] Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

[0044] Optionally, the network device may also include a transmitter and a receiver.

[0045] Eighthly, a communication apparatus is provided, comprising: a unit for implementing the method of the first aspect or any possible implementation thereof; or for implementing the method of the second aspect or any possible implementation thereof; or for implementing the method of the third aspect or any possible implementation thereof.

[0046] A ninth aspect provides a communication system comprising: a network device configured to perform the method as described in the first aspect or any possible implementation thereof; or to perform the method as described in the second aspect or any possible implementation thereof; or to perform the method as described in the third aspect or any possible implementation thereof.

[0047] In a tenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program or code, which, when executed on a computer, causes the computer to perform the methods of the first aspect or any possible implementation thereof, the second aspect or any possible implementation thereof, and the third aspect or any possible implementation thereof.

[0048] Eleventhly, a chip is provided, including at least one processor coupled to a memory for storing a computer program, the processor for calling and running the computer program from the memory, such that a network device equipped with the chip system performs the methods of the first aspect or any possible implementation of the first aspect, the second aspect or any possible implementation of the second aspect, and the third aspect or any possible implementation of the third aspect.

[0049] The chip may include an input circuit or interface for transmitting information or data, and an output circuit or interface for receiving information or data.

[0050] In a twelfth aspect, a computer program product is provided, the computer program product comprising: computer program code, which, when executed by a network device, causes the network device to perform the methods of the first aspect or any possible implementation thereof, the second aspect or any possible implementation thereof, and the third aspect or any possible implementation thereof.

[0051] According to the scheme of the embodiments of this application, the UPF can realize the control of the UPF by control plane network elements of other types other than SMF type, and the UPF can operate in isolation based on the different configurations of SMF network elements and other network elements, and process the same message in parallel, thereby realizing the control of the same UPF by multiple types of controllers. Attached Figure Description

[0052] Figure 1 This is a schematic diagram of an example of the communication system of this application.

[0053] Figure 2 This is a schematic diagram illustrating an example of the communication scenario described in this application.

[0054] Figure 3 This is a schematic diagram illustrating an example of a communication method applicable to this application.

[0055] Figure 4 This is a schematic diagram illustrating the message processing logic applicable to this application.

[0056] Figure 5 This is another schematic diagram illustrating a communication method applicable to this application.

[0057] Figure 6 This is another schematic diagram illustrating the communication method applicable to this application.

[0058] Figure 7 This is a schematic diagram of a communication device to which this application applies.

[0059] Figure 8This is another schematic diagram of a communication device to which this application applies.

[0060] Figure 9 This is yet another schematic diagram of a communication device to which this application applies.

[0061] Figure 10 This is a schematic diagram of a network device to which this application applies.

[0062] Figure 11 This is another schematic diagram of a network device to which this application applies.

[0063] Figure 12 This is yet another example of a network device to which this application applies. Detailed Implementation

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

[0065] The technical solutions of this application can be applied to various communication systems, such as: Global System of Mobile communication (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, 5G system, or New Radio (NR). They can also be extended to similar wireless communication systems, such as Wireless-Fidelity (WiFi), Worldwide Interoperability for Microwave Access (WIMAX), and cellular systems related to the 3rd Generation Partnership Project (3GPP).

[0066] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-everything (V2X) communication, such as vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

[0067] Figure 1 This is the network architecture applied to the embodiments of this application, and each network element that may be involved in the network architecture will be described separately.

[0068] 1. Terminal equipment 110: This may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities, as well as various forms of terminals, such as mobile stations (MS), terminals, user equipment (UE), soft terminals, etc. Examples include water meters, electricity meters, and sensors.

[0069] 2. Radio Access Network (R)AN element 120: Used to provide network access functionality for authorized terminal devices in a specific area, and can use transmission tunnels of different quality according to the level of the terminal device, service requirements, etc.

[0070] (R)AN network elements can manage wireless resources, provide access services for terminal devices, and then complete the forwarding of control signals and terminal device data between the terminal device and the core network. (R)AN network elements can also be understood as base stations in traditional networks.

[0071] It should be noted that the aforementioned "network element" can also be referred to as an entity, software, device, apparatus, or module, etc., and this application does not specifically limit it. Furthermore, in this application, for ease of understanding and explanation, the description of "network element" is omitted in some descriptions. For example, the (R)AN network element is abbreviated as (R)AN. In this case, the "(R)AN network element" should be understood as the (R)AN network element or (R)AN entity or (R)AN AN software. Hereinafter, descriptions of the same or similar cases are omitted.

[0072] 3. User plane function element 130: Used for packet routing and forwarding, as well as Quality of Service (QoS) processing of user plane data.

[0073] In 5G communication systems, this user plane network element can be a User Plane Function (UPF) network element. In future communication systems, the user plane network element can still be a UPF network element, or it can have other names; this application does not limit this.

[0074] 4. Data network element 140: Used to provide a network for transmitting data.

[0075] In 5G communication systems, this data network element can be a data network (DN) element. In future communication systems, the data network element can still be a DN element, or it can have other names; this application does not limit this.

[0076] 5. Access Management Network Element 150: Mainly used for mobility management and access management, it can be used to implement other functions of the Mobility Management Entity (MME) besides session management, such as lawful monitoring and access authorization / authentication.

[0077] In 5G communication systems, this access management network element can be an Access Management Function (AMF) network element. In future communication systems, the access management network element can still be an AMF network element, or it can have other names; this application does not limit this.

[0078] 6. Session Management Element 160: Primarily used for session management, allocation and management of Internet Protocol (IP) addresses for terminal devices, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink data notification, etc.

[0079] In 5G communication systems, this session management network element can be a Session Management Function (SMF) network element. In future communication systems, the session management network element can still be an SMF network element, or it can have other names; this application does not limit its scope.

[0080] 7. Policy Control Element 170: A unified policy framework used to guide network behavior, providing policy rule information to control plane functional elements (such as AMF, SMF, etc.).

[0081] In 4G communication systems, this policy control network element can be a Policy and Charging Rules Function (PCRF) network element. In 5G communication systems, this policy control network element can be a Policy Control Function (PCF) network element. In future communication systems, the policy control network element can still be a PCF network element, or it can have other names; this application does not limit this.

[0082] 8. Network storage function element 180: Used to maintain real-time information of all network function services in the network.

[0083] In 5G communication systems, this network storage element can be a Network Registration Function (NRF) element. In future communication systems, the network storage element can still be an NRF element, or it can have other names; this application does not limit its scope.

[0084] 9. Application Network Element 190: Used for data routing affected by applications, accessing network open function network elements, and interacting with the policy framework for policy control, etc.

[0085] In 5G communication systems, this application network element can be an Application Function (AF) network element. In future communication systems, the application network element can still be an AF network element, or it can have other names; this application does not limit this.

[0086] 10. Data Management Network Element 1100: Used for processing terminal device identification, access authentication, registration, and mobility management, etc.

[0087] In 5G communication systems, this data management network element can be a unified data management (UDM) network element. In future communication systems, unified data management can still be a UDM network element, or it can have other names; this application does not limit this.

[0088] 11. Group Management Network Element 1200: Used to manage the creation and membership of groups (specifically, terminal device groups) in mobile network local area networks (LANs), such as 5G LANs.

[0089] In 5G communication systems, the group management network element can also be the group management function (GMF) network element.

[0090] It should be noted that the aforementioned "network element" can also be referred to as an entity, device, apparatus, or module, etc., and this application does not specifically limit it. Furthermore, in this application, for ease of understanding and explanation, the description of "network element" is omitted in some descriptions. For example, the SMF network element is abbreviated as SMF. In this case, "SMF" should be understood as an SMF network element or an SMF entity. The following descriptions of the same or similar cases are omitted.

[0091] It is understood that the aforementioned network elements or functions can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0092] In this network architecture, the N2 interface serves as a reference point between RAN element 20 and AMF element 160, used for sending non-access stratum (NAS) messages, etc.; the N3 interface serves as a reference point between RAN element 120 and UPF element 130, used for transmitting user plane data, etc.; the N4 interface serves as a reference point between SMF element 170 and UPF element 130, used for transmitting information such as tunnel identification information for N3 connection, data buffer indication information, and downlink data notification messages, etc.; the N6 interface serves as a reference point between UPF element 130 and DN element 140, used for transmitting user plane data; and the N9 interface serves as a reference point between UPF element 130 and another UPF element, etc.

[0093] It should be understood that the prerequisite for implementing other types of control plane network element control UPF is that the two need to establish a connection, such as establishing a connection at the device level, or establishing a connection between devices, or using service interfaces or air interfaces to achieve the connection between the two.

[0094] It should be noted that the scope of SBA is limited to the control plane network elements of the core network, excluding the user plane function (UPF) network elements. Furthermore, the interfaces N3, N9, N6, and N4 supported by the UPF are not service-oriented interfaces. As can be seen from the architecture diagram above, the network element devices that can connect to the UPF include SMF, RAN, DN, and another UPF.

[0095] It should be understood that the network elements included in the communication system listed above are merely illustrative examples, and this application is not limited thereto. For example, it may also include, but is not limited to:

[0096] Authentication service network element: used for authentication services, generating keys to achieve two-way authentication of terminal devices, supporting a unified authentication framework, and can be an AUSF network element with authentication server function;

[0097] Network Open Function Element (NEF): This refers to the services and capabilities provided by securely open 3GPP network functions. These can be internally open or open to third parties.

[0098] Network slice selection function network element: used to select a set of network slice instances for user equipment, determine the allowed network slice selection assistance information (NSSAI), and determine the AMF set that can serve user equipment. It can be a network slice selection function (NSSF) network element.

[0099] Binding Support Function BSF Network Elements: Used to find the PCF associated with a session;

[0100] Network Data Analysis (NWDA) element: Used to collect and store information from terminal devices, RAN elements, and other network entities (e.g., AMF elements), analyze this information, generate contextual information about users (which can be considered application layer information), and distribute this application layer information.

[0101] 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 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.

[0102] For example, in some network architectures, network functional entities such as AMF, SMF, PCF, GMF, and UDM are all called Network Function (NF) network elements; or, in other network architectures, a collection of network elements such as AMF, SMF, PCF, GMF, and UDM can be called Control Plane Function (CPF) network elements.

[0103] Figure 2 A schematic block diagram of another architecture involved in this application is shown. For example... Figure 2 As shown, the SMF and other network elements control the UPF through configuration parameters A and B, respectively. The UPF executes the actions specified in configuration parameters A and B, which are mainly user plane packet processing.

[0104] It should be understood that other network elements can be control plane network elements other than SMF in the 5G network architecture, or other new network elements introduced as the 5G architecture evolves.

[0105] It should also be understood that in the technical solution of this application, the processing of packets by the UPF based on configuration parameter A and the processing of packets based on configuration parameter B are operated in isolation. That is, the UPF has different packet interfaces for different control plane network elements controlling the UPF. In addition, the rules used for packet processing in configuration parameter A and configuration parameter B can be the same or different, and this application does not limit this.

[0106] It should be noted that both configuration parameter A and configuration parameter B can include one of the following: Packet Detection Rule (PDR), Quality of Service Enforcement Rule (QER), Usage Reporting Rule (URR), Multi-Access Rule (MAR), and Forwarding Action Rule (FAR). These five types of rules are used by UPF for packet processing and all originate from the SMF configuration. Within the UPF's internal packet processing logic, PDR and FAR are mandatory packet processing rules, while the others are optional.

[0107] For example, the PDR is used to instruct the UPF to match information in a received message from an external source, such as the IP address in the message header. The message will only be processed according to the action specified in the configuration parameters if a PDR matches the message's information; otherwise, the message will be discarded.

[0108] FAR is used to instruct UPF on how to handle messages. Defined actions include forwarding, buffering, dropping, copying, etc.

[0109] It should be understood that a FAR is associated with a PDR, meaning that if the message information matches the PDR, the FAR associated with that PDR will be executed.

[0110] To facilitate understanding of the technical solution of this application, the following is a brief introduction to the method by which SMF controls UPF through the N4 interface:

[0111] (1) Establish connections at the equipment granularity level;

[0112] One possible implementation involves the SMF initiating an N4 association establishment request to the UPF, and the UPF sending an N4 association establishment response to the SMF.

[0113] It should be understood that establishing a connection at the device level is the first step in establishing communication between the SMF and the UPF. This step is used by the SMF to obtain information such as the UPF's identifier, capabilities, and load status.

[0114] (2) SMF configures session-level message processing rules for UPF.

[0115] One possible implementation includes: the SMF triggering the establishment of a Packet Data Unit (PDU) session or relocation of the UPF; the SMF initiating an N4 session establishment request to the UPF; the UPF sending an N4 session establishment response to the SMF; and interaction between the SMF and other network functions.

[0116] It should be understood that the SMF can only configure session-level packet processing rules for the UPF after a device-level connection has been established. It should be noted that the protocol used by the SMF to control the UPF is the Packet Forwarding Control Protocol (PFCP).

[0117] For other types of control plane network element control of UPF, control of UPF is generally achieved through SMF relay. That is, SMF will combine the control requests of other network elements with its own business logic to achieve configuration of UPF.

[0118] It should be understood that there can be various Packet Flow Detection (PDR) rules installed on a UPF, such as IP 5-tuples including source IP address, destination IP address, protocol number, source port, and destination port. For example, a packet flow detection rule might be associated with an application server (AF), such as an e-commerce server; this type of rule is called Packet Flow Detection (PFD). The AF wants to configure the PFD on the UPF to identify packets associated with that server. However, the current configuration process involves the AF first sending the PFD to the SMF, and then the SMF configuring the PFD on the UPF so that the server AF can control the UPF. One possible implementation involves the SMF, upon receiving an AF configuration request, triggering the provisioning or deletion of a set of PFDs belonging to an application ID; the SMF sending a PFD management request to the UPF; and the UPF sending a PFD management response to the SMF.

[0119] It should be understood that the above process of control plane network elements controlling UPF is only an illustrative example, and this application is not limited thereto. Other methods and processes that can control UPF fall within the protection scope of this application.

[0120] This application describes various embodiments in conjunction with core network equipment. The core network's main functions are to provide user connections, manage users, and bear services, serving as an interface to external networks. User connection establishment includes functions such as Mobile Management (MM), Connection Management (CM), switching / routing, and recording notifications. User management includes user descriptions, Quality of Service (QoS), user communication records, Virtual Home Environment (VHE), and security (provided by the authentication center, including security management of mobile services and security processing of external network access). Bearer connections include connections to the external Public Switched Telephone Network (PSTN), external circuit-switched data networks and packet-switched data networks, the internet and intranets, and the mobile network's own Short Message Service (SMS) server, etc.

[0121] The core network can provide basic services including mobile office, e-commerce, communication, entertainment, travel and location-based services, telemetry, simple messaging (surveillance and control), and so on.

[0122] As an example and not a limitation, core network equipment may include functional units such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Policy Control Function (PCF), and User Plane Function (UPF). These functional units can work independently or be combined to implement certain control functions. For example, AMF, SMF, and PCF can be combined as a management device to perform access control and mobility management functions such as access authentication, security encryption, and location registration for terminal devices, as well as session management functions such as the establishment, release, and modification of user plane transmission paths, and the function of analyzing some slice-related data (such as congestion) and terminal device-related data.

[0123] In the current SBA network architecture, only the SMF can control the UPF. However, with the evolution of 5G, the UPF's functionality is gradually becoming more powerful. For example, it can perform user service status analysis, including: whether traffic is abnormal, whether jitter is severe, whether latency meets service experience requirements, and so on. Other types of control plane network elements cannot directly obtain these functions from the UPF; instead, they need to request them indirectly from the SMF. This results in poor signaling throughput and data real-time performance. Therefore, enabling other types of control plane network elements to control the UPF is essential.

[0124] This application embodiment is applied to a communication system including at least one forwarding device and multiple core network devices. The following is a detailed description of the method for implementing other network element control UPF in this application embodiment with reference to the accompanying drawings.

[0125] By way of example and not limitation, embodiments of this application may include implementing SMF-controlled UPF, PCF-controlled UPF, NWDAF-controlled UPF, etc. The UPF primarily provides user plane service processing functions, including service routing, packet forwarding, anchoring, QoS mapping and execution, uplink identifier identification and routing to the data network, downlink packet caching and downlink data arrival notification triggering, and connection to external data networks.

[0126] For ease of explanation, this application uses SMF and UPF devices as examples to illustrate the method of controlling UPF by control plane network elements that are not SMF types. In the subsequent descriptions of this application, SMF can be replaced with Session Management Function network elements, and UPF can be replaced with User Plane Function network elements. For implementation methods where the device is a chip within an SMF or a chip within a UPF entity, please refer to the specific descriptions of the devices as SMF entities and UPF entities respectively, which will not be repeated here.

[0127] Figure 3 This is a schematic diagram illustrating an example of the communication method applicable to this application. For example... Figure 3 As shown, step 300 includes:

[0128] S310, Session Management Function Network Element Obtains Interface Identifier.

[0129] As an example and not a limitation, in one possible implementation, obtaining the interface identifier may include: the session management function network element independently determines the interface identifier, which corresponds to the first network element. That is, the session management function network element establishes communication at the device level, assigns an interface identifier to the user plane function network element, and sends the interface identifier to the user plane function network element through subsequent steps to inform the user plane function network element to configure the interface corresponding to the first network element.

[0130] It should be noted that the first network element refers to a network element that is not a session management function. For example, the first network element can be a control plane function (CPF) network element of different types, such as Access Management Function (AMF), Network Data Analysis Function (NWDAF), Policy Control Function (PCF), Group Management Function (GMF), Network Open Function (NEF), Unified Data Management Function (UDM), Media Function (MF), Network Registration Function (NRF), Authentication Server Function (AUSF), Binding Support Function (BSF), and Network Data Analysis Function (NWDA).

[0131] It should be understood that the interface corresponding to this interface identifier is the new message interface of the user plane function network element, including message exit and / or message entry.

[0132] As an example and not a limitation, in another possible implementation, obtaining the interface identifier may also include: the session management function network element receiving the interface identifier from the user plane function network element, that is, the user plane function network element assigning the interface identifier itself and sending the interface identifier to the session function management network element, and the interface identifier corresponding to the first network element.

[0133] In another possible implementation, the session management function network element can send first information to the user plane function network element, which instructs the user plane function network element to allocate the aforementioned interface identifier, i.e., to add a new message interface, which corresponds to the first network element.

[0134] Optionally, the first information may include one of the following: the identifier of the first network element, or the address of the first network element; a codeword, the service requirements of the first network element, and the service type; or, the message data size, whether the message is encrypted, etc. For example, the address of the first network element may include the IP address and the Media Access Control Address (MAC) of the first network element. The session management function network element can determine the user plane function network elements that the first network element can control based on the first information. The codeword can serve as a password for mutual detection between multiple devices.

[0135] In one possible implementation, a user plane function network element can send capability indication information to a session management function network element. This capability indication information indicates that the user plane function network element can be controlled by one or more network elements of the first type. It should be noted that the network elements of the first type are network elements that are not of the session management function type.

[0136] For example, this capability indication information may include: user plane function network elements reporting billing information, time, etc., to devices other than SMF types, such as charging function (CHF) network elements; or user plane function network elements reporting user service status analysis to devices other than SMF types, such as network data analysis function (NWDAF) network elements. For example, user service status analysis includes at least one of the following functions: whether traffic is abnormal, the severity of latency changes caused by network congestion, and whether latency meets service experience requirements. In other words, this capability indication information can indicate the specific types of devices that the user plane function network element can report to.

[0137] In another possible implementation, the first network element can send a request message to the session management function network element, which is used to request control of the user plane function network element.

[0138] It should be understood that the first network element can select a session management function network element based on at least one of the following: the service coverage area, the UE's camping area, and the jurisdiction of the first network element.

[0139] Optionally, the request message may include at least one of the following: the identifier of the user plane function network element (UPF ID), the service area covered by the user plane function network element, and the session identifier of the user equipment (UE session ID).

[0140] It should be understood that when the request message sent by the first network element includes a UPF ID, it means that the first network element has clearly informed the session management function network element which user plane function network element it wants to control. At this time, the session management function network element can find the corresponding user plane function network element.

[0141] When the request message sent by the first network element includes the service area covered by the user plane function network element, the first network element may not know which user plane function network element corresponds to it. In this case, the session management function network element can find one or more user plane function network elements in the service area and select one of them to be controlled by the first network element.

[0142] When the request message sent by the first network element includes the UE session ID, it means that the first network element wants to control a specific session of a user equipment. At this time, the session management function network element can find the user plane management network element corresponding to the specific session.

[0143] It should be noted that the UE session ID, also known as the Packet Data Unit (PDU) session identifier, or session ID, is used to identify a user equipment (UE) session. This UE session is managed by one or more user plane function elements (MPFs) to enable user plane connectivity. Therefore, the UE session ID can be associated with one or more MPFs.

[0144] S320, the session management function network element sends the address and interface identifier of the user plane function network element to the first network element, and correspondingly, the first network element receives the address and interface identifier of the user plane function network element from the session management function network element.

[0145] The interface identifier is used by the first network element to determine the interface corresponding to the interface identifier, and the address of the user plane function network element and the interface corresponding to the interface identifier are used by the first network element to control the user plane function network element.

[0146] It should be understood that by sending the address information of the user plane management network element to the first network element, the user plane management network element can flexibly interact with the first network element device without needing to forward the signaling through the session management function network element, thus reducing the signaling forwarding latency.

[0147] Optionally, the session management function network element can also send at least one of the identifier (UPFID) and codeword of the user plane management network element to the first network element.

[0148] S330, the first network element sends the Packet Detection Rule (PDR) and Packet Handle Rule (PHR) to the user plane management network element, and correspondingly, the user plane function network element receives the Packet Detection Rule (PDR) and Packet Handle Rule (PHR) from the first network element.

[0149] It should be understood that the message processing rules PHR here may include Quality of Service Enforcement Rules (QER), Usage Reporting Rules (URR), Multi-Access Rules (MAR), and Forwarding Action Rules (FAR), etc. This application does not specifically limit the types and number of message processing rules.

[0150] Optionally, the first network element can also send a codeword to the user plane management network element. This codeword can serve as a password for mutual detection between multiple devices.

[0151] S340, the user plane function network element receives downlink / uplink messages.

[0152] For example, a user equipment (UE) sends an uplink message to a user plane function network element, and / or a data network (DN) sends a downlink message to the user plane function network element; correspondingly, the user plane function network element receives the uplink message from the user equipment (UE) and / or receives the downlink message from the data network (DN).

[0153] It should be understood that the uplink / downlink message can be transmitted through at least one of the following methods: Radio Resource Control (RRC) signaling, Media Access Control (MAC CE) management element, and physical layer signaling (e.g., PDCCH).

[0154] In S350, user plane function network elements detect uplink / downlink packets according to the Packet Detection Rule (PDR) and process uplink / downlink packets according to the Packet Processing Rule (PHR).

[0155] It should be understood that before inspecting and processing packets, user plane function network elements should install packet inspection rules at the packet inlet and packet processing rules at the packet outlet. Figure 4 This diagram illustrates an example of the internal processing logic of a user plane function network element when it receives a packet from an external source. For example... Figure 4 As shown, a user plane function network element can include two layers of interfaces, such as a first-layer interface and a second-layer interface. External packet #1 first passes through the first-layer interface, and then the user plane function network element copies packet #1 to the second-layer interface. Assume that the second-layer interface of the user plane function network element has two pairs of packet ingress / egress points. Packet ingress / egress point #A is used by the Session Function Management (SMF) network element to control the user plane function network element, and packet ingress / egress point #B is used by the First Network Element (NWDAF) network element to control the user plane function network element. That is, the user plane management network element copies packet #1 to packet ingress point #A and packet ingress point #B respectively, and detects packet #1 according to the PDR #A of packet ingress point #A and the PDR #B of packet ingress point #B, for example, using the IP address in the packet header.

[0156] It is important to note that when the user plane function network element detects packet #1 according to packet processing rules PDR#A and PDR#B, it detects it from two different entry points, namely packet entry point #A and packet entry point #B. These two entry points are isolated, and the user plane function network element processes the same packet #1 in parallel through these two entry points. Correspondingly, packet exit points #A and #B are also isolated. In other words, each control plane network element installed on the user plane function network element has an independent packet interface, and the user plane function network element isolates the rule parameters PDR#A and PDR#B configured for the SMF network element and the NWDAF network element, respectively. Furthermore, packet detection rules #A and #B can be the same or different; this application does not impose any restrictions on this.

[0157] It should be understood that a packet will only be processed according to the actions specified in the configuration parameters if a PDR matches the packet's information; otherwise, the packet will be discarded. For example, if packet detection rule PDR#B matches packet #1, it means that packet #1 corresponds to the NWDAF network element. In this case, the user plane function network element will execute the corresponding packet processing rule PHR#B on packet #1, such as forwarding or copying, thereby enabling the NWDAF network element to control the user plane management function network element.

[0158] It should be noted that the above message processing rules PHR may include MAR, FAR, QER, URR, etc. Message ingress and message egress may exist simultaneously or separately, and this application does not limit this.

[0159] Based on the above possible implementation methods, the NWDAF network element can control the user plane function network element by executing packet detection rule #B and packet processing rule #B on packet #1. Furthermore, during packet processing, the user plane function network element can process the same data packet #1 in parallel based on both the packet detection rule #A corresponding to the SMF network element and the packet detection rule #B corresponding to the NWDAF network element. This isolates the different configurations of the SMF network element and the NWDAF network element, thereby enabling different types of controllers to control the same user plane function network element.

[0160] Figure 5 This is a schematic diagram illustrating a method for control plane network element #A to control UPF#A in the core network according to an embodiment of this application. As an example and not a limitation, it is exemplified by UPF#A automatically determining the interface identifier corresponding to network element #A. UPF#A acts as a forwarding device, SMF#A acts as a control device, and network element #A can be other control plane network element devices in the core network, such as the charging function network element CHF, policy control function network element PCF, and NWDAF. Figure 5 As shown, step 500 includes:

[0161] S510, UPF#A (i.e., an example of a user plane function network element) sends capability indication information #A to SMF#A (i.e., an example of a session management function network element), and correspondingly, SMF#A receives capability indication information #A from UPF#A.

[0162] The capability indication information #A indicates that the UPF#A can be controlled by other types of network elements (e.g., network element #A). Here, network element #A is a non-session management function type network element.

[0163] For example, the type of network element #A may include different types of control plane function CPF network elements such as AMF, NWDAF, PCF, GMF, NEF, UDM, MF, NRF, AUSF, BSF, and NWDA.

[0164] It should be understood that this capability indication information may include: user plane function network elements reporting billing information, time, etc., to devices other than SMF type, such as: billing function CHF network elements; or user plane function network elements reporting user service status analysis to devices other than SMF type, such as: network data analysis function NWDAF network elements, etc. For example, user service status analysis includes at least one of the following functions: whether the traffic is abnormal, whether the degree of latency change caused by network congestion is severe, and whether the latency meets the service experience requirements.

[0165] S520, network element #A (i.e., an example of the first network element) sends a request message #A to SMF#A, and correspondingly, SMF#A receives the request message #A from network element #A. This request message #A is used by network element #A to request control UPF#A.

[0166] It should be understood that network element #A can select SMF#A based on at least one of the following: the coverage area of ​​the service, the camping area of ​​the UE, and the jurisdiction of network element #A.

[0167] Optionally, the request message #A may include at least one of the following: the identification information of UPF#A (UPF ID), the service area covered by UPF#A, and the session ID of the user equipment (UE session ID).

[0168] S530, SMF#A determines the UPF#A used for network element #A control based on the received request message #A.

[0169] It should be understood that when the request message #A sent by network element #A includes a UPF ID, it means that network element #A explicitly tells SMF #A that it wants to control UPF #A. At this time, SMF #A can find the corresponding UPF #A.

[0170] When the request message #A sent by network element #A includes the service area covered by UPF#A, then network element #A may not know which UPF network element corresponds to it. In this case, SMF#A can find one or more UPF network elements in the service area and select one of the UPF#A network elements to be controlled by network element #A.

[0171] When the request message #A sent by network element #A includes the UE session ID, it means that network element #A wants to control a specific session of a user equipment. In this case, SMF#A can find the UPF#A network element corresponding to the specific session.

[0172] It should be noted that the UE session ID, also known as the Packet Data Unit (PDU) session identifier, or session ID, is used to identify a user equipment (UE) session. This UE session is managed by one or more User Plane Function (UPF) elements to enable user plane connectivity. Therefore, the UE session ID can be associated with one or more UPF elements.

[0173] S540, SMF#A sends first information #A to UPF#A, and correspondingly, UPF#A receives first information #A from SMF#A. This first information #A instructs UPF#A to allocate an interface identifier corresponding to network element #A, i.e., to add a new message interface, which corresponds to network element #A. In other words, UPF#A can have two sets of message interfaces at this time: one set for SMF#A and the other set for network element #A.

[0174] Optionally, the first information #A may include one of the following: the identifier of network element #A, or the address of network element #A; a codeword, the service requirements of network element #A, the service type; or, the message data size, whether the message is encrypted, etc. For example, the address of network element #A may include the IP address and the Media Access Control Address (MAC) of network element #A. SMF #A can determine the UPF #A that can be controlled for network element #A based on the first information #A. The codeword can serve as a password for mutual detection between multiple devices.

[0175] S541, UPF#A determines the interface identifier corresponding to network element #A and sends the interface identifier to SMF#A. Correspondingly, SMF#A receives the interface identifier from UPF#A. This interface identifier corresponds to network element #A.

[0176] S550, SMF#A sends the address and interface identifier of UPF#A to network element #A, and correspondingly, network element #A receives the address and interface identifier of UPF#A from SMF#A.

[0177] The interface identifier is used by network element #A to determine the interface corresponding to the interface identifier. The address of UPF#A and the interface corresponding to the interface identifier are used by network element #A to control the UPF#A network element.

[0178] It should be understood that the interface corresponding to this interface identifier is the new message interface of the UPF#A network element, including message exit and / or message entry. By sending the address information of UPF#A to network element #A, SMF#A enables UPF#A to interact flexibly with network element #A, and can forward without going through SMF#A, thus reducing signaling forwarding latency.

[0179] Optionally, the SMF#A may also send at least one of the identifier (UPF ID) and codeword of UPF#A to the network element #A.

[0180] Based on this, both UPF#A and network element #A have obtained the interface identification information and the identification information of UPF#A and network element #A.

[0181] S560, network element #A sends the message detection rule PDR and message processing rule PHR corresponding to network element #A to UPF#A, and correspondingly, UPF#A receives the message detection rule PDR and message processing rule PHR from network element #A.

[0182] It should be understood that the message processing rules PHR here may include Quality of Service Enforcement Rules (QER), Usage Reporting Rules (URR), Multi-Access Rules (MAR), and Forwarding Action Rules (FAR), etc. This application does not specifically limit the types and number of message processing rules.

[0183] Optionally, network element #A can also send a codeword to UPF#A. This codeword can serve as a password for mutual detection between multiple devices.

[0184] S570, UPF#A installs a Packet Detection Rule (PDR) at the new packet inlet and / or a Packet Processing Rule (PHR) at the new packet outlet. Both the new packet outlet and / or the new packet inlet correspond to network element #A.

[0185] It should be understood that the Packet Inspection Rule (PDR) corresponds to the newly added packet ingress, meaning the PDR instructs UPF#A to inspect packet information associated with network element #A. For example, if network element #A wants to identify packets related to a specific user's IP address, then UPF#A can match packets related to that specific user's IP address. Similarly, the Packet Processing Rule (PHR) corresponds to the newly added packet egress, meaning the PHR instructs UPF#A to send the processed packet to the appropriate controller. Optionally, the PHR may also include other additional processing information, such as instructions on the granularity at which UPF#A performs information statistics.

[0186] S581, the UE sends an uplink message to UPF#A through the interface corresponding to network element #A, and correspondingly, UPF#A receives uplink data messages from the user equipment UE through the interface corresponding to network element #A.

[0187] S582, the data network DN sends downlink data packets to UPF#A through the interface corresponding to network element #A, and correspondingly, UPF#A receives downlink data packets from the data network DN through the interface corresponding to network element #A.

[0188] It should be understood that the uplink and / or downlink messages in steps S581 and S582 can be transmitted through at least one of the following methods: Radio Resource Control (RRC) signaling, Media Access Control Management Unit (MAC) CE, and Physical Layer signaling.

[0189] S590, UPF#A detects uplink and / or downlink messages according to the Message Detection Rule (PDR) and processes uplink and / or downlink messages according to the Message Processing Rule (PHR).

[0190] The detection and processing of relevant uplink / downlink messages are described above. Figure 4 The details have already been explained in detail, so for the sake of brevity, they will not be repeated here.

[0191] It should be understood that the corresponding message processing rule will only be executed if a message detection rule (PDR) matches the information of an uplink / downlink message; otherwise, the uplink / downlink message will be discarded. It should be noted that message ingress and message egress can exist simultaneously or independently; this application does not impose any restrictions on this.

[0192] It should be understood that in the above embodiments, the number of message interfaces depends on the number of controllers requesting control of UPF#A, that is, one controller corresponds to one pair of message interfaces of UPF#A.

[0193] According to the above implementation method, the SMF#A network element instructs the UPF#A to allocate a new message interface corresponding to network element #A. The UPF#A sends the new interface identifier to the SMF#A, enabling control plane network elements of other types besides SM#A to control the UPF#A. Furthermore, the UPF#A can isolate the different configuration parameters of the SMF#A network element and network element #A, enabling parallel processing of the same data packet, and thus allowing multiple controllers of different types to control the same UPF#A.

[0194] Figure 6 This is a schematic diagram of a method for a control plane network element #a to control UPF#a in the core network according to an embodiment of this application. As an example and not a limitation, this implementation uses SMF#a assigning an interface identifier to UPF#a as an example. The main difference from step 500 above is that SMF#a may not send the first information to UPF#a, and SMF#a can independently determine the interface identifier information corresponding to network element #a and send the interface identifier to UPF#a. For example... Figure 6 As shown, step 600 includes:

[0195] S610, UPF#a (i.e., an example of a user plane function network element) sends capability indication information #a to SMF#a (i.e., an example of a session management function network element), and correspondingly, SMF#a receives capability indication information #a from UPF#a.

[0196] S620, network element #a (i.e., an example of the first network element) sends a request message #a to SMF#a, and correspondingly, SMF#a receives the request message #a from network element #a.

[0197] S630, SMF#a determines the UPF#a used for network element#a control based on request message #a.

[0198] It should be noted that steps S610 to S630 can be referred to the description of steps S510 to S530 above, and will not be repeated here for the sake of brevity.

[0199] S640, SMF#a determines the interface identifier corresponding to network element #a. Specifically, SMF#a allocates a new interface identifier for UPF#a in message processing. This interface identifier is used by network element #a to determine the interface corresponding to the interface identifier. This newly added message interface is used by network element #a to control UPF#a. The newly added message interface identifier corresponds to network element #a.

[0200] It should be understood that SMF#a determines the interface identifier corresponding to network element #a based on the device-level connection between SMF#a and UPF#a. Therefore, the message interface information of SMF#a for UPF#a (e.g., the number of allocated message interfaces, identification information, etc.) is determined, and SMF#a can allocate new message interface identifiers to UPF#a.

[0201] S650, SMF#a sends an interface identifier to UPF#a, and correspondingly, UPF#a receives an interface identifier from UPF#a, wherein the interface identifier corresponds to network element #a.

[0202] S660, SMF#a sends the address and interface identifier of UPF#a to network element #a, and correspondingly, network element #a receives the address and interface identifier of UPF#a from SMF#a.

[0203] S670, network element #a sends the Packet Detection Rule (PDR) and Packet Processing Rule (PHR) corresponding to network element #a to UPF #a. Correspondingly, UPF #a receives the Packet Detection Rule (PDR) and Packet Processing Rule (PHR) from network element #a. Here, network element #a is a non-session management function type network element.

[0204] S680, UPF#a installs a Packet Detection Rule (PDR) at the new packet inlet and / or a Packet Processing Rule (PHR) at the packet outlet. Both the new packet outlet and the new packet inlet correspond to network element #a.

[0205] S691, the UE sends an uplink message to UPF#a through the interface corresponding to network element #a, and correspondingly, UPF#a receives uplink data messages from the user equipment UE through the interface corresponding to network element #a.

[0206] S692, the data network DN sends downlink data packets to UPF#a through the interface corresponding to network element #a, and correspondingly, UPF#a receives downlink data packets from the data network DN through the interface corresponding to network element #a.

[0207] S693, UPF#a detects uplink and / or downlink messages according to the Message Detection Rule (PDR) and processes uplink and / or downlink messages according to the Message Processing Rule (PHR).

[0208] It should be noted that steps S660 to S693 can be referred to the description of steps S550 to S590 above, and will not be repeated here for the sake of brevity.

[0209] According to the above implementation method, UPF#a automatically determines the new message interface identifier corresponding to network element #a and sends the new message interface identifier to SMF#a, enabling control plane network elements of other types besides SM#a to control the UPF#a. Furthermore, UPF#a can isolate different configuration parameters of SMF#a network elements and network element #a, enabling parallel processing of the same data packet, and thus allowing multiple controllers of different types to control the same UPF#a.

[0210] The foregoing has described in detail the method for controlling UPF by control plane network elements of other types besides SMF according to embodiments of this application. The following will describe the apparatus for controlling UPF by control plane network elements of other types besides SMF according to embodiments of this application.

[0211] According to the aforementioned method, Figure 7 This is a schematic diagram of a communication device 10 (which may also be a network device, such as SMF#A) applicable to embodiments of this application. Figure 7 As shown, the communication device 10 includes a transceiver unit 11 and a processing unit 12.

[0212] For example, the processing unit 12 is used to obtain the interface identifier.

[0213] The transceiver unit 11 is used to send the address and interface identifier of the user plane function network element to the first network element. The interface identifier is used by the first network element to determine the interface corresponding to the interface identifier. The address and interface identifier of the user plane function network element are used by the first network element to control the user plane function network element.

[0214] It should be understood that the communication device 10 may correspond to the session function management network element in the method 300 / 500 / 600 of the first network element controlling the user plane function management network element according to the embodiments of this application. The communication device 10 may include functions for performing... Figure 3 / Figure 5 / Figure 6The method 300 / 500 / 600 for controlling user plane functions and managing network elements in the first network element control method is executed by a module (or unit) of a network device. Furthermore, each module (or unit) in the communication device 10 and the aforementioned other operations and / or functions are respectively for implementing... Figure 3 / Figure 5 / Figure 6 The method for managing network elements using the user plane control function of the first network element in China, and the corresponding procedures for 300 / 500 / 600.

[0215] For example, the transceiver unit 11 is used to execute S320, or S510, S520, S540, S541 and S550, or S610, S620, S650 and S660 in method 300 / 500 / 600; the processing unit 12 is used to execute S310, or S530, or S630 and S640 in method 300 / 500 / 600. The process of each module (or unit) executing the above corresponding steps has been described in detail in method 300 / 500 / 600, and will not be repeated here for the sake of brevity.

[0216] It should be understood that Figure 7 The structure of the example device 10 is merely one possible configuration and should not be construed as limiting the embodiments of this application. This application does not exclude the possibility of other configurations of network devices in the future.

[0217] It should be understood that the communication device 10 according to the embodiments of this application can correspond to the network device of the first network element control user plane function network element in the foregoing method embodiments, and the above and other management operations and / or functions of each module (or unit) in the communication device 10 are respectively to implement the corresponding steps of the foregoing methods, so the beneficial effects in the foregoing method embodiments can also be achieved.

[0218] It should also be understood that the processing module (or unit) in the embodiments of this application can be implemented by a processor, and the transceiver module (or unit) can be implemented by a transceiver. According to the foregoing method, Figure 8 This is a schematic diagram of a communication device 20 (which may also be a network device, such as UPF#A) applicable to embodiments of this application. Figure 8 As shown, the communication device 20 includes a transceiver unit 21 and a processing unit 22.

[0219] For example, the transceiver unit 21 is used to receive message detection rules and message processing rules corresponding to the first network element, where the first network element is a non-session management function type network element.

[0220] The transceiver unit 21 is also used to receive messages through the interface corresponding to the first network element.

[0221] The processing unit 22 is used to detect messages according to message detection rules and to process messages according to message processing rules.

[0222] It should be understood that the communication device 20 may correspond to the user plane function network element in the method 300 / 500 / 600 of the first network element controlling the user plane function network element according to the embodiments of this application, and the communication device 20 may include functions for performing... Figure 3 / Figure 5 / Figure 6 The method 300 / 500 / 600 for controlling user plane function network elements in the first network element is executed by a module (or unit) of a network device. Furthermore, each module (or unit) in the communication device 20 and the aforementioned other operations and / or functions are respectively for implementing... Figure 3 / Figure 5 / Figure 6 The method for controlling user plane function network elements by the first network element in the network is described in the corresponding procedures of 300 / 500 / 600.

[0223] For example, the transceiver unit 21 is used to execute S330 and S340, or S510, S540, S541, S560, S581, and S582, or S610, S650, S670, S691, and S692 in method 300 / 500 / 600; the processing unit 22 is used to execute S350, or S570 and S590, or S680 and S693 in method 300 / 500 / 600. The process of each module (or unit) executing the above-mentioned corresponding steps has been described in detail in method 300 / 500 / 600, and will not be repeated here for the sake of brevity.

[0224] It should be understood that Figure 8 The structure of the example device 20 is merely one possible configuration and should not be construed as limiting the embodiments of this application. This application does not exclude the possibility of other configurations of network devices in the future.

[0225] It should be understood that the communication device 20 according to the embodiments of this application can correspond to the network device of the first network element control user plane function network element in the foregoing method embodiments, and the above and other management operations and / or functions of each module (or unit) in the communication device 20 are respectively to implement the corresponding steps of the foregoing methods, so the beneficial effects in the foregoing method embodiments can also be achieved.

[0226] It should also be understood that the processing module (or unit) in the embodiments of this application can be implemented by a processor, and the transceiver module (or unit) can be implemented by a transceiver.

[0227] According to the aforementioned method, Figure 9 This is a schematic diagram of a communication device 30 (which may also be a network device, such as network element #A) applicable to embodiments of this application. Figure 9As shown, the communication device 30 includes a transceiver unit 31 and a processing unit 32.

[0228] For example, the transceiver unit 31 is used to receive the address and interface identifier of the user plane function network element from the session management function network element;

[0229] The processing unit 32 is used to determine the interface corresponding to the interface identifier based on the interface identifier;

[0230] The processing unit 32 is also used to control the user plane function network element according to the interface corresponding to the address and interface identifier of the user plane function network element; the transceiver unit 31 is also used to send the message detection rules and message processing rules corresponding to the first network element to the user plane function network element, wherein the first network element is a non-session management function type network element.

[0231] It should be understood that the communication device 30 may correspond to other types of control plane network elements of the non-session management function type in the method 300 / 500 / 600 for controlling user plane function network elements according to the embodiments of this application. The communication device 30 may include functions for performing... Figure 3 / Figure 5 / Figure 6 The method 300 / 500 / 600, which controls user plane function network elements in the first network element, is executed by modules (or units) of a network device 30. Furthermore, each module (or unit) in this network device 30 and the aforementioned other operations and / or functions are respectively for implementing... Figure 3 / Figure 5 / Figure 6 The method for controlling user plane function network elements by the first network element in the network is described in the corresponding procedures of 300 / 500 / 600.

[0232] For example, the transceiver unit 31 is used to execute S320 and S330, or S520, S550 and S560, or S620, S660 and S670 in methods 300 / 500 / 600. The process of each module (or unit) executing the above-mentioned corresponding steps has been described in detail in methods 300 / 500 / 600, and will not be repeated here for the sake of brevity.

[0233] It should be understood that Figure 9 The structure of the example device 30 is merely one possible configuration and should not be construed as limiting the embodiments of this application. This application does not exclude the possibility of other configurations of network devices in the future.

[0234] It should be understood that the communication device 30 according to the embodiments of this application can correspond to the network device of the first network element control user plane function network element in the foregoing method embodiments, and the above and other management operations and / or functions of each module (or unit) in the communication device 30 are respectively to implement the corresponding steps of the foregoing methods, so the beneficial effects in the foregoing method embodiments can also be achieved.

[0235] It should also be understood that the processing module (or unit) in the embodiments of this application can be implemented by a processor, and the transceiver module (or unit) can be implemented by a transceiver.

[0236] According to the aforementioned method, Figure 10 A schematic diagram of the communication device (also referred to as a network device) 40 provided in the embodiments of this application is shown below. Figure 10 As shown, the device 40 can be a network device (e.g., SMF), or a chip or circuit, such as a chip or circuit that can be set in a network device.

[0237] The device 40 may include a processor 41 (i.e., an example of a processing unit) and a memory 42. The memory 42 is used to store instructions, and the processor 41 is used to execute the instructions stored in the memory 42 to cause the device 40 to perform the steps performed by the network device (e.g., SMF) in the methods described above (e.g., method 300, method 500, or method 600).

[0238] Optionally, the device 40 may also include an input port 43 (i.e., an example of a communication unit) and an output port 44 (i.e., another example of a communication unit). It should be understood that the processor 41, memory 42, input port 43, and output port 44 can communicate with each other through internal connection paths to transmit control and / or data signals.

[0239] The memory 42 is used to store computer programs, and the processor 41 can be used to call and run the computer programs from the memory 42 to control the input port 43 to receive signals and control the output port 44 to send signals, thereby completing the steps of the network device in the above method.

[0240] The memory 42 can be integrated into the processor 41 or set separately from the processor 41.

[0241] Optionally, if the device 40 is a network device, the input port 43 is a receiver, and the output port 44 is a transmitter. The receiver and transmitter can be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.

[0242] Optionally, if the device 40 is a chip or circuit, the input port 43 is an input interface and the output port 44 is an output interface.

[0243] As one implementation method, the functions of input port 43 and output port 44 can be implemented using transceiver circuits or dedicated transceiver chips. Processor 41 can be implemented using dedicated processing chips, processing circuits, processors, or general-purpose chips.

[0244] As another implementation method, the network device provided in this application embodiment can be implemented using a general-purpose computer. The program code that implements the functions of processor 41, input port 43, and output port 44 is stored in memory 42, and the general-purpose processor implements the functions of processor 41, input port 43, and output port 44 by executing the code in memory 42.

[0245] In this embodiment of the application, the processor 41 is used to obtain the interface identifier.

[0246] The output port 44 is used to send the address and interface identifier of the user plane function network element to the first network element. The interface identifier is used by the first network element to determine the interface corresponding to the interface identifier. The address and interface identifier of the user plane function network element are used by the first network element to control the user plane function network element.

[0247] Optionally, the device 40 is configured in or is itself a Session Management Function (SMF) entity.

[0248] The functions and actions of each module or unit in the device 40 listed above are merely illustrative examples. Each module or unit in the device 40 can be used to perform the actions or processes performed by the network device in the above methods 300, 500, or 600. Here, to avoid redundancy, detailed descriptions are omitted.

[0249] For example, processor 41 can execute the actions performed by SMF in S530 or S630 and S640 described above.

[0250] For the concepts, explanations, detailed descriptions, and other steps related to the technical solutions provided in the embodiments of this application involved in the device 40, please refer to the descriptions of these contents in the foregoing methods or other embodiments, which will not be repeated here.

[0251] In one possible implementation, with the development of System-on-Chip (SoC) technology, all or part of the functions of device 40 are implemented by SoC technology, for example, by a network device function chip. This network device function chip integrates a processor, memory, communication interface, and other devices. The program for the network device-related functions is stored in the memory, and the processor executes the program to implement the base station's related functions. Optionally, the network device function chip can also read external memory to implement the base station's related functions.

[0252] It should be understood that Figure 10The structure of the example device 40 is merely one possible configuration and should not be construed as limiting the embodiments of this application. This application does not exclude the possibility of other base station structures in the future.

[0253] According to the aforementioned method, Figure 11 A schematic diagram of the communication device (also referred to as a network device) 50 provided in the embodiments of this application is shown below. Figure 11 As shown, the device 50 can be a network device (e.g., a UPF), or a chip or circuit, such as a chip or circuit that can be installed in a network device.

[0254] The device 50 may include a processor 51 (i.e., an example of a processing unit) and a memory 52. ​​The memory 52 is used to store instructions, and the processor 51 is used to execute the instructions stored in the memory 52 to cause the device 50 to perform the steps performed by the network device (e.g., UPF) in the methods described above (e.g., method 300, method 500, or method 600).

[0255] Optionally, the device 50 may also include an input port 53 (i.e., an example of a communication unit) and an output port 54 (i.e., another example of a communication unit). It should be understood that the processor 51, memory 52, input port 53, and output port 54 can communicate with each other through internal connection paths to transmit control and / or data signals.

[0256] The memory 52 is used to store computer programs, and the processor 51 can be used to call and run the computer programs from the memory 52 to control the input port 53 to receive signals and control the output port 54 to send signals, thereby completing the steps of the network device in the above method.

[0257] The memory 52 can be integrated into the processor 51 or set separately from the processor 51.

[0258] Optionally, if the device 50 is a network device, the input port 53 is a receiver, and the output port 54 is a transmitter. The receiver and transmitter can be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.

[0259] Optionally, if the device 50 is a chip or circuit, the input port 53 is an input interface and the output port 54 is an output interface.

[0260] As one implementation method, the functions of input port 53 and output port 54 can be implemented using transceiver circuits or dedicated transceiver chips. Processor 51 can be implemented using dedicated processing chips, processing circuits, processors, or general-purpose chips.

[0261] As another implementation method, the network device provided in this application embodiment can be implemented using a general-purpose computer. The program code that implements the functions of processor 51, input port 53, and output port 54 is stored in memory 52, and the general-purpose processor implements the functions of processor 51, input port 53, and output port 54 by executing the code in memory 52.

[0262] In this embodiment, the input port 53 is used to receive the message detection rules and message processing rules corresponding to the first network element, where the first network element is a non-session management function type network element.

[0263] The input port 53 is also used to receive messages through the interface corresponding to the first network element.

[0264] The processor 51 is used to detect packets according to packet detection rules and to process packets according to packet processing rules.

[0265] Optionally, the device 50 is configured in or is itself a user-plane functional entity (UPF).

[0266] The functions and actions of each module or unit in the device 50 listed above are merely illustrative examples. Each module or unit in the device 50 can be used to perform the actions or processes performed by the network device in the above methods 300, 500, or 600. Here, to avoid redundancy, detailed descriptions are omitted.

[0267] For example, processor 51 can execute the actions performed by UPF in S350, or S570 and S590, or S680 and S693.

[0268] For the concepts, explanations, detailed descriptions, and other steps related to the technical solutions provided in the embodiments of this application involved in the device 50, please refer to the descriptions of these contents in the foregoing methods or other embodiments, which will not be repeated here.

[0269] In one possible implementation, with the development of System-on-Chip (SoC) technology, all or part of the functions of device 50 are implemented by SoC technology, for example, by a network device function chip. This network device function chip integrates a processor, memory, communication interface, and other devices. The program for the network device-related functions is stored in the memory, and the processor executes the program to implement the base station's related functions. Optionally, the network device function chip can also read external memory to implement the base station's related functions.

[0270] It should be understood that Figure 11The structure of the example device 50 is merely one possible configuration and should not be construed as limiting the embodiments of this application. This application does not exclude the possibility of other base station structures in the future.

[0271] According to the aforementioned method, Figure 12 A schematic diagram of the communication device (also referred to as a network device) 60 provided in the embodiments of this application is shown below. Figure 12 As shown, the device 60 can be a network device (e.g., another network element), or a chip or circuit, such as a chip or circuit that can be set in a network device.

[0272] The device 60 may include a processor 61 (i.e., an example of a processing unit) and a memory 62. The memory 62 is used to store instructions, and the processor 61 is used to execute the instructions stored in the memory 62 to cause the device 60 to perform the steps performed by the network device (e.g., other network elements) in the methods described above (e.g., method 300, method 500, or method 600).

[0273] Optionally, the device 60 may also include an input port 63 (i.e., an example of a communication unit) and an output port 64 (i.e., another example of a communication unit). It should be understood that the processor 61, memory 62, input port 63, and output port 64 can communicate with each other through internal connection paths to transmit control and / or data signals.

[0274] The memory 62 is used to store computer programs, and the processor 61 can be used to call and run the computer programs from the memory 62 to control the input port 63 to receive signals and control the output port 64 to send signals, thereby completing the steps of the network device in the above method.

[0275] The memory 62 can be integrated into the processor 61 or set separately from the processor 61.

[0276] Optionally, if the device 60 is a network device, the input port 63 is a receiver, and the output port 64 is a transmitter. The receiver and transmitter can be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.

[0277] Optionally, if the device 60 is a chip or circuit, the input port 63 is an input interface and the output port 64 is an output interface.

[0278] As one implementation method, the functions of input port 63 and output port 64 can be implemented using transceiver circuits or dedicated transceiver chips. Processor 61 can be implemented using dedicated processing chips, processing circuits, processors, or general-purpose chips.

[0279] As another implementation method, the network device provided in this application embodiment can be implemented using a general-purpose computer. The program code that implements the functions of processor 61, input port 63, and output port 64 is stored in memory 62, and the general-purpose processor implements the functions of processor 61, input port 63, and output port 64 by executing the code in memory 62.

[0280] In this embodiment of the application, the input port 63 is used to receive the address and interface identifier of the user plane function network element from the session management function network element;

[0281] The processor 61 is used by the first network element to determine the interface corresponding to the interface identifier based on the interface identifier.

[0282] The processor 61 is also used by the first network element to control the user plane function network element according to the address and interface identifier of the user plane function network element.

[0283] The output port 64 is used to send the message detection rules and message processing rules corresponding to the first network element to the user plane function network element. The first network element is a non-session management function type network element.

[0284] Optionally, the device 60 may be configured in or be itself a controller of a type other than SMF.

[0285] The functions and actions of each module or unit in the device 60 listed above are merely illustrative examples. Each module or unit in the device 60 can be used to perform the actions or processes performed by the network device in the above methods 300, 500 or 600. Here, to avoid redundancy, detailed descriptions are omitted.

[0286] For the concepts, explanations, detailed descriptions, and other steps related to the technical solutions provided in the embodiments of this application involved in the device 60, please refer to the descriptions of these contents in the foregoing methods or other embodiments, which will not be repeated here.

[0287] In one possible implementation, with the development of System-on-Chip (SoC) technology, all or part of the functions of device 60 are implemented by SoC technology, for example, by a network device function chip. This network device function chip integrates a processor, memory, communication interface, and other devices. The program for the network device-related functions is stored in the memory, and the processor executes the program to implement the base station's related functions. Optionally, the network device function chip can also read external memory to implement the base station's related functions.

[0288] It should be understood that Figure 12The structure of the example device 60 is merely one possible configuration and should not be construed as limiting the embodiments of this application. This application does not exclude the possibility of other base station structures in the future.

[0289] According to the method provided in the embodiments of this application, the embodiments of this application also provide a communication system, which includes at least one forwarding device and one or more network devices as described above.

[0290] It should be understood that in the embodiments of this application, the processor can be a central processing unit (CPU), or it can 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.

[0291] 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 RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0292] 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.

[0293] 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. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0294] 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.

[0295] It should also be understood that the terms "first" and "second" mentioned in this document are used only to distinguish the technical solutions of this application more clearly, and should not constitute any limitation on this application.

[0296] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0297] 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.

[0298] 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.

[0299] 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.

[0300] 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.

[0301] 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.

[0302] 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.

[0303] 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, include: The session management function network element obtains the interface identifier; The session management function network element sends the address of the user plane function network element and the interface identifier to the first network element. The interface identifier is used by the first network element to determine the interface corresponding to the interface identifier. The address is used by the first network element to send the packet detection rules and packet processing rules corresponding to the first network element to the user plane function network element. The interface corresponding to the interface identifier corresponds to the first network element. The interface corresponding to the interface identifier, the packet detection rules, and the packet processing rules are used by the first network element to control the user plane function network element.

2. The method as described in claim 1, characterized in that, The method further includes: The session management function network element sends first information to the user plane function network element, the first information being used to instruct the user plane function network element to allocate the interface identifier.

3. The method as described in claim 1 or 2, characterized in that, The session management function network element obtains the interface identifier, including: The session management function network element receives the interface identifier from the user plane function network element.

4. The method as described in claim 1, characterized in that, The method further includes: The session management function network element sends the interface identifier to the user plane function network element.

5. The method as described in claim 1 or 2, characterized in that, The method further includes: The session management function network element receives capability indication information from the user plane function network element. The capability indication information is used to indicate that the user plane function network element can be controlled by a first type of network element, which is a non-session management function type network element.

6. The method as described in claim 1 or 2, characterized in that, The method further includes: The session management function network element receives a request message from the first network element, and the request message is used to request control of the user plane function network element.

7. The method as described in claim 6, characterized in that, The request message includes at least one of the following information: the identifier of the user plane function network element, the service area, and the session identifier of the user equipment.

8. A communication method, characterized in that, include: The user plane function network element receives the message detection rules and message processing rules corresponding to the first network element from the first network element, where the first network element is a non-session management function type network element; The user plane function network element receives messages through the interface corresponding to the first network element; The user plane function network element detects the packet according to the packet detection rules and processes the packet according to the packet processing rules.

9. The method as described in claim 8, characterized in that, The method further includes: The user plane function network element receives first information from the session management function network element, the first information being used to instruct the user plane function network element to allocate an interface identifier for the interface.

10. The method as described in claim 8 or 9, characterized in that, The method further includes: The user plane function network element sends the interface identifier of the interface to the session management function network element.

11. The method as described in claim 8, characterized in that, The method further includes: The user plane function network element receives the interface identifier of the interface from the session management function network element.

12. The method as described in claim 8 or 9, characterized in that, The method further includes: The user plane function network element sends capability indication information to the session management function network element. The capability indication information is used to indicate that the user plane function network element can be controlled by a first type of network element, which is a non-session management function type network element.

13. A communication method, characterized in that, include: The first network element receives the address and interface identifier of the user plane function network element from the session management function network element; The first network element determines the interface corresponding to the interface identifier based on the interface identifier, and the interface corresponding to the interface identifier corresponds to the first network element; The first network element sends the packet detection rules and packet processing rules corresponding to the first network element to the user plane function network element based on the address. The first network element is a non-session management function type network element. The first network element controls the user plane function network element based on the interface corresponding to the interface identifier, the packet detection rules, and the packet processing rules.

14. The method as described in claim 13, characterized in that, The method further includes: The first network element sends a request message to the session management function network element, the request message being used to request the first network element to control the user plane function network element.

15. The method as described in claim 14, characterized in that, The request message includes at least one of the following information: The identifier of the user plane function network element, the service area, and the session identifier of the user equipment.

16. A network device, characterized in that, include: The processing unit is used to obtain the interface identifier; The transceiver unit is used to send the address of the user plane function network element and the interface identifier to the first network element. The interface identifier is used by the first network element to determine the interface corresponding to the interface identifier. The address is used by the first network element to send the packet detection rules and packet processing rules corresponding to the first network element to the user plane function network element. The interface corresponding to the interface identifier corresponds to the first network element. The interface corresponding to the interface identifier, the packet detection rules, and the packet processing rules are used by the first network element to control the user plane function network element.

17. The network device as described in claim 16, characterized in that, The transceiver unit is further configured to send first information to the user plane function network element, the first information being used to instruct the user plane function network element to allocate the interface identifier.

18. The network device as described in claim 16 or 17, characterized in that, The processing unit is used to receive the interface identifier from the user plane function network element through the transceiver unit.

19. The network device as described in claim 16, characterized in that, The transceiver unit is also used to send the interface identifier to the user plane function network element.

20. The network device as described in claim 16 or 17, characterized in that, The transceiver unit is further configured to receive capability indication information from the user plane function network element. The capability indication information is used to indicate that the user plane function network element can be controlled by a first type of network element, wherein the first type of network element is a non-session management function type network element.

21. The network device as described in claim 16 or 17, characterized in that, The transceiver unit is further configured to receive a request message from the first network element, the request message being used to request control of the user plane function network element.

22. The network device as described in claim 21, characterized in that, The request message includes at least one of the following information: the identifier of the user plane function network element, the service area, and the session identifier of the user equipment.

23. A network device, characterized in that, include: The transceiver unit is used to receive message detection rules and message processing rules corresponding to the first network element from the first network element, wherein the first network element is a non-session management function type network element; The transceiver unit is also configured to receive messages through an interface corresponding to the first network element; The processing unit is configured to detect the message according to the message detection rules and process the message according to the message processing rules.

24. The network device as described in claim 23, characterized in that, The transceiver unit is further configured to receive first information from the session management function network element, the first information being used to instruct the user plane function network element to allocate an interface identifier for the interface.

25. The network device as described in claim 23 or 24, characterized in that, The transceiver unit is also used to send the interface identifier of the interface to the session management function network element.

26. The network device as described in claim 23, characterized in that, The transceiver unit is also used to receive the interface identifier of the interface from the session management function network element.

27. The network device as described in claim 23 or 24, characterized in that, The transceiver unit is also used to send capability indication information to the session management function network element. The capability indication information is used to indicate that the user plane function network element can be controlled by a first type of network element, which is a non-session management function type network element.

28. A network device, characterized in that, include: The transceiver unit is used to receive the address and interface identifier of the user plane function network element from the session management function network element; The processing unit is configured to determine the interface corresponding to the interface identifier based on the interface identifier, wherein the interface corresponding to the interface identifier corresponds to the first network element; The transceiver unit is also configured to send, based on the address, the message detection rules and message processing rules corresponding to the first network element to the user plane function network element, wherein the first network element is a non-session management function type network element; The processing unit is also used to control the user plane function network element based on the interface corresponding to the interface identifier, the message detection rule, and the message processing rule.

29. The network device as described in claim 28, characterized in that, The transceiver unit is further configured to send a request message from the first network element to the session management function network element, the request message being used to request the first network element to control the user plane function network element.

30. The network device as described in claim 29, characterized in that, The request message includes at least one of the following information: The identifier of the user plane function network element, the service area, and the session identifier of the user equipment.

31. A communication system, characterized in that, include: The network device as described in any one of claims 16 to 22, 23 to 27, or 28 to 30.

32. A computer-readable storage medium, characterized in that, include: The computer-readable storage medium stores a computer program that, when executed, causes the computer to perform the method as described in any one of claims 1 to 7, 8 to 12, or 13 to 15.

33. A chip, characterized in that, include: A processor for retrieving and running a computer program from memory, causing a communication device on which the chip is mounted to perform the method as described in any one of claims 1 to 7, 8 to 12, or 13 to 15.

Images