Apparatuses, methods, and computer programs relating to a connection of one or more non-3GPP devices to a network

Abstract

A terminal comprising: means for receiving (3) a session modification command from a network entity of a network, the session modification command indicating that a first non-3GPP device, connected to the network via a session between the network and the terminal, is at least one of no longer authorized or no longer available to access the network via the terminal; and means for sending (4a) a session modification request to the network entity of the network for modifying the session between the terminal and the network, such that said session can continue without traffic associated with the first non-3GPP device.

Description

APPARATUSES, METHODS, AND COMPUTER PROGRAMS RELATING TO A CONNECTION OF ONE OR MORE NON-3GPP DEVICES TO A NETWORKTECHNICAL FIELD

[0001] Various embodiments of this disclosure relate to methods, apparatuses, and computer programs, and - in particular, but not exclusively - to methods, apparatuses (e.g., terminals), and computer programs for connection of one or more non-3GPP devices to a network.BACKGROUND

[0002] A communication network can be seen as a facility that enables communications between two or more communication devices or provides communication devices access to a data network. A mobile or wireless communication network is one example of a communication network. A communication device may be provided with a service by an application server.

[0003] Such communication networks operate in according with standards such as those provided by 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of standards include the so-called 5G (5th Generation) standards and 6G (6th Generation) standards promulgated by 3GPP.SUMMARY

[0004] Some embodiments of this disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the embodiments of this disclosure, nor are they intended to be used to limit the scope of thereof. Other features, aspects, and elements will be readily apparent to a person skilled in the art in view of this disclosure.

[0005] According to a first aspect, there is provided a terminal comprising: means for sending a session request to a network entity of a network for requesting connection of a first non-3GPP device to the network via the terminal, said session request comprising identity information associated with an identity of the first non-3GPP device; and means for receiving, from the network, a response to the session request, said response to the session request rejecting the request for the connection of the first non-3GPP device to the network via the terminal, based on the first non-3GPP device being at least one of not authorized or not available to access the network via the terminal, said response to the session request indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0006] The session request may comprise a session establishment request or a session modification request.

[0007] The response to the session request may comprise information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0008] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise a rejection code associated with the first non-3GPP device.

[0009] The response to the session request may comprise the identity information of the first non-3GPP device.

[0010] The response to the session request may indicate that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal by omitting the identity information associated with the first non-3GPP device.

[0011] The terminal may comprise means for sending a request to the network requesting that the identity of the first non-3GPP device be added as at least one of an authorized or an available non-3GPP device associated with the terminal.

[0012] The terminal may comprise means for delaying a further session request associated with the first non-3GPP device by at least a first time period.

[0013] The terminal may comprise means for preventing a sending of a further session request associated with the first non-3GPP device.

[0014] The session request may further be for requesting connection of at least one further non-3GPP device to the network via the terminal, said session request further comprising identity information associated with each of the at least one further non-3GPP device.

[0015] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device, based on one or more of the at least one further non-3GPP device being at least one of not authorized or not available to access the network via the terminal.

[0016] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device that are at least one of authorised or available to access the network via the terminal, and does not comprise the respective identity information associated with one or more of the at least one further non-3GPP device that are at least one of not authorised or not available to access the network via the terminal.

[0017] The terminal may be implemented as a user equipment or provided in a user equipment.

[0018] According to a second aspect, there is provided a method comprising: sending a session request to a network entity of a network for requesting connection of a first non-3GPP device to the network via a terminal, said session request comprising identity information associated with an identity of the first non-3GPP device; and receiving, from the network, a response to the session request, said response to the session request rejecting the request for the connection of the first non-3GPP device to the network via the terminal, based on the first non-3GPP device being at least one of not authorized or not available to access the network via the terminal, said response to the session request indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0019] The session request may comprise a session establishment request or a session modification request.

[0020] The response to the session request may comprise information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0021] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise a rejection code associated with the first non-3GPP device.

[0022] The response to the session request may comprise the identity information of the first non-3GPP device.

[0023] The response to the session request may indicate that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal by omitting the identity information associated with the first non-3GPP device.

[0024] The method may comprise sending a request to the network requesting that the identity of the first non-3GPP device be added as at least one of an authorized or an available non-3 GPP device associated with the terminal.

[0025] The method may comprise delaying a further session request associated with the first non-3GPP device by at least a first time period.

[0026] The method may comprise preventing a sending of a further session request associated with the first non-3GPP device.

[0027] The session request may further be for requesting connection of at least one further non-3GPP device to the network via the terminal, said session request further comprising identity information associated with each of the at least one further non-3GPP device.

[0028] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device, based onsaid one or more of the at least one further non-3GPP device being at least one of not authorized or not available to access the network via the terminal.

[0029] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device that are at least one of authorised or available to access the network via the terminal, and does not comprise the respective identity information associated with one or more of the at least one further non-3GPP device that are at least one of not authorised or not available to access the network via the terminal.

[0030] The method may be performed by an apparatus (e.g., the terminal).

[0031] The terminal may be implemented as a user equipment or provided in a user equipment.

[0032] The apparatus may comprise means to perform the method.

[0033] The apparatus may comprise at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform any one of the methods of the second aspect.

[0034] According to a third aspect, there is provided an apparatus comprising: means for receiving a session request from a terminal requesting connection of a first non-3GPP device to a network via the terminal, said session request comprising identity information associated with an identity of the first non-3GPP device; and means for sending, to the terminal, a response to the session request, said response to the session request rejecting the request for the connection of the first non-3GPP device to the network via the terminal, based on the first non-3 GPP device being at least one of not authorized or not available to access the network via the terminal, said response to the session request indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0035] The session request may comprise a session establishment request or a session modification request.

[0036] The response to the session request may comprise information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0037] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise a rejection code associated with the first non-3GPP device.

[0038] The response to the session request may comprise the identity information of the first non-3GPP device.

[0039] The response to the session request may indicate that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal by omitting the identity information associated with the first non-3GPP device.

[0040] The session management function may comprise means for receiving a request from the terminal requesting that the identity of the first non-3GPP device be added as at least one of an authorized or an available non-3GPP device associated with the terminal.

[0041] The session request may further be for requesting connection of at least one further non-3GPP device to the network via the terminal, said session request further comprising identity information associated with each of the at least one further non-3GPP device.

[0042] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device, based on said one or more of the at least one further non-3GPP device being at least one of not authorized or not available to access the network via the terminal.

[0043] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device that are at least one of authorised or available to access the network via the terminal, and does not comprise the respective identity information associated with one or more of the at least one further non-3GPP device that are at least one of not authorised or not available to access the network via the terminal.

[0044] The apparatus may comprise a session management function.

[0045] The apparatus may be configured to provide a session management function.

[0046] According to a fourth aspect, there is provided a method comprising: receiving a session request from a terminal requesting connection of a first non-3GPP device to a network via the terminal, said session request comprising identity information associated with an identity of the first non-3GPP device; and sending, to the terminal, a response to the session request, said response to the session request rejecting the request for the connection of the first non-3GPP device to the network via the terminal, based on the first non-3GPP device being at least one of not authorized or not available to access the network via the terminal, said response to the session request indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0047] The session request may comprise a session establishment request or a session modification request.

[0048] The response to the session request may comprise information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0049] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise a rejection code associated with the first non-3GPP device.

[0050] The response to the session request may comprise the identity information of the first non-3GPP device.

[0051] The response to the session request may indicate that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal by omitting the identity information associated with the first non-3GPP device.

[0052] The method may comprise receiving a request from the terminal requesting that the identity of the first non-3GPP device be added as at least one of an authorized or an available non-3GPP device associated with the terminal.

[0053] The session request may further be for requesting connection of at least one further non-3GPP device to the network via the terminal, said session request further comprising identity information associated with each of the at least one further non-3GPP device.

[0054] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device, based on said one or more of the at least one further non-3GPP device being at least one of not authorized or not available to access the network via the terminal.

[0055] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device that are at least one of authorised or available to access the network via the terminal, and does not comprise the respective identity information associated with one or more of the at least one further non-3GPP device that are at least one of not authorised or not available to access the network via the terminal.

[0056] The method may be performed by an apparatus.

[0057] The apparatus may comprise a session management function.

[0058] The apparatus may be configured to provide a session management function.

[0059] The apparatus may comprise means to perform the method.

[0060] The apparatus may comprise at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform any one of the methods of the fourth aspect.

[0061] According to a fifth aspect, there is provided a terminal comprising: means for receiving a session modification command from a network entity of a network, the session modification command indicating that a first non-3GPP device, connected to the network via a session between the network and the terminal, is at least one of no longer authorized or no longer available to access the network via the terminal; and means for sending a session modification request to the network entity of the network for modifying the session between the terminal and the network, such that said session can continue without traffic associated with the first non-3GPP device.

[0062] The session modification command may comprise information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0063] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise identity information associated with the first non-3GPP device.

[0064] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise a rejection code associated with the first non-3GPP device.

[0065] The session modification command may not include identity information associated with the first non-3GPP device to indicate to the terminal that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0066] The terminal may comprise means for delaying a sending of a session request associated with the first non-3GPP device by a least a first time period after the sending of the session modification request.

[0067] The terminal may comprise means for preventing a sending of a session request associated with the first non-3GPP device after the sending of the session modification request.

[0068] The terminal may comprise means for sending a request to the network requesting that the identity of the first non-3GPP device be added as at least one of an authorized or an available non-3GPP device associated with the terminal.

[0069] The session may be used by a plurality of non-3GPP devices, and the session modification command may indicate one or more of the plurality of non-3GPP devices are at least one of no longer authorised or no longer available to access the network via the terminal.

[0070] The session modification command may comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of no longer authorized or no longer available to access the network via the terminal.

[0071] The session modification command may comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of authorized or available to access the network via the terminal, and does not comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of no longer authorised or no longer available to access the network via the terminal.

[0072] The terminal may be implemented as a user equipment or provided in a user equipment.

[0073] According to a sixth aspect, there is provided a method comprising: receiving a session modification command from a network entity of a network, the session modification command indicating that a first non-3GPP device, connected to the network via a session between the network and a terminal, is at least one of no longer authorized or no longer available to access the network via the terminal; and sending a session modification request to the network entity of the network for modifying the session between the terminal and the network, such that said session can continue without traffic associated with the first non-3GPP device.

[0074] The session modification command may comprise information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0075] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise identity information associated with the first non-3GPP device.

