WO2023185402A1

WO2023185402A1 - Communication method and apparatus

Info

Publication number: WO2023185402A1
Application number: PCT/CN2023/080131
Authority: WO
Inventors: 孙海洋; 李岩
Original assignee: 华为技术有限公司
Priority date: 2022-03-26
Filing date: 2023-03-07
Publication date: 2023-10-05
Also published as: CN116866986A

Abstract

The present application belongs to the technical field of communications. Provided are a communication method and apparatus, which aim to guarantee the QoS quality of a service by means of relatively low overheads. In the method, a PER corresponding to a service is configured for a terminal or an access network device, for example, a PER meeting a frame loss rate limit of the service, such that the terminal or the access network device can directly process a data packet of the service according to the PER without the need for identifying header information corresponding to the data packet, thereby guaranteeing the frame loss rate of the service by means of relatively low overheads, and thus the QoS quality of the service is guaranteed. The method can be applied to a 4G communication system, a 5G communication system, or a future communication system.

Description

Communication methods and devices

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on March 26, 2022, with application number 202210308243.6 and the application name "Communication Method and Device", the entire content of which is incorporated into this application by reference.

Technical field

The present application relates to the field of communication, and in particular, to a communication method and device.

Background technique

New radio (NR) is gradually incorporating some multimedia services with strong real-time performance and large data capacity requirements. For example, extended reality (XR), tactile Internet, etc. These businesses have very high requirements on quality of service (QoS) to ensure a good user experience. However, because the access network equipment does not perceive the correspondence between the data packets and frames of these services, the subsequently rendered data often does not correspond to the frames, resulting in frame loss, frame skipping, or frame lag, or inconsistency between the picture and audio, etc. situation, affecting the QoS quality of the business.

In response to this problem, the current solution is to add the corresponding relationship between frames and data packets in the data packet to alleviate the situation of frame loss, frame jump, or frame lag, or inconsistency between the picture and audio, etc., and ensure the QoS quality of the business . However, this method requires the access network device to identify the header information corresponding to each data packet, which is very expensive.

Contents of the invention

Embodiments of the present application provide a communication method and device to ensure QoS quality of services through lower overhead.

In order to achieve the above purpose, this application adopts the following technical solutions:

The first aspect is to provide a communication method. The method includes: the policy control network element obtains the packet error rate PER corresponding to the service, and sends the PER to the session management network element. Among them, PER is used by terminals or access network equipment to process service data packets based on PER.

According to the method described in the first aspect, by configuring the terminal or access network device with a PER corresponding to the service, such as a PER that meets the frame loss rate limit of the service, the terminal or access network device can directly process the frame loss based on the PER. For business data packets, there is no need to identify the header information corresponding to the data packet, so as to ensure the frame loss rate of the business through lower overhead, thereby ensuring the QoS quality of the business.

In one possible design solution, PER is a specified value. In other words, the policy control network element can instruct the terminal or access network equipment which value of PER to use, without the terminal or access network equipment needing to determine or adjust the PER, so as to reduce equipment overhead and improve operating efficiency. For example, the specified value of PER satisfies the following relationship: A/B% ≤ C ≤ A%, and the frame loss rate of the service is limited to A%. Among them, the number of data packets in the service frame (such as one frame) is B, the specified value of PER is C, the value of A is greater than 0, and B is a positive integer. It can be seen that a PER of A% is a relatively loose packet loss rate condition, while a PER of A/B% is a relatively strict packet loss rate condition. Each of the two constitutes a range, such as [A/B%, A%] , so that the PCF network element can select a suitable PER within this range to take into account equipment overhead and business requirements.

In one possible design solution, the policy control network element obtains the PER corresponding to the service, including: the policy control network element receives the PER of the service from the application function, so as to reduce the overhead of the policy control network element and improve operating efficiency. Among them, the PER It is determined based on the frame loss rate limit of the service. This PER is used to make the frame loss rate of the service meet the frame loss rate limit when the terminal or access network equipment processes the data packets of the service. Wherein, determining the PER according to the frame loss rate limit may be determining the frame loss rate limit as the PER. For example, the frame loss rate is limited to A%, and the PER is also A%, which is used to meet the frame loss rate limit of the service under specific circumstances (such as packet loss within the same frame).

Optionally, the PER is further determined based on the number of data packets in the service frame. For example, the policy control network element determines the quotient between the frame loss rate limit of the service and the number of data packets in the frame of the service, and determines the quotient value as PER, which is used to detect packet loss in any frame under any circumstances (such as packet loss in any frame). ) meets the frame loss rate limit of the service.

In another possible design solution, the policy control network element obtains the PER corresponding to the service, including: the policy control network element receives the frame loss rate limit information of the service from the application function, and determines the PER based on the frame loss rate limit information. That is to say, the application function can only provide service information, and the policy control network element determines the PER on its own, so as to reduce the overhead of the application function and improve operating efficiency. Among them, the PER is used to make the frame loss rate of the service meet the frame loss rate limit of the service when the terminal or the access network device processes the data packet of the service.

Optionally, the method described in the first aspect may further include: the policy control network element receives frame characteristic information of the service from the application function, and determines the number of data packets in the frame of the service based on the frame characteristic information. Correspondingly, the policy control network element determines the PER based on the frame loss rate limit information, including: the policy control network element determines the PER based on the frame loss rate limit information and the number of data packets in the service frame.

Optionally, the frame characteristic information includes at least one of the following: frame period, maximum number of data packets, maximum data burst amount, or data packet period. Among them, the frame period and data packet period can be used to determine the number of data packets in the frame of the service (recorded as the number of data packets in the frame). For example, the number of data packets in a frame = frame period/packet period; or, the maximum number of data packets can also be used to determine the number of data packets in a frame, such as the number of data packets in a frame = the maximum number of data packets; or, the maximum number of data bursts It can also be used to determine the number of data packets in a frame, such as the number of data packets in a frame = maximum data burst amount/maximum transmission unit MTU. In this way, the policy control network element can select parameters that it can recognize to determine the number of data packets in the frame, to avoid being unable to determine the number of data packets in the frame because the policy control network element does not support some of the above parameters, so as to ensure the reliability of the solution. sex. Moreover, in this case, determining the PER based on the number of data packets in the frame can also ensure that the frame loss rate of the service meets the frame loss rate limit under any circumstances.

Further, the frame characteristic information includes at least one of the following: burst arrival time BAT, or time information. Among them, BAT is used to indicate the arrival time of the first data packet of the service. In this way, the terminal or access network equipment can determine the data packets belonging to the same frame based on the frame characteristic information, thereby achieving a more accurate calculation of the packet loss rate of the service at the frame granularity. For example, the terminal or access network device determines how long after the first data packet arrives, all arriving data packets are data packets in the same frame. In addition, the time information may be used to indicate the time of the frame of the service (denoted as frame time). In this way, the terminal or access network equipment can also use different PERs at different times based on time information to take into account equipment overhead and business needs. For example, for non-key frames of the business within certain periods of time, the PER determined based on the frame loss rate limit information can be used to save overhead; for the key frames of the business within certain periods of time, the PER can be used based on the number of data packets in the frame. Determine the PER to avoid key frame loss and ensure business requirements.

In one possible design solution, PER is carried in the policy and charging control PCC rules to achieve cell reuse and improve communication efficiency.

In a possible design solution, the method described in the first aspect may further include: the policy control network element sends the execution condition of the PER to the session management network element. The execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within the specified time of the business, the PER is The specified value, or the specified value of PER in the case of packet loss or frame loss, so that the terminal or access network equipment can select appropriate execution conditions in the corresponding situation to take into account equipment overhead and business needs.

Optionally, the execution condition of PER includes at least one of the following: execution condition #1, execution condition #2, or execution condition #3. Execution condition #1 is used to indicate: the specified time includes key frames, and the specified value of PER satisfies the following relationship: A/B%=C, so as to avoid key frame loss as much as possible; or, the specified time includes non-key frames, The specified value of PER satisfies the following relationship: A/B%<C≤A%, so as to minimize equipment overhead while meeting business requirements. Execution condition #2 is used to indicate at least one of the following: the specified value of PER is negatively correlated with the number of lost frames, or the specified value of PER is negatively correlated with the number of lost packets. That is to say, as the number of frame loss and/or packet loss increases within the allowable range of the business, the PER gradually changes from a relatively loose packet loss rate condition to a relatively strict packet loss rate condition, achieving better performance in frame loss or packet loss. In the case of increased traffic, frame or packet loss can be alleviated by increasing the PER limit to ensure the QoS quality of the business. Execution condition #3 is used to indicate: in the case of packet loss within the same frame, the specified value of PER remains unchanged. For example, when the terminal or access network device calculates packet loss at frame granularity, if the terminal or access network device determines that packet loss occurs within the same frame, the specified value of PER can be kept unchanged according to execution condition #3. Change. In other words, for a frame that has already experienced packet loss, this frame has been lost. At this time, if this frame continues to lose packets, it will not affect the frame loss rate of the service. Therefore, the specified value of PER can be kept unchanged to avoid increasing invalid overhead and improve the operating efficiency of the device.

Optionally, the execution conditions of PER are carried in PCC rules to realize cell multiplexing and improve communication efficiency.

The second aspect is to provide a communication method. The method includes: the session management network element receives the packet error rate PER corresponding to the service from the policy control network element, and sends the corresponding relationship between the PER and the QoS flow to the terminal and/or the access network device. The corresponding relationship is used for the access network device or terminal to process the data packets of the service corresponding to the QoS flow according to the PER.

In one possible design solution, PER is a specified value.

Optionally, the specified value of PER satisfies the following relationship: A/B% ≤ C ≤ A%, the frame loss rate of the service is limited to A%, the number of data packets in the frame of the service is B, and the specified value of PER is C, the value of A is greater than 0, and B is a positive integer.

In one possible design solution, PER is determined based on the frame loss rate limit of the service. This PER is used to ensure that the frame loss rate of the service meets the frame loss rate limit of the service when the terminal or access network equipment processes the data packets of the service.

Optionally, PER can be determined based on the frame loss rate limit of the service and the number of data packets in the frame of the service.

Optionally, the number of data packets in a frame of the service is determined based on the frame characteristic information of the service. The frame characteristic information includes at least one of the following: frame period, maximum number of data packets, maximum data burst amount, or data packet period.

Further, the frame characteristic information of the service includes at least one of the following: BAT or time information. BAT is used to indicate the arrival time of the first data packet of the service, and the time information is used to indicate the time of the frame of the service.

In a possible design solution, the session management network element receives the PER corresponding to the service from the policy control network element, including: the session management network element receives the PCC rule from the policy control network element, and the PCC rule carries the PER.

Optionally, the method described in the second aspect may also include: the session management network element maps the PCC rules to the QoS flow, so as to ensure the QoS quality of the service with the QoS flow as a granularity.

Further, the session management network element maps the PCC rule to the QoS flow, including: the session management network element determines that the PER in the PCC rule is the same as the PER in the existing QoS flow parameter, and maps the PCC rule to the QoS flow parameter corresponding to QoS flows to reuse existing QoS flows and reduce overhead. Alternatively, the session management network element determines that the PER is different from the PER in the existing QoS flow parameters, creates a QoS flow, and maps the PCC rule to the created QoS flow to prevent the PCC rule from affecting the existing QoS flow.

In a possible design solution, the method described in the second aspect may also include: the session management network element receives a self-policy The execution condition of the PER of the network element is slightly controlled, and the execution condition of the PER is sent to the terminal or access network device. Among them, the execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Optionally, the execution condition of PER includes at least one of the following: execution condition #1, execution condition #2, or execution condition #3. Execution condition #1 is used to indicate: the specified time includes key frames, and the specified value of PER satisfies the following relationship: A/B%=C. Or, included within the specified time are non-key frames, and the specified value of PER satisfies the following relationship: A/B%<C≤A%. Execution condition #2 is used to indicate at least one of the following: the specified value of PER is negatively correlated with the number of lost frames, or the specified value of PER is negatively correlated with the number of lost packets. Execution condition #3 is used to indicate: in the case of packet loss within the same frame, the specified value of PER remains unchanged.

Further, the execution conditions for the session management network element to receive the PER from the policy control network element include: the session management network element receives the PCC rule from the policy control network element, and the PCC rule carries the execution condition for the PER.

In addition, other technical effects of the communication method described in the second aspect can be referred to the technical effects of the communication method described in the first aspect, which will not be described again here.

The third aspect is to provide a communication method. The method includes: receiving a correspondence between a PER and a QoS flow from a session management network element, and processing data packets of services corresponding to the QoS flow according to the PER. Among them, the PER corresponds to the business.

In one possible design solution, processing the data packets of the service corresponding to the QoS flow according to the PER includes: determining the link configuration corresponding to the QoS flow according to the PER, and sending the data packet of the service corresponding to the QoS flow according to the link configuration. To ensure that the frame loss rate of this service meets the frame loss rate limit.

In one possible design solution, PER is a specified value.

In one possible design solution, PER is determined based on the frame loss rate limit of the service. The PER is used to make the frame loss rate of the service meet the frame loss rate limit of the service when the terminal or access network device processes the data packet of the service.

Optionally, the PER is further determined based on the number of data packets in the frame of the service.

Optionally, the method described in the third aspect may further include: receiving frame characteristic information of the service, and determining, based on the frame characteristic information, data packets in the same frame belonging to the service. Correspondingly, processing the data packets of the service corresponding to the QoS flow according to the PER includes: processing the data of the service corresponding to the QoS flow according to the PER in a manner of discarding data packets in the same frame to ensure that the frame loss rate of the service meets the loss requirement. Frame rate limit.

In a possible design solution, the method described in the third aspect may further include: receiving execution conditions of the PER from the session management network element. Among them, the execution condition of PER can be used to indicate that when the execution condition is met, PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Optionally, the execution condition of PER includes at least one of the following: execution condition #1, execution condition #2, or execution condition #3. Execution condition #1 is used to indicate: the specified time includes key frames, and the specified value of PER satisfies the following relationship: A/B%=C; Or, the specified time includes non-key frames, and the specified value of PER satisfies the following relationship: A/B%<C≤A%. Execution condition #2 is used to indicate at least one of the following: the specified value of PER is negatively correlated with the number of lost frames, or the specified value of PER is negatively correlated with the number of lost packets. Execution condition #3 is used to indicate: in the case of packet loss within the same frame, the specified value of PER remains unchanged.

Optionally, the method described in the third aspect may also include: adjusting the specified value of PER according to the execution condition of PER, and adjusting the link resources corresponding to the QoS flow according to the adjusted specified value of PER, so as to adjust the link resource corresponding to the QoS flow according to the specified value after adjustment of PER. After adjusting the link resources, send the data packets of the service corresponding to the QoS flow to ensure that the frame loss rate of the service always meets the frame loss rate limit.

For other technical effects of the communication method described in the third aspect, reference can be made to the technical effects of the communication method described in the first aspect or the second aspect, and will not be described again here.

The fourth aspect is to provide a communication method. The method includes: the session management network element receives service-related information from the policy control network element, and sends the corresponding relationship between the service-related information and the QoS flow to the access network device. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate limit. The frame characteristic information is used to determine the number of data packets in the frame of the service. The relevant information of the service is used to determine the PER. The PER is used for the terminal or interface. The network access device processes service data packets based on the PER.

According to the method described in the fourth aspect, by configuring service-related information for the access network device, the access network device can determine the PER corresponding to the service based on the service-related information, such as the PER that satisfies the frame loss rate limit of the service. . In this way, the access network equipment can directly process the data packets of the service based on the PER without identifying the corresponding header information of the data packets, thereby ensuring the frame loss rate of the service and ensuring the QoS quality of the service through lower overhead.

In a possible design solution, the frame characteristic information includes at least one of the following: frame period, maximum number of data packets, maximum data burst amount, or data packet period.

Optionally, the frame characteristic information includes at least one of the following: BAT, or time information. BAT is used to indicate the arrival time of the first data packet of the service, and the time information is used to indicate the time of the frame of the service.

In a possible design solution, the session management network element receives service-related information from the policy control network element, including: the session management network element receives PCC rules from the policy control network element, and the PCC rules carry service-related information.

Optionally, the method described in the fourth aspect may further include: the session management network element maps the PCC rule to the QoS flow.

Further, the session management network element maps the PCC rule to the QoS flow, including: the session management network element determines that the service information in the PCC rule is the same as the service information in the existing QoS flow parameter, and maps the PCC rule to the QoS flow parameter. The corresponding QoS flow; or, the session management network element determines that the service information in the PCC rule is different from the service information in the existing QoS flow parameters, creates a QoS flow, and maps the PCC rule to the created QoS flow.

In a possible design solution, the method described in the fourth aspect may also include: the session management network element sending the corresponding relationship between the relevant information of the service and the QoS flow to the terminal, so that the terminal can determine the PER corresponding to the service based on the corresponding relationship, thereby The data packets of the service corresponding to the QoS flow are processed directly based on the PER without identifying the header information corresponding to each data packet, so as to ensure the frame loss rate of the service and the QoS quality of the service through lower overhead.

In addition, for other technical effects of the communication method described in the fourth aspect, reference can be made to the technical effects of the communication methods described in the first to third aspects, which will not be described again here.

The fifth aspect provides a communication method. The method includes: the access network device receives the corresponding relationship between the relevant information of the service from the session management network element and the QoS flow, and determines the PER according to the relevant information of the service, so as to process according to the PER. Process the data packets of the service corresponding to the QoS flow. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate limit, and the frame characteristic information is used to determine the number of data packets in the frame of the service.

In one possible design solution, the access network device processes the data packets of the service corresponding to the QoS flow based on the PER, including: the access network device determines the link configuration corresponding to the QoS flow based on the PER, and based on the link configuration, Send the data packet of the service corresponding to the QoS flow.

In a possible design solution, the frame characteristic information of the service includes at least one of the following: frame period, maximum number of data packets, maximum data burst amount, or data packet period.

Optionally, the frame characteristic information of the service includes at least one of the following: BAT, or time information. BAT is used to indicate the arrival time of the first data packet of the service, and the time information is used to indicate the time of the frame of the service.

Optionally, the method described in the fifth aspect may further include: the access network device determines the data packets in the same frame belonging to the service according to the frame characteristic information of the service. Correspondingly, the access network device processes the data packets of the service corresponding to the QoS flow according to the PER, including: the access network device processes the data packets of the service corresponding to the QoS flow according to the PER and discards the data packet in the same frame.

In one possible design solution, PER is a specified value.

Optionally, the specified value of PER satisfies the following relationship: A/B% ≤ C ≤ A%, the frame loss rate is limited to A%, the number of data packets is B, the specified value of PER is C, and the value of A Greater than 0, B is a positive integer.

In one possible design solution, the access network device determines the PER corresponding to the QoS flow based on service-related information, including: the access network device determines the PER based on the frame loss rate limit information. Alternatively, the access network device determines the PER based on the number of data packets and frame loss rate limit information.

In a possible design solution, the method described in the fifth aspect may also include: the access network device sending the corresponding relationship between the PER and the QoS flow to the terminal, that is, the access network device directly configures the PER of the QoS flow granularity for the terminal. , to reduce terminal overhead and improve battery life. The corresponding relationship is used for the terminal to process data packets of services corresponding to the QoS flow according to the PER.

In a possible design solution, the method described in the fifth aspect may further include: the access network device determines the execution condition of the PER based on the relevant information of the service. The execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Optionally, the method described in the fifth aspect may further include: the access network device adjusts the specified value of PER according to the execution condition of PER, and adjusts the link resources corresponding to the QoS flow according to the adjusted specified value of PER. , thereby sending the data packet of the service corresponding to the QoS flow according to the adjusted link resource.

Further, the method described in the fifth aspect may also include: the access network device sending the execution condition of the PER to the terminal, that is, configuring the execution condition for the terminal through the access network device, so as to reduce terminal overhead and improve battery life.

In addition, for other technical effects of the communication method described in the fifth aspect, reference can be made to the technical effects of the communication methods described in the first to fourth aspects, which will not be described again here.

The sixth aspect is to provide a communication method. The method includes: the terminal receives the corresponding relationship between the PER and the QoS flow from the access network device, or receives the corresponding relationship between the service related information and the QoS flow from the session management network element, so as to process the service corresponding to the QoS flow according to the PER. data pack. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate limit. The frame characteristic information is used to determine the number of data packets in the frame of the service. The PER is determined based on the relevant information of the service.

