Flexible handling of devices behind user equipment

Abstract

Systems, methods, apparatuses, and computer program products for flexible handling of devices behind a user equipment. A method may include establishing a communication connectivity with a network element. The method may also include receiving, from the network element, an indication including a device identifier information of a device connected to the network element behind a user equipment. The method may further include creating a quality of service flow between the user equipment and the network element based on the device identifier.

Description

TITLE:FLEXIBLE HANDLING OF DEVICES BEHIND USER EQUIPMENTFIELD:

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) new radio (NR) access technology, or 5G beyond, or sixth generation (6G) access technology, or other communications systems. For example, certain example embodiments may relate to apparatuses, systems, and / or methods for flexible handling of devices behind a user equipment (UE).BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE- Advanced (LTE-A), MulteFire, LTE-A Pro, fifth generation (5G) radio access technology or new radio (NR) access technology and / or sixth generation (6G) radio access technology. Fifth generation (5G) and sixth generation (6G) wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G network technology is mostly based on new radio (NR) technology, but the 5G network can also build on E-UTRAN radio. It is estimated that NR may provide bitrates on the order of 10-20 Gbit / s or higher, and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (IoT).SUMMARY:

[0003] Some example embodiments may be directed to a method. The method may include establishing a communication connectivity with a network element. The method may alsoinclude receiving, from the network element, a first indication including a device identifier information of a device connected to the network element behind a user equipment. The method may further include creating a quality of service flow between the user equipment and the network element based on the device identifier.

[0004] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory storing instructions that, when executed by a processor, cause the apparatus at least to establish a communication connectivity with a network element. The apparatus is also caused to receive, from the network element, a first indication including a device identifier information of a device connected to the network element behind the apparatus. The apparatus is further caused to create a quality of service flow between the user equipment and the network element based on the device identifier.

[0005] Other example embodiments may be directed to an apparatus. The apparatus may include means for establishing a communication connectivity with a network element. The apparatus may also include means for receiving, from the network element, a first indication including a device identifier information of a device connected to the network element behind the apparatus. The apparatus may further include means for creating a quality of service flow between the user equipment and the network element based on the device identifier.

[0006] In accordance with other example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include establishing a communication connectivity with a network element. The method may also include receiving, from the network element, a first indication including a device identifier information of a device connected to the network element behind a user equipment. The method may further include creating a quality of service flow between the user equipment and the network element based on the device identifier.

[0007] Other example embodiments may be directed to a computer program product that performs a method. The method may include establishing a communication connectivitywith a network element. The method may also include receiving, from the network element, a first indication including a device identifier information of a device connected to the network element behind a user equipment. The method may further include creating a quality of service flow between the user equipment and the network element based on the device identifier.

[0008] Other example embodiments may be directed to an apparatus that may include circuitry configured to establish a communication connectivity with a network element. The apparatus may also include circuitry configured to receive, from the network element, a first indication including a device identifier information of a device connected to the network element behind the apparatus. The apparatus may further include circuitry configured to create a quality of service flow between the user equipment and the network element based on the device identifier.

[0009] Further example embodiments may be directed to a method. The method may include establishing a communication connectivity with a user equipment. The method may also include transmitting, to the user equipment or a network element, a first indication including a device identifier information of a device behind the user equipment. The method may further include performing a communication transmission with the user equipment via a quality of service flow based on the device identifier.

[0010] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, with the at least one processor, cause the apparatus at least to establish a communication connectivity with a user equipment. The apparatus may also be caused to transmit, to the user equipment or a network element, a first indication including a device identifier information of a device behind the user equipment. The apparatus may further be caused to perform a communication transmission with the user equipment via a quality of service flow based on the device identifier.

[0011] Other example embodiments may be directed to an apparatus. The apparatus may include means for establishing a communication connectivity with a user equipment. Theapparatus may also include means for transmitting, to the user equipment or a network element, a first indication including a device identifier information of a device behind the user equipment. The apparatus may further include means for performing a communication transmission with the user equipment via a quality of service flow based on the device identifier.

[0012] In accordance with other example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include establishing a communication connectivity with a user equipment. The method may also include transmitting, to the user equipment or a network element, a first indication including a device identifier information of a device behind the user equipment. The method may further include performing a communication transmission with the user equipment via a quality of service flow based on the device identifier.

[0013] Other example embodiments may be directed to a computer program product that performs a method. The method may include establishing a communication connectivity with a user equipment. The method may also include transmitting, to the user equipment or a network element, a first indication including a device identifier information of a device behind the user equipment. The method may further include performing a communication transmission with the user equipment via a quality of service flow based on the device identifier.

