BR112020022033B1 - METHOD ON A NETWORK FUNCTION ENTITY, METHOD ON A USER EQUIPMENT TO RECEIVE PARAMETERS, NETWORK FUNCTION ENTITY, USER EQUIPMENT AND COMPUTER READABLE STORAGE MEDIA - Google Patents

Abstract

QOS FLOW CONTROL PARAMETER SIGNALING. The present invention provides methods for signaling QoS Flow control parameters and corresponding NF entities. The method comprises generating one or more data flow rules associated with a QoS Flow and a QoS Flow profile. The data flow rules include specific parameters for a data flow belonging to the QoS Flow, while the QoS Flow profile includes parameters that are common to all data streams belonging to the same QoS Flow. The present invention further discloses a corresponding method of receiving the QoS Flow control parameters. The present invention further provides means corresponding computer readable.

Description

TECHNICAL FIELD

[001] The present invention generally relates to the telecommunications technical field, and particularly to methods, Network Function (NF) entities, User Equipment (UEs) for signaling Quality of Service (QoS) Flow control parameters ) and corresponding readable media.

BACKGROUND

[002] This section is intended to provide an overview of the various embodiments of the technology described in this invention. The description in this section may include concepts that may be pursued, but are not necessarily those that have been previously conceived or pursued. Therefore, unless otherwise indicated in the present invention, what is described in this section is not prior art to the description and/or claims of this invention and is not admitted as prior art by mere inclusion in this section.

[003] In 5-generation (5G) networks, a Network Slice is presented as a logical network that provides specific network capabilities and network characteristics. An instance of a network slice (e.g., a network slice instance (NSI) is a set of Network Function (NF) instances and the required resources (e.g., compute, storage, and network resources) that form a deployed Network Slice. An NF is a processing function adopted from 3GPP or defined from 3GPP in a network, which has defined functional behavior and defined interfaces from 3GPP. An NF can be implemented as a network element on dedicated hardware, a software instance running on dedicated hardware or as a virtualized function instantiated on an appropriate platform, for example in a cloud infrastructure.

[004] 3GPP 5GS also defines a Quality of Service (QoS) Flow. A QoS Flow is the finest granularity for handling QoS forwarding in the 5G system. All traffic mapped to the same 5G QoS Stream receives the same forwarding treatment (e.g. scheduling policy, queue management policy, rate shaping policy, RLC configuration, etc.). Providing different QoS forwarding treatment requires separate 5G QoS Flow.

SUMMARY

[005] The present application relates to how to signal QoS Flow control parameters in a 5G or future developed system.

[006] According to a first aspect of the present invention, a method in a network node for signaling Quality of Service (QoS) Flow control parameters to a User Equipment, UE, is provided. The method comprises generating one or more data flow rules associated with a QoS Flow, wherein each of the one or more data flow rules comprises specific parameters for a data flow belonging to the QoS Flow. The method comprises further generating a QoS Flow profile for the UE for the QoS Flow, wherein the QoS flow profile comprises parameters that are common to all data flows belonging to the same QoS Flow. The method also comprises transmitting the one or more data flow rules and the QoS Flow profile for the UE.

[007] In an exemplary embodiment, each of the one or more data flow rules is represented by an identifier that is distinguished from one another that is transmitted to the UE.

[008] In an exemplary embodiment, each of the one or more data flow rules comprises parameters that are related to one or more Service Data Flow (SDF) models and/or one or more associated precedence values.

[009] In an exemplary embodiment, each of the one or more data flow rules and the QoS Flow profile comprises a QoS Flow identifier.

[010] In an exemplary embodiment, the method may further comprise transmitting the one or more data flow rules to the UE to inform the UE to add the one or more data flow rules to the QoS flow.

[011] In an exemplary embodiment, the method may further comprise transmitting a parameter to the UE if the parameter in the QoS Flow profile changes from that in the previous QoS Flow profile, to allow the UE to update the parameter in the Flow profile from QoS to the QoS Flow.

[012] In an exemplary embodiment, the method may further comprise transmitting an identifier of a data flow rule to the UE, to inform the UE to delete the data flow rule identified by the identifier.

[013] In an exemplary embodiment, the method may further comprise transmitting a QoS Flow identifier to the UE if a data flow rule to be removed is the last of the QoS Flow, to inform the UE to delete the QoS Flow profile QoS Flow for QoS Flow and the last data flow rule.

[014] According to a second aspect of the present invention, a method is provided for a User Equipment (UE) to receive parameter. The method comprises receiving one or more data flow rules associated with a Quality of Service (QoS) Flow, wherein each of the one or more data flow rules comprises specific parameters for a data flow belonging to that Quality of Service (QoS) Flow. QoS. The method further comprises receiving a QoS Stream profile for the QoS Stream, wherein the QoS stream profile comprises parameters that are common to all data streams belonging to the same QoS Stream.

[015] In an exemplary embodiment, the method may further comprise receiving an identifier from a data flow rule and deleting the data flow rule.

[016] In an exemplary embodiment, the method may additionally comprise receiving a data flow rule only.

[017] In an exemplary embodiment, the method may further comprise receiving an identifier of a QoS Flow and deleting the data flow rule and the QoS Flow profile associated with the QoS Flow.

[018] In an exemplary embodiment, the method may further comprise receiving a parameter and updating the parameter in the QoS Flow profile with the received parameter.

[019] According to a third aspect of the present invention, a method in a network node for signaling a Quality of Service (QoS) rule to a User Equipment (UE) is provided. The method comprises generating a QoS rule associated with a QoS Flow, wherein the QoS rule comprises parameters common to all data flows belonging to the same QoS Flow, and one or more sets of parameters, wherein each of the one or more parameter sets comprise parameters that are specific to a data stream belonging to the QoS Stream. The method then comprises transmitting the QoS rule to the UE.

[020] In an exemplary embodiment, each of the one or more sets of parameters is distinguished from one another by an identifier that is included in the one or more sets of parameters.

[021] In an exemplary embodiment, each of the one or more parameter sets comprises parameters that are related to one or more Service Data Flow (SDF) models and/or one or more associated precedence values.

[022] In an exemplary embodiment, the method may further comprise transmitting the parameter set along with a QoS rule identifier to the UE if the QoS rule has already been transmitted, to allow the UE to update the QoS rule to include the parameter set.

[023] In an exemplary embodiment, the method may further comprise transmitting one or more of the common parameters together with a QoS rule identifier to the UE, to allow the UE to update corresponding parameter in the QoS rule with the one or more parameters received.

[024] In an exemplary embodiment, the method may further comprise transmitting a parameter set identifier together with a QoS rule identifier to the UE, to allow the UE to update the QoS rule by deleting the parameter set of the QoS rule. QoS.

[025] In an exemplary embodiment, the method may further comprise transmitting a QoS Flow identifier to the UE if a set of parameters to be removed is the last of the QoS rule, to inform the UE to delete the QoS rule for o QoS Flow.

[026] In an exemplary embodiment, the method may further comprise transmitting a parameter and an identifier of a parameter set to which the parameter belongs along with an identifier of the QoS rule to the UE, to allow the UE to update the QoS rule updating the parameter in the parameter set.

[027] According to a fourth aspect of the present invention, a method in a User Equipment (UE) for receiving a Quality of Service (QoS) rule is provided. The method comprises receiving a QoS rule associated with a QoS Flow, wherein the QoS rule comprises parameters common to all data flows belonging to the same QoS Flow and one or more sets of parameters, wherein each of the one or more parameter sets comprise parameters that are specific to a data stream belonging to the QoS Stream.

[028] In an exemplary embodiment, the method may further comprise receiving the set of parameters together with a QoS rule identifier and updating the QoS rule to include the set of parameters.

[029] In an exemplary embodiment, the method may further comprise receiving a parameter set identifier along with a QoS rule identifier and updating the QoS rule by deleting the parameter set from the QoS rule.

[030] In an exemplary embodiment, the method may further comprise receiving one or more of the common parameters together with a QoS rule identifier and updating the corresponding parameter in the QoS rule with the received parameter.

[031] In an exemplary embodiment, the method may further comprise receiving a parameter and an identifier from a parameter set to which the parameter belongs together with a QoS rule identifier and updating the QoS rule by updating the parameter in the parameter set .

[032] According to a fifth aspect of the present invention, an NF entity is provided, comprising: at least one processor and a memory comprising instructions that, when executed by at least one processor, cause the NF entity to operate in a in accordance with the first and third aspects of the present invention.

[033] According to a sixth aspect of the present invention, a UE is provided, comprising: at least one processor and a memory comprising instructions which, when executed by at least one processor, cause the UE to operate in accordance with the second and fourth aspect of the present invention.

[034] According to a seventh aspect of the present invention, an NF entity is provided, comprising: a generation module configured to generate one or more data flow rules associated with a QoS Flow, wherein each of the or more data flow rules comprise parameters specific to a data flow belonging to the QoS Flow and the generation module further configured to generate a QoS Flow profile for the UE for the QoS Flow, wherein the QoS Flow comprises parameters that are common to all data flows that belong to the same QoS Flow; and a transmission module configured to transmit the one or more data flow rules and the QoS Flow profile to the UE.

[035] According to an eighth aspect of the present invention, a UE is provided, comprising: a receiving module configured to receive one or more data flow rules associated with a Quality of Service (QoS) Flow, each one of the one or more data flow rules comprises specific parameters for a data flow belonging to that QoS Flow; and the receiving module further configured to receive a QoS Stream profile for the QoS Stream, wherein the QoS Stream profile comprises parameters that are common to all data streams belonging to the same QoS Stream.

[036] According to a ninth aspect of the present invention, an NF entity is provided, comprising: a generation module configured to generate a QoS rule associated with a QoS Flow, wherein the QoS rule comprises parameters common to all data streams belonging to the same QoS Flow and one or more sets of parameters, each of the one or more sets of parameters comprising parameters that are specific to a data stream belonging to the QoS Flow; and a transmission module configured to transmit the QoS rule to the UE.

[037] According to a tenth aspect of the present invention, a UE is provided, comprising: a receiving module configured to receive a QoS rule associated with a QoS Flow, wherein the QoS rule comprises parameters common to all data streams belonging to the same QoS Stream and one or more parameter sets, wherein each of the one or more parameter sets comprises parameters that are specific to a data stream belonging to the QoS Stream.

[038] According to another aspect of the present invention, a computer-readable medium that stores a computer program comprising instructions that, when executed on at least one processor of a device, cause the device to perform the methods in accordance with the first, second, third and fourth aspects as discussed previously.

[039] According to the above technical solutions of the present invention, common parameters will be transmitted only once, thus the signaling efficiency is improved.

BRIEF DESCRIPTION OF THE DRAWINGS

[040] The objects, advantages and characteristics of the present invention will be more apparent, according to the descriptions of preferred embodiments in connection with the drawings, in which: Figure 1 illustrates an example of a wireless communications system in which embodiments of the present invention can be implemented; Figure 2 illustrates a wireless communication system represented as a 5G network architecture composed of core NFs; Figure 3 illustrates a 5G network architecture using service-based interfaces between NFs in the control plane, rather than the point/point-to-point reference interfaces used in the 5G network architecture of Figure 2; Figure 4 shows an exemplary signaling diagram illustrating the details of a method for signaling QoS Flow control parameters and/or a QoS rule; Figure 5 illustratively shows a flowchart of a method for signaling parameters for a UE in accordance with an exemplary embodiment of the present invention; Figure 6 illustratively shows a flowchart of a method for deleting a data flow rule in accordance with an exemplary embodiment of the present invention; Figure 7 illustratively shows a flowchart of a method for receiving parameters in accordance with an exemplary embodiment of the present invention; Figure 8 illustratively shows a flowchart of a method for signaling a QoS rule to a UE in accordance with an exemplary embodiment of the present invention; Figure 9 illustratively shows a flowchart of a method for deleting a set of parameters in accordance with an exemplary embodiment of the present invention; Figure 10 illustratively shows a flowchart of a method for receiving a QoS rule in accordance with an exemplary embodiment of the present invention; Figure 11 illustratively shows a schematic structural diagram of an NF entity according to an exemplary embodiment of the present invention; Figure 12 illustratively shows a schematic structural diagram of an NF entity according to an exemplary embodiment of the present invention; Figure 13 illustratively shows a schematic structural diagram of an NF entity according to an exemplary embodiment of the present invention; Figure 14 illustratively shows a schematic structural diagram of a UE in accordance with an exemplary embodiment of the present invention; Figure 15 illustratively shows a schematic structural diagram of an NF entity according to an exemplary embodiment of the present invention; Figure 16 illustratively shows a schematic structural diagram of an NF entity according to an exemplary embodiment of the present invention; Figure 17 illustratively shows a schematic structural diagram of an NF entity according to an exemplary embodiment of the present invention; Figure 18 illustratively shows a schematic structural diagram of a UE in accordance with an exemplary embodiment of the present invention; Figure 19 schematically illustrates a telecommunications network connected via an intermediate network to a host computer; Figure 20 is a generalized block diagram of a host computer communicating via a base station with user equipment over a partially wireless connection; and Figures 21 to 24 are flow charts illustrating a method implemented in a communication system including a host computer, a base station and user equipment.

[041] It should be noted that throughout the drawings, the same or similar reference numbers are used to indicate the same or similar elements; Various parts in the drawings are not drawn to scale, but for illustrative purposes only and should therefore not be construed as any limitations and restrictions on the scope of the present invention.

DETAILED DESCRIPTION

[042] Hereinafter, the principle and spirit of the present invention will be described with reference to illustrative embodiments. Some of the embodiments contemplated by the present invention will now be described more fully with reference to the accompanying figures. Other embodiments, however, are within the scope of the subject matter disclosed in the present invention and the subject matter disclosed should not be construed as limited only to the embodiments set forth in the present invention; rather, such embodiments are provided by way of example to convey the scope of the matter to those skilled in the art.

[043] References in this specification to “a modality”, “an exemplary modality” etc. indicate that the described embodiment may include a particular feature, structure or feature, but it is not necessary that each embodiment include the particular feature, structure or feature. Furthermore, such phrases do not necessarily refer to the same modality. Additionally, when a particular feature, structure or characteristic is described in connection with one embodiment, it is understood that it is within the competence of one skilled in the art to affect such feature, structure or characteristic in connection with other embodiments, whether or not this is explicitly described. .

[044] The terminology used in the present invention is for the purpose of describing particular embodiments only and is not intended to limit exemplary embodiments. As used in the present invention, the singular forms "a/an" and "the" are intended to also include the plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "having", "having", "includes" and/or "including", when used in the present invention, specify the presence of features, elements and/or components etc. established, but do not prevent the presence or addition of one or more other resources, elements, components and/or combinations thereof.

[045] In the following description and claims, unless otherwise defined, all technical and scientific terms used in the present invention have the same meaning as commonly understood by one skilled in the art to which this invention belongs.

[046] The techniques described in the present invention can be used for various wireless communication networks, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA ), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Long Term Evolution (LTE) and other networks developed in the future. The terms “network” and “system” are often used interchangeably. Just for illustration, certain aspects of the techniques are described below for the next, namely the 5th generation wireless communication network. However, it will be appreciated by the person skilled in the art that the techniques described in the present invention can also be used for other wireless networks, such as LTE and corresponding radio technologies mentioned in the present invention, as well as wireless networks and radio technologies proposed in the future. .

