WO2023185428A1

WO2023185428A1 - Method for reconstructing key service capability of user plane function network element, and communication apparatus

Info

Publication number: WO2023185428A1
Application number: PCT/CN2023/081007
Authority: WO
Inventors: 袁立平; 郭俊元; 胡彬
Original assignee: 华为技术有限公司
Priority date: 2022-03-26
Filing date: 2023-03-13
Publication date: 2023-10-05
Also published as: CN116867108A

Abstract

A method for reconstructing a key service capability of a user plane function (UPF) network element, and a communication apparatus. The method comprises: a UPF reporting algorithm operation information to an algorithm update network element, the algorithm referring to an algorithm used for matching a data packet with a PDR in the UPF; the algorithm update network element determining an updated algorithm or algorithm parameter according to the received algorithm operation information, and then notifying the UPF of the updated algorithm or algorithm parameter by means of algorithm indication information. According to the method in the present application, it is possible to perform online update of an algorithm or an algorithm parameter for an algorithm running in a UPF, according to data flow characteristics of the UPF, so as to achieve reconstruction of a key service capability of the UPF, optimize performance of the UPF in various forms, and improve an operation effect of the algorithm.

Description

A method and communication device for reconstructing key service capabilities of user plane functional network elements

Cross-references to related applications

This application requests the priority of the Chinese patent application submitted to the China Patent Office on March 26, 2022, with the application number 202210308229.6 and the application title "A method and communication device for reconstructing key service capabilities of user plane functional network elements", The entire contents of which are incorporated herein by reference.

Technical field

The present application relates to the field of wireless communication technology, and in particular, to a method and communication device for reconstructing key service capabilities of user plane functional network elements.

Background technique

In the 5G network, the user plane function (UPF) network element is mainly responsible for forwarding user data packets according to the rules configured by the session management function (SMF) network element, such as sending uplink data to the data network ( data network, DN) or other UPF, forwards downlink data to other UPF or wireless access network (radio access network, RAN) equipment.

When forwarding user data packets, the UPF network element will first match the packet detection rule (packet detection rule, PDR) rule, and then execute the forwarding action rule (FAR) corresponding to the selected PDR on the data packet, and perform quality of service After operations such as QoS enforcement rule (QER) and usage reporting rule (URR), the data packet is forwarded.

The key service capabilities of UPF network elements in supporting PDR rule matching are mainly implemented through algorithms. In the existing technology, all UPF network elements use the same algorithm to match PDR rules. Considering the different deployment forms and data characteristics of UPF network elements, the same algorithm cannot achieve the best results on all UPF network elements. If you want to update the algorithm in UPF network elements, you need to switch between software versions. , involving the reinstallation and startup of software. It can be seen that the methods in the existing technology cannot support the online reconstruction of key service capabilities of UPF network elements.

Contents of the invention

This application provides a method and communication device for reconstructing key service capabilities of user plane functional network elements, which are used to realize online updating and reconstruction of key service capabilities of user plane functional network elements and optimize the performance of user plane functional network elements.

In the first aspect, this application provides a method for reconstructing the key service capabilities of a user plane functional network element. This method can be executed by the user plane functional network element, or by components (such as chips or circuits) configured in the user plane functional network element. .

The method includes: a user plane functional network element reporting algorithm operation information to an algorithm update network element, where the algorithm operation information includes parameters collected by the user plane functional network element in the past period of time to characterize the operation of the algorithm, and the The algorithm is used to support the user plane functional network element to match packet detection rules PDR, and the parameters include data flow characteristics; the user plane functional network element receives algorithm update indication information from the algorithm update network element, and the algorithm updates The indication information is used to indicate the updated algorithm or algorithm parameters of the user plane functional network element.

In the technical solution in this application, the algorithm update unit can decide to update the algorithm based on the algorithm operation information reported by the user plane functional network element, such as updating the algorithm parameters or replacing it with a new algorithm, and informs the UPF of the updated algorithm or algorithm. method parameters to support online update of the UPF algorithm. This method can optimize the performance of various forms of UPF and improve the algorithm operation effect.

In a possible design, the method further includes: the user plane functional network element receiving algorithm collection configuration information from the algorithm update network element. The algorithm collection configuration information includes: algorithm type, algorithm instance number, Collect parameters and collection intervals; the user plane functional network element collects configuration information according to the algorithm and determines the algorithm running information.

In the technical solution of this application, the algorithm update network element can instruct the user plane functional network element the rules for collecting algorithm operation information in the above manner.

In a possible design, the method further includes: the user plane functional network element reporting algorithm update capability information to the algorithm update network element, where the algorithm update capability information is used to indicate to the user plane functional network element Support algorithm online update.

In a possible design, the algorithm update capability information includes: algorithm type, algorithm instance number, supported algorithm list, algorithm parameters that support adjustment, and supported collection parameters.

In the technical solution of this application, the user plane functional network element can inform the algorithm update network element through the above method before executing the algorithm online update, which supports the algorithm online update, thus triggering subsequent processing procedures.

In a possible design, when the algorithm type is a hash algorithm; the supported algorithm list includes one or more of MurmurHash, CRC32, FNV, and SIPHash; the supported collection parameters include loading factor, Conflict rate and data flow characteristics; the algorithm parameters that support adjustment include bucket size.

In a possible design, when the algorithm type is a tuple space search TSS algorithm; the supported algorithm list includes cutTSS and/or mergeTSS; the supported collection parameters include the number of tuples, tuple hit rate and Data flow characteristics; the algorithm parameters that support adjustment include tuple upper limit and tuple division rules.

The technical solution of this application can support two algorithm types: hash algorithm and TSS algorithm, and provides a specific implementation plan for online updating of algorithms corresponding to these two algorithm types, such as reporting algorithm operation information on the user plane functional network element side. When the user plane functional network element supports collection parameters and algorithm parameters that support adjustment are respectively set for these two algorithm types.

In a possible design, the data flow characteristics include source address, destination address, source port, destination port, flow service quality identifier, tunnel identifier, protocol identifier, and uniform resource location address.

In a possible design, the method further includes: applying the AB method to the user plane functional network element to install the updated algorithm or algorithm parameters.

In the technical solution of this application, the user plane functional network element uses the AB method to install the updated algorithm or algorithm parameters, which can effectively ensure the normal operation of the data forwarding service in the user plane functional network element and avoid service interruption during the online update of the algorithm. .

In a possible design, the algorithm update network element is a session management function network element or a network data analysis function network element or an operation and maintenance network element.

