QUALITY OF SERVICE FLOW TRANSMISSION METHOD, BASE STATION, TERMINAL, AND STORAGE MEDIUM

Information

  • Patent Application
  • 20240172039
  • Publication Number
    20240172039
  • Date Filed
    October 14, 2021
    2 years ago
  • Date Published
    May 23, 2024
    a month ago
Abstract
Provided are a quality of service flow transmission method, a base station, a terminal, and a storage medium. The quality of service flow transmission method includes acquiring at least one protocol data unit (PDU) session sent by a core network, where the information frame format of the PDU session carries indication information; and determining the category to which each PDU session belongs according to the indication information.
Description
TECHNICAL FIELD

The present application relates to the field of radio communication technology, for example, a quality of service flow transmission method and apparatus, a base station, a terminal, and a storage medium.


BACKGROUND

In a new radio (NR) communication network, a quality of service (QOS) parameter of traffic is configured to a base station through a control plane signaling, and the QoS parameter is configured based on a protocol data unit (PDU) session and a QoS flow level. One user equipment (UE) may establish up to 256 PDU sessions. One PDU session may contain up to 64 QoS flows. A QoS parameter is configured for a QoS flow. For downlink traffic, each PDU of the user plane is transmitted on a corresponding PDU tunnel, and the extension header of a PDU carries a QoS flow identifier (QFI) indication. In this manner, the association between a PDU and a QoS parameter is implemented, and the QoS parameter configuration of a QoS level is implemented. For uplink traffic, a base station may map different QoS flows to different data radio bearers (DRBs). Different DRBs correspond to different logical channel groups (LCGs). A UE carries an LCG identity (ID) in a buffer status report (BSR) request. The base station allocates an uplink scheduling resource based on BSR information. In this manner, different QoS parameters correspond to different resource allocation priorities. However, in the QoS strategy, multiple PDUs may not be corresponded to a respective application message, and information such as the category and the source of an application message cannot be identified. As a result, the availability and reliability of the application message are reduced. An application layer QOS directly determines the user experience. For example, an application message is not completely sent to a receiver, and even if the receiver receives a part of the application message, the receiver still considers that the message is not successfully received. As a result, the integrity of the application message is seriously affected, and the user experience is greatly decreased.


SUMMARY

The present application provides a quality of service flow transmission method and apparatus, a base station, a terminal, and a storage medium to determine the category corresponding to a quality of service flow, enhance the accuracy of quality of service flow transmission, reduce the problem of an information transmission error caused because the category of an application message cannot be identified, enhance the integrity of the application message, and improve a user experience.


An embodiment of the present application provides a quality of service flow transmission method. The method includes the following:


At least one PDU session sent by a core network is acquired. The information frame format of the PDU session carries indication information. The category to which the at least one PDU session belongs is determined according to the indication information.


An embodiment of the present application provides another quality of service flow transmission method. The method includes the following:


At least one issued packet data convergence protocol (PDCP) data PDU is received. The PDCP data PDU carries indication information. Message receiving feedback is sent according to the indication information.


An embodiment of the present application provides a quality of service flow transmission apparatus. The apparatus includes a session acquisition module and an application layer home module.


The session acquisition module is configured to acquire at least one PDU session sent by the core network. The information frame format of the PDU session carries the indication information. The application layer belonging module is configured to determine the category to which each PDU session belongs according to the indication information.


An embodiment of the present application provides another quality of service flow transmission apparatus. The apparatus includes a data unit receiving module and a message receiving feedback module.


The data unit receiving module is configured to receive at least one issued PDCP data PDU. The PDCP data PDU carries indication information. The message receiving feedback module is configured to send message receiving feedback according to the indication information.


An embodiment of the present application provides a base station. The base station includes one or more processors and a memory configured to store one or more programs. When executing the one or more programs, the one or more processors are caused to perform the quality of service flow transmission method according to any one of embodiments of the present application.


An embodiment of the present application provides a terminal. The terminal includes one or more processors and a memory configured to store one or more programs. When executing the one or more programs, the one or more processors are caused to perform the quality of service flow transmission method according to any one of the embodiments of the present application.


In the embodiments of the present application, at least one PDU session sent by the core network is acquired. The information frame format of the PDU session carries the indication information. The indication information is used for determining the categories corresponding to different PDU sessions. The category corresponding to each PDU session is determined through application message indication information. In this manner, the accuracy of quality of service flow transmission can be enhanced, the problem of an information transmission error caused because the category of the PDU session cannot be identified can be solved, the integrity of message transmission can be enhanced, and the user experience can be improved.





BRIEF DESCRIPTION OF DRAWINGS


FIG. 1 is a diagram illustrating the structure of an information frame format of a protocol data unit session in the related art.



FIG. 2 is a flowchart of a quality of service flow transmission method according to an embodiment of the present application.



FIG. 3 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application.



FIG. 4 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application.



FIG. 5 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application.



FIG. 6 is a diagram illustrating the information frame format of a PDU session according to an embodiment of the present application.



FIG. 7 is a diagram illustrating the information frame format of another PDU session according to an embodiment of the present application.



FIG. 8 is a diagram illustrating the information frame format of another PDU session according to an embodiment of the present application.



FIG. 9 is a diagram illustrating transmission of a PDU session according to an embodiment of the present application.



FIG. 10 is a diagram illustrating transmission of another PDU session according to an embodiment of the present application.



FIG. 11 is a diagram illustrating the information frame format of another PDU session according to an embodiment of the present application.



FIG. 12 is a flowchart of a quality of service flow transmission method according to an embodiment of the present application.



FIG. 13 is a diagram illustrating a buffer status report according to an embodiment of the present application.



FIG. 14 is a diagram illustrating another buffer status report according to an embodiment of the present application.



FIG. 15 is a diagram illustrating another buffer status report according to an embodiment of the present application.



FIG. 16 is a diagram illustrating another buffer status report according to an embodiment of the present application.



FIG. 17 is a diagram illustrating another buffer status report according to an embodiment of the present application.



FIG. 18 is a diagram illustrating another buffer status report according to an embodiment of the present application.



FIG. 19 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application.



FIG. 20 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application.



FIG. 21 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application.



FIG. 22 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application.



FIG. 23 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application.



FIG. 24 is a diagram illustrating the structure of a PDCP data PDU according to an embodiment of the present application.



FIG. 25 is a diagram illustrating the structure of another PDCP data PDU according to an embodiment of the present application.



FIG. 26 is a diagram illustrating the structure of another PDCP data PDU according to an embodiment of the present application.



FIG. 27 is a diagram illustrating the structure of another PDCP data PDU according to an embodiment of the present application.



FIG. 28 is a diagram illustrating the structure of a quality of service flow transmission apparatus according to an embodiment of the present application.



FIG. 29 is a diagram illustrating the structure of another quality of service flow transmission apparatus according to an embodiment of the present application.



FIG. 30 is a diagram illustrating the structure of a base station according to an embodiment of the present application.



FIG. 31 is a diagram illustrating the structure of a terminal according to an embodiment of the present application.





DETAILED DESCRIPTION

Sufixes such as “module”, “part”, or “unit” used for indicating elements in the subsequent description merely facilitate the description of the present application, and have no particular meaning in themselves. Therefore, “module”, “part”, or “unit” may be used in a mixed manner.



FIG. 1 is a diagram illustrating the structure of the information frame format of a protocol data unit session in the related art. Referring to FIG. 1, the information frame format of a protocol data unit (PDU) session is an extension header carried in a general packet radio service (GPRS) tunnel protocol (GTP)—user message protocol data unit, such as an NR RAN container or a PDU session container. It can be seen from this information frame format of the PDU session that a base station cannot determine which PDUs correspond to one application message from the information frame format. In industrial Internet of things (IIoT) traffic, an application message is considered to be successfully transmitted only if the application message is successfully transmitted in survival time. The information frame format of the PDU session is not conducive to the successful transmission of the application message.


