Network nodes and methods for handling quality of service parameters in a wireless communication network

Abstract

Methods and network nodes for handling quality of service (QoS) parameters in a wireless communication network (100) are provided A first network node receives (310) an indication indicating traffic flow direction applicability of the QoS 5 parameters from a second network node or a UE (130) and performs (320) certain actions based on the traffic flow direction applicability of the QoS parameters.

Description

[0001] NETWORK NODES AND METHODS FOR HANDLING QUALITY OF SERVICE

[0002] PARAMETERS IN A WIRELESS COMMUNICATION NETWORK

[0003] TECHNICAL FIELD

[0004] Embodiments herein relate to network nodes and methods therein. In particular, they relate to handling quality of services (QoS) parameters in a wireless communication network.

[0005] BACKGROUND

[0006] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, user equipments (UE) etc., communicate via a Radio Access Network (RAN) to one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a “NodeB” or “eNodeB” or “eNB” or “gNB”. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on radio frequencies with the wireless communication device within a range of the radio network node.

[0007] A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (4G) network or Long Term Evolution (LTE) have been completed within the 3rd Generation Partnership Project (3GPP) and this work continues in the coming 3GPP releases, for example to specify a Fifth Generation (5G) New Radio (NR) network, or Next Generation (NG) Radio Access Network (NG-RAN) and upcoming releases.

[0008] 3GPP is currently introducing standards support for Extended Reality (XR), including the addition of Packet Data Unit (PDU) Set Quality of Service (QoS) parameters information in the QoS profile. PDU Set QoS Parameters are defined in 3GPP TS 23.501 section 5.7.7.7, as parameters used to support PDU Set based QoS handling in the NG- RAN. At least one PDU Set QoS Parameter shall be sent to the NG-RAN to enable PDU Set based QoS handling. The following PDU Set QoS Parameters are specified:

[0009] 1) PDU Set Delay Budget (PSDB).

[0010] 2) PDU Set Error Rate (PSER).

[0011] 3) PDU Set Integrated Handling Information (PSI HI).

[0012] The Policy Control Function (PCF) determines the PDU Set QoS Parameters based on information provided by Application Function( AF) and / or local configuration. The PDU Set QoS parameters are sent to the Session Management Function (SMF) as part of Policy and Charging Control (PCC) rule. The SMF sends them to NG-RAN as part of the QoS Profile.

[0013] If the NG-RAN receives PDU Set QoS Parameters and supports them, it enables the PDU Set based QoS handling and applies PDU Set QoS Parameters as described in this clause.

[0014] In NG-RAN specification, the PDU Set QoS parameters have currently been defined as follows in NG Application Protocol (NGAP) baseline change Request (CR):

[0015] 9.3.1.x PDU Set QoS Parameters

[0016] This IE defines the PDU Set QoS Parameters to be applied to a QoS flow.

[0017] To support PDU Set based QoS handling, the PDU Session Anchor (PSA) User Plane Function (UPF) identifies PDUs that belong to PDU Sets and determines the below PDU Set Information which it sends to the NG-RAN in the GTP-U header, i.e. General Packet Radio Service Tunnelling Protocol User Plane (GTP-U). The PDU Set information is used by the NG-RAN for PDU Set based QoS handling as described above.

[0018] The PDU Set Information comprises:

[0019] - PDU Set Sequence Number.

[0020] - Indication of End PDU of the PDU Set.

[0021] - PDU Sequence Number within a PDU Set.

[0022] - PDU Set Size in bytes. - PDU Set Importance, which identifies the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow.

[0023] The NG-RAN may use the Priority Level, see clause 5.7.3.3 of TS 23.501 , across QoS Flows and PDU Set Importance within a QoS Flow for PDU Set level packet discarding in presence of congestion.

[0024] NOTE 1 : In addition to considering the PDU Set Importance within a QoS Flow, NG- RAN could also consider the relative PDU Set Importance across QoS Flows of the same Priority Level when determining which PDU Set needs to be discarded, which is up to implementation and configuration of operator.

[0025] NOTE 2: The PDU Set Information can be different for different PDU Sets within a QoS Flow.