[047] As used in the present invention, the term "UE" may be, by way of example and not limitation, a User Equipment (UE), an SS (Subscriber Station), a Portable Subscriber Station (PSS) , a Mobile Station (MS), a Mobile Terminal (MT) or an Access Terminal (AT). The UE may include, but is not limited to, mobile phones, cell phones, smartphones or personal digital assistants (PDAs), handheld computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage, and playback apparatus, wearable terminal devices, vehicle-mounted wireless terminal devices and the like. In the following description, the terms “UE”, “terminal device”, “mobile terminal” and “user equipment” may be used interchangeably.

[048] Figure 1 illustrates an example of a wireless communication system 100 in which embodiments of the present invention can be implemented. The wireless communication system 100 may be a cellular communication system, such as a 5G Novo Radio (NR) network or an LTE cellular communication system. As illustrated in this example, the wireless communication system 100 includes a plurality of radio access nodes 120 (e.g., Evolved Node Bs (eNBs), 5G base stations that are referred to as gNBs, or other base stations or the like) and a plurality of wireless communication devices 140 (e.g., conventional UEs, Machine Type Communication (MTC)/Machine-to-Machine (M2M) UEs). The wireless communication system 100 is organized into cells 160, which are connected to a core network 180 via corresponding radio access nodes 120. Radio access nodes 120 are capable of communicating with wireless communication devices 140 (also referred to in the present invention as wireless communication device 140 or UEs 140) together with any additional elements suitable for supporting communication between wireless communication devices. wireless communication or between a wireless communication device and another communication device (such as a landline telephone). The core network 180 includes one or more network nodes or functions 210. In some embodiments, the network nodes/functions 210 may comprise, for example, any of the network functions shown in Figures 2 and 3.

[049] Figure 2 illustrates a wireless communication system 200 represented as a 5G network architecture composed of core NFs, where the interaction between any two NFs is represented by a point-to-point reference point/interface.

[050] Seen from the access side, the 5G network architecture shown in Figure 2 comprises a plurality of User Equipment (UEs) connected to a radio Access Network (RAN) or an Access Network (AN), as well as an Access and Mobility Management Function (AMF). Typically, the RAN or AN comprises base stations, for example, as Evolved Node Bs (eNBs) or 5G base stations (gNBs) or the like. Viewed from the core network side, the 5G core NFs shown in Figure 2 include a Network Slice Selection Function (NSSF), an Authentication Server Function (AUSF), a Unified Data Management (UDM), a Access and Mobility Management (AMF), a Session Management Role (SMF), a Policy Control Role (PCF), an Application Role (AF).

[051] Reference point representations of the 5G network architecture are used to develop detailed call flows in regulatory standardization. The N1 reference point is defined to carry signaling between UE and AMF. The reference points for connection between AN and AMF and between AN and UPF are defined as N2 and N3, respectively. There is a reference point, N11, between AMF and SMF, which implies that SMF is at least partially controlled by AMF. N4 is used by SMF and UPF so that the UPF can be set using the control signal generated by the SMF and the UPF can report its status to the SMF. N9 is the reference point for connection between different UPFs, and N14 is the reference point for connection between different AMFs, respectively. N15 and N7 are defined because the PCF applies the policy to the AMF and SMP, respectively. N12 is required for the AMF to perform UE authentication. N8 and N10 are defined because UE signature data is required for AMF and SMF.

[052] The 5G core network aims to separate the user plane and the control plane. The user plane carries user traffic while the control plane carries signaling on the network. In Figure 2, the UPF is in the user plane and all other NFs, i.e., AMF, SMF, PCF, AF, AUSF, and UDM, are in the control plane. Separating the user and control planes ensures that each plane resource scales independently. It also allows UPFs to be deployed separately from control plane functions in a distributed manner. In this architecture, UPFs can be deployed very close to the UEs to shorten the round trip time (RTT) between the UEs and the data network for some applications that require low latency.

[053] The core 5G network architecture is composed of modularized functions. For example, AMF and SMF are independent functions in the control plane. Separate AMF and SMF allow for independent evolution and scaling. Other control plane functions like PCF and AUSF can be separated as shown in Figure 2. The modularized function design enables the 5G core network to support multiple services flexibly.

[054] Each NF interacts with another NF directly. You can use intermediate functions to route messages from one NF to another NF. In the control plane, a set of interactions between two NFs is defined as a service so that its reuse is possible. This service enables support for modularity. The user plane supports interactions such as forwarding operations between different UPFs.

[055] Figure 3 illustrates a 5G network architecture using service-based interfaces between the NFs in the control plane, rather than the point/point-to-point reference interfaces used in the 5G network architecture of Figure 2. However, the NFs described above with reference to Figure 2 correspond to the NFs shown in Figure 3. Services etc. that an NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. In Figure 3, service-based interfaces are indicated by the letter “N” followed by the name of the NF, for example, Namf for the AMF service-based interface, Nsmf for the SMF service-based interface, and so on. The Network Exposure Function (NEF) and Network Function Repository Function (NRF) in Figure 3 are not shown in Figure 2. However, it should be clarified that all NFs depicted in Figure 2 can interact with the NEF and the NRF of Figure 3 as required, although not explicitly indicated in Figures 2.