[0076] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise a rejection code associated with the first non-3GPP device.

[0077] The session modification command may not include identity information associated with the first non-3GPP device to indicate to the terminal that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal

[0078] The method may comprise delaying a sending of a session request associated with the first non-3GPP device by a least a first time period after the sending of the session modification request.

[0079] The method may comprise preventing a sending of a session request associated with the first non-3GPP device after the sending of the session modification request.

[0080] The method may comprise sending a request to the network requesting that the identity of the first non-3GPP device be added as at least one of an authorized or an available non-3 GPP device associated with the terminal.

[0081] The session may be used by a plurality of non-3GPP devices, and the session modification command may indicate one or more of the plurality of non-3GPP devices are at least one of no longer authorised or no longer available to access the network via the terminal.

[0082] The session modification command may comprise respective identity information associated with one or more of the plurality of non-3GPP devices which are at least one of no longer authorized or no longer available to access the network via the terminal.

[0083] The session modification command may comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of authorized or available to access the network via the terminal, and does not comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of no longer authorised or no longer available to access the network via the terminal.

[0084] The method may be performed by an apparatus (e.g., the terminal).

[0085] The terminal may be implemented as a user equipment or provided in a user equipment.

[0086] The apparatus may comprise means to perform the method.

[0087] The apparatus may comprise at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform any one of the methods of the sixth aspect.

[0088] According to a seventh aspect, there is provided an apparatus comprising: means for sending a session modification command to a terminal, the session modification command indicating that a first non-3GPP device, connected to a network via a session between the network and the terminal, is at least one of no longer authorized or no longer available to access the network via the terminal; and means for receiving a session modification request from the terminal for modifying the session between the terminal and the network, such that said session can continue without traffic associated with the first non-3GPP device.

[0089] The session modification command may comprise information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0090] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise identity information associated with the first non-3GPP device.

[0091] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise a rejection code associated with the first non-3GPP device.

[0092] The session modification command may not include identity information associated with the first non-3GPP device to indicate to the terminal that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal

[0093] The apparatus may comprise means for receiving a request from the terminal requesting that the identity of the first non-3GPP device be added as at least one of an authorized or an available non-3GPP device associated with the terminal.

[0094] The session may be used by a plurality of non-3GPP devices, and the session modification command may indicate one or more of the plurality of non-3GPP devices are at least one of no longer authorised or no longer available to access the network via the terminal.

[0095] The session modification command may comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of no longer authorized or no longer available to access the network via the terminal.

[0096] The session modification command may comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of authorized or available to access the network via the terminal, and does not comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of no longer authorised or no longer available to access the network via the terminal.

[0097] The apparatus may comprise a session management function.

[0098] The apparatus may be configured to provide a session management function.

[0099] According to an eighth aspect, there is provided a method comprising: sending a session modification command to a terminal, the session modification command indicating that a first non-3GPP device, connected to a network via a session between the network and the terminal, is at least one of no longer authorized or no longer available to access the network via the terminal; and receiving a session modification request from the terminal for modifying the session between the terminal and the network, such that said session can continue without traffic associated with the first non-3GPP device.

[0100] The session modification command may comprise information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0101] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise identity information associated with the first non-3GPP device.

[0102] The information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal may comprise a rejection code associated with the first non-3GPP device.

[0103] The session modification command may not include identity information associated with the first non-3GPP device to indicate to the terminal that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0104] The method may comprise receiving a request from the terminal requesting that the identity of the first non-3GPP device be added as at least one of an authorized or an available non-3GPP device associated with the terminal.

[0105] The session may be used by a plurality of non-3GPP devices, and the session modification command may indicate one or more of the plurality of non-3GPP devices are at least one of no longer authorised or no longer available to access the network via the terminal.

[0106] The session modification command may comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of no longer authorized or no longer available to access the network via the terminal.

[0107] The session modification command may comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of authorized or available to access the network via the terminal, and does not comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of no longer authorised or no longer available to access the network via the terminal.

[0108] The method may be performed by an apparatus.

[0109] The apparatus may comprise a session management function.

[0110] The apparatus may provide a session management function.[OHl] The apparatus may comprise means to perform the method.

[0112] The apparatus may comprise at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform any one of the methods of the eighth aspects.

[0113] According to a ninth aspect there is provided a terminal comprising: means for sending a session request to a network entity of a network for requesting connection of a first non-3GPP device to the network via the terminal, said session request comprising identity information associated with the first non-3GPP device; and means for receiving a response to the session request from the network, said response to the session request rejecting the session request, based on traffic associated with the first non-3GPP device not being accommodated in a session between the network and the terminal.

[0114] The traffic associated with the first non-3GPP device may not be accommodated in the session between the network and the terminal if a maximum limit for the session would be exceeded.

[0115] The traffic associated with the first non-3GPP device may not be accommodated in the session between the network and the terminal if a quality of service for the traffic cannot be met.

[0116] The session request may comprise a session establishment request or a session modification request.

[0117] The response to the session request may comprise information indicating that the first non-3GPP device is not accommodated in the session between the network and the terminal.

[0118] The information indicating that the first non-3GPP device is not accommodated in the session between the network and the terminal may comprise a rejection code associated with the first non-3GPP device.

[0119] The response to the session request may comprise the identity information associated with the first non-3GPP device that is not accommodated in the session between the network and the terminal.

[0120] The response to the session request may indicate that the first non-3GPP device is not accommodated in the session between the network and the terminal by omitting the identity information associated with the first non-3GPP device.

[0121] The terminal may comprise means for delaying a further session request associated with the first non-3GPP device by at least a first time period.

[0122] The terminal may comprise means for preventing a sending of a further session request associated with the first non-3GPP device.

[0123] The session request may further be for requesting connection of at least one further non-3GPP device to the network via the terminal, said session request further comprising identity information associated with each of the at least one further non-3GPP device.

[0124] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device, based on said one or more of the at least one further non-3GPP device not being accommodated in the session between the network and the terminal.

[0125] The response to the session request may further comprise the respective identity information associated with one or more of the at least one non-3GPP device accommodated in the session between the network and the terminal, and does not comprise the respectiveidentity information associated with one or more of the at least one non-3GPP device not accommodated in the session between the network and the terminal.

[0126] The terminal may be a user equipment or provided in a user equipment.

[0127] According to a tenth aspect there is provided a method comprising: sending a session request to a network entity of a network for requesting connection of a first non-3GPP device to the network via a terminal, said session request comprising identity information associated with the first non-3GPP device; and receiving a response to the session request from the network, said response to the session request rejecting the session request, based on traffic associated with the first non-3GPP device not being accommodated in a session between the network and the terminal.

[0128] The traffic associated with the first non-3GPP device may not be accommodated in the session between the network and the terminal if a maximum limit for the session would be exceeded.

[0129] The traffic associated with the first non-3GPP device may not be accommodated in the session between the network and the terminal if a quality of service for the traffic cannot be met.

[0130] The session request may comprise a session establishment request or a session modification request.

[0131] The response to the session request may comprise information indicating that the first non-3GPP device is not accommodated in the session between the network and the terminal.

[0132] The information indicating that the first non-3GPP device is not accommodated in the session between the network and the terminal may comprise a rejection code associated with the first non-3GPP device.

[0133] The response to the session request may comprise the identity information associated with the first non-3GPP device that is not accommodated in the session between the network and the terminal.

[0134] The response to the session request may indicate that the first non-3GPP device is not accommodated in the session between the network and the terminal by omitting the identity information associated with the first non-3GPP device.

[0135] The method may comprise delaying a further session request associated with the first non-3GPP device by at least a first time period.

[0136] The method may comprise preventing a sending of a further session request associated with the first non-3GPP device.

[0137] The session request may further be for requesting connection of at least one further non-3GPP device to the network via the terminal, said session request further comprising identity information associated with each of the at least one further non-3GPP device.

[0138] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device, based on said one or more of the at least one further non-3GPP device not being accommodated in the session between the network and the terminal.

[0139] The response to the session request may further comprise the respective identity information associated with one or more of the at least one non-3GPP device accommodated in the session between the network and the terminal, and does not comprise the respective identity information associated with one or more of the at least one non-3GPP device not accommodated in the session between the network and the terminal.

[0140] The method may be performed by an apparatus (e.g., the terminal).

[0141] The terminal may be implemented as a user equipment or provided in a user equipment.

[0142] The apparatus may comprise means to perform the method.

[0143] The apparatus may comprise at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform any one of the methods of the tenth aspect.

[0144] According to an eleventh aspect there is provided an apparatus comprising means for receiving, from a terminal, a session request for requesting connection of a first non-3GPP device to a network via the terminal, said session request comprising identity information associated with the first non-3GPP device; and means for sending a response to the session request to the terminal, said response to the session request rejecting the session request, based on traffic associated with the first non-3GPP device not being accommodated in a session between the network and the terminal.

[0145] The traffic associated with the first non-3GPP device may not be accommodated in the session between the network and the terminal if a maximum limit for the session would be exceeded.

[0146] The traffic associated with the first non-3GPP device may not be accommodated in the session between the network and the terminal if a quality of service for the traffic cannot be met.

[0147] The session request may comprise a session establishment request or a session modification request.

[0148] The response to the session request may comprise information indicating that the first non-3GPP device is not accommodated in the session between the network and the terminal.

[0149] The information indicating that the first non-3GPP device is not accommodated in the session between the network and the terminal may comprise a rejection code associated with the first non-3GPP device.

[0150] The response to the session request may comprise the identity information associated with the first non-3GPP device that is not be accommodated in the session between the network and the terminal.

[0151] The response to the session request may indicate that the first non-3GPP device is not accommodated in the session between the network and the terminal by omitting the identity information associated with the first non-3GPP device.

[0152] The session request may further be for requesting connection of at least one further non-3GPP device to the network via the terminal, said session request further comprising identity information associated with each of the at least one further non-3GPP device.

[0153] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device, based on said one or more of the at least one further non-3GPP device not being accommodated in the session between the network and the terminal.

[0154] The response to the session request may further comprise the respective identity information associated with one or more of the at least one non-3GPP devices accommodated in the session between the network and the terminal, and does not comprise the respective identity information associated with one or more of the at least one non-3GPP devices not accommodated in the session between the network and the terminal.

[0155] The apparatus may comprise a session management function.

[0156] The apparatus may be configured to provide a session management function.