An embodiment of the present application provides a quality of service flow transmission method. This embodiment of the present application may be applied to the case where the category of a protocol data unit session is determined. The method may be executed by a quality of service flow transmission apparatus according to this embodiment of the present application. The apparatus may be performed by software and/or hardware and may be generally integrated in a base station. The method according to this embodiment of the present application includes the following:


In S1, at least one PDU session sent by the core network is acquired. The information frame format of the PDU session carries indication information.


In this embodiment of the present application, the base station may receive one or more protocol data unit sessions sent by the core network. Each protocol data unit session may carry indication information. The indication information may be information on a field in the information frame format of the PDU session.


In S2, the category to which each PDU session belongs is determined according to the indication information.


The category may be information reflecting the attribute of the PDU session. The category may include a traffic type, a quality of service flow type, a transmission method, or the like.


The category to which each PDU session belongs may be determined according to different values of the indication information in the information frame format of each PDU session, and different values of the indication information represent that the corresponding PDU sessions belong to different categories.


Based on the preceding embodiment of the present application, the indication information includes a PDU session category index. Accordingly, the operation in which the category to which each PDU session belongs is determined according to the indication information includes the following:


At least one of the traffic type, the QoS type, a QoS flow group, or the transmission method corresponding to each PDU session is determined according to the PDU session category index.


In this embodiment of the present application, the PDU session category index is determined according to the indication information. A PDU session category index corresponds to an application message index. Alternatively, a PDU session category index corresponds to a traffic type. Alternatively, a PDU session category index corresponds to a QoS type. Alternatively, a PDU session category index corresponds to a QoS flow group. Alternatively, a PDU session category index corresponds to a transmission method. The type of the application message, the type of application traffic, or a QoS requirement may be determined according to the index, so that radio resource scheduling strategies such as an adopted radio bearer type and the scheduling priority of a radio resource are determined.


Based on the preceding embodiment of the present application, the indication information includes application message indication information. Accordingly, the operation in which the category to which each PDU session belongs is determined according to the indication information includes the following: The application message to which each PDU session belongs is determined according to the application message indication information; it is determined that each PDU session belongs to the same application message according to the application message indication information in the information frame format of the PDU session; and/or it is determined that transmission of the application message corresponding to each PDU session ends according to the application message indication information in the information frame format of each PDU session.



FIG. 2 is a flowchart of a quality of service flow transmission method according to an embodiment of the present application. This embodiment of the present application may be applied to the case where the application message to which a protocol data unit session belongs is determined. Referring to FIG. 2, the method may be executed by a quality of service flow transmission apparatus according to this embodiment of the present application. The apparatus may be implemented by software and/or hardware and may be generally integrated in a base station. Referring to FIG. 2, the method according to this embodiment of the present application includes the following:


In 110, at least one PDU session sent by the core network is acquired. The information frame format of the PDU session carries application message indication information.


The core network may be a component of a communication network and be responsible for associating data and enabling data routing exchange. The protocol data unit session may be a data unit session transmitted between peer levels. At different levels of the communication network, the protocol data unit session may be different. For example, the PDU session at a data link layer is a data frame session, the PDU session at a network layer is a data packet session, and the PDU session at a transmission layer is a data segment session. The application message indication information may be information for indicating the application message to which the PDU session belongs, and the application message may be indicated implicitly or explicitly.


In this embodiment of the present application, the core network may send multiple PDU sessions to the base station. The information frame format of each PDU session carries the application message indication information.


In 120, the application message to which each PDU session belongs is determined according to the application message indication information.


A respective application message corresponding to each PDU may be determined according to the application message indication information in the PDU session. Different application message indication information may correspond to different application messages.


In this embodiment of the present application, the PDU session carrying application message indication information which is in multiple information frame formats and sent by the core network is acquired. The corresponding application message is determined for each PDU session according to the respective application message indication information. The application message corresponding to each PDU session is determined through the application message indication information. In this manner, the accuracy of quality of service flow transmission can be enhanced, the problem of an information transmission error caused because the category and source of an application message cannot be identified can be reduced, the integrity of an application message can be enhanced, and the user experience can be improved.


Based on the preceding embodiments of the present application, the application message indication information includes at least one of an application message sequence number, an application message end mark, or an application message segment number indication.


In this embodiment of the present application, the information frame format of the PDU session may include at least one of an application message sequence number, an application message end mark, or an application message segment number indication. Different values may be used in the information frame format to identify different application message sequence numbers, application message end marks, or application message segment number indications.


The application message segment number indicates the number of application message segments or identifies which segment is the current PDU session in the corresponding application message or how many remaining segments are not transmitted.



FIG. 3 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application. This embodiment of the present application is described on the basis of the preceding embodiments of the present application. Referring to FIG. 3, the method according to this embodiment of the present application includes the following:


In 210, at least one PDU session sent by the core network is acquired. The information frame format of the at least one PDU session carries application message indication information.


In 220, it is determined that the at least one PDU session belongs to the same application message according to the application message sequence number in the information frame format of each PDU session.


In this embodiment of the present application, the application message sequence number in the information frame format of each PDU session may be extracted, and the application message to which each PDU session belongs is determined according to the value of the application message sequence number. PDU sessions having the same application message sequence number may belong to the same application message.


In 230, it is determined that transmission of an application message corresponding to each PDU session ends according to the application message end mark in the information frame format of each PDU session.


It may be determined whether there is an application message end mark in the information frame format of each PDU session. If the application message end mark exists, this PDU session is identified as the end of the application message, and when the PDU session is received, it may represent that the transmission of the application message ends. The next PDU session may belong to a new application message.


Based on the preceding embodiments of the present application, the application message indication information includes at least one of an application message sequence number or application message segment number.


In this embodiment of the present application, the information frame format of the PDU session may include at least one of an application message sequence number or an application message segment number. Different values may be used in the information frame format to identify different application message sequence numbers and application message segment numbers.



FIG. 4 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application. This embodiment of the present application is described on the basis of the preceding embodiments of the present application. Referring to FIG. 4, the method according to this embodiment of the present application includes the following:


In 310, at least one PDU session sent by the core network is acquired. The information frame format of the at least one PDU session carries application message indication information.


In 320, it is determined that the at least one PDU session belongs to the same application message according to the application message sequence number in the information frame format of each PDU session.


In 330, it is determined that an application message corresponding to each PDU session is completely received according to the application message segment number in the information frame format of each PDU session.


The application message segment number may represent the number of PDU sessions that an application message is divided into.


In this embodiment of the present application, the application segment number may be extracted from the information frame format of each PDU session, and it is determined whether the number of received PDU sessions satisfies the application segment number. If the number of received PDU sessions satisfies the application segment number, an application message is completely received. Otherwise, the reception of PDU sessions is continued.


Based on the preceding embodiments of the present application, the application message indication information includes at least one of an application message start mark or an application message end mark.



FIG. 5 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application. This embodiment of the present application is described on the basis of the preceding embodiments of the present application. Referring to FIG. 5, the method according to this embodiment of the present application includes the following:


In 410, at least one PDU session sent by the core network is acquired. The information frame format of the at least one PDU session carries application message indication information.


In 420, the start position of the application message corresponding to each PDU session is determined according to the application message start mark in the information frame format of each PDU session.