[0026] The SMF instructs PSA UPF to perform PDU Set marking and may provide the PSA UPF the Protocol Description indicating the header, extension header e.g. Real-time Transport Protocol and Secure RTP (RTP / SRTP) and payload type e.g. H.264, used by the service data flow. The Protocol Description may be received in the PCC rule, based on information provided by the AF or by PCF local policies as described in clause 5.37.5.1 of TS 23.501.

[0027] PSA UPF can identify the PDU Set Information using the Protocol Description and the received RTP / SRTP headers or using implementation specific means. The details of the RTP / SRTP headers, header extensions and / or payloads used to identify PDU Set Information are defined in TS 26.522.

[0028] For each downlink (DL) PDU received on N6 interface for which PDU Set based QoS handling is indicated from the SMF, the PSA UPF applies the rules for PDU Set identification and provides PDU Set Information which is available to the RAN in the GTP- U header.

[0029] SUMMARY

[0030] As part of developing embodiments herein problems were identified and will first be discussed.

[0031] In 3GPP TS 23.501 , there is an Editor’s note stipulating that:

[0032] - the applicability and details of supporting PDU Set handling in uplink direction is an open question

[0033] Currently, the specification does not define separate restriction for PDU Set QoS parameters e.g., PSDB for uplink (UL) and downlink (DL) traffic, hence RAN cannot guess the direction UL and DL of the parameters. In fact, to be more precise, it is not clear whether NG-RAN should utilize some resource capacity to search for PDU set Information in the GTP-ll header for DL traffic or that some consideration is to be taken for the UE. In case the source of the ‘PDU Sets’ is from the UE, some indication is needed to let NG-RAN understand that it can configure access stratum specific functionality, e.g., UE discarding of outdated or less important PDU Sets, in the UE.

[0034] Embodiments herein provides methods for signalling the applicability of PDU Set QoS parameters in the uplink direction.

[0035] NG-RAN is aware whether the PDU Set Info comes in DL or related functionality can be configured in UL, e.g., in the UE, or in both.

[0036] According to embodiments herein, several options for indicating the traffic flow e.g., uplink direction, applicability of the PDU Set QoS parameters signalled in NG-RAN, including all interfaces, e.g. NGAP, XnAP, F1AP, and E1AP, are described: a) A new indication indicating which flow direction, e.g. uplink or downlink, for the signaled PDU Set QoS parameters their usage applicable for. b) Including a new indication for each of the PSDB uplink and PSER uplink. c) Defining a new PDU Set QoS parameters for uplink. d) Redefining the “QoS Flow Level QoS Parameters IE” to include two “PDU Set QoS Parameters” lEs, one for downlink and another for uplink.

[0037] According to one aspect of the embodiments herein, the object is achieved by a first network node and method therein for handling quality of service (QoS) parameters in a wireless communication network. The first network node receives an indication indicating traffic flow direction applicability of the QoS parameters from a second network node or a User Equipment (UE), and performs certain actions based on the traffic flow direction applicability of the QoS parameters.

[0038] According to one aspect of the embodiments herein, the object is achieved by a second network node and method therein for handling quality of service (QoS) parameters in a wireless communication network. The second network node sends an indication indicating traffic flow direction applicability of the QoS parameters to a first network node. According to one aspect of the embodiments herein, the object is achieved by a UE and method therein for handling quality of service (QoS) parameters in a wireless communication network. The UE sends an indication indicating traffic flow direction applicability of the QoS parameters to a first network node.

[0039] Embodiments herein ensure that NG-RAN is aware of the uplink PDU Set QoS parameters, which it can use for scheduling UL resources when different UL grants are being allocated for the UE.

[0040] Embodiments herein ensure that NG-RAN can differentiate the cases where PDU Set Information is to be searched for in the DL NG-U traffic and or whether PDU Set Information will be available in the UE on the UL and therefore the necessary UE configuration can be enabled.

[0041] BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0043] Figure 1 is a schematic block diagram illustrating a wireless communication network; Figure 2(a) and 2(b) are signal flow charts illustrating example signal flow between a first and second network nodes, and between a first network node and UE according to embodiments herein;