[056] Some properties of the NFs shown in Figures 2 and 3 can be described as follows. AMF provides UE-based authentication, authorization, mobility management, etc. A UE, even using multiple access technologies, is basically connected to a single AMF because the AMF is independent of the access technologies. The SMF is responsible for session management and allocates IP addresses to UEs. It also selects and controls the UPF for data transfer. If a UE has multiple sessions, different SMFs can be allocated to each session to manage them individually and possibly provide different functionality per session. The AF provides packet flow information to the PCF responsible for policy control in order to support Quality of Service (QoS). Based on the information, the PCF determines policies around mobility and session management to make the AMF and SMF operate correctly. AUSF supports the authentication function for UEs or the like and therefore stores data for authentication of UEs or the like, while UDM stores UE signature data. The Data Network (DN), which is not part of the 5G core network, provides Internet access or operator services and the like.

[057] An NF can be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on an appropriate platform, for example, a cloud infrastructure.

[058] Next, a method for signaling QoS Flow control parameters according to an exemplary embodiment of the present invention will be described with reference to Figures 4 and 5.

[059] In the present invention, a QoS rule can be generated based on a Policy Control and Billing (PCC) rule and the precedence value of a QoS rule is set to the precedence value of the PCC rule; and parameters such as 5IQ and Averaging Window that are included in a QoS rule, along with some other parameters, are linked to a QoS flow.

[060] Figure 4 shows an exemplary signaling diagram illustrating the details of a method 400 for signaling QoS Flow control parameters and/or a QoS rule.

[061] As shown in Figure 4, method 400 may include steps S410~S430.

[062] In Step S410, the PCF 403 may provide a PCC rule to the SMF 402. This step is optional. A PCC rule can be provisioned in SMF 402 by default.

[063] SMF 402 then derives QoS Flow control parameters and/or a QoS rule in step S420 and transmits QoS Flow control parameters and/or a QoS rule to UE 401 in step S430.

[064] When multiple QoS rules with the same QoS Flow Identifier (QFI) are generated from multiple PCC rules and/or when multiple QoS rules for the same QoS Flow are generated from multiple PCC rules PCC, some of the parameters are repeated in different QoS rules. When the number of QoS rules for the same QFI is increased, the repetition times of some parameters are also increased. The more times it is repeated, the more degraded the signaling efficiency.

[065] Below is an example of x QoS rules with the same QFI value:

[066] Figure 5 illustratively shows a flowchart of a method 500 for signaling parameters for a UE in accordance with an exemplary embodiment of the present invention. In one embodiment, method 500 may be performed on a Network Function (NF) entity, such as an SMF.

[067] As shown in Figure 5, method 500 may include steps S510~S530.

[068] In Step S510, one or more data flow rules associated with a QoS Flow can be generated. Each of the one or more data flow rule rules comprises specific parameters for a data flow that belongs to the QoS Flow.

[069] In Step S520, a QoS Flow profile for the UE for the QoS Flow may be generated. The QoS Stream profile comprises parameters that are common to all data streams that belong to the same QoS Stream.

[070] Then, in step S530, the one or more data flow rules and the QoS Flow profile can be transmitted to the UE.

[071] It is noticed that when multiple QoS rules for the same QFI are generated from multiple PCC rules, some of the parameters are repeated in different QoS rules. In the present application, parameters in a QoS rule that are common to a QoS flow are included in a QoS flow profile, while parameters in a QoS rule that are specific to a data flow (such as an SDF) that belongs to the QoS Flow are included in a flow rule of data. The QoS flow profile and the data flow rule can be linked by any indication, such as a QoS flow identifier. By transmitting a QoS flow profile and the data flow rule separately to the UE, the signaling efficiency can be improved. For example, if there are two, three, or more QoS rules for the same QoS flow that are generated from two, three, or more PCC rules, a QoS flow profile, and two, three, or more QoS flow rules. data can be transmitted, wherein the parameters in the two, three or more QoS rules that are common are included in the QoS flow profile, while other parameters in a QoS rule besides the common parameters are included in a respective flow rule of data. Common parameters will only be transmitted once, therefore signaling efficiency is improved.

[072] Below is an example of the QoS flow profile and 3 data flow rules in the case of 3 data flows that belong to the same QFI value described above:

[073] The Data Flow rule and the QoS Flow profile can be transmitted in different or the same information elements.

[074] In one embodiment, each of the one or more data flow rules is represented by an identifier that is distinguished from one another that is transmitted to the UE. The identifier is shown as a data flow rule identifier in the example above.

[075] In one embodiment, each of the one or more data flow rules comprises parameters that are related to one or more SDF models and/or one or more associated precedence values. For example, in the example above, each data flow rule comprises one or more Packet filters and/or one or more precedence values.

[076] In one embodiment, each of the one or more data flow rules and the QoS Flow profile for the UE comprises a QoS Flow identifier. For example, the QoS Flow identifier may be a QoS Flow identifier. QoS Flow (QFI).

[077] As shown in Figure 5 , the method 500 may further comprise Step S540 of transmitting the one or more data flow rules to the UE, to inform the UE to add the one or more data flow rules to the flow For example, if a new PCC rule is provisioned and is linked to the same QoS Flow, a new QoS rule can be generated from the new PCC rule. A new dataflow rule is generated by the parameters that are specific to a service dataflow (controlled by the PCC rule) in the new QoS rule. If the parameters in the new QoS rule that are common to those in the Flow profile QoS rules do not change, only the new data flow rule is transmitted in step S540. In another embodiment, if any parameter in the new QoS rule which are common to those in the QoS Flow profile changes, i.e., any parameter changes from the one in the previous QoS Flow profile, the changed parameter is also transmitted to the UE in step S550, to allow the UE to update the common parameters for the QoS Flow.

[078] Figure 6 illustratively shows a flowchart of a method 600 for deleting a data flow rule in accordance with an exemplary embodiment of the present invention. In one embodiment, method 600 may be performed on a Network Function (NF) entity, such as an SMF.

[079] For example, when a PCC rule is removed, then a data flow rule comprising parameters specific to the service data flow (controlled by the PCC rule) must be removed. As shown in Figure 6, method 600 may further comprise step S610 of determining whether the data flow rule to be removed is the last one in the QoS Flow. If it is not the last one, it is determined whether to update the Data Flow profile. QoS in step S620. If any parameter in the QoS Flow profile changes, the changed parameter and a data flow rule identifier are passed in step S630. If there is no need to update the QoS Flow profile, only the data flow rule identifier is passed in step S640. If the data flow rule to be removed is the last one in the QoS Flow, a QoS Flow identifier is passed in step S650. For example, when a data flow is removed, the parameters associated with the data flow must be removed, including the data flow rule and the QoS Flow profile. Alternatively, a QoS Flow identifier and a rule identifier of data flow are transmitted in S650, to inform the UE to remove all parameters associated with the data flow, including the data flow rule and the QoS Flow profile.

[080] Figure 7 illustratively shows a flowchart of a method 700 for receiving parameters in accordance with an exemplary embodiment of the present invention. In one embodiment, method 700 may be performed on a UE.

[081] As shown in Figure 7, method 700 may include Step S710 of receiving one or more data flow rules associated with a QoS Flow. Each of the one or more data flow rules comprises parameters specific to a data stream that belongs to that QoS Stream. Method 700 may further include Step S720 of receiving a QoS Stream profile for the QoS Stream. The QoS Stream profile comprises parameters that are common to all data streams that belong to the same QoS Flow.

[082] In one embodiment, each of the one or more data flow rules is represented by an identifier that is distinguished from one another that is also received. In the example above, the identifier is a data flow rule identifier.

[083] In one embodiment, each of the one or more data flow rules and the QoS Flow profile comprises a QoS Flow identifier. For example, the QoS Flow identifier may be a QoS Flow identifier (QFI).

[084] In one embodiment, as shown in Figure 7, the method may include Step S730 of receiving an identifier from a data flow rule. When an identifier for a data flow rule is received, you are informed that the data flow rule should be deleted. The method therefore may include step S740 of deleting the data flow rule.

[085] In one embodiment, as shown in Figure 7, the method may include step S750 of receiving a data flow rule. A data flow rule that is received independently means that it is a new data flow rule for the QoS Flow. By an identifier included in the data flow rule that identifies the QoS Flow, the receiving entity (e.g. , the UE) can, for example, link the received data flow rule to the QoS Flow and thus to the QoS Flow profile of the QoS Flow.

[086] In one embodiment, as shown in Figure 7, the method may include step S770 of receiving an identifier of a QoS Flow to be removed. When receiving an identifier for a QoS Flow to be removed, it is informed that all parameters associated with the QoS Flow must be deleted. The method therefore may further comprise Step S780 of deleting the data flow rule and QoS Flow profile associated with the QoS Flow.

[087] In one embodiment, as shown in Figure 7, the method may include step S790 of receiving a parameter. When a parameter is received, it is informed that the parameter in the QoS Flow profile must be updated. The method therefore further comprises Step S7100 of updating the parameter in the QoS Flow profile with the received parameter.

[088] The steps can be performed in any combination. For example, if an identifier for a data flow rule is received (for example, as in step S730) and a parameter is received (for example, as in Step S790), the data flow rule is deleted and the parameter in the QoS Flow profile is updated with the received parameter. As another example, if a data flow rule is received (e.g., as in step S750) and a parameter is received (e.g., as in Step S790), the data flow rule is bound to the QoS Flow and the parameter in the QoS Flow profile is updated with the received parameter.

[089] It should be understood that the terms used in the present invention, such as “Data Flow rule”, “QoS Flow profile” are just examples. Other appropriate designations may also be applicable. For example, in the future developed standard, the Data Flow rule may still be named as “QoS rule” to maintain the conventional QoS rule, or the “QoS Flow profile” may be named in another way, such as “FLOW profile” as an example.

[090] Figure 8 illustratively shows a flowchart of a method 800 for signaling a QoS rule to a UE in accordance with an exemplary embodiment of the present invention. In one embodiment, method 800 may be performed on a Network Function (NF) entity, such as an SMF.

[091] As shown in Figure 8, method 800 may include Steps S810 and S820.

[092] In Step S810, a QoS rule associated with a QoS Flow can be generated. The QoS rule comprises parameters common to all SDFs that belong to the same QoS Flow and one or more parameter sets, wherein each of the one or more parameter sets comprises parameters that are specific to an SDF that belongs to the QoS Flow. .

[093] In Step S820, the generated QoS rule can be transmitted to the UE.

