Patent Description:
To meet the demand for wireless data traffic having increased since deployment of <NUM>th generation (<NUM>) communication systems, efforts have been made to develop an improved <NUM> or pre-<NUM> communication system. Therefore, the <NUM> or pre-<NUM> communication system is also called a 'Beyond <NUM> Network' or a 'Post long term evolution (LTE) System'. In the <NUM> system, hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as an advanced access technology have been developed.

As technology elements, such as "sensing technology", "wired/wireless communication and network infrastructure", "service interface technology", and "Security technology" have been demanded for IoT implementation, a sensor network, a machine-to-machine (M2M) communication, machine type communication (MTC), and so forth have been recently researched.

For example, technologies, such as a sensor network, machine type communication (MTC), and machine-to-machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas. Application of a cloud radio access network (RAN) as the above-described Big Data processing technology may also be considered to be as an example of convergence between the <NUM> technology and the IoT technology.

"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for <NUM> System (5GS); Stage <NUM> (Release <NUM>)", 3GPP Standard; Technical Specification; 3GPP TS <NUM>, <NUM> December <NUM>, discusses a Non-Access-Stratum (NAS) protocol for <NUM> System (5GS).

Service area restrictions define the rules to restrict access to services and where applicable the exceptions to these rules. However, services for CIoT 5GS optimization were not considered for service area restrictions. Hence, how the UE behaves when CIoT 5GS optimizations are used and when the UE is in a restricted service area was not at all defined.

Accordingly, an aspect of the disclosure is to provide an apparatus and method for defining UE behavior when CIoT optimization is being used and the UE is in a restricted service area.

Another aspect of the disclosure is to set conditions for transmitting different types of non-access stratum (NAS) messages based on the type of data or service required when the UE is in a restricted service area.

In accordance with an aspect of the disclosure, a method of a user equipment (UE) in a network, wherein the UE is using control plane cellular internet of things (CIoT) <NUM> system (5GS) optimization and is in a restricted service area is provided.

In accordance with another aspect of the disclosure, a UE using control plane CIoT 5GS optimization and being in a restricted service area is provided.

According to the examples of this disclosure, the UE may operate efficiently in a restricted service area.

Additional aspects and advantages of the present invention will be partially appreciated and become apparent from the descriptions below, or will be well learned from the practices of the present invention.

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the disclosure as defined by the claims.

Throughout the description and claims of this specification, the words "comprise", "include" and "contain" and variations of the words, for example "comprising" and "comprises", means "including but not limited to", and is not intended to (and does not) exclude other features, elements, components, integers, processes, operations, functions, characteristics, properties and/or groups thereof.

Throughout the description and claims of this specification, language in the general form of "X for Y" (where Y is some action, process, operation, function, or activity and X is some means for carrying out that action, process, operation, function, or activity) encompasses means X adapted, configured or arranged specifically, but not necessarily exclusively, to do Y.

Features, elements, components, integers, processes, operations, functions, characteristics, properties and/or groups thereof described or disclosed in conjunction with a particular aspect, embodiment, example or claim of the disclosure are to be understood to be applicable to any other aspect, embodiment, example or claim described herein unless incompatible therewith.

Herein, the following documents are referenced:.

Various acronyms and abbreviations used herein are defined at the end of this description.

The above documents disclose various operations and procedures, including the following.

5GS defines the concept of service area restrictions which determine where, i.e., which tracking areas (TAs) or TA identities (TAIs) the UE can request a service. The service area can either be defined to be of type "allowed tracking areas" or "non-allowed tracking areas". The UE can request normal service when it is in TAs that are considered to be "allowed tracking areas" or when it is not in TAs that are considered to be "non-allowed tracking areas", and vice versa as described below from section <NUM>. <NUM> of TS <NUM> [<NUM>]:.

The service area restrictions consist of tracking areas forming either an allowed area, or a non-allowed area. The tracking areas belong to either the registered Public Land Mobile Network (PLMN) or its equivalent PLMNs in the registration area. The allowed area can contain up to <NUM> tracking areas or include all tracking areas in the registered PLMN and its equivalent PLMN(s) in the registration area. The non-allowed area can contain up to <NUM> tracking areas. The network conveys the service area restrictions to the UE by including either an allowed area, or a non-allowed area, but not both, in the Service area list IE of a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message.