[0044] Figure 3 is a flow chart illustrating an example embodiment of a method performed in a first network node according to embodiments herein;

[0045] Figure 4 is a flow chart illustrating an example embodiment of a method performed in a second network node according to embodiments herein;

[0046] Figure 5 is a flow chart illustrating an example embodiment of a method performed in a UE according to embodiments herein;

[0047] Figure 6 is a schematic block diagram illustrating an example embodiment of a network node;

[0048] Figure 7 is a schematic block diagram illustrating an example embodiment of a UE; Figure 8 schematically illustrates a telecommunication network connected via an intermediate network to a host computer; Figure 9 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection; and

[0049] Figures 10-13 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.

[0050] DETAILED DESCRIPTION

[0051] Embodiments herein relate to communication networks in general. Figure 1 is a schematic overview depicting a communication network 100. The communication network 100 may be a wireless communication network comprising one or more RANs, and one or more CNs. The communication network 100 may use a number of different RATs, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, NR, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), NR etc. just to mention a few possible implementations.

[0052] In the wireless communication network 100, one or more wireless communication devices 130, 131 such as a UE, a mobile station or a wireless terminal communicates via one or more Radio Access Networks (RAN) to one or more core networks (CN). It should be understood by the skilled in the art that “wireless communication device” is a nonlimiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

[0053] Network nodes operate in the wireless communication network 100 such as a first network node 111, a second network node 112. The first and second network nodes 111, 112 may be any of RAN node, such as gNB, eNB, en-gNB, ng-eNB, gNB etc. The first network node 111 provides radio coverage over a geographical area, a service area 11 , which may also be referred to as a beam or a beam group where the group of beams is covering the service area of a first radio access technology (RAT), such as 5G, LTE, Wi-Fi or similar. The second network node 112 provides radio coverage over a geographical area, a service area 12, which may also be referred to as a beam or a beam group where the group of beams is covering the service area of a second radio access technology (RAT), such as 5G, LTE, Wi-Fi or similar. It should be noted that a network node may be a RAN node, a CN node or an GAM node. The first / second network nodes 111 / 112 may be a transmission and reception point e.g. a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, a gNB, an evolved Node B (eNB, eNode B), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of communicating with a wireless communication device within the service area served by the respective first / second network nodes 111 / 112 depending e.g. on the radio access technology and terminology used. The first and the second network nodes 111 / 112 may be referred to as a source and a target network node, respectively, and may communicate with the wireless communication device 130, 131 with Downlink (DL) transmissions to the wireless communication device 130, 131 and Uplink (UL) transmissions from the wireless communication device 130, 131.

[0054] A network node may be a RAN node, a gNB, an eNB, an en-gNB, a ng-eNB, a gNB-CU, a gNB-DU, a gNB-CU-CP, a gNB-CU-UP, an eNB-CU, an eNB-CU-CP, an eNB- CU-UP, an lAB-node, an lAB-donor DU, an lAB-donor-CU, an IAB-DU, an IAB-MT, an O- CU, an O-CU-CP, an O-CU-UP, an O-DU, an O-RU, an O-eNB, a Non-Real Time RAN Intelligent Controller (Non-RT RIC), a Real-Time RAN Intelligent Controller (RT-RIC), an CAM node, a Core Network node / function, a Cloud-based network function, a Cloudbased centralized training node etc.

[0055] According to some embodiments herein, new information about the PDU Set Delay Budget Uplink IE and PDU Set Error Rate Uplink IE are included in the PDU Set QoS parameters in NGAP. Without loss of generality, an example is provided below with new inclusions in underlined text:

[0056] 9.3.1.x PDU Set QoS Parameters

[0057] This IE defines the PDU Set QoS Parameters to be applied to a QoS flow.

[0058]

[0059] According to some embodiments herein, the PDU Set Delay Budget Uplink IE and PDU Set Error Rate Uplink IE are included in the PDU Set QoS parameters IE in XnAP, F1AP and E1AP specifications. According to some embodiments herein, a new IE about traffic flow direction, uplink or downlink, is included in the PDU Set QoS parameters IE in NGAP / F1AP / E1AP / XnAP. Without loss of generality, an example is provided below with new inclusions in underlined text.