In the second aspect, this application provides a method for reconstructing key service capabilities of a user plane functional network element. This method can be executed by an algorithm update network element, or by a component (such as a chip or circuit) configured in an algorithm update network element. The algorithm update network element can be a computing unit deployed in other core network elements except the user plane functional network element, such as the voice management functional network element or the network data analysis functional network element, or it can be deployed in the management plane network An element is a computing unit in operation and maintenance OAM, or it can be an independently deployed core network element.

The method includes: an algorithm update network element receives algorithm operation information from a user plane functional network element, where the algorithm operation information includes parameters collected by the user plane functional network element in the past period of time to characterize the operation of the algorithm, so The algorithm is used to support the user plane function network element to match the packet detection rule PDR, and the parameters include data flow characteristics; the algorithm updates the algorithm or algorithm parameters after the network element makes decisions based on the algorithm operation information; the algorithm The updating network element sends algorithm update indication information to the user plane functional network element, where the algorithm update indication information is used to indicate the updated algorithm or algorithm parameters of the user plane functional network element.

In a possible design, the method further includes: the algorithm update network element sending algorithm collection configuration information to the user plane functional network element. The algorithm collection configuration information includes: algorithm type, algorithm instance number, collection Parameters and collection intervals.

In a possible design, the method further includes: the algorithm update network element receiving algorithm update capability information from the user plane function network element, where the algorithm update capability information is used to indicate that the user plane function network element Meta support algorithm is updated online.

In a possible design, when the algorithm type is the tuple space search TSS algorithm; the supported algorithm list includes cutTSS, mergeTSS; the supported collection parameters include the number of tuples, tuple hit rate and data flow Features: The algorithm parameters that support adjustment include tuple upper limit, tuple division rules, etc.

For the technical effects of any possible design in the second aspect, please refer to the corresponding description in the first aspect and will not be repeated again.

In the third aspect, embodiments of the present application provide a communication device. The communication device may have the function of implementing the user plane function network element or the algorithm update network element in the above aspects. The communication device may be a network device or a network device. chip included.

The functions of the above communication device can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules or units or means corresponding to the above functions.

In a possible design, the structure of the communication device includes a processing module and a transceiver module, wherein the processing module is configured to support the communication device to perform functions corresponding to the user plane functional network elements in the above aspects, or to perform the above functions. The algorithm in this aspect updates the corresponding functions of the network element. The transceiver module is used to support communication between the communication device and other communication equipment. For example, when the communication device is a user plane functional network element, it can send algorithm running information to the algorithm update network element. The communication device may also include a storage module, which is coupled to the processing module and stores necessary program instructions and data for the communication device. As an example, the processing module can be a processor, the communication module can be a transceiver, and the storage module can be a memory. The memory can be integrated with the processor, or can be provided separately from the processor.

In another possible design, the structure of the communication device includes a processor and may also include a memory. The processor is coupled to the memory and can be used to execute computer program instructions stored in the memory, so that the communication device performs the methods in the above aspects. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface. When the communication device is a network device, the communication interface may be a transceiver or an input/output interface; when the communication device is a network device When a chip is included, the communication interface may be the chip's input/output interface. Alternatively, the transceiver may be a transceiver circuit, and the input/output interface may be an input/output circuit.

In a fourth aspect, embodiments of the present application provide a chip system, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the program or instructions are executed by the processor , so that the chip system implements the methods in the above aspects.

Optionally, the chip system further includes an interface circuit for exchanging code instructions to the processor.

Optionally, there may be one or more processors in the chip system, and the processor may be implemented by hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in memory.

Optionally, there may be one or more memories in the chip system. The memory can be integrated with the processor or can be provided separately from the processor. For example, the memory may be a non-transient processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip, or may be separately provided on different chips.

In a fifth aspect, embodiments of the present application provide a computer-readable storage medium on which a computer program or instructions are stored. When the computer program or instructions are executed, the communication device causes the communication device to perform the above aspects or any one of the aspects. methods in possible designs.

In a sixth aspect, embodiments of the present application provide a computer program product. When a communication device executes the computer program product, the communication device causes the communication device to execute the method in any of the above aspects or any possible design of the aspects.

In a seventh aspect, embodiments of the present application provide a communication system, which includes a user plane functional network element and an intermediate algorithm update network element.

Description of drawings

Figure 1 is a schematic diagram of a system architecture applicable to the embodiment of the present application;

Figure 2 is a schematic diagram of a specific system architecture applicable to the embodiment of the present application;

Figure 3 is a schematic diagram of the data flow processing flow in the UPF network element in the embodiment of the present application;

Figure 4 is a schematic diagram of the deployment form of UPF network elements in the embodiment of the present application;

Figure 5 is a schematic flowchart of a method for reconstructing key service capabilities of user plane functional network elements provided by an embodiment of the present application;

Figure 6 is a schematic flow chart of Example 1 provided by the embodiment of the present application;

Figure 7 is a schematic flow chart of Example 2 provided by the embodiment of the present application;

Figure 8 is a schematic flow chart of Example 3 provided by the embodiment of this application;

Figure 9 is a schematic diagram of the architecture and processing flow of reconstructing the key service capabilities of UPF network elements provided by the embodiment of the present application;

Figures 10 and 11 are schematic structural diagrams of a communication device provided by embodiments of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application.

The technical solutions in the embodiments of this application can be applied to a variety of communication systems, such as fifth generation (5th generation, 5G) mobile communication systems or new radio (new radio, NR) systems, or to future communication systems or other Similar communication systems, etc.

Figure 1 exemplarily shows a schematic diagram of a system architecture applicable to the embodiment of the present application. The system architecture is specifically a 5G system architecture. As shown in Figure 1, the system architecture includes terminal equipment, access network (AN), core network (Core) and data network (DN). Among them, the access network may be a radio access network (radio access network, RAN). In this system architecture, terminal equipment, AN and Core are the main parts of the system architecture. For network elements in AN and Core, they can be logically divided into two parts: the user plane and the control plane. The control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of business data. For example, in the system architecture shown in Figure 1, the NG2 reference point is located between the RAN control plane and the Core control plane, the NG3 reference point is located between the RAN user plane and the Core user plane, and the NG6 reference point is located between the Core user plane and the DN. between.

Among them, the terminal device is a device with wireless transceiver function. It is the entrance for mobile users to interact with the network. It can provide basic computing capabilities and storage capabilities, display business windows to users, and accept user operation inputs. In the 5G network, terminal equipment can use new radio (NR) technology to establish signal connections and data connections with the AN, thereby transmitting control signals and business data to the network.

