RU2787887C2 - Method and device for data processing and method and device for data sending - Google Patents

Abstract

FIELD: communication technologies.

SUBSTANCE: first network element receives the first data, which corresponds to a service flow, and which is located in each of at least two network elements. At the same time, the first data, which corresponds to the service flow, and which is located in each of network elements, includes the first identifier. The first network element receives, based on the first identifier and the first data, which corresponds to the service flow, and which is located in each of the mentioned network elements, the second data, which corresponds to the service flow, while the second data includes at least the first data, which corresponds to the service flow, and which is located in each of the mentioned network elements. At the same time, the first network element is a network element of a network data analysis function (NWDAF).

EFFECT: possibility of reception of data, which is related to a service flow and is distributed among different network elements.

24 cl, 5 tbl, 20 dwg

Description

The technical field to which the invention belongs

[0001] Embodiments of the present application relate to the field of communication technologies and, in particular, to a method and device for processing data, as well as a method and device for sending data.

State of the art

[0002] In 3GPP Release 15 (release 15, R15), the network element of the policy control function (PCF) on the core network side generates a set of quality of service (QoS) parameters for the service, but network data and data services change over time, which leads to a change in the quality of service. Therefore, only one set of QoS parameters cannot satisfy the ever-changing network environment (corresponding to network data) and service requirements (corresponding to service data). As shown in Fig. 1, the service starts at the first time T1 (time stamp 0000) and ends at the second time T2 (time stamp 0012). In the time period (eg, 12 seconds (s)) between T2 and T1, the mean opinion score (MOS) is calculated every second.

[0003] It can be understood from FIG. 1 that the main reasons for differences in voice MOS corresponding to different points in time lie in the state of the network and the change in time (meaning that network data and service data change over time) of some service parameters. For example, the service parameters may be: radio channel quality, bandwidth, delay, packet loss ratio, delay jitter buffer, transmission control protocol (TCP) congestion window, TCP receive window, and the like. in the terminal; radio link quality, bandwidth, latency, packet loss rate, congestion level, etc. on the radio interface of the access network; user plane bandwidth, user plane load information, and the like. on the side of the core network; and TCP congestion window, TCP receive window, media content encoding type, encoding rate, and the like. at the service level. These time-varying parameters at the terminal, access network, core network, and service layer affect service usage.

[0004] In a 5G system, a terminal service is carried in a sub-service flow. The sub-service flow may be a quality of service flow, that is, a QoS flow, or may be a service data flow, that is, a service data flow. Therefore, a service usage change is actually a usage change specific to a sub-service flow and corresponds to a change in parameters at the terminal, access network, core network, or service layer. Thus, obtaining parameters distributed to different network elements based on flow levels per service is a technical problem that needs to be urgently solved at present.

The essence of the invention

[0005] Embodiments of the present application provide a data processing method and apparatus, as well as a data sending method and apparatus for receiving data that is related to a sub-service flow and distributed across different network elements.

[0006] To achieve the above goal, the following technical solutions are used in the embodiments of the present application:

[0007] According to a first aspect, in one embodiment of the present application, a data processing method is provided, including: obtaining, by a first network element, first data that corresponds to a sub-service flow and that is in each of at least two network elements, wherein the first data , which correspond to the flow under the service and which are in each of the mentioned network elements, include the first identifier; and obtaining, by the first network element, based on the first identifier and the first data that corresponds to the sub-service flow and which is in each of said network elements, the second data that corresponds to the sub-service flow, the second data including at least the first the data that corresponds to a service flow and that resides in each of said network elements, or the second data includes at least a portion of the first data that corresponds to a service flow and that resides in each of said network elements.

[0008] This embodiment of the present application provides a data processing method. The first network element receives the first data that is related to the service flow and is in different network elements, and matches the first data that is related to the service flow and is in different network elements, based on the first identifiers in the first data sent from different network elements to obtain the second data. Thus, the first network element may subsequently schedule one or more sets of QoS parameters of the service to which the sub-service flow belongs, the user plane path corresponding to the session to which the sub-service flow belongs, dedicated logical segment resource optimization, user plane or control plane anomaly detection. etc.

[0009] With reference to the first aspect, in the first possible implementation of the first aspect, the method provided in the embodiment of the present application further includes: receiving, by the first network element, a first message that is sent from the second network element and that is used to indicate the first network element to receive from at least two network elements the first data corresponding to the sub-service flow. The first message includes one or more of the following information: an identifier of the service to which the sub-service flow belongs, the terminal type of the terminal corresponding to the sub-service flow, the network area in which the terminal corresponding to the sub-service flow is located, and the time window corresponding to the flow. under the service. The request is sent to the first network element using the first message, so that the first network element can determine that the first data, which corresponds to a sub-service flow and which is in different network elements, should be received from different network elements. Since the first message further carries a time window corresponding to the sub-service flow, the first network element can receive corresponding data that varies over time in different network elements.

[0010] With reference to the first aspect or the first possible implementation of the first aspect, in the second possible implementation of the first aspect, the method provided in this embodiment of the present application further includes: sending, by the first network element, the first request to each of at least at least two network elements, wherein the first request is used to request the first data that corresponds to a sub-service flow and which is in each of said network elements, and the first request includes one or more of the following information: an identifier of the service to which the service flow belongs , the terminal type of the terminal corresponding to the service flow, the network area in which the terminal corresponding to the service flow is located, and the time window corresponding to the service flow. Thus, after receiving the first request, each network element becomes aware of the first network element's requirement to send back the first data that corresponds to the sub-service flow that is in the network element and that satisfies the first network element's requirement.

[0011] With reference to any of the first aspect or the first or second possible implementation of the first aspect, in the third possible implementation of the first aspect, the receipt by the first network element of the first data that corresponds to a sub-service flow and that is on each of at least two network elements includes: receiving by the first network element of the second message that is sent from each of the said network elements and includes the first data that corresponds to the sub-service flow and that is in each of the said network elements.

[0012] With reference to any of the first aspect or the first to third possible implementations of the first aspect, in the fourth possible implementation of the first aspect, the first data further includes one or more of the following information: an identifier of the network element to which the first data belongs, corresponding to the sub-service flow, a terminal identifier and a data value of at least one data type of at least one of the at least two network elements. Thus, the information contained in the first data is more diverse.

[0013] For example, the terminal identifier in this embodiment of the present application may be one or more of the following: Internet Protocol (IP) address, subscription permanent identifier (SUPI), permanent equipment identifier , PEI), generic public subscription identifier (GPSI), international mobile subscriber identifier (IMSI), international mobile equipment identity (IMEI), 5-tuple IP (5- tuple) and the International Mobile Station ISDN Number (International Integrated Services Digital Network Number, MSISDN). For more information about the terminal ID in the following embodiments, please refer to the description. Details are not described further.

[0014] With reference to any of the first aspect or the first to fourth possible implementations of the first aspect, in the fifth possible implementation of the first aspect, at least two network elements include a third network element. When the third network element is an application function (AF) network element, the first data received from the third network element further includes one or more of the following information: an identifier of the service to which the sub-service flow belongs, a link template parameter of the service to which sub-service stream, first interface stream bit rate data, first interface delay data, first interface packet loss rate data, first interface packet data, timestamp, usage data of the service to which the sub-service stream belongs, delay jitter buffer data , transmission control protocol (TCP) congestion window data, TCP receive window data, media content coding type data, media content coding type data coding rate data, and buffer data, the first interface being an interface between a user plane function (UPF) network element ) and data network (DN) which th corresponds to the network element AF; when the third network element is a policy control function (PCF) network element, then the first data received from the third network element further includes one or more of the following information: an identifier of the service to which the sub-service flow belongs, a session identifier to which the flow belongs sub-service, data network name (DNN) of the session to which the sub-service flow belongs, identification information of the specialized logical segment to which the sub-service flow belongs, IP filtering information, media content bandwidth requirement, traffic routing information, delay jitter buffer requirement , TCP congestion window requirement, TCP receive window requirement, media content encoding type requirement, encoding rate requirement in media content encoding type requirement, service ID validity time window, and radio access technology type; when the third network element is a session management function (SMF) network element, then the first data received from the third network element further includes one or more of the following information: sub-service flow identifier, session identifier to which the sub-service flow belongs, DNN the session to which the service flow belongs, the identity of the dedicated logical segment to which the service flow belongs, the validity time window of the service flow identifier, and the radio access technology type; when the third network element is the first UPF network element, then the first data received from the third network element further includes one or more of the following information: sub-service flow identifier, time stamp, second interface flow bit rate data, bit rate data first interface bit rate data, third interface bit rate data, second interface delay data, first interface delay data, third interface delay data, first interface packet loss ratio data, second interface packet loss ratio data, loss ratio data packet data of the third interface, packet data of the first interface, packet data of the second interface and packet data of the third interface, receiving the second interface is the interface between the first UPF network element and the radio access network (RAN) device, and the third interface is the interface between the first UPF network element and the second m network element UPF; when the third network element is an access and mobility management (AMF) network element, then the first data received from the third network element further includes at least one of the following information: location information of the terminal corresponding to the sub-service flow, a session identifier, to which the service flow belongs, the DNN of the session to which the service flow belongs, the identity of the dedicated logical segment to which the service flow belongs, the validity time window of the session identifier to which the service flow belongs, and the type of radio access technology; when the network element is a RAN device, the first data received from the third network element further includes one or more of the following information: location information of the terminal corresponding to the sub-service flow, the identifier of the sub-service flow, the session identifier to which the sub-flow belongs service, identification information of the dedicated logical segment to which the flow under the service belongs, timestamp, fourth interface bit rate data, second interface bit rate data, second interface delay data, fourth interface delay data, received reference power data signal-to-interference-plus-noise ratio (SINR) data, channel quality information (CQI) data, block error rate (BLER) data, bit rate data packets, second interface packet data, packet data a fourth interface, a radio access technology type, and dual connectivity indication information, wherein the fourth interface is an interface between a RAN device and a terminal; or when the third network element is a terminal, the first data received from the third network element further includes one or more of the following information: location information of the terminal corresponding to the sub-service flow, a sub-service flow identifier, a session identifier to which the flow belongs sub-service, session DNN to which the sub-service flow belongs, identification information of the dedicated logical segment to which the sub-service flow belongs, fourth interface stream bit rate data, fourth interface delay data, fourth interface packet loss rate data, fourth interface packet data , timestamp, CPU usage data, memory usage data, service usage data, delay jitter buffer data, TCP congestion window data, TCP receive window data, media content encoding type data, type k data encoding rate data media content encoding, received reference signal power (RSRP) data, received reference signal quality (RSRQ) data, signal-to-interference plus noise ratio (SINR) data, channel quality information (CQI) data, block error rate data (BLER) and buffer data. Thus, the first data returned by different network elements is more varied.

[0015] For example, the identification information of a dedicated logical segment (slice) can be one or more of the following information: single network slice selection assistance information (S-NSSAI) and an instance ID of the network dedicated logical segment (network slice instance, NSI), while S-NSSAI includes a specialized logical segment type (slice type) and a client identifier (Tentant ID). For information about the identification information of the dedicated logical segment in the following embodiments, the implementation should refer to the description. Details are not described further.

[0016] For example, the location information of the terminal in this embodiment of the present application may be one or more of the following information: RAN device ID, Cell ID, and global positioning system (GPS). For information about the location information of the terminal in the following embodiments, the implementation should refer to the description. Details are not described further.

[0017] With reference to any of the first aspect, or the first through fifth possible implementations of the first aspect, in the sixth possible implementation of the first aspect, the first identifier included in the first data that corresponds to the sub-service flow and that is in each of said network elements , is one or more of the following information: ID of the service that owns the service flow, ID of the service flow, terminal ID, session ID of the session that owns the service flow, DNN of the session that owns the service flow, identification information of the segment that owns the service flow. Due to the diversity of the first identifier, the first network element can determine, based on the first identifier, the first data that corresponds to the same sub-service flow and that is in different network elements.

[0018] With reference to any of the first aspect or the first to the sixth possible implementations of the first aspect, in the seventh possible implementation of the first aspect, the first data that corresponds to a sub-service flow and that is in each of the network elements includes one and the same first identifier.

[0019] With reference to any of the first aspect, or the first to the seventh possible implementations of the first aspect, in the eighth possible implementation of the first aspect, the method provided in this embodiment of the present invention further includes: receiving by the first network element the third a request sent from a fourth network element, the third request being used to request allocation of a first flow identifier for a service; and sending, via the first network element, a third response to the third network element, the third response including the first identifier.

[0020] With reference to any of the first aspect or the first to eighth possible implementations of the first aspect, in the ninth possible implementation of the first aspect, the sub-service flow is a quality of service flow or a service data flow.

[0021] With reference to any of the first aspect or the first through ninth possible implementations of the first aspect, in the tenth possible implementation of the first aspect, obtaining by the first network element the first data that corresponds to a sub-service flow and that is on each of at least two network elements, includes: receiving by the first network element the first data that is sent from the operation, administration and maintenance network element, which corresponds to a sub-service flow and which is located on each of said at least two network elements.

[0022] According to a second aspect, in one embodiment of the present application, a data processing method is provided, the method including: determining, by a network element, that a first service flow identifier has been received, the first identifier being used to identify the first data that relates to flow under the service and which are located in the network element; and sending, via the network element, first data to the first network element, the first data being used by the first network element to obtain second data, the second data including the first data or the second data including a portion of the first data, and the first data carrying the first identifier.

[0023] With reference to the second aspect, in the first possible implementation of the second aspect, the method provided in this embodiment of the present application includes: receiving by the network element the first request sent from the first network element, and the first request is used to request the first data that corresponds to the service flow and which is in the network element, and the first request includes one or more of the following information: the identifier of the service to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, the network area corresponding to the terminal when the terminal is using the pod flow, and a time window corresponding to the pod flow.

[0024] With reference to the second aspect or the first possible implementation of the second aspect, in the second possible implementation of the second aspect, the first data further includes one or more of the following information: an identifier of the network element to which the first data corresponding to the sub-service flow belongs, a terminal identifier; and a data value of at least one data type of at least one of the two or more network elements.

[0025] With reference to any of the second aspect or the first or second possible implementation of the second aspect, in the third possible implementation of the second aspect, the data value of the data type of the network element includes: determining by the network element the second data value, based on the first data value the first data type of the network element, wherein the first data value belongs to the first value space, the second data value belongs to the second value space, and the first data type is some entry in the first data.

[0026] With reference to any of the second aspect or the first to third possible implementations of the second aspect, in the fourth possible implementation of the second aspect, the data value of the data type of the network element further includes: determining by the network element the fourth data value based on the third data values of the second data type of the network element, where the third data value belongs to the third value space, the fourth data value belongs to the fourth value space, and the second data type is some entry in the first data.

[0027] With reference to any of the second aspect or the first to fourth possible implementations of the second aspect, in the fifth possible implementation of the second aspect, the second value space is the same as the fourth value space.