[0014] Other example embodiments may be directed to an apparatus that may include circuitry configured to establish a communication connectivity with a user equipment. The apparatus may also include circuitry configured to transmit, to the user equipment or a network element, a first indication including a device identifier information of a device behind the user equipment. The apparatus may also include circuitry configured to perform a communication transmission with the user equipment via a quality of service flow based on the device identifier.BRIEF DESCRIPTION OF THE DRAWINGS:

[0015] For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0016] FIG. 1 illustrates an example arrangement of non-3rdGeneration Partnership Project (3GPP) devices behind a user equipment (UE).

[0017] FIG 2 illustrates an example protocol data unit (PDU) session communication.

[0018] FIG. 3 illustrates another example PDU session communication.

[0019] FIG. 4 illustrates an example signal diagram of a UE configuration update procedure.

[0020] FIG. 5 illustrates an example signal diagram, according to certain example embodiments.

[0021] FIG. 6 illustrates an example of a method, according to certain example embodiments.

[0022] FIG. 7 illustrates an example flow diagram of another method, according to certain example embodiments.

[0023] FIG. 8 illustrates a set of apparatuses, according to certain example embodiments.DETAILED DESCRIPTION:

[0024] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. The following is a detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for flexible handling of devices behind a UE.

[0025] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “an example embodiment,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic describedin connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “an example embodiment,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. Further, the terms “base station”, “cell”, “node”, “gNB”, “network” or other similar language throughout this specification may be used interchangeably. Additionally, although user equipment (UE) is discussed throughout, “UE” may also be treated as 5G-residential gateway (5G-RG).

[0026] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0027] FIG. 1 illustrates an example arrangement non-3GPP devices 100 behind a UE 105. As illustrated in FIG. 1, the devices 100 may be connected to the UE 105, which in turn is connected to the core network 115 (e.g., 5GC) which has a PDU session 110 established with the core network 115. As illustrated in FIG. 1, the core 115 should be able to identify traffic originating from the devices 100. According to the specifications of 3GPP, all UE / 5G-RG connected devices may be used at the same point of time. However, the devices 100 may not be authenticated individually by 3GPP. In some instances, it may be desirable for 5G Core (5GC) to identify traffic originated from individual non-3GPP devices 100 connected behind a UE 105 or 5G-residential gateway (5G-RG), and whether and how to provide policy control for the traffic associated with individual non-3GPP devices 100. To achieve this, the non-3GPP devices 100 traffic is (e.g., needs) to be identified, and it may be desirable to determine how an identifier(s) of a non-3GPP device 100 may be used by the core network 115 to control traffic to / from the UE 105 or 5G-RG when the traffic is associated with the non-3GPP devices 100. Thus, as described herein, certain example embodiments may provide a way to determine how an identifier of a device 100 may be used by the network to control traffic to / from the UE 105 or 5G-RG when the traffic isassociated with non-3GPP devices. Certain example embodiments may also be able to control the devices 100 by the core 115 and from inputs of an application function (AF). That is, in some example embodiments, each device of the devices 100 may benefit from (e.g., need) its own individual treatment. Certain example embodiments may also enable the core 115 to signal messages to the UE 105 for the UE to 105 to initiate individual QoS flows for a certain devices 100 that are active status while the other remaining devices 100 are not in active status. Additionally, in certain example embodiments, the UE 105 may receive an indication of which devices 100 are (e.g., need) to be treated differently (for e.g., under default QoS flows) based on the provisioning data that is available.

[0028] FIG. 2 illustrates an example PDU session communication, and FIG. 3 illustrates another example PDU session communication. According to 3GPP, all UE / 5G-RG connected devices 200, 300 may be used at the same point of time, and the devices 200, 300 are not individually authenticated by 3GPP. As also illustrated in FIGs. 2 and 3, there may be one or more PDU sessions; however, at least with one PDU session, all devices 200, 300 may access the network 215, 315. As illustrated in FIGs. 2 and 3, the core network 215, 315 may identify traffic of each device 200, 300 individually to allow policy control and differentiated QoS treatment for the selected device(s). As illustrated in FIG. 2, an individual PDU session may be established for a respective device 200 with the core network 215. However, in other instances, a single PDU session may be established for all devices 200, 300. Further, a PDU session may be established in non-roaming and roaming conditions with local breakout cases by establishing a new PDU session, handover of a PDN connection in an evolved packet system (EPS) to a PDU session in 5G system (5GS), switching an existing PDU session between non-3GPP access and 3GPP access, and requesting a PDU session for emergency services.

[0029] It may be desirable to determine how the 5GC identifies traffic of each device individually to allow policy control and differentiated QoS treatment for the selected devices. As illustrated in FIGs. 2 and 3, devices behind the UE may be treated differently by using an individual PDU Session for each of the connected devices, or using a single PDU session for all the connected devices, and potentially enabling different QoS flows.Thus, some example embodiments described herein may provide a way to determine the usage of individual QoS flows for the devices, by UE when the provided UE route selection policy (URSP) rules do not define rules for those device identifiers.

