WO2019242698A1 - 一种管理网元的方法、设备及系统 - Google Patents

一种管理网元的方法、设备及系统 Download PDF

Info

Publication number
WO2019242698A1
WO2019242698A1 PCT/CN2019/092132 CN2019092132W WO2019242698A1 WO 2019242698 A1 WO2019242698 A1 WO 2019242698A1 CN 2019092132 W CN2019092132 W CN 2019092132W WO 2019242698 A1 WO2019242698 A1 WO 2019242698A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
user plane
session management
plane network
service control
Prior art date
Application number
PCT/CN2019/092132
Other languages
English (en)
French (fr)
Inventor
胡翔
夏渊
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019242698A1 publication Critical patent/WO2019242698A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • Embodiments of the present application relate to the field of communications technologies, and in particular, to a method, device, and system for managing network elements.
  • the ratio between the Session Management Function (SMF) and the User Plane Function (UPF) is 1: M (M is greater than or equal to 2 Integer).
  • SMF Session Management Function
  • UPF User Plane Function
  • M M is greater than or equal to 2 Integer.
  • the same SMF can select one or more UPFs from multiple UPFs and manage the selected UPFs, such as: policies responsible for UPFs (such as: Policy and Charging Control (PCC) rules) ), And receive non-session level management functions such as UPF event reporting.
  • policies responsible for UPFs such as: Policy and Charging Control (PCC) rules
  • N is an integer greater than or equal to 2
  • SMF Session Management Function
  • UPF User Plane Function
  • N an integer greater than or equal to 2
  • one SMF may be connected to M UPFs and manage multiple UPFs
  • one UPF may be connected to N SMFs and managed by multiple SMFs.
  • the key information (such as the Internet Protocol (IP) address of the UPF and the Tunnel Endpoint Identifier) assigned by multiple SMFs to the same UPF , TEID), etc.) may be different, there is a configuration conflict.
  • IP Internet Protocol
  • TEID Tunnel Endpoint Identifier
  • each SMF independently selects the UPF based on the information of the UPF it manages, which easily results in uneven load on the UPF. And when the network topology is updated, it is necessary to manually update the information on the network elements one by one, which is wasteful and time consuming.
  • This application provides a method, device, and system for managing network elements.
  • the service control network element centrally manages the session management network element and the user plane network element.
  • the present application provides a method for managing a network element.
  • the method includes: the service control network element obtains a management relationship between a session management network element and a user plane network element in a network, and sends the The management network element sends a user plane network element list determined by the management relationship and used to characterize the user plane network element belonging to the management of the first session management network element, and the user for selecting the user plane network element by the first session management network element The area network element selection strategy; and sending a session management network element list to any first user area network element in the network for characterizing the session management network element that manages the connection of the first user area network element.
  • the service control network element Based on the method for managing a network element provided in this application, after the service control network element obtains the management relationship between the session management network element and the user plane network element in the network, it sends the user plane network element to the session management network element according to the acquired management relationship.
  • List and user plane network element selection strategy sending a session management network element list to the user plane network element, in order to establish a communication connection between the session management network element and the user plane network element, and for the end user to choose to establish a user plane network element carried by the user plane That is, the session management network element and the user plane network element are uniformly managed by the service control network element, and the information required for establishing a communication connection between the session management network element and the user plane network element is centrally distributed to realize the session management network element and the user plane network. Meta-automatic deployment and communication connections.
  • the method further includes: the service control network element receives the work status information reported by each user plane network element in the network, and according to the work status information reported by each user plane network element (Such as: one or more of the number of sessions carried, throughput, CPU load of the central processing unit, function enable statistics, resource usage, and operating conditions) update the user plane network element selection policy to the first session management network
  • the user sends the updated user plane network element selection strategy.
  • the user plane network element selection strategy issued to the session management network element can be dynamically and uniformly adjusted based on the working conditions of the user plane network elements in the entire network, so that the user plane network element selection among multiple session management network elements is more coordinated.
  • the service control network element receives the work status information reported by each user plane network element in the network, and according to the work status information reported by each user plane network element (Such as: one or more of the number of sessions carried, throughput, CPU load of the central processing unit, function enable statistics, resource usage, and operating conditions) update the user plane network element selection policy to the first session management
  • the method further includes: when adding or deleting a user plane network element connected to the first session management network element, the service control network The user updates the user plane network element list and the user plane network element selection strategy, and sends the updated user plane network element list and the user plane network element selection strategy to the first session management network element.
  • the service control network element can timely maintain the management relationship between the network elements by issuing an updated user plane network element list and adjust the user plane network element selection strategy to The user plane network elements managed among the session management network elements in time are coordinated in a timely manner without the need for manual manual updates, which is simple and fast.
  • the method further includes: when adding or deleting a session management network element connected to the first user plane network element, the service control network The element updates the list of session management network elements, and sends the updated list of session management network elements to the first user plane network element.
  • the service control NE can maintain the management relationship between the NEs in time by issuing an updated list of session management NEs, and by adding the new session management NEs to the network.
  • Send user plane network element selection strategy to coordinate user plane network elements managed between session management network elements in a timely manner, without manual manual updates, simple and fast.
  • the method further includes: obtaining, by the service control network element, an operator plan required by the operator including a user plane network element and a session management network element during operation.
  • the service control network element centrally manages the configuration data of each network element in the network, which avoids the situation where the same user plane network element is managed by multiple session management network elements, and each session management network element delivers the same configuration data.
  • the present application provides a service control network element, which can implement the functions performed by the service control network element in the above aspects or possible designs, and the functions can be implemented by hardware or by The hardware executes the corresponding software implementation.
  • the hardware or software includes one or more modules corresponding to the foregoing functions.
  • the service control network element may include: an obtaining unit and a sending unit;
  • An obtaining unit configured to obtain a management relationship between a session management network element and a user plane network element in the network
  • a sending unit configured to send to any first session management network element in the network a user plane network element list determined by the management relationship and used to characterize the user plane network element belonging to the first session management network element management, and A user plane network element selection strategy for selecting a user plane network element at the first session management network element; and sending a session management network element for characterizing and managing the connection of the first user plane network element to any first user plane network element in the network List of session management NEs.
  • the service control network element For a specific implementation manner of the service control network element, reference may be made to the behavior function of the service control network element in the method for managing a network element provided in the first aspect or any possible design provided by the first aspect, and details are not described herein again. Therefore, the provided service control network element can achieve the same beneficial effects as the first aspect or any possible design of the first aspect.
  • a service control network element including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the service control network element is running, the processor executes the computer execution instruction stored in the memory , So that the service control network element executes the method for managing a network element according to the first aspect or any possible design of the first aspect.
  • a computer-readable storage medium stores instructions, and when the computer-readable storage medium is run on a computer, the computer can execute the foregoing first aspect or any of the foregoing aspects. Design the described method of managing network elements.
  • a computer program product containing instructions, which, when run on a computer, enables the computer to execute the above-mentioned first aspect or any one of the above-mentioned possible design methods for managing a network element.
  • a chip system includes a processor and a communication interface, and is configured to support a service control network element to implement the functions involved in the foregoing aspect, for example, to support the processor to obtain the service control network element through a communication interface.
  • the management relationship between the session management network element and the user plane network element in the network, and sending to any first session management network element in the network is determined by the management relationship and is used to characterize the management attributed to the first session management network element.
  • the chip system further includes a memory, and the memory is configured to store program instructions and data necessary for the service control network element.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the present application provides a method for managing a network element, the method being executed by any session management network element in a network, the method comprising: the session management network element receiving from a service control network element determined by the management relationship And is used to characterize a user plane network element list belonging to the user plane network element managed by the first session management network element and a user plane network element selection strategy for the first session management network element to select a user plane network element , Establishing a communication connection with the user plane network element according to the received user plane network element list, and selecting a user plane network element for establishing a user plane bearer for the end user according to the user plane network element selection policy.
  • the session management network element receives the management of the service control network element, obtains the information needed by the session management network element to establish a communication connection from the service control network element, and realizes the automatic deployment and communication connection of the session management network element.
  • the session management network element sends the service management network element with the service address of the session management network element to request the service control network element to send the user plane network element list to the session management network element and Management request for user plane network element selection policy, receiving the user plane network element list and user plane network element selection policy sent by the service control network element.
  • the session management network element sends a registration request carrying the service address of the session management network element to the service control network element to indicate that the session management network element has completed instantiation and deployment, and receives a user plane network element list sent by the service control network element. And user plane network element selection strategy.
  • the session management network element further includes: when adding or deleting a user plane network element that establishes a communication connection with the session management network element, from the service control The network element receives the updated user plane network element list and the user plane network element selection strategy.
  • the service control network element can timely maintain the management relationship between the network elements by issuing an updated user plane network element list and adjust the user plane network element selection strategy to The user plane network elements managed among the session management network elements in time are coordinated in a timely manner without the need for manual manual updates, which is simple and fast.
  • the present application provides a session management network element.
  • the session management network element is any session management network element in the network.
  • the session management network element can implement the above aspects or the possible design of the session management network element.
  • the functions performed may be implemented by hardware, and may also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the foregoing functions.
  • the session management network element may include a receiving unit and a processing unit.
  • a receiving unit configured to receive, from a service control network element, a user plane network element list determined by the management relationship, and used to characterize a user plane network element belonging to the user plane network element managed by the first session management network element, and used for the first A user plane network element selection strategy for a session management network element selecting a user plane network element;
  • the processing unit is configured to establish a communication connection with the user plane network element according to the received user plane network element list, and select a user plane network element that establishes a user plane bearer for the end user according to the user plane network element selection policy.
  • the session management network element For a specific implementation manner of the session management network element, reference may be made to the behavior function of the session management network element in the method for managing a network element provided in the seventh aspect or any possible design provided in the seventh aspect, and details are not described herein again. Therefore, the provided session management network element can achieve the same beneficial effects as the seventh aspect or any possible design of the seventh aspect.
  • a session management network element including: a processor and a memory; the memory is configured to store computer execution instructions, and when the session management network element is running, the processor executes the computer execution instructions stored in the memory , So that the session management network element executes the method for managing a network element according to the seventh aspect or any one of the possible designs of the seventh aspect.
  • a computer-readable storage medium stores instructions, and when the computer-readable storage medium runs on the computer, the computer can execute the seventh aspect or any one of the foregoing aspects. Design the described method of managing network elements.
  • a computer program product containing instructions is provided, which, when run on a computer, enables the computer to execute the seventh aspect or any one of the foregoing aspects. .
  • a chip system includes a processor and a communication interface, and is configured to support a session management network element to implement the functions involved in the foregoing aspect, for example, to support a processor from a service control network element through a communication interface.
  • the chip system further includes a memory, where the memory is configured to store program instructions and data necessary for the session management network element.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the present application provides a method for managing a network element.
  • the method may be performed by any user plane network element in a network.
  • the method includes: the user plane network element receives from a service control network element and is determined by a management relationship.
  • a session management network element list for characterizing the session management network element that manages the connection of the first user plane network element, establishes a communication connection with the session management network element according to the session management network element list, and accepts the session management network element with which the communication connection is established. Node-level management information or session-level management information.
  • the user plane network element is managed by the service control network element, and the information required by the user plane network element to establish a communication connection is obtained from the service control network element to realize the automatic deployment and communication connection of the user plane network element.
  • the user plane network element receiving the session management network element list from the service control network element includes: the user plane network element sends a service address carrying the service address of the user plane network element to the service control network element.
  • the requesting service control network element sends the user plane network element list and the management request of the user plane network element selection policy to the user plane network element, and receives the user plane network element list and the user plane network element selection policy sent by the service control network element.
  • the user plane network element sends a registration request that carries the service address of the user plane network element to the service control network element to indicate that the user plane network element has completed instantiation and deployment, and receives the user plane network element list sent by the service control network element.
  • user plane network element selection strategy is used to select a registration request that carries the service address of the user plane network element to the service control network element to indicate that the user plane network element has completed instantiation and deployment.
  • the method further includes: when a session management network element connected to the user plane network element is added or deleted, the user plane network element is controlled from the service.
  • the network element obtains the updated session management network element list.
  • the service control NE can maintain the management relationship between the NEs in time by issuing an updated list of session management NEs, and by adding the new session management NEs to the network.
  • Send user plane network element selection strategy to coordinate user plane network elements managed between session management network elements in a timely manner, without manual manual updates, simple and fast.
  • the present application provides a user plane network element, which can implement the functions performed by the user plane network element in the above aspects or possible designs, and the functions can be implemented by hardware or
  • the corresponding software is implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the foregoing functions.
  • the user plane network element may include: a receiving unit and a processing unit;
  • a receiving unit configured to receive, from a service control network element, a session management network element list determined by a management relationship and used to represent a session management network element that manages a first user plane network element connection;
  • a processing unit is configured to establish a communication connection with the session management network element according to the session management network element list, and receive node-level management information or session-level management information of the session management network element with which the communication connection is established.
  • the user plane network element For the specific implementation of the user plane network element, reference may be made to the behavior function of the user plane network element in the method for managing a network element provided in the thirteenth aspect or any one of the possible designs provided by the thirteenth aspect, which is not repeated here. . Therefore, the provided user plane network element can achieve the same beneficial effects as the thirteenth aspect or any of the possible designs of the thirteenth aspect.
  • a user plane network element including: a processor and a memory; the memory is configured to store computer execution instructions; when the user plane network element is running, the processor executes the computer execution stored in the memory; An instruction to cause the user plane network element to execute the method for managing a network element according to the thirteenth aspect or any one of the thirteenth possible designs.
  • a computer-readable storage medium stores instructions that, when run on a computer, enable the computer to execute the thirteenth aspect or any of the foregoing aspects. It is possible to design the described method of managing network elements.
  • a computer program product containing instructions which, when run on a computer, enables the computer to execute the management network element described in the thirteenth aspect or any one of the foregoing possible designs. method.
  • a chip system includes a processor and a communication interface, and is configured to support a user plane network element to implement the functions involved in the foregoing aspect, for example, to support a processor to control a network element from a service through a communication interface.
  • Receive a session management network element list determined by the management relationship and used to represent the session management network element that manages the first user plane network element connection establish a communication connection with the session management network element according to the session management network element list, and accept a communication connection with it
  • the chip system further includes a memory, and the memory is configured to store program instructions and data necessary for the user-side network element.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the technical effects brought by any of the design methods in the fifteenth aspect to the eighteenth aspect can refer to the technical effects brought by the thirteenth aspect or any of the possible designs of the thirteenth aspect. More details.
  • the present application provides a system for managing a network element.
  • the system for managing a network element includes the service control network element according to the second aspect to the sixth aspect, and a plurality of the eighth aspect to the twelfth aspect.
  • FIG. 1 is a simplified schematic diagram of a system architecture according to an embodiment of the present application.
  • 2a is a simplified schematic diagram of a 5G system provided by an embodiment of the present application.
  • FIG. 2b is a simplified schematic diagram of a 4G system provided by an embodiment of this application.
  • FIG. 3 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 4 is a flowchart of a method for managing a network element according to an embodiment of the present application.
  • FIG. 5 is a flowchart of another method for managing a network element according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a service control network element according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a composition of a session management network element according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a user plane network element according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a system composition for managing a network element according to an embodiment of the present application.
  • the method for managing a network element may be applicable to the system shown in FIG. 1, and the system may include: a service control network element and a plurality of session management network elements (such as a session management network element 1 and a session management network element 2)
  • Multiple user plane network elements (such as user plane network element 1, user plane network element 2, etc.) may also include: terminals, access network equipment, access and mobility management function entities (Access and Mobility Management Function, AMF ), Data Network (DN), etc.
  • AMF Access and Mobility Management Function
  • DN Data Network
  • FIG. 1 is only an exemplary drawing.
  • the system may include other network elements.
  • the embodiment of the present application The number is not limited.
  • the service control network element in FIG. 1 may be called a Service Control Function (SCF).
  • SCF Service Control Function
  • the service control network element may be independently deployed in the system shown in FIG. 1 or may be deployed in the system shown in FIG. 1.
  • the service control network element has functions such as maintaining the management relationship between the session management network element and the user plane network element in the network shown in FIG. 1, and uniformly orchestrating the user plane network element selection strategy required by each session management network element to select the user plane network element.
  • the service control network element may obtain the management relationship between the session management network element and the user plane network element in the network, and send it to any first session management network element in the network, which is determined by the management relationship, and is used to characterize the belonging to the first
  • the area network element sends a session management network element list that is used to characterize the session management network element that manages the first user area network element connection.
  • FIG. 4 for the functions of the service control network element, refer to FIG. 4.
  • the session management network element in FIG. 1 can establish a communication connection with M (M is an integer greater than or equal to 2) user plane network elements at the same time, and can establish a communication plane with the user plane network elements according to the user plane network element selection strategy.
  • M is an integer greater than or equal to 2
  • the user plane network element in FIG. 1 can establish a communication connection with N (N is an integer greater than or equal to 2) session management network elements at the same time, and accepts some or all of the session management network element node levels of the N session management network elements.
  • N is an integer greater than or equal to 2
  • the system shown in FIG. 1 may be as shown in FIG. 2a fifth generation (5th Generation, 5G) system, it may also be a fourth-generation (4 th Generation) shown in 2b, the communication system and can follow the evolution of This embodiment of the present application does not limit this.
  • the session management network element in FIG. 1 may be a session management function (SMF)
  • the user plane network element may be a user plane function (user plane function, UPF).
  • SMS session management function
  • UPF user plane function
  • communication between each network element can be established through a next-generation network (next generation (NG) interface (not shown in Figure 2a)) to achieve communication.
  • NG next-generation network
  • the UPF can communicate with the SMF through the NG interface 4 (N4 for short).
  • Establish control plane signaling connection UPF can exchange user plane data with data network through NG interface 6 (referred to as N6), SCF can establish control with SMF and UPF through newly added NG interface x (referred to as Nx) (not yet defined).
  • Nx newly added NG interface x
  • FIG. 2a is only an exemplary architecture diagram.
  • the 5G system may also include other network elements, such as: terminals, access network equipment, access, and mobility management. Functions (Access and Mobility Management Function, AMF), etc., are not limited in this embodiment of the present application.
  • AMF Access and Mobility Management Function
  • the session management network element in FIG. 1 may be a control plane serving gateway (SGW-C) / control plane public data network gateway (Public Data NetWorks GateWay-Control (PGW-C) can also be a control plane detection function network element (Traffic Detection Function-Control, TDF-C), and the user plane network element can be a user plane service gateway (Serving GateWay-User, SGW-U ) / User plane public data network gateway (Public DataNetNet GateWay-User, PGW-U), can also be a user plane detection function network element (Traffic Detection Function-User, TDF-U).
  • SGW-C control plane serving gateway
  • PGW-C Public Data NetWorks GateWay-Control
  • TDF-C control plane detection function network element
  • TDF-C Transmission Detection Function-Control
  • the user plane network element can be a user plane service gateway (Serving GateWay-User, SGW-U ) /
  • SGW-U / PGW-U can establish control plane signaling connection with SGW-C / PGW-C through Gx interface; SCF can connect with SGW-C / PGW-C, SGW-U / through service interface The PGW-U establishes a control plane signaling connection.
  • SGW-C / PGW-C and SGW-U / PGW-U in Figure 2b can be independently deployed in a 4G system as shown in Figure 2b, and SGW-C / PGW-C and SGW- U / PGW-U is integrated in the same network element (such as SGW / PGW / TDF).
  • FIG. 2b is only an exemplary architecture diagram.
  • the network architecture may also include other network elements, such as a terminal, an access network device, and a mobile management entity (MME). ), Etc., this embodiment is not limited thereto.
  • the network elements in the above architecture and the names of the interfaces between the network elements are only examples. In specific implementation, the names of the network elements and the interfaces between the network elements may be other names, which are not specifically described in the embodiment of the present application. limited.
  • FIG. 3 is a schematic composition diagram of a communication device according to an embodiment of the present application.
  • the communication device 300 includes at least one processor 301, a communication line 302, and at least one communication interface 303. Further, Includes memory 304.
  • the processor 301, the memory 304, and the communication interface 303 may be connected through a communication line 302.
  • the processor 301 may be a central processing unit (CPU), a specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application. For example: one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs).
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • the communication line 302 may include a path for transmitting information between components included in a communication device.
  • the communication interface 303 is used to communicate with other devices or communication networks. Any device such as a transceiver can be used, such as Ethernet, Radio Access Network (RAN), and Wireless Local Area Networks (WLAN). Wait.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the memory 304 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (Random Access Memory, RAM), or other types that can store information and instructions
  • the dynamic storage device can also be Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc (Read-Only Memory, CD-ROM) or other optical disk storage, optical disk storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • CD-ROM Compact Disc
  • CD-ROM Compact Disc
  • optical disk storage including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • disk storage media or other magnetic storage devices or
  • the memory 304 may exist independently of the processor 301, that is, the memory 304 may be a memory external to the processor 301. At this time, the memory 304 may be connected to the processor 301 through a communication line 302 for storing execution The instructions or application code are controlled and executed by the processor 301 to implement the method for managing a network element provided in the following embodiments of the present application.
  • the memory 304 may also be integrated with the processor 301, that is, the memory 304 may be an internal memory of the processor 301.
  • the memory 304 is a cache and may be used to temporarily store some data and instructions. Information, etc.
  • the processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 3.
  • the communication device 300 may include multiple processors, such as the processor 301 and the processor 307 in FIG. 3.
  • the communication device 300 may further include an output device 305 and an input device 306.
  • the above-mentioned communication device 300 may be a general-purpose device or a special-purpose device.
  • the communication device 300 may be a desktop computer, a portable computer, a network server, a PDA, a mobile phone, a tablet computer, a wireless terminal, an embedded device, or a device with a similar structure in FIG. 3.
  • the embodiment of the present application does not limit the type of the communication device 300.
  • FIG. 4 is a method for managing network elements according to an embodiment of the present application, which is used to manage multiple session management network elements and user plane network elements in the network shown in FIG. 1 through a service control network element. As shown in FIG. 4, the method may include steps 401 to 405.
  • Step 401 The service control network element obtains a management relationship between the session management network element and the user plane network element in the network.
  • the management relationship between the session management network element and the user plane network element is used to indicate the physical connection relationship between the session management network element and the user plane network element in the network (such as a specific network slice) planned by the operator, that is, it is used for Indicates which session management network element establishes a physical connection with which user plane network element.
  • the network planned by the operator is shown in Figure 1.
  • the management relationship between the session management network element and the user plane network element may be: the session management network element 1 is connected to the user plane network element 1, the user plane network element 3, and the session Management network element 2 is connected to user plane network element 1, user plane network element 2, and user plane network element 3.
  • the physical connection may refer to a connection established between network elements through a wired transmission medium (such as a twisted pair, a coaxial cable, and an optical fiber) or a wireless transmission medium (such as radio waves, microwaves, etc.).
  • a wired transmission medium such as a twisted pair, a coaxial cable, and an optical fiber
  • a wireless transmission medium such as radio waves, microwaves, etc.
  • the service control network element may obtain the management relationship between the session management network element and the user plane network element in the network from the operator.
  • an operator may send a management relationship between a session management network element and a user plane network element to a service control network element through a Business Support System (BSS) / Operation Support System (OSS).
  • BSS Business Support System
  • OSS Operation Support System
  • the operator may input the management relationship between the session management network element and the user plane network element to the service control network element through a user interface (User Interface) of the service control network element.
  • the service control network element after the service control network element is turned on, it can send a request message to the operator through BSS / OSS, requesting the operator to send the management relationship between the session management network element and the user plane network element, and the operator receives the request message Then, the management relationship between the session management network element and the user plane network element is sent to the service control network element through BSS / OSS.
  • Step 402 The service control network element sends a user plane network element list and a user plane network element selection policy for the first session management network element to select the user plane network element to the first session management network element, and the first session management network element receives the user Face list and user plane network element selection strategy.
  • the first session management network element is any session management network element in the network shown in FIG. 1.
  • the service control network element may receive the request message sent by the first session management network element after the instantiation and deployment of the first session management network element is completed, and send a user plane network element list to the first session management network element according to the received request message and User plane network element selection strategy.
  • the service control network element sends to the first session management network element a software package that the service session network element requests from the virtual network function management entity (Virtual Network Function Management (VNFM)) to start when the first session management network element is started.
  • VNFM Virtual Network Function Management
  • Path deployment strategy, networking information of the service, initial running resources of the service (such as cache resources, service address of the network element, and service address of the service control network element), etc., to implement the instantiated deployment of the first session management network element .
  • the first session management network element may send a management request carrying the service address of the first session management network element to the service control network element, requesting the service control network element to send the user plane network element list and the user plane to the first session management network element.
  • Network element selection strategy carrying the service address of the first session management network element to the service control network element, requesting the service control network element to send the user plane network element list and the user plane to the first session management network element.
  • the service control network element After receiving the management request, the service control network element sends a user plane network element list and a user plane network element selection policy to the first session management network element.
  • the first session management network element may send a registration request to the service control network element that carries the service address of the first session management network element to indicate that the first session management network element has completed instantiated deployment, and the service control network element receives After the registration request is received, a user plane network element list and a user plane network element selection policy are sent to the first session management network element.
  • the user plane network element list is determined by the management relationship, and is used to characterize the user plane network elements belonging to the management of the first session management network element.
  • the user plane network element list may include the user plane network elements connected to the session management network element 1.
  • the information of the user plane network element is used to identify the user plane network element, which can be the identity (ID) of the user plane network element, or the service address of the user plane network element (such as the uniform resource positioning of the user plane network element). (Uniform Resource Locator, URL) or N4 interface address of the user plane network element). For example, taking FIG.
  • the session management network element 1 is connected to the user plane network element 1 and the user plane network element 2, and then the user plane network element list sent by the service control network element to the session management network element 1 is ⁇ user plane network Element 1, user plane network element 2 ⁇ .
  • the user plane network element selection policy defines one or more conditions that the user plane network element selection of the session management network element needs to meet.
  • the user plane network element selection policy can be selected by the user plane network element parameters and by the first session management network.
  • the information of the user plane network element of the meta management is determined.
  • User plane network element selection parameters may include some parameters that are planned in advance by the operator and are used by the session management network element to select user plane network elements.
  • These parameters may be typical user plane network element selection parameters, such as: user plane network elements Deployment location, load of user plane network elements, externally provided service capabilities of user plane network elements, system capacity of user plane network elements, functional deployment of user plane network elements, networking mode, user contracting strategy, user access Factors used in the selection of user-plane network elements in the input technology or other existing communication standards.
  • the deployment position of the user plane network element may refer to the physical position of the user plane network element in the entire communication system, and may be expressed by geographical coordinates or a region range.
  • the load of the user plane network element may refer to the CPU utilization of the user plane network element, the storage capacity of the user plane network element, and the like.
  • the service capability provided by the user plane network element can be used to define the external service provided by the user plane network element. It can include the type of the user plane network element receive / send service, the time period of the user plane network element receive / send service, and the user.
  • the system capacity of the user plane network element can refer to the maximum number of sessions that the user plane network element can carry within a certain period of time.
  • the function deployment of the user plane network element can refer to the capabilities supported by the sessions carried by the user plane network element, such as the bandwidth and delay.
  • the networking mode can refer to whether the user plane network element is connected to the DN that the user wants to access.
  • the user's contract strategy can be used to specify the user plane network elements to which the user is contracted.
  • the access technology used by a user may refer to an access technology used by a user to access a network, and may be a third generation (3G) technology or a 4G technology or 5G. Different access technologies may correspond to different user plane network elements.
  • 3G third generation
  • 4G technology 4G technology or 5G.
  • Different access technologies may correspond to different user plane network elements.
  • the value of the attribute can be dynamically adjusted according to the situation of the user plane network element managed by the session management network element, while the attribute values of other parameters are basically pre-made parameters, and the corresponding attribute values are fixed.
  • User plane network element selection strategy may include: user plane network element deployment location, user plane network element load, service capability provided by user plane network element, system capacity of user plane network element, function deployment of user plane network element, Networking method, user subscription strategy, user access technology, user plane network element weight, or other factors referenced when selecting user plane network elements in other existing communication standards, etc.
  • User plane network selected by the session management network element Yuan needs to meet some or all of these conditions.
  • the weight of the user plane network element is used to represent the ability of the user plane network element to carry a session among multiple user plane network elements selected by the session management network element.
  • the user plane network element selected by the session management network element 1 is the user plane network element 1 and the user plane network element 3, the user plane network element 1 has a weight of 10, and the user plane network element 3 has a weight of 90.
  • the session management network element 1 requests the user plane network element 1 to establish 10 sessions, and requests the user plane network element 2 to establish 90 sessions.
  • the user plane network element selection strategy is ⁇ the deployment position of the user plane network element is in area A, and the user plane network element can provide external services 1 ⁇ .
  • session management network element 1 can be based on the user plane network
  • the conditions specified in the meta selection policy determine that the user plane network element that meets the user selection policy is user plane network element 1.
  • Step 403 The service control network element sends a session management network element list to the first user plane network element, and the first user plane network element receives the session management network element list.
  • the first user plane network element is any user plane network element in the network shown in FIG. 1.
  • the service control network element may receive the request message sent by the first user plane network element after the first user plane network element is instantiated and deployed, and send a session management network element list to the first user plane network element according to the received request message.
  • the service control network element sends to the first user plane network element a software package download path, deployment strategy, service networking information, and service required to start the first user plane network element requested by the service control network element from the VNFM.
  • Information such as cache resources, service address of the network element, and service address of the service control network element, etc., to implement instantiation and deployment of the first user plane network element.
  • the first user plane network element may send a management request carrying the service address of the first user plane network element to the service control network element, requesting the service control network element to send the user plane network element list and the user plane to the first user plane network element.
  • Network element selection strategy After receiving the management request, the service control network element sends a session management network element list to the first user plane network element.
  • the first user plane network element may send a registration request carrying the service address of the first user plane network element to the service control network element to indicate that the first user plane network element has completed instantiation and deployment, and the service control network element receives After the registration request is received, a session management network element list is sent to the first user plane network element.
  • the session management network element list is determined by a management relationship, and is used to represent a session management network element that manages the connection of the first user plane network element.
  • the session management network element list may include information of the session management network element connected to the user plane network element 1.
  • the information of the session management network element may be used to identify the session management network element, which may be the ID of the session management network element, or the session management network element.
  • the service address of the element (such as the URL of the session management network element or the N4 interface address of the session management network element), or the serviced interface address of the session management network element (N session management network element). For example, taking FIG.
  • the user plane network element 1 is connected to the session management network element 1 and the session management network element 2, and the service control network element sends a session management network element list to the user plane network element ⁇ session management network element 1, Session Management Network Element 2 ⁇ .
  • this embodiment of the present application does not limit the execution order of steps 402 and 403. Except as shown in FIG. 4, the embodiment of the present application may also perform step 403, then step 402, or both steps 402 and 403. No restrictions.
  • Step 404 The first session management network element establishes a communication connection with the user plane network element according to the received user plane network element list, and selects a user plane network element for establishing a user plane bearer for the end user according to the user plane network element selection policy. .
  • Step 404 may refer to an existing process. For example, when the first session management network element receives a link establishment request (such as an N4 link establishment request) sent by the user plane network element and carrying the information of the user plane network element. The first session management network element checks whether the user plane network element is recorded in the locally saved user plane network element list, and if so, sends a successful establishment response to the user plane network element to indicate the user plane network element and the session management. The communication connection is successfully established between the network elements; otherwise, the link establishment request sent by the user plane network element is rejected.
  • a link establishment request such as an N4 link establishment request
  • the first session management network element may select the Among the user plane network elements for the first session management network element establishment link establishment, a user plane network element for establishing a user plane bearer is selected for the end user.
  • the selected user plane network element meets the conditions specified in the user plane network element selection policy.
  • the deployment position of the user plane network element includes the user plane network element in the deployment position specified in the user plane network element selection policy.
  • the load is less than or equal to the load specified by the user plane network element selection policy, the system capacity of the user plane network element is greater than or equal to the system capacity specified by the user plane network element selection policy, and the like.
  • Step 405 The first user plane network element establishes a communication connection with the session management network element according to the session management network element list, and accepts node-level management information or session-level management information of the session management network element with which the communication connection is established.
  • step 405 may refer to an existing process, for example, the first user plane network element enters the running state, checks its list of session management network elements, and sends a link establishment to the session management network element according to the service address of the session management network element. Request (such as: N4 link establishment request), to establish a communication connection with the session management network element.
  • Request such as: N4 link establishment request
  • the service address of the session management network element can be recorded in the session management network element list.
  • the first user plane network element can directly obtain the service address of the session management network element from the session management network element list.
  • the address sends a link establishment request to the session management network element; or, only the session management network element ID is recorded in the session management network element list, and the service address of the session management network element is not recorded.
  • the first user plane network element may Send a query request carrying the ID of the session management network element to the Network Storage Function (NRF), requesting the NRF to query the service address of the session management network element; the NRF receives the query request, and according to the ID of the session management network element and the session management Correspondence between the service addresses of network elements, determine the service address of the session management network element to be queried, and send the service address of the session management network element to be queried to the first user plane network element; the first user plane network element receives the session from the NRF The service address of the management network element sends a link establishment request to the session management network element according to the service address of the session management network element.
  • NRF Network Storage Function
  • the correspondence between the service address of the session management network element and the ID of the session management network element can be pre-existed in the NRF in the following manner: After the session management network element enters the running state, it can send the NRF carrying the session management network element. A registration request for the ID and the service address of the session management network element. The registration request is used to indicate that the session management network element can provide external services. After receiving the registration request, the NRF records the service address of the session management network element and the ID of the session management network element. Correspondence between.
  • this embodiment of the present application does not limit the execution order of steps 404 and 405. Except as shown in FIG. 4, the embodiment of the present application may also perform step 405, then step 404, or both step 404 and step 405. No restrictions.
  • the above text only describes the process of the service control network element sending a user plane network element list and a user plane network element selection policy to a session management network element, and sending a session management network element list to a user plane network element, as shown in the figure.
  • the service control network element may also send a user plane network element list and a user plane network element selection policy to other session management network elements by referring to step 402, and send a session management network element list to other user plane network elements by referring to step 403. No longer.
  • the service control network element After the service control network element obtains the management relationship between the session management network element and the user plane network element, it sends the user plane network element list and the user plane network element to the session management network element according to the acquired management relationship. Select a policy, send a session management NE list to the user plane network element, establish a communication connection between the session management NE and the user plane network element, and choose to establish a user plane network element carried by the user plane for the end user.
  • the service management network element performs unified management on the session management network element and the user plane network element, and centrally delivers the information required for the connection between the session management network element and the user plane network element, thereby realizing the session management network element and the user plane network element. Deploy and connect automatically.
  • the method may further include:
  • the service control network element receives the work status information reported by each user plane network element in the network
  • the service control network element updates the user plane network element selection policy of the first session management network element according to the work state information reported by each user plane network element, and sends the updated user plane network element selection policy to the first session management network element.
  • the working state information may include, but is not limited to, a combination of one or more of the number of sessions carried, throughput, CPU load, function enable statistics, resource usage, and operating conditions.
  • the number of sessions carried may refer to the number of sessions carried by a user plane network element when it is being used by a session management network element.
  • the number of sessions carried corresponds to the session management network element.
  • the same user plane network element is used by different session management networks.
  • the number of sessions carried by different session management NEs can be different or the same.
  • user plane NE 1 is managed by session management NE 1 and session management NE 2 at the same time, and session management NE 1 manages the user plane.
  • the user plane network element 1 carries 500 sessions.
  • the user plane network element 1 When the session management network element 2 manages the user plane network element 1, the user plane network element 1 carries 200 sessions. Throughput can refer to the amount of data successfully transmitted by the user plane network element in a unit time.
  • the CPU load can refer to the working status of the CPU of the user-side network element.
  • the CPU load can be used to represent the CPU load. The greater the CPU occupancy, the higher the CPU load, and conversely, the lower the CPU load.
  • Function enable statistics can refer to the number of sessions supported by a certain function of the user plane network element.
  • the resource usage can refer to the memory usage of the user plane network element.
  • the operating status may refer to the normal or failure of the user plane network element.
  • the service control network element updates the user plane network element selection strategy of the session management network element according to the work state information reported by each user plane network element.
  • the service control network element may adjust the user plane network element selection according to the work plane network element work state information.
  • the weight of each user plane network element in the policy For example, if a user plane network element is overloaded, the weight of selecting the user plane network element is reduced; when the user plane network element is low in load, increasing the weight of selecting the user plane network element.
  • each user plane network element may periodically report its work status information to the service control network element, for example, the work status information may be carried in a Node Status Report message / Node Status Response message. Sent to the service control network element on a regular basis; or each user plane network element receives a subscription request sent by the service control network element, and the subscription request is used to request the user plane network element to regularly report its work status information to the service control network element. According to the subscription request, Regularly report the work status information to the service control network element, and the work status information can be carried in the subscription response.
  • the user plane network element selection strategy of each session management network element can be dynamically and uniformly adjusted based on the working conditions of the user plane network elements of the entire network, so that the user plane network element selection among multiple session management network elements is more coordinated, avoiding multiple
  • the lack of a global perspective results in an uneven service load on the user plane network element.
  • the method may further include:
  • the service control network element updates the user plane network element list and the user plane network element selection policy originally issued to the first session management network element. Sending the updated user plane network element list and the user plane network element selection strategy to the first session management network element. Further, the service control network element may also send a session management network element list to the newly added user plane network element.
  • the service control network element may delete the information of the user plane network element from the user plane network element list and re-deliver the updated user plane network element list to the session management network element.
  • the service control network element may also actively notify each session management network element that manages the user plane network element to no longer select the user plane network element.
  • the service control network element can timely maintain the management relationship between the network elements by issuing an updated user plane network element list and adjust the user plane network element selection strategy to
  • the user plane network elements managed among the session management network elements in time are coordinated in a timely manner without the need for manual manual updates, which is simple and fast.
  • the method may further include:
  • the service control network element updates the list of session management network elements originally issued to the first user plane network element, and sends the list to the first user plane.
  • the network element sends an updated list of session management network elements.
  • the service control network element may also send a user plane network element list and a user plane network element selection policy to the newly added session management network element.
  • the service control NE can maintain the management relationship between the NEs in time by issuing an updated list of session management NEs, and by adding the new session management NEs to the network.
  • Send user plane network element selection strategy to coordinate user plane network elements managed between session management network elements in a timely manner, without manual manual updates, simple and fast.
  • the method further includes:
  • the service control network element obtains the configuration data planned by the operator, and configures the session management network element and the user plane network element in the network according to the configuration data.
  • the service control network element may configure the session management network element and the user plane network element in the network according to the configuration data and the functions enabled by the session management network element and the user plane network element; or, the service control network element may configure the And the functions of enabling the session management NE and the user plane network element, and the user group information supported by the network element to configure the session management NE and the user plane network element in the network.
  • the enabled functions can include billing (at what rate), blocking (whether you need to block the service), redirection (whether you need to redirect the service flow to a specific website), and header enhancement (whether you need to Transmission protocol (Hyper Text, Transfer Protocol, HTTP) message inserts some feature information to the server), bandwidth management (limiting the bandwidth of specific services) and other functions to charge and control the message.
  • the user group information can be used to identify the user groups that access the network and receive the services provided by the network, such as the user group that has signed up for the Tencent King Card package, the user group that has signed up for the Taobao package, and the user group that has 169 basic packages.
  • the configuration data may include configuration parameters (such as the logical interface address of the network element) required by the session management network element and the user plane network element for normal operation and enabling functions, and may also include the user plane network element to follow the user data forwarding Filters and processing strategies.
  • the configuration data may include one or more predefined rules.
  • the predefined rules are used to define the filtering conditions and corresponding processing policies of the data packets passing through the user-side network element.
  • the filtering conditions define the data that can hit this predefined rule.
  • L3, L4, L7 information of the packet such as: source / destination IP address, source / destination port, IP protocol (such as: Transmission Control Protocol (TCP)) or User Datagram Protocol (User Datagram Protocol, UDP ), Internet Control Message Protocol (Internet Control Message Protocol, ICMP), domain name, URL, etc.).
  • the policy part may include charging, blocking, redirection, and header enhancement policies for charging and controlling packets.
  • the predefined rule is identified by a predefined rule name. Different predefined rules may correspond to different predefined rule names.
  • the session management network element may issue a predefined rule name to the user plane network element to activate the predefined rule. For example, both the session management NE and the user plane NE are configured with a predefined rule.
  • the session management NE can send the name of the predefined rule to the user plane NE through the N4 interface and activate it.
  • the predefined rule enables the user plane network element to execute a corresponding service function according to the predefined rule.
  • the service control network element centrally manages the configuration data of each network element, which avoids the situation where the same user plane network element is managed by multiple session management network elements, and each session management network element sends the same configuration data to the user.
  • the problem of configuration data redundancy caused by network elements and the configuration conflict caused by different session management network elements issuing different configuration data for the same configuration object.
  • the service control network element is SCF
  • the session management network element is SMF
  • the user plane network element is UPF
  • the user plane network element list is the UPF list
  • the user plane network element selection strategy is the UPF selection strategy.
  • the session management network element list is an SMF list
  • the user plane network element selection parameter is a UPF selection parameter.
  • FIG. 5 is a method for managing a network element according to an embodiment of the present application, which is used to manage multiple SMFs and multiple UPFs in the network shown in FIG. 2a through an SCF, where an operator in the network shown in FIG. 2a is initially planned as : SMF1 is connected to UPF1 and UPF3, SMF2 is connected to UPF1, UPF2, and UPF3, and SMF3 and UPF4 are new network elements.
  • the method may include steps 501 to 514.
  • Step 501 The operator determines the management relationship between the SMF and the UPF according to its network planning requirements, and sends the management relationship between the SMF and the UPF to the SCF.
  • the management relationship between SMF and UPF is: SMF1 is connected to UPF1, UPF3, and SMF2 is connected to UPF1, UPF2, and UPF3.
  • SMF1 is connected to UPF1
  • UPF3 is connected to UPF1, UPF2, and UPF3.
  • SMF1 is connected to UPF1
  • UPF3 is connected to UPF1, UPF2, and UPF3.
  • SMF2 is connected to UPF1, UPF2, and UPF3.
  • Step 502 The SCF obtains the management relationship between the SMF and the UPF; sends service application requests to SMF1, SMF2, and UPF1 to UPF3, respectively, to implement the instantiation and deployment of SMF1, SMF2, and UPF1 to UPF3.
  • the service application request may carry the software package download path, deployment strategy, service networking information, and service initial running resources (such as cache resources) required by the SCF to start from the network element (SMF or UPF) requested by the VNFM.
  • service initial running resources such as cache resources
  • the service address of the network element, and the service address of the SCF is used to implement the instantiation and deployment of the network element.
  • the instantiation and deployment process of each network element can refer to the existing technology and will not be described in detail.
  • the SCF requests from VNFM the package download path, deployment strategy, service networking information, and initial service resources (such as cache resources and SMF1 service addresses) required for SMF1 startup. , SCF service address) and other information to implement the instantiation and deployment of SMF1.
  • initial service resources such as cache resources and SMF1 service addresses
  • Step 503 SMF1 sends a first request message to the SCF according to the service address of the SCF.
  • the first request message may be a management request, and the management request carries a service address of SMF1.
  • the management request may be used to request the SCF to send a UPF list and a UPF selection policy to SMF1. or,
  • the first request message may be a registration request.
  • the registration request may be used to indicate that SMF1 has completed instantiation and deployment, and may be managed by the SCF.
  • the registration request may carry the service address of the SMF.
  • Step 504 The SCF receives the first request message, sends a UPF list to SMF1 according to the management relationship between the SMF and the UPF obtained in step 502, and formulates a UPF selection policy for SMF1 according to the UPF selection parameters and the information of the UPF connected to SMF1. It sends a UPF selection strategy to SMF1. SMF1 receives and saves the UPF list and the UPF selection strategy.
  • SMF1 is connected to UPF1 and UPF2, and the UPF list sent by SCF to SMF1 is ⁇ UPF1, UPF2 ⁇ .
  • SMF1 further sends a response message to the SCF indicating that the UPF list and the UPF selection policy are received.
  • Step 505 SMF2 sends a second request message to the SCF according to the service address of the SCF.
  • step 505 reference may be made to step 503, and details are not described again.
  • Step 506 The SCF receives the second request message, sends the UPF list ⁇ UPF1, UPF2, UPF3 ⁇ to SMF1 according to the management relationship between SMF and UPF, and formulates a UPF selection policy for SMF2 according to the UPF selection parameter and the information of the UPF connected to SMF2. And send a UPF selection policy to SMF2, SMF2 receives and saves the UPF list and the UPF selection policy.
  • step 506 reference may be made to step 504, and details are not described again.
  • Step 507 UPF1 sends a third request message to the SCF according to the service address of the SCF.
  • the third request message may be a management request, where the management request carries a service address of UPF1, and the management request may be used to request the SCF to send an SMF list to UPF1.
  • the third request message may be a registration request.
  • the registration request may be used to indicate that UPF1 has completed instantiation and deployment, and may be managed by the SCF.
  • the registration request may carry the service address of UPF1.
  • Step 508 The SCF receives the third request message, and sends an SMF list to UPF1 according to the management relationship between the SMF and the UPF.
  • UPF1 receives and saves the SMF list.
  • UPF1 is connected to SMF1 and SMF2, and the SCF sends the SMF list ⁇ SMF1, SMF2 ⁇ to the UPF.
  • SMF1 sends the SMF list ⁇ SMF1, SMF2 ⁇ to the UPF.
  • UPF1 also sends a response message to the SCF indicating that the SMF list was received.
  • Step 509 UPF2 sends a fourth request message to the SCF according to the service address of the SCF.
  • step 509 reference may be made to step 507, and details are not described again.
  • Step 510 The SCF receives the fourth request message, and sends an SMF list ⁇ SMF2 ⁇ to the UPF2 according to the management relationship between the SMF and the UPF.
  • the UPF2 receives and saves the SMF list.
  • step 510 reference may be made to step 508, and details are not described again.
  • UPF3 can also send a request message to the SCF to receive and save the SMF list ⁇ SMF1, SMF2 ⁇ from the SCF (not shown in FIG. 5).
  • steps 503 to 504 does not limit the execution order of steps 503 to 504, steps 505 to 506, steps 507 to 508, steps 509 to 510, steps 503 to 504, steps 505 to 506, Steps 507 to 508 and steps 509 to 510 may be performed in parallel, or may be performed in sequence as shown in FIG. 5 without limitation.
  • Step 511 The SMF1 establishes a communication connection with the UPF according to the UPF list saved by the SMF1, and selects, based on the UPF selection policy saved by the SMF1, a UPF to establish a user plane bearer for the end user.
  • step 511 reference may be made to step 404, and details are not described again.
  • Step 512 The SMF2 establishes a communication connection with the UPF according to the UPF list saved by the SMF2, and selects, based on the UPF selection policy saved by the SMF2, a UPF to establish a user plane bearer for the end user.
  • step 512 reference may be made to step 511, and details are not described again.
  • Step 513 The UPF1 establishes a communication connection with the SMF according to the SMF list saved by the UPF1, and accepts node-level management information or session-level management information of the SMF with which the communication connection is established.
  • step 513 reference may be made to step 405, and details are not described herein again.
  • Step 514 The UPF2 establishes a communication connection with the SMF according to the SMF list saved by the UPF2, and accepts node-level management information or session-level management information of the SMF with which the communication connection is established.
  • step 514 reference may be made to step 510, and details are not described again.
  • UPF3 can also establish a communication connection with the SMF according to its saved SMF list, and accept node-level management information or session-level management information of the SMF with which the communication connection is established (not shown in Figure 5).
  • Steps 511, 512, 513, and 514 may be performed in parallel or in the order shown in FIG. 5 No restrictions.
  • the SCF obtains the management relationship between the SMF and the UPF planned by the operator and the UPF selection parameters, and then sends the UPF list and UPF selection policy to the SMF according to the obtained management relationship.
  • a communication connection is established between the SMF and the UPF, and an UPF carried by the user plane is selected for the end user.
  • the SMF and UPF are managed in a unified manner through the SCF, and the information required for the SMF and UPF link connection is distributed to realize the automatic deployment and connection of the SMF and UPF.
  • the method may further include:
  • the SCF receives the work status information reported by each UPF
  • the SCF updates the UPF selection policy of the SMF according to the work status information reported by each UPF, and sends the updated UPF selection policy to the SMF.
  • the SMF can be one or more SMFs managed by the SCF, such as SMF1 in Figure 2a And / or SMF2.
  • the UPF selection strategy of each SMF can be dynamically and uniformly adjusted based on the working situation of the UPF of the entire network, so that the UPF selection between multiple SMFs is more cooperative, and avoiding the lack of a global perspective when multiple SMFs independently select the UPF, resulting in UPF The problem of uneven business load.
  • the method may further include:
  • the SCF updates the UPF list and the UPF selection policy originally issued to the SMF, and sends the updated UPF list and the UPF selection policy to the SMF. Further, the SCF can also send an SMF list to the newly added UPF.
  • a new UPF4 is added to the system, where UPF4 is connected to SMF2, and the SCF updates the UPF list of SMF2 ⁇ UPF1, UPF2, UPF3 ⁇ to ⁇ UPF1, UPF2, UPF3, UPF4 ⁇ , which will be updated
  • the subsequent UPF list ⁇ UPF1, UPF2, UPF3, UPF4 ⁇ is sent to SMF2, and the SMF list ⁇ SMF2 ⁇ is sent to UPF4, so that UPF4 establishes a communication connection with SMF2.
  • the weight of the SMF to select the UPF can be increased in the initial stage.
  • the SCF can increase the weight of the UPF4 in the UPF selection strategy issued to the SMF2, so that the subsequent SMF2 preferentially selects the UPF4.
  • the SCF can delete the UPF information from the UPF list and resend the updated UPF list to the SMF.
  • the SCF can also actively notify the SMFs that manage the UPF not to select the UPF .
  • the SCF can timely maintain the management relationship between the network elements by issuing an updated UPF list, and adjust the UPF selection strategy to coordinate the UPFs managed by the SMFs in time, without the need for manual manual Updates are quick and easy.
  • the method may further include:
  • the SCF updates the SMF list originally delivered to the UPF, and sends the updated SMF list to the UPF. Further, the SCF can also send a UPF list and a UPF selection policy to the newly added SMF.
  • SMF3 is newly added to the system, where SMF3 is connected to UPF2 and UPF3, the SCF updates the SMF list ⁇ SMF2 ⁇ of UPF2 to ⁇ SMF2, SMF3 ⁇ , and updates the updated SMF list ⁇ SMF2 , SMF3 ⁇ to UPF2, update the SMF list ⁇ SMF1, SMF2 ⁇ of UPF3 to ⁇ SMF1, SMF2, SMF3 ⁇ , send the updated SMF list ⁇ SMF1, SMF2, SMF3 ⁇ to UPF3, and send to SMF3 Send UPF list ⁇ UPF2, UPF3 ⁇ and UPF selection policy, so that SMF3 establishes a communication connection with UPF2, UPF3, and selects UPF from UPF2 and UPF3.
  • the SCF can timely maintain the management relationship between the network elements by issuing an updated SMF list, and by sending UPF selection policies to the newly added SMFs, it can timely coordinate the management among the SMFs.
  • UPF no manual update required, simple and fast.
  • the method further includes: the SCF obtains configuration data planned by the operator, and configures the network shown in FIG. 2 a according to the configuration data. SMF and UPF.
  • the configuration data of each network element is centrally managed through the SCF, which avoids the problem of redundant configuration data caused by each SMF sending the same configuration data to the UPF when the same UPF is managed by multiple SMFs, and different SMF addresses the problem of configuration conflicts caused by different configuration data delivered by the same configuration object.
  • each node such as a service control network element, a user plane network element, and a session management network element, includes a hardware structure and / or a software module corresponding to each function.
  • this application can be implemented in hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
  • FIG. 6 shows a schematic diagram of a possible composition of a service control network element, and the service control network element may be used to perform functions of the service control network element involved in the foregoing embodiment.
  • the service control network element may include: an obtaining unit 60 and a sending unit 61;
  • the obtaining unit 60 is configured to obtain a management relationship between a session management network element and a user plane network element in the network; for example, the support service control network element executes step 401.
  • a sending unit 61 is configured to send a user plane network element list determined by a management relationship and used to characterize a user plane network element managed by the first session management network element to any first session management network element in the network, and A user plane network element selection strategy for the first session management network element to select a user plane network element; and sending a session management network for any first user plane network element in the network to characterize and manage the connection of the first user plane network element Meta-session management NE list.
  • the support service control network element performs steps 402 and 403.
  • the service control network element may be a communication device including a processing module and a communication module.
  • the communication device exists in the form of a chip product.
  • the processing module may integrate the function of the acquisition unit 60.
  • the communication module The function of the transmitting unit 61 may be integrated.
  • the processing module is used to support the apparatus to perform step 401 and other processes of the techniques described herein.
  • the communication module is configured to support communication between the device and other network entities, such as communication with the functional module or network entity shown in FIG. 1.
  • the device may further include a storage module for storing program code and data of the device.
  • the processing module may be a processor or a controller. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
  • a processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication module may be a transceiver circuit or a communication interface.
  • the memory module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the apparatus involved in this embodiment of the present application may be the communication device shown in FIG. 3.
  • FIG. 7 shows a possible composition diagram of a session management network element.
  • the session management network element is any session management network element in the network and can be used to perform the functions of the session management network element involved in the foregoing embodiment.
  • the session management network element may include a receiving unit 70 and a processing unit 71.
  • the receiving unit 70 is configured to receive, from a service control network element, a user plane network element list determined by the management relationship, and used to characterize a user plane network element belonging to the user plane network element managed by the first session management network element, and used for the The user plane network element selection strategy of the first session management network element selecting the user plane network element; for example, the session management network element supporting step 404 is performed.
  • a processing unit 71 is configured to establish a communication connection between the user plane network element list and the user plane network element received by the receiving unit 70, and select a user plane network element that establishes a user plane bearer for the end user according to the user plane network element selection policy. .
  • a session management network element performs step 404.
  • the session management network element provided in the embodiment of the present application is used to implement the foregoing method for managing a network element, and therefore, the same effect as that of the foregoing method for managing a network element can be achieved.
  • the session management network element may be a communication device including a processing module and a communication module.
  • the communication device exists in the form of a chip product.
  • the processing module may integrate the functions of the processing unit 71.
  • the communication module The functions of the receiving unit 70 may be integrated.
  • the processing module is used to support the apparatus to perform step 401 and other processes of the techniques described herein.
  • the communication module is configured to support communication between the device and other network entities, such as communication with the functional module or network entity shown in FIG. 1.
  • the device may further include a storage module for storing program code and data of the device.
  • the processing module may be a processor or a controller. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
  • a processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication module may be a transceiver circuit or a communication interface.
  • the memory module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the apparatus involved in this embodiment of the present application may be a communication device as shown in FIG. 3.
  • FIG. 8 shows a possible composition diagram of a user plane network element.
  • the user plane network element is any user plane network element in the network and can be used to perform the functions of the user plane network element involved in the foregoing embodiment.
  • the user plane network element may include a receiving unit 80 and a processing unit 81.
  • the receiving unit 80 is configured to receive, from the service control network element, a session management network element list determined by a management relationship and used to represent a session management network element that manages the connection of the first user plane network element; for example, the user plane network element performs step 405 .
  • the processing unit 81 is configured to establish a communication connection with the user plane network element according to the user plane network element list received by the receiving unit 80, and select a user plane network element that establishes a user plane bearer for the end user according to the user plane network element selection policy. . For example, if the user plane network element is supported, step 405 is performed.
  • the user plane network element provided in the embodiment of the present application is used to execute the foregoing method for managing a network element, and therefore, the same effect as that of the foregoing method for managing a network element can be achieved.
  • the above-mentioned user plane network element may be a communication device including a processing module and a communication module, wherein the communication device exists in the form of a chip product, and the processing module may integrate the function of the processing unit 81.
  • the communication module The function of the receiving unit 80 may be integrated.
  • the processing module is used to support the apparatus to perform step 401 and other processes of the techniques described herein.
  • the communication module is configured to support communication between the device and other network entities, such as communication with the functional module or network entity shown in FIG. 1.
  • the device may further include a storage module for storing program code and data of the device.
  • the processing module may be a processor or a controller. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the disclosure of this application.
  • a processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication module may be a transceiver circuit or a communication interface.
  • the memory module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the apparatus involved in this embodiment of the present application may be the communication device shown in FIG. 3.
  • FIG. 9 is a schematic diagram of a system for managing a network element according to an embodiment of the present application.
  • the system may include a service control network element 90, multiple session management network elements 91, and multiple user plane network elements. 92.
  • the service control network element 90 may establish communication connections with multiple session management network elements 91 and multiple user plane network elements 92, and centrally manage these session management network elements 91 and user plane network elements 92.
  • one session management network element 91 may establish a communication connection with one or more user plane network elements 92 at the same time
  • one user plane network element 92 may establish a communication connection with one or more session management network elements at the same time.
  • the service control network element 90 can be used to obtain the management relationship between the session management network element and the user plane network element in the network, and send the management relationship to any one of the plurality of session management network elements 91. Determined and used to characterize a user plane network element list belonging to the user plane network element managed by the session management network element 91, and a user plane network element selection strategy for the session management network element 91 to select the user plane network element; Any user plane network element 92 of the user plane network elements sends a session management network element list for characterizing the session management network element connected to the management user plane network element 92; the session management network element 91 is configured to The network element list establishes a communication connection with the user plane network elements, and selects a user plane network element to establish a user plane bearer for the end user according to the user plane network element selection strategy; the user plane network element 92 is used to manage the network element according to the session The list establishes a communication connection with the session management network element, and accepts node-level management information or session-level management
  • the session management network element and the user plane network element can be uniformly managed by the service control network element, and the information required for the connection between the session management network element and the user plane network element can be centrally distributed to realize the session management network element Automatic deployment and connection with user plane network elements.
  • the disclosed apparatus and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the modules or units is only a logical function division.
  • multiple units or components may be divided.
  • the combination can either be integrated into another device, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the unit described as a separate component may or may not be physically separated, and the component displayed as a unit may be a physical unit or multiple physical units, that is, may be located in one place, or may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit.
  • the integrated unit When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium.
  • the technical solutions of the embodiments of the present application essentially or partly contribute to the existing technology or all or part of the technical solutions may be embodied in the form of a software product, which is stored in a storage medium
  • the instructions include a number of instructions for causing a device (which can be a single-chip microcomputer, a chip, or the like) or a processor to execute all or part of the steps of the method described in each embodiment of the present application.
  • the foregoing storage medium includes various media that can store program codes, such as a U disk, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例公开了一种管理网元的方法、设备及系统，由服务控制网元集中管理会话管理网元和用户面网元。该方法包括：服务控制网元获取网络中会话管理网元与用户面网元之间的管理关系，向第一会话管理网元发送由管理关系确定，且用于表征归属于第一会话管理网元管理的用户面网元的用户面网元列表、以及用于第一会话管理网元选择用户面网元的用户面网元选择策略；以及向第一用户面网元发送用于表征管理第一用户面网元连接的会话管理网元的会话管理网元列表。

