CN111373834B

CN111373834B - Client device, access network device, method and computer program for establishing a data radio bearer

Info

Publication number: CN111373834B
Application number: CN201780096949.8A
Authority: CN
Inventors: 毗湿奴·普雷曼; 拉马·库马尔·莫匹代韦
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-11-16
Filing date: 2017-11-16
Publication date: 2022-05-24
Anticipated expiration: 2037-11-16
Also published as: CN111373834A; WO2019096393A1

Abstract

Quality of service parameters related to the application specific data (301, 401) may be sent to the wireless network when the client device starts to establish a radio bearer to the wireless network. A default data radio bearer may be established with the dedicated data radio bearer, wherein information required to establish a quality of service flow to satisfy the application may be transmitted along with signaling used to establish the default data radio bearer.

Description

Client device, access network device, method and computer program for establishing a data radio bearer

Technical Field

The present invention relates to the field of wireless communications, and more particularly, to wireless data transmission and establishment of a data radio bearer.

Background

To facilitate the development of wireless communication technologies, the third generation partnership project (3 GPP) has established a Long Term Evolution (LTE) project. To further advance transmission technology, a fifth generation radio (5G) next generation radio (NR) was established. In wireless communication, a client device, such as a user equipment, may communicate with a wireless network over a data radio bearer. Client devices sometimes need to establish a data radio bearer and acquire an IP address, for example, when the client device enters a new registration area or wakes up from a sleep state.

A client device may run an application with a specific QoS requirement (Quality of Service) such as video call or streaming data traffic when establishing a data radio bearer. The access network knows the nature of the uplink data packet to be processed only after establishing the default data radio bearer and receiving the first data packet through the default data radio bearer. The default data radio bearer may not support the QoS requirements of the application. And QoS requirement information, such as QoS flow, is transported to the access network over a default data bearer. Thus, a dedicated data bearer can be selected and established according to the QoS flow. The QoS flows in the dedicated data bearers that are typically established for the application data conform to the application requirements.

An example of the 5G NR QoS model is disclosed in the technical specification 3GPP TS 23.501 V1.4.0, chapter 5.7. The 5G QoS model supports a framework based on QoS flows. The 5G QoS model supports both QoS flows that require a guaranteed stream bit rate and QoS flows that do not require a guaranteed stream bit rate.

QoS flows are the finest granularity of QoS differentiation. The QoS Flow ID (QFI) is used to identify QoS flows in a 5G system. The QFI is carried in the encapsulation header without any changes to the end-to-end header. QFI is applicable to Protocol Data Units (PDUs) with different types of payloads, i.e., IP packets, unstructured PDUs, and ethernet frames. QFI is unique within a PDU session.

Disclosure of Invention

It is an object of the present invention to provide an efficient concept for establishing a dedicated data radio bearer.

This object is achieved by the features of the independent claims. Further inventive embodiments are apparent from the dependent claims, the description and the drawings.

The disclosed solution is based on the discovery that quality of service parameters related to application specific data can be sent to a wireless network when a client device starts to establish a radio bearer to the wireless network. A dedicated data radio bearer may be established together with a default data radio bearer, wherein information required for establishing a quality of service flow required for an application may be transmitted using signaling for establishing the default data radio bearer.

In a first aspect, a client device for communicating in a wireless network is disclosed. The client device is to: detecting application specific data transmitted over a radio bearer; detecting at least one quality of service parameter associated with the application specific data; sending information related to the quality of service parameter to the wireless network along with a radio bearer setup request; and establishing a default data radio bearer and a dedicated data radio bearer as a response to the information related to the quality of service parameter sent with the radio bearer establishment request.