Specifically, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons, satellites, etc.). The terminal device may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, an industrial control ( Wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and transportation safety Wireless terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc. The embodiments of this application do not limit application scenarios. Terminal equipment may sometimes also be called user equipment (UE), mobile station, remote station, etc. The embodiments of this application do not limit the specific technology, equipment form, and name used by the terminal equipment.

AN equipment can be deployed in the AN. The AN equipment can be deployed close to the terminal equipment to provide network access functions for authorized users in a specific area, and can determine transmission tunnels of different qualities to transmit user data according to the user's level, business needs, etc. . AN equipment can manage and rationally utilize its own resources, provide access services to terminal equipment on demand, and is responsible for forwarding control signals and business data between terminal equipment and the Core.

Specifically, possible deployment forms of AN equipment include: separation scenarios of centralized units (CU) and distributed units (DU), as well as single-site scenarios. Among them, in the separation scenario, CU supports protocols such as radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP); DU Mainly supports wireless link control layer (radio link control, RLC), media access control layer (media access control, MAC) and physical layer protocols. In a single-site scenario, a single site can include (new radio Node, gNB), evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB) , base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station, base band unit (base band unit, BBU), etc.

Core is responsible for maintaining mobile network subscription data, managing mobile network network elements, and providing terminal devices with functions such as session management, mobility management, policy management, and security authentication. For example, when the terminal device is attached, network access authentication is provided for the terminal device; when the terminal device has a service request, network resources are allocated to the terminal device; when the terminal device moves, network resources are updated for the terminal device; when the terminal device is idle time, providing a quick recovery mechanism for terminal equipment; When the terminal device detaches, network resources are released for the terminal device; when the terminal device has service data, it provides data routing functions for the terminal device, such as forwarding uplink data to the DN, or receiving downlink data from the DN and forwarding it to the AN.

DN is a data network that provides business services to users. In the actual communication process, the client is usually located in the terminal device and the server is located in the DN. DN can be a private network (such as a local area network), an external network not controlled by the operator (such as the Internet), or a proprietary network jointly deployed by the operator (such as an IP multimedia core network). subsystem, IMS) service network).

FIG. 2 is a schematic diagram of a specific system architecture applicable to the embodiment of the present application. This system architecture further refines the core network based on the system architecture shown in FIG. 1 . As shown in Figure 2, the system architecture includes terminal equipment, AN equipment, core network elements and DN. Among them, the core network can be divided into the core network user plane and the core network control plane. Specifically, the core network user plane includes user plane function (UPF) network elements; the core network control plane includes but is not limited to: access and mobility management function (AMF) network elements, Session management function (SMF) network element, authentication server function (AUSF), policy control function (PCF) network element, network slice selection function (NSSF) network Element, network exposure function (NEF) network element, network function repository function (NF repository function, NRF) network element, unified data management (UDM) network element, application function (AF) network element.

In the traditional core network architecture, point-to-point communication is used between control plane network elements. That is, the interface communication between control plane network elements uses a specific set of messages. The control plane network elements at both ends of the interface can only use this specific set of messages. messages to communicate. In the 5G core network architecture, the control plane network elements adopt a service-oriented architecture, that is, the interaction between the control plane network elements adopts the method of service invocation. The control plane network elements will open services to other control plane network elements for other control Network element call.

The above network elements are introduced in detail below respectively. For the relevant introduction of terminal equipment, AN equipment and DN, please refer to the description in Figure 1.

AMF network element: Mainly responsible for access management and mobility management of terminal equipment, such as status maintenance of terminal equipment, reachability management of terminal equipment, and non-mobility management access layer (mobility management non-access-stratum, MM) NAS) message forwarding, session management (session management, SM) N2 message forwarding.

SMF network element: Mainly used for session management of terminal equipment, such as session establishment, modification, and release, and allocating resources for sessions of terminal equipment. Among them, the resources may include session quality of service QoS, session path, forwarding rules, etc.

UPF network element: Mainly responsible for connecting to external networks. It can forward user data packets according to the routing rules of the SMF network element. For example, uplink data is sent to DN or other UPF network elements; downlink data is forwarded to other UPF network elements or AN equipment.

AUSF network element: Mainly responsible for performing security authentication of terminal equipment.

PCF network element: Mainly responsible for user policy management, such as policy authorization, service quality and billing rule generation, and delivers the corresponding rules to the UPF network element through the SMF network element to install the corresponding policies and rules.

NSSF network element: Mainly responsible for selecting appropriate network slices for terminal equipment services.

NEF network element: Exposes some network functions to applications in a controlled manner, such as opening network functions to third parties in the form of northbound API interfaces.

NRF network element: Provides storage and selection functions for network function entity information for other network elements.

UDM network element: mainly responsible for context management of user subscriptions. UDM network elements can be implemented by interacting with unified data repository (UDR) network elements to realize their functions. UDR network elements are used to store the data required when UDM network elements perform their operations. The UDM network element and the UDR network element can be two independent physical entities, or UDR network elements can also be integrated into UDM network elements, which is not specifically limited in this application.

AF network element: Mainly responsible for application management, such as providing service data of various applications to the control plane network element of the operator's communication network, or obtaining network data information and control information from the control plane network element of the communication network.

It should be noted that the network elements described in the embodiments of this application may be network elements in hardware devices, or may be functionally divided software (such as virtualization functions instantiated on a cloud platform), or both of the above. Combined structures (such as software functions running on specialized hardware). The network elements described in the embodiments of this application may also be called functional entities. For example, the policy control network elements may also be called policy control functional entities. The names of each network element are not limited in the embodiments of this application. Those skilled in the art can replace the names of the above network elements with other names to perform the same function. The network element described in the embodiments of this application can be implemented by one device, or can be implemented by multiple devices, or it can be a functional module in one device, which is not specifically limited in the embodiments of this application.

The system architecture and business scenarios described in the embodiments of this application are for the purpose of explaining the technical solutions of the embodiments of this application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art will know that with the communication With the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

The technical solutions in the embodiments of this application mainly involve the key service capabilities of the UPF network element. The key service capabilities refer to the UPF network element matching the corresponding packet detection rule (PDR) rules for the received data packets. ability.