In one possible design solution, the terminal processes data packets of services corresponding to the QoS flow based on the PER, including: the terminal determines the link configuration corresponding to the QoS flow based on the PER, and sends data of the service corresponding to the QoS flow based on the link configuration. Bag.

Optionally, the method described in the sixth aspect may further include: the terminal determines the data packets in the same frame belonging to the service according to the frame characteristic information of the service. Correspondingly, the terminal processes the data packets of the service corresponding to the QoS flow according to the PER, including: the terminal processes the data packets of the service corresponding to the QoS flow according to the PER and discards the data packets in the same frame.

In one possible design solution, PER is a specified value.

Optionally, the specified value satisfies the following relationship: A/B% ≤ C ≤ A%, the frame loss rate is limited to A%, the number of data packets is B, the specified value is C, the value of A is greater than 0, and B is a positive integer.

In a possible design solution, the method described in the sixth aspect may further include: the terminal determines the PER according to the frame loss rate limit information. Alternatively, the terminal determines the PER based on the number of data packets and frame loss rate limit information.

In a possible design solution, the method described in the sixth aspect may further include: the terminal receiving the execution condition of the PER from the access network device. The execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Optionally, the method described in the sixth aspect may also include: adjusting the specified value of PER according to the execution condition of PER, and adjusting the link resources corresponding to the QoS flow according to the adjusted specified value of PER, so as to adjust the link resource corresponding to the QoS flow according to the specified value after adjustment of PER. After adjusting the link resources, send the data packets of the service corresponding to the QoS flow. In addition, for other technical effects of the communication method described in the sixth aspect, reference can be made to the technical effects of the communication methods described in the first to fifth aspects, which will not be described again here.

The seventh aspect provides a communication method. The method includes: the policy control network element receives service-related information from the application function, and sends the service-related information to the session management network element. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate. Frame rate limit, frame characteristic information is used to determine the number of data packets in the frame of the service. The relevant information of the service is used to determine the PER, and the PER is used by the terminal or access network equipment to process the data packets of the service based on the PER.

In a possible design solution, the policy control network element sends service-related information to the session management network element, including: the policy control network element sends PCC rules to the session management network element, where the PCC rules carry service-related information.

In addition, for other technical effects of the communication method described in the seventh aspect, reference can be made to the technical effects of the communication methods described in the first to sixth aspects, which will not be described again here.

In an eighth aspect, a communication device is provided. The communication device includes: modules for executing the method described in the first aspect, such as a processing module and a transceiver module.

Among them, the processing module is used to obtain the PER corresponding to the service; the transceiving module is used to send the PER to the session management network element. Among them, PER is used by terminals or access network equipment to process service data packets based on PER.

In one possible design solution, PER is a specified value. For example, the specified value of PER satisfies the following relationship: A/B% ≤ C ≤ A%. Among them, the frame loss rate of the service is limited to A%, the number of data packets in the frame of the service is B, the specified value of PER is C, the value of A is greater than 0, and B is a positive integer.

In one possible design solution, the transceiver module is also used to receive PER from the application function. Among them, the PER is determined based on the frame loss rate limit of the service. This PER is used to make the frame loss rate of the service meet the frame loss rate limit when the terminal or access network equipment processes the data packets of the service.

In one possible design solution, the transceiver module is also used to receive the frame loss rate limit information from the application function service; the processing module is also used to determine the PER based on the frame loss rate limit information. Among them, the PER is used to make the frame loss rate of the service meet the frame loss rate limit of the service when the terminal or the access network device processes the data packet of the service.

Optionally, the transceiver module is also used to receive the frame characteristic information of the service from the application function; the processing module is also used to determine the number of data packets in the frame of the service based on the frame characteristic information, and determine the frame loss rate limit of the service The number of data packets within a frame of information and services determines the PER.

Optionally, the frame characteristic information includes at least one of the following: frame period, maximum number of data packets, maximum data burst amount, or data packet period.

Further, the frame characteristic information includes at least one of the following: BAT or time information. Among them, BAT is used to indicate the arrival time of the first data packet of the service. The time information is used to indicate the time of the frame of the service.

Optionally, PER is determined based on frame loss rate limit information. Alternatively, PER is determined based on packet number and frame loss rate limit information.

In one possible design solution, PER is carried in the PCC rules.

In one possible design solution, the transceiver module is also used to send PER execution conditions to the session management network element. The execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Optionally, the execution conditions of PER include at least one of the following: execution condition #1, execution condition #2, or execution condition #3. Execution condition #1 is used to indicate: the specified time includes key frames, and the specified value of PER satisfies the following relationship: A/B%=C; or, the specified time includes non-key frames, and the specified value of PER satisfies the following relationship: A/B%<C≤A%. Execution condition #2 is used to indicate at least one of the following: the specified value of PER is negatively correlated with the number of lost frames, or the specified value of PER is negatively correlated with the number of lost packets. Execution condition #3 is used to indicate: in the case of packet loss within the same frame, the specified value of PER remains unchanged.

Optionally, the transceiver module may include a sending module and a receiving module. The sending module is used to implement the sending function of the communication device described in the eighth aspect, and the receiving module is used to implement the receiving function of the communication device described in the eighth aspect.

Optionally, the communication device according to the eighth aspect may further include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device can execute the communication method described in the first aspect.

It should be noted that the communication device described in the eighth aspect may be a network device, such as a policy control network element, or may be a chip (system) or other component or component that can be disposed in the network device, or may include a network device. device, this application does not limit this.

In addition, the technical effects of the communication device described in the eighth aspect can be referred to the technical effects of the communication method described in the first aspect, which will not be described again here.

In a ninth aspect, a communication device is provided. The communication device includes: modules for performing the method described in the second aspect, such as a receiving module and a sending module.

Among them, the receiving module is used to receive the packet error rate PER corresponding to the service from the policy control network element; the sending module is used to send the corresponding relationship between the PER and the QoS flow to the terminal and/or access network equipment. The corresponding relationship is used for the access network device or terminal to process the data packets of the service corresponding to the QoS flow according to the PER.

In one possible design solution, PER is a specified value.

In a possible design solution, the receiving module is also used to receive PCC rules from the policy control network element, and the PCC rules carry PER.

Optionally, the device described in the ninth aspect may further include: a processing module. This processing module is used to map PCC rules to QoS flows.

Further, the processing module is also used to determine that the PER in the PCC rule is the same as the PER in the existing QoS flow parameter, and map the PCC rule to the QoS flow corresponding to the QoS flow parameter. Alternatively, the processing module is also used to determine that the PER in the PCC rule is different from the PER in the existing QoS flow parameters, create a QoS flow, and map the PCC rule to the created QoS flow.

In one possible design solution, the receiving module is also used to receive the execution conditions of the PER from the policy control network element; The sending module is also used to send the execution conditions of PER to the terminal or access network equipment. Among them, the execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Further, the receiving module is also used to receive PCC rules from the policy control network element. The PCC rules carry the execution conditions of the PER.

Optionally, the sending module and the receiving module can also be integrated into a transceiving module. Wherein, the transceiver module is used to implement the transceiver function of the communication device described in the ninth aspect.

Optionally, the communication device according to the ninth aspect may further include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device can execute the communication method described in the second aspect.

It should be noted that the communication device described in the ninth aspect may be a network device, such as a session management network element, or may be a chip (system) or other component or component that can be disposed in the network device, or may include a network device. device, this application does not limit this.

In addition, the technical effects of the communication device described in the ninth aspect can be referred to the technical effects of the communication method described in the second aspect, which will not be described again here.

In a tenth aspect, a communication device is provided. The communication device includes: modules for performing the method described in the third aspect, such as a processing module and a transceiver module.

Among them, the transceiver module is used to receive the correspondence between the PER and the QoS flow from the session management network element. Among them, the PER corresponds to the business. The processing module is used to process data packets of QoS flow corresponding services based on PER.

In a possible design solution, the processing module is also used to determine the link configuration corresponding to the QoS flow based on the PER, and control the transceiver module to send the data packet of the service corresponding to the QoS flow based on the link configuration.

In one possible design solution, PER is a specified value.

Further, the frame characteristic information includes at least one of the following: BAT or time information. BAT is used to indicate the arrival time of the first data packet of the service, and the time information is used to indicate the time of the frame of the service.

Optionally, the transceiver module is also configured to receive the frame characteristic information of the service; the processing module is also configured to determine the data packets in the same frame belonging to the service based on the frame characteristic information. As well as, the processing module is also used according to PER, and in The method of discarding data packets within the same frame processes the data corresponding to the QoS flow.

In one possible design solution, the transceiver module is also used to receive the execution conditions of the PER from the session management network element. Among them, the execution condition of PER can be used to indicate that when the execution condition is met, PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Optionally, the execution condition includes at least one of the following: execution condition #1, execution condition #2, or execution condition #3. Execution condition #1 is used to indicate: the specified time includes key frames, and the specified value of PER satisfies the following relationship: A/B%=C; or, the specified time includes non-key frames, and the specified value of PER satisfies the following relationship: A/B%<C≤A%. Execution condition #2 is used to indicate at least one of the following: the specified value of PER is negatively correlated with the number of lost frames, or the specified value of PER is negatively correlated with the number of lost packets. Execution condition #3 is used to indicate: in the case of packet loss within the same frame, the specified value of PER remains unchanged.

Optionally, the processing module is also used to adjust the specified value of PER according to the execution conditions of PER, and adjust the link resources corresponding to the QoS flow according to the adjusted specified value of PER, so as to adjust the link resources according to the adjusted link. Resources, control the transceiver module to send data packets corresponding to the QoS flow.

Optionally, the transceiver module may include a sending module and a receiving module. The sending module is used to implement the sending function of the communication device described in the tenth aspect, and the receiving module is used to implement the receiving function of the communication device described in the tenth aspect.

Optionally, the communication device according to the tenth aspect may further include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device can perform the communication method described in the third aspect.

It should be noted that the communication device described in the tenth aspect may be a terminal or network equipment, such as a UE or RAN equipment, or it may be a chip (system) or other component or component that can be disposed in the terminal or network equipment, or it may be It is a device including a terminal or network equipment, which is not limited in this application.

In addition, the technical effects of the communication device described in the tenth aspect can be referred to the technical effects of the communication method described in the third aspect, which will not be described again here.

In an eleventh aspect, a communication device is provided. The communication device includes: modules for performing the method described in the fourth aspect, such as a receiving module and a sending module.

Among them, the receiving module is used to receive relevant information about services from the policy control network element. The sending module is used to send service-related information to the access network device, as well as the correspondence between the service-related information and the QoS flow. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate limit. The frame characteristic information is used to determine the number of data packets in the frame of the service. The relevant information of the service is used to determine the PER. The PER is used for the terminal or interface. The network access device processes service data packets based on the PER.

In one possible design solution, the receiving module is also used to receive PCC rules from the policy control network element. The PCC rules carry business-related information.

Optionally, the device described in the eleventh aspect may further include: a processing module. This processing module is used to convert the PCC regulations into is mapped to the QoS flow.

Further, the processing module is also used to determine that the service information in the PCC rule is the same as the service information in the existing QoS flow parameters, and map the PCC rule to the QoS flow corresponding to the QoS flow parameter; or, the processing module is also used In order to determine that the service information in the PCC rule is different from the service information in the existing QoS flow parameters, a QoS flow is created, and the PCC rule is mapped to the created QoS flow.

In one possible design solution, the sending module is also used to send the corresponding relationship between the service-related information and the QoS flow to the terminal.

Optionally, the sending module and the receiving module can also be integrated into a transceiving module. Wherein, the transceiver module is used to implement the transceiver function of the communication device described in the eleventh aspect.

Optionally, the communication device according to the eleventh aspect may further include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device can perform the communication method described in the fourth aspect.

It should be noted that the communication device described in the eleventh aspect may be a network device, such as a session management network element, or may be a chip (system) or other component or component that can be installed in the network device, or may include a network device. The device of the equipment is not limited in this application.

In addition, the technical effects of the communication device described in the eleventh aspect can be referred to the technical effects of the communication method described in the fourth aspect, which will not be described again here.

In a twelfth aspect, a communication device is provided. The communication device includes: modules for performing the method described in the fifth aspect, such as a processing module and a transceiver module.

Among them, the transceiver module is used to receive the corresponding relationship between the relevant information of the service from the session management network element and the QoS flow; the processing module is used to determine the PER according to the relevant information of the service, so as to process the service corresponding to the QoS flow according to the PER. of data packets. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate limit, and the frame characteristic information is used to determine the number of data packets in the frame of the service.

Optionally, the processing module is also configured to determine the data packets in the same frame belonging to the service based on the frame characteristic information of the service. And, the processing module is also used to process the data packets of the service corresponding to the QoS flow according to the PER and by discarding the data packets in the same frame.

In one possible design solution, PER is a specified value.

In one possible design solution, the processing module is also used to determine the PER based on the frame loss rate limit information. Alternatively, the processing module is also used to determine the PER based on the number of data packets and frame loss rate limit information.

In one possible design solution, the transceiver module is also used to send the corresponding relationship between PER and QoS flows to the terminal. The corresponding relationship is used for the terminal to process data packets of services corresponding to the QoS flow according to the PER.

In one possible design solution, the processing module is also used to determine the execution conditions of PER based on business-related information. The execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Further, the transceiver module is also used to send the execution conditions of PER to the terminal.

Optionally, the transceiver module may include a sending module and a receiving module. Wherein, the sending module is used to realize the sending function of the communication device described in the twelfth aspect, and the receiving module is used to realize the receiving function of the communication device described in the twelfth aspect.

Optionally, the communication device according to the twelfth aspect may further include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device can perform the communication method described in the fifth aspect.

It should be noted that the communication device described in the twelfth aspect may be a network device, such as an access network device, or may be a chip (system) or other components or components that can be installed in the network device, or may include a network device. The device of the equipment is not limited in this application.

In addition, the technical effects of the communication device described in the twelfth aspect can be referred to the technical effects of the communication method described in the fifth aspect, which will not be described again here.

In a thirteenth aspect, a communication device is provided. The communication device includes: modules for performing the method described in the sixth aspect, such as a processing module and a transceiver module.

Among them, the transceiver module is used to receive the correspondence between the PER and the QoS flow from the access network device, or the correspondence between the service-related information from the session management network element and the QoS flow; the processing module is used to process according to the PER Send the data packet of the service corresponding to the QoS flow. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate limit. The frame characteristic information is used to determine the number of data packets in the frame of the service. The PER is determined based on the relevant information of the service.

Optionally, the processing module is also used to determine the number of data in the same frame belonging to the service based on the frame characteristic information of the service. According to the package. And, the processing module is also used to process the data packets of the service corresponding to the QoS flow according to the PER and by discarding the data packets in the same frame. In one possible design solution, PER is a specified value.

In a possible design solution, the transceiver module is also used to receive PER execution conditions from the access network device. The execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Optionally, the transceiver module may include a sending module and a receiving module. The sending module is used to implement the sending function of the communication device described in the thirteenth aspect, and the receiving module is used to implement the receiving function of the communication device described in the thirteenth aspect.

Optionally, the communication device according to the thirteenth aspect may further include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device can perform the communication method described in the sixth aspect.

It should be noted that the communication device described in the thirteenth aspect may be a terminal, such as a terminal, a chip (system) or other components or components that can be installed in the terminal, or a device including a terminal. This application There is no restriction on this.

In addition, the technical effects of the communication device described in the thirteenth aspect can be referred to the technical effects of the communication method described in the sixth aspect, which will not be described again here.

In a fourteenth aspect, a communication device is provided. The communication device includes: modules for performing the method described in the seventh aspect, such as a receiving module and a sending module.

Among them, the receiving module is used to receive service-related information from the application function; the sending module is used to send service-related information to the session management network element. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate limit, and the frame characteristic information is used to determine the number of data packets in the frame of the service. The relevant information of the service is used to determine the PER, and the PER is used by the terminal or access network equipment to process the data packets of the service based on the PER.

Optionally, the frame characteristic information of the service includes at least one of the following: BAT, or time information. BAT is used in the indication industry The arrival time of the first data packet of the service, and the time information is used to indicate the time of the frame of the service.

In a possible design solution, the sending module is also used to send PCC rules to the session management network element, where the PCC rules carry business-related information.

Optionally, the sending module and the receiving module can also be integrated into a transceiving module. The transceiver module is used to implement the transceiver function of the communication device described in the fourteenth aspect.

Optionally, the communication device described in the fourteenth aspect may further include a processing module, which is used to implement the processing function of the communication device.

Optionally, the communication device described in the fourteenth aspect may further include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device can perform the communication method described in the seventh aspect.

It should be noted that the communication device described in the fourteenth aspect may be a network device, such as a PCF network element, or may be a chip (system) or other component or component that can be installed in the network device, or may include a network device. device, this application does not limit this.

In addition, the technical effects of the communication device described in the fourteenth aspect can be referred to the technical effects of the communication method described in the seventh aspect, which will not be described again here.

In a fifteenth aspect, a communication device is provided. The communication device includes: a processor configured to execute the communication method described in any one of the first to seventh aspects.

In a possible design solution, the communication device described in the fifteenth aspect may further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be used for the communication device described in the fifteenth aspect to communicate with other communication devices.

In a possible design solution, the communication device described in the fifteenth aspect may further include a memory. This memory can be integrated with the processor or provided separately. The memory may be used to store computer programs and/or data involved in the communication method described in any one of the first to seventh aspects.

In this application, the communication device described in the fifteenth aspect may be a terminal or a network device, or a chip (system) or other component or component that may be disposed in the terminal or network device, or a device including the terminal or network device. device.

In addition, the technical effects of the communication device described in the fifteenth aspect can be referred to the technical effects of the communication method described in any one of the first to seventh aspects, and will not be described again here.

In a sixteenth aspect, a communication device is provided. The communication device includes: a processor coupled to a memory, and the processor is configured to execute a computer program stored in the memory, so that the communication device executes the communication method described in any one of the first to seventh aspects.

In a possible design solution, the communication device described in the sixteenth aspect may further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be used for the communication device described in the sixteenth aspect to communicate with other communication devices.

In this application, the communication device described in the sixteenth aspect may be a terminal or a network device, or a chip (system) or other component or component that may be disposed in the terminal or network device, or a device including the terminal or network device. device.

In addition, the technical effects of the communication device described in the sixteenth aspect can be referred to the technical effects of the communication method described in any one of the first to seventh aspects, and will not be described again here.

In a seventeenth aspect, a communication device is provided, including: a processor and a memory; the memory is used to store a computer program, and when the processor executes the computer program, the communication device executes the first to seventh aspects medium term The communication method described in one aspect.

In a possible design solution, the communication device described in the seventeenth aspect may further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be used for the communication device described in the seventeenth aspect to communicate with other communication devices.

In this application, the communication device described in the seventeenth aspect may be a terminal or a network device, or a chip (system) or other component or component that may be disposed in the terminal or network device, or a device including the terminal or network device. device.

In addition, the technical effects of the communication device described in the seventeenth aspect can be referred to the technical effects of the communication method described in any one of the first to seventh aspects, and will not be described again here.

In an eighteenth aspect, a communication device is provided, including: a processor. The processor is configured to be coupled to the memory, and after reading the computer program in the memory, execute the communication method as described in any one of the first to seventh aspects according to the computer program.

In a possible design solution, the communication device described in the eighteenth aspect may further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be used for the communication device described in the eighteenth aspect to communicate with other communication devices.

In this application, the communication device described in the eighteenth aspect may be a terminal or a network device, or a chip (system) or other component or component that may be disposed in the terminal or network device, or a device including the terminal or network device. device.

In addition, the technical effects of the communication device described in the eighteenth aspect can be referred to the technical effects of the communication method described in any one of the first to seventh aspects, and will not be described again here.

In a nineteenth aspect, a communication system is provided. The communication system includes: one or more terminals described in the above first to seventh aspects, and one or more network devices.

In a twentieth aspect, a computer-readable storage medium is provided, including: a computer program or instructions; when the computer program or instructions are run on a computer, the computer is caused to execute any one of the first to seventh aspects. communication method.

In a twenty-first aspect, a computer program product is provided, including: a computer program or an instruction, which when the computer program or instruction is run on a computer, causes the computer to execute any one of the steps described in the first to seventh aspects. Communication methods.

Description of drawings

Figure 1 is a schematic diagram of the non-roaming architecture of 5GS;

(a) and (b) in Figure 2 are schematic diagram 1 of the 5GS roaming architecture;

