WO2019223498A1 - 一种数据处理方法、发送方法及装置 - Google Patents

一种数据处理方法、发送方法及装置 Download PDF

Info

Publication number
WO2019223498A1
WO2019223498A1 PCT/CN2019/084816 CN2019084816W WO2019223498A1 WO 2019223498 A1 WO2019223498 A1 WO 2019223498A1 CN 2019084816 W CN2019084816 W CN 2019084816W WO 2019223498 A1 WO2019223498 A1 WO 2019223498A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
network element
service flow
interface
identifier
Prior art date
Application number
PCT/CN2019/084816
Other languages
English (en)
French (fr)
Inventor
辛阳
吴晓波
崇卫微
周润泽
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19807880.0A priority Critical patent/EP3755048B1/en
Publication of WO2019223498A1 publication Critical patent/WO2019223498A1/zh
Priority to US17/033,293 priority patent/US11463918B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0268Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/24Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2483Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0289Congestion control
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18Negotiating wireless communication parameters
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/16Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/12Setup of transport tunnels
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/0231Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0236Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay

Definitions

  • Embodiments of the present application relate to the field of communications technologies, and in particular, to a data processing method, a sending method, and a device.
  • the core network-side policy control function (PCF) network element In the 15th release (R15), the core network-side policy control function (PCF) network element generates a set of quality of service (QoS) parameters for a service, and the network data and service data It will change with time, resulting in a change in service experience. Therefore, a single set of QoS parameters cannot meet the changing network environment (corresponding to network data) and business requirements (corresponding to business data).
  • the service starts from the first time T1 (time stamp in FIG. 1 is 0000) and ends at the second time T2 (time stamp in FIG. 1 is 0012).
  • the average opinion score (MOS) is calculated every 1 s.
  • the root cause of the change in the voice MOS corresponding to different time points lies in the network condition and the time-varying nature of some service parameters (referring to the characteristics of network data and service data changing over time).
  • some service parameters referring to the characteristics of network data and service data changing over time.
  • the time-varying parameters of these terminals, access networks, core networks, and service layers affect the service experience.
  • terminal services are carried on a service flow.
  • This service flow can be a service quality flow, that is, a QoS flow, or a service data flow, that is, a service data flow. Therefore, the change in service experience is actually relatively Changes in the experience of a service flow correspond to changes in parameters of the terminal, access network, core network, and service layer. Therefore, how to obtain the parameters distributed on different network elements according to the service flow level is a technical problem that needs to be solved urgently.
  • the embodiments of the present application provide a data processing method, a sending method, and a device, so as to obtain data of service flows distributed on different network elements.
  • an embodiment of the present application provides a data processing method, including: a first network element acquiring first data corresponding to a service flow on each of the at least two network elements.
  • the first data on each network element corresponding to the service flow includes a first identifier.
  • the first network element obtains the second data corresponding to the service flow according to the first identifier and the first data on each network element corresponding to the service flow.
  • the second data includes at least the corresponding data on each network in the service flow.
  • the first data on the element, or the second data includes at least a part of the first data on each network element corresponding to the service flow.
  • An embodiment of the present application provides a data processing method.
  • the first data of a service flow on different network elements is obtained through a first network element, and the service flow is changed in different ways according to the first identifier in the first data sent by the different network elements.
  • the first data on the network element is correlated to obtain the second data, which is convenient for the first network element to subsequently plan one or more sets of QoS parameters of the service to which the service flow belongs, the user plane path and slice resource corresponding to the session to which the service flow belongs. Optimization, control plane or user plane anomaly detection, etc.
  • the method provided in the embodiment of the present application further includes: receiving, by the first network element, the first network element for instructing the first network element to send at least two Each network element obtains a first message of first data corresponding to a service flow.
  • the first message includes one or more of the following information: a service identifier to which the service flow belongs, a terminal type of a terminal corresponding to the service flow, a network area where the terminal corresponding to the service flow is located, and a time window corresponding to the service flow.
  • the first message is sent to the first network element through the first message, so that the first network element can determine that the first data corresponding to the service flow on different network elements needs to be obtained from different network elements. Since the first message also carries a time window corresponding to the service flow, in this way, the first network element can obtain data corresponding to changes over time on different network elements.
  • the method provided in this embodiment of the present application further includes: the first network element sends at least two Each network element in the network element sends a first request, which is used to request the first data on each network element corresponding to the service flow.
  • the first request includes one or more of the following information: service flow The service ID, terminal type of the terminal corresponding to the service flow, the network area where the terminal corresponding to the service flow is located, and the time window corresponding to the service flow. This facilitates each network element to clarify the requirements of the first network element after receiving the first request, so as to feedback the first data corresponding to the service flow that satisfies the requirements of the first network element on the network element.
  • the first network element obtains at least two network elements corresponding to the service flow.
  • the first data on each network element in the network includes: the first network element receives a second message sent by each network element and including the first data corresponding to the service flow on each network element.
  • the first data further includes one or more of the following information: An identifier of a network element where the first data corresponding to the service flow is located, an identifier of a terminal, and a data value of at least one data type of at least one of the at least two network elements. Make the information covered by the first data more diverse.
  • the identifier of the terminal in the embodiment of the present application may be one or more of the following: an Internet Protocol address (IP), a subscription permanent identifier (SUPI), and a permanent equipment identifier (permanent equipment identifier).
  • IP Internet Protocol address
  • SUPI subscription permanent identifier
  • a permanent equipment identifier permanent equipment identifier
  • PEI general public subscription identifier
  • IMSI international mobile subscriber identifier
  • IMEI international mobile equipment identity
  • MSISDN mobile station international integrated service digital network number
  • At least two network elements include a third network element.
  • the first data obtained from the third network element further includes one or more of the following information: a service identifier to which the service flow belongs, a communication mode parameter of a service to which the service flow belongs, First interface stream bit rate data, first interface delay data, first interface packet loss rate data, first interface packet data, timestamp, service experience data to which the service flow belongs, jitter buffer data, transmission control protocol TCP congestion window Data, TCP receiving window data, media encoding type data, media encoding type data, encoding rate data, and cache data; wherein the first interface is an interface between a user plane function UPF network element and a data network DN corresponding to an AF network element.
  • the first data obtained from the third network element further includes one or more of the following information: the service identifier to which the service flow belongs, and the identifier of the session in which the service flow belongs , Data network name DNN of the session where the service flow is located, identification information of the slice where the service flow is located, IP filtering information, media bandwidth requirements, traffic routing information, jitter buffering requirements, TCP congestion window requirements, TCP receiving window requirements, media encoding type requirements, Media coding types require coding rate requirements, valid time windows for service identification, and wireless access technology types.
  • the first data obtained from the third network element further includes one or more of the following information: the identifier of the service flow, the identifier of the session where the service flow is located, and the service.
  • the DNN of the session where the stream is located the identification information of the slice where the service flow is located, the valid time window of the service flow identifier, and the radio access technology type.
  • the first data obtained from the third network element further includes one or more of the following information: an identification of the service flow, a time stamp, and a bit rate of the second interface flow Data, first interface stream bit rate data, third interface bit rate data, second interface delay data, first interface delay data, third interface delay data, first interface packet loss rate data, second interface loss Packet rate data, third interface packet loss rate data, first interface packet data, second interface packet data, and third interface packet data.
  • the second interface is an interface between the first UPF network element and the radio access network RAN device; and the third interface is an interface between the first UPF network element and the second UPF network element.
  • the first data obtained from the third network element further includes at least one of the following information: the location information of the terminal corresponding to the service flow, and the location of the service flow
  • the first data obtained from the third network element further includes one or more of the following information: the location information of the terminal corresponding to the service flow, the identification of the service flow, and the location of the service flow Session identification, identification information of the slice where the service flow is located, timestamp, bit rate data of the fourth interface stream, bit rate data of the second interface stream, second interface delay data, fourth interface delay data, reference signal received power RSRP Data, reference signal reception quality RSRQ data, signal interference noise ratio SINR data, channel quality information CQI data, block error rate BLER data, packet rate data, second interface packet data and fourth interface packet data, wireless access technology type, Dual connectivity indication information; where the fourth interface is the interface between the RAN device and the terminal.
  • the first data obtained from the third network element further includes one or more of the following information: the location information of the terminal corresponding to the service flow, the identification of the service flow, and the session where the service flow is located ID of the session, DNN of the session where the service flow is located, identification information of the slice where the service flow is located, bit rate data of the fourth interface stream, fourth interface delay data, fourth interface packet loss rate data, fourth interface packet data, timestamp, CPU usage data, memory usage data, business experience data, jitter cache data, TCP congestion window data, TCP reception window data, media encoding type data, media encoding type data encoding rate data, reference signal received power RSRP data, reference Signal reception quality RSRQ data, signal interference to noise ratio SINR data, channel quality information CQI data, block error rate BLER data, and buffered data.
  • the network elements are different, the diversity of the first data fed back by the different network elements is more abundant.
  • the identification information of the slice may be one or more of the following information: single network slice selection (single information selection (S-NSSAI), network slice instance (NSI) ID, where The S-NSSAI includes a slice type and a tenant ID.
  • S-NSSAI single information selection
  • NSI network slice instance
  • the S-NSSAI includes a slice type and a tenant ID.
  • the location information of the terminal in the embodiments of the present application may be one or more of the following information: a RAN device ID, a cell ID, and a global positioning system (GPS).
  • GPS global positioning system
  • the first data location on each network element corresponding to the service flow is The first identifier included is one or more of the following information: the service identifier to which the service flow belongs, the identifier of the service flow, the identifier of the terminal, the identifier of the session where the service flow belongs, the DNN of the session where the service flow belongs, and the slice where the service flow belongs Identification information.
  • the types of the first identifier are diversified, which facilitates the first network element to determine the first data corresponding to the same service flow on different network elements according to the first identifier.
  • the first data location on each network element corresponding to the service flow is The first identifiers included are the same.
  • the method provided by the embodiment of the present invention further includes: receiving by the first network element A third request sent by the fourth network element, the third request is used to request a first identifier for the service flow; the first network element sends a third response to the third network element, and the third response includes the first identifier.
  • the service flow is a quality of service flow or a service data flow.
  • the first network element obtains at least two network elements corresponding to the service flow.
  • the first data on each network element in the network includes: the first network element receives the first data on each of the at least two network elements corresponding to the service flow sent by the operation management and maintenance network element.
  • an embodiment of the present application provides a data processing method.
  • the method includes: a network element determining to obtain a first identifier of a service flow, where the first identifier is used to identify first data of the service flow on the network element;
  • the network element sends the first data to the first network element, and the first data is used by the first network element to obtain the second data, where the second data includes the first data, or the second data includes a part of the first data,
  • the first data carries a first identifier.
  • the method provided in this embodiment of the present application includes: a network element receives a first request sent by a first network element, where the first request is used to request a service flow Corresponding first data on the network element, the first request includes one or more of the following information: the service identifier to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, and the corresponding value when the terminal uses the service flow Time zone corresponding to network area and service flow.
  • the first data further includes one or more of the following information: An identifier of a network element where the first data is located, an identifier of a terminal, and two or two data values of at least one data type of at least one network element in the network element.
  • the data value of the data type of the network element includes: The first data value of the first data type of the meta determines the second data value, wherein the first data value belongs to the first numerical space, the second data value belongs to the second numerical space, and the first data type is any of the first data.
  • the first data value of the first data type of the meta determines the second data value, wherein the first data value belongs to the first numerical space, the second data value belongs to the second numerical space, and the first data type is any of the first data.
  • the data value of the data type of the network element further includes: The third data value of the second data type of the network element determines the fourth data value, where the third data value belongs to the third numerical space, the fourth data value belongs to the fourth numerical space, and the second data type is the Any one.
  • the second value space is the same as the fourth value space.
  • the first data is also It includes one or more of the following information: the service identifier to which the service flow belongs, the communication mode parameter of the service to which the service flow belongs, the first interface stream bit rate data, the first interface delay data, and the first interface packet loss rate data , First interface packet data, timestamp, service experience data to which the service flow belongs, jitter buffer data, transmission control protocol TCP congestion window data, TCP receive window data, media encoding type data and media encoding type data encoding rate data, cache Data; where the first interface is the interface between the UPF network element and the data network DN corresponding to the AF network element.
  • the first data also includes one or more of the following information: the service identifier to which the service flow belongs, the identifier of the session where the service flow belongs, and the data network name of the session where the service flow belongs. DNN, identification information of the slice where the service flow is located, IP filtering information, media bandwidth requirements, traffic routing information, jitter buffering requirements, TCP congestion window requirements, TCP receiving window requirements, media encoding type requirements, media encoding type requirements, encoding rate requirements, and Valid time window of service identification, wireless access technology type.
  • the first data also includes one or more of the following information: the identification of the service flow, the identification of the session where the service flow is located, the DNN of the session where the service flow is located, and the slice where the service flow is located.
  • the identification of the service flow the identification of the session where the service flow is located
  • the DNN of the session where the service flow is located the DNN of the session where the service flow is located
  • the slice where the service flow is located The valid time window of the identification information and the identification of the service flow, and the type of wireless access technology.
  • the first data further includes one or more of the following information: service flow identification, time stamp, second interface stream bit rate data, first interface stream bit rate data, Third interface bit rate data, second interface delay data, first interface delay data, third interface delay data, first interface packet loss rate data, second interface packet loss rate data, third interface packet loss rate Data, first interface packet data, second interface packet data, and third interface packet data;
  • the second interface is the interface between the first UPF network element and the radio access network RAN device;
  • the third interface is the first UPF The interface between the network element and the second UPF network element.
  • the first data further includes at least one of the following information: location information of the terminal corresponding to the service flow, the identity of the session where the service flow is located, and the DNN of the session where the service flow is located , The identification information of the slice where the service flow is located, the valid time window of the identity of the session where the service flow is located, and the radio access technology type.
  • the first data also includes one or more of the following information: the location information of the terminal corresponding to the service flow, the identification of the service flow, the identification of the session where the service flow is located, and the identification of the slice where the service flow is located.
  • the first data also includes one or more of the following information: the location information of the terminal using the service flow, the identification of the service flow, the identification of the session in which the service flow is located, the DNN of the session in which the service flow is located, Identification information of the slice where the service flow is located, bit rate data of the fourth interface stream, delay data of the fourth interface, packet loss rate data of the fourth interface, packet data of the fourth interface, time stamp, processor CPU usage data, and memory usage Data, service experience data, jitter buffer data, transmission control protocol TCP congestion window data, TCP reception window data, media encoding type data, media encoding type data encoding rate data, reference signal reception power RSRP data, reference signal reception quality RSRQ data , Signal-to-interference and noise ratio SINR data, channel quality information CQI data, block error rate BLER data, and buffered data.
  • an embodiment of the present application provides The method further includes: the network element receives a second request sent by the application function AF network element, the second request is used to request establishment of a service flow, and the second request includes one or more of the following information: a service to which the service flow belongs Identification, IP filtering information, media bandwidth requirements, traffic routing information, jitter cache requirements, TCP congestion window requirements, TCP receive window requirements, media encoding type requirements, media encoding type requirements, encoding rate requirements, cache requirements, at least one data type Claim.
  • the first identifier is one or more of the following information: service The service identifier to which the flow belongs, the identifier of the service flow, the identifier of the terminal, the identifier of the session where the service flow belongs, the DNN of the session where the service flow belongs, and the identification information of the slice where the service flow belongs.
  • the service flow is a quality of service flow or a service data flow.
  • the network element sends a first message to the first network element, and the first message It is used to instruct the first network element to obtain first data corresponding to a service flow from at least two network elements, where the first message includes one or more of the following information: a service identifier to which the service flow belongs, a The terminal type of the terminal, the network area where the terminal corresponding to the service flow is located, and the time window corresponding to the service flow.
  • the data value of the data type of the network element further includes: The element determines a sixth data value according to a fifth data value of a third data type of the network element, where the fifth data value belongs to a fifth value space, the sixth data value belongs to a sixth value space, and the third data type Any one of the first data.
  • the second numerical space, the fourth numerical space, and the sixth The numerical spaces are equal to each other.
  • the sending unit is configured to send the first management operation and maintenance network element ⁇ ⁇ One data.
  • an embodiment of the present application provides a data sending method.
  • the method includes: sending, by a network element, a first network element to instruct a first network element to obtain first data corresponding to a service flow from at least two network elements.
  • the first message includes one or more of the following information: a service identifier to which the service flow belongs, a terminal type of a terminal corresponding to the service flow, a network area where the terminal corresponding to the service flow is located, and a time window corresponding to the service flow.
  • the present application provides a data processing device that can implement the first aspect or the method in any possible implementation manner of the first aspect, and therefore can also implement the first aspect or any possible implementation of the first aspect.
  • the data processing device may be a first network element, or may be a device that can support the first network element to implement the first aspect or the method in any possible implementation manner of the first aspect, such as a chip applied to the first network element. .
  • the device can implement the above method through software, hardware, or executing corresponding software through hardware.
  • An embodiment of the present application provides a data processing device.
  • the data processing device may be a first network element or a chip applied in the first network element.
  • the data processing device includes an obtaining unit and For obtaining the first data corresponding to the service flow on each of the at least two network elements, wherein the first data corresponding to the service flow on each of the network elements includes a first identifier; the processing unit is configured to: The first identifier and the first data on each network element corresponding to the service flow, to obtain second data corresponding to the service flow.
  • the second data includes at least the first data on each network element corresponding to the service flow. Data, or the second data includes at least a part of the first data corresponding to the service flow on each network element.
  • the apparatus provided in the embodiment of the present application further includes: a receiving unit, configured to receive a first message sent by a second network element, where the first message is used For instructing the first network element to obtain the first data corresponding to the service flow from at least two network elements, wherein the first message includes one or more of the following information: a service identifier to which the service flow belongs, and a terminal of the service flow corresponding to Terminal type, network area where the terminal corresponding to the service flow is located, and the time window corresponding to the service flow.
  • a receiving unit configured to receive a first message sent by a second network element, where the first message is used For instructing the first network element to obtain the first data corresponding to the service flow from at least two network elements, wherein the first message includes one or more of the following information: a service identifier to which the service flow belongs, and a terminal of the service flow corresponding to Terminal type, network area where the terminal corresponding to the service flow is located, and the time window corresponding to the service flow.
  • the apparatus provided in this embodiment of the present application further includes: a sending unit, configured to send at least two Each of the network elements sends a first request, where the first request is used to request first data corresponding to a service flow on each network element, and the first request includes one or more of the following information: The service identifier to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, the network area where the terminal corresponding to the service flow is located, and the time window corresponding to the service flow.
  • the receiving unit is further configured to receive a second message sent by each network element.
  • the second message includes first data on each network element corresponding to the service flow, and an obtaining unit, which is specifically configured to obtain the first data on the respective network element corresponding to the service flow from the second message sent by each network element. data.
  • the first data further includes one or more of the following information: service An identifier of a network element where the first data corresponding to the stream is located, an identifier of a terminal, and a data value of at least one data type of at least one of the at least two network elements.
  • At least two network elements include a third network element, and when the third network When the element is an application function AF network element, the first data obtained from the third network element further includes one or more of the following information: the service identifier to which the service flow belongs, the communication mode parameter of the service to which the service flow belongs, One interface stream bit rate data, first interface delay data, first interface packet loss rate data, first interface packet data, timestamp, service experience data to which a service flow belongs, jitter buffer data, transmission control protocol TCP congestion window data TCP receives window data, media encoding type data, encoding rate data of media encoding type data, and cache data.
  • the first interface is an interface between a user plane function UPF network element and a data network DN corresponding to an AF network element.
  • the third network element is a policy control function PCF network element
  • the first data obtained from the third network element further includes one or more of the following information: the service identifier to which the service flow belongs, and the identifier of the session in which the service flow belongs , Data network name DNN of the session where the service flow is located, identification information of the slice where the service flow is located, IP filtering information, media bandwidth requirements, traffic routing information, jitter buffer requirements, TCP congestion window requirements, TCP receiving window requirements, media encoding type requirements, Media coding types require coding rate requirements, valid time windows for service identification, and wireless access technology types.
  • the first data obtained from the third network element further includes one or more of the following information: the identifier of the service flow, the identifier of the session where the service flow is located, and the service.
  • the DNN of the session where the stream is located the identification information of the slice where the service flow is located, the valid time window of the service flow identifier, and the radio access technology type.
  • the first data obtained from the third network element further includes one or more of the following information: an identification of the service flow, a time stamp, and a bit rate of the second interface flow Data, first interface stream bit rate data, third interface bit rate data, second interface delay data, first interface delay data, third interface delay data, first interface packet loss rate data, second interface loss Packet rate data, third interface packet loss rate data, first interface packet data, second interface packet data, and third interface packet data; wherein the second interface is between the first UPF network element and the radio access network RAN device
  • the third interface is an interface between the first UPF network element and the second UPF network element.
  • the first data obtained from the third network element further includes at least one of the following information: the location information of the terminal corresponding to the service flow, and the location of the service flow
  • the first data obtained from the third network element further includes one or more of the following information: the location information of the terminal corresponding to the service flow, the identification of the service flow, and the location of the service flow Session identification, identification information of the slice where the service flow is located, timestamp, bit rate data of the fourth interface stream, bit rate data of the second interface stream, second interface delay data, fourth interface delay data, reference signal received power RSRP Data, reference signal reception quality RSRQ data, signal interference noise ratio SINR data, channel quality information CQI data, block error rate BLER data, second interface packet loss rate data, fourth interface packet loss rate data, second interface packet data and
  • the fourth interface includes data, a radio access technology type, and dual connection indication information.
  • the fourth interface is an interface between the RAN device and the terminal.
  • the first data obtained from the third network element further includes one or more of the following information: the location information of the terminal corresponding to the service flow, the identification of the service flow, and the session where the service flow is located ID of the session, DNN of the session where the service flow is located, identification information of the slice where the service flow is located, bit rate data of the fourth interface stream, fourth interface delay data, fourth interface packet loss rate data, fourth interface packet data, timestamp, Processor CPU usage data, memory usage data, business experience data, jitter cache data, TCP congestion window data, TCP reception window data, media encoding type data, media encoding type data encoding rate data, reference signal received power RSRP data , Reference signal receiving quality RSRQ data, signal interference noise ratio SINR data, channel quality information CQI data, block error rate BLER data, buffer data.
  • the first data corresponding to the service flow on each network element includes
  • the first identifier is one or more of the following information: the service identifier to which the service flow belongs, the service flow identifier, the terminal identifier, the session identifier of the service flow, the DNN of the session where the service flow is located, and the Identification information.
  • the first data corresponding to the service flow on each network element includes The first logo is the same.
  • the receiving unit is further configured to receive a third request sent by a fourth network element.
  • the third request is used to request the first identifier to be allocated for the service flow;
  • the sending unit is configured to send a third response to the third network element, and the third response includes the first identifier.
  • the service flow is a quality of service flow or a service data flow.
  • the receiving unit is configured to receive a service sent by an operation management and maintenance network element The stream corresponds to the first data on each of the at least two network elements.
  • an embodiment of the present application further provides a data processing device.
  • the data processing device may be a first network element or a chip applied to the first network element.
  • the device includes a processor and a communication device.
  • An interface where the communication interface is used to support the device to perform the steps of receiving / sending data / data on the device side as described in any one of the possible implementation manners of the first aspect to the first aspect.
  • the processor is configured to support the apparatus to execute the steps of performing message / data processing on the apparatus side described in any one of the possible implementation manners of the first aspect to the first aspect.
  • the communication interface and the processor of the data processing device are coupled to each other.
  • the data processing apparatus may further include a memory for storing code and data, and the processor, the communication interface, and the memory are coupled to each other.
  • the present application provides a data sending device that can implement the second aspect or the method in any possible implementation manner of the second aspect, and therefore can also implement the second aspect or any possible implementation of the second aspect.
  • the data sending device may be a network element, or may be a device that can support the network element to implement the second aspect or the method in any possible implementation manner of the second aspect, such as a chip applied to the network element.
  • the device can implement the above method through software, hardware, or executing corresponding software through hardware.
  • An embodiment of the present application provides a data sending device.
  • the data sending device may be a network element or a chip applied in the network element.
  • the data sending device includes: a determining unit, configured to determine the obtained The first identifier of the service flow, where the first identifier is used to identify the first data of the service flow on the network element; the sending unit is used to send the first data to the first network element, and the first data is used for the first
  • the network element obtains second data, where the second data includes the first data, or the second data includes at least a part of the first data, and the first data carries a first identifier.
  • the receiving unit is configured to receive a first request sent by a first network element, where the first request is used to request that a service flow corresponds to a network element.
  • the first data includes one or more of the following information: the service identifier to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, the network area corresponding to the service flow when the terminal uses the service flow, and the corresponding service flow. Time window.
  • the first data further includes one or more of the following information: An identifier of a network element where the first data is located, an identifier of a terminal, and two or two data values of at least one data type of at least one network element in the network element.
  • the data value of the data type of the network element specifically includes: a determining unit, Configured to determine a second data value according to a first data value of a first data type of the device, wherein the first data value belongs to a first numerical space, the second data value belongs to a second numerical space, and the first data type is first Any item in the data.
  • the data value of the data type of the network element further includes: a determining unit, For determining a fourth data value according to a third data value of a second data type of the device, wherein the third data value belongs to a third value space, the fourth data value belongs to a fourth value space, and the second data type is the first Any item in the data.
  • the second numerical space is the same as the fourth numerical space.
  • the first data is also It includes one or more of the following information: the service identifier to which the service flow belongs, the communication mode parameter of the service to which the service flow belongs, the first interface stream bit rate data, the first interface delay data, and the first interface packet loss rate data , First interface packet data, timestamp, service experience data to which the service flow belongs, jitter buffer data, transmission control protocol TCP congestion window data, TCP receive window data, media encoding type data and media encoding type data encoding rate data, cache Data; where the first interface is the interface between the user plane function UPF network element and the data network DN corresponding to the AF network element.
  • the first data also includes one or more of the following information: the service identifier to which the service flow belongs, the identifier of the session where the service flow belongs, and the data network name of the session where the service flow belongs. DNN, identification information of the slice where the service flow is located, IP filtering information, media bandwidth requirements, traffic routing information, jitter buffering requirements, TCP congestion window requirements, TCP receiving window requirements, media encoding type requirements, media encoding type requirements, encoding rate requirements, and Valid time window of service identification, wireless access technology type.
  • the first data also includes one or more of the following information: the identification of the service flow, the identification of the session where the service flow is located, the DNN of the session where the service flow is located, and the slice where the service flow is located.
  • the identification of the service flow the identification of the session where the service flow is located
  • the DNN of the session where the service flow is located the DNN of the session where the service flow is located
  • the slice where the service flow is located The valid time window of the identification information and the identification of the service flow, and the type of wireless access technology.
  • the first data further includes one or more of the following information: service flow identification, time stamp, second interface stream bit rate data, first interface stream bit rate data, Third interface bit rate data, second interface delay data, first interface delay data, third interface delay data, first interface packet loss rate data, second interface packet loss rate data, third interface packet loss rate Data, first interface packet data, second interface packet data, and third interface packet data;
  • the second interface is the interface between the first UPF network element and the radio access network RAN device;
  • the third interface is the first UPF The interface between the network element and the second UPF network element.
  • the first data further includes at least one of the following information: location information of the terminal corresponding to the service flow, the identity of the session where the service flow is located, and the DNN of the session where the service flow is located , The identification information of the slice where the service flow is located, the valid time window of the identity of the session where the service flow is located, and the radio access technology type.
  • the first data also includes one or more of the following information: the location information of the terminal corresponding to the service flow, the identification of the service flow, the identification of the session where the service flow is located, and the identification of the slice where the service flow is located.
  • the first data also includes one or more of the following information: the location information of the terminal using the service flow, the identification of the service flow, the identification of the session in which the service flow is located, the DNN of the session in which the service flow is located, Identification information of the slice where the service flow is located, bit rate data of the fourth interface stream, delay data of the fourth interface, packet loss rate data of the fourth interface, packet data of the fourth interface, timestamp, processor CPU usage data, memory usage Data, service experience data, jitter buffer data, transmission control protocol TCP congestion window data, TCP reception window data, media encoding type data, media encoding type data encoding rate data, reference signal reception power RSRP data, reference signal reception quality RSRQ data , Signal-to-interference and noise ratio SINR data, channel quality information CQI data, block error rate BLER data, and buffered data.
  • the location information of the terminal using the service flow the identification of the service flow, the identification of the session in which the service flow is located, the DNN of the session in which the service
  • the receiving unit is further configured to: Receive a second request sent by the application function AF network element.
  • the second request is used to request establishment of a service flow.
  • the second request includes one or more of the following information: the service identifier to which the service flow belongs, IP filtering information, and media bandwidth. Requirements, traffic routing information, jitter buffer requirements, TCP congestion window requirements, TCP receive window requirements, media encoding type requirements, media encoding type requirements, encoding rate requirements, cache requirements, and at least one data type requirement.
  • the first identifier is one or more of the following information: service The service identifier to which the flow belongs, the identifier of the service flow, the identifier of the terminal, the identifier of the session where the service flow is located, the DNN of the session where the service flow is located, and the identification information of the slice where the service flow is located.
  • the service flow is a quality of service flow or a service data flow.
  • the data value of the data type of the network element further includes: a determining unit To determine a sixth data value according to a fifth data value of a third data type of the device, wherein the fifth data value belongs to a fifth numerical space and the sixth data value belongs to the sixth numerical space,
  • the third data type is any one of the first data.
  • the second value space, the fourth value space, and the sixth value Spaces are equal to each other.
  • the sending unit sends the first to the operation management and maintenance network element. data.
  • an embodiment of the present application further provides a data sending device.
  • the data sending device may be a network element or a chip applied to the network element.
  • the data sending device includes a processor and a communication interface.
  • the communication interface is used to support the data sending device to perform the steps of receiving / sending data / data on the data sending device side described in any one of the possible implementation manners of the second aspect to the second aspect.
  • the processor is configured to support the data sending apparatus to perform the steps of performing message / data processing on the data sending apparatus side described in any one of the possible implementation manners of the second aspect to the second aspect.
  • the communication interface of the data sending device and the processor are coupled to each other.
  • the data sending apparatus may further include a memory for storing codes and data, and the processor, the communication interface, and the memory are coupled to each other.
  • the present application provides a data sending device that can implement the third aspect or the method in any possible implementation manner of the third aspect, and therefore can also implement the third aspect or any possible implementation of the third aspect.
  • the data sending device may be a network element, or may be a device that can support the network element to implement the third aspect or the method in any possible implementation manner of the third aspect, such as a chip applied to the network element.
  • the device can implement the above method through software, hardware, or executing corresponding software through hardware.
  • An embodiment of the present application provides a data sending device.
  • the data sending device is a network element or a chip applied in the network element.
  • the device includes a sending unit configured to send a data packet to the first network element.
  • the first message instructs the first network element to obtain first data corresponding to the service flow from at least two network elements.
  • the first message includes one or more of the following information: a service identifier to which the service flow belongs, a terminal type of a terminal corresponding to the service flow, a network area where the terminal corresponding to the service flow is located, and a time window corresponding to the service flow.
  • an embodiment of the present application further provides a data sending device.
  • the data sending device may be a network element or a chip applied in the network element.
  • the data sending device includes a communication interface, where communication The interface is used to support the data sending device to perform the steps of receiving / sending data / data on the data sending device side as described in any one of the possible implementation manners of the third aspect to the third aspect.
  • the device further includes: a processor configured to support the data sending device to perform the step of performing message / data processing on the data sending device side described in any one of the possible implementation manners of the third aspect to the third aspect. .
  • a processor configured to support the data sending device to perform the step of performing message / data processing on the data sending device side described in any one of the possible implementation manners of the third aspect to the third aspect.
  • the communication interface of the data sending device and the processor are coupled to each other.
  • the data sending apparatus may further include a memory for storing codes and data, and the processor, the communication interface, and the memory are coupled to each other.
  • the present application provides a computer-readable storage medium having instructions stored in the computer-readable storage medium, which when executed on a computer, causes the computer to execute the first aspect and various possible implementations of the first aspect. One or more of them.
  • the present application provides a computer-readable storage medium having instructions stored in the computer-readable storage medium, which when executed on a computer, causes the computer to execute the second aspect and various possible implementation manners of the second aspect One or more of them.
  • the present application provides a computer-readable storage medium.
  • the computer-readable storage medium stores instructions that, when run on a computer, cause the computer to execute various possible implementations of the third aspect and the fifth aspect. One or more of them.
  • the present application provides a computer program product including instructions that, when run on a computer, causes the computer to perform one or more of the first aspect and various possible designs of the first aspect.
  • the present application provides a computer program product including instructions that, when run on a computer, causes the computer to perform one or more of the second aspect and various possible designs of the second aspect.
  • the present application provides a computer program product including instructions that, when run on a computer, causes the computer to perform one or more of the third aspect and various possible designs of the third aspect.
  • the present application provides a chip that includes a processor and an interface circuit.
  • the interface circuit is coupled to the processor, and the processor is configured to run a computer program or instruction to implement the first aspect and various possible aspects of the first aspect.
  • the present application provides a chip.
  • the chip includes a processor and an interface circuit.
  • the interface circuit is coupled to the processor, and the processor is configured to run a computer program or instruction to implement the second aspect and the various possible aspects of the second aspect.
  • the present application provides a chip.
  • the chip includes a processor and an interface circuit.
  • the interface circuit is coupled to the processor, and the processor is configured to run a computer program or instruction to implement the third aspect and various possible implementations of the third aspect.
  • the chip described above in this application may further include at least one memory, and the at least one memory stores instructions or a computer program.
  • an embodiment of the present application provides a data processing system.
  • the data processing system includes: the fourth aspect and the data processing device described in various possible implementation manners of the fourth aspect, and at least two data processing devices as described in the fifth aspect.
  • the data sending apparatus described in various possible implementations of the aspect and the fifth aspect.
  • the data processing system further includes: the data sending device described in the sixth aspect.
  • FIG. 1 is a prior art voice MOS change curve diagram provided by an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of a data processing system according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a 5G network according to an embodiment of the present application.
  • 4 to 10 are schematic flowcharts of a data processing method according to an embodiment of the present application.
  • 11 to 13 are schematic structural diagrams of a data processing apparatus according to an embodiment of the present application.
  • FIG. 20 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • words such as “first” and “second” are used to distinguish the same or similar items having substantially the same functions and functions.
  • the first network element and the second network element are only for distinguishing different network elements, and do not limit their sequence.
  • the words “first”, “second” and the like do not limit the number and execution order, and the words “first” and “second” are not necessarily different.
  • the network architecture and service scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that with the network The evolution of the architecture and the emergence of new business scenarios. The technical solutions provided in the embodiments of the present application are also applicable to similar technical issues.
  • At least one means one or more, and “multiple” means two or more.
  • “And / or” describes the association relationship of related objects, and indicates that there can be three kinds of relationships, for example, A and / or B can indicate: A exists alone, A and B exist simultaneously, and B alone exists, where A, B can be singular or plural.
  • the character “/” generally indicates that the related objects are an "or” relationship.
  • “At least one or more of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items.
  • At least one (a) of a, b, or c can be expressed as: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • CDMA code division multiple access
  • TDMA time division multiple access
  • TDMA frequency division multiple access
  • FDMA frequency multiple access
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • the term "system” can be used interchangeably with "network.”
  • the CDMA system can implement wireless technologies such as universal wireless terrestrial access (UTRA) and CDMA2000.
  • UTRA may include Wideband CDMA (WCDMA) technology and other CDMA variant technologies.
  • CDMA2000 can cover the Interim Standard (IS) 2000 (IS-2000), IS-95 and IS-856 standards.
  • the TDMA system can implement wireless technologies such as the Global System for Mobile Communication (GSM).
  • GSM Global System for Mobile Communication
  • OFDMA system can implement e.g. evolved universal UTRA (E-UTRA), ultra mobile broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDMA And other wireless technologies.
  • E-UTRA evolved universal UTRA
  • UMB ultra mobile broadband
  • Wi-Fi IEEE 802.11
  • WiMAX IEEE 802.16
  • UTRA and E-UTRA are UMTS and UMTS evolved versions.
  • 3GPP is a new version of UMTS using E-UTRA in long term evolution (LTE) and various versions based on LTE evolution.
  • LTE long term evolution
  • NR New Radio
  • the communication system may also be applicable to future-oriented communication technologies, and both are applicable to the technical solutions provided in the embodiments of the present application.
  • FIG. 2 shows a schematic architecture diagram of a data processing system to which a data processing method provided in an embodiment of the present application is applied.
  • the first network element 101 and at least the first network element 101 connected to the first network element 101 Two network elements (only two network elements are shown in FIG. 2, for example, taking the network element 102 and the network element 103 as an example, it can be understood that there may be more than two network elements in an actual process).
  • At least two network elements in the embodiment of the present application may also be connected to each other, for example, the network element 102 and the network element 103 in FIG. 2 are connected to each other.
  • one network element exists in at least two network elements for providing the first network element with service data corresponding to the service flow on the network element, and in the at least two network elements, another network element exists.
  • One network element is used to provide network data of a service flow on the other network element to the first network element.
  • the service data involved in this application may be: the service identifier to which the service flow belongs, bandwidth, delay, packet loss rate, jitter buffer, TCP congestion window, TCP receiving window, media encoding type, media encoding rate, etc. Parameter data.
  • the data of a certain parameter may be the size, value, or requirement of the parameter.
  • the CQI data may refer to the size or value of the CQI.
  • the data, size, or value or requirement of a parameter expresses the data value collected or obtained by the parameter in the corresponding network element, as described below. Any reference to such descriptions can be referred to here, and will not be repeated hereafter.
  • the network data involved in this application can be any of the following parameters: bandwidth, delay, packet loss rate, reference signal receiving power (RSRP), reference signal receiving quality (RSRQ), Parameter data such as block error rate (BLER), channel quality indication (CQI), slice identification information, and data network name (DNN).
  • RSRP reference signal receiving power
  • RSRQ reference signal receiving quality
  • Parameter data such as block error rate (BLER), channel quality indication (CQI), slice identification information, and data network name (DNN).
  • the first network element 101 and the at least two network elements may be directly connected or indirectly connected through other network elements, which is not limited in this embodiment of the present application.
  • the network element among the at least two network elements used to provide network data for the first network element may be a terminal, a network element belonging to a core network, or an access network.
  • the network element for providing a data network to the first network element may be one or more of a user plane network element and a control plane network element in the core network.
  • a user plane network element may be: for example, a public data network gateway (PDN, GW, PGW for short), and a serving network element (SGW).
  • the control plane network element may be a mobility management entity (MME).
  • the terminals may be distributed throughout the wireless network, and each terminal may be static or mobile.
  • the network element or entity corresponding to the first network element 101 may be a network data analysis function (NWDAF) network element.
  • NWDAF network data analysis function
  • the network element or entity corresponding to the at least two network elements may be any two different network elements among the following multiple network elements: application function (also known as service function network element) (application function (AF) network element, policy Control (policy control function (PCF) network element, session management function (SMF) network element, user plane function (UPF) network element, access and mobility management function (AMF) network element, radio access network (radio access network, RAN) equipment and terminals.
  • application function also known as service function network element
  • PCF policy Control
  • SMF session management function
  • UPF user plane function
  • AMF access and mobility management function
  • radio access network radio access network
  • the RAN device is a network element belonging to a radio access network.
  • PCF network elements, SMF network elements, AMF network elements and UPF network elements are network elements belonging to the core network.
  • one of the at least two network elements 102 provides the first network element with the service data corresponding to the service flow on the network element 102
  • the other network element 103 provides the network data with the service flow on the network element 103.
  • the network element 102 may be an AF network element
  • the network element 103 may be an AMF network element
  • the network element 102 may be an AF network element
  • the network element 103 may be a UPF network element.
  • the 5G network may further include an access device (for example, an access network (AN)), a unified data management (UDM) network element, and an authentication server function (authentication server element (AUSF) network element, network slice selection function (NSSF) network element, network capability open function network element (NEF network element), network warehouse storage function (NRF)
  • AN access network
  • UDM unified data management
  • AUSF authentication server element
  • NSSF network slice selection function
  • NEF network element network capability open function network element
  • NRF network element
  • NRF network warehouse storage function
  • operation, management, and maintenance (operation, maintenance, and maintenance (OAM)) network elements can cover all network elements of the access network and core network. And can collect data from all of these network elements of the access network and the core network, and the OAM network element in the embodiment of the present application can also collect network data at the service flow level.
  • OAM operation, maintenance, and maintenance
  • the terminal communicates with the AMF network element through an N1 interface (referred to as N1).
  • the AMF entity communicates with the SMF network element through the N11 interface (referred to as N11).
  • the SMF network element communicates with one or more UPF network elements through an N4 interface (referred to as N4). Any two UPF network elements in one or more UPF network elements communicate through an N9 interface (referred to as N9 for short).
  • the UPF network element communicates with a data network (DN) controlled by the AF network element through an N6 interface (referred to as N6).
  • the terminal accesses the network through an access device (for example, a RAN device), and the access device communicates with the AMF network element through an N2 interface (referred to as N2 for short).
  • the SMF network element communicates with the PCF network element through the N7 interface (referred to as N7), and the PCF network element communicates with the AF network element through the N5 interface.
  • the access device communicates with the UPF network element through an N3 interface (referred to as N3). Any two AMF network elements communicate through an N14 interface (N14 for short).
  • the SMF network element communicates with the UDM through an N10 interface (referred to as N10).
  • the AMF network element communicates with the AUSF through the N12 interface (referred to as N12 for short).
  • the AUSF network element communicates with the UDM network element through the N13 interface (referred to as N13).
  • the AMF network element communicates with the UDM network element through the N8 interface (referred to as N8).
  • the 3rd AF network element and the Operator AF are both AF network elements.
  • the 3rd AF network element such as WeChat service server and Alipay payment service server
  • the Operator AF network element for example, the proxy-call session control function (P-CSCF) network element in IP multimedia system
  • P-CSCF proxy-call session control function
  • the 3rd AF network element needs to interact with the NWDAF network element. Through NEF network elements.
  • the PCF network element is used to forward the signaling or data of the AF network element to the SMF network element.
  • interface names between the various network elements in FIG. 3 are only examples, and the interface names may be other names in the specific implementation, which is not specifically limited in this embodiment of the present application.
  • the access device, AF network element, AMF network element, SMF network element, AUSF network element, UDM network element, UPF network element, and PCF network element in FIG. 3 are only a name, and the name does not refer to the device itself. Composition limitation. In the 5G network and other networks in the future, the network elements or entities corresponding to the access device, AF network element, AMF network element, SMF network element, AUSF network element, UDM network element, UPF network element, and PCF network element can also be used. Is another name, which is not specifically limited in the embodiment of the present application.
  • the UDM network element may also be replaced with a user home server (HSS), a user subscription database (USD), or a database entity, etc., which are described collectively here, and will not be described in detail below. .
  • a session in this application refers to a communication link between a connected terminal and a data network established by an SMF network element.
  • the communication chain includes a terminal, an access device, a UPF network element, and a corresponding UPF network element.
  • the session may be a protocol data unit session (PDU session) PDU, and the PDU session is used to provide a PDU data packet.
  • PDU session protocol data unit session
  • the control plane AMF network element, SMF network element, and PCF network element need to cooperate.
  • the service flow in this application includes QoS flow or service data flow.
  • QoS flow or service data flow is a communication link between a connected terminal of a service in a PDU session and a data network.
  • the communication link includes Terminal, access device, UPF network element and data network corresponding to UPF network element.
  • the control plane AMF network element, SMF network element, and PCF network element need to cooperate.
  • the terminal in this application may also be referred to as terminal equipment, user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, User terminal, terminal, wireless communication device, user agent, or user device.
  • the terminal device can be a station (STA) in a wireless local area network (WLAN), a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, or a wireless local loop loop (WLL) stations, personal digital processing (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, and next-generation communication systems,
  • STA wireless local area network
  • PDA personal digital processing
  • 5G fifth-generation
  • PLMN future evolved public land mobile network
  • the terminal may also be a wearable device.
  • Wearable devices can also be referred to as wearable smart devices, which are the general name for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a device that is worn directly on the body or is integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also powerful functions through software support, data interaction, and cloud interaction.
  • Broad-spectrum wearable smart devices include full-featured, large-sized, full or partial functions that do not rely on smart phones, such as smart watches or smart glasses, and only focus on certain types of application functions, and need to cooperate with other devices such as smart phones Use, such as smart bracelets, smart jewelry, etc. for physical signs monitoring.
  • the access device referred to in the embodiments of the present application refers to a device that accesses a core network, and may be, for example, a base station, a broadband network service gateway (BNG), an aggregation switch, and a non-third generation Partner project (3rd generation partnership project, 3GPP) access equipment, etc.
  • the base station may include various forms of base stations, such as: macro base stations, micro base stations (also called small stations), relay stations, access points, and the like.
  • the AMF network element involved in the embodiments of the present application may also be responsible for functions such as registration management, mobility management, and lawful interception, which are not specifically limited in this embodiment of the present application.
  • the SMF network elements involved in the embodiments of the present application are used for session management, including: session establishment, session modification, session release, and Internet protocol (IP) address allocation of terminals' networks. And management, UPF network element selection and control, legal monitoring and other session-related control functions.
  • session management including: session establishment, session modification, session release, and Internet protocol (IP) address allocation of terminals' networks.
  • IP Internet protocol
  • the UPF network elements involved in the embodiments of the present application may also implement a serving gateway (SGW) and a packet data network gateway (packet data). network gateway (PGW).
  • SGW serving gateway
  • PGW packet data network gateway
  • PGW packet data network gateway
  • the UPF network element may also be a software-defined network (SDN) switch, which is not specifically limited in the embodiment of the present application.
  • SDN software-defined network
  • the AUSF network element involved in the embodiment of the present application is used to perform authentication and authentication on the terminal based on the subscription data of the terminal.
  • the UDM network elements involved in the embodiments of the present application are used to store user subscription data.
  • the UDM network element also includes functions such as authentication and authentication, processing user identification, and contract management, which are not specifically limited in this embodiment of the present application.
  • the PCF network elements involved in the embodiments of the present application provide policy rules and support a unified policy architecture to manage network behaviors and other policy-related functions.
  • the user plane function network element in FIG. 3 may be implemented by one physical device, or may be implemented by multiple physical devices, or may be a logical function module in one physical device, which is not described in this embodiment of the present application. Specific limitations.
  • the SMF network element is used to reassign the UPF network element to the terminal based on the location information of the terminal or the characteristics of the data sent by the terminal or the location information between the UPF network element and the terminal. Newly allocated sessions between UPF network elements, thus improving the reconstructed session can optimize the user plane.
  • the access device is used to provide data services for the terminal, for example, receiving data sent by the terminal, or sending data to the terminal.
  • the access device may be a base station.
  • a base station may be a device that communicates with a user equipment (UE) or other communication site such as a relay station, and the base station may provide communication coverage of a specific physical area.
  • UE user equipment
  • the PCF network element is used to receive service information from the AF network element, and generate and distribute QoS parameters corresponding to the service flow based on the service information.
  • the AF network element is used to trigger the NWDAF network element to collect the first data corresponding to the service flow on different network elements, and send the first data corresponding to the service flow to the AF network element to the NWDAF network element.
  • the DN is used for external networks that provide data services.
  • the service flow in the embodiment of the present application refers to a data packet transmission channel of a service between a terminal and a data network, which is identified by an IP quintuple.
  • NWDAF network element used to collect time-varying networks or services or terminals and corresponding service experience data, and analyze and obtain different network conditions (corresponding network data) or service conditions (corresponding service data) or terminal conditions (corresponding to terminal data) of a service ) At least one set of QoS parameters.
  • the NWDAF network element can collect air interface stream bit rate data (data value, size, requirements, etc.) of a service on a base station and analyze to obtain a GFBR.
  • the NWDAF network element may collect delay data (data value, size, requirements, etc.) of a service between the base station and the UPF, and analyze and obtain a PDB.
  • NWDAF can collect TCP Congestion Window (CWND) data (data value, size, request, etc.) or TCP Receive Window (RWND) data (data value, size, request, etc.) on the AF network element or terminal. , Analyze to get recommended CWND or recommended RWND.
  • NWDAF can collect jitter buffer data on the AF network element or terminal, and analyze and get the recommended Jitter buffer.
  • the reason is at least a set of QoS parameters. For example, considering the service experience requirements for vertical industries (for example, the service MOS score is greater than 3.0), packet delay data and packet loss rate data conflict.
  • the RAN can transmit data packets several times to ensure the packet loss rate, but in this case, the packet delay will be increased, and further, the stream bit rate may be increased;
  • the RAN does not need to transmit multiple data packets. In this case, both the packet loss rate and the packet delay can be guaranteed. Further, the stream bit rate may be reduced.
  • the NWDAF network element obtains at least one set of QoS parameters of a service through a big data method based on time-varying network data or service data or terminal data and corresponding service experience data.
  • the process is as follows:
  • Step 1 The NWDAF network element first collects data from the AF network element, RAN equipment, UPF network element, UE, AMF network element, SMF network element, PCF network element and other network elements, and then passes the service identifier, service flow identifier, and terminal identifier.
  • the information such as the session ID where the service flow is located, the associated ID on each network element, and the time correlate the data of each network element to obtain complete training data.
  • the training data includes:
  • TCP congestion window data TCP reception window data, jitter buffer data, media encoding type and encoding rate data, buffer data, and data of at least one data type from the AF network element.
  • bit rate data From the RAN network element stream bit rate data, packet loss rate data, delay data, wireless channel quality data, data of at least one data type.
  • d streaming bit rate data, packet loss rate data, delay data, at least one data type data, TCP congestion window data, TCP reception window data, jitter buffer data, media encoding type and encoding rate data, buffer data from the UE , CPU usage, memory usage of at least one data type. and many more.
  • Step 2 Based on the Linear Regression method, the NWDAF network element obtains the relationship model between the service experience and other time-varying parameter data that affects the service experience data, that is, the service experience model.
  • the NWDAF network element can plan services based on this service experience model. One or more sets of QoS parameters.
  • NWDAF can also be used for UPF routing path selection, user plane or control plane fault diagnosis based on the obtained training data.
  • Table 1 and Table 2 show related information of service data and network data provided in the embodiments of the present application.
  • the UE ID in the embodiment of the present application may refer to the identifier of the terminal, and details are not described herein again.
  • Table 4 shows the communication mode parameters involved in Table 1:
  • the data processing method in the embodiments of the present application may be executed by the first network element, or may be executed by a device applied to the first network element, for example, a chip.
  • an example in which an execution subject of a data processing method is a first network element is used as an example for description.
  • the execution subject of a data sending method in the embodiments of the present application may be a network element or a device applied to the network element, for example, a chip.
  • the execution subject of a data sending method is A network element is used as an example for description.
  • FIG. 4 shows a data processing method provided by an embodiment of the present application.
  • the method includes:
  • At least two network elements determine to obtain a first identifier of a service flow.
  • At least two network elements may be a combination between any one or more of a PCF network element, an AMF network element, an SMF network element, a UPF network element, a RAN device, and a terminal, and an AF network element.
  • the service flow in the embodiment of the present application may be a quality of service flow or a service data flow.
  • step S101a may be used instead of step S101.
  • the network element determines that the first instruction information is received, and the first instruction information is used to instruct the first network element to report the corresponding service flow.
  • First data For example, the first indication may be Network Data Report Indicator.
  • Each of the at least two network elements sends the first data corresponding to the service flow on the respective network element to the first network element, and the first data carries a first identifier.
  • the first network element may be the NWDAF network element in FIG. 3 described above.
  • the first data corresponding to the service flow on each network element may be different, for example, taking at least two network elements as network element 1 and network element 2 as
  • the first data corresponding to the service flow on the network element 1 is network data, for example, a flow identifier.
  • the first data corresponding to the service flow on the network element 2 may be service data, for example, an identifier of a terminal. Then, when the network element 1 and the network element 2 determine that the first identifier is received, the network element 1 sends the flow identifier to the first network element, and the network element 2 sends the terminal identifier to the first network element.
  • the first network element As NWDAF as an example, due to different network elements, there are differences in the manner in which the network element sends the first data to the first network element. Therefore, the following will be introduced separately:
  • Example 1 When at least one of the two network elements is an AMF network element, an SMF network element, or a PCF network element, the one network element may directly send a first service element interface to the first network element to the first The network element sends the first data corresponding to the service flow.
  • the service-oriented interface can implement direct communication or interaction between any two network elements of the AMF network element, the SMF network element, the PCF network element, the NWDAF network element, and the NEF network element. For example, if the network element is an AMF network element, the network element sends the first data corresponding to the service flow to the first network element through a service-oriented interface with the first network element.
  • Example 2 One of the at least two network elements is a RAN device, and the RAN device may first send the first data corresponding to the service flow on the RAN device to the control plane network element accessed by the RAN device, such as AMF. Then, the control plane network element accessed by the RAN device passes the service-oriented interface between the control plane network element accessed by the RAN device and the first network element (for example, the service-oriented interface between the AMF network element and the NWDAF network element). Interface) to the first network element. Alternatively, the RAN device may send the first data corresponding to the service flow on the RAN device to the first network element by establishing a user plane tunnel with the first network element.
  • the control plane network element accessed by the RAN device passes the service-oriented interface between the control plane network element accessed by the RAN device and the first network element (for example, the service-oriented interface between the AMF network element and the NWDAF network element). Interface) to the first network element.
  • the RAN device may send the first data corresponding to the
  • Example 3 When at least two network elements have one network element that is a UPF network element, the UPF network element may first send the first data corresponding to the service flow on the UPF network element to the control plane network to which the UPF network element accesses Element, for example, an SMF network element. Then, the control plane network element accessed by the UPF network element passes the service-oriented interface between the control plane network element accessed by the UPF network element and the first network element (for example, the service between the SMF network element and the NWDAF network element). Interface) to the first network element. Alternatively, the UPF network element may send the first data corresponding to the service flow on the UPF network element to the first network element through a user plane tunnel with the first network element.
  • the control plane network element accessed by the UPF network element passes the service-oriented interface between the control plane network element accessed by the UPF network element and the first network element (for example, the service between the SMF network element and the NWDAF network element). Interface) to the first network element.
  • Example 4 When one of the at least two network elements is an AF network element, the method 1 may be that the AF network element uses a file transfer protocol (FTP) method to correspond to a service flow on the AF network element.
  • the first data is sent to the first network element.
  • the AF network element may send the first data corresponding to the service flow on the AF network element to the first network element through a user plane tunnel established with the first network element.
  • Method 3 The AF network element may continuously report the first data corresponding to the service flow on the AF network element to the first network element through the Naf_ServiceDataCollectionSubscription_Notify service.
  • Method 4 The AF network element may send the first data corresponding to the service flow on the AF network element to the first network element through the NEF.
  • the first identifier included in the first data corresponding to the service stream on each network element is one or more of the following information: the service identifier to which the service stream belongs, the service stream identifier, and the terminal identifier , The identifier of the session where the service flow is located, the data network name (DNN) of the session where the service flow is located, and the identification information of the slice where the service flow is located.
  • the first identifiers carried in the first data sent by the at least two network elements to the first network element may be the same.
  • the first identifier carried in data 1 sent by network element 1 is the identifier of the session where the service flow is located.
  • the first identifier carried in the data 2 sent by the network element 2 may also be an identifier of a session where the service flow is located.
  • the first identifiers carried in the first data sent by the at least two network elements to the first network element may be different.
  • the first identifier carried in data 1 sent by network element 1 is the identifier of the terminal.
  • the first identifier carried in the data 2 sent by the network element 2 may also be an identifier of a session where the service flow is located.
  • the first identifiers carried in the first data sent by different network elements to the first network element are different, there is a mapping relationship between the first identifiers carried in the first data sent by the different network elements. For example, there is a mapping relationship between the identity of the session where the service flow is located and the identity of the service flow. And the first network element stores a mapping relationship between the first identifiers sent by different network elements, so that when the first network element receives the first data corresponding to the service flow sent from the different network elements, it can determine the different The first data sent by the network element is data corresponding to the same service flow.
  • the first network element obtains first data on each network element of the at least two network elements corresponding to the service flow, where the first data on each network element corresponding to the service flow includes a first identifier.
  • the first network element receives the first data corresponding to the service flow from the network element in a corresponding manner, for example, When the network element is an AMF network element, the first network element receives the first data corresponding to the service flow sent by the AMF network element through the service interface between the AMF network element and the first network element, which is not described in the embodiment of this application. .
  • the first network element obtains the second data corresponding to the service flow according to the first identifier and the first data corresponding to the service flow on each network element.
  • the second data includes at least first data on each network element corresponding to the service flow, or the second data includes at least part of the first data on each network element corresponding to the service flow.
  • the first network element may directly correspond to the first data or the first data corresponding to the service flow on different network elements according to the first identifiers. At least a part of is divided into the same set to obtain the second data.
  • the first network element may, according to a pre-stored mapping relationship, match the first data corresponding to the service flow on different network elements with the mapping relationship or At least a part of the first data is divided into the same set to obtain the second data.
  • the first data corresponding to the service flow obtained by the first network element from the network element 1 is a flow identifier
  • the first data corresponding to the service flow obtained from the network element 2 is an identifier of the terminal.
  • the first data on the network element 1 carries the identifier 1
  • the first data on the network element 2 carries the identifier 2
  • there is a mapping relationship between the identifier 1 and the identifier 2 then the first network element can transfer the flow corresponding to the service flow.
  • the identifier is associated with the identifier of the terminal to obtain second data corresponding to the service flow. That is, the second data finally obtained includes the flow identifier and the terminal identifier corresponding to the service flow, as shown in Table 5:
  • the first data does not carry the first identifier, the PDU ID / QFI on the RAN device, the PDU ID / UE ID / timestamp on the AMF network element, and the PDU session ID / QFI / UE ID / timestamp, PDU session ID / QFI / timestamp on UPF network element, UE ID / application ID / timestamp on PCF network element, UE ID / application ID / timestamp on AF network element, Divide the first data sent by different network elements into the same set.
  • the first data on each network element corresponding to the service flow obtained by the first network element may also be sent to the first network element by the operation management and maintenance network element. Specifically, when determining that the first data corresponding to the service flow on the respective network element needs to be reported, each network element sends the first data corresponding to the service flow on the respective network element to the operation management and maintenance network element, so that the operation management The maintenance network element sends it to the first network element.
  • Table 5 uses the first network element to associate the first data on network element 1 with the second data on network element 2 as an example. It can be understood that in actual process, if the first data also includes: at the time stamp, the first network element may choose to only include at least a part of the first data corresponding to the service flow on the network element 1 and all the data on the network element 2 corresponding to the service flow. Or at least a part of the data is divided into a set to obtain the second data.
  • the first network element obtains different first data corresponding to the service flow on different network elements from at least two network elements, but the first network element may according to its own requirements, Selecting all or part of the first data on some network elements from at least two network elements into the same set to obtain the second data, which is not limited in this embodiment of the present application.
  • An embodiment of the present application provides a data processing method.
  • the first data of a service flow on different network elements is obtained through a first network element, and the service flow is changed in different ways according to the first identifier in the first data sent by the different network elements.
  • the first data on the network element is correlated to obtain the second data, which is convenient for the first network element to subsequently plan one or more sets of QoS parameters of the service to which the service flow belongs, the user plane path and slice resource corresponding to the session to which the service flow belongs. Optimization, control plane or user plane anomaly detection, etc.
  • the method provided in this embodiment of the present application further includes:
  • the second network element sends a first message to the first network element, where the first message is used to instruct the first network element to obtain first data corresponding to the service flow from at least two network elements, where the first message includes the following information One or more of the following: a service identifier to which the service flow belongs, a terminal type of a terminal corresponding to the service flow, a network area where the terminal corresponding to the service flow is located, and a time window corresponding to the service flow.
  • the first message may also carry the identities of at least two network elements and the identities of the second network elements.
  • the first message may further include one or more of the following information: one or more service identifiers other than the service identifier to which the service flow belongs, and one of the terminal types of the terminals corresponding to the service flow.
  • One or more other terminal types one or more network areas other than the network area where the terminal corresponding to the service flow is located, one or more time windows corresponding to the service flow time window.
  • the service identifier to which the service flow belongs is used to determine the service to which the service flow belongs.
  • the terminal type of the terminal corresponding to the service flow is used to determine the terminal type corresponding to the service flow.
  • the time window corresponding to the service flow is used to determine a list of time periods corresponding to the service flow, for example, from March 1, 2018 to March 8, 2018.
  • the network area where the terminal corresponding to the service flow is located for example, a tracking area (TA) or a TA list or a routing area (RA) or an RA list).
  • the second network element may be an AF network element
  • the first network element may be an NWDAF network element.
  • the AF may send the first message to the NWDAF network element through the PCF network element.
  • the first message may be a newly defined message between the first network element and the second network element, or may be an existing message between the first network element and the second network element, which is not limited in this embodiment of the present application.
  • the first message may be a Naf_DataCollectionCondition_Notify message.
  • the first network element receives a first message sent by the second network element.
  • the first network element can determine that the first data corresponding to the service flow needs to be collected from different network elements.
  • step S106 may further include: S107.
  • the first network element sends a first response to the second network element, where the first response is used to indicate that the first network element has received the first message.
  • steps S105 to S107 can be implemented alone or in combination with the above steps S101 to S104.
  • the S105 to S107 can be implemented before step S101.
  • the method provided in the embodiment of the present application further includes:
  • the first network element sends a first request to each of the at least two network elements.
  • the first request is used to request the first data corresponding to the service flow on each network element.
  • the first request includes the following information: One or more of the following: the service identifier to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, the network area where the terminal corresponding to the service flow is located, and the time window corresponding to the service flow.
  • the first request may further include one or more of the following information: one or more service identifiers other than the service identifier to which the service flow belongs, and one of the terminal types of the terminals corresponding to the service flow.
  • One or more other terminal types one or more network areas other than the network area where the terminal corresponding to the service flow is located, one or more time windows corresponding to the service flow time window.
  • the first request sent by the first network element to the network element may be an Npcf_NetworkDataCollectionSubscription request message.
  • the first request sent by the first network element to the network element may be a Naf_ServiceDataCollectionSubsctiption request message.
  • the network element sending the first request by the first network element may be the same network element as the network element receiving the first message, or it may be a different network element.
  • the AF1 network element sends a first message to the first network element, but the first network element requests the first data corresponding to the service flow from the AF2 network element.
  • At least two network elements receive a first request sent by a first network element.
  • the method may further include: S110.
  • Each of the at least two network elements sends a second response to the first request to the first network element. Yu indicates that the network element receives the first request.
  • the second response is: a Naf_ServiceDataCollectionSubsctiptionResponse message.
  • the second response is: Npcf_NetworkDataCollectionSubscriptionResponse message.
  • the method may further include: S111. At least two network elements send a second message to the first network element, where the second message carries the service flow corresponding to the respective network element. First data. S112. The first network element receives a second message sent by at least two network elements. Based on steps S111 and S112, step S103 in the present application is implemented in the following manner: the first network element obtains, from the second message sent by each network element, the first data corresponding to the service flow on each network element.
  • the first data sent by each network element to the first network element further includes one or more of the following information: the identifier of the network element where the first data corresponding to the service flow is located, and the A data value identifying at least one data type of at least one of the at least two network elements.
  • the first data is sent by the AF network element to the first network element, and the first data sent by the AF network element to the first network element further carries the identifier of the AF network element.
  • the data value of at least one data type of at least one of the at least two network elements refers to the first data sent by the network element to the first network element, which may carry the data value of the data type of the network element. Or the first data sent by the network element to the first network element may not only carry data values of the data type of the network element, but also may carry one or more other networks of the at least two network elements except the network element.
  • the data value of the metadata's data type For example, the first data sent by the AF network element to the first network element may carry data values of the data type of the AF network element and data values of the data type of the PCF network element.
  • the network element may further include: The following steps are performed to normalize the first data to obtain data values of the data types of each network element:
  • Each of the at least two network elements determines a second data value according to the first data value of the first data type of the respective network element, where the first data value belongs to the first numerical space and the second data value belongs to the first Two numerical spaces, the first data type is any one of the first data.
  • the method may further include:
  • Each network element determines a fourth data value according to the third data value of the second data type of the respective network element, where the third data value belongs to the third numerical space, the fourth data value belongs to the fourth numerical space, and the second The data type is any one of the first data.
  • the second numerical space is the same as the fourth numerical space. It is convenient for the first network element to process.
  • the normalization space of all data types is the same, and it is not further normalized to the same numerical space without NWDAF.
  • performing normalization processing on the first data to obtain data values of respective data types of each network element may further include: each of the at least two network elements is based on a third data type of the respective network element.
  • the fifth data value determines a sixth data value, wherein the fifth data value belongs to a fifth numerical space and the sixth data value belongs to a sixth numerical space.
  • the second numerical space is the same as the sixth numerical space.
  • Each of the at least two network elements may determine the second data value according to the first data value of the first data type of the respective network element or the third data value according to the second data type of the respective network element through normalization processing.
  • the data value determines the fourth data value or the sixth data value according to the fifth data value of the third data type of the respective network element.
  • the normalization process includes mapping the physical data value of the data type to a fixed numerical space. .
  • the normalization process mainly uses the maximum and minimum normalization method, Z-Score normalization method, etc. to map the physical data value of each data type to a fixed numerical space. In the process of data analysis, the model training convergence speed is improved, and on the other hand, a feature data transmission method is provided.
  • the first data obtained from the third network element may also have some information:
  • the first data obtained from the third network element further includes one or more of the following information: a service identifier to which the service flow belongs, and communication of a service to which the service flow belongs. Mode parameters, first interface stream bit rate data, first interface delay data, first interface packet loss rate data, first interface packet data, timestamp, service experience data to which the service flow belongs, jitter buffer data, and transmission control protocol TCP congestion window data, TCP reception window data, media encoding type data and media encoding type data and encoding rate data.
  • the first interface is an interface between the user plane function network element and the data network DN corresponding to the AF network element. Exemplarily, as shown in FIG. 3, the first interface may be an N6 interface.
  • the first data obtained from the third network element further includes one or more of the following information: the service identifier to which the service flow belongs, and the identifier of the session in which the service flow belongs , Data network name DNN of the session where the service flow is located, identification information of the slice where the service flow is located, IP filtering information, media bandwidth requirements, traffic routing information, jitter buffering requirements, TCP congestion window requirements, TCP receiving window requirements, media encoding type requirements, The encoding rate required by the media encoding type and the valid time window of the service identification.
  • the first data obtained from the third network element further includes one or more of the following information: the identifier of the service flow, the identifier of the session in which the service flow is located, and the session in which the service flow is located.
  • the DNN the identification information of the slice where the business flow is located, and the valid time window of the identification of the business flow.
  • the first data obtained from the third network element further includes one or more of the following information: an identification of the service flow, a time stamp, and a bit rate of the second interface flow Data, first interface stream bit rate data, third interface bit rate data, second interface delay data, first interface delay data, third interface delay data, first interface packet loss rate data, second interface loss Packet rate data, third interface packet loss rate data, first interface packet data, second interface packet data, and third interface packet data.
  • the second interface is an interface between the first UPF network element and the RAN device.
  • the third interface is an interface between the first UPF network element and the second UPF network element. Exemplarily, the second interface may be an N3 interface as shown in FIG. 3.
  • the third interface is an N9 interface.
  • the first data obtained from the third network element further includes at least one of the following information: the location information of the terminal corresponding to the service flow, the identifier of the session where the service flow is located, and the service flow The DNN of the session, the identification information of the slice where the service flow is located, and the valid time window of the identifier of the session where the service flow is located.
  • the first data obtained from the third network element further includes one or more of the following information: the location information of the terminal corresponding to the service flow, the identification of the service flow, and the location of the service flow Session identification, identification information of the slice where the service flow is located, timestamp, bit rate data of the fourth interface stream, bit rate data of the second interface stream, second interface delay data, fourth interface delay data, reference signal received power RSRP Data, reference signal reception quality RSRQ data, signal interference to noise ratio (SINR) data, CQI data, BLER data, congestion level, second interface packet loss rate data, fourth interface packet loss rate data, The second interface packet data and the fourth interface packet data.
  • the fourth interface is an interface between the RAN device and the terminal. For example, the Uu interface shown in FIG. 3.
  • the first data obtained from the third network element further includes one or more of the following information: the location information of the terminal corresponding to the service flow, the identification of the service flow, and the session where the service flow is located ID of the session, DNN of the session where the service flow is located, identification information of the slice where the service flow is located, bit rate data of the fourth interface stream, fourth interface delay data, fourth interface packet loss rate data, fourth interface packet data, timestamp, Service experience data, jitter buffer data, transmission control protocol TCP congestion window data, TCP reception window data, media encoding type data, media encoding data encoding rate data, RSRP data, RSRQ data, SINR data, CQI data, and BLER data.
  • the method provided in the embodiment of the present application further includes:
  • the fifth network element sends a second request to at least two network elements, where the second request is used to request establishment of a service flow, and the second request includes one or more of the following information: a service identifier to which the service flow belongs, IP filtering information, media bandwidth requirements, traffic routing information, jitter buffering requirements, TCP congestion window requirements, TCP receiving window requirements, media encoding type requirements, and encoding rate requirements for media encoding type requirements.
  • the fifth network element may be an AF network element.
  • the second request may be completed between the 3rd AF network element and the PCF network element through the NEF network element. Interaction.
  • the second request may be an Npcf_PolicyAuthorization_Create Request message.
  • At least two network elements receive a second request sent by a fifth network element.
  • the method provided in this embodiment of the present application further includes:
  • the fourth network element sends a third request to the first network element, where the third request is used to request that a first identifier be allocated to a service flow.
  • the fourth network element may be a PCF network element or an SMF network element.
  • the third request may be a Nnwaf_CorrelationIDAssignment Request message.
  • the third request may carry a service identifier to which the service flow belongs, an identifier of a session in which the service flow is located, and an identifier of a terminal corresponding to the service flow.
  • one request can request the correlation ID list of multiple SDFs in a PDU session ID.
  • the first network element receives a third request sent by the fourth network element.
  • the first network element sends a third response to the third network element, and the third response includes the first identifier.
  • the third response may be a Nnwdaf_CorrelacationIDAssignmentResponse message.
  • the method may further include:
  • the first network element determines at least one piece of service quality of service QoS description information according to the second data, where each piece of QoS description information in the at least one piece of QoS description information includes a QoS parameter type and / or a QoS parameter requirement.
  • each piece of QoS description information in the at least one piece of QoS description information further includes network element information, and the network element information is used to indicate a network element corresponding to a QoS parameter requirement.
  • step S101 in the embodiment of the present application may be implemented in the following ways:
  • the network element When the network element is a PCF network element, the network element sends a third request to the server network element.
  • the third request is used to request the first identity, and the third request includes the service identity and the identity of the terminal.
  • the network element receives a third response from the server network element, and the third response includes the first identifier.
  • the server network element may be a data analysis network element or a network function storage function network element or a domain name server.
  • the AF network element may obtain the first identifier from the second response to the second request sent by the PCF network element.
  • the SMF network element may obtain the first identifier from the PCF network element.
  • the PCF network element may send the first identifier corresponding to the service flow to the SMF network element through the Npcf_SMPolicyControl_UpdateNotify request message.
  • the network element is a UPF network element.
  • the SMF network element may send the first identification to the UPF network element.
  • the SMF network element may send the first identifier corresponding to the service flow to the UPF network element through the N4Session Modification Request / Response, that is, the N4 session modification process. That is, the UPF network element can obtain the first identity from the SMF network element through the N4 session modification process.
  • Case 5 When the network element is an AMF network element, specifically, after the SMF network element obtains the first identity, the SMF network element may send the first identity to the AMF network element, that is, the AMF network element may be from the SMF network element Obtain the first identity. It can be understood that Case 5 further includes a process in which the PCF network element sends the first identifier to the AMF network element through the SMF network element.
  • the SMF network element may send the first identifier to the AMF network element through a Namf_Communication_N1N2MessageTransfer message.
  • the RAN device receives the first identifier sent by the AMF network element or the SMF network element. That is, after the AMF network element or the SMF network element has the first identity, the AMF network element or the SMF network element may send the first identity to the RAN device. For example, the AMF network element may send the first identity to the RAN device through an N2Session request. It can be understood that the case 6 also includes a case where the PCF network element sends the first identifier to the RAN device through the AMF network element or the SMF network element.
  • the terminal receives the first identifier sent by the RAN device, AMF network element, or SMF network element, that is, after the RAN device, AMF network element, or SMF network element has the first identifier, the first identifier may be Send to the terminal, or the PCF network element may send the first identity to the terminal through the AMF network element, the SMF network element, or the RAN device.
  • each network element such as a data processing device and a data sending device, includes a hardware structure and / or a software module corresponding to each function.
  • this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
  • the functional processing unit and the data sending apparatus may be divided into functional units according to the foregoing method.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit. It should be noted that the division of the units in the embodiments of the present application is schematic, and is only a logical function division. In actual implementation, there may be another division manner.
  • FIG. 11 shows a possible structural diagram of a data processing device involved in the foregoing embodiment.
  • the data processing device may be a first network element or applied to a first network. Meta chip.
  • the data processing apparatus includes: an obtaining unit 201 and a processing unit 202.
  • the obtaining unit 201 is configured to support the data processing apparatus to execute step S103 in the foregoing embodiment.
  • the processing unit 202 is configured to support the data processing apparatus to execute step S104 in the foregoing embodiment.
  • the data processing apparatus further includes: a receiving unit 203, a sending unit 204, and a determining unit 205, where the receiving unit 203 is configured to support the data processing apparatus to execute steps S106 and S118 in the foregoing embodiment.
  • the sending unit 204 is used to support the data processing device to execute steps S107, S108, S119, and S112 in the above-mentioned embodiment.
  • the determining unit 205 is configured to instruct the data processing apparatus to execute step S110 in the foregoing embodiment. All relevant content of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.
  • FIG. 12 shows a schematic diagram of a possible logical structure of the data processing device involved in the foregoing embodiment, and the data processing device may be the first network element in the foregoing embodiment, or It is a chip applied in the first network element.
  • the data processing apparatus includes a processing module 212 and a communication module 213.
  • the processing module 212 is configured to control and manage the actions of the data processing device.
  • the processing module 212 is configured to perform the steps of performing message or data processing on the data processing device side.
  • the data processing device is supported to execute S104 and S110.
  • the communication module 213 is used to support the data processing device to execute S103, S107, S108, S119, and S112 in the above embodiments. And / or other processes performed by data processing devices for the techniques described herein.
  • the data processing apparatus may further include a storage module 211 for storing program code and data of the data processing apparatus.
  • the processing module 212 may be a processor or a controller, for example, it may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, Hardware components or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure.
  • the processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the communication module 213 may be a transceiver, a transceiver circuit, or a communication interface.
  • the storage module 211 may be a memory.
  • the processing module 212 is the processor 220
  • the communication module 213 is the communication interface 230 or the transceiver
  • the storage module 211 is the memory 240
  • the data processing apparatus involved in this application may be the device shown in FIG.
  • the communication interface 230, one or more (including two) processors 220, and the memory 240 are connected to each other through the bus 210.
  • the bus 210 may be a PCI bus, an EISA bus, or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 13, but it does not mean that there is only one bus or one type of bus.
  • the memory 240 is configured to store program codes and data of the data processing apparatus.
  • the communication interface 230 is used to support the data processing device to communicate with other devices (for example, a network element and a second network element), and the processor 220 is used to support the data processing device to execute the program code and data stored in the memory 240 to implement the application provided in this application S103, S104, S107, S108, S119, S110, and S112.
  • FIG. 14 shows a possible structural diagram of a data sending device involved in the foregoing embodiment, and the data sending device may be a network element or a chip in the network element.
  • the data sending apparatus includes a determining unit 301 and a sending unit 302.
  • the determining unit 301 is configured to support the data sending device to perform steps S101, S113, and S114 in the foregoing embodiment.
  • the sending unit 302 is configured to support the data sending device to perform steps S102 and S111 in the foregoing embodiment.
  • the data sending apparatus may further include: a receiving unit 303, configured to support the data sending apparatus to perform steps S109 and S116 in the foregoing embodiment. All relevant content of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.
  • FIG. 15 shows a schematic diagram of a possible logical structure of the data sending device involved in the foregoing embodiment, and the data sending device may be a network element in the foregoing embodiment or an application Chips in network elements.
  • the data sending device includes a processing module 312 and a communication module 313.
  • the processing module 312 is configured to control and manage the actions of the data sending device.
  • the processing module 312 is configured to perform steps of performing message or data processing on the data sending device side, for example, S101, S113, and S114.
  • the communication module 313 is used to support the data transmitting device to execute S102, S111, S109, and S116 in the above embodiments. And / or other processes performed by the data sending device for the techniques described herein.
  • the data sending device may further include a storage module 311 for storing program code and data of the data sending device.
  • the processing module 312 may be a processor or a controller, for example, it may be a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, Hardware components or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure.
  • the processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the communication module 313 may be a transceiver, a transceiver circuit, or a communication interface.
  • the storage module 311 may be a memory.
  • the processing module 312 is the processor 320
  • the communication module 313 is the communication interface 330 or the transceiver
  • the storage module 311 is the memory 340
  • the data sending device involved in this application may be the device shown in FIG.
  • the communication interface 330, one or more (including two) processors 320, and the memory 340 are connected to each other through a bus 310.
  • the bus 310 may be a PCI bus, an EISA bus, or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 16, but it does not mean that there is only one bus or one type of bus.
  • the memory 340 is configured to store program codes and data of the data sending device.
  • the communication interface 330 is used to support the data sending device to communicate with other devices (for example, the first network element), and the processor 320 is used to support the data sending device to execute the program code and data stored in the memory 340 to implement S101 and S113 provided in this application. , S114, S102, S111, S109, and S116.
  • FIG. 17 shows another possible structure diagram of the data sending device involved in the foregoing embodiment.
  • the data sending device may be a second network element, or may be applied to a second network element.
  • the data sending device includes a sending unit 401.
  • the sending unit 401 is configured to support the data sending device to execute S105 in the foregoing embodiment. All relevant content of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here.
  • FIG. 18 shows a schematic diagram of a possible logical structure of the data sending device involved in the foregoing embodiment.
  • the data sending device may be the second network element in the foregoing embodiment, or a chip applied in the second network element.
  • the data sending device includes a processing module 412 and a communication module 413.
  • the processing module 412 is configured to control and manage the operations of the data sending device.
  • the processing module 412 is configured to perform steps of performing message or data processing on the data sending device side.
  • the supporting data transmitting device executes S105 in the above-mentioned embodiment.
  • the communication module 413 is configured to support the data sending device to execute S105 in the foregoing embodiment. And / or other processes performed by the data sending device for the techniques described herein.
  • the data sending device may further include a storage module 411 for storing program code and data of the data sending device.
  • the processing module 412 may be a processor or a controller.
  • the processing module 412 may be a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or other programmable logic devices, transistor logic devices, Hardware components or any combination thereof. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure.
  • a processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the communication module 413 may be a transceiver, a transceiver circuit, or a communication interface.
  • the storage module 411 may be a memory.
  • the processing module 412 is the processor 420
  • the communication module 413 is the communication interface 430 or the transceiver
  • the storage module 411 is the memory 440
  • the data sending device involved in this application may be the device shown in FIG.
  • the communication interface 430, one or more (including two) processors 420, and the memory 440 are connected to each other through a bus 410.
  • the bus 410 may be a PCI bus, an EISA bus, or the like.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only a thick line is used in FIG. 19, but it does not mean that there is only one bus or one type of bus.
  • the memory 440 is configured to store program code and data of the data sending device.
  • the communication interface 430 is used to support the data sending device to communicate with other devices, and the processor 420 is used to support the data sending device to execute the program code and data stored in the memory 440 to implement S105 provided in this application.
  • FIG. 20 is a schematic structural diagram of a chip 150 according to an embodiment of the present invention.
  • the chip 150 includes one or more (including two) processors 1510 and an interface circuit 1530.
  • the chip 150 further includes a memory 1540.
  • the memory 1540 may include a read-only memory and a random access memory, and provide operation instructions and data to the processor 1510.
  • a part of the memory 1540 may further include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 1540 stores the following elements, executable modules or data structures, or their subsets, or their extended sets:
  • a corresponding operation is performed by calling an operation instruction stored in the memory 1540 (the operation instruction may be stored in an operating system).
  • a possible implementation manner is as follows: the first network element, the network element, and the second network element have similar chip structures, and different devices may use different chips to implement respective functions.
  • the processor 1510 controls operations of the first network element, the network element, and the second network element.
  • the processor 1510 may also be referred to as a central processing unit (CPU).
  • the memory 1540 may include a read-only memory and a random access memory, and provide instructions and data to the processor 1510.
  • a part of the memory 1540 may further include a non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • the memory 1540, the interface circuit 1530, and the memory 1540 are coupled together through a bus system 1520.
  • the bus system 1520 may include a power bus, a control bus, and a status signal bus in addition to a data bus. However, for the sake of clarity, various buses are marked as the bus system 1520 in FIG. 20.
  • the method disclosed in the foregoing embodiment of the present invention may be applied to the processor 1510, or implemented by the processor 1510.
  • the processor 1510 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 1510 or an instruction in the form of software.
  • the above-mentioned processor 1510 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or Other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • Various methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or executed.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a random storage, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and other mature storage media in the field.
  • the storage medium is located in the memory 1540, and the processor 1510 reads the information in the memory 1540 and completes the steps of the foregoing method in combination with its hardware.
  • the interface circuit 1530 is configured to execute the first network element, the network element, and the second network element in the embodiments shown in FIG. 4, FIG. 5, FIG. 6, FIG. 7, FIG. 8, FIG. 9, and FIG. Receiving and sending steps.
  • the processor 1510 is configured to execute the processing steps of the first network element, the network element, and the second network element in the embodiments shown in FIGS. 4, 5, 6, 7, 8, 9, and 10.
  • the instructions stored in the memory for execution by the processor may be implemented in the form of a computer program product.
  • the computer program product may be written in the memory in advance, or may be downloaded and installed in the memory in the form of software.
  • a computer program product includes one or more computer instructions.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center via a wired (e.g., Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server or data center.
  • a wired e.g., Coaxial cable, optical fiber, digital subscriber line (DSL)
  • wireless such as infrared, wireless, microwave, etc.
  • the computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server, a data center, and the like that includes one or more available mediums integrated.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • a computer storage medium stores instructions.
  • the first network element or a chip applied to the first network element executes S103, S104, S107, S108, S119 and S110, S112. And / or other processes performed by the first network element or a chip applied in the first network element for the techniques described herein.
  • a computer storage medium stores instructions.
  • the network element or a chip applied to the network element executes S101, S113, and S114, S102 in the embodiment. , S111, S109, and S116. And / or other processes performed by a network element or a chip applied in a network element for the techniques described herein.
  • a computer storage medium stores instructions.
  • the second network element or a chip applied to the second network element executes S105 in the embodiment. And / or other processes performed by the second network element or a chip applied in the second network element for the techniques described herein.
  • the foregoing readable storage medium may include: various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.
  • a computer program product including instructions.
  • the computer program product stores instructions.
  • the first network element or a chip applied to the first network element executes S103 and S104 in the embodiment. , S107, S108, S119 and S110, S112. And / or other processes performed by the first network element or a chip applied in the first network element for the techniques described herein.
  • a computer program product including instructions.
  • the computer program product stores instructions.
  • the network element or a chip applied to the network element executes S101, S113, and S114 in the embodiment.
  • an embodiment of the present application provides a computer program product including instructions.
  • the computer program product stores instructions.
  • the instructions are executed, the second network element or a chip applied to the second network element executes the embodiment.
  • S105 And / or other processes performed by the second network element or a chip applied in the second network element for the techniques described herein.
  • a chip is provided.
  • the chip is used in a first network element.
  • the chip includes one or more (including two) processors and interface circuits, and the interface circuit and the one or more (including two) processors.
  • the processors are interconnected through lines, and the processors are used to run instructions to execute S103, S104, S107, S108, S119, and S110, S112 in the embodiment. And / or other processes performed by the first network element for the techniques described herein.
  • a chip is provided.
  • the chip is used in a network element.
  • the chip includes one or more (including two) processors and interface circuits, and the interface circuit and the one or more (including two) processors
  • the processors are interconnected through lines, and the processor is used to execute instructions to execute S101, S113 and S114, S102, S111, S109, and S116 in the embodiments. And / or other processes performed by network elements for the techniques described herein.
  • a chip is provided.
  • the chip is applied to a second network element, and the chip includes one or more (including two) processors and interface circuits, and the interface circuit and the one or more (including two) processors
  • the processors are interconnected through lines, and the processors are used to run instructions to execute S105 in the embodiment. And / or other processes performed by the second network element for the techniques described herein.
  • the present application also provides a data processing system.
  • the data processing system includes a data processing device shown in FIG. 11 to FIG. 13, and a data sending device shown in FIG. 14 to FIG. 16.
  • the data processing system further includes: a data sending device shown in FIG. 17 to FIG. 19.
  • the above 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 whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center via a wired (for example, Coaxial cable, optical fiber, digital subscriber line (DSL), or wireless (such as infrared, wireless, microwave, etc.) for transmission to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, and the like that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (solid state disk (SSD)), and the like.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a DVD
  • a semiconductor medium for example, a solid state disk (solid state disk (SSD)

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例涉及通信技术领域,尤其涉及一种数据处理方法、发送方法及装置,用以获取业务流在不同网元上分布的数据,该方案包括:第一网元获取业务流对应的在至少两个网元中每个网元上的第一数据,其中,所述业务流对应的在每个网元上的第一数据包括第一标识;所述第一网元根据所述第一标识,以及所述业务流对应的在每个网元上的第一数据,得到所述业务流对应的第二数据,第二数据中至少包括业务流对应的在每个网元上的第一数据。

Description

一种数据处理方法、发送方法及装置
本申请要求于2018年05月21日提交国家知识产权局、申请号为201810490222.4、申请名称为“一种数据处理方法、发送方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域,尤其涉及一种数据处理方法、发送方法及装置。
背景技术
在第15版本(release 15,R15)中,核心网侧策略控制功能(policy control function,PCF)网元为一个业务生成一套服务质量(quality of service,QoS)参数,而网络数据和业务数据会随着时间的变化而变化,从而导致了业务体验的变化,因此仅一套QoS参数无法满足不断变化的网络环境(对应网络数据)和业务需求(对应业务数据)。如图1所示,业务从第一时间T1(图1中的时间戳为0000)开始,到第二时间T2(图1中的时间戳为0012)结束。在T2和T1时间段内(以12秒(second,s)为例),每隔1s计算一次平均意见分(mean opinion score,MOS)。
由图1可以知道,导致不同的时间点对应的语音MOS变化的根本原因在于网络状况以及部分业务参数的时变性(指网络数据以及业务数据随着时间变化的特性)。例如,终端上无线信道质量、带宽、时延、丢包率、抖动缓存、传输控制协议(transmission control protocol,TCP)拥塞窗口、TCP接收窗口等。接入网空口上无线信道质量、带宽、时延、丢包率、拥塞等级等。核心网侧用户面带宽、用户面负载信息等。业务层TCP拥塞窗口、TCP接收窗口、媒体编码类型或者编码速率等。这些终端、接入网、核心网、业务层的时变性参数,影响了业务体验。
在5G系统中,终端的业务承载于一个业务流上,这个业务流可以是服务质量流,即QoS flow,也可以是业务数据流,即service data flow,因此业务体验的变化,实际上是相对于一个业务流的体验变化,对应于终端、接入网、核心网、业务层的参数的变化。因此,如何按照业务流级别获取不同网元上分布的参数是当下亟需解决的技术问题。
发明内容
本申请实施例提供一种数据处理方法、发送方法及装置,用以获取业务流在不同网元上分布的数据。
为了达到上述目的,本申请实施例采用如下技术方案:
第一方面,本申请实施例提供一种数据处理方法,包括:第一网元获取业务流对应的在至少两个网元中每个网元上的第一数据。其中,该业务流对应的在每个网元上的第一数据包括第一标识。第一网元根据第一标识,以及业务流对应的在每个网元上的第一数据,得到业务流对应的第二数据,所述第二数据中至少包括业务流对应的在每个网元上的第一数据,或者,所述第二数据至少包括业务流对应的在每个网元上的第一数据的一部分。
本申请实施例提供一种数据处理方法,通过第一网元获取业务流在不同网元上的第一数据,并根据不同网元发送的第一数据中的第一标识,将业务流在不同网元上的第一数据进行关联以得到第二数据,这样便于第一网元后续规划业务流所属的业务的一套或者多套QoS参数、业务流所属的会话对应的用户面路径、切片资源优化、控制面或者用户面异常检测等等。
结合第一方面,在第一方面的第一种可能的实现方式中,本申请实施例提供的方法还包括:第一网元接收第二网元发送的用于指示第一网元从至少两个网元获取业务流对应的第一数据的第一消息。其中,第一消息包括以下信息中的一项或者多项:业务流所属的业务标识、业务流对应的终端的终端类型、业务流对应的终端所在的网络区域和业务流对应的时间窗。通过第一消息向第一网元发送需求,这样第一网元便可以确定需要从不同网元处获取业务流对应的在不同网元上的第一数据。由于第一消息中还携带业务流对应的时间窗,这样,第一网元便可以获取在不同网元上随着时间变化对应的数据。
结合第一方面或第一方面的第一种可能的实现方式中,在第一方面的第二种可能的实现方式中,本申请实施例提供的方法还包括:第一网元向至少两个网元中每个网元发送第一请求,该第一请求用于请求业务流对应的在每个网元上的第一数据,第一请求包括以下信息中的一项或者多项:业务流所属的业务标识、业务流对应的终端的终端类型、业务流对应的终端所在的网络区域和业务流对应的时间窗。这样便于每个网元在接收到第一请求以后,明确第一网元的需求,以便反馈业务流对应的在该网元上满足第一网元需求的第一数据。
结合第一方面至第一方面的第二种可能的实现方式中任一项,在第一方面的第三种可能的实现方式中,第一网元获取业务流对应的在至少两个网元中每个网元上的第一数据,包括:第一网元接收每个网元发送的包括业务流对应的在每个网元上的第一数据的第二消息。
结合第一方面至第一方面的第三种可能的实现方式中任一项,在第一方面的第四种可能的实现方式中,第一数据还包括以下信息中的一项或者多项:业务流对应的第一数据所在的网元的标识、终端的标识、至少两个网元中至少一个网元的至少一个数据类型的数据值。使得第一数据所涵盖的信息更加多样化。
示例性的,本申请实施例中的终端的标识可以为以下一个或者多个:网际协议地址(internet protocol,IP)、签约永久标识(subscription permanent identifier,SUPI)、永久设备标识(permanent equipment identifier,PEI)、通用公共签约标识(generic public subscription identifier,GPSI)、国际移动用户标识符(international mobile subscriber identifier,IMSI)、国际移动设备标识(international mobile equipment identity,IMEI)、IP五元组(5-tuple)和移动台国际综合业务数字网络号码(mobile station international integrated service digital network number,MSISDN)。下述实施例中但凡涉及到终端的标识均可以参考此处的描述,后续不再赘述。
结合第一方面至第一方面的第四种可能的实现方式中任一项,在第一方面的第五种可能的实现方式中,至少两个网元中包括第三网元,当第三网元为应用功能AF网元时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流所属 的业务标识、业务流所属的业务的通信模式参数、第一接口流比特率数据、第一接口时延数据、第一接口丢包率数据、第一接口包数据、时间戳、业务流所属的业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据和媒体编码类型数据的编码速率数据、缓存数据;其中,第一接口为用户面功能UPF网元和AF网元对应的数据网络DN之间的接口。当第三网元为策略控制功能PCF网元时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流所属的业务标识、业务流所在会话的标识、业务流所在会话的数据网络名称DNN、业务流所在切片的标识信息、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、媒体编码类型要求的编码速率要求和业务标识的有效时间窗、无线接入技术类型。当第三网元为会话管理功能SMF网元时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息和业务流的标识的有效时间窗、无线接入技术类型。当第三网元为第一UPF网元时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流的标识、时间戳、第二接口流比特率数据、第一接口流比特率数据、第三接口比特率数据、第二接口时延数据、第一接口时延数据、第三接口时延数据、第一接口丢包率数据、第二接口丢包率数据、第三接口丢包率数据、第一接口包数据、第二接口包数据和第三接口包数据。其中,第二接口为第一UPF网元和无线接入网RAN设备之间的接口;其中,第三接口为第一UPF网元与第二UPF网元之间的接口。当第三网元为接入和移动性管理AMF网元时,从第三网元获取到的第一数据还包括以下信息中的至少一项:业务流对应的终端的位置信息、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息和业务流所在会话的标识的有效时间窗、无线接入技术类型。当第三网元为RAN设备时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流对应的终端的位置信息、业务流的标识、业务流所在会话的标识、业务流所在切片的标识信息、时间戳、第四接口流比特率数据、第二接口流比特率数据、第二接口时延数据、第四接口时延数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据、误块率BLER数据、包率数据、第二接口包数据和第四接口包数据、无线接入技术类型、双连接指示信息;其中,第四接口为RAN设备与终端之间的接口。当第三网元为终端时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流对应的终端的位置信息、业务流的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息、第四接口流比特率数据、第四接口时延数据、第四接口丢包率数据、第四接口包数据、时间戳、CPU占用率数据、内存占用率数据、业务体验数据、抖动缓存数据、TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据、媒体编码类型数据的编码速率数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据和误块率BLER数据、缓存数据。在网元不同时,使得不同网元所反馈的第一数据的多样性更加丰富。
示例性的,切片的标识信息可以为如下信息中的一种或者多种:单网络切片选择 (single network slice selection assistance information,S-NSSAI)、网络切片实例(network slice instance,NSI)ID,其中S-NSSAI包括切片类型(slice type)、Tenant ID。下述实施例中但凡涉及到切片的标识信息均可以参考此处的描述,后续不再赘述。
示例性的,本申请实施例中的终端的位置信息可以为如下信息中的一种或者多种:RAN设备ID、小区(Cell)ID和全球定位系统(global positioning system,GPS)。下述实施例中但凡涉及到终端的位置信息均可以参考此处的描述,后续不再赘述。
结合第一方面至第一方面的第五种可能的实现方式中任一项,在第一方面的第六种可能的实现方式中,业务流对应的在每个网元上的第一数据所包括的第一标识为以下信息中的一项或者多项:业务流所属的业务标识、业务流的标识、终端的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息。第一标识的种类多样化,便于第一网元根据第一标识确定同一业务流对应的在不同网元上的第一数据。
结合第一方面至第一方面的第六种可能的实现方式中任一项,在第一方面的第七种可能的实现方式中,业务流对应的在每个网元上的第一数据所包括的第一标识相同。
结合第一方面至第一方面的第七种可能的实现方式中任一项,在第一方面的第八种可能的实现方式中,本发明实施例提供的方法还包括:第一网元接收第四网元发送的第三请求,第三请求用于请求为业务流分配第一标识;第一网元向第三网元发送第三响应,第三响应包括第一标识。
结合第一方面至第一方面的第八种可能的实现方式中任一项,在第一方面的第九种可能的实现方式中,业务流为服务质量流或者业务数据流。
结合第一方面至第一方面的第九种可能的实现方式中任一项,在第一方面的第十种可能的实现方式中,第一网元获取业务流对应的在至少两个网元中每个网元上的第一数据,包括:第一网元接收运行管理维护网元发送的业务流对应的在至少两个网元中每个网元上的第一数据。
第二方面,本申请实施例提供一种数据处理方法,该方法包括:网元确定获取到业务流的第一标识,其中,第一标识用于标识业务流在网元上的第一数据;网元向第一网元发送第一数据,第一数据用于第一网元得到第二数据,其中,第二数据包括第一数据,或者,所述第二数据包括第一数据的一部分,第一数据中携带第一标识。
结合第二方面,在第二方面的第一种可能的实现方式中,本申请实施例提供的方法包括:网元接收第一网元发送的第一请求,该第一请求用于请求业务流对应的在网元上的第一数据,该第一请求中包括以下信息中的一项或者多项:业务流所属的业务标识、业务流对应的终端的终端类型、终端使用业务流时对应的网络区域和业务流对应的时间窗。
结合第二方面或第二方面的第一种可能的实现方式,在第二方面的第二种可能的实现方式中,第一数据还包括以下信息中的一项或者多项:业务流对应的第一数据所在的网元的标识、终端的标识、两个或两个以上网元中至少一个网元的至少一个数据类型的数据值。
结合第二方面至第二方面的第二种可能的实现方式中任一项,在第二方面的第三种可能的实现方式中,网元的数据类型的数据值,包括:网元根据网元的第一数据类 型的第一数据值确定第二数据值,其中,第一数据值属于第一数值空间,第二数据值属于第二数值空间,第一数据类型为第一数据中的任何一项。
结合第二方面至第二方面的第三种可能的实现方式中任一项,在第二方面的第四种可能的实现方式中,网元的数据类型的数据值,还包括:网元根据网元的第二数据类型的第三数据值确定第四数据值,其中,第三数据值属于第三数值空间,第四数据值属于第四数值空间,第二数据类型为第一数据中的任何一项。
结合第二方面至第二方面的第四种可能的实现方式中任一项,在第二方面的第五种可能的实现方式中,第二数值空间与第四数值空间相同。
结合第二方面至第二方面的第五种可能的实现方式中任一项,在第二方面的第六种可能的实现方式中,当网元为应用功能AF网元时,第一数据还包括以下信息中的一项或者多项:业务流所属的业务标识、业务流所属的业务的通信模式参数、第一接口流比特率数据、第一接口时延数据、第一接口丢包率数据、第一接口包数据、时间戳、业务流所属的业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据和媒体编码类型数据的编码速率数据、缓存数据;其中,第一接口为UPF网元和AF网元对应的数据网络DN之间的接口。当网元为策略控制功能PCF网元时,第一数据中还包括以下信息中的一项或者多项:业务流所属的业务标识、业务流所在会话的标识、业务流所在会话的数据网络名称DNN、业务流所在切片的标识信息、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、媒体编码类型要求的编码速率要求和业务标识的有效时间窗、无线接入技术类型。当网元为会话管理功能SMF网元时,第一数据还包括以下信息中的一项或者多项:业务流的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息和业务流的标识的有效时间窗、无线接入技术类型。当网元为第一UPF网元时,第一数据还包括以下信息中的一项或者多项:业务流的标识、时间戳、第二接口流比特率数据、第一接口流比特率数据、第三接口比特率数据、第二接口时延数据、第一接口时延数据、第三接口时延数据、第一接口丢包率数据、第二接口丢包率数据、第三接口丢包率数据、第一接口包数据、第二接口包数据和第三接口包数据;第二接口为第一UPF网元和无线接入网RAN设备之间的接口;其中,第三接口为第一UPF网元与第二UPF网元之间的接口。当网元为接入和移动性管理AMF网元时,第一数据还包括以下信息中的至少一项:业务流对应的终端的位置信息、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息和业务流所在会话的标识的有效时间窗、无线接入技术类型。当网元为RAN设备时,第一数据还包括以下信息中的一项或者多项:业务流对应的终端的位置信息、业务流的标识、业务流所在会话的标识、业务流所在切片的标识信息、时间戳、第四接口流比特率数据、第二接口流比特率数据、第二接口时延数据、第四接口时延数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据、误块率BLER数据、第二接口丢包率数据、第四接口丢包率数据、第二接口包数据和第四接口包数据、无线接入技术类型、双连接指示信息;其中,第四接口为RAN设备与终端之间的接口。当网元为终端时,第一数据还包括以下信息中的一项或者多项:使用业务流的终端的位 置信息、业务流的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息、第四接口流比特率数据、第四接口时延数据、第四接口丢包率数据、第四接口包数据、时间戳、处理器CPU占用率数据、内存占用率数据、业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据、媒体编码类型数据的编码速率数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据和误块率BLER数据、缓存数据。
结合第二方面至第二方面的第六种可能的实现方式中任一项,在第二方面的第七种可能的实现方式中,当网元为策略控制网元时,本申请实施例提供的方法还包括:网元接收应用功能AF网元发送的第二请求,该第二请求用于请求建立业务流,第二请求中包括以下信息中的一项或者多项:业务流所属的业务标识、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、媒体编码类型要求的编码速率要求、缓存要求、至少一个数据类型的要求。
结合第二方面至第二方面的第七种可能的实现方式中任一项,在第二方面的第八种可能的实现方式中,第一标识为以下信息中的一项或者多项:业务流所属的业务标识、业务流的标识、终端的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息。
结合第二方面至第二方面的第八种可能的实现方式中任一项,在第二方面的第九种可能的实现方式中,业务流为服务质量流或者业务数据流。
结合第二方面至第二方面的第九种可能的实现方式中任一项,在第二方面的第十种可能的实现方式中,网元向第一网元发送第一消息,第一消息用于指示第一网元从至少两个网元上获取业务流对应的第一数据,其中,第一消息包括以下信息中的一项或者多项:业务流所属的业务标识、业务流对应的终端的终端类型、业务流对应的终端所在的网络区域和业务流对应的时间窗。
结合第二方面至第二方面的第十种可能的实现方式中的任一项,在第二方面的第十一种可能的实现方式中,网元的数据类型的数据值,还包括:网元根据网元的第三数据类型的第五数据值确定第六数据值,其中,所述第五数据值属于第五数值空间,所述第六数据值属于第六数值空间,第三数据类型为第一数据中的任何一项。
结合第二方面至第二方面的第十一种可能的实现方式中的任一项,在第二方面的第十二种可能的实现方式中,第二数值空间、第四数值空间、第六数值空间两两相等。
结合第二方面至第二方面的第十二种可能的实现方式中任一项,在第二方面的第十三种可能的实现方式中,发送单元,用于向运行管理维护网元发送第一数据。
第三方面,本申请实施例提供一种数据发送方法,该方法包括:网元向第一网元发送用于指示第一网元从至少两个网元上获取业务流对应的第一数据的第一消息。其中,该第一消息包括以下信息中的一项或者多项:业务流所属的业务标识、业务流对应的终端的终端类型、业务流对应的终端所在的网络区域和业务流对应的时间窗。
第四方面,本申请提供一种数据处理装置,该数据处理装置可以实现第一方面或第一方面的任意可能的实现方式中的方法,因此也能实现第一方面或第一方面任意可 能的实现方式中的有益效果。该数据处理装置可以为第一网元,也可以为可以支持第一网元实现第一方面或第一方面的任意可能的实现方式中的方法的装置,例如应用于第一网元中的芯片。该装置可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
一种可能的设计,本申请实施例提供一种数据处理装置,该数据处理装置可以为第一网元或者为应用于第一网元中的芯片,该数据处理装置,包括:获取单元,用于获取业务流对应的在至少两个网元中每个网元上的第一数据,其中,业务流对应的在每个网元上的第一数据包括第一标识;处理单元,用于根据第一标识,以及业务流对应的在每个网元上的第一数据,得到业务流对应的第二数据,所述第二数据中至少包括业务流对应的在每个网元上的第一数据,或者,所述第二数据至少包括业务流对应的在每个网元上的第一数据的一部分。
结合第四方面,在第四方面的第一种可能的实现方式中,本申请实施例提供的装置还包括:接收单元,用于接收第二网元发送的第一消息,该第一消息用于指示第一网元从至少两个网元获取业务流对应的第一数据,其中,第一消息包括以下信息中的一项或者多项:业务流所属的业务标识、业务流对应的终端的终端类型、业务流对应的终端所在的网络区域和业务流对应的时间窗。
结合第四方面或第四方面的第一种可能的实现方式,在第四方面的第二种可能的实现方式中,本申请实施例提供的装置,还包括:发送单元,用于向至少两个网元中每个网元发送第一请求,该第一请求用于请求业务流对应的在每个网元上的第一数据,该第一请求包括以下信息中的一项或者多项:业务流所属的业务标识、业务流对应的终端的终端类型、业务流对应的终端所在的网络区域和业务流对应的时间窗。
结合第四方面至第四方面的第二种可能的实现方式中任一项,在第四方面的第三可能的实现方式中,接收单元,还用于接收每个网元发送的第二消息,第二消息包括业务流对应的在每个网元上的第一数据,获取单元,具体用于从每个网元发送的第二消息中获取业务流对应的在各自网元上的第一数据。
结合第四方面至第四方面的第三种可能的实现方式中任一项,在第四方面的第四可能的实现方式中,第一数据还包括以下信息中的一项或者多项:业务流对应的第一数据所在的网元的标识、终端的标识、至少两个网元中至少一个网元的至少一个数据类型的数据值。
结合第四方面至第四方面的第四种可能的实现方式中任一项,在第四方面的第五可能的实现方式中,至少两个网元中包括第三网元,当第三网元为应用功能AF网元时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流所属的业务标识、业务流所属的业务的通信模式参数、第一接口流比特率数据、第一接口时延数据、第一接口丢包率数据、第一接口包数据、时间戳、业务流所属的业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据和媒体编码类型数据的编码速率数据、缓存数据;其中,第一接口为用户面功能UPF网元和AF网元对应的数据网络DN之间的接口。当第三网元为策略控制功能PCF网元时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流所属的业务标识、业务流所在会话的标识、业务流所在会话的数据网络名称DNN、 业务流所在切片的标识信息、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、媒体编码类型要求的编码速率要求和业务标识的有效时间窗、无线接入技术类型。当第三网元为会话管理功能SMF网元时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息和业务流的标识的有效时间窗、无线接入技术类型。当第三网元为第一UPF网元时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流的标识、时间戳、第二接口流比特率数据、第一接口流比特率数据、第三接口比特率数据、第二接口时延数据、第一接口时延数据、第三接口时延数据、第一接口丢包率数据、第二接口丢包率数据、第三接口丢包率数据、第一接口包数据、第二接口包数据和第三接口包数据;其中,第二接口为第一UPF网元和无线接入网RAN设备之间的接口;其中,第三接口为第一UPF网元与第二UPF网元之间的接口。当第三网元为接入和移动性管理AMF网元时,从第三网元获取到的第一数据还包括以下信息中的至少一项:业务流对应的终端的位置信息、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息和业务流所在会话的标识的有效时间窗、无线接入技术类型。当第三网元为RAN设备时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流对应的终端的位置信息、业务流的标识、业务流所在会话的标识、业务流所在切片的标识信息、时间戳、第四接口流比特率数据、第二接口流比特率数据、第二接口时延数据、第四接口时延数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据、误块率BLER数据、第二接口丢包率数据、第四接口丢包率数据、第二接口包数据和第四接口包数据、无线接入技术类型、双连接指示信息;其中,第四接口为RAN设备与终端之间的接口。当第三网元为终端时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流对应的终端的位置信息、业务流的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息、第四接口流比特率数据、第四接口时延数据、第四接口丢包率数据、第四接口包数据、时间戳、处理器CPU占用率数据、内存占用率数据、业务体验数据、抖动缓存数据、TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据、媒体编码类型数据的编码速率数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据和误块率BLER数据、缓存数据。
结合第四方面至第四方面的第五种可能的实现方式中任一项,在第四方面的第六可能的实现方式中,业务流对应的在每个网元上的第一数据所包括的第一标识为以下信息中的一项或者多项:业务流所属的业务标识、业务流的标识、终端的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息。
结合第四方面至第四方面的第六种可能的实现方式中任一项,在第四方面的第七可能的实现方式中,业务流对应的在每个网元上的第一数据所包括的第一标识相同。
结合第四方面至第四方面的第七种可能的实现方式中任一项,在第四方面的第八可能的实现方式中,接收单元,还用于接收第四网元发送的第三请求,该第三请求用于请求为业务流分配第一标识;发送单元,用于向第三网元发送第三响应,第三响应 包括第一标识。
结合第四方面至第四方面的第八种可能的实现方式中任一项,在第四方面的第九可能的实现方式中,业务流为服务质量流或者业务数据流。
结合第四方面至第四方面的第九种可能的实现方式中的任一项,在第四方面的第十中可能的实现方式中,接收单元,用于接收运行管理维护网元发送的业务流对应的在至少两个网元中每个网元上的第一数据。
另一种可能的设计中,本申请实施例还提供一种数据处理装置,该数据处理装置可以为第一网元或者为应用于第一网元中的芯片,该装置包括:处理器和通信接口,其中,通信接口用于支持该装置执行第一方面至第一方面的任意一种可能的实现方式中所描述的在该装置侧进行消息/数据接收和发送的步骤。处理器用于支持该装置执行第一方面至第一方面的任意一种可能的实现方式中所描述的在该装置侧进行消息/数据处理的步骤。具体相应的步骤可以参考第一方面至第一方面的任意一种可能的实现方式中的描述,本申请实施例在此不再赘述。
可选的,该数据处理装置的通信接口和处理器相互耦合。
可选的,该数据处理装置还可以包括存储器,用于存储代码和数据,处理器、通信接口和存储器相互耦合。
第五方面,本申请提供一种数据发送装置,该数据发送装置可以实现第二方面或第二方面的任意可能的实现方式中的方法,因此也能实现第二方面或第二方面任意可能的实现方式中的有益效果。该数据发送装置可以为网元,也可以为可以支持网元实现第二方面或第二方面的任意可能的实现方式中的方法的装置,例如应用于网元中的芯片。该装置可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
一种可能的设计,本申请实施例提供一种数据发送装置,该数据发送装置可以为网元或者为应用于网元中的芯片,该数据发送装置,包括:确定单元,用于确定获取到业务流的第一标识,其中,第一标识用于标识业务流在网元上的第一数据;发送单元,用于向第一网元发送第一数据,所述第一数据用于第一网元得到第二数据,其中,第二数据包括第一数据,或者,所述第二数据至少包括第一数据的一部分,第一数据中携带第一标识。
结合第五方面,在第五方面的第一种可能的实现方式中,接收单元,用于接收第一网元发送的第一请求,该第一请求用于请求业务流对应的在网元上的第一数据,该第一请求中包括以下信息中的一项或者多项:业务流所属的业务标识、业务流对应的终端的终端类型、终端使用业务流时对应的网络区域和业务流对应的时间窗。
结合第五方面或第五方面的第一种可能的实现方式,在第五方面的第二种可能的实现方式中,第一数据还包括以下信息中的一项或者多项:业务流对应的第一数据所在的网元的标识、终端的标识、两个或两个以上网元中至少一个网元的至少一个数据类型的数据值。
结合第五方面至第五方面的第二种可能的实现方式中任一项,在第五方面的第三种可能的实现方式中,网元的数据类型的数据值,具体包括:确定单元,用于根据该装置的第一数据类型的第一数据值确定第二数据值,其中,第一数据值属于第一数值空间,第二数据值属于第二数值空间,第一数据类型为第一数据中的任何一项。
结合第五方面至第五方面的第三种可能的实现方式中任一项,在第五方面的第四种可能的实现方式中,网元的数据类型的数据值,还包括:确定单元,用于根据该装置的第二数据类型的第三数据值确定第四数据值,其中,第三数据值属于第三数值空间,第四数据值属于第四数值空间,第二数据类型为第一数据中的任何一项。
结合第五方面至第五方面的第四种可能的实现方式中任一项,在第五方面的第五种可能的实现方式中,第二数值空间与第四数值空间相同。
结合第五方面至第五方面的第五种可能的实现方式中任一项,在第五方面的第六种可能的实现方式中,当网元为应用功能AF网元时,第一数据还包括以下信息中的一项或者多项:业务流所属的业务标识、业务流所属的业务的通信模式参数、第一接口流比特率数据、第一接口时延数据、第一接口丢包率数据、第一接口包数据、时间戳、业务流所属的业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据和媒体编码类型数据的编码速率数据、缓存数据;其中,第一接口为用户面功能UPF网元和AF网元对应的数据网络DN之间的接口。当网元为策略控制功能PCF网元时,第一数据中还包括以下信息中的一项或者多项:业务流所属的业务标识、业务流所在会话的标识、业务流所在会话的数据网络名称DNN、业务流所在切片的标识信息、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、媒体编码类型要求的编码速率要求和业务标识的有效时间窗、无线接入技术类型。当网元为会话管理功能SMF网元时,第一数据还包括以下信息中的一项或者多项:业务流的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息和业务流的标识的有效时间窗、无线接入技术类型。当网元为第一UPF网元时,第一数据还包括以下信息中的一项或者多项:业务流的标识、时间戳、第二接口流比特率数据、第一接口流比特率数据、第三接口比特率数据、第二接口时延数据、第一接口时延数据、第三接口时延数据、第一接口丢包率数据、第二接口丢包率数据、第三接口丢包率数据、第一接口包数据、第二接口包数据和第三接口包数据;第二接口为第一UPF网元和无线接入网RAN设备之间的接口;其中,第三接口为第一UPF网元与第二UPF网元之间的接口。当网元为接入和移动性管理AMF网元时,第一数据还包括以下信息中的至少一项:业务流对应的终端的位置信息、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息和业务流所在会话的标识的有效时间窗、无线接入技术类型。当网元为RAN设备时,第一数据还包括以下信息中的一项或者多项:业务流对应的终端的位置信息、业务流的标识、业务流所在会话的标识、业务流所在切片的标识信息、时间戳、第四接口流比特率数据、第二接口流比特率数据、第二接口时延数据、第四接口时延数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据、误块率BLER数据、第二接口丢包率数据、第四接口丢包率数据、第二接口包数据和第四接口包数据、无线接入技术类型、双连接指示信息;其中,第四接口为RAN设备与终端之间的接口。当网元为终端时,第一数据还包括以下信息中的一项或者多项:使用业务流的终端的位置信息、业务流的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息、第四接口流比特率数据、第四接口时延数据、 第四接口丢包率数据、第四接口包数据、时间戳、处理器CPU占用率数据、内存占用率数据、业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据、媒体编码类型数据的编码速率数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据和误块率BLER数据、缓存数据。
结合第五方面至第五方面的第六种可能的实现方式中任一项,在第五方面的第七种可能的实现方式中,当装置为策略控制网元时,接收单元,还用于接收应用功能AF网元发送的第二请求,第二请求用于请求建立业务流,第二请求中包括以下信息中的一项或者多项:业务流所属的业务标识、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、媒体编码类型要求的编码速率要求、缓存要求、至少一个数据类型的要求。
结合第五方面至第五方面的第七种可能的实现方式中任一项,在第五方面的第八种可能的实现方式中,第一标识为以下信息中的一项或者多项:业务流所属的业务标识、业务流的标识、终端的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息。
结合第五方面至第五方面的第八种可能的实现方式中任一项,在第五方面的第九种可能的实现方式中,业务流为服务质量流或者业务数据流。
结合第五方面至第五方面的第九种可能的实现方式中的任一项,在第五方面的第十种可能的实现方式中,网元的数据类型的数据值,还包括:确定单元,用来根据该装置的第三数据类型的第五数据值确定第六数据值,其中,所述第五数据值属于第五数值空间,所述第六数据值属于所述第六数值空间,第三数据类型为第一数据中的任何一项。
结合第五方面至第五方面的第十种可能的实现方式中的任一项,在第五方面的第十一种可能的实现方式中,第二数值空间、第四数值空间、第六数值空间两两相等。
结合第五方面至第五方面的第十一种可能的实现方式中的任一项,在第五方面的第十二中可能的实现方式中,发送单元,向运行管理维护网元发送第一数据。
另一种可能的设计中,本申请实施例还提供一种数据发送装置,该数据发送装置可以为网元或者为应用于网元中的芯片,该数据发送装置包括:处理器和通信接口,其中,通信接口用于支持该数据发送装置执行第二方面至第二方面的任意一种可能的实现方式中所描述的在该数据发送装置侧进行消息/数据接收和发送的步骤。处理器用于支持该数据发送装置执行第二方面至第二方面的任意一种可能的实现方式中所描述的在该数据发送装置侧进行消息/数据处理的步骤。具体相应的步骤可以参考第二方面至第二方面的任意一种可能的实现方式中的描述,本申请实施例在此不再赘述。
可选的,该数据发送装置的通信接口和处理器相互耦合。
可选的,该数据发送装置还可以包括存储器,用于存储代码和数据,处理器、通信接口和存储器相互耦合。
第六方面,本申请提供一种数据发送装置,该数据发送装置可以实现第三方面或第三方面的任意可能的实现方式中的方法,因此也能实现第三方面或第三方面任意可能的实现方式中的有益效果。该数据发送装置可以为网元,也可以为可以支持网元实 现第三方面或第三方面的任意可能的实现方式中的方法的装置,例如应用于网元中的芯片。该装置可以通过软件、硬件、或者通过硬件执行相应的软件实现上述方法。
一种可能的设计,本申请实施例提供一种数据发送装置,该数据发送装置为网元或者为应用于网元中的芯片,该装置包括:发送单元,用于向第一网元发送用于指示第一网元从至少两个网元上获取业务流对应的第一数据的第一消息。其中,第一消息包括以下信息中的一项或者多项:业务流所属的业务标识、业务流对应的终端的终端类型、业务流对应的终端所在的网络区域和业务流对应的时间窗。
另一种可能的设计中,本申请实施例还提供一种数据发送装置,该数据发送装置可以为网元或者为应用于网元中的芯片,该数据发送装置包括:通信接口,其中,通信接口用于支持该数据发送装置执行第三方面至第三方面的任意一种可能的实现方式中所描述的在该数据发送装置侧进行消息/数据接收和发送的步骤。
可选的,该装置还包括:处理器用于支持该数据发送装置执行第三方面至第三方面的任意一种可能的实现方式中所描述的在该数据发送装置侧进行消息/数据处理的步骤。具体相应的步骤可以参考第三方面至第三方面的任意一种可能的实现方式中的描述,本申请实施例在此不再赘述。
可选的,该数据发送装置的通信接口和处理器相互耦合。
可选的,该数据发送装置还可以包括存储器,用于存储代码和数据,处理器、通信接口和存储器相互耦合。
第七方面,本申请提供一种计算机可读存储介质,该计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机执行第一方面和第一方面各种可能的实现方式中的一个或多个。
第八方面,本申请提供一种计算机可读存储介质,该计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机执行第二方面和第二方面各种可能的实现方式中的一个或多个。
第九方面,本申请提供一种计算机可读存储介质,该计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机执行第三方面和第五方面各种可能的实现方式中的一个或多个。
第十方面,本申请提供一种包括指令的计算机程序产品,当其在计算机上运行时,使得计算机执行第一方面和第一方面各种可能的设计中的一个或多个。
第十一方面,本申请提供一种包括指令的计算机程序产品,当其在计算机上运行时,使得计算机执行第二方面和第二方面各种可能的设计中的一个或多个。
第十二方面,本申请提供一种包括指令的计算机程序产品,当其在计算机上运行时,使得计算机执行第三方面和第三方面各种可能的设计中的一个或多个。
第十三方面,本申请提供一种芯片,该芯片包括处理器和接口电路,接口电路和处理器耦合,处理器用于运行计算机程序或指令,以实现第一方面和第一方面各种可能的实现方式中的一个或多个。
第十四方面,本申请提供一种芯片,该芯片包括处理器和接口电路,接口电路和处理器耦合,处理器用于运行计算机程序或指令,以实现第二方面和第二方面各种可能的实现方式中的一个或多个。
第十五方面,本申请提供一种芯片,芯片包括处理器和接口电路,接口电路和处理器耦合,处理器用于运行计算机程序或指令,以实现第三方面和第三方面各种可能的实现方式中的一个或多个。
可选的,本申请中上述描述的芯片还可以包括至少一个存储器,该至少一个存储器中存储有指令或计算机程序。
第十六方面,本申请实施例提供一种数据处理系统,该数据处理系统包括:第四方面和第四方面各种可能的实现方式中所描述的数据处理装置,和至少两个如第五方面和第五方面各种可能的实现方式中所描述的数据发送装置。
可选的,该数据处理系统还包括:如第六方面所描述的数据发送装置。
附图说明
图1为本申请实施例提供的一种现有技术中的语音MOS变化曲线图;
图2为本申请实施例提供的一种数据处理系统的结构示意图;
图3为本申请实施例提供的一种5G网络示意图;
图4~图10为本申请实施例提供的一种数据处理方法的流程示意图;
图11~图13为本申请实施例提供的一种数据处理装置的结构示意图;
图14~图19为本申请实施例提供的一种数据发送装置的结构示意图;
图20为本申请实施例提供的一种芯片的结构示意图。
具体实施方式
为了便于清楚描述本申请实施例的技术方案,在本申请的实施例中,采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。例如,第一网元和第二网元仅仅是为了区分不同的网元,并不对其先后顺序进行限定。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定,并且“第一”、“第二”等字样也并不限定一定不同。
需要说明的是,本申请中,“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言,使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
本申请中,“至少一个”是指一个或者多个,“多个”是指两个或两个以上。“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B的情况,其中A,B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达,是指的这些项中的任意组合,包括单项(个)或复数项(个)的任意组合。例如,a,b,或c中的至少一项(个),可以表示:a,b,c,a-b,a-c,b-c,或a-b-c,其中a,b,c可以是单个,也可以是多个。
本申请实施例的技术方案可以应用于各种数据处理的通信系统,例如:码分多址 (code division multiple access,CDMA)、时分多址(time division multiple access,TDMA)、频分多址(frequency division multiple access,FDMA)、正交频分多址(orthogonal frequency-division multiple access,OFDMA)、单载波频分多址(single carrier FDMA,SC-FDMA)和其它系统等。术语“系统”可以和“网络”相互替换。CDMA系统可以实现例如通用无线陆地接入(universal terrestrial radio access,UTRA)、CDMA2000等无线技术。UTRA可以包括宽带CDMA(wideband CDMA,WCDMA)技术和其它CDMA变形的技术。CDMA2000可以覆盖过渡标准(interim standard,IS)2000(IS-2000),IS-95和IS-856标准。TDMA系统可以实现例如全球移动通信系统(global system for mobile communication,GSM)等无线技术。OFDMA系统可以实现诸如演进通用无线陆地接入(evolved UTRA,E-UTRA)、超级移动宽带(ultra mobile broadband,UMB)、IEEE 802.11(Wi-Fi),IEEE 802.16(WiMAX),IEEE 802.20,Flash OFDMA等无线技术。UTRA和E-UTRA是UMTS以及UMTS演进版本。3GPP在长期演进(long term evolution,LTE)和基于LTE演进的各种版本是使用E-UTRA的UMTS的新版本。5G通信系统、新空口(new radio,NR)是正在研究当中的下一代通信系统。此外,通信系统还可以适用于面向未来的通信技术,都适用本申请实施例提供的技术方案。
本申请实施例描述的系统架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。本申请实施例中以提供的方法应用于NR系统或5G网络中为例进行说明。
图2示出了本申请实施例提供的数据处理方法所应用的一种数据处理系统的架构示意图,如图2所示,包括:第一网元101和与该第一网元101连接的至少两个网元(图2中仅示出了两个网元,例如以网元102和网元103为例,可以理解的是,在实际过程中还可以存在两个以上的网元)。
可以理解的是,本本申请实施例中的至少两个网元之间也可以相互连接,例如,图2中网元102和网元103之间相互连接。
可以理解的是,本申请实施例中至少两个网元中存在一个网元用于为第一网元提供业务流对应的在该网元上的业务数据,该至少两个网元中存在另一个网元用于为第一网元提供业务流在该另一个网元上的网络数据。
示例性的,本申请所涉及到的业务数据可以为:业务流所属的业务标识、带宽、时延、丢包率、抖动缓存、TCP拥塞窗口、TCP接收窗口、媒体编码类型、媒体编码速率等参数的数据。
可以理解的是,本申请实施例中,某个参数的数据可以是该参数的大小、值或者要求。例如,CQI数据可以指CQI的大小或者值,在本发明实施例中,参数的数据、大小、或者值或者要求,表达的都是该参数在对应网元收集或者获取到的数据值,下述但凡涉及到此类描述,均可以参见此处,后续不再赘述。
本申请所涉及到的网络数据可以为以下任一个参数:带宽、时延、丢包率、参考信号接收功率(reference signal receiving power,RSRP)、参考信号接收质量(reference  signal receiving quality,RSRQ)、误块率(block error rate,BLER)和信道质量指示(channel quality indication,CQI)、切片标识信息、数据网络名称(data network name,DNN)等参数数据。
其中,第一网元101和至少两个网元之间可以直接连接,也可以通过其他网元间接连接,本申请实施例对此不作限定。
基于此,该至少两个网元中用于为第一网元提供网络数据的网元可以为终端、属于核心网或者接入网中的网元。
示例性的,用于为第一网元提供数据网络的网元可以为核心网中的用户面网元和控制面网元中的一个或者多个。
例如,在第四代(4th generation,4G)网络中用户面网元可以为:例如,公用数据网网关(public data network gateway,PDN GW,简称PGW)、服务网元(serving gateway,SGW)。控制面网元可以为移动性管理实体(mobility management entity,MME)。
在本发明实施例中,终端可以分布于整个无线网络中,每个终端可以是静态的或移动的。
其中,若上述数据处理系统应用于5G网络,则如图3所示,第一网元101所对应的网元或者实体可以为网络数据分析功能(network data analytics function,NWDAF)网元。至少两个网元所对应的网元或者实体可以为以下多个网元中任意两个不同的网元:应用功能(也可以称为业务功能网元)(application function,AF)网元、策略控制(policy control function,PCF)网元、会话管理功能(session management function,SMF)网元、用户面功能(user plane function,UPF)网元、接入和移动性管理功能(access and mobility management function,AMF)网元、无线接入网(radio access network,RAN)设备和终端。
其中,RAN设备为属于无线接入网的网元。PCF网元、SMF网元、AMF网元和UPF网元为属于核心网的网元。
为了使得至少两个网元中一个网元102为第一网元提供业务流对应的在该网元102上的业务数据,另一个网元103提供业务流在该网元103上的网络数据。示例性的,例如,网元102可以为AF网元,网元103可以为AMF网元。或者网元102可以为AF网元,网元103可以为UPF网元。
此外,如图3所示,该5G网络还可以包括接入设备(例如,接入网络(access network,AN))、统一数据管理(unified data management,UDM)网元、鉴权服务器功能(authentication server function,AUSF)网元、网络切片选择功能(network slice selection function,NSSF)网元、网络能力开放功能网元(network exposure function,NEF网元)、网络仓库贮存功能(network repository function,NRF)网元等,本申请实施例对此不作具体限定。
如图3所示,运行、管理和维护(运维)(operation,administration,and maintenance,OAM)网元(也可以称为运行管理维护网元)可以覆盖接入网和核心网的所有网元,并且可以从接入网和核心网的这些所有网元上收集数据,且本申请实施例中的OAM网元也可以收集业务流级别的网络数据。
其中,终端通过N1接口(简称N1)与AMF网元通信。AMF实体通过N11接口(简称N11)与SMF网元通信。SMF网元通过N4接口(简称N4)与一个或者多个UPF网元通信。一个或多个UPF网元中任意两个UPF网元通过N9接口(简称N9)通信。UPF网元通过N6接口(简称N6)与AF网元管控的数据网络(data network,DN)通信。终端通过接入设备(例如,RAN设备)接入网络,接入设备与AMF网元之间通过N2接口(简称N2)通信。SMF网元通过N7接口(简称N7)与PCF网元通信,PCF网元通过N5接口与AF网元通信。接入设备通过N3接口(简称N3)与UPF网元通信。任意两个AMF网元之间通过N14接口(简称N14)通信。SMF网元通过N10接口(简称N10)与UDM通信。AMF网元通过N12接口(简称N12)与AUSF通信。AUSF网元通过N13接口(简称N13)与UDM网元通信。AMF网元通过N8接口(简称N8)与UDM网元通信。
需要说明的是,在图3中3rd AF网元和Operator AF都属于AF网元,区别在于,3rd AF网元(比如微信业务服务器、支付宝支付业务服务器)不受运营商管控,Operator AF网元(例如,IP多媒体系统(IP multimedia system)中的代理-呼叫会话控制功能(proxy-call session control function,P-CSCF)网元)受运营商管控,3rd AF网元与NWDAF网元交互时需要通过NEF网元。
其中,PCF网元用于转发AF网元的信令或者数据到SMF网元。
需要说明的是,图3中的各个网元之间的接口名字只是一个示例,具体实现中接口名字可能为其他名字,本申请实施例对此不作具体限定。
需要说明的是,图3的接入设备、AF网元、AMF网元、SMF网元、AUSF网元、UDM网元、UPF网元和PCF网元等仅是一个名字,名字对设备本身不构成限定。在5G网络以及未来其它的网络中,接入设备、AF网元、AMF网元、SMF网元、AUSF网元、UDM网元、UPF网元和PCF网元所对应的网元或实体也可以是其他的名字,本申请实施例对此不作具体限定。例如,该UDM网元还有可能被替换为用户归属服务器(home subscriber server,HSS)或者用户签约数据库(user subscription database,USD)或者数据库实体,等等,在此进行统一说明,以下不再赘述。
需要说明的是,本申请中会话(session)即指SMF网元建立的连通终端和数据网络之间的通信链路,该通信链中包括终端,接入设备,UPF网元以及UPF网元对应的数据网络。会话可以为协议数据单元会话(protocol data unit session,PDU session)PDU,该PDU session用于提供PDU数据包。另外,为建立该会话,需要控制面AMF网元、SMF网元、PCF网元协同。
需要说明的是,本申请中业务流包括QoS flow或者service data flow,QoS flow或者service data flow是PDU session中的一个业务的连通终端和数据网络之间的通信链路,该通信链路中包括终端,接入设备,UPF网元以及UPF网元对应的数据网络。另外,为建立该业务流,需要控制面AMF网元、SMF网元、PCF网元协同。
可选的,本申请中的终端也可以称为终端设备,用户设备(user equipment,UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备可以是无线局域网(wireless local area networks,WLAN)中的站点(station,STA),可以是蜂窝电话、 无绳电话、会话启动协议(session initiation protocol,SIP)电话、无线本地环路(wireless local loop,WLL)站、个人数字处理(personal digital assistant,PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信系统,例如,第五代(fifth-generation,5G)通信网络中的终端设备或者未来演进的公共陆地移动网络(public land mobile network,PLMN)网络中的终端设备等。
作为示例,在本发明实施例中,该终端还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备,是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称,如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上,或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备,更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能,例如:智能手表或智能眼镜等,以及只专注于某一类应用功能,需要和其它设备如智能手机配合使用,如各类进行体征监测的智能手环、智能首饰等。
可选的,本申请实施例中所涉及到的接入设备指的是接入核心网的设备,例如可以是基站,宽带网络业务网关(broadband network gateway,BNG),汇聚交换机,非第三代合作伙伴计划(3rd generation partnership project,3GPP)接入设备等。基站可以包括各种形式的基站,例如:宏基站,微基站(也称为小站),中继站,接入点等。
可选的,本申请实施例中所涉及到的AMF网元还可以负责注册管理,移动性管理,合法监听等功能,本申请实施例对此不作具体限定。
可选的,本申请实施例中所涉及到的SMF网元用于进行会话管理,包括:会话建立,会话修改,会话释放,终端的网络之间互连的协议(internet protocol,IP)地址分配和管理,UPF网元的选择和控制,合法监听等与会话相关的控制功能。
可选的,本申请实施例中所涉及到的UPF网元除了具备图3所示的用户面功能网元的功能,还可实现服务网关(serving gateway,SGW)和分组数据网络网关(packet data network gateway,PGW)的用户面功能。此外,UPF网元还可以是软件定义网络(software defined network,SDN)交换机(switch),本申请实施例对此不作具体限定。
可选的,本申请实施例中所涉及到的AUSF网元用于基于终端的签约数据对终端进行鉴权认证。
可选的,本申请实施例中所涉及到的UDM网元用于储存用户签约数据。此外,UDM网元还包括鉴权认证,处理用户标识,签约管理等功能,本申请实施例对此不作具体限定。
可选的,本申请实施例中所涉及到的PCF网元提供策略规则,支持统一的策略架构管理网络行为等与策略相关的功能。
可选的,图3中的用户面功能网元可以由一个实体设备实现,也可以由多个实体设备共同实现,还可以是一个实体设备内的一个逻辑功能模块,本申请实施例对此不作具体限定。
其中,SMF网元用于根据终端的位置信息或者终端发送的数据的特征或者UPF 网元与终端之间的位置信息,UPF网元的服务质量为终端重新分配UPF网元,以重新建立终端和新分配的UPF网元之间的会话,从而提高重建后的会话能够优化用户面。
接入设备用于为终端提供数据服务,例如,接收终端发送的数据,或者向终端发送数据,在实际使用过程中接入设备可以为基站。其中,在本发明实施例中,基站(base station,BS)可以是与用户设备(user equipment,UE)或其它通信站点如中继站点,进行通信的设备,基站可以提供特定物理区域的通信覆盖。
PCF网元,用于从AF网元接收业务信息、基于业务信息生成以及分发业务流对应的QoS参数。
AF网元,用于触发NWDAF网元收集业务流对应的在不同网元上的第一数据、向NWDAF网元发送业务流对应的在该AF网元上的第一数据。
其中,DN用于提供数据服务的外部网络。
本申请实施例中的业务流指:终端与数据网络之间的业务的数据包传输通道,通过IP五元组标识。
NWDAF网元,用于收集时变性网络或者业务或者终端以及对应的业务体验数据,分析得到某个业务的不同网络状况(对应网络数据)或者业务状况(对应业务数据)或者终端状况(对应终端数据)下的至少一套QoS参数。例如,NWDAF网元可以收集一个业务在基站上的空口流比特率数据(数据值、大小、要求等),分析得到GFBR。或者,NWDAF网元可以收集一个业务在基站与UPF之间时延数据(数据值、大小、要求等),分析得到PDB。或者,NWDAF可以收集AF网元或者终端上TCP拥塞窗口(Congestion Window,CWND)数据(数据值、大小、要求等)或者TCP接收窗口(receiver window,RWND)数据(数据值、大小、要求等),分析得到推荐的CWND或者推荐的RWND。或者,NWDAF可以收集AF网元或者终端上的抖动缓存数据,分析得到推荐的Jitter Buffer。
针对某个业务,之所以是至少一套QoS参数,示例性的,考虑到针对垂直行业的业务体验要求(比如业务MOS分大于3.0),包时延数据与丢包率数据是冲突的,
比如1,在弱覆盖下,RAN可以多传几次数据包以保证丢包率,但是这种情况下,会增大包时延,进一步地,可能会增大流比特率;
比如2,在强覆盖下,RAN不需要传多次数据包,这种情况下包丢包率和包时延都可以保证,进一步地,可能会减小流比特率。
因此,针对一个业务,存在一套或者多套QoS参数。
具体地,NWDAF网元基于时变性网络数据或者业务数据或者终端数据以及对应的业务体验数据通过大数据方法得到业务的至少一套QoS参数。过程如下:
步骤一,NWDAF网元首先从AF网元、RAN设备、UPF网元、UE、AMF网元、SMF网元、PCF网元等网元分别收集数据,然后通过业务标识、业务流标识、终端标识、业务流所在的会话标识、每个网元上都有的关联标识、时间等信息将各个网元的数据关联起来,得到完整的训练数据。训练数据中包括:
1)、业务体验数据,来自AF网元。
2)、其他影响业务体验数据的时变性参数数据,包括,
a、来自AF网元的TCP拥塞窗口数据、TCP接收窗口数据、抖动缓存数据、媒体 编码类型以及编码速率数据、缓存数据、至少一个数据类型的数据。
b、来自RAN网元流比特率数据、丢包率数据、时延数据、无线信道质量数据、至少一个数据类型的数据。
c、来自UPF网元的流比特率数据、丢包率数据、时延数据、至少一个数据类型的数据。
d、来自UE的流比特率数据、丢包率数据、时延数据、至少一个数据类型的数据、TCP拥塞窗口数据、TCP接收窗口数据、抖动缓存数据、媒体编码类型以及编码速率数据、缓存数据、CPU占用率、内存占用率至少一个数据类型的数据。等等。
步骤二,NWDAF网元基于线性回归(Linear Regression)方法得到业务体验与其他影响业务体验数据的时变性参数数据的关系模型,即业务体验模型,NWDAF网元基于这个业务体验模型就可以规划业务的一套或者多套QoS参数。
此外,NWDAF基于得到的训练数据,还可以用于UPF路由路径选择、用户面或控制面故障诊断等。
如表1和表2所示,表1、表2和表3示出了本申请实施例提供的业务数据和网络数据的相关信息。
表1 业务数据
Figure PCTCN2019084816-appb-000001
Figure PCTCN2019084816-appb-000002
其中,本申请实施例中的UE ID可以参考终端的标识,此处不再赘述。
表2 网络数据
Figure PCTCN2019084816-appb-000003
Figure PCTCN2019084816-appb-000004
Figure PCTCN2019084816-appb-000005
Figure PCTCN2019084816-appb-000006
Figure PCTCN2019084816-appb-000007
Figure PCTCN2019084816-appb-000008
Figure PCTCN2019084816-appb-000009
表3 终端数据
Figure PCTCN2019084816-appb-000010
Figure PCTCN2019084816-appb-000011
Figure PCTCN2019084816-appb-000012
如表4所示,表4示出了表1所涉及到的通信模式参数:
表4 通信模式参数
Figure PCTCN2019084816-appb-000013
可以理解的是,本申请实施例中一种数据处理方法的可以由第一网元执行,也可以由应用于第一网元中的装置执行,例如,芯片。下述实施例中将以一种数据处理方法的执行主体为第一网元为例进行说明。本申请实施例中的一种数据发送方法的执行主体可以是网元,也可以是应用于网元中的装置,例如,芯片,下述实施例中将以一种数据发送方法的执行主体为网元为例进行说明。
如图4所示,图4示出了本申请实施例提供的一种数据处理方法,该方法包括:
S101、至少两个网元确定获取到业务流的第一标识。
此处的,至少两个网元可以为PCF网元、AMF网元、SMF网元、UPF网元、RAN设备以及终端中任意一个或者多个网元与AF网元之间的组合。
示例性的,本申请实施例中的业务流可以为服务质量流或者业务数据流。
可选的,本申请实施例中,还可以使用步骤S101a替代步骤S101,步骤S101a、网元确定接收到第一指示信息,该第一指示信息用于指示向第一网元上报业务流对应的第一数据。例如,第一指示可以为Network Data Report indicator。
S102、至少两个网元中每个网元向第一网元发送业务流对应的在各自网元上的第一数据,第一数据中携带第一标识。
示例性的,第一网元可以为上述图3中的NWDAF网元。
需要说明的是,当网元代表至少两个网元时,每个网元上具有的业务流对应的第 一数据可能不同,例如,以至少两个网元为网元1和网元2为例,其中,网元1上具有的业务流对应的第一数据为网络数据,例如,流标识。网元2上具有的业务流对应的第一数据可以为业务数据,例如,终端的标识。则网元1和网元2在确定接收到第一标识时,网元1将流标识发送给第一网元,网元2将终端的标识发送给第一网元。
示例性的,以第一网元为NWDAF为例,由于网元不同,该网元向第一网元发送第一数据的方式存在差异,因此,下述将分别介绍:
示例1、至少两个网元存在一个网元为AMF网元、SMF网元和PCF网元中至少一个时,该一个网元可以直接通过与第一网元之间的服务化接口向第一网元发送业务流对应的第一数据。其中,服务化接口可以实现AMF网元、SMF网元、PCF网元、NWDAF网元、NEF网元任意两个网元之间两两直接通信或交互。例如,网元为AMF网元则该网元通过与第一网元之间的服务化接口向第一网元发送业务流对应的第一数据。
示例2、至少两个网元中存在一个网元为RAN设备,该RAN设备可以先将该RAN设备上具有的业务流对应的第一数据发送给RAN设备所接入的控制面网元,例如AMF。然后,RAN设备所接入的控制面网元再通过RAN设备所接入的控制面网元和第一网元之间的服务化接口(例如,AMF网元和NWDAF网元之间的服务化接口)上报给第一网元。或者,RAN设备也可以通过建立与第一网元之间的用户面隧道将RAN设备上具有的业务流对应的第一数据发送第一网元。
示例3、至少两个网元存在一个网元为UPF网元时,该UPF网元可以先将UPF网元上具有的业务流对应的第一数据发送给UPF网元所接入的控制面网元,例如,SMF网元。然后,UPF网元所接入的控制面网元通过UPF网元所接入的控制面网元和第一网元之间的服务化接口(例如,SMF网元和NWDAF网元之间的服务化接口)上报给第一网元。或者,UPF网元也可以通过与第一网元之间的用户面隧道将UPF网元上具有的业务流对应的第一数据发送第一网元。
示例4、至少两个网元中存在一个网元为AF网元时,方式1、AF网元可以通过文件传输协议(file transfer protocol,FTP)方式,将该AF网元上具有的业务流对应的第一数据发送给第一网元。或者,方式2、AF网元可以通过与第一网元之间建立的用户面隧道,AF网元上具有的业务流对应的第一数据发送给第一网元。方式3、AF网元可以通过Naf_ServiceDataCollectionSubscription_Notify服务,不断上报AF网元上具有的业务流对应的第一数据给第一网元。方式4、AF网元可以通过NEF向第一网元发送AF网元上具有的业务流对应的第一数据给第一网元。
可选的,业务流对应的在每个网元上的第一数据所包括的第一标识为以下信息中的一项或者多项:业务流所属的业务标识、业务流的标识、终端的标识、业务流所在会话的标识、业务流所在会话的数据网络名称(data network name,DNN)、业务流所在切片的标识信息。
本申请实施例中:一方面,至少两个网元向第一网元发送的第一数据中所携带的第一标识可以相同。例如,网元1发送的数据1中携带的第一标识为业务流所在会话的标识。网元2发送的数据2中携带的第一标识也可以为业务流所在会话的标识。
另一方面,至少两个网元向第一网元发送的第一数据中所携带的第一标识可以不 相同。例如,网元1发送的数据1中携带的第一标识为终端的标识。网元2发送的数据2中携带的第一标识也可以为业务流所在会话的标识。
在不同网元向第一网元发送的第一数据中所携带的第一标识不相同的情况下,该不同网元发送的第一数据中所携带的第一标识之间具有映射关系。例如,业务流所在会话的标识和业务流的标识之间具有映射关系。且第一网元中存储有不同网元发送的第一标识之间具有的映射关系,这样第一网元在接收到来自不同网元发送的业务流对应的第一数据时,便可以确定不同网元发送的第一数据为同一个业务流对应的数据。
S103、第一网元获取业务流对应的在至少两个网元中每个网元上的第一数据,其中,业务流对应的在每个网元上的第一数据包括第一标识。
需要说明的是,当至少两个网元中一个网元为上述各种示例中的网元时,第一网元通过对应的方式从该网元上接收业务流对应的第一数据,例如,网元为AMF网元时,第一网元通过AMF网元和第一网元之间的服务化接口接收AMF网元发送的业务流对应的第一数据,本申请实施例在此不再赘述。
S104、第一网元根据第一标识,以及业务流对应的在每个网元上的第一数据,得到业务流对应的第二数据。
其中,第二数据中至少包括业务流对应的在每个网元上的第一数据,或者,第二数据至少包括业务流对应的在每个网元上的第一数据的至少一部分。
具体的,当至少两个网元发送的第一数据中所携带的第一标识相同时,第一网元可以直接根据第一标识将不同网元上业务流对应的第一数据或第一数据中的至少一部分划分至同一个集合中,以得到第二数据。当至少两个网元发送的第一数据中所携带的第一标识不同时,第一网元可以根据预先存储的映射关系,将具有映射关系的不同网元上业务流对应的第一数据或第一数据的至少一部分划分至同一个集合中,以得到第二数据。
示例性的,第一网元从网元1上获取的业务流对应的第一数据为流标识,从网元2上获取到的业务流对应的第一数据为终端的标识。其中,网元1上的第一数据中携带标识1,网元2上的第一数据携带标识2,标识1和标识2之间具有映射关系,则第一网元可以将业务流对应的流标识和终端的标识进行关联,从而得到业务流对应的第二数据。即最终得到的第二数据包括业务流对应的流标识和终端的标识,如表5所示:
表5 业务流对应的数据
Figure PCTCN2019084816-appb-000014
可选的,如果第一数据中不携带第一标识,可通过RAN设备上的PDU session ID/QFI、AMF网元上的PDU session ID/UE ID/时间戳(timestamp)、SMF网元上的PDU session ID/QFI/UE ID/timestamp、UPF网元上的PDU session ID/QFI/timestamp、PCF网元上的UE ID/application ID/timestamp、AF网元上的UE ID/application ID/timestamp,将不同网元发送的第一数据划分至同一个集合中。
需要说明的是,第一网元获取的业务流对应的在各个网元上的第一数据,还可以 由运行管理维护网元发送给第一网元。具体的,各个网元在确定需要上报业务流对应的在各自网元上的第一数据时,将业务流在各自网元上对应的第一数据发送给运行管理维护网元,以由运行管理维护网元发送给第一网元。
表5以第一网元将网元1上的第一数据和网元2上的第二数据全部关联得到第二数据为例,可以理解的是,在实际过程中,若网元1上的第一数据,还包括:时间戳时,则第一网元可以选择只将业务流对应的在网元1上的第一数据中的至少一部分和业务流对应的在网元2上的全部数据或者至少一部分数据划分至一个集合中,以得到第二数据。或者本申请实施例中还可能存在如下情况,第一网元从至少两个网元上获取业务流在不同网元上对应的不同的第一数据,但是第一网元可以根据自身的需求,从至少两个网元中选择部分网元上的第一数据中的全部或者部分划分至同一个集合中得到第二数据,本申请实施例对此不作限定。
本申请实施例提供一种数据处理方法,通过第一网元获取业务流在不同网元上的第一数据,并根据不同网元发送的第一数据中的第一标识,将业务流在不同网元上的第一数据进行关联以得到第二数据,这样便于第一网元后续规划业务流所属的业务的一套或者多套QoS参数、业务流所属的会话对应的用户面路径、切片资源优化、控制面或者用户面异常检测等等。
在实际过程中,若第二网元发现某些业务在某些终端类型、某些网络区域、某些时间段内存在问题,为了使得第一网元分析存在问题的原因,则第二网元便可以向第一网元提出分析上述原因的需求,以由第一网元收集业务流对应的来自不同网元的第一数据。因此,作为的另一个实施例,如图5所示,本申请实施例提供的方法还包括:
S105、第二网元向第一网元发送第一消息,该第一消息用于指示第一网元从至少两个网元获取业务流对应的第一数据,其中,第一消息包括以下信息中的一项或者多项:业务流所属的业务标识、业务流对应的终端的终端类型、业务流对应的终端所在的网络区域和业务流对应的时间窗。
可选的,该第一消息中还可以携带至少两个网元的标识,和第二网元的标识。
可选的,该第一消息中还可以包括以下信息中的一项或者多项:除业务流所属的业务标识之外的其他一个或多个业务标识、除业务流对应的终端的终端类型之外的其他一个或多个终端类型、除业务流对应的终端所在的网络区域之外的其他一个或多个网络区域、业务流对应的时间窗其他一个或多个时间窗。
其中,业务流所属的业务标识用于确定业务流所属的业务。业务流对应的终端的终端类型用于确定业务流对应的终端类型。业务流对应的时间窗用于确定业务流对应的时间段列表,例如,从2018年3月1日到2018年3月8日。业务流对应的终端所在的网络区域(例如,追踪区域(tacking area,TA)或TA列表或路由区域(routing area,RA)或者RA列表)。
示例性的,第二网元可以为AF网元,第一网元可以为NWDAF网元。例如,AF可以将第一消息通过PCF网元发送给NWDAF网元。
其中,第一消息可以为第一网元和第二网元之间新定义的消息,也可以为第一网元和第二网元之间现有的消息,本申请实施例对此不作限定。示例性的,该第一消息可以为Naf_DataCollectionCondition_Notify消息。
S106、第一网元接收第二网元发送的第一消息。
可以理解的是,第一网元在接收到第一消息之后,便可以确定需要从不同网元上收集业务流对应的第一数据。
可选的,本申请实施例在步骤S106之后还可以包括:S107、第一网元向第二网元发送第一响应,该第一响应用于表示第一网元已收到第一消息。
可以理解的是,上述步骤S105~S107可以单独实施,也可以与上述步骤S101~S104结合起来实施,当与S101~S104结合起来实施时,该S105~S107可以位于步骤S101之前实施。
作为本申请的另一个实施例,如图6所示,本申请实施例提供的方法,还包括:
S108、第一网元向至少两个网元中每个网元发送第一请求,第一请求用于请求业务流对应的在每个网元上的第一数据,第一请求包括以下信息中的一项或者多项:业务流所属的业务标识、业务流对应的终端的终端类型、业务流对应的终端所在的网络区域和业务流对应的时间窗。
可选的,该第一请求中还可以包括以下信息中的一项或者多项:除业务流所属的业务标识之外的其他一个或多个业务标识、除业务流对应的终端的终端类型之外的其他一个或多个终端类型、除业务流对应的终端所在的网络区域之外的其他一个或多个网络区域、业务流对应的时间窗其他一个或多个时间窗。
由于网元不同,第一网元向网元发送的第一请求的消息也不同,因此,下述实施例将分别介绍:
Case1、网元为PCF网元时,第一网元向网元发送的第一请求可以为Npcf_NetworkDataCollectionSubscription request消息。
Case2、网元为AF网元时,第一网元向网元发送的第一请求可以为Naf_ServiceDataCollectionSubsctiption request消息。
需要说明的是,当网元为PCF网元或者AF网元时,第一网元发送第一请求的网元可以和接收第一消息的网元是同一个网元,也可以是不同的网元。例如,AF1网元向第一网元发送第一消息,但是第一网元却从AF2网元上请求业务流对应的第一数据。
S109、至少两个网元接收第一网元发送的第一请求。
可选的,本申请实施例中在步骤S109之后,还可以包括:S110、至少两个网元中每个网元向第一网元发送针对第一请求的第二响应,该第二响应用于表示该网元接收到第一请求。示例性的,网元为AF网元时,第二响应为:Naf_ServiceDataCollectionSubsctiption Response消息。网元为PCF网元时,第二响应为:Npcf_NetworkDataCollectionSubscription Response消息。
可选的,本申请实施例中在S109之后,还可以包括:S111、至少两个网元向第一网元发送第二消息,该第二消息中携带业务流对应的在各自网元上的第一数据。S112、第一网元接收至少两个网元发送的第二消息。基于步骤S111和S112,本申请中的步骤S103通过以下方式实现:第一网元从每个网元各自发送的第二消息中,获取业务流在每个网元上各自对应的第一数据。
可选的,本申请实施例中各个网元向第一网元发送的第一数据还包括以下信息中的一项或者多项:业务流对应的第一数据所在的网元的标识、终端的标识、至少两个 网元中至少一个网元的至少一个数据类型的数据值。
示例性的,第一数据由AF网元发送给第一网元,则由AF网元发送给第一网元的第一数据中还携带AF网元的标识。
其中,至少两个网元中至少一个网元的至少一个数据类型的数据值指,该网元发送给第一网元的第一数据中可以携带该网元的数据类型的数据值。或者该网元发送给第一网元的第一数据中不仅可以携带该网元的数据类型的数据值,还可以携带至少两个网元中除该网元之外的其余一个或者多个网元的数据类型的数据值。例如,由AF网元发送给第一网元的第一数据中可以携带AF网元的数据类型的数据值,以及PCF网元的数据类型的数据值。
可选的,如图7所示,本申请实施例中至少两个网元中任一个网元在向第一网元发送业务流对应的在该网元上的第一数据之前,还可以包括如下步骤以对第一数据进行归一化处理以得到每个网元各自的数据类型的数据值:
S113、至少两个网元中每个网元根据各自网元的第一数据类型的第一数据值确定第二数据值,其中,第一数据值属于第一数值空间,第二数据值属于第二数值空间,第一数据类型为第一数据中的任何一项。
进一步的,为了对业务流在该网元上的第一数据进行归一化处理,在步骤S113之后,还可以包括:
S114、每个网元根据各自网元的第二数据类型的第三数据值确定第四数据值,其中,第三数据值属于第三数值空间,第四数据值属于第四数值空间,第二数据类型为第一数据中的任何一项。
可选的,第二数值空间与第四数值空间相同。便于第一网元处理,所有的数据类型的归一化空间一样的,不用NWDAF进一步归一化到同一个数值空间。
可选的,对第一数据进行归一化处理以得到每个网元各自的数据类型的数据值还可以包括:至少两个网元中每个网元根据各自网元的第三数据类型的第五数据值确定第六数据值,其中,第五数据值属于第五数值空间,第六数据值属于第六数值空间。
可选的,第二数值空间与第六数值空间相同。
其中,至少两个网元中每个网元可以通过归一化处理根据各自网元的第一数据类型的第一数据值确定第二数据值或者根据各自网元的第二数据类型的第三数据值确定第四数据值或者根据各自网元的第三数据类型的第五数据值确定第六数据值,所述归一化处理包括将所述数据类型的物理数据值映射到固定的数值空间。其中所述归一化处理主要是采用最大最小值归一化方法、Z-Score归一化方法等将每个数据类型的物理数据值映射到固定的数值空间,这种处理一方面便于在大数据分析过程中提高模型训练收敛速度,另一方面提供了一种特征数据传输方式。
由于至少两个网元可以为AMF网元、终端、SMF网元、PCF网元以及AF网元中任意两个不同的网元,当业务流对应的第一数据来源于AMF网元、终端、SMF网元、PCF网元以及AF网元中任一个网元时,第一数据存在差异,因此下述将以至少两个网元中包括第三网元为例,分别介绍第三网元为AMF网元、终端、SMF网元、PCF网元以及AF网元时,从第三网元获取到的第一数据还可以具有的一些信息:
当第三网元为应用功能AF网元时,从第三网元获取到的第一数据还包括以下信 息中的一项或者多项:业务流所属的业务标识、业务流所属的业务的通信模式参数、第一接口流比特率数据、第一接口时延数据、第一接口丢包率数据、第一接口包数据、时间戳、业务流所属的业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据和和媒体编码类型数据和的编码速率数据。其中,第一接口为用户面功能网元和AF网元对应的数据网络DN之间的接口。示例性的,如图3所示,第一接口可以为N6接口。
当第三网元为策略控制功能PCF网元时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流所属的业务标识、业务流所在会话的标识、业务流所在会话的数据网络名称DNN、业务流所在切片的标识信息、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、媒体编码类型要求的编码速率要求和业务标识的有效时间窗。
当第三网元为SMF网元时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息和业务流的标识的有效时间窗。
当第三网元为第一UPF网元时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流的标识、时间戳、第二接口流比特率数据、第一接口流比特率数据、第三接口比特率数据、第二接口时延数据、第一接口时延数据、第三接口时延数据、第一接口丢包率数据、第二接口丢包率数据、第三接口丢包率数据、第一接口包数据、第二接口包数据和第三接口包数据。其中,第二接口为第一UPF网元和RAN设备之间的接口。其中,第三接口为第一UPF网元与第二UPF网元之间的接口。示例性的,第二接口可以为如图3所示的N3接口。第三接口为N9接口。
当第三网元为AMF网元时,从第三网元获取到的第一数据还包括以下信息中的至少一项:业务流对应的终端的位置信息、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息和业务流所在会话的标识的有效时间窗。
当第三网元为RAN设备时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流对应的终端的位置信息、业务流的标识、业务流所在会话的标识、业务流所在切片的标识信息、时间戳、第四接口流比特率数据、第二接口流比特率数据、第二接口时延数据、第四接口时延数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比(signal to interference plus noise ratio,SINR)数据、CQI数据、BLER数据、拥塞等级、第二接口丢包率数据、第四接口丢包率数据、第二接口包数据和第四接口包数据。其中,第四接口为RAN设备与终端之间的接口。例如,图3所示的Uu接口。
当第三网元为终端时,从第三网元获取到的第一数据还包括以下信息中的一项或者多项:业务流对应的终端的位置信息、业务流的标识、业务流所在会话的标识、业务流所在会话的DNN、业务流所在切片的标识信息、第四接口流比特率数据、第四接口时延数据、第四接口丢包率数据、第四接口包数据、时间戳、业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据、媒体编码数据的编码速率数据、RSRP数据、RSRQ数据、SINR数据、CQI数据和BLER数据。
可选的,作为本申请的又一个实施例,如图8所示,本申请实施例提供的方法还包括:
S115、第五网元向至少两个网元发送第二请求,该第二请求用于请求建立业务流,第二请求中包括以下信息中的一项或者多项:业务流所属的业务标识、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、媒体编码类型要求的编码速率要求。
示例性的,第五网元可以为AF网元。
可选的,如果该至少两个网元中一个网元为PCF网元,且AF网元为3rd AF网元,则第二请求可以通过NEF网元完成3rd AF网元与PCF网元之间的交互。
示例性的,该第二请求可以为Npcf_PolicyAuthorization_Create Request消息。
S116、至少两个网元接收第五网元发送的第二请求。
可选的,如图9所示,本申请实施例提供的方法还包括:
S117、第四网元向第一网元发送第三请求,该第三请求用于请求为业务流分配第一标识。
示例性的,第四网元可以为PCF网元或者SMF网元。
示例性的,该第三请求可以为Nnwaf_CorrelationIDAssignment Request消息。
示例性的,第三请求中可以携带业务流所属的业务标识、业务流所在会话的标识以及业务流对应的终端的标识。
可选的,一次请求,可以请求一个PDU session ID里面多个SDF对应的correlation ID list。
S118、第一网元接收第四网元发送的第三请求。
S119、第一网元向第三网元发送第三响应,第三响应包括第一标识。
示例性的,第三响应可以为Nnwdaf_CorrelacationIDAssignment Response消息。
可选的,作为本申请的另一个实施例,如图10所示,在步骤S104之后,还可以包括:
S120、第一网元根据第二数据确定业务的至少一条服务质量QoS描述信息,其中,至少一条QoS描述信息中的每条QoS描述信息包括QoS参数类型和/或QoS参数要求。
可选的,至少一条QoS描述信息中的每条QoS描述信息还包括网元信息,网元信息用于指示QoS参数要求对应的网元。
可选的,本申请实施例中的步骤S101可以通过以下方式实现:
情况1、网元为PCF网元时,该网元向服务器网元发送第三请求,第三请求用于请求第一标识,第三请求中包括业务标识以及终端的标识。该网元从服务器网元接收第三响应,第三响应中包括第一标识。示例性的,服务器网元可以为:数据分析网元或者网络功能贮存功能网元或者域名服务器。
情况2、网元为AF网元时,在AF网元向PCF网元发送第二请求后,AF网元可以通过PCF网元发送的针对该第二请求的第二响应中获取第一标识。
情况3、网元为SMF网元,则SMF网元可以从PCF网元处获取第一标识。例如,PCF网元可以通过Npcf_SMPolicyControl_UpdateNotify request消息将业务流对应的第一标识发送给SMF网元。
情况4、网元为UPF网元,在SMF网元接收到第一标识以后,SMF网元可以将第一标识发送给UPF网元。例如,SMF网元可以通过N4Session Modification Request/Response,即N4会话修改流程,将业务流对应的第一标识发送给UPF网元。也即UPF网元可以通过N4会话修改流程从SMF网元处获取第一标识。
情况5、网元为AMF网元时,具体的,在SMF网元获取到第一标识以后,SMF网元可以将第一标识发送给AMF网元,也即AMF网元可以从SMF网元处获取第一标识。可以理解的是,情况5还包括:PCF网元将第一标识通过SMF网元发送给AMF网元的过程。
例如,SMF网元可以通过Namf_Communication_N1N2MessageTransfer消息将第一标识发送给AMF网元。
情况6、网元为RAN设备时,RAN设备接收AMF网元或者SMF网元发送的第一标识。也即在AMF网元或者SMF网元具有第一标识以后,该AMF网元或者SMF网元可以将第一标识发送给RAN设备。例如,AMF网元可以通过N2Session Request将第一标识发送给RAN设备。可以理解的是,该情况6同样包括:PCF网元通过AMF网元或者SMF网元将第一标识发送给RAN设备的情况。
情况7、网元为终端时,终端接收RAN设备、AMF网元或者SMF网元发送的第一标识,也即RAN设备、AMF网元或者SMF网元具有第一标识之后,可以将第一标识发送给终端,或者PCF网元可以通过AMF网元或者SMF网元、RAN设备将第一标识发送给终端。
上述主要从各个网元之间交互的角度对本申请实施例的方案进行了介绍。可以理解的是,各个网元,例如数据处理装置和数据发送装置等为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例数据处理装置和数据发送装置进行功能单元的划分,例如,可以对应各个功能划分各个功能单元,也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件功能单元的形式实现。需要说明的是,本申请实施例中对单元的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
在采用集成的单元的情况下,图11示出了上述实施例中所涉及的数据处理装置的一种可能的结构示意图,该数据处理装置可以为第一网元,或者为应用于第一网元中的芯片。该数据处理装置包括:获取单元201以及处理单元202。其中,获取单元201用于支持数据处理装置执行上述实施例中的步骤S103。处理单元202用于支持数据处理装置执行上述实施例中的步骤S104。可选的,该数据处理装置还包括:接收单元203、发送单元204和确定单元205,其中,接收单元203用于支持数据处理装置执行上述实施例中的步骤S106、S118。发送单元204用于支持数据处理装置执行上述实施例中 的步骤S107、S108、S119和S112。其中,确定单元205用于指示数据处理装置执行上述实施例中的步骤S110。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
在采用集成的单元的情况下,图12示出了上述实施例中所涉及的数据处理装置的一种可能的逻辑结构示意图,该数据处理装置可以为上述实施例中的第一网元,或者为应用于第一网元中的芯片。数据处理装置包括:处理模块212和通信模块213。处理模块212用于对数据处理装置的动作进行控制管理,例如,处理模块212用于执行在数据处理装置侧进行消息或数据处理的步骤,例如,支持数据处理装置执行上述实施例中的S104和S110。通信模块213用于支持数据处理装置执行上述实施例中的S103、S107、S108、S119和S112。和/或用于本文所描述的技术的其他由数据处理装置执行的过程。
可选的,数据处理装置还可以包括存储模块211,用于存储数据处理装置的程序代码和数据。
其中,处理模块212可以是处理器或控制器,例如可以是中央处理器单元,通用处理器,数字信号处理器,专用集成电路,现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。处理器也可以是实现计算功能的组合,例如包括一个或多个微处理器组合,数字信号处理器和微处理器的组合等等。通信模块213可以是收发器、收发电路或通信接口等。存储模块211可以是存储器。
当处理模块212为处理器220,通信模块213为通信接口230或收发器时,存储模块211为存储器240时,本申请所涉及的数据处理装置可以为图13所示的设备。
其中,通信接口230、一个或两个以上(包括两个)处理器220以及存储器240通过总线210相互连接。总线210可以是PCI总线或EISA总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示,图13中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。其中,存储器240用于存储数据处理装置的程序代码和数据。通信接口230用于支持数据处理装置与其他设备(例如,网元、第二网元)通信,处理器220用于支持数据处理装置执行存储器240中存储的程序代码和数据以实现本申请提供的S103、S104、S107、S108、S119、S110和S112。
在采用集成的单元的情况下,图14示出了上述实施例中所涉及的数据发送装置的一种可能的结构示意图,该数据发送装置可以为网元,或者为网元中的芯片。该数据发送装置包括:确定单元301和发送单元302。其中,确定单元301用于支持数据发送装置执行上述实施例中的步骤S101、S113和S114。发送单元302用于支持数据发送装置执行上述实施例中的步骤S102、S111。可选的,该数据发送装置还可以包括:接收单元303,用于支持数据发送装置执行上述实施例中的步骤S109和S116。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
在采用集成的单元的情况下,图15示出了上述实施例中所涉及的数据发送装置的一种可能的逻辑结构示意图,该数据发送装置可以为上述实施例中的网元,或者为应用于网元中的芯片。数据发送装置包括:处理模块312和通信模块313。处理模块312 用于对数据发送装置的动作进行控制管理,例如,处理模块312用于执行在数据发送装置侧进行消息或数据处理的步骤,例如,S101、S113和S114。通信模块313用于支持数据发送装置执行上述实施例中的S102、S111、S109和S116。和/或用于本文所描述的技术的其他由数据发送装置执行的过程。
可选的,数据发送装置还可以包括存储模块311,用于存储数据发送装置的程序代码和数据。
其中,处理模块312可以是处理器或控制器,例如可以是中央处理器单元,通用处理器,数字信号处理器,专用集成电路,现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。处理器也可以是实现计算功能的组合,例如包括一个或多个微处理器组合,数字信号处理器和微处理器的组合等等。通信模块313可以是收发器、收发电路或通信接口等。存储模块311可以是存储器。
当处理模块312为处理器320,通信模块313为通信接口330或收发器时,存储模块311为存储器340时,本申请所涉及的数据发送装置可以为图16所示的设备。
其中,通信接口330、一个或两个以上(包括两个)处理器320以及存储器340通过总线310相互连接。总线310可以是PCI总线或EISA总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示,图16中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。其中,存储器340用于存储数据发送装置的程序代码和数据。通信接口330用于支持数据发送装置与其他设备(例如,第一网元)通信,处理器320用于支持数据发送装置执行存储器340中存储的程序代码和数据以实现本申请提供的S101、S113、S114、S102、S111、S109和S116。
在采用集成的单元的情况下,图17示出了上述实施例中所涉及的数据发送装置的另一种可能的结构示意图,该数据发送装置可以为第二网元,或者为应用于第二网元中的芯片。该数据发送装置包括:发送单元401。其中,发送单元401用于支持数据发送装置执行上述实施例中的S105。上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
在采用集成的单元的情况下,图18示出了上述实施例中所涉及的数据发送装置的一种可能的逻辑结构示意图。该数据发送装置可以为上述实施例中的第二网元,或者为应用于第二网元中的芯片。数据发送装置包括:处理模块412和通信模块413。处理模块412用于对数据发送装置的动作进行控制管理。例如,处理模块412用于执行在数据发送装置侧进行消息或数据处理的步骤。例如,支持数据发送装置执行上述实施例中的S105。通信模块413用于支持数据发送装置执行上述实施例中的S105。和/或用于本文所描述的技术的其他由数据发送装置执行的过程。
可选的,数据发送装置还可以包括存储模块411,用于存储数据发送装置的程序代码和数据。
其中,处理模块412可以是处理器或控制器,例如可以是中央处理器单元,通用处理器,数字信号处理器,专用集成电路,现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框,模块和电路。处理器也可以是实现计算功能的 组合,例如包括一个或多个微处理器组合,数字信号处理器和微处理器的组合等等。通信模块413可以是收发器、收发电路或通信接口等。存储模块411可以是存储器。
当处理模块412为处理器420,通信模块413为通信接口430或收发器时,存储模块411为存储器440时,本申请所涉及的数据发送装置可以为图19所示的设备。
其中,通信接口430、一个或两个以上(包括两个)处理器420以及存储器440通过总线410相互连接。总线410可以是PCI总线或EISA总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示,图19中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。其中,存储器440用于存储数据发送装置的程序代码和数据。通信接口430用于支持数据发送装置与其他设备通信,处理器420用于支持数据发送装置执行存储器440中存储的程序代码和数据以实现本申请提供的S105。
图20是本发明实施例提供的芯片150的结构示意图。芯片150包括一个或两个以上(包括两个)处理器1510和接口电路1530。
可选的,该芯片150还包括存储器1540,存储器1540可以包括只读存储器和随机存取存储器,并向处理器1510提供操作指令和数据。存储器1540的一部分还可以包括非易失性随机存取存储器(non-volatile random access memory,NVRAM)。
在一些实施方式中,存储器1540存储了如下的元素,可执行模块或者数据结构,或者他们的子集,或者他们的扩展集:
在本发明实施例中,通过调用存储器1540存储的操作指令(该操作指令可存储在操作系统中),执行相应的操作。
一种可能的实现方式为:第一网元、网元和第二网元,所用的芯片的结构类似,不同的装置可以使用不同的芯片以实现各自的功能。
处理器1510控制第一网元、网元和第二网元的操作,处理器1510还可以称为中央处理单元(central processing unit,CPU)。存储器1540可以包括只读存储器和随机存取存储器,并向处理器1510提供指令和数据。存储器1540的一部分还可以包括非易失性随机存取存储器(non-volatile random access memory,NVRAM)。例如应用中存储器1540、接口电路1530以及存储器1540通过总线系统1520耦合在一起,其中总线系统1520除包括数据总线之外,还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见,在图20中将各种总线都标为总线系统1520。
上述本发明实施例揭示的方法可以应用于处理器1510中,或者由处理器1510实现。处理器1510可能是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法的各步骤可以通过处理器1510中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器1510可以是通用处理器、数字信号处理器(digital signal processing,DSP)、专用集成电路(application specific integrated circuit,ASIC)、现成可编程门阵列(field-programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等 本领域成熟的存储介质中。该存储介质位于存储器1540,处理器1510读取存储器1540中的信息,结合其硬件完成上述方法的步骤。
可选地,接口电路1530用于执行图4、图5、图6、图7、图8、图9和图10所示的实施例中的第一网元、网元和第二网元的接收和发送的步骤。
处理器1510用于执行图4、图5、图6、图7、图8、图9和图10所示的实施例中的第一网元、网元和第二网元处理的步骤。
在上述实施例中,存储器存储的供处理器执行的指令可以以计算机程序产品的形式实现。计算机程序产品可以是事先写入在存储器中,也可以是以软件形式下载并安装在存储器中。
计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时,全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一计算机可读存储介质传输,例如,计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质,(例如,软盘、硬盘、磁带)、光介质(例如,DVD)、或者半导体介质(例如固态硬盘solid state disk,SSD)等。
一方面,提供一种计算机存储介质,计算机可读存储介质中存储有指令,当指令被运行时,使得第一网元或者应用于第一网元中的芯片执行实施例中的S103、S104、S107、S108、S119和S110、S112。和/或用于本文所描述的技术的其他由第一网元或者应用于第一网元中的芯片执行的过程。
又一方面,提供一种计算机存储介质,计算机可读存储介质中存储有指令,当指令被运行时,使得网元或者应用于网元中的芯片执行实施例中的S101、S113和S114、S102、S111、S109和S116。和/或用于本文所描述的技术的其他由网元或者应用于网元中的芯片执行的过程。
另一方面,提供一种计算机存储介质,计算机可读存储介质中存储有指令,当指令被运行时,使得第二网元或者应用于第二网元中的芯片执行实施例中的S105。和/或用于本文所描述的技术的其他由第二网元或者应用于第二网元中的芯片执行的过程。
前述的可读存储介质可以包括:U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
一方面,提供一种包括指令的计算机程序产品,计算机程序产品中存储有指令,当指令被运行时,使得第一网元或者应用于第一网元中的芯片执行实施例中的S103、S104、S107、S108、S119和S110、S112。和/或用于本文所描述的技术的其他由第一网元或者应用于第一网元中的芯片执行的过程。
又一方面,提供一种包括指令的计算机程序产品,计算机程序产品中存储有指令,当指令被运行时,使得网元或者应用于网元中的芯片执行实施例中的S101、S113和S114、S102、S111、S109和S116。和/或用于本文所描述的技术的其他由网元或者应 用于网元中的芯片执行的过程。
再一方面,本申请实施例提供一种包括指令的计算机程序产品,计算机程序产品中存储有指令,当指令被运行时,使得第二网元或者应用于第二网元中的芯片执行实施例中的S105。和/或用于本文所描述的技术的其他由第二网元或者应用于第二网元中的芯片执行的过程。
一方面,提供一种芯片,该芯片应用于第一网元中,芯片包括一个或两个以上(包括两个)处理器和接口电路,接口电路和该一个或两个以上(包括两个)处理器通过线路互联,处理器用于运行指令,以执行实施例中的S103、S104、S107、S108、S119和S110、S112。和/或用于本文所描述的技术的其他由第一网元执行的过程。
又一方面,提供一种芯片,该芯片应用于网元中,芯片包括一个或两个以上(包括两个)处理器和接口电路,接口电路和该一个或两个以上(包括两个)处理器通过线路互联,处理器用于运行指令,以执行实施例中实施例中的S101、S113和S114、S102、S111、S109和S116。和/或用于本文所描述的技术的其他由网元执行的过程。
另一方面,提供一种芯片,该芯片应用于第二网元中,芯片包括一个或两个以上(包括两个)处理器和接口电路,接口电路和该一个或两个以上(包括两个)处理器通过线路互联,处理器用于运行指令,以执行实施例中的S105。和/或用于本文所描述的技术的其他由第二网元执行的过程。
此外,本申请还提供一种数据处理系统,该数据处理系统包括如图11~图13所示的数据处理装置,图14~图16所示的数据发送装置。
可选的,该数据处理系统还包括:图17~图19所示的数据发送装置。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时,可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时,全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line,简称DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可以用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如,软盘、硬盘、磁带),光介质(例如,DVD)、或者半导体介质(例如固态硬盘(solid state disk,简称SSD))等。
尽管在此结合各实施例对本申请进行了描述,然而,在实施所要求保护的本申请过程中,本领域技术人员通过查看附图、公开内容、以及所附权利要求书,可理解并实现公开实施例的其他变化。在权利要求中,“包括”(comprising)一词不排除其他组成部分或步骤,“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施,但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述,显而易见的,在不脱离本申请的精神和范围的情况下,可对其进行各种修改和组合。相应地,本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明,且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包括这些改动和变型在内。

Claims (45)

  1. 一种数据处理方法,其特征在于,包括:
    第一网元获取业务流对应的在至少两个网元中每个网元上的第一数据,其中,所述业务流对应的在每个网元上的第一数据包括第一标识;
    所述第一网元根据所述第一标识,以及所述业务流对应的在每个网元上的第一数据,得到所述业务流对应的第二数据,所述第二数据中至少包括所述业务流对应的在每个网元上的第一数据。
  2. 根据权利要求1所述的方法,其特征在于,所述方法还包括:
    所述第一网元接收第二网元发送的第一消息,所述第一消息用于指示所述第一网元从所述至少两个网元获取所述业务流对应的第一数据,其中,所述第一消息包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流对应的终端的终端类型、所述业务流对应的终端所在的网络区域和所述业务流对应的时间窗。
  3. 根据权利要求1或2所述的方法,其特征在于,所述方法还包括:
    所述第一网元向所述至少两个网元中每个网元发送第一请求,所述第一请求用于请求所述业务流对应的在所述每个网元上的第一数据,所述第一请求包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流对应的终端的终端类型、所述业务流对应的终端所在的网络区域和所述业务流对应的时间窗。
  4. 根据权利要求1-3任一项所述的方法,其特征在于,所述第一网元获取业务流对应的在至少两个网元中每个网元上的第一数据,包括:
    所述第一网元接收所述每个网元发送的第二消息,所述第二消息包括所述业务流对应的在各自网元上的第一数据。
  5. 根据权利要求1-4任一项所述的方法,其特征在于,所述第一数据还包括以下信息中的一项或者多项:所述业务流对应的第一数据所在的网元的标识、终端的标识、所述至少两个网元中至少一个网元的至少一个数据类型的数据值。
  6. 根据权利要求1-5任一项所述的方法,其特征在于,所述至少两个网元中包括第三网元,
    当所述第三网元为应用功能AF网元时,从所述第三网元获取到的第一数据还包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流所属的业务的通信模式参数、第一接口流比特率数据、第一接口时延数据、第一接口丢包率数据、第一接口包数据、时间戳、业务流所属的业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据和所述媒体编码类型数据的编码速率数据、缓存数据;其中,第一接口为用户面功能UPF网元和所述AF网元对应的数据网络DN之间的接口;
    当所述第三网元为策略控制功能PCF网元时,从所述第三网元获取到的第一数据还包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流所在会话的标识、所述业务流所在会话的数据网络名称DNN、所述业务流所在切片的标识信息、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、所述媒体编码类型要求的编码速率要求和所述业务标识的有效时间窗、无线接入技术类型;
    当所述第三网元为会话管理功能SMF网元时,从所述第三网元获取到的第一数据还包括以下信息中的一项或者多项:所述业务流的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息和所述业务流的标识的有效时间窗、无线接入技术类型;
    当所述第三网元为第一UPF网元时,从所述第三网元获取到的第一数据还包括以下信息中的一项或者多项:所述业务流的标识、时间戳、第二接口流比特率数据、第一接口流比特率数据、第三接口比特率数据、第二接口时延数据、第一接口时延数据、第三接口时延数据、第一接口丢包率数据、第二接口丢包率数据、第三接口丢包率数据、第一接口包数据、第二接口包数据和第三接口包数据;其中,所述第二接口为所述第一UPF网元和无线接入网RAN设备之间的接口;其中,第三接口为所述第一UPF网元与第二UPF网元之间的接口;
    当所述第三网元为接入和移动性管理AMF网元时,从所述第三网元获取到的第一数据还包括以下信息中的至少一项:所述业务流对应的终端的位置信息、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息和所述业务流所在会话的标识的有效时间窗、无线接入技术类型;
    当所述第三网元为RAN设备时,从所述第三网元获取到的第一数据还包括以下信息中的一项或者多项:所述业务流对应的终端的位置信息、所述业务流的标识、所述业务流所在会话的标识、所述业务流所在切片的标识信息、时间戳、第四接口流比特率数据、第二接口流比特率数据、第二接口时延数据、第四接口时延数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据、误块率BLER数据、拥塞等级、第二接口丢包率数据、第四接口丢包率数据、第二接口包数据和第四接口包数据、无线接入技术类型、双连接指示信息;其中,第四接口为所述RAN设备与所述终端之间的接口;
    当所述第三网元为终端时,从所述第三网元获取到的第一数据还包括以下信息中的一项或者多项:所述业务流对应的终端的位置信息、所述业务流的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息、第四接口流比特率数据、第四接口时延数据、第四接口丢包率数据、第四接口包数据、时间戳、处理器CPU占用率数据、内存占用率数据、业务体验数据、抖动缓存数据、TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据、所述媒体编码类型数据的编码速率数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据和误块率BLER数据、缓存数据。
  7. 根据权利要求1-6任一项所述的方法,其特征在于,所述业务流对应的在每个网元上的第一数据所包括的第一标识为以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流的标识、终端的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息。
  8. 根据权利要求1-6任一项所述的方法,其特征在于,所述业务流对应的在每个网元上的第一数据所包括的第一标识相同。
  9. 根据权利要求8所述的方法,其特征在于,所述方法还包括:
    所述第一网元接收第四网元发送的第三请求,所述第三请求用于请求为所述业务 流分配所述第一标识;
    所述第一网元向第三网元发送第三响应,所述第三响应包括所述第一标识。
  10. 根据权利要求1-9任一项所述的方法,其特征在于,所述业务流为服务质量流或者业务数据流。
  11. 一种数据发送方法,其特征在于,包括:
    网元确定获取到业务流的第一标识,其中,所述第一标识用于标识所述业务流对应的在所述网元上的第一数据;
    所述网元向第一网元发送所述第一数据,所述第一数据用于所述第一网元得到第二数据,其中,所述第二数据包括所述第一数据,所述第一数据中携带所述第一标识。
  12. 根据权利要求11所述的方法,其特征在于,包括:
    所述网元接收所述第一网元发送的第一请求,所述第一请求用于请求所述业务流对应的在所述网元上的第一数据,所述第一请求中包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流对应的终端的终端类型、所述终端使用所述业务流时对应的网络区域和所述业务流对应的时间窗。
  13. 根据权利要求11或12所述的方法,其特征在于,所述第一数据还包括以下信息中的一项或者多项:所述业务流对应的第一数据所在的网元的标识、终端的标识、两个或两个以上网元中至少一个网元的至少一个数据类型的数据值。
  14. 根据权利要求13所述的方法,其特征在于,所述网元的数据类型的数据值,具体包括:
    所述网元根据所述网元的第一数据类型的第一数据值确定第二数据值,其中,所述第一数据值属于第一数值空间,所述第二数据值属于第二数值空间,所述第一数据类型为第一数据中的任何一项。
  15. 根据权利要求13所述的方法,其特征在于,所述网元的数据类型的数据值,还包括:
    所述网元根据所述网元的第二数据类型的第三数据值确定第四数据值,其中,所述第三数据值属于第三数值空间,所述第四数据值属于第四数值空间,所述第二数据类型为所述第一数据中的任何一项。
  16. 根据权利要求14或15所述的方法,其特征在于,所述第二数值空间与第四数值空间相同。
  17. 根据权利要求11-16任一项所述的方法,其特征在于,
    当所述网元为应用功能AF网元时,所述第一数据还包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流所属的业务的通信模式参数、第一接口流比特率数据、第一接口时延数据、第一接口丢包率数据、第一接口包数据、时间戳、业务流所属的业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据和所述媒体编码类型数据的编码速率数据、缓存数据;其中,第一接口为用户面功能UPF网元和AF网元对应的数据网络DN之间的接口;
    当所述网元为策略控制功能PCF网元时,所述第一数据中还包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流所在会话的标识、所述业务流 所在会话的数据网络名称DNN、所述业务流所在切片的标识信息、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、所述媒体编码类型要求的编码速率要求和所述业务标识的有效时间窗、无线接入技术类型;
    当所述网元为会话管理功能SMF网元时,所述第一数据还包括以下信息中的一项或者多项:所述业务流的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息和所述业务流的标识的有效时间窗、无线接入技术类型;
    当所述网元为第一UPF网元时,所述第一数据还包括以下信息中的一项或者多项:所述业务流的标识、时间戳、第二接口流比特率数据、第一接口流比特率数据、第三接口比特率数据、第二接口时延数据、第一接口时延数据、第三接口时延数据、第一接口丢包率数据、第二接口丢包率数据、第三接口丢包率数据、第一接口包数据、第二接口包数据和第三接口包数据;所述第二接口为所述第一UPF网元和无线接入网RAN设备之间的接口;其中,第三接口为所述第一UPF网元与第二UPF网元之间的接口;
    当所述网元为接入和移动性管理AMF网元时,所述第一数据还包括以下信息中的至少一项:所述业务流对应的终端的位置信息、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息和所述业务流所在会话的标识的有效时间窗、无线接入技术类型;
    当所述网元为RAN设备时,所述第一数据还包括以下信息中的一项或者多项:所述业务流对应的终端的位置信息、所述业务流的标识、所述业务流所在会话的标识、所述业务流所在切片的标识信息、时间戳、第四接口流比特率数据、第二接口流比特率数据、第二接口时延数据、第四接口时延数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据、误块率BLER数据、第二接口丢包率数据、拥塞等级、第四接口丢包率数据、第二接口包数据和第四接口包数据、无线接入技术类型、双连接指示信息;其中,第四接口为所述RAN设备与所述终端之间的接口;
    当所述网元为终端时,所述第一数据还包括以下信息中的一项或者多项:使用所述业务流的终端的位置信息、所述业务流的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息、第四接口流比特率数据、第四接口时延数据、第四接口丢包率数据、第四接口包数据、时间戳、处理器CPU占用率数据、内存占用率数据、业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据、所述媒体编码类型数据的编码速率数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据和误块率BLER数据、缓存数据。
  18. 根据权利要求11-17任一项所述的方法,其特征在于,当所述网元为策略控制网元时,所述方法还包括:
    所述网元接收应用功能AF网元发送的第二请求,所述第二请求用于请求建立所述业务流,所述第二请求中包括以下信息中的一项或者多项:所述业务流所属的业务 标识、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、所述媒体编码类型要求的编码速率要求、缓存要求、至少一个数据类型的要求。
  19. 根据权利要求11-18任一项所述的方法,其特征在于,所述第一标识为以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流的标识、终端的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息。
  20. 根据权利要求11-19任一项所述的方法,其特征在于,所述业务流为服务质量流或者业务数据流。
  21. 一种数据发送方法,其特征在于,包括:
    网元向第一网元发送第一消息,所述第一消息用于指示所述第一网元从至少两个网元上获取业务流对应的第一数据,其中,所述第一消息包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流对应的终端的终端类型、所述业务流对应的终端所在的网络区域和所述业务流对应的时间窗。
  22. 一种数据处理装置,其特征在于,所述装置为第一网元或者为应用于第一网元中的芯片,所述装置包括:
    获取单元,用于获取业务流对应的在至少两个网元中每个网元上的第一数据,其中,所述业务流对应的在每个网元上的第一数据包括第一标识;
    处理单元,用于根据所述第一标识,以及所述业务流对应的在每个网元上的第一数据,得到所述业务流对应的第二数据,所述第二数据中至少包括业务流对应的在每个网元上的第一数据。
  23. 根据权利要求22所述的装置,其特征在于,所述装置还包括:
    接收单元,用于接收第二网元发送的第一消息,所述第一消息用于指示所述第一网元从所述至少两个网元获取所述业务流对应的第一数据,其中,所述第一消息包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流对应的终端的终端类型、所述业务流对应的终端所在的网络区域和所述业务流对应的时间窗。
  24. 根据权利要求22或23所述的装置,其特征在于,所述装置还包括:
    发送单元,用于向所述至少两个网元中每个网元发送第一请求,所述第一请求用于请求所述业务流对应的在所述每个网元上的第一数据,所述第一请求包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流对应的终端的终端类型、所述业务流对应的终端所在的网络区域和所述业务流对应的时间窗。
  25. 根据权利要求22-24任一项所述的装置,其特征在于,接收单元,还用于接收所述每个网元发送的第二消息,所述第二消息包括所述业务流对应的在各自网元上的第一数据,所述获取单元,具体用于从所述每个网元发送的第二消息中获取业务流对应的在至少两个网元中每个网元上的第一数据。
  26. 根据权利要求22-25任一项所述的装置,其特征在于,所述第一数据还包括以下信息中的一项或者多项:所述业务流对应的第一数据所在的网元的标识、终端的标识、所述至少两个网元中至少一个网元的至少一个数据类型的数据值。
  27. 根据权利要求22-26任一项所述的装置,其特征在于,所述至少两个网元中 包括第三网元,
    当所述第三网元为应用功能AF网元时,从所述第三网元获取到的第一数据还包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流所属的业务的通信模式参数、第一接口流比特率数据、第一接口时延数据、第一接口丢包率数据、第一接口包数据、时间戳、业务流所属的业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据和所述媒体编码类型数据的编码速率数据、缓存数据;其中,第一接口为用户面功能UPF网元和所述AF网元对应的数据网络DN之间的接口;
    当所述第三网元为策略控制功能PCF网元时,从所述第三网元获取到的第一数据还包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流所在会话的标识、所述业务流所在会话的数据网络名称DNN、所述业务流所在切片的标识信息、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、所述媒体编码类型要求的编码速率要求和所述业务标识的有效时间窗、无线接入技术类型;
    当所述第三网元为会话管理功能SMF网元时,从所述第三网元获取到的第一数据还包括以下信息中的一项或者多项:所述业务流的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息和所述业务流的标识的有效时间窗、无线接入技术类型;
    当所述第三网元为第一UPF网元时,从所述第三网元获取到的第一数据还包括以下信息中的一项或者多项:所述业务流的标识、时间戳、第二接口流比特率数据、第一接口流比特率数据、第三接口比特率数据、第二接口时延数据、第一接口时延数据、第三接口时延数据、第一接口丢包率数据、第二接口丢包率数据、第三接口丢包率数据、第一接口包数据、第二接口包数据和第三接口包数据;其中,所述第二接口为所述第一UPF网元和无线接入网RAN设备之间的接口;其中,第三接口为所述第一UPF网元与第二UPF网元之间的接口;
    当所述第三网元为接入和移动性管理AMF网元时,从所述第三网元获取到的第一数据还包括以下信息中的至少一项:所述业务流对应的的终端的位置信息、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息和所述业务流所在会话的标识的有效时间窗、无线接入技术类型;
    当所述第三网元为RAN设备时,从所述第三网元获取到的第一数据还包括以下信息中的一项或者多项:所述业务流对应的终端的位置信息、所述业务流的标识、所述业务流所在会话的标识、所述业务流所在切片的标识信息、时间戳、第四接口流比特率数据、第二接口流比特率数据、第二接口时延数据、第四接口时延数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据、误块率BLER数据、拥塞等级、第一接口丢包率数据、第二接口丢包率数据、第四接口丢包率数据、第二接口包数据和第四接口包数据、无线接入技术类型、双连接指示信息;其中,第四接口为所述RAN设备与所述终端之间的接口;
    当所述第三网元为终端时,从所述第三网元获取到的第一数据还包括以下信息中 的一项或者多项:所述业务流对应的终端的位置信息、所述业务流的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息、第四接口流比特率数据、第四接口时延数据、第四接口丢包率数据、第四接口包数据、时间戳、处理器CPU占用率数据、内存占用率数据、业务体验数据、抖动缓存数据、TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据、所述媒体编码类型数据的编码速率数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据和误块率BLER数据、缓存数据。
  28. 根据权利要求22-27任一项所述的装置,其特征在于,所述业务流对应的在每个网元上的第一数据所包括的第一标识为以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流的标识、终端的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息。
  29. 根据权利要求22-27任一项所述的装置,其特征在于,所述业务流对应的在每个网元上的第一数据所包括的第一标识相同。
  30. 根据权利要求29所述的装置,其特征在于,接收单元,还用于接收第四网元发送的第三请求,所述第三请求用于请求为所述业务流分配所述第一标识;
    发送单元,还用于向第三网元发送第三响应,所述第三响应包括所述第一标识。
  31. 根据权利要求22-30任一项所述的装置,其特征在于,所述业务流为服务质量流或者业务数据流。
  32. 一种数据发送装置,其特征在于,所述装置为网元或者为应用于网元中的芯片,所述装置包括:
    确定单元,用于确定获取到业务流的第一标识,其中,所述第一标识用于标识所述业务流在所述网元上的第一数据;
    发送单元,用于向第一网元发送所述第一数据,所述第一数据用于所述第一网元得到第二数据,其中,所述第二数据包括所述第一数据,所述第一数据中携带所述第一标识。
  33. 根据权利要求32所述的装置,其特征在于,包括:
    接收单元,用于接收所述第一网元发送的第一请求,所述第一请求用于请求所述业务流对应的在所述网元上的第一数据,所述第一请求中包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流对应的终端的终端类型、所述终端使用所述业务流时对应的网络区域和所述业务流对应的时间窗。
  34. 根据权利要求32或33所述的装置,其特征在于,所述第一数据还包括以下信息中的一项或者多项:所述业务流对应的第一数据所在的网元的标识、终端的标识、两个或两个以上网元中至少一个网元的至少一个数据类型的数据值。
  35. 根据权利要求33所述的装置,其特征在于,所述网元的数据类型的数据值,具体包括:
    所述确定单元,根据所述装置的第一数据类型的第一数据值确定第二数据值,其中,所述第一数据值属于第一数值空间,所述第二数据值属于第二数值空间,所述第一数据类型为第一数据中的任何一项。
  36. 根据权利要求33所述的装置,其特征在于,所述网元的数据类型的数据值, 还包括:
    所述确定单元,用于根据所述装置的第二数据类型的第三数据值确定第四数据值,其中,所述第三数据值属于第三数值空间,所述第四数据值属于第四数值空间,所述第二数据类型为所述第一数据中的任何一项。
  37. 根据权利要求35或36所述的装置,其特征在于,所述第二数值空间与第四数值空间相同。
  38. 根据权利要求32-37任一项所述的装置,其特征在于,
    当所述网元为应用功能AF网元时,所述第一数据还包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流所属的业务的通信模式参数、第一接口流比特率数据、第一接口时延数据、第一接口丢包率数据、第一接口包数据、时间戳、业务流所属的业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据和所述媒体编码类型数据的编码速率数据、缓存数据;其中,第一接口为用户面功能UPF网元和AF网元对应的数据网络DN之间的接口;
    当所述网元为策略控制功能PCF网元时,所述第一数据中还包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流所在会话的标识、所述业务流所在会话的数据网络名称DNN、所述业务流所在切片的标识信息、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、所述媒体编码类型要求的编码速率要求和所述业务标识的有效时间窗、无线接入技术类型;
    当所述网元为会话管理功能SMF网元时,所述第一数据还包括以下信息中的一项或者多项:所述业务流的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息和所述业务流的标识的有效时间窗、无线接入技术类型;
    当所述网元为第一UPF网元时,所述第一数据还包括以下信息中的一项或者多项:所述业务流的标识、时间戳、第二接口流比特率数据、第一接口流比特率数据、第三接口比特率数据、第二接口时延数据、第一接口时延数据、第三接口时延数据、第一接口丢包率数据、第二接口丢包率数据、第三接口丢包率数据、第一接口包数据、第二接口包数据和第三接口包数据;所述第二接口为所述第一UPF网元和无线接入网RAN设备之间的接口;其中,第三接口为所述第一UPF网元与第二UPF网元之间的接口;
    当所述网元为接入和移动性管理AMF网元时,所述第一数据还包括以下信息中的至少一项:所述业务流对应的终端的位置信息、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息和所述业务流所在会话的标识的有效时间窗、无线接入技术类型;
    当所述网元为RAN设备时,所述第一数据还包括以下信息中的一项或者多项:所述业务流对应的终端的位置信息、所述业务流的标识、所述业务流所在会话的标识、所述业务流所在切片的标识信息、时间戳、第四接口流比特率数据、第二接口流比特率数据、第二接口时延数据、第四接口时延数据、参考信号接收功率RSRP数据、参 考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据、误块率BLER数据、拥塞等级、第二接口丢包率数据、第四接口丢包率数据、第二接口包数据和第四接口包数据、无线接入技术类型、双连接指示信息;其中,第四接口为所述RAN设备与所述终端之间的接口;
    当所述网元为终端时,所述第一数据还包括以下信息中的一项或者多项:使用所述业务流的终端的位置信息、所述业务流的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息、第四接口流比特率数据、第四接口时延数据、第四接口丢包率数据、第四接口包数据、时间戳、处理器CPU占用率数据、内存占用率数据、业务体验数据、抖动缓存数据、传输控制协议TCP拥塞窗口数据、TCP接收窗口数据、媒体编码类型数据、所述媒体编码类型数据的编码速率数据、参考信号接收功率RSRP数据、参考信号接收质量RSRQ数据、信号干扰噪声比SINR数据、信道质量信息CQI数据和误块率BLER数据、缓存数据。
  39. 根据权利要求32-38任一项所述的装置,其特征在于,当所述装置为策略控制网元时,接收单元,还用于接收应用功能AF网元发送的第二请求,所述第二请求用于请求建立所述业务流,所述第二请求中包括以下信息中的一项或者多项:所述业务流所属的业务标识、IP过滤信息、媒体带宽要求、流量路由信息、抖动缓存要求、TCP拥塞窗口要求、TCP接收窗口要求、媒体编码类型要求、所述媒体编码类型要求的编码速率要求、缓存要求、至少一个数据类型的要求。
  40. 根据权利要求32-39任一项所述的装置,其特征在于,所述第一标识为以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流的标识、终端的标识、所述业务流所在会话的标识、所述业务流所在会话的DNN、所述业务流所在切片的标识信息。
  41. 根据权利要求32-40任一项所述的装置,其特征在于,所述业务流为服务质量流或者业务数据流。
  42. 一种数据发送装置,其特征在于,所述装置为网元或者为应用于网元中的芯片,所述装置包括:
    发送单元,用于向第一网元发送第一消息,所述第一消息用于指示所述第一网元从至少两个网元上获取业务流对应的第一数据,其中,所述第一消息包括以下信息中的一项或者多项:所述业务流所属的业务标识、所述业务流对应的终端的终端类型、所述业务流对应的终端所在的网络区域和所述业务流对应的时间窗。
  43. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质中存储有计算机程序或指令,当计算机程序或指令在计算机上运行时,使得计算机执行如权利要求1至10中任一项所述的方法,或者如权利要求11至20中任一项所述的方法,或者如权利要求21所述的方法。
  44. 一种芯片,其特征在于,所述芯片包括处理器和接口电路,所述接口电路和所述处理器耦合,所述处理器用于运行计算机程序或指令,以实现如权利要求1至10中任一项所述的方法,或者如权利要求11至20中任一项所述的方法,或者如权利要求21所述的方法,所述接口电路用于与所述芯片之外的其它模块进行通信。
  45. 一种系统,其特征在于,包括如权利要求22-31任一项所述的数据处理装置 和如权利要求32-41任一项所述的数据发送装置。
PCT/CN2019/084816 2018-05-21 2019-04-28 一种数据处理方法、发送方法及装置 WO2019223498A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19807880.0A EP3755048B1 (en) 2018-05-21 2019-04-28 Data processing method, and data transmission method and apparatus
US17/033,293 US11463918B2 (en) 2018-05-21 2020-09-25 Data processing method and apparatus, and data sending method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810490222.4 2018-05-21
CN201810490222.4A CN110519802B (zh) 2018-05-21 2018-05-21 一种数据处理方法、发送方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/033,293 Continuation US11463918B2 (en) 2018-05-21 2020-09-25 Data processing method and apparatus, and data sending method and apparatus

Publications (1)

Publication Number Publication Date
WO2019223498A1 true WO2019223498A1 (zh) 2019-11-28

Family

ID=68615663

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/084816 WO2019223498A1 (zh) 2018-05-21 2019-04-28 一种数据处理方法、发送方法及装置

Country Status (4)

Country Link
US (1) US11463918B2 (zh)
EP (1) EP3755048B1 (zh)
CN (1) CN110519802B (zh)
WO (1) WO2019223498A1 (zh)

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110062426B (zh) * 2019-04-02 2021-08-24 腾讯科技(深圳)有限公司 通信方法、装置、计算机可读介质及电子设备
CN113037645A (zh) * 2019-12-24 2021-06-25 深圳市中兴微电子技术有限公司 业务传输方法及装置、计算机可读的存储介质、电子装置
CN111050341B (zh) * 2019-12-24 2022-02-22 展讯通信(上海)有限公司 双连接场景下空口拥塞状态的判定方法及装置
CN111200541B (zh) * 2019-12-31 2022-04-12 山石网科通信技术股份有限公司 网络数据处理方法和装置
CN113162788B (zh) * 2020-01-23 2022-12-27 华为技术有限公司 报告信息的发送方法和通信装置以及通信系统
CN113179171B (zh) * 2020-01-24 2023-04-18 华为技术有限公司 故障检测方法、装置及系统
US11523377B2 (en) * 2020-02-14 2022-12-06 T-Mobile Usa, Inc. LTE resource allocation controller
US20220264439A1 (en) * 2020-05-08 2022-08-18 Nec Corporation Support for network slice quota event notification
CN113691483B (zh) * 2020-05-18 2022-06-14 华为技术有限公司 异常用户设备的检测方法、装置、设备及存储介质
CN111757316B (zh) * 2020-06-23 2022-08-19 中国联合网络通信集团有限公司 一种业务连接方法及装置
US11553354B2 (en) * 2020-06-29 2023-01-10 At&T Intellectual Property I, L.P. Apparatuses and methods for enhancing network controls based on communication device information
CN114071518A (zh) * 2020-07-31 2022-02-18 中移(苏州)软件技术有限公司 一种信息处理方法、装置、设备及计算机存储介质
CN114125882A (zh) * 2020-08-31 2022-03-01 华为技术有限公司 一种资源传输保障方法、装置及系统
CN112637132B (zh) * 2020-12-01 2022-03-11 北京邮电大学 一种网络异常检测方法、装置、电子设备和存储介质
CN116325686A (zh) * 2020-12-30 2023-06-23 华为技术有限公司 一种通信方法和装置
US11706821B2 (en) * 2021-02-12 2023-07-18 Verizon Patent And Licensing Inc. Systems and methods for facilitating connection to a data network in an interworking core network
CN114978559A (zh) * 2021-02-21 2022-08-30 华为技术有限公司 DDoS攻击检测的方法和装置
CN113179518B (zh) * 2021-06-30 2021-10-26 中移(上海)信息通信科技有限公司 一种数据传输方法、数据传输装置、数据传输设备及终端
US20230007573A1 (en) * 2021-07-01 2023-01-05 Samsung Electronics Co., Ltd. Methods and apparatus for media communication services using network slicing
CN114302429B (zh) * 2021-12-27 2023-04-28 中国联合网络通信集团有限公司 Nwdaf网元的确定方法、装置、设备及存储介质
CN116567730A (zh) * 2022-01-28 2023-08-08 大唐移动通信设备有限公司 一种通信方法及设备
CN117768943A (zh) * 2022-09-14 2024-03-26 华为技术有限公司 一种通信系统中传输数据的方法和通信装置
WO2024103300A1 (zh) * 2022-11-16 2024-05-23 Oppo广东移动通信有限公司 通信方法及通信装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015120601A1 (zh) * 2014-02-13 2015-08-20 华为技术有限公司 移动通信网络检测方法和装置
CN105072629A (zh) * 2015-06-30 2015-11-18 华为技术有限公司 测量终端上运行的业务的质量的方法、设备及系统
US9722887B2 (en) * 2011-03-15 2017-08-01 Verizon Patent And Licensing Inc. Adaptive quality of service (QoS) based on application latency requirements
CN107484224A (zh) * 2016-06-08 2017-12-15 中国移动通信有限公司研究院 一种数据传输方法及装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102098651B (zh) * 2011-01-21 2013-08-14 北京邮电大学 利用用户服务标识usid实施策略标识与控制的方法
US11444850B2 (en) 2016-05-02 2022-09-13 Huawei Technologies Co., Ltd. Method and apparatus for communication network quality of service capability exposure
US10142889B2 (en) * 2016-05-13 2018-11-27 Huawei Technologies Co., Ltd. Method and system for providing guaranteed quality of service and quality of experience channel
US10362507B2 (en) * 2016-06-10 2019-07-23 Huawei Technologies Co., Ltd. Systems and method for quality of service monitoring, policy enforcement, and charging in a communications network
US11368873B2 (en) * 2017-12-15 2022-06-21 Huawei Technologies Co., Ltd. Method and system of packet aggregation
US11134410B2 (en) * 2017-12-25 2021-09-28 Nokia Solutions And Networks Oy Quality of service (QoS) control in mobile edge computing (MEC)
US10986528B2 (en) * 2018-02-15 2021-04-20 Huawei Technologies Co., Ltd. Tracking QoS violated events
CN110351229B (zh) * 2018-04-04 2020-12-08 电信科学技术研究院有限公司 一种终端ue管控方法及装置
WO2019194473A1 (ko) * 2018-04-05 2019-10-10 엘지전자 주식회사 무선 통신 시스템에서 프로토콜 데이터 유닛 세션을 제어하는 방법 및 이를 위한 장치
US11140047B2 (en) * 2018-04-09 2021-10-05 Intel Corporation Network data analytics function (NWDAF) influencing fifth generation (5G) quality of service (QoS) configuration and adjustment
US11678252B2 (en) * 2018-10-05 2023-06-13 Huawei Technologies Co., Ltd. Quality of service information notification to user equipment, users, and application server

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9722887B2 (en) * 2011-03-15 2017-08-01 Verizon Patent And Licensing Inc. Adaptive quality of service (QoS) based on application latency requirements
WO2015120601A1 (zh) * 2014-02-13 2015-08-20 华为技术有限公司 移动通信网络检测方法和装置
CN105072629A (zh) * 2015-06-30 2015-11-18 华为技术有限公司 测量终端上运行的业务的质量的方法、设备及系统
CN107484224A (zh) * 2016-06-08 2017-12-15 中国移动通信有限公司研究院 一种数据传输方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3755048A4

Also Published As

Publication number Publication date
EP3755048B1 (en) 2022-04-06
EP3755048A4 (en) 2021-04-14
US20210014739A1 (en) 2021-01-14
EP3755048A1 (en) 2020-12-23
US11463918B2 (en) 2022-10-04
CN110519802A (zh) 2019-11-29
CN110519802B (zh) 2022-05-10

Similar Documents

Publication Publication Date Title
WO2019223498A1 (zh) 一种数据处理方法、发送方法及装置
US11588741B2 (en) Service flow processing method, communication method, and apparatus
WO2020207178A1 (zh) 一种漫游数据处理方法、装置及系统
WO2020200037A1 (zh) 一种数据处理方法、装置及系统
US11832352B2 (en) Service flow transmission method and apparatus and communications method and apparatus
US10581747B2 (en) System and method for low-overhead interoperability between 4G and 5G networks
WO2020108003A1 (zh) 一种用户接入控制方法、信息发送方法及装置
US8867447B2 (en) Dynamic header compression based on attributes of traffic
US20220030117A1 (en) Systems and methods to enable programmable xhaul transport
US11811650B2 (en) Systems and methods for user plane function (“UPF”) offload at configurable routing fabric
WO2020001336A1 (zh) 一种信息处理方法及装置
WO2020147756A1 (zh) 一种会话管理方法及装置
WO2019062496A1 (zh) 数据分析方法和数据分析装置
US11743772B2 (en) Systems and methods for differentiated traffic treatment for different traffic types associated with multi-persona applications
US20220417785A1 (en) QoS MAPPING
CN113923682B (zh) 通信方法、装置及系统
US20230142002A1 (en) Communication Method and Apparatus
US11115896B2 (en) Handling QoS rules on QoS operation errors
WO2021058029A1 (zh) 一种控制业务流传输的方法、装置及系统
WO2020034869A1 (zh) 一种业务流的传输方法、通信方法及装置
RU2787887C2 (ru) Способ и устройство обработки данных и способ и устройство отправки данных
US11350312B1 (en) Systems and methods for dynamic rule determination for user plane data in a wireless network
WO2024037256A1 (zh) 一种业务流路由方法及装置
US20220094566A1 (en) Policy control function fallback
OA20745A (en) QOS Mapping.

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019807880

Country of ref document: EP

Effective date: 20200916

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2020135511

Country of ref document: RU