Method and apparatus for defining UE behavior in a restricted service area

Abstract

The present disclosure relates to a communication method and system for integrating a fifth generation (5G) communication system and Internet of Things (IoT) technology for supporting higher data rates than fourth generation (4G) systems. The present disclosure can be applied to smart services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, smart retail, safety and security services. A method for user equipment (UE) in a network is provided. The UE is using control plane CIoT 5GS optimization and is in a restricted service area. The method includes determining one or more of a UE mode, a type of required data, and a requested service, and setting a UE behavior for initiating an NAS process based on one or more of the UE mode, the type of required data, and the requested service.

Description

Technical Field

[0001] The present disclosure relates to methods, apparatus, and systems for defining user equipment (UE) behavior in restricted service areas of a network. More specifically, the present disclosure relates to methods, apparatus, and systems for defining cellular Internet of Things (CIoT) UE behavior in restricted service areas in a 3rd Generation Partnership Project (3GPP) fifth generation system (5GS). Background Art

[0002] In order to meet the increased demand for wireless data traffic since the deployment of the fourth generation (4G) communication system, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "beyond 4G networks" or "post-Long Term Evolution (LTE) systems." 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 60 GHz bands) in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are being discussed in 5G communication systems. In addition, in 5G communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), receiving-end interference cancellation, etc. In 5G systems, hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet, a human-centric network of connected devices where humans generate and consume information, is now evolving into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), which combines IoT technology with big data processing technologies through connectivity with cloud servers, has emerged. Recent research has focused on sensor networks, machine-to-machine (M2M) communications, and machine-type communications (MTC), as technological elements necessary for IoT implementation. These include sensing technology, wired / wireless communications and network infrastructure, service interface technology, and security technology. Such an IoT environment can provide intelligent Internet technology services, creating new value for human life by collecting and analyzing data generated between connected things. Through the convergence and integration of existing information technology (IT) and various industrial applications, the IoT can be applied in a variety of fields, including smart homes, smart buildings, smart cities, smart cars (connected vehicles), smart grids, healthcare, smart appliances, and advanced medical services.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. Cloud radio access networks (RAN), as an application of the aforementioned big data processing technologies, can also be considered an example of the convergence between 5G and IoT technologies.

[0005] The above information is presented as background information only to assist in understanding the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art to the present disclosure. Summary of the Invention

[0006] Technical issues

[0007] Service area restrictions define the rules that restrict access to a service and the exceptions to those rules (if applicable). However, CIoT 5GS optimized services do not take service area restrictions into account. Therefore, how a UE behaves when using CIoT 5GS optimization and when the UE is in a restricted service area is not defined at all.

[0008] Technical Solutions

[0009] Aspects of the present disclosure address at least the above-mentioned problems and / or disadvantages and provide at least the advantages described below. Accordingly, one aspect of the present disclosure is to provide an apparatus and method for defining UE behavior when CIoT optimization is used and the UE is in a restricted service area.

[0010] Another aspect of the present 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 a UE is in a restricted service area.

[0011] According to one aspect of the present disclosure, a method is provided for a user equipment (UE) in a network, wherein the UE is using a control plane cellular Internet of Things (CIoT) 5G system (5GS) optimization and is in a restricted service area. The method includes identifying one or more of a mode of the UE, a type of required data, and a requested service, and setting a UE behavior for initiating an NAS procedure based on one or more of the mode of the UE, the type of required data, and the requested service.

[0012] According to another aspect of the present disclosure, a UE using control plane CIoT 5GS optimization and in a restricted service area is provided. The UE includes a transceiver and at least one processor coupled to the transceiver, the processor being configured to identify one or more of a UE mode, a type of required data, and a requested service, and to set a UE behavior for initiating a NAS procedure based on one or more of the UE mode, the type of required data, and the requested service.

[0013] According to another aspect of the present disclosure, a network including a UE is provided, wherein the UE is using control plane CIoT 5GS optimization and is in a restricted service area. The network includes a transceiver and at least one processor coupled to the transceiver and configured to identify one or more of a mode of the UE, a type of required data, and a requested service, and to set a UE behavior for initiating a NAS procedure based on one or more of the mode of the UE, the type of required data, and the requested service.

[0014] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0015] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

[0016] Beneficial effects

[0017] According to examples of the present disclosure, a UE may operate efficiently in a restricted service area.

[0018] Additional aspects and advantages of the invention will be understood and in part will become obvious from the following description, or may be well learned from practice of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0020] Figure 1 is a flow chart illustrating a configuration of UE behavior for initiating a non-access stratum (NAS) procedure according to an embodiment of the present disclosure;

[0021] Figure 2 is a flow chart illustrating a configuration of UE behavior for initiating a NAS procedure according to an embodiment of the present disclosure;

[0022] Figure 3 is a flow chart illustrating a configuration of UE behavior for initiating a NAS procedure according to an embodiment of the present disclosure; and

[0023] Figure 4 is a block diagram of a network entity according to an embodiment of the present disclosure.

[0024] Throughout the drawings, like reference numerals will be understood to refer to like parts, components, and structures. DETAILED DESCRIPTION

[0025] The following description, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in understanding, but these are to be regarded as exemplary only. Therefore, those skilled in the art will recognize that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. Furthermore, descriptions of well-known functions and structures may be omitted for clarity and conciseness.

[0026] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0027] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0028] Throughout the description and claims of this specification, the words "include", "comprises" and "contains" and variations of these words, such as "compose" and "consist of", mean "including but not limited to", and are not intended to (and do not exclude) other features, elements, components, integers, processes, operations, functions, characteristics, properties and / or combinations thereof.