[0030] FIG. 4 illustrates an example signal diagram of a UE configuration update procedure. This procedure may be initiated when a policy control function (PCF) desires to update UE policy information (e.g., UE policy) in the UE configuration. At 420, the policy control function (PCF) 415 decides to update UE policy based on triggering conditions such as an initial registration, registration with 5GS when the UE moves from EPS to 5GS, or need for updating UE policy. At 425, if the PCF 415 has not subscribed to be notified by the access and mobility management function (AMF) 410 about the UE 400 response to an update of UE policy information, the PCF 415 subscribes to the AMF 410 to be notified about the UE 400 response to an update of UE policy information. At 430, the PCF 415 invokes Namf_Communication_NlN2MessageTransfer service operation provided by the AMF 410. In an example, the message may include a 5G subscription permanent identifier (SUPI), UE Policy Container.

[0031] At 435, if the UE 400 is registered and reachable by the AMF 410 in either 3 GPP access or non-3GPP access, the AMF 410 transparently transfers the UE Policy Container to the UE 400 via the registered and reachable access. If the UE is registered in both 3 GPP and non-3GPP accesses and reachable on both access and served by the same AMF 410, the AMF 410 transparently transfers the UE Policy Container to the UE 400 via one of the accesses based on the AMF 410 local policy. However, if the UE is not reachable by the AMF 410 over both 3GPP access and non-3GPP access, the AMF 410 reports to the PCF 415 that the UE Policy Container could not be delivered to the UE 400 using Namf_Communication_N lN2TransferFailureNotification. On the other hand, if the AMF 410 decides to transparently transfer the UE Policy Container to the UE 400 via 3 GPP access (e.g., the UE 400 is registered and reachable by AMF 410 in 3GPP access only), or if the UE 400 is registered and reachable by AMF 410 in both 3 GPP and non-3GPP accesses served by the same AMF 410, and the AMF 410 decides to transparently transfer the UE Policy Container to the UE 400 via 3GPP access based on local policy and the UEis in CM-IDLE and reachable by AMF 410 in 3 GPP access, the AMF 410 starts the paging procedure by sending a paging message. Upon reception of paging request, the UE 400 initiates a UE triggered service request procedure.

[0032] At 440, if the UE is in CM-CONNECTED over 3GPP access or non-3GPP access, the AMF 410 transparently transfers the UE Policy Container (UE policy information) received from the PCF 415 to the UE 400. At 445, the UE 400 updates the UE policy provided by the PCF 415, and sends the result to the AMF 410. At 450, the AMF 410 forwards the response of the UE 400 to the PCF 415 using Namf_Communication_N 1 MessageNotify .

[0033] According to 3GPP TS 23.503, the PCF may include UE policy information delivered to the UE into a policy section identified by a policy section identifier (PSI). The PCF may divide the UE policy information into different policy sections, each one identified by a PSI. Each policy section provides a list of self-contained UE policy information to the UE via the AMF. The PCF ensures that a policy section is under a predefined size limit known by the PCF. Examples of self-contained UE policy information may imply that when the PCF delivers UE route selection policy (URSP) rules to the UE, the PCF provides the list of URSP rules in the order of precedence and without splitting a URSP rule across policy sections. The self-contained UE policy information may also imply that when the PCF delivers V2XP to the UE, the PCF provides the list of V2XP in the order of precedence and without splitting a V2XP across policy sections. The self-contained UE policy information may further imply that when the PCF delivers ProSeP to the UE, the PCF provides the list of ProSeP in the order of precedence and without splitting a ProSeP across policy sections. The self-contained UE policy information may also imply that when the PCF delivers A2XP to the UE, the PCF provides the list of A2XP in the order of precedence and without splitting a A2XP across policy sections. The self-contained UE policy information may further imply that when the PCF delivers ranging / sidelink positioning policy (RSLPP) information to the UE, the PCF provides the list of RSLPP in the order of precedence and without splitting a RSLPP across policy sections. Additionally, the self-contained UE policy information may imply thatwhen the PCF delivers WLAN selection policy (WLANSP) rules, the list of WLANSP rules are provided in the order of priority and without splitting a WLANSP rule across policy sections. Furthermore, the self-contained UE policy information may imply that when the PCF delivers the non-3GPP access network selection information, the whole list of non-3GPP access network selection information is provided in one policy section.