If the network does not convey the service area restrictions to the UE in the Service area list IE of a REGISTRATION ACCEPT message, the UE shall treat all tracking areas in the registered PLMN and its equivalent PLMN(s) in the registration area as allowed area and delete the stored list of "allowed tracking areas" or the stored list of "non-allowed tracking areas".

When the UE receives a Service area list IE with an allowed area indication during a registration procedure or a generic UE configuration update procedure:.

When the UE receives a Service area list IE with a non-allowed area indication during a registration procedure or a generic UE configuration update procedure, the UE shall delete the old list of "non-allowed tracking areas" and store the tracking areas in the non-allowed area as the list of "non-allowed tracking areas". If the UE has a stored list of "allowed tracking areas", the UE shall delete that list.

If the UE is successfully registered to a PLMN and has a stored list of "allowed tracking areas":.

If the UE is successfully registered to a PLMN and has a stored list of "non-allowed tracking areas":.

The list of "allowed tracking areas", as well as the list of "non-allowed tracking areas" shall be erased when:.

When a tracking area is added to the list of "5GS forbidden tracking areas for roaming" or to the list of "5GS forbidden tracking areas for regional provision of service" as specified in the subclauses <NUM>. <NUM> or <NUM>. <NUM>, the tracking area shall be removed from the list of "allowed tracking areas" if the tracking area is already present in the list of "allowed tracking areas" and from the list of "non-allowed tracking areas" if the tracking area is already present in the list of "non-allowed tracking areas".

As can be seen from the above, only certain services are allowed when the UE is in TAs that are considered to be "non-allowed tracking areas" e.g., emergency services, or reporting of 3GPP PS data off.

As part of <NUM> CIoT, the concept of small data rate control was introduced and it enables the network to limit the maximum number of data packets that can be sent by a CIoT UE (i.e., UE in narrowband (NB)-N1 mode or wideband (WB)-N1 mode) in a certain time interval. Small data rate control also defines the total number of so called exception data that the UE can send in a certain time interval. Exception data is a form of high priority data hence the term "exception data" and is used for exception data reporting. It should be noted that a separate RRC establishment cause is used to differentiate connections that are initiated for exception data reporting for UEs in NB-N1 mode as described in section <NUM>. <NUM> of TS <NUM> [<NUM>]. The small data rate control parameters are provided to the UE during protocol data unit (PDU) session establishment in the (extended) protocol configuration options (e)PCO parameter.

The home session management function ((H-)SMF) may consider, e.g., operator policy, subscription, data network name (DNN), single network slice selection assistance information (S-NSSAI), radio access technology (RAT) type or the like, to determine whether to apply Small Data Rate Control or not. The (H-)SMF can send a Small Data Uplink Rate Control command to the UE using the PCO information element. The (H-)SMF informs the user plane function (UPF) or network exposure function (NEF) of any Small Data Rate Control that shall be enforced.

The Small Data Uplink Rate Control applies to data PDUs sent on that PDU Session by either Data Radio Bearers or Signaling Radio Bearers (NAS Data PDUs).

The rate control information is separate for uplink and downlink and in the form of:.

The UE shall comply with this uplink rate control instruction. If the UE exceeds the uplink 'number of packets per time unit', the UE may still send uplink exception reports if allowed and the 'number of additional allowed exception reports per time unit' has not been exceeded. The UE shall consider this rate control instruction as valid until it receives a new one from (H-)SMF.

When a PDU Session is first established the (H-)SMF may provide the configured Small Data Rate Control parameters to the UE and UPF or NEF.

When the PDU Session is released, the Small Data Rate Control Status (including the number of packets still allowed in the given time unit, the number of additional exception reports still allowed in the given time unit and the termination time of the current Small Data Rate Control validity period) may be stored in the access and mobility management function (AMF) so that it can be retrieved for a subsequent re-establishment of a new PDU Session.

At subsequent establishment of a new PDU Session, the (H-)SMF may receive the previously stored Small Data Rate Control Status and if the validity period has not expired, it provides the parameters to the UE in the PCO and to the UPF/NEF as the initially applied parameters, in addition to the configured Small Data Rate Control parameters. If the initially applied parameters are provided, the UE and UPF or NEF use the configured Small Data Rate Control parameters once the initially applied Small Data Rate Control validity period expires.