[0028] With reference to the second aspect or the first to fifth possible implementations of the second aspect, in the sixth possible implementation of the second aspect, when the network element is an application function (AF) network element, the first data further includes one or more of the following information: ID of the service to which the sub-service flow belongs, communication pattern parameter of the service to which the sub-service flow belongs, bit rate data of the first interface stream, delay data of the first interface, packet loss rate data of the first interface, packet data of the first interface, timestamp, usage data of the service to which the stream sub-service belongs, delay jitter buffer data, transmission control protocol (TCP) congestion window data, TCP receive window data, media content coding type data, coding type data coding rate data media content and buffer data, with the first interface c is the interface between the UPF network element and the data network (DN) that corresponds to the AF network element; when the network element is a policy control function (PCF) network element, the first data further includes one or more of the following information: a service identifier to which the sub-service flow belongs, a session identifier to which the sub-service flow belongs, a data network name (DNN ) of the session that owns the service flow, identification information of the segment that owns the service flow, IP filtering information, media content bandwidth requirement, traffic routing information, delay jitter buffer requirement, TCP congestion window requirement, window requirement TCP reception, media content coding type requirement, coding rate requirement in media content coding type requirement, service ID validity time window, and radio access technology type; when the network element is a session management function (SMF) network element, the first data further includes one or more of the following information: a sub-service flow identifier, a session identifier to which the sub-service flow belongs, a session DNN to which the sub-service flow belongs, identification information of the dedicated logical segment to which the flow sub-service belongs, the time window of validity of the flow sub-service identifier, and the type of radio access technology; when the network element is the first network element of the UPF, the first data further includes one or more of the following information: sub-service flow identifier, timestamp, second interface flow bit rate data, first interface flow bit rate data, bit rate data 3rd interface speed data, 2nd interface delay data, 1st interface delay data, 3rd interface delay data, 1st interface packet loss rate data, 2nd interface packet loss rate data, 3rd interface packet loss rate data, 1st interface packet loss data , packet data of a second interface and packet data of a third interface, the second interface being an interface between the first UPF network element and a radio access network (RAN) device, and the third interface being the interface between the first UPF network element and the second UPF network element; when the network element is an Access and Mobility Management (AMF) network element, then the first data further includes at least one of the following information: location information of the terminal corresponding to the sub-service flow, session identifier to which the sub-service flow belongs, session DNN , to which the service flow belongs, the identity of the dedicated logical segment to which the service flow belongs, the validity time window, the session identifier to which the service flow belongs, and the type of radio access technology; when the network element is a RAN device, the first data further includes one or more of the following information: location information of the terminal corresponding to the sub-service flow, the ID of the sub-service flow, the identifier of the session to which the sub-service flow belongs, the identification information of the dedicated logical segment , which owns the sub-service stream, timestamp, fourth interface stream bit rate data, second interface stream bit rate data, second interface delay data, fourth interface delay data, received reference signal power (RSRP) data, received reference signal quality (RSRQ), signal-to-interference-plus-noise ratio (SINR) data, channel quality information (CQI) data, block error rate (BLER) data, second interface packet loss ratio data, fourth interface packet loss, packet data e of the second interface, the fourth interface packet data, the radio access technology type, and dual connectivity indication information, the fourth interface being the interface between the RAN device and the terminal; or when the network element is a terminal, the first data further includes one or more of the following information: location information of the terminal that uses the sub-service flow, the sub-flow ID, the session ID that the sub-service flow belongs to, the session DNN that sub-service flow belongs, identity of the dedicated logical segment to which the sub-service flow belongs, bit rate data of the fourth interface, delay data of the fourth interface, packet loss rate data of the fourth interface, packet data of the fourth interface, timestamp, usage data processing unit (CPU), memory usage data, service usage data, delay jitter buffer data, Transmission Control Protocol (TCP) congestion window data, TCP receive window data, media content encoding type data, data type encoding rate data kodi Received Reference Power (RSRP) Data, Received Reference Quality (RSRQ) Data, Signal to Interference Plus Noise Ratio (SINR) Data, Channel Quality Information (CQI) Data, Block Error Rate Data (BLER) and buffer data.

[0029] With reference to the second aspect, or the first to sixth possible implementations of the second aspect, in the seventh possible implementation of the second aspect, when the network element is a policy control network element, the method provided in this embodiment of the present application further includes itself: receiving by the network element a second request sent from an application function (AF) network element, wherein the second request is used to request establishment of a sub-service flow, and the second request includes one or more of the following information: an identifier of the service to which the sub-service flow belongs. service, IP filtering information, media bandwidth requirement, traffic routing information, delay jitter buffer requirement, TCP congestion window requirement, TCP receive window requirement, media content encoding type requirement, encoding rate requirement in type requirement mediacon encoding a tent, a buffer requirement, and a requirement for at least one data type.

[0030] With reference to the second aspect or the first to the seventh possible implementations of the second aspect, in the eighth possible implementation of the second aspect, the first identifier is one or more of the following information: the identifier of the service, which flow under the service, the identifier of the flow under the service, the identifier of the terminal, the session identifier to which the service flow belongs, the session DNN to which the service flow belongs, the identification information of the dedicated logical segment to which the service flow belongs.

[0031] With reference to any of the second aspect or the first to eighth possible implementations of the second aspect, in the ninth possible implementation of the second aspect, the sub-service flow is a quality of service flow or a service data flow.

[0032] With reference to any of the second aspect or the second aspect of the first through ninth possible implementations, in the tenth possible implementation of the second aspect, the network element sends a first message to the first network element, where the first message is used to instruct the first network element to receive from at least at least two network elements, the first data corresponding to the service flow, and the first message includes one or more of the following information: an identifier of the service to which the service flow belongs, a terminal type of the terminal corresponding to the service flow, a network area in which the a terminal corresponding to the service flow, and a time window corresponding to the service flow.

[0033] With reference to any of the second aspect or the second aspect of the first to tenth possible implementations, in the eleventh possible implementation of the second aspect, the data value of the data type of the network element further includes: determining by the network element a sixth data value based on the fifth value data of a third NE data type, wherein the fifth data value belongs to the fifth value space, the sixth data value belongs to the sixth value space, and the third data type is some entry in the first data.

[0034] With reference to any of the second aspect or the first to the eleventh possible implementations of the second aspect, in the twelfth possible implementation of the second aspect, every two of the second value space, the fourth value space and the sixth value space are the same.

[0035] With reference to any of the second aspect or the first to twelfth possible implementations of the second aspect, in the thirteenth possible implementation of the second aspect, the sender is configured to send the first data to the operation, administration and maintenance network element.

[0036] According to a third aspect, in one embodiment of the present application, a method is provided for sending data, the method including: sending, by means of a network element, to a first network element a first message used to instruct the first network element to receive from at least two said network elements the first data corresponding to the service flow, and the first message includes one or more of the following information: an identifier of the service to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, the network area in which the terminal corresponding to the service flow is located service, and a time window corresponding to the flow under the service.

[0037] According to a fourth aspect, the present application provides a data processing device. The data processing device may implement the method in the first aspect or any possible implementation of the first aspect and, therefore, may achieve beneficial effects in the first aspect or any possible implementation of the first aspect. The data processing device may be the first network element, or may be a device that can support the first network element in implementing the method in the first aspect, or any possible implementation of the first aspect, such as a chip used in the first network element. The device may implement the above method with software or hardware or a hardware implementation of the corresponding software.

[0038] In an exemplary embodiment, in one embodiment of the present application, a data processing device is provided. The data processing device may be the first network element or a chip used in the first network element. The data processing device includes: a receiving unit configured to receive the first data that corresponds to a sub-service flow and that is in each of at least two network elements, while the first data that corresponds to a sub-service flow and that is in each of said network elements, include a first identifier; and a processing unit configured to obtain, based on the first identifier and the first data that corresponds to the sub-service flow and which is in each of said network elements, the second data that corresponds to the sub-service flow, the second data including at least at least the first data that corresponds to a service flow and that resides in each of said network elements, or the second data includes at least a portion of the first data that corresponds to a service flow and that resides in each of said network elements.

[0039] With reference to the fourth aspect, in the first possible embodiment of the fourth aspect, the device provided by this embodiment of the present application further includes: a receiving unit configured to receive a first message sent from the second network element, wherein the first message is used to direct the first network element to receive from at least two network elements the first data corresponding to the service flow, and the first message includes one or more of the following information: an identifier of the service to which the service flow belongs, a terminal type of the terminal corresponding service flow, the network area in which the terminal corresponding to the service flow is located, and the time window corresponding to the service flow.

[0040] With reference to the fourth aspect or the first possible implementation of the fourth aspect, in the second possible implementation of the fourth aspect, the device provided by this embodiment of the present application further includes: a sending unit configured to send the first request to each of the at least two network elements, wherein the first request is used to request the first data that corresponds to a sub-service flow and that is in each of said network elements, and the first request includes one or more of the following information: an identifier of the service to which the flow belongs sub-service, a terminal type of the terminal corresponding to the sub-service flow, a network area in which the terminal corresponding to the sub-service flow is located, and a time window corresponding to the sub-service flow.

[0041] With reference to any of the fourth aspect or the first or second possible implementations of the fourth aspect, in the third possible implementation of the fourth aspect, the receiving unit is further configured to receive a second message sent from each of said network elements, wherein the second message includes including first data that corresponds to a sub-service flow and that is in said respective network elements; and the acquiring unit is specifically configured to obtain from the second message sent from each of said network elements the first data that corresponds to a sub-service flow and that is in said respective network elements.

[0042] With reference to any of the fourth aspect or the first to third possible embodiments of the fourth aspect, in the fourth possible implementation of the fourth aspect, the first data further includes one or more of the following information: an identifier of the network element to which the first data belongs, corresponding to the sub-service flow, a terminal identifier and a data value of at least one data type of at least one of the at least two network elements.

[0043] With reference to any of the fourth aspect or the first to fourth possible embodiments of the fourth aspect, in the fifth possible implementation of the fourth aspect, at least two network elements include a third network element. When the third network element is an application function (AF) network element, the first data received from the third network element further includes one or more of the following information: an identifier of the service to which the sub-service flow belongs, a link template parameter of the service to which sub-service stream, first interface stream bit rate data, first interface delay data, first interface packet loss rate data, first interface packet data, timestamp, usage data of the service to which the sub-service stream belongs, delay jitter buffer data , transmission control protocol (TCP) congestion window data, TCP receive window data, media content coding type data, media content coding type data coding rate data, and buffer data, the first interface being an interface between a user plane function (UPF) network element ) and data network (DN) which th corresponds to the network element AF; when the third network element is a policy control function (PCF) network element, then the first data received from the third network element further includes one or more of the following information: an identifier of the service to which the sub-service flow belongs, a session identifier to which the flow belongs sub-service, data network name (DNN) of the session to which the sub-service flow belongs, identification information of the specialized logical segment to which the sub-service flow belongs, IP filtering information, media content bandwidth requirement, traffic routing information, delay jitter buffer requirement , TCP congestion window requirement, TCP receive window requirement, media content encoding type requirement, encoding rate requirement in media content encoding type requirement, service ID validity time window, and radio access technology type; when the third network element is a session management function (SMF) network element, then the first data received from the third network element further includes one or more of the following information: sub-service flow identifier, session identifier to which the sub-service flow belongs, DNN the session to which the service flow belongs, the identity of the dedicated logical segment to which the service flow belongs, the validity time window of the service flow identifier, and the radio access technology type; when the third network element is the first UPF network element, then the first data received from the third network element further includes one or more of the following information: sub-service flow identifier, time stamp, second interface flow bit rate data, bit rate data first interface bit rate data, third interface bit rate data, second interface delay data, first interface delay data, third interface delay data, first interface packet loss ratio data, second interface packet loss ratio data, loss ratio data packet data of the third interface, packet data of the first interface, packet data of the second interface and packet data of the third interface, wherein the second interface is the interface between the first UPF network element and the radio access network (RAN) device, and the third interface is the interface between the first UPF network element and the W the first UPF NE; when the third network element is an access and mobility management (AMF) network element, then the first data received from the third network element further includes at least one of the following information: location information of the terminal corresponding to the sub-service flow, a session identifier, to which the service flow belongs, the DNN of the session to which the service flow belongs, the identity of the dedicated logical segment to which the service flow belongs, the validity time window of the session identifier to which the service flow belongs, and the type of radio access technology; when the third network element is a RAN device, the first data received from the third network element further includes one or more of the following information: location information of the terminal corresponding to the sub-service flow, sub-service flow ID, session ID to which the flow belongs sub-service, identification information of the dedicated logical segment to which the sub-service stream belongs, timestamp, fourth interface stream bit rate data, second interface stream bit rate data, second interface delay data, fourth interface delay data, received power data reference signals (RSRP), received reference signal quality (RSRQ), signal-to-interference-plus-noise ratio (SINR) data, channel quality information (CQI) data, block error rate (BLER) data, gain packet loss of the second interface, data on the coefficient packet loss of the fourth interface, packet data of the second interface, packet data of the fourth interface, radio access technology type, and dual connectivity indication information, the fourth interface being the interface between the RAN device and the terminal; or when the third network element is a terminal, the first data received from the third network element further includes one or more of the following information: location information of the terminal corresponding to the sub-service flow, a sub-service flow identifier, a session identifier to which the flow belongs sub-service, session DNN to which the sub-service flow belongs, identification information of the dedicated logical segment to which the sub-service flow belongs, fourth interface stream bit rate data, fourth interface delay data, fourth interface packet loss rate data, fourth interface packet data , timestamp, CPU usage data, memory usage data, service usage data, delay jitter buffer data, TCP congestion window data, TCP receive window data, media content encoding type data, encoding rate datamedia content coding type data, reference signal received power (RSRP) data, reference signal received quality (RSRQ) data, signal-to-interference plus noise ratio (SINR) data, channel quality information (CQI) data, error rate data in blocks (BLER) and buffer data.

[0044] With reference to any of the fourth aspect, or the first to fifth possible implementations of the fourth aspect, in the sixth possible implementation of the fourth aspect, the first identifier included in the first data that corresponds to the sub-service flow and that is in each of said network elements , is one or more of the following information: ID of the service that owns the service flow, ID of the service flow, terminal ID, session ID of the session that owns the service flow, DNN of the session that owns the service flow, identification information of the segment that owns the service flow.

[0045] With reference to any of the fourth aspect, or the first to sixth embodiments of the fourth aspect, in the seventh embodiment of the fourth aspect, the first data that corresponds to a sub-service flow and that is in each of the network elements includes one and the same first identifier.

[0046] With reference to any of the fourth aspect, or the first through seventh possible embodiments of the fourth aspect, in the eighth possible implementation of the fourth aspect, the receiving unit is further configured to receive a third request sent from the fourth network element, the third request being used to requesting allocation of the first identifier to the flow under the service; and the sender is configured to send a third response to the third network element, where the third response includes the first identifier.

[0047] With reference to any of the fourth aspect or the first to eighth embodiments of the fourth aspect, in a ninth embodiment of the fourth aspect, the sub-service flow is a quality of service flow or a service data flow.

[0048] With reference to any of the fourth aspect, or the first to ninth possible embodiments of the fourth aspect, in the tenth possible embodiment of the fourth aspect, the receiving unit is further configured to receive the first data that is sent from the operation, management, and maintenance network element, which correspond to a sub-service flow and that reside on each of the at least two network elements.

[0049] In another possible embodiment, an embodiment of the present application further provides a data processing device. The data processing device may be the first network element or a chip used in the first network element. The device includes a processor and a communication interface. The communication interface is configured to be supported by the device in performing the steps of receiving and sending a message/data on the device side in any of the first aspect or possible implementations of the first aspect. The processor is configured to support the device in performing the message/data processing step on the device side in any of the first aspect or possible implementations of the first aspect. For the specific appropriate step, reference should be made to the description in any of the first aspect or possible implementations of the first aspect. Details are again not described in this embodiment of the present application.

[0050] Optionally, the communication interface and the processor of the data processing device are connected to each other.

[0051] Optionally, the data processing device may further include a memory adapted to store code and data. The processor, communication interface and memory are connected to each other.

[0052] According to the fifth aspect, the present application proposes a device for sending data. The data sender may implement the method in the second aspect, or any possible implementation of the second aspect, and therefore can achieve benefits in 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 in implementing the method in the second aspect, or any possible implementation of the second aspect, such as a chip used in the network element. The device may implement the above method with software or hardware or a hardware implementation of the corresponding software.

[0053] In an exemplary embodiment, in one embodiment of the present application, a data sending device is provided. The data sender may be a network element or a chip used in the network element. The data sending apparatus includes: a determining unit, configured to determine that a first sub-service flow identifier has been received, the first identifier being used to identify first data that is related to a sub-service flow and resides in a network element; and a sending unit configured to send the first data to the first network element, where the first data is used by the first network element to obtain the second data, the second data includes the first data or the second data includes a part of the first data, and the first data contains the first identifier .

[0054] With reference to a fifth aspect, in a first possible implementation of the fifth aspect, the device includes a receiving unit configured to receive a first request sent from a first network element, where the first request is used to request the first data that corresponds to a sub-service flow and which are in the network element, and the first request includes one or more of the following information: an identifier of the service to which the sub-stream belongs, the terminal type of the terminal corresponding to the sub-stream, the network area corresponding to the terminal when the terminal uses the sub-stream. service, and a time window corresponding to the flow under the service.