In this embodiment of the present application, information may be extracted at the position of the application message start mark in the information frame format of the PDU session, and whether a PDU session is at the start position of the application message is determined according to the extracted information. For example, when the application start mark in the information frame format of a PDU session is 1, the PDU session is at the start position of the application message. If the application start mark is 0, the PDU session is not at the start position of the application message.


In 430, the end position of the application message corresponding to each PDU session is determined according to the application message end mark in the information frame format of each PDU session.


In this embodiment of the present application, information may be extracted at the position of the application message end mark in the information frame format of the PDU session, and whether a PDU session is at the end position of the application message is determined according to the extracted information. For example, when the application end mark in the information frame format of a PDU session is 1, the PDU session is at the end position of the application message. If the application start mark is 0, the PDU session is not at the end position of the application message. PDU sessions belonging to the same application message may be determined through the start position and the end position of the application message. For example, all PDU sessions between the start position and the end position, including the PDU session at the start position and the PDU session at the end position, belong to the same application message.


In an exemplary embodiment, referring to FIG. 6, the information frame format of the PDU session carries at least one of an application message sequence number or an application message end mark. The application message sequence number is used by the base station for identifying whether PDUs correspond to the same application message. Under the same QoS flow, PDUs of the same sequence number correspond to the same application message, and PDUs of different sequence numbers correspond to different application messages. The application message end mark is used for indicating the last one of PDUs corresponding to the same application message.


The base station may determine whether PDUs of a new application message start and whether different PDUs correspond to the same application message based on the application message sequence number. The base station may determine whether the transmission of PDUs of an application message ends based on the application message end mark. The end mark having the value of 1 indicates that the transmission ends.


From the start of the PDUs of a new application message to the end of the transmission of PDUs of the application message, PDUs of the same application message sequence number under the same QoS flow correspond to a complete application message.


Alternatively, whether the application message sequence number of the current PDU is the same as the application message sequence number of the next PDU may also be used for identifying whether the application message corresponding to the current PDU ends. If the transmission of a new application message starts, it implicitly represents that the transmission of the previous application message ends. At this time, the application message end mark is not required.


In another exemplary embodiment, referring to FIG. 7, the information frame format of the PDU session carries at least one of an application message sequence number or an application message segment number. In the information frame format, when the application message segment number exists, the number of octets for padding is 0 to 2. It should be noted that when the application message segment number does not exist, the number of octets for padding is 0 to 3.


The application message sequence number is used by the base station for identifying whether PDUs correspond to the same application message. Under the same QoS flow, PDUs of the same sequence number correspond to the same application message, and PDUs having different sequence numbers correspond to different application messages. The application message segment number is used for indicating how many PDUs is the application message divided into for transmission.


The base station may determine whether PDUs of a new application message starts and whether different PDUs correspond to the same application message based on the application message sequence number. The base station may determine whether PDUs of an application message are completely received based on the application message segment number.


Starting from the PDUs of a new application message, if the number of PDUs which have the same application message sequence number and are received by the base station under the same QoS flow reaches the application message segment number, it is considered that the application message is received completely. PDUs of the same application message sequence number correspond to a complete application message.


In another exemplary embodiment, referring to FIG. 8, the information frame format of the PDU session carries at least one of an application message start mark or an application message end mark. The mark bit may occupy 2 bits. Four values respectively represent at least one of the following: The mark bit does not exist, the transmission of an application message starts, the transmission of an application message ends, or an application message has only one PDU. For example, when the 2 bits are ‘00’, it represents that the mark bit does not exist (does not indicate the start and end of the application message). The start and end of the application message cannot be determined. Alternatively, an application message corresponds to a PDU by default.


When the 2 bits are ‘01’, it represents that transmission of an application message starts. When the 2 bits are ‘10’, it represents that transmission of an application message ends. When the 2 bits are ‘11’, it represents that an application message has only one PDU. In this manner, from the start of transmission of an application message to the end of the transmission of the application message, all PDUs under the same QoS flow correspond to the same application message.


The mark bit may occupy 1 bit. When this 1 bit is 1, it represents that transmission of the application message under the same QoS flow starts (start mark) or ends (end mark) (a new start is the old end).


For example, the value of the 1 bit is 1, which represents the start of transmission of an application message (start mark). All PDUs under the same QoS flow correspond to one application message until 1 bit is 1. FIG. 9 is a diagram illustrating transmission of a PDU session according to an embodiment of the present application. As shown in FIG. 9, StartMark=1 occurs once in PDU1, and the last occurrence of StartMark=1 is PDU m+1. Then, PDU1, PDU2 . . . and PDU m correspond to the same application message.


Alternatively, the value of the 1 bit is 1, which represents the end of transmission of an application message (end mark). This PDU and the previous contiguous PDUs with End mark=0 under the same QoS flow correspond to an application message. FIG. 10 is a diagram illustrating transmission of another PDU session according to an embodiment of the present application. As shown in FIG. 10, StartMark=1 occurs once in PDU m+1. The PDU m+1 and previous contiguous PDUs (PDU2 . . . and PDU m) with End mark=0 correspond to an application message.


Referring to FIG. 11, the method described above is also applicable to the application message determination inside a radio access network (RAN) (X2-U, Xn-U, and F1-U user plane interfaces). The frame format of the PDU session inside the RAN (X2-U, Xn-U, and F1-U user plane interfaces) is as follows: A spare bit in the frame format may be extended to one of the preceding meanings to represent which PDUs belong to the same application message.



FIG. 12 is a flowchart of a quality of service flow transmission method according to an embodiment of the present application. This embodiment of the present application is described on the basis of the preceding embodiments of the present application. Referring to FIG. 12, the method according to this embodiment of the present application includes the following:


In 510, at least one PDU session sent by the core network is acquired. The information frame format of the PDU session carries application message indication information.


In 520, the application message to which each PDU session belongs is determined according to the application message indication information.


In 530, the size of the buffer data volume corresponding to the application message sent by a UE through a buffer status report (BSR) is acquired.


In this embodiment of the present application, due to the limitation of radio resources and UE capabilities, an uplink application message may be segmented at Uu interface. The base station maps the QoS flow to a data radio bearer (DRB) and a logical channel group (LCG) through radio bearer configuration. The UE requests a radio resource (buffer status report (BSR)) based on the LCG. The base station performs uplink resource scheduling based on the BSR. When the UE requests the radio resource (BSR) based on the LCG, the sum of the buffer size corresponding to the LCG is requested, and the number of application messages included in the buffer size is not distinguished.


The base station may receive the size of the buffer data volume corresponding to the application message sent by the UE through the BSR and may determine the number of feedback application messages through the size of the buffer data volume. The number of BSRs reported by the UE may be one or more.


Based on the preceding embodiments of the present application, the size of the buffer data volume corresponding to the application message includes the size of the application message reported according to a logical channel group.


In this embodiment of the present application, the size of the buffer data volume of the application message sent by the UE may be the size of the application message reported according to the logical channel group.


Based on the preceding embodiments of the present application, the size of the buffer data volume corresponding to the application message includes the size of the application message reported according to a logical channel.


In this embodiment of the present application, the size of the buffer data volume of the application message sent by the UE may be the size of the application message reported according to the logical channel.


In an exemplary embodiment, an application message may correspond to the size of a buffer data volume. Referring to FIGS. 13 and 14, the base station may request a BSR according to the application message. An application message corresponds to a buffer size (message size). If the buffer corresponding to the same LCG includes multiple application messages, the correspondence between LCGs and buffer sizes is reported. The base station schedules an uplink radio resource based on the buffer size. The UE transmits uplink data on the corresponding radio resource. In this manner, the base station may determine whether an application message is completely received.