Figure 3 exemplarily shows the data flow processing process in the UPF network element. As shown in Figure 3, the SMF network element can deliver session rules, such as PDR and forwarding behavior rules, to the UPF network element through the N4 interface. forwarding action rule (FAR), QoS enforcement rule (QoS enforcement rule, QER), usage reporting rule (URR), etc. Since the UPF network element supports rule-based packet forwarding, after the UPF network element receives the data packet, the UPF network element can first transfer the data flow characteristics (such as source address, destination address, source port, destination port, flow service quality identifier, Tunnel identification, protocol identification, uniform resource location address, etc.) are matched with the PDR, and then the PDR with the highest priority is selected from the matching PDRs as the final selected PDR, and the FAR, QER, and URR corresponding to the selected PDR are executed on the data packet. After the operation, the data packet is forwarded.

The key service capabilities of UPF network elements to support PDR matching are mainly implemented through algorithms, such as hash algorithms, tuple space search (TSS) algorithms, etc. The effect depends on the algorithm and data flow characteristics. The specific parameters describing the effect can be are storage consumption and search time. The algorithms mentioned below in this application are all PDR matching algorithms.

For example, the hash algorithm performs hash calculation on the input data through a hash function to obtain a hash value, and then finds the bucket location through the hash value. When the hash values are the same and the same bucket is found, It will be hung on the bucket in the form of a slot chain; the ratio of the used buckets to the total number of buckets is called the load factor, and the slot chain is called a conflict. What we hope is that the load factor is as high as possible, and conflicts As few as possible, so that the search time will be short enough and the storage consumption will be small enough. From the description of the above principles, it can be seen that the combination of data flow characteristics (such as source/destination addresses, etc.) and hash algorithm (and parameters) will affect the final storage consumption and search time. In pursuit of the best performance, hash algorithms are constantly optimized, and a variety of hash algorithms have been produced for different data flow characteristics, such as MurMurHash, CRC32, FNV (Fowler–Noll–Vo), SIPhash, etc. The effect of the TSS algorithm is also related to the data flow characteristics and the algorithm (and parameters), so a variety of algorithms have emerged, such as cutTSS, MergeTSS, etc.

With the development of 5G communication technology, UPF network elements have appeared in various forms, such as regional UPF network elements and edge UPF network elements. As shown in Figure 4, the coverage range of regional UPF network elements is larger, while the coverage range of edge UPF network elements is smaller. area UPF network elements are deployed inside the core network, connected to the Internet, and used to forward traffic from terminal devices accessing the Internet. The edge UPF network element is deployed at the edge of the network and connected to the local network. It is used to locally divert the traffic of terminal devices accessing the local network, such as the traffic accessing the content delivery network (content delivery network, CDN) or local application (APP). The data flow characteristics of regional UPF network elements and edge UPF network elements are different. For example, there are many types of data in the traffic accessing the Internet, and the characteristics are discrete; while for CDN/APP, there are few types of data, and the characteristics can be divided into several categories. In addition, different edge UPF network elements will have different data flow characteristics due to regional characteristics.

In view of this, it is understandable that the same algorithm cannot achieve optimal results on all UPF network elements. A method is needed that can support different forms of UPF network elements to adopt algorithms (and parameters) suitable for their data flow characteristics to improve the performance of UPF network elements and learn and change the key service capabilities of UPF network elements online.

In order to solve the problem in the prior art that UPF network elements use the same PDR matching algorithm, and updating the PDR matching algorithm in UPF network elements requires switching between software versions, which may cause service interruption of UPF network elements, embodiments of this application provide a A method for reconstructing the key service capabilities of user plane functional network elements. This method can update the PDR matching algorithm or algorithm parameters applied in UPF network elements online, so that the key service capabilities of UPF network elements can be reconstructed, thereby realizing various The performance of various forms of UPF network elements is optimized to improve the algorithm operation effect.

Figure 5 exemplarily shows a flowchart of a method for reconstructing key service capabilities of user plane functional network elements provided by an embodiment of the present application. As shown in Figure 5, the method includes:

Step 501: The UPF network element reports algorithm update capability information to the algorithm update network element. The algorithm update capability information is used to indicate that the UPF network element supports algorithm online update.

The algorithm update capability information may include algorithm type, algorithm instance number, supported algorithm list, algorithm parameters that support adjustment, supported collection parameters, etc.

The algorithm update capability information may indicate the UPF network element to support algorithm online update in an explicit or implicit manner. The explicit indication method means that the algorithm update capability information includes indication information for instructing the UPF network element to support algorithm online update, for example, it can be a flag bit additionally included in the algorithm update capability information; the implicit The indication method means that when the UPF network element sends the above algorithm update capability information, it means that the UPF network element supports algorithm online update. That is, when the algorithm update network element receives the above algorithm update capability information from the UPF network element, the algorithm update network element will It can be considered that the UPF network element supports online update of the algorithm. In this application, the online update of the algorithm may include an online update of the algorithm or an online update of the algorithm parameters.

The algorithm type may be a hash algorithm or a TSS algorithm.

For example, for the hash algorithm, the algorithm type is the hash algorithm, and the algorithm instance number is 0x0001; the algorithm list supported by the UPF network element may include one or more of MurmurHash, CRC32, FNV, and SIPHash; the UPF network element supports The adjusted algorithm parameters may include bucket size; the collection parameters supported by UPF network elements may include loading factor, conflict rate and data flow characteristics.

For the TSS algorithm, the algorithm type is the TSS algorithm, and the algorithm instance number is 0x0001; the algorithm list supported by the UPF network element includes cutTSS and/or mergeTSS; the algorithm parameters supported by the UPF network element include the tuple upper limit and tuple division rules; the UPF network element supports The collection parameters include the number of tuples, tuple hit rate and data flow characteristics.

The algorithm update network element may be an SMF network element, a NWDAF network element, an OAM network element, or a functional module located in the above network element, which is not specifically limited in this application. If the algorithm update network element is an SMF network element or an OAM network element, the UPF network element can directly send the algorithm update capability information to the SMF network element or OAM network element; if the algorithm update network element is a NWDAF network element, the UPF network element can directly send the algorithm update capability information to the SMF network element or OAM network element. The SMF network element sends the algorithm update capability information, and then forwards the algorithm update capability information to the NWDAF network element through the SMF network element. Similarly, in the following steps 502-505, if the algorithm is updated If the network element is an NWDAF network element, the UPF network element can interact with the NWDAF network element through the forwarding of the SMF network element, and transmit information such as algorithm collection configuration information, algorithm running information, algorithm update instruction information, etc.

Step 502: The algorithm update network element sends algorithm collection configuration information to the UPF network element. The algorithm collection configuration information includes: algorithm type, algorithm instance number, collection parameters, and collection interval.