[094] It is noted that when multiple QoS rules for the same QFI are generated from multiple PCC rules, some of the parameters are repeated in different QoS rules. In the present application, a new (modified) QoS rule is proposal. Parameters that are common to a QoS Flow are included in a QoS rule once, while parameters that are specific to a data flow (such as an SDF) that belongs to the QoS Flow are included in a parameter set. By transmitting a QoS rule comprising common parameters and one or more parameter sets to the UE, signaling efficiency can be improved. For example, if there are two, three or more legacy QoS rules for the same QoS flow that are generated from two, three or more PCC rules, a QoS rule (new/modified) can be passed, where parameters that are common are included in the QoS rule once, while parameters other than common parameters are included in a respective parameter set. Common parameters will only be transmitted once, therefore signaling efficiency is improved.

[095] Below is an example of the new QoS rule in case multiple data streams use the same QFI value described above:

Mapped Traffic Flow Model

[096] In one embodiment, each of the one or more parameter sets is distinguished from one another by an identifier that is included in the one or more parameter sets. The identifier is shown as a parameter set identifier in the example above.

[097] In one embodiment, each of the one or more parameter sets comprises parameters that are related to one or more service data flow (SDF) models and/or one or more associated precedence values. For example, in the example above, each set of parameters comprises one or more Packet filters and/or one or more precedence values.

[098] As shown in Figure 8 , method 800 may further comprise step S830 of transmitting the set of parameters along with a QoS rule identifier to the UE if the QoS rule has already been transmitted, to allow the UE Update the QoS rule to include the parameter set. For example, if a new PCC rule is provisioned and is linked to the same QoS Flow, a new set of parameters can be generated from the new PCC rule. If parameters that are common to the QoS Flow do not change, only the parameter set is passed in step S830. In another embodiment, if any parameters in the QoS rule that are common to the QoS Flow change, that is, any parameter changes from that in the previous QoS rule, the changed parameter is also transmitted to the UE in step S840, to allow the UE update common parameters for QoS Flow.

[099] As shown in Figure 8, method 800 may further comprise step S840 of transmitting a parameter and an identifier of a parameter set to which the parameter belongs together with a QoS rule identifier to the UE, to allow the UE update the QoS rule by updating the parameter in the parameter set. For example, if a PCC rule changes, one or more parameters in the parameter set generated from the PCC may change. In that case, the changed parameter and the identifier of the parameter set to which the parameter belongs are transmitted to the UE, to allow the UE to update the parameter.

[100] Figure 9 illustratively shows a flowchart of a method 900 for excluding a parameter set in accordance with an exemplary embodiment of the present invention. In one embodiment, method 900 may be performed on a Network Function (NF) entity, such as an SMF.

[101] For example, when a PCC rule is removed, then a parameter set comprising parameters specific to a service data stream (controlled by the PCC rule) must be removed. As shown in Figure 9, method 900 may further comprise step S910 of determining whether the parameter set to be removed is the last one in the QoS Flow. If it is not the last one, determining whether it needs to update the common parameters in step S920 . If any of the common parameters change, a QoS rule identifier, the changed parameter, and a parameter set identifier are passed in step S930. If there is no need to update the common parameters, only the parameter set identifier is passed in step S940. If the parameter set to be removed is the last one in the QoS Flow, a QoS Flow identifier, or a QoS rule identifier is passed in step S950. For example, when a data flow is removed, the parameters associated with the data flow, that is, the QoS rule, must be removed, including the common parameters and parameter set.

[102] In one embodiment, in order to associate the transmitted parameter set/parameter to the QoS rule to which the parameter set belongs in steps S830, S840, S930, S940, a QoS rule identifier or a Flow identifier QoS rule is transmitted together, so that the UE can associate the received set of parameters/parameters with the QoS rule.

[103] Figure 10 illustratively shows a flowchart of a method 1000 for receiving a QoS rule in accordance with an exemplary embodiment of the present invention. In one embodiment, method 1000 may be performed on a UE.

[104] As shown in Figure 10, method 1000 may include step S1010 of receiving a QoS rule associated with a QoS Flow, wherein the QoS rule comprises parameters common to all data flows belonging to the same Flow of QoS Flow, and one or more parameter sets, wherein each of the one or more parameter sets comprises parameters that are specific to a data stream belonging to the QoS Flow.

[105] In one embodiment, each of the one or more sets of parameters is distinguished from one another by an identifier that is included in the one or more sets of parameters. In the example above, the identifier is a parameter set identifier.

[106] In one embodiment, as shown in Figure 10, the method may include step S1020 of receiving a set of parameters with a QoS rule identifier. A set of parameters that is received independently means that it is a new set of parameters to the QoS Flow. By the QoS rule identifier that identifies the QoS Flow/QoS rule, the receiving entity (e.g., the UE) can update the QoS rule to include the parameter set received in step S1030 .

[107] In one embodiment, as shown in Figure 10, the method may include Step S1040 of receiving a parameter set identifier together with a QoS rule identifier. When a parameter set identifier is received, it is informed that the parameter set must be deleted. Method 1000 therefore may include step S1050 of updating the QoS rule by deleting the QoS rule parameter set.

[108] In one embodiment, as shown in Figure 10 , the method may include Step S1060 of receiving one or more of the common parameters along with a QoS rule identifier and Step S1070 of updating the corresponding parameter in the QoS rule with the received parameter. When the receiving entity (e.g., the UE) receives one or more of the common parameters, it is informed to update the common parameters. The receiving entity will therefore update those in the QoS rule with those received.

[109] In one embodiment, as shown in Figure 10, the method may include Step S1080 of receiving a parameter and an identifier of a parameter set to which the parameter belongs together with a QoS rule identifier and Step S1090 of update the QoS rule by updating the parameter in the parameter set. When the receiving entity receives one or more parameters in a parameter set, it is informed to update them in the parameter set. The receiving entity will therefore update those in the parameter set with the received ones.

[110] Hereinafter, a structure of an NF entity will be described with reference to Figure 11. Figure 11 illustratively shows a schematic diagram of the structure of an NF entity 1100 in accordance with an exemplary embodiment of the present invention. The NF entity 1100 in Figure 11 can perform methods 500 and 600 for signaling parameters described previously with reference to Figures 5-6. Therefore, some detailed description in the NF entity 1100 may refer to the corresponding description of methods 400 and 500 for signaling parameters as discussed previously.

[111] As shown in Figure 11, the NF entity 1100 may include a generation module 1101 and a transmission module 1102. As will be understood by those skilled in the art, common components in the NF entity 1100 are omitted in Figure 11 so as not to obscure the idea of the present invention. Additionally, some modules can be distributed across more modules or integrated into fewer modules.

[112] The generation module 1101 of the NF entity 1100 can be configured to generate one or more data flow rules associated with a QoS Flow and a QoS Flow profile for the UE for the QoS Flow.

[113] Transmission module 1102 of NF entity 1100 may be configured to transmit one or more data flow rules and the QoS Flow profile.

[114] In one embodiment, the transmission module 1102 of the NF entity 1100 may be further configured to transmit only one or more data flow rules to the UE. For example, if a new PCC rule is provisioned and is linked to the same QoS Flow, a new QoS rule can be generated from the new PCC rule. A new data flow rule is generated by the parameters that are specific to a service data flow (controlled by the PCC rule) in the new QoS rule. If the parameters in the new QoS rule that are common to those in the Flow profile QoS rules do not change, only the new data flow rule is transmitted. In another embodiment, if any parameter in the new QoS rule that is common to those in the QoS Flow profile changes, i.e., any parameter changes from that in the previous QoS Flow profile, the transmission module 1102 of the NF entity 1100, can be additionally configured to transmit the changed parameter to the UE, to allow the UE to update the common parameters for the QoS Flow.

[115] In one embodiment, the NF entity 1100 may additionally include a determination module 1103. The determination module 1103 of the NF entity 1100 may be configured to determine whether the data flow rule to be removed is the last of the If it is determined that it is not the latter, the determination module 1103 of the NF entity 1100 may be configured to determine whether it needs to update the QoS Flow profile. If it is determined that any parameter in the QoS Flow profile changes, the transmission module 1102 of the NF entity 1100 transmits the changed parameter and a data flow rule identifier. If it is determined that there is no need to update the QoS Flow profile, the transmission module 1102 of the NF entity 1100 transmits only the data flow rule identifier. If it is determined that the data flow rule to be removed is the last one in the QoS Stream, the transmission module 1102 of the NF entity 1100 transmits a QoS Stream identifier. For example, when a data stream is removed, parameters associated with the data flow must be removed, including the data flow rule and the QoS Flow profile. Alternatively, the transmission module 1102 of the NF entity 1100 transmits a QoS Flow identifier and a rule identifier flow profile, to inform the UE to remove all parameters associated with the data flow, including the data flow rule and the QoS Flow profile.

[116] Hereinafter, another structure of an NF entity 1200 will be described with reference to Figure 12. Figure 12 illustratively shows a schematic diagram of the structure of an NF entity 1200 according to an exemplary embodiment of the present invention. The NF entity 1200 in Figure 12 can perform methods 500 and 600 for signaling parameters described previously with reference to Figures 5-6. Therefore, some detailed description in the NF entity 1200 may refer to the corresponding description of methods 500 and 600 for signaling parameters as discussed previously.

[117] As shown in Figure 12, the NF entity 1200 may include at least one controller or processor 1203 including, for example, any suitable Central Processing Unit, CPU, microcontroller, Digital Signal Processor, DSP, etc., capable of executing computer program instructions. Computer program instructions may be stored in a memory 1205. The memory 1205 may be any combination of RAM (Random Access Memory) and ROM (Read Only Memory). The memory may also comprise persistent storage, which, for example, may be any one or combination of magnetic memory, optical memory or solid state memory or even remotely mounted memory. The exemplary NF entity 1200 further comprises a communication interface 1201 arranged for communication.

[118] The instructions, when loaded from memory 1205 and executed by at least one processor 1203, may cause the NF entity 1200 to perform methods 500 and 600 as previously described.

[119] In particular, the instructions, when loaded from memory 1205 and executed by at least one processor 1203, may cause the NF entity 1200 to generate one or more data flow rules associated with a QoS Flow, wherein each of the one or more data flow rules comprises specific parameters for a data flow belonging to the QoS Flow, and generates a QoS Flow profile for the UE for the QoS Flow, wherein the QoS Flow profile QoS Stream comprises parameters that are common to all data streams that belong to the same QoS Stream. The instructions, when loaded from memory 1205 and executed by at least one processor 1203, may cause the NF entity 1200 transmit one or more data flow rules and the QoS Flow profile to the UE.