In an exemplary embodiment, referring to FIG. 15, the base station requests a BSR according to the application message. An application message corresponds to a buffer size (message size). A BSR includes an LCG ID, an MsgNum field, and an MsgNum of buffer size fields.


In an exemplary embodiment, referring to FIGS. 16, 17, and 18, an application message corresponds to a QoS flow. A QoS flow corresponds to a logical channel. The UE may request a BSR according to an LC identifier (ID), so that an LC-level BSR request may be implemented. In addition, the BSR carries the application message sequence number, and the application message sequence number may be used by the base station for identifying which PDUs correspond to the same application message; the BSR carries time stamp information of the application message reaching a UE buffer, and the time stamp information may be used by the base station for determining a resource allocation priority when resources are congested. In FIG. 16, the base station reports the buffer size and application message sequence number corresponding to each application message according to the LC ID. In FIG. 17, the base station reports the message quantity and message size corresponding to one LC ID. The message size may be the total size of multiple messages. In FIG. 18, the base station requests a BSR according to the application message. An application message corresponds to a buffer size (message size). A BSR includes an LC ID, an MsgNum field, and an MsgNum of buffer size fields.



FIG. 19 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application. This embodiment of the present application is described on the basis of the preceding embodiments of the present application. Referring to FIG. 19, the method according to this embodiment of the present application includes the following:


In 610, at least one PDU session sent by the core network is acquired. The information frame format of the PDU session carries application message indication information.


In 620, the application message to which each PDU session belongs is determined according to the application message indication information.


In 630, a characteristic parameter of the application message is determined according to an information element of a Qos flow in the PDU session. The characteristic parameter of the corresponding application message may be determined through the information element of the Qos flow included in the PDU session.


Based on the preceding embodiment of the present application, the characteristic parameter includes at least one of the following: an application availability target, an application reliability target, a video traffic coding rate, video traffic transmission duration, or a transmission video scale.


In an exemplary embodiment, the base station may identify the availability target and the reliability target in the application message. The core network provides the base station with the characteristic parameter of the application message through the information element in the QoS flow. The characteristic parameter of the application message includes at least one of the following: the application message availability target, the application message reliability target, the video traffic coding rate, the video traffic transmission duration, or the total size of a video.



FIG. 20 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application. This embodiment of the present application is described on the basis of the preceding embodiments of the present application. Referring to FIG. 20, the method according to this embodiment of the present application includes the following:


In 710, at least one PDU session sent by the core network is acquired. The information frame format of the PDU session carries application message indication information.


In 720, an application message to which each PDU session belongs is determined according to the application message indication information.


In 730, when at least one of the following operations is performed, configuration information provided by the core network through dedicated signaling is received, and the operations include establishing/modifying a dedicated connection with a UE of the core network, establishing/modifying a PDU session with a UE of the core network, and establishing/modifying an evolved radio access bearer (E-RAB) with a UE of the core network.


In this embodiment of the present application, the core network may provide the configuration information operated in the base station through the dedicated information. The operations performed by the base station may include one or more of establishment/modification of the dedicated connection with the UE of the core network, establishment/modification of the PDU session with the UE of the core network, and establishment/modification of the E-RAB with the UE of the core network.


Based on the preceding embodiments of the present application, the configuration information includes at least one of the following: a UE traffic bearer maximum rate requirement, a UE traffic bearer delay requirement, a UE traffic bearer transmission frequency, a UE bearer traffic data volume, UE power consumption information, UE battery charge information, or UE mobility prediction information.


Based on the preceding embodiments of the present application, the UE mobility prediction information includes at least one of the following: historical cell information, historical cell camping duration, camping duration of the current cell, a camping start time point of the current cell, a radio resource control (RRC) connection release interval, an RRC connection suspension interval, a traffic interval, or a traffic frequency.


In an exemplary embodiment, the base station may identify the characteristic information of a UE. During the establishment/modification (initial context setup request, UE context modification request, handover request, and path switch request acknowledge) of the dedicated connection (NG interface application protocol (NGAP)/S1 interface application protocol (S1AP)) with the UE of the core network, or the establishment/modification of the PDU session (PDU session resource setup request and PDU session resource modify request) with the UE of the core network, or the establishment/modification of the E-RAB with the UE of the core network, the core network provides the base station with at least one of the following through the dedicated signaling: the maximum rate requirement of traffic bore by the UE, a delay requirement of traffic bore by the UE, a transmission frequency of traffic bore by the UE, the data volume size of traffic bore by the UE, UE power consumption information, UE battery charge information (whether a power supply is connected, whether a power supply is passive, or whether there is an energy saving requirement), or UE mobility prediction related information.


The UE mobility prediction related information includes at least one of the following: historical cell information, historical cell camping duration, camping duration or a camping start point of the current cell before the traffic is initiated, an RRC connection release/suspension interval, the traffic interval, or the traffic frequency.


An embodiment of the present application provides a quality of service flow transmission method. This embodiment of the present application may be applied to the case where the category of a protocol data unit session is determined. The method may be executed by a quality of service flow transmission apparatus according to this embodiment of the present application. The apparatus may be performed by software and/or hardware. The method according to this embodiment of the present application includes the following:


In S11, at least one issued PDCP data PDU is received. The PDCP data PDU carries indication information.


In this embodiment of the present application, one or more PDCP data PDUs issued may be received. Each PDCP data PDU may carry indication information. The indication information may be information on a field in an information frame format of a PDU session.


In S12, message receiving feedback is sent according to the indication information.


The manner in which each PDU session sends the message receiving feedback may be determined according to different values of the indication information in the information frame format of each PDCP data PDU. For example, PDCP data PDUs may be divided into different categories according to the indication information in the information frame format of each PDCP data PDU, and the message receiving feedback may be sent for a category of PDCP data PDUs.


Based on the preceding embodiments of the present application, the indication information includes a PDU session category index. Accordingly, the operation in which the message receiving feedback is sent according to the indication information includes the following:


At least one of a traffic type, a QoS type, a QoS flow group, or a transmission method corresponding to each PDCP data PDU is determined according to the PDU session category index. The message receiving feedback is sent according to the at least one of the traffic type, the QoS type, the QoS flow group, or the transmission method.


In this embodiment of the present application, the PDU session category index is determined according to the indication information. A PDU session category index corresponds to an application message index. Alternatively, a PDU session category index corresponds to a traffic type. Alternatively, a PDU session category index corresponds to a QoS type. Alternatively, a PDU session category index corresponds to a QoS flow group. Alternatively, a PDU session category index corresponds to a transmission method. The type of the application message, the type of application traffic, or a QoS requirement may be determined according to the index, so that radio resource scheduling strategies such as an adopted radio bearer type and the scheduling priority of a radio resource are determined.


When the message receiving feedback is sent, the message receiving feedback is sent for different traffic types, QoS types, QoS flow groups, and transmission methods.


Based on the preceding embodiments of the present application, the indication information includes application message indication information. Accordingly, the operation in which the message receiving feedback is sent according to the indication information includes the following: An application message to which each PDCP data PDU belongs is determined according to the application message indication information, and it is determined whether each PDU session belongs to the same application message according to the application message indication information in the information frame format of each PDU session; and/or it is determined that transmission of the application message corresponding to each PDU session ends according to the application message indication information in the information frame format of each PDU session. Moreover, the message receiving feedback is sent according to the application message to which the PDCP data PDU belongs.



FIG. 21 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application. This embodiment of the present application may be applied to the case where the application message to which a protocol data unit session belongs is determined. The method may be executed by a quality of service flow transmission apparatus according to this embodiment of the present application. The apparatus may be implemented by software and/or hardware and may be generally integrated in a terminal or base station. Referring to FIG. 21, the method according to this embodiment of the present application includes the following:


In 810, at least one issued PDCP data PDU is received. The PDCP data PDU carries application message indication information.


The packet data convergence protocol data protocol data unit may be a data unit sent by the base station in a downlink sending process, and the data unit is received by the terminal. Alternatively, the packet data convergence protocol data protocol data unit may be a data unit sent by the terminal in an uplink sending process, and the data unit is received by the base station.


In this embodiment of the present application, the PDCP data PDU carrying the application message indication information may be received. The number of PDCP data PDUs may be one or more.


In 820, message receiving feedback is sent according to the application message indication information.


The application message corresponding to each PDCP data PDU is determined according to the application message indication information, and the message receiving feedback may be generated and sent according to different application messages.


In this embodiment of the present application, at least one issued PDCP Data PDU is received. The PDCP data PDU carries an application indication message. The message receiving feedback is sent according to the application indication message. In this manner, the integrity of the application message receiving is improved, and the communication quality can be enhanced.


Based on the preceding embodiments of the present application, the method also includes sending at least one PDCP data PDU. The PDCP data PDU carries the application message indication information.



FIG. 22 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application. This embodiment of the present application is described on the basis of the preceding embodiments of the present application. Referring to FIG. 22, the method according to this embodiment of the present application includes the following:


In 910, at least one PDCP data PDU issued is received. The PDCP data PDU carries application message indication information.


In 920, a PDCP status packet or a radio link control protocol (RLC) status packet is fed back for each PDCP data PDU.


In this embodiment of the present application, a PDCP status packet or an RLC status packet may be fed back every time a PDCP data PDU is received.



FIG. 23 is a flowchart of another quality of service flow transmission method according to an embodiment of the present application. This embodiment of the present application is described on the basis of the preceding embodiments of the present application. Referring to FIG. 23, the method according to this embodiment of the present application includes the following:


In 911, at least one PDCP data PDU issued is received. The PDCP data PDU carries application message indication information.


In 912, the application message to which each PDCP data PDU belongs is determined, and a PDCP status packet or an RLC status packet is fed back for the application message to which each PDCP data PDU belongs.


The application message indication information in each PDCP data PDU may be determined to determine the corresponding application message. A PDCP status packet or an RLC status packet is fed back for each application message.


Based on the preceding embodiments of the present application, the application message to which each PDCP data PDU belongs is determined in the following manner: The application message to which each PDCP data PDU belongs is determined according to the application message indication information carried in the PDCP data PDU.


In this embodiment of the present application, the corresponding application message may be determined through the application message indication carried in the information frame format of the PDCP data PDU.


Based on the preceding embodiments of the present application, the application message indication information includes at least one of an application message sequence number, an application message start mark, an application message end mark, or an application message segment number indication.


Based on the preceding embodiments of the present application, the operation in which the application message to which each PDCP data PDU belongs is determined according to the application message indication information carried in the PDCP data PDU includes at least one the following manners:


It is determined whether each PDCP data PDU belongs to the same application message according to the application message sequence number in the information frame format of each PDCP data PDU; it is determined that transmission of the application message corresponding to each PDCP data PDU starts according to the application message start mark in the information frame format of each PDCP data PDU; or it is determined that transmission of the application message corresponding to each PDCP data PDU ends according to the application message end mark in the information frame format of each PDCP data PDU.


Based on the preceding embodiments of the present application, the method also includes carrying the application message indication information through a medium access control (MAC) header, an RLC header, and a media access control control element (MAC CE).


Based on the preceding embodiments of the present application, the method also includes receiving the number of PDUs corresponding to the application message and configured by the base station and determining the application message to which each PDCP data PDU belongs according to the number of PDUs.


Based on the preceding embodiments of the present application, the number of PDUs corresponding to the application message is carried by at least one of an RRC message, a PDCP header, MAC, an RLC header, or an MAC CE.


In an exemplary embodiment, due to the factors such as the limitation of radio resources and the limitation of UE capabilities, after the base station receives downlink PDUs of the same application message, the base station may perform segment transmission at Uu interface. Only if all Uu interface segments of the same application message are successfully transmitted, the application message is considered to be successfully transmitted. Scheduling of the base station needs to ensure that the same application message is successfully transmitted with the survival time. Whether a downlink message is successfully transmitted requires feedback from the UE. In the determination of whether the downlink survival time is satisfied, there are the following methods: a determination mechanism based on PDCP status packet feedback (sequence number (SN)), a determination mechanism based on a hybrid automatic repeat request (hybrid automatic repeat request acknowledgement/non-acknowledgement (HARQ ACK/NACK)) feedback, and a determination mechanism based on automatic repeat request acknowledgement/non-acknowledgement (ARQ ACK/NACK) feedback.


If the determination mechanism is based on the ARQ ACK/NACK feedback, since the ARQ ACK/NACK feedback is relatively timely, there will be feedback as long as a data packet error occurs. A sender may determine in real time whether PDUs corresponding to the same application message are successfully transmitted.


If the determination mechanism is based on the PDCP status packet feedback (SN) or based on the HARQ ACK/NACK feedback, the UE does not feed back a status packet for each PDU. As a result, the sender cannot determine timely whether PDUs corresponding to the same application message are successfully transmitted, thereby affecting the determination of whether the survival time is satisfied.


The solutions are below.


Method one: Each time a PDU is received, the UE feeds back a PDCP status packet or an RLC status packet.


Method two: The UE perceives which PDUs correspond to an application message and feeds back a PDCP status packet or an RLC status packet after the same application message is successfully received.


Method one may occupy more radio resources due to frequent feedback of status packet information. Thus, the present method mainly focuses on how the UE perceives which PDUs correspond to an application message.


In an exemplary embodiment, a PDCP data PDU format having a 12-bit PDCP SN and an application message sequence number may be shown in FIG. 24. A PDCP data PDU format of a DRB has an 18-bit PDCP SN and an application message sequence number and may be shown in FIG. 25. Referring to FIGS. 24 and 25, the application message sequence number is used by the base station for identifying whether PDUs correspond to the same application message. PDUs of the same sequence number under the same QoS flow correspond to the same application message. PDUs having different sequence numbers correspond to different application messages. The application message end mark is used for indicating the last one of PDUs corresponding to the same application message.


The base station may determine whether PDUs of a new application message start and whether different PDUs correspond to the same application message based on the application message sequence number. From the start of the PDUs of a new application message to the end of the transmission of the PDUs of an application message, the PDUs of the same application message sequence number under the same QoS flow correspond to a complete application message.


In another exemplary embodiment, the PDCP data PDU format having a 12-bit PDCP SN and an application message start/end mark may be shown in FIG. 26. The PDCP data PDU format of a DRB has an 18-bit PDCP SN and an application message start/end mark and may be shown in FIG. 27. In FIGS. 26 and 27, the application message start and end marks indicate the start or end of the application message, respectively. The mark bit may occupy 2 bits. Four values respectively represent at least one of the following: The mark bit does not exist, transmission of an application message starts, transmission of an application message ends, or an application message has only one PDU.


For example, when the 2 bits are ‘00’, it represents that the mark bit does not exist (does not indicate the start and end of the application message). The start and end of the application message cannot be determined. Alternatively, an application message corresponds to a PDU by default.


When the 2 bits are ‘01’, it represents that transmission of an application message starts. When the 2 bits are ‘10’, it represents that transmission of an application message ends. When the 2 bits are ‘11’, it represents that an application message has only one PDU. In this manner, from the start of the transmission of the application message to the end of the transmission of the application message, all PDUs correspond to the same application message.