The algorithm collection configuration information is used to indicate the collection rules of the UPF network element algorithm operation information, that is, to collect some parameters of the operation process of the specified algorithm instance at specified time intervals. The collection parameters are a set of parameters that the algorithm update network element requires the UPF network element to collect, and can also be called parameters to be collected. The parameters to be collected can be some or all of the supported collection parameters reported by the UPF network element. , is not limited. The collection interval may also be a collection frequency. For example, the UPF network element may be instructed to collect and report data flow characteristics once every hour. In this way, the UPF network element can collect configuration information based on the algorithm and obtain the algorithm operation information that needs to be reported.

Step 503: The UPF network element reports algorithm operation information to the algorithm update network element. The algorithm operation information includes parameters collected by the UPF network element in the past period of time to characterize the operation of the algorithm. The algorithm is used to support the UPF network element. Matching packet detection rules PDR, the parameters include data flow characteristics.

The parameters are the collection parameters indicated by the algorithm update network element to the UPF network element in step 502. For the hash algorithm, the parameters may also include the loading factor and the conflict rate; for the TSS algorithm, the parameters may also include the number of tuples and the tuple hit rate.

In this application, the data flow characteristics refer to one or more of the source address, destination address, source port, destination port, flow service quality identifier, tunnel identifier, protocol identifier, and unified resource location address.

Step 504: The algorithm update network element decides on the updated algorithm or algorithm parameters based on the received algorithm operation information.

In this application, updating the algorithm refers to replacing a new algorithm for PDR matching, and updating algorithm parameters refers to adjusting some parameters of the currently used algorithm. Optionally, the algorithm update network element can only update between algorithms of the same type when deciding to update the algorithm. For example, if a certain hash algorithm is currently running on the UPF network element, the updated algorithm can be another hash algorithm. The TSS algorithm is similar to this.

For example, for the hash algorithm, the algorithm update network element can calculate the impact of higher loading factors and smaller conflict rates corresponding to data flow characteristics based on the received loading factors, conflict rates and data flow characteristics within a period of time. parameters and better algorithms, and then combine historical data and operating data of other UPF network elements to select optimal algorithm parameters (such as bucket size) or other hash algorithms from multiple results.

For the TSS algorithm, the algorithm update network element can calculate the impact of better tuple division and better algorithm based on the number of tuples received, tuple hit rate and data flow characteristics, and combine historical data and the operation data of other UPF network elements to derive Select the optimal parameters (such as tuple division) or other TSS algorithms from multiple results.

Step 505: The algorithm update network element sends algorithm update indication information to the UPF network element. The algorithm update indication information is used to indicate the updated algorithm or algorithm parameters of the UPF network element.

Step 506: The UPF network element installs the updated algorithm or algorithm parameters.

In a possible design, the UPF network element can apply the AB method to install the updated algorithm or algorithm parameters. For example, the original algorithm generates table A, and the operating data is also in table A. The new algorithm or the algorithm that updates parameters generates table B, and the operating data is migrated to table B one by one or in batches. For the new data flow characteristics, in A and B The tables are inserted at the same time. When the migration is completed, table AB is switched and table B is switched to the currently used data table.

After the new algorithm or new parameters of the UPF network element take effect, the UPF network element can execute the new algorithm operation data collection process.

The technical solutions provided by the embodiments of this application are specifically described below through several examples.

Example 1

In Example 1, the hash algorithm is used as an example to illustrate the process of UPF reconstructing key service capabilities through the N4 interface. In this example 1, the algorithm update network element is a functional module in SMF or NWDAF, which can be recorded as a computing unit.

As shown in Figure 6, it includes the following steps:

Step 601: UPF reports the support algorithm online update capability to SMF through the packet filter control protocol (PFCP) connection establishment or update process (PFCP Association Setup Procedure or PFCP Association Update Procedure) of the N4 interface, such as reporting algorithm type, Algorithm instance number, supported algorithm list, algorithm parameters that support adjustment, supported collection parameters and other information. Take the hash algorithm as an example. The algorithm type is hash algorithm and the algorithm instance number is 0x0001. The supported algorithm list can include MurmurHash, CRC32, FNV, SIPHash and other algorithms. The supported collection parameters can include loading factor, conflict rate and data flow. Features etc.

Step 601-a, if the computing unit is in NWDAF, SMF can send the above algorithm online update capability to NWDAF through analysis information request (Nnwdaf_AnalyticsInfo_Request).

Step 602: SMF sets the algorithm type, algorithm instance number, parameters to be collected, and reporting interval/frequency through the PFCP connection establishment or update process (PFCP Association Setup Procedure or PFCP Association Update Procedure) of the N4 interface. Taking the hash function as an example, the algorithm type is hash algorithm, the algorithm instance number is 0x0001, and the parameters to be collected, such as data flow characteristics, are reported every hour.

Step 603: UPF reports algorithm running information through the PFCP Session Report Request of the N4 interface. The algorithm running information includes the collected information.

After SMF receives the algorithm running information reported by UPF within a period of time, it can calculate the adjustable parameters or select a new algorithm based on the algorithm running information; taking the hash algorithm as an example, SMF will calculate the adjustable parameters or select a new algorithm based on the received loading factor, conflict rate and data. Flow characteristics, calculate parameters and better algorithms that affect higher load factors and smaller conflict rates corresponding to data flow characteristics, combine historical data and other UPF operating data, and select optimal parameters from multiple results (such as bucket size) or choose another hashing algorithm.

Step 603-a, if the computing unit is in NWDAF, SMF sends the above algorithm running information to NWDAF through analysis information request (Nnwdaf_AnalyticsInfo_Request), and NWDAF decides on the new algorithm or algorithm parameters, and then returns the decision result to SMF.

Step 604: SMF sends an update instruction to UPF through the PFCP Association Update Procedure of the N4 interface, and sets the updated algorithm type, algorithm instance number, and algorithm parameters through the update instruction.

After UPF receives the instruction message from SMF, UPF can use the AB method to install a new algorithm or update algorithm parameters, and complete the migration of original data.

In this example 1, UPF reports algorithm running information through the N4 interface and uses an external computing unit to update algorithm parameters or new algorithms, which can realize the reconstruction of UPF's key service capabilities.

Example 2

In Example 2, the hash algorithm is used as an example to illustrate the process of UPF reconstructing key service capabilities through the O&M interface. In this second example, the algorithm update network element is a functional module in O&M and can be recorded as a computing unit.

As shown in Figure 7, it includes the following steps:

Step 701: UPF reports the supported algorithm online update capability to O&M through O&M's MIB interface or yang model interface, such as reporting algorithm type, algorithm instance number, supported algorithm list, supported adjustable algorithm parameters, supported collection parameters and other information. Take the hash algorithm as an example. The algorithm type is hash algorithm and the algorithm instance number is 0x0001. The supported algorithm list can include MurmurHash, CRC32, FNV, SIPHash and other algorithms, and the supported collection parameters can include loading factors, conflict rates and data flow characteristics.

Step 702: O&M issues algorithm collection information through the interface between UPF and O&M, and sets the algorithm type, algorithm instance number, parameters to be collected, and reporting interval/frequency. Taking the hash function as an example, the algorithm type is hash algorithm, the algorithm instance number is 0x0001, and the parameters to be collected, such as data flow characteristics, are reported every hour.

Step 703: UPF reports algorithm running information through the interface with O&M. The algorithm running information includes the collected information.

After O&M receives the algorithm operation information reported by UPF within a period of time, it can calculate the adjustable parameters or select a new algorithm based on the algorithm operation information. Taking the hash algorithm as an example, O&M calculates parameters and better algorithms that affect higher load factors and smaller conflict rates corresponding to data flow characteristics based on the received load factors, conflict rates, and data flow characteristics, combined with historical data. and other UPF running data, select optimal parameters (such as bucket size) from multiple results or select other hashing algorithms.

Step 704: O&M issues algorithm update parameters or new algorithms through the interface with UPF, including, for example, the updated algorithm type, algorithm instance number, algorithm parameters, etc. After UPF receives the message from O&M, it can use the AB method to install a new algorithm or update the algorithm parameters, and complete the migration of the original data.

In this second example, UPF reports algorithm running information through the O&M interface and uses an external computing unit to update algorithm parameters or new algorithms, which can realize the reconstruction of UPF's key service capabilities.

Example three

In Example 3, the TSS algorithm is used as an example to illustrate the process of UPF reconstructing key service capabilities through service-oriented interfaces. In this example three, the algorithm update network element is a functional module in SMF or NWDAF, which can be recorded as a computing unit.

As shown in Figure 8, it includes the following steps:

Step 801: UPF as a producer reports its supported algorithm online update capabilities to NRF through the Nnrf_Nfmanagement service through the service interface, such as reporting algorithm type, algorithm instance number, supported algorithm list, supported algorithm parameters for adjustment, supported collection parameters, etc. information. Take the TSS algorithm as an example. The algorithm type is the TSS algorithm, and the algorithm instance number is 0x0001. The supported algorithm list can include cutTSS, mergeTSS and other algorithms. The supported parameters for adjustment can include the upper limit of tuples and tuple division rules. The supported collection parameters can include tuples. Quantity, tuple hit rate and data flow characteristics, etc.

Step 802: SMF/NWDAF as a consumer obtains a UPF that can provide services from NRF through the network function discovery (Nnrf_NFDiscovery) process.

Step 803: SMF/NWDAF delivers algorithm collection information through the service interface (such as Nupf_CapabilityManagement), and sets the algorithm type, algorithm instance number, parameters to be collected, and reporting interval/frequency. Taking the TSS algorithm as an example, the algorithm type is TSS algorithm, the algorithm instance number is 0x0001, and the parameters to be collected, such as data flow characteristics, are reported every hour.

Step 804: UPF reports algorithm running information to SMF/NWDAF through Nupf_EventExposure of the service interface. The algorithm running information contains the collected information.

After SMF/NWDAF receives the algorithm running information reported by UPF within a period of time, it can calculate the adjustable parameters or select a new algorithm based on the algorithm running information. Taking the TSS algorithm as an example, SMF/NWDAF calculates the adjustable parameters or selects a new algorithm based on the number of tuples received. Hit rate and data flow characteristics are estimated to influence better tuple division and better algorithms, combined with historical data. According to the operation data of other UPF, select the optimal parameters (such as tuple partition) from multiple results or choose other TSS algorithms.

Step 805: SMF/NWDAF issues algorithm update parameters or new algorithms through Nupf_CapabilityManagement of the service interface, and sets the updated algorithm type, algorithm instance number, and algorithm parameters.

After receiving the setting message, UPF uses the AB method to install a new algorithm or update the algorithm parameters, and completes the migration of the original data.

In this embodiment, the UPF's key service capabilities are reconstructed by reporting through the service interface UPF and using an external computing unit to update the parameters of the algorithm or a new algorithm.

As shown in Figure 9, in order to realize the reconstruction of the key service capabilities of the algorithm in UPF, the processing flow needs to be improved in both UPF and algorithm update network elements. Taking the algorithm update network element as the functional module-computing unit in O&M/SMF/NWDAF as an example, the UPF and computing unit in this application may include the following software architecture.

UPF includes three functional modules: algorithm management, algorithm execution and data collection. Among them, algorithm management mainly performs the allocation of algorithm instances, management of algorithm parameters, and instantiation of algorithms; algorithm execution mainly performs the operation management and switching of algorithms; data collection mainly performs collection and collection of operating parameters of different instances based on collection parameters. request reporting;

The computing unit includes functional modules such as algorithm analysis, algorithm simulation, algorithm library, data collection, algorithm decision-making and historical data. Among them, algorithm analysis mainly receives operating parameters through data collection, obtains new algorithms or algorithm updated parameters from algorithm simulation, and submits the results of simulation operations to algorithm decision-making; algorithm decision-making is based on the results of algorithm analysis, from the algorithm library and historical data. Obtain algorithms or parameters that better match the simulation running results to make decisions, and send the decision results to UPF for execution.

To sum up, in the context of UPF distribution, the data characteristics of UPF service objects are ever-changing, and the effect of a single algorithm is limited. Therefore, it is necessary to support the online effect of algorithms oriented to data characteristics, which requires learning, training and updating. To find algorithm parameters or effective algorithms. Based on this, this application provides an algorithm online learning and updating method that supports UPF key service capabilities, supports the above application scenarios, can effectively improve algorithm efficiency, and change the effectiveness of UPF services.

Specifically, this application uses UPF to report to the external algorithm update network element the results of a key algorithm instance processing the data flow for a period of time, that is, the algorithm running information, which is used to represent the effect of the algorithm on the data flow characteristics. The algorithm update network element performs algorithm analysis on the algorithm operation information reported by UPF. Based on the algorithm operation information, combined with historical data and other UPF operation effects, it makes decisions to update the algorithm, such as updating algorithm parameters or replacing new algorithms. This enables UPF to support algorithm online updates. This method can optimize performance for UPFs of different UPF forms and improve algorithm operation effects.