[0157] According to an twelfth aspect there is provided a method comprising: receiving, from a terminal, a session request for requesting connection of a first non-3GPP device to a network via the terminal, said session request comprising identity information associated with the first non-3GPP device; and sending a response to the session request to the terminal, said response to the session request rejecting the session request, based on traffic associated with the first non-3GPP device not being accommodated in a session between the network and the terminal.

[0158] The traffic associated with the first non-3GPP device may not be accommodated in the session between the network and the terminal if a maximum limit for the session would be exceeded.

[0159] The traffic associated with the first non-3GPP device may not be accommodated in the session between the network and the terminal if a quality of service for the traffic cannot be met.

[0160] The session request may comprise a session establishment request or a session modification request.

[0161] The response to the session request may comprise information indicating that the first non-3GPP device is not accommodated in the session between the network and the terminal.

[0162] The information indicating that the first non-3GPP device is not accommodated in the session between the network and the terminal may comprise a rejection code associated with the first non-3GPP device.

[0163] The response to the session request may comprise the identity information associated with the first non-3GPP device that is not accommodated in the session between the network and the terminal.

[0164] The response to the session request may indicate that the first non-3GPP device is not accommodated in the session between the network and the terminal by omitting the identity information associated with the first non-3GPP device.

[0165] The session request may further be for requesting connection of at least one further non-3GPP device to the network via the terminal, said session request further comprising identity information associated with each of the at least one further non-3GPP device.

[0166] The response to the session request may further comprise the respective identity information associated with one or more of the at least one further non-3GPP device, based on said one or more of the at least one further non-3GPP device not being accommodated in the session between the network and the terminal.

[0167] The response to the session request may further comprise the respective identity information associated with one or more of the at least one non-3GPP devices accommodated in the session between the network and the terminal, and does not comprise the respective identity information associated with one or more of the at least one non-3GPP devices not accommodated in the session between the network and the terminal.

[0168] The method may be performed by an apparatus.

[0169] The apparatus may comprise a session management function.

[0170] The apparatus may be configured to provide a session management function.

[0171] The apparatus may comprise means to perform the method.

[0172] The apparatus may comprise at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform any one of the methods of the twelfth aspect.

[0173] According to another aspect, there is provided a computer readable medium comprising program instructions stored thereon for performing at least one of the above methods.

[0174] According to an aspect, there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing at least one of the above methods.

[0175] According to an aspect, there is provided a non-volatile tangible memory medium comprising program instructions stored thereon for performing at least one of the above methods.

[0176] In the above, many different aspects have been described. It should be appreciated that further aspects may be provided by the combination of any two or more of the aspects described above.

[0177] Various other aspects are also described in the following detailed description and in the claims.BRIEF DESCRIPTION OF THE FIGURES

[0178] Some embodiments will now be described, by way of non-limiting and illustrative example only, with reference to the accompanying Figures in which:

[0179] Fig. 1 shows an example of a communication network to which examples disclosed herein may be applied.

[0180] Fig. 2 a schematic representation of a communication system, for example a 5G communication system (5GS).

[0181] Fig. 3 illustrates an example of three non-3GPP devices connected to a core via a user equipment;

[0182] Fig. 4 illustrates a first procedure according to some embodiments.

[0183] Fig. 5 illustrates a second procedure according to some embodiments;

[0184] Fig. 6 illustrates a third procedure according to some embodiments;

[0185] Fig. 7 shows a first method according to some embodiments;

[0186] Fig. 8 shows a second method according to some embodiments;

[0187] Fig. 9 shows a third method according to some embodiments;

[0188] Fig. 10 shows a fourth method according to some embodiments;

[0189] Fig. 11 shows a fifth method according to some embodiments;

[0190] Fig. 12 shows a sixth method according to some embodiments; and

[0191] Fig. 13 shows an example of an apparatus.DETAILED DESCRIPTION

[0192] The following embodiments are provided by way of non-limiting and illustrative example. Although this disclosure may refer to “an”, “one”, or “some” embodiment(s) in several locations herein, this does not necessarily mean that each reference is made to the same embodiment s), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it intended such feature, structure, or characteristic may be applied in connection with other embodiments (whether or not explicitly described).

[0193] It shall be understood that although the terms “first”, “second”, and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are merely used to distinguish one element from another.

[0194] As used herein, the phrases “at least one of A or B”, “at least one of A and B”, and “A and / or B” means (A), (B), or (A and B). Analogously, the phrase “A, B, and / or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0195] As used herein, the term “or” refers to a non-exclusive “or” unless otherwise indicated (e.g., use of “or else” or “or in the alternative”).

[0196] As used herein and unless stated explicitly, performing a respective feature, step, or functionality “in response to A” does not indicate that the respective feature, step, or functionality is performed immediately after “A” occurs as one or more intervening features, steps, or functionalities may be performed (at least in part) between an occurrence of the respective feature, step, or function and “A”. Analogously, performing a respective feature, step, or functionality “based on A” does not indicate that the respective feature, step, or functionality is performed solely based on “A” as the respective feature, step, or functionality may be further based on one or more other features, steps, or functionalities in addition to “A”. Embodiments described herein may be implemented in a communication network, such as any of the following radio access technologies (RATs): Worldwide Interoperability for Micro-wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE),LTE-Advanced, and enhanced LTE (eLTE), 5G (also called NR), 6G, or beyond. Moreover, communication within the communication network may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), and / or Discrete Fourier Transform spread OFDM (DFT-s-OFDM). As used herein, reference to a user equipment (UE) may be understood to be a reference to any suitable terminal (otherwise referred to as a terminal device).

[0197] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of non-limiting and illustrative example, a terminal device may be also referred to as a communication device, UE, a Subscriber Station (SS), or a Mobile Station (MS). The terminal device may be implemented as or included in a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, USB dongles, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and / or the like.

[0198] Fig. 1 illustrates an example of a communication network to which examples disclosed herein may be applied. The communication network or a cellular communication network may comprise a network node 110 configured to provide one or more cells, such as cell 100, and a network node 112 configured to provide one or more other cells, such as cell 102. Each cell may be, e.g., a macro cell, a micro cell, femto, or a pico cell, for example. The cell may define a coverage area or a service area of the corresponding node.

[0199] The network node 110 may provide a user equipment (UE) 120 (one or more UEs) with wireless access to the communication network. The wireless access may comprise downlink (DL) communication from the network node to the UE 120 and uplink (UL) communication from the UE 120 to the network node. Examples of uplink channels comprise physical uplink control channel (PUCCH) for transmitting control information and physical uplink shared channel (PUSCH) for transmitting data towards the network. Examples of downlink channelscomprise physical downlink control channel (PDCCH) for transmitting control information and physical downlink shared channel (PDSCH) for transmitting data towards the user equipment.

[0200] There may be a plurality of UEs 120, 122 in the system. Each of the plurality of UEs 120, 122 may be served by the same or by different network nodes 110, 112. A UE may be configured with dual connectivity (DC), wherein the UE, e.g. UE 120, may be connected to multiple network nodes 110, 112. The UEs 120, 122 may communicate with each other, in case device-to-device (D2D) communication interface is established between them via a so-called “sidelink” (SL). Such D2D communications may be referred to as machine-to-machine, peer-to-peer (P2P) communications, or vehicle-to-vehicle (V2V), for example.

[0201] In the case of multiple network nodes in the communication network, the network nodes may be connected to each other via an interface. LTE specifications refer to such an interface as an X2 interface. An interface between an LTE node and a 5G node, or between two 5G nodes may be referred to as an Xn interface.

[0202] The network nodes 110 and 112 may be further connected via another interface to a core network 202 of the communication network.

[0203] For example, LTE specifications specify the core network as an evolved packet core (EPC), and the core network may comprise e.g. a mobility management entity (MME) and a gateway node. The MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signalling connections between the terminal devices and the core network. The gateway node may handle data routing in the core network and to / from the terminal devices.

[0204] For example, 5G specifications specify the core network as a 5G core (5GC). The 5G core may comprise e.g. an access and mobility management function (AMF) and a user plane function / gateway (UPF) and other functions. The AMF may handle termination of non-access stratum (NAS) signalling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The UPF node may support packet routing and forwarding, packet inspection and quality of service (QoS) handling, for example.

[0205] Fig. 2 shows a schematic representation of a communication system, for example a 5G communication system (5GS). The 5GS may comprise a user equipment (UE), a 5G core network (5GC) 202, and one or more application functions 203. The UE may connect to the 5GC via network node 110 (e.g., a radio access node) of a radio access network. An Application Function (AF) 203 may be deployed in the 5GS as trusted application function or may bedeployed or host on one or more application servers of the data network (DN) 204. Such application functions may be untrusted application functions. The 5GS may be configured to connect the UE to a data network, the access network, and / or the 5GC 202 (e.g., a UPF of the 5GC).

[0206] The 5GC may comprise the following network functions: Network Slice Selection Function (NSSF); Network Exposure Function (NEF) 205; Network Repository Function (NRF); Policy Control Function (PCF); Unified Data Management (UDM) 206; Application Function (AF) 203; Authentication Server Function (AUSF) 207; an Access and Mobility Management Function (AMF) 208; Session Management Function (SMF) 209; and / or a User Plane Function (UPF) 210.

[0207] Fig. 2 also shows the various interfaces (Nl, N2, etc.) that may be implemented between the various elements of the system. Not all of the above network functions are shown in Fig. 2, and some examples of the 5GC may comprise additional network functions other than those mentioned above.

[0208] The AMF 208 may be configured to handle termination of non-access stratum (NAS) signalling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, and / or security context management. The UPF 210 may support packet routing and forwarding, and / or packet inspection and quality of service (QoS) handling, for example.

[0209] Reference is made to Fig. 3, which schematically shows the UE 120. In the example of Fig. 3, there are three non-3GPP devices 300a, 300b, and 300c. There may of course be more or less than three non-3GPP devices in other examples. The non-3GPP devices may be any suitable device, for example a computer, a tablet, and / or the like. By way of non-limiting and illustrative example only, a non-3GPP device may be a device which is configured to use the UE to connect to a 5GC network. For example, the non-3GPP device may be configured to connect to the UE using non-3GPP means, such as a so-called “hot spot” or as a tethering device, and the UE then connects to 5GC using 3GPP means.