The mark bit may also occupy 1 bit. When the value of this bit is 1, it represents that the transmission of the application message starts (start mark) or ends (end mark) (the new start is the old end).


For example, the value of the 1 bit is 1, which represents the start of transmission of an application message (start mark). All PDUs correspond to one application message until the 1 bit is 1. Referring to FIG. 9, StartMark=1 occurs once in PDU1, and the last occurrence of StartMark=1 is in PDU m+1. Then, PDU1, PDU2 . . . and PDU m correspond to the same application message.


Alternatively, the value of the 1 bit is 1, which represents the end (end mark) of transmission of an application message. This PDU and previous contiguous PDUs of End mark=0 correspond to an application message. Referring to FIG. 10, StartMark=1 occurs once in PDU m+1. The PDU m+1 and the previous contiguous PDUs (PDU2 . . . and PDU m) with End mark=0 correspond to an application message.


The preceding information may also be carried by an MAC header, an RLC header, and an MAC CE. In addition, the base station may configure the UE with the number of PDUs corresponding to an application message. The UE determines whether the application message is successfully received based on the number of PDUs corresponding to the application message and whether the number of received PDUs of the application message reaches the number. The number of PDUs corresponding to an application message may be carried by an RRC message, a PDCP header, an MAC header, an RLC header, and an MAC CE.


When the preceding method is used, the UE requires to report the capability of application message identification, and the base station configures a status report reporting indication based on the application message for the UE.


Only when the UE supports the capability of application message identification, the base station can configure the status report reporting indication based on the application message for the UE.


When the UE receives the status report reporting indication based on the application message, and the UE successfully receives all PDUs corresponding to an application message, the UE triggers a PDCP status packet or an RLC status packet once.


In an exemplary embodiment, a quality of service flow transmission apparatus may execute the quality of service flow transmission method provided by any embodiment of the present application and has functional modules and beneficial effects corresponding to the method executed. The apparatus may be performed by software and/or hardware. The apparatus includes a session transmission module and a category determination module.


The session transmission module is configured to acquire at least one protocol data unit (PDU) session sent by the core network. The information frame format of the PDU session carries indication information.


The category determination module is configured to determine the category to which each PDU session belongs according to the indication information.


In an exemplary embodiment, a quality of service flow transmission apparatus may execute the quality of service flow transmission method provided by any embodiment of the present application and has functional modules and effects corresponding to the method executed. The apparatus may be performed by software and/or hardware. The apparatus includes an index acquisition module and a type identification module.


The index acquisition module is configured to acquire at least one protocol data unit (PDU) session sent by the core network. The information frame format of the PDU session carries a PDU session category index.


The type identification module is configured to determine at least one of a traffic type, the QoS type, the QoS flow group, or the transmission method corresponding to each PDU session according to the PDU session category index.



FIG. 28 is a diagram illustrating the structure of a quality of service flow transmission apparatus according to an embodiment of the present application. The apparatus may execute the quality of service flow transmission method provided by any embodiment of the present application and has functional modules and effects corresponding to the method executed. The apparatus may be performed by software and/or hardware. The apparatus includes a session acquisition module 10 and an application layer belonging module 11.


The session acquisition module 10 is configured to acquire at least one protocol data unit (PDU) session sent by a core network. An information frame format of the PDU session carries application message indication information. The application layer belonging module 11 is configured to determine an application message to which each PDU session belongs according to the application message indication information.


In this embodiment of the present application, the PDU session carrying application message indication information in multiple information frame formats sent by the core network is acquired by the session acquisition module 10. The application layer belonging module 11 determines the corresponding application message for each PDU session according to the respective application message indication information. The application message corresponding to each PDU session is determined through the application message indication information. In this manner, the accuracy of quality of service flow transmission can be enhanced, the problem of an information transmission error caused because the category and source of an application message cannot be identified, the integrity of an application message can be enhanced, and the user experience can be improved.


Based on the preceding embodiments of the present application, the application message indication information in the apparatus includes at least one of an application message sequence number, an application message end mark, or an application message segment number indication.


Based on the preceding embodiments of the present application, the application layer belonging module 11 includes a first same belonging unit and a first message end unit.


The first same belonging unit is configured to determine that at least one PDU session belongs to the same application message according to the application message sequence number in the information frame format of each PDU session.


The first message end unit is configured to determine that transmission of the application message corresponding to each PDU session ends according to the application message end mark in the information frame format of each PDU session.


Based on the preceding embodiments of the present application, the application message indication information in the apparatus includes at least one of an application message sequence number or an application message segment number.


Based on the preceding embodiment of the present application, the application layer belonging module 11 includes a second same belonging unit and a second message end unit.


The second same belonging unit is configured to determine that at least one PDU session belongs to the same application message according to the application message sequence number in the information frame format of each PDU session.


The second message end unit is configured to determine that the application message corresponding to each PDU session is completely received according to the application message segment number in the information frame format of each PDU session.


Based on the preceding embodiments of the present application, the application message indication information in the apparatus includes at least one of an application message start mark or an application message end mark.


A start position unit is configured to determine the start position of the application message corresponding to each PDU session according to the application message start mark in the information frame format of each PDU session.


An end position unit is configured to determine the end position of the application message corresponding to each PDU session according to the application message end mark in the information frame format of each PDU session.


Based on the preceding embodiments of the present application, the apparatus also includes a buffer report module.


The buffer report module is configured to acquire the size of the buffer data volume corresponding to the application message sent by the UE through a buffer status report (BSR).


Based on the preceding embodiments of the present application, the size of the buffer data volume corresponding to the application message in the buffer report module includes the size of the application message reported according to a logical channel group.


Based on the preceding embodiment of the present application, the size of the buffer data volume corresponding to the application message in the buffer report module includes the size of the application message reported according to a logical channel.


Based on the preceding embodiments of the present application, the apparatus also includes a characteristic parameter module.


The characteristic parameter module is configured to determine a characteristic parameter of the application message according to an information element of a Qos flow in the PDU session.


Based on the preceding embodiments of the present application, the characteristic parameter in the characteristic parameter module includes at least one of the following: an application availability target, an application reliability target, a video traffic coding rate, video traffic transmission duration, or a transmission video scale.


Based on the preceding embodiment of the present application, the apparatus also includes an operation configuration module.


The operation configuration module is configured to, when at least one of the following operations is performed, receive configuration information provided by the core network through dedicated signaling. The operations include establishment/modification of a dedicated connection with the UE of the core network, establishment/modification of a PDU session with the UE of the core network, and establishment/modification of an evolved radio access bearer (E-RAB) with the UE of the core network.


Based on the preceding embodiments of the present application, the configuration information in the operation configuration module includes at least one of a UE traffic bearer maximum rate requirement, a UE traffic bearer delay requirement, a UE traffic bearer transmission frequency, a UE bearer traffic data volume, UE power consumption information, UE battery charge information, or UE mobility prediction information.


Based on the preceding embodiments of the present application, the UE mobility prediction information in the configuration information of the operation configuration module includes at least one of the following: historical cell information, historical cell camping duration, camping duration of the current cell, a camping start time point of the current cell, a radio resource control (RRC) connection release interval, an RRC connection suspension interval, a traffic interval, or a traffic frequency.


In an exemplary embodiment, a quality of service flow transmission apparatus may execute the quality of service flow transmission method provided by any embodiment of the present application and has functional modules and beneficial effects corresponding to the method executed. The apparatus may be performed by software and/or hardware. The apparatus includes an indication receiving module and a feedback sending module.


The indication receiving module is configured to receive at least one issued packet data convergence protocol (PDCP) data protocol data unit (PDU). The PDCP data PDU carries indication information.