[120] In one embodiment, each of the one or more data flow rules is represented by an identifier that is distinguished from one another in which it is transmitted to the UE. The identifier is shown as a data flow rule identifier in the example above.

[121] In one embodiment, each of the one or more data flow rules comprises parameters that are related to one or more SDF models and/or one or more associated precedence values. For example, in the example above, each data flow rule comprises one or more Packet filters and/or one or more precedence values.

[122] In one embodiment, each of the one or more data flow rules and the QoS Flow profile for the UE comprises a QoS Flow identifier. For example, the QoS Flow identifier may be a QoS Flow identifier. QoS Flow (QFI).

[123] The instructions, when loaded from memory 1205 and executed by at least one processor 1203, may cause the NF entity 1200 to transmit one or more data flow rules to the UE. For example, if a new PCC rule is provisioned and is linked to the same QoS Flow, a new QoS rule can be generated from the new PCC rule. A new data flow rule is generated by the parameters that are specific to a service data flow (controlled by the PCC rule) in the new QoS rule. If the parameters in the new QoS rule that are common to those in the Flow profile QoS rules do not change, only the new data flow rule is transmitted. In another embodiment, if any parameter in the new QoS rule that is common to those in the QoS Flow profile changes, i.e., any parameter changes from that in the previous QoS Flow profile, the instructions, when loaded from memory 1205 and performed by at least one processor 1203, may cause the NF entity 1200 to also transmit the changed parameter to the UE, to allow the UE to update the common parameters for the QoS Flow.

[124] When a PCC rule is removed, then a dataflow rule that comprises specific parameters for a service dataflow (controlled by the PCC rule) must be removed. The instructions, when loaded from memory 1205 and executed by at least one processor 1203, may cause the NF entity 1200 to determine whether the dataflow rule to be removed is the last one in the QoS Flow. lastly, the instructions, when loaded from memory 1205 and executed by at least one processor 1203, may cause the NF entity 1200 to determine whether it needs to update the QoS Flow profile. QoS change instructions, when loaded from memory 1205 and executed by at least one processor 1203, may cause NF entity 1200 to transmit the changed parameter and a data flow rule identifier. If there is no need to update the QoS Flow profile, the instructions, when loaded from memory 1205 and executed by at least one processor 1203, may cause the NF entity 1200 to transmit only the flow rule identifier. data. If the data flow rule to be removed is the last one in the QoS Flow, the instructions, when loaded from memory 1205 and executed by at least one processor 1203, may cause the NF entity 1200 to transmit an identifier of the QoS Flow. For example, when a data flow is removed, the parameters associated with the data flow must be removed, including the data flow rule and the QoS Flow profile. Alternatively, instructions, when loaded from of memory 1205 and executed by at least one processor 1203, may cause the NF entity 1200 to transmit a QoS Flow identifier and a data flow rule identifier, to inform the UE to remove all parameters associated with the flow including data flow rule and QoS Flow profile.

[125] Hereinafter, a structure of a UE will be described with reference to Figure 13. Figure 13 illustratively shows a schematic structure diagram of a UE 1300 in accordance with an exemplary embodiment of the present invention. UE 1300 in Fig. 13 may perform method 700 for receiving parameters previously described with reference to Fig. 7. Therefore, some detailed description in UE 1300 may refer to the corresponding description of method 700 as discussed above.

[126] As shown in Figure 13, the UE 1300 may include a receiving module 1301. As will be understood by those skilled in the art, common components in the UE 1300 are omitted in Figure 13 so as not to obscure the idea of the present invention. Additionally, some modules can be distributed across more modules or integrated into fewer modules.

[127] The receiving module 1301 of the UE 1300 may be configured to receive one or more data flow rules associated with the QoS Stream. Each of the one or more data flow rules comprises specific parameters for a data flow that belongs to that QoS Stream. The receiving module 1301 of the UE 1300 may additionally be configured to receive a QoS Stream profile for the QoS Stream. The QoS Stream profile comprises parameters that are common to all data streams that belong to the same QoS Flow.

[128] In one embodiment, each of the one or more data flow rules is represented by an identifier that is distinguished from the other in which it is also received. In the example above, the identifier is a data flow rule identifier.

[129] In one embodiment, each of the one or more data flow rules and the QoS Flow profile comprises a QoS Flow identifier. For example, the QoS Flow identifier may be a QoS Flow identifier (QFI).

[130] In one embodiment, the receiving module 1301 of the UE 1300 may be further configured to receive an identifier of a data flow rule.

[131] In one embodiment, the UE 1300 may include a deletion module 1302. When the receiving module 1301 receives an identifier from a data flow rule, it is informed that the data flow rule should be deleted. The deletion module 1302 of the UE 1300 may be configured to delete the data flow rule.

[132] In one embodiment, the receiving module 1301 of the UE 1300 may be further configured to receive a data flow rule. A data flow rule that is received independently means that it is a new data flow rule for the QoS Flow. By an identifier included in the data flow rule that identifies the QoS Flow, the UE 1300 may, e.g. , link the received data flow rule to the QoS Flow and thus to the QoS Flow profile of the QoS Flow.

[133] In one embodiment, the receiving module 1301 of the UE 1300 may be further configured to receive an identifier of a QoS Flow to be removed. When receiving an identifier for a QoS Flow to be removed, it is informed that all parameters associated with the QoS Flow must be deleted. The deletion module 1302 of the UE 1300 may therefore be configured to delete the data flow rule and the QoS Flow profile associated with the QoS Flow.

[134] In one embodiment, the receiving module 1301 of the UE 1300 may be additionally configured to receive a parameter. When a parameter is received, it is informed that the parameter in the QoS Flow profile must be updated.

[135] In one embodiment, the UE 1300 may include an update module 1303. When the receiving module 1301 receives a parameter, the update module 1303 of the UE 1300 may be configured to update the parameter in the QoS Flow profile with the received parameter.

[136] Hereinafter, another structure of an NF entity will be described with reference to Figure 14. Figure 14 illustratively shows a schematic structure diagram of a UE 1400 in accordance with an exemplary embodiment of the present invention. The UE 1400 in Figure 14 may perform the method 700 for receiving parameters previously described with reference to Figure 5. Therefore, some detailed description in the UE 1400 may refer to the corresponding description of the method 500 as discussed above.

[137] As shown in Figure 14, the UE 1400 may include at least one controller or processor 1403 including, for example, any suitable Central Processing Unit, CPU, microcontroller, Digital Signal Processor, DSP, etc. execute computer program instructions. Computer program instructions may be stored in memory 1405. Memory 1405 may be any combination of RAM (Random Access Memory) and ROM (Read Only Memory). The memory can also comprise persistent storage, which, for example, can be any or combination of magnetic memory, optical memory or solid state memory or even remotely mounted memory. The exemplary UE 1400 further comprises a communication interface 1401 arranged for communication.

[138] The instructions, when loaded from memory 1405 and executed by at least one processor 1403, may cause the UE 1400 to perform method 700 as previously described.

[139] In particular, the instructions, when loaded from memory 1405 and executed by at least one processor 1403, may cause the UE 1400 to receive one or more data flow rules associated with a QoS Flow and a profile The QoS Flow profile each of the one or more data flow rules comprises parameters specific to a data flow that belongs to that QoS Flow. The QoS Flow profile comprises parameters that are common to all data flows that belong to the same QoS Stream.

[140] In one embodiment, each of the one or more data flow rules is represented by an identifier that is distinguished from the other in which it is also received. In the example above, the identifier is a data flow rule identifier.

[141] In one embodiment, each of the one or more data flow rules and the QoS Flow profile comprises a QoS Flow identifier. For example, the QoS Flow identifier may be a QoS Flow identifier (QFI).

[142] In one embodiment of the present invention, instructions, when loaded from memory 1405 and executed by at least one processor 1403, may cause UE 1400 to receive an identifier of a data flow rule. When an identifier for a data flow rule is received, you are informed that the data flow rule should be deleted. The instructions, when loaded from memory 1405 and executed by at least one processor 1403, may cause the UE 1400 to delete the data flow rule.

[143] In one embodiment of the present invention, instructions, when loaded from memory 1405 and executed by at least one processor 1403, can cause UE 1400 to receive a data flow rule. A data flow rule that is received independently means that it is a new data flow rule for the QoS Flow. By an identifier included in the data flow rule that identifies the QoS Flow, the NF entity can e.g. For example, link the received data flow rule to the QoS Flow and thus to the QoS Flow profile of the QoS Flow.

[144] In one embodiment of the present invention, instructions, when loaded from memory 1405 and executed by at least one processor 1403, may cause UE 1400 to receive an identifier of a QoS Flow to be removed. When receiving an identifier for a QoS Flow to be removed, it is informed that all parameters associated with the QoS Flow must be deleted. The instructions, when loaded from memory 1405 and executed by at least one processor 1403 may cause the UE 1400 to delete the data flow rule and the QoS Flow profile associated with the QoS Flow.

[145] In one embodiment of the present invention, instructions, when loaded from memory 1405 and executed by at least one processor 1403, may cause the UE 1400 to receive a parameter. When a parameter is received, it is informed that the parameter in the QoS Flow profile must be updated. The instructions, when loaded from memory 1405 and executed by at least one processor 1403 may cause the UE 1400 to update the parameter in the QoS Flow profile with the received parameter.

[146] Hereinafter, a structure of an NF entity will be described with reference to Figure 15. Figure 15 illustratively shows a schematic diagram of the structure of an NF entity 1500 in accordance with an exemplary embodiment of the present invention. The NF entity 1500 in Figure 15 may perform methods 800 and 900 for signaling a QoS rule to a UE described previously with reference to Figures 8-9. Therefore, some detailed description in the NF entity 1500 may refer to the corresponding description of methods 800 and 900 for signaling a QoS rule to a UE as discussed previously.

[147] As shown in Figure 15, the NF entity 1500 may include a generation module 1501 and a transmission module 1502. As will be understood by those skilled in the art, common components in the NF entity 1500 are omitted in Figure 15 so as not to obscure the idea of the present invention. Additionally, some modules can be distributed across more modules or integrated into fewer modules.

[148] The generation module 1501 of the NF entity 1500 can be configured to generate QoS rule associated with a QoS Flow. The QoS rule comprises parameters common to all SDFs that belong to the same QoS Flow and one or more sets of parameters, wherein each of the one or more parameter sets comprises parameters that are specific to an SDF that belongs to the QoS Stream.