[0210] A session 302 may be provided between the UE and the core network. Traffic to and from a given non-3GPP device may be provided via the session between the UE and the core network 202. The non-3GPP devices may be configured to share a session, for example a PDU (packet data unit) session. In the example of Fig. 3, the letter “a” refers to traffic associated with the non-3GPP device referenced 300a, the letter “b” refers to traffic associated with the non-3GPP device referenced 300b, and the letter “c” refers to traffic associated with the non-3GPP device referenced 300c. The UE is configured to relay the traffic of connected non-3GPP devices via the 5GC to their respective destinations.

[0211] As illustrated in Fig. 3, a non-3GPP device may be configured to connect to the communication network behind a UE. A non-3GPP device may be associated with a non-3GPP device identifier. The UE may be configured to bind a device identifier to a non-3GPP device. After the UE binds the device identifier to the non-3GPP device, QoS (quality of service) differentiation may be performed within a PDU Session (for example, using different QoS flows) or between PDU Sessions. In the case of two or more non-3GPP devices sharing a PDU session, the QoS flows may be provisioned in the UE using PDU session modification procedures.

[0212] The UE may send the device identifier and / or user plane address of the non-3GPP device to the SMF. The device identifier and / or user plane address of the non-3GPP device may be sent to the SMF in a NAS-SM (non-access stratum session management) message. The SMF may forward the device identifier and / or user plane address to the PCF. The PCF may use the device identifier to retrieve information from the UDR. The PCF may use the retrieved information for policy decisions for the non-3GPP device associated with the device identifier.

[0213] The user plane address for a non-3GPP device may be: (i) the IP Address of the UE and / port ranges in case of IPv4; (ii) an IPv6 address for an IP PDU session type; and / or (iii) the MAC (medium access control) address and / or a VLAN (virtual local area network) tag ID that is associated with traffic of the non-3GPP device for an ethernet PDU Session type.

[0214] A UE may attempt to establish or modify a PDU session for one or more non-3GPP devices. The UE may provide the device identifier for a respective non-3GPP device. Some embodiments may address the scenario where a respective non-3GPP device is at least one of not authorized or not available. For example, the device identifier may not be present in the UDR, or the device identifier may be associated with an indication that the associated non-3GPP device is at least one of not currently authorized or not currently available.

[0215] When the SMF receives PDU session modification or establishment request from the UE, which comprises one or more device identifiers of one or more respective non-3GPP devices. The SMF may attempt to verify the device identifiers of one or more respective non-3 GPP devices. The SMF may not be able to at least one of authorize one or more device identifiers or determine one or more device identifiers are available, for example via the UDR, due to: (i) a device identifier is not present or available in the UDR; (ii) a device identifier is not associated with the UE from which the PDU session modification or establishment request is received; or (iii) the device identifier is not authorized at the time of the request (e.g., adevice identifier may be associated with a non-3GPP device which can only be used at certain times).

[0216] Where one or more of the device identifiers are at least one of not authorised or not available, the SMF is configured to reject the PDU session establishment / modification request in a response to the request.

[0217] The response to the request may comprise a cause value which indicates that the non-3 GPP device connected behind the UE is at least one of not authorized or not available. The cause value may indicate the reason for the non-3GPP device connected behind the UE is at least one of not authorized or not available. For example, there is a mismatch between the UE and the device identifier, the device identifier is not authorised for the UE, the device identifier is not allowed for the UE, the device identifier is not available in the list of devices (e.g., authorized devices) for the UE, and / or the device identifier is otherwise not available (e.g., for the UE, for a plurality of UEs including the UE, or for all UEs).

[0218] The response to the request may comprise cause value #29 - user authentication or authorization failed.

[0219] The response to the request may comprise an error cause indication, which may indicate that that UE is authorized, but the non-3GPP device or device(s) behind the UE are at least one of not authorised or not available. This may be expressed, for example, as a non-3GPP device behind UE is at least one of not authorized or not available. One or more cause values may be associated with this error cause indication.

[0220] If UE request contains only one device identifier for a given non-3GPP device, then the SMF may send the reject cause in the response without including the device identifier for the given non-3GPP device.

[0221] If UE request contains two or more device identifiers, SMF may send the reject cause with one or more of the device identifiers which are at least one of not authorized or not available.

[0222] When the UE receives the response from the SMF rejecting the PDU session establishment / modification request, the UE may send another PDU session establishment / modification request, which does not include the device identifier that has been rejected.

[0223] In some embodiments, the rejected device identifier may not be used again.

[0224] In some embodiments, the rejected device identifier may not be used until the device identifier is registered.

[0225] In some embodiments, the rejected device identifier may not be used in a PDU session establishment / modification for a time Tl. This time T1 may be locally configured (e.g., in the UE), pre-agreed with the UE, or provided by the network. For example, the time Tl may be provided in the response from the SMF rejecting the PDU session establishment / modification request.

[0226] The SMF may send time information to the UE for indicating at least one of authorization or availability of a device associated with a device identifier, and / or send time information to the UE indicating at least one of non-authorization or non-availability of a device associated with a device identifier. The time information may be provided in association with the device identifier.

[0227] For example, a device associated with a device identifier may be at least one of authorized or available between time tl to time t2 time, or for a time period, or for at given time T.

[0228] The given time T may be defined as a given time (e.g. 2pm) or may be defined relative to a current time (e.g. 10 minutes from now).

[0229] For example, a device associated with a device identifier may be at least one of not authorized or not available between time tl to time t2, or for a given time period, or at given time T.

[0230] The UE may request that the rejected device identifier be added as at least one of an authorized, an allowed, or an available device identifier. This may request may cause the information in the UDR associated with the UE to be updated to include the rejected device identifier as at least one of an authorized, an allowed, or an available device identifier.

[0231] The UE may send the request that the rejected device identifier be added as at least one of an authorized, an allowed, or an available device identifier to an application.

[0232] The UE may put the traffic associated with an authorized device identifier in a specific QoS flow.

[0233] Reference is made to Fig. 4, which shows a first example procedure according to some embodiments where a respective non-3GPP device is at least one of not authorized or not available.

[0234] As referenced at 1, the UE registers with the 5GC via the RAN. The UE may register via the AMF. The UE may be associated with a SUCI (subscription concealed identifier) and / or SUPI (subscription permanent identifier) and / or any other suitable identifier of the UE. The UE may use one or more of the identifiers associated with the UE when the UE registers with the AMF.

[0235] As referenced at 2, the UE subscription has one or more user profiles associated with the same UE and / or one or more device identifiers respectively associated with one or more non-3GPP devices, associated with the UE. One or more non-3GPP devices may thus be associated with the UE. The UDM / UDR may store a mapping between a respective identifier associated with a respective non-3GPP device and the UE. The mapping may be between a respective identifier associated with a respective non-3GPP device and one or more of the identifiers associated with the UE. Thus, one or more non-3GPP devices are associated with the subscription of the UE in the UDR.

[0236] As referenced at 3, the SMF receives a PDU session modification or establishment request from UE, which includes one or more of the device identifiers respectively associated with one or more of the non-3GPP devices.

[0237] As referenced by 4, the SMF and / or PCF attempts to verify each of the one or more of the device identifiers respectively associated with the one or more non-3GPP devices. SMF and / or PCF may use the information about the subscription of the UE stored in the UDR to verify each of the one or more of the device identifiers respectively associated with the one or more non-3GPP devices. In the example shown in Fig. 4, one or more of the device identifiers respectively associated with one or more non-3GPP devices is at least one of not verified, not authorized, or not available.

[0238] Two example options will now be described for the part of the procedure referenced at 5.

[0239] In a first option, the SMF rejects PDU session establishment / modification. The procedure may be rejected with a cause value. The cause value may indicate that the non-3GPP device connected behind the UE is at least one of not authorized or not available. The cause value may indicate the reason for the non-3GPP device connected behind the UE being at least one of not authorized or not available. For example, there is a mismatch between the UE and the device identifier, the device identifier is not authorised for the UE, the device identifier is not available in the list of devices (e.g., authorized devices) for the UE, and / or the device identifier is otherwise not available (e.g., for the UE, for a plurality of UEs including the UE, or for all UEs).

[0240] The response may comprise cause value #29 - user authentication or authorization failed.

[0241] If UE request contains only one device identifier for a given non-3GPP device, then the SMF may send the reject cause in the response excluding the device identifier for the given non-3GPP device.

[0242] If UE request contains two or more device identifiers, SMF may send the reject cause with the device identifiers that are at least one of not authorized or not available.

[0243] In a second option, the SMF sends aPDU session establishment / modification ACCEPT message with each of the one or more device identifiers, which are at least one of not authorized or not available. This second option may be used where one or more device identifiers are at least one of authorized or available.

[0244] The SMF may send time information to the UE for indicating at least one of authorization or availability of a non-3GPP device associated with a device identifier, or send time information to the UE for indicating at least one of non-authorization or non-availability of a non-3GPP device associated with a device identifier. The time information may be provided in association with the device identifier. This may be provided in the response from the SMF.

[0245] For example, a device associated with a device identifier may be at least one of authorized or available between time tl to time t2 time, or for a time period Tl, or for at given time T.

[0246] The given time T may be defined as a given time (e.g. 2pm), or may be defined relative to a current time (e.g. 10 minutes from now).

[0247] For example, a non-3GPP device associated with a device identifier may be at least one of not authorized or not available between time tl to time t2, or for a given time period Tl, or at given time T.

[0248] As referenced at 6, the UE, may upon receiving the response from SMF, send another PDU session establishment / modification request which does not include the device identifier which has been rejected.

[0249] In some embodiments, the rejected device identifier may not be used again.

[0250] In some embodiments, the rejected device identifier may not be used until the device identifier is registered.

[0251] In some embodiments, the rejected device identifier may not be used in a PDU session establishment / modification for a time Tl. This time Tl may be locally configured (e.g., in the UE), pre-agreed with the UE, or provided by the network. For example, the time Tl may be provided in the response from the SMF rejecting the PDU session establishment / modification request.

[0252] The UE may request that the rejected device identifier be added as at least one of an allowed, an authorized, or an available device identifier. This request may cause the information in the UDR associated with the UE to be updated to include the rejected deviceidentifier as at least one of an allowed, an authorized, or an available device identifier. This may be done using an API (application programming interface) and / or application option. The UE may indicate to the application (e.g., using an error message or button) that the UE received, from the network, an error associated with the non-3GPP device that was at least one of not authorized or not available. The application then can configure (e.g., through the AF / NEF functions in the 5GC) in the UDR the device identifier of the non-3GPP device, so that next time UE includes the device identifier of the non-3GPP device in a session modification request or session establishment request, that request will be approved or authorized by the 5GC at least for that particular non-3GPP device.