The feedback sending module is configured to send message receiving feedback according to the indication information.


In an exemplary embodiment, a quality of service flow transmission apparatus may execute the quality of service flow transmission method provided by any embodiment of the present application and has functional modules and effects corresponding to the method executed. The apparatus may be performed by software and/or hardware. The apparatus includes an index receiving module and an index feedback sending module.


The index receiving module is configured to receive at least one issued packet data convergence protocol (PDCP) data protocol data unit (PDU). The PDCP data PDU carries a PDU session category index.


The index feedback sending module is configured to determine at least one of the traffic type, the quality of service (QOS) type, the QoS flow group, or the transmission method corresponding to each PDCP data session according to the PDU session category index and send the message receiving feedback according to at least one of the traffic type, the QoS type, the QoS flow group, or the transmission method.



FIG. 29 is a diagram illustrating the structure of another quality of service flow transmission apparatus according to an embodiment of the present application. The apparatus may execute the quality of service flow transmission method provided by any embodiment of the present application and has functional modules and beneficial effects corresponding to the method executed. The apparatus may be performed by software and/or hardware. The apparatus includes a data unit receiving module 20 and a message receiving feedback module 21.


The data unit receiving module 20 is configured to receive at least one issued packet data convergence protocol (PDCP) data protocol data unit (PDU). The PDCP data PDU carries application message indication information.


The message receiving feedback module 21 is configured to send the message receiving feedback according to the application message indication information.


In this embodiment of the present application, at least one issued PDCP data PDU is received by the data unit receiving module 20. The PDCP data PDU carries the application indication message. The message receiving feedback module 21 sends the message receiving feedback according to the application indication message. In this manner, the integrity of the application message receiving is improved, and the communication quality can be enhanced.


Based on the preceding embodiments of the present application, the apparatus also includes a data unit sending module.


The data unit sending module is configured to send at least one PDCP data PDU. The PDCP data PDU carries the application message indication information.


Based on the preceding embodiments of the present application, the message receiving feedback module 21 includes a data feedback unit.


The data feedback unit is configured to feed back a packet data convergence protocol (PDCP) status packet or a radio link layer control protocol (RLC) status packet for each PDCP data PDU.


Based on the preceding embodiments of the present application, the message receiving feedback module 21 includes an application feedback unit.


The application feedback unit is configured to determine the application message to which each PDCP data PDU belongs and feed back a PDCP status packet or an RLC status packet for the application message to which each PDCP data PDU belongs.


Based on the preceding embodiments of the present application, the application feedback unit is configured to determine the application message to which each PDCP data PDU belongs according to the application message indication information carried in the PDCP data PDU.


Based on the preceding embodiments of the present application, the application message indication information in the apparatus includes at least one of an application message sequence number, an application message start mark, or an application message end mark.


Based on the preceding embodiments of the present application, the application feedback unit includes a same belonging unit, a start position unit, and an end position unit.


The same belonging unit is configured to determine whether each PDCP data PDU belongs to the same application message according to the application message sequence number in the information frame format of each PDCP data PDU.


The start position unit is configured to determine that transmission of the application message corresponding to each PDCP data PDU starts according to the application message start mark in the information frame format of the protocol frame of each PDCP data PDU.


The end position unit is configured to determine that transmission of the application message corresponding to each PDCP data PDU ends according to the application message end mark in the information frame format of the protocol frame of each PDCP data PDU.


Based on the preceding embodiments of the present application, the apparatus also includes an information indication module.


The information indication module is configured to carry the application message indication information by a medium access control (MAC) header, an RLC header, and a media access control control element (MAC CE).


Based on the preceding embodiments of the present application, the apparatus also includes a number determination unit and a belong determination unit.


The number determination unit is configured to receive the number of PDUs corresponding to the application message and configured by the base station.


The belong determination unit is configured to determine the application message to which each PDCP data PDU belongs according to the number of PDUs.


Based on the preceding embodiments of the present application, the number of PDUs corresponding to the application message in the apparatus is carried by at least one of an RRC message, a PDCP header, MAC, an RLC header, or an MAC CE.



FIG. 30 is a diagram illustrating the structure of a base station according to an embodiment of the present application. The base station includes a processor 50, a memory 51, an input apparatus 52, and an output apparatus 53. One or more processors 50 may be disposed in the base station, and one processor 50 is used as an example in FIG. 30. The processor 50, the memory 51, the input apparatus 52, and the output apparatus 53 in the base station may be connected through a bus or other modes. A connection through the bus is used as an example in FIG. 30.


As a computer-readable storage medium, the memory 51 may be configured to store software programs and computer-executable programs and modules, such as the modules (the session acquisition module 10 and the application layer belonging module 11, and/or the data unit receiving module 20 and the message receiving feedback module 21) corresponding to the quality of service flow transmission apparatus in this embodiment of the present application. The processor 50 runs the software programs, instructions, and modules stored in the memory 51 to perform function applications and data processing of the base station, that is, to implement the quality of service flow transmission method described above.


The memory 51 may mainly include a program storage region and a data storage region. The program storage region may store an operating system and an application program required for at least one function, and the data storage region may store data or the like created according to the use of the base station. Additionally, the memory 51 may include a high-speed random-access memory and may also include a non-volatile memory, for example, at least one magnetic disk memory, a flash memory, or another non-volatile solid-state memory. In some examples, the memory 51 may include memories that are remotely disposed with respect to the processor 50. These remote memories may be connected to the base station via a network. Examples of the preceding network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.


The input apparatus 52 may be used for receiving inputted digital or character information and for generating key signal input related to user settings and function control of the base station. The output apparatus 53 may include a display device, for example, a display screen.



FIG. 31 is a diagram illustrating the structure of a terminal according to an embodiment of the present application. The terminal includes a processor 60, a memory 61, an input apparatus 62, and an output apparatus 63. One or more processors 60 may be disposed in the terminal, and one processor 60 is used as an example in FIG. 31. The processor 60, the memory 61, the input apparatus 62, and the output apparatus 63 in the terminal may be connected through a bus or other modes. A connection through a bus is used as an example in FIG. 31.


As a computer-readable storage medium, the memory 61 may be configured to store software programs and computer-executable programs and modules, such as the modules (the data unit receiving module 20 and the message receiving feedback module 21) corresponding to the quality of service flow transmission apparatus in this embodiment of the present application. The processor 60 runs the software programs, instructions, and modules stored in the memory 61 to perform function applications and data processing of the terminal, that is, to implement the quality of service flow transmission method described above.


The memory 61 may mainly include a program storage region and a data storage region. The program storage region may store an operating system and an application program required for at least one function, and the data storage region may store data or the like created according to the use of the terminal. Additionally, the memory 61 may include a high-speed random-access memory and may also include a non-volatile memory, for example, at least one magnetic disk memory, a flash memory, or another non-volatile solid-state memory. In some examples, the memory 61 may include memories which are remotely disposed with respect to the processors 60. These remote memories may be connected to the terminal via a network. Examples of the preceding network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.


The input device 62 may be used for receiving inputted digital or character information and for generating key signal input related to user settings and function control of the terminal. The output apparatus 63 may include a display device, for example, a display screen.


An embodiment of the present application provides a storage medium including computer-executable instructions. When executing the computer-executable instructions, a computer processor is configured to perform a quality of service flow transmission method. The method includes the following:


At least one protocol data unit (PDU) session sent by a core network is acquired, where information frame format of the PDU session carries application message indication information; and an application message to which each PDCP session belongs is determined according to the application message indication information.


Moreover/Alternatively, the session acquisition module is configured to acquire at least one PDU session sent by the core network. The information frame format of the PDU session carries the application message indication information. The application layer belonging module is configured to determine the application message to which each PDU session belongs according to the application message indication information.