[0034] When the provisioning data is available for a UE / 5G-RG related to device identifiers, the network may provide the URSP rules, which results in the individual PDU session per the corresponding device identifiers. When the URSP rules do not indicate an individual PDU session (based on the device identifiers IE or based on PIN ID IE or based on Connection Group IE of the URSP rule), or when the URSP rules indicate individual PDU session only for a few device identifiers, the UE may consider creating the individual QoS flows (with request for sub prefix / framed IP) for each of the rest of the devices not in the URSP rules. This results in the UE making a request for specific individual handling for each of the devices. Alternatively, the UE may use the default QoS flow for the rest of the devices not included in the URSP rules. However, this behavior leaves it to the UE implementation, which may benefit from (e.g. need) standardization where the network could indicate if the UE should use individual flows for each device (not indicated in the URSP). Alternatively, the network could indicate if the UE should use a default QoS flow for the rest of the devices.

[0035] It may be assumed that there may not be any signaling to 5GC for each device connecting behind a UE / 5G-RG. The devices sharing the same PDU session and using a default QoS of the PDU session may not trigger any signaling in 5GC. Considerations may be taken concerning mechanisms to optionally restrict, within the 5GS, the maximum number of simultaneously identifiable and by traffic QoS treatment differentiated active device identifiers per UE / 5G-RG.

[0036] As described herein, certain example embodiments may address the above- mentioned drawbacks by providing a new UE policy container (for e.g., named as device handling policy), which may include device identifiers that the UE may process to implement specific treatments. The treatments may include, but not limited to, forexample, providing individual QoS flow and associate sub prefixes based on certain priorities, time of applicability, and status. Based on the defined procedures, the UE may (based on provided parameters for each device behind the UE) implement individual QoS flows, and notify the network of the action the UE has taken. The network may then update the AF about the status of the action taken by the UE and the network. In certain example embodiments, the sub prefixes may correspond to an address used by a UE for a particular device as a network entity to route data packets.

[0037] FIG. 5 illustrates an example signal diagram, according to certain example embodiments. As illustrated in FIG. 5, at 530, identifiers of the non-3GPP device 500 and related policy parameters may be provided to the unified data repository (UDR) 520 by the AF 525 through a network exposure function (NEF). Alternatively, in other example embodiments, the identifiers of the non-3GPP devices 500 and related policy parameters may be provided to the UDR 520 by a provisioning system. According to certain example embodiments, the related policy parameters may include device (e.g., non-3GPP devices) identifier(s) corresponding to a permanent identifier (e.g., a generic string). The parameters may also include a device identifier state, which may include provisioned, active, or blocked. The different states may correspond to the configured / provisioned state (by the network / network operator / AF) of the individual device identifier. When the non- 3GPP device 500 may be in the provisioned state, the non-3GPP device 500 is simply programmed in the network. Under the provisioned state, the network may send an indication to the UE 505 indicating that it is just a provision state, and the UE 505 refrains from requesting individual treatment for the non-3GPP device 500 in provisioned state. However, in the active state, the network may indicate to the UE 505 that the UE 505 can initiate individual QoS flows for that particular device identifier, which has an active status. On the other hand, when the non-3GPP device 500 is in the blocked state, the non-3GPP devices 500 are blocked for access, and no individual treatment is performed / requested for the non-3GPP devices 500.

[0038] According to certain example embodiments, operator policies and an AF request may implement the state as “provisioned” initially. The parameters may also include adevice identifier priority, which indicates a priority level such as, for example, high, medium, or low. In certain example embodiments, the device identifier priority may be applicable when there is a benefit (e.g., a need) to limit the maximum number of devices 500, which are obliged to differentiated QoS treatment. In some example embodiments, the benefit (e.g., the need) to limit the maximum number of QoS differentiated device identifiers may be determined based on the limited capabilities (e.g., processing load, usable memory etc.) of handling at the UE. In other example embodiments, the parameters may include time period(s) for the specific state of the device identifier (e.g., provisioned, active, or blocked). The time periods during which the specific state is (e.g., needs) to be used may be defined as a time range such as, for example, between 8:00 PM and 9:00 PM, during which devices 1 and 2 may be handled with the individual QoS flows, and during other hours using a default QoS flow for them.

[0039] At 535, a PDU session is established with the network (e.g., SMF 515, UPF, AMF 510, UDR / PCF 120, and / or AF 525). The network may provide a shorter prefix than / 64 prefix, and the PDU session may also provide an indication to the UE 505 of which device identifiers of the non-3GPP device(s) 500 that the UE 505 can use (if the state of “active” is indicated) in the network. At 540, the UE 505 may transmit a request to the network to change the status for a certain device identifier. At 545, the AF 525 updates the state(s) and priority for one or more device identifiers. The AF 525 may also implement a change of the state and priorities of the non-3GPP devices 500 based on internal mechanisms (e.g., application level mechanisms out of 3 GPP) and / or a request from a device of the user equipment subscriber.