Quality of service describes a connection attribute between two or more entities, an end-to-end connection attribute, or an edge-to-edge attribute between a user equipment and a user plane function. Quality of service parameters used in 3GPP include, for example, QCI, Allocation and Retention Priority (ARP), Guaranteed Bit Rate (GBR), Maximum Bit Rate (MBR), and AMBR. More generally, the QoS parameter may be service response time, loss, signal-to-noise ratio, crosstalk, echo, interruption, frequency response, loudness level, jitter, hysteresis, packet delay, packet error rate, averaging window, or any parameter related to communication quality. In one example, the application specific data is related data in a peer-to-peer communication, wherein the client device transmits the data to the wireless network. Applications that generate application specific data include, for example, conversational voice, conversational video, live streaming, real-time gaming, interactive gaming, buffered streaming, IMS signaling, video, TCP-based applications such as www, email, chat, ftp, p2p file sharing, progressive format video, mission critical delay sensitive signaling, mission critical data, or V2X messages. The information related to the quality of service parameter may comprise a plurality of parameters.

The default radio bearer and the dedicated data radio bearer may be established simultaneously, or at least continuously, since the information related to the quality of service parameters is sent to the wireless network with the radio bearer establishment request. Thus, an efficient concept of establishing dedicated data radio bearers is achieved.

In a further implementation manner of the first aspect, the radio bearer establishment request is a radio resource control connection request. In one embodiment, the radio bearer setup request is a request to obtain an IP address from a network. A Radio Resource Control (RRC) protocol is a layer between a User Equipment (UE) and an evolved NodeB (eNB), and exists in an IP layer. RRC messages may be transmitted through the PDCP protocol.

In a further implementation of the first aspect, the client device is configured to detect at least one quality of service parameter related to the application specific data from at least one data item of the group of: destination address, source address, destination port, and source port. The data items are Internet Protocol (IP) data items. Applications may be detected by addresses or ports having standardized purposes. In one embodiment, the addresses or ports have been mapped into a database with corresponding QoS parameters. The client device and the network may include copies of the database. Thus, the client device may determine the QoS parameters from these data items. The QoS parameters need not be explicitly indicated by the application.

In a further implementation of the first aspect, the client device comprises a non-access stratum comprising an upstream packet filter for detecting the at least one quality of service parameter related to the application specific data. The upstream packet filter may be used to detect IP data items, such as addresses or ports; in a further embodiment, the upstream packet filter is configured to receive information about the usage of the upstream packet from an application or operating system. In further embodiments, a set of packet filters is used in the QoS rules or SDF templates to identify QoS flows. The packet filter set may contain packet filters in the downstream direction, packet filters in the upstream direction, or packet filters for both directions. Corresponding to the PDU session type, the packet filter set is an IP packet filter set in one embodiment; in one embodiment, is an ethernet packet filter set.

In a further implementation manner of the first aspect, the information related to the qos parameter is a Quality of Service flow identifier (QFI). The client device may classify and label the upstream user plane traffic based on the QoS rules, associating the upstream traffic with the QoS flows. A QoS rule may include a QoS rule identification unique in the PDU session, the QFI of the associated QoS flow, one or more packet filters, or a priority value. For an assigned QFI, the QoS rules may contain the QoS parameters related to the client device and/or the application providing application specific data. In a further embodiment, multiple QoS rules are associated with the same QoS flow, i.e. with the same QFI.

In further embodiments of the first aspect, the client device is configured to transmit the first data packet of the application specific data using the dedicated data radio bearer. In one example, the dedicated data radio bearer may be established in the same step as the default data radio bearer, which may not be used at all for transmitting any of the application specific data. Thereby ensuring that the application specific data is transmitted from the beginning using the dedicated radio bearer with the respective QoS parameters.

In a further embodiment of the first aspect, the client device is configured to transmit all data packets of the application specific data of an application session using the dedicated data radio bearer. Thus, the application specific data is not transmitted on the default radio bearer. An application session is defined as a period during which the application transmits uplink data to the wireless network. The client device may run multiple application sessions simultaneously.

In a further embodiment of the first aspect, the client device is configured to transmit the information related to the quality of service parameter in an uplink data status cell header. In one embodiment, the quality of service parameter is a QoS flow identification.

In further embodiments of the first aspect, the client device is configured to encode the information related to the quality of service parameter into a bitmap of a quality of service flow identification. An example of a quality of service flow identification bitmap showing a standardized 5QI to QoS feature mapping is disclosed in 3GPP TS 23.501 V1.4.0, chapter 5.7.4.