(a) and (b) in Figure 3 are schematic diagram 2 of the 5GS roaming architecture;

Figure 4 is a schematic diagram of a data connection session;

Figure 5 is a schematic diagram of the QoS flow architecture;

Figure 6 is a schematic diagram 2 of the QoS flow architecture;

Figure 7 is a schematic diagram of the architecture of the interoperability between the TSN system and 5GS;

Figure 8 is a schematic diagram of downlink transmission;

Figure 9 is a schematic diagram of the 5GS architecture for TSC services in non-TSN scenarios;

Figure 10 is a schematic diagram of the correspondence between data packets and frames;

Figure 11 is a schematic architectural diagram of a communication system provided by an embodiment of the present application;

Figure 12 is a schematic flowchart 1 of the communication method provided by the embodiment of the present application;

Figure 13 is a schematic flowchart 2 of the communication method provided by the embodiment of the present application;

Figure 14 is a schematic flowchart three of the communication method provided by the embodiment of the present application;

Figure 15 is a schematic flowchart 4 of the communication method provided by the embodiment of the present application;

Figure 16 is a schematic flow chart 5 of the communication method provided by the embodiment of the present application;

Figure 17 is a schematic flow chart 6 of the communication method provided by the embodiment of the present application;

Figure 18 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

Figure 19 is a schematic structural diagram 2 of a communication device provided by an embodiment of the present application;

Figure 20 is a schematic third structural diagram of a communication device provided by an embodiment of the present application.

Detailed ways

To facilitate understanding, the technical terms involved in the embodiments of this application are first introduced below.

1. Fifth generation (5th generation, 5G) mobile communication system (referred to as 5G system (5G system, 5GS)):

Figure 1 is a schematic diagram of the non-roaming architecture of 5GS. As shown in Figure 1, 5GS includes: access network (AN) and core network (core network, CN), and can also include: terminals.

The above-mentioned terminal may be a terminal with a transceiver function, or a chip or chip system that can be installed on the terminal. The terminal can also be called user equipment (UE), access terminal, subscriber unit (subscriber unit), user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, User terminal, terminal, wireless communication device, user agent or user device. The terminal in the embodiment of the present application may be a mobile phone (mobile phone), cellular phone (cellular phone), smart phone (smart phone), tablet computer (Pad), wireless data card, personal digital assistant computer (personal digital assistant, PDA) ), wireless modems, handheld devices, laptop computers, machine type communication (MTC) terminals, computers with wireless transceiver functions, virtual reality (VR) Terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, smart grids Wireless terminals in grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, vehicle-mounted terminals, roadside units with terminal functions (road side unit, RSU) etc. The terminal of this application may also be a vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip, or vehicle-mounted unit built into the vehicle as one or more components or units.

The above-mentioned AN is used to implement access-related functions. It can provide network access functions for authorized users in specific areas, and can determine transmission links of different qualities to transmit user data according to user levels, business needs, etc. The AN forwards control signals and user data between the terminal and the CN. AN may include: access network equipment, which may also be called radio access network equipment (radio access network, RAN) equipment. CN is mainly responsible for maintaining mobile network subscription data and providing terminals with functions such as session management, mobility management, policy management, and security authentication. CN mainly includes the following network elements: user plane function (UPF) network element, authentication server function (AUSF) network element, access and mobility management function (AMF) network element Element, session management function (SMF) network element, network slice selection function (NSSF) network element, network exposure function (NEF) network element, network function repository function (NF repository) function (NRF) network element, policy control function (PCF) network element, unified data management (UDM) network element, unified data repository (UDR), and application function (application function) , AF).

As shown in (a) in Figure 1, the UE accesses the 5G network through the RAN device, and the UE communicates with the AMF network element through the N1 interface (referred to as N1); the RAN network element communicates with the AMF network element through the N2 interface (referred to as N2); The RAN network element communicates with the UPF network element through the N3 interface (referred to as N3); the SMF communicates with the UPF network element through the N4 interface (referred to as N4), and the UPF network element accesses the data network (DN) through the N6 interface (referred to as N6). In addition, the AUSF network element, AMF network element, SMF network element, NSSF network element, NEF network element, NRF network element, PCF network element, UDM network element, UDR network element or AF shown in (a) in Figure 1 Control plane functions use service-based interfaces for interaction. For example, the external service interface provided by the AUSF network element is Nausf; the external service interface provided by the AMF network element is Namf; the external service interface provided by the SMF network element is Nsmf; the external service interface provided by the NSSF is Nnssf; the NEF network The external service interface provided by the NRF network element is Nnef; the external service interface provided by the NRF network element is Nnrf; the external service interface provided by the PCF network element is Npcf; the external service interface provided by the UDM network element is Nudm; the external service interface provided by the UDR network element is Nudm; The service-oriented interface provided is Nudr; the service-oriented interface provided by AF to the outside world is Naf. In addition, as shown in (b) in Figure 1, network elements such as NSSF network element, AUSF network element, UDM network element, UE, RAN network element, PCF network element, and SMF network element can also communicate with AMF network elements. . AUSF network elements can also communicate with UDM network elements, and UDM can also communicate with SMF network elements. In addition to communicating with AMF network elements and UDM network elements, SMF network elements can also communicate with UPF network elements and PCF network elements. PCF network elements can also communicate with AF and NEF network elements. NEF network elements can also communicate with AF. UPF network elements can communicate with RAN equipment and DN. As shown in (b) in Figure 1, "Nxx" between two network elements indicates the interface between the two network elements. For example, N22 represents the interface between NSSF network element and AMF network element, N12 represents the interface between AUSF network element and AMF network element, and N8 represents the interface between UDM network element and AMF network element. We will not list them one by one here. List etc.

RAN equipment may be equipment that provides access to terminals. For example, RAN equipment may include: next-generation mobile communication systems, such as 6G access network equipment, such as 6G base stations, or in the next-generation mobile communication system, the network equipment may also have other naming methods, which are all covered by this application Within the protection scope of the embodiments, this application does not impose any limitations on this. Alternatively, the RAN equipment may also include 5G, such as gNB in the new radio (NR) system, or one or a group (including multiple antenna panels) antenna panels of the base station in 5G, or may also be composed of gNB, transmission point (transmission and reception point, TRP or transmission point, TP) or transmission measurement function (TMF) network node, such as baseband unit (building base band unit, BBU), or centralized unit (centralized unit (CU) or distributed unit (DU), RSU with base station function, or wired access gateway, or 5G core network element. Alternatively, RAN equipment can also include access points (APs) in wireless fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also (called small stations), relay stations, access points, wearable devices, vehicle-mounted devices, etc.

The UPF network element is mainly responsible for user data processing (forwarding, receiving, accounting, etc.). For example, the UPF network element can receive user data from the data network (DN) and forward the user data to the terminal through the access network device. The UPF network element can also receive user data from the terminal through the access network equipment and forward the user data to the DN. DN network element refers to the operator network that provides data transmission services to users. For example, Internet protocol (IP), multimedia service (IP multi-media service, IMS), Internet, etc. The DN can be an operator's external network or a network controlled by the operator, used to provide business services to terminal devices.

The AUSF network element is mainly used to perform terminal security authentication.

AMF network elements are mainly used for mobility management in mobile networks. For example, user location update, user registration network, user switching, etc.

SMF network elements are mainly used for session management in mobile networks. For example, session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users, selecting UPF network elements that provide data packet forwarding functions, etc.

The PCF network element mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is also responsible for obtaining user subscription information related to policy decisions. PCF network elements can provide policies to AMF network elements and SMF network elements, such as quality of service (QoS) policies, slice selection policies, etc.

NSSF network elements are mainly used to select network slices for terminals.

NEF network elements are mainly used to support the opening of capabilities and events.

UDM network elements are mainly used to store user data, such as contract data, authentication/authorization data, etc.

UDR network elements are mainly used to store structured data. The stored content includes contract data and policy data, externally exposed structured data and application-related data.

AF mainly supports interaction with CN to provide services, such as affecting data routing decisions, policy control functions, or providing some third-party services to the network side.

Figure 2 is a schematic diagram of the 5GS roaming architecture, such as the 5G network in the local breakout (LBO) roaming scenario. As shown in Figure 2, the 5G network includes a home public land mobile network (HPLMN) and a visited public land mobile network (VPLMN). HPLMN is the home network of the UE, and VPLMN is the roaming network of the UE. In this scenario, services need to be offloaded at VPLMN, that is, the DN is at VPLMN. Among them, VPLMN and HPLMN communicate through the visited security edge protection proxy (vSEPP) and the home security edge protection proxy (hSEPP).

Among them, as shown in (a) in Figure 2, in VPLMN, the UE accesses the 5G network through the RAN device, and the UE communicates with the AMF network element through the N1 interface (referred to as N1); the RAN device communicates with the AMF network element through the N2 interface (referred to as N2) Communication; RAN equipment communicates with UPF network elements through the N3 interface (referred to as N3); SMF network elements communicate with UPF network elements through the N4 interface (referred to as N4), and UPF network elements access the DN through the N6 interface (referred to as N6). The VPLMN control plane functions such as NSSF network element, NEF network element, AMF network element, SMF network element, NRF network element, PCF network element, or AF shown in (a) in Figure 2 use service-oriented interfaces to interact. For example, the external service interface provided by the AMF network element is Namf; the external service interface provided by the SMF network element is Nsmf; the external service interface provided by the NSSF network element is Nnssf; the external service interface provided by the NEF network element is Nnef; The external service interface provided by the NRF network element is Nnrf; the external service interface provided by the PCF network element is Npcf; and the external service interface provided by the AF is Naf. The HPLMN control plane functions such as UDM, AUSF network element, PCF network element, NRF network element, NSSF network element, or NEF network element shown in (a) of Figure 2 also use service-oriented interfaces for interaction. For example, the external service interface provided by the AUSF network element is Nausf; the external service interface provided by the UDM network element is Nudm, etc. In addition, as shown in (b) of Figure 2, in the LBO roaming scenario, the NSSF network elements, UE, RAN equipment, SMF network elements in the VPLMN, and the AUSF network elements and UDM network elements in the HPLMN can communicate with each other. AMF communication within VPLMN. The SMF network element in the VPLMN can also communicate with the UPF network element, PCF network element (also called vPCF) in the VPLMN, and the UDM network element in the HPLMN. The PCF network element in the VPLMN can also communicate with the AF in the VPLMN and the PCF network element (also called hPCF) in the HPLMN. The UPF network element in the VPLMN can also communicate with the RAN equipment and DN in the VPLMN. “Nxx” between the two network elements shown in (b) of Figure 2 represents the interface between the two network elements, and specific examples will not be given one by one.

Figure 3 is a schematic diagram 2 of the 5GS roaming architecture, such as home routed (HR) roaming scenario. 5G network. As shown in Figure 3, the 5G network includes HPLMN and VPLMN. HPLMN is the home network of the UE, and VPLMN is the roaming network of the UE. VPLMN and HPLMN communicate through vSEPP and hSEPP. Different from the network architecture shown in Figure 2, in the scenario shown in Figure 3, services need to be offloaded at HPLMN, that is, the DN is at HPLMN.

Among them, as shown in (a) of Figure 3, in VPLMN, the UE accesses the 5G network through the RAN device, and the UE communicates with the AMF network element through the N1 interface (referred to as N1); the RAN device communicates with the AMF network element through the N2 interface (referred to as N2). AMF network elements communicate; RAN equipment communicates with UPF network elements through the N3 interface (referred to as N3); SMF network elements communicate with UPF network elements through the N4 interface (referred to as N4). In HPLMN, the UPF network element accesses the DN through the N6 interface (referred to as N6); the UPF network element communicates with the SMF network element through the N4 interface (referred to as N4). And the UPF network element in the VPLMN communicates with the UPF network element in the HPLMN through the N9 interface (referred to as N2). In addition, control plane functions such as the NSSF network element, NEF network element, AMF network element, SMF network element, NRF network element, or PCF network element of the VPLMN shown in (a) of Figure 3 use service-based interfaces for interaction. For example, the external service interface provided by the AMF network element is Namf; the external service interface provided by the SMF network element is Nsmf; the external service interface provided by the NSSF network element is Nnssf; the external service interface provided by the NEF network element is Nnef; The external service interface provided by the NRF network element is Nnrf; the external service interface provided by the PCF network element is Npcf. The HPLMN control plane functions such as UDM network element, AUSF network element, PCF network element, NRF network element, NSSF network element, AF, or NEF network element shown in (a) of Figure 3 also use service-oriented interfaces for interaction. For example, the service-oriented interface provided by the AUSF network element to the outside world is Nausf; the service-oriented interface provided by the UDM network element to the outside world is Nudm; and the service-oriented interface provided by the AF to the outside world is Naf. In addition, as shown in (b) of Figure 3, in the HR roaming scenario, the NSSF network element, UE, RAN equipment, SMF network element, PCF network element in the VPLMN, and the AUSF network element and UDM network in the HPLMN All elements can communicate with the AMF network elements in the VPLMN. The SMF network elements in the VPLMN can also communicate with the UPF network elements in the VPLMN and the SMF network elements in the HPLMN. The PCF network elements in the VPLMN can also communicate with the PCF network elements in the HPLMN. The UPF network elements in the VPLMN can also communicate with the RAN equipment in the VPLMN and the UPF network elements in the HPLMN. The NSSF network elements in the VPLMN can also communicate with the NSSF network elements in the HPLMN. The SMF network element in the HPLMN can also communicate with the UPF network element, UDM network element and PCF network element in the HPLMN. The UDM network element in the HPLMN can also communicate with the AUS network element F in the HPLMN. The PCF network element in the HPLMN can also communicate with the AF in the HPLMN. The UPF network element in the HPLMN can also access the DN communication in the VPLMN. “Nxx” between the two network elements shown in (b) of Figure 3 represents the interface between the two network elements, and specific examples will not be given one by one.

2. QoS:

The UE and the UPF network element can establish a data connection session (such as a protocol data unit (PDU) session, or other sessions, such as an IP-CAN session, etc.). The following is an explanation method, using a PDU session. Take an example to illustrate. For a PDU session, QoS flow (flow) is the smallest granularity that distinguishes QoS. The QoS flow can be a QoS flow that supports guaranteed bit rate (GBR) QoS, or GBR QoS flow, or a QoS flow that supports non guaranteed bit rate (non-GBR) QoS, or QoS flow. non-GBR QoS flow. A PDU session can include multiple QoS flows, for example, it supports up to 64 QoS flows. Each QoS flow has its own corresponding QoS flow identifier (QoS flow ID, QFI) to distinguish different QoS flows. User plane service flows with the same QFI can be mapped to the same QoS flow to process them using the same service forwarding processing method (such as scheduling). In addition, Figure 4 is a schematic diagram of a PDU session. As shown in Figure 4, a PDU session can correspond to multiple radio bearers (radio bearers, RBs) on the air interface, and a radio bearer can include one or Multiple QoS flows, or carry one or more QoS flows.

QoS configuration is at the QoS flow level, that is, QoS flow is used as the granularity for configuration. For example, Figure 5 is a schematic diagram of the QoS flow architecture. As shown in Figure 5, the characteristics of the QoS flow can be represented by some parameters. The SMF network element configures these parameters to pre-configure, establish or modify the corresponding QoS flow. For example, for a QoS flow, these parameters include: QoS configuration (QoS profile) on the RAN device side, QoS rules (QoS rule) on the UE side, and uplink packet detection rules (packet detection rule, PDR) and downlink PDR.

Among them, QoS configuration includes uplink and/or downlink QoS configuration, which is configured by the SMF network element to the RAN device through the N2 interface, or is pre-configured by the RAN device. In one example, the QoS configuration may include: 5G quality identity (5QI), assignment and retain priorities (ARP), guaranteed flow bit rate (GFBR), Maximum flow bit rate (MFBR), maximum packet loss rate (MPLR), and reflective QoS attribute (RQA).

5QI is used to indicate the wireless characteristics of this QoS flow. For example, 5QI includes at least one of the following: resource type, priority, data delay budget (PDB), packet error rate (packet error rate, PER), average window, or maximum data burst (maximum data burst, MDB). Among them, the resource type is used to indicate the type of the QoS flow, such as GBR QoS flow or non-GBR QoS flow. The priority is used to indicate the scheduling priority of the QoS flow on the air interface. Specifically, it can be the priority between QoS flows of different UEs, or the priority between different QoS flows of the same UE. The PDB is used to indicate the upper limit of time that the data packet of this QoS flow may be delayed between the UE and the UPF network element (the UPF network element serving as the N6 termination point). PDB can include: access network data delay (AN PDB) and core network data delay (CN PDB). AN PDB is the data delay between UE and AN, that is, RAN equipment. CN PDB is the data delay between AN and the UPF network element as the N6 termination point. AN PDB can be determined by subtracting CN PDB from PDB. The averaging window is the time period used to determine the GFBR and MFBR of a GBR QoS flow. MDB is used to indicate that AN needs services within the cycle of AN PDB, or the maximum amount of data that needs to be transmitted.

ARP is used to indicate the priority of the QoS flow on the next generation (NG) interface. Specifically, it can be the priority between QoS flows of different UEs, or the priority between different QoS flows of the same UE.

GFBR is used to indicate the guaranteed data rate for GBR QoS flows, including the guaranteed data rate for upstream and the guaranteed data rate for downlink. MFBR is used to indicate the maximum data rate for GBR QoS flows, including the maximum data rate for upstream and the maximum data rate for downstream.

MPLR is used to indicate the maximum packet loss rate that a QoS flow can tolerate. MPLR may only be used for GBR QoS.

The reflective QoS attribute is used to indicate whether the upstream of a non-GBR QoS flow obeys mirror mapping, that is, whether the upstream QoS rules can be derived through reflection of the downstream QoS rules.

Among them, QoS rules are mainly used for classifying and marking uplink user plane data services performed by the UE, for example, associating uplink data to corresponding QoS flows according to QoS rules. The QoS rule may include: the QFI of the QoS flow associated with the QoS rule, the packet filter set (filter list) corresponding to the QoS flow, and the priority of the QoS flow. Among them, the packet filter set is mainly used to associate upstream data with the corresponding QoS flow. For example, Figure 6 is the second architectural diagram of the QoS flow. As shown in Figure 6, if the ID of the uplink data packet matches the ID in the packet filter set, that is, the uplink data packet matches the corresponding QoS rule, the UE will The upstream data packet is associated with the QoS flow corresponding to the QoS rule. If the ID of the uplink data packet does not match the ID in the packet filter set, that is, the uplink data packet does not match the corresponding QoS rule, the UE discards the uplink data. QoS rules can be communicated to the UE by the SMF network element through the N1 interface. Configuration, or pushed out by the UE through the reflective QoS mechanism. For example, if downlink QoS rules are configured, the UE will derive the uplink QoS rules based on the downlink QoS rules. In addition, a QoS flow can have multiple QoS rules. Each PDU session must be configured with a default QoS rule, and the default QoS rule is associated with a QoS flow.

Among them, the uplink PDR and downlink PDR are configured by the SMF network element to the UPF network element through the N4 interface. The uplink PDR is used by the UPF network element to perform classification and labeling of uplink user plane data services. For example, as shown in Figure 6, the UPF network element associates the uplink data to the corresponding QoS flow based on the uplink PDR. The downlink PDR is used by the UPF network element to perform classification and marking of downlink user plane data services. For example, as shown in Figure 6, the UPF network element associates the downlink data to the corresponding QoS flow based on the downlink PDR. If a data packet does not match any uplink PDR or downlink PDR, the UPF network element discards the data packet.

It should be pointed out that the data flow is an IP flow at the IP layer, the data flow is a QoS flow at the non-access stratum (NAS) layer, and the data flow is a data resource at the access stratum (AS) layer. Bearer (data radio bearer, DRB). Therefore, there are two levels of mapping relationships between QoS flows, namely, the mapping relationship between QoS flows and IP flows, and the mapping relationship between QoS flows and DRBs.

3. Mapping mechanism:

The mapping mechanism is the process of associating business data flows with the QoS flows that are considered to transport the business data flows. Among them, the service data flow is defined in the PCC rules through the service data flow (SDF) model. The mapping mechanism includes the following steps:

Step 1, session mapping, that is, one-to-one correspondence between application function session (AF session) and PDU session.

Step 2: PCC rule authorization, that is, the PCF network element authorizes the PCC rule and allocates QoS parameters to the PCC rule.

Step 3, QoS flow mapping, that is, the association of PCC rules with QoS flows in the PDU session. QoS flow mapping is performed using the following mapping parameters: 5QI, ARP, QoS notification control (QNC) (if available in PCC rules), priority (if available in PCC rules), averaging window (if available in PCC rules) ), and maximum data burst volume (MDBV) (if available in PCC rules).