[149] The transmission module 1502 of the NF entity 1500 may be configured to transmit the generated QoS rule.

[150] In one embodiment, the transmission module 1502 of the NF entity 1500 can be further configured to transmit the set of parameters together with an identifier of the QoS rule to the UE if the QoS rule has already been transmitted, to allow for the UE to update the QoS rule to include the parameter set. For example, if a new PCC rule is provisioned and is linked to the same QoS Flow, a new set of parameters can be generated from the new PCC rule. If the parameters that are common to the QoS Flow do not change, the transmission module 1502 of the NF entity 1500 transmits only the set of parameters. In another embodiment, if any parameter in the QoS rule that is common to the QoS Flow changes, that is, any parameter changes from that in the previous QoS rule, the transmission module 1502 of the NF entity 1500 also transmits the changed parameter, to allow the UE to update the common parameters for the QoS Flow.

[151] In one embodiment, the transmission module 1502 of the NF entity 1500 may be further configured to transmit a parameter and an identifier of a parameter set to which the parameter belongs together with a QoS rule identifier to the UE, to allow the UE to update the QoS rule by updating the parameter in the parameter set. For example, if a PCC rule changes, one or more parameters in the parameter set generated from the PCC may change. In this case, the changed parameter and the identifier of the parameter set to which the parameter belongs are transmitted to the UE, to allow the UE to update the parameter.

[152] In one embodiment, the NF entity 1500 may further include a determination module 1503. The determination module 1503 of the NF entity 1500 may be configured to determine whether the set of parameters to be removed is the last of the QoS. If not the latter, the NF entity determination module 1503 1500 can be configured to determine whether it needs to update the common parameters. If any one of the common parameters changes, the transmit module 1502 of the NF entity 1500 can be further configured to transmit the changed parameter and a parameter set identifier. If there is no need to update the common parameters, the transmitting module 1502 of the NF entity 1500 can be further configured to transmit only the parameter set identifier. If the set of parameters to be removed is the last of the QoS Flow, the transmitting module 1502 of the NF entity 1500 can be further configured to transmit a QoS Flow identifier, or a QoS rule identifier. When a data flow is removed, the parameters associated with the data flow, that is, the QoS rule, must be removed, including the common parameters and the parameter set.

[153] Hereinafter, another structure of an NF entity 1600 will be described with reference to Figure 16. Figure 16 illustratively shows a schematic diagram of the structure of an NF entity 1600 according to an exemplary embodiment of the present invention. The NF entity 1600 in Figure 16 may perform methods 800 and 900 for signaling a QoS rule to a UE previously described with reference to Figures 8 and 9. Therefore, some detailed description in the NF entity 1600 may refer to the corresponding description of methods 800 and 900 for signaling a QoS rule to a UE as discussed above.

[154] As shown in Figure 16, the NF entity 1600 may include at least one controller or processor 1603 including, for example, any suitable Central Processing Unit, CPU, microcontroller, Digital Signal Processor, DSP, etc., capable of executing computer program instructions. Computer program instructions may be stored in memory 1605. Memory 1605 may be any combination of RAM (Random Access Memory) and ROM (Read Only Memory). The memory may also comprise persistent storage, which, for example, may be any one or combination of magnetic memory, optical memory or solid state memory or even remotely mounted memory. The exemplary NF entity 1600 further comprises a communication interface 1601 arranged for communication.

[155] The instructions, when loaded from memory 1605 and executed by at least one processor 1603, may cause the NF entity 1600 to perform methods 800 and 900 as previously described.

[156] In particular, instructions, when loaded from memory 1605 and executed by at least one processor 1603, may cause the NF entity 1600 to generate QoS rule associated with a QoS Stream. The QoS rule comprises parameters common to all SDFs belonging to the same QoS Flow and one or more parameter sets, wherein each of the one or more parameter sets comprises parameters that are specific to an SDF belonging to the QoS Flow.

[157] The instructions, when loaded from memory 1605 and executed by at least one processor 1603, may cause the NF entity 1600 to transmit the set of parameters along with an identifier of the QoS rule to the UE if the rule has already been transmitted, to allow the UE to update the QoS rule to include the parameter set. For example, if a new PCC rule is provisioned and is linked to the same QoS Flow, a new set of parameters can be generated from the new PCC rule. If parameters that are common to the QoS Flow do not change, the instructions, when loaded from the memory 1605 and executed by at least one processor 1603, can cause the NF entity 1600 to transmit only the set of parameters. In another embodiment, if any parameter in the QoS rule that are common to the QoS Flow changes, i.e., any parameter changes from that in the previous QoS rule, the instructions, when loaded from memory 1605 and executed by at least one processor 1603, may cause the NF entity 1600 to transmit the changed parameter, to allow the UE to update the common parameters for the QoS Flow.

[158] In one embodiment, the instructions, when loaded from memory 1605 and executed by at least one processor 1603, may cause the NF entity 1600 to transmit a parameter and a parameter set identifier to which the parameter belongs along with a QoS rule identifier for the UE, to allow the UE to update the QoS rule by updating the parameter in the parameter set. For example, if a PCC rule changes, one or more parameters in the parameter set generated from the PCC may change. In this case, the changed parameter and the identifier of the parameter set to which the parameter belongs are transmitted to the UE, to allow the UE to update the parameter.

[159] In one embodiment, the instructions, when loaded from memory 1605 and executed by at least one processor 1603, may cause the NF entity 1600 to determine whether the set of parameters to be removed is the last of the Flow of QoS. If not the latter, the instructions, when loaded from memory 1605 and executed by at least one processor 1603, may cause the NF entity 1600 to determine whether it needs to update common parameters. If any of the common parameters change, the instructions, when loaded from memory 1605 and executed by at least one processor 1603, may cause the NF entity 1600 to transmit the changed parameter and a parameter set identifier. If there is no need to update the common parameters, the instructions, when loaded from memory 1605 and executed by at least one processor 1603, may cause the NF entity 1600 to transmit only the parameter set identifier. If the set of parameters to be removed is the last of the QoS Flow, the instructions, when loaded from the memory 1605 and executed by at least one processor 1603, may cause the NF entity 1600 to transmit an identifier of the Flow of QoS, or a QoS rule identifier. For example, when a data flow is removed, the parameters associated with the data flow, i.e., the QoS rule, must be removed, including the common parameters and parameter set .

[160] Hereinafter, a structure of a UE will be described with reference to Figure 17. Figure 17 illustratively shows a schematic diagram of the structure of a UE 1700 in accordance with an exemplary embodiment of the present invention. The UE 1700 in Figure 17 may perform the method 1000 for receiving a QoS rule described previously with reference to Figure 10. Therefore, some detailed description in the UE 1700 may refer to the corresponding description of the method 1000 as discussed previously.

[161] As shown in Figure 17, the UE 1700 may include a reception module 1701. As will be understood by those skilled in the art, common components in the UE 1700 are omitted in Figure 17 so as not to obscure the idea of the present invention. Additionally, some modules can be distributed across more modules or integrated into fewer modules.

[162] The receiving module 1701 of the UE 1700 may be configured to receive a QoS rule associated with a QoS Stream, wherein the QoS rule comprises parameters common to all data streams belonging to the same QoS Stream, and one or more parameter sets, wherein each of the one or more parameter sets comprises parameters that are specific to a data stream belonging to the QoS Stream.

[163] In one embodiment, each of the one or more sets of parameters is distinguished from one another by an identifier that is included in the one or more sets of parameters. In the example above, the identifier is a parameter set identifier.

[164] In one embodiment, the UE 1700 may include an update module 1702.

[165] In one embodiment, the receiving module 1701 of the UE 1700 can be configured to receive a set of parameters along with a QoS rule identifier. A set of parameters that is independently received means that it is a new set of parameters for the QoS Flow. By the QoS rule identifier that identifies the QoS Flow/QoS Rule, the update module 1702 of the UE 1700 can be configured to update the QoS rule to include the received parameter set.

[166] In one embodiment, the receiving module 1701 of the UE 1700 may be configured to receive a parameter set identifier along with a QoS rule identifier. When a parameter set identifier is received, it is informed that the parameter set must be deleted. The update module 1702 of the UE 1700 may be configured to update the QoS rule by deleting the QoS rule parameter set.

[167] In one embodiment, the receive module 1701 of the UE 1700 may be configured to receive one or more of the common parameters along with a QoS rule identifier, and the update module 1702 of the UE 1700 may be configured to update the corresponding parameter in the QoS rule with the received parameter. When the receiving entity (e.g., the UE) receives one or more of the common parameters, it is informed to update the common parameters. The UE 1700 will therefore update those in the QoS rule with those received.

[168] In one embodiment, the receive module 1701 of the UE 1700 may be configured to receive a parameter and an identifier from a parameter set to which the parameter belongs together with a QoS rule identifier, and the update module 1702 of the UE 1700 can be configured to update the QoS rule by updating the parameter in the parameter set. When the receiving entity receives one or more parameters in a parameter set, it is told to update them in the parameter set. The receiving entity will therefore update those in the parameter set with the received ones.

[169] Hereinafter, another structure of an NF entity will be described with reference to Figure 18. Figure 18 illustratively shows a schematic structure diagram of a UE 1800 in accordance with an exemplary embodiment of the present invention. The UE 1800 in Figure 18 may perform the method 1000 for receiving a QoS rule described previously with reference to Figure 10. Therefore, some detailed description in the UE 1800 may refer to the corresponding description of the method 1000 as discussed previously.

[170] As shown in Figure 18, the UE 1800 may include at least one controller or processor 1803 including, for example, any suitable Central Processing Unit, CPU, microcontroller, Digital Signal Processor, DSP, etc., capable of execute instructions from computer programs. Computer program instructions may be stored in memory 1805. Memory 1805 may be any combination of RAM (Random Access Memory) and ROM (Read Only Memory). The memory may also comprise persistent storage, which, for example, may be any one or combination of magnetic memory, optical memory or solid state memory or even remotely mounted memory. Exemplary UE 1800 further comprises a communication interface 1801 arranged for communication.

[171] The instructions, when loaded from memory 1805 and executed by at least one processor 1803, may cause the UE 1800 to perform method 1000 as previously described.