In a further implementation of the first aspect, the radio bearer setup request comprises a non-access stratum service request message or a tracking area update request message.

A second aspect discloses an access network device for receiving a radio bearer setup request from a client device; receiving information related to a quality of service parameter while receiving the radio bearer establishment request; and

establishing a default data radio bearer and a dedicated data radio bearer with the client device as a response to the radio bearer establishment request; wherein the dedicated data radio bearer comprises a quality of service flow that conforms to the at least one quality of service parameter received from the client device. The establishment of the default data radio bearer and the dedicated data radio bearer may be performed simultaneously in the same step or may be performed continuously. The data radio bearer is established by the access network through a radio resource control reconfiguration message. The information about the default data radio bearer and the required dedicated data radio bearer may reside in a single radio resource control reconfiguration message, wherein the establishment of both data radio bearers occurs simultaneously.

In an embodiment of the second aspect, the access network device is an evolved NodeB (eNB) or a next generation base station (gNB). The data radio bearer is established by the NodeB. The NodeB processes the radio resource control connection request. The client device, e.g., user equipment, sends QFI information for non-access stratum messages. And the core network receives the QFI information and sends the QFI information to the access network equipment.

In a further embodiment of the second aspect, the radio bearer setup request is a radio resource control connection request. In a further embodiment of the second aspect, the information related to the quality of service parameter comprises a quality of service flow identification. In a further embodiment of the second aspect, the access network device is configured to receive the information related to the quality of service parameter in an uplink data status information element header.

In a further embodiment of the second aspect, the information related to the quality of service parameter is encoded into a bitmap of quality of service flow identifications. In a further embodiment of the second aspect, the radio bearer setup request comprises a non-access stratum service request message or a tracking area update request message.

A third aspect discloses a method for a client device, comprising: detecting application specific data transmitted over a radio bearer; detecting at least one quality of service parameter associated with the application specific data; sending information related to the service quality parameter to a wireless network along with a radio bearer establishment request; and establishing a default data radio bearer and a dedicated data radio bearer as a response to the information related to the quality of service parameter sent with the radio bearer establishment request.

In a further embodiment of the third aspect, the radio bearer setup request is a radio resource control connection request. In a further embodiment of the third aspect, the method comprises detecting at least one quality of service parameter related to the application specific data from at least one data item of the group of: destination address, source address, destination port, and source port. In a further embodiment of the third aspect, the method comprises a non-access stratum comprising an uplink packet filter for detecting the at least one quality of service parameter related to the application specific data. In a further embodiment of the third aspect, the information related to the quality of service parameter is a quality of service flow identity. In a further embodiment of the third aspect, the method comprises transmitting the first data packet of the application specific data using the dedicated data radio bearer. In a further embodiment of the third aspect, the method comprises transmitting all data packets of the application specific data of an application session using the dedicated data radio bearer. In a further embodiment of the third aspect, the method includes receiving the information related to the quality of service parameter in an uplink data status cell header. In a further embodiment of the third aspect, the method comprises encoding the information related to the quality of service parameter into a bitmap of a quality of service flow identification. In a further embodiment of the third aspect, the radio bearer setup request comprises a non-access stratum service request message or a tracking area update request message.

A fourth aspect discloses a method for an access network device, comprising: receiving a radio bearer establishment request from a client device; receiving information related to a quality of service parameter while receiving the radio bearer establishment request; and establishing a default data radio bearer and a dedicated data radio bearer as a response to the radio bearer establishment request; wherein the dedicated data radio bearer comprises a quality of service flow that conforms to at least one quality of service parameter received from the client device.

In a further embodiment of the fourth aspect, the radio bearer setup request is a radio resource control connection request. In a further embodiment of the fourth aspect, the information related to the quality of service parameter comprises a quality of service flow identification. In a further embodiment of the fourth aspect, the method includes receiving the information related to the quality of service parameter in an uplink data status cell header. In a further embodiment of the fourth aspect, the information related to the quality of service parameter is encoded into a bitmap of quality of service flow identifications. In a further embodiment of the fourth aspect, the radio bearer setup request comprises a non-access stratum service request message or a tracking area update request message.