[0055] With reference to the fifth aspect or the first possible implementation of the fifth aspect, in the second possible implementation of the fifth aspect, the first data further includes one or more of the following information: an identifier of the network element to which the first data corresponding to the sub-service flow belongs, a terminal identifier; and a data value of at least one data type of at least one of the two or more network elements.

[0056] With reference to any of the fifth aspect or the first or second possible implementation of the fifth aspect, in the third possible implementation of the fifth aspect, the data value of the data type of the network element specifically includes: determining, by means of the determining unit, the second data value based on the first data value the first device data type, where the first data value belongs to the first value space, the second data value belongs to the second value space, and the first data type is some entry in the first data.

[0057] With reference to any of the fifth aspect or the first to third possible implementations of the fifth aspect, in the fourth possible implementation of the fifth aspect, the data value of the data type of the network element further includes: determining, by means of the determining unit, a fourth data value based on the third value data of the second device data type, where the third data value belongs to the third value space, the fourth data value belongs to the fourth value space, and the second data type is some entry in the first data.

[0058] With reference to any of the fifth aspect or the first to fourth possible implementations of the fifth aspect, in the fifth possible implementation of the fifth aspect, the second value space is the same as the fourth value space.

[0059] With reference to any of the fifth aspect or the first to fifth possible implementations of the fifth aspect, in the sixth possible implementation of the fifth aspect, when the network element is an application function (AF) network element, the first data further includes one or more of the following information: identifier of the service to which the sub-service flow belongs, communication template parameter of the service to which the sub-service flow belongs, bit rate data of the first interface stream, delay data of the first interface, packet loss rate data of the first interface, packet data of the first interface, timestamp, usage data of the service to which the sub-service stream belongs, delay jitter buffer data, Transmission Control Protocol (TCP) congestion window data, TCP receive window data, media content coding type data, data coding rate data media content encoding type and buffer data, where the first in an interface is an interface between a user plane function (UPF) network element and a data network (DN) that corresponds to the AF network element; when the network element is a policy control function (PCF) network element, the first data further includes one or more of the following information: a service identifier to which the sub-service flow belongs, a session identifier to which the sub-service flow belongs, a data network name (DNN ) of the session that owns the service flow, identification information of the segment that owns the service flow, IP filtering information, media content bandwidth requirement, traffic routing information, delay jitter buffer requirement, TCP congestion window requirement, window requirement TCP reception, media content coding type requirement, coding rate requirement in media content coding type requirement, service ID validity time window, and radio access technology type; when the network element is a session management function (SMF) network element, the first data further includes one or more of the following information: a sub-service flow identifier, a session identifier to which the sub-service flow belongs, a session DNN to which the sub-service flow belongs, identification information of the dedicated logical segment to which the flow sub-service belongs, the time window of validity of the flow sub-service identifier, and the type of radio access technology; when the network element is the first network element of the UPF, the first data further includes one or more of the following information: sub-service flow identifier, timestamp, second interface flow bit rate data, first interface stream bit rate data, bit rate data 3rd interface speed data, 2nd interface delay data, 1st interface delay data, 3rd interface delay data, 1st interface packet loss rate data, 2nd interface packet loss rate data, 3rd interface packet loss rate data, 1st interface packet loss data , packet data of a second interface and packet data of a third interface, where the second interface is an interface between the first UPF network element and a radio access network (RAN) device, and the third interface is the interface between the first UPF network element and the second UPF network element; when the network element is an Access and Mobility Management (AMF) network element, then the first data further includes at least one of the following information: location information of the terminal corresponding to the sub-service flow, session identifier to which the sub-service flow belongs, session DNN , to which the service flow belongs, the identity of the dedicated logical segment to which the service flow belongs, the validity time window, the session identifier to which the service flow belongs, and the type of radio access technology; when the network element is a RAN device, the first data further includes one or more of the following information: location information of the terminal corresponding to the sub-service flow, the ID of the sub-service flow, the identifier of the session to which the sub-service flow belongs, the identification information of the dedicated logical segment , which owns the sub-service stream, timestamp, fourth interface stream bit rate data, second interface stream bit rate data, second interface delay data, fourth interface delay data, received reference signal power (RSRP) data, received reference signal quality (RSRQ), signal-to-interference-plus-noise ratio (SINR) data, channel quality information (CQI) data, block error rate (BLER) data, second interface packet loss ratio data, fourth interface packet loss, packet data e of the second interface, the fourth interface packet data, the radio access technology type, and the dual connectivity indication information, where the fourth interface is the interface between the RAN device and the terminal; or when the network element is a terminal, the first data further includes one or more of the following information: location information of the terminal that uses the sub-stream flow, a sub-stream ID, a session ID to which the sub-stream belongs, a session DNN to which sub-service stream belongs, identity of the dedicated logical segment to which the sub-service stream belongs, fourth interface stream bit rate data, fourth interface delay data, fourth interface packet loss rate data, fourth interface packet data, timestamp, usage data processing unit (CPU), memory usage data, service usage data, delay jitter buffer data, Transmission Control Protocol (TCP) congestion window data, TCP receive window data, media content encoding type data, data type encoding rate data kodi Received Reference Power (RSRP) Data, Received Reference Quality (RSRQ) Data, Signal to Interference Plus Noise Ratio (SINR) Data, Channel Quality Information (CQI) Data, Block Error Rate Data (BLER) and buffer data.

[0060] With reference to any of the fifth aspect or the first to sixth possible implementations of the fifth aspect, in the seventh possible implementation of the fifth aspect, when the device is a network policy control element, then the receiving unit is further configured to receive a second request sent from application function (AF) network element, where the second request is used to request the establishment of a sub-service flow, and the second request includes one or more of the following information: identifier of the service to which the sub-service flow belongs, IP filtering information, bandwidth requirement media content, traffic routing information, delay jitter buffer requirement, TCP congestion window requirement, TCP receive window requirement, media content encoding type requirement, encoding rate requirement in media content encoding type requirement, buffer requirement, and requirement for at least at least one data type.

[0061] With reference to any of the fifth aspect, or the first through seventh possible implementations of the fifth aspect, in the eighth possible implementation of the fifth aspect, the first identifier is one or more of the following information: the identifier of the service to which the stream under the service belongs, the identifier of the stream under service, terminal ID, session ID that owns the sub-service flow, DNN of the session that owns the sub-service flow, identification information of the dedicated logical segment that owns the sub-service flow.

[0062] With reference to any of the fifth aspect or the first to eighth embodiments of the fifth aspect, in the ninth embodiment of the fifth aspect, the sub-service flow is a quality of service flow or a service data flow.

[0063] With reference to any of the fifth aspect, or the first to the ninth possible implementations of the fifth aspect, in the tenth possible implementation of the fifth aspect, the data value of the data type of the network element further includes: determining by the determination block of the sixth data value based on the fifth value data of a third device data type, where the fifth data value belongs to the fifth value space, the sixth data value belongs to the sixth value space, and the third data type is some entry in the first data.

[0064] With reference to any of the fifth aspect or the first to the tenth possible implementations of the fifth aspect, in the eleventh possible implementation of the fifth aspect, every two of the second value space, the fourth value space and the sixth value space are the same.

[0065] With reference to any of the fifth aspect, or the first to the eleventh possible implementations of the fifth aspect, in the twelfth possible implementation of the fifth aspect, the sender is configured to send the first data to the operation, administration, and maintenance network element.

[0066] In another possible embodiment, an embodiment of the present application further provides a data sender. The data sender may be a network element or a chip used in the network element. The data sending device includes a processor and a communication interface. The communication interface is configured to support the data sending device in performing the steps of receiving and sending a message/data on the side of the data sending device in any of the second aspect or possible implementations of the second aspect. The processor is configured to: support the data sender in performing the message/data processing step on the side of the data sender in any of the second aspect or possible implementations of the second aspect. For information about the particular step involved, refer to the description in any of the second aspect or possible implementations of the second aspect. Details are again not described in this embodiment of the present application.

[0067] Optionally, the communication interface and the processor of the data sending device are connected to each other.

[0068] Optionally, the data sender may further include a memory adapted to store code and data. The processor, communication interface and memory are connected to each other.

[0069] According to the sixth aspect, the present application proposes a device for sending data. The data sender may implement the method in the third aspect, or any possible embodiment of the third aspect, and therefore may achieve benefits in 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 in implementing the method in the third aspect, or any possible implementation of the third aspect, such as a chip used in the network element. The device may implement the above method with software or hardware or a hardware implementation of the corresponding software.

[0070] In an exemplary embodiment, in one embodiment of the present application, a data sending device is provided. The data sender is a network element or a chip used in a network element. The device includes: a sender configured to send to the first network element a first message used to instruct the first network element to receive from at least two network elements the first data corresponding to a sub-service flow, and the first message includes one or more of the following information: ID of the service to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, the area of the network in which the terminal corresponding to the service flow is located, and the time window corresponding to the service flow.

[0071] In another possible embodiment, an embodiment of the present application further provides a data sending device. The data sender may be a network element or a chip used in the network element. The data sending device includes a communication interface. The communication interface is configured to support the data sending device in performing the steps of receiving and sending a message/data on the side of the data sending device in any of the third aspect or possible implementations of the third aspect.

[0072] Optionally, the device further includes a processor configured to: support the data sender in performing a message/data processing step on the data sender side in any of the third aspect or possible embodiments of the third aspect. Refer to the description in any of the third aspect or possible embodiments of the third aspect for details of the particular step involved. Details are again not described in this embodiment of the present application.

[0073] Optionally, the communication interface and the processor of the sending device are connected to each other.

[0074] Optionally, the data sender may further include a memory adapted to store code and data. The processor, communication interface and memory are connected to each other.

[0075] According to a seventh aspect, a computer-readable storage medium is provided herein. The computer-readable storage medium stores instructions, and when the instructions are executed on a computer, one or more of the first aspect and possible implementations of the first aspect are caused to be executed by the computer.

[0076] According to an eighth aspect, a computer-readable storage medium is provided herein. The computer-readable storage medium stores instructions, and when the instructions are executed on a computer, one or more of the second aspect and possible implementations of the second aspect are caused to be executed by the computer.

[0077] According to a ninth aspect, a computer-readable storage medium is provided herein. The computer-readable storage medium stores the instructions, and when the instructions are executed on the computer, the computer is caused to execute one or more of the third aspect and the possible implementations of the fifth aspect.

[0078] According to a tenth aspect, the present application provides a computer program product including instructions. When a computer program product is executed on a computer, one or more of the first aspect and possible embodiments of the first aspect are provided for the computer to execute.

[0079] According to an eleventh aspect, the present application provides a computer program product including instructions. When a computer program product is executed on a computer, one or more of the second aspect and possible embodiments of the second aspect are provided for the computer to execute.

[0080] According to a twelfth aspect, the present application provides a computer program product including instructions. When a computer program product is executed on a computer, one or more of the third aspect and possible embodiments of the third aspect are provided for the computer to execute.

[0081] According to a thirteenth aspect, the present application provides a microcircuit, wherein the microcircuit includes a processor and an interface circuit, the interface circuit is connected to the processor, and the processor is configured to execute a computer program or instructions to implement one or more of the first aspect and options implementations of the first aspect.

[0082] According to a fourteenth aspect, the present application provides a chip, wherein the chip includes a processor and an interface circuit, the interface circuit is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement one or more of the second aspect and options implementation of the second aspect.

[0083] According to a fifteenth aspect, the present application provides a chip, wherein the chip includes a processor and an interface circuit, the interface circuit is connected to the processor, and the processor is configured to execute a computer program or instructions to implement one or more of the third aspect and options implementation of the third aspect.

[0084] Optionally, the aforementioned chip in the present application may further include at least one memory. At least one memory stores instructions or a computer program.

[0085] According to a sixteenth aspect, in one embodiment of the present application, a data processing system is provided, wherein the data processing system includes the data processing device described in the fourth aspect and possible embodiments of the fourth aspect, and at least two data sending devices described in the fifth aspect and possible implementations of the fifth aspect.

[0086] Optionally, the data processing system further includes a data sender described in the sixth aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

[0087] FIG. 1 is a diagram of a voice MOS curve in the prior art;

[0088] FIG. 2 is a schematic block diagram of a data processing system according to one embodiment of the present application;

[0089] Fig. 3 is a schematic diagram of a 5G network according to one embodiment of the present application;

[0090] Figures 4-10 are schematic flowcharts of a data processing method according to embodiments of the present application;

[0091] Figures 11-13 are schematic block diagrams of a data processing apparatus according to embodiments of the present application;

[0092] FIGS. 14-19 are schematic structural diagrams of a data sender according to embodiments of the present application; and

[0093] FIG. 20 is a schematic block diagram of a chip according to one embodiment of the present application.

Description of Embodiments

[0094] In order to clearly describe the technical solutions in the embodiments of the present application, the embodiments of the present application use terms such as "first" and "second" to distinguish between the same elements or similar elements that have basically the same function and use. For example, the first network element and the second network element are merely intended to distinguish between different network elements, and are not intended to limit their sequence. One skilled in the art can understand that terms such as "first" and "second" do not limit the number or sequence of execution, and that terms such as "first" and "second" do not indicate a particular difference.

[0095] It should be noted that in this application, the word "for example" is used to provide an example, illustration, or description. Any embodiment or design scheme described as "for example" in this application should not be explained as preferable or having more advantages than another embodiment or design scheme. Exactly, the use of the word "example" or the like is intended to represent a relative concept in a particular way.

[0096] The network architecture and service scenario described in the embodiments of the present application are intended to more clearly describe the technical solutions in the embodiments of the present application and do not represent limitations of the technical solutions presented in the embodiments of the present application. One skilled in the art may be aware that: With the evolution of network architecture and the advent of new service scenarios, the technical solutions presented in the embodiments of the present application are also applicable to similar technical problems.

[0097] As used herein, "at least one" refers to one or more, and "multiple" refers to two or more. The term "and/or" describes a correlation relationship to describe correlated objects and means that there may be three relationships. For example, A and/or B may represent the following cases: Only A exists, both A and B exist, and only B exists, where A and B can be singular or plural. The "/" symbol usually indicates an "or" relationship between correlated objects. "At least one of the following items (parts)" or a similar expression indicates any combination of these items, including any combination of a single item (part) or multiple items (parts). For example, at least one of a, b, or c may represent a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c may be singular or plural.

[0098] The technical solutions in the embodiments of the present application can be applied to various communication systems for data processing, for example, code division multiple access (CDMA), multiple access with time division (time division multiple access, TDMA), multiple access with frequency division (frequency division multiple access, FDMA), multiple access with orthogonal frequency division (orthogonal frequency-division multiple access, OFDMA), multiple access with one carrier with frequency division (single carrier FDMA, SC-FDMA) and others systems. The terms "system" and "network" can be used interchangeably. A CDMA system may implement wireless technologies such as universal terrestrial radio access (UTRA) and CDMA2000. UTRA may include wideband CDMA (wideband CDMA, WCDMA) technology and other varieties of CDMA technology. CDMA2000 may cover the interim standard (IS) 2000 (IS-2000), the IS-95 standard, and the IS-856 standard. A TDMA system may implement a radio technology such as global system for mobile communications (GSM). The OFDMA system can implement radio technologies such as advanced universal terrestrial radio access (evolved UTRA, E-UTRA), ultra mobile broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and flash OFDMA. UTRA and E-UTRA are enhanced versions of UMTS. A new version of UMTS, namely E-UTRA, is used in the 3GPP (long term evolution, LTE) standard and various versions advanced based on LTE. The 5G communication system and new radio communication (new radio, NR) are the next generation communication systems that are being studied. In addition, communication systems can be further applied to future-oriented communication technology and applicable to the technical solutions provided in the embodiments of the present application.

[0100] The system architecture and service scenario described in the embodiments of the present application are intended to more clearly describe the technical solutions in the embodiments of the present application and do not represent limitations of the technical solutions presented in the embodiments of the present application. One of ordinary skill in the art can understand that: With the evolution of network architecture and the advent of new service scenarios, the technical solutions presented in the embodiments of the present application are also applicable to similar technical problems. In embodiments of the present application, that the provided method is applied to an NR system or a 5G network is used as an example for description.