[0060] 9.3.1.x PDU Set QoS Parameters This IE defines the PDU Set QoS Parameters to be applied to a QoS flow.

[0061] According to some embodiments herein, two separate lEs, one for PDU Set Parameters Downlink, another for PDU Set Parameters Uplink are introduced at high level. When at least one of the two PDU Set Parameter lEs is present, then PDU Set information is present. Refer to the below table. Underlined text are the changes. Note, the PDU Set QOS parameter IE does not need to contain an Flow Direction indicator in this case.

[0062] TS 38.413, Chapter 9.3.1.12 QoS Flow Level QoS Parameters. This IE defines the QoS parameters to be applied to a QoS flow.

[0063]

[0064] 9.3.1.x PDU Set QoS Parameters

[0065] This IE defines the PDU Set QoS Parameters to be applied to a QoS flow in UL, DL or 5 both.

[0066] According to some embodiments herein, upon receiving the indication that there will be PDU Set info on the UL in the UE, the NG-RAN can configure the UE, e.g., to drop PDU Sets packets when some timer is exceeded. This may be based on the uplink value of PSDB.

[0067] Figure 2(a) shows a signal flow chart illustrating an example signal flow between the first and second network nodes 111 / 112, and Figure 2(b) shows a signal flow chart illustrating an example signal flow between the first network node 111 and UE 130 according to embodiments herein.

[0068] The first network node 111 receives an indication indicating traffic flow direction applicability of the QoS parameters from a second network node in signal flow 20a or from a UE,e.g. UE 130 in signal flow 20b.

[0069] According to embodiments described above, a method performed by a first network node 111 for handling quality of service (QoS) parameters in a wireless communication network 100 will be described with reference to Figure 3. The method comprises one or more of the following actions which may be performed in any suitable order.

[0070] Action 310

[0071] The first network node 111 receives an indication indicating traffic flow direction applicability of the QoS parameters from a second network node 112 or from a UE 130.

[0072] According to some embodiments herein, the QoS parameters may be a Packet Data Unit Set Quality of Service (DU Set QoS) parameters.

[0073] According to some embodiments herein, the indication may be a new Information Element (IE) indicating which traffic flow direction, downlink, or uplink, or both downlink and uplink, is applicable for signalled QoS parameters. The new IE may be included in lEs of PDU Set QoS parameters.

[0074] According to some embodiments herein, the indication may be included in Information Element (IE) of PDU Set QoS parameters. One IE for PDU Set Delay Budget (PSDB) uplink indicting the PSDB parameter is applicable for uplink and one IE for PDU Set Error Rate (PSER) uplink indicting the PSER parameter is applicable for uplink.

[0075] According to some embodiments herein the indication may be a modified existing IE of PDU Set QoS parameters, where one IE of PDU Set Packet Delay Budget is modified to PDU Set Packet Delay Budget downlink for indicating the PSDB parameter is applicable for downlink, one IE of PDU Set Error Rate is modified to PDU Set Error Rate downlink for indicting the PSER parameter is applicable for downlink.

[0076] According to some embodiments herein, the indication may be a new PDU Set QoS parameter for uplink.

[0077] According to some embodiments herein, the indication may be included in QoS Flow Level QoS Parameters Information Element (IE), where one IE is PDU Set QoS Parameters downlink for indicating the PDU Set QoS parameter is applicable for downlink and one IE is PDU Set QoS Parameters uplink for indicating the PDU Set QoS parameter is applicable for uplink.

[0078] According to some embodiments herein, the indication may be included in NGAP, XnAP, F1AP and E1AP and sent via NG, or E1, or F1 , or Xn interfaces.

[0079] According to some embodiments herein, the first and second network nodes may be any one of an NG-RAN network node, a gNB, an eNB, an en-gNB, a ng-eNB, a gNB-CU, a gNB-DU, a gNB-CU-CP, a gNB-CU-UP, an eNB-CU, an eNB-CU-CP, an eNB-CU-UP, an lAB-node, an lAB-donor DU, an lAB-donor-CU, an IAB-DU, an IAB-MT, an O-CU, an O-CU-CP, an O-CU-UP, an O-DU, an O-RU, an O-eNB, a Non-Real Time RAN Intelligent Controller (Non-RT RIC), a Real-Time RAN Intelligent Controller (RT-RIC), an QAM node, a Core Network node / function, a Cloud-based network function, a Cloud-based centralized training node.