A fifth aspect discloses a computer program comprising program code for performing the method according to claim 17 or 18 when said program code is executed on a computer. The computer program may be executed by a client device or by an access network device. The client device or the access network device may be programmably arranged to execute the computer program.

Aspects disclosed herein reduce the delay in establishing a dedicated radio bearer for pending uplink data. The signaling required to establish multiple radio bearers in the network is reduced, thereby saving radio transmission bandwidth. This scheme may be used when application specific IP packets belonging to one or more QoS flows are waiting to be sent on the uplink. The proposal accelerates the establishment of the special DRB and reduces signaling by establishing a plurality of DRBs simultaneously.

Embodiments or aspects of the invention may be implemented in hardware, software, or any combination thereof. Many of the attendant features will become more readily apparent as the same becomes better understood by reference to the following detailed description considered in connection with the accompanying drawings. The aspects and embodiments described herein are not limited to embodiments that solve any or all disadvantages of known wireless transmission systems.

Drawings

Embodiments of the invention will be described in conjunction with the following drawings, in which:

fig. 1a schematically shows an example of a telecommunication system for practicing an embodiment of the invention.

Fig. 1b schematically shows an example of a telecommunication system for practicing an embodiment of the invention.

Fig. 2 shows a simplified diagram of an example of an embodiment with functional modules of a client device.

Figure 3 shows a simplified signaling flow diagram of an example of an embodiment.

Figure 4 shows a simplified signaling flow diagram of an example of an embodiment.

Fig. 5 shows an example of an embodiment with cells.

Fig. 6 shows an example of an embodiment with information elements.

Fig. 7 shows an example of an embodiment with cells.

Fig. 8 shows a simplified flowchart of an example of a method embodiment.

Fig. 9 shows a simplified flowchart of an example of a method embodiment.

The same reference numerals are used to denote the same or at least functionally equivalent features.

Detailed Description

The detailed description provided below in connection with the appended drawings is intended as a description of the present examples and is not intended to represent the only forms in which the present example may be constructed or utilized. However, the same or equivalent functions and sequences may be accomplished by different examples.

Fig. 1a schematically shows a simplified example of a telecommunication network disclosing an exemplary embodiment of an access network device and a client device. In this example, the

client devices

130, 140, 150 are wirelessly connected to the access network device 120. All

client devices

130, 140, 150 include similar components as client device 130: at least one processor 131 and memory 132 to store instructions that, when executed, cause the client device 130 to perform the functions described below. The transceiver 133 is used to provide a communication link to a telecommunications network via a wireless link. The functions of the transceiver 133 may be independent in that the transceiver may have a dedicated processor. The processor 131 can be used to cause the transceiver to perform specific functions. One example of a

client device

130, 140, 150 is a user device, a device for wirelessly connecting to the access network device 120. The

client devices

130, 140, 150 may be functional modules for operation in a user device, such as a communication module of a smartphone.

The access network device 120 provides the serving cell 121 to the

user equipment

130, 140, 150. In this example, a portion of the telecommunications network 100 is represented by a cloud, as the telecommunications network 100 may be implemented in a variety of ways. The telecommunications network 100 may reside at least partially in a cloud computing environment. In one embodiment, part of the functionality of the access network equipment 120 is distributed to the devices 110 connected to the access network equipment 120 over the telecommunications network 100. The apparatus 110 includes at least one processor 111 and memory 112 for storing instructions that, when executed, cause the apparatus 110 and the access network device 120 to perform the functions described herein. The transceiver 113 is used to provide communication links to the

client devices

130, 140, 150 over wireless links. Further, in one embodiment, the apparatus 110 is configured to control the functions of the access network device 120.

The access network device 120 may be an evolved NodeB (eNB) or a next generation NodeB (gNB) providing a direct wireless link to the

client devices