[172] In particular, instructions, when loaded from memory 1805 and executed by at least one processor 1803, may cause UE 1800 to receive a QoS rule associated with a QoS Flow, where the QoS rule comprises parameters common to all data streams belonging to the same QoS Stream and one or more parameter sets, wherein each of the one or more parameter sets comprises parameters that are specific to a data stream belonging to the QoS Stream. QoS.

[173] In one embodiment of the present invention, instructions, when loaded from memory 1805 and executed by at least one processor 1803, may cause UE 1800 to receive a set of parameters along with a QoS rule identifier. A parameter set that is independently received means that it is a new parameter set for the QoS Flow. By the QoS rule identifier that identifies the QoS Flow/QoS Rule, the UE 1800 can update the QoS rule to include the set of received parameters.

[174] In one embodiment of the present invention, instructions, when loaded from memory 1805 and executed by at least one processor 1803, may cause the UE 1800 to receive a parameter set identifier along with a control rule identifier. QoS. When an identifier for a parameter set is received, it is informed that the parameter set should be deleted. The instructions, when loaded from memory 1805 and executed by at least one processor 1803 may cause the UE 1800 to update the QoS rule by deleting the QoS rule parameter set.

[175] In one embodiment of the present invention, instructions, when loaded from memory 1805 and executed by at least one processor 1803, may cause the UE 1800 to receive one or more of the common parameters along with a rule identifier. QoS, and update the corresponding parameter in the QoS rule with the received one. When the receiving entity (e.g., the UE) receives one or more common parameters, it is informed to update the common parameters. The receiving entity will therefore update those in the QoS rule with those received. In one embodiment of the present invention, the instructions, when loaded from memory 1805 and executed by at least one processor 1803, may cause the UE 1800 to receive a parameter and an identifier from a parameter set in which the parameters belong together. with a QoS rule identifier, and update the QoS rule by updating the parameter in the parameter set. When the receiving entity receives one or more parameters in a parameter set, it is informed to update those in a parameter set. The receiving entity will therefore update those in the QoS rule with those received.

[176] Referring to Figure 19, according to one embodiment, a communication system includes a telecommunications network 1910, such as a 3GPP-type cellular network, which comprises an access network 1911, such as a radio access network and core network 1914. The access network 1911 comprises a plurality of base stations 1912a, 1912b, 1912c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1913a, 1913b, 1913c. Each base station 1912a, 1912b, 1912c is connectable to the core network 1914 via a wired or wireless connection 1915. A first user equipment (UE) 1991 located in coverage area 1913c is configured to connect wirelessly or be radiolocated by corresponding 1912c base station. A second UE 1992 in coverage area 1913a is wirelessly connectable to the corresponding base station 1912a. Although a plurality of UEs 1991, 1992 are illustrated in this example, the disclosed embodiments are equally applicable to a situation in which a single UE is in the coverage area or in which a single UE is connecting to the corresponding base station 1912.

[177] The telecommunications network 1910 itself is connected to a host computer 1930, which may be incorporated into the hardware and/or software of a standalone server, a server deployed in the cloud, a distributed server, or as processing resources on a data farm. servers. The host computer 1930 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. Connections 1921, 1922 between the telecommunications network 1910 and the host computer 1930 may extend directly from the core network 1914 to the host computer 1930 or may pass through an optional intermediate network 1920. Intermediate network 1920 may be one of or a combination of more than one of a public, private, or hosted network; intermediate network 1920, if any, may be a backbone network or the internet; in particular, intermediate network 1920 may comprise two or more subnets (not shown).

[178] The communication network of Figure 19, as a whole, allows connectivity between the connected UEs 1991, 1992 and the host computer 1930. The connectivity can be described as an Over-the-Top (OTT) connection 1950. The computer host 1930 and the connected UEs 1991, 1992 are configured to communicate data and/or signaling over the OTT connection 1950, using the access network 1911, the core network 1914, any intermediate network 1920 and possible additional infrastructures (not illustrated) as intermediaries . The OTT connection 1950 may be transparent in the sense that the participating communication devices through which the OTT connection 1950 passes are unaware of the uplink and downlink communications routing. For example, base station 1912 cannot or does not need to be informed of the past routing of an incoming downlink communication with data originating from host computer 1930 to be forwarded (e.g., handed over) to a connected UE 1991. Similarly, the base station 1912 does not need to know the future routing of an outbound uplink communication originating from the UE 1991 toward the host computer 1930.

[179] Examples of implementations, in accordance with one embodiment, of the UE, the base station and the host computer discussed in the preceding paragraphs will now be described with reference to Figure 20. In a communication system 2000, a host computer 2010 comprises hardware 2015 , including a communication interface 2016 configured to establish and maintain a wired or wireless connection with an interface of a communication device other than the communication system 2000. The host computer 2010 further comprises a set of processing circuitry 2018, the which may have storage and/or processing capabilities. In particular, the processing circuitry 2018 may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 2010 further comprises software 2011, which is stored on or accessible by the host computer 2010 and executable by the processing circuitry 2018. The software 2011 includes the host application 2012. The host application 2012 may be operable to provide a service to a remote user, such as a UE 2030 connecting via an OTT connection 2050 terminating at the UE 2030 and the host computer 2010. When providing the service to the remote user, the host application 2012 may provide user data that is transmitted using OTT 2050 connection.

[180] The communication system 2000 additionally includes a base station 2020 provided in a telecommunications system and comprising hardware 2025, allowing it to communicate with the host computer 2010 and the UE 2030. The hardware 2025 may include a communication interface 2026 for preparing and maintaining a wired or wireless connection with an interface of a communication device other than the communication system 2000, as well as a radio interface 2027 for preparing and maintaining at least one wireless connection 2070 with a UE 2030 located in a coverage area (not illustrated in Figure 20) served by the base station 2020. The communication interface 2026 may be configured to facilitate a connection 2060 with the host computer 2010. The connection 2060 may be direct or may pass through a core network (not shown in Figure 20) of the telecommunications system and/or through one or more intermediate networks outside the telecommunications system. In the embodiments shown, hardware 2025 of base station 2020 additionally includes processing circuitry 2028, which may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not illustrated) adapted to carry out instructions. The 2020 base station additionally has 2021 software stored internally or accessible via an external connection.

[181] The 2000 communication system additionally includes the aforementioned EU 2030. Its hardware 2035 may include a radio interface 2037 configured to prepare and maintain a wireless connection 2070 with a base station serving a coverage area in which the UE 2030 currently locates. UE 2030 hardware 2035 further includes processing circuitry 2038, which may comprise one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not illustrated) adapted to perform instructions. The UE 2030 further comprises software 2031, which is stored in or accessible by the UE 2030 and executable by the processing circuitry 2038. The software 2031 includes the client application 2032. The client application 2032 may be operable to provide a service to a human or non-human user via the UE 2030, supported by the host computer 2010. On the host computer 2010, a running host application 2012 can communicate with the running client application 2032 via the OTT connection 2050 terminating at the UE 2030 and on the host computer 2010. In providing the service to the user, the client application 2032 may receive request data from the host application 2012 and provide the user data in response to the request data. The OTT 2050 connection can transfer both request data and user data. The client application 2032 may interact with the user to generate the user data it provides.

[182] It is noted that the host computer 2010, the base station 2020 and the UE 2030 illustrated in Figure 20 may be similar or identical to the host computer 1930, one of the base stations 1912a, 1912b, 1912c and one of the UEs 1991 , 1992 of Figure 19, respectively. That is, the internal workings of these entities may be as shown in Figure 20 and, independently, the topology of the surrounding network may be that of Figure 19.

[183] In Figure 20, the OTT connection 2050 has been abstractly drawn to illustrate the communication between the host computer 2010 and the user equipment 2030 through the base station 2020, without explicit reference to any intermediate devices and the precise routing of messages through these devices. The network infrastructure may determine routing, which may be configured to be hidden from the UE 2030, the service provider operating the host computer 2010, or both. While the OTT connection 2050 is active, the network infrastructure may additionally make decisions whereby it dynamically changes the routing (e.g. based on consideration of load balancing or network reconfiguration).

[184] The wireless connection 2070 between the UE 2030 and the base station 2020 is in accordance with the teachings of the embodiments described throughout this invention. One or more of the various embodiments enhances the performance of OTT services provided to the UE 2030 using the OTT connection 2050, wherein the wireless connection 2070 forms the last segment. More precisely, the teachings of these modalities can improve latency and thereby provide benefits such as decreased user waiting time and improved responsiveness.

[185] A measurement procedure may be provided for the purpose of monitoring the data rate, latency, and other factors improved by one or more modalities. Additionally, there may be optional network functionality to reconfigure the OTT connection 2050 between the host computer 2010 and the UE 2030 in response to variations in measurement results. The measurement procedure and/or network functionality for reconfiguring the OTT connection 2050 may be implemented in software 2011 of the host computer 2010, in software 2031 of the UE 2030, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 2050 passes; the sensors can participate in the measurement procedure by providing values of the monitored quantities exemplified above or by providing values of other physical quantities from which software 2011, 2031 can calculate or estimate the monitored quantities. Reconfiguration of the OTT 2050 connection may include message format, retransmission adjustments, preferred routing, etc.; the reconfiguration need not affect the base station 2020 and may be unknown or imperceptible to the base station 2020. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling, facilitating the host computer 2010 with measurements of throughput, propagation times, latency, and the like. The measurements can be implemented so that the software 2011, 2031 causes messages to be transmitted, particularly 'dummy' or empty messages, using an OTT connection 2050, while monitoring propagation times, errors, etc.

[186] Figure 21 is a flowchart illustrating a method implemented in a communication system, according to an embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 19 and 20. To simplify the present invention, only references in drawing to Figure 21 will be included in this section. In a first step 2110 of the method, the host computer provides user data. In an optional substep 2111 of the first step 2110, the host computer provides user data when executing a host application. In a second step 2120, the host computer initiates a transmission carrying the user data to the UE. In an optional third step 2130, the base station transmits to the UE the user data that was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this invention. In an optional fourth step 2140, the UE executes a client application associated with the host application executed by the host computer.

[187] Figure 22 is a flowchart illustrating a method implemented in a communication system, according to an embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 19 and 20. To simplify the present invention, only drawing references to Figure 22 will be included in this section. In a first step 2210 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides user data by running a host application. In a second step 2220, the host computer initiates a transmission carrying the user data to the UE. Transmission may pass through the base station in accordance with the teachings of the embodiments described throughout this invention. In an optional third step 2230, the UE receives the user data ported in the transmission.