[0253] The UE may be configured to put the traffic associated with at least one of an authorized or an available device identifier in a specific QoS flow.

[0254] A UE may have a PDU session established for one or more non-3GPP devices, where one or more of the non-3GPP devices may be mismatched or unauthorised. Reference is made to Fig. 5, which shows a second example procedure according to some embodiments.

[0255] It should be appreciated that the part of the procedure referenced at 1 of Fig. 5, is broadly in line with the part of the procedure referenced at 1 to 5 in Fig. 4.

[0256] In the example of Fig. 5, the UE has registered with the core and there are one or more identifiers respectively for one or more non-3GPP devices associated with the subscription for the UE in the UDR. The UE has established PDU session for one or more non-3GPP devices behind the UE. The one or more non-3GPP devices are at least one of authorized, or available at the UDR. The device identifier associated with at least one of an authorized or an available non-3GPP device is stored in the UDR in association with the subscription of the UE.

[0257] As referenced at 2, one or more of the non-3GPP devices connected via the UE is at least one of no longer authorized or no longer available. This may be due to an operator policy change, an AF subscription expiry, the time for which the non-3GPP device is allowed to be connected has expired, and / or the like.

[0258] As referenced at 3, the network (for example the SMF) sends a PDU session modification request to the UE. The PDU session modification request comprises a device identifier for each of the one or more non-3GPP devices, which are no longer authorised.

[0259] As referenced at 4a, the UE sends a PDU session modification request to the network, for example the SMF. The PDU session modification request is excluding the device identifier for each of the one or more non-3GPP devices which are at least one of no longer authorised or no longer available. The traffic associated with the one or more non-3GPP devices which are at least one of no longer authorised or no longer available is removed from the PDU session.

[0260] As referenced at 4b, the UE may request that the rejected device identifier be added as at least one of an allowed or an available device identifier. This may request may cause the information in the UDR associated with the UE to be updated to include the rejected device identifier as at least one of an allowed or an available device identifier. This may be done using an API (application programming interface) and / or an application option.

[0261] A UE may attempt to establish or modify a PDU session for one or more non-3GPP devices. For example, the UE may provide the device identifier for the non-3GPP device. Some embodiments may address the scenario where a non-3GPP device is not able to be supported. This may be due to the non-3GPP device being unable to be supported by the PDU session with a satisfactory level of QoS.

[0262] The rejection by the network, for example by the SMF, may because the network cannot provide the QoS requirement for the non-3GPP device. For example, the required QoS is more than the allowed UE-AMBR (aggregate maximum bit rate).

[0263] The network may reject the PDU session establishment / modification request with a cause value, which indicates that the non-3GPP device cannot be supported.

[0264] The network may reject the PDU session establishment / modification request with a cause value, which indicates that there are insufficient resources to support the non-3GPP device.

[0265] The cause value may be indicated by a back-off timer value IE (information element) and / or a 5G SM (session management) cause value #26, which indicates insufficient resources.

[0266] The network may send one or more device identifiers respectively associated with one or more non-3GPP devices, which cannot be supported.

[0267] The network may send time information along with the rejection of the PDU session establishment / modification request. The time information may indicate a length of time for which the rejection of a respective non-3GPP device is valid.

[0268] The UE, upon receiving the rejection message from the SMF, may not include the respective device identifier in a PDU session establishment / modification request in the future. This may be permanent or for a given amount of time or until a given event has occurred.

[0269] The UE may initiate a further PDU session establishment / modification request without one or more device identifiers respectively associated with the one or more non-3GPP devices, which cannot be supported.

[0270] The UE may not include the one or more device identifiers respectively associated with the one or more non-3GPP devices, which cannot be supported in a PDU session establishment / modification request for a time Tl. The time T1 may be locally configured (e.g.,in the UE), pre-agreed with the UE, or provided by the network. For example, the time T1 may be provided in the response from the SMF rejecting the PDU session establishment / modification request.

[0271] Reference is made to Fig. 6, which shows an example according to some procedures where a UE attempts to establish or modify a PDU session for one or more non-3GPP devices and a respective non-3GPP device is not able to be supported.

[0272] The part of the procedure referenced at 1 to 3 of Fig. 6 is broadly in line with the part of the procedure referenced 1 to 3 of Fig. 4.

[0273] As referenced at 4, the SMF / PCF determines that it cannot provide the QoS requirement for one or more of the one or more non-3GPP devices. For example, the required QoS is more than the allowed UE-AMBR.

[0274] Additionally or alternatively, the SMF / PCF determines for which of the one or more non-3GPP devices the required QoS can be provided.

[0275] As referenced at 5, the SMF sends a response the PDU session modification or establishment request.

[0276] The response may comprise a device identifier respectively associated with a non-3GPP device, which cannot be supported. Additionally or alternatively, the response may comprise a device identifier respectively associated with a non-3GPP device, which can be supported.

[0277] The response may comprise information indicating a cause. The cause may indicate that a non-3GPP device connected behind the UE cannot be supported. The cause may indicate that there are insufficient resources to support the non-3GPP device.

[0278] Alternatively, the response may comprise a back-off timer value IE (information element) and / or cause value, for example cause value #26, which indicates that there are insufficient resources.

[0279] The response may comprise one or more device identifiers respectively associated with one or more non-3GPP devices, which are to be removed. This may be due to higher QoS requirements.

[0280] Additionally or alternatively, the response may comprise one or more device identifiers respectively associated with one or more non-3GPP devices that can be supported. Where only the one or more device identifiers respectively associated with one or more non-3GPP devices that can be supported are provided, the UE may determine that the one or more device identifiers that are not provided in the response are respectively associated with one or more non-3GPP devices that cannot be supported.

[0281] As referenced at 6, the UE, upon receiving the response from the SMF may remove the device identifier for the non-3GPP device which cannot be supported from the PDU session establishment or modification request. This, for example, will prevent this non-3GPP device from being tethered to the 5G network via the UE.

[0282] Additionally or alternatively, the UE may send a further PDU session establishment or modification request without the device identifier for the non-3GPP device, which cannot be supported.

[0283] Additionally or alternatively, the UE may send a further PDU session establishment or modification request with the respective device identifier for the non-3GPP device which cannot be supported for at least a time Tl. This time T1 may be locally configured (e.g., in the UE), pre-agreed with the UE, or provided by the network. For example, the time Tl may be provided in the response from the SMF rejecting the PDU session establishment / modification request.

[0284] It should be appreciated that in some embodiments, the SMF may send a PDU session modification request if the network dynamically decides to restrict the QoS cap of an already established PDU session. This modification request will indicate to the UE that one or more of the non-3GPP devices are to be removed from the existing PDU session. The modification request may comprise the device identifier of any non-3GPP devices to be removed from the PDU session and / or the device identifier of any non-3GPP devices to be retained in the PDU session.

[0285] In the previous examples, reference has been made to a UE. This reference is provided by way of non-limiting and illustrative example, and the device may be any suitable terminal device as described herein, such as 5G RG (5G residential gateway), or any other suitable device.

[0286] In the previous examples, reference has been made to a SMF configured to provide various functions. This reference is provided by way of non-limiting and illustrative example, and any other suitable network function (e.g., another management network function) or entity may be configured to provide one or more of the functions described in relation to the SMF.

[0287] In the previous examples, reference has been made to a PCF configured to provide various functions. This reference is provided by way of non-limiting and illustrative example, and any other suitable network function (e.g., another policy network function) or entity may be configured to provide one or more of the functions described in relation to the PCF.

[0288] In the previous examples, reference has been made to a UDM / UDR configured to provide various functions. This reference is provided by way of non-limiting and illustrativeexample, and any other suitable network function(s) (e.g., other repository network function(s)) or entit(ies) may be configured to provide one or more of the functions described in relation to the UDM / UDR.

[0289] Reference is made to Figs. 7 to 12 which show some methods according to some embodiments.

[0290] Each method may be performed by an apparatus.

[0291] The apparatus may comprise suitable means, such as circuitry for providing the respective method.

[0292] Additionally or alternatively, the apparatus may comprise at least one processor and at least one memory storing instructions that, when executed by the at least one processor cause the apparatus at least to provide the respective method.

[0293] Additionally or alternatively, the apparatus may be such as discussed in relation to Fig.13.

[0294] The respective methods may be provided by computer program code or computer executable instructions.

[0295] Reference is made to Fig. 7. The apparatus (e.g., the terminal) may be implemented as a user equipment or provided in a user equipment.

[0296] The method comprises, as referenced at Al, sending a session request to a network entity of a network for requesting connection of a first non-3GPP device to the network via a terminal, said session request comprising identity information associated with an identity of the first non-3GPP device.

[0297] The method comprises, as referenced at A2, receiving, from the network, a response to the session request, said response to the session request rejecting the request for the connection of the first non-3GPP device to the network via the terminal, based on the first non-3GPP device being at least one of not authorized or not available to access the network via the terminal, said response to the session request indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0298] Reference is made to Fig. 8. The apparatus may be configured to provide a network function, such as a session management function. The apparatus may comprise a network function, such as a session management function.

[0299] The method comprises, as referenced at Bl, receiving a session request from a terminal requesting connection of a first non-3GPP device to a network via the terminal, said session request comprising identity information associated with an identity of the first non-3GPP device.

[0300] The method comprises as referenced at B2, sending, to the terminal, a response to the session request, said response to the session request rejecting the request for the connection of the first non-3GPP device to the network via the terminal, based on the first non-3GPP device being at least one of not authorized or not available to access the network via the terminal, said response to the session request indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

[0301] Reference is made to Fig. 9. The apparatus (e.g., the terminal) may be implemented as a user equipment or provided in a user equipment.

[0302] The method comprises as referenced at Cl, receiving a session modification command from a network entity of a network, the session modification command indicating that a first non-3GPP device, connected to the network via a session between the network and the terminal, is at least one of no longer authorized or no longer available to access the network via the terminal.

[0303] The method comprises as referenced at C2, sending a session modification request to the network entity of the network for modifying the session between the terminal and the network, such that said session can continue without traffic associated with the first non-3GPP device.