130, 140, 150, an access network device aggregation, an access node, or a network eNB.

Fig. 1b schematically shows another simplified example of a telecommunications network, disclosing one exemplary embodiment of an access network device 120 and a user equipment 130, where the apparatus 110 resides at the network device 120. Apparatus 110 and its components may be defined as part of access network device 120. Examples of wireless communication technologies of embodiments disclosed herein are LTE networks or 5G NR networks.

In 5G NR, the QoS model supports a QoS flow-based framework. QoS flows are the finest granularity of QoS differentiation in a PDU session. A PDU session is an association between a User Equipment (UE) and a data network providing PDU exchange. The higher layer packet is mapped to the appropriate radio resource in two steps:

1. non-access stratum (NAS) mapping: the high-layer packet is mapped to different QoS flows through a packet filter;

2. access Stratum (AS) mapping: the QoS flows are mapped to different radio resources.

The mapping configuration may be received at PDU session setup or QoS flow setup. The NAS layer has enough information to map incoming IP packets to corresponding QoS flows through packet filters. As an example of the prior art solution, considering a case that a default Data Radio Bearer (DRB) does not exist, for example, since a Radio Resource Control (RRC) connection has been released or is suspended due to inactivity and an Uplink (UL) packet should be sent, the NAS initiates a service request procedure. The gNB of the access network establishes the RRC connection and the default DRB. And the user equipment sends the UL packet to be processed through the default DRB. When the gNB receives a packet through a default DRB, the gNB is used to evaluate whether a dedicated DRB needs to be established. And the gNB establishes the special DRB according to the QoS processing requirement of the received packet. In other words, the private DRB is established after the data packet is transmitted through the default DRB.

Similarly, if a registration procedure is initiated during the pending UL data, the ue notifies the Core Network (CN) of the pending uplink data. The CN sends the information to AN Access Network (AN), and the access network establishes a default radio bearer after the registration process. After the network receives the first data packet from the user equipment through the default DRB, a dedicated DRB is established if necessary.

According to aspects disclosed herein, the network knows the QoS treatment required for pending upstream packets even before the default DRB is established. This is achieved by establishing a dedicated DRB by providing access network information before establishing a default DRB.

Embodiments of the present invention take advantage of the fact that with the NAS upstream packet filter, the client device 130 is able to derive the QoS flow (and thus the QoS parameters) to which the pending upstream packets for application specific data belong. The network receives information of the dedicated DRB required for the pending uplink packet through a corresponding QFI containing the pending packet, for example, in an uplink data status element (IE).

The uplink data state IE is implemented under two scenarios described in the 3GPP TS 24.890 protocol 1.0.3 release:

(a) when UL user data is pending and there is no DRB present (e.g., RRC connection release or suspension), the NAS initiates a service request procedure to establish a DRB, as will be explained in connection with fig. 3;

(b) when UL user data is pending and the user equipment is not registered in the current zone, the NAS initiates a registration request flow, as will be explained in connection with fig. 4.

The client device 130 is configured to include QFI in the upstream data state IE for any flow that requires the upstream data state IE. The network receives QoS processing information required by the uplink packet to be processed according to the IE, and establishes at least one special DRB together with the default DRB.

Receiving an upstream NAS filter in the user equipment at PDU session establishment. The upstream NAS filter displays/defines the mapping of IP packets to corresponding QoS flows according to the IP header information. Examples of the information include a destination address, a source address, a destination port, and a source port. Thus, with an upstream NAS filter, the client device 130 can detect a quality of service parameter (e.g., QoS flow) associated with the upstream data from the IP header information in the upstream data.

An example of an embodiment is shown in fig. 2, which shows a simplified diagram of a client device 130, in this example the client device 130 is a user device. The non-access stratum configures the application data controller 220 using an upstream packet filter. Application data controller 220 is a functional module in one example of user device 130.