[0101] FIG. 2 is a schematic diagram of an architecture of a data processing system in which a data processing method according to embodiments of the present application is applied. As shown in FIG. 2, the data processing system includes a first network element 101 and at least two network elements connected to the first network element 101 (only two network elements are shown in FIG. 2, for example, a network element 102 and a network element 103. It can be appreciated that there may be more than two network elements in a real process).

[0102] It can be understood that at least two network elements in the embodiments of the present application can be connected to each other. For example, network element 102 and network element 103 in FIG. 2 are connected to each other.

[0103] It can be understood that in at least two network elements in the embodiments of the present application, one network element is configured to provide the first network element with service data that is in the network element and corresponds to a sub-service flow, and the other network element in at least at least two network elements is configured to provide the first network element with network data related to the sub-service flow and located on another network element.

[0104] For example, the service data in the present application may be: parameter data such as service identifier to which the sub-service stream belongs, bandwidth, delay, packet loss ratio, delay jitter buffer, TCP congestion window, TCP receive window, coding type media content and media content encoding rate.

[0105] It can be understood that in embodiments of the present application, the parameter data may be the size, value, or requirement of the parameter. For example, the CQI data may refer to the size or value of the CQI. In embodiments of the present invention, the parameter data, size, value, or requirement indicates the value of the data collected or received by the corresponding network element for the parameter. For all related content below, please refer to the description here. Details are not described further.

[0106] The network data in this application can be any one of the following parameters: parameter data such as bandwidth, delay, packet loss ratio, received power of the reference signals (reference signal receiving power, RSRP), received quality of the reference signals (reference signal receiving quality (RSRQ), block error rate (BLER) and channel quality indication (CQI), specialized logical segment (slice) identifier information, and data network name (DNN).

[0107] The first network element 101 and at least two network elements may be connected directly or may be connected indirectly using another network element. In embodiments of the present application, this is not limited.

[0108] Based on this, the network element that resides in at least two network elements and that is configured to provide network data to the first network element may be a terminal or a network element that belongs to a core network or an access network.

[0109] For example, the network element configured to provide network data 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.

[0110] For example, in a fourth generation network (4th generation, 4G), a user plane network element may be, for example, a public data network gateway (PDN GW, (PGW for short)) or a serving network element (serving gateway, SGW) and the control plane network element may be a mobility management entity (MME).

[0111] In embodiments of the present invention, terminals may be widely distributed in a wireless network. Each terminal may be fixed or mobile.

[0112] If the above data processing system is applied to a 5G network, then the network element or node corresponding to the first network element 101 may be a network data analytics function (NWDAF) network element as shown in FIG. Network elements or nodes (subjects) corresponding to at least two network elements can be any two different network elements in the following set of network elements: application function (AF) network element (also called service function network element), network element policy control function (PCF), session management function (SMF) network element, user plane function (UPF) network element, access and mobility management function network element , AMF), a radio access network (RAN) device, and a terminal.

[0113] A RAN device is a network element belonging to a radio access network. The PCF network element, the SMF network element, the AMF network element, and the UPF network element are network elements belonging to the core network.

[0114] The network element 102 in at least two network elements provides the first network element with service data that corresponds to the sub-service flow and which is in the network element 102, and the other network element 103 provides the network element of the sub-service flow in the network element 103. For example , the network element 102 may be an AF network element and the network element 103 may be an AMF network element. Alternatively, the network element 102 may be an AF network element and the network element 103 may be a UPF network element.

[0115] Further, as shown in FIG. 3, the 5G network may further include an access device (e.g., an access network (AN)), a network element of a unified data management (UDM), a network element Authentication server function (AUSF), Network slice selection function (NSSF) network element, Network exposure function (NEF) network element, Network repository function (NEF) network element , NRF), etc. This is not specifically limited in the embodiments of the present application.

[0116] As shown in FIG. 3, the operation, administration, and maintenance, OAM (O&M) network element may cover all network elements in the access network and the core network, and may also collect data from all network elements in the access network and core network. In addition, the OAM network element in the embodiments of the present application can also collect network data that is in the sub-service flow layer.

[0117] The terminal communicates with the AMF network element through the N1 interface (abbreviated as N1). The AMF node communicates with the SMF NE through the N11 interface (N11 for short). The SMF network element communicates with one or more UPF network elements via an N4 interface (N4 for short). Any two of one or more UPF NEs communicate with each other via an N9 interface (N9 for short). The UPF network element communicates through an N6 interface (N6 for short) with a data network (DN) managed and administered by the AF network element. The terminal accesses the network with an access device (eg, a RAN device), and the access device communicates with the AMF network element via an N2 interface (abbreviated as N2). The SMF network element communicates with the PCF network element via the N7 interface (N7 for short) and the PCF network element communicates with the AF network element via the N5 interface. The access device communicates with the UPF NE via the N3 interface (N3 for short). Any two AMF NEs communicate with each other via the N14 interface (N14 for short). The SMF network element communicates with the UDM network element via the N10 interface (N10 for short). The AMF network element communicates with the AUSF via the N12 interface (N12 for short). The AUSF network element communicates with the UDM network element via the N13 interface (N13 for short). The AMF network element communicates with the UDM network element via the N8 interface (N8 for short).

[0118] It should be noted that both the third-party AF network element and the operator AF in Fig. 3 are AF network elements, and the differences are that the third-party AF network element (for example, WeChat service server or Alipay payment service server) is controlled and is not administered by the operator, but the operator network element AF (e.g., proxy-call session control function (P-CSCF) network element in the IP multimedia system) is controlled and administered by the operator, and the NEF network element shall be used when a third party AF network element interacts with the NWDAF network element.

[0119] The PCF network element is configured to forward signaling or data of the AF network element to the SMF network element.

[0120] It should be noted that the names of the interfaces between network elements in FIG. 3 are merely examples, and the interfaces may have other names in a particular implementation. This is not specifically limited in the embodiments of the present application.

[0121] It should be noted that an access device, an AF network element, an AMF network element, an SMF network element, an AUSF network element, a UDM network element, a UPF network element, a PCF network element, and the like. 3 are simply titles, and these titles do not limit the devices. In the 5G network and other future network, the network elements or nodes 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 may have other names. This is not specifically limited in the embodiments of the present application. For example, the UDM network element may be replaced by a home subscriber server (HSS), a user subscription database (USD), a database node, and the like. A description is provided here, and details are again not described below.

[0122] It should be noted that in the present application, a session (session) is a communication line that is established by the SMF network element and connects the terminal to the data network. The communication link includes a terminal, an access device, a UPF network element, and a data network corresponding to the 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 packet. In addition, communication between the AMF network element, the SMF network element, and the PCF network element, which belong to the control plane, is required to establish a session.

[0123] It should be noted that in the present application, a sub-service flow includes a QoS flow or a service data flow. A QoS flow or service data flow is a link that refers to a service in a PDU session and connects a terminal and a data network. The communication link includes a terminal, an access device, a UPF network element, and a data network corresponding to the UPF network element. In addition, the AMF network element, the SMF network element, and the PCF network element, which belong to the control plane, must cooperate to establish a sub-service flow.

[0124] Alternatively, a terminal in this application may also be referred to as a terminal device, user equipment (user equipment, UE), access terminal, user equipment, subscriber station, mobile station, mobile console, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. A terminal device may be a station (STA) in a wireless local area network (WLAN) and may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless subscriber line station (wireless local loop (WLL), personal digital assistant (PDA), handheld device with wireless capability, computing device, other data processing device connected to a wireless modem, vehicle-mounted device, wearable device, and next generation communication system , for example, a terminal device in a fifth-generation network (5G) or a terminal device in a future developed public land mobile network (PLMN).

[0125] In one exemplary embodiment of the present invention, the terminal may alternatively be a wearable device. A wearable device may also be referred to as a wearable smart device, and is a general term for wearable devices such as glasses, gloves, watches, clothing, and shoes that are developed by applying wearable technology to smart everyday clothing designs. A wearable device is a portable device that can be worn directly on the body or integrated into the wearer's clothing or accessory. A wearable device is not just a hardware device, it further realizes powerful functions through software support, data sharing, and cloud interaction. Generalized wearable smart devices include full-featured and large-sized devices that can realize full or partial functions independently of smartphones, such as smart watches or smart glasses, as well as devices that focus on only one type of application function and need to work with other devices, such as smart phones, such as various smart bracelets or smart jewelry to track physical signs.

[0126] Optionally, an access device in embodiments of the present application is a device that accesses a core network, such as a base station, a broadband network gateway (BNG), an aggregation switch, or a non-design standard access device. 3rd generation partnership project (3GPP). The base station may include a macro base station, a micro base station (also referred to as a small cell), a relay station, an access point, and the like. in different forms.

[0127] Optionally, the AMF network element in embodiments of the present application may be additionally responsible for functions such as registration management, mobility management, and lawful interception. This is not specifically limited in the embodiments of the present application.

[0128] Optionally, the SMF network element in the embodiments of the present application is configured to perform session management, including: session establishment, session change and session release, assignment of Internet Protocol (IP) addresses and terminal management, selection and control of the UPF host, lawful interception, and other session-related control functions.

[0129] Optionally, in addition to the user plane function network element function shown in FIG. 3, the UPF network element in the embodiments of the present application may further implement the serving gateway (SGW) user plane function and the packet data network gateway function. (packet data network gateway, PGW). Furthermore, the UPF network element may alternatively be a software defined network (SDN) switch. This is not specifically limited in the embodiments of the present application.

[0130] Optionally, the AUSF network element in embodiments of the present application is configured to authenticate a terminal based on the terminal's subscription data.

[0131] Optionally, the UDM network element in embodiments of the present application is configured to store user subscription data. In addition, the UDM network element further includes functions such as authentication, user ID processing, and subscription management. This is not specifically limited in the embodiments of the present application.

[0132] Optionally, the PCF network element in embodiments of the present application provides a policy rule and implements policy-related functions such as support for a unified policy architecture to control network behavior.

[0133] Optionally, the user plane function network element of FIG. 3 may be implemented by a physical device, or may be implemented jointly by multiple physical devices, or may be a logical functional unit in a physical device. This is not specifically limited in the embodiments of the present application.

[0134] The SMF network element is configured to reallocate the UPF network element to the terminal based on the location information of the terminal, the characteristics of the data sent from the terminal, or the location information between the UPF network element and the terminal, or the quality of service of the UPF network element to re-establish a session between the terminal and the newly allocated UPF network element so that the user plane can be optimized by improving the quality of the re-established session.

[0135] The access device is configured to provide a data service to the terminal, for example, to receive data sent from the terminal or to send data to the terminal. The access device may be a base station during actual use. In embodiments of the present invention, a base station (BS) may be a device that communicates with a user equipment (user equipment, UE) or another communication station such as a relay station, and the base station may provide communication coverage in a certain physical areas.

[0136] The PCF network element is configured to: receive overhead information from the AF network element, and generate and distribute, based on the overhead information, a QoS parameter corresponding to a sub-service flow.

[0137] The AF network element is configured to: start the NWDAF network element to collect the first data that corresponds to the sub-service flow and which is in different network elements, and send to the NWDAF network element the first data that corresponds to the sub-service flow and which is in NE AF.

[0138] DN is an external network providing a data service.

[0139] A sub-service flow in embodiments of the present application refers to a service data packet transmission channel between a terminal and a data network, and is identified using a 5 IP tuple.

[0140] The NWDAF network element is configured to: collect time-varying network data, service data or terminal data and corresponding service usage data, and obtain, by parsing, at least one set of QoS parameters under different network conditions (corresponding to network data) , service conditions (corresponding to the service data), or terminal conditions (corresponding to the terminal data) of the service. For example, the NWDAF network element may collect air interface bit rate data (data value, size, requirement, etc.) of the service at the base station and obtain the GFBR through parsing. Alternatively, the NWDAF network element may collect the delay data (data value, size, requirement, etc.) of the service between the base station and the UPF and obtain the PDB through analysis. Alternatively, NWDAF may collect TCP Congestion Window (CWND) data (data value, size, request, etc.) or TCP receiver window (RWND) data (data value, size, request). etc.) at the AF NE or terminal, and obtain the recommended CWND or the recommended RWND through analysis. Alternatively, the NWDAF may collect data on the delay jitter buffer at the AF network element or terminal and obtain the recommended delay jitter buffer through analysis.

[0141] The service requires at least one set of QoS parameters. This is because, for example, considering service usage requirements (eg, service MOS greater than 3.0) in vertical industries, packet delay data conflicts with packet loss rate data.

[0142] In example 1, within the weak coverage, the RAN may transmit the data packet multiple times to ensure the packet loss rate. However, in this case, the packet delay increases, and the bit rate of the stream can be additionally increased.

[0143] In Example 2, within a strong RAN coverage, it is not required to transmit a data packet multiple times. In this case, both the packet loss ratio and the packet delay can be ensured, and furthermore, the bit rate can be reduced.

[0144] Therefore, there are one or more sets of QoS parameters for a service.

[0145] Specifically, the NWDAF network element uses a big data technique to obtain at least one set of service QoS parameters based on time-varying network data, service data, or terminal data and corresponding service usage data. The process looks like this:

[0146] Step 1: The NWDAF network element first collects data separately from network elements such as the AF network element, RAN device, UPF network element, UE, AMF network element, SMF network element, and PCF network element, and then matches the data across all network elements using information such as service ID, sub service flow ID, terminal ID, session ID to which the sub service flow belongs, mapping ID for each network element, and time to obtain complete training data. Training data includes:

(1) service usage data that comes from the AF network element; and

(2) other data about the parameters of changes over time that affect the data on the use of the service, including:

a. TCP congestion window data, TCP receive window data, delay jitter buffer data, media content coding type data and coding rate data, buffer data and data of at least one type of data that come from the AF network element;

b. a bit rate data stream, packet loss rate data, delay data, radio link quality data, and data of at least one type of data that come from the RAN network element;

c. bit rate data, packet loss rate data, delay data, and data of at least one type of data that come from the UPF network element;

d. bit rate data, packet loss rate data, delay data, TCP congestion window data, TCP receive window data, delay jitter buffer data, coding type data and media content coding rate data, buffer data, usage CPU, memory usage, and data of at least one type of data from the UE. The training data is not limited to the above data.

[0147] Step 2: Based on the Linear Regression method, the NWDAF network element obtains a relational model, namely a service usage model, between service usage and other time variation parameter data that affects service usage data, and the network element The NWDAF may schedule one or more sets of service QoS parameters based on the service usage model.

[0148] In addition, based on the received training data, the NWDAF may be further configured to select a UPF routing path, diagnose user plane or control plane failures, and the like.

[0149] As shown in Table 1 and Table 2, Table 1, Table 2 and Table 3 show information related to service data and network data that are provided in embodiments of the present application.

Table 1 Service data

Information NE name Description 1 Description 2 IDAF AMF Network Element AF ID Identifies the service server Mapping ID Mapping ID Used to map network data to service data Application ID Service ID Identifies the service, i.e. service ID timestamp timestamp Fix time used to record the time at which the third-party AF calculates service usage information, and also used to match service data with network data UE-ID Terminal ID Identifies the terminal and is used to match the first data that corresponds to a sub-service flow and resides in different network elements. Link Template Options Link Template Parameter A communication template for a service, which is basically a set of parameters for an ultra-reliable and low-latency communication (URLLC) service, such as a periodic interactive service (for example, under the Narrowband Internet of Things accounting service). of things, NB-IoT), once a month). TCP congestion window size TCP congestion window size TCP congestion window size TCP Receiver Window Size TCP receive window size TCP receive window size codec mode/application codec/media content Encoding rate/encoding type of media content/service Encoding rate or encoding type of media content/service media/application bandwidth Bandwidth of media content/services Bandwidth of media content/services Service use Service use Service usage data used to determine network QoS parameters, UPF selection, etc. Feature Z1 Z1 data type in AF network element and affecting service usage A specific service data type corresponding to the application ID in the AF network element, where the data type is invisible or visible to the AF network element. … … … characteristic ZZ ZZ data type in AF network element and affecting service usage A specific service data type corresponding to the application ID in the AF, where the data type is invisible or visible to the AF.

[0150] For the UE ID, in the embodiments of the present application, refer to the terminal ID. Details are not described here again.

