QOS control method and apparatus, and communication device, communication system and storage medium
Patent Information
- Application Number
- PCT/CN2023/093712
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-14
Smart Images

Figure CN2023093712_14112024_PF_FP_ABST
Abstract
Description
QoS control method and device, communication equipment, communication system, and storage medium Technical Field
[0001] The present disclosure relates to the field of communication technologies, and in particular to a quality of service (QoS) control method and apparatus, communication equipment, a communication system, and a storage medium. Background Art
[0002] In communication technologies such as the fifth generation mobile networks (5G), mobile media services, online extended reality (XR), online games, and video-based remote control of machines or drones are expected to contribute an increasing amount of traffic to communication networks.
[0003] Currently, due to the high throughput, low latency, and high reliability requirements of XRM and eXtended Reality and interactive media services, the QoS characteristics of service data flows (SDFs) need to be comprehensively considered.
[0004] Summary of the Invention
[0005] Therefore, there is no solution for processing the packet data units (PDUs) in an SDF containing both PDUs and PDU sets, making it difficult to guarantee the QoS characteristics of the SDF.
[0006] Embodiments of the present disclosure provide a QoS control method and apparatus, communication equipment, a communication system, and a storage medium.
[0007] According to a first aspect of an embodiment of the present disclosure, a QoS control method is provided. The QoS control method is performed by a first network function. The method includes: receiving a first PDU, wherein the first PDU belongs to a first SDF; determining that the first PDU does not have an extended header, wherein the extended header is used to identify a PDU set; and mapping the first PDU to a first PDU set.
[0008] According to a second aspect of an embodiment of the present disclosure, a QoS control method is provided. The method is performed by a second network function. The method includes: determining first information associated with a first SDF; and sending the first information to the first network function, wherein the first information is used by the first network function to perform QoS control on a first PDU in the first SDF, where the first PDU does not have an extended header, and the extended header is used to identify a PDU set.
[0009] According to a third aspect of an embodiment of the present disclosure, a QoS control method is provided. The method is performed by an access network device. The method includes receiving a second PDU sent by a first network function, wherein the second PDU is obtained by mapping a first PDU belonging to a first SDF to a first PDU set, and the first PDU does not have an extended header, and the extended header is used to identify the PDU set.
[0010] According to a fourth aspect of an embodiment of the present disclosure, a QoS control method is provided. The method is performed by a terminal. The method includes: receiving a second PDU from an access network device, wherein the second PDU is obtained by mapping a first PDU belonging to a first SDF to a first PDU set, and the first PDU does not have an extended header, and the extended header is used to identify the PDU set.
[0011] According to a fifth aspect of an embodiment of the present disclosure, a QoS control method is provided. The method is used in a communication system. The method includes: a network device sending a second PDU to a terminal, wherein the second PDU is obtained by mapping a first PDU belonging to a first SDF to a first PDU set, and the first PDU does not have an extended header, and the extended header is used to identify the PDU set.
[0012] According to a sixth aspect of an embodiment of the present disclosure, a QoS control method is provided. The method is used in a core network device. The method includes: receiving a first PDU, wherein the first PDU belongs to a first SDF; determining that the first PDU does not have an extended header, wherein the extended header is used to represent a PDU set; and mapping the first PDU to the first PDU set.
[0013] According to a seventh aspect of an embodiment of the present disclosure, a QoS control device is provided. The device includes a receiving module and a processing module. The receiving module is configured to receive a first PDU, wherein the first PDU belongs to a first SDF. The processing module is configured to: determine that the first PDU does not have an extended header, wherein the extended header is used to identify a PDU set; and map the first PDU to the first PDU set.
[0014] According to an eighth aspect of an embodiment of the present disclosure, a QoS control apparatus is provided. The apparatus includes a processing module and a sending module. The processing module is configured to determine first information associated with a first SDF. The sending module is configured to send the first information to a first network function, wherein the first information is used by the first network function to perform QoS control on a first PDU in the first SDF, where the first PDU does not have an extended header, and the extended header is used to identify a PDU set.
[0015] According to a ninth aspect of an embodiment of the present disclosure, a QoS control device is provided. The device includes a receiving module. The receiving module is configured to receive a second PDU sent by a first network function, wherein the second PDU is obtained by mapping a first PDU belonging to a first SDF to a first PDU set, and the first PDU does not have an extended header, and the extended header is used to identify the PDU set.
[0016] According to a tenth aspect of an embodiment of the present disclosure, a QoS control apparatus is provided. The apparatus includes a receiving module. The receiving module is configured to receive a second PDU from an access network device, wherein the second PDU is obtained by mapping a first PDU belonging to a first SDF to a first PDU set, and the first PDU does not have an extended header, and the extended header is used to identify the PDU set.
[0017] According to an eleventh aspect of the present disclosure, a communication device is provided. The communication device includes at least one processor and at least one memory. The memory is configured to store instructions. The processor is configured to invoke the instructions so that the communication device executes the methods described in aspects 1 to 6.
[0018] According to a twelfth aspect of an embodiment of the present disclosure, a communication system is provided. The communication system includes a first network function, a second network function, an access network device, and a terminal. The first network function is configured to execute the method described in the first aspect. The second network function is configured to execute the method described in the second aspect. The access network device is configured to execute the method described in the third aspect. The terminal is configured to execute the method described in the fourth aspect.
[0019] According to a thirteenth aspect of the embodiments of the present disclosure, a storage medium is provided. The storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the method according to the first to sixth aspects.
[0020] Through the embodiments of the present disclosure, the QoS characteristics of SDF in XRM and interactive media services are guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.
[0022] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.
[0023] FIG2 is an interactive schematic diagram illustrating a QoS control method according to an embodiment of the present disclosure.
[0024] FIG3 is a flow chart showing a QoS control method according to an embodiment of the present disclosure.
[0025] FIG4 is a flow chart showing a QoS control method according to an embodiment of the present disclosure.
[0026] FIG5 is a flow chart showing a QoS control method according to an embodiment of the present disclosure.
[0027] FIG6 is a flow chart showing a QoS control method according to an embodiment of the present disclosure.
[0028] FIG7 is a flow chart showing a QoS control method according to an embodiment of the present disclosure.
[0029] FIG8 is a flow chart showing a QoS control method according to an embodiment of the present disclosure.
[0030] FIG9 is a schematic structural diagram of a first QoS control device according to an embodiment of the present disclosure.
[0031] FIG10 is a schematic structural diagram of a second QoS control device according to an embodiment of the present disclosure.
[0032] FIG11 is a schematic structural diagram of a third QoS control device according to an embodiment of the present disclosure.
[0033] FIG12 is a schematic structural diagram of a fourth QoS control device according to an embodiment of the present disclosure.
[0034] FIG13 is a schematic structural diagram of a fifth QoS control device according to an embodiment of the present disclosure.
[0035] FIG14 is a schematic structural diagram of a communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0036] Embodiments of the present disclosure provide a QoS control method and apparatus, communication equipment, a communication system, and a storage medium.
[0037] In a first aspect, embodiments of the present disclosure provide a QoS control method. The QoS control method is performed by a first network function. The method includes: receiving a first PDU, wherein the first PDU belongs to a first SDF; determining that the first PDU does not have an extended header, wherein the extended header is used to identify a PDU set; and mapping the first PDU to a first PDU set.
[0038] In the above embodiment, the first network function maps the first SDF, which does not have an extension header for indicating a PDU set, to the first PDU set, thereby mapping the first PDU in the first SDF that does not belong to an existing PDU set to the PDU set. This allows the first network function to perform QoS control on the first PDU that does not belong to an existing PDU set, thereby ensuring the QoS characteristics of the first SDF.
[0039] In combination with some embodiments of the first aspect, in some embodiments, the extended packet header may include at least one of the following: PDU set sequence number, the start PDU or end PDU of the PDU set, the PDU sequence number within the PDU set, the number of PDUs within the PDU set, the importance of the PDU set, the size of the PDU set, and the end of the data burst.
[0040] In the above embodiment, the extended header includes PDU set information. This PDU set information is used to indicate that the PDU belongs to a PDU set. Thus, if it is determined that the first PDU does not have an extended header, it can be determined that the first PDU does not belong to an existing PDU set, and the first PDU is mapped to the first PDU set.
[0041] In combination with some embodiments of the first aspect, in some embodiments, the first PDU set may be integrated by one or more PDUs, and the one or more PDUs do not include an extended header.
[0042] In the above embodiment, the first PDU is mapped to the first PDU set, and all PDUs in the first PDU set do not have an extended header. Any PDU in the first PDU set can be considered a first PDU. In this way, one or more first PDUs can be mapped to the first PDU set for QoS control.
[0043] In combination with some embodiments of the first aspect, in some embodiments, one or more PDUs of the first PDU set arrive within a time window.
[0044] In the above embodiment, the PDUs in the first PDU set arrive within the time window. In this way, unified QoS control can be performed on the first PDUs arriving within the time window.
[0045] In combination with some embodiments of the first aspect, in some embodiments, the first PDU set may belong to a first QoS flow corresponding to the first SDF, and all PDU sets in the first QoS flow may have the same PDU set QoS parameters.
[0046] In the above embodiment, all PDU sets in the first QoS flow corresponding to the first SDF can have the same PDU set QoS parameters. In other words, the first PDU set and other PDU sets in the first QoS flow can have the same PDU set QoS parameters. In this way, the first PDU and other PDUs in the first SDF (PDUs with extended headers and PDUs without extended headers) can apply the previously agreed PDU set QoS parameters.
[0047] In combination with some embodiments of the first aspect, in some embodiments, determining that the first PDU does not have an extended header can be achieved by at least one of the following: matching the header and payload of RTP and / or SRTP; using a new RTP extended header; information provided by the N6 encapsulation header; detection based on traffic characteristics; UPF local configuration.
[0048] In the above embodiment, it is possible to determine that the first PDU does not have an extended header in a variety of ways, thereby improving the flexibility of the determination operation.
[0049] In combination with some embodiments of the first aspect, in some embodiments, the operation of mapping the first PDU to the first PDU set may include: mapping the first PDU to the first PDU set according to first information associated with the first SDF.
[0050] In the above embodiment, the first network function may map the first PDU to the first PDU set according to the first information associated with the first SDF, thereby maintaining the association and / or consistency between the first PDU set and other PDU sets in the first SDF.
[0051] In combination with some embodiments of the first aspect, in some embodiments, the first information may include at least one of the following: PDU set QoS parameters, protocol description, and PDR.
[0052] In the above embodiment, the mapping of the first PDU can be implemented based on at least one of the PDU set QoS parameters, the protocol description, and the PDR. In this way, the correlation and / or consistency of the first PDU set with other PDU sets in the first SDF in at least one of the PDU set QoS parameters, the protocol description, and the PDR can be maintained.
[0053] In combination with some embodiments of the first aspect, in some embodiments, before receiving the first PDU, the above method may further include: receiving first information from a second network function.
[0054] In the above embodiment, the first information may be sent by the second network function to the first network function. In this way, the first network function can implement mapping of the first PDU according to the received external information.
[0055] In combination with some embodiments of the first aspect, in some embodiments, after mapping the first PDU to the first PDU set, the above method may further include: sending a second PDU to the access network device, wherein the second PDU is obtained by mapping the first PDU to the first PDU set.
[0056] In the above embodiment, after mapping the first PDU to the first PDU set to obtain the second PDU, the second PDU can be sent to the access network device. Therefore, the second PDU is a PDU belonging to the first PDU set. As such, transmission of the second PDU between the first network function and the access network device can utilize PDU set-based QoS control.
[0057] In a second aspect, embodiments of the present disclosure provide a QoS control method. The method is performed by a second network function. The method includes: determining first information associated with a first SDF; and sending the first information to the first network function, wherein the first information is used by the first network function to perform QoS control on a first PDU in the first SDF, where the first PDU does not have an extended header, and the extended header is used to identify a PDU set.
[0058] In the above embodiment, the first information may be sent by the second network function to the first network function. In this way, the first network function can implement mapping of the first PDU based on the received external information, so that the first network function can perform QoS control on the first PDU that does not belong to the existing PDU set, thereby ensuring the QoS characteristics of the first SDF.
[0059] In combination with some embodiments of the second aspect, in some embodiments, the first information may include at least one of the following: PDU set QoS parameters, protocol description, and PDR.
[0060] In combination with some embodiments of the second aspect, in some embodiments, the operation of determining the first information associated with the first SDF may include: receiving second information, wherein the second information includes at least one of the following: PDU set QoS parameters, protocol description; and determining the first information based on the second information.
[0061] In the above embodiment, the second network function may determine the first information according to the PDU set QoS parameters and / or protocol description in the received second information.
[0062] In combination with some embodiments of the second aspect, in some embodiments, the above method may further include: sending third information to the access network device, wherein the third information includes at least one of the following: PDU set QoS parameters, protocol description.
[0063] In the above embodiment, the third information is sent to the access network device, so that the access network device can implement QoS control based on the PDU set for the first SDF.
[0064] In a third aspect, embodiments of the present disclosure provide a QoS control method. The method is performed by an access network device. The method includes receiving a second PDU sent by a first network function, wherein the second PDU is obtained by mapping a first PDU belonging to a first SDF to a first PDU set, and the first PDU does not have an extended header, which is used to identify the PDU set.
[0065] In the above embodiment, the second PDU is obtained by mapping the first PDU belonging to the first SDF to the first PDU set. Therefore, the second PDU is a PDU belonging to the first PDU set. In this way, the transmission of the second PDU between the first network function and the access network device can adopt PDU set-based QoS control, thereby ensuring the QoS characteristics of the first SDF.
[0066] In combination with some embodiments of the third aspect, in some embodiments, a PDU set may be integrated by one or more PDUs, and the one or more PDUs do not include an extended header.
[0067] In combination with some embodiments of the third aspect, in some embodiments, one or more PDUs of the first PDU set may arrive within a time window.
[0068] In combination with some embodiments of the third aspect, in some embodiments, the first PDU set may belong to a first QoS flow corresponding to the first SDF, and all PDU sets in the first QoS flow may have the same PDU set QoS parameters.
[0069] In combination with some embodiments of the third aspect, in some embodiments, the second PDU may include at least one of the following: the sequence number of the first PDU set; the start PDU or end PDU of the first PDU set; the PDU sequence number within the first PDU set; the number of PDUs within the first PDU set; the importance of the first PDU set; the size of the first PDU set; the end of the data burst.
[0070] In combination with some embodiments of the third aspect, in some embodiments, the above method may further include: sending a second PDU to the terminal.
[0071] In the above embodiment, the second PDU is obtained by mapping the first PDU belonging to the first SDF to the first PDU set. Therefore, the second PDU is a PDU belonging to the first PDU set. In this way, the transmission of the second PDU between the access network device and the terminal can adopt PDU set-based QoS control.
[0072] In conjunction with some embodiments of the third aspect, in some embodiments, the method may further include: receiving third information sent by the first network function, where the third information includes at least one of the following: a PDU set QoS parameter and a protocol description. The operation of sending the second PDU to the terminal may include: sending the second PDU to the terminal based on the third information.
[0073] In combination with some embodiments of the third aspect, in some embodiments, the above method may further include: sending fourth information to the terminal based on the third information, wherein the fourth information includes at least one of the following: PDU set QoS parameters, protocol description.
[0074] In the above embodiment, the fourth information is obtained based on the third information and sent to the terminal. The fourth information includes the PDU set QoS parameters and / or protocol description, which enables the terminal to take the PDU set QoS parameters and / or protocol description into consideration when sending uplink data related to the first SDF (i.e., uplink PDU).
[0075] In a fourth aspect, embodiments of the present disclosure provide a QoS control method. The method is performed by a terminal. The method includes receiving a second PDU from an access network device, wherein the second PDU is obtained by mapping a first PDU belonging to a first SDF to a first PDU set, and the first PDU does not have an extended header, and the extended header is used to identify the PDU set.
[0076] In the above embodiment, the second PDU is obtained by mapping the first PDU belonging to the first SDF to the first PDU set. Therefore, the second PDU is a PDU belonging to the first PDU set. In this way, the transmission of the second PDU between the access network device and the terminal can adopt PDU set-based QoS control, thereby ensuring the QoS characteristics of the first SDF. The terminal can receive all PDUs of the first SDF under PDU set-based QoS control.
[0077] In combination with some embodiments of the fourth aspect, in some embodiments, the above method may further include: receiving fourth information from an access network device, wherein the fourth information includes at least one of the following: PDU set QoS parameters, protocol description, and the fourth information is used to send uplink data.
[0078] In the above embodiment, the received fourth information includes PDU set QoS parameters and / or protocol description, which enables the terminal to take the PDU set QoS parameters and / or protocol description into consideration when sending uplink data related to the first SDF (i.e., uplink PDU).
[0079] In a fifth aspect, embodiments of the present disclosure provide a QoS control method for a communication system. The method includes: a network device sending a second PDU to a terminal, wherein the second PDU is obtained by mapping a first PDU belonging to a first SDF to a first PDU set, and the first PDU does not have an extended header, which is used to identify the PDU set.
[0080] In combination with some embodiments of the fifth aspect, in some embodiments, the above method may also include: the network device sends fourth information to the terminal, wherein the fourth information includes at least one of the following: PDU set QoS parameters, protocol description; the fourth information is used for the terminal to send uplink data to the network device.
[0081] In a sixth aspect, embodiments of the present disclosure provide a QoS control method. The method is applied to a core network device. The method includes: receiving a first PDU, wherein the first PDU belongs to a first SDF; determining that the first PDU does not have an extended header, wherein the extended header is used to represent a PDU set; and mapping the first PDU to the first PDU set.
[0082] In combination with some embodiments of the sixth aspect, in some embodiments, the extended packet header may include at least one of the following: PDU set sequence number; the start PDU or end PDU of the PDU set; the PDU sequence number within the PDU set; the number of PDUs within the PDU set; the PDU set importance; the PDU set size; and the end of the data burst.
[0083] In combination with some embodiments of the sixth aspect, in some embodiments, the first PDU set can be integrated by one or more PDUs, and one or more PDUs do not include an extended header.
[0084] In combination with some embodiments of the sixth aspect, in some embodiments, one or more PDUs of the first PDU set may arrive within a time window.
[0085] In combination with some embodiments of the sixth aspect, in some embodiments, the first PDU set may belong to a first QoS flow corresponding to the first SDF, and all PDU sets in the first QoS flow may have the same PDU set QoS parameters.
[0086] In combination with some embodiments of the sixth aspect, in some embodiments, determining that the first PDU does not have an extended header can be achieved by at least one of the following: matching the header and payload of RTP and / or SRTP; using a new RTP extended header; information provided by the N6 encapsulation header; detection based on traffic characteristics; UPF local configuration.
[0087] In combination with some embodiments of the sixth aspect, in some embodiments, the operation of mapping the first PDU to the first PDU set may include: mapping the first PDU to the first PDU set according to first information associated with the first SDF.
[0088] In combination with some embodiments of the sixth aspect, in some embodiments, the above method may further include: determining first information associated with the first SDF.
[0089] In combination with some embodiments of the sixth aspect, in some embodiments, the operation of determining the first information associated with the first SDF may include: determining the first information based on second information, wherein the second information includes at least one of the following: PDU set QoS parameters, protocol description.
[0090] In combination with some embodiments of the sixth aspect, in some embodiments, the first information may include at least one of the following: PDU set QoS parameters, protocol description, and PDR.
[0091] In combination with some embodiments of the sixth aspect, in some embodiments, the above method may further include: sending a second PDU to the access network device, wherein the second PDU is obtained by mapping the first PDU to the first PDU set.
[0092] In combination with some embodiments of the sixth aspect, in some embodiments, the second PDU may include at least one of the following: the serial number of the first PDU set; the start PDU or end PDU of the first PDU set; the PDU sequence number within the first PDU set; the number of PDUs within the first PDU set; the importance of the first PDU set; the size of the first PDU set; the end of the data burst.
[0093] In combination with some embodiments of the sixth aspect, in some embodiments, the above method may further include: sending third information to the access network device, wherein the third information includes at least one of the following: PDU set QoS parameters, protocol description.
[0094] In a seventh aspect, embodiments of the present disclosure provide a first QoS control apparatus. The apparatus includes a receiving module and a processing module. The receiving module is configured to receive a first PDU, wherein the first PDU belongs to a first SDF. The processing module is configured to: determine that the first PDU does not have an extended header, wherein the extended header is used to identify a PDU set; and map the first PDU to the first PDU set.
[0095] In combination with some embodiments of the seventh aspect, in some embodiments, the extended packet header may include at least one of the following: PDU set sequence number, the start PDU or end PDU of the PDU set, the PDU sequence number within the PDU set, the number of PDUs within the PDU set, the importance of the PDU set, the size of the PDU set, and the end of the data burst.
[0096] In combination with some embodiments of the seventh aspect, in some embodiments, the first PDU set can be integrated by one or more PDUs, and one or more PDUs do not include an extended header.
[0097] In combination with some embodiments of the seventh aspect, in some embodiments, one or more PDUs of the first PDU set arrive within a time window.
[0098] In combination with some embodiments of the seventh aspect, in some embodiments, the first PDU set may belong to a first QoS flow corresponding to the first SDF, and all PDU sets in the first QoS flow may have the same PDU set QoS parameters.
[0099] In combination with some embodiments of the seventh aspect, in some embodiments, determining that the first PDU does not have an extended header can be achieved by at least one of the following: matching the header and payload of RTP and / or SRTP; using a new RTP extended header; information provided by the N6 encapsulation header; detection based on traffic characteristics; UPF local configuration.
[0100] In combination with some embodiments of the seventh aspect, in some embodiments, the processing module can be configured to: map the first PDU to the first PDU set based on first information associated with the first SDF.
[0101] In combination with some embodiments of the seventh aspect, in some embodiments, the first information may include at least one of the following: PDU set QoS parameters, protocol description, and PDR.
[0102] In combination with some embodiments of the seventh aspect, in some embodiments, the receiving module can be configured to: receive first information from the second network function.
[0103] In conjunction with some embodiments of the seventh aspect, in some embodiments, the apparatus may further include a sending module. The sending module may be configured to: send a second PDU to the access network device, wherein the second PDU is obtained by mapping the first PDU to the first PDU set.
[0104] In an eighth aspect, embodiments of the present disclosure provide a second QoS control apparatus. The apparatus includes a processing module and a sending module. The processing module is configured to determine first information associated with a first SDF. The sending module is configured to send the first information to a first network function, wherein the first information is used by the first network function to perform QoS control on a first PDU in the first SDF, where the first PDU does not have an extended header, and the extended header is used to identify a PDU set.
[0105] In combination with some embodiments of the eighth aspect, in some embodiments, the first information may include at least one of the following: PDU set QoS parameters, protocol description, and PDR.
[0106] In conjunction with some embodiments of the eighth aspect, in some embodiments, the apparatus may include a receiving module. The receiving module may be configured to receive second information, where the second information includes at least one of the following: a PDU set QoS parameter and a protocol description. The processing module may be configured to determine the first information based on the second information.
[0107] In combination with some embodiments of the eighth aspect, in some embodiments, the sending module can be configured to: send third information to the access network device, wherein the third information includes at least one of the following: PDU set QoS parameters, protocol description.
[0108] In a ninth aspect, embodiments of the present disclosure provide a third QoS control device. The device includes a receiving module configured to receive a second PDU sent by a first network function, wherein the second PDU is obtained by mapping a first PDU belonging to a first SDF to a first PDU set, and the first PDU does not have an extended header, which is used to identify the PDU set.
[0109] In combination with some embodiments of the ninth aspect, in some embodiments, a PDU set may be integrated by one or more PDUs, and one or more PDUs do not include an extended header.
[0110] In combination with some embodiments of the ninth aspect, in some embodiments, one or more PDUs of the first PDU set may arrive within a time window.
[0111] In combination with some embodiments of the ninth aspect, in some embodiments, the first PDU set may belong to a first QoS flow corresponding to the first SDF, and all PDU sets in the first QoS flow may have the same PDU set QoS parameters.
[0112] In combination with some embodiments of the ninth aspect, in some embodiments, the second PDU may include at least one of the following: the serial number of the first PDU set; the start PDU or end PDU of the first PDU set; the PDU sequence number within the first PDU set; the number of PDUs within the first PDU set; the importance of the first PDU set; the size of the first PDU set; the end of the data burst.
[0113] In conjunction with some embodiments of the ninth aspect, in some embodiments, the apparatus may include a sending module. The sending module may be configured to: send the second PDU to the terminal.
[0114] In conjunction with some embodiments of the ninth aspect, in some embodiments, the receiving module may be configured to: receive third information sent by the first network function, where the third information includes at least one of the following: PDU set QoS parameters and a protocol description. The sending module may be configured to: send the second PDU to the terminal based on the third information.
[0115] In combination with some embodiments of the ninth aspect, in some embodiments, the sending module can be configured to: send fourth information to the terminal based on the third information, wherein the fourth information includes at least one of the following: PDU set QoS parameters, protocol description.
[0116] In a tenth aspect, an embodiment of the present disclosure provides a fourth QoS control apparatus. The apparatus includes a receiving module configured to receive a second PDU from an access network device, wherein the second PDU is obtained by mapping a first PDU belonging to a first SDF to a first PDU set, and the first PDU does not have an extended header, which is used to identify the PDU set.
[0117] In combination with some embodiments of the tenth aspect, in some embodiments, the receiving module can be configured to: receive fourth information from the access network device, wherein the fourth information includes at least one of the following: PDU set QoS parameters, protocol description, and the fourth information is used for sending uplink data.
[0118] In an eleventh aspect, an embodiment of the present disclosure provides a fifth QoS control apparatus. The apparatus includes a receiving module and a processing module. The receiving module is configured to receive a first PDU, wherein the first PDU belongs to a first SDF. The processing module is configured to determine that the first PDU does not have an extended header, wherein the extended header is used to indicate a PDU set; and map the first PDU to the first PDU set.
[0119] In combination with some embodiments of the eleventh aspect, in some embodiments, the extended packet header may include at least one of the following: PDU set sequence number; the start PDU or end PDU of the PDU set; the PDU sequence number within the PDU set; the number of PDUs within the PDU set; the importance of the PDU set; the size of the PDU set; and the end of the data burst.
[0120] In combination with some embodiments of the eleventh aspect, in some embodiments, the first PDU set can be integrated by one or more PDUs, and one or more PDUs do not include an extended header.
[0121] In combination with some embodiments of the eleventh aspect, in some embodiments, one or more PDUs of the first PDU set may arrive within a time window.
[0122] In combination with some embodiments of the eleventh aspect, in some embodiments, the first PDU set may belong to a first QoS flow corresponding to the first SDF, and all PDU sets in the first QoS flow may have the same PDU set QoS parameters.
[0123] In combination with some embodiments of the eleventh aspect, in some embodiments, determining that the first PDU does not have an extended header can be achieved by at least one of the following: matching the header and payload of RTP and / or SRTP; using a new RTP extended header; information provided by the N6 encapsulation header; detection based on traffic characteristics; UPF local configuration.
[0124] In combination with some embodiments of the eleventh aspect, in some embodiments, the processing module may be configured to: map the first PDU to the first PDU set according to first information associated with the first SDF.
[0125] In combination with some embodiments of the eleventh aspect, in some embodiments, the processing module may be configured to: determine first information associated with the first SDF.
[0126] In combination with some embodiments of the eleventh aspect, in some embodiments, the processing module can be configured to: determine the first information based on the second information, wherein the second information includes at least one of the following: PDU set QoS parameters, protocol description.
[0127] In combination with some embodiments of the eleventh aspect, in some embodiments, the first information may include at least one of the following: PDU set QoS parameters, protocol description, and PDR.
[0128] In conjunction with some embodiments of the eleventh aspect, in some embodiments, the apparatus may include a sending module configured to send a second PDU to the access network device, where the second PDU is obtained by mapping the first PDU to the first PDU set.
[0129] In combination with some embodiments of the eleventh aspect, in some embodiments, the second PDU may include at least one of the following: the serial number of the first PDU set; the start PDU or end PDU of the first PDU set; the PDU sequence number within the first PDU set; the number of PDUs within the first PDU set; the importance of the first PDU set; the size of the first PDU set; the end of the data burst.
[0130] In combination with some embodiments of the eleventh aspect, in some embodiments, the sending module can be configured to: send third information to the access network device, wherein the third information includes at least one of the following: PDU set QoS parameters, protocol description.
[0131] In a twelfth aspect, an embodiment of the present disclosure provides a communications device. The communications device includes at least one processor and at least one memory. The memory is configured to store instructions. The processor is configured to invoke the instructions to cause the communications device to execute the methods described in aspects 1 to 6, and in optional implementations of aspects 1 to 6.
[0132] In a thirteenth aspect, an embodiment of the present disclosure provides a communications system. The communications system includes a first network function, a second network function, an access network device, and a terminal. The first network function is configured to execute the method described in the first aspect and its optional implementation. The second network function is configured to execute the method described in the second aspect and its optional implementation. The access network device is configured to execute the method described in the third aspect and its optional implementation. The terminal is configured to execute the method described in the fourth aspect and its optional implementation.
[0133] In a fourteenth aspect, an embodiment of the present disclosure provides a storage medium. The storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the method as described in aspects 1 to 6, and the optional implementations of aspects 1 to 6.
[0134] In a fifteenth aspect, an embodiment of the present disclosure provides a program product. When the program product is executed by a communication device, the communication device executes the method as described in the first to sixth aspects and the optional implementations of the first to sixth aspects.
[0135] In a sixteenth aspect, an embodiment of the present disclosure provides a computer program. When the computer program is executed on a computer, the computer is caused to execute the method as described in the first to sixth aspects and the optional implementations of the first to sixth aspects.
[0136] It can be understood that the above-mentioned first QoS control device, second QoS control device, third QoS control device, fourth QoS control device, fifth QoS control device, communication device, communication system, storage medium, program product, and computer program are all used to perform the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved by the above-mentioned first QoS control device, second QoS control device, third QoS control device, fourth QoS control device, fifth QoS control device, communication device, communication system, storage medium, program product, and computer program can refer to the beneficial effects in the corresponding method and will not be repeated here.
[0137] The present disclosure provides a QoS control method and apparatus, a communication device, a communication system, and a storage medium. In some embodiments, the terms "QoS control method" and "information processing method" and "communication method" are interchangeable; the terms "QoS control apparatus" and "information processing apparatus" and "communication apparatus" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.
[0138] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. Unless there is any contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementations in a certain embodiment can be arbitrarily combined. In addition, the embodiments can be arbitrarily combined. For example, some or all of the steps of different embodiments can be arbitrarily combined. For another example, a certain embodiment can be arbitrarily combined with the optional implementations of other embodiments.
[0139] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.
[0140] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.
[0141] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.
[0142] In the embodiments of the present disclosure, “plurality” refers to two or more.
[0143] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," and the like can be used interchangeably.
[0144] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.
[0145] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.
[0146] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.
[0147] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0148] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.
[0149] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.
[0150] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.
[0151] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).
[0152] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.
[0153] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.
[0154] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.
[0155] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.
[0156] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
[0157] In some embodiments, data, information, etc. may be obtained with the user's consent.
[0158] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.
[0159] FIG1 is a schematic diagram illustrating the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 includes a terminal 101 , an access network device 102 , and a core network device 103 .
[0160] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.
[0161] In some embodiments, the access network device 102 is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.
[0162] In some embodiments, the technical solution of the present disclosure can be applied to the open radio access network (Open RAN) architecture. In this case, the interfaces between access network devices or within access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.
[0163] In some embodiments, the access network device 102 can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.
[0164] In some embodiments, the access network device 102 may be referred to as an access network function.
[0165] In some embodiments, the core network device 103 may be a single device including a first network function 1031, a second network function 1032, a third network function 1033, a fourth network function 1034, a fifth network function 1035, etc., or may be a plurality of devices or a device group including all or part of the first network function 1031, the second network function 1032, the third network function 1033, the fourth network function 1034, the fifth network function 1035, etc. The network function may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).
[0166] In some embodiments, the core network device 103 may be referred to as a core network function.
[0167] In some embodiments, the first network function 1031 is, for example, a user plane function (UPF).
[0168] In some embodiments, the first network function 1031 is used to implement functions such as user plane (UP) data forwarding, session / flow-level based billing statistics, bandwidth limitation, UP QoS processing, etc., and the name is not limited to this.
[0169] In some embodiments, the second network function 1032 is, for example, a session management function (SMF).
[0170] In some embodiments, the second network function 1032 is used to implement session management functions, mainly performing session management, execution of control policies issued by PCF, selection of UPF, UE Internet Protocol (IP) address allocation and other functions, the name is not limited to this.
[0171] In some embodiments, the third network function 1033 is, for example, a policy control function (PCF).
[0172] In some embodiments, the third network function 1033 is used to implement policy control functions, and is mainly responsible for policy decisions related to charging policies, QoS bandwidth guarantees and policies for sessions and business flows, and the name is not limited to this.
[0173] In some embodiments, the fourth network function 1034 is, for example, an application function (AF).
[0174] In some embodiments, the fourth network function 1034 is used to provide policy management for business services, and the name is not limited thereto.
[0175] In some embodiments, the fourth network function 1034 may be independent of the core network device 103 .
[0176] In some embodiments, the fourth network function 1034 may be part of the core network device 103 .
[0177] In some embodiments, the fifth network function 1035 is, for example, an application server (AS).
[0178] In some embodiments, the fifth network function 1035 is used to provide business services, and the name is not limited thereto.
[0179] In some embodiments, the fifth network function 1035 may be independent of the core network device 103 .
[0180] In some embodiments, the fifth network function 1035 may be part of the core network device 103 .
[0181] In some embodiments, the fifth network function 1035 can be a server function of the fourth network function 1034.
[0182] In some embodiments, the fifth network function 1035 may be part of the fourth network function 1034 .
[0183] In some embodiments, the fifth network function 1035 can be independent of the fourth network function 1034.
[0184] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.
[0185] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or some of the entities in the communication system 100 , but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system 100 may include all or some of the entities shown in FIG1 , or may include other entities other than those shown in FIG1 . The number and form of the entities are arbitrary. The entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.
[0186] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).
[0187] In some cases, services such as mobile media services, online AR / VR and other XR services, online gaming, and video-based remote control of machines or drones are expected to contribute increasingly high traffic volumes to communication networks. XR services involve multimodal data streams. Multimodal data is data describing the same service / application that is input from the same device or different devices (including sensors) and may be output to one or more destination devices. The data streams within multimodal data often have some, or even strong, correlation, such as synchronization between audio and video streams, or between touch and vision. These media services share common characteristics within their data streams, between the data streams themselves, and in terms of the network transmission requirements. Effectively identifying and leveraging these characteristics will facilitate network and service transmission and control, as well as enhance service assurance and user experience.
[0188] In further cases, XRM services and interactive media services require the communication system to comprehensively consider the QoS characteristics of service data flows. Such QoS characteristics may include, for example, at least one of the following: whether parameters such as delay-sensitive guaranteed bit rate (GBR) data flows, guaranteed flow bit rate (GFBR), packet delay budget (PDB), and default maximum data burst volume (MDBV) can be simultaneously met and coordinated. It also involves multiple XRM data flows of a terminal, and XRM data flows of multiple terminals, and the consistency of QoS authorization and execution between each other.
[0189] In some embodiments, the SDF of the XRM may support PDU set-based processing, thereby enhancing QoS awareness and assurance of the SDF and improving the user's quality of experience (QoE).
[0190] In some embodiments, in systems such as 4G, 5G, 6G, and V2X, the AF may provide PDU set QoS parameters and a protocol description. In some embodiments, the PDU set QoS parameters may include at least one of the following: PDU set delay budget (PSDB), PDU set error rate (PSER), and PDU set integrated handling information (PSIHI). Then, the SMF and UPF may extend the header of the PDU in the PDU set of the SDF in combination with the protocol description and protocol header extension provided by the AF to carry the PDU set information. The carried PDU information can be used by the access network to perform PDU set-based QoS control.
[0191] In some embodiments, the PDU information may include at least one of the following: a PDU set sequence number, a start PDU or end PDU of a PDU set, a PDU sequence number within a PDU set, the number of PDUs within a PDU set, PDU set importance, and PDU set size. Here, the PDU set importance is used to indicate the importance of a PDU set relative to other PDU sets in the same QoS flow.
[0192] It can be understood that the UPF performs the mapping of the SDF to the QoS flow based on the PDR, and maps (also referred to as encapsulating) the mutually related PDUs into the PDU set. In addition, the UPF can adopt the same QoS policy for all PDU sets in the QoS flow. For example, the UPF can apply the same PDU set QoS parameters to all PDU sets in the QoS flow. In one example, the UPF can map the application flow to the QoS flow based on the packet detection information in the PDR. Some PDUs in the QoS flow can be associated with media components (for example, intra-frame coded frames and predicted frames), and the UPF classifies these PDUs as belonging to the PDU set and performs corresponding control.
[0193] Figure 2 is an interactive diagram illustrating a QoS control method according to an embodiment of the present disclosure. The present disclosure embodiment relates to a QoS control method, which is used in a communication system 100. As shown in Figure 2, the QoS control method of the present disclosure embodiment includes steps S201 to S211.
[0194] In step S201 , the fourth network function 1034 sends second information to the third network function 1033 .
[0195] In some embodiments, third network function 1033 may receive fifth information from fourth network function 1034 .
[0196] In some embodiments, the fifth information may be associated with the first SDF.
[0197] In some embodiments, the fifth information may be used by the third network function 1033 to perform QoS control on the PDU in the first SDF.
[0198] In some embodiments, the fifth information may be information related to PDU set QoS control provided by the fourth network function 1034 to the third network function 1033 .
[0199] In some embodiments, the fifth information may include at least one of the following: protocol description, PDU set QoS parameters.
[0200] In some embodiments, the protocol description may include parameters related to frame identification.
[0201] In some embodiments, the PDU set QoS parameters may be included in PDU set related assistance information.
[0202] In some embodiments, the PDU set QoS parameters may include QoS parameters for a PDU set in a QoS flow.
[0203] In some embodiments, the PDU set QoS parameter may include at least one of the following: a PDU set control indication, a PSDB, a PSER, and PDU set integrated handling information (PSIHI).
[0204] In some embodiments, a PDU set control indication may be used to indicate whether PDU set based control is activated for a flow.
[0205] In some embodiments, the PDU set control indication may be implicitly indicated through other PDU set related information provided by the fourth network function 1034 .
[0206] In some embodiments, the PDU set integration control information may be used to indicate to the application layer whether all PDUs are required for use of the PDU set.
[0207] In some embodiments, the fourth network function 1034 may send the second information to the third network function 1033 through an AF session with required QoS procedure.
[0208] In some embodiments, the fourth network function 1034 may send an Nnef_AFsessionWithQoS_Create request message to the third network function 1033. In some embodiments, the third network function 1033 may receive the Nnef_AFsessionWithQoS_Create request message from the fourth network function 1034. The Nnef_AFsessionWithQoS_Create request message may include the second information.
[0209] In some embodiments, the fourth network function 1034 may send the second information to the third network function 1033 in a PDU Session Establishment procedure.
[0210] In some embodiments, the fourth network function 1034 may send the second information to the third network function 1033 before the PDU session establishment procedure.
[0211] In step S202 , the third network function 1033 sends second information to the second network function 1032 .
[0212] In some embodiments, third network function 1033 may generate second information and send the second information to second network function 1032 .
[0213] In some embodiments, second network function 1032 may receive second information from third network function 1033 .
[0214] In some embodiments, the second information may be associated with the first SDF.
[0215] In some embodiments, the second information may be used by the second network function 1032 to perform QoS control on the PDU in the first SDF.
[0216] In some embodiments, the second information may include at least one of the following: protocol description, PDU set QoS parameters.
[0217] In some embodiments, the PDU set QoS parameters may be included in the PDU set related assistance information.
[0218] In some embodiments, the PDU set QoS parameters may include QoS parameters for a PDU set in a QoS flow.
[0219] In some embodiments, the PDU set QoS parameter may include at least one of the following: PSDB, PSER, PSIHI, and indication information of whether to discard the PDU set when the PSDB is exceeded.
[0220] In some embodiments, the third network function 1033 may generate the second information based on the fifth information.
[0221] In some embodiments, the third network function 1033 may generate a policy control and charging (PCC) rule based on the fifth information, and send the PCC rule to the second network function 1032. The PCC rule may include the second information.
[0222] In some embodiments, the third network function 1033 may generate a PCC rule based on the fifth information.
[0223] In some embodiments, the third network function 1033 may send the second information to the second network function 1032 in the PDU session establishment process.
[0224] In some embodiments, the third network function 1033 may send the second information to the second network function 1032 through a session management policy association establishment (SM Policy Association Establishment) process.
[0225] In some embodiments, the third network function 1033 may send an Npcf_SMPolicyControl_Create response message to the second network function 1032. In some embodiments, the second network function 1032 may receive the Npcf_SMPolicyControl_Create response message from the third network function 1033. The Npcf_SMPolicyControl_Create response message may include the second information.
[0226] In some embodiments, the third network function 1033 may send the second information to the second network function 1032 in a PDU Session Modification process.
[0227] In some embodiments, the third network function 1033 may send the second information to the second network function 1032 through a session management policy association modification (SM Policy Association Modification) process.
[0228] In some embodiments, the third network function 1033 may send an Npcf_SMPolicyControl_Update response message to the second network function 1032. In some embodiments, the second network function 1032 may receive the Npcf_SMPolicyControl_Update response message from the third network function 1033. The Npcf_SMPolicyControl_Update response message may include the second information.
[0229] In some embodiments, the second information and the fifth information may be the same.
[0230] In step S203 , the second network function 1032 determines the first information.
[0231] In some embodiments, the first information may be associated with a first SDF.
[0232] In some embodiments, the first information may be used by the first network function 1031 to perform QoS control on the PDU in the first SDF.
[0233] In some embodiments, the first information may include at least one of the following: protocol description, PDU set QoS parameters, and PDR.
[0234] In some embodiments, the PDU set QoS parameters may be included in the PDU set related assistance information.
[0235] In some embodiments, the PDU set QoS parameters may include QoS parameters for a PDU set in a QoS flow.
[0236] In some embodiments, the PDU set QoS parameter may include at least one of the following: PSDB, PSER, PSIHI, and indication information of whether to discard the PDU set when the PSDB is exceeded.
[0237] In some embodiments, the second network function 1032 may determine the first information based on the second information.
[0238] In some embodiments, the second network function 1032 may determine the first information based on a protocol description and / or a PDU set QoS parameter.
[0239] In some embodiments, second network function 1032 may determine the first information without receiving the second information.
[0240] In some embodiments, the second network function 1032 may determine the first information based on a local configuration.
[0241] In some embodiments, the local configuration of the second network function 1032 may include at least one of the following: operator configuration, subscriber configuration, and default configuration.
[0242] In some embodiments, the second network function 1032 may generate an N4 rule. The N4 rule may include the first information.
[0243] In some embodiments, the second network function 1032 may generate an N4 rule based on the second information.
[0244] In some embodiments, the second network function 1032 may generate N4 rules based on a local configuration.
[0245] In some embodiments, the first information and the second information may be the same.
[0246] In step S204 , the second network function 1032 sends the first information to the first network function 1031 .
[0247] In some embodiments, first network function 1032 may receive first information from second network function 1032 .
[0248] In some embodiments, the second network function 1032 may send an N4 rule to the first network function 1031. The N4 rule may include the first information.
[0249] In some embodiments, the second network function 1032 may send the first information to the first network function 1031 in the PDU session establishment process.
[0250] In some embodiments, the second network function 1032 may send the first information to the first network function 1031 in a PDU session modification procedure.
[0251] In step S205 , the second network function 1032 sends third information to the access network device 102 .
[0252] In some embodiments, the second network function 1032 may determine third information and send the third information to the access network device 102 .
[0253] In some embodiments, the access network device 102 may receive third information from the second network function 1032 .
[0254] In some embodiments, the third information may be associated with the first SDF.
[0255] In some embodiments, the third information may be used by the access network device 102 to perform QoS control on the PDU in the first SDF.
[0256] In some embodiments, the third information may include at least one of the following: protocol description, PDU set QoS parameters.
[0257] In some embodiments, the PDU set QoS parameters may be included in the PDU set related assistance information.
[0258] In some embodiments, the PDU set QoS parameters may include QoS parameters for a PDU set in a QoS flow.
[0259] In some embodiments, the PDU set QoS parameter may include at least one of the following: PSDB, PSER, PSIHI, and indication information of whether to discard the PDU set when the PSDB is exceeded.
[0260] In some embodiments, second network function 1032 may determine third information based on the second information.
[0261] In some embodiments, the second network function 1032 may determine the third information based on the protocol description and / or the PDU set QoS parameters.
[0262] In some embodiments, the second network function 1032 may determine the third information without receiving the second information.
[0263] In some embodiments, the second network function 1032 may determine the third information based on a local configuration.
[0264] In some embodiments, the local configuration of the second network function 1032 may include at least one of the following: operator configuration, subscriber configuration, and default configuration.
[0265] In some embodiments, the second network function 1032 may generate a QoS profile. The QoS profile may include third information.
[0266] In some embodiments, the second network function 1032 may generate a QoS configuration based on the second information.
[0267] In some embodiments, the second network function 1032 may generate a QoS configuration based on a local configuration.
[0268] In some embodiments, the second network function 1032 may send the QoS configuration to the access network device 102 .
[0269] In some embodiments, the second network function 1032 may send third information to the access network device 102 during the PDU session establishment process.
[0270] In some embodiments, the second network function 1032 may send third information to the access network device 102 in a PDU session modification procedure.
[0271] In some embodiments, the third information may be the same as the second information.
[0272] In step S206 , the access network device 102 sends fourth information to the terminal 101 .
[0273] In some embodiments, the access network device 102 may determine fourth information based on the third information and send the fourth information to the terminal 101 .
[0274] In some embodiments, the terminal 101 may receive fourth information from the access network device 102 .
[0275] In some embodiments, the fourth information may be associated with the first SDF.
[0276] In some embodiments, the fourth information may be used to perform QoS control on the PDU in the first SDF at the terminal 101 .
[0277] In some embodiments, the fourth information may be used for uplink data transmission by the terminal 101 .
[0278] In some embodiments, the fourth information may be used for PDU set-based QoS control of uplink data sent by terminal 101 .
[0279] In some embodiments, the fourth information may include at least one of the following: protocol description, PDU set QoS parameters.
[0280] In some embodiments, the PDU set QoS parameters may be included in the PDU set related assistance information.
[0281] In some embodiments, the PDU set QoS parameters may include QoS parameters for a PDU set in a QoS flow.
[0282] In some embodiments, the PDU set QoS parameter may include at least one of the following: PSDB, PSER, PSIHI, and indication information of whether to discard the PDU set when the PSDB is exceeded.
[0283] In some embodiments, the fourth information may be the same as the third information.
[0284] In step S207 , the fifth network function 1035 sends a first PDU to the first network function 1031 .
[0285] In some embodiments, the first PDU may belong to a first SDF.
[0286] In some embodiments, the first PDU may belong to a first QoS flow corresponding to the first SDF.
[0287] In some embodiments, the first QoS flow may include one or more PDU sets.
[0288] In some embodiments, different PDU sets in the first QoS flow may have the same or different numbers of PDUs.
[0289] In some embodiments, all PDU sets in the first QoS flow may have the same PDU set QoS parameters.
[0290] In some embodiments, the first PDU may not have an extended header.
[0291] In some embodiments, the extended header may be used by the first network function 1031 to identify PDU set information for the PDU.
[0292] In some embodiments, the extended header may be used by the first network function 1031 to identify the PDU set to which the PDU belongs.
[0293] In some embodiments, an extended header may be used to identify a PDU set.
[0294] In some embodiments, an extended header may be used to identify the end of a data burst.
[0295] In some embodiments, the extended header may include PDU set information.
[0296] In some embodiments, the PDU set information may include at least one of the following: a PDU set sequence number (PSSN), a start PDU or end PDU of a PDU set, a PDU sequence number within a PDU set (PSN), the number of PDUs in a PDU set, PDU set importance (PSI), PDU set size (PSSize), and an end of data burst (EDB).
[0297] In some embodiments, the identification of the PDU set in the extension header can be used to identify the media component.
[0298] In some embodiments, the end of a data burst indication in the extended header may be used to identify the media component.
[0299] In some embodiments, a PDU with an extension header may be identified as a media component and as belonging to a PDU set.
[0300] In some embodiments, a QoS flow may be identified using a QoS flow identifier.
[0301] In some embodiments, each PDU set in a QoS flow may be identified using a PDU set sequence number of the PDU set.
[0302] In some embodiments, a QoS flow may include one or more PDU sets.
[0303] In some embodiments, different PDU sets in a QoS flow may have the same or different numbers of PDUs, that is, different PDU sets in a flow may have the same or different sizes.
[0304] In step S208 , the first network function 1031 determines that the first PDU does not have an extended header.
[0305] In some embodiments, the first network function 1031 may determine, based on the first information, that the first PDU does not have an extended header.
[0306] In some embodiments, the first network function 1031 may determine, based on a local configuration, that the first PDU does not have an extended header.
[0307] In some embodiments, the first network function 1031 may determine, based on the protocol description and / or the PDR, that the first PDU does not have an extended header.
[0308] In some embodiments, the first network function 1031 may determine that the first PDU does not have an extended header based on PDU set information identification for the first PDU.
[0309] In some embodiments, when the first PDU does not include any PDU set information, the first network function 1031 may determine that the first PDU does not have an extended header.
[0310] In some embodiments, the first network function 1031 can determine that the first PDU does not have an extended header by at least one of the following methods: matching the header and payload of RTP and / or SRTP, using a new RTP extended header, information provided by the N6 encapsulation header, detection based on traffic characteristics, and UPF local configuration.
[0311] In step S2019 , the first network function 1031 maps the first PDU to a first PDU set.
[0312] In some embodiments, mapping the first PDU to the first PDU set by the first network function 1031 can be understood as the first network function 1031 encapsulating the first PDU into the first PDU set.
[0313] In some embodiments, the first network function 1031 may map the first PDU without the extended header to the first PDU set.
[0314] In some embodiments, the first network function 1031 may map the first PDU to a first PDU set based on the first information.
[0315] In some embodiments, the first network function 1031 may map the first PDU to the first PDU set according to local configuration.
[0316] In some embodiments, the first PDU set may belong to a first QoS flow corresponding to a first SDF.
[0317] In some embodiments, the first PDU set may be a PDU set independent of an existing PDU set in the first QoS flow corresponding to the first SDF.
[0318] In some embodiments, the first PDU set and other PDU sets in the first QoS flow corresponding to the first SDF may have the same PDU set QoS parameters.
[0319] In some embodiments, the first PDU set may be a new PDU set.
[0320] In some embodiments, the first PDU set may be integrated from one or more first PDUs.
[0321] In some embodiments, the first PDU set may be integrated from one or more PDUs, and none of these PDUs include an extended header.
[0322] In some embodiments, one or more PDUs of the first PDU set may have the same or similar PDU characteristics.
[0323] In some embodiments, the PDUs in the first PDU set may arrive within a time window.
[0324] In some embodiments, the time window may be a time length expressed in time units such as frames, subframes, and time slots.
[0325] In some embodiments, the time window may be a time length expressed in time units such as seconds, microseconds, femtoseconds, or picoseconds.
[0326] In some embodiments, the time window may be of relatively small duration.
[0327] In some embodiments, the PDUs in the first PDU set may arrive at the same or similar times.
[0328] In some embodiments, the first PDU set may include one PDU.
[0329] In some embodiments, the time window may have a relatively large duration.
[0330] In some embodiments, the PDUs in the first PDU set may arrive within a preset length of time.
[0331] In some embodiments, the first network function 1031 maps the first PDU to the first PDU set to obtain the second PDU.
[0332] In step S210 , the first network function 1031 sends a second PDU to the access network device 102 .
[0333] In some embodiments, the access network device 102 may receive a second PDU from the first network function 1031 .
[0334] In some embodiments, the second PDU may be a PDU obtained by mapping the first PDU to the first PDU set.
[0335] In some embodiments, the second PDU may include PDU set information.
[0336] In some embodiments, the second PDU may include an extended header, and the extended header may include PDU set information.
[0337] In some embodiments, the PDU set information of the second PDU may include at least one of the following: the sequence number of the first PDU set, the start PDU or end PDU of the first PDU set, the PDU sequence number within the first PDU set, the number of PDUs within the first PDU set, the importance of the first PDU set, the size of the first PDU set, and the end of the data burst.
[0338] In step S211 , the access network device 102 sends a second PDU to the terminal 101 .
[0339] In some embodiments, the terminal 101 may receive a second PDU from the access network device 102 .
[0340] In some embodiments, the access network device 102 may perform QoS control based on the PDU set according to the third information.
[0341] In some embodiments, the access network device 102 may send a second PDU to the terminal 101 based on the third information.
[0342] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.
[0343] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.
[0344] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.
[0345] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.
[0346] In some embodiments, terms such as "frame", "radio frame", "subframe", "slot", "sub-slot", "mini-slot", "symbol", "symbol", and "transmission time interval (TTI)" can be used interchangeably.
[0347] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.
[0348] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.
[0349] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "some", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, some A, any A, or first A, etc., but not limited to this.
[0350] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values (for example, comparison with a predetermined value), but is not limited thereto.
[0351] The QoS control method involved in the embodiments of the present disclosure may include at least one of steps S201 to S211. For example, step S204 can be implemented as an independent embodiment. For example, the combination of steps S203 and S204 can be implemented as an independent embodiment. For example, the combination of steps S207, S208, and S209 can be implemented as an independent embodiment. For example, the combination of steps S204, S207, S208, S209, and S210 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S201 to S211 are not limited to this.
[0352] In some embodiments, at least two of steps S201 to S211 may be performed in an interchangeable order or simultaneously. For example, steps S204 and S205 may be performed in an interchangeable order or simultaneously. For example, steps S206 and S211 may be performed in an interchangeable order or simultaneously.
[0353] In some embodiments, steps S201 to S203 and S204 to S211 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
[0354] In some embodiments, steps S201 to S206 and S210 to S211 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
[0355] FIG3 is a flow chart illustrating a QoS control method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a QoS control method. The QoS control method is executed by the first network function 1031. As shown in FIG3 , the method includes steps S301 to S305.
[0356] In step S301, first information is obtained.
[0357] The optional implementation of step S301 can refer to the optional implementation of step S204 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.
[0358] In some embodiments, first network function 1031 may receive the first information from second network function 1032 , but is not limited thereto. In some embodiments, first network function 1031 may receive the first information from another entity other than second network function 1032 .
[0359] In some embodiments, the first network function 1031 may obtain first information specified by a protocol.
[0360] In some embodiments, the first network function 1031 may obtain the first information from a higher layer.
[0361] In some embodiments, the first network function 1031 may perform processing to obtain the first information.
[0362] In step S302, a first PDU is obtained.
[0363] The optional implementation of step S302 can refer to the optional implementation of step S207 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.
[0364] In some embodiments, the first network function 1031 may receive the first PDU from the fifth network function 1035 , but is not limited thereto. In some embodiments, the first network function 1031 may receive the first PDU from another entity other than the fifth network function 1035 .
[0365] In some embodiments, the first network function 1031 may obtain the first PDU based on a local configuration.
[0366] In some embodiments, the fifth network function 1035 may be configured to send the first PDU to the first network function 1031 .
[0367] In step S303, it is determined that the first PDU does not have an extended header.
[0368] The optional implementation of step S303 can refer to the optional implementation of step S208 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.
[0369] In some embodiments, in some embodiments, the extended header may include PDU set information.
[0370] In some embodiments, the extended header may include at least one of the following: PDU set sequence number, start PDU or end PDU of the PDU set, PDU sequence number within the PDU set, number of PDUs within the PDU set, PDU set importance, PDU set size, and end of data burst.
[0371] In some embodiments, the first network function 1031 can determine that the first PDU does not have an extended header by at least one of the following methods: matching the header and payload of RTP and / or SRTP, using a new RTP extended header, information provided by the N6 encapsulation header, detection based on traffic characteristics, and UPF local configuration.
[0372] In step S304, the first PDU is mapped to a first PDU set.
[0373] The optional implementation of step S304 can refer to the optional implementation of step S209 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.
[0374] In some embodiments, the first PDU set may be integrated from one or more PDUs, and the one or more PDUs do not include an extended header.
[0375] In some embodiments, the PDUs of the first PDU set may arrive within a time window.
[0376] In some embodiments, the first PDU set may belong to a first QoS flow corresponding to the first SDF, and all PDU sets in the first QoS flow may have the same PDU set QoS parameters.
[0377] In some embodiments, the first network function 1031 may map the first PDU to a first PDU set based on first information associated with the first SDF.
[0378] In step S305 , a second PDU is sent.
[0379] The optional implementation of step S305 can refer to the optional implementation of step S210 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.
[0380] In some embodiments, the second PDU may be obtained by mapping the first PDU to the first PDU set.
[0381] In some embodiments, the first network function 1031 may send the second PDU to the access network device 102 , but is not limited thereto. In some embodiments, the first network function 1031 may send the second PDU to another entity other than the fifth network function 1035 .
[0382] In some embodiments, the access network device 102 may be configured to receive a second PDU from the first network function 1031 .
[0383] The QoS control method involved in the embodiments of the present disclosure may include at least one of steps S301 to S305. For example, step S301 can be implemented as an independent embodiment. For example, the combination of steps S302, S303, and S304 can be implemented as an independent embodiment. For example, the combination of steps S301, S302, S303, and S304 can be implemented as an independent embodiment. For example, the combination of steps S302, S303, S304, and S305 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S301 to S305 are not limited to this.
[0384] In some embodiments, steps S302 to S305 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
[0385] In some embodiments, steps S301 and S305 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
[0386] FIG4 is a flow chart illustrating a QoS control method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a QoS control method. The QoS control method is executed by the second network function 1032. As shown in FIG4 , the method includes steps S401 to S404.
[0387] In step S401, second information is obtained.
[0388] The optional implementation of step S401 can refer to the optional implementation of step S202 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
[0389] In some embodiments, second network function 1032 may receive the second information from third network function 1033 , but is not limited thereto. In some embodiments, second network function 1032 may receive the second information from another entity other than third network function 1033 .
[0390] In some embodiments, the second network function 1032 may obtain second information specified by the protocol.
[0391] In some embodiments, the second network function 1032 may obtain the second information from a higher layer.
[0392] In some embodiments, the second network function 1032 may perform processing to obtain the second information.
[0393] In some embodiments, the second information may include at least one of the following: PDU set QoS parameters, protocol description.
[0394] In step S402, first information is determined.
[0395] The optional implementation of step S402 can refer to the optional implementation of step S203 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
[0396] In some embodiments, the second network function 1032 may determine the first information based on the second information.
[0397] In step S403, the first information is sent.
[0398] The optional implementation of step S403 can refer to the optional implementation of step S204 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
[0399] In some embodiments, second network function 1032 may send the first information to first network function 1031 , but is not limited thereto. In some embodiments, first network function 1031 may send the first information to another entity other than first network function 1031 .
[0400] In some embodiments, the first information may include at least one of the following: PDU set QoS parameters, protocol description, and PDR.
[0401] In some embodiments, the first network function 1031 may be configured to receive first information from the second network function 1032 .
[0402] In some embodiments, the first information can be used by the first network function 1031 to determine that the first PDU does not have an extended header and to map the first PDU to a first PDU set. For optional implementations, see the optional implementations of steps S208 and S209 in FIG. 2 , as well as other related portions of the embodiment involved in FIG. 2 , which are not further described here.
[0403] In step S404, the third information is sent.
[0404] The optional implementation of step S404 can refer to the optional implementation of step S205 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.
[0405] In some embodiments, the third information may include at least one of the following: PDU set QoS parameters, protocol description.
[0406] In some embodiments, the second network function 1031 may send the third information to the access network device 102, but is not limited thereto. In some embodiments, the first network function 1031 may send the third information to another entity other than the access network device 102.
[0407] In some embodiments, the access network device 102 may be configured to receive third information from the second network function 1032 .
[0408] In some embodiments, the third information may be used by the access network device 102 to send the fourth information. Optional implementations thereof may refer to the optional implementations of step S206 in FIG2 and other related parts of the embodiment involved in FIG2 , which will not be described in detail here.
[0409] The QoS control method involved in the embodiments of the present disclosure may include at least one of steps S401 to S404. For example, step S403 may be implemented as an independent embodiment. For example, the combination of steps S402 and S403 may be implemented as an independent embodiment. For example, the combination of steps S403, S304, and S405 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S401 to S404 are not limited to this.
[0410] In some embodiments, steps S401 , S402 , and S404 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
[0411] FIG5 is a flow chart illustrating a QoS control method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a QoS control method. The QoS control method is executed by access network device 102. As shown in FIG5, the method includes steps S501 to S505.
[0412] In step S501, third information is obtained.
[0413] The optional implementation of step S501 can refer to the optional implementation of step S205 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.
[0414] In some embodiments, the access network device 102 may receive the third information from the second network function 1032 , but is not limited thereto. In some embodiments, the access network device 102 may receive the third information from other entities besides the second network function 1032 .
[0415] In some embodiments, the third information may include at least one of the following: PDU set QoS parameters, protocol description.
[0416] In some embodiments, the access network device 102 may obtain third information specified by the protocol.
[0417] In some embodiments, the access network device 102 may obtain the third information from a higher layer.
[0418] In some embodiments, the access network device 102 may perform processing to obtain the third information.
[0419] In step S502, a second PDU is obtained.
[0420] The optional implementation of step S502 can refer to the optional implementation of step S210 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.
[0421] In some embodiments, the second PDU may be obtained by mapping the first PDU belonging to the first SDF to the first PDU set.
[0422] In some embodiments, the first PDU may not have an extended header.
[0423] In some embodiments, an extended header may be used to identify a PDU set.
[0424] In some embodiments, the first PDU set may be integrated from one or more PDUs.
[0425] In some embodiments, none of the PDUs in the first PDU set may include an extension header.
[0426] In some embodiments, the PDUs of the first PDU set may arrive within a time window.
[0427] In some embodiments, the first PDU set may belong to a first QoS flow corresponding to a first SDF.
[0428] In some embodiments, all PDU sets in the first QoS flow may have the same PDU set QoS parameters.
[0429] In some embodiments, the second PDU may include at least one of the following: the sequence number of the first PDU set, the start PDU or end PDU of the first PDU set, the PDU sequence number within the first PDU set, the number of PDUs within the first PDU set, the importance of the first PDU set, the size of the first PDU set, and the end of the data burst.
[0430] In some embodiments, the access network device 102 may receive the second PDU from the first network function 1031 , but is not limited thereto. In some embodiments, the access network device 102 may receive the second PDU from another entity other than the first network function 1031 .
[0431] In some embodiments, the access network device 102 may obtain the second PDU based on local configuration.
[0432] In some embodiments, the first network function 1031 may be configured to send a second PDU to the access network device 102 .
[0433] In step S503, a second PDU is sent.
[0434] The optional implementation of step S503 can refer to the optional implementation of step S211 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.
[0435] In some embodiments, the access network device 102 may send the second PDU to the terminal 101 , but the present invention is not limited thereto. In some embodiments, the access network device 102 may send the second PDU to another entity other than the terminal 101 .
[0436] In step S504, the fourth information is sent.
[0437] The optional implementation of step S504 can refer to the optional implementation of step S206 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.
[0438] In some embodiments, the access network device 102 may send the fourth information to the terminal 101 , but the present invention is not limited thereto. In some embodiments, the access network device 102 may send the fourth information to another entity other than the terminal 101 .
[0439] In some embodiments, the access network device 102 may send fourth information to the terminal based on the third information.
[0440] In some embodiments, the fourth information may include at least one of the following: PDU set QoS parameters, protocol description.
[0441] In some embodiments, the terminal 101 may be configured to receive fourth information from the access network device 102 .
[0442] In some embodiments, the fourth information may be used for uplink data transmission by the terminal 101 .
[0443] The QoS control method involved in the embodiments of the present disclosure may include at least one of steps S501 to S504. For example, step S502 may be implemented as an independent embodiment. For example, the combination of steps S501 and S502 may be implemented as an independent embodiment. For example, the combination of steps S501, S502, and S503 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more steps from steps S501 to S504 are not limited to this.
[0444] In some embodiments, at least two of steps S501 to S504 may be performed in an exchanged order or simultaneously. For example, steps S503 and S504 may be performed in an exchanged order or simultaneously.
[0445] In some embodiments, steps S501 , S503 , and S504 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
[0446] FIG6 is a flow chart illustrating a QoS control method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a QoS control method. The QoS control method is executed by terminal 101. As shown in FIG6, the method includes steps S601 to S602.
[0447] In step S601, a second PDU is obtained.
[0448] The optional implementation of step S602 can refer to the optional implementation of step S211 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.
[0449] In some embodiments, the terminal 101 may receive the second PDU from the access network device 102 , but the present invention is not limited thereto. In some embodiments, the terminal 101 may receive the second PDU from another entity other than the access network device 102 .
[0450] In some embodiments, the access network device 102 may be configured to send a second PDU to the terminal 101 .
[0451] In step S602, fourth information is obtained.
[0452] The optional implementation of step S602 can refer to the optional implementation of step S206 in FIG2 and other related parts in the embodiment involved in FIG2 , which will not be described in detail here.
[0453] In some embodiments, the fourth information may include at least one of the following: PDU set QoS parameters, protocol description.
[0454] In some embodiments, the access network device 102 may send the fourth information to the terminal 101 , but the present invention is not limited thereto. In some embodiments, the access network device 102 may send the fourth information to another entity other than the terminal 101 .
[0455] In some embodiments, the access network device 102 may be configured to send fourth information to the terminal 101 .
[0456] In some embodiments, the fourth information may be used for uplink data transmission by the terminal 101 .
[0457] The QoS control method involved in the embodiments of the present disclosure may include at least one of steps S601 and S602. For example, step S601 may be implemented as an independent embodiment. For example, a combination of steps S601 and S602 may be implemented as an independent embodiment. It should be noted that the possible independent embodiments consisting of one or more of steps S601 and S602 are not limited to this.
[0458] In some embodiments, steps S601 and S602 may be performed in an exchanged order or simultaneously.
[0459] In some embodiments, steps S601 and S602 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
[0460] FIG7 is a flow chart illustrating a QoS control method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a QoS control method. The QoS control method is executed by a communication system 100. As shown in FIG7 , the method includes steps S701 to S707.
[0461] In step S701 , the second network function 1032 determines first information.
[0462] The optional implementation of step S701 can refer to the optional implementation of step S203 in Figure 2, step S4102 in Figure 4, and other related parts in the embodiments involved in Figures 2 and 4, which will not be repeated here.
[0463] In step S702 , the second network function 1032 sends first information to the first network function 1031 .
[0464] Optional implementations of step S702 can refer to the optional implementations of step S204 in FIG. 2 , step S301 in FIG. 3 , step S403 in FIG. 4 , and other related parts in the embodiments involved in FIG. 2 , FIG. 3 , and FIG. 4 , which will not be described in detail here.
[0465] In step S703 , the first network function 1031 obtains a first PDU.
[0466] The optional implementation of step S703 can refer to the optional implementation of step S207 in Figure 2, the optional implementation of step S302 in Figure 3, and other related parts in the embodiments involved in Figures 2 and 3, which will not be repeated here.
[0467] In step S704 , the first network function 1031 determines that the first PDU does not have an extended header.
[0468] Optional implementations of step S704 can refer to step S208 in FIG. 2 , optional implementations of step S303 in FIG. 3 , and other related parts in the embodiments involved in FIG. 2 and FIG. 3 , which will not be described in detail here.
[0469] In step S705 , the first network function 1031 maps the first PDU to a first PDU set.
[0470] Optional implementations of step S705 can refer to step S209 in FIG. 2 , optional implementations of step S304 in FIG. 3 , and other related parts in the embodiments involved in FIG. 2 and FIG. 3 , which will not be described in detail here.
[0471] In step S706 , the first network function 1031 sends the second PDU to the access network device 102 .
[0472] Optional implementations of step S706 can refer to the optional implementations of step S210 in FIG. 2 , step S305 in FIG. 3 , step S502 in FIG. 5 , and other related parts in the embodiments involved in FIG. 2 , FIG. 3 , and FIG. 5 , which will not be described in detail here.
[0473] In step S707 , the access network device 102 sends the second PDU to the terminal 101 .
[0474] Optional implementations of step S707 can refer to the optional implementations of step S211 in FIG. 2 , step S503 in FIG. 5 , step S601 in FIG. 6 , and other related parts in the embodiments involved in FIG. 2 , FIG. 5 , and FIG. 6 , which will not be described in detail here.
[0475] In some embodiments, the above method may include the method described in the above-mentioned embodiments of the communication system side, terminal side, access network equipment side, core network equipment side, first network function side, second network function side, etc., which will not be repeated here.
[0476] FIG8 is a flow chart illustrating a QoS control method according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a QoS control method. The QoS control method is executed by core network device 103. As shown in FIG8 , the method includes steps S801 to S803.
[0477] In step S801 , the core network device 103 obtains a first PDU.
[0478] Optional implementations of step S801 can refer to step S203 in FIG. 2 , optional implementations of step S402 in FIG. 4 , and other related parts in the embodiments involved in FIG. 2 and FIG. 4 , which will not be described in detail here.
[0479] In step S802 , the core network device 103 determines that the first PDU does not have an extended header.
[0480] The optional implementation of step S802 can refer to the optional implementation of step S208 in Figure 2, the optional implementation of step S303 in Figure 3, and other related parts in the embodiments involved in Figures 2 and 3, which will not be repeated here.
[0481] In step S803 , the first network function 1031 maps the first PDU to a first PDU set.
[0482] Optional implementations of step S803 may refer to step S209 in FIG. 2 , optional implementations of step S304 in FIG. 3 , and other related parts in the embodiments involved in FIG. 2 and FIG. 3 , which will not be described in detail here.
[0483] In some embodiments, the above method may include the method described in the above embodiments of the communication system side, core network side, first network function side, second network function side, etc., which will not be repeated here.
[0484] The embodiments of the present disclosure also propose an apparatus for implementing any of the above methods. For example, a device is proposed, wherein the device includes a unit or module for implementing each step performed by a terminal in any of the above methods. For another example, another device is proposed, which includes a unit or module for implementing each step performed by a network device (such as an access network device, a core network function node, a core network device, etc.) in any of the above methods. It should be understood that the division of the units or modules in the above apparatus is only a division of logical functions. In actual implementation, they can be fully or partially integrated into a physical entity or physically separated. In addition, the units or modules in the apparatus can be implemented in the form of a processor calling software: for example, the apparatus includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the units or modules of the above apparatus, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the apparatus or a memory outside the apparatus. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.
[0485] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.
[0486] Figure 9 is a schematic structural diagram of a first QoS control device according to an embodiment of the present disclosure. As shown in Figure 9, the first QoS control device 900 includes a receiving module 901 and a processing module 902. The receiving module 901 is configured to receive a first PDU, wherein the first PDU belongs to a first SDF. The processing module 902 is configured to determine that the first PDU does not have an extended header, wherein the extended header is used to identify a PDU set; and map the first PDU to the first PDU set. Optionally, the receiving module 901 can be used to execute the steps related to reception performed by the first network function 1031 in any of the above methods, and the processing module 902 can be used to execute the steps related to determination and mapping performed by the first network function 1031 in any of the above methods, which are not repeated here. Optionally, the first QoS control device 900 may also include a sending module. The sending module is used to execute the steps related to sending performed by the first network function 1031 in any of the above methods, which are not repeated here.
[0487] Figure 10 is a schematic diagram of the structure of a second QoS control device according to an embodiment of the present disclosure. As shown in Figure 10, the second QoS control device 1000 includes a processing module 1001 and a sending module 1002. The processing module 1001 is configured to determine first information associated with a first SDF. The sending module 1002 is configured to send the first information to the first network function 1031, where the first information is used by the first network function 1031 to perform QoS control on a first PDU in the first SDF. The first PDU does not have an extended header, which is used to identify a PDU set. Optionally, the processing module 1001 can be configured to execute the determination-related steps performed by the second network function 1032 in any of the above methods, and the sending module 1002 can be configured to execute the sending-related steps performed by the second network function 1032 in any of the above methods, which are not further described here. Optionally, the second QoS control device 1000 may also include a receiving module. The receiving module is configured to execute the reception-related steps performed by the second network function 1032 in any of the above methods, which are not further described here.
[0488] Figure 11 is a structural diagram of the third QoS control device according to an embodiment of the present disclosure. As shown in Figure 11, the third QoS control device 1100 includes a receiving module 1101. The receiving module 1101 is configured to receive a second PDU sent by the first network function 1031, wherein the second PDU is obtained by mapping the first PDU belonging to the first SDF to the first PDU set, and the first PDU does not have an extended header, and the extended header is used to identify the PDU set. Optionally, the receiving module 1101 can be used to execute the steps related to reception performed by the access network device 102 in any of the above methods, which will not be repeated here. Optionally, the first QoS control device 1100 may also include a sending module. The sending module is used to execute the steps related to sending performed by the access network device 102 in any of the above methods, which will not be repeated here.
[0489] FIG12 is a schematic structural diagram of a fourth QoS control device according to an embodiment of the present disclosure. As shown in FIG12 , the fourth QoS control device 12100 includes a receiving module 1201. The receiving module 1201 is configured to receive a second PDU sent by the access network device 1031, wherein the second PDU is obtained by mapping the first PDU belonging to the first SDF to the first PDU set, and the first PDU does not have an extended header, and the extended header is used to identify the PDU set. Optionally, the receiving module 1201 can be used to execute the steps related to reception performed by the terminal 101 in any of the above methods, which will not be repeated here.
[0490] Figure 13 is a schematic structural diagram of a fifth QoS control device according to an embodiment of the present disclosure. As shown in Figure 13, the fifth QoS control device 13100 includes a receiving module 1301 and a processing module 1302. The receiving module 1301 is configured to receive a first PDU, wherein the first PDU belongs to a first SDF. The processing module 1302 is configured to determine that the first PDU does not have an extended header, wherein the extended header is used to identify a PDU set; and map the first PDU to the first PDU set. Optionally, the receiving module 1301 can be used to execute the steps related to reception performed by the core network device 103 in any of the above methods, and the processing module 1302 can be used to execute the steps related to determination and mapping performed by the core network device 103 in any of the above methods, which are not repeated here. Optionally, the fifth QoS control device 1300 may also include a sending module. The sending module is used to execute the steps related to sending performed by the core network device 103 in any of the above methods, which are not repeated here.
[0491] Figure 14 is a schematic diagram of the structure of a communication device 1400 according to an embodiment of the present disclosure. Communication device 1400 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 1400 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.
[0492] As shown in Figure 14, the communication device 1400 includes one or more processors 1401. The processor 1401 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The processor 1401 is used to call instructions to enable the communication device 1400 to perform any of the above methods.
[0493] In some embodiments, the communication device 1401 further includes one or more memories 1402 for storing instructions. Optionally, all or part of the memories 1402 may be located outside the communication device 1400.
[0494] In some embodiments, the communication device 1400 further includes one or more transceivers 1403. When the communication device 1400 includes one or more transceivers 1403, the communication steps such as sending and receiving in the above method are performed by the transceiver 1403, and the other steps are performed by the processor 1401.
[0495] Optionally, the communication device 1400 further includes one or more interface circuits 1404, which are connected to the memory 1402. The interface circuits 1404 may be configured to receive signals from the memory 1402 or other devices, and may be configured to send signals to the memory 1402 or other devices. For example, the interface circuits 1404 may read instructions stored in the memory 1402 and send the instructions to the processor 1401.
[0496] The communication device 1400 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 1400 described in the present disclosure is not limited thereto, and the structure of the communication device 1400 may not be limited by FIG. 14. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.
[0497] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the communication device 1400, the communication device 1400 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.
[0498] The present disclosure also provides a program product, which, when executed by the communication device 1400, enables the communication device 1400 to perform any of the above methods. Optionally, the program product is a computer program product.
[0499] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.
Claims
1. A method for controlling quality of service (QoS), characterized in that: Executed by a first network function, the method includes: Receiving a first packet data unit PDU, wherein the first PDU belongs to a first service data flow SDF; Determining that the first PDU does not have an extended header, wherein the extended header is used to identify a PDU set; The first PDU is mapped to a first PDU set.
2. The method according to claim 1, characterized in that: The extended packet header includes at least one of the following: PDU set sequence number; The start PDU or end PDU of a PDU set; The PDU sequence number within the PDU set; The number of PDUs in the PDU set; PDU set importance; PDU set size; The data burst ends.
3. The method according to claim 1 or 2, characterized in that: The first PDU set is integrated by one or more PDUs, and the one or more PDUs do not include the extended header.
4. The method according to claim 3, characterized in that The one or more PDUs of the first PDU set arrive within a time window.
5. The method according to any one of claims 1 to 4, characterized in that The first PDU set belongs to a first QoS flow corresponding to the first SDF, and all PDU sets in the first QoS flow have the same PDU set QoS parameters.
6. The method according to claim 1, characterized in that The determining that the first PDU does not have an extended header is implemented by at least one of the following: Packet header and payload matching of the real-time transport protocol RTP and / or the secure real-time transport protocol SRTP; Use new RTP extension header; Information is provided by the N6 encapsulation header; Detection based on flow characteristics; The user plane function UPF is configured locally.
7. The method according to any one of claims 1 to 6, characterized in that Mapping the first PDU to a first PDU set includes: The first PDU is mapped to the first PDU set according to first information associated with the first SDF.
8. The method according to claim 7, characterized in that The first information includes at least one of the following: PDU set QoS parameters, protocol description, and packet detection rule PDR.
9. The method according to claim 7 or 8, characterized in that: Before receiving the first PDU, the method further includes: The first information is received from a second network function.
10. The method according to any one of claims 1 to 9, characterized in that After mapping the first PDU to the first PDU set, the method further includes: A second PDU is sent to the access network device, wherein the second PDU is obtained by mapping the first PDU to the first PDU set.
11. A method for controlling quality of service (QoS), characterized in that: Executed by a second network function, the method includes: Determining first information associated with a first service data flow SDF; The first information is sent to a first network function, wherein the first information is used by the first network function to perform QoS control on a first packet data unit PDU in the first SDF, the first PDF does not have an extended header, and the extended header is used to identify a PDU set.
12. The method according to claim 11, characterized in that The first information includes at least one of the following: PDU set QoS parameters, protocol description, and packet detection rule PDR.
13. The method according to claim 11 or 12, characterized in that: The determining the first information associated with the first SDF includes: receiving second information, wherein the second information includes at least one of the following: the PDU set QoS parameter and the protocol description; The first information is determined according to the second information.
14. The method according to any one of claims 11 to 13, characterized in that The method further comprises: Sending third information to the access network device, wherein the third information includes at least one of the following: PDU set QoS parameters and protocol description.
15. A method for controlling quality of service (QoS), characterized in that: The method is performed by an access network device and includes: A second packet data unit PDU sent by a first network function is received, wherein the second PDU is obtained by mapping a first PDU belonging to a first service data flow SDF to a first PDU set, and the first PDU does not have an extended header, and the extended header is used to identify the PDU set.
16. The method according to claim 15, characterized in that The first PDU set is integrated by one or more PDUs, and the one or more PDUs do not include the extended header.
17. The method according to claim 16, characterized in that The one or more PDUs of the first PDU set arrive within a time window.
18. The method according to any one of claims 15 to 17, characterized in that The first PDU set belongs to a first QoS flow corresponding to the first SDF, and all PDU sets in the first QoS flow have the same PDU set QoS parameters.
19. The method according to any one of claims 15 to 18, characterized in that The second PDU includes at least one of the following: a sequence number of the first PDU set; The start PDU or the end PDU of the first PDU set; a PDU sequence number in the first PDU set; the number of PDUs in the first PDU set; The importance of the first PDU set; the size of the first PDU set; The data burst ends.
20. The method according to any one of claims 15 to 19, characterized in that The method further comprises: Send the second PDU to the terminal.
21. The method according to any one of claims 15 to 20, characterized in that The method further comprises: Receiving third information sent by the first network function, wherein the third information includes at least one of the following: PDU set QoS parameters and protocol description; The sending the second PDU to the terminal includes: The second PDU is sent to the terminal according to the third information.
22. The method according to claim 21, characterized in that The method further comprises: The fourth information is sent to the terminal according to the third information, wherein the fourth information includes at least one of the following: the PDU set QoS parameter and the protocol description.
23. A method for controlling quality of service (QoS), characterized in that: Executed by a terminal, the method includes: A second packet data unit PDU is received from an access network device, wherein the second PDU is obtained by mapping a first PDU belonging to a first service data flow SDF to a first PDU set, and the first PDU does not have an extended header, and the extended header is used to identify the PDU set.
24. The method according to claim 23, characterized in that The method further comprises: receiving fourth information from the access network device, wherein the fourth information includes at least one of the following: a PDU set QoS parameter and a protocol description; The fourth information is used for uplink data sending.
25. A quality of service (QoS) control device, characterized in that: The device comprises: A receiving module, configured to receive a first packet data unit PDU, wherein the first PDU belongs to a first service data flow SDF; The processing module is configured to determine that the first PDU does not have an extended header, wherein the extended header is used to identify a PDU set; and to map the first PDU to a first PDU set.
26. A quality of service (QoS) control device, characterized in that: The device comprises: A processing module, configured to determine first information associated with a first service data flow SDF; A sending module is configured to send the first information to a first network function, wherein the first information is used by the first network function to perform QoS control on a first packet data unit PDU in the first SDF, and the first PDF does not have an extended header, and the extended header is used to identify a PDU set.
27. A quality of service (QoS) control device, characterized in that: The device comprises: A receiving module is configured to receive a second packet data unit PDU sent by the first network function, wherein the second PDU belongs to The first PDU of the first service data flow SDF is mapped to the first PDU set, where the first PDU does not have an extended header, and the extended header is used to identify the PDU set.
28. A quality of service (QoS) control device, characterized in that: The device comprises: The receiving module is configured to receive a second packet data unit PDU from an access network device, wherein the second PDU is obtained by mapping a first PDU belonging to a first service data flow SDF to a first PDU set, and the first PDU does not have an extended header, and the extended header is used to identify the PDU set.
29. A communication device, characterized in that: The communication device comprises: at least one processor; at least one memory for storing instructions; The processor is used to call the instruction so that the communication device executes the quality of service QoS control method as described in any one of claims 1 to 24.
30. A communication system, characterized in that: The communication system comprises: A first network function, configured to perform the method according to any one of claims 1 to 10; A second network function, configured to perform the method according to any one of claims 11 to 14; Access network equipment, configured to perform the method according to any one of claims 15 to 22; A terminal, configured to execute the method as claimed in claim 23 or 24.
31. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the quality of service (QoS) control method according to any one of claims 1 to 24.
Citation Information
Patent Citations
Data transmission guaranteeing method and communication equipment
CN111436081A
Device requested protocol data unit session modification in the 5g system
US20190116518A1
Cited By
Scheduling of DL PDU set based on DL delay
WO2026051390A1