[188] Figure 23 is a flowchart illustrating a method implemented in a communication system, according to an embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 19 and 20. To simplify the present invention, only drawing references to Figure 23 will be included in this section. In an optional first step 2310 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 2320, the UE provides user data. In an optional substep 2321 of the second step 2320, the UE provides user data when executing a client application. In an additional optional substep 2311 of the first step 2310, the UE executes a client application that provides user data in response to input data received and provided by the host computer. When providing user data, the executed client application may additionally consider user input received from the user. Regardless of the specific manner in which the user data is provided, the UE begins, in an optional third substep 2330, the transmission of the user data to the host computer. In a fourth step 2340 of the method, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this invention.

[189] Figure 24 is a flowchart illustrating a method implemented in a communication system, according to an embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 19 and 20. To simplify the present invention, only drawing references to Figure 24 will be included in this section. In an optional first step 2410 of the method, in accordance with the teachings of the embodiments described throughout this invention, the base station receives user data from the UE. In an optional second step 2420, the base station initiates transmission of the received user data to the host computer. In a third step 2430, the host computer receives the ported user data in the transmission initiated by the base station.

[190] The foregoing description of implementations provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings, or may be acquired from the practice of the invention.

[191] Aspects of the invention may also be embodied as computer program methods and/or products. Therefore, the invention can be embodied in hardware and/or in hardware/software (including firmware, resident software, microcode, etc.). Furthermore, embodiments may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embedded in the medium for use by or in connection with a instruction execution system. Such an instruction execution system can be implemented in a standalone or distributed manner. The actual software code or specialized control hardware used to implement embodiments described in the present invention is not limiting the invention. Thus, the operation and behavior of the aspects have been described without reference to specific software code, it being understood that those skilled in the art will be able to design software and control hardware to implement the aspects based on the description of the present invention.

[192] Furthermore, certain portions of the invention may be implemented as “logic” that performs one or more functions. This logic may include hardware, such as an application-specific integrated circuit or field-programmable gate array, or a combination of hardware and software.

[193] It should be emphasized that the term “comprises” when used in this specification is used to specify the presence of indicated characteristics, integers, steps, components or groups, but does not preclude the presence or addition of one or more other characteristics, integers, steps, components or groups thereof.

[194] No element, act or instruction used in the invention should be construed as critical or essential to the invention unless explicitly described as such. Furthermore, as used in the present invention, the article “a” is intended to include one or more items. When only one item is intended, the term “one” or similar language is used. Furthermore, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.

[195] The foregoing description only gives embodiments of the present invention and is not intended to limit the present invention in any way. Thus, any modification, substitution, improvement or the like made within the spirit and principle of the present invention must be encompassed by the scope of the present invention.

Claims (26)

1. Method (500; 600) in a network function entity for signaling Quality of Service, QoS, control parameters for a QoS Flow to a User Equipment, UE, characterized in that it comprises: generate ( S510), based on a PCC rule, one or more data flow rules associated with the QoS Flow, wherein each of the one or more data flow rules comprises specific parameters for a data flow associated with the QoS Flow. QoS; generating (S520) a QoS Stream profile for the QoS Stream, wherein the QoS stream profile comprises parameters that are common to all data streams associated with the same QoS Stream; and transmitting (S530) the one or more data flow rules and the QoS Flow profile to the UE, wherein, when a plurality of data flow rules associated with the same QoS flow are generated based on a plurality of data flow rules associated with the same QoS flow of PCC rules, a single QoS Flow profile including a common parameter for the plurality of data flow rules is transmitted to the UE. 2. Method (500; 600), according to claim 1, characterized by the fact that each of the one or more data flow rules is represented by an identifier that is distinguished from each other in which it is transmitted to the UE . 3. Method (500; 600), according to claim 1 or 2, characterized by the fact that each of the one or more data flow rules comprises parameters that are related to one or more Service Data Flow models , SDF, and/or one or more associated precedence values. 4. Method (500; 600), according to any one of claims 1 to 3, characterized by the fact that each of the one or more data flow rules and the QoS Flow profile comprises a QoS Flow identifier . 5. Method (500; 600), according to any one of claims 1 to 4, characterized by the fact that it further comprises: transmitting (S540) one or more data flow rules to the UE, to inform the UE to add one or more data flow rules to the QoS flow. 6. Method (500; 600), according to any one of claims 1 to 5, characterized by the fact that it further comprises: transmitting (S550) at least one parameter to the UE if the at least one parameter in the Data Flow profile QoS change from that in the previous QoS Flow profile, to allow the UE to update the at least one parameter in the QoS Flow profile to the QoS Flow. 7. Method (500; 600), according to any one of claims 1 to 6, characterized by the fact that it further comprises: transmitting (S640) an identifier of a data flow rule to the UE, to inform the UE to delete the data flow rule identified by the identifier. 8. Method (500; 600), according to any one of claims 1 to 7, characterized by the fact that it further comprises: transmitting (S650) a QoS Flow identifier to the UE if a data flow rule to be removed is the last one from the QoS Flow, to inform the UE to delete the QoS Flow profile for the QoS Flow and the last data flow rule. 9. Method (700) in a User Equipment, UE, for receiving parameters, characterized in that it comprises: receiving (S7) one or more data flow rules associated with a Quality of Service Flow, QoS, in which each of the one or more data flow rules is generated based on a PCC rule and comprises specific parameters for a data flow belonging to that QoS Flow; and receiving (S720) a QoS Stream profile for the QoS Stream, wherein the QoS Stream profile comprises parameters that are common to all data streams belonging to the same QoS Stream, wherein, when a plurality of data flow rules associated with the same QoS Flow are generated based on a plurality of PCC rules, a single QoS Flow profile including a common parameter for the plurality of data flow rules is received by the UE. 10. Method (700), according to claim 9, characterized by the fact that each of the one or more data flow rules is represented by an identifier that is distinguished from the other in which it is also received. 11. Method (700), according to claim 9 or 10, characterized by the fact that each of the one or more data flow rules and the QoS Flow profile comprises a QoS Flow identifier. Method (700) according to any one of claims 9 to 11, characterized in that it further comprises: receiving (S730) an identifier of a data flow rule; and delete (S740) the data flow rule. A method (700) according to any one of claims 9 to 11, characterized in that it further comprises: receiving (S750) a data flow rule only. 14. Method (700) according to any one of claims 9 to 11, characterized in that it additionally comprises: receiving (S770) an identifier of a QoS Flow; and delete (S780) the data flow rule and QoS Flow profile associated with the QoS Flow. 15. Method (700), according to any one of claims 9 to 14, characterized by the fact that it further comprises: receiving (S790) at least one parameter, and updating (S7100) the at least one parameter in the Data Flow profile QoS with the received parameter. 16. Network Function Entity, NF, (1200) in a network, characterized by the fact that it comprises: at least one processor (1203), and a memory (1205) comprising instructions that, when executed by at least one processor ( 1203), make the NF entity (1200): generate (S510), based on a PCC rule, one or more data flow rules associated with the QoS Flow, wherein each of the one or more flow rules data stream comprises specific parameters for a data stream that belongs to the QoS Stream; generating (S520) a QoS Flow profile for a UE for the QoS Flow, wherein the QoS Flow profile comprises parameters that are common to all data flows belonging to the same QoS Flow; and transmitting (S530) the one or more data flow rules and the QoS Flow profile to the UE, wherein, when a plurality of data flow rules associated with the same QoS Flow are generated based on a plurality of PCC rules, a single QoS Flow profile including a common parameter for the plurality of data flow rules is transmitted to the UE. 17. NF entity, according to claim 16, characterized by the fact that the instructions, when executed by at least one processor (1203), cause the NF entity (1200): transmit to one or more flow rules data to the UE, to inform the UE to add one or more data flow rules to the QoS flow. 18. NF entity, according to claim 16 or 17, characterized by the fact that the instructions, when executed by at least one processor (1203), cause the NF entity (1200): transmit a parameter to the UE if the parameter in the QoS Flow profile changes from that in the previous QoS Flow profile, to allow the UE to update the parameter in the QoS Flow profile for the QoS Flow. 19. NF entity, according to any one of claims 16 to 18, characterized by the fact that the instructions, when executed by at least one processor (1203), cause the NF entity (1200): transmit an identifier of a data flow rule to the UE, to inform the UE to delete the data flow rule identified by the identifier. 20. NF entity, according to any one of claims 16 to 19, characterized by the fact that the instructions, when executed by at least one processor (1203), cause the NF entity (1200): transmit a Stream identifier QoS profile for the UE if a data flow rule to be removed is at least one from the QoS Flow, to inform the UE to delete the QoS Flow profile for the QoS Flow and the last data flow rule. 21. User Equipment, UE, (1400), characterized by the fact that it comprises: at least one processor (1403), and a memory (1405) comprising instructions that, when executed by at least one processor (1403), do the UE (1400): receive (S710) one or more data flow rules associated with a QoS Flow, wherein each of the one or more data flow rules is generated based on a PCC rule and comprises specific parameters for a data stream that belongs to that QoS Stream; and receiving (S720) a QoS Stream profile for the QoS Stream, wherein the QoS Stream profile comprises parameters that are common to all data streams belonging to the same QoS Stream, wherein, when a plurality of data flow rules associated with the same QoS Flow are generated based on a plurality of PCC rules, a single QoS Flow profile including a common parameter for the plurality of data flow rules is received by the UE. 22. UE (1400), according to claim 21, characterized by the fact that the instructions, when executed by at least one processor (1403), cause the UE (1400) to additionally: receive an identifier of a flow rule data; and delete the data flow rule. 23. UE (1400), according to claim 21 or 22, characterized by the fact that the instructions, when executed by at least one processor (1403), cause the UE (1400) to additionally: receive a data flow rule just. 24. UE (1400), according to any one of claims 21 to 23, characterized by the fact that the instructions, when executed by at least one processor (1403), cause the UE (1400) to additionally: receive an identifier from a QoS flow; and delete the data flow rule and QoS Flow profile associated with the QoS Flow. 25. UE (1400), according to any one of claims 21 to 24, characterized by the fact that the instructions, when executed by at least one processor (1403), cause the UE (1400) to additionally: receive at least one parameter ; and updating the at least one parameter in the QoS Flow profile with the received parameter. 26. A computer-readable storage medium comprising instructions stored therein, the instructions, when executed by at least one processor in a device, cause the device to perform the method as defined in any one of claims 1 to 15.