[0080] Action 320

[0081] The first network node 111 performs certain actions based on the traffic flow direction applicability of the QoS parameters.

[0082] According to some embodiments herein, performing certain actions based on the traffic flow direction applicability of the QoS parameters may comprise any one or a combination of: scheduling UL resources; configuring UE with related functionality in uplink and / or downlink. According to embodiments described above, a method performed by a second network node 112 for handling quality of service (QoS) parameters in a wireless communication network 100 will be described with reference to Figure 4. The method comprises one or more of the following actions which may be performed in any suitable order.

[0083] Action 410

[0084] The second network node 112 sends an indication indicating traffic flow direction applicability of the QoS parameters to a first network node 111.

[0085] According to embodiments described above, a method performed by a UE 130 for handling quality of service (QoS) parameters in a wireless communication network 100 will be described with reference to Figure 5. The method comprises the following actions which may be performed in any suitable order.

[0086] Action 510

[0087] The UE 130 sends an indication indicating traffic flow direction applicability of the QoS parameters to a first network node 110.

[0088] To perform the methods in the first / second network nodes 111 / 112, the first / second network nodes 111 / 112 comprises modules as shown in Figure 6. The first / second network nodes 111 / 112 comprises a receiving module 610, a transmitting module 620, a determining module 630, a processing module 640, a memory 650 etc.

[0089] The first network node 111 is configured to perform any one of the Actions 310-320 described above.

[0090] For example, the first network node 111 is configured to, by means of e.g. the receiving module 610 being configured to, receive an indication indicating traffic flow direction applicability of the QoS parameters from a second network node 112 or a UE 130.

[0091] The first network node 111 is configured to, by means of e.g. the processing module 640 being configured to, perform certain actions based on the traffic flow direction applicability of the QoS parameters, such as scheduling UL resources for the UE 130, configuring the UE 130 with related functionality in uplink and / or downlink.

[0092] The second network node 112 is configured to perform the Action 410 described above. The second network node 112 is configured to, by means of e.g. the transmitting module 620, send an indication indicating traffic flow direction applicability of the QoS parameters to a first network node 111.

[0093] The methods according to embodiments herein may be implemented through one or more processors, such as the processor 660 in the first / second network nodes 111 / 112 together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of computer readable medium or a data carrier 680 carrying computer program code 670, as shown in Figure 6, for performing the embodiments herein when being loaded into the first / second network nodes 111 / 112. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server or a cloud and downloaded to the first / second network nodes 111 / 112.

[0094] To perform the methods in the UE 130, the UE 130 comprises modules as shown in Figure 7. The UE 130 comprises a receiving module 710, a transmitting module 720, a determining module 730, a processing module 740, a memory 750 etc.

[0095] The UE 130 is configured to perform the Action 510 described above.

[0096] For example, the UE 130 is configured to, be means of e.g. the transmitting module 730 being configured to, send an indication indicating traffic flow direction applicability of the QoS parameters to a first network node 111.The methods according to embodiments herein may be implemented through one or more processors, such as the processor 760 in the UE 130 together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of computer readable medium or a data carrier 780 carrying computer program code 770, as shown in Figure 7, for performing the embodiments herein when being loaded into the UE 130. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server or a cloud and downloaded to the UE 130.

[0097] With reference to Figure 8, in accordance with an embodiment, a communication system includes a telecommunication network 3210, such as a 3GPP- type cellular network, which comprises an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points being examples of the radio network node 12 herein, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215. A first user equipment (UE) 3291 , being an example of the UE 230, located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c. A second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291 , 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.

[0098] The telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220. The intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub-networks (not shown).

[0099] The communication system of Figure 8 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230. The connectivity may be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291 , 3292 are configured to communicate data and / or signaling via the OTT connection 3250, using the access network 3211 , the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries. The OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications. For example, a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.