Description

一种管理网元的方法、设备及系统
本申请要求于2018年6月22日提交中国国家知识产权局、申请号为201810654545.2、发明名称为“一种管理网元的方法、设备及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种管理网元的方法、设备及系统。
背景技术
在第五代(5th Generation，5G)发展的初期阶段，会话管理功能(Session Management Function，SMF)与用户面功能(User Plane Function，UPF)之间为1：M(M为大于或者等于2的整数)的部署形态。在该部署形态下，同一SMF可以从多个UPF中选择一个或者多个UPF，并管理选择的UPF，如：负责UPF的策略(如：策略与计费控制(Policy and Charging Control，PCC)规则)下发，以及接收UPF的事件上报等非会话级的管理功能等。
随着5G业务的持续发展，第三代合作伙伴项目(the 3rd Generation Partnership Project，3GPP)协议规定SMF和UPF之间可以采用N：M的全连接方式部署，N为大于或者等于2的整数，如：一个SMF可能与M个UPF连接，管理多个UPF；一个UPF可能与N个SMF连接，被多个SMF管理。在此部署形态下，由于同一UPF可能被多个SMF共同管理，多个SMF分配给同一UPF的关键信息(如：UPF的因特网协议(Internet Protocol，IP)地址、隧道端点标识符(Tunnel Endpoint Identifier，TEID)等)可能不同，存在配置冲突。此外，各个SMF独立地根据其管理的UPF的信息选择UPF，容易导致UPF负荷不均。并且当网络拓扑发生更新时，需要手动逐一更新网元上的信息，浪费人力且耗时较长。
发明内容
本申请提供一种管理网元的方法、设备及系统，由服务控制网元集中管理会话管理网元和用户面网元。
为达到上述目的，本申请采用如下技术方案：
第一方面，本申请提供一种管理网元的方法，该方法包括：服务控制网元获取网络中会话管理网元与用户面网元之间的管理关系，向网络中的任一第一会话管理网元发送由管理关系确定，且用于表征归属于第一会话管理网元管理的用户面网元的用户面网元列表、以及用于第一会话管理网元选择用户面网元的用户面网元选择策略；以及向网络中的任一第一用户面网元发送用于表征管理第一用户面网元连接的会话管理网元的会话管理网元列表。基于本申请提供的管理网元的方法，服务控制网元获取网络中会话管理网元与用户面网元间的管理关系后，根据获取到的管理关系集中向会话管理网元发送用户面网元列表和用户面网元选择策略，向用户面网元发送会话管理网元列表，以便会话 管理网元与用户面网元间建立通信连接，以及为终端用户选择建立用户面承载的用户面网元，即通过服务控制网元对会话管理网元和用户面网元进行统一管理，集中下发会话管理网元和用户面网元建立通信连接所需的信息，实现会话管理网元和用户面网元的自动部署和通信连接。
在一种可能的设计中，结合第一方面，所述方法还包括：服务控制网元接收网络中每个用户面网元上报的工作状态信息，根据每个用户面网元上报的工作状态信息(如：承载的会话数、吞吐量、中央处理单元CPU负荷、功能使能统计、资源使用情况、运行情况中的一个或多个信息)更新用户面网元选择策略，向第一会话管理网元发送更新后的用户面网元选择策略。如此，可以基于整个网络中用户面网元的工作情况动态统一调整下发给会话管理网元的用户面网元选择策略，让多个会话管理网元之间的用户面网元选择更为协同，避免多个会话管理网元独立选择用户面网元时，因缺少全局视角，导致用户面网元的业务负荷不均的问题。
在又一种可能的设计中，结合第一方面或者上述任一可能的设计，所述方法还包括：当新增或删除与第一会话管理网元连接的用户面网元时，服务控制网元更新用户面网元列表以及用户面网元选择策略，向第一会话管理网元发送更新后的用户面网元列表以及用户面网元选择策略。如此，当网络中新增或删除用户面网元时，服务控制网元可以通过下发更新后的用户面网元列表及时维护网元间的管理关系，以及通过调整用户面网元选择策略来及时协调各个会话管理网元间管理的用户面网元，无需人工手动更新，简单快捷。
在又一种可能的设计中，结合第一方面或者上述任一可能的设计，所述方法还包括：当新增或删除与第一用户面网元连接的会话管理网元时，服务控制网元更新会话管理网元列表，并向第一用户面网元发送更新后的会话管理网元列表。如此，当网络中新增或删除会话管理网元时，服务控制网元可以通过下发更新后的会话管理网元列表及时维护网元间的管理关系，以及通过向新增会话管理网元下发用户面网元选择策略来及时协调各个会话管理网元间管理的用户面网元，无需人工手动更新，简单快捷。
在再一种可能的设计中，结合第一方面或者上述任一可能的设计，所述方法还包括：服务控制网元获取运营商规划的包括用户面网元和会话管理网元运行时所需要的配置参数、以及用户面网元转发数据报文时所遵循的过滤条件和处理策略的配置数据，根据配置数据配置网络中的会话管理网元和用户面网元。如此，通过服务控制网元对网络中各个网元的配置数据进行集中管理，避免了同一用户面网元被多个会话管理网元管理的情况下，各会话管理网元分别下发相同配置数据到同一用户面网元带来的配置数据冗余的问题，以及不同会话管理网元针对同一配置对象下发不同配置数据带来的配置冲突的问题。
第二方面，本申请提供一种服务控制网元，该服务控制网元可以实现上述各方面或者各可能的设计中服务控制网元所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。如：该服 务控制网元可以包括：获取单元，发送单元；
获取单元，用于获取网络中会话管理网元与用户面网元之间的管理关系；
发送单元，用于向网络中的任一第一会话管理网元发送由管理关系确定，且用于表征归属于第一会话管理网元管理的用户面网元的用户面网元列表、以及用于第一会话管理网元选择用户面网元的用户面网元选择策略；以及向网络中的任一第一用户面网元发送用于表征管理第一用户面网元连接的会话管理网元的会话管理网元列表。
其中，服务控制网元的具体实现方式可以参考第一方面或第一方面的任一种可能的设计提供的管理网元的方法中服务控制网元的行为功能，在此不再重复赘述。因此，该提供的服务控制网元可以达到与第一方面或者第一方面的任一种可能的设计相同的有益效果。
第三方面，提供了一种服务控制网元，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该服务控制网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该服务控制网元执行如上述第一方面或者第一方面的任一种可能的设计所述的管理网元的方法。
第四方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第一方面或者上述方面的任一种可能的设计所述的管理网元的方法。
第五方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第一方面或者上述方面的任一种可能的设计所述的管理网元的方法。
第六方面，提供了一种芯片系统，该芯片系统包括处理器、通信接口，用于支持服务控制网元实现上述方面中所涉及的功能，例如支持处理器通过通信接口获取服务控制网元获取网络中会话管理网元与用户面网元之间的管理关系，以及向网络中的任一第一会话管理网元发送由管理关系确定，且用于表征归属于第一会话管理网元管理的用户面网元的用户面网元列表和用于第一会话管理网元选择用户面网元的用户面网元选择策略；向网络中的任一第一用户面网元发送用于表征管理第一用户面网元连接的会话管理网元的会话管理网元列表。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存服务控制网元必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第三方面至第六方面中任一种设计方式所带来的技术效果可参见上述第一方面或者第一方面的任一种可能的设计所带来的技术效果，不再赘述。
第七方面，本申请提供一种管理网元的方法，该方法由网络中的任一会话管理网元执行，该方法包括包括：会话管理网元从服务控制网元接收由所述管理关系确定，且用于表征归属于所述第一会话管理网元管理的用户面网元的用户面网元列表以及用于所述第一会话管理网元选择用户面网元的用户面网元选择策略，根据接收到的用户面网元列表与用户面网元间建立通信连接，以及根据用户面网元选择策略选择出为终端用户建立用户面承载的用户面网元。基于本申请提供的方法，会话管理网元接受服务控制网元的管理，从服务控制网元获取会话管理网元建立通信连接所需的信息，实现会话管理网元自动部署和通信连接。
一种可能的设计中，结合第七方面，会话管理网元向服务控制网元发送携带会话管理 网元的服务地址的用于请求服务控制网元向会话管理网元发送用户面网元列表以及用户面网元选择策略的管理请求，接收服务控制网元发送的用户面网元列表和用户面网元选择策略。或者，会话管理网元向服务控制网元发送携带会话管理网元的服务地址的、用于指示会话管理网元已完成实例化部署的注册请求，接收服务控制网元发送的用户面网元列表和用户面网元选择策略。
又一种可能的设计中，结合第七方面或上述可能的设计，所述会话管理网元还包括：当新增或删除与会话管理网元建立通信连接的用户面网元时，从服务控制网元接收更新后的用户面网元列表以及用户面网元选择策略。如此，当网络中新增或删除用户面网元时，服务控制网元可以通过下发更新后的用户面网元列表及时维护网元间的管理关系，以及通过调整用户面网元选择策略来及时协调各个会话管理网元间管理的用户面网元，无需人工手动更新，简单快捷。
第八方面，本申请提供一种会话管理网元，该会话管理网元为网络中的任一会话管理网元，该会话管理网元可以实现上述各方面或者各可能的设计中会话管理网元所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。如：该会话管理网元可以包括：接收单元、处理单元。
接收单元，用于从服务控制网元接收由所述管理关系确定，且用于表征归属于所述第一会话管理网元管理的用户面网元的用户面网元列表以及用于所述第一会话管理网元选择用户面网元的用户面网元选择策略；
处理单元，用于根据接收到的用户面网元列表与用户面网元间建立通信连接，以及根据用户面网元选择策略选择出为终端用户建立用户面承载的用户面网元。
其中，会话管理网元的具体实现方式可以参考第七方面或第七方面的任一种可能的设计提供的管理网元的方法中会话管理网元的行为功能，在此不再重复赘述。因此，该提供的会话管理网元可以达到与第七方面或者第七方面的任一种可能的设计相同的有益效果。
第九方面，提供了一种会话管理网元，包括：处理器和存储器；该存储器用于存储计算机执行指令，当该会话管理网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该会话管理网元执行如上述第七方面或者第七方面的任一种可能的设计所述的管理网元的方法。
第十方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第七方面或者上述方面的任一种可能的设计所述的管理网元的方法。
第十一方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第七方面或者上述方面的任一种可能的设计所述的管理网元的方法。
第十二方面，提供了一种芯片系统，该芯片系统包括处理器、通信接口，用于支持会话管理网元实现上述方面中所涉及的功能，例如支持处理器通过通信接口从服务控制网元接收由所述管理关系确定，且用于表征归属于所述第一会话管理网元管理的用户面网元的用户面网元列表以及用于所述第一会话管理网元选择用户面网元的用户面网元选择 策略，根据接收到的用户面网元列表与用户面网元间建立通信连接，以及根据用户面网元选择策略选择出为终端用户建立用户面承载的用户面网元。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存会话管理网元必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第九方面至第十二方面中任一种设计方式所带来的技术效果可参见上述第七方面或者第七方面的任一种可能的设计所带来的技术效果，不再赘述。
第十三方面，本申请提供一种管理网元的方法，该方法可以由网络中的任一用户面网元执行，该方法包括：用户面网元从服务控制网元接收由管理关系确定，用于表征管理第一用户面网元连接的会话管理网元的会话管理网元列表，根据会话管理网元列表与会话管理网元间建立通信连接，接受与其建立通信连接的会话管理网元的节点级管理信息或会话级管理信息。基于本申请提供的方法，用户面网元接受服务控制网元的管理，从服务控制网元获取用户面网元建立通信连接所需的信息，实现用户面网元自动部署和通信连接。
一种可能的设计中，结合第十三方面，用户面网元从服务控制网元接收会话管理网元列表包括：用户面网元向服务控制网元发送携带用户面网元的服务地址的用于请求服务控制网元向用户面网元发送用户面网元列表以及用户面网元选择策略的管理请求，接收服务控制网元发送的用户面网元列表和用户面网元选择策略。或者，用户面网元向服务控制网元发送携带用户面网元的服务地址的、用于指示用户面网元已完成实例化部署的注册请求，接收服务控制网元发送的用户面网元列表和用户面网元选择策略。
又一种可能的设计中，结合第十三方面或者上述可能的设计，所述方法还包括：当新增或删除与用户面网元连接的会话管理网元时，用户面网元从服务控制网元获取更新后的会话管理网元列表。如此，当网络中新增或删除会话管理网元时，服务控制网元可以通过下发更新后的会话管理网元列表及时维护网元间的管理关系，以及通过向新增会话管理网元下发用户面网元选择策略来及时协调各个会话管理网元间管理的用户面网元，无需人工手动更新，简单快捷。
第十四方面，本申请提供一种用户面网元，该用户面网元可以实现上述各方面或者各可能的设计中用户面网元所执行的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。如：该用户面网元可以包括：接收单元，处理单元；
接收单元，用于从服务控制网元接收由管理关系确定，用于表征管理第一用户面网元连接的会话管理网元的会话管理网元列表；
处理单元，用于根据会话管理网元列表与会话管理网元间建立通信连接，接受与其建立通信连接的会话管理网元的节点级管理信息或会话级管理信息。
其中，用户面网元的具体实现方式可以参考第十三方面或第十三方面的任一种可能的设计提供的管理网元的方法中用户面网元的行为功能，在此不再重复赘述。因此，该提供的用户面网元可以达到与第十三方面或者第十三方面的任一种可能的设计相同的有益效果。
第十五方面，提供了一种用户面网元，包括：处理器和存储器；该存储器用于存储计 算机执行指令，当该用户面网元运行时，该处理器执行该存储器存储的该计算机执行指令，以使该用户面网元执行如上述第十三方面或者第十三方面的任一种可能的设计所述的管理网元的方法。
第十六方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述第十三方面或者上述方面的任一种可能的设计所述的管理网元的方法。
第十七方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述第十三方面或者上述方面的任一种可能的设计所述的管理网元的方法。
第十八方面，提供了一种芯片系统，该芯片系统包括处理器、通信接口，用于支持用户面网元实现上述方面中所涉及的功能，例如支持处理器通过通信接口从服务控制网元接收由管理关系确定，用于表征管理第一用户面网元连接的会话管理网元的会话管理网元列表，根据会话管理网元列表与会话管理网元间建立通信连接，接受与其建立通信连接的会话管理网元的节点级管理信息或会话级管理信息。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存用户面网元必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
其中，第十五方面至第十八方面中任一种设计方式所带来的技术效果可参见上述第十三方面或者第十三方面的任一种可能的设计所带来的技术效果，不再赘述。
第十九方面，本申请提供一种管理网元的系统，该管理网元的系统包括如第二方面至第六方面所述的服务控制网元、多个如第八方面至第十二方面所述的会话管理网元以及多个如第十四方面至第十八方面所述的用户面网元。
附图说明
图1为本申请实施例提供的一种系统架构的简化示意图；
图2a为本申请实施例提供的5G系统的简化示意图；
图2b为本申请实施例提供的4G系统的简化示意图；
图3为本申请实施例提供的一种通信设备的组成示意图；
图4为本申请实施例提供的一种管理网元的方法流程图；
图5为本申请实施例提供的又一种管理网元的方法流程图；
图6为本申请实施例提供的一种服务控制网元的组成示意图；
图7为本申请实施例提供的一种会话管理网元的组成示意图；
图8为本申请实施例提供的一种用户面网元的组成示意图；
图9为本申请实施例提供的一种管理网元的系统组成示意图。
具体实施方式
下面结合说明书附图对本申请实施例提供的方案进行描述。
本申请实施例提供的管理网元的方法可以适用于图1所示系统，该系统可以包括：服务控制网元、多个会话管理网元(如会话管理网元1、会话管理网元2)、多个用户面网元(如用户面网元1、用户面网元2等)，还可以包括：终端、接入网设备、接入和移动性管 理功能实体(Access and Mobility Management Function，AMF)、数据网络(Data Network，DN)等。需要说明的是，图1仅为示例性附图，除图1所示网元之外，该系统还可以包括其他网元，同时，本申请实施例对图1所示系统包括的网元的数量也不予限制。
其中，图1中的服务控制网元可称为服务控制功能(Service Control Function，SCF)，服务控制网元可以独立部署在图1所示系统中，还可以部署在图1所示系统中的某个核心网网元中。服务控制网元具有维护图1所示网络中会话管理网元与用户面网元间的管理关系、统一编排各个会话管理网元选择用户面网元所需的用户面网元选择策略等功能。例如，服务控制网元可以获取网络中会话管理网元与用户面网元之间的管理关系，向网络中的任一第一会话管理网元发送由管理关系确定，且用于表征归属于第一会话管理网元管理的用户面网元的用户面网元列表、以及用于第一会话管理网元选择用户面网元的用户面网元选择策略；以及向网络中的任一第一用户面网元发送用于表征管理第一用户面网元连接的会话管理网元的会话管理网元列表。具体的，服务控制网元的功能可参照图4中所述。
图1中的会话管理网元可以同时与M(M为大于或等于2的整数)个用户面网元建立通信连接，且可以根据用户面网元选择策略从与其建立通信连接的用户面网元中选择为终端用户建立用户面承载的用户面网元，并管理选择的用户面网元，如：主要用于实现其管理的用户面网元上用户面传输路径的建立、释放和更改等会话管理功能。
图1中的用户面网元可以同时与N(N为大于或等于2的整数)个会话管理网元建立通信连接，并接受N个会话管理网元中部分或全部会话管理网元的节点级管理或者会话级管理，并在会话管理网元的管理下建立用户面承载的建立、完成用户面数据的路由转发等功能，如：与终端间建立通道(即用户面传输路径)，在该通道上转发终端和DN之间的数据包；以及负责对终端的数据报文过滤、数据传输/转发、速率控制、生成计费信息等。
其中，图1所示系统可以为图2a所示的第五代(5th Generation，5G)系统，还可以为图2b所示的第四代(4 thGeneration)，又可以为后续演进的通信系统，本申请实施例对此不予限制。当图1所示系统为图2a所示5G系统时，图1中的会话管理网元可以为会话管理功能(session management function，SMF)，用户面网元可以为用户面功能(user plane function，UPF)。在5G系统中，各网元之间可以通过下一代网络(next generation，NG)接口(图2a中未示出)建立通信连接实现通信，如：UPF可以通过NG接口4(简称N4)与SMF建立控制面信令连接，UPF可以通过NG接口6(简称N6)与数据网络交互用户面数据，SCF可以通过新增的NG接口x(简称Nx)(暂未定义)与SMF、以及UPF建立控制面信令连接。需要说明的是，图2a仅为示例性架构图，除图2a中所示网元之外，该5G系统还可以包括其他网元，如：终端、接入网设备、接入和移动性管理功能(Access and Mobility Management Function，AMF)等，本申请实施例对此不进行限定。
当图1所示通信网络为图2b所示4G系统时，图1中的会话管理网元可以为控制面服务网关(Serving GateWay-Control，SGW-C)/控制面公用数据网网关(Public Data NetWorks GateWay-Control，PGW-C)，还可以为控制面探测功能网元(Traffic Detection Function-Control，TDF-C)，用户面网元可以为用户面服务网关(Serving GateWay-User，SGW-U)/用户面公用数据网网关(Public Data NetWorks GateWay-User，PGW-U)，还可以为用户面探测功能网 元(Traffic Detection Function-User，TDF-U)。在4G系统中，SGW-U/PGW-U可以通过Gx接口与SGW-C/PGW-C建立控制面信令连接；SCF可以通过服务化接口与SGW-C/PGW-C、SGW-U/PGW-U建立控制面信令连接。需要说明的是，图2b中的SGW-C/PGW-C和SGW-U/PGW-U可以如图2b所示，独立部署在4G系统，还可以将SGW-C/PGW-C和SGW-U/PGW-U集成在同一网元(如SGW/PGW/TDF)中。此外，图2b仅为示例性架构图，除图2b中所示网元之外，该网络架构还可以包括其他网元，如：终端、接入网设备、移动管理实体(Mobile Management Entity，MME)等，本申请实施例对此不进行限定。
需要说明的是，上述架构中的网元以及各个网元之间的接口名字只是一个示例，具体实现中网元以及网元之间的接口名字可能为其他名字，本申请实施例对此不作具体限定。
具体的，为了实现本申请实施例提供的管理网元的方法，图1中的服务控制网元、会话管理网元、用户面网元等网元可以包括图3所示部件。图3为本申请实施例提供的一种通信设备的组成示意图，如图3所示，该通信设备300包括至少一个处理器301，通信线路302，以及至少一个通信接口303；进一步的，还可以包括存储器304。其中，处理器301，存储器304以及通信接口303三者之间可以通过通信线路302连接。
处理器301可以是一个中央处理器(Central Processing Unit，CPU)，也可以是特定集成电路(Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个数字信号处理器(Digital Signal Processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)。
通信线路302可包括一通路，用于在通信设备包括的部件之间传送信息。
通信接口303，用于与其他设备或通信网络通信，可以使用任何收发器一类的装置，如以太网，无线接入网(Radio Access Network，RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。
存储器304可以是只读存储器(Read-Only Memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(Random Access Memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。一种可能的设计中，存储器304可以独立于处理器301存在，即存储器304可以为处理器301外部的存储器，此时，存储器304可以通过通信线路302与处理器301相连接，用于存储执行指令或者应用程序代码，并由处理器301来控制执行，实现本申请下述实施例提供的管理网元的方法。又一种可能的设计中，存储器304也可以和处理器301集成在一起，即存储器304可以为处理器301的内部存储器，例如，该存储器304为高速缓存，可以用于暂存一些数据和指令信息等。
作为一种可实现方式，处理器301可以包括一个或多个CPU，例如图3中的CPU0和CPU1。作为另一种可实现方式，通信设备300可以包括多个处理器，例如图3中的处理器301和处理器307。作为再一种可实现方式，通信设备300还可以包括输出设备305和输入 设备306。
需要说明的是，上述的通信设备300可以是一个通用设备或者是一个专用设备。例如，通信设备300可以是台式机、便携式电脑、网络服务器、PDA、移动手机、平板电脑、无线终端、嵌入式设备或有图3中类似结构的设备。本申请实施例不限定通信设备300的类型。
下面结合图1所示通信系统，对本申请实施例提供的管理网元的方法进行描述。需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
图4为本申请实施例提供的一种管理网元的方法，用于通过服务控制网元管理图1所示网络中的多个会话管理网元和用户面网元。如图4所示，该方法可以包括步骤401～步骤405。
步骤401：服务控制网元获取网络中会话管理网元与用户面网元之间的管理关系。
其中，会话管理网元与用户面网元间的管理关系用于指示运营商规划的网络(如某个特定网络切片)中会话管理网元与用户面网元间的物理连接关系，即用于指示哪个会话管理网元与哪个用户面网元建立物理连接。例如，运营商规划的网络如图1所示，则会话管理网元与用户面网元间的管理关系可以为：会话管理网元1与用户面网元1、用户面网元3连接，会话管理网元2与用户面网元1、用户面网元2、用户面网元3连接。在本申请各实施例中，物理连接可以指：网元间通过有线传输介质(如双绞线、同轴电缆和光纤等)或无线传输介质(如无线电波、微波等)建立的连接，物理连接的网元间可以建立一个或多个通信连接，通过通信链路实现互相通信。
具体的，服务控制网元可以从运营商获取网络中会话管理网元与用户面网元之间的管理关系。一种示例中，运营商可以通过业务支撑系统(Business Support System，BSS)/运营支撑系统(Operation Support System，OSS)向服务控制网元发送会话管理网元与用户面网元间的管理关系。又一种示例中，运营商可以通过服务控制网元的用户界面(User Interface，UI)向服务控制网元输入会话管理网元与用户面网元间的管理关系。再一种示例中，服务控制网元开机之后，可以通过BSS/OSS向运营商发送请求消息，请求运营商发送会话管理网元与用户面网元间的管理关系，运营商接收到该请求消息后，通过BSS/OSS向服务控制网元发送会话管理网元与用户面网元间的管理关系。
步骤402：服务控制网元向第一会话管理网元发送用户面网元列表以及用于第一会话管理网元选择用户面网元的用户面网元选择策略，第一会话管理网元接收用户面列表以及用户面网元选择策略。
其中，第一会话管理网元为图1所示网络中的任一会话管理网元。服务控制网元可以在第一会话管理网元完成实例化部署后，接收第一会话管理网元发送的请求消息，根据接收到的请求消息向第一会话管理网元发送用户面网元列表以及用户面网元选择策略。
如：服务控制网元向第一会话管理网元发送携带服务控制网元从虚拟网络功能管理 实体(Virtual Network Function Management，VNFM)中请求的第一会话管理网元启动时需要使用的软件包下载路径、部署策略、服务的组网信息、服务的初始运行资源(如：缓存资源、网元的服务地址、服务控制网元的服务地址)等信息，实现第一会话管理网元的实例化部署。随后，第一会话管理网元可以向服务控制网元发送携带第一会话管理网元的服务地址的管理请求，请求服务控制网元向第一会话管理网元发送用户面网元列表以及用户面网元选择策略，服务控制网元接收到管理请求后，向第一会话管理网元发送用户面网元列表和用户面网元选择策略。或者，第一会话管理网元可以向服务控制网元发送携带第一会话管理网元的服务地址的、用于指示第一会话管理网元已完成实例化部署的注册请求，服务控制网元接收到注册请求后，向第一会话管理网元发送用户面网元列表和用户面网元选择策略。
其中，用户面网元列表由管理关系确定，且用于表征归属于第一会话管理网元管理的用户面网元；用户面网元列表可以包括与会话管理网元1连接的用户面网元的信息，用户面网元的信息用于标识用户面网元，可以为用户面网元的标识(Identity，ID)，或者用户面网元的服务地址(如：用户面网元的统一资源定位符(Uniform Resource Locator，URL)或者用户面网元的N4接口地址)等。例如，以图1为例，会话管理网元1与用户面网元1、用户面网元2连接，则服务控制网元向会话管理网元1发送的用户面网元列表为{用户面网元1、用户面网元2}。
其中，用户面网元选择策略定义了会话管理网元选择的用户面网元需要满足的一个或多个条件，用户面网元选择策略可以由用户面网元选择参数以及由第一会话管理网元管理的用户面网元的信息确定。用户面网元选择参数可以包括运营商提前规划好的、会话管理网元选择用户面网元时所依据的一些参数，这些参数可以为典型的用户面网元选择参数，如：用户面网元的部署位置、用户面网元的负荷、用户面网元对外提供的业务能力、用户面网元的系统容量、用户面网元的功能部署、组网方式、用户的签约策略、用户使用的接入技术或者其他现有通信标准中选择用户面网元时所参考的因素等。其中，用户面网元的部署位置可以指用户面网元在整个通信系统中的物理位置，可以用地理坐标或者区域范围表示。用户面网元的负荷可以指用户面网元的CPU占用率、用户面网元的存储能力等。用户面网元对外提供的业务能力可以用于定义用户面网元对外提供的业务的情况，可以包括用户面网元收/发业务的类型、用户面网元收/发业务的时间周期、用户面网元收/发业务的包大小、用户面网元收/发业务的功率、用户面网元收/发业务的带宽大小等。用户面网元的系统容量可以指用户面网元在一定时间内可以承载的最大会话数。用户面网元的功能部署可以指用户面网元承载的会话所支持的能力，如带宽大小、时延等情况。组网方式可以指用户面网元与用户要访问的DN是否有连接。用户的签约策略可以用于规定用户签约的用户面网元。用户使用的接入技术可以指用户接入网络所使用的接入技术，可以为第三代(3th Generation，3G)技术或4G技术或5G，不同接入技术可以对应不同用户面网元。需要说明的是，服务控制网元在为会话管理网元执行用户面网元选择策略时，上述参数中用户面网元的部署位置、用户面网元的负荷、用户面网元的系统容量对应的属性值可以根据会话管理网元管理的用户面网元的情况动态 调整，而其他参数的属性值基本是预制好的参数，其对应的属性值固定不变。
用户面网元选择策略可以包括：用户面网元的部署位置、用户面网元的负荷、用户面网元对外提供的业务能力、用户面网元的系统容量、用户面网元的功能部署、组网方式、用户的签约策略、用户使用的接入技术、用户面网元的权重或者其他现有通信标准中选择用户面网元时所参考的因素等，会话管理网元选择的用户面网元需要满足这些条件中的部分或者全部条件。其中，用户面网元的权重用于表征用户面网元在会话管理网元选择的多个用户面网元中承载会话的能力。比如：会话管理网元1选择的用户面网元为用户面网元1和用户面网元3，用户面网元1的权重为10、用户面网元3权重为90，当需要建立100个会话时，会话管理网元1会请求用户面网元1建立10个会话，请求用户面网元2建立90个会话。例如，用户面网元选择策略为{用户面网元的部署位置在区域A，用户面网元对外可提供业务1}，此时，若与会话管理网元1连接的用户面网元1和用户面网元2中，用户面网元1位于区域A，且对外可提供业务1；用户面网元2位于区域B，且对外可提供业务1，则会话管理网元1可以根据用户面网元选择策略规定的条件，确定满足用户选择策略的用户面网元为用户面网元1。
步骤403：服务控制网元向第一用户面网元发送会话管理网元列表，第一用户面网元接收会话管理网元列表。
其中，第一用户面网元为图1所示网络中的任一用户面网元。服务控制网元可以在第一用户面网元完成实例化部署后，接收第一用户面网元发送的请求消息，根据接收到的请求消息向第一用户面网元发送会话管理网元列表。
如：服务控制网元向第一用户面网元发送携带服务控制网元从VNFM中请求的第一用户面网元启动时需要使用的软件包下载路径、部署策略、服务的组网信息、服务的初始运行资源(如：缓存资源、网元的服务地址、服务控制网元的服务地址)等信息，实现第一用户面网元的实例化部署。随后，第一用户面网元可以向服务控制网元发送携带第一用户面网元的服务地址的管理请求，请求服务控制网元向第一用户面网元发送用户面网元列表以及用户面网元选择策略，服务控制网元接收到管理请求后，向第一用户面网元发送会话管理网元列表。或者，第一用户面网元可以向服务控制网元发送携带第一用户面网元的服务地址的、用于指示第一用户面网元已完成实例化部署的注册请求，服务控制网元接收到注册请求后，向第一用户面网元发送会话管理网元列表。
其中，会话管理网元列表由管理关系确定，用于表征管理第一用户面网元连接的会话管理网元。会话管理网元列表可以包括与用户面网元1连接的会话管理网元的信息，会话管理网元的信息可以用于标识会话管理网元，可以是会话管理网元的ID，或者会话管理网元的服务地址(如：会话管理网元的URL或者会话管理网元的N4接口地址)，或者会话管理网元的服务化接口地址(N会话管理网元)。例如，以图1为例，用户面网元1与会话管理网元1、会话管理网元2连接，则服务控制网元向用户面网元发送会话管理网元列表{会话管理网元1、会话管理网元2}。
需要说明的是，本申请实施例不限制步骤402、步骤403的执行顺序，除图4所示， 本申请实施例也可以先执行步骤403、再执行步骤402，或者同时执行步骤402和步骤403，不予限制。
步骤404：第一会话管理网元根据接收到的用户面网元列表与用户面网元间建立通信连接，并根据用户面网元选择策略选择出为终端用户建立用户面承载的用户面网元。
其中，步骤404可参照现有流程，如：当第一会话管理网元接收用户面网元发送的、携带有用户面网元的信息的链路建立请求(如：N4链路建立请求)时，第一会话管理网元查看本地保存的用户面网元列表中是否记载有该用户面网元，若有，则向该用户面网元发送成功建立响应，以指示用户面网元与会话管理网元间成功建立通信连接，否则，拒绝用户面网元发送的链路建立请求。后续，当第一会话管理网元接收到终端用户发送的会话建立请求(Session Establishment Request)/会话修改请求(Session Modification Request)时，第一会话管理网元可以根据用户面网元选择策略从与第一会话管理网元建立链路建立的用户面网元中，为终端用户选择出建立用户面承载的用户面网元。其中，选择出的用户面网元符合用户面网元选择策略所规定的条件，如：用户面网元的部署位置包括在用户面网元选择策略所规定的部署位置中、用户面网元的负荷小于或等于用户面网元选择策略所规定的负荷、用户面网元的系统容量大于或等于用户面网元选择策略所规定的系统容量等。
步骤405：第一用户面网元根据会话管理网元列表与会话管理网元间建立通信连接，接受与其建立通信连接的会话管理网元的节点级管理信息或会话级管理信息。
具体的，步骤405可参照现有流程，如：第一用户面网元进入运行状态，查看其保存的会话管理网元列表，根据会话管理网元的服务地址向会话管理网元发送链路建立请求(如：N4链路建立请求)，实现与会话管理网元间建立通信连接。
其中，会话管理网元的服务地址可以记录在会话管理网元列表中，第一用户面网元可以直接从会话管理网元列表中获取会话管理网元的服务地址，根据会话管理网元的服务地址向会话管理网元发送链路建立请求；或者，会话管理网元列表中仅记录有会话管理网元的ID，未记录会话管理网元的服务地址，此时，第一用户面网元可以向网络存储功能(Network Repository Function，NRF)发送携带有会话管理网元的ID的查询请求，请求NRF查询会话管理网元的服务地址；NRF接收查询请求，根据会话管理网元的ID与会话管理网元的服务地址的对应关系，确定待查询的会话管理网元的服务地址，向第一用户面网元发送待查询的会话管理网元的服务地址；第一用户面网元从NRF接收会话管理网元的服务地址，根据会话管理网元的服务地址向会话管理网元发送链路建立请求。其中，会话管理网元的服务地址与会话管理网元的ID间的对应关系可以通过下述方式预先存在NRF中：会话管理网元进入运行状态后，可以向NRF发送携带有会话管理网元的ID以及会话管理网元的服务地址的注册请求，该注册请求用于指示会话管理网元可对外提供服务，NRF接收到注册请求后，记录会话管理网元的服务地址与会话管理网元的ID间的对应关系。
需要说明的是，本申请实施例不限制步骤404、步骤405的执行顺序，除图4所示， 本申请实施例也可以先执行步骤405、再执行步骤404，或者同时执行步骤404和步骤405，不予限制。
此外，上述文字仅对服务控制网元向一个会话管理网元发送用户面网元列表和用户面网元选择策略，向一个用户面网元发送会话管理网元列表的过程进行了描述，如图4所示，服务控制网元还可以可参照步骤402向其他会话管理网元发送用户面网元列表和用户面网元选择策略，参照步骤403向其他用户面网元发送会话管理网元列表，不再赘述。
基于图4所示方案，服务控制网元获取会话管理网元与用户面网元间的管理关系后，根据获取到的管理关系集中向会话管理网元发送用户面网元列表和用户面网元选择策略，向用户面网元发送会话管理网元列表，实现会话管理网元与用户面网元间建立通信连接，以及为终端用户选择建立用户面承载的用户面网元。如此，通过服务控制网元对会话管理网元和用户面网元进行统一管理，集中下发会话管理网元和用户面网元链接连接需要的信息，实现会话管理网元和用户面网元的自动部署和连接。
进一步的，在图4所示方案中，所述方法还可以包括：
服务控制网元接收网络中每个用户面网元上报的工作状态信息；
服务控制网元根据每个用户面网元上报的工作状态信息更新第一会话管理网元的用户面网元选择策略，向第一会话管理网元发送更新后的用户面网元选择策略。
其中，工作状态信息可以包括但不限于承载的会话数、吞吐量、CPU负荷、功能使能统计、资源使用情况、运行情况中的一个或多个信息的组合。承载的会话数可以指：用户面网元被某个会话管理网元时其上承载的会话的个数，承载的会话数与会话管理网元相对应，同一用户面网元被不同会话管理网元管理时，对于不同会话管理网元，承载的会话数可以不同或相同，例如，用户面网元1被会话管理网元1和会话管理网元2同时管理，会话管理网元1管理用户面网元1时，用户面网元1上承载500条会话，会话管理网元2管理用户面网元1时，用户面网元1承载200条会话。吞吐量可以指：在单位时间内用户面网元成功传输的数据的数量。CPU负荷可以指：用户面网元的CPU的工作情况，可以用CPU的占用率来表征CPU负荷，CPU的占用率越大，CPU负荷越高，反之，CPU负荷越低。功能使能统计可以指用户面网元某个功能所支持的会话数。资源使用情况可以指用户面网元的内存使用情况。运行情况可以指用户面网元运行正常或者故障。
服务控制网元根据每个用户面网元上报的工作状态信息更新会话管理网元的用户面网元选择策略可以包括：服务控制网元根据用户面网元的工作状态信息调整用户面网元选择策略中各个用户面网元的权重。比如：某用户面网元超负荷，降低选择该用户面网元的权重；用户面网元负荷低，增加选择该用户面网元的权重。
具体的，各个用户面网元可以定期向服务控制网元上报其工作状态信息，如：可以将工作状态信息携带在节点状态上报(Node Status Report)消息/节点状态响应(Node  Status Response)消息中定期向服务控制网元发送；或者各个用户面网元接收服务控制网元发送的订阅请求，该订阅请求用于请求用户面网元定期向服务控制网元上报其工作状态信息，根据订阅请求，定期向服务控制网元上报工作状态信息，该工作状态信息可携带在订阅响应中。
如此，可以基于全网用户面网元的工作情况动态统一调整各个会话管理网元的用户面网元选择策略，让多个会话管理网元之间的用户面网元选择更为协同，避免多个会话管理网元独立选择用户面网元时，因缺少全局视角，导致用户面网元的业务负荷不均的问题。
进一步的，在图4所示方案中，所述方法还可以包括：
当新增或删除与第一会话管理网元连接的用户面网元时，服务控制网元更新原有下发给该第一会话管理网元的用户面网元列表以及用户面网元选择策略，向该第一会话管理网元发送更新后的用户面网元列表以及用户面网元选择策略。进一步的，服务控制网元还可以向新增的用户面网元发送会话管理网元列表。
同理，用户面网元删除时，服务控制网元可以将该用户面网元的信息从用户面网元列表中删除，并重新向会话管理网元下发更新后的用户面网元列表，同时，服务控制网元还可以主动通知管理该用户面网元的各会话管理网元不再选择该用户面网元。
如此，当网络中新增或删除用户面网元时，服务控制网元可以通过下发更新后的用户面网元列表及时维护网元间的管理关系，以及通过调整用户面网元选择策略来及时协调各个会话管理网元间管理的用户面网元，无需人工手动更新，简单快捷。
进一步的，在图4所示方案中，所述方法还可以包括：
当新增或删除与第一用户面网元连接的会话管理网元时，服务控制网元更新原有下发给该第一用户面网元的会话管理网元列表，向该第一用户面网元发送更新后的会话管理网元列表。进一步的，服务控制网元还可以向新增的会话管理网元发送用户面网元列表以及用户面网元选择策略。
如此，当网络中新增或删除会话管理网元时，服务控制网元可以通过下发更新后的会话管理网元列表及时维护网元间的管理关系，以及通过向新增会话管理网元下发用户面网元选择策略来及时协调各个会话管理网元间管理的用户面网元，无需人工手动更新，简单快捷。
进一步的，在图4所示方案中，为了实现会话管理网元对用户面网元的非会话级管理和会话级管理，所述方法还包括：
服务控制网元获取运营商规划的配置数据，根据配置数据配置网络中的会话管理网元和用户面网元。
具体的，服务控制网元可以根据配置数据、以及会话管理网元和用户面网元使能的功能配置网络中的会话管理网元和用户面网元；或者，服务控制网元根据配置数据、以 及会话管理网元和用户面网元使能的功能、网元支持的用户组信息配置网络中的会话管理网元和用户面网元。
其中，使能的功能可以包括计费(按什么费率计费)、阻塞(是否需要阻塞业务)、重定向(是否需要重定向该业务流到特定网站)、头增强(是否需要在超文本传输协议(Hyper Text Transfer Protocol，HTTP)报文中插入一些特性信息发送到服务器)、带宽管理(限制特定业务的带宽)等对报文进行计费和控制的功能。用户组信息可以用于标识接入网络、接受网络提供的服务的用户组，比如：可以为签约腾讯大王卡套餐的用户组，签约淘宝套餐的用户组，169基础套餐的用户组等。
其中，配置数据可以包括会话管理网元和用户面网元正常运行及使能功能所需要的配置参数(如：网元的逻辑接口地址等)，还可以包括用户面网元转发用户数据所遵循的过滤条件和处理策略。比如：配置数据可以包括一个或多个预定义规则，预定义规则用于定义通过用户面网元的数据报文的过滤条件和相应的处理策略，过滤条件定义了可以命中这个预定义规则的数据报文的L3、L4、L7层信息，比如：源/目标IP地址、源/目标端口、IP Protocol(如：传输控制协议(Transmission Control Protocol，TCP)或者用户数据报协议(User Datagram Protocol，UDP)、Internet控制消息协议(Internet Control Message Protocol，ICMP)、域名、URL等)。策略部分可以包括计费、阻塞、重定向、头增强等对报文进行计费和控制的策略。预定义规则由预定义规则名称所标识，不同的预定义规则可以对应不同的预定义规则名称，会话管理网元可以向用户面网元下发预定义规则名称，以激活预定义规则。例如：会话管理网元和用户面网元都配置有某个预定义规则，当需要执行该预定义规则时，会话管理网元可以通过N4接口向用户面网元下发预定义规则名称，激活该预定义规则，使用户面网元按照该预定义规则执行相应的业务功能。
如此，通过服务控制网元对各个网元的配置数据进行集中管理，避免了同一用户面网元被多个会话管理网元管理的情况下，各会话管理网元分别下发相同配置数据到用户面网元带来的配置数据冗余的问题，以及不同会话管理网元针对同一配置对象下发不同配置数据带来的配置冲突的问题。
下面结合图2a所示通信系统，以服务控制网元为SCF，会话管理网元为SMF，用户面网元为UPF，用户面网元列表为UPF列表，用户面网元选择策略为UPF选择策略，会话管理网元列表为SMF列表、用户面网元选择参数为UPF选择参数为例，对图4所示方法进行详细描述。
图5为本申请实施例提供的一种管理网元的方法，用于通过SCF管理图2a所示网络中的多个SMF和多个UPF，其中，图2a所示网络中运营商最初规划为：SMF1与UPF1、UPF3连接，SMF2与UPF1、UPF2、UPF3连接，SMF3、UPF4为新增网元。如图5所示，该方法可以包括步骤501～步骤514。
步骤501：运营商根据其网络规划需求，确定SMF与UPF间的管理关系，并向SCF下发SMF与UPF间的管理关系。
其中，如图2a所示，SMF与UPF间的管理关系为：SMF1与UPF1、UPF3连接，SMF2与UPF1、UPF2、UPF3连接。运营商向SCF下发SMF与UPF间的管理关系的方式可参照步骤401所述，不再赘述。
步骤502：SCF获取SMF与UPF间的管理关系；向SMF1、SMF2以及UPF1～UPF3分别发送服务应用请求，实现SMF1、SMF2以及UPF1～UPF3的实例化部署。
其中，服务应用请求中可以携带SCF从VNFM中请求的网元(SMF或者UPF)启动时需要使用的软件包下载路径、部署策略、服务的组网信息、服务的初始运行资源(如：缓存资源、网元的服务地址、SCF的服务地址)等信息，用于实现网元的实例化部署。具体的，各个网元实例化部署过程可参照现有技术，不予赘述。
例如，以SMF1实例化部署为例，SCF从VNFM中请求SMF1启动时所需的软件包下载路径、部署策略、服务的组网信息、服务的初始运行资源(如：缓存资源、SMF1的服务地址、SCF的服务地址)等信息，实现SMF1的实例化部署。
步骤503：SMF1根据SCF的服务地址，向SCF发送第一请求消息。
其中，该第一请求消息可以为管理请求，该管理请求中携带SMF1的服务地址，该管理请求可以用于请求SCF向SMF1发送UPF列表以及UPF选择策略。或者，
该第一请求消息可以为注册请求，该注册请求可以用于指示SMF1已完成实例化部署，可以接受SCF的管理，该注册请求可以携带SMF的服务地址。
步骤504：SCF接收第一请求消息，根据步骤502中获取到的SMF与UPF间的管理关系，向SMF1发送UPF列表，以及根据UPF选择参数以及SMF1连接的UPF的信息为SMF1制定UPF选择策略，并向SMF1发送UPF选择策略，SMF1接收并保存UPF列表以及UPF选择策略。
其中，以图2a为例，SMF1与UPF1、UPF2连接，则SCF向SMF1发送的UPF列表为{UPF1、UPF2}。可选的，SMF1接收到UPF列表和UPF选择策略之后，还向SCF发送用于指示接收到UPF列表和UPF选择策略的响应消息。
步骤505：SMF2根据SCF的服务地址，向SCF发送第二请求消息。
其中，步骤505可参照步骤503所述，不再赘述。
步骤506：SCF接收第二请求消息，根据SMF与UPF间的管理关系，向SMF1发送UPF列表{UPF1、UPF2、UPF3}，以及根据UPF选择参数以及SMF2连接的UPF的信息为SMF2制定UPF选择策略，并向SMF2发送UPF选择策略，SMF2接收并保存UPF列表以及UPF选择策略。
其中，步骤506可参照步骤504所述，不再赘述。
步骤507：UPF1根据SCF的服务地址，向SCF发送第三请求消息。
其中，该第三请求消息可以为管理请求，该管理请求中携带UPF1的服务地址，该 管理请求可以用于请求SCF向UPF1发送SMF列表。或者，该第三请求消息可以为注册请求，该注册请求可以用于指示UPF1已完成实例化部署，可以接受SCF的管理，该注册请求可以携带UPF1的服务地址。
步骤508：SCF接收第三请求消息，根据SMF与UPF间的管理关系，向UPF1发送SMF列表，UPF1接收并保存SMF列表。
其中，以图2a为例，UPF1与SMF1、SMF2连接，则SCF向UPF发送SMF列表{SMF1、SMF2}。可选的，UPF1接收到SMF列表之后，还向SCF发送用于指示接收到SMF列表的响应消息。
步骤509：UPF2根据SCF的服务地址，向SCF发送第四请求消息。
其中，步骤509可参照步骤507所述，不再赘述。
步骤510：SCF接收第四请求消息，根据SMF与UPF间的管理关系，向UPF2发送SMF列表{SMF2}，UPF2接收并保存SMF列表。
其中，步骤510可参照步骤508所述，不再赘述。
同理，UPF3也可以向SCF发送请求消息，从SCF中接收并保存SMF列表{SMF1、SMF2}(图5中未示出)。
需要说明的是，本申请实施例不限定步骤503～步骤504、步骤505～步骤506、步骤507～步骤508、步骤509～步骤510的执行顺序，步骤503～步骤504、步骤505～步骤506、步骤507～步骤508、步骤509～步骤510可以并列执行，也可以如图5所示顺序执行，不予限制。
步骤511：SMF1根据其保存的UPF列表与UPF间建立通信连接，并根据其保存的UPF选择策略选择出为终端用户建立用户面承载的UPF。
其中，步骤511可参照步骤404所述，不再赘述。
步骤512：SMF2根据其保存的UPF列表与UPF间建立通信连接，并根据其保存的UPF选择策略选择出为终端用户建立用户面承载的UPF。
其中，步骤512可参照步骤511所述，不再赘述。
步骤513：UPF1根据其保存的SMF列表与SMF间建立通信连接，接受与其建立通信连接的SMF的节点级管理信息或会话级管理信息。
具体的，步骤513可参照步骤405所述，不再赘述。
步骤514：UPF2根据其保存的SMF列表与SMF间建立通信连接，接受与其建立通信连接的SMF的节点级管理信息或会话级管理信息。
其中，步骤514可参照步骤510所述，不再赘述。
同理，UPF3也可以根据其保存的SMF列表与SMF间建立通信连接，接受与其建 立通信连接的SMF的节点级管理信息或会话级管理信息(图5中未示出)。
需要说明的是，本申请实施例不限定步骤511、步骤512、步骤513、步骤514的执行顺序，步骤511、步骤512、步骤513、步骤514可以并列执行，也可以如图5所示顺序执行，不予限制。
基于图5所示方案，SCF获取运营商规划的SMF与UPF间的管理关系以及UPF选择参数后，根据获取到的管理关系集中向SMF发送UPF列表、UPF选择策略，向UPF发送SMF列表，实现SMF与UPF间建立通信连接，以及为终端用户选择建立用户面承载的UPF。如此，通过SCF对SMF和UPF进行统一管理，集中下发SMF和UPF链接连接需要的信息，实现SMF和UPF的自动部署和连接。
进一步的，在图5所示方案中，所述方法还可以包括：
SCF接收每个UPF上报的工作状态信息；
SCF根据每个UPF上报的工作状态信息更新SMF的UPF选择策略，向SMF发送更新后的UPF选择策略，该SMF可以为SCF所管理的一个或多个SMF，如：可以为图2a中的SMF1和/或SMF2。
其中，UPF的工作状态信息的相关描述可参照图4对应的实施例中所述，不再赘述。
如此，可以基于全网UPF的工作情况动态统一调整各个SMF的UPF选择策略，让多个SMF之间的UPF选择更为协同，避免多个SMF独立选择UPF时，因缺少全局视角，导致UPF的业务负荷不均的问题。
进一步的，在图5所示方案中，所述方法还可以包括：
当新增或删除与SMF连接的UPF时，SCF更新原有下发给该SMF的UPF列表以及UPF选择策略，向该SMF发送更新后的UPF列表以及UPF选择策略。进一步的，SCF还可以向新增的UPF发送SMF列表。
例如，如图2a所示，该系统中新增UPF4，其中，UPF4与SMF2连接，则SCF将SMF2的UPF列表{UPF1、UPF2、UPF3}更新为{UPF1、UPF2、UPF3、UPF4}，将更新后的UPF列表{UPF1、UPF2、UPF3、UPF4}下发给SMF2，将SMF列表{SMF2}下发给UPF4，以便UPF4与SMF2建立通信连接。同时，由于新增UPF一般为空闲态，此时，可以在初期增加SMF选择该UPF的权重，如：SCF可以在下发给SMF2的UPF选择策略中增加UPF4的权重，以便后续SMF2优先选择UPF4。
同理，UPF删除时，SCF可以将该UPF的信息从UPF列表中删除，并重新向SMF下发更新后的UPF列表，同时，SCF还可以主动通知管理该UPF的各SMF不再选择该UPF。
如此，当网络中新增或删除UPF时，SCF可以通过下发更新后的UPF列表及时维护网元间的管理关系，以及通过调整UPF选择策略来及时协调各个SMF间管理的UPF，无需人工手动更新，简单快捷。
进一步的，在图5所示方案中，所述方法还可以包括：
当新增或删除与UPF连接的SMF时，SCF更新原有下发给该UPF的SMF列表，向该UPF发送更新后的SMF列表。进一步的，SCF还可以向新增的SMF发送UPF列表以及UPF选择策略。
例如，如图2a所示，该系统中新增SMF3，其中，SMF3与UPF2、UPF3连接，则SCF将UPF2的SMF列表{SMF2}更新为{SMF2、SMF3}，将更新后的SMF列表{SMF2、SMF3}下发给UPF2，将UPF3的SMF列表{SMF1、SMF2}更新为{SMF1、SMF2、SMF3}，将更新后的SMF列表{SMF1、SMF2、SMF3}下发给UPF3，以及向SMF3下发UPF列表{UPF2、UPF3}以及UPF选择策略，以便SMF3与UPF2、UPF3建立通信连接，并从UPF2、UPF3中选择出UPF。
如此，当网络中新增或删除SMF时，SCF可以通过下发更新后的SMF列表及时维护网元间的管理关系，以及通过向新增SMF下发UPF选择策略来及时协调各个SMF间管理的UPF，无需人工手动更新，简单快捷。
进一步的，在图5所示方案中，为了实现SMF对UPF的非会话级管理和会话级管理，所述方法还包括：SCF获取运营商规划的配置数据，根据配置数据配置图2a所示网络中的SMF和UPF。
其中，配置数据的相关描述以及配置SMF和UPF的过程可参照图4对应的实施例中的相关描述，不再赘述。如此，通过SCF对各个网元的配置数据进行集中管理，避免了同一UPF被多个SMF管理的情况下，各SMF分别下发相同配置数据到UPF带来的配置数据冗余的问题，以及不同SMF针对同一配置对象下发不同配置数据带来的配置冲突的问题。
上述主要从各个节点之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个节点，例如服务控制网元、用户面网元、会话管理网元为了实现上述功能，其包括了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
图6示出了服务控制网元的一种可能的组成示意图，该服务控制网元可以用于执行上述实施例中涉及的服务控制网元的功能。如图6所示，该服务控制网元可以包括：获取单元60，发送单元61；
获取单元60，用于获取网络中会话管理网元与用户面网元之间的管理关系；如：支持服务控制网元执行步骤401。
发送单元61，用于向网络中的任一第一会话管理网元发送由管理关系确定，且用于表征归属于第一会话管理网元管理的用户面网元的用户面网元列表、以及用于第一会话管理网元选择用户面网元的用户面网元选择策略；以及向网络中的任一第一用户面网 元发送用于表征管理第一用户面网元连接的会话管理网元的会话管理网元列表。如：支持服务控制网元执行步骤402、步骤403。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。本申请实施例提供的服务控制网元，用于执行上述管理网元的方法，因此可以达到与上述管理网元的方法相同的效果。
又一种可能的组成方式中，上述服务控制网元可以为包括处理模块和通信模块的通信装置，其中，该通信装置以芯片的产品形态存在，处理模块可以集成获取单元60的功能，通信模块可以集成发送单元61的功能。例如，处理模块用于支持该装置执行步骤401以及本文所描述的技术的其它过程。通信模块用于支持装置与其他网络实体的通信，例如与图1示出的功能模块或网络实体之间的通信。该装置还可以包括存储模块，用于存储装置的程序代码和数据。
其中，处理模块可以是处理器或控制器。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块可以是收发电路或通信接口等。存储模块可以是存储器。当处理模块为处理器，通信模块为通信接口，存储模块为存储器时，本申请实施例所涉及的装置可以为图3所示通信设备。
图7示出了会话管理网元的一种可能的组成示意图，该会话管理网元为网络中的任一会话管理网元，可以用于执行上述实施例中涉及的会话管理网元的功能。如图7所示，该会话管理网元可以包括：接收单元70、处理单元71。
接收单元70，用于从服务控制网元接收由所述管理关系确定，且用于表征归属于所述第一会话管理网元管理的用户面网元的用户面网元列表以及用于所述第一会话管理网元选择用户面网元的用户面网元选择策略；如：支持会话管理网元执行步骤404。
处理单元71，用于根据接收单元70接收到的用户面网元列表与用户面网元间建立通信连接，以及根据用户面网元选择策略选择出为终端用户建立用户面承载的用户面网元。如：支持会话管理网元执行步骤404。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。本申请实施例提供的会话管理网元，用于执行上述管理网元的方法，因此可以达到与上述管理网元的方法相同的效果。
又一种可能的组成方式中，上述会话管理网元可以为包括处理模块和通信模块的通信装置，其中，该通信装置以芯片的产品形态存在，处理模块可以集成处理单元71的功能，通信模块可以集成接收单元70的功能。例如，处理模块用于支持该装置执行步骤401以及本文所描述的技术的其它过程。通信模块用于支持装置与其他网络实体的通信，例如与图1示出的功能模块或网络实体之间的通信。该装置还可以包括存储模块，用于存储装置的程序代码和数据。
其中，处理模块可以是处理器或控制器。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块可以是收发电路或通信接口等。存储模块可以是存储器。当处理模块为处理器，通信模块为通信接口，存储模 块为存储器时，本申请实施例所涉及的装置可以为图3所示通信设备。
图8示出了用户面网元的一种可能的组成示意图，该用户面网元为网络中的任一用户面网元，可以用于执行上述实施例中涉及的用户面网元的功能。如图8所示，该用户面网元可以包括：接收单元80、处理单元81。
接收单元80，用于从服务控制网元接收由管理关系确定，用于表征管理第一用户面网元连接的会话管理网元的会话管理网元列表；如：支持用户面网元执行步骤405。
处理单元81，用于根据接收单元80接收到的用户面网元列表与用户面网元间建立通信连接，以及根据用户面网元选择策略选择出为终端用户建立用户面承载的用户面网元。如：支持用户面网元执行步骤405。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。本申请实施例提供的用户面网元，用于执行上述管理网元的方法，因此可以达到与上述管理网元的方法相同的效果。
又一种可能的组成方式中，上述用户面网元可以为包括处理模块和通信模块的通信装置，其中，该通信装置以芯片的产品形态存在，处理模块可以集成处理单元81的功能，通信模块可以集成接收单元80的功能。例如，处理模块用于支持该装置执行步骤401以及本文所描述的技术的其它过程。通信模块用于支持装置与其他网络实体的通信，例如与图1示出的功能模块或网络实体之间的通信。该装置还可以包括存储模块，用于存储装置的程序代码和数据。
其中，处理模块可以是处理器或控制器。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块可以是收发电路或通信接口等。存储模块可以是存储器。当处理模块为处理器，通信模块为通信接口，存储模块为存储器时，本申请实施例所涉及的装置可以为图3所示通信设备。
图9为本申请实施例提供的一种管理网元的系统的组成示意图，如图9所示，该系统可以包括服务控制网元90、多个会话管理网元91以及多个用户面网元92，服务控制网元90可以与多个会话管理网元91以及多个用户面网元92建立通信连接，集中管理这些会话管理网元91和用户面网元92。如图9所示，一个会话管理网元91可以同时与一个或多个用户面网元92建立通信连接，一个用户面网元92可以同时与一个或个会话管理网元建立通信连接。
其中，服务控制网元90，可以用于获取网络中会话管理网元与用户面网元之间的管理关系，向多个会话管理网元91中的任一会话管理网元91发送由管理关系确定，且用于表征归属于会话管理网元91管理的用户面网元的用户面网元列表、以及用于会话管理网元91选择用户面网元的用户面网元选择策略；以及向多个用户面网元中的任一用户面网元92发送用于表征管理用户面网元92连接的会话管理网元的会话管理网元列表；会话管理网元91，用于根据接收到的用户面网元列表与用户面网元间建立通信连接，并根据用户面网元选择策略选择出为终端用户建立用户面承载的用户面网元；用户面网元92，用于根据会话管理网元列表与会话管理网元间建立通信连接，接受与其建立通信连接的会话管理网元的节点级管理信息或会话级管理信息。
需要说明的是，图9所示系统中各功能节点所执行的各步骤的详细过程可参照上述实施例中所述，在此不再赘述。基于图9所示系统，可以通过服务控制网元对会话管理网元和用户面网元进行统一管理，集中下发会话管理网元和用户面网元链接连接需要的信息，实现会话管理网元和用户面网元的自动部署和连接。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (12)

  1. 一种管理网元的方法，其特征在于，所述方法包括：
    服务控制网元获取网络中会话管理网元与用户面网元之间的管理关系；
    所述服务控制网元向第一会话管理网元发送用户面网元列表以及用于所述第一会话管理网元选择用户面网元的用户面网元选择策略；其中，所述第一会话管理网元为所述网络中的任一个会话管理网元，所述用户面网元列表由所述管理关系确定，且用于表征归属于所述第一会话管理网元管理的用户面网元；所述用户面网元选择策略由用户面网元选择参数以及由所述第一会话管理网元管理的用户面网元的信息确定；
    所述服务控制网元向第一用户面网元发送会话管理网元列表；其中，所述第一用户面网元为所述网络中的任一个用户面网元，所述会话管理网元列表用于表征管理所述第一用户面网元连接的会话管理网元。
  2. 根据权利要求1所述的管理网元的方法，其特征在于，所述方法还包括：
    所述服务控制网元接收所述网络中每个用户面网元上报的工作状态信息；
    所述服务控制网元根据每个用户面网元上报的工作状态信息更新所述用户面网元选择策略，向所述第一会话管理网元发送更新后的用户面网元选择策略；
    所述每个用户面网元上报的工作状态信息包括承载的会话数、吞吐量、中央处理单元CPU负荷、功能使能统计、资源使用情况、运行情况中的一个或多个信息。
  3. 根据权利要求1或2所述的管理网元的方法，其特征在于，所述方法还包括：
    当新增或删除与所述第一会话管理网元连接的用户面网元时，所述服务控制网元更新所述用户面网元列表以及所述用户面网元选择策略，向所述第一会话管理网元发送更新后的用户面网元列表以及用户面网元选择策略。
  4. 根据权利要求1-3任一项所述的管理网元的方法，其特征在于，所述方法还包括：
    当新增或删除与所述第一用户面网元连接的会话管理网元时，所述服务控制网元更新所述会话管理网元列表，并向所述第一用户面网元发送更新后的会话管理网元列表。
  5. 根据权利要求1-4任一项所述的管理网元的方法，其特征在于，所述方法还包括：
    所述服务控制网元获取运营商规划的配置数据；
    所述服务控制网元根据所述配置数据配置所述网络中的会话管理网元和用户面网元；
    其中，所述配置数据包括用户面网元和会话管理网元运行时所需要的配置参数、以及用户面网元转发数据报文时所遵循的过滤条件和处理策略。
  6. 一种服务控制网元，其特征在于，所述服务控制网元包括：
    获取单元，用于获取网络中会话管理网元与用户面网元之间的管理关系；
    发送单元，用于向第一会话管理网元发送用户面网元列表以及用于所述第一会话管理网元选择用户面网元的用户面网元选择策略；其中，所述第一会话管理网元为所述网络中的任一个会话管理网元，所述用户面网元列表由所述管理关系确定，且用于表征归属于所述第一会话管理网元管理的用户面网元；所述用户面网元选择策略由用户面网元选择参数以及由所述第一会话管理网元管理的用户面网元的信息确定；
    以及，向第一用户面网元发送会话管理网元列表；其中，所述第一为所述网络中的任一个用户面网元，所述会话管理网元列表用于表征管理所述第一用户面网元连接的会话管理网元。
  7. 根据权利要求6所述的服务控制网元，其特征在于，所述服务控制网元还包括：
    所述服务控制网元接收所述网络中每个用户面网元上报的工作状态信息；
    所述服务控制网元根据每个用户面网元上报的工作状态信息更新所述用户面网元选择策略，向所述第一会话管理网元发送更新后的用户面网元选择策略；
    所述每个用户面网元上报的工作状态信息包括承载的会话数、吞吐量、中央处理单元CPU负荷、功能使能统计、资源使用情况、运行情况中的一个或多个信息。
  8. 根据权利要求6或7所述的服务控制网元，其特征在于，所述服务控制网元还包括：
    当新增或删除与所述第一会话管理网元连接的用户面网元时，所述服务控制网元更新所述用户面网元列表以及所述用户面网元选择策略，向所述第一会话管理网元发送更新后的用户面网元列表以及用户面网元选择策略。
  9. 根据权利要求6-8任一项所述的服务控制网元，其特征在于，所述服务控制网元还包括：
    当新增或删除与所述第一用户面网元连接的会话管理网元时，所述服务控制网元更新所述会话管理网元列表，并向所述第一用户面网元发送更新后的会话管理网元列表。
  10. 根据权利要求6-9任一项所述的服务控制网元，其特征在于，所述服务控制网元还包括：
    所述服务控制网元获取运营商规划的配置数据；
    所述服务控制网元根据所述配置数据配置所述网络中的会话管理网元和用户面网元；
    其中，所述配置数据包括用户面网元和会话管理网元运行时所需要的配置参数、以及用户面网元转发数据报文时所遵循的过滤条件和处理策略。
  11. 一种通信设备，包括：至少一个处理器，以及存储器；其特征在于，
    所述存储器用于存储计算机程序，使得所述计算机程序被所述至少一个处理器执行时实现如权利要求1-5中任一项所述的管理网元的方法。
  12. 一种计算机存储介质，其上存储有计算机程序，其特征在于，所述程序被处理器执行时实现如权利要求1-5中任一项所述的管理网元的方法。
PCT/CN2019/092132 2018-06-22 2019-06-20 一种管理网元的方法、设备及系统 WO2019242698A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810654545.2 2018-06-22
CN201810654545.2A CN110636552B (zh) 2018-06-22 2018-06-22 一种管理网元的方法、设备及系统

Publications (1)

Publication Number Publication Date
WO2019242698A1 true WO2019242698A1 (zh) 2019-12-26

Family

ID=68967661

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/092132 WO2019242698A1 (zh) 2018-06-22 2019-06-20 一种管理网元的方法、设备及系统

Country Status (2)

Country Link
CN (1) CN110636552B (zh)
WO (1) WO2019242698A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023125307A1 (zh) * 2021-12-30 2023-07-06 中国电信股份有限公司 网元切换方法及装置、存储介质及电子设备
US11924662B2 (en) * 2020-11-13 2024-03-05 At&T Intellectual Property I, L.P. Remote user plane deployment and configuration

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11516090B2 (en) * 2018-07-17 2022-11-29 Telefonaktiebolaget Lm Ericsson (Publ) Open network automation platform (ONAP)—fifth generation core (5GC) interaction for analytics
CN115134936A (zh) * 2021-03-24 2022-09-30 海能达通信股份有限公司 用户会话的处理方法及相关装置
CN114786249A (zh) * 2022-03-31 2022-07-22 联想(北京)有限公司 一种用户面网元配置方法、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106792858A (zh) * 2016-12-30 2017-05-31 南京邮电大学 一种基于软件定义的超密集无线网络体系结构及实现方法
WO2017110650A1 (en) * 2015-12-22 2017-06-29 Nec Corporation Method for selection and relocation of user plane functionality
CN107872326A (zh) * 2016-09-26 2018-04-03 华为技术有限公司 一种释放会话资源的方法、装置和系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9473986B2 (en) * 2011-04-13 2016-10-18 Interdigital Patent Holdings, Inc. Methods, systems and apparatus for managing and/or enforcing policies for managing internet protocol (“IP”) traffic among multiple accesses of a network
WO2016065639A1 (zh) * 2014-10-31 2016-05-06 华为技术有限公司 数据处理的方法、装置、终端、移动管理实体及系统
CN106559917A (zh) * 2015-09-30 2017-04-05 中国移动通信集团公司 用户设备初始附着方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017110650A1 (en) * 2015-12-22 2017-06-29 Nec Corporation Method for selection and relocation of user plane functionality
CN107872326A (zh) * 2016-09-26 2018-04-03 华为技术有限公司 一种释放会话资源的方法、装置和系统
CN106792858A (zh) * 2016-12-30 2017-05-31 南京邮电大学 一种基于软件定义的超密集无线网络体系结构及实现方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11924662B2 (en) * 2020-11-13 2024-03-05 At&T Intellectual Property I, L.P. Remote user plane deployment and configuration
WO2023125307A1 (zh) * 2021-12-30 2023-07-06 中国电信股份有限公司 网元切换方法及装置、存储介质及电子设备

Also Published As

Publication number Publication date
CN110636552A (zh) 2019-12-31
CN110636552B (zh) 2021-06-08

Similar Documents

Publication Publication Date Title
US11350336B2 (en) Systems and methods for user plane path selection, reselection, and notification of user plane changes
US11671373B2 (en) Systems and methods for supporting traffic steering through a service function chain
CN111758279B (zh) 跟踪QoS违规事件
EP4221150A1 (en) System, apparatus and method to support data server selection
WO2019242698A1 (zh) 一种管理网元的方法、设备及系统
US9510371B2 (en) Method and apparatus for controlling service transmission
WO2018161803A1 (zh) 一种网络切片的选择方法及装置
WO2019223661A1 (zh) 一种识别应用标识的方法、设备及系统
WO2021254001A1 (zh) 会话建立方法、装置、系统及计算机存储介质
WO2018233451A1 (zh) 通信方法、装置和系统
JP2021517376A (ja) 伝送方法及び伝送装置
EP3002916B1 (en) Packet forwarding system, device and method
WO2021115429A1 (zh) 一种通信方法及装置
WO2023185428A1 (zh) 一种重构用户面功能网元关键服务能力的方法及通信装置
WO2018177003A1 (zh) 一种计费方法、相关设备和系统
KR20230157194A (ko) 스위치를 이용하는 트래픽 처리를 위한 장치 및 방법
JP7507144B2 (ja) インジケーション情報送信方法、装置およびシステム、および記憶媒体
WO2021103009A1 (zh) 上行pdr的生成方法、装置及系统
WO2023280000A1 (zh) 一种通信方法、系统和装置
US20230345347A1 (en) Method for determining mec access point and apparatus
JP7472282B2 (ja) 通信ネットワークのネットワーク機能を選択するための通信ネットワーク構成及び方法
WO2023061207A1 (zh) 一种通信方法、通信装置及通信系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19822404

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19822404

Country of ref document: EP

Kind code of ref document: A1