WO2021017689A1 - 一种用户面数据的获取方法、装置及存储介质 - Google Patents
一种用户面数据的获取方法、装置及存储介质 Download PDFInfo
- Publication number
- WO2021017689A1 WO2021017689A1 PCT/CN2020/097769 CN2020097769W WO2021017689A1 WO 2021017689 A1 WO2021017689 A1 WO 2021017689A1 CN 2020097769 W CN2020097769 W CN 2020097769W WO 2021017689 A1 WO2021017689 A1 WO 2021017689A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network element
- user plane
- function network
- information
- request message
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
Definitions
- This application relates to the field of communication technology, and in particular to a method, device and storage medium for obtaining user plane data.
- NWDAF network data analysis function
- PCF policy control function
- AMF Access or mobility management function
- SMF Session Management Function
- NWDAF analysis results are generated based on user plane data, so NWDAF needs to obtain relevant user plane data in advance.
- NWDAF needs to obtain relevant user plane data in advance.
- the present application provides a method, device, and storage medium for acquiring user plane data, which are used to enable the first network element to acquire required user plane data.
- the present application provides a method for obtaining user plane data.
- the method includes a first network element sending a first request message to a session management function network element, and the first network element obtains user plane data from the user plane function network element
- the first request message is used to instruct the session management function network element to request the user plane function network element to provide user plane data.
- the first network element when it determines that it needs to obtain user plane data, it can send the first request message to the session management function network element, thereby obtaining the user plane data that needs to be obtained from the user plane function network element.
- the session management function network element thereby obtaining the user plane data that needs to be obtained from the user plane function network element.
- the user plane data that needs to be acquired includes, but is not limited to, user plane data related to the terminal device and data corresponding to the user plane function network element supporting the first feature.
- the first network element may send a second request message to the data management network element and receive a second response message from the data management network element, where the second request message is used for
- the data management network element is requested for information of the user plane function network element serving the terminal device, and the second response message includes the information of the user plane function network element.
- the first network element can obtain user plane data related to a certain terminal device, and since the first network element can first obtain the user plane function network element that serves the terminal device, it can limit the final session management function network element The scope of the user plane function network element of the subscription target, thereby helping to avoid sending subsequent subscription request messages to unrelated user plane function network elements, which can save signaling overhead.
- the first network element may send a third request message to the network storage function network element, and receive the first request message from the network storage function network element.
- Three response messages where the third request message is used to request information of the session management function network element corresponding to the user plane function network element from the network storage function network element, and the third response message includes the information of the session management function network element.
- the first request message may include the information of the user plane function network element.
- the session management function network element can determine the user plane function network element that provides user plane data according to the information of the user plane function network element in the first request message, so that it can request the user plane data from the user plane function network element.
- the manner in which the first network element obtains user plane data includes one of the following manners.
- the first network element may receive a first response message sent by the session management function network element, where the first response message includes user plane data.
- Manner 2 The first network element receives a fourth response message sent by the user plane function network element, the fourth response message includes the first user plane data; wherein, the fourth response message is sent by the user plane function network element receiving the session management function network element After the fourth request message is sent to the first network element, the fourth request message is generated by the session management function network element according to the first request message.
- the first request message includes a first identifier
- the first identifier is used to indicate the type of user plane data to the session management function network element
- the fourth request message includes a second identifier
- the second identifier is used for Indicate the type of user plane data to the user plane function network element
- the fourth response message further includes a second identifier
- the first network element maps the second identifier to the first identifier according to the association relationship between the first identifier and the second identifier.
- the first identifier is the first event identifier.
- the second identifier is the second event identifier.
- the fourth response message further includes an association relationship between the second identifier and the first identifier. Based on this, after receiving the fourth response message, the first network element can directly map the second event identifier to the first event identifier according to the association relationship between the first event identifier and the second event identifier.
- the first request message further includes first filtering information
- the fourth request message further includes second filtering information
- the fourth response message further includes second filtering information; in this case, the first network
- the element maps the second filter information to the first filter information according to the association relationship between the first filter information and the second filter information.
- the fourth response message further includes an association relationship between the second filtering information and the first filtering information. Based on this, after the first network element receives the fourth response message, the first network element may directly map the second filtering information to the first filtering information according to the association relationship between the first filtering information and the second filtering information.
- the first network element obtains the information of the session management function network element from the data management network element, and the session management function network element serves the terminal device.
- the third request message includes the first characteristic. It is convenient for the network storage function network element to determine the user plane function network element supporting the first characteristic according to the first characteristic.
- the third response message further includes information of the user plane function network element.
- the session management function network element it is convenient for the session management function network element to quickly determine the object when the first request message is sent, that is, the user plane function network element.
- the first network element determines the second feature supported by the session management function network element according to the first feature; the third request message further includes the second feature.
- the first feature includes: information about the session management function network element associated with the user plane function network element, application information supported by the user plane function network element, and whether the user plane function network element supports capability opening service information , At least one of the service area information of the user plane function network element and the user group information served by the user plane function network element.
- this application provides a method for acquiring network element information.
- the method includes a data management network element receiving a second request message from a first network element, and sending a second response message to the first network element, and the second request message It is used to request information of the user plane function network element serving the terminal device from the data management network element, and the second response message includes the information of the user plane function network element.
- the first network element can obtain user plane data related to a certain terminal device, and since the first network element can first obtain the user plane function network element serving the terminal device, the session management function network can be limited.
- the range of the user plane function network element to which the element is finally subscribed can help avoid sending subsequent subscription request messages to unrelated user plane function network elements, which can save signaling overhead.
- the second request message is also used to request information of the session management function network element serving the terminal device from the data management network element, and the second response message further includes the information of the session management function network element.
- the first network element it is convenient for the first network element to directly send the first request message to the session management function network element in the second response message.
- the data management network element receives a first registration request message from the session management function network element and/or the user plane function network element, where the first registration request message includes information about the user plane function network element; data;
- the management network element saves the information of the user plane function network element in the data management network element according to the first registration request message.
- the data management network element stores information of the session management function network element in the data management network element according to the first registration request message, where the first registration request message also includes the session management function network element Information.
- this application provides a method for acquiring network element information.
- the method includes a network storage function network element receiving a third request message from a first network element, and the third request message is used to request a user from the network storage function network element Information about the session management function network element corresponding to the plane function network element, the third request message includes the first feature supported by the user plane function network element; the network storage function network element determines the session management function network element information according to the third request message; The storage function network element sends a third response message to the first network element, where the third response message includes the information of the session management function network element.
- the first network element obtains relevant user plane data from the user plane function network element supporting the first feature, and the first network element first determines the session management function network element through the first feature, thus Helps avoid subscribing to network elements that are not related to the session management function. That is, the scope of the subscribed session management function network elements is limited, and signaling overhead can be saved.
- the network storage function network element receives the second registration request message sent by the user plane function network element, and the network storage function network element combines the first registration request message supported by the user plane function network element according to the second registration request message.
- the characteristics are stored in a network storage function network element, and the second registration request message includes the first characteristics.
- Registering the first feature supported by the user plane function network element to the network storage function network element is convenient for the network storage function network element to store and manage the user plane function network element. Moreover, it may also be convenient for other network elements to subsequently determine the session management function network element corresponding to the user plane function network element supporting the first characteristic according to the first characteristic.
- the network storage function determines the second characteristic supported by the session management function network element according to the first characteristic, and determines the information of the session management function network element according to the second characteristic.
- the network storage function network element receives a third registration request message sent by the session management function network element, the third registration request message includes the second feature, and the network storage function network element responds to the third registration request message , Save the second characteristic in the network storage function network element.
- the first feature includes at least one of the following: information about the session management function network element associated with the user plane function network element, application information supported by the user plane function network element, and user plane function network element Whether to open the service information, the service area information of the user plane function network element, and the user group information served by the user plane function network element.
- the network storage function network element determines that the first characteristic includes the information of the session management function network element associated with the user plane function network element, and may be based on the session management function network element associated with the user plane function network element. Information, which determines the information of the session management function network element.
- this application provides a method for obtaining user plane data.
- the method includes a session management function network element receiving a first request message from a first network element, where the first request message is used to instruct the session management function network element to request the user plane.
- the functional network element provides user plane data
- the first request message includes a first identifier
- the first identifier is used to indicate the type of user plane data to the session management function network element
- the session management function network element may determine the fourth request message according to the first identifier
- the second identifier is included.
- the second identifier is used to indicate the type of user plane data to the user plane function network element.
- the session management function network element may send a fourth request message to the user plane function network element.
- the plane function network element requests user plane data.
- the first request message further includes information of the first user plane function network element.
- the first request message further includes first filtering information
- the session management function network element determines the second filtering information included in the fourth request message according to the first filtering information.
- the fourth request message further includes destination address information
- the destination address information is used to inform the user plane function network element of the destination address for reporting user plane data
- the destination address information is the address information of the first network element or Address information of the session management function network element. If the destination address is the address information of the first network element, the user plane function network element can directly report the fourth response message to the first network element without processing by the session management function network element. In this way, the number of session management function network elements can be reduced Receiving, processing, and storing data that is not needed by itself, thereby helping to reduce the workload of the session management function network element, and realizes that the user plane function network element directly reports the user plane data to the first network element.
- the session management function network element sends a first response message to the first network element, and the first response message includes user plane data.
- the session management function network element sends a fourth request message to the user plane function network element through a servicing interface; or the session management function network element sends a fourth request message to the user plane function network element through the N4 interface news.
- this application provides a method for obtaining user plane data.
- the method includes a user plane function network element receiving a fifth request message from a first network element, and the fifth request message is used to request a user plane data from the user plane function network element. Data; the user plane function network element sends a fifth response message to the first network element, and the fifth response message includes user plane data.
- the first network element can directly request user plane data from the user plane function network element without processing by the session management function network element. In this way, it can reduce the session management function network element receiving, processing, storing and unnecessary. Data, thereby helping to reduce the workload of the session management function network element, and realizes that the user plane function network element directly reports the user plane data to the first network element.
- the user plane function network element receives the fifth request message from the first network element through the servicing interface.
- the user plane function network element sends a fifth response message to the first network element through a service-oriented interface.
- this application provides a method for obtaining user plane data.
- the method includes a user plane function network element receiving a fourth request message from a session management function network element, the fourth request message being used to request a user from the user plane function network element Plane data; the user plane function network element sends a fourth response message to the first network element, and the fourth response message includes the user plane data.
- the user plane function network element directly sends the fourth response message to the first network element, which can save the session management function network element receiving, processing, and storing data that it does not need, thereby helping to reduce the session management function network. Yuan workload.
- the user plane function network element may send a fourth response message to the first network element according to the destination address information.
- the fourth request message also includes destination address information, and the destination address information is address information of the first network element.
- the destination address information is address information of the first network element.
- the user plane function network element may send the fourth response message to the first network element through the servicing interface.
- the fourth request message also includes destination address information.
- the destination address information may also be the address information of the session management function network element.
- the user plane function network element may send a fourth response to the session management function network element Message, the session management function network element forwards the fourth response message to the first network element.
- the user plane function network element may send a fourth response message to the session management function network element through a servicing interface; or the user plane function network element may send a fourth response message to the session management function network element through the N4 interface.
- the fourth request message further includes an association relationship between the first identifier and the second identifier, the first identifier is used to indicate the type of user plane data to the session management function network element, and the second identifier is used to Indicate the type of user plane data to the user plane function network element; the user plane function maps the second identifier to the first identifier according to the association relationship between the first identifier and the second identifier.
- the fourth request message also includes an association relationship between the first filtering information and the second filtering information; the user plane function divides the second filtering information according to the association relationship between the first filtering information and the second filtering information. The information is mapped to the first filtering information.
- the fourth response message further includes an association relationship between the first identifier and the second identifier, and/or an association relationship between the first filtering information and the second filtering information.
- this application provides a registration method.
- the method includes a session management function network element receiving a session establishment request message sent by a terminal device, a session management function network element sending a first registration request message to a data management network element, and a first registration
- the request message includes information about the user plane function network element serving the terminal device; among them, the session establishment request message is used to request the session management function network element to establish a session for the terminal device, and the first registration request message is used to request the data management network element to transfer the user
- the information of the surface function network element is stored in the data management network element.
- the session management function network element can register the information of the user plane function network element to the data management network element.
- the first registration request message further includes information of the session management function network element, and the first registration request is also used for the data management network element to save the information of the session management function network element in the data management network element.
- the present application provides a registration method, the method includes a user plane function network element receiving a connection establishment request message sent by a session management function network element, and the user plane function network element sending a first registration request message to the data management network element;
- the first registration request message includes information about the user plane function network element serving the terminal device
- the connection establishment request message is used to request the user plane function network element to establish a user plane transmission tunnel for the terminal device
- the first registration request message is used to request
- the data management network element saves the information of the user plane function network element in the data management network element.
- the user-plane function network element can directly register its own information with the data management network element.
- this application provides a registration method.
- the method includes a user plane function network element sending a second registration request message to a network storage function network element, the second registration request message including the first feature supported by the user plane function network element, The second registration request message is used to request the network storage function network element to save the first characteristic.
- the first characteristic of the user plane function network element can be registered in the network storage function network element, which is convenient for the network storage function network element to store and manage the user plane function network element. Moreover, it may also be convenient for other network elements to subsequently determine the session management function network element corresponding to the user plane function network element supporting the first characteristic according to the first characteristic.
- the first feature includes at least one of the following: information about the session management function network element associated with the user plane function network element, application information supported by the user plane function network element, and user plane function network element Whether to open the service information, the service area information of the user plane function network element, and the user group information served by the user plane function network element.
- this application provides a communication device, which may be a first network element (such as a data analysis network element), a session management function network element, a data management network element, a network storage function network element, or a user plane function network yuan.
- the communication device has the function of realizing the first network element, the session management function network element, the data management network element, the network storage function network element, or the user plane function network element in the foregoing embodiment.
- This function can be realized by hardware, or by hardware executing corresponding software.
- the hardware or software includes one or more units or modules corresponding to the above-mentioned functions.
- the communication device includes a processor and a transceiver, and the processor is configured to support the communication device to execute the first network element, the session management function network element, and the data management in the communication method shown above. Corresponding functions of network elements, network storage function network elements, or user plane function network elements.
- the transceiver is used to support communication between the communication device and other communication devices. Among them, the transceiver can be an independent receiver, an independent transmitter, a transceiver with integrated transceiver functions, or an interface circuit.
- the communication device may further include a memory, and the storage may be coupled with the processor, which stores program instructions and data necessary for the communication device.
- the communication device may be a first network element, a session management function network element, a data management network element, a network storage function network element, or a user plane function network element, or may be used for the first network element, session management network element, or user plane function network element.
- this application provides a communication device, which is used to implement any one of the foregoing first aspect or the first aspect, or is used to implement any one of the foregoing second or second aspects, Or used to implement any one of the foregoing third aspect or third aspect, or used to implement any one of the foregoing fourth aspect or fourth aspect, or used to implement the foregoing fifth or fifth aspect
- the eighth aspect or any one of the methods of the eighth aspect, or any one of the methods used to implement the ninth aspect or the ninth aspect includes corresponding functional modules, which are respectively used to implement the steps in the above methods.
- the function can be realized by hardware, or by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the above-mentioned functions.
- the structure of the communication device includes a processing unit and a transceiving unit, and these units can perform corresponding functions in the foregoing method examples.
- the transceiver unit may be a transceiver or a communication interface.
- the first network element may be a data analysis network element, for example: a network data analysis function network element.
- this application provides a chip system including a processor.
- a processor may also include a memory, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the device installed with the chip system executes the first aspect to the ninth aspect and possible implementations thereof Any method in.
- the present application provides a computer storage medium.
- the computer storage medium stores instructions that, when run on a computer, cause the computer to execute the first aspect to the ninth aspect and any one of its possible implementations. Any method.
- this application provides a computer program product including instructions, which when run on a computer, causes the computer to execute any method in the first to ninth aspects and any possible implementation manners thereof.
- Figure 1 is a schematic diagram of a communication system architecture provided by this application.
- FIG. 2 is a schematic flowchart of a method for acquiring user plane data provided by this application
- Figure 3a is a schematic flow chart of a method for acquiring network element information provided by this application.
- Figure 3b is a schematic flowchart of another method for acquiring network element information provided by this application.
- FIG. 4 is a schematic flowchart of another method for obtaining user plane data provided by this application.
- FIG. 5 is a schematic flowchart of another method for obtaining user plane data provided by this application.
- Figure 6a is a schematic flow diagram of a registration method provided by this application.
- Figure 6b is a schematic flow diagram of another registration method provided by this application.
- Figure 7a is a schematic flow diagram of a registration method provided by this application.
- FIG. 7b is a schematic flowchart of another registration method provided by this application.
- FIG. 8 is a schematic structural diagram of a communication device provided by this application.
- FIG. 9 is a schematic diagram of a communication device provided by this application.
- Fig. 1 exemplarily shows a schematic diagram of a communication system architecture provided by the present application.
- the communication system may include a data analysis network element, a data management network element, a network storage function network element, a session management function network element, a user plane function network element, and terminal equipment.
- data analysis network elements, data management network elements, network storage function network elements, and session management function network elements may be connected via a bus.
- the bus here refers to the logical connection and communication of the network elements in the communication system, and the connection and communication between the network elements in the communication system can be realized through interfaces or networks.
- the session management function network element is connected to the user plane function network element.
- the session management function network element can be used to control the user plane function network element to implement user plane related policies, or the session management function network element can be used to control the terminal through the mobility management network element
- the device or radio access network (radio access network, RAN) executes session-related policies.
- Data analysis network elements are mainly used to collect data from network function (NF) network elements, operation administration maintenance (OAM) systems, terminal equipment or application layer function (AF) network elements, and Analyze the collected data to obtain data analysis results.
- the data analysis network element can also send the obtained data analysis results to the NF, OAM system, terminal equipment or AF network element, so that these entities can make corresponding policy formulation and operation execution.
- data analysis network elements can be network data analysis function (NWDAF) network elements, management data analysis service (management data analytics service, MDAS) network elements Etc., in future communications such as 6th generation (6G) communications, the data analysis network element may still be NWDAF or MDAS network element, or have other names, which are not limited by this application.
- NF network elements include, but are not limited to, the mobility management function (access and mobility management function, AMF) network elements, session management function (SMF), policy control function (PCF) network elements in 5G. Yuan etc.
- the data management network element is mainly used to manage and store user data, such as contract information, authentication/authorization information.
- data management network elements can be unified data management (UDM) network elements or unified data repository (UDR) network elements.
- UDM unified data management
- UDR unified data repository
- future communications such as 6G, data management network elements can still be used It is a UDM network element or UDR network element, or has other names, and is not limited in this application.
- the network storage function network element is mainly used to support the service registration of the network function network element, network element status monitoring, etc., to realize the automatic management, selection and expansion of network function services.
- network storage function network elements can be network storage function (network repository function, NRF) network elements.
- network storage function network elements can still be NRF network elements, or have other names. This application There is no restriction on this.
- the session management function network element is mainly used for session management in the mobile network and the selection and control of the user plane function network element. Among them, session management such as session creation, modification, and release. Specific functions include, for example, assigning Internet Protocol (IP) addresses to users, selecting user plane function network elements that provide message forwarding functions, and so on.
- IP Internet Protocol
- the session management function network element may be a session management function (session management function, SMF) network element.
- SMF session management function
- future communications such as 6G, the session management function network element may still be an SMF network element or have other names.
- the application is not limited.
- User plane function network elements mainly used for user plane service processing, such as data packet routing and transmission, packet inspection, service usage reporting, quality of service (QoS) processing, lawful monitoring, upstream packet inspection, and downstream data packets Storage etc.
- the user plane function network element can be a user plane function (UPF) network element.
- UPF user plane function
- future communications such as 6G
- the user plane function network element can still be a UPF network element, or have other names.
- the application is not limited. It should be noted that the UPF in this application is the abbreviation of the core network UPF, and both have the same meaning and will not be described separately in the following.
- Access network equipment (also referred to as radio access network (RAN) equipment) is a device that provides wireless communication functions for terminals.
- Access network equipment includes, but is not limited to: next-generation base stations (gnodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (RNC), node B (node B) B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc.
- next-generation base stations evolved node B, eNB
- RNC radio network controller
- node B node B
- BSC base station controller
- BTS base transceiver station
- home base station for example, home evolved nodeB, or home node B, HNB
- Terminal equipment also known as user equipment (UE) is a device with wireless transceiver function, which can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ship Etc.); it can also be deployed in the air (for example, airplanes, balloons, satellites, etc.).
- the terminal can be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, and an industrial control (industrial control).
- VR virtual reality
- AR augmented reality
- industrial control industrial control
- Wireless terminals wireless terminals in self-driving (self-driving), wireless terminals in remote medical (remote medical), wireless terminals in smart grid, wireless terminals in transportation safety, smart cities
- the mobility management entity (MME) in 4G provides the function of the mobility management network element in this application; the MME and the serving gateway (SGW) in 4G provide the session management function network in this application.
- the shape and number of the network elements shown in FIG. 1 are only for example, and do not constitute a limitation to this application.
- the first network element needs to obtain user plane data for the purpose of data analysis, traffic monitoring, or billing of the network.
- the type of user plane data that the first network element needs to obtain may be of any granularity and of any type.
- it may be user plane data associated with a specific UE, or user plane data for UPF supporting specific characteristics.
- the user plane data of a specific UE includes, but is not limited to: the traffic usage of the specific UE, the flow bit rate measurement value of the service flow corresponding to an application in the specific UE, and the specific UE The start time and end time of user plane data transmission, and the start or end time of data transmission of a certain application of a specific UE (application data transportation start or end time).
- the user plane data of a UPF that supports a specific feature includes, but is not limited to: the traffic usage of all UEs on the UPF within a certain area, and the data packet size of the application on the UPF that supports a specific application. For different types of user data, how should the first network element obtain the required user plane data?
- FIG. 2 it is a schematic diagram of the method flow of a method for acquiring user plane data provided by this application.
- the method includes the following steps:
- Step 201 The first network element determines user plane data to be acquired.
- This step 201 is an optional step.
- the user plane data to be obtained can be user plane data related to a certain terminal device, or user plane data corresponding to a user plane function network element supporting a certain characteristic. Data, or other types of user plane data.
- Step 202 The first network element sends a first request message to the session management function network element.
- the first request message is used to instruct the session management function network element to request the user plane function network element to provide user plane data.
- the user plane data may be the user plane data to be obtained in step 201, and the first request message may be a subscription request message.
- Step 203 The first network element obtains user plane data from the user plane function network element.
- the user plane function network element may directly send the user plane data to the first network element, or the user plane function network element may send the user plane data to the NWDAF via the SMF.
- step 201 to step 203 above it can be seen that when the first network element determines that it needs to obtain user plane data, it can send the first request message to the SMF to obtain the user plane data that needs to be obtained from the user plane function network element. .
- the first network element determines that it needs to obtain user plane data
- it can send the first request message to the SMF to obtain the user plane data that needs to be obtained from the user plane function network element. .
- a process of how the first network element obtains user plane data is given.
- the first network element may be a data analysis network element, or any other network function network element that needs to obtain user plane data, where the data analysis network element may be the NWDAF network element shown in Figure 1, or it may be the future A network element in the communication system that has the function of the above-mentioned NWDAF network element.
- the data management network element in this application may be the UDM or UDR network element shown in FIG. 1, or may be a network element having the function of the above UDM network element in the future communication system.
- the network storage function network element in this application may be the NRF network element shown in FIG. 1, or may be a network element having the function of the aforementioned NRF network element in a future communication system.
- the session management function network element in this application may be the SMF network element shown in FIG. 1, or may be a network element having the function of the above SMF network element in a future communication system.
- the user plane function network element in this application may be the UPF network element shown in FIG. 1, or may be a network element having the function of the above UPF network element in the future communication system.
- the session management function network element is the SMF network element
- the user plane function network element is the UPF network element
- the first network element is the data analysis network element
- the data analysis network element is the NWDAF network element.
- Data management The network element is a UDM network element
- the network storage function network element is an NRF network element as an example for description.
- SMF SMF
- UPF UPF
- UDM UDM
- NWDAF NWDAF
- the terminal device is abbreviated as UE.
- the SMF described later in this application can be replaced with a session management function network element
- UPF can be replaced with a user plane function network element
- NWDAF can be replaced with a data analysis network element
- UDM can be replaced with a data management network element
- NRF Both can be replaced with network storage function network elements
- UE can be replaced with terminal equipment.
- Scenario 1 NWDAF needs to obtain user plane data related to terminal equipment. That is, in this scenario 1, the user plane data to be acquired is UE-related user plane data. To facilitate the description of the solution, the user plane data related to the UE is referred to as the first user plane data as follows.
- FIG. 3a it is a schematic flowchart of a method for acquiring information of a network element provided by this application.
- This method exemplarily provides a way to determine the UPF of the first user plane data. That is, when NWDAF needs to obtain user plane data of a certain UE, NWDAF addresses the UPF method.
- the method includes the following steps:
- Step 301 NWDAF sends a second request message to UDM.
- UDM receives the second request message from NWDAF.
- the second request message is used to request UDM information about the UPF serving the UE, for example, the identifier of the UPF serving the UE, or the address of the UPF serving the UE, or the address of the UPF serving the UE.
- the second request message can be an event exposure subscribe request message, a user context management (UE-CM)-get request message, or other forms that implement the above functions Request message, this application does not specifically limit the form of the second request message.
- UE-CM user context management
- the second request message may include UE information, for example, the identity of the UE. Specifically, it may be a subscription permanent identifier (SUPI) of the UE or a global positioning system identity (global positioning system). system identifier, GPSI).
- SUPI subscription permanent identifier
- global positioning system identity global positioning system identity
- GPSI global positioning system identifier
- Step 302 UDM sends a second response message to NWDAF.
- NWDAF receives the second response message from UDM.
- the second response message includes information about the UPF serving the UE.
- the UPF information can refer to the introduction of step 301 above, which will not be repeated here.
- the second response message may also be an event exposure subscribe response message.
- NWDAF can obtain user plane data related to a certain UE, and since NWDAF can first obtain the UPF serving the UE, it can limit the scope of the ultimate SMF subscription object UPF. This helps to avoid sending subsequent subscription request messages to unrelated UPFs, and can save signaling overhead.
- NWDAF also needs to determine the SMF serving the UE. Since a UPF may belong to one SMF or multiple SMFs, the SMF serving the UE corresponds to the UPF serving the UE.
- the following exemplarily provides three possible implementation methods for determining the SMF serving the UE.
- NWDAF can obtain the SMF serving the UE from the UDM.
- the second request message in the above step 301 may also be used to request UDM information about the SMF serving the UE, for example, the identifier of the SMF serving the UE, or the address of the SMF serving the UE ( address), or, the name of the SMF serving the UE, etc.
- the second response message in step 302 may also include information about the SMF serving the UE. It can also be understood that when NWDAF obtains the information of the UPF serving the UE from the UDM, it also obtains the information of the SMF serving the UE.
- the NWDAF may also request the UDM separately for the information of the SMF serving the UE, that is, the NWDAF may first request the UDM for the information of the UPF serving the UE, and then request the UDM for the information of the SMF serving the UE.
- Implementation manner B the association relationship between the UE and the SMF serving the UE is configured or stored in the NWDAF.
- the association relationship between the UE and the SMF serving the UE may come from the configuration of the operator, or may be stored by the NWDAF in the data collection and data association process.
- NWDAF finds from the collected data corresponding to the UE that the session management data of the UE comes from an SMF, then the SMF is determined to be the SMF serving the UE, and NWDAF is the association between the UE and the SMF serving the UE Save it.
- NWDAF finds from the collected data corresponding to the UE that the session management data of the UE comes from multiple SMFs, and the multiple SMFs serving the UE are all determined to be the SMFs serving the UE. The association relationship with the multiple SMFs serving the UE is saved.
- NWDAF obtains the SMF serving the UE from the NRF.
- the NWDAF can query the NRF for the SMF serving the UE.
- NWDAF may send a query request to NRF.
- the query request may include the current state information of the UE, such as the current network location and time of the UE, information about the group where the UE is located, public land mobile network (PLMN) to which the UE belongs, slice information, etc.
- PLMN public land mobile network
- the NRF receives the query request from the NWDAF, and can determine the SMF serving the UE based on the current state information of the UE in the query request.
- Scenario 2 NWDAF obtains user plane data corresponding to UPF that supports a certain feature.
- the user plane data is the user plane data corresponding to the UPF supporting a certain characteristic.
- the first feature is UPF profile
- UPF Profile the user plane data corresponding to the UPF
- the SMF corresponding to the UPF supporting the first feature in this scenario 2 may be the same as or different from the SMF serving the UE in the above scenario 1; the UPF supporting the first feature may be the same as the SMF serving the UE in the above scenario 1.
- the UPF of the UE is the same or may be different.
- the first characteristic may include information about the SMF associated with the UPF (for example, the name of the SMF, the identifier of the SMF, or the address of the SMF), and the application information supported by the UPF (for example, the name of the supported application or the Application identifier), at least one of capability opening service information (for example, UPF supports event exposure service), UPF service area information (UPF service area), and user group information of UPF service.
- the SMF associated with the UPF for example, the name of the SMF, the identifier of the SMF, or the address of the SMF
- the application information supported by the UPF for example, the name of the supported application or the Application identifier
- at least one of capability opening service information for example, UPF supports event exposure service
- UPF service area information UPF service area
- user group information of UPF service As shown in Table 1, the relationship between a UPF provided by this application and the first feature supported.
- Table 1 A relationship between UPF and the first characteristic.
- the first characteristic is a specific service area (service area).
- NWDAF needs to subscribe to the data packet size of the application on the UPF that supports a specific application (application), and the first feature is to support the specific application.
- NWDAF needs to subscribe to a certain user group (UE group) corresponding to the relevant user plane data on the UPF, and the first feature is to support specific groups.
- UE group user group
- the NWDAF In order to obtain the user plane data corresponding to the UPF supporting a certain feature, the NWDAF needs to obtain the user plane data from the UPF supporting a certain feature, and the NWDAF can first address the SMF corresponding to the first specific UPF to the NRF. In this application, NWDAF can determine the SMF corresponding to the UPF supporting the first feature based on the above first feature. That is, the NWDAF may first address the SMF corresponding to the UPF supporting the first feature to the NRF. As shown in FIG. 3b, it is a schematic flowchart of another method for acquiring information of a network element provided in this application. This method exemplarily provides a method for determining the SMF corresponding to the UPF supporting the first feature. The method includes the following steps:
- Step 311 NWDAF sends a third request message to NRF.
- the NRF receives the third request message from NWDAF.
- the NWDAF can determine the second feature supported by the SMF corresponding to the UPF supporting the first feature according to the first feature (the second feature is the SMF profile). That is, NWDAF can generate the second characteristic according to the first characteristic.
- the first feature includes public land mobile network identification (PLMN ID) 1, single network slice selection support information (single network slice selection assistance information, S-NSSAI) ID 1, service area (service area)1, NWDAF can generate the second characteristics according to the first characteristic: PLMN ID 1, S-NSSAI ID1, service area 2 (including service area 1).
- the third request message may include the first characteristic, or may also include the second characteristic, or may also include the first characteristic and the second characteristic.
- the third request message may include the first characteristic, or may also include the second characteristic, or may also include the first characteristic and the second characteristic.
- the third request message includes the first characteristic.
- the first feature is used by the NRF to determine the SMF corresponding to the UPF supporting the first feature.
- the first feature includes the information of the SMF associated with the UPF that supports the first feature, indicating that when the UPF registers with the NRF, the information of the SMF associated with the UPF that supports the first feature is also stored as the first feature of the UPF In NRF.
- SMF is responsible for selecting and allocating UPF for UE, there is a certain association relationship between SMF and UPF.
- a UPF is under the jurisdiction of a SMF.
- the service area (service area 1) of UPF is included in the service area (service area 2) of SMF.
- UPF and SMF are in the same slice.
- Scenario A-1 can also be understood as that the third request message includes the first feature, and the first feature includes information about the SMF associated with the UPF supporting the first feature.
- the first feature does not include information about the SMF associated with the UPF supporting the first feature. That is, the third request message includes the first feature, and the first feature does not include the information of the SMF associated with the UPF supporting the first feature.
- the second characteristic is included in the third request message.
- the second characteristic is used by the NRF to determine the information of the SMF supporting the second characteristic.
- the third request message includes the first characteristic and the second characteristic.
- the first feature includes information about the SMF associated with the UPF supporting the first feature. That is, the third request message includes the first characteristic and the second characteristic, and the first characteristic includes information about the SMF associated with the UPF supporting the first characteristic.
- the first feature does not include the SMF associated with the UPF supporting the first feature. That is, the third request message includes the first characteristic and the second characteristic, and the first characteristic does not include the information of the SMF associated with the UPF supporting the first characteristic.
- Step 312 The NRF determines the SMF information corresponding to the UPF supporting the first feature according to the third request message.
- the NRF may directly determine the SMF information corresponding to the UPF supporting the first feature according to the information of the SMF associated with the UPF supporting the first feature included in the first feature.
- the NRF may compare the first characteristic with the second characteristic of each SMF stored locally, and determine the SMF corresponding to the second characteristic that has the commonality with the first characteristic as the SMF corresponding to the UPF supporting the first characteristic.
- the first feature includes PLMN ID1, S-NSSAI ID 1, service area 1, and NRF finds PLMN ID 1, S-NSSAI ID 1, service area 2 (including service The SMF corresponding to the feature of area 1) is determined as the SMF corresponding to the UPF supporting the first feature.
- the NRF determines the SMF information corresponding to the UPF supporting the first feature according to the second feature.
- the SMF determines the SMF information corresponding to the UPF supporting the first feature according to the second feature.
- the NRF can directly determine the SMF information corresponding to the UPF supporting the first feature according to the SMF associated with the UPF supporting the first feature, and the determined UPF corresponding to the first feature supported The SMF needs to support the second feature.
- the NRF may determine the SMF information corresponding to the UPF supporting the first feature according to the second feature.
- the NRF may determine the SMF information corresponding to the UPF supporting the first feature according to the second feature.
- Step 313 NRF sends a third response message to NWDAF. Accordingly, NWDAF receives the third response message from NRF.
- the third response message includes SMF information corresponding to the UPF supporting the first feature.
- the third response message may be a discovery response message.
- the NRF may also determine the corresponding UPF information according to the first characteristic.
- the third response may also include UPF information supporting the first feature.
- NWDAF obtains relevant user plane data from UPF supporting the first feature, and NWDAF first determines the SMF through the first feature, thereby helping to avoid subscribing to unrelated SMFs. That is, the scope of the subscribed SMF is limited, which can save signaling overhead.
- the first identifier may be a first event identifier (event ID), and the second identifier may be a second event identifier.
- the first identifier is used to indicate the type of user plane data to the SMF, and the second identifier is used to indicate the type of user plane data to the UPF.
- the first identifier between NWDAF and SMF is called the first event identifier (the event identifier is also called event type), and the second identifier between UPF and SMF is called the second event identifier; that is, The first event identifier is used to identify the event between NWDAF and SMF, and the second event identifier is used to identify the event between UPF and SMF.
- the filtering information (event filter) between NWDAF and SMF is called first filtering information
- the filtering information between UPF and SMF is called second filtering information.
- the first request message may include the first event identifier, may also include the first filtering information, or may also include the first event identifier and the first filtering information.
- the first request message includes the first event identifier and the first filtering information as an example.
- FIG. 4 it is a schematic flowchart of another method for acquiring user plane data provided by this application.
- the method includes the following steps:
- Step 411 NWDAF sends a first request message to SMF.
- SMF receives the first request message from NWDAF.
- the first request message may be an event exposure subscription (event exposure subscribe) request message.
- the first request message may also include the first event identifier and the first filtering information.
- the NWDAF may set the first event identifier and the first filtering information subscribed to the SMF according to the type of user plane data to be obtained.
- NWDAF needs to obtain user plane data associated with a certain UE. For example, the traffic usage of a UE in a certain area within a certain period of time, NWDAF can set the first event identifier as a traffic usage report, and can set the first filter information as ⁇ time information (time), area information (area), UE ID (UE ID) ⁇ and other possible filtering information (other option filter).
- NWDAF can set the first event identifier as the measurement value of the traffic bit rate measurement, and can set the first filtering information It is ⁇ application ID (application ID), UE ID (first UE ID) ⁇ and other possible filtering information (other option filters).
- NWDAF needs to obtain the data corresponding to the UPF supporting the first feature. For example, if NWDAF needs to obtain traffic statistics of all UPFs in a certain area within a certain period of time, NWDAF can set the first event identifier as UPF traffic measurement report (traffic measurement report), and set the first filter information as ⁇ time information (time) , Area information (area) ⁇ . For another example, if NWDAF needs to obtain the measurement value of the traffic bit rate measurement of a service flow corresponding to an application (application), NWDAF can set the first event identifier as the measurement value of the traffic bit rate measurement, and the first filtering information is ⁇ application identifier (application ID) ⁇ . It can also be understood that NWDAF can generate first filtering information according to the first characteristic.
- Step 412 The SMF may generate a fourth request message according to the first request message.
- the first request message may include the first event identifier and the first filtering information. Because the first event identifier is different from the second event identifier, and the first filtering information and the second filtering information are also different. Therefore, the SMF needs to determine the second event identifier according to the first event identifier, and determine the second filter information according to the first filter information. That is, the fourth request message includes the second event identifier and the second filtering information.
- the SMF may map the second event identifier to the first event identifier according to the association relationship between the first event identifier and the second event identifier.
- the SMF may map the first filtering information to the second filtering information according to the association relationship between the first filtering information and the second filtering information.
- the first filtering information includes the UE ID (such as SUPI, GPSI)
- the SMF may map the UE ID to the UE ID' (such as the UE IP address) that can be recognized by the UPF.
- the second filtering information may include the IP address of the UE.
- the SMF can learn the location information of the UE and determine the UE based on the location information of the UE.
- the UPF that provides the service at the location determines the time range of the UE at the location. That is, the SMF can map the area information in the first filtering information to UPF and time information serving the UE.
- the second filtering information may include UPF and time information serving the UE.
- first event identifier and the second event identifier may also be the same, and the first filtering information and the second filtering information may also be the same.
- first request message and the fourth request message are the same.
- Step 413 The SMF sends a fourth request message to the UPF.
- the UPF receives the fourth request message from the SMF.
- the first request message may include UPF information.
- the SMF can determine the UPF that provides the user plane data according to the information of the UPF in the received first request message, so that it can request the user plane data from the UPF.
- the SMF requests user plane data related to the UE.
- the information of the sending object UPF of the fourth request message is obtained from the UDM, and the specific process can be referred to the introduction of the above FIG. 3a, which will not be repeated here.
- the SMF requests user plane data corresponding to the UPF supporting the first feature.
- determining the sending target UPF of the fourth request message can be implemented in the following three ways.
- SMF can determine the sending object UPF of the fourth request message according to the first filtering information contained in the first request message.
- the SMF can determine the UPF according to the first filtering information. For example, if the SMF executes the UPF selected for a specific application and saves the association relationship between the application identifier and the selected UPF, the SMF can map the corresponding UPF according to the application identifier. For another example, SMF executes to select UPF for the PDU session corresponding to a specific DNN, and saves the association relationship between the DNN identifier and the selected UPF, then the SMF can map the corresponding UPF according to the data network name (DNN) identifier.
- DNN data network name
- the above-mentioned third response message carries UPF information (that is, the information that NWDAF obtains UPF from NRF).
- the NRF may also determine the corresponding UPF information according to the first characteristic in the third request message.
- NRF sends the third response message to NWDAF, it can carry UPF information.
- NWDAF sends the first request message to the SMF, it may carry UPF information in the first request message.
- the SMF can send the fourth request message to the UPF through the following two types of interfaces.
- Type a a service-oriented interface between SMF and UPF.
- the SMF may send the fourth request message to the UPF through the servicing interface. Specifically, the SMF sends the fourth request message to the UPF through the servicing interface with the UPF.
- the fourth request message may be an event exposure-subscribe message.
- a service-oriented interface can target a certain network function network element, and the network function network element can interact with other network function network elements through this service interface, and other network function network elements can pass through
- the service-oriented interface corresponding to the service-oriented interface interacts with the network function network element.
- each network function network element can provide external services through its own service-oriented interface, and allow other authorized network function network elements to access or invoke its own services.
- the network function network element that provides the service is called the service provider, and the network function network element that accesses and invokes the service is called the service user. They can exchange specific messages by subscribing to request messages and notification messages.
- the SMF sends the fourth request message to the UPF through the N4 interface. That is, the SMF sends the fourth request message to the UPF through the N4 interface with the UPF.
- the fourth request message may be a packet forwarding control protocol (PFCP) session establishment request (session establishment request) message.
- PFCP packet forwarding control protocol
- the SMF can set the second event identifier subscribed to the UPF, the second filtering information, etc. in a usage report rule (URR).
- URR usage report rule
- SMF can obtain user plane data from UPF by adding a second event identifier and second filtering information to the URR.
- the SMF may send the URR to the UPF through the PFCP session establishment request message.
- the priority between the N4 interface and the servicing interface can be set. For example, the priority of the N4 interface can be set higher than that of the servicing interface. If the SMF determines that the user plane data that NWDAF needs to obtain can be provided by the N4 interface, the SMF can send the fourth request message through the N4 interface with the UPF. If the SMF determines that the N4 interface of user plane data that NWDAF needs to obtain cannot be provided, the SMF may send the fourth request message through the servicing interface with the UPF.
- the fourth request message may also include target address information.
- the target address information is used to inform the UPF of the destination address for reporting user plane data.
- the specific destination address may be NWDAF address information or SMF address information. Based on the destination address information carried in the fourth request message, it can be divided into the following three situations. For case 1, step 414 and step 415 are executed after step 413; for case 2, step 416 is executed after step 413.
- the destination address information is SMF address information.
- Step 414 UPF sends user plane data to SMF. Accordingly, SMF receives user plane data from UPF.
- the UPF can report the acquired user plane data to the SMF according to the second event identifier and the second filtering information.
- the SMF can map the second event identifier to the first event identifier according to the association relationship between the first event identifier and the second event identifier; and according to the first filtering information and the second filtering information
- the association relationship maps the second filtering information to the first filtering information.
- SMF converts the list of UE IP addresses into the group ID of the UE, and then converts the quality of service flow ID (QFI) to application ID, and then converts the quality of service flow ID to application ID.
- the flow bitrate measurement values (flow bitrate measurement) of the identification list are aggregated into the bitrate measurement corresponding to the PDU session.
- Step 415 SMF sends a first response message to NWDAF. Accordingly, NWDAF receives the first response message from SMF.
- the first response message includes the acquired user plane data. That is, the SMF may send the first response message to the NWDAF according to the mapped first event identifier and the first filtering information. Correspondingly, after receiving the first response message, the NWDAF can directly obtain the first event identifier and the first filtering information.
- the first response message may be an event exposure notification response message.
- the UPF sends the acquired user plane data to the SMF, which may be through the servicing interface between SMF and UPF, or through the N4 interface between SMF and UPF.
- the SMF since the SMF is responsible for selecting and allocating UPF for the UE, when the UE moves from one UPF to another new UPF, the SMF can send a fourth request message to the new UPF, and can cancel the subscription process to the original UPF.
- the destination address is the address information of NWDAF.
- Step 416 UPF sends a fourth response message to NWDAF. Accordingly, NWDAF receives the fourth response message from UPF.
- UPF can directly report the fourth response message to NWDAF without SMF processing. In this way, it can reduce SMF receiving, processing, and storing data that it does not need, thereby helping to reduce SMF workload. Moreover, UPF directly reports user plane data to NWDAF.
- the fourth request message carries the association relationship between the second event identifier and the first event identifier and the association relationship between the second filtering information and the first filtering information.
- the second event identifier can be mapped to the first event according to the association relationship between the first event identifier and the second event identifier Identification; and according to the association relationship between the first filtering information and the second filtering information, the second filtering information is mapped to the first filtering information.
- the UPF may directly send the acquired user plane data to the NWDAF according to the first event identifier and the first filtering information, that is, the UPF may directly send the fourth response message to the NWDAF.
- NWDAF can directly parse out the first event identifier and the first filtering information.
- the fourth request message does not include the association relationship between the first event identifier and the second event identifier and the association relationship between the first filtering information and the second filtering information.
- the UPF may send a fourth response message to the NWDAF after acquiring the user plane data according to the second event identifier and the second filtering information.
- the fourth response message may include an association relationship between the first event identifier and the second event identifier, and an association relationship between the first filtering information and the second filtering information.
- the SMF may also send the association relationship between the first event identifier and the second event identifier, and the association relationship between the first filtering information and the second filtering information to the NWDAF.
- NWDAF can map the second event identifier to the first event identifier according to the association relationship between the first event identifier and the second event identifier, and based on the first filtering information and the second filtering information
- the association relationship of the second filter information is mapped to the first filter information.
- NWDAF converts the UE’s IP address list into the UE’s group ID (group ID), and then converts the quality of service flow ID (QFI) into an application ID (application ID), and then converts the quality of service flow ID to application ID.
- the flow bit rate measurement values (flow bitrate measurement) of the identification list (quality of service flow list) are aggregated into the bit rate measurement value (bitrate measurement) corresponding to the PDU session.
- the reported user plane data is UE-related user plane data. If it is based on the above scenario 2, the reported user plane data is the user plane data corresponding to the UPF supporting the first feature.
- NWDAF requests user plane data from UPF via SMF
- SMF determines that the UPF request user plane data itself has been obtained from UPF through the N4 interface or is about to be obtained from UPF through the N4 interface, SMF will no longer call the event exposure service of UPF. You can directly send the user plane data that you have stored or will be stored in the future to SMF.
- the fourth request message can also carry reporting conditions, which are used in the form of SMF instructing UPF to send the fourth response message, such as SMF instructing UPF to periodically report the fourth response message or instructing UPF to be based on events Trigger reporting of the fourth response message.
- the fourth response message may be an event exposure notification response message.
- NWDAF can also directly obtain user plane data from UPF.
- FIG. 5 it is a schematic flowchart of another method for obtaining user plane data provided by this application. The method includes the following steps:
- Step 501 NWDAF sends a fifth request message to UPF.
- the fifth request message is used to request user plane data from the UPF.
- the NWDAF may send the fifth request message to the UPF through the servicing interface.
- Step 502 UPF sends a fifth response message to NWDAF.
- the fifth response message includes user plane data.
- the UPF may send the fifth response message to the NWDAF through the servicing interface.
- NWDAF can directly obtain user plane data from UPF without SMF processing. In this way, it can reduce SMF receiving, processing, storage and data not needed by itself, thereby helping to reduce SMF work Moreover, UPF directly reports user plane data to NWDAF.
- the SMF in the process of establishing or modifying the session (session) of the UE’s packet data unit (PDU), when the SMF serving the UE registers with the UDM, the SMF can also register the UPF serving the UE with the UDM in.
- PDU packet data unit
- Step 601 The SMF receives the session establishment or modification request message sent by the UE.
- the session establishment or modification request message is used to request the SMF to establish a session for the UE.
- the SMF is the SMF serving the UE. This step is optional.
- Step 602 SMF sends a first registration request message to UDM. Accordingly, UDM receives the first registration request from SMF.
- the first registration request message is used to request the UDM to save the information of the UPF serving the UE in the UDM.
- the UPF serving the UE corresponds to the SMF serving the UE.
- the UPF information serving the UE under each SMF may be registered in the UDM.
- the specific registration method is not limited.
- each SMF can separately register the information of the UPF serving the UE under it with the UDM, or the anchor SMF can register itself and the UPF information of the UE serving the UE under the scope of all intermediate SMFs in the UDM.
- the first registration request message may include UPF information, for example, the identifier of the UPF, or the address of the UPF, or the name of the UPF.
- the UDM may save the information of the UPF serving the UE in the UDM according to the first registration request message.
- the first registration request message in step 602 also includes information about the SMF serving the UE.
- the UDM may also save the information of the SMF serving the UE in the UDM according to the first registration request message.
- this method can realize the SMF to register the UPF information in the UDM.
- the UPF serving the UE can also directly register with the UDM.
- another registration method provided for this application includes the following steps:
- Step 611 The UPF serving the UE receives the connection establishment request message sent by the SMF serving the UE.
- connection establishment request message is used to request the UPF to establish a user plane transmission tunnel for the UE.
- the UPF receives the PDCP message sent by the SMF to request the establishment of the user plane transmission tunnel of the UE.
- Step 612 The UPF serving the UE sends a first registration request message to the UDM.
- the UDM receives the first registration request message from the UPF serving the UE.
- the first registration request message may include UPF information, for example, the identifier of the UPF, or the address of the UPF, or the name of the UPF.
- each UPF serving the UE may register its own information with the UDM, or the anchor UPF serving the UE may register itself and all intermediate UPF information in the UDM.
- Step 613 The UDM stores the information of the UPF serving the UE in the UDM according to the first registration request message.
- UPF can also register the supported first feature with NRF.
- another registration method provided for this application includes the following steps:
- Step 701 The UPF supporting the first feature sends a second registration request message to the NRF.
- the second registration request includes the first feature supported by UPF, where the first feature may include information of the SMF associated with the UPF (for example, the name of the SMF, the identifier of the SMF, or the address of the SMF), and the application information supported by the UPF (for example, At least one of supported application name or supported application identification), whether UPF supports capability exposure service information (for example, UPF event exposure service), UPF service area information (UPF service area), and user group information of UPF service item.
- This step 701 can also be understood as that the UPF registers the first feature supported by itself in the NRF.
- Step 702 The NRF saves the first characteristic in the NRF according to the second registration request message.
- the first feature of the UPF can be registered in the NRF, which facilitates the storage and management of the UPF by the NRF. Moreover, it may also be convenient for other network elements to determine the SMF corresponding to the UPF supporting the first feature according to the first feature. Moreover, the first feature includes the information of the SMF associated with the UPF. In this way, when NWDAF needs to obtain related user plane data from the UPF supporting the first feature, NWDAF first quickly determines the SMF corresponding to the UPF of the first feature. This helps to avoid subscribing to unrelated SMFs and can save signaling overhead.
- Step 711 The SMF supporting the second feature sends a third registration request message to the NRF.
- the third registration request message includes the second characteristic.
- SMF registers the second feature supported by itself in NRF.
- Step 712 the NRF stores the second feature supported by the SMF in the NRF according to the third registration request message.
- the second feature of the SMF supporting the second feature can be registered in the NRF, so that the NRF can store and manage the SMF. Moreover, it can also facilitate subsequent other network elements to determine the SMF according to the second characteristic.
- the method of determining UPF information shown in FIG. 3a may be independent of the method of obtaining user plane data shown in FIG. 2.
- the method for obtaining user plane data shown in FIG. 2 may be implemented based on the method for determining UPF information shown in FIG. 3a.
- the method for determining the SMF corresponding to the UPF supporting the first feature shown in FIG. 3b may be independent of the method for acquiring user plane data shown in FIG. 2.
- the user plane data acquisition method shown in FIG. 2 may be implemented based on the SMF method shown in FIG. 3b for determining the UPF corresponding to the first feature.
- FIG. 8 a schematic diagram of a communication device provided in this application is shown.
- the communication device is used to execute any one of the solutions on the first network element, the session management function network element, the data management network element, the network storage function network element, or the user plane function network element in the foregoing method flow.
- the communication device 800 in this example may include: a processor 801 and a transceiver 802.
- a memory 803 and a communication line 804 may also be included.
- the processor 801, the transceiver 802, and the memory 803 may be connected to each other through a communication line 804;
- the communication line 804 may be a peripheral component interconnection standard (peripheral component interconnect, PCI for short) bus or an extended industry standard architecture (extended industry standard architecture) , Referred to as EISA) bus and so on.
- the communication line 804 can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only one thick line is used in FIG. 8 to represent, but it does not mean that there is only one bus or one type of bus.
- the processor 801 may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of the present application.
- the transceiver 802 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), Wired access network, etc.
- the transceiver 802 may be a communication interface, and the communication interface may implement the function of the N4 interface or the service-oriented interface in the foregoing embodiment.
- the memory 803 may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions
- the dynamic storage device can also be electrically erasable programmable read-only memory (electrically programmable read-only memory, EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, Optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can Any other medium accessed by the computer, but not limited to this.
- the memory can exist independently and is connected to the processor through a communication line 804. The memory can also be integrated with the processor.
- the memory 803 is used to store computer-executed instructions for executing the solution of the present application, and the processor 801 controls the execution.
- the processor 801 is configured to execute computer-executable instructions stored in the memory 803, so as to implement the user plane data acquisition method provided in the foregoing embodiment of the present application.
- the computer-executable instructions in the embodiments of the present application may also be referred to as application program code, which is not specifically limited in the embodiments of the present application.
- the communication device 800 may be a first network element, and the first network element includes:
- the transceiver 802 is configured to send a first request message to the session management function network element, where the first request message is used to instruct the session management function network element to request the user plane function network element to provide user plane data.
- the processor 801 is configured to obtain user plane data from a user plane function network element.
- the transceiver 802 is also used to send a second request message to the data management network element, and the second request message is used to request the data management network element to serve the user of the terminal device And receive a second response message from the data management network element, where the second response message includes the information of the user plane function network element.
- the transceiver 802 is also used to send a third request message to the network storage function network element, and the third request message is used to send the network storage function
- the network element requests information of the session management function network element corresponding to the user plane function network element; and receives a third response message from the network storage function network element, where the third response message includes the information of the session management function network element.
- the first request message may include the information of the user plane function network element.
- the transceiver 802 is specifically configured to receive a first response message sent by a session management function network element, where the first response message includes user plane data; or, receive a fourth response message sent by a user plane function network element.
- Response message the fourth response message includes the first user plane data; wherein, the fourth response message is sent to the first network element after the user plane function network element receives the fourth request message sent by the session management function network element, the fourth request The message is generated by the session management function network element according to the first request message.
- the first request message may include a first identifier
- the first identifier is used to indicate the type of user plane data to the session management function network element
- the fourth request message may include a second identifier. Used to indicate the type of user plane data to the user plane function network element; the fourth response message may also include a second identifier; the processor 801 is specifically configured to map the second identifier according to the association relationship between the first identifier and the second identifier For the first logo.
- association relationship between the second identifier and the first identifier may be carried in the fourth response message.
- the first request message may further include first filtering information
- the fourth request message may further include second filtering information
- the fourth response message may further include second filtering information
- the processor 801 specifically It is used to map the second filter information to the first filter information according to the association relationship between the first filter information and the second filter information.
- association relationship between the second filtering information and the first filtering information may also be carried in the fourth response message.
- the processor 801 is further configured to obtain information of the session management function network element from the data management network element, and the session management function network element serves the terminal device.
- the third request message includes the first characteristic.
- the third response message further includes information of the user plane function network element.
- the processor 801 is further configured to determine a second feature supported by the session management function network element according to the first feature. Wherein, the third request message also includes the second characteristic.
- the first characteristic includes information about the session management function network element associated with the user plane function network element, application information supported by the user plane function network element, whether the user plane function network element supports capability opening service information, and the user plane function network element At least one of service area information and user group information served by the user plane function network element.
- the communication device 800 may be a data management network element, and the data management network element includes:
- the processor 801 and the transceiver 802 cooperate to receive a second request message from the first network element.
- the second request message is used to request information from the data management network element for the user plane function network element serving the terminal device;
- the first network element sends a second response message, and the second response message includes the information of the user plane function network element.
- the second request message is also used to request information of the session management function network element serving the terminal device from the data management network element, and the second response message further includes the information of the session management function network element.
- the transceiver 802 is further configured to receive a first registration request message from a session management function network element and/or a user plane function network element, where the first registration request message includes the user plane function network element information.
- the processor 801 is further configured to store the information of the user plane function network element in the data management network element according to the first registration request message.
- the first registration request message also includes the information of the session management function network element; the processor 801 is specifically configured to store the information of the session management function network element in the data according to the first registration request message. Manage network elements.
- the communication device 800 may be a network storage function network element, and the network storage function network element includes:
- the transceiver 802 is configured to receive a third request message from the first network element, the third request message is used to request the network storage function network element for information about the session management function network element corresponding to the user plane function network element, and the third request message It includes the first feature supported by the user plane function network element.
- the processor 801 is configured to determine the information of the session management function network element according to the third request message.
- the transceiver 802 is further configured to send a third response message to the first network element, where the third response message includes the information of the session management function network element.
- the transceiver 802 is further configured to receive a second registration request message sent by a user plane function network element, and the second registration request message includes the first characteristic.
- the processor 801 is further configured to store the first feature supported by the user plane function network element in the network storage function network element according to the second registration request message.
- the processor 801 is specifically configured to determine the second characteristic supported by the session management function network element according to the first characteristic, and determine the information of the session management function network element according to the second characteristic.
- the transceiver 802 is further configured to receive a third registration request message sent by a session management function network element, and the third registration request message includes the second characteristic.
- the processor 801 is further configured to store the second characteristic in the network storage function network element according to the third registration request message.
- the first feature includes the information of the session management function network element associated with the user plane function network element, the application information supported by the user plane function network element, whether the user plane function network element is capable of opening service information, and the user At least one of service area information of the plane function network element and user group information served by the user plane function network element.
- the processor 801 is specifically configured to determine that the first characteristic includes information about the session management function network element associated with the user plane function network element; and according to the session management function network element associated with the user plane function network element Information to determine the information of the session management function network element.
- the communication device 800 may be a session management function network element, and the session management function network element includes:
- the transceiver 802 is configured to receive a first request message from a first network element, where the first request message is used to instruct the session management function network element to request the user plane function network element to provide user plane data, and the first request message includes a first identifier, The first identifier is used to indicate the type of user plane data to the session management function network element.
- the processor 801 is configured to determine a second identifier included in the fourth request message according to the first identifier, and the second identifier is used to indicate the type of user plane data to the user plane function network element.
- the transceiver 802 is further configured to send a fourth request message to the user plane function network element, and the fourth request message is used to request user plane data from the user plane function network element.
- the first request message further includes information of the first user plane function network element.
- the first request message further includes first filtering information; the processor 801 is specifically configured to determine the second filtering information included in the fourth request message according to the first filtering information.
- the fourth request message further includes destination address information
- the destination address information is used to inform the user plane function network element of the destination address for reporting user plane data
- the destination address information is the address information of the first network element or Address information of the session management function network element.
- the transceiver 802 is further configured to send a first response message to the first network element, where the first response message includes user plane data.
- the transceiver 802 may be a servicing interface or an N4 interface, which can send the fourth request message to the user plane function network element through the servicing interface; or, to the user plane function network element through the N4 interface Yuan sends the fourth request message.
- the communication device 800 may be a session management function network element, and the session management function network element includes:
- the transceiver 802 is configured to receive a session establishment request message sent by a terminal device.
- the session establishment request message is used to request a session management function network element to establish a session for the terminal device; and send a first registration request message to the data management network element, the first registration
- the request message includes the information of the user plane function network element serving the terminal device; the first registration request message is used to request the data management network element to save the user plane function network element information in the data management network element.
- the first registration request message further includes information of the session management function network element, and the first registration request is also used for the data management network element to save the information of the session management function network element in the data management network element.
- the communication device 800 may be a user plane function network element, and the user plane function network element includes:
- the processor 801 and the transceiver 802 cooperate to receive a fifth request message from the first network element, the fifth request message is used to request user plane data from the user plane function network element; and send a fifth response to the first network element Message, the fifth response message includes user plane data.
- the transceiver 802 may be a servicing interface, and specifically may receive the fifth request message from the first network element through the servicing interface.
- the transceiver 802 may be a servicing interface, and specifically, may send the fifth response message to the first network element through the servicing interface.
- the communication device 800 may be a user plane function network element, and the user plane function network element includes:
- the processor 801 and the transceiver 802 cooperate to receive a fourth request message from the session management function network element.
- the fourth request message is used to request user plane data from the user plane function network element; and send the fourth request message to the first network element.
- the response message, the fourth response message includes user plane data.
- the fourth request message further includes destination address information, and the destination address information is address information of the first network element.
- the transceiver 802 may be specifically configured to send a fourth response message to the first network element according to the destination address information.
- the transceiver 802 may be a servicing interface, and specifically, may send the fourth response message to the first network element through the servicing interface.
- the destination address information may also be address information of the session management function network element; the transceiver 802 may be specifically configured to send a fourth response message to the session management function network element according to the destination address information.
- the transceiver 802 may specifically be a servicing interface or an N4 interface, which can send the fourth response message to the session management function network element through the servicing interface; or, to the session management function network element through the N4 interface
- the meta sends a fourth response message.
- the fourth request message further includes an association relationship between the first identifier and the second identifier, the first identifier is used to indicate the type of user plane data to the session management function network element, and the second identifier is used to Indicate the type of user plane data to the user plane function network element; the processor 801 is specifically configured to map the second identifier to the first identifier according to the association relationship between the first identifier and the second identifier.
- the fourth request message also includes an association relationship between the first filtering information and the second filtering information; the processor 801 is specifically configured to be able to perform an association based on the first filtering information and the second filtering information To map the second filtering information to the first filtering information.
- the fourth response message further includes an association relationship between the first identifier and the second identifier, and/or an association relationship between the first filtering information and the second filtering information.
- the communication device 800 may be a user plane function network element, and the user plane function network element includes:
- the transceiver 802 receives a connection establishment request message sent by the session management function network element, the connection establishment request message is used to request the user plane function network element to establish a user plane transmission tunnel for the terminal device; and sends a first registration request message to the data management network element
- the first registration request message includes the information of the user plane function network element serving the terminal device; wherein the first registration request message is used to request the data management network element to save the user plane function network element information in the data management network element.
- the communication device 800 may be a user plane function network element, and the user plane function network element includes:
- the transceiver 802 sends a second registration request message to the network storage function network element, the second registration request message includes the first feature supported by the user plane function network element, and the second registration request message is used to request the network storage function network element to save the first characteristic.
- the first feature includes: information about the session management function network element associated with the user plane function network element, application information supported by the user plane function network element, whether the user plane function network element is capable of opening service information, and the service of the user plane function network element At least one of area information and user group information served by the user plane function network element.
- this application provides a communication device for executing the first network element, the session management function network element, the data management network element, the network storage function network element, or the user plane function network element in the above method flow Either plan of the side.
- Fig. 9 exemplarily shows a schematic structural diagram of a communication device provided in this application.
- the communication device 900 in this example may include: a processing unit 901 and a transceiving unit 902.
- the processing unit 901 is used to control and manage the actions of the communication device 900.
- the transceiver unit 902 is used to support communication between the communication device 900 and other network entities.
- the communication device 900 may further include a storage unit 903 for storing program codes and data of the communication device 900.
- the processing unit 901 may be a processor or a controller, for example, a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing (digital signal processing, DSP), and an application specific integrated circuit (application specific integrated circuit). circuits, ASIC), field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of the present invention.
- the processor may also be a combination that implements computing functions, for example, including a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
- the transceiver unit 902 may be a communication interface, a transceiver, or a transceiver circuit, etc., where the communication interface is a general term. In a specific implementation, the communication interface may include multiple interfaces.
- the storage unit 903 may be a memory.
- the processing unit 901 may be implemented by the processor 801 in FIG. 8, and the transceiver unit 902 may be implemented by the transceiver 802 in FIG. 8. That is to say, the transceiver unit 902 in this application can execute the solution executed by the transceiver 802 in FIG. 8, and the processing unit 901 in this application can execute the solution executed by the processor 801 in FIG. 8, and the rest of the content can be referred to the above content. , I won’t repeat it here.
- the memory 803 included in the communication device 800 may be used to store the code when the processor 801 included in the communication device 800 executes the solution, and the code may be a program/code pre-installed when the communication device 800 leaves the factory.
- the present application provides a communication system.
- the communication system may include the above-mentioned first network element, and a session management function network element.
- the first network element can execute any method on the first network element side
- the session management function network element can execute any method on the session management function network element side.
- the possible implementation of the first network element and the session management function network element can be found in the above introduction, and will not be repeated here.
- the communication system may further include a user plane function network element and a data management network element.
- the first network element can execute any method on the first network element side shown in Figure 2, Figure 3a, Figure 4, or Figure 5, and the session management function network element can execute the method described in Figure 2, Figure 4, 6a or 6b.
- the user plane function network element can execute any method on the user plane function network element side shown in Figure 2, Figure 4, Figure 5 or Figure 6b, and the data management network element can execute
- the possible implementation manners of the user plane function network element and the data management network element can be referred to the above introduction, and will be repeated here.
- the communication system may further include a user plane function network element and a network storage function network element.
- the first network element can execute any method on the first network element side shown in Figure 2, Figure 3b, Figure 4, or Figure 5, and the session management function network element can execute the session shown in Figure 2, Figure 4, or Figure 7a.
- the user plane function network element can execute any method on the user plane function network element side shown in Figure 2, Figure 4, Figure 5 or Figure 7b
- the network storage function network element can execute the above figure 3b, the arbitrary method on the network storage function network element side shown in FIG. 7a or FIG. 7b
- the possible implementation manners of the user plane function network element and the network storage function network element can refer to the above introduction, and repeat them here.
- the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
- a software program it may be implemented in the form of a computer program product in whole or in part.
- the computer program product includes one or more instructions.
- the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part.
- the computer can be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices. Instructions can be stored in a computer storage medium, or transmitted from one computer storage medium to another computer storage medium.
- the instructions can be sent from a website, computer, server, or data center through wired (such as coaxial cable, optical fiber, digital user DSL) or wireless (such as infrared, wireless, microwave, etc.) to another website, computer, server or data center.
- a computer storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
- Usable media can be magnetic media (for example, floppy disks, hard drives, magnetic tapes, magneto-optical disks (MO), etc.), optical media (for example, CD, DVD, BD, HVD, etc.), or semiconductor media (for example, ROM, EPROM, EEPROM, etc.)
- Non-volatile memory NAND FLASH
- solid state disk Solid State Disk, SSD
- the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the embodiments of the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
- computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
- These instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device, and the instruction device implements A function specified in a flow or multiple flows in a flowchart and/or a block or multiple blocks in a block diagram.
- These instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so that the instructions executed on the computer or other programmable equipment provide Steps used to implement the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请提供一种用户面数据的获取方法、装置及存储介质。其中方法包括第一网元向会话管理功能网元发送第一请求消息,第一请求消息用于指示会话管理功能网元请求用户面功能网元提供用户面数据;第一网元获取来自用户面功能网元的用户面数据。如此,当第一网元在确定需要获取用户面数据时,可通过向会话管理功能网元发送第一请求消息,从而实现从用户面功能网元获取用户面数据。也就是说,通过上述方案,给出第一网元如何获取用户面数据的过程。
Description
相关申请的交叉引用
本申请要求在2019年07月26日提交中国专利局、申请号为201910683670.0、发明名称为“一种用户面数据的获取方法、装置及存储介质”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信技术领域,尤其涉及一种用户面数据的获取方法、装置及存储介质。
在第五代(the fifth generation,5G)移动通信系统中,一些功能网元需要获取用户面数据,以基于获取的用户面数据进行分析。例如网络数据分析功能(network data analytics function,NWDAF)网元能够对大量通信网络相关数据进行分析,并将分析结果发送给其他功能网元,如策略控制功能(policy control function,PCF)网元、接入或移动性管理功能(Access and Mobility Management Function,AMF)网元,会话管理功能(Session Management Function,SMF)网元等,其他功能网元参考分析结果执行相应的通信业务策略。
在很多场景下,NWDAF的分析结果是基于用户面数据生成的,则NWDAF需提前获取相关用户面数据。目前,并未公开NWDAF如何获取需要的用户面数据。
发明内容
本申请提供一种用户面数据的获取方法、装置及存储介质,用于实现第一网元获取到需要的用户面数据。
第一方面,本申请提供一种用户面数据的获取方法,该方法包括第一网元向会话管理功能网元发送第一请求消息,第一网元获取来自用户面功能网元的用户面数据第一请求消息用于指示会话管理功能网元请求用户面功能网元提供用户面数据。
基于该方案,第一网元在确定需要获取用户面数据时,可通过向会话管理功能网元发送第一请求消息,从而实现从用户面功能网元获取到需要获取的用户面数据。也就是说,通过上述方案,给出第一网元如何获取用户面数据的过程。
本申请中,需要获取的用户面数据包括但不限于终端设备相关的用户面数据、支持第一特性的用户面功能网元所对应的数据。
在用户面数据为终端设备相关的用户面数据的情况下,第一网元可向数据管理网元发送第二请求消息,接收来自数据管理网元的第二响应消息,第二请求消息用于向数据管理网元请求服务于终端设备的用户面功能网元的信息,第二响应消息包括用户面功能网元的信息。如此,第一网元可以实现获取某一终端设备相关的用户面数据,且由于第一网元可先获取到服务于该终端设备的用户面功能网元,从而可限定会话管理功能网元最终的订阅对象用户面功能网元的范围,从而有助于避免向不相关的用户面功能网元发送后续的订阅请求消息,可节约信令的开销。
在用户面数据为支持第一特性的用户面功能网元所对应的数据的情况下,第一网元可向网络存储功能网元发送第三请求消息,并接收来自网络存储功能网元的第三响应消息,其中,第三请求消息用于向网络存储功能网元请求用户面功能网元对应的会话管理功能网元的信息,第三响应消息包括会话管理功能网元的信息。如此,实现了第一网元从支持第一特性的用户面功能网元中获取相关的用户面数据,且是第一网元先通过第一特性确定出会话管理功能网元,从而有助于避免向不相关的会话管理功能网元订阅。即限制了订阅的会话管理功能网元的范围,可节约信令的开销。
在一种可能的实现方式中,第一请求消息可包括用户面功能网元的信息。如此,会话管理功能网元可根据第一请求消息中的户面功能网元的信息的确定出提供用户面数据的户面功能网元,从而可向该户面功能网元请求用户面数据。
在一种可能的实现方式中,第一网元获取用户面数据的方式包括以下方式中的一种。
方式一,第一网元可接收会话管理功能网元发送的第一响应消息,第一响应消息包括用户面数据。
方式二,第一网元接收用户面功能网元发送的第四响应消息,第四响应消息包括第一用户面数据;其中,第四响应消息是用户面功能网元接收会话管理功能网元发送的第四请求消息后向第一网元发送的,第四请求消息是会话管理功能网元根据第一请求消息生成的。
在一种可能的实现方式中,第一请求消息包括第一标识,第一标识用于向会话管理功能网元指示用户面数据的类型,第四请求消息包括第二标识,第二标识用于向用户面功能网元指示用户面数据的类型;第四响应消息还包括第二标识;第一网元根据第一标识与第二标识的关联关系,将第二标识映射为第一标识。如此,当第一网元与会话管理功能网元之间可识别的用户面数据的类型,与会话管理功能网元和用户面功能网元之间可识别的用户面数据的类型不同时,通过该映射过程,可实现了用户面数据的类型之间的转化。
应理解,若第一请求消息为订阅请求消息,则第一标识为第一事件标识。相应地,第四请求消息为也为订阅请求消息,则第二标识为第二事件标识。
进一步,第四响应消息还包括第二标识与第一标识的关联关系。基于此,第一网元接收到第四响应消息后,可根据第一事件标识与第二事件标识的关联关系,直接将第二事件标识映射为第一事件标识。
在一种可能的实现方式中,第一请求消息还包括第一过滤信息,第四请求消息还包括第二过滤信息,第四响应消息还包括第二过滤信息;在该情况下,第一网元根据第一过滤信息与第二过滤信息的关联关系,将第二过滤信息映射为第一过滤信息。
进一步,第四响应消息还包括第二过滤信息与第一过滤信息的关联关系。基于此,第一网元接收到第四响应消息后,第一网元可根据第一过滤信息与第二过滤信息的关联关系,直接将第二过滤信息映射为第一过滤信息。
在一种可能的实现方式中,第一网元从数据管理网元获取会话管理功能网元的信息,会话管理功能网元服务于终端设备。
在一种可能的实现方式中,第三请求消息中包括第一特性。便于网络存储功能网元根据第一特性确定出支持第一特性的用户面功能网元。
在一种可能的实现方式中,第三响应消息还包括用户面功能网元的信息。如此,可便于会话管理功能网元快速的确定出发送第一请求消息时对象,即用户面功能网元。
在一种可能的实现方式中,第一网元根据第一特性确定会话管理功能网元支持的第二 特性;第三请求消息中还包括第二特性。
在一种可能的实现方式中,第一特性包括:用户面功能网元关联的会话管理功能网元的信息、用户面功能网元支持的应用信息、用户面功能网元是否支持能力开放服务信息、用户面功能网元的服务区域信息、以及用户面功能网元服务的用户群组信息中的至少一项。
第二方面,本申请提供一种网元信息的获取方法,该方法包括数据管理网元接收来自第一网元的第二请求消息,向第一网元发送第二响应消息,第二请求消息用于向数据管理网元请求服务于终端设备的用户面功能网元的信息,第二响应消息包括用户面功能网元的信息。
基于该方案,第一网元可以实现获取某一终端设备相关的用户面数据,且由于第一网元可先获取到服务于该终端设备的用户面功能网元,从而可限定会话管理功能网元最终的订阅对象用户面功能网元的范围,从而有助于避免向不相关的用户面功能网元发送后续的订阅请求消息,可节约信令的开销。
在一种可能的实现方式中,第二请求消息还用于向数据管理网元请求服务于终端设备的会话管理功能网元的信息,第二响应消息还包括会话管理功能网元的信息。如此,可便于第一网元直接向第二响应消息中的会话管理功能网元发送第一请求消息。
在一种可能的实现方式中,数据管理网元接收来自会话管理功能网元和/或用户面功能网元的第一注册请求消息,第一注册请求消息包括用户面功能网元的信息;数据管理网元根据第一注册请求消息,将用户面功能网元的信息保存于数据管理网元。
在一种可能的实现方式中,数据管理网元根据第一注册请求消息,将会话管理功能网元的信息保存于数据管理网元,其中,第一注册请求消息中还包括会话管理功能网元的信息。
第三方面,本申请提供一种网元信息的获取方法,该方法包括网络存储功能网元接收来自第一网元的第三请求消息,第三请求消息用于向网络存储功能网元请求用户面功能网元对应的会话管理功能网元的信息,第三请求消息包括用户面功能网元支持的第一特性;网络存储功能网元根据第三请求消息确定会话管理功能网元的信息;网络存储功能网元向第一网元发送第三响应消息,第三响应消息包括会话管理功能网元的信息。
基于该方案,实现了第一网元从支持第一特性的用户面功能网元中获取相关的用户面数据,且是第一网元先通过第一特性确定出会话管理功能网元,从而有助于避免向不相关的会话管理功能网元订阅。即限制了订阅的会话管理功能网元的范围,可节约信令的开销。
在一种可能的实现方式中,网络存储功能网元接收用户面功能网元发送的第二注册请求消息,网络存储功能网元根据第二注册请求消息,将用户面功能网元支持的第一特性保存于网络存储功能网元,第二注册请求消息中包括第一特性。将用户面功能网元支持的第一特性注册到网络存储功能网元中,便于网络存储功能网元存储和管理用户面功能网元。而且,也可以便于后续其它网元根据第一特性确定出支持第一特性的用户面功能网元对应的会话管理功能网元。
在一种可能的实现方式中,网络存储功能根据第一特性确定会话管理功能网元支持的第二特性,并根据第二特性确定会话管理功能网元的信息。
在一种可能的实现方式中,网络存储功能网元接收会话管理功能网元发送的第三注册请求消息,第三注册请求消息中包括第二特性,网络存储功能网元根据第三注册请求消息,将第二特性保存于网络存储功能网元。
在一种可能的实现方式中,第一特性包括以下内容中至少一项:用户面功能网元关联的会话管理功能网元的信息、用户面功能网元支持的应用信息、用户面功能网元是否能力开放服务信息、用户面功能网元的服务区域信息、用户面功能网元服务的用户群组信息。
在一种可能的实现方式中,网络存储功能网元确定第一特性包括用户面功能网元关联的会话管理功能网元的信息,并可根据用户面功能网元关联的会话管理功能网元的信息,确定会话管理功能网元的信息。
第四方面,本申请提供一种用户面数据获取方法,该方法包括会话管理功能网元接收来自第一网元的第一请求消息,第一请求消息用于指示会话管理功能网元请求用户面功能网元提供用户面数据,第一请求消息包括第一标识,第一标识用于向会话管理功能网元指示用户面数据的类型,会话管理功能网元可根据第一标识确定第四请求消息包括的第二标识,第二标识用于向用户面功能网元指示用户面数据的类型,会话管理功能网元可向用户面功能网元发送第四请求消息,第四请求消息用于向用户面功能网元请求用户面数据。
基于该方案,当第一网元与会话管理功能网元之间可识别的用户面数据的类型,与会话管理功能网元和用户面功能网元之间可识别的用户面数据的类型不同时,通过该映射过程,可实现了用户面数据的类型之间的转化。
在一种可能的实现方式中,第一请求消息还包括第一用户面功能网元的信息。
在一种可能的实现方式中,第一请求消息还包括第一过滤信息,会话管理功能网元根据第一过滤信息确定第四请求消息包括的第二过滤信息。
在一种可能的实现方式中,第四请求消息还包括目的地址信息,目的地址信息用于告知用户面功能网元上报用户面数据的目的地址,目的地址信息为第一网元的地址信息或会话管理功能网元的地址信息。若目的地址为第一网元的地址信息,用户面功能网元可以将第四响应消息直接上报至第一网元,无需经过会话管理功能网元的处理,如此,可减少会话管理功能网元接收、处理、存储与自身不需要的数据,进而有助于减少会话管理功能网元的工作量,而且,实现了用户面功能网元直接向第一网元上报用户面数据。
在一种可能的实现方式中,若目的地址为会话管理功能网元的地址信息,会话管理功能网元向第一网元发送第一响应消息,第一响应消息包括用户面数据。
在一种可能的实现方式中,会话管理功能网元通过服务化接口向用户面功能网元发送第四请求消息;或者,会话管理功能网元通过N4接口向用户面功能网元发送第四请求消息。
第五方面,本申请提供一种用户面数据获取方法,该方法包括用户面功能网元接收来自第一网元的第五请求消息,第五请求消息用于向用户面功能网元请求用户面数据;用户面功能网元向第一网元发送第五响应消息,第五响应消息包括用户面数据。
基于该方案,第一网元可直接向用户面功能网元请求用户面数据,无需经过会话管理功能网元的处理,如此,可减少会话管理功能网元接收、处理、存储与自身不需要的数据,进而有助于减少会话管理功能网元的工作量,而且,实现了用户面功能网元直接向第一网元上报用户面数据。
在一种可能的实现方式中,用户面功能网元通过服务化接口接收来自第一网元的第五请求消息。
在一种可能的实现方式中,用户面功能网元通过服务化接口向第一网元发送第五响应消息。
第六方面,本申请提供一种用户面数据获取方法,该方法包括用户面功能网元接收来自会话管理功能网元的第四请求消息,第四请求消息用于向用户面功能网元请求用户面数据;用户面功能网元向第一网元发送第四响应消息,第四响应消息包括用户面数据。
基于该方案,用户面功能网元直接向第一网元发送第四响应消息,可省去会话管理功能网元接收、处理、存储与自身不需要的数据,进而有助于减少会话管理功能网元的工作量。
在一种可能的实现方式中,用户面功能网元可根据目的地址信息向第一网元发送第四响应消息。
示例一,第四请求消息还包括的目地址信息,目的地址信息为第一网元的地址信息。如此,可减少会话管理功能网元接收、处理、存储与自身不需要的数据,进而有助于减少会话管理功能网元的工作量,而且,实现了用户面功能网元直接向第一网元上报用户面数据。
基于该示例一中,用户面功能网元可通过服务化接口向第一网元发送第四响应消息。
示例二,第四请求消息还包括的目地址信息,目的地址信息也可以是会话管理功能网元的地址信息,在该情况下,用户面功能网元可向会话管理功能网元发送第四响应消息,会话管理功能网元再将第四响应消息转发至第一网元。
基于该示例二,用户面功能网元可通过服务化接口向会话管理功能网元发送第四响应消息;或者,用户面功能网元可通过N4接口向会话管理功能网元发送第四响应消息。
在一种可能的实现方式中,第四请求消息中还包括第一标识与第二标识的关联关系,第一标识用于向会话管理功能网元指示用户面数据的类型,第二标识用于向用户面功能网元指示用户面数据的类型;用户面功能根据第一标识与第二标识的关联关系,将第二标识映射为第一标识。
在一种可能的实现方式中,第四请求消息中还包括第一过滤信息与第二过滤信息的关联关系;用户面功能根据第一过滤信息与第二过滤信息的关联关系,将第二过滤信息映射为第一过滤信息。
在一种可能的实现方式中,第四响应消息还包括第一标识与第二标识的关联关系,和/或,第一过滤信息与第二过滤信息关联关系。
第七方面,本申请提供一种注册方法,该方法包括会话管理功能网元接收终端设备发送的会话建立请求消息,会话管理功能网元向数据管理网元发送第一注册请求消息,第一注册请求消息包括服务于终端设备的用户面功能网元的信息;其中,会话建立请求消息用于请求会话管理功能网元为终端设备建立会话,第一注册请求消息用于请求数据管理网元将用户面功能网元的信息保存于数据管理网元。
基于该方案,可实现会话管理功能网元将用户面功能网元的信息注册于数据管理网元。
在一种可能的实现方式中,第一注册请求消息还包括会话管理功能网元的信息,第一注册请求还用于数据管理网元将会话管理功能网元的信息保存于数据管理网元。
第八方面,本申请提供一种注册方法,该方法包括用户面功能网元接收会话管理功能网元发送的连接建立请求消息,用户面功能网元向数据管理网元发送第一注册请求消息;其中,第一注册请求消息包括服务于终端设备的用户面功能网元的信息,连接建立请求消息用于请求用户面功能网元为终端设备建立用户面传输隧道,第一注册请求消息用于请求数据管理网元将用户面功能网元的信息保存于数据管理网元。
基于该方案,可用户面功能网元直接向数据管理网元将自身的信息进行注册。
第九方面,本申请提供一种注册方法,该方法包括用户面功能网元向网络存储功能网元发送第二注册请求消息,第二注册请求消息包括用户面功能网元支持的第一特性,第二注册请求消息用于请求网络存储功能网元保存第一特性。
基于该方案,可将用户面功能网元的第一特性注册到网络存储功能网元中,便于网络存储功能网元存储和管理用户面功能网元。而且,也可以便于后续其它网元根据第一特性确定出支持第一特性的用户面功能网元对应的会话管理功能网元。
在一种可能的实现方式中,第一特性包括以下内容中至少一项:用户面功能网元关联的会话管理功能网元的信息、用户面功能网元支持的应用信息、用户面功能网元是否能力开放服务信息、用户面功能网元的服务区域信息、用户面功能网元服务的用户群组信息。
第十方面,本申请提供一种通信装置,该通信装置可以是第一网元(如数据分析网元)、会话管理功能网元、数据管理网元、网络存储功能网元或用户面功能网元。该通信装置具有实现上述实施例中的第一网元、会话管理功能网元、数据管理网元、网络存储功能网元或用户面功能网元的功能。该功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种可能的实现方式中,该通信装置包括:处理器和收发器,该处理器被配置为支持该通信装置执行以上所示通信方法中第一网元、会话管理功能网元、数据管理网元、网络存储功能网元或用户面功能网元的相应功能。该收发器用于支持该通信装置与其它通信装置之间的通信。其中,收发器可以为独立的接收器、独立的发射器、集成收发功能的收发器、或者是接口电路。可选地,该通信装置还可以包括存储器,该存储可以与处理器耦合,其保存该通信装置必要的程序指令和数据。
在一个可能的实现方式中,该通信装置可以是第一网元、会话管理功能网元、数据管理网元、网络存储功能网元或用户面功能网元,或者可用于第一网元、会话管理功能网元、数据管理网元、网络存储功能网元或用户面功能网元的部件,例如芯片或芯片系统或者电路。
第十一方面,本申请提供一种通信装置,用于实现上述第一方面或第一方面中的任意一种方法,或者用于实现上述第二方面或第二方面中的任意一种方法,或者用于实现上述第三方面或第三方面中的任意一种方法,或者用于实现上述第四方面或第四方面中的任意一种方法,或者用于实现上述第五方面或第五方面中的任意一种方法,或者用于实现上述第六方面或第六方面中的任意一种方法,或者用于实现上述第七方面或第七方面中的任意一种方法,或者用于实现上述第八方面或第八方面中的任意一种方法,或者用于实现上述第九方面或第九方面中的任意一种方法,包括相应的功能模块,分别用于实现以上方法中的步骤。功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的实施方式中,通信装置的结构中包括处理单元和收发单元,这些单元可以执行上述方法示例中相应功能,具体参见方法示例中的详细描述,此处不做赘述。其中,收发单元可以为收发器、或者是通信接口。
在上述任意一方面中,第一网元可以是数据分析网元,例如:网络数据分析功能网元。
第十二方面,本申请提供了一种芯片系统,包括处理器。可选地,还可包括存储器,存储器用于存储计算机程序,处理器用于从存储器中调用并运行计算机程序,使得安装有 芯片系统的装置执行上述第一方面至第九方面及其可能的实施方式中的任一方法。
第十三方面,本申请提供一种计算机存储介质,计算机存储介质中存储有指令,当其在计算机上运行时,使得计算机执行第一方面至第九方面及其任一可能的实施方式中的任一方法。
第十四方面,本申请提供一种包括指令的计算机程序产品,当其在计算机上运行时,使得计算机执行第一方面至第九方面及其任一可能的实施方式中的任一方法。
图1为本申请提供的一种通信系统架构示意图;
图2为本申请提供的一种用户面数据的获取方法流程示意图;
图3a为本申请提供的一种网元信息的获取方法流程示意图;
图3b为本申请提供的另一种网元信息的获取方法流程示意图;
图4为本申请提供的另一种用户面数据的获取方法流程示意图;
图5为本申请提供的再一种用户面数据的获取方法流程示意图;
图6a为本申请提供的一种注册方法流程示意图;
图6b为本申请提供的一种另一种注册方法流程示意图;
图7a为本申请提供的一种注册方法流程示意图;
图7b为本申请提供的另一种注册方法流程示意图;
图8为本申请提供的一种通信装置的结构示意图;
图9为本申请提供的一种通信装置的示意图。
为了使本申请实施例的目的、技术方案和优点更加清楚,下面将结合附图对本申请实施例作进一步地详细描述。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
图1示例性示出了本申请提供的一种通信系统架构示意图。如图1所示,该通信系统可以包括数据分析网元、数据管理网元、网络存储功能网元、会话管理功能网元、用户面功能网元和终端设备。其中,数据分析网元、数据管理网元、网络存储功能网元、会话管理功能网元可以通过总线连接。这里的总线是指在逻辑上能够实现通信系统中各网元的连接通信,通信系统中的各网元之间可以通过接口或网络来实现连接通信。会话管理功能网元和用户面功能网元连接,会话管理功能网元可以用于控制用户面功能网元执行用户面相关策略,或者会话管理功能网元可以用于通过移动性管理网元控制终端设备或无线接入网(radio access network,RAN)执行会话相关策略。
数据分析网元,主要用于从网络功能(network function,NF)网元、操作管理维护(operation administration maintenance,OAM)系统、终端设备或应用层功能(application function,AF)网元收集数据,并对收集的数据进行分析,从而得到数据分析结果。数据 分析网元还可以将所得的数据分析结果发送给NF、OAM系统、终端设备或AF网元,以便于这些实体做相应的策略制定、操作执行等。在第五代(the 5th generation,5G)通信中,数据分析网元可以是网络数据分析功能(network data analytics function,NWDAF)网元、管理面数据分析服务(management data analytics service,MDAS)网元等,在未来通信如第6代(6th generation,6G)通信中,数据分析网元仍可以是NWDAF或MDAS网元,或有其它的名称,本申请不做限定。其中,NF网元包括但不限于5G中的移动性管理功能(access and mobility management function,AMF)网元、会话管理功能(session management function,SMF)、策略控制功能(policy control function,PCF)网元等。
数据管理网元,主要用于管理、存储用户数据,如签约信息、鉴权/授权信息。在5G中,数据管理网元可以是统一数据管理(unified data management,UDM)网元或统一数据仓库功能(unified data repository,UDR)网元,在未来通信如6G中,数据管理网元仍可以是UDM网元或UDR网元,或有其它的名称,本申请不做限定。
网络存储功能网元,主要用于支持网络功能网元的服务注册登记、网元状态监测等,实现网络功能服务自动化管理,选择和扩展。在5G中,网络存储功能网元可以是网络存储功能(network repository function,NRF)网元,在未来通信如6G中,网络存储功能网元仍可以是NRF网元,或者有其它名称,本申请对此不作限定。
会话管理功能网元,主要用于移动网络中的会话管理和用户面功能网元的选择和控制。其中,会话管理如会话创建、修改、释放。具体功能比如包括为用户分配互联网协议(internet protocol,IP)地址、选择提供报文转发功能的用户面功能网元等。在5G中,会话管理功能网元可以是会话管理功能(session management function,SMF)网元,在未来通信如6G中,会话管理功能网元仍可以是SMF网元,或有其它的名称,本申请不做限定。
用户面功能网元,主要用于用户平面的业务处理,例如数据包路由和传输、包检测、业务用量上报、服务质量(Quality of Service,QoS)处理、合法监听、上行包检测、下行数据包存储等。在5G中,用户面功能网元可以是用户面功能(user plane function,UPF)网元,在未来通信如6G中,用户面功能网元仍可以是UPF网元,或有其它的名称,本申请不做限定。需要说明的是,本申请中的UPF是核心网UPF的简称,二者具有相同的含义,后续不再单独说明。
接入网设备(也称为无线接入网(radio access network,RAN)设备),是一种为终端提供无线通信功能的设备。接入网设备包括但不限于:5G中的下一代基站(g nodeB,gNB)、演进型节点B(evolved node B,eNB)、无线网络控制器(radio network controller,RNC)、节点B(node B,NB)、基站控制器(base station controller,BSC)、基站收发台(base transceiver station,BTS)、家庭基站(例如,home evolved nodeB,或home node B,HNB)、基带单元(baseBand unit,BBU)、传输点(transmitting and receiving point,TRP)、发射点(transmitting point,TP)、移动交换中心等。
终端设备(也可以称为用户设备(user equipment,UE))是一种具有无线收发功能的设备,可以部署在陆地上,包括室内或室外、手持或车载;也可以部署在水面上(如轮船等);还可以部署在空中(例如飞机、气球和卫星上等)。终端可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality,VR)终端、增强现实(augmented reality,AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
需要说明的是,本申请也可以应用于第四代(the 4th generation,4G)网络架构。比如,由4G中的移动性管理实体(mobility management entity,MME)提供本申请中移动性管理网元的功能;由4G中的MME和服务网关(serving gateway,SGW)提供本申请中会话管理功能网元的功能;由4G中的分组数据网网关(PDN gateway,PGW)提供本申请中核心网UPF的功能;由4G中的数据分析网元提供本申请中数据分析网元的功能等。另外,图1中所示的网元的形态和数量仅用于举例,并不构成对本申请的限定。
在介绍本申请的方法之前,首先对本申请所涉及的应用场景进行进一步的介绍说明,以便于理解本方案。需要说明的是,该部分内容也作为本申请的发明内容的一部分可选地的内容。
第一网元为了实现网络的数据分析、流量监控、或计费等目的,需要获取用户面数据。针对不同的需求,第一网元需要获取的用户面数据的类型可能是任意粒度和任意类型的。例如,可以是针对特定UE相关联的用户面数据,也可以是针对支持特定特性的UPF的用户面数据。示例性地,特定UE的用户面数据包括但不限于:特定UE的流量使用情况、特定UE中某个应用(application)对应的业务流的流量比特率测量(flow bit rate measurement)值、特定UE的用户面数据传输的起始时间和终止时间、特定UE的某个应用的数据传输开始或结束时间(application data transportation start or end time)。支持特定特性的UPF的用户面数据包括但不限于:某区域范围内的UPF上的所有UE的流量使用情况、支持某个特定application的UPF上该application的数据包大小等。针对不同类型的用户数据,第一网元该如何获取需要的用户面数据。
鉴于上述的技术问题,下面结合附图介绍本申请实施例提供的技术方案。如图2所示,为本申请提供的一种用户面数据的获取方法的方法流程示意图。该方法包括以下步骤:
步骤201,第一网元确定待获取的用户面数据。
该步骤201为可选步骤,在该步骤201中,待获取的用户面数据可以是某一终端设备相关的用户面数据,也可以是支持某一特性的用户面功能网元所对应的用户面数据,或者也可以是其它类型的用户面数据。
步骤202,第一网元向会话管理功能网元发送第一请求消息。
此处,第一请求消息用于指示会话管理功能网元请求用户面功能网元提供用户面数据。该用户面数据可以为步骤201中待获取的用户面数据,该第一请求消息可以为订阅请求消息。
步骤203,第一网元获取来自用户面功能网元的用户面数据。
此处,用户面功能网元可直接向第一网元发送用户面数据,或者用户面功能网元经SMF向NWDAF发送用户面数据。
从上述步骤201至步骤203可以看出,第一网元在确定需要获取用户面数据时,可通过向SMF发送第一请求消息,从而实现从用户面功能网元获取到需要获取的用户面数据。也就是说,通过上述方案,给出第一网元如何获取用户面数据的过程。
本申请中,第一网元可以是数据分析网元、或者任意其他需要获取用户面数据的网络功能网元,其中,数据分析网元可以是图1所示的NWDAF网元,也可以是未来通信系统 中的具有上述NWDAF网元的功能的网元。本申请中数据管理网元可以是图1所示的UDM、UDR网元,也可以是未来通信系统中的具有上述UDM网元的功能的网元。本申请中网络存储功能网元可以是图1所示的NRF网元,也可以是未来通信系统中的具有上述NRF网元的功能的网元。本申请中的会话管理功能网元可以是图1所示的SMF网元,也可以是未来通信系统中的具有上述SMF网元的功能的网元。本申请中的用户面功能网元可以是图1所示的UPF网元,也可以是未来通信系统中的具有上述UPF网元的功能的网元。
为方便说明,本申请后续,以会话管理功能网元为SMF网元,用户面功能网元为UPF网元,第一网元为数据分析网元,数据分析网元为NWDAF网元,数据管理网元为UDM网元,网络存储功能网元为NRF网元为例进行说明。进一步地,将SMF网元简称为SMF,UPF网元简称为UPF,UDM网元简称为UDM,NWDAF网元简称为NWDAF,终端设备简称为UE。即本申请后续所描述的SMF均可替换为会话管理功能网元,UPF均可替换为用户面功能网元,NWDAF均可替换为数据分析网元,UDM均可替换为数据管理网元,NRF均可替换为网络存储功能网元,UE均可替换为终端设备。
基于NWDAF需要获取的不同类型的用户面数据,如下结合具体的场景,分别详细介绍NWDAF如何确定第一请求消息的发送对象SMF,以及如何确定提供用户面数据的UPF。
场景一:NWDAF需要获取终端设备相关的用户面数据。也就是说,在该场景一中,待获取的用户面数据为UE相关的用户面数据。如下为了便于方案的说明,将UE相关的用户面数据称为第一用户面数据。
如图3a所示,为本申请提供的一种网元的信息的获取方法的方法流程示意图。该方法示例性地给出了提供第一用户面数据的UPF的确定方式。即NWDAF需要获取某UE的用户面数据时,NWDAF寻址UPF的方法。该方法包括如下步骤:
步骤301,NWDAF向UDM发送第二请求消息。相应地,UDM接收来自NWDAF的第二请求消息。
其中,第二请求消息用于向UDM请求服务于该UE的UPF的信息,例如,服务于该UE的UPF的标识、或者、服务于该UE的UPF的地址(address)、或者、服务于该UE的UPF的名称,等。另外,第二请求消息可以是事件开放订阅(event exposure subscribe)请求消息,也可以是获取用户上下文管理(context management,UE-CM)-get请求消息,或者也可以是实现上述功能的其他形式的请求消息,本申请对第二请求消息的形式不做具体限定。
在一种可能的实现方式中,该第二请求消息中可包括UE的信息,例如,UE的标识,具体可以为UE的用户永久标识(subscription permanent identifier,SUPI)或全球定位系统标识(global positioning system identifier,GPSI)。以便于UDM根据UE的信息以及自身存储的该UE相关的签约信息、上下文信息,确定服务于该UE的UPF的信息。
步骤302,UDM向NWDAF发送第二响应消息。相应地,NWDAF接收来自UDM的第二响应消息。
其中,第二响应消息包括服务于该UE的UPF的信息。其中,UPF的信息可参见上述步骤301的介绍,此处不再赘述。另外,第二响应消息也可以是事件开放订阅(event exposure subscribe)响应消息。
通过上述步骤301至步骤302可以看出,NWDAF可以实现获取某一UE相关的用户 面数据,且由于NWDAF可先获取到服务于该UE的UPF,从而可限定SMF最终的订阅对象UPF的范围,从而有助于避免向不相关的UPF发送后续的订阅请求消息,可节约信令的开销。
进一步,NWDAF还需要确定服务于该UE的SMF,由于一个UPF可能属于一个SMF管辖,也可能属于多个SMF管辖,因此,服务于该UE的SMF与服务于该UE的UPF对应。如下示例性的提供了三种确定服务于该UE的SMF的可能实现方式。
实现方式A,NWDAF可从UDM中获取服务于该UE的SMF。
具体可以是,在上述步骤301的第二请求消息还可用于向UDM请求服务于该UE的SMF的信息,例如,服务于该UE的SMF的标识、或者、服务于该UE的SMF的地址(address)、或者、服务于该UE的SMF的名称等。相应地,在上述步骤302的第二响应消息中还可包括该服务于UE的SMF的信息。也可以理解为,NWDAF从UDM中获取服务于该UE的UPF的信息的同时,获取该服务于该UE的SMF的信息。当然,NWDAF也可单独向UDM请求服务于该UE的SMF的信息,也就是说,NWDAF可以先向UDM请求服务于UE的UPF的信息,再向UDM请求服务于UE的SMF的信息。
实现方式B,NWDAF中配置或保存有UE与服务于该UE的SMF之间的关联关系。
其中,UE与服务于该UE的SMF之间的关联关系可以来自运营商的配置,也可以是NWDAF在数据收集和数据关联流程中保存的。例如,NWDAF从已经收集的UE对应的数据中发现,UE的会话管理数据来源于一个SMF,则该SMF确定为服务于该UE的SMF,NWDAF将该UE与服务于该UE的SMF的关联关系进行保存。再比如,NWDAF从已经收集的UE对应的数据中发现,UE的会话管理数据来源于多个SMF,则这多个服务于该UE的SMF均确定为服务于该UE的SMF,NWDAF将该UE与这多个服务于该UE的SMF的关联关系进行保存。
实现方式C,NWDAF从NRF中获取服务于该UE的SMF。
NWDAF可向NRF查询服务于该UE的SMF。示例性地,NWDAF可向NRF发送查询请求。具体地,查询请求中可包括UE的当前状态信息,如UE当前所在的网络位置、时间、UE所在的群组信息、UE所属的公共陆地移动网(public land mobile network,PLMN)、切片信息等。相应地,NRF接收来自NWDAF的查询请求,并可基于该查询请求中UE的当前状态信息确定服务于该UE的SMF。
场景二,NWDAF获取支持某一特性的UPF所对应的用户面数据。在该场景二中,用户面数据为支持某一特性的UPF对应的用户面数据。如下为了便于方案的说明,以支持第一特性的UPF(第一特性即为UPF profile)为例,其中,第一特性即为UPF所支持的某一特性(UPF Profile);将支持第一特性的UPF所对应的用户面数据称为第二用户面数据。应理解,该场景二中的支持第一特性的UPF对应的SMF可能与上述场景一中服务于UE的SMF相同,也可能不相同;支持第一特性的UPF可能与上述场景一中的服务于UE的UPF相同,也可能不相同。
在一种可能的实现方式中,第一特性可包括UPF关联的SMF的信息(例如SMF的名称、SMF的标识或SMF的地址)、UPF支持的应用信息(例如,支持的应用名称或支持的应用标识)、UPF是否支持能力开放服务信息(例如,UPF支持event exposure service)、UPF的服务区域信息(UPF service area)、和UPF服务的用户群组信息中的至少一项。如 表1所示,为本申请提供的一种UPF与所支持的第一特性的关系。
表1一种UPF与所第一特性的关系。
示例性地,若NWDAF需要订阅特定区域范围内的UPF上的所有UE的流量使用情况,则第一特性为特定服务区域(service area)。又如,NWDAF需要订阅支持某个特定应用(application)的UPF上该应用的数据包大小,则第一特性为支持特定应用。又如,NWDAF需要订阅某个用户群组(UE group)对应UPF上相关用户面数据,则第一特性为支持特定群组。
为了获取到支持某一特性的UPF对应的用户面数据,NWDAF需要从支持某一特性的UPF中获取用户面数据,则NWDAF可先向NRF寻址支持第一特定的UPF对应的SMF。本申请中,NWDAF可基于上述第一特性,确定出支持第一特性的UPF对应的SMF。即NWDAF可先向NRF寻址支持第一特性的UPF对应的SMF。如图3b所示,为本申请提供的另一种网元的信息的获取方法的方法流程示意图。该方法示例性地给出了确定支持第一特性的UPF对应的SMF的方法。该方法包括以下步骤:
步骤311,NWDAF向NRF发送第三请求消息。相应地,NRF接收来自NWDAF的第三请求消息。
此处,第三请求消息用于向NRF请求支持第一特性的UPF对应的SMF的信息。进一步,也可以确定出第三请求消息用于指示寻址的对象为SMF(即target NF type=SMF)。在一种可能的实现方式中,第三请求消息可为发现(discover)请求消息。
在一种可能的实现方式中,NWDAF可根据第一特性确定出支持第一特性的UPF对应的SMF所支持的第二特性(第二特性即为SMF profile)。也就是说,NWDAF可根据第一特性生成第二特性。示例性地,第一特性包括公共陆地移动网标识(public land mobile network identification,PLMN ID)1,单网络切片选择支撑信息(single network slice selection assistance information,S-NSSAI)ID 1,服务区域(service area)1,则NWDAF可根据第一特性,生成的第二特性为:PLMN ID 1,S-NSSAI ID1,service area 2(包括service area1)。
在该步骤311中,第三请求消息中可包括第一特性,或者也可包括第二特性,或者也可包括第一特性和第二特性。如下,基于第三请求消息所携带的具体内容(也可称为筛选SMF的条件),分如下三种情形分别详细介绍。
情形A,第三请求消息中包括第一特性。其中,第一特性用于NRF确定支持第一特性的UPF所对应的SMF。
基于该情形A,又可分如下两种情形。
情形A-1,第一特性中包括支持第一特性的UPF关联的SMF的信息,说明UPF在向NRF注册时,将支持第一特性的UPF关联的SMF的信息作为UPF的第一特性也保存于NRF中。可以理解的是,由于SMF负责为UE选择和分配UPF,因此,SMF和UPF之间存在一定的关联关系。比如,某个UPF属于某个SMF管辖。再比如,UPF的服务区域(service area 1)包括于SMF的服务区域(service area 2)。在比如,UPF与SMF在相同的切片中。情形A-1也可以理解为,第三请求消息中包括第一特性,且第一特性包括支持第一特性的UPF关联的SMF的信息。
情形A-2,第一特性中未包括支持第一特性的UPF关联的SMF的信息。也就是说,第三请求消息中包括第一特性,且第一特性中不包括支持第一特性的UPF关联的SMF的信息。
情形B,第三请求消息中包括第二特性。其中,第二特性用于NRF确定支持第二特性的SMF的信息。
情形C,第三请求消息中包括第一特性和第二特性。
基于该情形C,又可分如下两种情形。
情形C-1,第一特性中包括支持第一特性的UPF关联的SMF的信息。即,第三请求消息中包括第一特性和第二特性,且第一特性包括支持第一特性的UPF关联的SMF的信息。
情形C-2,第一特性中未包括支持第一特性的UPF关联的SMF。即,第三请求消息中包括第一特性和第二特性,且第一特性不包括支持第一特性的UPF关联的SMF的信息。
步骤312,NRF根据第三请求消息确定支持第一特性的UPF对应的SMF的信息。
基于上述步骤311中情形A-1,NRF可根据第一特性中包括的支持第一特性的UPF关联的SMF的信息,直接确定出支持第一特性的UPF对应的SMF的信息。
基于上述步骤311中情形A-2,由于NRF可根据第一特性确定出关联的第二特性,进而可根据第二特性确定出支持第一特性的UPF对应的SMF的信息。具体地,NRF可比较第一特性与本地存储的各个SMF的第二特性,将与第一特性存在共性的第二特性所对应的SMF,确定为支持第一特性的UPF对应的SMF。例如,第一特性包括PLMN ID1,S-NSSAI ID 1,service area 1,则NRF从本地存储的全部SMF的第二特性中,找出PLMN ID1,S-NSSAI ID 1,service area 2(包括service area 1)的特性对应的SMF,确定为支持第一特性的UPF对应的SMF。
基于上述步骤311中的情形B,NRF根据第二特性确定支持第一特性的UPF对应的SMF的信息,具体可参考现有技术的介绍,此处不再赘述。
基于上述步骤311中情形C-1,NRF可根据该支持第一特性的UPF关联的SMF,直接确定出支持第一特性的UPF对应的SMF的信息,且确定出的支持第一特性的UPF对应的SMF需支持第二特性。
基于上述步骤311中情形C-2,NRF可根据第二特性确定支持第一特性的UPF对应的SMF的信息。具体可参考现有技术的介绍,此处不再赘述。
步骤313,NRF向NWDAF发送第三响应消息。相应地,NWDAF接收来自NRF的第三响应消息。
其中,第三响应消息包括支持第一特性的UPF对应的SMF的信息。另外,第三响应 消息可为发现(discover)响应消息。
进一步,当第三请求消息中包括第一特性时,NRF还可根据第一特性确定出对应的UPF的信息。相应地,第三响应中也可包括支持第一特性的UPF的信息。
通过上述步骤311至步骤313,实现了NWDAF从支持第一特性的UPF中获取相关的用户面数据,且是NWDAF先通过第一特性确定出SMF,从而有助于避免向不相关的SMF订阅。即限制了订阅的SMF的范围,可节约信令的开销。
如下基于不同的情形,进一步详细介绍NWDAF获取用户面数据的方法。
如下以订阅过程为例说明,在订阅过程中,第一标识可为第一事件标识(event ID),第二标识可为第二事件标识。其中,第一标识用于向SMF指示用户面数据的类型,第二标识用于向UPF指示用户面数据的类型。为了便于方案的介绍,将NWDAF和SMF之间的第一标识称为第一事件标识(事件标识也称为事件类型),将UPF和SMF之间的第二标识称为第二事件标识;即第一事件标识用于标识NWDAF和SMF之间的事件,第二事件标识用于标识UPF和SMF之间的事件。进一步,将NWDAF和SMF之间的过滤信息(event filter)称为第一过滤信息,将UPF和SMF之间的过滤信息称为第二过滤信息。
需要说明的是,第一请求消息中可包括第一事件标识,也可包第一过滤信息,或者也可包括第一事件标识和第一过滤信息。如下,为了便于方案的说明,以第一请求消息中包括第一事件标识和第一过滤信息为例说明。
如图4所示,为本申请提供的又一种用户面数据的获取方法流程示意图。该方法包括以下步骤:
步骤411,NWDAF向SMF发送第一请求消息。相应地,SMF接收来自NWDAF的第一请求消息。
该步骤411中,该第一请求消息可以为事件开放订阅(event exposure subscribe)请求消息。其中,第一请求消息还可包括第一事件标识和第一过滤信息。具体可以是NWDAF根据待获取的用户面数据的类型,设置向SMF订阅的第一事件标识和第一过滤信息。
基于上述场景一,NWDAF需要获取某一UE关联的用户面数据。例如某一UE在某个区域某段时间内流量使用情况,则NWDAF可设置第一事件标识为流量使用报告(traffic usage report),可设置第一过滤信息为{时间信息(time),区域信息(area),UE标识(UE ID)}等其它可能的过滤信息(other option filter)。再比如,若NWDAF需要获取某一UE的某个应用所对应的业务流的流量比特率的测量值,则NWDAF可设置第一事件标识为流量比特率测量的测量值,可设置第一过滤信息为{应用标识(application ID),UE标识(第一UE ID)}等其它可能的过滤信息(other option filter)。
基于上述场景二,NWDAF需要获取支持第一特性的UPF所对应的数据。例如,NWDAF需要获取某个区域所有UPF某段时间内流量统计情况,则NWDAF可设置第一事件标识为UPF流量测量报告(traffic measurement report),可设置第一过滤信息为{时间信息(time),区域信息(area)}。再比如,若NWDAF需要获取某个应用(application)对应业务流的流量比特率测量的测量值,则NWDAF可设置第一事件标识为流量比特率测量的测量值,第一过滤信息为{应用标识(application ID)}。也可以理解为,NWDAF可根据第一特性生成第一过滤信息。
步骤412,SMF可根据第一请求消息生成第四请求消息。
具体地,第一请求消息中可包括第一事件标识和第一过滤信息。由于第一事件标识与第二事件标识不同,且第一过滤信息与第二过滤信息也不同。因此,SMF需根据第一事件标识确定第二事件标识,根据第一过滤信息确定第二过滤信息。即第四请求消息中包括第二事件标识和第二过滤信息。
在一种可能的实现方式中,SMF可根据第一事件标识与第二事件标识的关联关系,将第二事件标识映射为第一事件标识。类似地,SMF可根据第一过滤信息与第二过滤信息的关联关系,将第一过滤信息映射为第二过滤信息。示例性地,若第一过滤信息中包括UE ID(如SUPI、GPSI),若UPF无法识别SUPI或GPSI,SMF可将UE ID映射为UPF可以识别的UE ID’(如UE IP address)。也就是说,第二过滤信息可包括UE IP address。再比如,第一过滤信息中包括的区域信息,若UPF无法区分UE的位置信息,但可以识别时间信息,因此,SMF可获知UE所在的位置信息,并根据UE所在的位置信息确定出该UE在该位置提供服务的UPF,再确定出UE在该位置的时间范围。即SMF可将第一过滤信息中区域信息映射为服务于UE的UPF和时间信息。也就是说,第二过滤信息可包括服务于UE的UPF和时间信息。
需要说明的是,第一事件标识和第二事件标识也可能相同,第一过滤信息和第二过滤信息也可能相同。当第一事件标识和第二事件标识相同,且第一过滤信息和第二过滤信息也相同时,第一请求消息和第四请求消息相同。
步骤413,SMF向UPF发送第四请求消息。相应地,UPF接收来自SMF的第四请求消息。
在一种可能的实现方式中,第一请求消息中可包括UPF的信息。SMF可根据接收到的第一请求消息中的UPF的信息的确定出提供用户面数据的UPF,从而可向该UPF请求用户面数据。
基于上述场景一,则SMF请求的是UE相关的用户面数据。针对上述场景一,第四请求消息的发送对象UPF的信息是从UDM中获取的,具体过程可参见上述图3a的介绍,此处不再赘述。
若是基于上述场景二,则SMF请求的是支持第一特性的UPF对应的用户面数据。针对上述场景二,确定第四请求消息的发送对象UPF可通过如下三种实现方式。
实现方式Ⅰ,SMF可根据第一请求消息中包含的第一过滤信息确定第四请求消息的发送对象UPF。
由于SMF负责为UE选择和分配UPF,因此,SMF和UPF之间存在一定的关联关系。也就是说,SMF可根据第一过滤信息确定出UPF。例如,SMF执行为特定应用选择的UPF,并保存应用标识与所选UPF的关联关系,则SMF可以根据应用标识映射出对应的UPF。又如,SMF执行为特定的DNN对应PDU session选择UPF,并保存DNN标识与所选UPF的关联关系,则SMF可以根据数据网络名称(data network name,DNN)标识映射出对应的UPF。
实现方式Ⅱ,SMF向NRF查询第一请求中第一过滤信息对应的UPF。
具体可参见现有技术中SMF在UE的PDU会话流程中选择UPF的流程,此处不再赘述。
实现方式Ⅲ,上述第三响应消息中携带UPF的信息(即NWDAF从NRF中获取到UPF的信息)。
结合上述图3b,当第三请求消息中包括第一特性时,NRF还可根据第三请求消息中的第一特性确定出对应的UPF的信息。相应地,NRF向NWDAF发送第三响应消息时,可携带UPF的信息。NWDAF向SMF发送第一请求消息时,可在第一请求消息中携带UPF的信息。
本申请中,SMF可通过如下两种类型的接口向UPF发送第四请求消息。
类型a,SMF与UPF之间的服务化接口。
具体可以是,SMF可通过服务化接口向UPF发送第四请求消息。具体为,SMF通过与UPF之间的服务化接口向UPF发送第四请求消息。在类型a中,第四请求消息可以是事件开放订阅(event exposure-subscribe)消息。
需要说明的是,一个服务化接口可针对某个网络功能网元,该网络功能网元可通过这个服务化接口可向外与其它的网络功能网元进行交互,其它的网络功能网元可通过与该服务化接口相对应的服务化接口与该网络功能网元进行交互。也就是说,每个网络功能网元可通过各自的服务化接口对外提供服务,并允许其他获得授权的网络功能网元访问或调用自身的服务。提供服务的网络功能网元称为服务提供者,访问和调用服务的网络功能网元被称为服务使用者,他们之间可通过订阅请求消息和通知消息的方式进行具体的消息交互。
类型b,SMF与UPF之间的N4接口。
具体可以是,SMF通过N4接口向UPF发送第四请求消息。即SMF通过与UPF之间的N4接口向UPF发送第四请求消息。在类型b中,第四请求消息可以是报文转发控制协议(packet forwarding control protocol,PFCP)会话建立请求(session establishment request)消息。在一种可能的实现方式中,SMF可在使用报告规则(usage report rule,URR)中设置向UPF订阅的第二事件标识以及第二过滤信息等。也就是说,SMF可通过在URR中新增第二事件标识和第二过滤信息等,以实现从UPF中获取用户面数据。具体地,SMF可通过PFCP会话建立请求消息将URR发送至UPF。
需要说明的是,当SMF与UPF之间的同时存在类型a的服务化接口和类型b的N4接口时,可以设置N4接口和服务化接口的之间的优先级。例如,可设置N4接口的优先级高于服务化接口,若SMF确定NWDAF需要获取的用户面数据是N4接口可以提供的,则SMF可通过与UPF之间的N4接口发送第四请求消息。若SMF确定NWDAF需要获取的用户面数据N4接口不能提供,则SMF可通过与UPF之间的服务化接口发送第四请求消息。
本申请中,第四请求消息还可包括目的地址(target address)信息,目的地址信息用于告知UPF上报用户面数据的目的地址,具体目的地址可为NWDAF的地址信息或SMF的地址信息。基于第四请求消息携带的目的地址信息,可分如下三种情形。针对情形1,步骤413之后执行步骤414和步骤415;针对情形2,步骤413之后执行步骤416。
情形1,目的地址信息为SMF的地址信息。
步骤414,UPF向SMF发送用户面数据。相应地,SMF接收来自UPF的用户面数据。
在该情形1中,UPF可按照第二事件标识和第二过滤信息向SMF上报获取的用户面数据。相应地,SMF接收到用户面数据后,可根据第一事件标识与第二事件标识的关联关系,将第二事件标识映射为第一事件标识;以及根据第一过滤信息与第二过滤信息的关联关系,将第二过滤信息映射为第一过滤信息。例如,SMF将UE IP地址列表转换成UE的组标识(group ID),再比如将业务质量流标识(quality of service flow ID,QFI)转换成应 用标识(application ID),再比如将业务质量流标识列表(quality of service flow list)的流比特率测量值(flow bitrate measurement)聚合成PDU session对应的bitrate measurement。
步骤415,SMF向NWDAF发送第一响应消息。相应地,NWDAF接收来自SMF的第一响应消息。
在该步骤415中,第一响应消息包括获取的用户面数据。也就是说,SMF可按照映射后的第一事件标识和第一过滤信息向NWDAF发送第一响应消息。相应地,NWDAF接收到第一响应消息后,可直接获得第一事件标识和第一过滤信息。另外,第一响应消息可为事件开放通知(event exposure notify)响应消息。
需要说明的是,在该情形1中,UPF向SMF发送获取的用户面数据,可以是通过SMF与UPF之间的服务化接口,或者通过SMF与UPF之间的N4接口。具体可参见上述类型a和类型b的介绍,此处不再赘述。另外,由于SMF负责为UE选择和分配UPF,因此,当UE从一个UPF移动到另一个新的UPF,则SMF可以向新的UPF发送第四请求消息,并可取消对原UPF的订阅流程。
情形2,目的地址为NWDAF的地址信息。
步骤416,UPF向NWDAF发送第四响应消息。相应地,NWDAF接收来自UPF的第四响应消息。
基于该情形2,UPF可以将第四响应消息直接上报至NWDAF,无需经过SMF的处理,如此,可减少SMF接收、处理、存储与自身不需要的数据,进而有助于减少SMF的工作量,而且,实现了UPF直接向NWDAF上报用户面数据。
基于上述情形2,又可分如下两种可能情形。
情形2.1,第四请求消息中携带第二事件标识与第一事件标识的关联关系和第二过滤信息与第一过滤信息的关联关系。
在该情形2.1中,在UPF按照第二事件标识和第二过滤信息获取到用户面数据后,可根据第一事件标识与第二事件标识的关联关系,将第二事件标识映射为第一事件标识;以及根据第一过滤信息与第二过滤信息的关联关系,将第二过滤信息映射为第一过滤信息。进一步,UPF可根据第一事件标识和第一过滤信息直接向NWDAF发送获取到的用户面数据,即UPF可直接向NWDAF发送第四响应消息。相应地,NWDAF接收到第四响应消息后,可直接解析出第一事件标识和第一过滤信息。
情形2.2,第四请求消息中未包括第一事件标识与第二事件标识的关联关系和第一过滤信息与第二过滤信息的关联关系。
在该情形2.2中,UPF可按照第二事件标识和第二过滤信息获取到用户面数据后,向NWDAF发送第四响应消息。一种可能的实现方式中,该第四响应消息可包括第一事件标识与第二事件标识的关联关系,以及第一过滤信息与第二过滤信息的关联关系。在另一种可能的实现方式中,也可以是SMF向NWDAF发送第一事件标识与第二事件标识的关联关系,以及第一过滤信息与第二过滤信息的关联关系。基于此,NWDAF接收到第四响应消息后,可根据第一事件标识与第二事件标识的关联关系,将第二事件标识映射为第一事件标识,以及根据第一过滤信息与第二过滤信息的关联关系,将第二过滤信息映射为第一过滤信息。例如,NWDAF将UE IP地址列表转换成UE的组标识(group ID),再比如将业务质量流标识(quality of service flow ID,QFI)转换成应用标识(application ID),再比如将业务质量流标识列表(quality of service flow list)的流比特率测量值(flow bitrate measurement)聚合成PDU session对应的比特率测量值(bitrate measurement)。
需要说明的是,若是基于上述场景一,则上报的用户面数据是UE相关的用户面数据。若是基于上述场景二,则上报的用户面数据是支持第一特性的UPF对应的用户面数据。另外,若NWDAF经SMF向UPF请求用户面数据,如果SMF确定UPF请求用户面数据自身已经通过N4接口或即将通过N4接口从UPF获取,则SMF不再调用UPF的事件开放(event exposure)服务,可直接将自身已经存储的或者未来存储的该用户面数据发送至给SMF。
还需要说明的是,第四请求消息中还可携带上报条件,上报条件用于SMF指示UPF发送第四响应消息的形式,如用于SMF指示UPF周期性上报第四响应消息或者指示UPF基于事件触发上报第四响应消息。另外,第四响应消息可为事件开放通知(event exposure notify)响应消息。
本申请中,NWDAF还可向UPF直接获取用户面数据。如图5所示,为本申请提供的再一种用户面数据的获取方法流程示意图。该方法包括以下步骤:
步骤501,NWDAF向UPF发送第五请求消息。其中,第五请求消息用于向UPF请求用户面数据。
此处,NWDAF可以是通过服务化接口向UPF发送第五请求消息。
步骤502,UPF向NWDAF发送第五响应消息。其中,第五响应消息包括用户面数据。
此处,UPF可以是通过服务化接口向NWDAF发送第五响应消息。
基于图5所示的方案,NWDAF可直接从UPF获取到用户面数据,无需经过SMF的处理,如此,可减少SMF接收、处理、存储与自身不需要的数据,进而有助于减少SMF的工作量,而且,实现了UPF直接向NWDAF上报用户面数据。
本申请中,UE的分组数据单元(packet data unit,PDU)会话(session)建立或修改流程中,服务于UE的SMF向UDM进行注册时,SMF还可将服务于UE的UPF也注册于UDM中。如图6a所示,为本申请提供的一种注册方法,该方法包括以下步骤:
步骤601,SMF接收UE发送的会话建立或修改请求消息。
其中,会话建立或修改请求消息用于请求SMF为UE建立会话。该SMF为服务于UE的SMF。该步骤为可选步骤。
步骤602,SMF向UDM发送第一注册请求消息。相应地,UDM接收来自SMF的第一注册请求。
此处,第一注册请求消息用于请求UDM将服务于UE的UPF的信息保存于UDM。其中,服务于UE的UPF与服务于UE的SMF对应。在某些场景下,服务于UE的SMF可能为多个,例如包括中间SMF和锚点SMF,则此种场景中,可以将每个SMF下服务于UE的UPF信息都注册于UDM中。具体的注册方式不限,例如可以由每个SMF分别向UDM注册其下服务于UE的UPF的信息,也可以由锚点SMF将自身以及所有中间SMF范围下服务于UE的UPF信息注册于UDM中。具体地,第一注册请求消息可包括UPF的信息,例如,UPF的标识、或者UPF的地址、或者UPF的名称。
步骤603,UDM可根据第一注册请求消息,将服务于UE的UPF的信息保存于UDM。
进一步,步骤602中的第一注册请求消息还包括服务于UE的SMF的信息。相应地, 步骤603中,UDM可根据第一注册请求消息,将服务于UE的SMF的信息也保存于UDM。
从上述步骤601至步骤603可以看出,该方法可实现SMF将UPF的信息注册于UDM。
本申请中,服务于UE的UPF也可直接向UDM进行注册。如图6b所示,为本申请提供的另一种注册方法,该方法包括以下步骤:
步骤611,服务于UE的UPF接收服务于该UE的SMF发送的连接建立请求消息。
此处,连接建立请求消息用于请求UPF为UE建立用户面传输隧道。例如,UPF接收SMF发送的PDCP消息请求建立UE的用户面传输隧道。
步骤612,服务于该UE的UPF向UDM发送第一注册请求消息。相应地,UDM接收来自服务于该UE的UPF的第一注册请求消息。
在该步骤中,第一注册请求消息可包括UPF的信息,例如,UPF的标识、或者UPF的地址、或者UPF的名称。
在某些场景下,服务于UE的UPF可能为多个,例如包括中间UPF和锚点UPF,则此种场景中,可以将每个UPF的信息都注册于UDM中。具体的注册方式不限,例如可以由每个服务于UE的UPF分别向UDM注册其自身信息,也可以由服务于UE的锚点UPF将自身以及所有中间UPF的信息注册于UDM中。
步骤613,UDM根据第一注册请求消息,将服务于该UE的UPF的信息保存于UDM。
从上述步骤611至步骤613可以看出,该方法可实现UPF直接向UDM将自身的信息进行注册。
本申请中,UPF也可将支持的第一特性注册于NRF。如图7a所示,为本申请提供的又一种注册方法,该方法包括以下步骤:
步骤701,支持第一特性的UPF向NRF发送第二注册请求消息。
其中,第二注册请求包括UPF支持的第一特性,其中,第一特性可包括UPF关联的SMF的信息(例如SMF的名称、SMF的标识或SMF的地址)、UPF支持的应用信息(例如,支持的应用名称或支持的应用标识)、UPF是否支持能力开放服务信息(例如,UPF event exposure service)、UPF的服务区域信息(UPF service area)、和UPF服务的用户群组信息中的至少一项。该步骤701也可理解为,UPF将自身支持的第一特性注册于NRF中。
步骤702,NRF根据第二注册请求消息,将第一特性保存于NRF。
通过上述步骤701和步骤702,可将UPF的第一特性注册到NRF中,便于NRF存储和管理UPF。而且,也可以便于后续其它网元根据第一特性确定出支持第一特性的UPF对应的SMF。而且,第一特性中包括UPF关联的SMF的信息,如此,当NWDAF需要从支持第一特性的UPF中获取相关的用户面数据时,NWDAF先快速的确定出第一特性的UPF对应的SMF,从而有助于避免向不相关的SMF订阅,可节约信令的开销。
如图7b所示,为本申请提供的另一种注册方法,该方法包括以下步骤:
步骤711,支持第二特性的SMF向NRF发送第三注册请求消息。
其中,第三注册请求消息中包括第二特性。也就是说,SMF将自身支持的第二特性注册于NRF中。
步骤712,NRF根据第三注册请求消息,将SMF所支持的第二特性保存于NRF。
通过上述步骤711和步骤712,可将支持第二特性的SMF的第二特性注册于NRF中, 便于NRF存储和管理SMF。而且,也可以便于后续其它网元根据第二特性确定出SMF。
需要说明的是,本身申请中,图3a所示的确定UPF的信息的方法可独立于图2所示的用户面数据的获取方法。或者,图2所示的用户面数据的获取方法可以是基于图3a所示的确定UPF的信息的方法来实现。类似地,图3b所示的确定支持第一特性的UPF对应的SMF方法可独立于图2所示的用户面数据的获取方法。或者,图2所示的用户面数据的获取方法可以是基于图3b所示的确定支持第一特性的UPF对应的SMF方法来实现。
基于上述内容和相同构思,参考图8所示,为本申请提供的一种通信装置示意图。该通信装置用于执行上述方法流程中的第一网元、会话管理功能网元、数据管理网元、网络存储功能网元或用户面功能网元侧的任一个方案。该示例中的通信装置800可以包括:处理器801和收发器802。可选地,还可包括存储器803和通信线路804。其中,处理器801和收发器802以及存储器803可以通过通信线路804相互连接;通信线路804可以是外设部件互连标准(peripheral component interconnect,简称PCI)总线或扩展工业标准结构(extended industry standard architecture,简称EISA)总线等。通信线路804可以分为地址总线、数据总线、控制总线等。为便于表示,图8中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
处理器801可以是一个CPU,微处理器,ASIC,或一个或多个用于控制本申请方案程序执行的集成电路。
收发器802,使用任何收发器一类的装置,用于与其他设备或通信网络通信,如以太网,无线接入网(radio access network,RAN),无线局域网(wireless local area networks,WLAN),有线接入网等。可选地,收发器802可以为通信接口,通信接口可实现上述实施例中N4接口或服务化接口的功能。
存储器803可以是只读存储器(read-only memory,ROM)或可存储静态信息和指令的其他类型的静态存储设备,随机存取存储器(random access memory,RAM)或者可存储信息和指令的其他类型的动态存储设备,也可以是电可擦可编程只读存储器(electrically er服务器able programmable read-only memory,EEPROM)、只读光盘(compact disc read-only memory,CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。存储器可以是独立存在,通过通信线路804与处理器相连接。存储器也可以和处理器集成在一起。
其中,存储器803用于存储执行本申请方案的计算机执行指令,并由处理器801来控制执行。处理器801用于执行存储器803中存储的计算机执行指令,从而实现本申请上述实施例提供的用户面数据的获取方法。
可选的,本申请实施例中的计算机执行指令也可以称之为应用程序代码,本申请实施例对此不作具体限定。
在第一种应用中,该通信装置800可以是第一网元,第一网元包括:
收发器802,用于向会话管理功能网元发送第一请求消息,第一请求消息用于指示会话管理功能网元请求用户面功能网元提供用户面数据。处理器801,用于获取来自用户面 功能网元的用户面数据。
当用户面数据为终端设备相关的用户面数据时;收发器802,还用于向数据管理网元发送第二请求消息,第二请求消息用于向数据管理网元请求服务于终端设备的用户面功能网元的信息;并接收来自数据管理网元的第二响应消息,第二响应消息包括用户面功能网元的信息。
当用户面数据为支持第一特性的用户面功能网元所对应的数据时;收发器802,还用于向网络存储功能网元发送第三请求消息,第三请求消息用于向网络存储功能网元请求用户面功能网元对应的会话管理功能网元的信息;并接收来自网络存储功能网元的第三响应消息,第三响应消息包括会话管理功能网元的信息。
在一种可能的实现方式中,第一请求消息可包括用户面功能网元的信息。
在一种可能的实现方式中,收发器802,具体用于接收会话管理功能网元发送的第一响应消息,第一响应消息包括用户面数据;或者,接收用户面功能网元发送的第四响应消息,第四响应消息包括第一用户面数据;其中,第四响应消息是用户面功能网元接收会话管理功能网元发送的第四请求消息后向第一网元发送的,第四请求消息是会话管理功能网元根据第一请求消息生成的。
在一种可能的实现方式中,第一请求消息可包括第一标识,第一标识用于向会话管理功能网元指示用户面数据的类型,第四请求消息可包括第二标识,第二标识用于向用户面功能网元指示用户面数据的类型;第四响应消息还可包括第二标识;处理器801,具体用于根据第一标识与第二标识的关联关系,将第二标识映射为第一标识。
其中,第二标识与第一标识的关联关系可以携带于第四响应消息中。
在一种可能的实现方式中,第一请求消息还可包括第一过滤信息,第四请求消息还可包括第二过滤信息,第四响应消息还可包括第二过滤信息;处理器801,具体用于根据第一过滤信息与第二过滤信息的关联关系,将第二过滤信息映射为第一过滤信息。
其中,第二过滤信息与第一过滤信息的关联关系也可携带与第四响应消息中。
所述处理器801,还用于从数据管理网元获取会话管理功能网元的信息,会话管理功能网元服务于终端设备。
在一种可能的实现方式中,第三请求消息中包括第一特性。
在一种可能的实现方式中,第三响应消息还包括用户面功能网元的信息。
在一种可能的实现方式中,处理器801,还用于根据第一特性确定会话管理功能网元支持的第二特性。其中,第三请求消息中还包括第二特性。
示例性地,第一特性包括用户面功能网元关联的会话管理功能网元的信息、用户面功能网元支持的应用信息、用户面功能网元是否支持能力开放服务信息、用户面功能网元的服务区域信息以及用户面功能网元服务的用户群组信息中的至少一项。
在第二种应用中,该通信装置800可以是数据管理网元,该数据管理网元包括:
处理器801和收发器802协作,用于接收来自第一网元的第二请求消息,第二请求消息用于向数据管理网元请求服务于终端设备的用户面功能网元的信息;并向第一网元发送第二响应消息,第二响应消息包括用户面功能网元的信息。
在一种可能的实现方式中,第二请求消息还用于向数据管理网元请求服务于终端设备的会话管理功能网元的信息,第二响应消息还包括会话管理功能网元的信息。
在一种可能的实现方式中,收发器802,还用于接收来自会话管理功能网元和/或用户 面功能网元的第一注册请求消息,第一注册请求消息包括用户面功能网元的信息。处理器801,还用于根据第一注册请求消息,将用户面功能网元的信息保存于数据管理网元。
在一种可能的实现方式中,第一注册请求消息中还包括会话管理功能网元的信息;处理器801,具体用于根据第一注册请求消息,将会话管理功能网元的信息保存于数据管理网元。
在第三种应用中,该通信装置800可以是网络存储功能网元,该网络存储功能网元包括:
收发器802,用于接收来自第一网元的第三请求消息,第三请求消息用于向网络存储功能网元请求用户面功能网元对应的会话管理功能网元的信息,第三请求消息包括用户面功能网元支持的第一特性。处理器801,用于根据第三请求消息确定会话管理功能网元的信息。收发器802,还用于向第一网元发送第三响应消息,第三响应消息包括会话管理功能网元的信息。
在一种可能的实现方式中,收发器802,还用于接收用户面功能网元发送的第二注册请求消息,第二注册请求消息中包括第一特性。处理器801,还用于根据第二注册请求消息,将用户面功能网元支持的第一特性保存于网络存储功能网元。
在一种可能的实现方式中,处理器801,具体用于根据第一特性确定会话管理功能网元支持的第二特性,并根据第二特性确定会话管理功能网元的信息。
在一种可能的实现方式中,收发器802,还用于接收会话管理功能网元发送的第三注册请求消息,第三注册请求消息中包括第二特性。处理器801,还用于根据第三注册请求消息,将第二特性保存于网络存储功能网元。
在一种可能的实现方式中,第一特性包括用户面功能网元关联的会话管理功能网元的信息、用户面功能网元支持的应用信息、用户面功能网元是否能力开放服务信息、用户面功能网元的服务区域信息、以及用户面功能网元服务的用户群组信息中的至少一项。
在一种可能的实现方式中,处理器801,具体用于确定第一特性包括用户面功能网元关联的会话管理功能网元的信息;并根据用户面功能网元关联的会话管理功能网元的信息,确定会话管理功能网元的信息。
在第四种应用中,该通信装置800可以是会话管理功能网元,该会话管理功能网元包括:
收发器802,用于接收来自第一网元的第一请求消息,第一请求消息用于指示会话管理功能网元请求用户面功能网元提供用户面数据,第一请求消息包括第一标识,第一标识用于向会话管理功能网元指示用户面数据的类型。处理器801,用于根据第一标识确定第四请求消息包括的第二标识,第二标识用于向用户面功能网元指示用户面数据的类型。收发器802,还用于向用户面功能网元发送第四请求消息,第四请求消息用于向用户面功能网元请求用户面数据。
在一种可能的实现方式中,第一请求消息还包括第一用户面功能网元的信息。
在一种可能的实现方式中,第一请求消息还包括第一过滤信息;处理器801,具体用于根据第一过滤信息确定第四请求消息包括的第二过滤信息。
在一种可能的实现方式中,第四请求消息还包括目的地址信息,目的地址信息用于告知用户面功能网元上报用户面数据的目的地址,目的地址信息为第一网元的地址信息或会话管理功能网元的地址信息。
若目的地址为会话管理功能网元的地址信息,收发器802,还用于向第一网元发送第一响应消息,第一响应消息包括用户面数据。
在一种可能的实现方式中,收发器802具体可以是服务化接口或者N4接口,即可通过服务化接口向用户面功能网元发送第四请求消息;或者,通过N4接口向用户面功能网元发送第四请求消息。
在第五种应用中,该通信装置800可以是会话管理功能网元,该会话管理功能网元包括:
收发器802,用于接收终端设备发送的会话建立请求消息,会话建立请求消息用于请求会话管理功能网元为终端设备建立会话;并向数据管理网元发送第一注册请求消息,第一注册请求消息包括服务于终端设备的用户面功能网元的信息;其中,第一注册请求消息用于请求数据管理网元将用户面功能网元的信息保存于数据管理网元。
在一种可能的实现方式中,第一注册请求消息还包括会话管理功能网元的信息,第一注册请求还用于数据管理网元将会话管理功能网元的信息保存于数据管理网元。
在第六种应用中,该通信装置800可以是用户面功能网元,该用户面功能网元包括:
处理器801和收发器802协作,用于接收来自第一网元的第五请求消息,第五请求消息用于向用户面功能网元请求用户面数据;并向第一网元发送第五响应消息,第五响应消息包括用户面数据。
在一种可能的实现方式中,收发器802可以为服务化接口,具体可通过服务化接口接收来自第一网元的第五请求消息。
在一种可能的实现方式中,收发器802可以为服务化接口,具体可通过服务化接口向第一网元发送第五响应消息。
在第七种应用中,该通信装置800可以是用户面功能网元,该用户面功能网元包括:
处理器801和收发器802协作,用于接收来自会话管理功能网元的第四请求消息,第四请求消息用于向用户面功能网元请求用户面数据;并向第一网元发送第四响应消息,第四响应消息包括用户面数据。
在一种可能的实现方式中,第四请求消息还包括的目地址信息,目的地址信息为第一网元的地址信息。收发器802,可具体用于根据目的地址信息向第一网元发送第四响应消息。
在一种可能的实现方式中,收发器802可以为服务化接口,具体可通过服务化接口向第一网元发送第四响应消息。
在一种可能的实现方式中,目的地址信息还可以为会话管理功能网元的地址信息;收发器802,可具体用于根据目的地址信息向会话管理功能网元发送第四响应消息。
在一种可能的实现方式中,收发器802具体可以是服务化接口或者N4接口,即可通过服务化接口向会话管理功能网元发送第四响应消息;或者,通过N4接口向会话管理功能网元发送第四响应消息。
在一种可能的实现方式中,第四请求消息中还包括第一标识与第二标识的关联关系,第一标识用于向会话管理功能网元指示用户面数据的类型,第二标识用于向用户面功能网元指示用户面数据的类型;处理器801,具体用于根据第一标识与第二标识的关联关系,将第二标识映射为第一标识。
在一种可能的实现方式中,第四请求消息中还包括第一过滤信息与第二过滤信息的关 联关系;处理器801,具体用于能根据第一过滤信息与第二过滤信息的关联关系,将第二过滤信息映射为第一过滤信息。
在一种可能的实现方式中,第四响应消息还包括第一标识与第二标识的关联关系,和/或,第一过滤信息与第二过滤信息关联关系。
在第八种应用中,该通信装置800可以是用户面功能网元,该用户面功能网元包括:
收发器802,接收会话管理功能网元发送的连接建立请求消息,连接建立请求消息用于请求用户面功能网元为终端设备建立用户面传输隧道;并向数据管理网元发送第一注册请求消息,第一注册请求消息包括服务于终端设备的用户面功能网元的信息;其中,第一注册请求消息用于请求数据管理网元将用户面功能网元的信息保存于数据管理网元。
在第九种应用中,该通信装置800可以是用户面功能网元,该用户面功能网元包括:
收发器802,向网络存储功能网元发送第二注册请求消息,第二注册请求消息包括用户面功能网元支持的第一特性,第二注册请求消息用于请求网络存储功能网元保存第一特性。
其中,第一特性包括:用户面功能网元关联的会话管理功能网元的信息、用户面功能网元支持的应用信息、用户面功能网元是否能力开放服务信息、用户面功能网元的服务区域信息、以及用户面功能网元服务的用户群组信息中的至少一项。
基于上述内容和相同构思,本申请提供一种通信装置,用于执行上述方法流程中的第一网元、会话管理功能网元、数据管理网元、网络存储功能网元或用户面功能网元侧的任一个方案。图9示例性示出了本申请提供的一种通信装置的结构示意图。该示例中的通信装置900可以包括:处理单元901和收发单元902。处理单元901用于对通信装置900的动作进行控制管理。收发单元902用于支持通信装置900与其他网络实体的通信。通信装置900还可以包括存储单元903,用于存储通信装置900的程序代码和数据。
其中,处理单元901可以是处理器或控制器,例如可以是通用中央处理器(central processing unit,CPU),通用处理器,数字信号处理(digital signal processing,DSP),专用集成电路(application specific integrated circuits,ASIC),现场可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。处理器也可以是实现计算功能的组合,例如包括一个或多个微处理器组合,DSP和微处理器的组合等等。收发单元902可以是通信接口、收发器或收发电路等,其中,该通信接口是统称,在具体实现中,该通信接口可以包括多个接口。存储单元903可以是存储器。
应理解,以上各通信装置的单元的划分仅仅是一种逻辑功能的划分,实际实现时可以全部或部分集成到一个物理实体上,也可以物理上分开。本申请中,处理单元901可以由上述图8的处理器801实现,收发单元902可以由上述图8的收发器802实现。也就是说,本申请中收发单元902可以执行上述图8的收发器802所执行的方案,本申请中处理单元901可以执行上述图8的处理器801所执行的方案,其余内容可以参见上述内容,在此不再赘述。如上述图8所示,通信装置800包括的存储器803中可以用于存储该通信装置800包括的处理器801执行方案时的代码,该代码可为通信装置800出厂时预装的程序/代码。
基于上述内容和相同构思,本申请提供一种通信系统。该通信系统可包括上述第一网元、以及、会话管理功能网元。第一网元可执行第一网元侧任意方法,会话管理功能网元可执行会话管理功能网元侧任意方法。第一网元和会话管理功能网元可能的实现方式可参见上述介绍,此处不再赘述。
在一种可能的实现方式中,该通信系统还可包括用户面功能网元和数据管理网元。其中,第一网元可执行上述图2、图3a、图4或图5所示的第一网元侧的任意方法,会话管理功能网元可执行上述图2、图4、6a或6b所示的会话管理功能网元侧的任意方法,用户面功能网元可执行上述图2、图4、图5或图6b所示的用户面功能网元侧的任意方法,数据管理网元可执行上述图3a、6a或6b所示的数据管理网元侧任意的方法,用户面功能网元和数据管理网元可能的实现方式可参见上述介绍,此处再赘述。
在另一种可能的实现方式中,该通信系统还可包括用户面功能网元和网络存储功能网元。第一网元可执行上述图2、图3b、图4或图5所示的第一网元侧的任意方法,会话管理功能网元可执行上述图2、图4或图7a所示的会话管理功能网元侧的任意方法,用户面功能网元可执行上述图2、图4、图5或图7b所示的用户面功能网元侧的任意方法,网络存储功能网元可执行上述图3b、图7a或图7b所示的网络存储功能网元侧任意的方法,用户面功能网元和网络存储功能网元可能的实现方式可参见上述介绍,此处再赘述。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现、当使用软件程序实现时,可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个指令。在计算机上加载和执行计算机程序指令时,全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。指令可以存储在计算机存储介质中,或者从一个计算机存储介质向另一个计算机存储介质传输,例如,指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质,(例如,软盘、硬盘、磁带、磁光盘(MO)等)、光介质(例如,CD、DVD、BD、HVD等)、或者半导体介质(例如ROM、EPROM、EEPROM、非易失性存储器(NAND FLASH)、固态硬盘(Solid State Disk,SSD))等。
本领域内的技术人员应明白,本申请实施例可提供为方法、系统、或计算机程序产品。因此,本申请实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本申请实施例可采用在一个或多个其中包括有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请实施例是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包括这些改动和变型在内。
Claims (31)
- 一种用户面数据的获取方法,其特征在于,包括:第一网元向会话管理功能网元发送第一请求消息,所述第一请求消息用于指示所述会话管理功能网元请求用户面功能网元提供用户面数据;所述第一网元获取来自所述用户面功能网元的所述用户面数据。
- 如权利要求1所述的方法,其特征在于,所述用户面数据为终端设备相关的用户面数据;所述方法还包括:所述第一网元向数据管理网元发送第二请求消息,所述第二请求消息用于向所述数据管理网元请求服务于所述终端设备的所述用户面功能网元的信息;所述第一网元接收来自所述数据管理网元的第二响应消息,所述第二响应消息包括所述用户面功能网元的信息。
- 如权利要求1所述的方法,其特征在于,所述用户面数据为支持第一特性的用户面功能网元所对应的数据;所述方法还包括:所述第一网元向网络存储功能网元发送第三请求消息,所述第三请求消息用于向所述网络存储功能网元请求所述用户面功能网元对应的所述会话管理功能网元的信息;所述第一网元接收来自所述网络存储功能网元的第三响应消息,所述第三响应消息包括所述会话管理功能网元的信息。
- 如权利要求1至3任一所述的方法,其特征在于,所述第一请求消息包括所述用户面功能网元的信息。
- 如权利要求1至4任一项所述的方法,其特征在于,所述第一网元获取来自所述用户面功能网元的所述用户面数据,包括:所述第一网元接收所述会话管理功能网元发送的第一响应消息,所述第一响应消息包括所述用户面数据;或者,所述第一网元接收所述用户面功能网元发送的第四响应消息,所述第四响应消息包括所述第一用户面数据;其中,所述第四响应消息是所述用户面功能网元接收所述会话管理功能网元发送的第四请求消息后向所述第一网元发送的,所述第四请求消息是所述会话管理功能网元根据所述第一请求消息生成的。
- 如权利要求5所述的方法,其特征在于,所述第一请求消息包括第一标识,所述第一标识用于向所述会话管理功能网元指示所述用户面数据的类型,所述第四请求消息包括第二标识,所述第二标识用于向所述用户面功能网元指示所述用户面数据的类型;所述第四响应消息还包括所述第二标识;所述方法还包括:所述第一网元根据第一标识与第二标识的关联关系,将所述第二标识映射为所述第一标识。
- 如权利要求6所述的方法,其特征在于,所述第四响应消息还包括所述第二标识与第一标识的关联关系。
- 如权利要求4至7任一项所述的方法,其特征在于,所述第一请求消息还包括第 一过滤信息,所述第四请求消息还包括第二过滤信息,所述第四响应消息还包括所述第二过滤信息;所述方法还包括:所述第一网元根据第一过滤信息与第二过滤信息的关联关系,将所述第二过滤信息映射为所述第一过滤信息。
- 如权利要求8所述的方法,其特征在于,所述第四响应消息还包括所述第二过滤信息与第一过滤信息的关联关系。
- 如权利要求1或2所述的方法,其特征在于,所述方法还包括:所述第一网元从所述数据管理网元获取所述会话管理功能网元的信息,所述会话管理功能网元服务于所述终端设备。
- 如权利要求3所述的方法,其特征在于,所述第三请求消息中包括所述第一特性。
- 如权利要求3或11所述的方法,其特征在于,所述第三响应消息还包括所述用户面功能网元的信息。
- 如权利要求3、11或12所述的方法,其特征在于,所述方法还包括:所述第一网元根据所述第一特性确定所述会话管理功能网元支持的第二特性;所述第三请求消息中还包括所述第二特性。
- 如权利要求3、11至13任一项所述的方法,其特征在于,所述第一特性包括以下内容中至少一项:所述用户面功能网元关联的会话管理功能网元的信息、所述用户面功能网元支持的应用信息、所述用户面功能网元是否支持能力开放服务信息、所述用户面功能网元的服务区域信息、所述用户面功能网元服务的用户群组信息。
- 一种通信装置,其特征在于,包括收发单元和处理单元:所述收发单元,用于向会话管理功能网元发送第一请求消息,所述第一请求消息用于指示所述会话管理功能网元请求用户面功能网元提供用户面数据;所述处理单元,用于获取来自所述用户面功能网元的所述用户面数据。
- 如权利要求15所述的通信装置,其特征在于,所述用户面数据为终端设备相关的用户面数据;所述收发单元,还用于向数据管理网元发送第二请求消息,以及接收来自所述数据管理网元的第二响应消息,所述第二请求消息用于向所述数据管理网元请求服务于所述终端设备的所述用户面功能网元的信息,所述第二响应消息包括所述用户面功能网元的信息。
- 如权利要求15所述的通信装置,其特征在于,所述用户面数据为支持第一特性的用户面功能网元所对应的数据;所述收发单元,还用于向网络存储功能网元发送第三请求消息,以及接收来自所述网络存储功能网元的第三响应消息,所述第三响应消息包括所述会话管理功能网元的信息,所述第三请求消息用于向所述网络存储功能网元请求所述用户面功能网元对应的会话管理功能网元的信息。
- 如权利要求15至17任一所述的通信装置,其特征在于,所述第一请求消息包括所述用户面功能网元的信息。
- 如权利要求15至18任一项所述的通信装置,其特征在于,所述收发单元,具体用于:接收所述会话管理功能网元发送的第一响应消息,所述第一响应消息包括所述用户面数据;或者,接收所述用户面功能网元发送的第四响应消息,所述第四响应消息包括所述第一用户面数据;其中,所述第四响应消息是所述用户面功能网元接收所述会话管理功能网元发送的第四请求消息后向所述第一网元发送的,所述第四请求消息是所述会话管理功能网元根据所述第一请求消息生成的。
- 如权利要求19所述的通信装置,其特征在于,所述第一请求消息包括第一标识,所述第一标识用于向所述会话管理功能网元指示所述用户面数据的类型,所述第四请求消息包括第二标识,所述第二标识用于向所述用户面功能网元指示所述用户面数据的类型;所述第四响应消息还包括所述第二标识;所述处理单元,还用于:根据第一标识与第二标识的关联关系,将所述第二标识映射为所述第一标识。
- 如权利要求20所述的通信装置,其特征在于,所述第四响应消息还包括所述第二标识与第一标识的关联关系。
- 如权利要求18至21任一项所述的通信装置,其特征在于,所述第一请求消息还包括第一过滤信息,所述第四请求消息还包括第二过滤信息,所述第四响应消息还包括所述第二过滤信息;所述处理单元,还用于:根据第一过滤信息与第二过滤信息的关联关系,将所述第二过滤信息映射为所述第一过滤信息。
- 如权利要求22所述的通信装置,其特征在于,所述第四响应消息还包括所述第二过滤信息与第一过滤信息的关联关系。
- 如权利要求15或16所述的通信装置,其特征在于,所述处理单元,还用于:从所述数据管理网元获取所述会话管理功能网元的信息,所述会话管理功能网元服务于所述终端设备。
- 如权利要求17所述的通信装置,其特征在于,所述第三请求消息中包括所述第一特性。
- 如权利要求17或25所述的通信装置,其特征在于,所述第三响应消息还包括所述用户面功能网元的信息。
- 如权利要求17、25或26所述的通信装置,其特征在于,所述处理单元,还用于:根据所述第一特性确定所述会话管理功能网元支持的第二特性;所述第三请求消息中还包括所述第二特性。
- 如权利要求17、25至27任一项所述的通信装置,其特征在于,所述第一特性包括以下内容中至少一项:所述用户面功能网元关联的会话管理功能网元的信息、所述用户面功能网元支持的应用信息、所述用户面功能网元是否支持能力开放服务信息、所述用户面功能网元的服务区域信息、所述用户面功能网元服务的用户群组信息。
- 一种计算机可读存储介质,其特征在于,包括指令,当其在计算机上运行时,使得计算机执行如权利要求1~14任一的方法。
- 一种计算机程序产品,其特征在于,包括指令,当所述指令在计算机上运行时, 使得所述计算机执行如权利要求1~14任一的方法。
- 一种通信系统,其特征在于,包括如权利要求15-28中任意一项所述的通信装置和用于与所述通信装置进行通信的会话管理功能网元。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP20847206.8A EP3996408A4 (en) | 2019-07-26 | 2020-06-23 | METHOD AND DEVICE FOR DATA COLLECTION AT USER LEVEL AND STORAGE MEDIUM |
US17/585,254 US20220150685A1 (en) | 2019-07-26 | 2022-01-26 | User plane data obtaining method, apparatus, and storage medium |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910683670.0A CN112312418A (zh) | 2019-07-26 | 2019-07-26 | 一种用户面数据的获取方法、装置及存储介质 |
CN201910683670.0 | 2019-07-26 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/585,254 Continuation US20220150685A1 (en) | 2019-07-26 | 2022-01-26 | User plane data obtaining method, apparatus, and storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021017689A1 true WO2021017689A1 (zh) | 2021-02-04 |
Family
ID=74230079
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/097769 WO2021017689A1 (zh) | 2019-07-26 | 2020-06-23 | 一种用户面数据的获取方法、装置及存储介质 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20220150685A1 (zh) |
EP (1) | EP3996408A4 (zh) |
CN (1) | CN112312418A (zh) |
WO (1) | WO2021017689A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114189885A (zh) * | 2021-09-27 | 2022-03-15 | 阿里巴巴达摩院(杭州)科技有限公司 | 网元信息处理方法、设备及存储介质 |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2593979B (en) * | 2020-03-20 | 2022-09-14 | Samsung Electronics Co Ltd | Improvements in and relating to data analytics in a telecommunication network |
CN112969199B (zh) * | 2021-02-24 | 2023-05-26 | 中国联合网络通信集团有限公司 | 一种数据采集方法和设备 |
CN115250466A (zh) * | 2021-04-26 | 2022-10-28 | 中国移动通信有限公司研究院 | 用户数据容灾方法、装置、网元设备及存储介质 |
CN115277583A (zh) * | 2021-04-30 | 2022-11-01 | 华为技术有限公司 | 一种业务流识别方法及装置 |
CN115955716A (zh) * | 2021-10-08 | 2023-04-11 | 华为技术有限公司 | 数据收集方法、通信装置及通信系统 |
CN116567801A (zh) * | 2022-01-28 | 2023-08-08 | 维沃移动通信有限公司 | 服务化用户面的注册方法、装置、通信设备、系统及存储介质 |
CN116828443A (zh) * | 2022-03-21 | 2023-09-29 | 维沃移动通信有限公司 | 数据采集方法及通信设备 |
WO2023179672A1 (zh) * | 2022-03-25 | 2023-09-28 | 维沃移动通信有限公司 | 用户面功能网元确定方法及装置 |
CN117062105A (zh) * | 2022-05-06 | 2023-11-14 | 中国移动通信有限公司研究院 | 一种通信方法、装置、网络功能和存储介质 |
CN115474189B (zh) * | 2022-08-18 | 2023-09-01 | 广州爱浦路网络技术有限公司 | 通知数据采集方法、通信核心网、计算机装置及存储介质 |
CN115297020A (zh) * | 2022-08-24 | 2022-11-04 | 中国电信股份有限公司 | 通信控制方法及装置、电子设备、存储介质 |
CN117835359A (zh) * | 2022-09-29 | 2024-04-05 | 大唐移动通信设备有限公司 | 路径选择方法、信息上报方法及装置 |
CN118158235A (zh) * | 2022-12-05 | 2024-06-07 | 大唐移动通信设备有限公司 | 算网融合方法、装置及存储介质 |
WO2024130602A1 (zh) * | 2022-12-21 | 2024-06-27 | Oppo广东移动通信有限公司 | 通信方法、装置、设备、存储介质、芯片、产品及程序 |
WO2024083417A1 (en) * | 2023-07-28 | 2024-04-25 | Lenovo (Singapore) Pte. Ltd | Privacy protection in a wireless communication network |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108632307A (zh) * | 2017-03-17 | 2018-10-09 | 电信科学技术研究院 | 一种会话连接建立方法以及smf |
CN109121170A (zh) * | 2017-06-26 | 2019-01-01 | 华为技术有限公司 | 会话管理的方法、装置、设备及系统 |
CN109996346A (zh) * | 2017-12-29 | 2019-07-09 | 华为技术有限公司 | 会话建立方法、设备及系统 |
CN110049508A (zh) * | 2018-01-15 | 2019-07-23 | 华为技术有限公司 | 一种获取业务数据的方法及装置 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10986516B2 (en) * | 2017-03-10 | 2021-04-20 | Huawei Technologies Co., Ltd. | System and method of network policy optimization |
CN108632904B (zh) * | 2017-03-24 | 2019-09-17 | 电信科学技术研究院 | 一种通信方法及设备 |
CN109600759B (zh) * | 2017-09-30 | 2022-04-29 | 华为技术有限公司 | 一种策略确定的方法及通信装置 |
EP3777344A1 (en) * | 2018-04-06 | 2021-02-17 | Convida Wireless, LLC | Methods of managing connections to a local area data network (ladn) in a 5g network |
AU2018418065A1 (en) * | 2018-04-13 | 2020-11-26 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method and device for establishing transmission path |
WO2020207607A1 (en) * | 2019-04-11 | 2020-10-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Optimization of services applied to data packet sessions |
-
2019
- 2019-07-26 CN CN201910683670.0A patent/CN112312418A/zh active Pending
-
2020
- 2020-06-23 EP EP20847206.8A patent/EP3996408A4/en active Pending
- 2020-06-23 WO PCT/CN2020/097769 patent/WO2021017689A1/zh unknown
-
2022
- 2022-01-26 US US17/585,254 patent/US20220150685A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108632307A (zh) * | 2017-03-17 | 2018-10-09 | 电信科学技术研究院 | 一种会话连接建立方法以及smf |
CN109121170A (zh) * | 2017-06-26 | 2019-01-01 | 华为技术有限公司 | 会话管理的方法、装置、设备及系统 |
CN109996346A (zh) * | 2017-12-29 | 2019-07-09 | 华为技术有限公司 | 会话建立方法、设备及系统 |
CN110049508A (zh) * | 2018-01-15 | 2019-07-23 | 华为技术有限公司 | 一种获取业务数据的方法及装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3996408A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114189885A (zh) * | 2021-09-27 | 2022-03-15 | 阿里巴巴达摩院(杭州)科技有限公司 | 网元信息处理方法、设备及存储介质 |
CN114189885B (zh) * | 2021-09-27 | 2024-01-12 | 阿里巴巴达摩院(杭州)科技有限公司 | 网元信息处理方法、设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN112312418A (zh) | 2021-02-02 |
EP3996408A1 (en) | 2022-05-11 |
US20220150685A1 (en) | 2022-05-12 |
EP3996408A4 (en) | 2022-08-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021017689A1 (zh) | 一种用户面数据的获取方法、装置及存储介质 | |
US11381956B2 (en) | Obtaining of UE policy | |
WO2020147760A1 (zh) | 一种局域网通信方法、装置及系统 | |
KR102224248B1 (ko) | 통신 시스템에서 PDU(Protocol Data Unit) 세션을 설립하는 방법 | |
WO2020001171A1 (zh) | 一种网络切片的资源分配方法及装置 | |
US11172405B2 (en) | Method for checking change in wireless connection type of terminal in third-party application server | |
US20220103990A1 (en) | Communication Method, Apparatus, and System | |
WO2020108002A1 (zh) | 一种传输策略确定方法、策略控制方法及装置 | |
EP3984306B1 (en) | Methods and apparatuses for logical tsn bridge | |
WO2021051420A1 (zh) | 一种dns缓存记录的确定方法及装置 | |
US20210153157A1 (en) | Method and apparatus for improving network slice control accuracy in wireless communication system | |
WO2022068771A1 (zh) | 一种通信方法及通信装置 | |
WO2023213177A1 (zh) | 一种通信方法及装置 | |
US9756597B1 (en) | User equipment (UE) attachment to multiple mobility management entities (MMES) for multiple data services | |
EP4090083A1 (en) | Communication method, apparatus, and system | |
US20230037402A1 (en) | Communication method, apparatus, and system | |
US20230247686A1 (en) | Apparatus and method for supporting slice interworking | |
WO2021218244A1 (zh) | 通信方法、装置及系统 | |
US20230104162A1 (en) | Using dnai to identify a smf supporting connection to a local dn | |
WO2021138784A1 (zh) | 一种接入网络的方法、装置及系统 | |
WO2021147105A1 (zh) | 通信方法及装置 | |
WO2021081712A1 (zh) | 一种dns查询方法及装置 | |
WO2021081915A1 (zh) | 通信方法、装置及系统 | |
WO2023061207A1 (zh) | 一种通信方法、通信装置及通信系统 | |
WO2021164428A1 (zh) | 通信方法、装置及系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20847206 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2020847206 Country of ref document: EP Effective date: 20220204 |