From the preceding description of the embodiments, the present application may be implemented by means of both software and required general-purpose hardware, and also by means of hardware. The technical solutions of the present application may be essentially embodied in the form of a software product. The software product in a computer may be stored in a computer-readable storage medium such as a floppy disk, a read-only memory (ROM), a random-access memory (RAM), a flash memory, a hard disk, or an optical disc in the computer and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to perform the method of the embodiments of the present application.


Units and modules included in the embodiment of the quality of service flow transmission apparatus are just divided according to the functional logic, and the division is not limited to this, as long as the corresponding functions can be implemented. In addition, the names of each functional unit are just intended for distinguishing and are not to limit the protection scope of the embodiments of the present application.


All or part of the steps in the method, and functional modules/units in the system and device disclosed above may be implemented as software, firmware, hardware and appropriate combinations thereof.


In the hardware implementation, the division of the preceding functional modules/units may not correspond to the division of physical components. For example, one physical component may have multiple functions, or one function or step may be performed jointly by several physical components. Some or all physical components may be implemented as software executed by a processor such as a central processing unit, a digital signal processor or a microprocessor, may be implemented as hardware, or may be implemented as integrated circuits such as application-specific integrated circuits. Such software may be distributed over computer-readable media. The computer-readable media may include computer storage media (or non-transitory media) and communication media (or transitory media). As is known to those having ordinary skill in the art, the term computer storage media include volatile and non-volatile as well as removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). The computer storage media include, but are not limited to, a RAM, a ROM, an electrically erasable programmable read-only memory (EEPROM), a flash memory, or other memory technologies, a compact disc read-only memory (CD-ROM), a digital versatile disc (DVD) or other optical disc memories, magnetic cassettes, magnetic tapes, magnetic disk memories or other magnetic storage apparatuses, or any other medium used for storing the desired information and accessible by a computer. Moreover, as is known to those having ordinary skill in the art, the communication media generally include computer-readable instructions, data structures, program modules or other data in carriers or in modulated data signals transported in other transport mechanisms and may include any information delivery medium.

Claims
  • 1. A quality of service flow transmission method, comprising: acquiring at least one protocol data unit (PDU) session sent by a core network, wherein an information frame format of the at least one PDU session carries indication information; anddetermining, according to the indication information, a category to which the at least one PDU session belongs.
  • 2. The method according to claim 1, wherein the indication information comprises application message indication information, and determining, according to the indication information, the category to which the at least one PDU session belongs comprises: determining an application message to which the at least one PDU session belongs according to the application message indication information.
  • 3. (canceled)
  • 4. The method according to claim 2, wherein the application message indication information comprises at least one of an application message sequence number, an application message end mark, or an application message segment number indication.
  • 5. The method according to claim 2, wherein determining, according to the application message indication information, the application message to which the at least one PDU session belongs comprises at least one of the following: determining, according to an application message sequence number in the information frame format of the at least one PDU session, that different PDU sessions in the at least one PDU session belong to a same application message; ordetermining, according to an application message end mark in the information frame format of the at least one PDU session, that transmission of the application message corresponding to the at least one PDU session ends.
  • 6. The method according to claim 2, wherein the application message indication information comprises at least one of an application message sequence number or an application message segment number.
  • 7. (canceled)
  • 8. The method according to claim 2, wherein the application message indication information comprises at least one of an application message start mark or an application message end mark; wherein determining, according to the application message indication information, the application message to which the at least one PDU session belongs comprises:determining, according to the application message start mark in the information frame format of the at least one PDU session, a start position of the application message corresponding to the at least one PDU session; anddetermining, according to the application message end mark in the information frame format of the at least one PDU session, an end position of the application message corresponding to the at least one PDU session.
  • 9. (canceled)
  • 10. The method according to claim 1, further comprising: acquiring a size of a buffer data volume corresponding to an application message sent by a user equipment (UE) through a buffer status report (BSR).
  • 11. The method according to claim 10, wherein the size of the buffer data volume corresponding to the application message comprises a size of the application message reported according to a logical channel group.
  • 12. The method according to claim 10, wherein the size of the buffer data volume corresponding to the application message comprises a size of the application message reported according to a logical channel.
  • 13. The method according to claim 1, further comprising: determining a characteristic parameter of an application message according to an information element of a QoS flow in the at least one PDU session;wherein the characteristic parameter comprises at least one of the following:an application availability target, an application reliability target, a video traffic coding rate, video traffic transmission duration, or a transmission video scale.
  • 14. (canceled)
  • 15. The method according to claim 1, further comprising: in a case where at least one of the following operations is performed, receiving configuration information provided by the core network through dedicated signaling:establishing or modifying a dedicated connection with a UE of the core network; establishing or modifying a PDU session with a UE of the core network; or establishing or modifying an evolved radio access bearer (E-RAB) with a UE of the core network.
  • 16. The method according to claim 15, wherein the configuration information comprises at least one of the following: a UE traffic bearer maximum rate requirement, a UE traffic bearer delay requirement, a UE traffic bearer transmission frequency, a UE bearer traffic data volume, UE power consumption information, UE battery charge information, or UE mobility prediction information.
  • 17. (canceled)
  • 18. A quality of service flow transmission method, comprising: receiving at least one issued packet data convergence protocol (PDCP) data protocol data unit (PDU), wherein the at least one PDCP data PDU carries indication information; andsending message receiving feedback according to the indication information.
  • 19. The method according to claim 18, wherein the indication information comprises application message indication information, and sending the message receiving feedback according to the indication information comprises: determining, according to the application message indication information, an application message to which the at least one PDCP data PDU belongs, and sending the message receiving feedback according to the application message to which the at least one PDCP data PDU belongs.
  • 20. The method according to claim 18, wherein the indication information comprises a PDU session category index, and sending the message receiving feedback according to the indication information comprises: determining at least one of a traffic type corresponding to the at least one PDCP data PDU, a quality of service (QOS) type corresponding to the at least one PDCP data PDU, a QoS flow group corresponding to the at least one PDCP data PDU, or a transmission method corresponding to the at least one PDCP data PDU according to the PDU session category index; andsending the message receiving feedback according to the at least one of the traffic type, the QoS type, the QoS flow group, or the transmission method.
  • 21-23. (canceled)
  • 24. The method according to claim 19, wherein the application message indication information comprises at least one of an application message sequence number, an application message start mark, an application message end mark, or an application message segment number indication.
  • 25-26. (canceled)
  • 27. The method according to claim 19, further comprising: receiving a number of PDUs corresponding to the application message and configured by a base station; anddetermining the application message to which the at least one PDCP data PDU belongs according to the number of PDUs.
  • 28-30. (canceled)
  • 31. A base station, comprising: at least one processor; anda memory configured to store at least one program,wherein when executing the at least one program, the at least one processor performs the following:acquiring at least one protocol data unit (PDU) session sent by a core network, wherein an information frame format of the at least one PDU session carries indication information; anddetermining, according to the indication information, a category to which the at least one PDU session belongs.
  • 32. A terminal, comprising: at least one processor; anda memory configured to store at least one program,wherein when executing the at least one program, the at least one processor performs the quality of service flow transmission method according to claim 18.
  • 33. A non-transitory computer-readable storage medium storing a computer program, wherein when executed by a processor, the computer program performs the quality of service flow transmission method according to claim 1.
Priority Claims (1)
Number Date Country Kind
202110358304.5 Apr 2021 CN national
PCT Information
Filing Document Filing Date Country Kind
PCT/CN2021/123728 10/14/2021 WO