An embodiment of the present application also provides a communication device. Please refer to FIG. 10 , which is a schematic structural diagram of a communication device provided by an embodiment of the present application. The communication device 1000 includes: a transceiver module 1010 and a processing module 1020. The communication device can be used to implement the functions of the user plane function network element or the algorithm update network element in any of the above method embodiments.

The communication device may be a network device, or a device (such as a chip included in the network device) that can support the network device to implement the corresponding functions in the above method embodiment.

Exemplarily, when the communication device performs the operations or steps corresponding to the user plane function network element in the method embodiment shown in Figure 5, the transceiver module 1010 is used to report algorithm operation information to the algorithm update network element. The algorithm The operation information includes parameters collected by the user plane functional network element in the past period of time to characterize the operation of the algorithm. The method is used to support the user plane function network element matching packet detection rule PDR, and the parameters include data flow characteristics; the transceiver module 1010 is also used to receive algorithm update instruction information from the algorithm update network element, the The algorithm update indication information is used to indicate the updated algorithm or algorithm parameters of the user plane functional network element.

In a possible design, the transceiver module 1010 is also used to receive algorithm collection configuration information from the algorithm update network element. The algorithm collection configuration information includes: algorithm type, algorithm instance number, collection parameters and collection parameters. interval; the processing module 1020 is used to collect configuration information according to the algorithm and determine the algorithm running information.

In a possible design, the transceiver module 1010 is also configured to report algorithm update capability information to the algorithm update network element. The algorithm update capability information is used to indicate that the user plane function network element supports algorithm online update. .

In a possible design, the processing module 1020 is also used to install the updated algorithm or algorithm parameters using the AB method.

When the communication device performs operations or steps corresponding to the algorithm update network element in the method embodiment shown in Figure 5, the transceiver module 1010 is used to receive algorithm operation information from the user plane functional network element. The algorithm operation information includes Parameters collected by the user plane functional network element in the past period of time to characterize the operation of the algorithm. The algorithm is used to support the user plane functional network element to match the packet detection rule PDR. The parameters include data flow characteristics; The processing module 1020 is used to determine the updated algorithm or algorithm parameters based on the algorithm operation information; the transceiver module 1010 is also used to send algorithm update indication information to the user plane functional network element. The indication information is used to indicate the updated algorithm or algorithm parameters of the user plane functional network element.

In a possible design, the transceiver module 1010 is also used to send algorithm collection configuration information to the user plane functional network element. The algorithm collection configuration information includes: algorithm type, algorithm instance number, collection parameters and collection parameters. interval.

In a possible design, the transceiver module 1010 is configured to receive algorithm update capability information from the user plane functional network element, where the algorithm update capability information is used to indicate that the user plane functional network element supports algorithm online. renew.

The processing module 1020 involved in the communication device can be implemented by at least one processor or processor-related circuit component, and the transceiver module 1010 can be implemented by at least one transceiver or transceiver-related circuit component or communication interface. The operations and/or functions of each module in the communication device are respectively to implement the corresponding processes of the methods shown in Figures 5 to 8. For the sake of simplicity, they will not be described again here. Optionally, the communication device may also include a storage module, which may be used to store data and/or instructions, and the transceiver module 1010 and/or the processing module 1020 may read the data and/or instructions in the access module, Thus, the communication device implements the corresponding method. The memory module can be implemented, for example, by at least one memory.

The above-mentioned storage module, processing module and transceiver module can exist separately, or all or part of the modules can be integrated, for example, the storage module and the processing module are integrated, or the processing module and the transceiver module are integrated.

Please refer to FIG. 11 , which is another schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device can be used to implement functions corresponding to the user plane function network element or the algorithm update network element in the above method embodiment. The communication device may be a network device or a device (such as a chip included in the network device) that can support the network device to implement the corresponding functions in the above method embodiment.

The communication device 1100 may include a processor 1101 and a memory 1102. The memory 1102 is used to store program instructions and/or data, and the processor 1101 is used to execute the program instructions stored in the memory 1102, thereby implementing the method in the above method embodiment.

Optionally, the memory 1102 is coupled to the processor 1101. The coupling is an indirect coupling or communication connection between devices, units or modules, which may be electrical, mechanical or other forms, and is used between devices, units or modules. information interaction.

Optionally, the communication device 1100 may also include a communication interface 1103, which is used to communicate with other devices through a transmission medium, such as transmitting signals received from other communication devices to the processor 1101, or from the processor. 1101 signal is transmitted to other communication devices. The communication interface 1103 may be a transceiver or an interface circuit, such as a transceiver circuit, a transceiver chip, etc.

In one embodiment, the communication interface 1103 can be specifically used to perform the actions of the above-mentioned transceiver module 1010, and the processor 1101 can be specifically used to perform the actions of the above-mentioned processing module 1020, which will not be described again in this application.

The embodiment of the present application does not limit the specific connection medium between the processor 1101, the memory 1102 and the communication interface 1103. In the embodiment of the present application, the processor 1101, the memory 1102 and the communication interface 1103 are connected through a bus 1104 in Figure 11. The bus is represented by a thick line in Figure 11. The connection methods between other components are only schematically explained. , is not limited. The bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one thick line is used in Figure 11, but it does not mean that there is only one bus or one type of bus.

An embodiment of the present application also provides a chip system, including: a processor, the processor is coupled to a memory, and the memory is used to store programs or instructions. When the program or instructions are executed by the processor, the The chip system implements the method corresponding to the session function network element or the algorithm update network element in any of the above method embodiments.

Optionally, there may be one or more processors in the chip system. The processor can be implemented in hardware or software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. when passing soft When implemented as software, the processor may be a general-purpose processor implemented by reading software code stored in memory.

Optionally, there may be one or more memories in the chip system. The memory may be integrated with the processor or may be provided separately from the processor, which is not limited by this application. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip, or may be separately provided on different chips. This application describes The type of memory and the arrangement of the memory and processor are not specifically limited.