The user device 130 may run the application 210 or the user device 130 may receive application specific data from an application running on an external device, wherein the user device 130 provides wireless transmission for the application. In step 21, the application specific data from the application arrives at the application data controller 220. The application data controller 220 determines whether the user equipment 130 has an established data radio bearer. If there is no data radio bearer, the application data controller 220 should extract the QFI of the data packet using the configured upstream packet filter. In step 22, the application data controller 220 is configured to notify the NAS230 of the cached application specific data and the at least one QFI. Application specific data may be buffered by placing it in a queue. NAS230 is used to maintain a bitmap that assigns QoS flows to IP packets.

To establish the default DRB and/or the dedicated DRB, an RRC connection is established. In step 23, the NAS is configured to send a service request message to the access network 240 if the RRC connection has been released or suspended. In step 24, the access network 240 is configured to establish a default radio bearer and a dedicated radio bearer after receiving the service request message.

In 5G NR, a service request message includes an uplink data status element (IE) having a PDU session ID. The embodiment of the invention also transmits the QoS flow ID of the corresponding UL packet to be processed in the uplink data state IE besides the PDU session ID.

Fig. 3 shows a service request flow based on QFI in the uplink data state IE, where the access and mobility management function (AMF) informs the gNB. In an embodiment, if the default DRB does not meet the QoS requirements of the application, the gNB is used to establish the default DRB and the dedicated DRB.

In step 300, the user equipment 130 initially does not have a radio resource control connection. In step 301, the application 210 generates application specific data 301 that is sent to the NAS 230. In step 302, NAS230 sends a service request to Access Stratum (AS) 240. In step 303, AS 240 establishes random access to the nodeb 250 using an RRC connection request. In step 304, an RRC connection is established. Step 305 completes the RRC connection setup for the service request from AS 240 to the gnnodeb 250. In step 306, the nodeb sends the service request to the AMF260 with NAS signaling (QoS flow information, e.g. QoS flow ID, QFI, containing pending application specific data). Information related to the QoS parameters of the application specific data 301 is transmitted to the AMF. In step 307, a dedicated data radio bearer and a default data radio bearer are established between the access stratum 240 and the gNodeB 250. In other words, at least two data bearers are established in step 307. If the user equipment 130 has application specific data 301 requiring a plurality of dedicated data radio bearers, these dedicated data radio bearers may also be established in step 307. Steps 308 to 310 complete the security and radio bearer configuration and NAS signaling. In step 311, the application specific data is transmitted on the dedicated radio bearer according to the defined QoS flow.

In one example, since the user equipment 130 is not registered in the current registration area, the uplink data is pending, as shown in step 400 in fig. 4. The user equipment 130 may trigger a registration procedure including the uplink data state IE. The QoS flow ID of the pending UL packet may be transmitted in the uplink data state IE of the registration request.

Fig. 4 is a simplified signaling diagram of a registration procedure based on QFI in the uplink data state IE. In this example, AMF260 notifies gNB 250. Then, accordingly, the gNB 250 establishes a default DRB and a dedicated DRB based on the information received from the AMF 260. Since the access network device 250 directly receives the QFI of the pending UL packet before the default DRB is established, the access network device 250 can simultaneously establish the default DRB and the dedicated DRB corresponding to the application data QoS requirement. Accordingly, the first packet of the QoS flow may be sent directly from the client device 130 to the access network device 250 through the dedicated DRB.

The diagram in fig. 4 is now explained in detail. In step 401, the application 210 generates application specific data 401 that is sent to the NAS 230. In step 402, NAS230 sends a service request to Access Stratum (AS) 240. In step 403, AS 240 establishes random access to the nodebs 250 using an RRC connection request. In step 404, an RRC connection is established, and in step 405, the RRC connection establishment is completed for the service request from AS 240 to the gnnodeb 250. The RRC complete message carries a NAS message, where the NAS message includes a QoS parameter of the application specific data, such as QFI. In step 406, the nodeb sends the service request to the AMF260 along with NAS signaling, which carries the NAS message received from the AS 240. Accordingly, information related to the QoS parameters of the specific application data 401 is transmitted to the AMF 260. In step 407, NAS230 and gNB 250 complete NAS registration. In step 408, the access network device, the gNB, reconfigures the RRC and establishes a dedicated data radio bearer and a default data radio bearer. At least two data bearers are established in step 408. If the user equipment 130 has application specific data 401 that requires multiple dedicated data radio bearers, these dedicated data radio bearers may also be established in step 408. In step 409, the application specific data is transmitted to the access network according to the defined QoS flow.