Specifically, when the PCF network element provides the PCC rule, the SMF network element can determine whether there is a QoS flow with the same QoS parameters as the mapping parameters in step 3 above. If such a QoS flow does not exist, the SMF network element uses the parameters in the PCC rule to determine the QoS parameters of the new QoS flow, and establishes a new QoS flow based on the QoS parameters. At this time, the PCC rules are mapped to the new QoS flow. If there is a QoS flow with the same QoS parameters as the mapping parameters, the SMF network element maps the PCC rule to the existing QoS flow. In addition, if the PCF network element requests that the PCC rule be mapped to the QoS flow associated with the default QoS rule, the SMF network element may not perform the above judgment.

In addition, "mapping" is only an exemplary description method, and it can also be replaced by any other possible description, such as "binding", "correspondence", etc., and there is no specific limitation on this.

4. Time sensitive network (TSN): Refer to Figure 7 below for introduction.

Figure 7 is a schematic diagram of the architecture of the interoperability between the TSN system and 5GS. As shown in Figure 7, 5GS (including TSN translator (TT)) as a whole serves as a logical TSN bridge (bridge) for realizing communication between different TSN systems. For the control plane, 5GS can exchange control plane information with nodes in the TSN system through TSN AF (AF capable of communicating with TSN), including: 5GS capability information, TSN configuration information, time scheduling information of TSN input and output ports, and time synchronization Information etc. For the data plane, 5GS uses device-side TSN translator (DS-TT) on the UE side and network-side TSN translator (NW-TT) on the UPF network element side. Exchange data plane information with nodes in the TSN system to achieve communication between different TSN systems. DS-TT may be located within the UE or outside the UE. NW-TT can be located within the UPF network element.

The centralized network configuration (CNC) of the TSN system can configure the arrival time and departure time of the corresponding TSN flow to 5GS for 5GS according to the TSN flow granularity, so that DS-TT or NW-TT can transfer the data of the TSN flow The packet is buffered until the time it leaves 5GS and then sent out, eliminating the impact of uncertainty delays caused by air interface and wired transmission between UE and UPF, ensuring end-to-end, such as from TSN talker to TSN listener ( There is a deterministic delay between listeners).

Taking downlink transmission as an example (refer to uplink transmission for understanding), Figure 8 is a schematic diagram of downlink transmission. As shown in (a) in Figure 8, the downlink data packets are transmitted from the TSN system to the NW-TT, and are transmitted by the NW-TT. After being sent to DS-TT, DS-TT caches the data packet to the sending time window configured by the CNC so that the data packet can be sent out when it leaves 5GS. In this case, in order to catch up with the sending time window configured by the CNC, 5GS needs to determine the corresponding PDB according to the data packet requirements, and ensure that the transmission time of the data packet between the UE and the UPF network element is not greater than the PDB, ensuring that the data packet can be advanced in advance Arrives at DS-TT and buffers at DS-TT until the sending time window. As shown in (b) in Figure 8, TSN AF can obtain the scheduling information of the TSN flow from the CNC and determine the time when the TSN flow arrives at 5GS, that is, the time when the TSN flow arrives at the NW-TT inlet in the downstream direction, or in other words The time when the first data packet in a burst of data of the TSN flow arrives at the NW-TT inlet, that is, the downlink (down link, DL) burst arrival time (DL burst arrival time, DL BAT)). TSN AF can send DL BAT to SMF network element through PCF network element. For example, a time sensitive communication assistance container (TSCAC) carrying the DL BAT is sent to the SMF network element through the PCF network element. The SMF network element can determine the time for the downlink TSN flow to arrive at the RAN device based on the DL BAT and the downlink core network data delay (DL CN PDB), such as adding the DL BAT and DL CN PDB, or the burst of the downlink TSN flow. The time when the first data packet in the transmitted data arrives at the RAN device, and the latest possible time when the UE leaves in the uplink TSN flow, or the latest possible time when the UE leaves in the burst data of the uplink TSN flow. Later possible time. Then, the SMF network element carries this information in the TSCAI. For example, TSCAI includes: flow direction, period, and BAT. The flow direction is used to indicate whether the TSC flow is an upstream TSC flow or a downstream TSC flow. Period refers to the interval between two adjacent BATs. For the downlink, the BAT can be used to indicate the time when the first packet in the burst data of the TSN flow in the downlink direction arrives at the RAN device. Alternatively, for the uplink, the BAT may be used to indicate the latest possible time for the UE to leave the first packet in the burst of data for the uplink TSN flow. Finally, the SMF network element sends TSCAI to the RAN device so that the RAN device reserves resources in advance based on the TSCAI to ensure that the transmission time between the UE and the UPF network element is not greater than the PDB. In addition, in this scenario, the SMF network element can map the delay-sensitive service to a QoS flow, that is, there is a corresponding relationship between the QoS flow and the delay-sensitive service, such as a one-to-one correspondence, to ensure that the delay-sensitive service Data streams can be transmitted normally in 5GS.

It should be pointed out that for TSC services in non-TSN scenarios, 5GS can also be implemented in a TSN-like manner. For example, Figure 9 is a schematic diagram of the 5GS architecture for TSC services in non-TSN scenarios. As shown in Figure 9, the time sensitive communication and time synchronization function (TSCTSF) network element can enable TSC services in non-TSN scenarios. TSC business. For example, the TSCTSF network element can determine TSCAC based on the TSC service type parameters provided by the AF/NEF network element. The TSCTSF network element sends the TSCAC to the PCF network element to configure DS-TT and NW-TT to ensure delay certainty. The specific principle is similar to the above-mentioned TSN, which can be understood by reference and will not be repeated.

5. Business:

With the continuous development of 5GS, its data transmission delay continues to decrease and its transmission capacity becomes larger and larger. Some services with strong real-time performance and large data capacity requirements, such as extended reality (XR), tactile Internet and other services, have been Gradually applied to 5GS. Among them, a typical example of XR is virtual reality (VR). At present, VR has been applied to education, entertainment, military, medical care, environmental protection, transportation, public health and other fields closely related to people's production and life. VR has the advantages of multiple viewing angles and strong interactivity, providing users with a brand new visual experience. As a new business, tactile Internet can realize remote touch applications and remote control of machines, and realize remote perception in terms of vision, hearing, touch, and smell. Tactile Internet has great room for development in industrial automation, medical care, distance education and other related fields. It provides users with a new tactile interactive experience and has great application value and commercial potential.

These services have high QoS requirements to ensure a good user experience. However, because the RAN equipment does not perceive the correspondence between the data packets and frames of these services, the subsequently rendered data often does not correspond to the frames, causing frame drops, frame jumps, or frame lags, or inconsistencies between the images and audio, etc. Affects the QoS quality of the business. For example, Figure 10 is a schematic diagram of the correspondence between data packets and frames. As shown in Figure 10, the RAN device receives data packet #0 in frame #0, decodes and sends data packet #0 to the UE in frame #1, and the UE receives data packet #0 in frame #1. 2 Rendering displays the data corresponding to packet #0. The RAN device receives data packet #1 in frame #1 and frame #2, decodes and sends data packet #1 to the UE in frame #3, and the UE renders and displays the data corresponding to data packet #1 in frame #4. At this time, a display lag occurs, that is, because the reception time of data packet #1 is later than the time when it should be decoded and rendered, the data that should be displayed in frame #3 is delayed until frame #4 is displayed, making Frame #3 still displays the data of the previous frame, and the display screen freezes. The RAN device receives packet #2 in frame #2 and frame #3, receives packet #3 in frame #3, decodes and sends packet #2 and packet #3 to the UE in frame #4. At this time, since data packet #3 is the latest data packet, the data corresponding to data packet #2 is discarded. The UE renders and displays the data corresponding to data packet #3 in frame #4, that is, a display jump occurs (that is, the data is lost). frame), the data that should be displayed in frame #4 is not displayed, but the data that should be displayed in the next frame is displayed, and the display screen freezes.

To address this problem, the current solution is to target services with integrated transmission requirements (such as data packets in the same frame). The business layer notifies the CN of the integrity transmission requirements, and the network elements of the CN, such as SMF Network elements are marked in the QoS configuration. The SMF network element sends the QoS configuration to the RAN device so that the RAN device transmits data packets belonging to the same frame as a whole. The expression form of integrity transmission can be: content integrity transmission, task integrity transmission, event integrity, or object/class integrity. Among them, content integrity can be the intrinsic correlation between multiple dimensions of information, such as multiple data packets corresponding to the same picture frame, the basic layer and enhancement layer corresponding to the same picture frame, or multiple data packets corresponding to the picture frame and audio, etc. wait. In addition, multiple dimensions of information, such as the basic layer and the enhanced layer, may each correspond to different QoS requirements, that is, different QoS, so that integrity transmission may also have scheduling priorities. Task/Event/Object Integrity can be data within the same task that has integrity requirements. For example, in the tactile Internet, when a robotic arm is remotely operated to play basketball, during transmission, multiple data packets corresponding to video, audio, motion, touch, smell and other information have dependencies and correlations.

As an implementation method, frame information can be added to the data packet to indicate the correspondence between the frame and the data packet, that is, data packets with the same frame information belong to the same frame. Add parameters, such as integrity transmission parameters, to the characteristic attributes of the QoS flow to indicate whether integrity transmission is enabled for the service corresponding to the QoS flow. Also, add attributes in 5QI, such as integrity transmission attributes, to indicate whether the service corresponding to the QoS flow enables integrity transmission. In this way, when integrity transmission is turned on, the RAN device can determine which data packets belong to the same frame by parsing the data packets, so that the data corresponding to these data packets can be displayed in the same frame. In this way, the data corresponding to each frame can be displayed or played in order to slow down Solve the situation of frame loss, frame jump, or frame lag, or inconsistency between picture and audio, etc. to ensure the QoS quality of the business. However, this method requires the RAN device to identify the header information corresponding to each data packet, which is very expensive.

In summary, in response to the above technical problems, the embodiments of this application propose the following technical solutions to ensure the QoS quality of services in a low-overhead manner. The technical solutions in this application will be described below with reference to the accompanying drawings.

The technical solutions of the embodiments of this application can be applied to various communication systems, such as wireless fidelity (WiFi) systems, vehicle to everything (V2X) communication systems, device-to-device (D2D) Communication systems, Internet of Vehicles communication systems, 4G, such as LTE systems, global interoperability for microwave access (WiMAX) communication systems, 5G, such as NR systems, and future communication systems, such as the 6th generation , 6G) mobile communication systems, etc.

This application will present various aspects, embodiments, or features in terms of systems, which may include multiple devices, components, modules, etc. It should be understood and appreciated that various systems may include additional devices, components, modules, etc., and/or may not include all devices, components, modules, etc. discussed in connection with the figures. Additionally, a combination of these scenarios can be used.

In addition, in the embodiments of this application, words such as "exemplary" and "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described herein as "example" is not intended to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the word example is intended to present a concept in a concrete way.

In the embodiments of this application, "information", "signal", "message", "channel" and "signaling" can sometimes be used interchangeably. It should be noted that, When the difference is not emphasized, the meanings they convey are consistent. "Of", "corresponding, relevant" and "corresponding" can sometimes be used interchangeably. It should be noted that when the difference is not emphasized, the meanings they convey are consistent. In addition, the "/" mentioned in this application may be used to express an "or" relationship. In the embodiment of this application, "frame" can also be replaced with other similar expressions. For example, a frame may contain multiple different slices. When a slice is transmitted in 5GS, it will be composed of different data packets, such as a set of data packets. Therefore, "frame" can also be replaced by "slice" or "data". "Packet Group (PDU Set)", there is no specific limit on this.

The network architecture and business scenarios described in the embodiments of this application are for the purpose of explaining the technical solutions of the embodiments of this application more clearly, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art will know that with the network With the evolution of architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

In order to facilitate understanding of the embodiments of the present application, the communication system applicable to the embodiments of the present application is first described in detail, taking the communication system shown in FIG. 11 as an example. Exemplarily, FIG. 11 is a schematic architectural diagram of a communication system to which the communication method provided by the embodiment of the present application is applicable.

As shown in Figure 11, this communication system can be applied to the above-mentioned 5GS, and mainly includes: terminals, access network equipment, policy control network elements, and session management network elements. Among them, under the non-roaming architecture of 5GS, the policy control network element can be a PCF network element, and the session management network element can be an SMF network element. Under the LBO architecture of 5GS, the policy control network element can be the PCF network element in the VPLMN, and the session management network element can be the SMF network element in the VPLMN. Under the HR architecture of 5GS, the policy control network element can be the PCF network element in HPLMN, and the session management network element can be the SMF network element in HPLMN. At this time, the terminal or access network device can communicate with the policy control network element and session management network element through the AMF network element and SMF network element in the VPLMN. In addition, the relevant functions of terminals, access network equipment, policy control network elements, and session management network elements can be referred to the relevant introduction in the above 5GS and will not be described again. The communication system can also be applied to future communication systems, such as 6G communication systems, without specific limitations.

In this embodiment of the present application, the policy control network element can configure the PER corresponding to the service for the terminal or access network device through the session management network element, for example, the PER that meets the frame loss rate limit of the service. Alternatively, the policy control network element can also configure the relevant information of the service for the terminal or access network device through the session management network element, so that the terminal or access network device can determine the PER corresponding to the service accordingly. In this way, the terminal or access network equipment can directly process the data packets of the service based on the PER without identifying the header information corresponding to the data packets, thereby ensuring the frame loss rate of the service through lower overhead, thereby ensuring the QoS quality of the service. .

To facilitate understanding, the interaction process between the above-mentioned terminal, access network device, policy control network element and session management network element will be introduced in detail through method embodiments with reference to Figures 12 to 17. In the method embodiment, the UE may be a terminal in the above communication system, the RAN device may be an access network device in the above communication system, the SMF network element may be a session management network element in the above communication system, and the PCF network element may be The policy control network elements in the above communication system. Details are introduced below.

scene 1:

Exemplarily, FIG. 12 is a schematic flowchart 1 of the communication method provided by the embodiment of the present application. In scenario 1, the PCF network element can send the PER corresponding to the service to the SMF network element. The SMF network element uses the QoS flow as the granularity to configure the PER for the UE or RAN device, so that the UE or RAN device processes the QoS flow corresponding to the PER. of the data packets of the service to ensure the frame loss rate of the service, thereby ensuring the QoS quality of the service.

Specifically, as shown in Figure 12, the flow of this communication method is as follows:

S1201, establish a data connection session.

The UE can access the 5G network and initiate a session request. The SMF network element can establish a corresponding data connection session, such as a PDU session, for the UE to ensure that user plane data can be transmitted normally. Among them, the process of establishing a PDU session can refer to the definition in Chapter 4.3.2 of TS23.502 in the 3rd generation partnership project (3GPP), which will not be described again. To facilitate understanding, the following uses a PDU session as an example for introduction.

S1202. The AF sends the relevant information of the service and/or the PER corresponding to the service to the PCF network element. Correspondingly, the PCF network element receives the relevant information of the service from the AF and/or the PER corresponding to the service.

Among them, the business-related information may be related to the needs of the business. The relevant information of the service may include at least one of the following items of the service: frame characteristic information or frame loss rate limit information.

The frame loss rate limit information of the service can be used to indicate that the frame loss rate of the service is less than or equal to the frame loss rate limit of the service, that is, the maximum frame loss rate that the service can accept. Optionally, one expression form of the frame loss rate limit of this service is: the frame loss rate limit of this service is A%, which means that a maximum of A frames can be lost in every 100 frames, and the value of A is greater than 0. For example, the frame loss rate of this service is limited to 10%, which means that a maximum of 1 frame can be lost every 10 frames. For another example, the frame loss rate of this service is limited to 5%, which means that a maximum of 1 frame can be lost every 20 frames. Or, when the terminal or access network equipment defaults to a number of frames as the unit, one expression form of the frame loss rate limit of the service is: the frame loss rate limit of the service is A, which is expressed in the default number of frames. At most A frames can be lost. For example, the default unit is 50 frames, and A is 5, which means that a maximum of 5 frames can be lost every 50 frames. For another example, the default unit is 100 frames, and A is 5, which means that a maximum of 5 frames can be lost every 100 frames. Or, optionally, one expression form of the frame loss rate limit of this service is: one frame is allowed to be lost for every A frame. For example, A is 10, which means that a maximum of 1 frame can be lost every 10 frames.

The frame characteristic information of the service can describe the frame characteristics of the service. The frame characteristic information of the service can be used by the PCF network element to determine the number of data packets in the frame of the service (recorded as the number of data packets in the frame, the same below), such as the maximum number of data packets in the frame, or the average number of data packets in the frame, so that PCF The network element can convert the frame loss rate of the service into the packet loss rate of the service, that is, PER, based on the number of data packets in the frame. For example, the frame characteristic information of the service includes at least one of the following: frame period, maximum data packet quantity, maximum data burst, or packet period. The frame period is similar to the period in TSCAI mentioned above, and is used to indicate the interval between two adjacent frames of the service, that is, the interval between two adjacent bursts. This BAT is similar to the BAT in the above-mentioned TSCAI. The BAT can be used to indicate the time when the first data packet in a burst of data (or a frame) of the service arrives at the RAN device, that is, the downlink BAT. Alternatively, BAT can also be used to indicate the time when the first data packet in a burst of data (or a frame) of the service leaves the UE, such as the latest possible time, that is, the uplink BAT. The maximum number of data packets can refer to the maximum number of data packets within the unit time (or time window) of a frame, and the unit time can be less than or equal to the frame period. The maximum data burst amount can refer to the maximum data amount within the unit time (or time window) of a frame, or the maximum data flow. Packet period can refer to the interval between two adjacent data packets within a frame.

It should be pointed out that although data is sent at intervals of the data packet period, the duration of data sending within a frame does not necessarily last for the entire frame period.

On this basis, the PCF network element can select the parameters it supports to determine the number of data packets in the frame based on the various parameters in the frame characteristic information of the service, so as to avoid causing problems due to the PCF network element not supporting some of the above parameters. The number of packets within a frame cannot be determined to ensure the reliability of the scheme. Among them, the PCF network element can determine the number of data packets in the frame based on the frame period and data packet period. For example, the number of data packets in the frame = frame period/data packet period; or, the PCF network element can determine the number of data packets in the frame based on the maximum number of data packets, such as the number of data packets in the frame = the maximum number of data packets. The PCF network element can also determine the number of data packets in the frame based on the maximum data burst volume. For example, the number of data packets in a frame = maximum data burst/maximum transmission unit (maximum transmission unit, MTU). The MTU may be preconfigured by the PCF network element, or reported by the SMF network element to the PCF network element. The PCF network element can also determine the number of data packets in the frame based on the unit time and data packet period. For example, the number of data packets in a frame = unit time/data packet period.

It can be understood that the above is an example in which the PCF network element determines the number of data packets in the frame by itself, and is not a limitation. For example, the PCF network element can also directly obtain the number of data packets in the frame from the AF.

The PER corresponding to the business (or the demand corresponding to the business) can be determined based on the relevant information of the above business. Among them, the PCF network element can determine the PER corresponding to the service based on the frame loss rate limit information of the service. For example, if the frame loss rate limit of the service is A%, it is determined that the PER is also A%. Alternatively, the PCF network element can also determine the PER corresponding to the service based on the frame loss rate limit information of the service and the number of data packets in the frame. For example, if the frame loss rate of the service is limited to A%, the number of intra-frame data packets is B, and B is a positive integer, then the PER is determined to be A/B%. Among them, PER of A% is a relatively loose packet loss rate condition, while PER of A/B% is a relatively strict packet loss rate condition. Each of the two constitutes a range, such as [A/B%, A%], such that The PCF network element can select a suitable PER within this range, that is, A/B% ≤ C ≤ A%, where C is the specified value of PER to take into account both overhead and business requirements.

It can be understood that to determine the PER by limiting the frame loss rate of the service to A%, it is necessary to first determine that at most one frame can be lost every few frames. Of course, other ways of determining PER can also be used. For example, if the frame loss rate of the service is limited to A%, the number of intra-frame data packets is B, and B is a positive integer. Then it is determined that A%=1-(1-PER)^B, thus further determining It can be seen that the PER determined in this way can accurately represent the correspondence between the loss of a single packet and the loss of the entire frame. Therefore, this calculation method does not require first determining that at most one frame can be lost every few frames.