Table 2 Network data

Information NE name Description 1 Description 2 (example) AF ID PCF NE AF ID Identifies the service server Application ID PCF NE Service ID Identifies the service, i.e. service ID UE-ID PCF NE/AMF NE/SMF NE Terminal ID Identifies the terminal and is used to match the first data that corresponds to a sub-service flow and resides in different network elements. QoS flow identifier (QFI) SMF NE/UPF NE/RAN device Thread ID Identifies the service data flow or QoS flow Session ID of the protocol data unit (PDU) SMF NE/UPF NE/RAN device PDU session ID Identifies the session that owns the flow under the service Single network slice selection assistance information (S-NSSAI) RAN device/AMF NE/SMF NE/PCF NE Specialized logical segment type identifier Used to identify the type of specialized logical segment Instance ID of a network specialized logical segment (network slice instance, NSI) RAN device/AMF NE/SMF NE/PCF NE Specialized logical segment instance ID Used to identify an instance of a specialized logical segment Mapping ID UE/RAN Device/AMF NE/SMF NE/UPF NE/PCF NE/AF NE Mapping ID, i.e. the first ID in the following embodiments A special mapping identifier used to map the first data that corresponds to a sub-service flow and that is in different network elements timestamp Timestamps corresponding to all network elements when network elements report data timestamp Records the point in time at which each indicator is recorded in the corresponding network element and sets the parameter (quality of service, QoS): Average window size RAN ID / cell ID RAN device/AMF NE Base Station ID or Cell ID Identifies the base station or cell that is serving a sub-service flow. RAN Tunnel Information RAN device Base Station Tunnel Information Identifies the tunnel through which the sub-service flow connects to the UPF network element at the RAN device. Packet delay Uu uplink (uplink, UL) or downlink (downink, DL) RAN device Uplink/downlink interface packet delay Uu Specifies the QoS setting, such as Uu-PDB Packet Delay N3 UL or DL RAN device/UPF NE Uplink/downlink N3 interface packet delay Sets the QoS setting: N3-PDB Uu-FBR UL or DL RAN device Uplink/downlink interface stream bandwidth Uu Sets the QoS parameter: Uu-GFBR (Guaranteed Bit Rate) N3-FBR UL or DL RAN device/UPF NE Uplink/downlink N3 interface stream bandwidth Specifies the QoS setting, such as N3-GFBR PLR UL or DL RAN device Uplink/downlink packet loss ratio Specifies a QoS setting such as Max PLR (Maximum Packet Loss Ratio) PER UL or DL RAN device Uplink/downlink packet error rate Sets the QoS parameter: PER (Packet Error Rate) data packet size RAN device Packet size Sets the QoS parameter: Maximum data packet size RSRP/RSRQ/SINR/CQI RAN network element Four types of radio channel quality, such as CQI, RSRP, RSRQ and BLER. RAN Device Side Radio Link Quality Used to Specify QoS Parameter: HO Threshold/Max PLR RAT type RAN network element Type of radio access technology, such as LTE Identifies the radio access technology type of the terminal. Possibility of double connection RAN network element Dual Connectivity Indication Information Dual Connectivity Indication Information characteristic X1 RAN network element X1 data type in RAN and affects service usage The specific data type on the RAN device, where the data type is invisible or visible to NWDAF, is used to indicate the QoS parameter visible to the RAN device … … … feature XX RAN network element XX data type in RAN and affects service usage The specific data type on the RAN device, where the data type is invisible or visible to the NWDAF NE, is used to indicate the QoS parameter visible to the RAN device ID UPF Network element UPF UPF ID Identifies the UPF NE that serves the service data flow used to select the UPF NE/traffic routing. UPF Tunnel Information Network element UPF UPF Tunnel ID Identifies the tunnel through which a sub-service flow connects to a RAN device on a UPF NE, used for UPF NE selection/traffic routing Packet Delay N6/ Packet Delay N9 UL or DL Network element UPF Uplink or downlink N9/N6 interface packet delay Specifies the QoS setting: N9-PDB or N6-PDB N9-FBR/N6-FBR UL or DL Network element UPF Uplink or downlink N9/N6 interface packet bandwidth Specifies the QoS setting: N9-GFBR or N6-PDB UL or DL package size Network element UPF Uplink or downlink packet size passing through the UPF NE The traffic pattern of the UE is obtained to analyze whether the UE is under security attack. characteristic Y1 Network element UPF Y1 data type in UPF NE affecting service usage The specific data type in the UPF NE, where the data type is invisible or visible to the NWDAF NE, is used to indicate the QoS parameter visible to the UPF NE … … … characteristic YY Network element UPF YY data type in UPF NE affecting service usage The specific data type in the UPF NE, where the data type is invisible or visible to the NWDAF NE, is used to indicate the QoS parameter visible to the UPF NE Session ID N4 UPF NE/SMF NE Session ID N4 Identifies a signaling channel between an SMF NE and a UPF NE ID SMF NE SMF SMF ID Identifies the SMF NE information about the topology of an instance of a network specialized logical segment NE SMF Information about the topology of a dedicated logical segment instance Used to select UPF NE/traffic routing RAT type NE SMF Type of radio access technology, such as LTE Identifies the radio access technology type of the terminal characteristic P1 NE SMF P1 data type in SMF NE affecting service usage The specific data type in the SMF NE, where the data type is not visible or visible to the NWDAF NE, is used to set the QoS setting that is visible to the SMF NE … … … characteristic PP NE SMF PP Data Type in SMF NE and Impact on Service Usage The specific data type in the SMF NE, where the data type is not visible or visible to the NWDAF NE, is used to set the QoS setting that is visible to the SMF NE ID AMF AMF Network Element AMF ID Identifies an AMF NE Network Area (TA List/TA/RA/RA List) AMF Network Element Network Region (UE Tracking Region List, Tracking Region, Routing Region List, and Routing Region) Identifies the network area of the UE RAT type AMF Network Element Type of radio access technology, such as LTE Identifies the radio access technology type of the terminal characteristic Q1 AMF Network Element Q1 data type in AMF NE affecting service usage The specific data type in the AMF NE where the data type is invisible or visible to the NWDAF is used to set the QoS parameter visible to the AMF NE … … … characteristic QQ AMF Network Element QQ data type in AMF NE and impact on service usage The specific data type in the AMF NE, where the data type is invisible or visible to the NWDAF NE, is used to indicate the QoS setting that is visible to the AMF NE PCF ID PCF NE PCF ID Identifies the PCF NE IP Filter Information PCF NE Information about IP filtering Identifies the service data flow (SDF) from the AF network element media/application bandwidth PCF NE Media content/service bandwidth requirement Service bandwidth requirement from AF NE usage threshold PCF NE Uses a threshold requirement, such as volume/time threshold Uses a threshold requirement to identify the service from the AF NE traffic routing information PCF NE Requiring traffic routing information, such as a DNAI list UPF NE selection requirement information from AF NE RAT type PCF NE Type of radio access technology, such as LTE Identifies the radio access technology type of the terminal characteristic M1 PCF NE M1 data type in PCF NE affecting service usage A specific data type in the PCF NE, where the data type is not visible or visible to the NWDAF NE, used to indicate the QoS setting that is visible to the PCF NE … … … characteristic MM PCF NE M1 data type in PCF NE affecting service usage The specific data type in the PCF NE, where the data type is not visible or visible to the NWDAF NE, is used to indicate the QoS setting that is visible to the PCF NE

Table 3 Terminal data

Information NE Name Description 1 Description 2 Mapping ID Mapping ID Special identifier used to match network data with service data Application ID Service ID Identifies the service, i.e. service identifier timestamp timestamp Fix time used to record the time at which third-party AF calculates service usage information and is also used to match service data with network data UE ID Terminal ID Identifies the terminal and is used for the first data that corresponds to a sub-service flow and resides in different network elements. TCP congestion window size TCP congestion window size TCP congestion window size TCP Receiver Window Size TCP receive window size TCP receive window size codec mode / application codec / media content Encoding rate/encoding type of media content/service Encoding rate or encoding type of media content/service Bandwidth of media content/services Bandwidth of media content/services Bandwidth of media content/services Service use Service use Service usage data used to determine network QoS parameters, select UPF NEs, etc. RSRP/RSRQ/SINR/CQI Four types of radio channel quality, such as CQI, RSRP, RSRQ and BLER. The quality of the radio link on the side of the network element RAN, used to indicate the QoS parameter: Threshold HO/Max PLR CPU load CPU usage CPU usage Memory loading Memory usage Memory usage Delay jitter buffer size Delay jitter buffer size Delay jitter buffer size Buffer size Buffer size Buffer size Feature N1 N1 data type in UE and impact on service usage Specific service data type corresponding to the application identifier in the UE network element, where the data type is invisible or visible to the NWDAF network element … … … NN characteristic NN data type in UE network element and impact on service usage Specific service data type corresponding to the application identifier in the UE network element, where the data type is invisible or visible to the NWDAF network element

[0151] As shown in Table 4, Table 4 shows the communication template parameters related to Table 1.

Table 4 Link Template Parameter

Parameter CP Description periodic communication indicator Identifies whether the UE is performing periodic communication communication duration time Duration of each interaction, e.g. 5 minutes periodic time Interaction period, for example, once an hour or once a month. scheduled communication time Interaction time plan, for example, Time: 13:00-20:00, day: Monday stationary indication Determines if the UE is stationary or moving

[0152] It can be understood that the data processing method in the embodiments of the present application may be performed by the first network element, or may be performed by a device used in the first network element, such as a chip. In the following embodiments, an example is used for description in which the data processing method is performed by the first network element. The method of sending data in the embodiments of the present application may be performed by a network element, or may be performed by a device used in the network element, such as a chip. In the following embodiments, an example is used for description in which the data sending method is performed by the network element.

[0153] FIG. 4 shows a data processing method according to one embodiment of the present application. The method includes the following steps.

[0154] S101. At least two network elements determine that the first sub-service flow identifier has been received.

[0155] Here, the at least two network elements may be a combination of an AF network element and any one or more of the PCF network elements, the AMF network element, the SMF network element, the UPF network element, the RAN device, and the terminal.

[0156] For example, in this embodiment of the present application, the sub-service flow may be a quality of service flow or a service data flow.

[0157] Optionally, in this embodiment of the present application, step S101 may be replaced by step S101a. In step S101a, the network element determines that the first indication information has been received, where the first indication information is used to indicate to report the first data corresponding to the sub-service flow to the first network element. For example, the first indication may be a network data report indicator.

[0158] S102. Each of the at least two network elements sends to the first network element the first data which corresponds to the sub-service flow and which is in said corresponding network elements, where the first data carries the first identifier.

[0159] For example, the first network element may be the NWDAF network element in FIG.

[0160] It should be noted that if there are at least two network elements, the first data that corresponds to a sub-service flow and that is in each of said network elements may be different. For example, at least two network elements are network element 1 and network element 2. The first data that corresponds to a sub-service flow and that is in network element 1 is network data, such as a flow identifier. The first data that corresponds to a sub-service flow and that is in the network element 2 may be service data, such as a terminal ID. In this case, when network element 1 and network element 2 determine that the first ID has been received, then network element 1 sends the flow ID to the first network element, and network element 2 sends the terminal ID to the first network element.

[0161] For example, the first network element is NWDAF. Because the network elements are different, the ways in which the network elements send the first data to the first network element are different. Thus, the following describes the options separately.

[0162] Example 1: When one of the at least two network elements is at least one of an AMF network element, an SMF network element, and a PCF network element, the network element may directly send, to the first network element, via a service-based interface between network element and the first network element, the first data corresponding to the sub-service flow. The service-based interface may implement direct communication or interaction between any two network elements of an AMF network element, an SMF network element, a PCF network element, an NWDAF network element, and a NEF network element. For example, if the network element is an AMF network element, then the network element sends to the first network element via the service interface between the network element and the first network element the first data corresponding to the sub-service flow.

[0163] Example 2: When at least two network elements include a RAN device, first the RAN device may send the first data that corresponds to a sub-service flow and that is in the RAN device to a control plane network element connected to the RAN device e.g. AMF. Then, the control plane network element connected to the RAN device reports the first data to the first network element via a service interface (e.g., a service interface between the AMF network element and the NWDAF network element) between the first network element and the control plane network element that is connected to the RAN device. Alternatively, the RAN device may send, using the user plane tunnel established between the RAN device and the first network element, the first data that corresponds to the sub-service flow and that is in the RAN device to the first network element.

[0164] Example 3: When at least two network elements include a UPF network element, then first the UPF network element may send the first data that corresponds to a sub-service flow and that is in the UPF network element to the control plane network element , connected to a UPF NE, such as an SMF NE. Then, the control plane network element connected to the UPF network element reports the first data to the first network element via a service interface (e.g., a service interface between the SMF network element and the NWDAF network element) between the first network element and the control plane network element that is connected to the network element. UPF. Alternatively, the UPF network element may send, using the user plane tunnel between the UPF network element and the first network element, the first data that corresponds to the sub-service flow and that is in the UPF network element.

[0165] Example 4: When at least two network elements include an AF network element, in option 1, the AF network element may send the first data that corresponds to a sub-service flow and that is in the AF network element to the first network element with file transfer protocol (FTP). Alternatively, in option 2, the AF network element may send the first data that corresponds to the sub-service flow and that is in the AF network element to the first network element using the user plane tunnel established between the AF network element and the first network element. In option 3, the AF network element may continuously notify the first data that corresponds to the sub-service flow and that is in the AF network element to the first network element using the Naf_ServiceDataCollectionSubscription_Notify service. In method 4, the AF network element may send the first data that corresponds to the sub-service flow and that is in the AF network element to the first network element using NEF.

[0166] Optionally, the first identifier included in the first data that corresponds to a sub-service flow and which is located on each of said network elements is one or more of the following information: an identifier of the service to which the sub-service flow belongs, a flow identifier a sub-service, a terminal identifier, a session identifier to which the sub-service flow belongs, a data network name (DNN) of the session to which the sub-service flow belongs, and the identification information of the dedicated logical segment to which the sub-service flow belongs.

[0167] In this embodiment of the present application, on the one hand, the first identifiers carried in the first data sent from at least two network elements to the first network element may be the same. For example, the first identifier carried in data 1 sent from network element 1 is the identifier of the session to which the stream belongs to the service, and the first identifier carried in data 2 sent from network element 2 may also be the identifier of the session to which the stream belongs under the service.

[0168] On the other hand, the first identifiers carried in the first data sent from at least two network elements to the first network element may be different. For example, the first identifier carried in data 1 sent from network element 1 is the identifier of the terminal, and the first identifier carried in data 2 sent from network element 2 may be the identifier of the session to which the sub-service flow belongs.

[0169] When the first identifiers carried in the first data sent from different network elements to the first network element are different, there is a binding relationship between the first identifiers carried in the first data sent from different network elements. For example, there is a binding relationship between the session ID to which the sub-service flow belongs and the sub-service flow ID. In addition, the first network element stores the binding relationship between the first identifiers sent from different network elements. Thus, when receiving the first data that corresponds to a sub-service flow and that is sent from different network elements, the first network element can determine that the first data sent from different network elements is data corresponding to the same service flow.

[0170] S103. The first network element receives the first data that corresponds to the service flow and that is in each of at least two network elements, where the first data that corresponds to the service flow and that is in each of said network elements includes the first identifier.

[0171] It should be noted that when one of the at least two network elements is a network element in the previous various examples, the first network element receives from the network element, as appropriate, the first data corresponding to the sub-service flow. For example, when the network element is an AMF network element, the first network element receives, via a service-based interface between the AMF network element and the first network element, the first data that corresponds to a sub-service flow and is sent from the AMF network element. Details are not described in this embodiment of the present application.

[0172] S104. The first network element obtains, based on the first identifier and the first data, which corresponds to the sub-service flow and which is in each of said network elements, the second data, which corresponds to the sub-service flow.

[0173] The second data includes at least the first data that corresponds to a sub-service flow and that is in each of said network elements, or the second data includes at least a portion of the first data that corresponds to a sub-service flow. service and which reside in each of the network elements.