Small Data rate control is based on a 'maximum allowed rate' per direction. If (H-)SMF provided the 'number of additional allowed exception report packets per time unit' to the UE, then the 'maximum allowed rate' is equal to the 'number of packets per time unit' plus the 'number of additional allowed exception report packets per time unit'. Otherwise, the 'maximum allowed rate' is equal to the 'number of packets per time unit'.

The UPF or NEF may enforce the uplink rate by discarding or delaying packets that exceed the 'maximum allowed rate'. The UPF or NEF shall enforce the downlink rate by discarding or delaying packets that exceed the downlink part of the 'maximum allowed rate'.

NOTE <NUM>: It is assumed that the Serving PLMN Rate is sufficiently high to not interfere with the Small Data Rate Control as the Small Data Rate Control, if used, is assumed to allow fewer messages. NAS PDUs related to exception reports are not subject to the Serving PLMN Rate Control.

For NB-IoT the AMF maintains an "MO Exception Data Counter" which is incremented when RRC establishment cause "MO exception data" is received from <NUM> RAN (NG-RAN). The AMF reports the "MO Exception Data Counter" to all (H-)SMFs which have PDU Sessions that are subject to Small Data Rate Control and informs the SMF when UE is accessing with "MO exception data" RRC establishment cause. Upon receiving such indication of "MO exception data" RRC establishment cause from the AMF, each (H-)SMF reports the "MO Exception Data Counter" to each UPF and NEF for each PDU Session to which Small Data Rate Control applies. After receiving the "MO Exception Data Counter", each NEF and UPF consider PDUs transferred during an RRC Connection established for "MO Exception data" to be exception data for Small Data Rate Control purposes. The UPF indicates each use of the RRC establishment cause "MO Exception Data" by the related counter on its charging data record (CDR).

NOTE <NUM>: Since Exception Data PDUs and normal priority PDUs cannot be distinguished within an RRC connection, the AMF is only counting the number of RRC Connection establishments with "MO Exception data" priority.

If the UE moves to evolved packet core (EPC) then the UE and the user plane component of PGW (PGW-U)+UPF store the current Small Data Rate Control Status for all PDU Sessions that are not released. If the UE moves back to <NUM> Core (5GC) the stored Small Data Rate Control Status is restored and continues to apply to PDU Session(s) that are moved from EPC to 5GC, taking into account remaining validity period of the stored Small Data Rate Control Status. When the UE moves to EPC the Small Data Rate Control Status for all PDU Session(s) may also be stored in the AMF if the PDU Session is released while the UE is connected to EPC and re-established when the UE moves to 5GC. The time to store the Small Data Rate Control Status information is implementation specific.

Finally, it should be noted that small data rate control applies to both CIoT data that is sent over the user plane or the control plane as stated in the quoted text above.

Certain examples of the disclosure provide methods, apparatus and systems for defining UE behavior in restricted service areas of a network. For example, certain examples of the disclosure provide methods, apparatus and systems for defining CIoT UE behavior in restricted service areas in 3GPP 5GS. However, the skilled person will appreciate that the disclosure is not limited to these examples, and may be applied in any suitable system or standard, for example one or more existing and/or future generation wireless communication systems or standards.

The following examples are applicable to, and use terminology associated with, 3GPP <NUM>. However, the skilled person will appreciate that the techniques disclosed herein are not limited to 3GPP <NUM>. For example, the functionality of the various network entities and messages disclosed herein may be applied to corresponding or equivalent entities and messages in other communication systems or standards. Corresponding or equivalent entities and messages may be regarded as entities and messages that perform the same or similar role within the network. The skilled person will also appreciate that the transmission of information between network entities is not limited to the specific form, type or order of messages described in relation to the examples disclosed herein.

A particular network entity may be implemented as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., on a cloud infrastructure.

The skilled person will appreciate that the disclosure is not limited to the specific examples disclosed herein. For example:.

Certain examples of the disclosure may be provided in the form of an apparatus/device/network entity configured to perform one or more defined network functions and/or a method therefor. Certain examples of the disclosure may be provided in the form of a system comprising one or more such apparatuses/devices/network entities, and/or a method therefor.

In the techniques of the related art, for example those referred to above, there occur the following problems.