[0029] Throughout the description and claims of this specification, language in the general form of "X for Y" (where Y is some action, procedure, operation, function, or activity, and X is some means for performing the action, procedure, operation, function, or activity) includes means X that is specifically, but not necessarily exclusively, adapted, configured, or arranged to perform Y.

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

[0031] The following documents are referenced here:

[0032] [1]3GPP TS 24.501 V16.3.0

[0033] [2]3GPP TS 23.501 V16.3.0

[0034] Various acronyms and abbreviations used herein are defined at the end of this specification.

[0035] The aforementioned documents disclose various operations and processes, including the following.

[0036] Overview of service area restrictions in 5GS

[0037] 5GS defines the concept of service area restrictions, which determine where a UE can request service, i.e. which Tracking Areas (TAs) or TA Identifiers (TAIs). A service area can be defined as an "allowed tracking area" or a "not allowed tracking area". A UE can request normal service when it is in a TA that is considered an "allowed tracking area" or when it is not in a TA that is considered a "not allowed tracking area", and vice versa, as described in section 5.3.5 of TS 24.501 [1] below:

[0038] The service area restriction includes tracking areas that form an allowed area or a disallowed area. A tracking area belongs to a registered public land mobile network (PLMN) or its equivalent PLMN in a registration area. An allowed area may contain up to 16 tracking areas, or include all tracking areas in a registered PLMN and its equivalent PLMN(s) in a registration area. A disallowed area may contain up to 16 tracking areas. The network communicates the service area restriction to the UE by including either the allowed area or the disallowed area, but not both, in the service area list IE of the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message.

[0039] If the network does not communicate service area restrictions to the UE in the Service Area List IE of the REGISTRATION ACCEPT message, the UE shall consider all tracking areas in the registered PLMN and its (multiple) equivalent PLMNs in the registration area as allowed areas and delete the stored list of "allowed tracking areas" or the stored list of "not allowed tracking areas".

[0040] When the UE receives the Service Area List IE with the Allowed Area Indication during the Registration procedure or the General UE Configuration Update procedure:

[0041] a) If the "List Type" included in the Service Area List IE does not indicate "All TAIs belonging to PLMNs in the registration area are allowed areas", the UE shall delete the old "Allowed Tracking Areas" list and store the tracking areas in the allowed areas as the "Allowed Tracking Areas" list. If the UE has a stored list of "Not Allowed Tracking Areas", the UE shall delete the list; or

[0042] b) If the "Type of List" included in the Service Area List IE indicates "All TAIs belonging to the PLMN in the registered area are allowed areas", the UE shall regard all tracking areas of the registered PLMN and its (multiple) equivalent PLMNs as allowed areas and delete the stored list of "Allowed Tracking Areas" or the stored list of "Not Allowed Tracking Areas".

[0043] When the UE receives a Service Area List IE with a Not Allowed Area Indication during a Registration procedure or a General UE Configuration Update procedure, the UE shall delete the old list of "Not Allowed Tracking Areas" and store the tracking areas in the Not Allowed Areas as the list of "Not Allowed Tracking Areas". If the UE has a stored list of "Allowed Tracking Areas", the UE shall delete the list.

[0044] If the UE is successfully registered to the PLMN and has a stored list of “Allowed Tracking Areas”:

[0045] a) When camped on a cell whose TAI is in the list of “Allowed Tracking Areas”, the UE shall stay or enter state 5GMM-REGISTERED.NORMAL-SERVICE and any 5GMM and 5GSM procedures shall be allowed to be initiated; and

[0046] b) when camped on a cell in a PLMN in the list of registered PLMNs or equivalent PLMNs and whose TAI is in the registration area and not in the list of “allowed tracking areas”, the UE shall enter state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and;

[0047] 1) If the UE is in 5G MM-IDLE mode via 3GPP access, the UE:

[0048] i) Registration procedures for mobility and periodic registration updates using the Uplink Data Status IE are not performed except for emergency services or high priority access; and

[0049] ii) a service request procedure shall not be initiated except for emergency services, high priority access, in response to paging or notification, or to indicate a change in UE state with 3GPP Packet Switched (PS) Data Off; and

[0050] 2) If the UE is in 5G MM-CONNECTED mode through 3GPP access or 5G MM-CONNECTED mode with Radio Resource Control (RRC) inactivity indication, the UE:

[0051] i) Registration procedures for mobility and periodic registration updates using the Uplink Data Status IE are not performed except for emergency services or high priority access; and

[0052] ii) the Service Request Procedure shall not be initiated except for emergency services, high priority access, or in response to a paging or notification on a non-3GPP access; and

[0053] iii) 5GSM procedures shall not be initiated except for emergency services, high priority access or a change in UE state indicating 3GPP PS Data Off.

[0054] If the UE is successfully registered to the PLMN and has a stored list of "Not Allowed Tracking Areas":

[0055] a) when camped on a PLMN that is in the list of registered PLMNs or equivalent PLMNs and whose TAI is not in the list of “not allowed tracking areas”, the UE shall stay in or enter state 5GMM-REGISTERED.NORMAL-SERVICE and any 5GMM and 5GSM procedures shall be allowed to be initiated; and

[0056] b) When camped on a cell whose TAI is in the list of “not allowed tracking areas”, the UE shall enter state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and;

[0057] 1) If the UE is in 5G MM-IDLE mode via 3GPP access, the UE:

[0058] i) Registration procedures for mobility and periodic registration updates utilizing the Uplink Data Status IE should not be performed except for emergency services or high priority access; and