[0040] At 550, the UDR 520 triggers the PCF 520 about changed device identifiers with regard to the device identifiers’ status and / or priority, and the PCF 520 indicates the status change to the SMF 515. At 555, the PCF 520 initiates a UE policy update and includes the UE policy information. For example, the PCF 520 may initiate a UE configuration update procedure for transparent UE policy delivery request with the new UE policy container type (e.g., device handling policy). That is, the network indicates to the UE 505 of the device identifiers that the UE 505 can use, and indicates to the UE 505 the correspondingstates and priority of the device identifiers.

[0041] At 560, the UE 505 provides a policy delivery response to the network based on the applied actions on priorities with the UE policy container e.g., device handling policy) status for the network to re-assign different policies in the future. According to certain example embodiments, the UE 505 may enforce the policies provided by the network by implementing specific treatment such as, for example, providing individual QoS flow and associating the sub prefixes, based on priorities, time, and status. As described herein, the priorities may relate to handling the device identifiers. For instance, in certain example embodiments, the priorities may prioritize the devices whose traffic is (e.g., needs) to be differentiated. In other example embodiments, the priorities may be utilized in case a QoS control is requested for the presence of too many devices behind the UE 505, and there is a benefit (e.g., need) to limit the maximum number of such simultaneously active device identifiers per the UE / 5G-RG.

[0042] At 565, if the device identifier policy (e.g., change of state) requires, the UE 505 may request a PDU session modification procedure with individual QoS flows and sub prefixes. In other words, the UE 505 may request a different QoS flow for handling individual device traffic based on the associated sub prefix or a framed address. In certain example embodiments, under the PDU session modification procedure, the UE 505 may submit a request to the network for different QoS flows based on a range of the sub prefixes (from the short prefix), or from a framed IP address (e.g., framed Ipv4 address) allocated to the UE 505. At 570, the network notifies / updates the AF 525 about the status of the action taken by the UE 505 and the network related to the requested device handling policy. In some example embodiments, the action of the network may include notifying the AF 525 about the UE 505 establishing the device specific QoS flows (which may be subject to priorities vs UE capabilities), and overall success of the AF 525 requested device traffic differentiation.

[0043] FIG. 6 illustrates an example flow diagram of a method, according to certain example embodiments. In an example embodiment, the method of FIG. 6 may be performed by a UE similar to one of apparatuses 10 or 20 illustrated in FIG. 8. The methodof FIG. 6 is not limited to the order or the steps as illustrated, and may include less or additional steps described herein.

[0044] According to certain example embodiments, the method of FIG. 6 may include, at 600, establishing a communication connectivity with a network element. The method may also include, at 605, receiving, from the network element, a first indication including a device identifier information of a device connected to the network element behind a user equipment. The method may further include, at 610, creating a quality of service flow between the user equipment and the network element based on the device identifier.

[0045] According to certain example embodiments, the device identifier information comprises a device identifier and at least one of a status of the device, wherein the status comprises provisioned, active, or blocked, a priority of the device whose traffic is (e.g. needs) to be differentiated, or a time period during which a specific state of the device is (e.g., needs) to be used. According to some example embodiments, the priority of the device may assist limiting the maximum number of simultaneously active device identifiers, whose traffic is differentiated. According to other example embodiments, when the status of the device is active, the first indication defines the device identifier can be used.

[0046] In certain example embodiments, the method may also include enforcing user equipment policies by considering individual quality of service flow and associating a sub prefix for the corresponding identifier of the device. In some example embodiments, the method may further include requesting a protocol data unit session modification procedure with individual quality of service flows and the associated sub prefix when an identifier policy of the device indicates a change of a state of the device. In other example embodiments, the method may include requesting a different quality of service flow based on the associated sub prefix or a framed address. In further example embodiments, the method may include notifying a different network element of the status of the enforcement of the requested action for the devices between the user equipment and the network element. Additionally, in some example embodiments, the method may include receiving, from the network element, a second indication identifying which identifiers of a pluralityof devices can be used by the user equipment.

[0047] FIG. 7 illustrates an example flow diagram of another method, according to certain example embodiments. In an example embodiment, the method of FIG. 7 may be performed by a network entity, or a group of multiple network elements in a 3 GPP system, such as LTE or 5G-NR. For instance, in an example embodiment, the method of FIG. 7 may be performed by a gNB or network, similar to one of apparatuses 10 or 20 illustrated in FIG 8. The method of FIG. 7 is not limited to the order or the steps as illustrated, and may include less or additional steps described herein.

[0048] According to certain example embodiments, the method of FIG. 7 may include, at 700, establishing a communication connectivity with a user equipment. The method may also include, at 705, transmitting, to the user equipment or a network element, a first indication including a device identifier information of a device behind the user equipment. The method may further include, at 710, performing a communication transmission with the user equipment via a quality of service flow based on the device identifier.