[0100] Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 9. In a communication system 3300, a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300. The host computer 3310 further comprises processing circuitry 3318, which may have storage and / or processing capabilities. In particular, the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The host computer 3310 further comprises software 3311 , which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318. The software 3311 includes a host application 3312. The host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.

[0101] The communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330. The hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Figure 9) served by the base station 3320. The communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 may be direct or it may pass through a core network (not shown in Figure 9) of the telecommunication system and / or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station 3320 further has software 3321 stored internally or accessible via an external connection.

[0102] The communication system 3300 further includes the UE 3330 already referred to. Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located. The hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 3330 further comprises software 3331 , which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338. The software 3331 includes a client application 3332. The client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310. In the host computer 3310, an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the user, the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 may transfer both the request data and the user data. The client application 3332 may interact with the user to generate the user data that it provides.

[0103] It is noted that the host computer 3310, base station 3320 and UE 3330 illustrated in Figure 9 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 of Figure 9, respectively. This is to say, the inner workings of these entities may be as shown in Figure 9 and independently, the surrounding network topology may be that of Figure 9.

[0104] In Figure 9, the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 3350 between the host computer 3310 and UE 3330, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both.

[0105] It is noted that the host computer 3310, base station 3320 and UE 3330 illustrated in Figure 9 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 of Figure 9, respectively. This is to say, the inner workings of these entities may be as shown in Figure 9 and independently, the surrounding network topology may be that of Figure 9.

[0106] In Figure 9, the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the user equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0107] The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may achieve an efficient RACH process and thereby provide benefits such as improved battery time, and better responsiveness.

[0108] The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may achieve an efficient QoE reporting and thereby provide benefits such as improved UE experience, and better responsiveness. A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 3350 between the host computer 3310 and UE 3330, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signalling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.

[0109] Figure 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 9 will be included in this section. In a first step 3410 of the method, the host computer provides user data. In an optional substep 3411 of the first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission carrying the user data to the UE. In an optional third step 3430, the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer. Figure 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 10 will be included in this section. In a first step 3510 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In a second step 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step 3530, the UE receives the user data carried in the transmission.

[0110] Figure 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 11 will be included in this section. In an optional first step 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 3620, the UE provides user data. In an optional substep 3621 of the second step 3620, the UE provides the user data by executing a client application. In a further optional substep 3611 of the first step 3610, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in an optional third substep 3630, transmission of the user data to the host computer. In a fourth step 3640 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0111] Figure 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 8 and 9. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section. In an optional first step 3710 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In an optional second step 3720, the base station initiates transmission of the received user data to the host computer. In a third step 3730, the host computer receives the user data carried in the transmission initiated by the base station.

[0112] As used herein, the term “processing module” may refer to a processing circuit, a processing unit, a processor, an Application Specific integrated Circuit (ASIC), a Field- Programmable Gate Array (FPGA) or the like. As an example, a processor, an ASIC, an FPGA or the like may comprise one or more processor kernels. In some examples, the processing module may be embodied by a software module or hardware module. Any such module may be a determining means, estimating means, capturing means, associating means, comparing means, identification means, selecting means, receiving means, transmitting means or the like as disclosed herein. As an example, the expression “means” may be a module, such as a determining module, selecting module, etc.

[0113] As used herein, the expression “configured to” may mean that a processing circuit is configured to, or adapted to, by means of software configuration and / or hardware configuration, perform one or more of the actions described herein.

[0114] As used herein, the term “memory” may refer to a hard disk, a magnetic storage medium, a portable computer diskette or disc, flash memory, random access memory (RAM) or the like. Furthermore, the term “memory” may refer to an internal register memory of a processor or the like.

[0115] As used herein, the term “computer readable medium” may be a Universal Serial Bus (USB) memory, a DVD-disc, a Blu-ray disc, a software module that is received as a stream of data, a Flash memory, a hard drive, a memory card, such as a Memory Stick, a Multimedia Card (MMC), etc.

[0116] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings.

[0117] Some example embodiments are listed in the following:

[0118] Embodiment 1 : A method performed in a first network node 110 for handling quality of service, QoS, parameters in a wireless communication network, the method comprising: receiving (310) an indication indicating traffic flow direction applicability of the QoS parameters from a second network node 112 or a User Equipment, UE 130; performing (320) certain actions based on the traffic flow direction applicability of the QoS parameters.

[0119] Embodiment 2: A method performed in a second network node (112) for handling quality of service, QoS, parameters in a wireless communication network, the method comprising: sending (410) an indication indicating traffic flow direction applicability of the QoS parameters to a first network node (111).

[0120] Embodiment 3: A method performed in a User Equipment, UE, for handling quality of service, QoS, parameters in a wireless communication network, the method comprising: sending (510) an indication indicating traffic flow direction applicability of the QoS parameters to a first network node (111).

[0121] Embodiment 4: The method according to any one of Embodiments 1-3, wherein the QoS parameters is a Packet Data Unit Set Quality of Service, PDU Set QoS, parameters.

[0122] Embodiment 5: The method according to Embodiment 4, wherein the indication is a new Information Element, IE, indicating which traffic flow direction, downlink, or uplink, or both downlink and uplink, is applicable for signaled QoS parameters, and the new IE is included in lEs of PDU Set QoS parameters.

[0123] Embodiment 6: The method according to Embodiment 4, wherein the indication is included in Information Element, IE, of PDU Set QoS parameters, and where one IE for PDU Set Delay Budget, PSDB, uplink indicating the PSDB parameter is applicable for uplink and one IE for PDU Set Error Rate, PSER, uplink indicting the PSER parameter is applicable for uplink.

[0124] Embodiment 7: The method according to Embodiment 4, wherein the indication is a modified existing IE of PDU Set QoS parameters, where one IE of PDU Set Packet Delay Budget is modified to PDU Set Packet Delay Budget downlink for indicating the PSDB parameter is applicable for downlink, one IE of PDU Set Error Rate is modified to PDU Set Error Rate downlink for indicting the PSER parameter is applicable for downlink.

[0125] Embodiment 8: The method according to Embodiment 4, wherein the indication is a new PDU Set QoS parameter for uplink.

[0126] Embodiment 9: The method according to Embodiments 4, wherein the indication is included in QoS Flow Level QoS Parameters Information Element, IE, where one IE is PDU Set QoS Parameters downlink for indicating the PDU Set QoS parameter is applicable for downlink and one IE is PDU Set QoS Parameters uplink for indicating the PDU Set QoS parameter is applicable for uplink.

[0127] Embodiment 10: The method according to Embodiments 4, wherein the indication is an IE defines the PDU Set QoS Parameters to be applied to a QoS flow in UL, DL or both.

[0128] Embodiment 11 : The method according to any one of Embodiments 1-10, wherein the indication is included in NGAP, XnAP, F1 AP and E1AP and sent via NG, or E1 , or F1 , or Xn interfaces.

[0129] Embodiment 12: The method according to Embodiment 2, wherein performing (S02) certain actions based on the traffic flow direction applicability of the QoS parameters comprises any one or a combination of: scheduling UL resources; configuring UE with related functionality in uplink and / or downlink.

[0130] Embodiment 13: The method according to any one of Embodiments 1-11, wherein the first network node 111 and the second network node 112 is any one of a gNB, an eNB, an en-gNB, a ng-eNB, a gNB-CU, a gNB-DU, a gNB-CU-CP, a gNB-CU-UP, an eNB-CU, an eNB-CU-CP, an eNB-CU-UP, an lAB-node, an lAB-donor DU, an IAB- donor-CU, an IAB-DU, an IAB-MT, an O-CU, an O-CU-CP, an O-CU-UP, an O-DU, an O-RU, an O-eNB, a Non-Real Time RAN Intelligent Controller (Non-RT RIC), a Real- Time RAN Intelligent Controller (RT-RIC), an QAM node, a Core Network node / function, a Cloud-based network function, a Cloud-based centralized training node.

Claims

Claims1. A method performed in a first network node (111) for handling quality of service, QoS, parameters in a wireless communication network (100), the method comprising: receiving (310) an indication indicating traffic flow direction applicability of the QoS parameters from a second network node (112) or a User Equipment, UE (130); performing (320) certain actions based on the traffic flow direction applicability of the QoS parameters.