[0059] ii) the service request procedure shall not be initiated except for emergency services, high priority access, in response to paging or notification, or to indicate a change in 3GPP PS Data Off UE state; and

[0060] 2) If the UE is in 5G MM-CONNECTED mode or 5G MM-CONNECTED mode with RRC inactivity indication through 3GPP access, the UE:

[0061] i) except for emergency services or high priority access, the registration procedure should not be performed for mobility and registration updates utilizing the Uplink Data Status IE; and

[0062] ii) the Service Request Procedure shall not be initiated except for emergency services, high priority access, or in response to a paging or notification on a non-3GPP access; and

[0063] iii) 5GSM procedures shall not be initiated except for emergency services, high priority access or a change in UE state indicating 3GPP PS Data Off.

[0064] The list of "allowed tracking areas" and the list of "disallowed tracking areas" should be erased when the following conditions occur:

[0065] a) the UE is switched off; and

[0066] b) Removal of the UICC containing the Universal Subscriber Identity Module (USIM).

[0067] When a tracking area is added to the list of “5GS prohibited roaming tracking areas” or the list of “5GS prohibited regional service tracking areas” as specified in subclauses 5.5.1.2.5 or 5.5.1.3.5, the tracking area shall be removed from the list of “allowed tracking areas” if it already appears in the list of “allowed tracking areas”, or removed from the list of “disallowed tracking areas” if it already appears in the list of “disallowed tracking areas”.

[0068] As can be seen above, when the UE is in a TA that is considered a "Not Allowed Tracking Area", only certain services such as emergency services or reporting of 3GPP PS Data Off are allowed.

[0069] Overview of CIoT Small Data Rate Control

[0070] As part of 5G CIoT, the concept of small data rate control is introduced and it enables the network to limit the maximum number of data packets that a CIoT UE (i.e. a UE in narrowband (NB)-N1 mode or wideband (WB)-N1 mode) can send in a specific time interval. Small data rate control also defines the total amount of so-called exception data that a UE can send in a specific time interval. Exception data is a form of high priority data, hence the name "exceptional data" for exception data reporting. It should be noted that a separate RRC establishment cause is used to distinguish connections initiated for exception data reporting for UEs in NB-N1 mode, as described in section 5.31.14.3 of TS 23.501 [2]. The small data rate control parameter is provided to the UE during protocol data unit (PDU) session establishment in the (extended) protocol configuration option (e) PCO parameter.

[0071] The Home Session Management Function ((H-)SMF) may consider, for example, operator policy, subscription, Data Network Name (DNN), Single Network Slice Selection Assistance Information (S-NSSAI), Radio Access Technology (RAT) type, etc. to determine whether to apply small data rate control. The (H-)SMF may 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 to be implemented.

[0072] Small data uplink rate control applies to data PDUs (NAS data PDUs) sent on a PDU session over a data radio bearer or a signaling radio bearer.

[0073] The rate control information is separate for uplink and downlink and has the following form:

[0074] - the integer 'number of packets per time unit', and

[0075] - integer 'number of additional allowed anomaly report packets per time unit' once the rate control limit is reached.

[0076] The UE will 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 "additional allowed number of exception reports per time unit" is not exceeded. The UE will consider this rate control instruction valid until it receives a new instruction from the (H-)SMF.

[0077] 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.

[0078] When a PDU session is released, the small data rate control state (including the number of packets still allowed in a given time unit, the number of additional exception reports still allowed in a given time unit, and the end time of the current small data rate control validity period) can be stored in the Access and Mobility Management Function (AMF) so that it can be retrieved for subsequent re-establishment of a new PDU session.

[0079] When a new PDU session is subsequently established, the (H-)SMF may receive the previously stored small data rate control state in addition to the configured small data rate control parameters, and if the validity period has not expired, it provides the parameters to the UE and UPF / NEF in the PCO as the parameters for initial application. If the parameters for initial application are provided, once the small data rate control validity period for initial application expires, the UE and UPF or NEF use the configured small data rate control parameters.

[0080] NOTE 2 For very long time intervals, storage of small data rate control state information may be implementation specific.

[0081] Small data rate control is based on the "maximum allowed rate" in each direction. If the (H-)SMF provides 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 data packets per time unit".

[0082] UPF or NEF can enforce the uplink rate by dropping or delaying packets that exceed the "maximum allowed rate". UPF or NEF will enforce the downlink rate by dropping or delaying packets that exceed the downlink portion of the "maximum allowed rate".

[0083] NOTE 3: It is assumed that the serving PLMN rate is high enough not to interfere with the low data rate control, as low data rate control (if used) is assumed to allow for fewer messages. NAS PDUs associated with exception reporting are not subject to the serving PLMN rate control.

[0084] For NB-IoT, the AMF maintains a "MO exception data counter", which is incremented when the RRC establishment cause "MO exception data" is received from the 5G RAN (NG-RAN). The AMF reports the "MO exception data counter" to all (H-)SMFs with PDU sessions subject to small data rate control and notifies the SMF when the UE is accessing with the "MO exception data" RRC establishment cause. Upon receiving such indication of the "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 is applied. After receiving the "MO exception data counter", each NEF and UPF regards the PDUs transmitted during the RRC connection established for "MO exception data" as exception data for small data rate control purposes. The UPF indicates on its Charging Data Record (CDR) each use of the relevant counter for the RRC establishment cause "MO exception data".

[0085] NOTE 4: Since it is not possible to distinguish between exception data PDUs and normal priority PDUs in an RRC connection, the AMF only counts the number of RRC connection establishments with “MO exception data” priority.