Only specific services are to be allowed when the UE is in a restricted service area i.e., when the TAs in the Service area list IE indicate are set to "non-allowed tracking areas". However, the current specification does not address CIoT UEs that may be in a restricted service area either when the UE's mode is 5GMM-CONNECTED mode, or 5GMM-CONNECTED mode with RRC inactive indication, or 5GMM-IDLE mode. This is especially problematic for UEs that use control plane CIoT 5GS optimization for which the data is sent over the control plane. Note that such a UE will use the uplink (UL) NAS TRANSPORT message to send data over NAS (referred to as CIoT user data) when the UE is in 5GMM-CONNECTED mode. However, normally in a restricted service area, the UE is not allowed to send data unless it is for emergency services, or if the UE is a high priority access UE. As such, the UE's behavior when using CIoT 5GS optimization should be defined for the cases when the UE is in restricted service areas.

Moreover, this behavior is not defined for UEs that need to send exception data reports which are considered to be of higher priority data than "normal" data.

Furthermore, the current specification would prohibit the establishment of a PDU session for exception data reporting as the UE, per the quoted text above, "shall not initiate a 5GSM procedure except for emergency services, high priority access or indicating a change of 3GPP PS data off UE status". This behavior does is not suitable for exception data reporting.

Certain examples of the disclosure address the above problems. For example, certain examples of the disclosure define UE behavior when CIoT optimization is being used and the UE is in a restricted service area. Certain examples of the disclosure set conditions for sending different types of NAS messages based on the type of data or service required when the UE is in a restricted service area.

Accordingly, certain examples of the disclosure may apply one or more of the following techniques.

Certain examples of the disclosure provide a method, for a UE in a network, wherein the UE is using control plane CIoT 5GS optimization and is in a restricted service area, the method comprising: determining one or more of a mode of the UE, a type of data required, and a service requested; and setting a UE behavior for initiating a NAS procedure based on one or more of the mode of the UE, the type of data required, and the service requested.

In certain examples of the disclosure, the UE behavior may comprise one or more of: an allowed behavior; a prohibited behavior; and a required behavior.

In certain examples of the disclosure, the UE behavior comprises UE behavior according to one or more of the examples disclosed herein.

Certain examples of the disclosure provide a UE configured to operate according to a method according to any of the examples disclosed herein.

In certain examples, setting the behavior may comprise:.

In certain examples, the one or more predefined types of operation may comprise sending an UL NAS TRANSPORT message comprising one or more predefined types of data.

In certain examples, the one or more predefined types of operation may comprise one or more of an SMS and a sending a location service message.

In certain examples, the one or more predefined types of operation comprise responding to notification received (e.g., over non-3GPP access); sending an SOR transport container; sending a UE policy container; and sending a UE parameters update transport container.

In certain examples, the data comprises one or more of an SMS, an LPP message, a location services message, an SOR transport container, a UE policy container, a UE parameters update transport container, and a CIoT user data container.

In certain examples, the one or more predefined types of operation may comprise one or more of: emergency services, high priority access, and responding to paging or responding to notification received (e.g., over non-3GPP access).

In an embodiment, setting the behavior may comprise:.

In certain examples, setting the behavior may comprise:\.

Certain examples of the disclosure provide a network comprising a UE according to any of the examples disclosed herein.

Certain examples of the disclosure provide a computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according to any of the examples disclosed herein.

Certain examples of the disclosure provide a computer or processor-readable data carrier having stored thereon a computer program according to any of the examples disclosed herein.

This section proposes the UE behavior when the UE is using CIoT optimizations and is in a restricted service area. Note that "restricted service area" can mean that the UE is in a TA that is set to "non-allowed tracking area" in the Service area list IE, or the UE is not in a TA that is set to be "allowed tracking area" in the Service area list IE. The UE behavior should be as follows:.

The UE behavior for initiating NAS procedures when CIoT 5GS optimization is being used and the UE is in a restricted area is not defined thereby leaving the UE behavior unpredictable and possible incompatible with the network expectation. The present application proposes standardized UE behavior for the identified scenario such that a CIoT device can predictably operate when it is in a restricted service area.

Note that the proposals above also apply when the UE needs to send other data in the UL NAS TRANSPORT message, such as SMS or location service message or any other data that may be introduced in the future.

Note that the term "user data is related to an exceptional event" can also be interpreted to mean data for exception reporting.

<FIG> illustrates a flowchart illustrating setting of a UE behavior for initiating a NAS procedure according to an embodiment of the disclosure.

In particular, <FIG> illustrates a technique for determining whether to send data for a UE capable of operating in a certain mode (e.g., using control plane CIoT 5GS optimization).