[0049] According to certain example embodiments, the device identifier information may include a device identifier and at least one of a status of the device, wherein the status comprises provisioned, active, or blocked, a priority of the device whose traffic is (e.g., needs) to be differentiated, or a time period during which a specific state of the device is (e.g., needs) to be used. According to some example embodiments, the priority of the device defines the priority amongst various device identifiers that the user equipment has to choose to implement limited device accesses for individual quality of service flows. According to other example embodiments, when the status of the device is active, the first indication defines the device identifier can be used. According to further example embodiments, the method may also include receiving, from the user equipment, a request of a protocol data unit session modification procedure with individual quality of service flows and the associated sub prefix when an identifier policy of the device indicates a change of a state of the device.

[0050] In certain example embodiments, the method may also include receiving, from the user equipment, a request for a different quality of service flow based on the associated subprefix or a framed address. In some example embodiments, the method may further include, in response to receiving the request, updating a logical network element of a communication network about a status of action taken by the user equipment and a network element related to a device identifier. In other example embodiments, the method may also include transmitting, to the user equipment, a second indication identifying which identifiers of a plurality of devices can be used by the user equipment.

[0051] FIG. 8 illustrates a set of apparatuses 10 and 20 according to certain example embodiments. In certain example embodiments, apparatuses 10 and 20 may be elements in a communications network or associated with such a network. For example, apparatus 10 may be a UE or other similar radio communication computer device, and apparatus 20 may be a network (i.e., gNB).

[0052] In some example embodiments, apparatuses 10 and 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and / or a user interface. In some example embodiments, apparatuses 10 and 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatuses 10 and 20 may include components or features not shown in FIG. 8.

[0053] As illustrated in the example of FIG. 8, apparatuses 10 and 20 may include or be coupled to a processors 12 and 22 for processing information and executing instructions or operations. Processors 12 and 22 may be any type of general or specific purpose processor. In fact, processors 12 and 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, DSPs, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multicore processor architecture, as examples. While a single processors 12 and 22 is shown in FIG. 8, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatuses 10and 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processors 12 may represent a multiprocessor) that may support multiprocessing. According to certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0054] Processors 12 and 22 may perform functions associated with the operation of apparatuses 10 and 20 including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatuses 10 and 20, including processes and examples illustrated in FIGs. 1-7.

[0055] Apparatuses 10 and 20 may further include or be coupled to a memories 14 and 24 (internal or external), which may be respectively coupled to processors 12 and 22 for storing information and instructions that may be executed by processors 12 and 22. Memories 14 and 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and / or removable memory. For example, memories 14 and 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non- transitory machine or computer readable media. The instructions stored in memories 14 and 24 may include program instructions or computer program code that, when executed by processors 12 and 22, enable the apparatuses 10 and 20 to perform tasks as described herein.

[0056] In certain example embodiments, apparatuses 10 and 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processors 12 and 22 and / or apparatuses 10 and 20 to perform any of the methods and examples illustrated in FIGs. 1-7.

[0057] In some example embodiments, apparatuses 10 and 20 may also include or be coupled to one or more antennas 15 and 25 for receiving a downlink signal and for transmitting via an UL from apparatuses 10 and 20. Apparatuses 10 and 20 may further include a transceivers 18 and 28 configured to transmit and receive information. The transceivers 18 and 28 may also include a radio interface (e.g., a modem) coupled to the antennas 15 and 25. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an UL.

[0058] For instance, transceivers 18 and 28 may be configured to modulate information on to a carrier waveform for transmission by the antennas 15 and 25 and demodulate information received via the antenna 15 and 25 for further processing by other elements of apparatuses 10 and 20. In other example embodiments, transceivers 18 and 28 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 10 may include an input and / or output device (I / O device). In certain example embodiments, apparatuses 10 and 20 may further include a user interface, such as a graphical user interface or touchscreen.

[0059] In certain example embodiments, memories 14 and 34 store software modules that provide functionality when executed by processors 12 and 22. The modules may include, for example, an operating system that provides operating system functionality for apparatuses 10 and 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatuses 10 and 20. The components of apparatuses 10 and 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to certain example embodiments, apparatuses 10 and 20 may optionally be configured to communicate eachother (in any combination) via a wireless or wired communication links 70 according to any radio access technology, such as NR.

[0060] According to certain example embodiments, processors 12 and 22 and memories 14 and 24 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceivers 18 and 28 may be included in or may form a part of transceiving circuitry.

[0061] For instance, in certain example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to establish a communication connectivity with a network element. Apparatus 10 may also be controlled by memory 14 and processor 12 to receive, from the network element, a first indication including a device identifier information of a device connected to the network element behind the apparatus. Apparatus 10 may further be controlled by memory 14 and processor 12 to create a quality of service flow between the apparatus and the network element based on the device identifier.