[0304] Reference is made to Fig. 10. The apparatus may be configured to provide a network function, such as a session management function. The apparatus may comprise a network function, such as a session management function.

[0305] The method comprises as referenced at DI, sending to a terminal, a session modification command indicating that a first non-3GPP device, connected to a network via a session between the network and the terminal, is at least one of no longer authorized or no longer available to access the network via the terminal.

[0306] The method comprises as referenced at D2, receiving a session modification request from the terminal for modifying the session between the terminal and the network, such that said session can continue without traffic associated with the first non-3GPP device.

[0307] Reference is made to Fig. 11. The apparatus (e.g., the terminal) may be implemented as a user equipment or provided in a user equipment.

[0308] The method comprises as referenced at El, sending a session request to a network entity of a network for requesting connection of a first non-3GPP device to the network via a terminal, said session request comprising identity information associated with the first non-3GPP device.

[0309] The method comprises as referenced at E2, receiving, from the network, a response to the session request, said response to the session request rejecting the session request, based ontraffic associated with the first non-3GPP device not being accommodated in a session between the network and the terminal.

[0310] Reference is made to Fig. 12. The apparatus may be configured to provide a network function, such as a session management function. The apparatus may comprise a network function, such as a session management function.

[0311] The method comprises as referenced at Fl, receiving, from a terminal, a session request for requesting connection of a first non-3GPP device to a network via the terminal, said session request comprising identity information associated with the first non-3GPP device.

[0312] The method comprises as referenced at F2, sending a response to the session request to the terminal, said response to the session request rejecting the session request based on traffic associated with the first non-3GPP device not being accommodated in a session between the network and the terminal.

[0313] It should be appreciated that any of the methods described in relation to Figs. 7 to 12 may be modified to include one or more of the features discussed in relation to the previous examples.

[0314] It is understood that references in the above to various network functions may comprise apparatus that perform at least some of the functionality associated with those network functions. Further, an apparatus comprising a network function may comprise a virtual network function instance of that network function.

[0315] Although the apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.

[0316] It is noted that whilst some embodiments have been described in relation to 5G networks and beyond, similar principles can be applied in relation to other networks and communication systems. Some embodiments may be used in relating to 6G networks. Therefore, although certain embodiments were described above by way of non-limiting and illustrative example with reference to certain example architectures for wireless networks, technologies and standards, embodiments may be applied to any other suitable forms of communication systems than those illustrated and described herein.

[0317] It is also noted herein that while the above describes embodiments, there are several variations and modifications which may be made herein without departing from the scope of this disclosure.

[0318] Fig. 13 shows, by way of non-limiting and illustrative example, a block diagram of an apparatus 10. The apparatus 10 comprises, for example, at least one processor 12 and at least one memory 14 storing instructions 15 that, when executed by the at least one processor, causethe apparatus 10 at least to perform the method or methods (or portion(s) thereof) as disclosed herein, and any of the embodiments (or respective portion(s) thereof). In an example, the at least one memory and the instructions, are configured, with the at least one processor, to cause the apparatus 10 to perform the method or methods (or portion(s) thereof) as disclosed herein, and any of the embodiments (or respective portion(s) thereof).

[0319] A processor 12 may comprise circuitry, or be constituted as circuitry or circuitries, the circuitry or circuitries being configured to perform phases of methods in accordance with embodiments described herein.

[0320] As used herein, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in analog, digital and / or quantum circuitry, and (b) combinations of hardware circuit(s) and software, such as (as applicable): (i) a combination of analog, digital and / or quantum hardware circuit(s) with software / firmware and (ii) any or all portions of hardware processor(s) (including digital and / or quantum processor(s)) with software, and memory(ies) that work together to cause an apparatus, such as a mobile device, user equipment, computing device, or server, to perform various functions) and (c) any or all portions of hardware circuit(s), such as a microprocessor(s), processor(s) and / or quantum processor(s), that require software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

[0321] The memory 14 may be implemented using any suitable data storage technology. The memory may comprise a database for storing data. The memory 14 may, for example, be at least in part external to apparatus 10 but accessible to apparatus 10.

[0322] The instructions 15 may be comprised in a computer readable medium or a non-transitory computer readable medium. A term non-transitory, as used herein, is a limitation of the medium itself (i.e. tangible, not a signal) as opposed to a limitation on data storage persistency (e.g. random-access memory, RAM, vs. read only memory, ROM).

[0323] For example, the apparatus 10 may be implemented as a UE or provided in a UE. The apparatus may comprise a chipset. The apparatus 10 may be caused or configured to performat least the method of Figs. 7, 9 and 11 and / or any one or more of the embodiments described herein.

[0324] For example, the apparatus 10 may be configured to provide a network entity, such as an SMF. The apparatus may comprise a network entity, such as an SMF. The apparatus may comprise a chipset, The apparatus 10 may be caused or configured to perform at least the method of Fig. 8, 10, and 12, and / or any one or more of the embodiments described herein.

[0325] The apparatus may comprise one or more entities of any of protocol layers, such as a MAC entity, an RRC entity, an RLC entity, a PDCP entity or a PHY entity.

[0326] The apparatus 10 optionally comprises a radio interface 16. The radio interface 16 may provide the apparatus 10 with communication capabilities. The radio interface 16 may comprise a receiver configured to receive information in accordance with at least one cellular or non-cellular standard. The radio interface 16 may comprise a transmitter configured to transmit information in accordance with at least one cellular or non-cellular standard. The receiver may comprise more than one receiver. The transmitter may comprise more than one transmitter. The radio interface 16 may comprise a transceiver configured to receive and transmit information in accordance with at least one cellular or non-cellular standard. The transceiver may comprise more than one transceiver.

[0327] The apparatus 10 may optionally comprise an interface 18 (e.g., user interface) comprising, for example, at least one of a keypad, a microphone, a touch display, a display, a speaker, etc. The interface 18 (e.g., user interface) may be used to control the apparatus. The interface 18 (e.g., user interface) may be external to the apparatus 10. For example, the apparatus 10 may be connected to another device, such as a computer, either via wireless or wired connection, and the apparatus 10 is controlled via the computer.

[0328] In an embodiment, at least some of the processes described herein may be carried out by an apparatus comprising means for carrying out at least some of the described processes. Means for performing method steps as disclosed herein may include software and / or hardware components of the apparatus 10. For example, the at least one processor 12, the memory 14, and the computer program code form means for carrying out the method or methods (or portion(s) thereof) as disclosed herein, and any of the embodiments (or respective portion(s) thereof).

[0329] In an embodiment, an example change request to 3GPP TS 24.501 V19.1.1 is provided as follows.

[0330] Reason for change: This CR proposes stage-3 method(S) to provide error cause handling to notify the UE that the Non-3GPP Device Identifier is not available for the UE.

[0331] Summary of change: Enhancement in the PDU session modification request rejected by the network (SMF) due to non-availability of the non-3GPP device identifier in the UDR.

[0332] Consequence if not approved: Stage-2 requirement for supporting of Non-3GPP Device Identifier connecting behind the UE not fulfilled.

[0333] Clauses affected: 6.4.2.4.1, 6.4.2.4.3, 9.11.4.2* * * First Change * * *

[0334] 6.4.2.4.1 General

[0335] Upon receipt of a PDU SESSION MODIFICATION REQUEST message, if the SMF does not accepts the request to modify the PDU session, the SMF shall create a PDU SESSION MODIFICATION REJECT message.

[0336] The SMF shall set the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message to indicate the reason for rejecting the PDU session modification.

[0337] The 5GSM cause IE typically indicates one of the following SM cause values:

[0338] #26 insufficient resources;

[0339] #29 user authentication or authorization failed;

[0340] #31 request rej ected, unspecified;

[0341] #32 service option not supported;

[0342] #33 requested service option not subscribed;

[0343] #35 PTI already in use;

[0344] #37 5GS QoS not accepted;

[0345] #43 Invalid PDU session identity;

[0346] #44 Semantic errors in packet filter(s);

[0347] #45 Syntactical error in packet filter(s);

[0348] #46 out of LADN service area;

[0349] #59 unsupported 5 QI value;

[0350] #67 insufficient resources for specific slice and DNN;

[0351] #69 insufficient resources for specific slice;

[0352] #83 Semantic error in the QoS operation;

[0353] #84 Syntactical error in the QoS operation; or

[0354] #95 - 111 protocol errors.

[0355] #XX - non-3GPP device not available.

[0356] If the UE requests a PDU session modification for an LADN when the UE is located outside of the LADN service area, the SMF shall include the 5GSM cause value #46 "out of LADN service area" in the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message.

[0357] If the Extended protocol configuration options IE of the PDU SESSION MODIFICATION REQUEST message indicates 3GPP PS data off UE status and the SMF detects the change of the 3GPP PS data off UE status, the SMF shall not include the 5GSM cause value #26 "insufficient resources", the 5GSM cause value #67 "insufficient resources for specific slice and DNN", the 5GSM cause value #69 "insufficient resources for specific slice" and the 5GSM cause value #46 "out of LADN service area" in the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message.

[0358] If the UE initiates UE-requested PDU session modification procedure to modify the PDU session transferred from EPS to an MA PDU session with the Request type IE set to "MA PDU request" in the UL NAS TRANSPORT message as specified in 3GPP TS 24.193 [13B] and the SMF determines, based on operator policy and subscription information, that the PDU SESSION MODIFICATION REQUEST message is to be rejected, the SMF shall include the 5GSM cause value #33 "requested service option not subscribed" in the 5GSM cause IE of the PDU SESSION MODIFICATION REJECT message.

[0359] NOTETf the SMF determines, based on operator policy and subscription information, that the PDU SESSION MODIFICATION REQUEST message is to be accepted as single access PDU session, the ATSSS container IE cannot be included in the PDU SESSION MODIFICATION COMMAND message.

[0360] The network may include a Back-off timer value IE in the PDU SESSION MODIFICATION REJECT message.

[0361] If the 5GSM cause value is #26"insufficient resources", #67 "insufficient resources for specific slice and DNN", or #69 "insufficient resources for specific slice" and the PDU SESSION MODIFICATION REQUEST message was received from a UE configured for high priority access in selected PLMN or SNPN or the request type provided during the PDU session establishment is set to "initial emergency request" or "existing emergency PDU session", the network shall not include a Back-off timer value IE.

[0362] The SMF shall send the PDU SESSION MODIFICATION REJECT message.