Referring to <FIG>, in a first operation <NUM>, the UE determines if it is operating in a certain mode. For example, the UE may determine if it is using control plane CIoT 5GS optimization. If the UE is using control plane CIoT 5GS optimization, the flow proceeds to a next operation <NUM>, otherwise the UE operates according to another mode.

In operation <NUM>, the UE receives a request to send data over the control plane. For example, the request may come from upper layers and/or the data may be CIoT user data.

In a next operation <NUM>, the UE performs a first check. For example, the UE may check if it is in a restricted service area. In certain examples, the UE may check if it is in a non-allowed area and/or if it is outside of an allowed area. The UE may decide whether or not to send the data based on a result of the first check. For example, if the UE is not in a restricted service area then the UE sends the data. On the other hand, if the UE is in a restricted service area then the flow proceeds to a next operation <NUM>.

In operation <NUM>, the UE performs a second check. For example, the UE may check if it is in a certain mode. In certain examples, the UE may check if it is in 5GMM-CONNECTED mode or in 5GMM-CONNECTED mode with RRC inactive indication. The UE may decide whether or not to send the data based on a result of the second check. For example, if the UE is in 5GMM-CONNECTED mode or in 5GMM-CONNECTED mode with RRC inactive indication then the UE sends the data, otherwise the UE does not send the data.

The skilled person will appreciate that the operations of <FIG> may be performed in a different order in alternative examples. In particular, the second check may be performed by the first check to achieve the same overall UE behavior in dependence on the results of the first and second checks.

In particular, <FIG> illustrates a technique for determining whether to send a NAS message for a UE capable of operating in a certain mode (e.g., using control plane CIoT 5GS optimization).

In operation <NUM>, the UE receives a request to send a NAS message. For example, the request may come from upper layers.

In a next operation <NUM>, the UE performs a first check. For example, the UE may check if it is in a restricted service area. In certain examples, the UE may check if it is in a non-allowed area and/or if it is outside of an allowed area. The UE may decide whether or not to send the NAS message based on a result of the first check. For example, if the UE is not in a restricted service area then the UE sends the NAS message. On the other hand, if the UE is in a restricted service area then the flow proceeds to a next operation <NUM>.

In operation <NUM>, the UE performs a second check. For example, the UE may check if it is in a certain mode. In certain examples, the UE may check if it is in 5GMM-CONNECTED mode or in 5GMM-CONNECTED mode with RRC inactive indication. The UE may decide whether or not to send the NAS message based on a result of the second check. For example, if the UE is not in 5GMM-CONNECTED mode or not in 5GMM-CONNECTED mode with RRC inactive indication then the UE does not send the NAS message, otherwise the flow proceeds to a next operation <NUM>. In some embodiments, if the UE is not in 5GMM-CONNECTED mode or not in 5GMM-CONNECTED mode with RRC inactive indication then a further check may be applied, for example based on the type of data or content of the NAS message, to determine whether or not to send the NAS message. For example, if the UE is not in 5GMM-CONNECTED mode or not in 5GMM-CONNECTED mode with RRC inactive indication then the UE does not send the NAS message unless the data or content of the NAS message is of a certain type, for example SMS or LPP.

In operation <NUM>, the UE performs a third check. For example, the UE may check if the request is for sending data over control plane (e.g., CIoT user data) or a location services message. The UE may decide whether or not to send the NAS message based on a result of the third check. For example, if the request is for sending data over control plane (e.g., CIoT user data) or a location services message then the UE sends the NAS message, otherwise the UE does not send the NAS message. In some embodiments, if the request is for sending neither data over control plane nor a location services message then a further check may be applied, for example based on the type of data or content of the NAS message, to determine whether or not to send the NAS message. For example, if the request is for sending neither data over control plane nor a location services message then the UE does not send the NAS message unless the data or content of the NAS message is of a certain type, for example SMS or LPP.

The skilled person will appreciate that the operations of <FIG> may be performed in a different order in alternative examples. In particular, the first to third checks may be performed in an alternative order to achieve the same overall UE behavior in dependence on the results of the first to third checks.

In particular, <FIG> illustrates a technique for determining whether to send data and/or resume a connection for a UE capable of operating in a certain mode (e.g., using user plane CIoT 5GS optimization).

Referring to <FIG>, in a first operation <NUM>, the UE determines if it is operating in a certain mode. For example, the UE may determine if it is using user plane CIoT 5GS optimization. If the UE is using user plane CIoT 5GS optimization, the flow proceeds to a next operation <NUM>, otherwise the UE operates according to another mode.