It should be pointed out that if the PER is A%, it is necessary to ensure that packets are lost within the same frame to meet the frame loss rate limit of the service. For example, take 10 frames, each frame includes 5 data packets. If the frame loss rate of the service is limited to 10% and the PER is 10%, then these 50 data packets can lose up to 5 data packets. At this time, it is necessary to ensure that these 5 data packets belong to the same frame, that is, 1 frame is lost in 10 frames to meet the frame loss rate limit of the service. Otherwise, if these 5 packets belong to different frame, the number of lost frames in these 10 frames will be greater than 1, thus failing to meet the frame loss rate limit of the service. However, if the PER is A/B%, it can obviously meet the frame loss rate limit of the business. For example, taking 10 frames and each frame including 5 data packets as an example, if the frame loss rate limit of the business is 10%, the PER is 10/5%=2%, then these 50 data packets can lose at most 1 data packet, that is, at most 1 frame is lost in 10 frames, which meets the frame loss rate limit of the business.

In addition, the above is an example in which the PCF network element determines the PER on its own, and is not a limitation. For example, the AF can pre-configure the PER corresponding to the service, or the AF can determine the PER corresponding to the service based on the relevant information of the service. In this way, the PCF network element can directly obtain the PER corresponding to the service from the AF, thereby reducing the cost of the PCF network element and improving operating efficiency. For another example, AF can store the relevant information of the service/the PER (requirement) corresponding to the service into the UDR network element, such as through NEF. After the PDU session is established, the PCF network element can obtain the relevant information of the service/the PER (requirement) corresponding to the service from the UDR network element. For example, the PCF network element can send service description information, such as application identifiers or service data flow filters, to the UDR network element. Correspondingly, the UDR network element returns the relevant information of the service/the PER corresponding to the service to the PCF network element according to the service description information.

In the embodiment of this application, for the relevant information of the service sent by the AF and/or the PER corresponding to the service, the AF can reuse the existing message, such as calling any possible service-oriented interface service, such as through the policy authorization (Npcf_PolicyAuthorization) service. Send relevant information of the service and/or PER corresponding to the service to the PCF network element to reduce communication overhead and improve communication efficiency. Alternatively, the AF can also send the relevant information of the service and/or the PER corresponding to the service to the PCF network element through a new service, without any specific limitation.

S1203. The PCF network element sends PER to the SMF network element. Correspondingly, the SMF network element receives the PER from the PCF network element.

Among them, PER can be carried in policy and charging control (PCC) rules to reuse existing cells, reduce communication overhead, and improve communication efficiency. Of course, PER can also be carried in any other possible information element, and there is no specific limitation on this.

S1204: The SMF network element maps the PCC rule to the QoS flow.

Since PCC rules are rules at the granularity of service data flow (SDF), and RAN equipment schedules services at the granularity of QoS flows, the SMF network element needs to map the SDF to the corresponding QoS flow, that is, the PCC rules Map to the corresponding QoS flow (establish the corresponding relationship between PCC rules and the corresponding QoS flow) to ensure the QoS quality of the service with the QoS flow as the granularity.

In one possible way, the SMF network element uses the PER in the PCC rule as a mapping parameter. The SMF network element can determine whether the PER in the PCC rule and the PER in the QoS flow parameters are the same. If the PER in the PCC rule is the same as the PER in the QoS flow parameter, map the PCC rule to the QoS flow corresponding to the QoS flow parameter to reuse the existing QoS flow and reduce overhead. Of course, in this case, other binding parameters in the PCC rules need to be the same. For the specific implementation principles of other mapping parameters, you can refer to the relevant introduction in "3. Mapping Mechanism" above, and will not be described again. Alternatively, if the PER in the PCC rule is different from the PER in the QoS flow parameters, the SMF network element can create a QoS flow and map the PCC rule to the created QoS flow binding to prevent the PCC rule from affecting the existing QoS flow. For example, the parameters of QoS flow #1 include: PER#1, the parameters of QoS flow #2 include: PER#2, and the PCC rule includes: PER#1. In this way, the SMF network element determines that PER#1 in the parameters of QoS flow #1 is the same as PER#1 in the PCC rule, and maps the PCC rule to QoS flow #1. For another example, the parameters of QoS flow #1 include: PER#1, the parameters of QoS flow #2 include: PER#2, and the PCC rule includes: PER#3. In this way, the SMF network element determines that the PER in all QoS flow parameters is different from the PER#3 in the PCC rule, thereby creating a new QoS flow #3 and mapping the PCC rule to QoS flow #3.

Or, in another possible way, the SMF network element may not perform the matching of the above QoS flow parameters with the PCC rules. configuration, directly create an independent QoS flow, and map PCC rules to the independent QoS flow. Optionally, in this case, no other PCC rules are mapped to this QoS flow.

It can be understood that since the PCC rule is bound to the QoS flow, the PER in the PCC rule is the same as the PER of the QoS flow.

S1205. The SMF network element sends the corresponding relationship between PER and QoS flow to the RAN device. Correspondingly, the RAN device receives the correspondence between the PER and the QoS flow from the SMF network element.

The PER may be the PER in the PCC rule mapped in S1204.

One possibility of the correspondence between the SMF network element sending the PER and the QoS flow is: the SMF network element sends the QoS flow identification information and the PER to the RAN device, and the QoS flow identification information corresponds to the PER by default. This correspondence can be carried in existing messages, such as calling any possible service, to achieve signaling multiplexing and improve communication efficiency. Alternatively, the corresponding relationship can also be carried in a newly created message, and there is no specific limitation on this.

Optionally, referring to the introduction in S1202 above, it can be seen that if PER is a relatively loose packet loss rate condition, such as PER is A%, the SMF network element can also send indication information #1 to the RAN device to indicate that the RAN device needs Packets are lost within the same frame to meet the frame loss rate limit of the service. Alternatively, the SMF network element may not send indication information #1 to the RAN device, and the RAN device needs to lose packets in the same frame by default.

S1206: The RAN device processes the data packet of the service corresponding to the QoS flow according to the PER.

The RAN device can determine the PER of the QoS flow based on the corresponding relationship between the PER and the QoS flow. In this way, the RAN device can determine the link configuration corresponding to the QoS flow, or the link layer configuration, based on the PER. For example, the configuration of radio link control (RLC) and/or the configuration of hybrid automatic repeat request (HARQ), or any other possible configuration. In this way, the RAN device can send the data packets of the service corresponding to the QoS flow according to the link configuration to ensure that the packet loss rate of the service can meet the requirements of the PER, thereby ensuring the frame loss rate of the service.

S1207. The SMF network element sends the corresponding relationship between PER and QoS flow to the UE. Correspondingly, the UE receives the correspondence between the PER and the QoS flow from the SMF network element.

Among them, the corresponding relationship between the PER and the QoS flow can be carried in existing messages, such as any possible NAS messages, to achieve signaling multiplexing and improve communication efficiency. Alternatively, the corresponding relationship can also be carried in a newly created message, and there is no specific limitation on this.

Optionally, referring to the introduction in S1202 above, it can be seen that if the PER is a relatively loose packet loss rate condition, such as the PER is A%, the SMF network element can also send indication information #1 to the UE to instruct the UE to send the packet loss rate that needs to be Packets are lost within the same frame to meet the frame loss rate limit of the service. Alternatively, the SMF network element may not send indication information #1 to the UE, and the UE needs to lose packets in the same frame by default.

S1208: The UE processes the data packet of the service corresponding to the QoS flow according to the PER.

The UE can determine the PER of the QoS flow based on the corresponding relationship between the PER and the QoS flow. In this way, the UE can determine the link configuration corresponding to the QoS flow based on the PER. For example, RLC configuration and/or HARQ configuration, or any other possible configuration. In this way, the UE can send data packets of the service corresponding to the QoS flow according to the link configuration to ensure that the packet loss rate of the service can meet the requirements of the PER, thereby ensuring the frame loss rate of the service.

It should be pointed out that the execution order between S1205-S1206 and S1207-S1208 is not limited. S1205-S1206 and S1207-S1208 are optional steps. For example, the SMF network element can only send the corresponding relationship to the RAN, or the SMF network element can only send the corresponding relationship to the UE. In addition, the PER in the corresponding relationship sent by the SMF network element to the RAN is consistent with the SMF network element. The PERs in the corresponding relationship sent by the UE to the UE may be the same or different, and there is no specific limitation on this.

Scenario 2:

Exemplarily, FIG. 13 is a schematic flowchart 2 of the communication method provided by the embodiment of the present application. In scenario 2, the PCF network element can send the PER corresponding to the service and the execution conditions of the PER (recorded as execution conditions) to the SMF network element. SMF network elements use QoS flows as granularity to configure PER and execution conditions for UE or RAN equipment. In this way, the UE or RAN device can obtain the actual packet loss rate or frame loss rate of the service based on the execution conditions, and dynamically select the PER currently corresponding to the QoS flow based on the packet loss rate or frame loss rate to ensure that the PER can meet The current needs of the business, thereby ensuring the frame loss rate of the business.

Specifically, as shown in Figure 13, the flow of this communication method is as follows:

S1301, establish a data connection session.

Among them, the specific implementation principle of S1301 can be referred to the relevant introduction of S1201 above, and will not be described again.

S1302: The AF sends the relevant information of the service and/or the PER corresponding to the service to the PCF network element. Correspondingly, the PCF network element receives the relevant information of the service from the AF and/or the PER corresponding to the service.

The service-related information may be related to the requirements of the service, including at least one of the following: frame loss rate limit information, or frame characteristic information. For the specific implementation principle of the frame loss rate limit information of the service, please refer to the relevant introduction in S1202 above, and will not be described again. The frame characteristic information of the service may include at least one of the following: frame period, maximum number of data packets, maximum data burst amount, or data packet period. For specific implementation principles, please refer to the relevant introduction in S1202 above, which will not be described again. Optionally, the frame characteristic information of the service may include at least one of the following: BAT. BAT can be used to indicate the arrival time of the first data packet of the service. For specific implementation principles, you can also refer to the relevant introduction in 1202 above, which will not be described again.