[0363] Upon receipt of a PDU SESSION MODIFICATION REJECT message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE shallstop timer T3581, release the allocated PTI value, and enter the state PROCEDURE TRANSACTION INACTIVE.

[0364] If the PDU SESSION MODIFICATION REQUEST message was sent with the Requested MBS container IE included and the MBS operation set to "Join MBS session", and the UE receives a PDU SESSION MODIFICATION REJECT message, then the UE shall consider the requested MBS join as rejected.

[0365] If the PDU SESSION MODIFICATION REQUEST message was sent with the Requested MBS container IE included and the MBS operation set to "Leave MBS session", and the UE receives a PDU SESSION MODIFICATION REJECT message, then the UE shall locally leave the multicast MBS session(s) corresponding to the TMGI(s) in the Requested MBS container IE of the PDU SESSION MODIFICATION REQUEST message.

[0366] If the UE enables QoS differentiation of traffic for non-3GPP device(s), includes the non-3GPP device connection information IE in the PDU SESSION MODIFICATION REQUEST message and SMF determines that the corresponding non-3GPP device identifier is not available for the UE then the SMF shall reject the PDU SESSION MODIFICATION REQUEST with 5GSM cause value is #XX ”non-3GPP device not available”.

[0367] 6.4.2.4.3 Handling of network rejection not due to congestion control

[0368] If the 5GSM cause value is different from #26 "insufficient resources", #37 "5GS QoS not accepted", #44 "Semantic errors in packet filter(s)", #45 "Syntactical error in packet filter(s)", #46 "out of LADN service area", #59 "unsupported 5QI value", #67 "insufficient resources for specific slice and DNN", #69 "insufficient resources for specific slice", #83 "Semantic error in the QoS operation", and #84 "Syntactical error in the QoS operation", and the Back-off timer value IE is included, the UE shall behave as follows: (if the UE is a UE configured for high priority access in selected PLMN or SNPN, exceptions are specified in subclause 6.2.12):

[0369] a) if the timer value indicates neither zero nor deactivated and:

[0370] 1) if the UE provided DNN and S-NSSAI to the network during the PDU session establishment, the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the PDU session modification procedure and:

[0371] i) in a PLMN, [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session] combination. The UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN and the (mapped) HPLMN S-NSSAI of the PDU session in the current PLMN, until the back-off timer expires, the UE is switched off, or the USIM is removed; or

[0372] ii) in an SNPN, [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI] combination. The UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN and (mapped) subscribed SNPN S-NSSAI of the PDU session in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the back-off timer expires, the UE is switched off, the USIM is removed, or the selected entry of the "list of subscriber data" is updated;

[0373] 2) if the UE did not provide a DNN or S-NSSAI or any of the two parameters to the network during the PDU session establishment, it shall start the back-off timer accordingly for the PDU session modification procedure and:

[0374] i) in a PLMN, [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session] or [PLMN, no DNN, no S-NSSAI] combination. Dependent on the combination, the UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session] or [PLMN, no DNN, no S-NSSAI] combination in the current PLMN, until the back-off timer expires, the UE is switched off, or the USIM is removed; or

[0375] ii) in an SNPN, [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session] or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination. Dependent on the combination, the UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session] or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination in the current SNPN, untilthe back-off timer expires, the UE is switched off, the USIM is removed, or the selected entry in the "list of subscriber data" is updated;

[0376] b) if the timer value indicates that this timer is deactivated and:

[0377] 1) if the UE provided DNN and S-NSSAI to the network during the PDU session establishment, the UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for:

[0378] i) in a PLMN, the same DNN and the (mapped) HPLMN S-NSSAI of the PDU session in the current PLMN, until the UE is switched off, or the USIM is removed; or

[0379] ii) in an SNPN, the same DNN and the (mapped) subscribed SNPN S-NSSAI of the PDU session in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the UE is switched off, or the USIM is removed, or the selected entry in the "list of subscriber data";

[0380] 2) if the UE did not provide a DNN or S-NSSAI or any of the two parameters to the network during the PDU session establishment, the UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for:

[0381] i) in a PLMN; the same [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session] or [PLMN, no DNN, no S-NSSAI] combination in the current PLMN, until the UE is switched off, or the USIM is removed; or

[0382] ii) in an SNPN, the same [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session] or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the UE is switched off, the USIM is removed, or the selected entry in the "list of subscriber data" is updated; and

[0383] c) if the timer value indicates zero, the UE may send another PDU SESSION MODIFICATION REQUEST message for:

[0384] 1) in a PLMN, the same combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [PLMN, no DNN, no S-NSSAI] in the current PLMN; or

[0385] 2) in an SNPN, the same combination of [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session], or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] in the current SNPN.

[0386] If the Back-off timer value IE is not included, then the UE shall ignore the Re-attempt indicator IE provided by the network in the PDU SESSION MODIFICATION REJECT message, if any.

[0387] a) Additionally, if the 5GSM cause value is #32 "service option not supported", or #33 "requested service option not subscribed", then:

[0388] 1) the UE not operating in SNPN access operation mode shall proceed as follows:

[0389] i) if the UE is registered in the HPLMN or in a PLMN that is within the EHPLMN list, the UE shall behave as described above in the present subclause using the configured SM Retry Timer value as specified in 3 GPP TS 24.368

[0017] orinUSIMfileNAScoNFioas specified in 3GPP TS 31.102

[0022] , if available, as back-off timer value; and

[0390] NOTE 1 : The way to choose one of the configured SM Retry Timer values for back-off timer value is up to UE implementation if the UE is configured with:an SM Retry Timer value in the ME as specified in 3GPP TS 24.368

[0017] ; and an SM Retry Timer value in USIM file NASCONFIG as specified in 3GPP TS 31.102

[0022] ,

[0391] ii) otherwise, if the UE is not registered in its HPLMN or in a PLMN that is within the EHPLMN list, or if the SM Retry Timer value is not configured, the UE shall behave as described above in the present subclause, using the default value of 12 minutes for the backoff timer; or

[0392] 2) the UE operating in SNPN access operation mode shall proceed as follows:

[0393] i) if:

[0394] A) the SM Retry Timer value for the current SNPN as specified in 3GPP TS 24.368

[0017] is available; or

[0395] B) the SM Retry Timer value in USIM file NASCONFIG as specified in 3GPP TS 31.102

[0022] is available and the UE used the USIM for registration to the current SNPN;

[0396] then the UE shall behave as described above in the present subclause using the configured SM Retry Timer value as back-off timer value; or

[0397] NOTE 2: The way to choose one of the configured SM Retry Timer values for back-off timer value is up to UE implementation if both conditions in bullets A) and B) above are satisfied.

[0398] ii) otherwise, the UE shall behave as described above in the present subclause, using the default value of 12 minutes for the back-off timer.

[0399] b) For 5GSM cause values different from #32 "service option not supported", or #33 "requested service option not subscribed", the UE behaviour regarding the start of a backoff timer is specified in subclause 6.2.12.

[0400] The UE shall not stop any back-off timer:

[0401] a) upon a PLMN or SNPN change;

[0402] b) upon an inter-system change; or

[0403] c) upon registration over another access type.

[0404] If the network indicates that a back-off timer for the PDU session modification procedure is deactivated, then it remains deactivated:

[0405] a) upon a PLMN or SNPN change;

[0406] b) upon an inter-system change; or

[0407] c) upon registration over another access type.

[0408] NOTE 3 : This means the back-off timer can still be running or be deactivated for the given 5GSM procedure when the UE returns to the PLMN or SNPN or when it performs inter-system change back from SI mode to N1 mode. Thus the UE can still be prevented from sending another PDU SESSION MODIFICATION REQUEST message for the combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [PLMN, no DNN, no S-NSSAI] in the PLMN, or for the combination of [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed S-NSSAI], or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] in the SNPN.

[0409] If the back-off timer is started upon receipt of a PDU SESSION MODIFICATION REJECT (i.e. the timer value was provided by the network, a configured value is available orthe default value is used as explained above) or the back-off timer is deactivated, the UE behaves as follows:

[0410] a) after a PLMN or SNPN change the UE may send a PDU SESSION MODIFICATION REQUEST message for:

[0411] 1) in a PLMN, the combination of [new PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [new PLMN, DNN, no S-NSSAI], [new PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [new PLMN, no DNN, no S-NSSAI] in the new PLMN, if the back-off timer is not running and is not deactivated for the PDU session modification procedure and the combination of [new PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [new PLMN, DNN, no S-NSSAI], [new PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [new PLMN, no DNN, no S-NSSAI]; or

[0412] 2) in an SNPN, the combination of [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session], [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session], or [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] in the new SNPN, if the back-off timer is not running and is not deactivated for the PDU session modification procedure and the combination of [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session], [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session], or [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI];

[0413] Furthermore, as an implementation option, for the 5GSM cause value #32 "service option not supported" or #33 "requested service option not subscribed", if the network does not include a Re-attempt indicator IE, the UE may decide not to automatically send another PDU SESSION MODIFICATION REQUEST message:

[0414] 1) in a PLMN, the same combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [PLMN, no DNN, no S-NSSAI], if the UE is registered to a new PLMN which is in the list of equivalent PLMNs; or

[0415] 2) in an SNPN, if the UE supports equivalent SNPNs, the same combination of [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session], or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI], if the UE is registered to a new SNPN which is in the list of equivalent SNPNs.

[0416] b) if the network does not include the Re-attempt indicator IE to indicate whether re-attempt in SI mode is allowed, or the UE ignores the Re-attempt indicator IE, e.g. because the Back-off timer value IE is not included, then:

[0417] 1) if the UE is registered in its HPLMN or in a PLMN that is within the EHPLMN list and the back-off timer is running for the combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session] or [PLMN DNN, no S-NSSAI], the UE shall apply the configured SM RetryAtRATChange value as specified in 3GPP TS 24.368

[0017] or in USIM file NASCONFIG as specified in 3GPP TS 31.102

[0022] , if available, to determine whether the UE may attempt an EPS bearer resource allocation procedure or an EPS bearer resource modification procedure for the same [PLMN, DNN] combination in SI mode; and

[0418] NOTE 4: The way to choose one of the configured SM RetryAtRATChange values for back-off timer value is up to UE implementation if the UE is configured with:an SM RetryAtRATChange value in ME as specified in 3GPP TS 24.368

[0017] ; and an SM_RetryAtRATChange value in USIM file NASCONFIG as specified in 3GPP TS 31.102