[0086] If the UE moves to the Evolved Packet Core (EPC), the user plane components of the UE and PGW (PGW-U) + UPF store the current small data rate control state of all unreleased PDU sessions. If the UE moves back to the 5G Core (5GC), the stored small data rate control state is restored and continues to apply to the (multiple) PDU sessions moved from the EPC to the 5GC, taking into account the remaining validity period of the stored small data rate control state. When the UE moves to the EPC, if the PDU session was released when the UE was connected to the EPC and was re-established when the UE moved to the 5GC, the small data rate control state of all (multiple) PDU sessions may also be stored in the AMF. The time for storing the small data rate control state information is implementation specific.

[0087] Finally, it should be noted that small data rate control applies to CIoT data sent over the user plane or the control plane, as described in the text cited above.

[0088] The above information is presented as background information only to assist in understanding the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art to the present disclosure.

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

[0090] The following examples apply to 3GPP 5G and use terminology associated therewith. However, those skilled in the art will appreciate that the technology disclosed herein is not limited to 3GPP 5G. For example, the functionality of the various network entities and messages disclosed herein can be applied to corresponding or equivalent entities and messages in other communication systems or standards. Corresponding or equivalent entities and messages can be viewed as entities and messages that perform the same or similar roles in the network. Those skilled in the art 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 conjunction with the examples disclosed herein.

[0091] A particular network entity may be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, and / or as a virtualized function instantiated on an appropriate platform (eg, on a cloud infrastructure).

[0092] It will be understood by those skilled in the art that the present disclosure is not limited to the specific examples disclosed herein. For example:

[0093] The technology disclosed herein is not limited to 3GPP 5G.

[0094] • One or more entities in the examples disclosed herein may be replaced with one or more alternative entities that perform equivalent or corresponding functions, procedures, or operations.

[0095] • One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals, or other types of information carriers that convey equivalent or corresponding information.

[0096] • One or more other elements or entities may be added to the examples disclosed herein.

[0097] • In some examples, one or more non-essential elements or entities may be omitted.

[0098] • The functionality, process, or operation of a particular entity in one example may be divided between two or more separate entities in another example.

[0099] • The functions, processes, or operations of two or more separate entities in one example may be performed by a single entity in alternative examples.

[0100] • Information carried by a particular message in one example may be carried by two or more separate messages in another example.

[0101] • Information carried by two or more separate messages in one example may be carried by a single message in another example.

[0102] • In alternative examples, the order in which operations are performed and / or the order in which messages are sent may be modified, if possible.

[0103] Certain examples of the present disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions and / or methods thereof. Certain examples of the present disclosure may be provided in the form of a system including one or more such apparatus / device / network entities and / or methods thereof.

[0104] In related art technologies, such as those mentioned above, the following problems arise.

[0105] Undefined CIoT UE behavior when in restricted service area

[0106] When the UE is in a restricted service area, i.e. when the TA indication in the Service Area List IE is set to "Not Allowed Tracking Area", only specific services are allowed. However, the current specification does not address CIoT UEs that may be in a restricted service area when the UE's mode is 5GMM CONNECTED mode, 5GMM CONNECTED mode with RRC Inactive Indication, or 5GMM-IDLE mode. This is particularly problematic for UEs using control plane CIoT 5GS optimization, for which data is sent over the control plane. Note that when the UE is in 5GMM CONNECTED mode, such a UE will use uplink (UL) NAS TRANSPORT messages to send data (called CIoT user data) over NAS. However, typically 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. Therefore, when the UE is in a restricted service area, the UE behavior when using CIoT 5GS optimization should be defined for these cases.

[0107] Furthermore, there is no defined behavior for UEs that need to send exception data reports that are considered to be higher priority data than "normal" data.

[0108] Furthermore, the current specification would prohibit the establishment of a PDU session for exception data reporting because, according to the text quoted above, the UE “shall not initiate 5GSM procedures except for emergency services, high priority access, or a change in UE state indicating 3GPP PS Data Off.” This behavior is not suitable for exception data reporting.

[0109] Certain examples of the present disclosure address the aforementioned issues. For example, certain examples of the present disclosure define UE behavior when CIoT optimization is used and the UE is in a restricted service area. Certain examples of the present disclosure set conditions for sending different types of NAS messages based on the type of data or service required by the UE when in a restricted service area.

[0110] Therefore, certain examples of the present disclosure may apply one or more of the following techniques.

[0111] Certain examples of the present 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 required data, and a requested service; and setting a UE behavior for initiating a NAS procedure based on one or more of the mode of the UE, the type of required data, and the requested service.

[0112] In certain examples of the present disclosure, UE behavior may include one or more of: allowed behavior; prohibited behavior; and required behavior.

[0113] In certain examples of the present disclosure, UE behavior includes UE behavior according to one or more examples disclosed herein.

[0114] Certain examples of the present disclosure provide a UE configured to operate according to a method according to any example disclosed herein.

[0115] In some examples, setting behavior can include:

[0116] If the UE is in 5G MM-IDLE mode with a suspend indication (e.g., via 3GPP access),

[0117] The UE shall not request lower layers to resume a suspended connection.

[0118] In addition to performing one or more actions of predefined types.

[0119] In some examples, the one or more predefined types of operations may include sending a UL NAS TRANSPORT message including data of the one or more predefined types.

[0120] In some examples, the one or more predefined types of operations may include one or more of SMS and sending a location services message.

[0121] In some examples, the one or more predefined types of operations may include one or more of responding to a notification received (e.g., via a non-3GPP access); sending a SOR transmit container; sending a UE policy container; and sending a UE parameter update transmit container.