The PCF network element can determine the PER based on the relevant information of the service. For specific implementation principles, you can also refer to the relevant introduction in 1202 above, which will not be described again. In addition, the PCF network element can also determine the execution conditions based on the relevant information of the service. The execution conditions can be used to indicate the specified value of PER in the case of packet loss or frame loss. Optionally, the execution condition can be used to indicate one of the following: the specified value of PER is negatively correlated with the number of lost frames, the specified value of PER is negatively correlated with the number of lost packets, or the specified value of PER is negatively correlated with the packet loss rate wait. The number of lost frames can be understood as the actual number of lost frames or the instantaneous number of lost frames, the number of lost packets can be understood as the actual number of lost frames or the number of instantaneous lost packets, and the number of lost packets can be understood as the actual number of lost frames or the number of instantaneous lost frames. Packet loss rate. Execution conditions can include: the range of packet loss or frame loss, and the value range of PER. There is a corresponding relationship between these two ranges. For example, execution condition = {(PER#1, number of frames lost/number of packets lost/packet loss rate #1),….(PER#i, number of frames lost/number of packets lost/packet loss rate #i),…. (PER#n, number of frames lost/number of packets lost/packet loss rate #n)}, n is an integer greater than 1, and i is an integer ranging from 1 to n. This execution condition is used to indicate that as one or more of the actual number of frames lost, the number of packets lost, and the frame loss rate increases within the scope allowed by the business, the PER can also gradually change from a relatively loose packet loss rate condition. It becomes a relatively strict packet loss rate condition, so that when frame or packet loss increases, the UE or RAN device can alleviate the frame or packet loss by increasing the PER limit to ensure the QoS quality of the service (see S1306 and S1308).

For example, taking 10 frames and each frame including 5 data packets, if the frame loss rate of the service is limited to 10%, the value range of PER is 2% to 10%, and the number of packet losses allowed by the service is 1 to 10%. 5. In this case, the execution condition = {(PER=10%, the number of packet losses=1), (PER=8%, the number of packet losses=2), (PER=6%, the number of packet losses=3), (PER =4%, the number of lost packets = 4), (PER = 2%, the number of lost packets = 5)}. That is, PER is divided into 5 levels, namely PER is 2%, PER is 4%, PER is 6%, PER is 8%, and PER is 10%. A PER of 10% corresponds to 1 packet loss, a PER of 8% corresponds to 2 packet losses, a PER of 6% corresponds to 3 packet losses, and a PER of 4% corresponds to 4 packet losses. , and a PER of 2% corresponds to 5 packet losses.

Optionally, this execution condition can also be used to indicate that in the case of packet loss within the same frame, the specified value of PER can remain unchanged. In other words, for a frame that has already experienced packet loss, this frame has been lost. At this time, if this frame continues to lose packets, it will not affect the frame loss rate of the service. Therefore, the specified value of PER can be kept unchanged to avoid increasing invalid overhead and improve the operating efficiency of the device.

S1303. The PCF network element sends the PER and execution conditions to the SMF network element. Correspondingly, the SMF network element receives the PER and execution conditions from the PCF network element.

Among them, PER and execution conditions can be carried in PCC rules, such as the same cell or different cells of PCC rules, to reuse existing cells, reduce communication overhead, and improve communication efficiency. Of course, PER and execution conditions can also be carried in any other possible information element, and there is no specific limitation on this.

Optionally, the PCF network element can also send indication information #2 to the UE or RAN device through the SMF network element. Instruction information #2 can indicate the above-mentioned frame characteristic information, such as frame period and BAT, and is used by the UE or RAN device to determine the data packets in the same frame, such as determining how long after the first data packet arrives, all arriving data packets are For data packets in the same frame, the UE or RAN can calculate packet loss at the frame granularity. In this way, if the UE or RAN device determines that packets are lost within the same frame, the specified value of PER remains unchanged according to the above execution conditions. In addition, the indication information #2 may also indicate at least one of the following: data packet period, maximum number of data packets, maximum data burst amount, or number of data packets within a frame, to assist the UE or RAN device in determining the number of data packets within the same frame. data pack. Instruction information #2, the above-mentioned PER and the execution conditions of the PER may be carried in the same cell, such as PCC rules, or may be carried in different cells, and there is no specific limitation on this. Of course, the UE or RAN device can also configure the frame period and BAT locally by default. The PCF network element may not send instruction information #2 to save overhead.

S1304: The SMF network element maps the PCC rule to the QoS flow.

Among them, the SMF network element can use the PER+ execution condition in the PCC rule as a mapping parameter to map the PCC rule to the QoS flow. For example, the SMF network element can determine whether the PER+ execution condition in the PCC rule is the same as the PER+ execution condition in the QoS flow parameter. If the PER+ execution condition in the PCC rule is the same as the PER+ execution condition in the QoS flow parameter, map the PCC rule to the QoS flow corresponding to the QoS flow parameter to reuse the existing QoS flow and reduce overhead. Of course, in this case, other mapping parameters in the PCC rules need to be the same. For the specific implementation principles of other mapping parameters, please refer to the relevant introduction in "3. Mapping Mechanism" above, which will not be described again. Or, if the PER+ execution conditions in the PCC rules are different from the PER+ execution conditions in the QoS flow parameters, the SMF network element can create a QoS flow and map the PCC rules to the created QoS flow to prevent the PCC rules from affecting the existing QoS flows. .

It should be noted that when PER has multiple values and/or multiple execution conditions, these PERs and execution conditions need to be the same before they can be mapped to existing QoS flows. Alternatively, the SMF network element can also map PCC rules (PCC rules containing execution condition #1+PER) to a separate QoS flow. For example, the SMF network element creates an independent QoS flow and maps the PCC rule to the independent QoS flow. flow. Alternatively, the SMF network element can also use the mapping method introduced in S1204 above to map the PCC rules to the corresponding QoS flows. For specific implementation principles, please refer to the relevant introduction in S1204 above, which will not be described again.

S1305. The SMF network element sends execution conditions and the corresponding relationship between PER and QoS flows to the RAN device. Correspondingly, the RAN device receives the execution conditions from the SMF network element and the corresponding relationship between PER and QoS flows.

Among them, one possibility for the SMF network element to send execution conditions and the corresponding relationship between PER and QoS flows is: the SMF network element sends QoS flow identification information, PER and the execution conditions to the RAN device, and the QoS flow identification information is the same as the PER default correspond. Execution conditions and the corresponding relationship can be carried in existing messages, such as any possible service interface messages to achieve signaling reuse and improve communication efficiency. Alternatively, the execution condition and the corresponding relationship can also be carried in a newly created message, without any specific limitation.

Optionally, referring to the introduction in S1202 above, it can be seen that if PER is a relatively loose packet loss rate condition, such as PER is A%, the SMF network element can also send indication information #1 to the RAN device to indicate that the RAN device needs Packets are lost within the same frame to meet the frame loss rate limit of the service. The instruction information #1 and the above-mentioned execution conditions and corresponding relationships may be carried in the same message, or in different messages, and there is no specific limitation on this. Alternatively, the SMF network element may not send indication information #1 to the RAN device, and the RAN device needs to lose packets in the same frame by default.

Optionally, if the SMF network element receives indication information #2 from the PCF network element, the SMF network element can also forward the indication information #2 to the RAN device. The instruction information #2 and the above-mentioned execution conditions and corresponding relationships may be carried in the same message, or may be carried in different messages, and there is no specific limitation on this.

S1306: The RAN device processes the data packet of the service corresponding to the QoS flow according to the PER indicated by the execution condition.

The RAN device can determine the PER of the QoS flow based on the corresponding relationship. The RAN device can determine the current PER according to the execution conditions, and determine the link configuration (uplink or downlink link configuration) corresponding to the QoS flow based on the PER. For example, RLC configuration and/or HARQ configuration, or any other possible configuration. In this way, the RAN device can send the data packets of the service corresponding to the QoS flow according to the link configuration to ensure that the packet loss rate of the service can meet the requirements of the PER, thereby ensuring the frame loss rate of the service. After that, the RAN device can also adjust the specified value of PER according to the execution conditions of PER, and adjust the link resources corresponding to the QoS flow according to the adjusted specified value of PER, so as to send the QoS flow based on the adjusted link resources. The QoS flow corresponds to the data packet of the service to ensure that the frame loss rate of the service always meets the frame loss rate limit.

For example, the RAN device can select a relatively loose PER based on the execution conditions, and determine the link configuration corresponding to the QoS flow based on the relatively loose PER. At this time, the link configuration is also relatively loose, for example, the link resources indicated by the link configuration are relatively few. The RAN device can determine which data packets of the corresponding QoS flow belong to the same frame based on the frame period and BAT; or, the RAN device can also determine which data packets of the corresponding QoS flow belong to the same frame based on the frame information in the data packet. In this way, the RAN device can determine which data packets within the same frame were not sent successfully (ie, packet loss/frame loss) to record one or more of the current packet loss number, packet loss rate, and frame loss number of the QoS flow . Afterwards, as the packet loss or frame loss recorded by the RAN device gradually increases, the RAN device can gradually adjust the relatively loose PER to the relatively strict PER according to the execution conditions, that is, gradually reduce the specified value of PER. In this way, the RAN device can set the link configuration corresponding to the QoS flow based on the specified value after the PER is reduced. At this time, the adjusted link configuration is also relatively strict. For example, the link configuration indicates relatively more link resources to meet the relatively strict PER. Alternatively, if the RAN device determines that packets are lost within the same frame, the RAN device can also keep the specified value of PER unchanged according to the execution conditions. That is, the RAN device can process the data of the service corresponding to the QoS flow according to the PER and by discarding the data packets in the same frame.

S1307. The SMF network element sends execution conditions and the corresponding relationship between PER and QoS flows to the UE. Correspondingly, the UE receives the execution conditions from the SMF network element and the corresponding relationship between PER and QoS flow.

Among them, the execution conditions and the corresponding relationship between PER and QoS flows can be carried in existing messages, such as any possible service-oriented interface messages, to achieve signaling multiplexing and improve communication efficiency. Alternatively, the execution conditions and the corresponding relationship between the PER and the QoS flow can also be carried in the newly created message, and there is no specific limitation on this.

Optionally, referring to the introduction in S1202 above, it can be seen that if the PER is a relatively loose packet loss rate condition, such as the PER is A%, the SMF network element can also send indication information #1 to the UE to instruct the UE to send the packet loss rate that needs to be Packet loss within the same frame, To meet the frame loss rate limit of the business. The instruction information #1 and the above-mentioned execution conditions and corresponding relationships may be carried in the same message, or in different messages, and there is no specific limitation on this. Alternatively, the SMF network element may not send indication information #1 to the UE, and the UE needs to lose packets in the same frame by default.

Optionally, if the SMF network element receives indication information #2 from the PCF network element, the SMF network element can also forward the indication information #2 to the UE. The instruction information #2 and the above-mentioned execution conditions and corresponding relationships may be carried in the same message, or may be carried in different messages, and there is no specific limitation on this.

S1308: The UE processes the data packet of the service corresponding to the QoS flow according to the PER indicated by the execution condition.

The UE can determine the PER of the QoS flow according to the corresponding relationship. The UE can determine the current PER according to the execution conditions, and determine the link configuration (uplink link configuration) corresponding to the QoS flow based on the PER. For example, RLC configuration and/or HARQ configuration, or any other possible configuration. In this way, the UE can send data packets of the service corresponding to the QoS flow according to the link configuration to ensure that the packet loss rate of the service can meet the requirements of the PER, thereby ensuring the frame loss rate of the service. After that, the UE can also adjust the specified value of PER according to the execution conditions of PER, and adjust the link resources corresponding to the QoS flow according to the adjusted specified value of PER, so as to send the QoS according to the adjusted link resources. Stream the data packets of the corresponding service to ensure that the frame loss rate of the service always meets the frame loss rate limit.

For example, the UE can select a relatively loose PER based on the execution conditions, and determine the link configuration corresponding to the QoS flow based on the relatively loose PER. At this time, the link configuration is also relatively loose, for example, the link resources indicated by the link configuration are relatively few. The UE can determine which data packets of the corresponding QoS flow belong to the same frame based on the frame period and BAT; or, the UE can also determine which data packets of the corresponding QoS flow belong to the same frame based on the frame information in the data packet. In this way, the UE can determine which data packets within the same frame were not sent successfully (i.e., packet loss/frame loss) to record one or more of the current packet loss number, packet loss rate, and frame loss number of the QoS flow. Afterwards, as the packet loss or frame loss recorded by the UE gradually increases, the UE can gradually adjust the relatively loose PER to the relatively strict PER according to the execution conditions, that is, gradually reduce the specified value of PER. In this way, the UE can set the link configuration corresponding to the QoS flow according to the specified value after the PER is reduced. At this time, the adjusted link configuration is also relatively strict. For example, the link configuration indicates relatively more link resources to meet the relatively strict PER. Alternatively, if the UE determines that packets are lost within the same frame, the UE can also keep the specified value of PER unchanged according to the execution conditions. That is, the UE can process the data of the service corresponding to the QoS flow according to the PER and by discarding the data packets in the same frame.

In addition, it should be pointed out that the execution order between S1305-S1306 and S1307-S1308 is not limited. S1305-S1306 and S1307-S1308 are optional steps. For example, the SMF network element can only send the execution conditions and the correspondence between PER and QoS flows to the RAN, or the SMF network element can only send the execution conditions and the correspondence between PER and QoS flows to the UE. relation. In addition, the execution conditions sent by the SMF network element to the RAN and the execution conditions sent by the SMF network element to the UE may be the same, or they may be different. For example, the uplink PER value range may be different from the downlink PER value range. At this time, different PER value ranges may correspond to different PERs, that is, the PER sent by the SMF network element to the RAN and the PER sent by the SMF network element to the UE may also be different.

Scene 3:

Exemplarily, FIG. 14 is a schematic flowchart 3 of the communication method provided by the embodiment of the present application. In scenario 3, the PCF network element can send the PER and execution conditions corresponding to the service to the SMF network element. SMF network elements use QoS flows as granularity to configure PER and execution conditions for UE or RAN equipment. In this way, the UE or RAN device can select different PERs corresponding to the QoS flows at different times based on the execution conditions to ensure that the PER can meet the needs of the service at different times, thereby ensuring the frame loss rate of the service.

Specifically, as shown in Figure 14, the flow of this communication method is as follows:

S1401, establish a data connection session.

Among them, the specific implementation principle of S1401 can refer to the relevant introduction of S1201 above, and will not be described again.

S1402. The AF sends the relevant information of the service/PER corresponding to the service to the PCF network element. Correspondingly, the PCF network element receives the relevant information of the service from the AF/the PER corresponding to the service.

The relevant information of the service may be related to the requirements of the service, including at least one of the following: frame loss rate limit information, or frame characteristic information. For the specific implementation principle of the frame loss rate limit information of the service, please refer to the relevant introduction in S1202 above, and will not be described again. The frame characteristic information of the service may include at least one of the following: frame period, maximum number of data packets, maximum data burst amount, or data packet period. For specific implementation principles, please refer to the relevant introduction in S1202 above, which will not be described again. Optionally, the frame characteristic information of the service may include at least one of the following: BAT, or time information.

BAT can be used to indicate the arrival time of the first data packet of the service. For specific implementation principles, you can also refer to the relevant introduction in 1202 above, which will not be described again.

The time information can be used to indicate the time of the service frame (recorded as frame time), such as the time when a certain downlink frame arrives at the RAN device, or the time when a certain uplink frame is sent from the UE. Among them, the frame time can be characterized by absolute time. For example, the total duration of the service is 2 hours, and the indicated frame corresponds to which time within the 2 hours. Alternatively, frame time can also be characterized by relative time. For example, the indicated frame is a frame corresponding to how long before or after a certain reference time of the service. Alternatively, the frame time can be implicitly represented by the frame number. For example, the service includes N frames, the indicated frame is the i-th frame, N is a positive integer, and i ranges from 1 to N. Alternatively, the frame time can also be implicitly represented by the sequence number offset of the frame. For example, the service includes N frames, and there are j frames between the indicated frame and the i-th frame. N is a positive integer, i ranges from 1 to N, j ranges from 1 to N, and i+j≤N. Of course, the time information used to indicate the time of key frames and non-key frames of the service is only an example. The time information can also be used to indicate the time of other types of frames of the service, and there is no specific limitation on this.

The PCF network element can determine the PER based on the relevant information of the service. For specific implementation principles, you can also refer to the relevant introduction in 1202 above, which will not be described again. PCF network elements can also determine execution conditions based on service-related information. For example, execution condition = {(PER#1, time window #1),….(PER#i, time window #i),….(PER#n, time window #n)}, n is an integer greater than 1 , i is an integer ranging from 1 to n. In this way, the execution condition can be used to indicate that the PER is a specified value within a specified time (time window) of the service.

Taking business key frames and non-key frames as an example, key frames can refer to frames that contain relatively important business data, such as frames corresponding to scenes where shots are switched. Non-key frames may refer to frames that contain relatively minor business data, such as frames corresponding to still shots. The PCF network element can determine the designated time containing the key frame based on the time information, and determine that within the designated time, the designated value of PER satisfies the following relationship: A/B%=C, so as to avoid key frame loss as much as possible. The PCF network element can also determine the designated time containing non-key frames based on the time information, and determine that within the designated time, the designated value of PER satisfies the following relationship: A/B%<C≤A%, for example, PER is A% , or use the method in S1302 above to set the specified value of PER in stages to minimize equipment overhead while meeting business needs. That is, the execution condition = {(PER=A/B%, including the specified time of key frames), (A/B%<PER≤A%, including the specified time of non-key frames)}. In addition, the above is based on key frames and non-key frames as examples. The PCF network element can also determine the PER corresponding to other types of frames within a specified time, and there is no specific limitation on this.

It should be pointed out that the sum of the specified times of the business should cover the duration of the entire business to ensure that the business has a corresponding PER at any time.

Optionally, this execution condition can also be used to indicate that in the case of packet loss within the same frame, the specified value of PER remains unchanged. Change. In other words, for a frame that has already experienced packet loss, this frame has been lost. At this time, if this frame continues to lose packets, it will not affect the frame loss rate of the service. Therefore, the specified value of PER can be kept unchanged to avoid invalid overhead and improve equipment operating efficiency.

S1403. The PCF network element sends the PER and execution conditions to the SMF network element. Correspondingly, the SMF network element receives the PER and execution conditions from the PCF network element.

Among them, the specific implementation principle of S1403 can be referred to the relevant introduction of S1303 above, and will not be described again.

S1404: The SMF network element maps the PCC rule to the QoS flow.

It should be noted that when PER has multiple values and/or multiple execution conditions, these PERs and execution conditions need to be the same in order to be mapped to the existing QoS flow. Alternatively, the SMF network element can also map PCC rules (PCC rules including execution conditions + PER) to a separate QoS flow. For example, the SMF network element creates an independent QoS flow and maps the PCC rule to the independent QoS flow. Alternatively, the SMF network element can also use the mapping method introduced in S1204 above to map the PCC rules to the corresponding QoS flows. For specific implementation principles, please refer to the relevant introduction in S1204 above, which will not be described again.

S1405: The SMF network element sends execution conditions and the corresponding relationship between PER and QoS flows to the RAN device. Correspondingly, the RAN device receives the execution conditions from the SMF network element and the corresponding relationship between PER and QoS flows.

Among them, the specific implementation principle of S1405 can be referred to the relevant introduction of S1305 above, and will not be described again.

S1406: The RAN device processes the data packet of the service corresponding to the QoS flow according to the PER indicated by the execution condition.

For example, the RAN device determines, based on the execution conditions, which PER with a specified value to use at the specified time when the service first starts, and determines the link configuration corresponding to the QoS flow based on the PER. After that, the service enters the next designated time, and the RAN device determines which PER with a designated value to use at the next designated time based on the execution conditions, and adjusts the link configuration corresponding to the QoS flow based on the PER. And so on until the end of the business.

For another example, the RAN device can also determine which data packets corresponding to the QoS flow belong to the same frame based on the frame period and BAT; or, the RAN device can also determine which data packets corresponding to the QoS flow based on the frame information in the data packet. belong to the same frame. In this way, the RAN device can determine which data packets within the same frame were not sent successfully (i.e. packet/frame loss). At this time, if the RAN device determines that packets are lost within the same frame, the RAN device can also keep the specified value of PER unchanged according to the execution conditions. That is, the RAN device can process the data of the service corresponding to the QoS flow according to the PER and by discarding the data packets in the same frame.

S1407. The SMF network element sends execution conditions and the corresponding relationship between PER and QoS flows to the UE. The corresponding UE receives the execution conditions from the SMF network element and the corresponding relationship between PER and QoS flow.

Among them, the specific implementation principle of S1407 can be referred to the relevant introduction of S1307 above, and will not be described again.

S1408: The UE processes the data packet of the service corresponding to the QoS flow according to the PER indicated by the execution condition.

For example, based on the execution conditions, the UE determines which PER with a specified value is used at the specified time when the service first starts, and determines the link configuration corresponding to the QoS flow based on the PER. After that, the service enters the next designated time, and the UE determines which PER with designated value to use at the next designated time based on the execution conditions, and adjusts the link configuration corresponding to the QoS flow based on the PER. And so on until the end of the business.

For another example, the UE can also determine which data packets of the corresponding QoS flow belong to the same frame based on the frame period and BAT; or, the UE can also determine which data packets of the corresponding QoS flow belong to the same frame based on the frame information in the data packet. . In this way, the UE can determine which data packets within the same frame were not sent successfully (ie, packet/frame loss). At this time, if the UE determines that packets are lost within the same frame, the UE can also keep the specified value of PER unchanged according to the execution conditions. That is, the UE can process the data of the service corresponding to the QoS flow according to the PER and by discarding the data packets in the same frame.

It should be pointed out that the execution order between S1405-S1406 and S1407-S1408 is not limited. S1405-S1406 and S1407-S1408 are optional steps. For example, the SMF network element can only send the execution conditions and the correspondence between PER and QoS flows to the RAN, or the SMF network element can only send the execution conditions and the correspondence between PER and QoS flows to the UE. relation. In addition, the execution conditions sent by the SMF network element to the RAN and the execution conditions sent by the SMF network element to the UE may be the same, or they may be different. For example, the designated time for uplink and the designated time for downlink may be different, and different designated times may correspond to Different PERs, that is, the PER sent by the SMF network element to the RAN and the PER sent by the SMF network element to the UE can also be different.

In addition, the above solutions can be combined. For example, the solution in scenario 2 and the solution in scenario 3 can be combined and implemented. For example, the SMF network element sends execution conditions to the RAN device or UE. The execution conditions not only include the value range of PER, It also includes the designated time of the business, which will not be described again.

The specific process of the communication method provided by the embodiment of the present application in Scenario 1 to Scenario 3 is described in detail above with reference to Figures 12 to 14. The following describes the overall process of this communication method in Scenario 1-Scenario 3 with reference to Figure 15.

Exemplarily, FIG. 15 is a schematic flowchart 4 of the communication method provided by the embodiment of the present application. The communication method is suitable for communication between terminals, access network equipment, session management network elements, and policy control network elements in the above communication system. As shown in Figure 15, the flow of this communication method is as follows:

S1501. The policy control network element obtains the PER corresponding to the service.

Among them, PER is used for terminals or access network equipment to process service data packets based on PER. The PER is a specified value. In other words, the policy control network element can instruct the terminal or access network equipment which value of PER to use, without the terminal or access network equipment needing to determine or adjust the PER, so as to reduce equipment overhead and improve operating efficiency. For example, if the specified value satisfies the following relationship: A/B% ≤ C ≤ A%, the frame loss rate of the service is limited to A%. Among them, the number of data packets in the service frame (such as one frame) is B, the specified value of PER is C, the value of A is greater than 0, and B is a positive integer. It can be seen that a PER of A% is a relatively loose packet loss rate condition, while a PER of A/B% is a relatively strict packet loss rate condition. Each of the two constitutes a range, such as [A/B%, A%] , so that the PCF network element can select a suitable PER within this range to take into account equipment overhead and business requirements.

In one possible design solution, the policy control network element can receive PER from the application function to reduce the overhead of the policy control network element and improve operating efficiency. Among them, the PER is determined based on the frame loss rate limit of the service. This PER is used to make the frame loss rate of the service meet the frame loss rate limit when the terminal or access network equipment processes the data packets of the service. Wherein, determining the PER according to the frame loss rate limit may be determining the frame loss rate limit as the PER. For example, the frame loss rate is limited to A%, and the PER is also A%, which is used to meet the frame loss rate limit of the service under specific circumstances (such as packet loss within the same frame).

Optionally, the PER may be further determined based on the number of intra-frame data packets of the service. For example, the policy control network element determines the quotient between the frame loss rate limit of the service and the number of data packets in the frame of the service, and determines the quotient value as PER, which is used to detect packet loss in any frame under any circumstances (such as packet loss in any frame). ) meets the frame loss rate limit of the service.

Or, in another possible design solution, the policy control network element can receive the frame loss rate limit information of the service from the application function, and determine the PER based on the frame loss rate limit information. That is to say, the application function can only provide service information, and the policy control network element determines the PER on its own, so as to reduce the overhead of the application function and improve operating efficiency.

Optionally, the policy control network element can also receive frame characteristic information from the service of the application function, and determine the number of data packets in the frame of the service based on the frame characteristic information. Correspondingly, the policy control network element determines the PER based on the frame loss rate limit information, including: the policy control network element determines the PER based on the frame loss rate limit information and the number of data packets in the service frame.

Optionally, the frame characteristic information may include at least one of the following: frame period, maximum number of data packets, maximum data burst amount, or data packet period. Among them, the frame period and data packet period can be used to determine the number of data packets in the frame of the service (recorded as the number of data packets in the frame). For example, the number of data packets in a frame = frame period/packet period; or, the maximum number of data packets can also be used to determine the number of data packets in a frame, such as the number of data packets in a frame = the maximum number of data packets; or, the maximum number of data bursts It can also be used to determine the number of data packets in a frame, such as the number of data packets in a frame = maximum data burst/MTU. In this way, the policy control network element can select parameters that it can recognize to determine the number of data packets in the frame, to avoid being unable to determine the number of data packets in the frame because the policy control network element does not support some of the above parameters, so as to ensure the reliability of the solution. sex. Moreover, in this case, determining the PER based on the number of data packets in the frame can also ensure that the frame loss rate of the service meets the frame loss rate limit under any circumstances.

And, the frame characteristic information may also include at least one of the following: BAT, or time information. Among them, BAT is used to indicate the arrival time of the first data packet of the service. In this way, the terminal or access network equipment can determine the data packets belonging to the same frame based on the frame characteristic information, thereby achieving a more accurate calculation of the packet loss rate of the service at the frame granularity. For example, the terminal or access network device determines how long after the first data packet arrives, all arriving data packets are data packets in the same frame. In addition, the time information may be used to indicate the time of the frame of the service (denoted as frame time). In this way, the terminal or access network equipment can also use different PERs at different times based on time information to take into account equipment overhead and business requirements. For example, for non-key frames of the service within certain periods of time, the PER determined based on the frame loss rate limit information can be used to save overhead; for For the key frames of the business within certain periods of time, PER can be further determined based on the number of data packets in the frame to avoid key frame frame loss and ensure business needs.

In one possible design solution, PER can be carried in the policy and charging control PCC rules to achieve cell reuse and improve communication efficiency.

In addition, for the specific implementation principle of S1501, you can also refer to the relevant introductions in S1202, S1302, and S1402 above, which will not be described again.

S1502. The policy control network element sends the PER to the session management network element. Correspondingly, the session management network element receives the PER from the policy control network element.

Among them, PER can be carried in PCC rules. That is, the policy control network element sends the PCC rule to the session management network element, and accordingly, the session management network element receives the PCC rule from the policy control network element, and the PCC rule carries the PER.

Optionally, the policy control network element can also send the execution conditions of the PER to the session management network element. The execution condition may be determined by the policy control network element. This execution condition can be used to indicate that when the execution condition is met, PER will take a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the case of packet loss or frame loss, so that the terminal or access network device can Select appropriate execution conditions under corresponding circumstances to take into account equipment overhead and business needs.

For example, the execution conditions of PER include at least one of the following: execution condition #1, execution condition #2, or execution condition #3. Execution condition #1 is used to indicate: the specified time includes key frames, and the specified value of PER satisfies the following relationship: A/B%=C, so as to avoid key frame loss as much as possible; or, the specified time includes non-key frames, The specified value of PER satisfies the following relationship: A/B%<C≤A%, so as to minimize equipment overhead while meeting business requirements. Execution condition #2 is used to indicate at least one of the following: the specified value of PER is negatively correlated with the number of lost frames, or the specified value of PER is negatively correlated with the number of lost packets. That is to say, as the number of frame loss and/or packet loss increases within the allowable range of the business, the PER gradually changes from a relatively loose packet loss rate condition to a relatively strict packet loss rate condition, achieving better performance in frame loss or packet loss. In the case of increased traffic, increase the PER limit to alleviate frame or packet loss to ensure the QoS quality of the business. Execution condition #3 is used to indicate: in the case of packet loss within the same frame, the specified value of PER remains unchanged. For example, when the terminal or access network device calculates packet loss at frame granularity, if the terminal or access network device determines that packet loss occurs within the same frame, the specified value of PER can be kept unchanged according to execution condition #3. Change. In other words, for a frame that has already experienced packet loss, this frame has been lost. At this time, if this frame continues to lose packets, it will not affect the frame loss rate of the service. Therefore, the specified value of PER can be kept unchanged to avoid increasing the invalid overhead of the device and improve operating efficiency.

Optionally, the execution conditions of PER can also be carried in PCC rules. That is, the policy control network element sends the PCC rule to the session management network element, and accordingly, the session management network element receives the PCC rule from the policy control network element, and the PCC rule carries the execution condition of the PER.

In addition, the specific implementation principle of S1502 can also refer to the relevant introductions in S1203, S1303, and S1403 above, and will not be described again.

S1503. The session management network element sends the corresponding relationship between PER and QoS flow to the terminal and/or access network device. Correspondingly, the terminal and/or the access network device receive the corresponding relationship between the PER and the QoS flow from the session management network element.

Among them, the session management network element can map PCC rules to QoS flows to ensure the QoS quality of services at the granularity of QoS flows. For example, the session management network element can determine that the PER in the PCC rule is the same as the PER in the existing QoS flow parameters, and map the PCC rule to the QoS flow corresponding to the QoS flow parameter to reuse the existing QoS flow and reduce overhead. . Alternatively, the session management network element may determine that the PER is different from the PER in the existing QoS flow parameters and create QoS flow, map PCC rules to the created QoS flow to prevent PCC rules from affecting existing QoS flows. Afterwards, the session management network element can send the corresponding relationship (ie, mapping relationship) between the PER and the QoS flow to the terminal and/or the access network device.

Optionally, the session management network element can also send execution conditions to the terminal or access network device respectively. Correspondingly, the terminal or access network device can receive execution conditions from the session management network element.

In addition, the specific implementation principle of S1503 can also refer to the relevant introductions in the above-mentioned S1204-S1205, S1207, S1304-S1305, S1307, and S1404-S1405, S1407, which will not be described again.

S1504: The terminal or access network device processes data packets of services corresponding to the QoS flow according to the PER.

Among them, the terminal or access network device can determine the link configuration corresponding to the QoS flow based on the PER, and send the data packets of the service corresponding to the QoS flow according to the link configuration to ensure that the frame loss rate of the service meets the frame loss rate limit. . Optionally, the terminal or access network equipment can also adjust the specified value of PER according to the execution conditions of PER, and adjust the link resources corresponding to the QoS flow according to the adjusted specified value of PER, so as to adjust the link resources corresponding to the QoS flow according to the adjusted specified value. Link resources, send the data packets of the service corresponding to the QoS flow to ensure that the frame loss rate of the service always meets the frame loss rate limit. Optionally, the terminal or the access network device can also receive the frame characteristic information of the service, and determine the data packets in the same frame belonging to the service based on the frame characteristic information. In this way, the terminal or access network equipment can process the data of the service corresponding to the QoS flow based on the PER and discard the data packets in the same frame to ensure that the frame loss rate of the service meets the frame loss rate limit.

In addition, the specific implementation principle of S1504 can also refer to the relevant introductions in the above-mentioned S1206 and S1208, S1306 and S1308, S1406 and S1408, and will not be described again. Of course, terminals and access network equipment can also use other methods to ensure the frame loss rate limit, which is not specifically limited in the embodiments of this application.

In summary, based on the methods introduced in Scenario 1 to Scenario 3 above, by configuring the PER corresponding to the service for the terminal or access network device, such as the PER that meets the frame loss rate limit of the service, the terminal or access network device can directly configure the PER according to the service. PER processes the data packets of this service without identifying the header information corresponding to the data packets, so as to ensure the frame loss rate of the service and the QoS quality of the service through lower overhead.

Scene 4:

For example, FIG. 16 is a schematic flowchart 5 of the communication method provided by the embodiment of the present application. In scenario 4, the PCF network element can send service-related information to the SMF network element. The SMF network element uses the QoS flow as the granularity to configure the relevant information of the service for the UE or RAN device. In this way, the UE or RAN device can determine the PER corresponding to the service based on the relevant information of the service, thereby ensuring the frame loss rate of the service.

Specifically, as shown in Figure 16, the flow of this communication method is as follows:

S1601, establish a data connection session.

Among them, the specific implementation principle of S1601 can be referred to the relevant introduction of S1201 above, and will not be described again.

S1602: AF sends service-related information to the PCF network element. Correspondingly, the PCF network element receives service-related information from the AF.

The service-related information may be related to the requirements of the service, including at least one of the following: frame loss rate limit information, or frame characteristic information. For the specific implementation principle of the frame loss rate limit information of this service, please refer to the relevant introduction in S1202 above, and will not be described again. For the specific implementation principle of the frame feature information of this service, please refer to the relevant introductions in S1202, S1302 and S1402 above, and will not be described again.

S1603: The PCF network element sends service-related information to the SMF network element. Correspondingly, the SMF network element receives service-related information from the PCF network element.

Among them, business-related information can be carried in PCC rules to reuse existing cells, reduce communication overhead, and improve communication efficiency. Of course, service-related information can also be carried in any other possible information element, and there is no specific limitation on this.

Optionally, the PCF network element can also send indication information #2 to the UE or RAN device through the SMF network element. For specific implementation principles, please refer to the relevant introduction in S1303 above, which will not be described again.

S1604: The SMF network element maps the PCC rule to the QoS flow.

In one possible way, the SMF network element can determine whether the service information in the PCC rules, such as 5QI, ARP, etc., is the same as the service information in the QoS flow parameters. If the service information in the PCC rule is the same as the service information in the QoS flow parameter, map the PCC rule to the QoS flow corresponding to the QoS flow parameter. Alternatively, if the service information in the PCC rule is different from the service information in the QoS flow parameters, the SMF network element can create a QoS flow and map the PCC rule to the created QoS flow. For example, QoS flow parameters include: parameters of QoS flow #1 and parameters of QoS flow #2. The parameters of QoS flow #1 include: ARP#1, the parameters of QoS flow #2 include: ARP#2, and the PCC rule includes: ARP#1. In this way, the SMF network element determines that ARP#1 in the parameters of QoS flow #1 is the same as ARP#1 in the PCC rule, and maps the PCC rule to QoS flow #1. For another example, the QoS flow parameters include: parameters of QoS flow #1 and parameters of QoS flow #2. The parameters of QoS flow #1 include: ARP#1, the parameters of QoS flow #2 include: ARP#2, and the PCC rule includes: ARP#3. In this way, the SMF network element determines that the ARP in all QoS flow parameters is different from ARP#3 in the PCC rule, thereby creating QoS flow #3 and mapping the PCC rule to QoS flow #3.

Or, in another possible way, the SMF network element may directly create a QoS flow without performing the above matching of service information, and map the PCC rules to the created QoS flow.

It can be understood that since the PCC rule has a mapping relationship with the QoS flow, the relevant information of the service in the PCC rule and the QoS flow also have a corresponding corresponding relationship, for example, the relevant information of the service and the identifier of the QoS flow, such as QoS Corresponds to the ID of the stream.

In addition, for the convenience of understanding, the specific implementation principle of S1604 can also refer to the relevant introduction in "3. Mapping Mechanism" above.

S1605: The SMF network element sends the corresponding relationship between the service-related information and the QoS flow to the RAN device. Correspondingly, the RAN device receives the correspondence between the service-related information and the QoS flow from the SMF network element.

Among them, the corresponding relationship between business-related information and QoS flows can be carried in existing messages, such as any possible service-oriented interface messages, to achieve signaling multiplexing and improve communication efficiency. Alternatively, the corresponding relationship between the service-related information and the QoS flow can also be carried in the newly created message, and there is no specific limitation on this.

S1606: The RAN device determines the PER corresponding to the service based on the relevant information of the service, and processes the data packet of the service corresponding to the QoS flow based on the PER.

The RAN device can determine the PER corresponding to the service based on the relevant information of the service, and determine the PER of the QoS flow based on the corresponding relationship between the relevant information of the service and the QoS flow. In this way, the RAN device can process the data packets of the service corresponding to the QoS flow based on the PER. For specific implementation principles, please refer to the relevant introductions in Scenario 1 to Scenario 3 above, which will not be described again.

Optionally, the RAN device can also determine the execution conditions based on the relevant information of the service, so that the RAN device can select the specified value of PER based on the execution conditions. For specific implementation principles, you can also refer to the relevant introductions in Scenario 1 to Scenario 3 above. No longer.

S1607: The SMF network element sends the corresponding relationship between the service-related information and the QoS flow to the UE. Correspondingly, the UE receives the correspondence between the service-related information and the QoS flow from the SMF network element.

Among them, the corresponding relationship between business-related information and QoS flows can be carried in existing messages, such as any possible NAS messages, to achieve signaling multiplexing and improve communication efficiency. Alternatively, the corresponding relationship between the service-related information and the QoS flow can also be carried in the newly created message, and there is no specific limitation on this.

S1608: The UE determines the PER corresponding to the service based on the relevant information of the service, and processes the data packet of the service corresponding to the QoS flow based on the PER.

The UE can determine the PER corresponding to the service based on the relevant information of the service, and the PER of the QoS flow based on the corresponding relationship between the relevant information of the service and the QoS flow. In this way, the UE can process the data packets of the service corresponding to the QoS flow based on the PER. For specific implementation principles, please refer to the relevant introductions in Scenario 1 to Scenario 3 above, which will not be described again.

Optionally, the UE can also determine the execution conditions based on the relevant information of the service, so that the UE can select the designated value of PER according to the execution conditions. For specific implementation principles, you can also refer to the relevant introductions in Scenario 1 to Scenario 3 above. Repeat.

It should be pointed out that the execution order between S1605-S1606 and S1607-S1608 is not limited. S1607-S1608 are optional steps. For example, the SMF network element can only send the correspondence between service-related information and QoS flows to the RAN device. Optionally, the RAN device can also send the corresponding relationship between the service-related information and the QoS flow to the UE, so that the UE can determine the PER corresponding to the service based on the corresponding relationship. Alternatively, the RAN device can send the corresponding relationship between the PER and the QoS flow to the UE, that is, the RAN device can directly configure the PER of the QoS flow granularity for the UE, so as to reduce the UE overhead and improve the battery life. Optionally, the RAN device can also send execution conditions to the UE, that is, the RAN device can directly configure execution conditions for the UE, thereby reducing UE overhead and improving battery life.

The specific process of the communication method provided by the embodiment of the present application in Scenario 4 is described in detail above with reference to FIG. 16 . The following describes the overall process of this communication method in scenario 4 with reference to Figure 17.

Exemplarily, FIG. 17 is a schematic flowchart 6 of the communication method provided by the embodiment of the present application. The communication method is suitable for communication between terminals, access network equipment, session management network elements, and policy control network elements in the above communication system. As shown in Figure 17, the flow of this communication method is as follows:

S1701. The policy control network element receives service-related information from the application function.

The service-related information includes at least one of the following: frame characteristic information or frame loss rate limit information. The frame characteristic information is used to determine the number of data packets in the frame of the service. For example, the frame characteristic information includes at least one of the following: frame period, maximum number of data packets, maximum data burst amount, or data packet period. Optionally, the frame characteristic information may also include at least one of the following: BAT, or time information. Among them, BAT is used to indicate the arrival time of the first data packet of the service. The time information is used to indicate the time of the frame of the service. The frame loss rate limit information is used to indicate that the frame loss rate of the service is less than or equal to the frame loss rate limit.

In addition, for the specific implementation principle of S1701, you can also refer to the relevant introductions in S1202, S1302, and S1402 above, which will not be described again.

S1702: The policy control network element sends service-related information to the session management network element. Correspondingly, the session management network element receives service-related information from the policy control network element.

Among them, business-related information is carried in PCC rules. That is, the policy control network element sends the PCC rule to the session management network element. Correspondingly, the session management network element receives the PCC rule from the policy control network element, and the PCC rule carries service-related information.

In addition, the specific implementation principle of S1702 can also refer to the relevant introductions in S1203 and S1303 above, and will not be described again.

S1703. The session management network element sends the corresponding relationship between the service-related information and the QoS flow to the access network device. corresponding , the access network device receives the corresponding relationship between the service-related information from the session management network element and the QoS flow.

Among them, the session management network element can map PCC rules to QoS flows. For example, the session management network element determines that the service information in the PCC rule is the same as the service information in the existing QoS flow parameters, and maps the PCC rule to the QoS flow corresponding to the QoS flow parameter; or the session management network element determines that the service information in the PCC rule is the same. The service information is different from the service information in the existing QoS flow parameters. Create a QoS flow and map the PCC rules to the created QoS flow. In this way, the session management network element can send the corresponding relationship (that is, the mapping relationship) between the service-related information and the QoS flow to the access network device.

In addition, the specific implementation principle of S1703 can also refer to the relevant introduction in S1604-S1605 above, and will not be described again.

S1704: The access network device determines the PER based on the relevant information of the service, and processes the data packets of the service corresponding to the QoS flow based on the PER.

Among them, the access network device can determine the PER based on the frame loss rate limit information. Alternatively, the access network device determines the PER based on the number of data packets and frame loss rate limit information. The PER can take a specified value. The specified value of the PER satisfies the following relationship: A/B% ≤ C ≤ A%. The frame loss rate of the service is limited to A%, the number of data packets in the frame of the service is B, the specified value of PER is C, the value of A is greater than 0, and B is a positive integer. In this way, the access network device can determine the link configuration corresponding to the QoS flow based on the PER, and send the data packet of the service corresponding to the QoS flow according to the link configuration.

Optionally, the access network device determines execution conditions based on service-related information. The execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss. For example, the execution condition includes at least one of the following: execution condition #1, execution condition #2, or execution condition #3. Execution condition #1 is used to indicate that within the specified time of the service, PER is the specified value, execution condition #2 is used to indicate the specified value of PER in the case of packet loss or frame loss, and execution condition #3 is used to indicate that PER is in the specified time. Specified value in case of continuous packet loss. For example, execution condition #1 is used to indicate: the specified time includes key frames, and the specified value of PER satisfies the following relationship: A/B%=C; or, the specified time includes non-key frames, and the specified value of PER satisfies the following relationship: Relationship: A/B%<C≤A%. Execution condition #2 is used to indicate at least one of the following: the specified value of PER is negatively correlated with the number of lost frames, or the specified value of PER is negatively correlated with the number of lost packets. Execution condition #3 is used to indicate: in the case of packet loss within the same frame, the specified value of PER remains unchanged. Of course, the access network equipment can also use other methods to ensure the frame loss rate limit, which is not specifically limited in the embodiments of this application. In this way, the access network device can adjust the specified value of PER according to the execution conditions of PER, and adjust the link resources corresponding to the QoS flow according to the adjusted specified value of PER, thereby sending the QoS flow according to the adjusted link resources. This QoS flow corresponds to the data packet of the service.

Optionally, the access network device can also determine the data packets in the same frame belonging to the service based on the frame characteristic information of the service. In this way, the access network device can process the data packets of the service corresponding to the QoS flow according to the PER and by discarding the data packets in the same frame.

In addition, the specific implementation principles of S1704 can be referred to the relevant introductions in Scenario 1 to Scenario 3 above, and will not be described again.

S1705: The session management network element sends the corresponding relationship between the service-related information and the QoS flow to the terminal. Correspondingly, the terminal receives the correspondence between the service-related information and the QoS flow from the session management network element.

Among them, the specific implementation principle of S1705 can also refer to the above-mentioned S1607, as well as the relevant introduction in the above-mentioned Scenario 1 to Scenario 3, and will not be described again.

S1706: The access network device sends the corresponding relationship between PER and QoS flow to the terminal. Correspondingly, the terminal receives the correspondence between the PER and the QoS flow from the access network device.

On this basis, optionally, the access network device can also send execution conditions to the terminal. Correspondingly, the terminal receives Execution conditions for self-access network equipment.

In addition, the specific implementation principle of S1706 can be referred to the relevant introduction in Scenario 4 above, and will not be described again.

It should be pointed out that S1705 and S1706 are optional steps, that is, configuring service-related information for the terminal so that the terminal can determine the PER by itself, and/or you can also directly configure the PER for the terminal. In addition, the terminal can also use other methods to ensure the frame loss rate limit, which is not specifically limited in the embodiments of this application.

S1707: The terminal processes data packets of services corresponding to the QoS flow according to the PER.

Among them, the terminal can determine the PER corresponding to the service according to the relevant information of the service, and map the PER to the QoS flow according to the corresponding relationship between the relevant information of the service and the QoS flow. In this way, the terminal can process data packets of services corresponding to the QoS flow according to the PER. For example, the terminal can determine the link configuration corresponding to the QoS flow based on the PER, and send the data packet of the service corresponding to the QoS flow based on the link configuration.

Optionally, the terminal can also determine the execution conditions of the PER based on service-related information. In this way, the terminal can also adjust the specified value of PER according to the execution conditions of PER, and adjust the link resources corresponding to the QoS flow according to the adjusted specified value of PER, thereby sending the QoS according to the adjusted link resources. The flow corresponds to the data packet of the service.

Optionally, the terminal can also determine the data packets in the same frame belonging to the service based on the frame characteristic information in the relevant information of the service. In this way, the terminal can also process the data packets of the service corresponding to the QoS flow according to the PER and by discarding the data packets in the same frame.

Among them, the specific implementation principle of S1707 can be referred to the relevant introduction in Scenario 1 to Scenario 3 above, and will not be described again.

In summary, based on the method introduced in Scenario 4 above, by configuring service-related information for the access network device, the access network device can determine the PER corresponding to the service, such as the PER that meets the frame loss rate limit of the service. In this way, the access network device can directly send the data packet of the service based on the PER without identifying the header information corresponding to the data packet, thereby ensuring the frame loss rate of the service and ensuring the QoS quality of the service through lower overhead.

It should be pointed out that the core network, such as the PCF network element, can also choose the configuration method introduced in Scenario 1 to Scenario 3, or the configuration method introduced in Scenario 4 according to the capabilities of the RAN device or UE. For example, if the capabilities of the RAN equipment or UE are relatively weak, choose the configuration method introduced in Scenario 1-Scenario 3, that is, configure PER on the PCF network element. If the capabilities of the RAN device or UE are relatively strong, choose the configuration method introduced in Scenario 4, that is, configure the relevant information of the PCF network element service, and the UE or RAN device determines the PER on its own.

The communication method provided by the embodiment of the present application is described in detail above with reference to Figures 12-17. The communication device used to perform the communication method provided by the embodiment of the present application will be described in detail below with reference to FIGS. 18-20.

In some embodiments, the communication device is applicable to the above scenarios 1 to 3. Details are introduced below.

For example, Figure 18 is a schematic structural diagram of a communication device provided by an embodiment of the present application. As shown in Figure 18, the communication device 1800 may include some functional modules for executing the PCF network elements in the above scenarios 1 to 3, or Policies control the functions of network elements. For example, the communication device 1800 includes: a transceiver module 1801 and a processing module 1802.

Among them, the processing module 1802 is used to obtain the PER corresponding to the service; the transceiving module 1801 is used to send the PER to the session management network element. Among them, PER is used by terminals or access network equipment to process service data packets based on PER.

In one possible design solution, PER is a specified value. For example, the specified value satisfies the following relationship: A/B% ≤ C ≤ A%. Among them, the frame loss rate of the service is limited to A%, the number of data packets in the frame of the service is B, the specified value of PER is C, the value of A is greater than 0, and B is a positive integer.

In a possible design solution, the transceiver module 1801 is also used to receive the PER from the application function. Among them, the PER is determined based on the frame loss rate limit of the service. The PER is used to process service data at the terminal or access network equipment. packet, so that the frame loss rate of the service meets the frame loss rate limit.

Optionally, PER is further determined based on the number of intra-frame data packets of the service.

In one possible design solution, the transceiver module 1801 is also used to receive frame loss rate limit information from the service of the application function; the processing module 1802 is also used to determine the PER based on the frame loss rate limit information. Among them, the PER is used to make the frame loss rate of the service meet the frame loss rate limit of the service when the terminal or the access network device processes the data packet of the service.

Optionally, the transceiver module 1801 is also used to receive the frame characteristic information of the service from the application function; the processing module 1802 is also used to determine the number of data packets in the frame of the service based on the frame characteristic information, and to determine the number of data packets in the frame according to the frame loss of the service. The number of data packets within the frame of rate-limited information and services determines the PER.

In one possible design solution, PER is carried in the PCC rules.

In a possible design solution, the transceiver module 1801 is also used to send the execution conditions of the PER to the session management network element. The execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Optionally, the transceiver module 1801 may include a sending module and a receiving module. Among them, the sending module is used to realize the sending function of the communication device 1800, and the receiving module is used to realize the receiving function of the communication device 1800.

Optionally, the communication device 1800 may also include a storage module that stores programs or instructions. When the processing module 1802 executes the program or instruction, the communication device 1800 can perform the functions of the PCF network element in the communication method as shown in Figures 12-14, or perform the policy control network in the communication method as shown in Figure 15 Yuan function.

It should be noted that the communication device 1800 can be a network device, such as a PCF network element, or a chip (system) or other components or components that can be installed in the network device, or a device including network devices. This application describes This is not limited.

In addition, the technical effects of the communication device 1800 can be referred to the technical effects of the communication methods shown in Figures 12 to 15, which will not be described again here.

As another example, Figure 19 is a second structural schematic diagram of a communication device provided by an embodiment of the present application. As shown in Figure 19, the communication device 1900 may include some functional modules for executing the SMF network elements in the above scenarios 1 to 3. Or the function of session management network element. For example, the communication device 1900 includes: a receiving module 1901 and a sending module 1902.

Among them, the receiving module 1901 is used to receive the PER corresponding to the service from the policy control network element; the sending module 1902, used to send the corresponding relationship between PER and QoS flow to the terminal and/or access network device. The corresponding relationship is used for the access network device or terminal to process the data packets of the service corresponding to the QoS flow according to the PER.

In one possible design solution, PER is a specified value.

In a possible design solution, the receiving module 1901 is also used to receive PCC rules from the policy control network element, where the PCC rules carry PER.

Optionally, the communication device 1900 may further include: a processing module (not shown in Figure 19). This processing module is used to map PCC rules to QoS flows.

In a possible design solution, the receiving module 1901 is also used to receive the execution conditions of the PER from the policy control network element; the sending module 1902 is also used to send the execution conditions of the PER to the terminal or access network device. Among them, the execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Further, the receiving module 1901 is also configured to receive PCC rules from the policy control network element. The PCC rules carry the execution conditions of the PER.

Optionally, the sending module 1902 and the receiving module 1901 can also be integrated into a transceiving module. Among them, the transceiver module is used to implement the transceiver function of the communication device 1900.

Optionally, the communication device 1900 may also include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device 1900 can perform the functions of the SMF network element in the communication method as shown in Figures 12-14, or perform the session management network element in the communication method as shown in Figure 15 function.

It should be noted that the communication device 1900 may be a network device, such as an SMF network element, or may be configured on the network. The chip (system) or other components or components in the network equipment may also be a device including the network equipment, which is not limited in this application.

In addition, the technical effects of the communication device 1900 can be referred to the technical effects of the communication methods shown in Figures 12 to 15, which will not be described again here.

As another example, as shown in Figure 18, the communication device 1800 may include some functional modules for performing the functions of the UE or RAN device, or the terminal or the access network device in the above scenarios 1 to 3. For example, the communication device 1800 includes: a transceiver module 1801 and a processing module 1802.

Among them, the transceiver module 1801 is used to receive the correspondence between the PER and the QoS flow from the session management network element. Among them, the PER corresponds to the business. The processing module 1802 is used to process data packets of services corresponding to the QoS flow according to the PER.

In a possible design solution, the processing module 1802 is also used to determine the link configuration corresponding to the QoS flow based on the PER, and control the transceiver module 1801 to send the data packet of the service corresponding to the QoS flow based on the link configuration.

In one possible design solution, PER is a specified value.

Optionally, the PER is further determined based on the frame loss rate limit of the service and the number of data packets in the frame of the service.

Optionally, the transceiving module 1801 is also configured to receive the frame characteristic information of the service; the processing module 1802 is also configured to determine the data packets in the same frame belonging to the service based on the frame characteristic information. In addition, the processing module 1802 is also configured to process data corresponding to the QoS flow according to the PER in a manner of discarding data packets in the same frame.

In one possible design solution, the transceiver module 1801 is also used to receive the execution conditions of the PER from the session management network element. Among them, the execution condition of PER can be used to indicate that when the execution condition is met, PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Optionally, the processing module 1802 is also configured to adjust the specified value of PER according to the execution condition of PER, and adjust the link resources corresponding to the QoS flow according to the adjusted specified value of PER, so as to adjust the link resources corresponding to the adjusted link. path resources, and controls the transceiver module 1801 to send the data packet of the service corresponding to the QoS flow.

Optionally, the transceiver module 1801 may include a sending module and a receiving module. Among them, the sending module is used to implement communication The sending function of the device 1800 and the receiving module are used to implement the receiving function of the communication device 1800 .

Optionally, the communication device 1800 may also include a storage module that stores programs or instructions. When the processing module 1802 executes the program or instruction, the communication device 1800 can perform the functions of the UE or RAN device in the communication method as shown in Figure 12-14, or perform the terminal or RAN device in the communication method as shown in Figure 15. Functions of access network equipment.

It should be noted that the communication device 1800 may be a terminal or network equipment, such as a UE or RAN equipment, or may be a chip (system) or other components or components that can be disposed in the terminal or network equipment, or may include a terminal or network device. The device of the equipment is not limited in this application.

In other embodiments, the communication device is suitable for the above scenario 4. Details are introduced below.

For example, as shown in Figure 19, the communication device 1900 may include some functional modules for executing the functions of the SMF network element or the session management network element in the above scenario 4. For example, the communication device 1900 includes: a receiving module 1901 and a sending module 1902.

Among them, the receiving module 1901 is used to receive service-related information from the policy control network element. The sending module 1902 is configured to send service-related information to the access network device, as well as the correspondence between the service-related information and the QoS flow. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate limit. The frame characteristic information is used to determine the number of data packets in the frame of the service. The relevant information of the service is used to determine the PER. The PER is used for the terminal or interface. The network access device processes service data packets based on the PER.

In a possible design solution, the receiving module 1901 is also used to receive PCC rules from the policy control network element. The PCC rules carry business-related information.

In one possible design solution, the sending module 1902 is also used to send service-related information to the terminal, as well as the correspondence between the service-related information and the QoS flow.

Optionally, the communication device 1900 may also include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device 1900 can perform the function of the SMF network element in the communication method as shown in Figure 16, or the function of the session management network element in the communication method as shown in Figure 17.

It should be noted that the communication device 1900 may be a network device, such as an SMF network element, a chip (system) or other components or components that can be installed in the network device, or a device including network devices. This application is intended to This is not limited.

In addition, the technical effects of the communication device 1900 can be referred to the technical effects of the communication method shown in FIGS. 16 and 17 , which will not be described again here.

For another example, as shown in Figure 18, the communication device 1800 may include some functional modules for performing the functions of the RAN device or the access network device in the above scenario 4. For example, the communication device 1800 includes: a transceiver module 1801 and a processing module 1802.

Among them, the transceiver module 1801 is used to receive service-related information from the session management network element, as well as the corresponding relationship between the service-related information and the QoS flow; the processing module 1802 is used to determine the PER according to the service-related information. , processing the data packets of the service corresponding to the QoS flow. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate limit, and the frame characteristic information is used to determine the number of data packets in the frame of the service.

Optionally, the processing module 1802 is also configured to determine the data packets in the same frame belonging to the service based on the frame characteristic information of the service. In addition, the processing module 1802 is also configured to process the data packets of the service corresponding to the QoS flow according to the PER in a manner of discarding the data packets in the same frame.

In one possible design solution, PER is a specified value.

In one possible design solution, the transceiver module 1801 is also used to send the corresponding relationship between the PER and the QoS flow to the terminal. The corresponding relationship is used by the terminal to process data packets of services corresponding to the QoS flow according to the PER.

In a possible design solution, the processing module 1802 is also used to determine the execution conditions of the PER based on business-related information. The execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Optionally, the processing module 1802 is also configured to adjust the specified value of PER according to the execution condition of PER, and adjust the link resources corresponding to the QoS flow according to the adjusted specified value of PER, so as to adjust the link resources corresponding to the adjusted link. road resources, Control the transceiver module 1801 to send the data packet of the service corresponding to the QoS flow.

Further, the transceiver module 1801 is also used to send the execution conditions of the PER to the terminal.

Optionally, the communication device 1800 may also include a storage module that stores programs or instructions. When the processing module 1802 executes the program or instruction, the communication device 1800 can perform the functions of the RAN device in the communication method as shown in Figure 16, or perform the functions of the access network device in the communication method as shown in Figure 17.

It should be noted that the communication device 1800 may be a network device, such as a RAN device, or it may be a chip (system) or other component or component that can be disposed in the network device, or it may be a device including a network device. This application will No restrictions.

In addition, the technical effects of the communication device 1800 can be referred to the technical effects of the communication method shown in FIGS. 16 and 17 , which will not be described again here.

As another example, as shown in Figure 18, the communication device 1800 may include some functional modules for performing the functions of the UE or terminal in the above scenario 4. For example, the communication device 1800 includes: a transceiver module 1801 and a processing module 1802.

Among them, the transceiver module 1801 is used to receive the corresponding relationship between the PER and the QoS flow from the access network device, or to receive the corresponding relationship between the service-related information of the session management network element and the QoS flow; the processing module 1802 is used to receive the corresponding relationship between the PER and the QoS flow according to the PER. , processing and sending data packets corresponding to the QoS flow. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate limit. The frame characteristic information is used to determine the number of data packets in the frame of the service. The PER is determined based on the relevant information of the service.

In one possible design solution, PER is a specified value.

In a possible design, the processing module 1802 is also used to determine the PER based on the frame loss rate limit information. Alternatively, the processing module 1802 is also used to determine the PER based on the number of data packets and the frame loss rate limit information.

In a possible design solution, the transceiver module 1801 is also used to receive the PER execution conditions from the access network device. The execution condition can be used to indicate that when the execution condition is met, the PER takes a specified value. For example, the execution condition can be used to indicate at least one of the following: within a specified time of the service, the PER is a specified value, or the PER is a specified value in the event of packet loss or frame loss.

Optionally, the communication device 1800 may also include a storage module that stores programs or instructions. When the processing module 1802 executes the program or instruction, the communication device 1800 can perform the functions of the UE in the communication method as shown in Figure 16, or the functions of the terminal in the communication method as shown in Figure 17.

It should be noted that the communication device 1800 may be a terminal, such as a UE, a chip (system) or other components or components that can be installed in the terminal, or a device including a terminal, which is not limited in this application.

For example, as shown in Figure 19, the communication device 1900 may include some functional modules for executing the functions of the PCF network element or the policy control network element in the above scenario 4. For example, the communication device 1900 includes: a receiving module 1901 and a sending module 1902.

Among them, the receiving module 1901 is used to receive service-related information from the application function; the sending module 1902 is used to send service-related information to the session management network element. The service-related information includes at least one of the following: frame loss rate limit information or frame characteristic information. The frame loss rate limit information indicates that the frame loss rate of the service is less than or equal to the frame loss rate limit, and the frame characteristic information is used to determine the number of data packets in the frame of the service. The relevant information of the service is used to determine the PER, and the PER is used by the terminal or access network equipment to process the data packets of the service based on the PER.

In a possible design solution, the sending module 1902 is also used to send PCC rules to the session management network element, where the PCC rules carry service-related information.

Optionally, the communication device 1900 may also include a storage module that stores programs or instructions. When the processing module executes the program or instruction, the communication device 1900 can perform the functions of the PCF network element in the communication method as shown in Figure 16, or perform the functions of the policy control network element in the communication method as shown in Figure 17.

It should be noted that the communication device 1900 can be a network device, such as a PCF network element, or a chip (system) or other components or components that can be installed in the network device, or a device including network devices. This application describes This is not limited.

In addition, the technical effects of the communication device 1900 can be referred to the technical effects of the communication method shown in Figures 16 and 17, No further details will be given here.

Exemplarily, FIG. 20 is a schematic structural diagram three of a communication device provided by an embodiment of the present application. The communication device may be a terminal, or a chip (system) or other components or components that can be installed in the terminal. As shown in FIG. 20, the communication device 2000 may include a processor 2001. Optionally, the communication device 2000 may also include a memory 2002 and/or a transceiver 2003. The processor 2001 is coupled to the memory 2002 and the transceiver 2003, for example, through a communication bus.

The following is a detailed introduction to each component of the communication device 2000 with reference to Figure 20:

Among them, the processor 2001 is the control center of the communication device 2000, and may be a processor or a collective name for multiple processing elements. For example, the processor 2001 is one or more central processing units (CPUs), may also be an application specific integrated circuit (ASIC), or may be configured to implement one or more embodiments of the present application. An integrated circuit, such as one or more microprocessors (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA).

Optionally, the processor 2001 can perform various functions of the communication device 2000 by running or executing software programs stored in the memory 2002 and calling data stored in the memory 2002, for example, performing the functions shown in FIGS. 12 to 17 above. communication method.

In a specific implementation, as an embodiment, the processor 2001 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 20 .

In specific implementation, as an embodiment, the communication device 2000 may also include multiple processors, such as the processor 2001 and the processor 2004 shown in FIG. 20 . Each of these processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor here may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

The memory 2002 is used to store the software program for executing the solution of the present application, and is controlled by the processor 2001 for execution. For specific implementation methods, reference can be made to the above method embodiments, which will not be described again here.

Optionally, the memory 2002 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory (RAM)) or a random access memory (RAM) that can store information and instructions. Other types of dynamic storage devices for instructions can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical discs Storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and any other media capable of being accessed by a computer, without limitation. The memory 2002 may be integrated with the processor 2001, or may exist independently and be coupled to the processor 2001 through the interface circuit (not shown in Figure 20) of the communication device 2000. This is not specifically limited in the embodiment of the present application.

Transceiver 2003, used for communication with other communication devices. For example, the communication device 2000 is a terminal, and the transceiver 2003 can be used to communicate with a network device or with another terminal device. For another example, the communication device 2000 is a network device, and the transceiver 2003 can be used to communicate with a terminal or another network device.

Optionally, the transceiver 2003 may include a receiver and a transmitter (not shown separately in Figure 20). Among them, the receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.

Optionally, the transceiver 2003 can be integrated with the processor 2001, or can exist independently and communicate through The interface circuit (not shown in Figure 20) of the device 2000 is coupled to the processor 2001, which is not specifically limited in the embodiment of the present application.

It should be noted that the structure of the communication device 2000 shown in Figure 20 does not constitute a limitation on the communication device. The actual communication device may include more or less components than shown in the figure, or some components may be combined, or Different component arrangements.

In addition, the technical effects of the communication device 2000 can be referred to the technical effects of the communication method described in the above method embodiments, which will not be described again here.

It should be understood that the processor in the embodiment of the present application can be a central processing unit (CPU). The processor can also be other general-purpose processors, digital signal processors (DSP), special-purpose integrated processors, etc. Circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

It should also be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of illustration, but not limitation, many forms of random access memory (RAM) are available, such as static random access memory (static RAM (SRAM)), dynamic random access memory (DRAM), synchronous dynamic random access memory (RAM) Access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware (such as circuits), firmware, or any other combination. When implemented using software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmit to another website, computer, server or data center through wired (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server or a data center that contains one or more sets of available media. The usable media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media. The semiconductor medium may be a solid state drive.

It should be understood that the term "and/or" in this article is only an association relationship describing related objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, and A and B exist simultaneously. , there are three cases of B alone, where A and B can be singular or plural. In addition, the character "/" in this article generally indicates that the related object is a It is an "or" relationship, but it may also represent an "and/or" relationship. Please refer to the context for understanding.

In this application, "at least one" refers to one or more, and "plurality" refers to two or more. "At least one of the following" or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items). For example, at least one of a, b, or c can mean: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .

It should be understood that in the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A communication method, characterized in that the method includes:

The policy control network element obtains the packet error rate PER corresponding to the service;

The policy control network sends the PER to the session management network element, where the PER is used to instruct the terminal or the access network device to process the data packet of the service according to the PER.
The method according to claim 1, characterized in that the policy control network element obtains the PER corresponding to the service, including:

The policy control network element receives the PER from the application function; the PER is determined according to the frame loss rate limit of the service; the PER is used to process the PER at the terminal or the access network device. data packets of the service, so that the frame loss rate of the service satisfies the frame loss rate limit.
The method according to claim 2, characterized in that the PER is further determined based on the number of data packets in a frame of the service.
The method according to claim 1, characterized in that the policy control network element obtains the PER corresponding to the service, including:

The policy control network element receives the frame loss rate limit information of the service from the application function;

The policy control network element determines the PER according to the frame loss rate limit information; the PER is used to ensure that when the terminal or the access network device processes the data packet of the service, the The frame loss rate meets the frame loss rate limit of the service.
The method of claim 4, further comprising:

The policy control network element receives frame characteristic information of the service from the application function;

The policy control network element determines the number of data packets in the frame of the service based on the frame characteristic information;

The policy control network element determines the PER based on the frame loss rate limit information, including:

The policy control network element determines the PER based on the frame loss rate limit information and the number of data packets in the frame of the service.
The method according to any one of claims 1 to 5, characterized in that the PER is carried in a policy and charging control PCC rule.
The method according to any one of claims 1-5, characterized in that the method further includes:

The policy control network element sends the execution condition of the PER to the session management network element; the execution condition is used to indicate that the PER is a specified value when the execution condition is met.
The method according to claim 7, characterized in that the execution conditions of the PER are carried in PCC rules.
A communication method, characterized in that the method includes:

The session management network element receives the packet error rate PER corresponding to the service from the policy control network element;

The session management network element sends the corresponding relationship between the PER and the quality of service QoS flow to the terminal and/or access network equipment, wherein the corresponding relationship indicates that the access network equipment or the terminal performs the following tasks according to the PER , processing the data packets of the service corresponding to the QoS flow.
The method according to claim 9, characterized in that the session management network element receives the PER corresponding to the service from the policy control network element, including:

The session management network element receives the policy and charging control PCC rules from the policy control network element, and the PCC The rule carries the PER.
The method of claim 10, further comprising:

The session management network element maps the PCC rule to the QoS flow.
The method according to claim 11, characterized in that the session management network element maps the PCC rule to the QoS flow, including:

The session management network element determines that the PER in the PCC rule is the same as the PER in the existing QoS flow parameter, and maps the PCC rule to the QoS flow corresponding to the QoS flow parameter; or,

The session management network element determines that the PER is different from the PER in the existing QoS flow parameters, creates the QoS flow, and maps the PCC rule to the created QoS flow.
The method of claim 9, further comprising:

The session management network element receives the execution condition of the PER from the policy control network element; the execution condition is used to indicate that the PER is a specified value when the execution condition is met.
The method according to claim 13, characterized in that the session management network element receives execution conditions of the PER from the policy control network element, including:

The session management network element receives the PCC rule from the policy control network element, and the PCC rule carries the execution condition of the PER.
A communication method, characterized in that the method includes:

Receive the correspondence between the packet error rate PER from the session management network element and the quality of service QoS flow; the PER corresponds to the service;

According to the PER, process data packets of the QoS flow corresponding to the service.
The method according to claim 9 or 15, characterized in that the PER is determined according to the frame loss rate limit of the service; the PER is used to process data packets of the service at a terminal or access network device time, so that the frame loss rate of the service satisfies the frame loss rate limit.
The method according to claim 16, characterized in that the PER is further determined based on the number of data packets in a frame of the service.
The method according to claim 3 or 17, characterized in that the number of data packets in the frame of the service is determined according to the frame characteristic information of the service, and the frame characteristic information includes at least one of the following: frame period, maximum Number of packets, maximum data burst size, or packet period.
The method according to claim 18, characterized in that the frame characteristic information includes at least one of the following: burst arrival time (BAT) or time information, the BAT is used to indicate the arrival time of the first data packet of the service. Arrival time, the time information is used to indicate the time of the frame of the service.
The method of claim 15, further comprising:

Receive the execution condition of the PER from the session management network element; the execution condition is used to indicate that the PER has a specified value when the execution condition is met.
A communication device, characterized by comprising: a module for executing the method according to any one of claims 1-8.
A communication device, characterized by comprising: a module for executing the method according to any one of claims 9-14.
A communication device, characterized by comprising: configured to perform the method according to any one of claims 15-20 method module.
A communication device, characterized in that the communication device includes: a processor; wherein,

The processor is configured to execute the communication method according to any one of claims 1-20.
A communication device, characterized in that the communication device includes: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device executes the instructions as claimed in claim 1 -The communication method described in any one of 20.
A communication system, characterized in that the communication system includes: at least one communication device for performing the method according to any one of claims 1-20.
A computer-readable storage medium, characterized in that the computer-readable storage medium includes a computer program or instructions that, when the computer program or instructions are run on a computer, cause the computer to execute the instructions in claims 1-20 The communication method described in any one of the above.
A communication method characterized by:

The policy control network element obtains the packet error rate PER corresponding to the service;

The session management network element receives the PER sent by the policy control network element, and the PER is used to instruct the terminal or the access network device to process the data packet of the service according to the PER.
The method of claim 28, further comprising:

The session management network element sends the corresponding relationship between the PER and the quality of service QoS flow to the terminal and/or access network equipment, wherein the corresponding relationship indicates that the access network equipment or the terminal performs the following tasks according to the PER , processing the data packets of the service corresponding to the QoS flow.
The method according to claim 28 or 29, characterized in that the method further includes:

The terminal or access network device receives the corresponding relationship between the PER and the QoS flow from the session management network element; the PER corresponds to the service;

The terminal or the access network device processes the data packet of the QoS flow corresponding to the service according to the PER.