[0062] In other example embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to establish a communication connectivity with a user equipment. Apparatus 20 may also be controlled by memory 24 and processor 22 to transmit, to the user equipment or a network element, a first indication including a device identifier information of a device behind the user equipment. Apparatus 20 may further be controlled by memory 24 and processor 22 to perform a communication transmission with the user equipment via a quality of service flow based on the device identifier.

[0063] In some example embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for causing the performance of the operations.

[0064] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for establishing a communication connectivity with a user equipment. The apparatus may also include means for transmitting, to the user equipment or a network element, a firstindication including a device identifier information of a device behind the user equipment. The apparatus may further include means for performing a communication transmission with the user equipment via a quality of service flow based on the device identifier.

[0065] Other example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for transmitting a communication connectivity with a network element. The apparatus may also include means for receiving, from the network element, a first indication including a device identifier information of a device connected to the network element behind the apparatus. The apparatus may further include means for creating a quality of service flow between the apparatus and the network element based on the device identifier.

[0066] Certain example embodiments described herein provide several technical improvements, enhancements, and / or advantages. For instance, in some example embodiments, it may be possible to for the UE to implement individual QoS flows based on the state, priority, and time periods defined by the network provided for each device behind the UE and, thus, enable differentiated priority services for the devices based on their needs (e.g., individual or collective), also in the timely manner (e.g. time of the day). Certain example embodiments may also enable the UE to limit the number of devices to which it provides the QoS differentiation based on the defined priorities and its own capabilities. The UE may also implement and notify the network concerning the action that the UE has taken for the network to potentially re-assign different policies. Additionally, the network may update the AF concerning the status of the action taken by the UE and the network.

[0067] A computer program product may include one or more computer-executable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of certain example embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

[0068] As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and / or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power to be utilized (e.g., needed), the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0069] In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus 10 or apparatus 20), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0070] According to certain example embodiments, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

[0071] One having ordinary skill in the art will readily understand that the disclosure as discussed above may be practiced with procedures in a different order, and / or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the disclosure has been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments. Although the above embodiments refer to 5GNR and LTE technology, the above embodiments may also apply to any other present or future 3GPP technology, such as LTE-advanced, and / or fourth generation (4G) technology.

[0072] Partial Glossary:

[0073] 3GPP 3rd Generation Partnership Project

[0074] 5G 5th Generation