[0122] In some examples, setting behavior can include:

[0123] If the UE is in 5G MM-CONNECTED mode or 5G MM-CONNECTED mode with RRC Inactivity Indication (e.g., via 3GPP access),

[0124] The UE shall not perform the NAS transmission procedure.

[0125] In addition to sending a UL NAS TRANSPORT message including data of one or more predefined types.

[0126] In some examples, the data may include one or more of: SMS, LPP message, location service message, SOR delivery container, UE policy container, UE parameter update delivery container, and CIoT user data container.

[0127] In some examples, setting behavior can include:

[0128] If the UE is in 5G MM-CONNECTED mode with RRC Inactivity indication (e.g., accessed via 3GPP),

[0129] The UE shall not request lower layers to resume a suspended connection.

[0130] In addition to performing one or more actions of predefined types.

[0131] In some examples, the one or more predefined types of operations may include one or more of: emergency services, high priority access, and responding to a page or responding to a notification received (eg, via non-3GPP access).

[0132] In some examples, setting behavior can include:

[0133] If the UE is in 5G MM-CONNECTED mode or 5G MM-CONNECTED with RRC Inactivity Indication,

[0134] The UE shall not send UL NAS TRANSPORT message with the payload type set to "CIoT User Data Container".

[0135] Unless the UE receives a UL NAS TRANSPORT with the payload type set to "CIoT User Data Container".

[0136] In some examples, setting behavior can include:

[0137] If, in response to paging, the UE transitions to 5G MM-CONNECTED mode using a SERVICE REQUEST message or REGISTRATION REQUEST message,

[0138] The UE may send a UL NAS TRANSPORT message with the payload type set to "CIoT User Data Container".

[0139] In some examples, setting behavior can include:

[0140] If the UE is in 5G MM-CONNECTED mode and NB-N1 mode, and

[0141] If the UE needs to send CIoT user data for abnormal data reporting,

[0142] The UE shall send a UL NAS TRANSPORT message with the payload type set to "CIoT User Data Container".

[0143] In some examples, setting behavior can include:

[0144] If the UE is in 5G MM-CONNECTED mode and NB-N1 mode, and

[0145] If the RRC connection is established with the RRC establishment cause set to mo-ExceptionData,

[0146] The UE may send a UL NAS TRANSPORT message with the payload type set to "CIoT User Data Container".

[0147] In some examples, setting behavior can include:

[0148] If the UE is in 5G MM-CONNECTED mode, and

[0149] If the UE establishes a PDU session for the purpose of exception data reporting,

[0150] The UE shall send a PDU Session Establishment Request message in the UL NAS TRANSPORT message.

[0151] In some examples,

[0152] If the maximum number of active user plane resources is reached and the UE's upper layers request user plane resources for exception data reporting,

[0153] The UE shall (is allowed to) send a PDU Session Release Request message in a UL NAS TRANSPORT message to release the PDU Session in order to establish another PDU Session for exception data reporting.

[0154] In some examples, setting behavior can include:

[0155] If the UE is in 5GMM-IDLE mode,

[0156] The UE is not allowed to initiate the service request process.

[0157] Unless the UE needs to establish a PDU session for abnormal data reporting, or requests user plane resource establishment to send data for abnormal data reporting, or uses a control plane service request message to send abnormal data report.

[0158] In some examples, setting behavior can include:

[0159] If the UE is in 5G MM-CONNECTED mode,

[0160] The UE is not allowed to initiate the service request process.

[0161] Unless the UE needs to request user plane resource establishment to send data for abnormal data reporting.

[0162] In some examples, setting behavior can include:

[0163] If the UE is in 5G MM-IDLE mode with a suspend indication,

[0164] The UE shall not request the lower layers to restore the connection.