[0174] In particular, when the first identifiers carried in the first data sent from at least two network elements are the same, the first network element can be directly classified into the same set based on the first identifiers, the first data, or at least , a part of the first data corresponding to the sub-service flow and located in different network elements, to obtain the second data. When the first identifiers carried in the first data sent from at least two network elements are different, then the first network element may classify the first data, or at least a portion of the first data, into the same set based on the previously stored binding relationship, which correspond to the sub-service flow and are in different network elements having a binding relation to obtain the second data.

[0175] For example, the first data that corresponds to a service flow and that is received by the first network element from network element 1 is a flow identifier, and the first data that corresponds to a service flow and that is received from network element 2 is a terminal identifier. The first data in network element 1 contains identifier 1, the first data in network element 2 contains identifier 2, and there is a binding relationship between identifier 1 and identifier 2. In this case, the first network element may match the flow identifier corresponding to the sub-service flow with the terminal identifier to obtain second data corresponding to the sub-service flow. More specifically, the finally obtained second data includes a flow ID corresponding to a sub-service flow and a terminal ID, as shown in Table 5.

Table 5 Data corresponding to the sub-service flow

Service flow First data in NE 1 First data in NE 2 Second data Stream for service 1 (Stream id, id 1) (Terminal ID, ID 2) (Stream id, terminal id)

[0176] Optionally, if the first data does not carry the first identifier, the first data sent from different network elements may be classified into the same set using the PDU/QFI session ID at the RAN, the PDU session ID/UE ID /timestamp in the AMF NE, PDU/QFI Session ID/UE ID/Timestamp in the SMF NE, PDU/QFI Session ID/Timestamp in the UPF NE, UE ID/Application ID/Timestamp in the NE the PCF element and the UE ID/application ID/time stamp in the AF network element.

[0177] It should be noted that the first data that is received by the first network element that corresponds to a sub-service flow and that is in each of said network elements can alternatively be sent from the operation, administration and maintenance network element to the first network element . In particular, when determining that it is necessary to report the first data that corresponds to the sub-service flow and which is in each of said network elements, the respective network elements send the first data that corresponds to the sub-service flow and which is in said respective network elements, to the operation, administration and maintenance network element so that the operation, administration and maintenance network element sends the first data to the first network element.

[0178] Table 5 uses an example in which the first network element matches all first data in network element 1 with all first data in network element 2 to obtain second data. It can be understood that in a real process, if the first data in the network element 1 further includes a timestamp, then the first network element may choose to classify only at least a portion of the first data that corresponds to a sub-service flow and that is in the network element 1, and all or at least part of the data that corresponds to the sub-service flow and that is in the network element 2 into one set to obtain the second data. Alternatively, in this embodiment of the present application, the following case may exist. The first network element receives from at least two network elements different first data that corresponds to a sub-service flow and that is in different network elements, but the first network element can classify, according to the requirement of the first network element, all or part of the first data that is on some of the at least two network elements into one set to obtain the second data. This is not limited in this embodiment of the present application.

[0179] This embodiment of the present application provides a data processing method. The first network element receives the first data that is related to the service flow and is in different network elements, and matches the first data that is related to the service flow and is in different network elements, based on the first identifiers in the first data sent from different network elements to obtain the second data. Thus, the first network element can subsequently schedule one or more sets of QoS parameters of the service to which the sub-service flow belongs, the user plane path corresponding to the session to which the sub-service flow belongs, dedicated logical segment resource optimization, user plane or control plane collision detection. etc.

[0180] In a real process, if the second network element detects that some services corresponding to some types of terminals, in some network areas or in some time periods, have a problem, then in order for the first network element to analyze the cause of the problem, the second network element may suggest the first network element is requested to analyze the cause. The first network element collects the first data that corresponds to the sub-service flow and comes from different network elements. Therefore, in another embodiment, as shown in FIG. 5, the method presented in this embodiment of the present application further includes the following steps.

[0181] S105. The second network element sends a first message to the first network element, where the first message is used to direct the first network element to receive from at least two network elements the first data corresponding to a sub-service flow, and the first message includes one or more of the following information: a service identifier , to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, the area of the network in which the terminal corresponding to the service flow is located, and the time window corresponding to the service flow.

[0182] Optionally, the first message may further carry the identifiers of at least two network elements and the identifier of the second network element.

[0183] Optionally, the first message may further include one or more of the following information: one or more other service identifiers other than the identifier of the service to which the flow sub-service belongs, one or more other terminal types other than the terminal type the terminal corresponding to the service flow has one or more other network areas other than the network area in which the terminal corresponding to the service flow is located, and one or more other time windows other than the time window corresponding to the service flow.

[0184] The identifier of the service to which the sub-service flow belongs is used to determine the service to which the sub-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 the list of time periods corresponding to the service flow, for example, from March 1, 2018 to March 8, 2018. The network area in which the terminal corresponding to the service flow is located is used to determine a network area (eg, tracking area (TA), TA list, routing area (RA), or RA list) corresponding to the sub-service flow.

[0185] For example, the second network element may be an AF network element and the first network element may be an NWDAF network element. For example, the AF may send the first message to the NWDAF NE using the PCF NE.

[0186] The first message may be a message newly defined between the first network element and the second network element, or may be a message existing between the first network element and the second network element. This is not limited in this embodiment of the present application. For example, the first message may be a Naf_DataCollectionCondition_Notify message.

[0187] S106. The first network element receives the first message sent from the second network element.

[0188] It can be understood that after receiving the first message, the first network element may determine that the first data corresponding to the sub-service flow should be collected from different network elements.

[0189] Optionally, in this embodiment of the present application, after step S106, the method may further include: step 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.

[0190] It can be understood that the above steps S105 to S107 can be implemented separately or can be implemented in combination with the above steps S101 to S104. When steps S105 to S107 are implemented in conjunction with S101 to S104, S105 to S107 may be implemented before step S101.

[0191] In another embodiment of the present application, as shown in Fig.6, the method presented in this application also includes the following steps.

[0192] S108. The first network element sends a first request to each of at least two network elements, where the first request is used to request the first data that corresponds to a sub-service flow and which is in each of said network elements, and the first request includes one or more of the following information: ID of the service to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, the area of the network in which the terminal corresponding to the service flow is located, and the time window corresponding to the service flow.

[0193] Optionally, the first message may further include one or more of the following information: one or more identifiers of other services other than the identifier of the service to which the flow sub-service belongs, one or more other types of terminal other than the type of terminal the terminal corresponding to the service flow has one or more other network areas other than the network area in which the terminal corresponding to the service flow is located, and one or more other time windows other than the time window corresponding to the service flow.

[0194] Since the network elements are different, the messages used by the first network element to send the first request to the network elements are also different. Therefore, in the following embodiment, descriptions are provided separately.

[0195] Case 1: When the network element is a PCF network element, the first request sent from the first network element to the network element may be an Npcf_NetworkDataCollectionSubscription request message.

[0196] Case 2: When the network element is an AF network element, the first request sent from the first network element to the network element may be a Naf_ServiceDataCollectionSubsctiption request message.

[0197] It should be noted that when the network element is a PCF network element or an AF network element, the network element to which the first network element sends the first request and the network element which sends the first message may be the same network element, or may be different network elements. For example, the network element AF1 sends a first message to the first network element, and the first network element requests the network element AF2 for the first data corresponding to the sub-service flow.

[0198] S109. At least two network elements receive the first request sent from the first network element.

[0199] Optionally, in this embodiment of the present application, after step S109, the method may further include step S110. Each of the at least two network elements sends to the first network element a second response to the first request, where the second response is used to indicate that the network element accepts the first request. For example, when the network element is an AF network element, the second response is a Naf_ServiceDataCollectionSubsctiption Response message. When the network element is a PCF network element, the second response is an Npcf_NetworkDataCollectionSubscription Response message.

[0200] Optionally, in this embodiment of the present application, after S109, the method may further include steps: S111. At least two network elements send a second message to the first network element, where the second message carries the first data that corresponds to the sub-service flow and which is in said corresponding network elements. S112. The first network element receives a second message sent from at least two network elements. Based on steps S111 and S112, step S103 in the present application is implemented as follows: The first network element obtains from the second message sent by each of the network elements the first data that corresponds to the sub-service flow and that is in each of said network elements.

[0201] Optionally, in this embodiment of the present application, the first data sent from each of said network elements to the first network element further includes one or more of the following information: an identifier of the network element to which the first data corresponding to the flow belongs a sub-service, a terminal identifier, and a data value of at least one data type of at least one of the at least two network elements.

[0202] For example, the first data is sent from the AF network element to the first network element, and the first data sent from the AF network element to the first network element further carries an AF network element identifier.

[0203] For a data value of at least one data type of at least one of at least two network elements, the first data sent from the network element to the first network element may carry a data value of the network element data type, or the first data sent from the network element to the first network element may not only carry the data type data value of the network element, but also carry the data type data value of one or more other network elements other than the network element in at least two network elements. For example, the first data sent from the AF network element to the first network element may carry an AF network element data type data value and a PCF network element data type data value.

[0204] Optionally, as shown in FIG. 7, in this embodiment of the present application, before any of the at least two network elements sends to the first network element the first data that corresponds to the sub-service flow and that is in the network element, the method may further include the following steps to perform normalization processing on the first data to obtain a data value of the corresponding data type of each network element:

[0205] S113. Each of the at least two network elements determines the second data value based on the first data value of the first data type of the network element, where the first data value belongs to the first value space, the second data value belongs to the second value space, and the first data type is some entry in the first data .

[0206] In addition, in order to perform normalization processing on the first data that is related to the sub-service flow and is in the network element, after step S113, the method may further include the following step:

[0207] S114. Each network element determines the fourth data value based on the third data value of the second data type of the network element, where the third data value belongs to the third value space, the fourth data value belongs to the fourth value space, and the second data type is some entry in the first data.

[0208] Optionally, the second value space is the same as the fourth value space. To facilitate processing by the first network element, the normed space is the same for all data types, and NWDAF does not need to further normalize the first data into the same value space.

[0209] Optionally, performing normalization processing of the first data to obtain a data value of the respective data type of each network element may further include: each of the at least two network elements determines a sixth data value according to a fifth data value of the third data type of each network element. element, where the fifth data value belongs to the fifth data value space and the sixth data value belongs to the sixth value space.

[0210] Optionally, the second value space is the same as the sixth value space.

[0211] Through normalization processing, each of the at least two network elements may determine the second data value based on the first data value of the first data type of each network element, or determine the fourth data value based on the third data value of the second data type of each network element, or determine the sixth a data value based on the fifth data value of the third data type of each network element. Normalization processing involves mapping the physical data value of a data type into a fixed value space. The normalization processing is mainly for mapping the physical value of data of each data type to a fixed value space using the maximum-minimum value normalization method, the Z-score normalization method, and the like. This processing not only improves the rate of convergence of model training during big data analysis, but also provides a way to communicate feature data.

[0212] Since the at least two network elements can be any two different network elements from the AMF network element, the terminal, the SMF network element, the PCF network element, and the AF network element, when the first data corresponding to the sub-service flow comes from any of the network AMF element, terminal, SMF NE, PCF NE, and AF NE, the first data is different. Therefore, an example in which at least two network elements include a third network element is used below to separately describe some information that the first data received from the third network element may additionally have when the third network element is an AMF network element, the terminal , an SMF network element, a PCF network element, and an AF network element.

[0213] When the third network element is an application function (AF) network element, the first data received from the third network element further includes one or more of the following information: an identifier of the service to which the sub-service flow belongs, a service link pattern parameter which the sub-service stream belongs to, the first interface stream bit rate data, the first interface delay data, the first interface packet loss rate data, the first interface packet data, the timestamp, the usage data of the service to which the sub-service stream belongs, the delay jitter buffer, Transmission Control Protocol (TCP) congestion window data, TCP receive window data, media content coding type data, and media content coding type data coding rate data. The first interface is the interface between the user plane function network element and the data network (DN) that corresponds to the AF network element. For example, as shown in FIG. 3, the first interface may be the N6 interface.

[0214] When the third network element is a Policy Control Function (PCF) network element, the first data received from the third network element further includes one or more of the following information: a service identifier to which the sub-service flow belongs, a session identifier to which sub-service flow belongs, data network name (DNN) of the session to which the sub-service flow belongs, identification information of the segment to which the sub-service flow belongs, IP filtering information, media content bandwidth requirement, traffic routing information, delay jitter buffer requirement , the TCP congestion window requirement, the TCP receive window requirement, the media content encoding type requirement, the encoding rate requirement in the media content encoding type requirement, and the service ID validity time window.

[0215] When the third network element is an SMF network element, the first data received from the third network element further includes one or more of the following information: a sub-service flow identifier, a session identifier to which the sub-service flow belongs, a session DNN to which the service flow belongs, the identification information of the segment to which the service flow belongs, and the validity time window of the service flow identifier.

[0216] When the third network element is the first network element of the UPF, the first data received from the third network element further includes one or more of the following information: a sub-service flow identifier, a timestamp, second interface flow bit rate data, first interface 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, data about the third interface packet loss rate, the first interface packet data, the second interface packet data, and the third interface packet data. The second interface is the interface between the first UPF network element and the RAN device. The third interface is the interface between the first UPF network element and the second UPF network element. For example, the second interface may be the N3 interface shown in FIG. 3, and the third interface may be the N9 interface.

[0217] When the third network element is an Access and Mobility Management (AMF) network element, the first data received from the third network element further includes at least one of the following information: location information of the terminal corresponding to the sub-service flow, the session identifier to which the service flow belongs, the DNN of the session to which the service flow belongs, the identification information of the segment to which the service flow belongs, and the validity time window of the session identifier to which the service flow belongs.

[0218] When the third network element is a RAN device, the first data received from the third network element further includes one or more of the following information: location information of a terminal corresponding to a sub-service flow, a sub-service flow ID, a session ID, to which the service flow belongs, identification information of the dedicated logical segment to which the service flow belongs, timestamp, fourth interface flow bit rate data, second interface stream bit rate data, second interface delay data, fourth interface delay data, data reference signal received power (RSRP), reference signal received quality (RSRQ) data, signal to interference plus noise ratio (SINR) data, CQI data, BLER data, congestion level, second interface packet loss ratio data, packet loss ratio of the fourth interface, n packet data of the second interface; and packet data of the fourth interface. The fourth interface is the interface between the RAN device and the terminal, such as the Uu interface shown in FIG.

[0219] When the network element is a terminal, the first data received from the third network element further includes one or more of the following information: location information of the terminal corresponding to the sub-service flow, the identifier of the sub-service flow, the identifier of the session to which the sub-service flow, session DNN to which the sub-service flow belongs, identification information of the dedicated logical segment to which the sub-service flow belongs, bit rate data of the fourth interface stream, fourth interface delay data, packet loss rate data of the fourth interface, packet data of the fourth interface, timestamp, service usage data, delay jitter buffer data, Transmission Control Protocol (TCP) congestion window data, TCP receive window data, media content coding type data, media content coding type coding rate data, data RSRP, RSRQ data, SINR data, CQI data and BLER data.

[0220] In another embodiment of the present application, as shown in Fig.8, the method presented in this embodiment of the present application further includes the following steps.

[0221] S115. 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 sub-service flow, and the second request includes one or more of the following information: identifier of the service to which the sub-service flow belongs, IP filtering information , media bandwidth requirement, traffic routing information, delay jitter buffer requirement, TCP congestion window requirement, TCP receive window requirement, media content encoding type requirement, and encoding rate requirement in the media content encoding type requirement.

[0222] For example, the fifth network element may be an AF network element.

[0223] Optionally, if one of the at least two network elements is a PCF network element and the AF network element is a third party AF network element, then a second request may be transmitted between the third party AF network element and the PCF network element using the NEF network element .

[0224] For example, the second request may be an Npcf_PolicyAuthorization_Create Request message.

[0225] S116. At least two network elements receive the second request sent from the fifth network element.

[0226] Optionally, as shown in FIG. 9, the method presented in this embodiment of the present application further includes the following steps.

[0227] S117. The fourth network element sends a third request to the first network element, where the third request is used to request the allocation of the first service flow identifier.

[0228] For example, the fourth network element may be a PCF network element or an SMF network element.

[0229] For example, the third request may be an Nnwaf_CorrelationIDAssignment Request message.