One example of an embodiment for embedding the QFI in the upstream data status IE is to use the bitmap 500, as shown in fig. 5. Bitmap 500 represents the valid QFI. Assume that QFI consists of 7 bits, allowing values from 0 to 127. The bitmap 500, which may be 16 bytes in length, may be included in the upstream data state IE. As shown in fig. 5, the leftmost bit (bit at 127) represents QFI 127, and the rightmost bit (bit at 0) represents QFI 0.

Fig. 6 shows an uplink data state IE including a bitmap. If the application specific data packet buffered in the user equipment belongs to QFI x, 0 < x < 127, bit x in the bitmap will be set to 1. If any of these values are retained as defined by the standard, they will be set to zero and the recipient (network) of the message may be configured to discard the value.

Different schemes of encoding QFI as an upstream data state IE may be used. According to another example of an embodiment, the leftmost bit may represent QFI 0 and the rightmost bit may represent QFI 127. In the uplink data state IE, byte 1 may be written immediately after "PDU session ID and any other NAS parameters", as shown in fig. 6. The QFI value is not limited by any current value and the size of the bitmap can be increased accordingly. QFI may indicate a particular application, rather than a separate usage class.

One example of an embodiment for embedding the QFI in the upstream data state IE includes a fixed number of QFIs. The scheme includes a fixed number n of QFIs. If the number of QFIs corresponding to the cached application-specific package exceeds N, only the N QFIs with the highest priority are included. The priority is determined from the priority classes in table 5.7.4-1 according to the 3GPP TS 23.501 protocol. For example, fig. 7 shows that N is 5. Assuming that the number of QFIs corresponding to the packets cached in the user equipment exceeds 5, the 5 QFIs with the highest priority are selected to be included in the uplink data state IE, "QFI a" is the highest priority, "QFI b" is the next highest priority, and so on.

Fig. 8 shows a flowchart of one exemplary embodiment of a method for the client device 130. The method comprises the following steps: in step 801, application specific data for transmission over a radio bearer is detected. Step 802 comprises detecting at least one quality of service parameter associated with the application specific data. Step 803 comprises sending information related to the quality of service parameter to the wireless network with the radio bearer setup request. Step 804 comprises establishing a default data radio bearer and a dedicated data radio bearer in response to the information related to the quality of service parameter sent with the radio bearer establishment request.

The method described in accordance with fig. 8 may be performed by the client device 130. The detecting step 801 may be performed, for example, by the processor 131, and the sending step 803 may be performed, for example, by the transceiver 133. Further features of the method stem from the functionality of the apparatus 100. The method may be performed by a computer program.

Fig. 9 shows a flowchart of an exemplary embodiment of a method for accessing network device 120 according to fig. 1a or 1 b. The access network device may be the gNB 250. The method comprises the following steps: in step 901, a radio bearer establishment request from a client device is received; in step 902, receiving the radio bearer establishment request and receiving information related to a quality of service parameter; and step 903, establishing a default data radio bearer and a dedicated data radio bearer as a response to the radio bearer establishment request. The dedicated data radio bearer comprises a quality of service flow that conforms to at least one quality of service parameter received from the client device.

The method described in fig. 9 may be performed by access network device 120. The receiving step 901 may be performed, for example, by the transceiver 113 and the establishing step 903 may be performed, for example, by the processor 111. Other features of the method stem directly from the functionality of the access network equipment 120. The method may be performed by a computer program.

The invention is described herein in connection with various embodiments. Other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed invention, from a study of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the indefinite article "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage. A computer program may be stored or distributed on a suitable medium, such as an optical storage medium or a solid-state medium supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the internet or other wired or wireless telecommunication systems.

Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims.