[0075] 5GCN 5G Core Network[0076J 5G-RG 5G Residential Gateway

[0077] 5GS 5G System

[0078] BS Base Station

[0079] DCI Donwlink Control Indication

[0080] DL Downlink

[0081] eNB Enhanced Node B

[0082] E-UTRAN Evolved UTRAN

[0083] gNB 5G or Next Generation NodeB

[0084] LTE Long Term Evolution

[0085] MCS Modulation and Coding Scheme

[0086] NR New Radio

[0087] QoS Quality of Service

[0088] RRC Radio Resource Control

[0089] RS Reference Signal

[0090] UCI Uplink Control Information

[0091] UDR Unified Data Repository

[0092] UE User Equipment

[0093] UL Uplink

Claims

23WE CLAIM:

1. A method, comprising: establishing a communication connectivity with a network element; receiving, from the network element, a first indication comprising a device identifier information of a device connected to the network element behind a user equipment; and creating a quality of service flow between the user equipment and the network element based on the device identifier.

2. The method according to claim 1, wherein the device identifier information comprises a device identifier and at least one of the following: a status of the device, wherein the status comprises provisioned, active, or blocked, a priority of the device whose traffic is to be differentiated, or a time period during which a specific state of the device is to be used.

3. The method according to claim 2, wherein the priority of the device assists limiting the maximum number of simultaneously active device identifiers, whose traffic is differentiated.

4. The method according claim 2, wherein when the status of the device is active, the first indication defines the device identifier can be used.

5. The method according to any of claims 1-4, further comprising: enforcing user equipment policies by considering individual quality of service flow and associating a sub prefix for the corresponding identifier of the device.

6. The method according to any of claims 1-5, further comprising: requesting a protocol data unit session modification procedure with individual quality of service flows and the associated sub prefix when an identifier policy of the deviceindicates a change of a state of the device.

7. The method according to claim 6, further comprising: requesting a different quality of service flow based on the associated sub prefix or a framed address.

8. The method according to any of claims 1-7, further comprising: notifying a different network element of the status of the enforcement of the requested action for the devices between the user equipment and the network element.

9. The method according to any of claims 1-8, further comprising: receiving, from the network element, a second indication identifying which identifiers of a plurality of devices can be used by the user equipment.

10. A method, comprising: establishing a communication connectivity with a user equipment; transmitting, to the user equipment or a network element, a first indication comprising a device identifier information of a device behind the user equipment; and performing a communication transmission with the user equipment via a quality of service flow based on the device identifier.

11. The method according to claim 10, wherein the device identifier information comprises a device identifier and at least one of the following: a status of the device, wherein the status comprises provisioned, active, or blocked, a priority of the device whose traffic is to be differentiated, or a time period during which a specific state of the device is to be used.

12. The method according to claim 11, wherein the priority of the device defines the priority amongst various device identifiers that the user equipment has to choose toimplement limited device accesses for individual quality of service flows.

13. The method according to claim 11 , wherein when the status of the device is active, the first indication defines the device identifier can be used.

14. The method according to any of claims 10-13, further comprising: receiving, from the user equipment, a request of a protocol data unit session modification procedure with individual quality of service flows and the associated sub prefix when an identifier policy of the device indicates a change of a state of the device.

15. The method according to claim 14, further comprising: receiving, from the user equipment, a request for a different quality of service flow based on the associated sub prefix or a framed address.

16. The method according to claim 15, further comprising: in response to receiving the request, updating a logical network element of a communication network about a status of action taken by the user equipment and a network element related to a device identifier.

17. The method according to any of claims 10-16, further comprising: transmitting, to the user equipment, a second indication identifying which identifiers of a plurality of devices can be used by the user equipment.

18. An apparatus, comprising: at least one processor; and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to: establish a communication connectivity with a network element; receive, from the network element, a first indication comprising a device identifier26 information of a device connected to the network element behind the apparatus; and create a quality of service flow between the apparatus and the network element based on the device identifier.

19. The apparatus according to claim 18, wherein the device identifier information comprises a device identifier and at least one of the following: a status of the device, wherein the status comprises provisioned, active, or blocked, a priority of the device whose traffic is to be differentiated, or a time period during which a specific state of the device is to be used.

20. The apparatus according to claim 19, wherein the priority of the device assists limiting the maximum number of simultaneously active device identifiers, whose traffic is differentiated.

21. The apparatus according claim 19, wherein when the status of the device is active, the first indication defines the device identifier can be used.

22. The apparatus according to any of claims 18-21, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to: enforce user equipment policies by considering individual quality of service flow and associating a sub prefix for the corresponding identifier of the device.

23. The apparatus according to any of claims 18-22, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to: request a protocol data unit session modification procedure with individual quality of service flows and the associated sub prefix when an identifier policy of the device indicates a change of a state of the device.2724. The apparatus according to claim 23, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to: request a different quality of service flow based on the associated sub prefix or a framed address.

25. The apparatus according to any of claims 18-24, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to: notify a different network element of the status of the enforcement of the requested action for the devices between the apparatus and the network element.

26. The apparatus according to any of claims 18-25, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to: receive, from the network element, a second indication identifying which identifiers of a plurality of devices can be used by the apparatus.

27. An apparatus, comprising: at least one processor; and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to: establish a communication connectivity with a user equipment; transmit, to the user equipment or a network element, a first indication comprising a device identifier information of a device behind the user equipment; and perform a communication transmission with the user equipment via a quality of service flow based on the device identifier.

28. The apparatus according to claim 27, wherein the device identifier information comprises a device identifier and at least one of the following: a status of the device, wherein the status comprises provisioned, active, or blocked, a priority of the device whose traffic is to be differentiated, or28 a time period during which a specific state of the device is to be used.

29. The apparatus according to claim 28, wherein the priority of the device defines the priority amongst various device identifiers that the user equipment has to choose to implement limited device accesses for individual quality of service flows.

30. The apparatus according to claim 28, wherein when the status of the device is active, the first indication defines the device identifier can be used.

31. The apparatus according to any of claims 27-30, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to: receive, from the user equipment, a request of a protocol data unit session modification procedure with individual quality of service flows and the associated sub prefix when an identifier policy of the device indicates a change of a state of the device.

32. The apparatus according to claim 31, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to: receive, from the user equipment, a request for a different quality of service flow based on the associated sub prefix or a framed address.

33. The apparatus according to claim 32, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to: in response to receiving the request, update a logical network element of a communication network about a status of action taken by the user equipment and a network element related to a device identifier.

34. The apparatus according to any of claims 27-33, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to: transmit, to the user equipment, a second indication identifying which identifiers of29 a plurality of devices can be used by the user equipment.

35. A non- transitory computer readable medium comprising program instructions stored thereon for performing the method according to any of claims 1-17.

36. An apparatus comprising circuitry configured to cause the apparatus to perform a process according to any of claims 1-17.

37. An apparatus comprising means for performing the method according to any of claims 1-17

Images