[0165] Unless the UE needs to send exception data for exception data reporting, or the UE needs to send a PDU session establishment request message for sending exception data for exception data reporting, or the UE needs to release the PDU session (after the maximum number of active user plane resources is reached and the UE's upper layer requests user plane resources for exception data reporting) in order to establish another PDU session for exception data reporting.

[0166] Certain examples of the present disclosure provide a network including a UE according to any of the examples disclosed herein.

[0167] Certain examples of the present disclosure provide a computer program comprising instructions that, when executed by a computer or a processor, cause the computer or processor to perform a method according to any example disclosed herein.

[0168] Certain examples of the present disclosure provide a computer or processor readable data carrier having stored thereon a computer program according to any example disclosed herein.

[0169] UE behavior with regard to using CIoT optimization when in a restricted service area

[0170] This section proposes the UE behavior when the UE uses CIoT optimization 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 "Not Allowed Tracking Area" in the Service Area List IE, or the UE is not in a TA that is set to "Allowed Tracking Area" in the Service Area List IE. The UE behavior should be as follows:

[0171] The default behavior should be that a UE that is using control plane CIoT 5GS optimization, is in 5G MM-CONNECTED mode, or is in 5G MM-CONNECTED mode with RRC inactivity indication should not send UL NAS TRANSPORT with the payload type set to "CIoT user data container". However, if the UE receives a UL NAS TRANSPORT message with the payload type set to "CIoT user data container", the UE is allowed to send a UL NAS TRANSPORT message with the payload type set to "CIoT user data container". Alternatively, if the UE has transitioned to 5G MM-CONNECTED mode using a SERVICE REQUEST message or a REGISTRATION REQUEST message in response to paging, the UE may send a UL NAS TRANSPORT message with the payload type set to "CIoT user data container".

[0172] If the UE is an NB-N1 mode UE and is in 5G MM-CONNECTED mode, and the UE needs to send CIoT user data for exception data reporting, the UE SHOULD send a UL NAS TRANSPORT message with the payload type set to "CIoT user data container" even if the UE is in a restricted service area. If the RRC connection is established with the RRC establishment cause set to mo-ExceptionData, the UE MAY send a UL NAS TRANSPORT message with the payload type set to "CIoT user data container".

[0173] If a UE in 5G MM-CONNECTED mode establishes a PDU Session for the purpose of exception data reporting, the UE shall send a PDU SESSION SETUP REQUEST message in the UL NAS TRANSPORT message even if the UE is in a restricted service area. If the maximum number of active user plane resources is reached and the UE's upper layers request user plane resources for exception data reporting, the UE shall (is allowed to) send a PDU SESSION RELEASE REQUEST message in the UL NAS TRANSPORT message to release the PDU Session in order to establish another PDU Session for exception data reporting.

[0174] If the UE is in 5G MM-IDLE mode, the UE is not allowed to initiate a service request procedure, or a registration procedure for mobility and periodic registration updates that utilizes the uplink data status IE, unless the UE needs to establish a PDU session for exception data reporting, or requests the establishment of user plane resources for sending data for exception data reporting, or sends an exception data report using a control plane service request message.

[0175] If the UE is in 5G MM-CONNECTED mode, the UE is not allowed to initiate a service request procedure, or a registration procedure for mobility and periodic registration updates that utilize the uplink data status IE, unless the UE needs to request user plane resource establishment to send data for exception data reporting.

[0176] If the UE is in 5G MM-IDLE mode with a suspend indication, the UE shall not request lower layers to resume the connection unless the UE needs to send exception data for exception data reporting, or the UE needs to send a PDU Session Establishment Request message for sending exception data for exception data reporting, or the UE needs to release a PDU Session (after the maximum number of active user plane resources has been reached and the UE's upper layers request user plane resources for exception data reporting) in order to establish another PDU Session for exception data reporting.

[0177] When CIoT 5GS optimization is being used and the UE is in a restricted area, the UE behavior for initiating NAS procedures is undefined, making the UE behavior unpredictable and potentially incompatible with network expectations. This application proposes standardized UE behavior for the identified scenario so that CIoT devices can function predictably when they are in a restricted service area.

[0178] Note that the above proposal also applies when the UE needs to send other data in the UL NAS TRANSPORT message, such as SMS or location service messages or any other data that may be introduced in the future.

[0179] Note that the term "user data associated with an exception event" can also be interpreted as data used for exception reporting.

[0180] Figure 1 A flow chart illustrating a configuration of UE behavior for initiating a NAS procedure according to an embodiment of the present disclosure is shown.

[0181] Specifically, Figure 1 Techniques for determining whether to send data for a UE capable of operating in a particular mode are shown (e.g., using control plane CIoT 5GS optimization).

[0182] refer to Figure 1 In a first operation 101, the UE determines whether it is operating in a certain mode. For example, the UE may determine whether it is using control plane CIoT 5GS optimization. If the UE is using control plane CIoT 5GS optimization, the process proceeds to the next operation 102, otherwise the UE operates according to another mode.

[0183] In operation 102, the UE receives a request to transmit data via the control plane. For example, the request may come from an upper layer and / or the data may be CIoT user data.

[0184] In the next operation 103, the UE performs a first check. For example, the UE may check whether it is in a restricted service area. In some examples, the UE may check whether it is in a disallowed area and / or whether it is outside a permitted area. The UE may decide whether to send data based on the result of the first check. For example, if the UE is not in the restricted service area, the UE sends data. On the other hand, if the UE is in the restricted service area, the process proceeds to the next operation 104.

[0185] In operation 104, the UE performs a second check. For example, the UE may check whether it is in a specific mode. In some examples, the UE may check whether it is in 5G MM-CONNECTED mode or 5G MM-CONNECTED mode with an RRC inactivity indication. The UE may decide whether to send data based on the result of the second check. For example, if the UE is in 5G MM-CONNECTED mode or 5G MM-CONNECTED mode with an RRC inactivity indication, the UE sends data; otherwise, the UE does not send data.

[0186] Those skilled in the art will appreciate that in alternative examples, Figure 1 The operations may be performed in a different order. Specifically, the second check may be performed by the first check to achieve the same overall UE behavior based on the results of the first and second checks.

[0187] Figure 2A flow chart illustrating a configuration of UE behavior for initiating a NAS procedure according to an embodiment of the present disclosure is shown.

[0188] Specifically, Figure 2 Techniques for determining whether to send a NAS message for a UE capable of operating in a particular mode are shown (e.g., using control plane CIoT 5GS optimization).

[0189] refer to Figure 2 In a first operation 201, the UE determines whether it is operating in a certain mode. For example, the UE may determine whether it is using control plane CIoT 5GS optimization. If the UE is using control plane CIoT 5GS optimization, the process proceeds to the next operation 202, otherwise the UE operates according to another mode.

[0190] In operation 202, the UE receives a request to send a NAS message. For example, the request may come from an upper layer.

[0191] In the next operation 203, the UE performs a first check. For example, the UE may check whether it is in a restricted service area. In some examples, the UE may check whether it is in a disallowed area and / or outside a permitted area. The UE may decide whether to send an NAS message based on the result of the first check. For example, if the UE is not in a restricted service area, the UE sends a NAS message. On the other hand, if the UE is in a restricted service area, the process proceeds to the next operation 204.

[0192] In operation 204, the UE performs a second check. For example, the UE may check whether it is in a specific mode. In some examples, the UE may check whether it is in 5GMM-CONNECTED mode or in 5GMM-CONNECTED mode with an RRC inactivity indication. The UE may decide whether to send a NAS message based on the result of the second check. For example, if the UE is not in 5GMM-CONNECTED mode or is not in 5GMM-CONNECTED mode with an RRC inactivity indication, the UE does not send a NAS message, otherwise the process proceeds to the next operation 205. In some embodiments, if the UE is not in 5GMM-CONNECTED mode or is not in 5GMM-CONNECTED mode with an RRC inactivity indication, further checks may be applied, such as based on the type of data or content of the NAS message, to determine whether to send the NAS message. For example, if the UE is not in 5GMM-CONNECTED mode or is not in 5GMM-CONNECTED mode with an RRC inactivity indication, the UE does not send a NAS message unless the data or content of the NAS message is of a specific type, such as SMS or LPP.

[0193] In operation 205, the UE performs a third check. For example, the UE may check whether the request is for sending data through the control plane (e.g., CIoT user data) or a location service message. The UE may decide whether to send a NAS message based on the result of the third check. For example, if the request is for sending data through the control plane (e.g., CIoT user data) or a location service message, the UE sends a NAS message, otherwise the UE does not send a NAS message. In some embodiments, if the request is neither for sending data through the control plane nor for sending a location service message, further checks may be applied, such as based on the type of data or content of the NAS message, to determine whether to send a NAS message. For example, if the request is neither for sending data through the control plane nor for sending a location service message, the UE does not send a NAS message unless the data or content of the NAS message is of a specific type, such as SMS or LPP.

[0194] Those skilled in the art will appreciate that in alternative examples, Figure 2 The operations may be performed in a different order. Specifically, depending on the results of the first to third checks, the first to third checks may be performed in an alternative order to achieve the same overall UE behavior.

[0195] Figure 3 A flow chart illustrating a configuration of UE behavior for initiating a NAS procedure according to an embodiment of the present disclosure is shown.

[0196] Specifically, Figure 3 Techniques for determining whether to send data and / or resume a connection for a UE capable of operating in a particular mode (e.g., using user plane CIoT 5GS optimization) are shown.

[0197] refer to Figure 3 In a first operation 301, the UE determines whether it is operating in a certain mode. For example, the UE may determine whether it is using user plane CIoT 5GS optimization. If the UE is using user plane CIoT 5GS optimization, the process proceeds to the next operation 302, otherwise the UE operates according to another mode.

[0198] In operation 302, the UE receives a request to transmit data. For example, the request may come from an upper layer.

[0199] In the next operation 303, the UE performs a first check. For example, the UE may check whether it is in a restricted service area. In some examples, the UE may check whether it is in a disallowed area and / or whether it is outside a permitted area. Based on the result of the first check, the UE may decide whether to request the lower layer to restore the RRC connection and / or whether to send data. For example, if the UE is not in the restricted service area, the UE may request the lower layer to restore the RRC connection and / or send data. On the other hand, if the UE is in the restricted service area, the process proceeds to the next operation 304.

[0200] In operation 304, the UE performs a second check. For example, the UE may check whether it is in a specific mode. In some examples, the UE may check whether it is in a 5G MM-IDLE mode with a pause indication. The UE may decide whether to request the lower layer to resume the RRC connection and / or whether to send data based on the result of the second check. For example, if the UE is not in a 5G MM-IDLE mode with a pause indication, the UE sends data if the UE has sufficient radio resources, and / or the UE requests the lower layer to resume the RRC connection (to send data), otherwise the process proceeds to the next operation 305.

[0201] In operation 305, the UE performs a third check. For example, the UE may check whether the request is for sending abnormal data or other data. Based on the result of the third check, the UE may decide whether to request the lower layer to resume the suspended connection and send the data. For example, if the request is for sending abnormal data, the UE requests the lower layer to resume the suspended connection and send the data. On the other hand, if the request is for sending other data, the UE does not request the lower layer to resume the suspended connection and does not send the data.

[0202] The skilled person will appreciate that in an alternative example, Figure 3 The operations may be performed in a different order. Specifically, depending on the results of the first to third checks, the first to third checks may be performed in an alternative order to achieve the same overall UE behavior.

[0203] Those skilled in the art will appreciate that a request to send data is an example of an operation that may require initiating a NAS process. Figure 1-3 As described above, a request to send data may result in sending a NAS message by initiating a NAS transfer procedure, in which the UE sends a UL NAS TRANSPORT message.

[0204] Figure 4 is a block diagram of a network entity according to an embodiment of the present disclosure.

[0205] Those skilled in the art will appreciate that network entities may be implemented, for example, as network elements on dedicated hardware, software instances running on dedicated hardware, and / or virtualized functions instantiated on an appropriate platform (e.g., cloud infrastructure).

[0206] refer to Figure 4 , entity or UE 400 includes a processor (or controller) 401, a transmitter 403, and a receiver 405. The receiver 105 is configured to receive one or more messages from one or more other network entities, such as described above. The transmitter 403 is configured to send one or more messages to one or more other network entities, such as described above. The processor 401 is configured to perform one or more operations, such as those described above.

[0207] The technology described herein can be implemented using any appropriately configured device and / or system. Such a device and / or system can be configured to perform a method according to any aspect, embodiment, example, or claim disclosed herein. Such a device may include one or more elements, such as one or more of a receiver, a transmitter, a transceiver, a processor, a controller, a module, a unit, etc., each of which is configured to perform one or more corresponding processes, operations, and / or method operations to implement the technology described herein. For example, the operation / function of X can be performed by a module (or X module) configured to perform X. One or more elements can be implemented in the form of hardware, software, or any combination of hardware and software.

[0208] It should be understood that examples of the present 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, such as a storage device like a read-only memory (ROM), whether erasable or rewritable, or in the form of a memory, such as RAM, a memory chip, device, or integrated circuit, or on an optical or magnetically readable medium, such as, for example, a compact disc (CD), a digital versatile disc (DVD), a magnetic disk, or a tape.

[0209] It should be understood that storage devices and storage media are embodiments of machine-readable storage that are suitable for storing one or more programs comprising instructions that, when executed, implement certain examples of the present disclosure. Thus, certain examples provide programs comprising code for implementing a method, apparatus, or system according to any example, embodiment, aspect, and / or claim disclosed herein, and / or machine-readable storage storing such programs. Furthermore, such programs may be transmitted electronically via any medium, such as a communication signal transmitted over a wired or wireless connection.

[0210] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. A method for a user equipment (UE) in a network, the method comprising: Identifying that the UE is in a restricted service area; Identifying a mode of the UE; as well as In a case where the mode of the UE is a 5GS Mobility Management 5GMM Connection Mode accessed through the 3rd Generation Partnership Project 3GPP or a 5GMM Connection Mode with a Radio Resource Control RRC Inactivity Indication, the non-access stratum NAS transfer procedure is not performed except for the sending of an uplink NAS transfer message including a plurality of predefined types of data including a Cellular Internet of Things CIoT user data container.

2. The method according to claim 1, further comprising: In case that the mode of the UE is 5GMM idle mode with suspension indication accessed through 3GPP, a lower layer is requested to resume a suspended connection for performing one or more predefined types of operations.

3. The method of claim 2, wherein the one or more predefined types of operations include sending an uplink NAS transfer message including data of one or more predefined types.

4. The method of claim 2, wherein the one or more predefined types of operations include one or more of the following: Send Short Message Service (SMS); and Send location service message.

5. The method of claim 2, wherein the one or more predefined types of operations include one or more of the following: responding to notifications received via non-3GPP access; Send roaming guidance SOR transfer container; Send UE policy container; as well as Send UE parameter update delivery container.

6. The method of claim 1 , wherein the plurality of predefined types of data further comprises at least one of the following: Roaming guide SOR transfer container; UE Policy Container; and UE parameter update transmission container.

7. The method according to claim 1, further comprising: In case that the mode of the UE is a 5GMM connected mode with an RRC inactivity indication accessed through 3GPP, the lower layer is requested to resume the suspended connection for performing one or more predefined types of operations.

8. The method of claim 7, wherein the one or more predefined types of operations include one or more of the following: emergency services; High priority access; and Responding to a paging or responding to a notification received via a non-3GPP access.

9. The method according to claim 1, further comprising: in case the mode of the UE is 5GMM connected mode or 5GMM connected mode with RRC inactivity indication, when the UE receives a downlink NAS transport message with a payload type set to the type of CIoT user data container, sending an uplink NAS transport message with a payload type set to the type of CIoT user data container, and In case the UE transitions to 5GMM connected mode with a service request message or a registration request message in response to paging, an uplink NAS transfer message with a payload type set to the type of CIoT user data container is sent.

10. The method according to claim 1, further comprising: In the case where the UE mode is 5GMM connected mode and NB-N1 mode and the UE needs to send CIoT user data for abnormal data reporting, sending an uplink NAS transfer message with a payload type set to CIoT user data container, and In a case where the UE mode is 5GMM connected mode and NB-N1 mode and the RRC connection is established with the RRC establishment cause set to mo-ExceptionData, an uplink NAS transfer message with the payload type set to the type of CIoT user data container is sent.

11. The method according to claim 1 , further comprising: In case the mode of the UE is the 5GMM connected mode and the UE establishes a protocol data unit (PDU) session for abnormal data reporting, a PDU session establishment request message is sent in an uplink NAS transmission message.

12. The method according to claim 11, further comprising: In case the maximum number of active user plane resources is reached and upper layers of the UE request user plane resources for exception data reporting, a PDU session release request message is sent in an uplink NAS transport message to release the PDU session in order to establish another PDU session for exception data reporting.

13. The method according to claim 1, further comprising: In the case where the UE mode is 5GMM idle mode, when the UE needs to establish a PDU session for abnormal data reporting, or request user plane resource establishment for sending data for abnormal data reporting, or send abnormal data report using a control plane service request message, initiate a service request procedure, and When the UE is in 5GMM connected mode, a service request process is initiated when the UE needs to request user plane resource establishment for sending data for abnormal data reporting.

14. The method according to claim 1, further comprising: In the case where the mode of the UE is 5GMM idle mode with a pause indication, when the UE needs to send data for an abnormal data report, or when the UE needs to send a PDU session establishment request message for sending data for an abnormal data report, or when the UE needs to release the PDU session in order to establish another PDU session for sending an abnormal data report, the lower layer is requested to resume the connection.

15. A user equipment (UE) in a network, the UE comprising: transceiver; and at least one processor coupled to the transceiver and configured to: Identifying that the UE is in a restricted service area; Identifying a mode of the UE; as well as In a case where the mode of the UE is a 5GS Mobility Management 5GMM Connection Mode accessed through the 3rd Generation Partnership Project 3GPP or a 5GMM Connection Mode with a Radio Resource Control RRC Inactivity Indication, the non-access stratum NAS transfer procedure is not performed except for the sending of an uplink NAS transfer message including a plurality of predefined types of data including a Cellular Internet of Things CIoT user data container.

Images