While the invention has been described with reference to specific features and embodiments thereof, it will be apparent that various modifications and combinations of the invention can be made without departing from the spirit and scope of the invention. The specification and figures are to be regarded only as illustrative of the invention as defined in the appended claims and any and all modifications, variations, combinations, or equivalents that fall within the scope of the specification are contemplated.

Claims

1. A client device for communicating in a wireless network, comprising a processor and memory to:

detecting application specific data (301, 401) transmitted over a radio bearer;

detecting at least one quality of service parameter related to the application specific data (301, 401);

sending information related to the quality of service parameters (303, 403) to the wireless network with a radio bearer setup request, the radio bearer setup request being a radio resource control connection request; and

-establishing a default data radio bearer and a dedicated data radio bearer (307, 408) as a response to said information related to said quality of service parameters (303, 403) sent with said radio bearer establishment request.

2. A client device according to claim 1, characterized in that it is arranged to detect at least one quality of service parameter related to said application specific data (301, 401) from at least one data item from the group of: destination address, source address, destination port, and source port.

3. A client device according to claim 1 or 2, comprising a non-access stratum comprising an upstream packet filter for detecting said at least one quality of service parameter related to said application specific data (301, 401).

4. A client device according to claim 1 or 2, characterized in that the information related to the quality of service parameters (303, 403) is a quality of service flow identification.

5. A client device according to claim 1, characterized by a first data packet for transmitting said application specific data (301, 401) using said dedicated data radio bearer.

6. A client device according to claim 1 or 5, characterized by means for transmitting all data packets of said application specific data (301, 401) of an application session using said dedicated data radio bearer.

7. A client device according to claim 1, characterized by being configured to transmit said information related to said quality of service parameters (303, 403) in an uplink data status cell header.

8. A client device according to claim 1, characterized in that it is arranged to encode said information relating to said quality of service parameters (303, 403) into a bitmap (500) of quality of service flow identities.

9. The client device of claim 1, wherein the radio bearer setup request comprises a non-access stratum service request message or a tracking area update request message.

10. An access network device comprising a processor and memory to:

receiving a radio bearer establishment request from a client device (130);

receiving information related to the service quality parameters while receiving the radio bearer establishment request, wherein the radio bearer establishment request is a radio resource control connection request; and

establishing a default data radio bearer and a dedicated data radio bearer (307, 408) with the client device (130) as a response to the radio bearer establishment request;

wherein the dedicated data radio bearer comprises a quality of service flow conforming to at least one quality of service parameter received from the client device (130).

11. The access network apparatus of claim 10, characterized in that the information related to the quality of service parameters (303, 403) comprises a quality of service flow identification.

12. An access network arrangement according to claim 10 or 11, characterised by being arranged to receive said information relating to said quality of service parameters (303, 403) in an uplink data status cell header.

13. An access network arrangement as claimed in claim 10, characterised in that said information relating to quality of service parameters (303, 403) is encoded into a bitmap (500) of quality of service flow identities.

14. The access network device of claim 10, wherein the radio bearer setup request comprises a non-access stratum service request message or a tracking area update request message.

15. A method for a client device (130), comprising:

detecting (801) application specific data (301, 401) transmitted over a radio bearer;

detecting (802) at least one quality of service parameter related to the application specific data (301, 401);

-sending (803) information related to said quality of service parameters (303, 403) to the wireless network with a radio bearer setup request, said radio bearer setup request being a radio resource control connection request; and

-establishing (804) a default and dedicated data radio bearer (307, 408) as a response (804) to the information related to the quality of service parameters (303, 403) sent with the radio bearer establishment request.

16. A method for an access network device (120), comprising:

receiving (901) a radio bearer establishment request from a client device;

receiving (902) information related to quality of service parameters while receiving the radio bearer establishment request, the radio bearer establishment request being a radio resource control connection request; and

establishing (903) a default data radio bearer and a dedicated data radio bearer as a response to the radio bearer establishment request;

wherein the dedicated data radio bearer comprises a quality of service flow that conforms to at least one quality of service parameter received from the client device.