[0230] For example, the third request may contain a service identifier to which the sub-service flow belongs, a session identifier to which the sub-service flow belongs, and a terminal identifier corresponding to the sub-service flow.

[0231] Optionally, a single request may be used to request lists of mapping identifiers corresponding to multiple SDFs in a single session PDU.

[0232] S118. The first network element receives the third request sent from the fourth network element.

[0233] S119. The first network element sends a third response to the third network element, where the third response includes the first identifier.

[0234] For example, the third response may be an Nnwdaf_CorrelationIDAssignment Response message.

[0235] Optionally, in another embodiment of the present application, as shown in FIG. 10, after step S104, the method may further include the following step:

[0236] S120. The first network element determines at least one piece of service quality of service (QoS) description information based on the second data, where each of the at least one piece of QoS description information includes a QoS parameter type and/or a QoS parameter requirement.

[0237] Optionally, each of 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 the QoS parameter requirement.

[0238] Optionally, step S101 in this embodiment of the present application may be implemented as follows:

[0239] Case 1: When the network element is a PCF network element, the network element sends a third request to the server network element, where the third request is used to request a first identifier, and the third request includes a service identifier and a terminal identifier. The network element receives a third response from the server network element, where the third response includes the first identifier. For example, the server network element may be a data analysis network element, a network storage function network element, or a domain name server.

[0240] Case 2: When the network element is an AF network element, after the AF network element sends a second request to the PCF network element, the AF network element can obtain the first identifier from the second response that is sent from the PCF network element in response to the second request .

[0241] Case 3: If the network element is an SMF network element, the SMF network element may obtain the first identifier from the PCF network element. For example, the PCF network element may send the first identifier corresponding to the sub-service flow to the SMF network element with an Npcf_SMPolicyControl_UpdateNotify request message.

[0242] Case 4: When the network element is a UPF network element, after the SMF network element receives the first identifier, the SMF network element may send the first identifier to the UPF network element. For example, the SMF network element may send the first identifier corresponding to the sub-service flow to the UPF network element using the N4 session change request/response, namely the N4 session change procedure. In other words, the UPF NE can obtain the first identifier from the SMF NE using the session change procedure N4.

[0243] Case 5: When the network element is an AMF network element, specifically, after the SMF network element receives the first identifier, the SMF network element may send the first identifier to the AMF network element. In other words, the AMF NE can obtain the first identifier from the SMF NE. It can be understood that case 5 alternatively includes a process in which the PCF network element sends the first identifier to the AMF network element using the SMF network element.

[0244] For example, the SMF network element may send the first identifier to the AMF network element using a Namf_Communication_N1N2MessageTransfer message.

[0245] Case 6: When the network element is a RAN device, then the RAN device receives the first identifier sent from the AMF network element or the SMF network element. In other words, after the AMF network element or the SMF network element has the first identifier, the AMF network element or the SMF network element can send the first identifier to the RAN device. For example, the AMF network element may send the first identifier to the RAN device using an N2 session request. It can be understood that case 6 alternatively includes: the PCF network element sends the first identifier to the RAN device using the AMF network element or the SMF network element.

[0246] Case 7: When the network element is a terminal, the terminal receives the first identifier sent from the RAN device, the AMF network element, or the SMF network element. In other words, after acquiring the first identifier, the RAN device, the AMF network element, or the SMF network element may send the first identifier to the terminal. Alternatively, the PCF network element may send the first identifier to the terminal using an AMF network element, an SMF network element, or a RAN device.

[0247] The foregoing describes the solutions in the embodiments of the present application mainly in terms of interaction between network elements. It can be understood that each network element, such as a data processing device or a data sending device, includes an appropriate hardware structure and/or a software module for performing each function in order to realize the above functions. One skilled in the art will readily appreciate that, in conjunction with the examples described in the embodiments disclosed in this specification, the blocks, steps of the algorithms may be implemented in hardware or a combination of hardware and computer software. The performance of a function by hardware or hardware controlled by computer software depends on the particular application and design constraints of the technical solutions. A person skilled in the art can use different methods to implement the described functions for each particular application, but such an implementation should not be considered to be outside the scope of this application.

[0248] The division of the data processing device and the data sending device into functional blocks can be performed in accordance with the above example methods in the embodiments of the present application. For example, each function block may be obtained by dividing according to each function, or two or more functions may be integrated into one processing block. An integrated block may be implemented in hardware or may be implemented in a software function block. It should be noted that in this embodiment of the present application, the division into blocks is exemplary and is simply a division of logical functions. In an actual implementation, a different partitioning method may be used.

[0249] When an integrated unit is used, FIG. 11 shows a possible block diagram of a data processing apparatus in the above embodiments. The data processing device may be the first network element or a chip used in the first network element. The data processing apparatus includes a receiving unit 201 and a processing unit 202 . The acquisition unit 201 is configured to support the data processing apparatus in performing step S103 in the above embodiments. The processing unit 202 is configured to support the data processing apparatus in executing step S104 in the above embodiments. Optionally, the data processing apparatus further includes a receiving block 203, a sending block 204, and a determining block 205. The receiving unit 203 is configured to support the data processing apparatus in performing steps S106 and S118 in the above embodiments. The sending unit 204 is configured to support the data processing apparatus in performing steps S107, S108, S119, and S112 in the above embodiments. The determination unit 205 is configured to support the data processing apparatus in performing step S110 in the above embodiments. All related contents of the steps in the above method embodiments can be cited in the function descriptions of the respective functional modules. Details are not described here again.

[0250] When an integrated unit is used, FIG. 12 shows a possible circuit diagram of the logical structure of the data processing apparatus in the above embodiments. The data processing device may be the first network element in the above embodiments, or a chip used in the first network element. The data processing device includes a processing module 212 and a communication module 213 . The processing module 212 is configured to administer and control the operation of the data processing device. For example, the processing unit 212 is configured to perform a message or data processing step performed on the data processing device side, for example, to support the data processing device in executing S104 and S110 in the above embodiments. The communication unit 213 is configured to support the data processing device in performing S103, S107, S108, S119, and S112 in the above embodiments, and/or is configured to perform another process performed by the data processing device in the technology described herein.

[0251] Optionally, the data processing device may further include a storage module 211 configured to store program code and data of the data processing device.

[0252] The processing module 212 may be a processor or controller, for example, the processing module may be a central processing unit, a general purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), programmable field programmable gate array (FPGA) or other programmable logic device, transistorized logic device, hardware component, or any combination thereof. The controller/processor may implement or execute various exemplary logical blocks, modules, and circuits described with reference to the content disclosed in the present invention. Alternatively, the processor may be a combination of processors that implement a computing function, such as a combination of one or more microprocessors, or a combination of a digital signal processor and a microprocessor. The communication module 213 may be a transceiver, a transceiver circuit, a communication interface, or the like. The storage module 211 may be a memory.

[0253] When the processing module 212 is the processor 220, the communication module 213 is the communication interface 230 or transceiver, and the storage module 211 is the memory 240, the data processing device in the present application may be the device shown in FIG.

[0254] Communication interface 230, one or more (including two) processors 220, and memory 240 are connected to each other via bus 210. 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 presentation, only one thick line is used to represent the tire in Fig. 13, but this does not mean that there is only one tire or only one type of tire. The memory 240 is configured to store the program code and data of the data processing device. Communication interface 230 is configured to support communication of the data processing device with another device (eg, a second network element). The processor 220 is configured to support the data processing device in executing the program code and data stored in the memory 240 to implement steps S103, S104, S107, S108, S119, S110, and S112 provided herein.

[0255] When an integrated unit is used, FIG. 14 shows a possible block diagram of the data sending apparatus in the above embodiments. The data sender may be a network element or a chip in a network element. The data sender includes a determination block 301 and a send block 302 . The determining unit 301 is configured to support the data sending apparatus in performing steps S101, S113, and S114 in the above embodiments. The sending unit 302 is configured to support the data sending apparatus in performing steps S102 and S111 in the above embodiments. Optionally, the data sending device may further include a receiving unit 303, configured to support the data sending device in performing steps S109 and S116 in the above embodiments. All related contents of the steps in the above method embodiments can be cited in the function descriptions of the respective functional modules. Details are not described here again.

[0256] When an integrated unit is used, FIG. 15 shows a possible circuit diagram of the logical structure of the data sending device in the above embodiments. The data sending device may be a network element in the above embodiments, or may be a chip used in the network element. The data sender includes a processing module 312 and a communication module 313 . The processing module 312 is configured to administer and control the operation of the data sending device. For example, the processing unit 312 is configured to perform a message or data processing step performed on the data sender side, such as S101, S113, and S114. The communication module 313 is configured to support the data sender in performing S102, S111, S109, and S116 in the above embodiments and/or is configured to perform another process performed by the data sender in the technology described herein.

[0257] Optionally, the data sender may further include a storage module 311 configured to store program code and data of the data sender.

[0258] The processing module 312 may be a processor or controller, for example, the processing module may be a central processing unit, a general purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), programmable field programmable gate array (FPGA) or other programmable logic device, transistorized logic device, hardware component, or any combination thereof. The controller/processor may implement or execute various exemplary logical blocks, modules, and circuits described with reference to the content disclosed in the present invention. Alternatively, the processor may be a combination of processors that implement a computing function, such as a combination of one or more microprocessors, or a combination of a digital signal processor and a microprocessor. The communication module 313 may be a transceiver, a transceiver circuit, a communication interface, or the like. The storage module 311 may be a memory.

[0259] When the processing module 312 is the processor 320, the communication module 313 is the communication interface 330 or transceiver, and the storage module 311 is the memory 340, the data sending device in the present application may be the device shown in FIG.

[0260] Communication interface 330, one or more (including two) processors 320, and memory 340 are connected to each other via bus 310. 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 presentation, only one thick line is used to represent the tire in Fig. 16, but this does not mean that there is only one tire or only one type of tire. The memory 340 is configured to store the program code and data of the data sender. The communication interface 330 is configured to support the data sending device in communicating with another device (eg, via the first network element). The processor 320 is configured to support the sender in executing the program code and data stored in the memory 340 to implement the S101, S113, S114, S102, S111, S109, and S116 provided herein.

[0261] When an integrated unit is used, FIG. 17 shows another possible schematic block diagram of the data sending device in the above embodiments. The data sender may be a second network element or a chip used in the second network element. The data sending device includes a sending unit 401 . The sending unit 401 is configured to support the data sending apparatus in execution S105 in the above embodiments. All related contents of the steps in the above method embodiments can be cited in the function descriptions of the respective functional modules. Details are not described here again.

[0262] When an integrated unit is used, FIG. 18 shows a possible circuit diagram of the logical structure of the data sender in the above embodiments. The data sending device may be the second network element in the above embodiments, or may be a chip used in the second network element. The data sender includes a processing module 412 and a communication module 413 . The processing module 412 is configured to administer and control the operation of the data sending device. For example, the processing unit 412 is configured to perform a message or data processing step performed on the data sending device side, for example, to support the data sending device in executing S105 in the above embodiments. The communication module 413 is configured to support the data sender in execution S105 in the above embodiments, and/or is configured to perform another process performed by the data sender in the technology described herein.

[0263] Optionally, the data sender may further include a storage module 411 configured to store program code and data of the data sender.

[0264] The processing module 412 may be a processor or controller, for example, the processing module 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 device, a transistorized logic device, a hardware component, or any combination of them. The controller/processor may implement or execute various exemplary logical blocks, modules, and circuits described with reference to the content disclosed in the present invention. Alternatively, the processor may be a combination of processors that implement a computing function, such as a combination of one or more microprocessors, or a combination of a digital signal processor and a microprocessor. The communication module 413 may be a transceiver, a transceiver circuit, a communication interface, or the like. The storage module 411 may be a memory.

[0265] When the processing module 412 is the processor 420, the communication module 413 is the communication interface 430 or transceiver, and the storage module 411 is the memory 440, the data sending device in the present application may be the device shown in FIG.

[0266] Communication interface 430, one or more (including two) processors 420, and memory 440 are connected to each other via bus 410. 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 presentation, only one thick line is used to represent the tire in Fig. 19, but this does not mean that there is only one tire or only one type of tire. The memory 440 is configured to store the program code and data of the data sender. The communication interface 430 is configured to support the data sending device in communicating with another device. The processor 420 is configured to support the sender in executing the program code and data stored in the memory 440 to implement the S105 provided herein.

[0267] FIG. 20 is a schematic block diagram of a chip 150 according to one embodiment of the present invention. Chip 150 includes one or more (including two) processors 1510 and interface circuit 1530.

[0268] Optionally, chip 150 further includes memory 1540. Memory 1540 may include read-only memory and random access memory and provides functional instructions and data to processor 1510. Memory portion 1540 may further include nonvolatile (non-volatile ) random access memory (non-volatile random access memory, NVRAM).

[0269] In some implementations, the memory 1540 stores the following elements: an executable module or a data structure, or a subset of them, or their extended set.

[0270] In this embodiment of the present invention, the corresponding operation is performed by calling the function instruction stored in the memory 1540 (the function instruction may be stored in the operating system).

[0271] Possible implementation: The structures of the chips used by the first network element and the second network element are similar, and different devices may use different chips to implement the functions of the devices.

[0272] The processor 1510 controls the operations of the first network element and the second network element. The processor 1510 may also be referred to as a central processing unit (CPU). Memory 1540 may include read-only memory and main memory and provide instructions and data to processor 1510. Memory portion 1540 may further include non-volatile random access memory (NVRAM). For example, in one application, processor 1540, interface circuitry 1530, and memory 1540 are coupled together via bus system 1520, where bus system 1520 may further include a power bus, a control bus, and a status signal bus. etc. in addition to the data bus. However, for a clear description, the different types of tires in FIG. 20 are referred to as bus system 1520.

[0273] The methods disclosed in the above embodiments of the present invention may be applied to processor 1510 or implemented by processor 1510. Processor 1510 may be an integrated circuit chip and may process signals. During implementation, the steps of the above methods may be implemented using a hardware integrated logic circuit in the processor 1510 or using instructions in the form of software. 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 device, a discrete gate or transistor logic device, or a discrete hardware component. It may implement or perform the methods, steps, and flowcharts that are disclosed in the embodiments of the present invention. A general purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like. The steps of the methods disclosed with reference to embodiments of the present invention may be directly executed and executed by a hardware decoding processor, or may be executed and executed by a combination of hardware and software modules in a decoding processor. The software module may be located on a conventional storage medium of the art, such as RAM, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, a register, or the like. The storage medium is located in the memory 1540 and the processor 1510 reads the information in the memory 1540 and performs the steps in the above methods in conjunction with the processor hardware.

[0274] Optionally, the interface circuit 1530 is configured to perform the steps of receiving and sending the first 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.10.

[0275] The processor 1510 is configured to perform the processing steps of the first 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. 10.

[0276] In the above embodiments, the instructions that are stored in the memory and that are to be executed by the processor may be implemented in the form of a computer program product. The computer program product may be stored in memory in advance, or may be downloaded and installed in memory in the form of software.

[0277] The computer program product includes one or more computer instructions. When computer program instructions are downloaded and executed on the computer, the procedure or functions according to embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a specialized computer, a computer network, or other programmable devices. The computer instructions may be stored on a computer-readable medium or may be transferred from one computer-readable medium to another computer-readable medium. For example, computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center over a wire (for example, coaxial cable, fiber optic cable, or digital subscriber line (DSL)) or wirelessly (eg via infrared, radio, microwave, etc.). A computer-readable medium can be any suitable medium accessible to a computer, or a storage device such as a server or data center that combines one or more usable media. The medium used may be a magnetic medium (eg, a floppy disk, hard disk, or magnetic tape), an optical medium (eg, a DVD), a semiconductor medium (eg, a solid state drive (SSD)) or the like.

[0278] According to one aspect, a computer storage medium is provided. A computer-readable storage medium stores instructions. When the instructions are executed, it is ensured that the first network element or chip used in the first network element executes steps S103, S104, S107, S108, S119, S110 and S112 in the embodiments and/or performs another process performed by the first network element or chip, applied in the first network element in the technology described in this document.