In operation <NUM>, the UE receives a request to send data. For example, the request may come from upper layers.

In a next operation <NUM>, the UE performs a first check. For example, the UE may check if it is in a restricted service area. In certain examples, the UE may check if it is in a non-allowed area and/or if it is outside of an allowed area. The UE may decide whether or not to request the lower layers to resume the RRC connection and/or whether or not to send data based on a result of the first check. For example, if the UE is not in a restricted service area then the UE requests the lower layers to resume the RRC connection and/or sends the data. On the other hand, if the UE is in a restricted service area then the flow proceeds to a next operation <NUM>.

In operation <NUM>, the UE performs a second check. For example, the UE may check if it is in a certain mode. In certain examples, the UE may check if it is in 5GMM-IDLE mode with suspend indication. The UE may decide whether or not to request the lower layers to resume the RRC connection and/or whether or not to send the data based on a result of the second check. For example, if the UE is not in 5GMM-IDLE mode with suspend indication then the UE sends the data if the UE has sufficient radio resources, and/or the UE requests the lower layers to resume the RRC connection (to send the data), otherwise the flow proceeds to a next operation <NUM>.

In operation <NUM>, the UE performs a third check. For example, the UE may check if the request is for sending exception data or other data. The UE may decide whether or not to request lower layers to resume a suspended connection and send the data based on a result of the third check. For example, if the request is for sending exception data then the UE requests lower layers to resume the suspended connection and sends the data. On the other hand, if the request is for sending other data then the UE does not request lower layers to resume the suspended connection and does not send the data.

The skilled person will appreciate that a request to send data is one example of an operation in which a NAS procedure may need to be initiated. For example, in <FIG> and related description, a request to send data may result in the sending of a NAS message by initiating a NAS transport procedure in which the UE sends the UL NAS TRANSPORT message.

<FIG> is a block diagram of a network entity according to an embodiment of the disclosure.

The skilled person will appreciate that a network entity may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., on a cloud infrastructure.

Referring to <FIG>, an entity or UE <NUM> comprises a processor (or controller) <NUM>, a transmitter <NUM> and a receiver <NUM>. The receiver <NUM> is configured for receiving one or more messages from one or more other network entities, for example as described above. The transmitter <NUM> is configured for transmitting one or more messages to one or more other network entities, for example as described above. The processor <NUM> is configured for performing one or more operations, for example according to the operations as described above.

The techniques described herein may be implemented using any suitably configured apparatus and/or system. Such an apparatus and/or system may be configured to perform a method according to any aspect, embodiment, example or claim disclosed herein. Such an apparatus may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and/or method operations for implementing the techniques described herein. For example, an operation/function of X may be performed by a module configured to perform X (or an X-module). The one or more elements may be implemented in the form of hardware, software, or any combination of hardware and software.

It will be appreciated that examples of the disclosure may be implemented in the form of hardware, software or any combination of hardware and software. Any such software may be stored in the form of volatile or non-volatile storage, for example a storage device like a read only memory (ROM), whether erasable or rewritable or not, or in the form of memory, such as, for example, RAM, memory chips, device or integrated circuits or on an optically or magnetically readable medium, such as, for example, a compact disc (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like.

It will be appreciated that the storage devices and storage media are embodiments of machine-readable storage that are suitable for storing a program or programs comprising instructions that, when executed, implement certain examples of the disclosure. Accordingly, certain example provides a program comprising code for implementing a method, apparatus or system according to any example, embodiment, aspect and/or claim disclosed herein, and/or a machine-readable storage storing such a program. Still further, such programs may be conveyed electronically via any medium, for example a communication signal carried over a wired or wireless connection.

Claim 1:
A method of a user equipment, UE, (<NUM>) in a network, wherein the UE is using control plane cellular internet of things, CloT, <NUM> system, 5GS, optimization, the method comprising:
identifying that the UE (<NUM>) is in a restricted service area;
identifying a mode of the UE (<NUM>); and
in case that the mode of the UE (<NUM>) is 5GS mobility management, 5GMM, connected mode or 5GMM connected mode with radio resource control, RRC, inactive indication over 3rd Generation Partnership Project, 3GPP, access, not transmitting an uplink NAS transport message with a payload type set to a type of the CloT user data container, unless the UE receives a downlink NAS transport message with the payload type set to a type of the CloT user data container.