WO2022151206A1 - 通信方法和网络设备 - Google Patents

通信方法和网络设备 Download PDF

Info

Publication number
WO2022151206A1
WO2022151206A1 PCT/CN2021/071854 CN2021071854W WO2022151206A1 WO 2022151206 A1 WO2022151206 A1 WO 2022151206A1 CN 2021071854 W CN2021071854 W CN 2021071854W WO 2022151206 A1 WO2022151206 A1 WO 2022151206A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
user plane
plane function
function network
interface
Prior art date
Application number
PCT/CN2021/071854
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 华为技术有限公司
Priority to CN202180051556.1A priority Critical patent/CN115918240A/zh
Priority to PCT/CN2021/071854 priority patent/WO2022151206A1/zh
Publication of WO2022151206A1 publication Critical patent/WO2022151206A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • the present application relates to the field of communication, and more particularly, to a communication method and network device.
  • SMF Session Management Function
  • UPF User Plane Function
  • the functions of UPF are gradually becoming stronger. For example, it can analyze the user's business status, including: whether the traffic is abnormal, whether the delay caused by network congestion changes greatly, Whether the delay satisfies the service experience, etc.
  • NWDAF Network Data Analytics Funtion
  • the present application provides a communication method and network device, which can realize other network elements other than SMF types to control UPF network elements, and UPF network elements can operate in isolation based on different configurations of SMF network elements and other types of network elements, and process the same report in parallel. This allows multiple types of controllers to control the same UPF network element.
  • a first aspect provides a communication method, comprising: a session management function network element acquiring an interface identifier; the session management function network element sending the address of the user plane function network element and the interface identifier to a first network element, the The interface identifier is used by the first network element to determine the interface corresponding to the interface identifier, and the address of the user plane function network element and the interface corresponding to the interface identifier are used by the first network element to control the user plane function network element.
  • the interface corresponding to the interface identifier is a message interface newly added by the user plane functional network element, including: a message exit and/or a message entry.
  • the session management function network element can obtain the interface identifier and send the address of the user plane function network element and the interface identifier to the first network element, so that the first network element can realize the address of the user plane function network element through the first network element.
  • the interface corresponding to the interface identifier controls the user plane function network element.
  • the user plane functional network elements can operate in isolation based on the different configurations of the session management function network elements and other types of network elements, and process the same packet in parallel, thereby enabling multiple types of controllers to control the user plane function network elements.
  • the session management function network element sends first information to the user plane function network element, where the first information is used to indicate the user plane function network element meta-assigns the interface identifier.
  • acquiring the interface identifier by the session management function network element includes: the session management function network element receiving the interface identifier from the user plane function network element.
  • the session management function network element sends the interface identifier to the user plane function network element.
  • the session management function network element receives capability indication information from the user plane function network element, where the capability indication information is used to indicate that the user plane function network element can be controlled by the network element of the first type, and the The network element of the first type is a network element other than the session management function type.
  • the network elements of the first type may include: an access management function (Access and Mobility Management Function, AMF), a network data analysis function NWDAF, a policy control function (policy control function, PCF), a group management function ( Group Management Function (GMF), Network Expsorue Function (NEF), Unified Data Management (UDM), Media Function (MF), Network Repository Function (NRF), Authentication Different types of Control Plane Function (CPF) network elements such as Authentication Server Function (AUSF), Binding Support Function (BSF), Network Data Analysis (NWDA), etc.
  • AMF Access and Mobility Management Function
  • NWDAF policy control function
  • PCF policy control function
  • GMF Group Management Function
  • NEF Network Expsorue Function
  • UDM Unified Data Management
  • MF Media Function
  • NRF Network Repository Function
  • CPF Control Plane Function
  • AUSF Authentication Server Function
  • BSF Binding Support Function
  • NWDA Network Data Analysis
  • the session management function network element receives a request message from the first network element, where the request message is used to request to control the user plane function network element.
  • the request message includes at least one of the following information: an identifier of the user plane function network element, a service area covered by the user plane function network element, and a session identifier of the user equipment.
  • a second aspect provides a communication method, comprising: a user plane function network element receiving a packet detection rule and a packet processing rule corresponding to the first network element from a first network element, where the first network element is A network element of a non-session management function type; the user plane function network element receives a packet through an interface corresponding to the first network element; the user plane function network element detects the packet according to the packet detection rule , and process the message according to the message processing rule.
  • the user plane function network element receives the packet detection rule and the packet processing rule corresponding to the first network element from the first network element, and according to the packet detection rule and the packet processing rule The packets are detected and processed respectively, so that the first network element can control the user plane function network element through the interface corresponding to the address of the user plane function network element and the interface identifier.
  • the user plane functional network elements can operate in isolation based on the different configurations of the session management function network elements and other types of network elements, and process the same packet in parallel, thereby enabling multiple types of controllers to control the user plane function network elements.
  • the user plane function network element receives first information from the session management function network element, where the first information is used to indicate allocation of the user plane function network element The interface identifier of the interface.
  • the user plane function network element sends the interface identifier of the interface to the session management function network element.
  • the user plane function network element receives the interface identifier of the interface from the session management function network element.
  • the user plane function network element sends capability indication information to the session management function network element, where the capability indication information is used to indicate that the user plane function network element can be controlled by the network element of the first type, and the The network element of the first type is a network element of a non-session management function type.
  • a third aspect provides a communication method, comprising: a first network element receiving an address and an interface identifier of a user plane function network element from a session management function network element; the first network element determining the interface according to the interface identifier Identifies the corresponding interface; the first network element is used by the first network element to control the user plane function network element according to the address of the user plane function network element and the interface corresponding to the interface identifier; the first network element controls the user plane function network element; The network element sends a packet detection rule and a packet processing rule corresponding to the first network element to the user plane function network element, where the first network element is a network element of a non-session management function type.
  • the first network element receives the address and interface identifier of the user plane function network element from the session management function network element, and sends a report corresponding to the first network element to the user plane function network element.
  • the message detection rule and the message processing rule can realize that the first network element controls the user plane function network element through the interface corresponding to the address of the user plane function network element and the interface identifier.
  • the user plane functional network elements can operate in isolation based on the different configurations of the session management function network elements and other types of network elements, and process the same packet in parallel, thereby enabling multiple types of controllers to control the user plane function network elements.
  • the first network element sends a request message to the session management function network element, where the request message is used to request the first network element to request the control Describe the user plane functional network elements.
  • the request message includes at least one of the following information: an identifier of the user plane function network element, a service area covered by the user plane function network element, and a session identifier of the user equipment.
  • a network device comprising: a processing unit for acquiring an interface identifier; a transceiver unit for sending an address of a user plane function network element and the interface identifier to a first network element, the user plane The address of the functional network element and the interface identifier are used by the first network element to control the user plane functional network element through the interface corresponding to the interface identifier.
  • the transceiver unit is further configured to send first information to the user plane function network element, where the first information is used to indicate the user plane function
  • the network element assigns the interface identifier
  • the processing unit is configured to receive the interface identifier from the user plane function network element through the transceiver unit.
  • the transceiver unit is further configured to send the interface identifier to the user plane function network element.
  • the transceiver unit is further configured to receive capability indication information from the user plane function network element, where the capability indication information is used to indicate that the user plane function network element can be controlled by a network element of the first type,
  • the first type of network element is a network element of a non-session management function type.
  • the transceiver unit is further configured to receive a request message from the first network element, where the request message is used to request to control the user plane function network element.
  • the request message includes at least one of the following information: an identifier of the user plane function network element, a service area covered by the user plane function network element, and a session identifier of the user equipment.
  • a network device comprising: a transceiver unit configured to receive a packet detection rule and a packet processing rule corresponding to the first network element from a first network element, wherein the first network element is a network element of a non-session management function type; the transceiver unit is further configured to receive a message through an interface corresponding to the first network element; a processing unit is configured to detect the message according to the message detection rule, and The message is processed according to the message processing rule.
  • the transceiver unit is further configured to receive first information from a session management function network element, where the first information is used to indicate the user plane function network element An interface identifier for the interface is assigned.
  • the transceiver unit is further configured to send the interface identifier of the interface to the session management function network element.
  • the transceiver unit is further configured to receive an interface identifier of the interface from the session management function network element.
  • the transceiver unit is further configured to send capability indication information to the session management function network element, where the capability indication information is used to indicate that the user plane function network element can be controlled by a network element of the first type,
  • the first type of network element is a network element of a non-session management function type.
  • a network device comprising: a transceiver unit, configured to receive an address and an interface identifier of a user plane function network element from a session management function network element; a processing unit, configured to determine the interface according to the interface identifier identify the corresponding interface; the processing unit is further configured to control the user plane function network element according to the address of the user plane function network element and the interface identifier; the transceiver unit is further configured to send the user plane function network element to the user plane
  • the functional network element sends a packet detection rule and a packet processing rule corresponding to the first network element, where the first network element is a network element of a non-session management function type.
  • the transceiver unit is further configured to send a request message to the session management function network element, where the request message is used to request the first network element to request The user plane functional network element is controlled.
  • the request message includes at least one of the following information: an identifier of the user plane function network element, a service area covered by the user plane function network element, and a session identifier of the user equipment.
  • a network device including a transceiver, a processor, and a memory, where the processor is used to control the transceiver to send and receive signals, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory A computer program, causing the network device to execute the method in the first aspect or any possible implementation manner of the first aspect, or the method in the second aspect or any possible implementation manner of the second aspect, or the third aspect or the method in any possible implementation manner of the third aspect.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the network device further includes a transmitter (transmitter) and a receiver (receiver).
  • a communication device comprising: a unit for implementing the method in the first aspect or any possible implementation manner of the first aspect; or a unit for implementing the second aspect or any possible implementation manner of the second aspect A method in an implementation manner; or a method for implementing the third aspect or any possible implementation manner of the third aspect.
  • a communication system including: a network device for performing the method in the first aspect or any possible implementation manner of the first aspect; or for performing the second aspect or the second aspect as described above A method in any possible implementation manner of the aspect; or for performing the method in any of the above-mentioned third aspect or any possible implementation manner of the third aspect.
  • a tenth aspect provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program or code, and when the computer program or code runs on a computer, causes the computer to execute the above-mentioned first aspect or A method in any possible implementation manner of the first aspect, a method in any possible implementation manner of the second aspect or the second aspect, and a method in the third aspect or any possible implementation manner of the third aspect.
  • a chip comprising at least one processor coupled to a memory for storing a computer program, the processor for invoking and executing the computer program from the memory, such that
  • the network device on which the chip system is installed executes the method in the first aspect or any possible implementation manner of the first aspect, the second aspect or the method in any possible implementation manner of the second aspect, and the third aspect or the method in any possible implementation manner of the second aspect.
  • the method in any of the three possible implementations.
  • the chip may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.
  • a twelfth aspect provides a computer program product, the computer program product comprising: computer program code, when the computer program code is run by a network device, the network device is made to perform the above-mentioned first aspect or the first aspect A method in any possible implementation manner, a method in any possible implementation manner of the second aspect or the second aspect, and a method in the third aspect or any possible implementation manner of the third aspect.
  • the UPF can implement other types of control plane network elements other than the SMF type to control the UPF, and the UPF can operate in isolation based on the different configurations of the SMF network element and other network elements, and process the same packet in parallel, thereby Implement multiple types of controllers to control the same UPF.
  • FIG. 1 is a schematic diagram of an example of the communication system of the present application.
  • FIG. 2 is a schematic diagram of an example of a communication scenario of the present application.
  • FIG. 3 is a schematic diagram of an example of a communication method to which the present application is applied.
  • FIG. 4 is a schematic diagram of an example of message processing logic to which the present application is applied.
  • FIG. 5 is a schematic diagram of another example of the communication method to which the present application is applied.
  • FIG. 6 is a schematic diagram of another example of the communication method to which the present application is applied.
  • FIG. 7 is a schematic diagram of an example of a communication device to which the present application is applied.
  • FIG. 8 is a schematic diagram of another example of a communication device to which the present application is applied.
  • FIG. 9 is a schematic diagram of another example of a communication device to which the present application is applied.
  • FIG. 10 is a schematic diagram of an example of a network device to which the present application is applied.
  • FIG. 11 is a schematic diagram of another example of a network device to which the present application is applied.
  • FIG. 12 is a schematic diagram of another example of a network device to which the present application is applied.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • CDMA Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • General Packet Radio Service General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • 5G system or New Radio New Radio, NR
  • V2V Vehicle to Vehicle
  • V2I Vehicle to Infrastructure
  • V2P Vehicle to Pedestrian
  • V2N Vehicle to Network
  • FIG. 1 is a network architecture applied to an embodiment of the present application, and each network element that may be involved in the network architecture will be described separately.
  • Terminal device 110 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of terminals, mobile stations, MS), terminal (terminal), user equipment (user equipment, UE), soft terminal and so on. For example, water meters, electricity meters, sensors, etc.
  • (Radio Access Network, (R)AN) network element 120 used to provide network access functions for authorized terminal equipment in a specific area, and can use different quality according to the level of terminal equipment, service requirements, etc. transmission tunnel.
  • the (R)AN network element can manage wireless resources, provide access services for terminal equipment, and then complete the forwarding of control signals and terminal equipment data between the terminal equipment and the core network.
  • the (R)AN network element can also be understood as a traditional network. in the base station.
  • network element may also be referred to as an entity, software, equipment, device, or module, etc., which is not particularly limited in this application.
  • the description of “network element” is omitted in some descriptions.
  • the (R)AN network element is abbreviated as (R)AN, in this case, the “(R)AN ”)AN network element” should be understood as (R)AN network element network element or (R)AN entity or (R)AN AN software, hereinafter, the description of the same or similar situations is omitted.
  • User plane function network element 130 used for packet routing and forwarding, and quality of service (Quality of Service, QoS) processing of user plane data, and the like.
  • QoS Quality of Service
  • the user plane network element may be a user plane function UPF network element.
  • the user plane network element may still be the UPF network element, or may have other names, which are not limited in this application.
  • Data network network element 140 used to provide a network for transmitting data.
  • the data network element may be a data network (Data Network, DN) network element.
  • the data network element may still be a DN network element, or may have other names, which are not limited in this application.
  • Access management network element 150 mainly used for mobility management and access management, etc., and can be used to implement other functions in the mobility management entity (Mobility Management Entity, MME) function except for session management, for example, legal Monitoring and access authorization/authentication functions.
  • MME Mobility Management Entity
  • the access management network element may be an access management function AMF network element.
  • the access management network element may still be an AMF network element, or may have other names, which are not limited in this application.
  • Session management network element 160 mainly used for session management, Internet Protocol (IP) address allocation and management of terminal devices, selection of the endpoints and downlinks of interfaces that can manage user plane functions, policy control and charging functions data notification, etc.
  • IP Internet Protocol
  • the session management network element may be a session management function SMF network element.
  • the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.
  • Policy control network element 170 a unified policy framework for guiding network behavior, providing policy rule information and the like for control plane functional network elements (eg, AMF, SMF network elements, etc.).
  • control plane functional network elements eg, AMF, SMF network elements, etc.
  • the policy control network element may be a Policy and Charging Rules Function (Policy and Charging Rules Function, PCRF) network element.
  • Policy and Charging Rules Function Policy and Charging Rules Function
  • PCRF Policy and Charging Rules Function
  • the policy control network element may be a policy control function PCF network element.
  • the policy control network element may still be the PCF network element, or may have other names, which are not limited in this application.
  • Network storage function network element 180 used to maintain real-time information of all network function services in the network.
  • the network storage network element may be a network registration function NRF network element.
  • the network storage network element may still be an NRF network element, or may have other names, which are not limited in this application.
  • Application network element 190 used to perform data routing affected by the application, access network element with open functions, and interact with the policy framework to perform policy control and the like.
  • the application network element may be an application function (Application Function, AF) network element.
  • AF Application Function
  • the application network element may still be the AF network element, or may have other names, which are not limited in this application.
  • Data management network element 1100 used for processing terminal equipment identification, access authentication, registration, and mobility management.
  • the data management network element may be a unified data management UDM network element.
  • the unified data management may still be a UDM network element, or may have other names, which are not limited in this application.
  • Group management network element 1200 used to be responsible for the creation and member management of a mobile network local area network (LAN), for example, a 5G LAN group (specifically, a terminal device group).
  • LAN mobile network local area network
  • 5G LAN group specifically, a terminal device group.
  • the group management network element may also be a group management function GMF network element.
  • network element may also be referred to as an entity, a device, an apparatus, or a module, etc., which is not particularly limited in this application.
  • SMF SMF network element
  • SMF entity SMF entity
  • network elements or functions may be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (eg, a cloud platform).
  • the N2 interface is the reference point of the RAN network element 20 and the AMF network element 160, and is used for sending non-access stratum (NAS) messages;
  • the N3 interface is the RAN network element 120 and the UPF.
  • the reference point between the network elements 130 is used to transmit data on the user plane, etc.;
  • the N4 interface is the reference point between the SMF network element 170 and the UPF network element 130, used to transmit, for example, the tunnel identification information of the N3 connection, the data cache indication information, and information such as downlink data notification messages;
  • the N6 interface is the reference point between the UPF network element 130 and the DN network element 140, which is used to transmit data on the user plane;
  • the N9 interface is the connection between the UPF network element 130 and another UPF network element reference points, etc.
  • control plane network elements to control UPF also requires the establishment of a connection between the two, such as establishing a connection at the device granularity, or establishing a connection between devices, or using a service interface and an air interface to realize the connection between the two.
  • the scope of the SBA is limited to the control plane network elements of the core network, excluding the user plane function UPF network elements. Moreover, the interfaces N3, N9, N6, and N4 supported by UPF are not service interfaces. As can be seen from the above architecture diagram, the network element devices that can be connected to the UPF include SMF, RAN, DN and another UPF.
  • each network element included in the communication system listed above is only an exemplary illustration, and the present application is not limited to this.
  • it may also include but not limited to:
  • Authentication service network element used for authentication service and key generation to realize two-way authentication of terminal equipment, supports a unified authentication framework, and can be an authentication server function AUSF network element;
  • Network open function network element It is used for the services and capabilities provided by the secure open 3GPP network function, which can be open internally or open to a third party, etc. It can be a network open function network element NEF;
  • Network slice selection function network element used to select a set of network slice instances for the user equipment, determine the allowed network slice selection assistance information (Network Slice Selection Assistance Information, NSSAI), and determine the AMF set that can serve the user equipment, which can be slice selection Function network element (Network Slice Selection Function, NSSF);
  • NSSAI Network Slice Selection Assistance Information
  • NSSF Network Slice Selection Function
  • Binding support function BSF network element used to find the PCF associated with the session
  • NWDA network elements used to collect and store information from terminal equipment, RAN network elements, and other network entities (eg, AMF network elements), analyze this information, and generate contextual information about users ( It can be considered as the information of the application layer), and distribute the information of the application layer, etc.
  • network function entities such as AMF, SMF, PCF, GMF, and UDM are called network function (Network Function, NF) network elements; or, in other network architectures, AMF, SMF, PCF
  • AMF, SMF, PCF A set of network elements such as , GMF and UDM can be called control plane function CPF network elements.
  • FIG. 2 shows a schematic block diagram of another example architecture involved in the present application.
  • the SMF and other network elements control the UPF through the configuration parameter A and the configuration parameter B, respectively, and the UPF executes the actions specified in the configuration parameter A and the configuration parameter B respectively, that is, mainly user plane packet processing.
  • the other network elements may be other types of control plane network elements other than SMF in the 5G network architecture, or other new network elements introduced with the evolution of the 5G architecture.
  • the UPF's processing of packets based on the configuration parameter A and the processing of the packets based on the configuration parameter B are run in isolation, that is, for different control plane network elements to control the UPF, the UPF is different. message interface.
  • the rules for packet processing in the configuration parameter A and the configuration parameter B may be the same or different, which is not limited in this application.
  • both the configuration parameter A and the configuration parameter B may include one of the following: a packet detection rule (Packet Detection Rule, PDR), a quality of service enforcement rule (Quality of Service Enforcement Rule, QER), a usage reporting rule ( Usage Reporting Rule, URR), multi-access rule (Multi-Access Rule, MAR) and forwarding action rule (Forwarding Action Rule, FAR), these five types of rules are UPF rules for packet processing, all from SMF configuration. In the logic of processing packets in UPF, PDR and FAR are required packet processing rules, and others are optional.
  • PDR Packet Detection Rule
  • QER Quality of Service Enforcement Rule
  • URR Usage Reporting Rule
  • MAR multi-access Rule
  • FAR Forwarding Action Rule
  • the PDR is used to indicate that when receiving a packet from the outside, the UPF uses the PDR to match the information in the packet, such as using the IP address in the packet header. Only when a certain PDR matches the information of the packet, the packet will continue to be processed according to the actions specified in the configuration parameters; otherwise, the packet will be discarded.
  • the FAR is used to instruct the UPF how to process the message.
  • the defined actions include: forwarding, buffering, discarding, copying, and so on.
  • a FAR is associated with a PDR, that is, if the information of the packet matches the PDR, the FAR associated with the PDR is executed.
  • a possible implementation manner includes: the SMF initiates an N4 association establishment request to the UPF; the UPF sends an N4 association establishment response to the SMF.
  • the establishment of a connection at the device granularity is the first step in establishing communication between the SMF and the UPF, and this step is used for the SMF to obtain information such as the identifier, capability, and load status of the UPF.
  • a possible implementation includes: the SMF triggers the establishment of a Packet Data Unit (PDU) session or relocates the UPF; the SMF initiates an N4 session establishment request to the UPF; the UPF sends an N4 session establishment response to the SMF; SMF and other network functions interaction.
  • PDU Packet Data Unit
  • the SMF can configure session-granularity packet processing rules for the UPF only after a device-granularity connection is established. It should be noted here that the protocol used by the SMF to control the UPF is the Packet Forwarding Control Protocol (PFCP) protocol.
  • PFCP Packet Forwarding Control Protocol
  • the UPF is generally relayed through the SMF to realize the control of the UPF, that is, the SMF will combine the control requests of other network elements with its own service logic to realize the configuration of the UPF.
  • IP 5-tuple including source IP address, destination IP address, protocol number, source port, and destination port.
  • PFD Packet Flow Detection
  • the AF hopes to configure the PFD on the UPF to identify the packets related to the server AF.
  • the current configuration process is that the AF first sends the PFD to the SMF, and then the SMF configures the PFD to the UPF, so that the server AF can control the UPF.
  • a possible implementation includes: when the SMF receives an AF configuration request, triggering to provide or delete a PFD set belonging to an application ID; the SMF sends a PFD management request to the UPF; and the UPF sends a PFD management response to the SMF.
  • the embodiments of the present application describe various embodiments in conjunction with core network equipment, wherein the functions of the core network are mainly to provide user connection, user management, and service bearer, as the bearer network provides an interface to an external network.
  • the establishment of a user connection includes functions such as mobility management (Mobile Management, MM), call management (Connection Management, CM), switching/routing, and recording notification.
  • User management includes user description, quality of service (QoS), user communication records (accounting), virtual home environment (Virtual Home Environment, VHE) and security (corresponding security measures provided by the authentication center include security for mobile services) management and security handling of access to external networks).
  • Bearer connections include access to external public switched telephone networks (PSTNs), external circuit data networks and packet data networks, the internet and intranets, and mobile phone text messages from the mobile network itself Service (Short Message Service, SMS) server and so on.
  • PSTNs public switched telephone networks
  • SMS Short Message Service
  • the basic services that the core network can provide include mobile office, e-commerce, communications, entertainment services, travel and location-based services, telemetry, simple messaging (monitoring and control), and so on.
  • the core network device may include: access and mobility management function AMF, session management function SMF, policy control function PCF, user plane function UPF and other functional units, these functional units can work independently, or can be combined in Some control functions are realized together, such as: AMF, SMF and PCF can be combined as a management device to complete access control and mobility management functions such as access authentication, security encryption, location registration of terminal devices, and user Session management functions such as establishment, release, and modification of plane transmission paths, as well as functions of analyzing some slice-related data (such as congestion) and terminal equipment-related data.
  • the embodiments of the present application are applied to a communication system including at least one forwarding device and multiple core network devices.
  • the following describes in detail how other network elements control the UPF in the embodiments of the present application with reference to the accompanying drawings.
  • the embodiments of the present application may include implementing SMF-controlled UPF, PCF-controlled UPF, NWDAF-controlled UPF, and the like.
  • UPF mainly provides service processing functions of the user plane, including service routing, packet forwarding, anchoring function, QoS mapping and execution, uplink identification and routing to the data network, downlink packet buffering and downlink data.
  • Incoming notification triggers, connection to external data network, etc.
  • the present application takes the apparatuses SMF and UPF as examples to describe the method for controlling the UPF by the non-SMF type control plane network element.
  • the SMF described later in this application can be replaced by a session management function network element, and the UPF can be replaced by a user plane function network element.
  • the device is a chip in an SMF or a chip in a UPF entity, reference may be made to the specific description that the device is a SMF entity and a UPF entity, and the description will not be repeated.
  • FIG. 3 is a schematic diagram of an example of a communication method to which the present application is applied. As shown in Figure 3, the implementation step 300 includes:
  • the session management function network element acquires the interface identifier.
  • acquiring the interface identifier may include: the session management function network element determines the interface identifier by itself, where the interface identifier corresponds to the first network element. That is to say, the session management function network element assigns an interface identifier to the user plane function network element based on the communication establishment of the device granularity, and sends the interface identifier to the user plane function network element through the following steps, so as to inform the user plane function network element of the interface identifier. The element configures the interface corresponding to the first network element.
  • the first network element refers to a network element of a non-session management function type.
  • the first network element may be an access management function AMF, a network data analysis function NWDAF, a policy control function PCF, a group management function GMF, a network opening function NEF, a unified data management UDM, a media function MF, a network registration function NRF, Authentication server function AUSF, binding support function BSF, network data analysis NWDA and other different types of control plane functions CPF network elements.
  • the interface corresponding to the interface identifier is a newly added packet interface of the user plane functional network element, including packet egress and/or packet entry.
  • acquiring the interface identifier may further include: the session management function network element receives the interface identifier from the user plane function network element, that is, the user plane function network element allocates the interface identifier by itself, and The interface identifier is sent to the session function management network element, where the interface identifier corresponds to the first network element.
  • the session management function network element may send first information to the user plane function network element, where the first information is used to instruct the user plane function network element to assign the above-mentioned interface identifier, that is, a new message
  • the interface corresponds to the first network element.
  • the first information may include one of the following: the identifier of the first network element, or the address of the first network element; a codeword (codeword), service requirements and service types of the first network element; or, a message Data size, whether the message is encrypted, etc.
  • the address of the first network element may include an IP address and a media access control address (Media Access Control Address, MAC) of the first network element.
  • the session management function network element may determine, according to the first information, user plane function network elements that the first network element can control. Among them, the code word can be used as a kind of password for mutual detection between multiple devices.
  • the user plane function network element may send capability indication information to the session management function network element, where the capability indication information is used to indicate that the user plane function network element can be used by one or more network elements of the first type. Meta control. It should be noted that the network element of the first type is a network element of a non-session management function type.
  • the capability indication information may include: the user plane function network element reports charging information, time, etc. to a device other than the SMF type, such as: a charging function (Charging Function, CHF) network element; or a user plane function
  • the network element reports the user service status analysis to devices other than the SMF type, such as the network data analysis function NWDAF network element.
  • the user service status analysis includes at least one of: whether the traffic is abnormal, whether the degree of delay change caused by network congestion is severe, and whether the delay satisfies the service experience and other functions.
  • the capability indication information may indicate a specific type of device to which the user plane function network element can report.
  • the first network element may send a request message to the session management function network element, where the request message is used to request to control the user plane function network element.
  • the first network element may select the session management function network element based on at least one of the coverage area of the service, the camping area of the UE, and the jurisdiction of the first network element.
  • the request message may include at least one of the following: the identifier of the user plane function network element (UPF ID), the service area (service area) covered by the user plane function network element, and the session identifier of the user equipment (UE session ID) .
  • UPF ID the identifier of the user plane function network element
  • service area service area covered by the user plane function network element
  • session ID session identifier of the user equipment
  • the request message sent by the first network element includes the UPF ID, it means that the first network element explicitly informs the session management function network element which user plane function network element it wants to control. At this time, the session management function network element will The corresponding user plane function network element can be found out.
  • the first network element may not know which user plane function network element corresponds to the first network element.
  • the session management function network element can find one or more user plane function network elements in the service area, and select one of the user plane network elements to be controlled by the first network element.
  • the session management function network element manages the user plane management network element corresponding to the specific session. Just find out.
  • the UE session ID also known as the identifier of the PDU session, or the session ID, the session identifier
  • the session ID is used to mark a session of a user equipment, and the session of the user equipment is composed of one or more user plane function networks.
  • the meta is responsible for implementing the user plane connection of the session. Therefore, the UE session ID can be associated with one or more user plane functional network elements.
  • the session management function network element sends the address and interface identifier of the user plane function network element to the first network element, and correspondingly, the first network element receives the address and interface identifier of the user plane function network element from the session management function network element.
  • the interface identifier is used by the first network element to determine the interface corresponding to the interface identifier, and the interface corresponding to the address of the user plane function network element and the interface identifier is used by the first network element to control the user plane function network element.
  • the user plane management network element can flexibly interact with the first network element device, and does not need to be forwarded by the session management function network element, reducing signaling. forwarding delay.
  • the session management function network element may also send at least one of an identifier (UPF ID) and a codeword (codeword) of the user plane management network element to the first network element.
  • UPF ID an identifier
  • codeword codeword
  • the first network element sends the packet detection rule PDR and the packet processing rule (Packet Handle Rule, PHR) to the user plane management network element.
  • the user plane functional network element receives the packet detection rule PDR from the first network element and the packet processing rule PHR.
  • packet processing rules PHR may include quality of service enforcement rules QER, usage reporting rules URR, multi-access rules MAR and forwarding action rules FAR, etc.
  • QER quality of service enforcement rules
  • URR usage reporting rules
  • MAR multi-access rules
  • FAR forwarding action rules
  • the first network element may also send a codeword to the user plane management network element.
  • the code word can be used as a kind of password for mutual detection between multiple devices.
  • the user plane functional network element receives downlink/uplink packets.
  • the user equipment UE sends an uplink message to the user plane functional network element, and/or the data network DN sends a downlink message to the user plane functional network element; correspondingly, the user plane functional network element receives the uplink message from the user equipment UE message, and/or receive downlink messages from the data network DN.
  • uplink message/downlink message can be performed through radio resource control (Radio Resource Control, RRC) signaling, media access control management unit (Media Access Control, Control Element, MAC CE), physical layer signaling (for example: PDCCH) in at least one way.
  • RRC Radio Resource Control
  • MAC CE media access control management unit
  • PDCCH physical layer signaling
  • the user plane functional network element detects uplink/downlink packets according to the packet detection rule PDR, and processes the uplink/downlink packets according to the packet processing rule PHR.
  • FIG. 4 is a schematic diagram showing an example of internal processing logic when a user plane functional network element receives a packet in from the outside.
  • the user plane function network element may include two layers of interfaces, for example, the first layer interface and the second layer interface, the external packet #1 first passes through the first layer interface, and then the user plane function network element will copy the The packet #1 goes to the Layer 2 interface. Assume that the Layer 2 interface of the user plane function network element has two pairs of packet entry and exit.
  • Packet entry and exit #A is used for the session function management network element (for example: SMF network element) to control the user plane function network element.
  • the packet entrance and exit #B is used for the first network element (for example: NWDAF network element) to control the user plane function network element. That is, the user plane management network element copies the packet #1 to the packet entry #A and the packet entry #B respectively, detects the packet #1 according to the PDR#A of the packet entry #A, and detects the packet #1 according to the packet entry #A.
  • the PDR#B of #B detects the packet #1, for example, by using the IP address in the packet header.
  • the user plane function NE detects the packet #1 according to the packet processing rule PDR#A and the packet processing rule PDR#B respectively, it detects from two different entrances, namely, the packet entrance# A and packet entry #B, these two packet entries are isolated, and the user plane function NE processes the same packet #1 in parallel through these two packet entries.
  • packet egress #A and packet egress #B are also isolated. That is to say, each control plane NE installed on the user plane functional NE has an independent packet interface.
  • the user plane functional NE isolates the SMF NE and the NWDAF NE respectively configured with the rule parameter PDR#A and PDR#B.
  • the packet detection rule #A and the packet detection rule #B may be the same or different, which is not limited in this application.
  • the packet detection rule PDR#B matches the packet #1, it means that the packet #1 corresponds to the NWDAF network element.
  • the user plane function network element executes the corresponding packet processing rule for the packet #1.
  • PHR#B such as forwarding, copying, etc., so as to realize the NWDAF network element to control the user plane management function network element.
  • the above-mentioned packet processing rule PHR may include MAR, FAR, QER, URR, etc.
  • the packet entry and the packet exit may exist simultaneously or independently, which is not limited in this application.
  • the NWDAF network element executes the packet detection rule #B and the packet processing rule #B on the packet #1, so that the NWDAF network element can control the user plane function network element.
  • the user plane functional network elements can process the same data packet in parallel based on the packet detection rule #A corresponding to the SMF network element and the packet detection rule #B corresponding to the NWDAF network element, respectively.
  • the user plane functional network elements are separated from the different configurations of the SMF network element and the NWDAF network element, thereby enabling different types of controllers to control the same user plane functional network element.
  • FIG. 5 is a schematic diagram of a method for controlling UPF#A by a control plane network element #A in a core network according to an embodiment of the present application.
  • UPF#A take UPF#A's own determination of the interface identifier corresponding to network element #A as an example, where UPF#A is used as a forwarding device, SMF#A is used as a control device, and network element #A can be a computer in the core network.
  • Other control plane network elements such as the network element CHF with the charge function, the network element with the policy control function PCF, and the NWDAF.
  • the implementation step 500 includes:
  • UPF#A ie, an example of a user plane function network element
  • SMF#A ie, an example of a session management function network element
  • SMF#A receives the capability from UPF#A Indication information #A.
  • the capability indication information #A is used to indicate that the UPF #A can be controlled by other types of network elements (eg, network element #A).
  • network element #A is a non-session management function type network element.
  • the type of the network element #A may include: AMF, NWDAF, PCF, GMF, NEF, UDM, MF, NRF, AUSF, BSF, NWDA and other different types of control plane function CPF network elements.
  • the capability indication information may include: the user plane functional network element reports charging information, time, etc. to devices other than the SMF type, such as the charging function CHF network element; or the user plane functional network element reports the user service Status analysis is reported to devices other than SMF types, such as: network data analysis function NWDAF network element, etc.
  • the analysis of user service status includes: whether the traffic is abnormal, whether the degree of delay change caused by network congestion is severe, whether the delay meets at least one of the functions such as service experience.
  • the network element #A (ie, an example of the first network element) sends the request message #A to the SMF #A, and accordingly, the SMF #A receives the request message #A from the network element #A.
  • the request message #A is used by the network element #A to request to control the UPF #A.
  • the network element #A may select the SMF #A based on at least one of the coverage area of the service, the camping area of the UE, and the jurisdiction of the network element #A.
  • the request message #A may include at least one of the following: identification information (UPF ID) of UPF #A, a service area (service area) covered by UPF #A, and a session identifier (UE session ID) of the user equipment.
  • UPF ID identification information
  • service area service area covered by UPF #A
  • UE session ID session identifier
  • SMF#A determines the UPF#A used for the control of network element #A according to the received request message #A.
  • the request message #A sent by network element #A includes the service area covered by UPF #A, for network element #A, it may not know which UPF network element corresponds to this network element #A. At this time, SMF#A can find one or more UPF network elements in the service area, and select one of the UPF#A network elements to be controlled by network element #A.
  • the request message #A sent by the network element #A includes the UE session ID, it means that the network element #A wishes to control a specific session of a user equipment.
  • SMF#A will send the UPF#A network element corresponding to the specific session. Just find out.
  • the UE session ID also known as the identifier of the PDU session, or the session ID, the session identifier
  • the session ID is used to mark a session of a user equipment
  • the session of the user equipment is composed of one or more user plane function networks.
  • the meta is responsible for implementing the user plane connection of the session. Therefore a UE session ID can be associated with one or more UPFs.
  • SMF#A sends the first information #A to UPF#A, and accordingly, UPF#A receives the first information #A from SMF#A.
  • the first information #A is used to instruct the UPF #A to allocate an interface identifier corresponding to the network element #A, that is, a new message interface, and the message interface corresponds to the network element #A. That is to say, at this time, UPF#A can have two sets of packet interfaces, one for SMF#A and the other for NE #A.
  • the first information #A may include one of the following: the identifier of network element #A, or the address of network element #A; a codeword (codeword), service requirements and service type of network element #A; or, Packet data size, whether the packet is encrypted, etc.
  • the address of the network element #A may include the IP address and the media access control address MAC of the network element #A.
  • the SMF#A can determine the controllable UPF#A for the network element #A according to the first information #A.
  • the code word can be used as a kind of password for mutual detection between multiple devices.
  • UPF#A determines the interface identifier corresponding to network element #A, and sends the interface identifier to SMF#A, and accordingly, SMF#A receives the interface identifier from UPF#A.
  • the interface identifier corresponds to network element #A.
  • SMF#A sends the address and interface identifier of UPF#A to network element #A, and correspondingly, network element #A receives the address and interface identifier of UPF#A from SMF#A.
  • the interface identifier is used by the network element #A to determine the interface corresponding to the interface identifier, and the interface corresponding to the address of the UPF#A and the interface identifier is used by the network element #A to control the UPF#A network element.
  • the interface corresponding to the interface identifier is the newly added packet interface of the UPF#A network element, including the packet exit and/or the packet entry.
  • the SMF#A may also send at least one of an identifier (UPF ID) and a codeword (codeword) of the UPF#A to the network element #A.
  • UPF ID an identifier
  • codeword codeword
  • the network element #A sends the packet detection rule PDR and the packet processing rule PHR corresponding to the network element #A to the UPF #A.
  • the UPF #A receives the packet detection rule PDR and the packet from the network element #A Processing rule PHR.
  • packet processing rules PHR may include quality of service enforcement rules QER, usage reporting rules URR, multi-access rules MAR and forwarding action rules FAR, etc.
  • QER quality of service enforcement rules
  • URR usage reporting rules
  • MAR multi-access rules
  • FAR forwarding action rules
  • the network element #A may also send a codeword to the UPF #A.
  • the code word can be used as a kind of password for mutual detection between multiple devices.
  • UPF#A installs the packet detection rule PDR at the entry of the newly added packet, and/or installs the packet processing rule PHR at the exit of the newly added packet.
  • the newly added message exit and/or the newly added message entry both correspond to network element #A.
  • the packet detection rule PDR corresponds to the newly added packet entry, that is, the PDR is used to instruct UPF#A to detect the packet information associated with network element #A. If the packet is related to the user's IP address, the packets related to the specific user's IP address in the UPF#A match are sufficient.
  • the message processing rule PHR corresponds to the newly added message export, that is, the PHR is used to instruct UPF#A to which corresponding controller to send the processed message.
  • the PHR may also include other additional processing information, for example, used to indicate the granularity in which the UPF#A performs information statistics, and the like.
  • UE sends an uplink packet to UPF#A through an interface corresponding to network element #A, and accordingly, UPF#A receives an uplink data packet from user equipment UE through an interface corresponding to network element #A.
  • the data network DN sends a downlink data packet to the UPF#A through the interface corresponding to the network element #A, and accordingly, the UPF#A receives the downlink data packet from the data network DN through the interface corresponding to the network element #A.
  • uplink messages and/or downlink messages in steps S581 and S582 may be transmitted by at least one of radio resource control RRC signaling, medium access control management unit MAC CE, and physical layer signaling.
  • UPF#A detects the uplink packet and/or the downlink packet according to the packet detection rule PDR, and processes the uplink packet and/or the downlink packet according to the packet processing rule PHR.
  • the number of message interfaces depends on the number of controllers requesting to control UPF#A, that is, one controller corresponds to a pair of message interfaces of UPF#A.
  • the SMF#A network element instructs the UPF#A to allocate the newly added packet interface corresponding to the network element #A, and the UPF#A sends the newly added interface identifier to the SMF#A, so that the non-SM#A type Other types of control plane network elements can control the UPF#A.
  • UPF#A can isolate different configuration parameters of SMF#A network element and network element #A, realize parallel processing of the same data packet, and then realize that different types of multi-controllers control the same UPF#A.
  • FIG. 6 is a schematic diagram of a method for controlling UPF #a by a control plane network element #a in a core network according to an embodiment of the present application.
  • this implementation takes SMF#a assigning an interface identifier to UPF#a as an example.
  • the main difference from the above step 500 is that SMF #a may not send the first information to UPF #a, and SMF #a may determine the interface identification information corresponding to network element #a by itself, and send the interface identification to UPF #a.
  • the implementation step 600 includes:
  • UPF#a ie, an example of a user plane function network element
  • SMF#a ie, an example of a session management function network element
  • SMF#a receives the capability from UPF#a Indication information #a.
  • the network element #a (ie, an example of the first network element) sends the request message #a to the SMF #a, and correspondingly, the SMF #a receives the request message #a from the network element #a.
  • the SMF #a determines the UPF #a used for the control of the network element #a according to the request message #a.
  • steps S610 to S630 reference may be made to the descriptions of the foregoing steps S510 to S530, which are not repeated here for brevity.
  • SMF#a determines the interface identifier corresponding to the network element #a, that is, SMF#a adds a new interface identifier for the UPF#a distribution packet, and the interface identifier is used by the network element #a to determine the interface corresponding to the interface identifier.
  • a new message interface is added for NE #a to control UPF#a. The newly added message interface identifier corresponds to the network element #a.
  • SMF#a determines the interface identifier corresponding to NE #a based on the device granularity connection between SMF#a and UPF#a. Therefore, SMF#a has a The number information, identification information, etc. of the message interface) is determined, and the SMF#a can realize the allocation of the newly added message interface identifier for the UPF#a.
  • SMF#a sends the interface identifier to UPF#a, and correspondingly, UPF#a receives the interface identifier from UPF#a, where the interface identifier corresponds to network element #a.
  • S660, SMF#a sends the address and interface identifier of UPF#a to network element #a, and correspondingly, network element #a receives the address and interface identifier of UPF#a from SMF#a.
  • the network element #a sends the packet detection rule PDR and the packet processing rule PHR corresponding to the network element #a to the UPF #a.
  • the UPF #a receives the packet detection rule PDR and the packet from the network element #a Processing rule PHR.
  • the network element #a is a network element of a non-session management function type.
  • UPF#a installs the packet detection rule PDR at the entry of the newly added packet, and/or installs the packet processing rule PHR at the packet exit.
  • the newly added message exit and the newly added message entry both correspond to network element #a.
  • the UE sends an uplink packet to UPF#a through an interface corresponding to network element #a, and accordingly, UPF#a receives an uplink data packet from the user equipment UE through an interface corresponding to network element #a.
  • the data network DN sends a downlink data packet to the UPF #a through the interface corresponding to the network element #a, and accordingly, the UPF #a receives the downlink data packet from the data network DN through the interface corresponding to the network element #a.
  • UPF#a detects the upstream message and/or the downstream message according to the message detection rule PDR, and processes the upstream message and/or the downstream message according to the message processing rule PHR.
  • steps S660 to S693 reference may be made to the descriptions of the foregoing steps S550 to S590, which are not repeated here for brevity.
  • the interface identifier of the newly added message corresponding to the network element #a is determined by the UPF#a, and the identifier of the newly added message interface is sent to the SMF#a, so that other types of control planes other than SM#a
  • the network element controls the UPF#a.
  • UPF#a can isolate different configuration parameters of SMF#a network element and network element #a, realize parallel processing of the same data packet, and further realize that different types of multi-controllers control the same UPF#a.
  • FIG. 7 is a schematic diagram of a communication apparatus 10 (which may also be a network device, such as SMF#A) applicable to this embodiment of the present application.
  • the communication device 10 includes: a transceiver unit 11 and a processing unit 12 .
  • the processing unit 12 is used to obtain the interface identifier.
  • the transceiver unit 11 is configured to send the address and interface identifier of the user plane function network element to the first network element, where the interface identifier is used by the first network element to determine the interface corresponding to the interface identifier, the address and interface of the user plane function network element The identifier is used by the first network element to control the user plane function network element.
  • the communication apparatus 10 may correspond to the session function management network element in the method 300/500/600 of the method 300/500/600 for the first network element to control the user plane function management network element according to the embodiment of the present application, and the communication apparatus 10 may include a method for executing A module (or unit) of a method performed by a network device in the method 300/500/600 of the method 300/500/600 for the first network element to control the user plane function management network element in FIG. 3/FIG. 5/FIG.
  • each module (or unit) and the above-mentioned other operations and/or functions in the communication device 10 are used to implement the method 300/500 of the first network element controlling the user plane function in FIG. 3/FIG. 5/FIG. 6, respectively, for managing network elements /600 corresponding process.
  • the transceiver unit 11 is configured to execute S320 in the methods 300/500/600, or S510, S520, S540, S541 and S550, or S610, S620, S650 and S660;
  • the processing unit 12 is configured to execute the methods 300/500/ S310 in 600, or S530, or S630 and S640.
  • the process of each module (or unit) performing the above-mentioned corresponding steps has been described in detail in the methods 300/500/600, and for the sake of brevity, it will not be repeated here.
  • FIG. 7 It should be understood that the structure of the apparatus 10 illustrated in FIG. 7 is only a possible form, and should not constitute any limitation to the embodiments of the present application. This application does not exclude the possibility of other forms of network equipment that may appear in the future.
  • the communication apparatus 10 may correspond to the first network element in the foregoing method embodiments to control the network equipment of the user plane function network element, and the above and other aspects of each module (or unit) in the communication apparatus 10 may be controlled
  • the management operations and/or functions are respectively to implement the corresponding steps of the foregoing methods, so the beneficial effects in the foregoing method embodiments can also be realized.
  • FIG. 8 is a schematic diagram of a communication apparatus 20 (which may also be a network device, such as UPF#A) applicable to this embodiment of the present application.
  • the communication device 20 includes: a transceiver unit 21 and a processing unit 22 .
  • the transceiver unit 21 is configured to receive a packet detection rule and a packet processing rule corresponding to the first network element from a first network element, where the first network element is a network element of a non-session management function type.
  • the transceiver unit 21 is further configured to receive packets through the interface corresponding to the first network element.
  • the processing unit 22 is configured to detect the message according to the message detection rule, and process the message according to the message processing rule.
  • the communication apparatus 20 may correspond to the user plane function network element in the method 300/500/600 for the first network element to control the user plane function network element according to the embodiment of the present application, and the communication apparatus 20 may include a method for executing the diagram 3/ The module (or unit) of the method performed by the network device of the method 300/500/600 for the first network element to control the user plane function network element in FIG. 5/ FIG. 6 .
  • each module (or unit) and the above-mentioned other operations and/or functions in the communication device 20 are respectively for realizing the method 300/500/ of the first network element in FIG. 3/FIG. 5/FIG. 6 controlling the user plane function network element. 600 corresponding process.
  • the transceiving unit 21 is configured to perform S330 and S340 in the methods 300/500/600, or S510, S540, S541, S560 and S581 and S582, or S610, S650, S670, S691 and S692;
  • the processing unit 22 is configured to Perform S350, or S570 and S590, or S680 and S693 in the method 300/500/600.
  • the process of each module (or unit) performing the above-mentioned corresponding steps has been described in detail in the methods 300/500/600, and for the sake of brevity, it will not be repeated here.
  • FIG. 8 It should be understood that the structure of the apparatus 20 illustrated in FIG. 8 is only a possible form, and should not constitute any limitation to the embodiments of the present application. This application does not exclude the possibility of other forms of network equipment that may appear in the future.
  • the communication apparatus 20 may correspond to the first network element in the foregoing method embodiments to control the network equipment of the user plane function network element, and the above and other aspects of each module (or unit) in the communication apparatus 20 may be controlled
  • the management operations and/or functions are respectively to implement the corresponding steps of the foregoing methods, so the beneficial effects in the foregoing method embodiments can also be realized.
  • processing module in the embodiments of the present application may be implemented by a processor
  • transceiver module or unit
  • transceiver may be implemented by a transceiver
  • FIG. 9 is a schematic diagram of a communication apparatus 30 (which may also be a network device, such as network element #A) applicable to this embodiment of the present application.
  • the communication device 30 includes: a transceiver unit 31 and a processing unit 32 .
  • the transceiver unit 31 is configured to receive the address and interface identifier of the user plane function network element from the session management function network element;
  • the processing unit 32 is configured to determine the interface corresponding to the interface identifier according to the interface identifier;
  • the processing unit 32 is further configured to control the user plane function network element according to the interface corresponding to the address of the user plane function network element and the interface identifier; the transceiver unit 31 is further configured to send a message corresponding to the first network element to the user plane function network element
  • the packet detection rules and packet processing rules are based on the packet detection rules and packet processing rules, wherein the first network element is a network element of a non-session management function type.
  • the communication apparatus 30 may correspond to other types of control plane network elements of a non-session management function type in the method 300/500/600 for the first network element to control a user plane function network element according to the embodiment of the present application, and the communication The apparatus 30 may include a module (or unit) for performing the method performed by the network device of the method 300/500/600 of the first network element controlling the user plane function network element in FIG. 3/FIG. 5/FIG. 6.
  • each module (or unit) and the above-mentioned other operations and/or functions in the network device 30 are respectively to implement the method 300/500/ of the first network element in FIG. 3/FIG. 5/FIG. 6 to control the user plane function network element. 600 corresponding process.
  • the transceiver unit 31 is configured to perform S320 and S330, or S520, S550 and S560, or S620, S660 and S670 in the methods 300/500/600.
  • the process of each module (or unit) performing the above-mentioned corresponding steps has been described in detail in the methods 300/500/600, and for the sake of brevity, it will not be repeated here.
  • the communication apparatus 30 may correspond to the first network element in the foregoing method embodiments to control the network equipment of the user plane function network element, and the above and other aspects of the various modules (or units) in the communication apparatus 30 may be controlled
  • the management operations and/or functions are respectively to implement the corresponding steps of the foregoing methods, so the beneficial effects in the foregoing method embodiments can also be realized.
  • processing module in the embodiments of the present application may be implemented by a processor
  • transceiver module or unit
  • transceiver may be implemented by a transceiver
  • FIG. 10 is a schematic diagram of a communication device (also referred to as a network device) 40 provided by an embodiment of the present application.
  • the device 40 may be a network device (eg, SMF) or a chip Or a circuit, such as a chip or circuit that can be provided in a network device.
  • a network device eg, SMF
  • a chip or circuit such as a chip or circuit that can be provided in a network device.
  • the apparatus 40 may include a processor 41 (ie, an example of a processing unit) and a memory 42 .
  • the memory 42 is used for storing instructions
  • the processor 41 is used for executing the instructions stored in the memory 42, so that the apparatus 40 implements the network device (for example, SMF) in the above method (for example, the method 300 or the method 500 or the method 600). steps to perform.
  • the network device for example, SMF
  • the device 40 may also include an input port 43 (ie, an example of a communication unit) and an output port 44 (ie, another example of a communication unit). It should be understood that the processor 41, the memory 42, the input port 43 and the output port 44 can communicate with each other through an internal connection path to transmit control and/or data signals.
  • an input port 43 ie, an example of a communication unit
  • an output port 44 ie, another example of a communication unit.
  • the processor 41, the memory 42, the input port 43 and the output port 44 can communicate with each other through an internal connection path to transmit control and/or data signals.
  • the memory 42 is used to store a computer program, and the processor 41 can be used to call and run the computer program from the memory 42 to control the input port 43 to receive signals, and control the output port 44 to send signals to complete the network device in the above method. A step of.
  • the memory 42 may be integrated in the processor 41 or may be provided separately from the processor 41 .
  • the input port 43 is a receiver
  • the output port 44 is a transmitter.
  • the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.
  • the input port 43 is an input interface
  • the output port 44 is an output interface
  • the functions of the input port 43 and the output port 44 can be considered to be realized by a transceiver circuit or a dedicated chip for transceiver.
  • the processor 41 can be considered to be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.
  • a general-purpose computer may be used to implement the network device provided in the embodiments of the present application.
  • the program codes that will implement the functions of the processor 41 , the input port 43 and the output port 44 are stored in the memory 42 , and the general-purpose processor implements the functions of the processor 41 , the input port 43 and the output port 44 by executing the codes in the memory 42 .
  • the processor 41 is configured to acquire the interface identifier.
  • the output port 44 is used to send the address and interface identifier of the user plane function network element to the first network element, the interface identifier is used by the first network element to determine the interface corresponding to the interface identifier, the address and interface of the user plane function network element The identifier is used by the first network element to control the user plane function network element.
  • the apparatus 40 is configured in or is itself a session management function entity SMF.
  • modules or units in the apparatus 40 listed above are only exemplary descriptions, and the modules or units in the apparatus 40 may be used to perform actions or processes performed by the network equipment in the above method 300 or 500 or 600 For the process, here, in order to avoid redundant description, the detailed description thereof is omitted.
  • the processor 41 may perform the actions performed by the SMF in the above S530 or S630 and S640.
  • SoC system-on-chip
  • all or part of the functions of the device 40 are implemented by SoC technology, for example, by a network device function chip, the network device
  • the function chip integrates a processor, a memory, a communication interface and other devices, and the program related to the network equipment functions is stored in the memory, and the processor executes the program to realize the related functions of the base station.
  • the network device function chip can also read the external memory of the chip to realize the related functions of the base station.
  • FIG. 11 is a schematic diagram of a communication device (also referred to as a network device) 50 provided by an embodiment of the present application.
  • the device 50 may be a network device (for example, UPF) or a chip Or a circuit, such as a chip or circuit that can be provided in a network device.
  • the apparatus 50 may include a processor 51 (ie, an example of a processing unit) and a memory 52 .
  • the memory 52 is used for storing instructions
  • the processor 51 is used for executing the instructions stored in the memory 52, so that the apparatus 50 implements the network device (for example, UPF) in the above method (for example, the method 300 or the method 500 or the method 600 ). steps to perform.
  • the network device for example, UPF
  • the apparatus 50 may further include an input port 53 (ie, an example of a communication unit) and an output port 54 (ie, another example of a communication unit). It should be understood that the processor 51, the memory 52, the input port 53 and the output port 54 may communicate with each other through an internal connection path to transmit control and/or data signals.
  • an input port 53 ie, an example of a communication unit
  • an output port 54 ie, another example of a communication unit.
  • the processor 51, the memory 52, the input port 53 and the output port 54 may communicate with each other through an internal connection path to transmit control and/or data signals.
  • the memory 52 is used to store a computer program, and the processor 51 can be used to call and run the computer program from the memory 52 to control the input port 53 to receive signals, control the output port 54 to send signals, and complete the network device in the above method. A step of.
  • the memory 52 may be integrated in the processor 51 or may be provided separately from the processor 51 .
  • the input port 53 is a receiver
  • the output port 54 is a transmitter.
  • the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.
  • the input port 53 is an input interface
  • the output port 54 is an output interface
  • the functions of the input port 53 and the output port 54 can be considered to be implemented by a transceiver circuit or a dedicated chip for transceiver.
  • the processor 51 can be considered to be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.
  • a general-purpose computer may be used to implement the network device provided by the embodiments of the present application.
  • the program codes that will implement the functions of the processor 51 , the input port 53 and the output port 54 are stored in the memory 52 .
  • the input port 53 is used to receive a packet detection rule and a packet processing rule corresponding to the first network element from the first network element, where the first network element is a network element with a non-session management function type .
  • the input port 53 is also used for receiving packets through the interface corresponding to the first network element.
  • the processor 51 is configured to detect the message according to the message detection rule, and process the message according to the message processing rule.
  • the apparatus 50 is configured in or is a user plane functional entity UPF.
  • modules or units in the apparatus 50 listed above are only exemplary descriptions, and the modules or units in the apparatus 50 can be used to perform actions or processes performed by the network equipment in the above method 300 or 500 or 600 For the process, here, in order to avoid redundant description, the detailed description thereof is omitted.
  • the processor 51 may perform the actions performed by the UPF in the above-mentioned S350, or S570 and S590, or S680 and S693.
  • SoC system-on-chip
  • all or part of the functions of the device 50 are implemented by SoC technology, for example, by a network device function chip
  • the network device The function chip integrates a processor, a memory, a communication interface and other devices, and the program related to the network equipment functions is stored in the memory, and the processor executes the program to realize the related functions of the base station.
  • the network device function chip can also read the external memory of the chip to realize the related functions of the base station.
  • FIG. 11 the structure of the apparatus 50 illustrated in FIG. 11 is only a possible form, and should not constitute any limitation to the embodiments of the present application. This application does not exclude the possibility of other forms of base station structures that may appear in the future.
  • FIG. 12 is a schematic diagram of a communication device (also referred to as a network device) 60 provided by an embodiment of the present application.
  • the device 60 may be a network device (for example, other network element other NF), It can also be a chip or circuit, such as a chip or circuit that can be provided in a network device.
  • the apparatus 60 may include a processor 61 (ie, an example of a processing unit) and a memory 62 .
  • the memory 62 is used for storing instructions
  • the processor 61 is used for executing the instructions stored in the memory 62, so that the apparatus 60 implements the network device (for example, other network devices) in the above method (for example, the method 300 or the method 500 or the method 600). element) steps to perform.
  • the device 60 may also include an input port 63 (ie, an example of a communication unit) and an output port 64 (ie, another example of a communication unit). It should be understood that the processor 61, the memory 62, the input port 63 and the output port 64 may communicate with each other through an internal connection path to transmit control and/or data signals.
  • an input port 63 ie, an example of a communication unit
  • an output port 64 ie, another example of a communication unit.
  • the processor 61, the memory 62, the input port 63 and the output port 64 may communicate with each other through an internal connection path to transmit control and/or data signals.
  • the memory 62 is used to store a computer program, and the processor 61 can be used to call and run the computer program from the memory 62 to control the input port 63 to receive signals, control the output port 64 to send signals, and complete the network device in the above method. A step of.
  • the memory 62 can be integrated in the processor 61 or can be provided separately from the processor 61 .
  • the input port 63 is a receiver
  • the output port 64 is a transmitter.
  • the receiver and the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.
  • the input port 63 is an input interface
  • the output port 64 is an output interface
  • the functions of the input port 63 and the output port 64 can be considered to be implemented by a transceiver circuit or a dedicated chip for transceiver.
  • the processor 61 can be considered to be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.
  • a general-purpose computer may be used to implement the network device provided in the embodiments of the present application.
  • the program codes to realize the functions of the processor 61 , the input port 63 and the output port 64 are stored in the memory 62 , and the general-purpose processor implements the functions of the processor 61 , the input port 63 and the output port 64 by executing the codes in the memory 62 .
  • the input port 63 is used to receive the address and interface identifier of the user plane function network element from the session management function network element;
  • the processor 61 is configured for the first network element to determine the interface corresponding to the interface identifier according to the interface identifier,
  • the processor 61 is further configured for the first network element to control the user plane function network element according to the address of the user plane function network element and the interface corresponding to the interface identifier.
  • the output port 64 is used to send the packet detection rule and the packet processing rule corresponding to the first network element to the user plane functional network element, where the first network element is a network element of a non-session management function type.
  • the device 60 is configured in or is itself a controller of other types than the SMF type.
  • each module or unit in the above-listed apparatus 60 is merely illustrative, and each module or unit in the apparatus 60 may be used to perform each action or process performed by the network device in the above method 300 or 500 or 600 For the process, here, in order to avoid redundant description, the detailed description thereof is omitted.
  • SoC system-on-chip
  • all or part of the functions of the device 60 are implemented by SoC technology, for example, by a network device function chip, the network device
  • the function chip integrates a processor, a memory, a communication interface and other devices, and the program related to the network equipment functions is stored in the memory, and the processor executes the program to realize the related functions of the base station.
  • the network device function chip can also read the external memory of the chip to realize the related functions of the base station.
  • the embodiment of the present application further provides a communication system, which includes the aforementioned at least one forwarding device and one or more than one network device.
  • the processor may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), dedicated integrated Circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDR SDRAM Double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination.
  • the above-described embodiments may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server or data center by wire (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that contains one or more sets of available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media.
  • the semiconductor medium may be a solid state drive.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
  • a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and the computing device may be components.
  • One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer and/or distributed between 2 or more computers.
  • these components can execute from various computer readable media having various data structures stored thereon.
  • a component may, for example, be based on a signal having one or more data packets (eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals) Communicate through local and/or remote processes.
  • data packets eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, removable hard disk, read only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes.

Landscapes

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

Abstract

本申请提供了一种通信方法和装置，该方法包括：会话管理功能网元获取接口标识；所述会话管理功能网元向第一网元发送用户面功能网元的地址和所述接口标识，所述接口标识用于所述第一网元确定所述接口标识对应的接口，所述用户面功能网元的地址和所述接口标识对应的接口用于所述第一网元控制所述用户面功能网元。在本申请实施例的通信方法中，UPF能够实现非SMF类型的其他类型的控制面网元控制UPF网元，而且UPF网元能够基于SMF网元和其他网元的不同配置隔离运行，并行处理同一个报文，从而实现多类型的控制器控制同一UPF网元。

Description

通信方法和网络设备 技术领域
本申请涉及通信领域，并且更具体地，涉及一种通信方法和网络设备。
背景技术
目前，在基于服务的架构(Service Based Architecture，SBA)中，有且只有会话管理功能(Session Management Function，SMF)网元可以控制用户面功能(User Plane Function，UPF)网元。例如，SMF网元可以通过N4接口控制UPF网元，其他网元则需要经过SMF网元中转才可以控制UPF网元。
随着第五代(the 5th Generation，5G)网络的演进，UPF的功能也逐渐强大，比如：它可以做用户业务状态分析，包括：流量是否异常、网络拥塞导致的延迟变化的程度是否厉害、时延是否满足业务体验，等等。这些功能可以满足网络数据分析功能(NetWork Data Analytics Funtion，NWDAF)网元的需求，且是实时感知的，而当前NWDAF网元并不能直接控制UPF网元。
因此，上述技术已经无法很好地满足UPF网元功能的实现，如何使得非SMF类型的网元控制UPF网元，以及UPF网元如何将SMF网元和其他类型的网元的配置隔离运行成为亟待解决的问题。
发明内容
本申请提供一种通信方法和网络设备，能够实现非SMF类型的其他网元控制UPF网元，而且UPF网元能够基于SMF网元和其他类型网元的不同配置隔离运行，并行处理同一个报文，从而实现多类型的控制器控制同一个UPF网元。
第一方面，提供了一种通信方法，包括：会话管理功能网元获取接口标识；所述会话管理功能网元向第一网元发送用户面功能网元的地址和所述接口标识，所述接口标识用于所述第一网元确定所述接口标识对应的接口，所述用户面功能网元的地址和所述接口标识对应的接口用于所述第一网元控制所述用户面功能网元。
应理解，所述接口标识对应的接口是所述用户面功能网元新增的报文接口，包括：报文出口和/或报文入口。
根据本申请提供的方案，会话管理功能网元通过获取接口标识以及向第一网元发送用户面功能网元的地址和所述接口标识，能够实现第一网元通过用户面功能网元的地址和接口标识对应的接口控制所述用户面功能网元。同时，用户面功能网元能够基于会话管理功能网元和其他类型网元的不同配置隔离运行，并行处理同一个报文，从而实现多类型的控制器控制用户面功能网元。
结合第一方面，在第一方面的某些实现方式中，所述会话管理功能网元向所述用户面功能网元发送第一信息，所述第一信息用于指示所述用户面功能网元分配所述接口标识。
结合第一方面，在第一方面的某些实现方式中，所述会话管理功能网元获取接口标识，包括：所述会话管理功能网元从所述用户面功能网元接收所述接口标识。
结合第一方面，在第一方面的某些实现方式中，所述会话管理功能网元向所述用户面功能网元发送所述接口标识。
可选地，所述会话管理功能网元从所述用户面功能网元接收能力指示信息，所述能力指示信息用于指示所述用户面功能网元能被第一类型的网元控制，所述第一类型的网元为除会话管理功能类型的网元。
示例地，所述第一类型的网元可以包括：接入管理功能(Access and Mobility Management Function，AMF)、网络数据分析功能NWDAF、策略控制功能(policy control function，PCF)、群组管理功能(Group Management Function，GMF)、网络开放功能(Network Expsorue Function，NEF)、统一数据管理(Unified Data Management，UDM)、媒体功能(Media Function，MF)、网络注册功能(Network Repository Function，NRF)、认证服务器功能(Authentication Server Function，AUSF)、绑定支持功能(Binding Support Function，BSF)、网络数据分析(Network Data Analysis，NWDA)等不同类型的控制面功能(Control Plane Function，CPF)网元。
可选地，所述会话管理功能网元从所述第一网元接收请求消息，所述请求消息用于请求控制所述用户面功能网元。
示例地，所述请求消息包括以下至少一种信息：所述用户面功能网元的标识，所述用户面功能网元覆盖的服务区域，用户设备的会话标识。
第二方面，提供了一种通信方法，包括：用户面功能网元从第一网元接收与所述第一网元对应的报文检测规则和报文处理规则，所述第一网元为非会话管理功能类型的网元；所述用户面功能网元通过与所述第一网元对应的接口接收报文；所述用户面功能网元根据所述报文检测规则检测所述报文，以及根据所述报文处理规则处理所述报文。
根据本申请提供的方案，用户面功能网元通过从第一网元接收与所述第一网元对应的报文检测规则和报文处理规则，并根据该报文检测规则和报文处理规则分别对报文进行检测和处理，能够实现第一网元通过用户面功能网元的地址和接口标识对应的接口控制所述用户面功能网元。同时，用户面功能网元能够基于会话管理功能网元和其他类型网元的不同配置隔离运行，并行处理同一个报文，从而实现多类型的控制器控制用户面功能网元。
结合第二方面，在第二方面的某些实现方式中，所述用户面功能网元从会话管理功能网元接收第一信息，所述第一信息用于指示所述用户面功能网元分配所述接口的接口标识。
结合第二方面，在第二方面的某些实现方式中，所述用户面功能网元向所述会话管理功能网元发送所述接口的接口标识。
结合第二方面，在第二方面的某些实现方式中，所述用户面功能网元从所述会话管理功能网元接收所述接口的接口标识。
可选地，所述用户面功能网元向所述会话管理功能网元发送能力指示信息，所述能力指示信息用于指示所述用户面功能网元能被第一类型的网元控制，所述第一类型的网元为非会话管理功能类型的网元。
第三方面，提供了一种通信方法，包括：第一网元从会话管理功能网元接收用户面功 能网元的地址和接口标识；所述第一网元根据所述接口标识确定所述接口标识对应的接口；所述第一网元根据所述用户面功能网元的地址和所述接口标识对应的接口用于所述第一网元控制所述用户面功能网元；所述第一网元向所述用户面功能网元发送与所述第一网元对应的报文检测规则和报文处理规则，所述第一网元为非会话管理功能类型的网元。
根据本申请提供的方案，第一网元通过从会话管理功能网元接收用户面功能网元的地址和接口标识，并向所述用户面功能网元发送与所述第一网元对应的报文检测规则和报文处理规则，能够实现第一网元通过用户面功能网元的地址和接口标识对应的接口控制所述用户面功能网元。同时，用户面功能网元能够基于会话管理功能网元和其他类型网元的不同配置隔离运行，并行处理同一个报文，从而实现多类型的控制器控制用户面功能网元。
结合第三方面，在第三方面的某些实现方式中，所述第一网元向所述会话管理功能网元发送请求消息，所述请求消息用于请求所述第一网元请求控制所述用户面功能网元。
示例地，所述请求消息包括以下至少一种信息：所述用户面功能网元的标识，所述用户面功能网元覆盖的服务区域，用户设备的会话标识。
第四方面，提供了一种网络设备，包括：处理单元，用于获取接口标识；收发单元，用于向第一网元发送用户面功能网元的地址和所述接口标识，所述用户面功能网元的地址和所述接口标识用于所述第一网元通过接口标识对应的接口控制所述用户面功能网元。
结合第四方面，在第四方面的某些实现方式中，所述收发单元，还用于向所述用户面功能网元发送第一信息，所述第一信息用于指示所述用户面功能网元分配所述接口标识。
结合第四方面，在第四方面的某些实现方式中，所述处理单元用于通过所述收发单元从所述用户面功能网元接收所述接口标识。
结合第四方面，在第四方面的某些实现方式中，所述收发单元，还用于向所述用户面功能网元发送所述接口标识。
可选地，所述收发单元，还用于从所述用户面功能网元接收能力指示信息，所述能力指示信息用于指示所述用户面功能网元能被第一类型的网元控制，所述第一类型的网元为非会话管理功能类型的网元。
可选地，所述收发单元，还用于从所述第一网元接收请求消息，所述请求消息用于请求控制所述用户面功能网元。
示例地，所述请求消息包括以下至少一种信息：所述用户面功能网元的标识，所述用户面功能网元覆盖的服务区域，用户设备的会话标识。
第五方面，提供了一种网络设备，包括：收发单元，用于从第一网元接收与所述第一网元对应的报文检测规则和报文处理规则，所述第一网元为非会话管理功能类型的网元；所述收发单元，还用于通过与所述第一网元对应的接口接收报文；处理单元，用根据所述报文检测规则检测所述报文，以及根据所述报文处理规则处理所述报文。
结合第五方面，在第五方面的某些实现方式中，所述收发单元，还用于从会话管理功能网元接收第一信息，所述第一信息用于指示所述用户面功能网元分配所述接口的接口标识。
结合第五方面，在第五方面的某些实现方式中，所述收发单元，还用于向所述会话管理功能网元发送所述接口的接口标识。
结合第五方面，在第五方面的某些实现方式中，所述收发单元，还用于从所述会话管 理功能网元接收所述接口的接口标识。
可选地，所述收发单元，还用于向所述会话管理功能网元发送能力指示信息，所述能力指示信息用于指示所述用户面功能网元能被第一类型的网元控制，所述第一类型的网元为非会话管理功能类型的网元。
第六方面，提供了一种网络设备，包括：收发单元，用于从会话管理功能网元接收用户面功能网元的地址和接口标识；处理单元，用于根据所述接口标识确定所述接口标识对应的接口；所述处理单元，还用于根据所述用户面功能网元的地址和所述接口标识控制所述用户面功能网元；所述收发单元，还用于向所述用户面功能网元发送与所述第一网元对应的报文检测规则和报文处理规则，所述第一网元为非会话管理功能类型的网元。
结合第六方面，在第六方面的某些实现方式中，所述收发单元，还用于向所述会话管理功能网元发送请求消息，所述请求消息用于请求所述第一网元请求控制所述用户面功能网元。
示例地，所述请求消息包括以下至少一种信息：所述用户面功能网元的标识，所述用户面功能网元覆盖的服务区域，用户设备的会话标识。
第七方面，提供了一种网络设备，包括，收发器，处理器，存储器，该处理器用于控制收发器收发信号，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该网络设备执行上述第一方面或第一方面中任一种可能实现方式中的方法，或者第二方面或第二方面中任一种可能实现方式中的方法，或者第三方面或第三方面中任一种可能实现方式中的方法。
可选地，所述处理器为一个或多个，所述存储器为一个或多个。
可选地，所述存储器可以与所述处理器集成在一起，或者所述存储器与处理器分离设置。
可选地，该网络设备还包括，发射机(发射器)和接收机(接收器)。
第八方面，提供了一种通信装置，包括：用于实现第一方面或第一方面任一种可能实现方式中的方法的单元；或者用于实现第二方面或第二方面任一种可能实现方式中的方法；或者用于实现第三方面或第三方面任一种可能实现方式中的方法。
第九方面，提供了一种通信***，包括：网络设备，用于执行如上述第一方面或第一方面任一种可能实现方式中的方法；或者用于执行如上述第二方面或第二方面任一种可能实现方式中的方法；或者用于执行如上述第三方面或第三方面任一种可能实现方式中的方法。
第十方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序或代码，所述计算机程序或代码在计算机上运行时，使得所述计算机执行上述第一方面或第一方面任一种可能实现方式中的方法，第二方面或第二方面任一种可能实现方式中的方法，以及第三方面或第三方面任一种可能实现方式中的方法。
第十一方面，提供了一种芯片，包括至少一个处理器，所述至少一个处理器与存储器耦合，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得安装有该芯片***的网络设备执行上述第一方面或第一方面任一种可能实现方式中的方法，第二方面或第二方面任一种可能实现方式中的方法，以及第三方面或第三方面任一种可能实现方式中的方法。
其中，该芯片可以包括用于发送信息或数据的输入电路或者接口，以及用于接收信息或数据的输出电路或者接口。
第十二方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被网络设备运行时，使得所述网络设备执行上述第一方面或第一方面任一种可能实现方式中的方法，第二方面或第二方面任一种可能实现方式中的方法，以及第三方面或第三方面任一种可能实现方式中的方法。
根据本申请实施例的方案，UPF能够实现非SMF类型的其他类型的控制面网元控制UPF，而且UPF能够基于SMF网元和其他网元的不同配置隔离运行，并行处理同一个报文，从而实现多类型的控制器控制同一UPF。
附图说明
图1是本申请的通信***的一例的示意图。
图2是本申请的通信场景的一例的示意图。
图3是适用本申请的通信方法的一例示意图。
图4是适用本申请的报文处理逻辑的一例示意图。
图5是适用本申请的通信方法的另一例示意图。
图6是适用本申请的通信方法的又一例示意图。
图7是适用本申请的通信装置的一例示意图。
图8是适用本申请的通信装置的另一例示意图。
图9是适用本申请的通信装置的又一例示意图
图10是适用本申请的网络设备的一例示意图。
图11是适用本申请的网络设备的另一例示意图。
图12是适用本申请的网络设备的又一例示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信***，例如：全球移动通讯(Global System of Mobile communication，GSM)***、码分多址(Code Division Multiple Access，CDMA)***、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)***、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)***、LTE频分双工(Frequency Division Duplex，FDD)***、LTE时分双工(Time Division Duplex，TDD)、通用移动通信***(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信***、5G***或新无线(New Radio，NR),也可以扩展到类似的无线通信***中，如无线保真(wireless-fidelity，WiFi)，全球微波互联接入(Worldwide Interoperability for Microwave Access，WIMAX)，以及第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)相关的蜂窝***等。
通常来说，传统的通信***支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信***将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device， D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车联网(Vehicle To Everything，V2X)通信，例如，车到车(Vehicle to Vehicle，V2V)通信、车到基础设施(Vehicle to Infrastructure，V2I)通信，车到行人(Vehicle to Pedestrian，V2P)通信，车道网络(Vehicle to Network，V2N)通信。
图1是应用于本申请实施例的网络架构，该网络架构中可能涉及的各个网元分别进行说明。
1、终端设备110：可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的终端，移动台(mobile station，MS)，终端(terminal)，用户设备(user equipment，UE)，软终端等等。例如，水表、电表、传感器等。
2、(无线)接入网络(Radio Access Network，(R)AN)网元120：用于为特定区域的授权终端设备提供入网功能，并能够根据终端设备的级别，业务的需求等使用不同质量的传输隧道。
(R)AN网元能够管理无线资源，为终端设备提供接入服务，进而完成控制信号和终端设备数据在终端设备和核心网之间的转发，(R)AN网元也可以理解为传统网络中的基站。
需要说明的是，上述“网元”也可以称为实体、软件、设备、装置或模块等，本申请并未特别限定。并且，在本申请中，为了便于理解和说明，在对部分描述中省略“网元”这一描述，例如，将(R)AN网元简称(R)AN，此情况下，该“(R)AN网元”应理解为(R)AN网元网元或(R)AN实体或(R)AN AN软件，以下，省略对相同或相似情况的说明。
3、用户面功能网元130：用于数据包分组路由和转发以及用户面数据的服务质量(Quality of Service，QoS)处理等。
在5G通信***中，该用户面网元可以是用户面功能UPF网元。在未来通信***中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。
4、数据网络网元140：用于提供传输数据的网络。
在5G通信***中，该数据网络网元可以是数据网络(Data Network，DN)网元。在未来通信***中，数据网络网元仍可以是DN网元，或者，还可以有其它的名称，本申请不做限定。
5、接入管理网元150：主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(Mobility Management Entity，MME)功能中除会话管理之外的其它功能，例如，合法监听以及接入授权/鉴权等功能。
在5G通信***中，该接入管理网元可以是接入管理功能AMF网元。在未来通信***中，接入管理网元仍可以是AMF网元，或者，还可以有其它的名称，本申请不做限定。
6、会话管理网元160：主要用于会话管理、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户面功能、策略控制和收费功能接口的终结点以及下行数据通知等。
在5G通信***中，该会话管理网元可以是会话管理功能SMF网元。在未来通信***中，会话管理网元仍可以是SMF网元，或者，还可以有其它的名称，本申请不做限定。
7、策略控制网元170：用于指导网络行为的统一策略框架，为控制面功能网元(例如AMF，SMF网元等)提供策略规则信息等。
在4G通信***中，该策略控制网元可以是策略和计费规则功能(Policy and Charging Rules Function，PCRF)网元。在5G通信***中，该策略控制网元可以是策略控制功能PCF网元。在未来通信***中，策略控制网元仍可以是PCF网元，或者，还可以有其它的名称，本申请不做限定。
8、网络存储功能网元180：用于维护网络中所有网络功能服务的实时信息。
在5G通信***中，该网络存储网元可以是网络注册功能NRF网元。在未来通信***中，网络存储网元仍可以是NRF网元，或者，还可以有其它的名称，本申请不做限定。
9、应用网元190：用于进行应用影响的数据路由，接入网络开放功能网元，与策略框架交互进行策略控制等。
在5G通信***中，该应用网元可以是应用功能(Application Function，AF)网元。在未来通信***中，应用网元仍可以是AF网元，或者，还可以有其它的名称，本申请不做限定。
10、数据管理网元1100：用于处理终端设备标识，接入鉴权，注册以及移动性管理等。
在5G通信***中，该数据管理网元可以是统一数据管理UDM网元。在未来通信***中，统一数据管理仍可以是UDM网元，或者，还可以有其它的名称，本申请不做限定。
11、群组管理网元1200：用于负责移动网络局域网(local area network，LAN)，例如，5G LAN的群组(具体地说，是终端设备群组)的创建和成员管理。
在5G通信***中，群组管理网元也可以为群组管理功能GMF网元。
需要说明的是，上述“网元”也可以称为实体、设备、装置或模块等，本申请并未特别限定。并且，在本申请中，为了便于理解和说明，在对部分描述中省略“网元”这一描述，例如，将SMF网元简称SMF，此情况下，该“SMF”应理解为SMF网元或SMF实体，以下，省略对相同或相似情况的说明。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。
在该网络架构中，N2接口为RAN网元20和AMF网元160的参考点，用于非接入层(non-access stratum，NAS)消息的发送等；N3接口为RAN网元120和UPF网元130之间的参考点，用于传输用户面的数据等；N4接口为SMF网元170和UPF网元130之间的参考点，用于传输例如N3连接的隧道标识信息，数据缓存指示信息，以及下行数据通知消息等信息；N6接口为UPF网元130和DN网元140之间的参考点，用于传输用户面的数据；N9接口为UPF网元130和另一个UPF网元之间的参考点等。
应理解，实现其他类型的控制面网元控制UPF的前提还需要二者建立连接，比如建立设备粒度的连接，或者建立设备之间的连接，或者利用服务化接口、空口实现二者的连接。
需要说明的是，SBA的范围限于核心网的控制面网元，不包括用户面功能UPF网元。而且，UPF支持的接口N3，N9，N6，N4都不是服务化接口。从上述架构图中可见，与UPF可以连接的网元设备有SMF，RAN，DN和另一个UPF。
应理解，以上列举的通信***包括的各网元仅为示例性说明，本申请并未限定于此，例如，还可以包括但不限于：
认证服务网元：用于鉴权服务、产生密钥实现对终端设备的双向鉴权，支持统一的鉴权框架，可以是认证服务器功能AUSF网元；
网络开放功能网元：用于安全的开放3GPP网络功能提供的业务和能力，有内部开放，或者开放给第三方等，可以是网络开放功能网元NEF；
网络切片选择功能网元：用于为用户设备选择一组网络切片实例、确定允许的网络切片选择辅助信息(Network Slice Selection Assistance Information，NSSAI)和确定可以服务用户设备的AMF集，可以是切片选择功能网元(Network Slice Selection Function，NSSF)；
绑定支持功能BSF网元：用于查找会话所关联的PCF；
网络数据分析NWDA网元：用于收集与存储来自于终端设备，RAN网元，以及其他网络实体(例如，AMF网元)的信息，并对这些信息进行分析，以及生成关于用户的上下文信息(可以认为是应用层的信息)，并对此应用层的信息进行分发等。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的从服务化架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
例如，在某些网络架构中，AMF、SMF、PCF、GMF以及UDM等网络功能实体都称为网络功能(Network Function，NF)网元；或者，在另一些网络架构中，AMF、SMF、PCF、GMF及UDM等网元的集合都可以称为控制面功能CPF网元。
图2示出了本申请涉及的另一例架构的示意性框图。如图2所示，SMF和其他网元分别通过配置参数A和配置参数B控制UPF，UPF分别执行配置参数A和配置参数B中规定的动作，即主要是用户面报文处理。
应理解，其他网元可以是5G网络架构中除SMF以外的其他类型的控制面网元，或者随着5G架构的演进引入的其他新网元。
还应理解，在本申请技术方案中，UPF基于配置参数A对于报文的处理与基于配置参数B对于报文的处理是隔离运行的，即对于不同的控制面网元控制UPF，UPF有不同的报文接口。另外，配置参数A和配置参数B中用于报文处理的规则，可以相同，也可以不同，本申请对此不做限定。
需要说明的是，配置参数A和配置参数B中均可以包括以下一种：报文检测规则(Packet Detection Rule，PDR)，服务质量执行规则(Quality of Service Enforcement Rule，QER)，用量上报规则(Usage Reporting Rule，URR)，多接入规则(Multi-Access Rule，MAR)和转发动作规则(Forwarding Action Rule，FAR)，这五类规则是UPF用于报文处理的规则，均来自于SMF的配置。在UPF内部处理报文的逻辑中，PDR和FAR是必需的报文处理规则，其他是可选的。
示例地，PDR用于指示当收到来自外部的报文，UPF使用PDR去匹配报文中的信息，如利用报文头部的IP地址等。只有当某个PDR与报文的信息匹配时，才会根据配置参数中规定的动作继续处理该报文，否则就丢弃该报文。
FAR用于指示UPF如何处理报文的动作，已经定义的动作包括：转发、缓存、丢弃、复制等等。
应理解，一个FAR关联于一个PDR，即如果报文的信息匹配中了这个PDR，则执行该PDR关联的FAR。
为了便于理解本申请的技术方案，下面简单介绍SMF通过N4接口控制UPF的方法：
(1)建立设备粒度的连接；
一种可能的实现方式包括：SMF向UPF发起N4关联建立请求；UPF向SMF发送N4关联建立响应。
应理解，设备粒度的连接建立是SMF和UPF之间建立通信的第一步，该步骤用于SMF获取UPF的标识、能力、负荷状态等信息。
(2)SMF为UPF配置会话粒度的报文处理规则。
一种可能的实现方式包括：SMF触发建立分组数据单元(Packet Data Unit，PDU)会话或重定位UPF；SMF向UPF发起N4会话建立请求；UPF向SMF发送N4会话建立响应；SMF与其他网络功能的交互。
应理解，只有在建立设备粒度的连接后，SMF才可以为UPF配置会话粒度的报文处理规则。这里需要说明的是，SMF控制UPF的协议是报文转发控制(Packet Forwarding Control Protocol，PFCP)协议。
关于其他类型的控制面网元控制UPF，一般是通过SMF中转，实现对UPF的控制，即SMF会将其他网元的控制请求与自身的业务逻辑相结合，以实现对UPF的配置。
应理解，在UPF上安装的报文检测规则PDR可以有多种，比如：IP 5元组，包括源IP地址、目的IP地址、协议号、源端口、目的端口。示例地，有一种报文检测规则与应用服务器(AF)关联，比如：提供电子商务的服务器等，这种类型的报文检测规则被称为数据包流检测(Packet Flow Detection，PFD)。AF希望将PFD配置在UPF上，用于识别与该服务器AF相关的报文。但是，目前的配置过程是AF先将该PFD发送至SMF，然后SMF将该PFD配置到UPF，以使得服务器AF可以控制该UPF。一种可能的实现方式包括：SMF在接收AF配置请求时，触发以提供或删除属于一个应用程序ID的PFD集；SMF向UPF发送PFD管理请求；UPF向SMF发送PFD管理响应。
应理解，以上控制面网元控制UPF的过程仅为示例性说明，本申请并未限定于此，其他能够实现控制UPF的方法及过程均落入本申请的保护范围内。
本申请实施例结合核心网设备描述了各个实施例，其中，核心网的功能主要是提供用户连接、对用户的管理以及对业务完成承载，作为承载网络提供到外部网络的接口。用户连接的建立包括移动性管理(Mobile Management，MM)、呼叫管理(Connection Management，CM)、交换/路由、录音通知等功能。用户管理包括用户的描述、服务质量QoS、用户通信记录(accounting)、虚拟归属环境(Virtual Home Environment，VHE)和安全性(由鉴权中心提供相应的安全性措施包含了对移动业务的安全性管理和对外部网络访问的安全性处理)。承载连接(access)包括到外部的公共交换电话网络(Public Switched Telephone Network，PSTN)、外部电路数据网和分组数据网、互联网络(internet)和内联网(intranets)、以及移动网络自身的手机短信服务(Short Message Service，SMS)服务器等等。
核心网可以提供的基本业务包括移动办公、电子商务、通信、娱乐性业务、旅行和基于位置的服务、遥感业务(telemetry)、简单消息传递业务(监视控制)等等。
作为示例而非限定，核心网设备可以包括：接入和移动性管理功能AMF、会话管理功能SMF、策略控制功能PCF、用户面功能UPF等功能单元，这些功能单元可以独立工 作，也可以组合在一起实现某些控制功能，如：AMF、SMF和PCF可以组合在一起作为管理设备，用于完成终端设备的接入鉴权、安全加密、位置注册等接入控制和移动性管理功能，以及用户面传输路径的建立、释放和更改等会话管理功能，以及分析一些切片(slice)相关的数据(如拥塞)、终端设备相关的数据的功能。
在目前的SBA网络架构中，只有SMF可以控制UPF。但是随着5G的演进，UPF的功能也逐渐强大，比如：它可以做用户业务状态分析，包括：流量是否异常、抖动是否厉害、时延是否满足业务体验，等等。这些功能对于其他类型的控制面网元来说是不能直接从UPF获取的，而是需要从SMF请求再间接获得。无论是信令数量还是数据实时性都不好。因此，实现其他类型的控制面网元设备控制UPF是很有必要的。
本申请实施例应用于包括至少一个转发设备和多个核心网设备的通信***中，下面结合附图对本申请实施例中实现其他网元控制UPF的方式进行详细说明。
作为示例而非限定，本申请实施例可以包括实现SMF控制UPF、PCF控制UPF、NWDAF控制UPF等。其中，UPF主要提供用户平面的业务处理功能，包括业务路由、包转发、锚定功能、服务质量QoS映射和执行、上行链路的标识识别并路由到数据网络、下行包缓存和下行链路数据到达的通知触发、与外部数据网络连接等。
为了方便说明，本申请以装置SMF、UPF为例，对非SMF类型的控制面网元控制UPF的方法进行说明。本申请后续所描述的SMF均可替换为会话管理功能网元，UPF均可替换为用户面功能网元。对于装置为SMF内的芯片或为UPF实体内的芯片的实现方法，可参考装置分别为SMF实体、UPF实体的具体说明，不再重复介绍。
图3是适用本申请的通信方法的一例示意图。如图3所示，实现步骤300包括：
S310，会话管理功能网元获取接口标识。
作为示例而非限定，在一种可能的实现方式中，获取接口标识可以包括：会话管理功能网元自行确定接口标识，该接口标识与第一网元对应。也就是说，会话管理功能网元基于设备粒度的通信建立，为用户面功能网元分配接口标识，并通过后面的步骤将接口标识发送给该用户面功能网元，用于告知用户面功能网元配置与第一网元对应的接口。
需要说明的是，该第一网元是指非会话管理功能类型的网元。例如，第一网元可以是接入管理功能AMF、网络数据分析功能NWDAF、策略控制功能PCF、群组管理功能GMF、网络开放功能NEF、统一数据管理UDM、媒体功能MF、网络注册功能NRF、认证服务器功能AUSF、绑定支持功能BSF、网络数据分析NWDA等不同类型的控制面功能CPF网元。
应理解，该接口标识对应的接口是用户面功能网元的新增报文接口，包括报文出口，和/或报文入口。
作为示例而非限定，在另一种可能的实现方式中，获取接口标识还可以包括：会话管理功能网元从用户面功能网元接收接口标识，即用户面功能网元自行分配接口标识，并将该接口标识发送给会话功能管理网元，该接口标识与第一网元对应。
在另一种可能的实现方式中，会话管理功能网元可以向用户面功能网元发送第一信息，该第一信息用于指示该用户面功能网元分配上述接口标识，即新增报文接口，该接口与第一网元对应。
可选地，该第一信息可以包括以下一种：第一网元的标识、或者第一网元的地址；码 字(codeword)、第一网元的业务需求、业务类型；或者，报文数据大小、报文是否加密等。例如，第一网元的地址可以包括第一网元的IP地址和媒体访问控制地址(Media Access Control Address，MAC)。会话管理功能网元可以根据该第一信息确定第一网元可以控制的用户面功能网元。其中，码字可以作为一种密码，用于多设备之间的相互检测。
在一种可能的实现方式中，用户面功能网元可以向会话管理功能网元发送能力指示信息，该能力指示信息用于指示该用户面功能网元能被一个或多个第一类型的网元控制。需要说明的是，该第一类型的网元为非会话管理功能类型的网元。
示例地，该能力指示信息可以包括：用户面功能网元将计费信息、时间等上报给除SMF类型之外的设备，如：计费功能(Charging Function，CHF)网元；或者用户面功能网元将用户业务状态分析上报给除SMF类型之外的设备，如：网络数据分析功能NWDAF网元等。例如，用户业务状态分析包括：流量是否异常、网络拥塞导致的延迟变化的程度是否厉害、时延是否满足业务体验等功能中的至少一项。换句话说，该能力指示信息可以指示用户面功能网元能够向其上报的设备的具体类型。
在另一种可能的实现方式中，第一网元可以向会话管理功能网元发送请求消息，该请求消息用于请求控制该用户面功能网元。
应理解，第一网元可以基于业务的覆盖区域，UE的驻留区域，第一网元的管辖范围中的至少一项选择会话管理功能网元。
可选地，该请求消息可以包括以下至少一种：用户面功能网元的标识(UPF ID)，用户面功能网元覆盖的服务区域(service area)，用户设备的会话标识(UE session ID)。
应理解，当第一网元发送的请求消息中包括UPF ID，那么说明第一网元明确告知会话管理功能网元想控制的用户面功能网元是哪一个，此时会话管理功能网元将对应的用户面功能网元找出即可。
当第一网元发送的请求消息中包括用户面功能网元覆盖的服务区域，那么对于第一网元来说，它可以不知道与该第一网元对应的用户面功能网元是哪一个，此时会话管理功能网元可以在该服务区域内找到一个或多个用户面功能网元，并选择其中一个用户面网元被第一网元控制即可。
当第一网元发送的请求消息中包括UE session ID，那么说明第一网元希望控制某一用户设备的特定会话，此时会话管理功能网元将与该特定会话对应的用户面管理网元找出即可。
需要说明的是，UE session ID，也称为分组数据单元PDU会话的标识，或者session ID、会话标识，用于标记一个用户设备的会话，该用户设备的会话由一个或者多个用户面功能网元负责，以实现会话的用户面连接。因此UE session ID可以关联到一个或者多个用户面功能网元。
S320，会话管理功能网元向第一网元发送用户面功能网元的地址和接口标识，相应的，第一网元从会话管理功能网元接收用户面功能网元的地址和接口标识。
其中，该接口标识用于第一网元确定该接口标识对应的接口，该用户面功能网元的地址和接口标识对应的接口用于第一网元控制该用户面功能网元。
应理解，通过向第一网元发送用户面管理网元的地址信息，使得用户面管理网元能够灵活地和第一网元设备交互，不需要通过会话管理功能网元转发，减少了信令的转发时延。
可选地，该会话管理功能网元还可以向第一网元发送用户面管理网元的标识(UPF ID)、码字(codeword)中的至少一项。
S330，第一网元向用户面管理网元发送报文检测规则PDR和报文处理规则(Packet Handle Rule，PHR)，相应的，用户面功能网元从第一网元接收报文检测规则PDR和报文处理规则PHR。
应理解，这里报文处理规则PHR可以包括服务质量执行规则QER，用量上报规则URR，多接入规则MAR和转发动作规则FAR等，本申请对报文处理规则的种类和数量不作具体限定。
可选地，该第一网元还可以向用户面管理网元发送码字。其中，该码字可以作为一种密码，用于多设备之间的相互检测。
S340，用户面功能网元接收下行/上行报文。
示例地，用户设备UE向用户面功能网元发送上行报文，和/或数据网络DN向用户面功能网元发送下行报文；相应地，该用户面功能网元从用户设备UE接收上行报文，和/或从数据网络DN接收下行报文。
应理解，该上行报文/下行报文可以通过无线资源控制(Radio Resource Control，RRC)信令，媒体访问控制管理单元(Media Access Control，Control Element，MAC CE)，物理层信令(例如：PDCCH)中的至少一种方式传递。
S350，用户面功能网元根据报文检测规则PDR检测上行/下行报文，以及根据报文处理规则PHR处理上行/下行报文。
应理解，用户面功能网元在对报文进行检测和处理之前，应该在报文入口安装报文检测规则，同时在报文出口安装报文处理规则。图4示出了用户面功能网元收到来自外部的报文(packet in)时内部的处理逻辑的一例示意图。如图4所示，用户面功能网元可以包括两层接口，例如，第一层接口和第二层接口，外部的报文#1首先通过第一层接口，然后用户面功能网元会复制该报文#1至第二层接口处。假设此时用户面功能网元的第二层接口有两对报文出入口，报文出入口#A用于会话功能管理网元(例如：SMF网元)控制该用户面功能网元，报文出入口#B用于第一网元(例如：NWDAF网元)控制该用户面功能网元。即用户面管理网元将报文#1分别复制到报文入口#A和报文入口#B处，并根据报文入口#A的PDR#A检测该报文#1，以及根据报文入口#B的PDR#B检测该报文#1，例如利用报文头部的IP地址等。
需要特别说明的是，用户面功能网元根据报文处理规则PDR#A和报文处理规则PDR#B分别检测报文#1时，是从两个不同的入口检测的，即报文入口#A和报文入口#B，这两个报文入口是隔离的，用户面功能网元通过这两个报文入口并行处理同一报文#1。相应的，报文出口#A和报文出口#B也是隔离的。也就是说，在用户面功能网元上安装的每个控制面网元都是有独立的报文接口的，用户面功能网元隔离SMF网元和NWDAF网元分别配置的规则参数PDR#A和PDR#B。另外，报文检测规则#A和报文检测规则#B可以相同，也可以不同，本申请对此不作任何限定。
应理解，只有当某个PDR与报文的信息匹配中时，才会根据配置参数中规定的动作继续处理该报文，否则就丢弃该报文。假设报文检测规则PDR#B与该报文#1匹配中，说明报文#1是与NWDAF网元对应的，此时，用户面功能网元将报文#1执行相应地报文处 理规则PHR#B，例如转发，复制等，以此实现NWDAF网元控制该用户面管理功能网元。
需要说明的是，上述报文处理规则PHR可以包括MAR、FAR、QER、URR等，报文入口和报文出口可以同时存在，也可以单独存在，本申请对此不作限定。
基于上述可能的实现方式，NWDAF网元通过对报文#1执行报文检测规则#B和报文处理规则#B，使得NWDAF网元可以控制用户面功能网元。而且，在报文处理过程中，用户面功能网元能够分别基于与SMF网元对应的报文检测规则#A和与NWDAF网元对应的报文检测规则#B，并行处理同一个数据报文#1，使得用户面功能网元隔离SMF网元和NWDAF网元的不同配置，进而实现不同类型的控制器控制同一个用户面功能网元。
图5是本申请一实施例的核心网中控制面网元#A控制UPF#A方法的示意图。作为示例而非限定，以UPF#A自行确定与网元#A对应的接口标识为例，其中，UPF#A作为转发设备，SMF#A作为控制设备，网元#A可以是核心网中计费功能网元CHF、策略控制功能网元PCF、NWDAF等其它控制面网元设备。如图5所示，实现步骤500包括：
S510，UPF#A(即，用户面功能网元的一例)向SMF#A(即，会话管理功能网元的一例)发送能力指示信息#A，相应的，SMF#A从UPF#A接收能力指示信息#A。
其中，该能力指示信息#A用于指示该UPF#A可以被其他类型的网元(例如，网元#A)控制。这里网元#A为非会话管理功能类型网元。
示例地，该网元#A的类型可以包括：AMF、NWDAF、PCF、GMF、NEF、UDM、MF、NRF、AUSF、BSF、NWDA等不同类型的控制面功能CPF网元。
应理解，该能力指示信息可以包括：用户面功能网元将计费信息、时间等上报给除SMF类型之外的设备，如：计费功能CHF网元；或者用户面功能网元将用户业务状态分析上报给除SMF类型之外的设备，如：网络数据分析功能NWDAF网元等。例如，用户业务状态分析，包括：流量是否异常、网络拥塞导致的延迟变化的程度是否厉害、时延是否满足业务体验等功能中的至少一项。
S520，网元#A(即，第一网元的一例)向SMF#A发送请求消息#A，相应的，SMF#A从网元#A接收请求消息#A。其中，该请求消息#A用于网元#A请求控制UPF#A。
应理解，网元#A可以基于业务的覆盖区域，UE的驻留区域，网元#A的管辖范围中的至少一项选择SMF#A。
可选地，请求消息#A可以包括以下至少一种：UPF#A的标识信息(UPF ID)、UPF#A覆盖的服务区域(service area)、用户设备的会话标识(UE session ID)。
S530，SMF#A根据接收的请求消息#A确定用于网元#A控制的UPF#A。
应理解，当网元#A发送的请求消息#A中包括UPF ID，那么说明网元#A明确告知SMF#A想控制UPF#A，此时SMF#A将对应的UPF#A找出即可。
当网元#A发送的请求消息#A中包括UPF#A覆盖的服务区域，那么对于网元#A来说，它可以不知道与该网元#A对应的UPF网元是哪一个，此时SMF#A可以在该服务区域内找到一个或多个UPF网元，并选择其中一个UPF#A网元被网元#A控制即可。
当网元#A发送的请求消息#A中包括UE session ID，那么说明网元#A希望控制某一用户设备的特定会话，此时SMF#A将与该特定会话对应的UPF#A网元找出即可。
需要说明的是，UE session ID，也称为分组数据单元PDU会话的标识，或者session ID、会话标识，用于标记一个用户设备的会话，该用户设备的会话由一个或者多个用户面功能 网元负责，以实现会话的用户面连接。因此UE session ID可以关联到一个或者多个UPF。
S540，SMF#A向UPF#A发送第一信息#A，相应的，UPF#A从SMF#A接收第一信息#A。其中，该第一信息#A用于指示UPF#A分配与网元#A对应的接口标识，即新增报文接口，该报文接口与网元#A对应。也就是说，此时UPF#A可以有两套报文接口，一套用于SMF#A，另一套用于网元#A。
可选地，该第一信息#A可以包括以下一种：网元#A的标识、或者网元#A的地址；码字(codeword)、网元#A的业务需求、业务类型；或者，报文数据大小、报文是否加密等。例如：网元#A的地址可以包括网元#A的IP地址和媒体访问控制地址MAC。SMF#A可以根据该第一信息#A为网元#A确定可以控制的UPF#A。其中，码字可以作为一种密码，用于多设备之间的相互检测。
S541，UPF#A确定与网元#A对应的接口标识，并向SMF#A发送该接口标识，相应的，SMF#A从UPF#A接收接口标识。其中，该接口标识与网元#A对应。
S550，SMF#A向网元#A发送UPF#A的地址和接口标识，相应的，网元#A从SMF#A接收UPF#A的地址和接口标识。
其中，该接口标识用于网元#A确定该接口标识对应的接口，该UPF#A的地址和接口标识对应的接口用于网元#A控制该UPF#A网元。
应理解，该接口标识对应的接口是UPF#A网元的新增报文接口，包括报文出口，和/或报文入口。SMF#A通过向网元#A发送UPF#A的地址信息，使得UPF#A能够灵活地和网元#A交互，可以不通过SMF#A转发，减少了信令的转发时延。
可选地，该SMF#A还可以向网元#A发送UPF#A的标识(UPF ID)，码字(codeword)中的至少一项。
在此基础上，UPF#A与网元#A均已获知接口标识信息、UPF#A与网元#A的标识信息。
S560，网元#A向UPF#A发送与网元#A对应的报文检测规则PDR和报文处理规则PHR，相应的，UPF#A从网元#A接收报文检测规则PDR和报文处理规则PHR。
应理解，这里报文处理规则PHR可以包括服务质量执行规则QER，用量上报规则URR，多接入规则MAR和转发动作规则FAR等，本申请对报文处理规则的种类和数量不作具体限定。
可选地，该网元#A还可以向UPF#A发送码字。其中，该码字可以作为一种密码，用于多设备之间的相互检测。
S570，UPF#A在新增报文入口安装报文检测规则PDR，和/或在新增报文出口安装报文处理规则PHR。其中，该新增报文出口和/或新增报文入口均与网元#A对应。
应理解，报文检测规则PDR与新增的报文入口对应，即该PDR用于指示UPF#A检测与网元#A关联的报文信息，例如，网元#A希望识别与某个特定用户的IP地址相关的报文，那么UPF#A匹配中与该特定用户的IP地址相关的报文即可。类似地，报文处理规则PHR与新增的报文出口对应，即该PHR用于指示UPF#A将处理后的报文发给哪个相应的控制器。可选地，PHR还可以包括其他额外的处理信息，比如：用于指示UPF#A以何种粒度的方式进行信息统计等。
S581，UE通过与网元#A对应的接口向UPF#A发送上行报文，相应的，UPF#A通过 与网元#A对应的接口从用户设备UE接收上行数据报文。
S582，数据网络DN通过与网元#A对应的接口向UPF#A发送下行数据报文，相应的，UPF#A通过与网元#A对应的接口从数据网络DN接收下行数据报文。
应理解，步骤S581和S582中的上行报文和/或下行报文可以通过无线资源控制RRC信令，媒体访问控制管理单元MAC CE，物理层信令中至少一种方式传递。
S590，UPF#A根据报文检测规则PDR检测上行报文和/或下行报文，以及根据报文处理规则PHR处理上行报文和/或下行报文。
相关上行/下行报文的检测和处理过程在上述图4中已经详细说明，为了简洁，此处不再赘述。
应理解，只有当某个报文检测规则PDR与上行/下行报文的信息匹配中时，才会继续执行相应的报文处理规则，否则就丢弃该上行/下行报文。需要说明的是，报文入口和报文出口可以同时存在，也可以单独存在，本申请对此不作限定。
应理解，在上述实施例中，报文接口的数量取决于请求控制UPF#A的控制器的数量，即一个控制器对应UPF#A的一对报文接口。
根据上述实施方式，通过SMF#A网元指示UPF#A分配与网元#A对应的新增报文接口，UPF#A向SMF#A发送新增的接口标识，使得非SM#A类型的其他类型的控制面网元可以控制该UPF#A。另外，UPF#A能够将SMF#A网元和网元#A的不同配置参数隔离，实现并行处理同一个数据报文，进而实现不同类型的多控制器控制同一UPF#A。
图6是本申请一实施例的核心网中控制面网元#a控制UPF#a方法的示意图。作为示例而非限定，该实现方式以SMF#a为UPF#a分配接口标识为例。与上述步骤500的主要区别在于，SMF#a可以不向UPF#a发送第一信息，且SMF#a可以自行确定与网元#a对应的接口标识信息，并向UPF#a发送该接口标识。如图6所示，实现步骤600包括：
S610，UPF#a(即，用户面功能网元的一例)向SMF#a(即，会话管理功能网元的一例)发送能力指示信息#a，相应的，SMF#a从UPF#a接收能力指示信息#a。
S620，网元#a(即，第一网元的一例)向SMF#a发送请求消息#a，相应的，SMF#a从网元#a接收请求消息#a。
S630，SMF#a根据请求消息#a确定用于网元#a控制的UPF#a。
需要说明的是，步骤S610至S630可以参考上述步骤S510至S530的描述，为了简洁，此处不再赘述。
S640，SMF#a确定与网元#a对应的接口标识，即SMF#a为UPF#a分配报文新增接口标识，该接口标识用于网元#a确定与接口标识对应的接口，该新增报文接口用于网元#a控制UPF#a。其中，该新增的报文接口标识与网元#a对应。
应理解，SMF#a确定与网元#a对应的接口标识是基于SMF#a和UPF#a之间的设备粒度连接，所以SMF#a对于UPF#a的报文接口信息(例如，分配报文接口的数量信息、标识信息等)是确定的，SMF#a可以实现为UPF#a分配新增报文接口标识。
S650，SMF#a向UPF#a发送接口标识，相应的，UPF#a从UPF#a接收接口标识，其中，该接口标识与网元#a对应。
S660，SMF#a向网元#a发送UPF#a的地址和接口标识，相应的，网元#a从SMF#a接收UPF#a的地址和接口标识。
S670，网元#a向UPF#a发送与网元#a对应的报文检测规则PDR和报文处理规则PHR，相应的，UPF#a从网元#a接收报文检测规则PDR和报文处理规则PHR。其中，该网元#a为非会话管理功能类型的网元。
S680，UPF#a在新增报文入口安装报文检测规则PDR，和/或在报文出口安装报文处理规则PHR。其中，该新增报文出口和新增报文入口均与网元#a对应。
S691，UE通过与网元#a对应的接口向UPF#a发送上行报文，相应的，UPF#a通过与网元#a对应的接口从用户设备UE接收上行数据报文。
S692，数据网络DN通过与网元#a对应的接口向UPF#a发送下行数据报文，相应的，UPF#a通过与网元#a对应的接口从数据网络DN接收下行数据报文。
S693，UPF#a根据报文检测规则PDR检测上行报文和/或下行报文，以及根据报文处理规则PHR处理上行报文和/或下行报文。
需要说明的是，步骤S660至S693可以参考上述步骤S550至S590的描述，为了简洁，此处不再赘述。
根据上述实施方式，通过UPF#a自行确定与网元#a对应的新增报文接口标识，并向SMF#a发送该新增报文接口标识，使得非SM#a的其他类型的控制面网元控制该UPF#a。另外，UPF#a能够将SMF#a网元和网元#a的不同配置参数隔离，实现并行处理同一个数据报文，进而实现不同类型的多控制器控制同一UPF#a。
上文中详细描述了本申请实施例的非SMF类型的其他类型的控制面网元控制UPF的方法，下面将描述本申请实施例的非SMF类型的其他类型的控制面网元控制UPF的装置。
根据前述方法，图7是适用于本申请实施例的通信装置10(也可以为网络设备，例如：SMF#A)的示意图。如图7所示，该通信装置10包括：收发单元11和处理单元12。
示例地，该处理单元12用于获取接口标识。
该收发单元11用于向第一网元发送用户面功能网元的地址和接口标识，该接口标识用于第一网元确定该接口标识对应的接口，该用户面功能网元的地址和接口标识用于第一网元控制该用户面功能网元。
应理解，通信装置10可以对应于根据本申请实施例的第一网元控制用户面功能管理网元的方法300/500/600中的会话功能管理网元，该通信装置10可以包括用于执行图3/图5/图6中第一网元控制用户面功能管理网元的方法300/500/600的网络设备执行的方法的模块(或单元)。并且，该通信装置10中的各模块(或单元)和上述其他操作和/或功能分别为了实现图3/图5/图6中第一网元控制用户面功能管理网元的方法300/500/600的相应流程。
示例地，收发单元11用于执行方法300/500/600中的S320，或者S510，S520，S540，S541和S550，或者S610，S620，S650和S660；处理单元12用于执行方法300/500/600中的S310，或者S530，或者S630和S640。各模块(或单元)执行上述相应步骤的过程在方法300/500/600中已经详细说明，为了简洁，在此不再赘述。
应理解，图7示例的装置10的结构仅为一种可能的形态，而不应对本申请实施例构成任何限定。本申请并不排除未来可能出现的其他形态的网络设备的可能。
应理解，根据本申请实施例的通信装置10可对应于前述方法实施例的第一网元控制用户面功能网元的网络设备，并且通信装置10中的各个模块(或单元)的上述和其它管 理操作和/或功能分别为了实现前述各个方法的相应步骤，因此也可以实现前述方法实施例中的有益效果。
还应理解，本申请实施例中的处理模块(或单元)可以由处理器实现，收发模块(或单元)可以由收发器实现。根据前述方法，图8是适用于本申请实施例的通信装置20(也可以为网络设备，例如：UPF#A)的示意图。如图8所示，该通信装置20包括：收发单元21和处理单元22。
示例地，该收发单元21用于从第一网元接收与该第一网元对应的报文检测规则和报文处理规则，第一网元为非会话管理功能类型的网元。
该收发单元21还用于通过与第一网元对应的接口接收报文。
该处理单元22用于根据报文检测规则检测报文，以及根据报文处理规则处理报文。
应理解，通信装置20可以对应于根据本申请实施例的第一网元控制用户面功能网元的方法300/500/600中的用户面功能网元，该通信装置20可以包括用于执行图3/图5/图6中第一网元控制用户面功能网元的方法300/500/600的网络设备执行的方法的模块(或单元)。并且，该通信装置20中的各模块(或单元)和上述其他操作和/或功能分别为了实现图3/图5/图6中第一网元控制用户面功能网元的方法300/500/600的相应流程。
示例地，收发单元21用于执行方法300/500/600中的S330和S340，或者S510，S540，S541，S560和S581和S582，或者S610，S650，S670，S691和S692；处理单元22用于执行方法300/500/600中的S350，或者S570和S590，或者S680和S693。各模块(或单元)执行上述相应步骤的过程在方法300/500/600中已经详细说明，为了简洁，在此不再赘述。
应理解，图8示例的装置20的结构仅为一种可能的形态，而不应对本申请实施例构成任何限定。本申请并不排除未来可能出现的其他形态的网络设备的可能。
应理解，根据本申请实施例的通信装置20可对应于前述方法实施例的第一网元控制用户面功能网元的网络设备，并且通信装置20中的各个模块(或单元)的上述和其它管理操作和/或功能分别为了实现前述各个方法的相应步骤，因此也可以实现前述方法实施例中的有益效果。
还应理解，本申请实施例中的处理模块(或单元)可以由处理器实现，收发模块(或单元)可以由收发器实现。
根据前述方法，图9是适用于本申请实施例的通信装置30(也可以为网络设备，例如：网元#A)的示意图。如图9所示，该通信装置30包括：收发单元31和处理单元32。
示例地，该收发单元31用于从会话管理功能网元接收用户面功能网元的地址和接口标识；
该处理单元32用于根据该接口标识确定该接口标识对应的接口；
该处理单元32还用于根据该用户面功能网元的地址和接口标识对应的接口控制该用户面功能网元；该收发单元31还用于向用户面功能网元发送与第一网元对应的报文检测规则和报文处理规则，其中，第一网元为非会话管理功能类型的网元。
应理解，通信装置30可以对应于根据本申请实施例的第一网元控制用户面功能网元的方法300/500/600中的非会话管理功能类型的其他类型的控制面网元，该通信装置30可以包括用于执行图3/图5/图6中第一网元控制用户面功能网元的方法300/500/600的网络 设备执行的方法的模块(或单元)。并且，该网络设备30中的各模块(或单元)和上述其他操作和/或功能分别为了实现图3/图5/图6中第一网元控制用户面功能网元的方法300/500/600的相应流程。
示例地，收发单元31用于执行方法300/500/600中的S320和S330，或者S520，S550和S560，或者S620，S660和S670。各模块(或单元)执行上述相应步骤的过程在方法300/500/600中已经详细说明，为了简洁，在此不再赘述。
应理解，图9示例的装置30的结构仅为一种可能的形态，而不应对本申请实施例构成任何限定。本申请并不排除未来可能出现的其他形态的网络设备的可能。
应理解，根据本申请实施例的通信装置30可对应于前述方法实施例的第一网元控制用户面功能网元的网络设备，并且通信装置30中的各个模块(或单元)的上述和其它管理操作和/或功能分别为了实现前述各个方法的相应步骤，因此也可以实现前述方法实施例中的有益效果。
还应理解，本申请实施例中的处理模块(或单元)可以由处理器实现，收发模块(或单元)可以由收发器实现。
根据前述方法，图10为本申请实施例提供的通信装置(也可以称为网络设备)40的示意图，如图10所示，该装置40可以为网络设备(例如，SMF)，也可以为芯片或电路，比如可设置于网络设备的芯片或电路。
该装置40可以包括处理器41(即，处理单元的一例)和存储器42。该存储器42用于存储指令，该处理器41用于执行该存储器42存储的指令，以使该装置40实现上述方法(例如，方法300或方法500或方法600)中网络设备(例如，SMF)执行的步骤。
可选地，该装置40还可以包括输入口43(即，通信单元的一例)和输出口44(即，通信单元的另一例)。应理解，该处理器41、存储器42、输入口43和输出口44可以通过内部连接通路互相通信，传递控制和/或数据信号。
该存储器42用于存储计算机程序，该处理器41可以用于从该存储器42中调用并运行该计算计程序，以控制输入口43接收信号，控制输出口44发送信号，完成上述方法中网络设备的步骤。
该存储器42可以集成在处理器41中，也可以与处理器41分开设置。
可选地，若该装置40为网络设备，该输入口43为接收器，该输出口44为发送器。其中，接收器和发送器可以为相同或者不同的物理实体。为相同的物理实体时，可以统称为收发器。
可选地，若该装置40为芯片或电路，该输入口43为输入接口，该输出口44为输出接口。
作为一种实现方式，输入口43和输出口44的功能可以考虑通过收发电路或者收发的专用芯片实现。处理器41可以考虑通过专用处理芯片、处理电路、处理器或者通用芯片实现。
作为另一种实现方式，可以考虑使用通用计算机的方式来实现本申请实施例提供的网络设备。即将实现处理器41、输入口43和输出口44功能的程序代码存储在存储器42中，通用处理器通过执行存储器42中的代码来实现处理器41、输入口43和输出口44的功能。
在本申请实施例中，该处理器41用于获取接口标识。
该输出口44用于向第一网元发送用户面功能网元的地址和接口标识，该接口标识用于第一网元确定该接口标识对应的接口，该用户面功能网元的地址和接口标识用于第一网元控制该用户面功能网元。
可选地，该装置40配置在或本身即为会话管理功能实体SMF。
其中，以上列举的装置40中各模块或单元的功能和动作仅为示例性说明，装置40中各模块或单元可以用于执行上述方法300或500或600中网络设备所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
例如，处理器41可以执行上述S530或者S630和S640中由SMF执行的动作。
该装置40所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
在一种可能的实施方式中，随着片上***(System-on-chip，SoC)技术的发展，装置40的全部或者部分功能由SoC技术实现，例如由一网络设备功能芯片实现，该网络设备功能芯片集成了处理器、存储器、通信接口等器件，网络设备相关功能的程序存储在存储器中，由处理器执行程序以实现基站的相关功能。可选地，该网络设备功能芯片也能够读取该芯片外部的存储器以实现基站的相关功能。
应理解，图10示例的装置40的结构仅为一种可能的形态，而不应对本申请实施例构成任何限定。本申请并不排除未来可能出现的其他形态的基站结构的可能。
根据前述方法，图11为本申请实施例提供的通信装置(也可以称为网络设备)50的示意图，如图11所示，该装置50可以为网络设备(例如，UPF)，也可以为芯片或电路，比如可设置于网络设备的芯片或电路。
该装置50可以包括处理器51(即，处理单元的一例)和存储器52。该存储器52用于存储指令，该处理器51用于执行该存储器52存储的指令，以使该装置50实现上述方法(例如，方法300或方法500或方法600)中网络设备(例如，UPF)执行的步骤。
可选地，该装置50还可以包括输入口53(即，通信单元的一例)和输出口54(即，通信单元的另一例)。应理解，该处理器51、存储器52、输入口53和输出口54可以通过内部连接通路互相通信，传递控制和/或数据信号。
该存储器52用于存储计算机程序，该处理器51可以用于从该存储器52中调用并运行该计算计程序，以控制输入口53接收信号，控制输出口54发送信号，完成上述方法中网络设备的步骤。
该存储器52可以集成在处理器51中，也可以与处理器51分开设置。
可选地，若该装置50为网络设备，该输入口53为接收器，该输出口54为发送器。其中，接收器和发送器可以为相同或者不同的物理实体。为相同的物理实体时，可以统称为收发器。
可选地，若该装置50为芯片或电路，该输入口53为输入接口，该输出口54为输出接口。
作为一种实现方式，输入口53和输出口54的功能可以考虑通过收发电路或者收发的专用芯片实现。处理器51可以考虑通过专用处理芯片、处理电路、处理器或者通用芯片实现。
作为另一种实现方式，可以考虑使用通用计算机的方式来实现本申请实施例提供的网 络设备。即将实现处理器51、输入口53和输出口54功能的程序代码存储在存储器52中，通用处理器通过执行存储器52中的代码来实现处理器51、输入口53和输出口54的功能。
在本申请实施例中，该输入口53用于从第一网元接收与该第一网元对应的报文检测规则和报文处理规则，第一网元为非会话管理功能类型的网元。
该输入口53还用于通过与第一网元对应的接口接收报文。
该处理器51用于用于根据报文检测规则检测报文，以及根据报文处理规则处理报文。
可选地，该装置50配置在或本身即为用户面功能实体UPF。
其中，以上列举的装置50中各模块或单元的功能和动作仅为示例性说明，装置50中各模块或单元可以用于执行上述方法300或500或600中网络设备所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
例如，处理器51可以执行上述S350，或者S570和S590，或者S680和S693中由UPF执行的动作。
该装置50所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
在一种可能的实施方式中，随着片上***(System-on-chip，SoC)技术的发展，装置50的全部或者部分功能由SoC技术实现，例如由一网络设备功能芯片实现，该网络设备功能芯片集成了处理器、存储器、通信接口等器件，网络设备相关功能的程序存储在存储器中，由处理器执行程序以实现基站的相关功能。可选地，该网络设备功能芯片也能够读取该芯片外部的存储器以实现基站的相关功能。
应理解，图11示例的装置50的结构仅为一种可能的形态，而不应对本申请实施例构成任何限定。本申请并不排除未来可能出现的其他形态的基站结构的可能。
根据前述方法，图12为本申请实施例提供的通信装置(也可以称为网络设备)60的示意图，如图12所示，该装置60可以为网络设备(例如，其他网元other NF)，也可以为芯片或电路，比如可设置于网络设备的芯片或电路。
该装置60可以包括处理器61(即，处理单元的一例)和存储器62。该存储器62用于存储指令，该处理器61用于执行该存储器62存储的指令，以使该装置60实现上述方法(例如，方法300或方法500或方法600)中网络设备(例如，其他网元)执行的步骤。
可选地，该装置60还可以包括输入口63(即，通信单元的一例)和输出口64(即，通信单元的另一例)。应理解，该处理器61、存储器62、输入口63和输出口64可以通过内部连接通路互相通信，传递控制和/或数据信号。
该存储器62用于存储计算机程序，该处理器61可以用于从该存储器62中调用并运行该计算计程序，以控制输入口63接收信号，控制输出口64发送信号，完成上述方法中网络设备的步骤。
该存储器62可以集成在处理器61中，也可以与处理器61分开设置。
可选地，若该装置60为网络设备，该输入口63为接收器，该输出口64为发送器。其中，接收器和发送器可以为相同或者不同的物理实体。为相同的物理实体时，可以统称为收发器。
可选地，若该装置60为芯片或电路，该输入口63为输入接口，该输出口64为输出接口。
作为一种实现方式，输入口63和输出口64的功能可以考虑通过收发电路或者收发的专用芯片实现。处理器61可以考虑通过专用处理芯片、处理电路、处理器或者通用芯片实现。
作为另一种实现方式，可以考虑使用通用计算机的方式来实现本申请实施例提供的网络设备。即将实现处理器61、输入口63和输出口64功能的程序代码存储在存储器62中，通用处理器通过执行存储器62中的代码来实现处理器61、输入口63和输出口64的功能。
在本申请实施例中，该输入口63用于从会话管理功能网元接收用户面功能网元的地址和接口标识；
该处理器61用于第一网元根据接口标识确定该接口标识对应的接口，
该处理器61还用于第一网元根据用户面功能网元的地址和接口标识对应的接口控制该用户面功能网元。
该输出口64用于向用户面功能网元发送与第一网元对应的报文检测规则和报文处理规则，第一网元为非会话管理功能类型的网元。
可选地，该装置60配置在或本身即为除SMF类型外的其他类型的控制器。
其中，以上列举的装置60中各模块或单元的功能和动作仅为示例性说明，装置60中各模块或单元可以用于执行上述方法300或500或600中网络设备所执行的各动作或处理过程，这里，为了避免赘述，省略其详细说明。
该装置60所涉及的与本申请实施例提供的技术方案相关的概念，解释和详细说明及其他步骤请参见前述方法或其他实施例中关于这些内容的描述，此处不做赘述。
在一种可能的实施方式中，随着片上***(System-on-chip，SoC)技术的发展，装置60的全部或者部分功能由SoC技术实现，例如由一网络设备功能芯片实现，该网络设备功能芯片集成了处理器、存储器、通信接口等器件，网络设备相关功能的程序存储在存储器中，由处理器执行程序以实现基站的相关功能。可选地，该网络设备功能芯片也能够读取该芯片外部的存储器以实现基站的相关功能。
应理解，图12示例的装置60的结构仅为一种可能的形态，而不应对本申请实施例构成任何限定。本申请并不排除未来可能出现的其他形态的基站结构的可能。
根据本申请实施例提供的方法，本申请实施例还提供一种通信***，其包括前述的至少一个转发设备和一个或多于一个网络设备。
应理解，本申请实施例中，该处理器可以为中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)， 其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
还应理解，本文提及的“第一”和“第二”等等仅仅是为了更清楚地表述本申请的技术方案而加以区分，不应对本申请构成任何限定。
在本说明书中使用的术语“部件”、“模块”、“***”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在2个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可例如根据具有一个或多个数据分组(例如来自与本地***、分布式***和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它***交互的互联网)的信号通过本地和/或远程进程来通信。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本 申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM)、随机存取存储器(RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (33)

  1. 一种通信方法，其特征在于，包括：
    会话管理功能网元获取接口标识；
    所述会话管理功能网元向第一网元发送用户面功能网元的地址和所述接口标识，所述接口标识用于所述第一网元确定所述接口标识对应的接口，所述用户面功能网元的地址和所述接口标识对应的接口用于所述第一网元控制所述用户面功能网元。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述会话管理功能网元向所述用户面功能网元发送第一信息，所述第一信息用于指示所述用户面功能网元分配所述接口标识。
  3. 如权利要求1或2所述的方法，其特征在于，所述会话管理功能网元获取接口标识，包括：
    所述会话管理功能网元从所述用户面功能网元接收所述接口标识。
  4. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    所述会话管理功能网元向所述用户面功能网元发送所述接口标识。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理功能网元从所述用户面功能网元接收能力指示信息，所述能力指示信息用于指示所述用户面功能网元能被第一类型的网元控制，所述第一类型的网元为非会话管理功能类型的网元。
  6. 如权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理功能网元从所述第一网元接收请求消息，所述请求消息用于请求控制所述用户面功能网元。
  7. 如权利要求6所述的方法，其特征在于，所述请求消息包括以下至少一种信息：所述用户面功能网元的标识，服务区域，用户设备的会话标识。
  8. 一种通信方法，其特征在于，包括：
    用户面功能网元从第一网元接收与所述第一网元对应的报文检测规则和报文处理规则，所述第一网元为非会话管理功能类型的网元；
    所述用户面功能网元通过与所述第一网元对应的接口接收报文；
    所述用户面功能网元根据所述报文检测规则检测所述报文，以及根据所述报文处理规则处理所述报文。
  9. 如权利要求8所述的方法，其特征在于，所述方法还包括：
    所述用户面功能网元从会话管理功能网元接收第一信息，所述第一信息用于指示所述用户面功能网元分配所述接口的接口标识。
  10. 如权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述用户面功能网元向所述会话管理功能网元发送所述接口的接口标识。
  11. 如权利要求8所述的方法，其特征在于，所述方法还包括：
    所述用户面功能网元从所述会话管理功能网元接收所述接口的接口标识。
  12. 如权利要求8至11中任一项所述的方法，其特征在于，所述方法还包括：
    所述用户面功能网元向所述会话管理功能网元发送能力指示信息，所述能力指示信息用于指示所述用户面功能网元能被第一类型的网元控制，所述第一类型的网元为非会话管理功能类型的网元。
  13. 一种通信方法，其特征在于，包括：
    第一网元从会话管理功能网元接收用户面功能网元的地址和接口标识；
    所述第一网元根据所述接口标识确定所述接口标识对应的接口；
    所述第一网元根据所述用户面功能网元的地址和所述接口标识对应的接口控制所述用户面功能网元；
    所述第一网元向所述用户面功能网元发送与所述第一网元对应的报文检测规则和报文处理规则，所述第一网元为非会话管理功能类型的网元。
  14. 如权利要求13所述的方法，其特征在于，所述方法还包括：
    所述第一网元向所述会话管理功能网元发送请求消息，所述请求消息用于请求所述第一网元请求控制所述用户面功能网元。
  15. 如权利要求14所述的方法，其特征在于，所述请求消息包括以下至少一种信息：
    所述用户面功能网元的标识，服务区域，用户设备的会话标识。
  16. 一种网络设备，其特征在于，包括：
    处理单元，用于获取接口标识；
    收发单元，用于向第一网元发送用户面功能网元的地址和所述接口标识，所述接口标识用于所述第一网元确定所述接口标识对应的接口，所述用户面功能网元的地址和所述接口标识对应的接口用于所述第一网元控制所述用户面功能网元。
  17. 如权利要求16所述的网络设备，其特征在于，
    所述收发单元，还用于向所述用户面功能网元发送第一信息，所述第一信息用于指示所述用户面功能网元分配所述接口标识。
  18. 如权利要求16或17所述的网络设备，其特征在于，
    所述处理单元用于通过所述收发单元从所述用户面功能网元接收所述接口标识。
  19. 如权利要求16所述的网络设备，其特征在于，
    所述收发单元，还用于向所述用户面功能网元发送所述接口标识。
  20. 如权利要求16至19中任一项所述的网络设备，其特征在于，
    所述收发单元，还用于从所述用户面功能网元接收能力指示信息，所述能力指示信息用于指示所述用户面功能网元能被第一类型的网元控制，所述第一类型的网元为非会话管理功能类型的网元。
  21. 如权利要求16至20中任一项所述的网络设备，其特征在于，
    所述收发单元，还用于从所述第一网元接收请求消息，所述请求消息用于请求控制所述用户面功能网元。
  22. 如权利要求21所述的网络设备，其特征在于，所述请求消息包括以下至少一种信息：所述用户面功能网元的标识，服务区域，用户设备的会话标识。
  23. 一种网络设备，其特征在于，包括：
    收发单元，用于从第一网元接收与所述第一网元对应的报文检测规则和报文处理规则，所述第一网元为非会话管理功能类型的网元；
    所述收发单元，还用于通过与所述第一网元对应的接口接收报文；
    处理单元，用于根据所述报文检测规则检测所述报文，以及根据所述报文处理规则处理所述报文。
  24. 如权利要求23所述的网络设备，其特征在于，
    所述收发单元，还用于从会话管理功能网元接收第一信息，所述第一信息用于指示所述用户面功能网元分配所述接口的接口标识。
  25. 如权利要求23或24所述的网络设备，其特征在于，
    所述收发单元，还用于向所述会话管理功能网元发送所述接口的接口标识。
  26. 如权利要求23所述的网络设备，其特征在于，
    所述收发单元，还用于从所述会话管理功能网元接收所述接口的接口标识。
  27. 如权利要求23至26中任一项所述的网络设备，其特征在于，
    所述收发单元，还用于向所述会话管理功能网元发送能力指示信息，所述能力指示信息用于指示所述用户面功能网元能被第一类型的网元控制，所述第一类型的网元为非会话管理功能类型的网元。
  28. 一种网络设备，其特征在于，包括：
    收发单元，用于从会话管理功能网元接收用户面功能网元的地址和接口标识；
    处理单元，用于根据所述接口标识确定所述接口标识对应的接口；
    所述处理单元，还用于根据所述用户面功能网元的地址和所述接口标识对应的接口控制所述用户面功能网元；
    所述收发单元，还用于向所述用户面功能网元发送与所述第一网元对应的报文检测规则和报文处理规则，所述第一网元为非会话管理功能类型的网元。
  29. 如权利要求28所述的网络设备，其特征在于，
    所述收发单元，还用于所述第一网元向所述会话管理功能网元发送请求消息，所述请求消息用于请求所述第一网元请求控制所述用户面功能网元。
  30. 如权利要求29所述的网络设备，其特征在于，所述请求消息包括以下至少一种信息：
    所述用户面功能网元的标识，服务区域，用户设备的会话标识。
  31. 一种通信***，其特征在于，包括：
    如权利要求16至22或23至27或28至30中任意一项所述的网络设备。
  32. 一种计算机可读存储介质，其特征在于，包括：
    所述计算机可读存储介质上存储有计算机程序，当所述计算机程序运行时，使得所述计算机执行如权利要求1至7或8至12或13至15中任意一项所述的方法。
  33. 一种芯片，其特征在于，包括：
    处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的通信装置执行如权利要求1至7或8至12或13至15中任意一项所述的方法。
PCT/CN2021/071854 2021-01-14 2021-01-14 通信方法和网络设备 WO2022151206A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202180051556.1A CN115918240A (zh) 2021-01-14 2021-01-14 通信方法和网络设备
PCT/CN2021/071854 WO2022151206A1 (zh) 2021-01-14 2021-01-14 通信方法和网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/071854 WO2022151206A1 (zh) 2021-01-14 2021-01-14 通信方法和网络设备

Publications (1)

Publication Number Publication Date
WO2022151206A1 true WO2022151206A1 (zh) 2022-07-21

Family

ID=82447865

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/071854 WO2022151206A1 (zh) 2021-01-14 2021-01-14 通信方法和网络设备

Country Status (2)

Country Link
CN (1) CN115918240A (zh)
WO (1) WO2022151206A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115665042A (zh) * 2022-12-12 2023-01-31 深圳艾灵网络有限公司 数据处理方法、装置、用户平面功能实体及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110662308A (zh) * 2018-06-30 2020-01-07 华为技术有限公司 一种通信方法及装置
WO2020088528A1 (en) * 2018-11-02 2020-05-07 Huawei Technologies Co., Ltd. Method and system for using policy to handle packets
US20200396779A1 (en) * 2018-02-15 2020-12-17 Telefonaktiebolaget Lm Ericsson (Publ) Sx protocol extension to support node pdr

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200396779A1 (en) * 2018-02-15 2020-12-17 Telefonaktiebolaget Lm Ericsson (Publ) Sx protocol extension to support node pdr
CN110662308A (zh) * 2018-06-30 2020-01-07 华为技术有限公司 一种通信方法及装置
WO2020088528A1 (en) * 2018-11-02 2020-05-07 Huawei Technologies Co., Ltd. Method and system for using policy to handle packets

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115665042A (zh) * 2022-12-12 2023-01-31 深圳艾灵网络有限公司 数据处理方法、装置、用户平面功能实体及存储介质
CN115665042B (zh) * 2022-12-12 2023-02-28 深圳艾灵网络有限公司 数据处理方法、装置、用户平面功能实体及存储介质

Also Published As

Publication number Publication date
CN115918240A8 (zh) 2024-05-10
CN115918240A (zh) 2023-04-04

Similar Documents

Publication Publication Date Title
US11102828B2 (en) User plane function selection for isolated network slice
US20230345354A1 (en) Network slice for visited network
KR102469191B1 (ko) 정보 전송방법 및 장치, 컴퓨터 판독가능 저장 매체
TWI524707B (zh) 進階應用介面之可調政策控制封包檢查系統及方法
US20210168151A1 (en) Method for implementing user plane security policy, apparatus, and system
WO2021232897A1 (zh) 中继链接建立、配置信息发送方法、装置和可读存储介质
US20230397145A1 (en) Mobility in Non-Public Networks
US20210385283A1 (en) Multimedia Priority Service
AU2020206808A1 (en) Communication method and communication apparatus
US20230354463A1 (en) State Transition of Wireless Device
US11824783B2 (en) Maximum data burst volume (MDBV) determining method, apparatus, and system
US20240073848A1 (en) Network Slice in a Wireless Network
US20240022952A1 (en) Resource Allocation in Non-Public Network
US20230328821A1 (en) Modifying PDU Sessions In Underlay Networks
US20240015630A1 (en) Routing Between Networks Based on Identifiers
CN113747479A (zh) 获取网络资源的方法、设备及***
WO2022012361A1 (zh) 一种通信方法及装置
US20240129794A1 (en) Network Congestion Control
WO2022151206A1 (zh) 通信方法和网络设备
WO2022174802A1 (zh) 密钥更新的方法和装置
WO2022067736A1 (zh) 一种通信方法及装置
WO2024032178A1 (zh) 一种通信方法及装置
WO2023185772A1 (zh) 一种通信方法及装置
WO2023015973A1 (zh) 一种网络切片准入控制方法和装置
US20240129793A1 (en) Network Overload Control

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: 21918414

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: 21918414

Country of ref document: EP

Kind code of ref document: A1