[0279] According to another aspect, a computer storage medium is provided. A computer-readable storage medium stores instructions. When the instructions are executed, it causes the network element or the chip applied to the network element to execute steps S101, S113 and S114, S102, S111, S109 and S116 in the embodiments and/or to execute another process performed by the network element or the chip applied to the network element. element in the technology described in this document.

[0280] According to another aspect, a computer storage medium is provided. The computer-readable storage medium stores instructions, and when the instructions are executed, the second network element or chip used in the second network element of step S105 in the embodiment is executed and/or another process is performed by the second network element or chip used in the second network element in the embodiment. technology described in this document.

[0281] The aforementioned readable storage medium may include: any medium that can store program code, such as a removable hard disk, read only memory, random access memory, magnetic disk, or optical disk.

[0282] According to one aspect, a computer program product is provided that includes instructions. A computer program product stores instructions. When the instructions are executed, it is ensured that the first network element or chip used in the first network element executes steps S103, S104, S107, S108, S119, S110, and S112 in the embodiments and/or performs another process performed by the first network element or chip, applied in the first network element in the technology described in this document.

[0283] According to another aspect, a computer program product is provided including instructions. A computer program product stores instructions. When the instructions are executed, it causes the network element or the chip applied in the network element to execute steps S101, S113, S114, S102, S111, S109 and S116 in the embodiments and/or to execute another process performed by the network element or the chip applied in the network element. element in the technology described in this document.

[0284] According to another aspect, in one embodiment of the present application, a computer program product is provided, including instructions. A computer program product stores instructions. When the instructions are executed, it causes the second network element or chip in the second network element to execute step S105 in the embodiments and/or to perform another process performed by the second network element or chip used in the second network element in the technology described herein.

[0285] According to an aspect, a chip is provided. The chip is applied in the first network element. The chip includes one or more (including two) processors and an interface circuit. The interface circuit and one or more (including two) processors are interconnected by a line. The processor is configured to: execute instructions for executing S103, S104, S107, S108, S119 and S110, S112 in the embodiments and/or configured to execute another process performed by the first network element in the technology described herein.

[0286] According to another aspect, a chip is provided. The microcircuit is used in a network element. The chip includes one or more (including two) processors and an interface circuit. The interface circuit and one or more (including two) processors are interconnected by a line. The processor is configured to execute instructions to execute S101, S113 and S114, S102, S111, S109 and S116 in embodiments and/or execute another process performed by a network element in the technology described herein.

[0287] According to another aspect, a chip is provided. The chip is used in the second network element. The chip includes one or more (including two) processors and an interface circuit. The interface circuit and one or more (including two) processors are interconnected by a line. The processor is configured to execute instructions to perform step S105 in the embodiments and/or configured to perform another process performed by the second network element in the technology described herein.

[0288] In addition, the present application further proposes a data processing system. The data processing system includes a data processing device shown in Figs. 11-13 and a data sending device shown in Figs. 14-16.

[0289] Optionally, the data processing system further includes a data sender shown in FIGS. 17-19.

[0290] All or some of the above embodiments may be implemented in software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, the embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When computer program instructions are downloaded and executed on the computer, the procedure or functions according to embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a specialized computer, a computer network, or other programmable devices. The computer instructions may be stored on a computer-readable medium or may be transferred from one computer-readable medium to another computer-readable medium. For example, computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center over a wire (for example, coaxial cable, fiber optic cable, or digital subscriber line (DSL)) or wirelessly (eg via infrared, radio, microwave, etc.). A computer-readable medium can be any suitable medium accessible to a computer, or a storage device such as a server or data center that combines one or more usable media. The medium used may be a magnetic medium (eg, a floppy disk, hard disk, or magnetic tape), an optical medium (eg, a DVD), a semiconductor medium (eg, a solid state drive (SSD)) or the like.

[0291] Although the present invention has been described with reference to the embodiments, however, in the process of implementing the present invention, which is to be protected, those skilled in the art can understand and implement another embodiment of the disclosed embodiments by viewing the accompanying drawings, the disclosure, and the appended claims. . In the claims, "comprising" does not exclude another component or another step, and "one" does not exclude the meaning of a plurality. One processor or other block can perform several functions listed in the claims. Some characteristics are written in dependent claims that differ from each other, but this does not mean that these characteristics cannot be combined to obtain a better effect.

[0292] Although the present invention has been described with reference to specific functions and their embodiments, it is obvious that various modifications and combinations can be made to them without going beyond the essence and scope of the present invention. Accordingly, the description and accompanying drawings are merely an exemplary description of the present invention as defined by the appended claims, and are construed as any or all modifications, variations, combinations or equivalents that fall within the scope of the present invention. Obviously, a person skilled in the art can make various modifications and changes to the present invention without going beyond the scope of the present invention. The present invention is intended to cover these modifications and variations of the present invention, provided that they fall within the scope of protection defined by the following claims and their equivalent technologies.

Claims (47)

1. A data processing method, comprising the steps of: receive by means of the first network element the first data that corresponds to the service flow and that is in each of at least two network elements, while the first data that corresponds to the service flow and that is in each of said at least two network elements contains the first identifier; and receive by the first network element on the basis of the first identifier and the first data that corresponds to the service flow and which is in each of the at least two network elements mentioned, the second data that corresponds to the service flow, while the second data contains at least the first data, which correspond to a service flow and which reside in each of said at least two network elements; wherein the first network element is a Network Data Analysis Function (NWDAF) network element. 2. The method of claim 1, wherein the method further comprises receiving, via the first network element, a first message sent from the second network element, the first message being used to direct the first network element to receive the first data from the at least two network elements. corresponding to the service flow, and the first message contains one or more of the following information: an identifier of the service to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, the area of the network in which the terminal corresponding to the service flow is located, and the time window corresponding to service flow. 3. The method according to claim 1 or 2, wherein the method further comprises sending, via the first network element, a first request to each of at least two network elements, wherein the first request is used to request the first data that corresponds to the service flow and which are located in each of the at least two network elements, and the first request contains one or more of the following information: the identifier of the service to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, the network area in which the terminal corresponding to the service flow is located, service flow, and a time window corresponding to the service flow. 4. The method according to claim 1 or 2, wherein receiving by the first network element the first data that corresponds to the service flow and which is in each of the at least two network elements, comprises receiving by the first network element a second message, sent from each of said at least two network elements, wherein the second message contains the first data which corresponds to the service flow and which is in said respective network elements. 5. The method according to claim 1 or 2, wherein the first data further comprises one or more of the following information: an identifier of the network element to which the first data corresponding to the service flow belongs, a terminal identifier, and a data value of at least one data type of at least one of said at least two network elements. 6. The method according to claim 1 or 2, in which the mentioned at least two network elements contain a third network element; and when the third network element is an application function (AF) network element, the first data received from the third network element further comprises one or more of the following information: an identifier of the service to which the service flow belongs, a link template parameter of the 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 usage data of the service flow to which the service stream belongs, delay jitter buffer data, congestion window data transmission control protocol (TCP), TCP receive window information, media content encoding type data, media content encoding type data encoding rate and buffer information, wherein the first interface is an interface between a user plane function (UPF) network element and a data network (DN) that matches network element AF; when the third network element is a Policy Control Function (PCF) network element, then the first data received from the third network element further comprises one or more of the following information: a service identifier to which the service flow belongs, a session identifier to which the service flow belongs, a name data network (DNN) of the session to which the service flow belongs, identity of the dedicated logical segment to which the service flow belongs, IP filtering information, media content bandwidth requirement, traffic routing information, delay jitter buffer requirement, TCP congestion window requirement , TCP receive window requirement, media coding type requirement, coding rate requirement in media coding type requirement, service ID validity time window, and radio access technology type; when the third network element is a session management function (SMF) network element, then the first data received from the third network element further comprises one or more of the following information: service flow identifier, session identifier to which the service flow belongs, session DNN to which the service flow, the identity of the dedicated logical segment to which the service flow belongs, the validity time window of the service flow identifier, and the radio access technology type; when the third network element is the first network element of the UPF, then the first data received from the third network element further comprises one or more of the following information: service flow identifier, timestamp, second interface bit rate data, first interface bit rate data. interface, 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, packet data of the first interface, packet data of the second interface and packet data of the third interface, wherein the second interface is the interface between the first UPF network element and the radio access network (RAN) device, and the third interface is the interface between the first UPF network element and the second network element. UPF element; when the third network element is an Access and Mobility Management Function (AMF) network element, the first data received from the third network element further comprises at least one of the following information: the service flow, the DNN of the session to which the service flow belongs, the identity of the dedicated logical segment to which the service flow belongs, the validity time window of the session identifier to which the service flow belongs, and the radio access technology type; when the third network element is a RAN device, the first data received from the third network element further contains one or more of the following information: location information of the terminal corresponding to the service flow, service flow identifier, session identifier to which the service flow belongs, identification information dedicated logical segment to which the service flow belongs, time stamp, fourth interface bit rate data, second interface bit rate data, second interface delay data, fourth interface delay data, received reference signal power (RSRP) data, reference signal received quality (RSRQ) data, signal-to-interference-plus-noise ratio (SINR) data, channel quality information (CQI) data, block error rate (BLER) data, congestion level, second packet loss ratio data interface, loss ratio data and fourth interface packets, second interface packet data, fourth interface packet data, radio access technology type, and dual connectivity indication information, wherein the fourth interface is an interface between a RAN device and a terminal. 7. The method according to claim 1 or 2, wherein the first identifier contained in the first data that corresponds to the service flow and which is located on each of said network elements is one or more of the following information: the identifier of the service to which the service flow belongs, service flow identifier, terminal identifier, session identifier to which the service flow belongs, session DNN to which the service flow belongs, identification information of the dedicated logical segment to which the service flow belongs. 8. The method according to claim 1 or 2, wherein the first data that corresponds to the service flow and that is in each of said at least two network elements contains the same first identifier. 9. The method of claim 8, wherein the method further comprises: receiving, by means of the first network element, a third request sent from the fourth network element, the third request being used to request allocation of a first service flow identifier; and by means of the first network element, a third response is sent to the fourth network element, wherein the third response contains the first identifier. 10. The method of claim 1 or 2, wherein the service flow is a quality of service flow or a service data flow. 11. A method for sending data, comprising the steps of: determining by the network element that a first service flow identifier has been obtained, the first identifier being used to identify the first data that corresponds to the service flow and which is in the network element; and sending by means of the network element the first data to the first network element, the first data being used by the first network element to obtain the second data, the second data containing the first data and the first data containing the first identifier. 12. The method of claim 11, comprising receiving, by means of the network element, a first request sent from a first network element, wherein the first request is used to request the first data that corresponds to the service flow and which is in the network element, and the first request contains one or more of the following information: an identifier of the service to which the service flow belongs, the terminal type of the terminal corresponding to the service flow, the network area in which the terminal uses the service flow, and the time window corresponding to the service flow. 13. The method according to claim 11 or 12, wherein the first data further comprises one or more of the following information: an identifier of the network element to which the first data corresponding to the service flow belongs, a terminal identifier, and a data value of at least one data type of at least one of said two or more network elements. 14. The method of claim 13, wherein the data value of the network element data type specifically comprises determining, by the network element, a second data value based on the first data value of the first network element data type, wherein the first data value belongs to the first value space, the second data value belongs to the second value space, and the first data type is some entry in the first data. 15. The method of claim 13, wherein the network element data type data value further comprises determining, by the network element, a fourth data value based on a third data value of the second network element data type, 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 some record in the first data. 16. The method of claim 14, wherein the second value space is the same as the fourth value space. 17. The method according to claim 11 or 12, in which when the network element is an application function (AF) network element, the first data further comprises one or more of the following information: an identifier of the service to which the service flow belongs, a link template parameter of the service to which the service flow belongs, bit rate data of the first interface flow, first interface delay data, first interface packet loss rate data, first interface packet data, timestamp, usage data of the service to which the service flow belongs, delay jitter buffer data, transmission control protocol (TCP) congestion window data, data the TCP receive window, the media content coding type data, the media content coding type data coding rate, and the buffer data, wherein the first interface is the interface between the user plane function (UPF) network element and the data network (DN) that corresponds to the network element AF; when the network element is a policy control function (PCF) network element, the first data further comprises one or more of the following information: a service identifier to which the service flow belongs, a session identifier to which the service flow belongs, a data network name (DNN) of the session to which belongs to the service flow, identity of the dedicated logical segment to which the service flow belongs, IP filtering information, media bandwidth requirement, traffic routing information, delay jitter buffer requirement, TCP congestion window requirement, TCP receive window requirement, requirement to the media content coding type, the encoding rate requirement in the media content encoding type requirement, the validity time window of the service identifier, and the radio access technology type; when the network element is a session management function (SMF) network element, the first data further comprises one or more of the following information: service flow identifier, session identifier to which the service flow belongs, session DNN to which the service flow belongs, dedicated logical segment identification information , to which the Service Flow belongs, the validity time window of the Service Flow ID, and the type of radio access technology; when the network element is the first UPF network element, the first data further comprises one or more of the following information: service flow identifier, timestamp, second interface flow 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, packet data a second interface and packet data of a third interface, the second interface being the interface between the first UPF network element and a radio access network (RAN) device, and the third interface being the interface between the first UPF network element and the second UPF network element; when the network element is an Access and Mobility Management (AMF) network element, the first data further comprises at least one of the following information: location information of the terminal corresponding to the service flow, session identifier to which the service flow belongs, session DNN to which the flow belongs services, the identity of the dedicated logical segment to which the service flow belongs, the time window of validity of the session identifier to which the service flow belongs, and the type of radio access technology; when the network element is a RAN device, the first data further comprises one or more of the following information: location information of the terminal corresponding to the service flow, service flow identifier, session identifier to which the service flow belongs, identification information of the dedicated logical segment to which the service flow belongs , timestamp, fourth interface bit rate data, second interface bit rate data, second interface delay data, fourth interface delay data, received reference signal power (RSRP) data, received reference signal quality (RSRQ) data ), signal-to-interference-plus-noise ratio (SINR) data, channel quality information (CQI) data, block error rate (BLER) data, second interface packet loss rate data, congestion level, fourth interface packet loss rate data interface, packet data in the second interface, the fourth interface packet data, the radio access technology type, and the dual connectivity indication information, the fourth interface being the interface between the RAN device and the terminal. 18. The method of claim 11 or 12, wherein when the network element is a policy control network element, the method further comprises receiving, via the network element, a second request sent from the application function (AF) network element, wherein the second the request is used to request the establishment of a service flow, and the second request contains one or more of the following information: identifier of the service to which the service flow belongs, IP filtering information, media content bandwidth requirement, traffic routing information, delay jitter buffer requirement, requirement to the TCP congestion window, the TCP receive window requirement, the media content encoding type requirement, the encoding rate requirement in the media content encoding type requirement, the buffer requirement, and the requirement for at least one data type. 19. The method of claim 11 or 12, wherein the first identifier is one or more of the following: service identifier to which the service flow belongs, service flow identifier, terminal identifier, session identifier to which the service flow belongs, session DNN to which service flow, identification information of the dedicated logical segment to which the service flow belongs. 20. The method of claim 11 or 12, wherein the service flow is a quality of service flow or a service data flow. 21. A method for sending data, comprising the step of: sending by means of the network element a first message to the first network element, wherein the first message is used to instruct the first network element to receive from at least two network elements the first data corresponding to the service flow, and the first message contains one or more of the following information: an identifier of the service, which the service flow belongs to, the terminal type of the terminal corresponding to the service flow, the network area in which the terminal corresponding to the service flow is located, and the time window corresponding to the service flow. 22. A wireless communication device comprising at least one processor connected to the memory, wherein at least one processor is configured to execute instructions stored in the memory to cause the device to perform the method according to any one of claims 1, 11 and 21. 23. A computer-readable storage medium, wherein the computer-readable storage medium stores one or more programs, which one or more programs contain instructions that, when executed by at least one processor of the device, cause the device to perform the method according to any one of claims 1, 11 and 21 . 24. A data processing system, comprising: a Network Data Analysis Function (NWDAF) network element, configured to implement the method of claim 1; and a core network element configured to send the first data that corresponds to the service flow and that is in the core network element to the NWDAF network element, the first data containing the first identifier.

Images