For example, the chip system can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC). It can also be a central processor (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (micro controller unit (MCU), or a programmable logic device (PLD) or other integrated chip.

It should be understood that each step in the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software. The method steps disclosed in conjunction with the embodiments of this application can be directly implemented by a hardware processor, or executed by a combination of hardware and software modules in the processor.

Embodiments of the present application also provide a computer-readable storage medium. Computer programs or instructions are stored in the computer storage medium. When the computer program or instructions are executed, the communication device is caused to perform the method in any of the above method embodiments. .

An embodiment of the present application also provides a computer program product, which when a communication device reads and executes the computer program product, causes the communication device to execute the method in any of the above method embodiments.

An embodiment of the present application also provides a communication system. The communication system includes a user plane functional network element and an algorithm updating network element. The user plane functional network element and the algorithm updating network element can execute the method in any of the above method embodiments.

It should be understood that the processor mentioned in the embodiments of this application may be a CPU, or other general-purpose processors, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

It should also be understood that the memory mentioned in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be ROM, programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (EPROM) ,EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of illustration, 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 (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (direct rambus RAM, DR RAM).

It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) is integrated in the processor.

It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

It should be understood that the various numerical numbers involved in the various embodiments of the present application are only for convenience of description, and the above The size of the serial numbers of each process or step described above does not mean the order of execution. The execution order of each process or step should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, 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 described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

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

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.

If the functions are implemented in the form of 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 the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

In the various embodiments of this application, if there are no special instructions or logical conflicts, the terms and/or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments are based on their inherent Logical relationships can be combined to form new embodiments.

Claims

A method for reconstructing key service capabilities of user plane functional network elements, characterized in that the method includes:

The user plane functional network element reports algorithm operation information to the algorithm update network element. The algorithm operation information includes parameters collected by the user plane functional network element in the past period of time to characterize the operation of the algorithm. The algorithm is used to support The user plane functional network element matches the packet detection rule PDR, and the parameters include data flow characteristics;

The user plane functional network element receives algorithm update indication information from the algorithm update network element, and the algorithm update indication information is used to indicate the updated algorithm or algorithm parameters of the user plane functional network element.
The method of claim 1, further comprising:

The user plane functional network element receives algorithm collection configuration information from the algorithm update network element. The algorithm collection configuration information includes: algorithm type, algorithm instance number, collection parameters and collection interval;

The user plane functional network element collects configuration information according to the algorithm and determines the algorithm running information.
The method according to claim 1 or 2, characterized in that, the method further includes:

The user plane functional network element reports algorithm update capability information to the algorithm update network element, and the algorithm update capability information is used to indicate that the user plane functional network element supports algorithm online update.
The method according to claim 3, characterized in that the algorithm update capability information includes: algorithm type, algorithm instance number, supported algorithm list, supported algorithm parameters for adjustment and supported collection parameters.
The method according to claim 4, characterized in that when the algorithm type is a hash algorithm;

The supported algorithm list includes one or more of MurmurHash, CRC32, FNV, and SIPHash;

The supported collection parameters include load factor, conflict rate and data flow characteristics;

The algorithm parameters that support adjustment include bucket size.
The method according to claim 4, characterized in that when the algorithm type is a tuple space search TSS algorithm;

The supported algorithm list includes cutTSS and/or mergeTSS;

The supported collection parameters include the number of tuples, tuple hit rate and data flow characteristics;

The algorithm parameters that support adjustment include tuple upper limit and tuple division rules.
The method according to any one of claims 1 to 6, characterized in that the data flow characteristics include source address, destination address, source port, destination port, flow service quality identifier, tunnel identifier, protocol identifier, unified resource Locate address.
The method according to any one of claims 1 to 7, characterized in that the method further includes:

The user plane functional network element uses the AB method to install the updated algorithm or algorithm parameters.
The method according to any one of claims 1 to 8, characterized in that the algorithm update network element is a session management function network element or a network data analysis function network element or an operation and maintenance network element.
A method for reconstructing key service capabilities of user plane functional network elements, characterized in that the method includes:

The algorithm update network element receives algorithm operation information from the user plane functional network element. The algorithm operation information includes parameters collected by the user plane functional network element in the past period of time to characterize the operation of the algorithm. The algorithm is used to Support the user plane functional network element matching packet detection rule PDR, and the parameters include data flow characteristics;

The algorithm updates the network element to decide on the updated algorithm or algorithm parameters based on the algorithm operation information;

The algorithm update network element sends algorithm update indication information to the user plane functional network element, and the algorithm update indication information is used to indicate the updated algorithm or algorithm parameters of the user plane functional network element.
The method of claim 10, further comprising:

The algorithm update network element sends algorithm collection configuration information to the user plane functional network element. The algorithm collection configuration information includes: algorithm type, algorithm instance number, collection parameters, and collection interval.
The method according to claim 10 or 11, characterized in that, the method further includes;

The algorithm update network element receives algorithm update capability information from the user plane functional network element, and the algorithm update capability information is used to indicate that the user plane functional network element supports algorithm online update.
The method according to claim 12, characterized in that the algorithm update capability information includes: algorithm type, algorithm instance number, supported algorithm list, supported algorithm parameters for adjustment and supported collection parameters.
The method according to claim 13, characterized in that when the algorithm type is a hash algorithm;

The supported algorithm list includes one or more of MurmurHash, CRC32, FNV, and SIPHash;

The supported collection parameters include load factor, conflict rate and data flow characteristics;

The algorithm parameters that support adjustment include bucket size.
The method according to claim 13, characterized in that when the algorithm type is a tuple space search TSS algorithm;

The supported algorithm list includes cutTSS and/or mergeTSS;

The supported collection parameters include the number of tuples, tuple hit rate and data flow characteristics;

The algorithm parameters that support adjustment include tuple upper limit and tuple division rules.
The method according to any one of claims 10 to 15, characterized in that the data flow characteristics include source address, destination address, source port, destination port, flow service quality identifier, tunnel identifier, protocol identifier, unified resource Locate address.
The method according to any one of claims 10 to 15, characterized in that the algorithm update network element is a session management function network element or a network data analysis function network element or an operation and maintenance network element.
A communication device, characterized by comprising a module for executing the method according to any one of claims 1 to 9.
[Correction 11.04.2023 under Rule 91]
A communication device, characterized by comprising a module for executing the method according to any one of claims 10 to 17.
A communication device, characterized in that it includes a processor and a memory, the processor is coupled to the memory, and the processor is used to control the device to implement the method according to any one of claims 1 to 9.
[Correction 11.04.2023 under Rule 91]
A communication device, characterized in that it includes a processor and a memory, the processor is coupled to the memory, and the processor is used to control the device to implement the method according to any one of claims 10 to 17.
[Correction 11.04.2023 under Rule 91]
A computer-readable storage medium, characterized in that a computer program or instructions are stored in the storage medium. When the computer program or instructions are executed by a communication device, claims 1 to 9, or 10 to 17 are implemented. any one of the methods.
A communication system, characterized by comprising the communication device according to claim 18 or 20, and the communication device according to claim 19 or 21.
[Correction 11.04.2023 under Rule 91]
A computer program product containing instructions, which, when run on a computer, causes the computer to perform the method according to any one of claims 1 to 9, or 10 to 17.