[0022] ,

[0419] 2) if the UE is not registered in its HPLMN or in a PLMN that is within the EHPLMN list, or if the NAS configuration MO as specified in 3GPP TS 24.368

[0017] is not available and the value for inter-system change is not configured in the USIM file NASCONFIG, then the UE behaviour regarding an EPS bearer resource allocation procedure or an EPS bearer resource modification procedure for the same [PLMN, DNN] combination in SI mode is unspecified; and

[0420] c) if the network includes the Re-attempt indicator IE indicating that re-attempt in an equivalent PLMN or equivalent SNPN is not allowed, then depending on the timer value received in the Back-off timer value IE, for:

[0421] 1) in a PLMN, each combination of a PLMN from the equivalent PLMN list and the respective [DNN, (mapped) HPLMN S-NSSAI of the PDU session], [DNN, no S-NSSAI],[no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [no DNN, no S-NSSAI] combination, the UE shall start a back-off timer for the PDU session modification procedure with the value provided by the network, or deactivate the respective back-off timer as follows:

[0422] i) if the Re-attempt indicator IE additionally indicates that re-attempt in SI mode is allowed, the UE shall start or deactivate the back-off timer for N1 mode only; and

[0423] ii) otherwise, the UE shall start or deactivate the back-off timer for SI and N1 mode

[0424] 2) in a SNPN, if the UE supports equivalent SNPNs, each combination of a SNPN from the equivalent SNPN list and the respective [the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session], [the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI of the PDU session], or [the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination, the UE shall start a back-off timer for the PDU session modification procedure with the value provided by the network, or deactivate the respective back-off timer, for N 1 mode in an SNPN.

[0425] If the back-off timer for a [PLMN, DNN] or [PLMN, no DNN] combination was started or deactivated in SI mode upon receipt of BEARER RESOURCE ALLOCATION REJECT message or BEARER RESOURCE MODIFICATION REJECT message (see 3GPP TS 24.301

[0015] ) and the network indicated that re-attempt in N1 mode is allowed, then this back-off timer does not prevent the UE from sending a PDU SESSION MODIFICATION REQUEST message in this PLMN for the same DNN after inter-system change to N1 mode. If the network indicated that re-attempt in N1 mode is not allowed, the UE shall not send any PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, in this PLMN for the same DNN in combination with any S-NSSAI or without S-NSSAI, after inter-system change to N1 mode until the timer expires, the UE is switched off or the USIM is removed.

[0426] NOTE 5: The back-off timer is used to describe a logical model of the required UE behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp.

[0427] NOTE 6: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the UE. Whether the UE uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to UE implementation.

[0428] If the 5GSM cause value is #46 "out of LADN service area", the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. If the UE is not located inside the LADN service area, the UE shall not send another PDU SESSION MODIFICATION REQUEST message except for indicating a change of 3GPP PS data off UE status or another PDU SESSION ESTABLISHMENT REQUEST message for the LADN DNN provided by the UE during the PDU session establishment procedure until the LADN information for the specific LADN DNN or the extended LADN information for the specific LADN DNN and S-NSSAI is updated as described in subclause 5.4.4 and subclause 5.5.1. If the UE is not located inside the LADN service area, the UE shall not indicate the PDU session(s) for the LADN DNN provided by the UE during the PDU session establishment procedure in the Uplink data status IE included in the SERVICE REQUEST message until the LADN information for the specific LADN DNN or the extended LADN information for the specific LADN DNN and S-NSSAI is provided by network as described in subclause 5.4.4 and subclause 5.5.1.

[0429] NOTE 7: Based on UE implementation, the UE locating inside the LADN service area can send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the LADN DNN which was rejected with the 5GSM cause value #46 "out of LADN service area".

[0430] NOTE 7A: If the UE does not receive a CONFIGURATION UPDATE COMMAND message with new LADN information within an implementation dependent time, the UE can request this information by initiating a registration procedure for mobility or periodic registration update (see subclause 5.5.1.3.2, item q).

[0431] If the PDU SESSION MODIFICATION REQUEST message contained the non-3GPP device connection information IE and the SMF rejects the PDU SESSION MODIFICATION REQUEST with 5GSM cause value is #XX ”non-3GPP device not available”., the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. The UE, if required, may send another PDU SESSION MODIFICATION REQUEST message to establish a new PDU session with the non-3GPP device connection information IE for a new non-3GPP device connected behind the UE.

[0432] If the 5GSM cause value is #37 "5GS QoS not accepted", #44 "Semantic errors in packet filter(s)", #45 "Syntactical error in packet filter(s)", #59 "unsupported 5QI value", #83 "Semantic error in the QoS operation" or #84 "Syntactical error in the QoS operation", the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. The UE should pass the corresponding error cause to the upper layers.

[0433] NOTE 8: How to solve the issues of not accepted 5GS QoS and unsupported 5QI value in the upper layers is UE implementation specific.

[0434] 9.11.4.2 5GSM cause

[0435] The purpose of the 5GSM cause information element is to indicate the reason why a 5GSM request is rejected.

[0436] The 5GSM cause information element is coded as shown in table 9.11.4.2.1a and table 9.11.4.2. lb.

[0437] The 5GSM cause is a type 3 information element with a length of 2 octets.8 7 6 5 4 3octet 1octet 2Table 9.11.4.2.1a: 5GSM cause information element (above)Table 9.11.4.2.1b: 5GSM cause information element (below)" "" "* * * End of Changes * * *

[0438] As used herein, the term “means” is to be construed in singular form, i.e. referring to a single element, or in plural form, i.e. referring to a combination of single elements. Therefore, terminology “means for [performing A, B, C]”, is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C. Further, terminology “means for performing A, means for performing B, means for performing C” is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C.

[0439] Even though various embodiments of this disclosure have been described above with reference to non-limiting and illustrative examples of the Figures, it is clear that the scope of this disclosure is not restricted thereto - but can be modified in many different ways. As technology advances, it will become apparent to a person skilled in art as to how certain embodiments of this disclosure can be further implemented and / or modified in various ways. Further, it is clear to a person skilled in the art that any of the embodiments described herein may, but are not required to, be combined in various ways with any other embodiments described herein.

[0440] As used herein, the term “means” is to be construed in singular form, i.e. referring to a single element, or in plural form, i.e. referring to a combination of single elements. Therefore, terminology “means for [performing A, B, C]”, is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C.Further, terminology “means for performing A, means for performing B, means for performing C” is to be interpreted to cover an apparatus in which there is only one means for performing A, B and C, or where there are separate means for performing A, B and C, or partially or fully overlapping means for performing A, B, C.

[0441] Even though various embodiments of this disclosure have been described above with reference to non-limiting and illustrative examples of the Figures, it is clear that the scope of this disclosure is not restricted thereto - but can be modified in many different ways. As technology advances, it will become apparent to a person skilled in art as to how certain embodiments of this disclosure can be further implemented and / or modified in various ways. Further, it is clear to a person skilled in the art that any of the embodiments described herein may, but are not required to, be combined in various ways with any other embodiments described herein.

Claims

CLAIMS1. A terminal comprising:means for receiving a session modification command from a network entity of a network, the session modification command indicating that a first non-3GPP device, connected to the network via a session between the network and the terminal, is at least one of no longer authorized or no longer available to access the network via the terminal; andmeans for sending a session modification request to the network entity of the network for modifying the session between the terminal and the network, such that said session can continue without traffic associated with the first non-3GPP device.

2. The terminal as claimed in claim 1, wherein session modification command comprises information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

3. The terminal as claimed in claim 2, wherein the information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal comprises identity information associated with the first non-3GPP device.

4. The terminal as claimed in claim 2 or 3, wherein the information indicating that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal comprises a rejection code associated with the non-3GPP device.

5. The terminal as claimed in claim 1, wherein the session modification command does not include identity information associated with the first non-3GPP device to indicate to the terminal that the first non-3GPP device is at least one of not authorized or not available to access the network via the terminal.

6. The terminal as claimed in any of claims 1 to 5, comprising means for delaying a sending of a session request associated with the first non-3GPP device by a least a first time period after the sending of the session modification request.

7. The terminal as claimed in any of claims 1 to 5, comprising means for preventing a sending of a session request associated with the first non-3GPP device after the sending of the session modification request.

8. The terminal as claimed in any preceding claim, comprising means for sending a request to the network requesting that the identity of the first non-3GPP device be added as at least one of an authorized or an available non-3GPP device associated with the terminal.

9. The terminal as claimed in any preceding claim, wherein the session is used by a plurality of non-3GPP devices, and the session modification command indicates one or more of the plurality of non-3GPP devices are at least one of no longer authorised or no longer available to access the network via the terminal.

10. The terminal as claimed in claim 9, wherein the session modification command comprises respective identity information associated with one or more of the plurality of non-3 GPP devices that are at least one of no longer authorized or no longer available to access the network via the terminal.

11. The terminal as claimed in claim 9, wherein the session modification command comprises respective identity information associated with one or more of the plurality of non-3 GPP devices that are at least one of authorized or available to access the network via the terminal, and does not comprise respective identity information associated with one or more of the plurality of non-3GPP devices that are at least one of no longer authorised or no longer available to access the network via the terminal.

12. An apparatus comprising:means for sending a session modification command to a terminal, the session modification command indicating that a first non-3GPP device, connected to a network via a session between the network and the terminal, is at least one of no longer authorized or no longer available to access the network via the terminal; andmeans for receiving a session modification request from the terminal for modifying the session between the terminal and the network, such that said session can continue without traffic associated with the first non-3GPP device.

13. A method compri sing :receiving a session modification command from a network entity of a network, the session modification command indicating that a first non-3GPP device, connected to thenetwork via a session between the network and a terminal, is at least one of no longer authorized or no longer available to access the network via the terminal; andsending a session modification request to the network entity of the network for modifying the session between the terminal and the network, such that said session can continue without traffic associated with the first non-3GPP device.

14. A method comprising:sending a session modification command to a terminal, the session modification command indicating that a first non-3GPP device, connected to a network via a session between the network and the terminal, is at least one of no longer authorized or no longer available to access the network via the terminal; andreceiving a session modification request from the terminal for modifying the session between the terminal and the network, such that said session can continue without traffic associated with the first non-3GPP device.

15. A computer program comprising computer executable instructions which when run cause the method of claim 13 or 14 to be performed.

Images