2. The method according to claim 1 , wherein performing (320) certain actions based on the traffic flow direction applicability of the QoS parameters comprises any one or a combination of: scheduling (321) UL resources for the UE(130); configuring (322) the UE (130) with related functionality in uplink and / or downlink.

3. A method performed in a second network node (112) for handling quality of service, QoS, parameters in a wireless communication network (100), the method comprising: sending (410) an indication indicating traffic flow direction applicability of the QoS parameters to a first network node (111).

4. A method performed in a User Equipment, UE (130), for handling quality of service, QoS, parameters in a wireless communication network (100), the method comprising: sending (510) an indication indicating traffic flow direction applicability of the QoS parameters to a first network node (111).

5. The method according to any one of claims 1-4, wherein the QoS parameters is a Packet Data Unit Set Quality of Service, PDU Set QoS, parameters.

6. The method according to claim 5, wherein the indication is a new Information Element, IE, indicating which traffic flow direction, downlink, or uplink, or bothdownlink and uplink, is applicable for signaled QoS parameters, and the new IE is included in lEs of PDU Set QoS parameters.

7. The method according to claim 5, wherein the indication is included in Information Element, IE, of PDU Set QoS parameters, and where one IE for PDU Set Delay Budget, PSDB, uplink indicating the PSDB parameter is applicable for uplink and one IE for PDU Set Error Rate, PSER, uplink indicting the PSER parameter is applicable for uplink.

8. The method according to claim 5, wherein the indication is a modified existing IE of PDU Set QoS parameters, where one IE of PDU Set Packet Delay Budget is modified to PDU Set Packet Delay Budget downlink for indicating the PSDB parameter is applicable for downlink, one IE of PDU Set Error Rate is modified to PDU Set Error Rate downlink for indicting the PSER parameter is applicable for downlink.

9. The method according to claim 5, wherein the indication is a new PDU Set QoS parameter for uplink.

10. The method according to claims 5, wherein the indication is included in QoS Flow Level QoS Parameters Information Element, IE, where one IE is PDU Set QoS Parameters downlink for indicating the PDU Set QoS parameter is applicable for downlink and one IE is PDU Set QoS Parameters uplink for indicating the PDU Set QoS parameter is applicable for uplink.

11. The method according to claims 5, wherein the indication is an IE defines the PDU Set QoS Parameters to be applied to a QoS flow in UL, DL or both.

12. The method according to any one of claims 1-11, wherein the indication is included in NGAP, XnAP, F1 AP and E1AP and sent over NG, Xn, F1 , E1 interfaces respectively.

13. The method according to any one of claims 1-12, wherein the first network node (111) and the second network node (112) is any one of a gNB, an eNB, an en- gNB, a ng-eNB, a gNB-CU, a gNB-DU, a gNB-CU-CP, a gNB-CU-UP, an eNB-CU, an eNB-CU-CP, an eNB-CU-UP, an lAB-node, an lAB-donor DU, an lAB-donor-CU, an IAB-DU, an IAB-MT, an O-CU, an O-CU-CP, an O-CU-UP, an O-DU, an O-RU, an O-eNB, a Non-Real Time RAN Intelligent Controller (Non-RT RIC), a Real-Time RAN Intelligent Controller (RT-RIC), an CAM node, a Core Network node / function, a Cloud-based network function, a Cloud-based centralized training node.

14. A first network node (111) for handling quality of service, QoS, parameters in a wireless communication network (100), the first network node (111) is configured to: receive an indication indicating traffic flow direction applicability of the QoS parameters from a second network node (112) or a User Equipment, UE (130); perform certain actions based on the traffic flow direction applicability of the QoS parameters.

15. A second network node (112) for handling quality of service, QoS, parameters in a wireless communication network (100), the second network node (112) is configured to: send an indication indicating traffic flow direction applicability of the QoS parameters to a first network node (111).

16. A User Equipment, UE (130), for handling quality of service, QoS, parameters in a wireless communication network (100), the UE (130) is configured to: send an indication indicating traffic flow direction applicability of the QoS parameters to a first network node (111).

Images