METHOD FOR MAIN NETWORK NODE, METHOD FOR USER EQUIPMENT, MAIN NETWORK NODE AND USER EQUIPMENT

Description

[001] Divided from BR112020006939-6, filed on August 22, 2019. Technical Field

[002] This disclosure refers to the procedure for updating the parameters related to Unified Access Control. Antecedent Technique

[003] In 5GS, Unified Access Control (UAC) is defined to perform access control of UE signaling in various situations (e.g., congestion, network maintenance, etc.). The UE (User Equipment) is configured with an access identity, and the event is categorized as an access category. The access category is further categorized as a default access category and an operator-defined access category. The operator-defined access category is also denoted as the PLMN operator-defined access category. The PLMN operator-defined access category is sent to the UE in a NAS message. The current operator-defined access categories are 1) DNN, 2) 5G QoS ID, 3) OS ID + APP ID, and 4) S-NSSAI. The operator-defined access categories are based on PLMN.

[004] When the UE is required to access a network, the layer The UE NAS layer determines the access type and access category of the event. The UE NAS layer provides this parameter to the UE access stratum (e.g., RRC layer, SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer) for the access control procedure. The access layer is based on the category. PÊtiÇãã(88703000S9225dd<006 / 0 / 20035ppgg1 7 / 467 2 / 28 The access layer and type determine whether network access is allowed or not. If network access is allowed, the UE establishes the RRC connection and sends the initial NAS message. If network access is not allowed for the event, the Access Stratum (AS) layer informs the NAS layer that access is not allowed for the event. In this case, the NAS layer neither establishes the NAS signaling connection nor sends the NAS message until network access is allowed. List of Citations Non-Patent Literature

[005] NPL 1: 3GPP TS 24.501 V15.0.0 (2018-6) Summary of the Invention Technical Problem

[006] Problem Statement 1:

[007] The network transmits the Operator Defined Access Category Definition (ODACD) to the UE in a NAS message. However, sending the ODACD message in the Configuration Update Command, as defined in NPL 1, is not efficient because the network needs to send the ODACD in the Configuration Update Command message after the registration procedure is successfully completed. This will delay the ODACD configuration on the UE, and therefore the access control mechanism will not be applied by the UE until the Configuration Update Command message reaches the UE after the registration procedure is completed. Additionally, 5GS has a feature called follow-up request. In the case of a follow-up request, the UE includes an active flag information element in the registration request message to establish the PDU session(s) immediately after the registration procedure is completed.In this case, the UAC to limit the MO call to the Operator Defined Access Category does not work at all. PÊtiÇãã(88703000S9225dd<006 / 0 / 20035ppgg1 8 / 467 3 / 28

[008] In these scenarios, if the network is congested and wants to stop signaling from the UE, the network will not be able to stop signaling. The congestion situation may worsen. This requires extra signaling to transmit ODACD.

[009] Furthermore, when the network configures a UE with ODACD, then it is necessary to acknowledge a successful reception of the ODACD on the network, since the NAS message containing the ODACD may not be received by the UE when the NAS message is lost (for example, due to radio link failure between the UE and the NG-RAN before the NAS message is transferred to the UE).

[0010] Problem Statement 2:

[0011] The network may not configure UEs with ODACD due to some network condition (e.g., congestion). In such a situation, the network may not keep track of which UEs are configured with ODACD and which UEs are not configured with ODACD. The network may not be able to configure the UE with ODACD. This UE does not have ODACD configured and will not apply ODACD to the PLMN.

[0012] Also in some situations, the network may not be able to know which UE is currently using the ODACD. In this scenario, when the network needs to update the UE with the ODACD, the network does not know which UEs need to be updated. This can lead the network to update all UEs with the current ODACD, even if the UE already has the latest ODACD configured. This will result in extra signaling. Solution to the Problem

[0013] A method for the main network node, according to a first aspect of this disclosure, includes sending to a User Equipment (UE) a REGISTRATION ACCEPTANCE message containing at least one operator-defined access category definition, wherein containing at least one operator-defined access category definition causes the PÊtiÇãã(88703000S9225dd<006 / 0 / 20035ppgg1 8 / 467 4 / 28 The UE sends the COMPLETE REGISTRATION message; receiving, from the UE, a COMPLETE REGISTRATION message indicating confirmation of receipt of at least one access category definition defined by the operator.

[0014] A main network node according to a second aspect of this disclosure includes memory storage instructions; and at least one hardware processor configured to process the instruction to: send, to a User Equipment (UE), a REGISTRATION ACCEPTANCE message containing at least one operator-defined access category definition, wherein containing at least one operator-defined access category definition causes the UE to send the REGISTRATION COMPLETE message; receive, from the UE, a REGISTRATION COMPLETE message indicating confirmation of receipt of at least one operator-defined access category definition.

[0015] A User Equipment (UE) according to a third aspect of this disclosure includes memory storage instructions; and at least one hardware processor configured to process the instruction to: receive, from a core network node, a REGISTRATION ACCEPTANCE message including at least one operator-defined access category definition; store at least one received operator-defined access category definition; and send, to the core network node, a COMPLETE REGISTRATION message indicating the acknowledgment of at least one received operator-defined access category definition. Brief Description of the Drawings

[0016] [Figure 1] Figure 1 illustrates the signaling flow of solution 1. 11:21^08^12255101893225,4^^:.116118212255.1))00. 1BM857 5 / 28

[0017] [Figure 2] Figure 2 illustrates the signaling flow of solution 2.

[0018] [Figure 3] Figure 3 illustrates the general block diagram for the UE.

[0019] [Figure 4] Figure 4 illustrates the general block diagram for (R) AN.

[0020] [Figure 5] Figure 5 illustrates the general block diagram for AMF. Description of the Implementations Abbreviations

[0021] For the purposes of this document, the abbreviations indicated in 3GPP TR 21.905 V15.0.0 (2018-03) and the following apply. An abbreviation defined in this document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 V15.0.0 (2018-03). 5GC Main Network 5G 5GS 5G System 5G-NA 5G Access Network 5G-GUTI 5G Globally Unique Temporary Identifier 5G S-TMSI 5G Temporary Mobile Signature Identifier 5QI 5G QoS Identifier AF Application Function AMF Access and Mobility Management Function NA Access Node AS Access Stratum AUSF Authentication Server Function CM Connection Management CP Control Plane CSFB Circuit-switched fallback (CS) DL Downlink Ptáçõmímss^^ 6 / 28 DN Data Network DNAI Access Identifier DN DNN Data Network Name EDT Data Advance Transmission EPS Evolved Packet System EPC Evolved Packet Core FQDN Fully Qualified Domain Name GFBR Guaranteed Stream Bit Rate GMLC Gateway Mobile Location Center GPSI Generic Public Signature Identifier GUAMI Globally Unique AMF Identifier HR National Roaming I-RNTI Temporary Radio Network Identifier LADN Local Area Data Network LBO Local Interrupt (roaming) LMF Location Management Function LRF Location Recovery Function MAC Medium Access Control MFBR Maximum Stream Bit Rate MICO Mobile Connection Initiated Only MME Mobility Management Entity N3IWF Non-3GPP Common Work Function NAI Network Access Identifier NAS Non-Access Stratum NEF Network Exposure Function NF NG-RAN Network Function, Next Generation NR Radio Access Network, New NRF RadioNetwork Repository Function NSI ID Network Slice Instance Identifier 1121^00885125510189325,45^:.11611851255,1^0.11.2112 / 857 7 / 28 NSSAI Network Slice Selection Assistance Information NSSF Network Slice Selection Function NSSP Network Slice Selection Policy PCF Policy Control Function PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PLMN Public Terrestrial Mobile Network PPD Paging Policy Differentiation PPI Paging Policy Indicator PSA Session Anchor PDU QFI QoS Flow Identifier QoE Quality of Experience (R)NA RLC Radio Access Network RM Record Management RQA Reflective QoS Attribute RQI Reflective QoS Indication RRC Radio Resource Control SANR New Autonomous Radio SBA Service-Based Architecture SBI Service-Based Interface SD Slice Differentiator SDAP Service Data Adaptation Protocol SEAF Security Anchor Function SEPP Security Edge Protection Proxy SMF Function Session Management Information S-NSSAISlice Selection Assistance Simple Network 11^1^08^1^00893225.4^^:116108:212255.1^0^.212 / / 85 8 / 28 SSC Session and Service Continuity SST Slice / Service Type SUCI Hidden Subscription Identifier SUPI Permanent Subscription Identifier UDSF Unstructured Data Storage Function UL Uplink UL CL Uplink Classifier UPF User Plan Function UDR Unified Data Store URSP UE Route Selection Policy SMS Short Message Service SMSF SMS Function MT Cellular Closed UAC Unified Access Control ODACD Operator-Defined Access Category Definitions Operating System Definitions

[0022] For the purposes of this document, the terms and definitions provided in 3GPP TR 21.905 V15.0.0 (2018-03) and the following apply. A term defined in this document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 V15.0.0 (2018-03).

[0023] First aspect (solution 1 to solve problem statement 1):

[0024] Transmitting a NAS message acknowledging receipt of ODACD in a NAS message.

[0025] Some instances of the first aspect of solution 1 are provided below.

[0026] 1. A network sends ODACD in a NAS message and Ptáçõmímss^^ 9 / 28 starts a timer for an UE. In one case, the network includes an indication requesting the UE to transmit acknowledgment of ODACD reception.

[0027] 2. The UE upon receiving the NAS message containing only The Unified Access Control (UE) system, after receiving an ODACD or both, and an indication requesting that the UE send confirmation of ODACD reception, removes the previously received ODACD, stores the newly received ODACD in the first NAS message, and transmits a NAS message containing an indicator pointing to the successful reception of the ODACD on the network. The UE then applies the received ODACD parameters to the Unified Access Control system.

[0028] 3. When the timer started in step 1 expires, the network retransmits another NAS message with the content defined in step 1.

[0029] Another instance of the first aspect of solution 1 is described below and in Figure 1.

[0030] 1- 2. A network transmits a first message Stratum No Access (NAS) containing an ODACD (Operator Defined Access Category Definitions) information element for a UE. The network starts a T1 timer after transmitting the first NAS message.

[0031] In one example, the first NAS message contains ODACD and an ACK information element requesting that the UE send a second NAS message as an acknowledgment of ODACD reception. The network starts timer T1 only when the ACK and ODACD information are included in the first NAS message; that is, if it does not include the ODACD and the ACK information element, the network does not start timer T1.

[0032] 3. The UE receives the first NAS message. The UE removes the previously received ODACD and stores the newly received ODACD in the first NAS message as the most recent ODACD. 11^1^08^1^00893225,4^^:116108:212255,1^0^.215 / 85 10 / 28

[0033] 4. The UE determines whether the first NAS message contains the ODACD information element. If the first NAS message contains the ODACD information element, the UE will transmit the second NAS message containing the current ODACD or current ODACD information element and ACK, indicating successful reception of the ODACD in the first NAS message or just a NAS message.

[0034] In an example, if the first NAS message contains the ODACD information element and ACK then the UE transmits the second NAS message containing the current ODACD or current ODACD information element and ACK, indicating successful reception of the ODACD in the first NAS message or just a NAS message.

[0035] 5. The second NAS message is lost.

[0036] 6-8. Timer T1 expires and the network retransmits the third NAS message. The third NAS message contains the latest UE ODACD. The network follows the procedure as described in step 1. In one example, the timer expiration in step 6 may occur in a situation where the first NAS message in step 1 is lost.

[0037] 9-10. After receiving the third NAS message, the UE executes the procedure as described in steps 3 and 4.

[0038] 11. Upon receiving the following NAS message containing an information element indicating successful reception from the ODACD, the network pauses time T1. In one example, the network pauses timer T1 when it receives ODACD or ODACD and an information element indicating successful reception from the ODACD. In another example, the network will pause timer T1 when it receives the following NAS message indicating successful reception from the ODACD, that is, the following NAS message does not include any acknowledgment of reception from the ODACD itself or the ODACD itself. 11^1^08^1^00893225,4^^:116108:212255,1^0^.215 / / 85 11 / 28

[0039] In one example, the first NAS message and the third NAS message is the Registration Acceptance message, as defined in TS 24.501 [4] and the second NAS message and the following NAS message is the Registration Complete message, as defined in TS 24.501 [4].

[0040] The T1 unit of the timer can be milliseconds, seconds, minutes, or hours.

[0041] In one example, the first NAS message or the third NAS message is DL NAS TRANSPORT as defined in TS 24.501 [4] and the second NAS message or the following message NAS is UL NAS TRANSPORT as defined in TS 24.501 [4]. Timer T1 is a new timer.

[0042] In one example, the first NAS message or the third NAS message is a new NAS message or an existing NAS message that is not the Configuration Update Command, and the second NAS message or the following NAS message is another new message or an existing NAS message that is not a Complete Configuration Update message. Timer T1 is a new timer.

[0043] In one example, the network or 5GC in solution 1 is the AMF.

[0044] In one example, the network in solution 1 is the MME.

[0045] In an example of solution 1, the information element ACK is always defined together with the ODACD information element. However, the network may indicate the ACK information element to the standalone UE in the first NAS message and the third NAS message whenever the network requires an acknowledgment message from the UE to ensure that all information in the first NAS message or the third NAS message is correctly received by the UE. If the UE receives the ACK information element in the first NAS message and the third NAS message, and the UE has received adequate information, the ACK will be correctly received. 11^1^08^1^00893225,4^^:116108:212255,1^0^.217 / 85 12 / 28 After the first NAS message or the third NAS message, the UE sends the second NAS message or the following NAS message to the network. The second NAS message and the following NAS message may include the ACK information element and an information element requested by the network in the first NAS message or the third NAS message. This mechanism can be thought of as a general mechanism for synchronizing configuration data between the UE and the network.

[0046] In one example, the network does not include the ACK information element. When the UE receives the ODACD information element in a NAS message, then the UE always transmits a NAS message indicating confirmation of ODACD receipt.

[0047] In one example, the UE transmits the second NAS message or the following NAS message without containing any information that explicitly indicates the reception of the ODACD. After the second NAS message or the following NAS message is received on the network, the network determines that the ODACD has been successfully received by the UE.

[0048] Alternatively or in addition to the above, the UE may determine whether or not transmission of the NAS message including ODACD reception acknowledgment is required based on the combination of a specific NAS message and the ODACD IE. The specific NAS message may be the registration acceptance message, the DL NAS TRANSPORT message, or an existing NAS message other than the Configuration Update Command. For example, the 3GPP technical standards may define that the UE will transmit the NAS message including ODACD reception acknowledgment if the specific NAS message received includes the ODACD IE and if the specific NAS message is a Registration Acceptance message. In this situation, if the UE received the registration acceptance message... 11^1^08^1^00893225,4^^:116108:212255,1^^^.217 / / 85 13 / 28 tro, including the ODACD IE, then the EU determines that the transmission of the NAS message, including the ODACD's acknowledgment of receipt, is required.

[0049] Second aspect (Solution 2 solves problem statement 2):

[0050] The EU indicating the current ODACD configuration for the network.

[0051] Some instances of the second aspect of solution 2 are provided below. Figure 2 shows the steps of solution 2.

[0052] 1. When a UE transmits a NAS message to the network, the UE includes a current ODACD for that network. In one instance, the UE transmits the ODACD IE in the NAS message when the UE has not been configured with any ODACD.

[0053] 2. When the network receives the ODACD in a message NAS, then the network compares the received ODACD with the current ODACD of the UE. If the ODACD received from the UE is different from the current ODACD on the network, then the network transmits the ODACD in a NAS message.

[0054] 3. When a UE receives the ODACD in the NAS message, it then removes any previously configured ODACD, stores the received ODACD, and uses the ODACD in the UAC procedure.

[0055] Another instance of the second aspect of solution 2 is described below.

[0056] 1. A UE sends an initial NAS message containing the current ODACD configured on the UE.

[0057] In one example, if the UE has not been configured with ODACD, ODACD IE indicates that ODACD is not configured in UE. Here, ODACD IE can explicitly indicate that ODACD is not configured in UE. Alternatively, ODACD IE can implicitly indicate that ODACD is not configured in UE by emptying ODACD IE content.

[0058] In one example, when UE is not configured with 11^1^08^1^00893225.4^^:116108:212255.1^0...218 / / 85 14 / 28 ODACD, then the UE starts a timer T1 and executes step 1 when timer T1 expires.

[0059] 2 - 3. Upon receiving the first NAS message on the network, the network determines whether the received ODACD is the most recent ODACD configured for the UE or if the ODACD indicates that the UE is not configured with any ODACD. If the received ODACD is not the most recent or if the ODACD indicates that the UE is not configured with the ODACD, then the network will transmit a second NAS message containing the most recent ODACD for the UE. The network starts a timer T1.

[0060] In one scenario, the network includes an indicator requesting that the The EU will send a NAS message indicating receipt of the NAS message containing ODACD.

[0061] 4. Upon receiving the second NAS message, the UE transmits the third NAS message containing an information element indicating successful reception from the ODACD.

[0062] In one example, the UE includes the ODACD received from the network in the third NAS message.

[0063] In one example, the UE transmits the third NAS message when the second NAS message includes ODACD and the ACK information element requesting the UE to transmit a NAS message upon receipt of the ODACD.

[0064] 5. The network receiving the third NAS message for timer T1.

[0065] In one example, the first NAS message is the message Registration Request, Service Request Message, NAS TRANSPORT UL Message, or an existing NAS message or a new NAS message. The second NAS message is a Registration Acceptance message, NAS TRANSPORT DL message as defined in TS 24.501, Configuration Update Command, any other existing NAS message, or a new NAS message. To have 11^1^08^1^00893225,4^^:116108:212255,1^0^.:291 / 85 15 / 28 The first NAS message is UL NAS TRANSPORT, Full Configuration Update, an existing NAS message as defined in TS 24.501, or a new NAS message. Timer T1 is a new timer.

[0066] The T1 unit of the timer can be milliseconds, seconds, minutes, or hours.

[0067] In one example, the network includes an information element requesting that the UE send confirmation of ODACD reception in the second NAS message. Upon receiving the information element, the UE transmits the second NAS message containing an information element indicating that the UE received the ODACD. In another example, the UE includes in the third NAS message the ODACD Information Element as received in the second NAS message. In one example, the UE transmits the second NAS message or the following NAS message without containing any information element explicitly indicating reception of the ODACD. After the reception of the third NAS message or the following NAS message on the network, the network determines that the ODACD was successfully received by the UE.

[0068] In one example, the UE and the network will follow steps 3 to 11, as captured in solution 1 of this document.

[0069] In one example, the network or 5GC in solution 2 is the AMF.

[0070] In one example, the network or 5GC in solution 2 is the AMF.

[0071] In one example, the network in solution 2 is the MME. Another aspect

[0072] The ODACD mentioned above may include the following parameters:

[0073] (a) a precedence value that indicates the order in which the The EU should assess the category definition assigned by the operator for a match;

[0074] (b) an access category number defined by the ope 11^1^08^1^00893225,4^^:116108:212255,1^0^..2)1 / 85 16 / 28 rador, that is, access category number in the range 32-63 that uniquely identifies the access category in the PLMN in which the access categories are being sent to the UE; and

[0075] (c) one or more access category criteria types and associated access category criteria type values. The access category criteria type can be defined as one of the following:

[0076]

[0077]

[0078] 1) DNN Name; 2) 5QI; 3) OS Id + OS App Id of the application triggering the tension tactic of access; or

[0079] 4) S-NSSAI; and

[0080] (d) optionally, a standardized access category, which is used in combination with access identities to determine the cause of the establishment.

[0081] Here, each operator-defined access category can have a different precedence value. Multiple operator-defined access category definitions can have the same operator-defined access category number.

[0082] In one example, when receiving a signaling message For NAS devices with one or more operator-defined access category settings, the UE must store the operator-defined access category settings for the registered PLMN.

[0083] In one example, when receiving a signaling message For NAS devices with zero operator-defined access category settings, the UE must delete the stored operator-defined access category settings for the registered PLMN.

[0084] In one example, when the UE is switched off, the UE must retain the access category settings defined by the operator so that the access category settings defined by the operator Ptáçõmímss^^ 17 / 28 radar can be used after activation.

[0085] In one example, when the UE selects a new PLMN that is not equivalent to the previously selected PLMN, the UE must stop using the operator-defined access category settings configured for the previously selected PLMN and must retain the operator-defined access category settings configured for the previously selected PLMN. Another Aspect

[0086] Any NAS messages mentioned above can be transmitted between the UE and AMF via an NGRAN node (i.e., gNB).

[0087] Furthermore, some of the sequences, procedures or messages mentioned above may not always be necessary to identify one or more inventions.

[0088] User Equipment (or UE, mobile station, mobile device or wireless device) in this disclosure is an entity connected to a network via a wireless interface.

[0089] It should be noted that the UE in this specification is not limited to a dedicated communication device and can be applied to any device having a communication function as a UE described in this specification, as explained in the following paragraphs.

[0090] The terms User Equipment or UE (as the term is used by 3GPP), mobile station, mobile device and wireless device are generally intended to be synonymous with each other and include independent mobile stations such as terminals, cell phones, smartphones, tablets, cellular IoT devices, IoT devices and machines.

[0091] It will be appreciated that the terms EU and wireless device also cover devices that remain stationary for a 11:210200885122510189322.4:2111611821225.1))010..22 / / 807 18 / 28 long period of time.

[0092] A UE may, for example, be an item of equipment for production or manufacturing and / or an item of energy-related machinery (for example, equipment or machinery such as: boilers; motors; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and / or associated equipment; heavy electrical machinery; pumps, including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metalworking machines; manipulators; robots and / or their application systems; tools; molds or dies; rollers; transport equipment; lifting equipment; material handling equipment; textile machines; sewing machines; printing and / or related machines; paper converting machines; chemical machinery; mining and / or construction machinery and / or related equipment;Machinery and / or implements for agriculture, forestry and / or fishing; safety and / or environmental protection equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubrication equipment; valves; pipe fittings; and / or application systems for any equipment or machinery mentioned above, etc.).

[0093] A UE can, for example, be an item of transport equipment (e.g., transport equipment such as: rolling stock; motor vehicles; motorcycles; bicycles; trains; buses; trailers; truck bodies; rickshaws; ships and other vessels; aircraft; rockets; satellites; drones; balloons, etc.).

[0094] A UE can, for example, be an item of information and communication equipment (e.g., information and communication equipment such as: electronic computer and related equipment). Ptáçõmímss^^ 19 / 28 swimming; communication and related equipment; electronic components, etc.).

[0095] A UE may, for example, be a refrigeration machine, a product applied to a refrigeration machine, an item of commercial and / or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, an electronic and consumer electronic appliance (for example, a consumer electronic appliance such as: audio equipment; video equipment; a loudspeaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electric fan or related device; a cleaner, etc.).

[0096] An UE can, for example, be an electrical application system or equipment (for example, an electrical application system or equipment such as: an x-ray system; a particle accelerator; radioisotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment, etc.).

[0097] A UE may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester or a research or detection instrument (for example, a research or detection instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch, a laboratory instrument, an optical apparatus, medical equipment and / or system, a weapon, an item of cutlery, a hand tool or similar.

[0098] A UE can, for example, be a wireless equipped personal digital assistant or related equipment (such as a wireless board or module designed for connection to or insertion into another electronic device (e.g., a personal computer, a machine) 112ίκοο8851>5510189325,45ί1161:.185ι55.|);1,,,25.Κ,5 20 / 28 electrical measurement)).

[0099] A UE can be a device or part of a system that provides applications, services, and solutions described below, such as the Internet of Things (IoT), using a variety of wired or wireless communication technologies.

[00100] Internet of Things (or things) devices may be equipped with suitable electronics, software, sensors, network connectivity, and / or similar components that enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follows instructions from software stored in internal memory. IoT devices may operate without the need for human supervision or interaction. IoT devices may also remain stationary and / or inactive for extended periods of time. IoT devices may be implemented as part of a (usually) stationary appliance. IoT devices may also be incorporated into non-stationary appliances (e.g., vehicles) or attached to animals or people to be monitored / tracked.

[00101] It will be appreciated that IoT technology can be implemented in any communication device that can connect to a communication network to send / receive data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.

[00102] It will be appreciated that IoT devices are sometimes also called Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices or Narrowband Internet of Things User Equipment (NB-IoT UE). It will be appreciated that a UE can support one or more applications 11:91^00885122510189325.45416118:21225.1)100.. / 5 / / 8 / 5 21 / 28 vos IoT or MTC. Some examples of MTC applications are listed in Table 1 (source: 3GPP TS 22.368 V14.0.1 (2017-08), Appendix B, the contents of which are incorporated here by reference). This list is not exhaustive and is intended to be indicative of some examples of machine-to-machine communication applications. Table 1: Some examples of communication applications by machine type. Service Area MTC Applications Security Surveillance Systems Alternative to Landline Phones Physical Access Control (e.g., buildings) Car / Driver Security Tracking & Reconstruction Fleet Management Order Management Pay as you drive Asset Tracking Navigation Traffic Information Road Tolls Road Traffic Optimization / Direction Payment Point of Sale Vending Machines Gaming Machines Health Vital Signs Monitoring Support for the Elderly or Disabled Telemedicine Points with Web Access Remote Diagnosis Remote Maintenance / Control Sensors Lighting Pumps Valves Elevator Control Vending Machine Control Ptáçõmímss^^ 22 / 28 Vehicle Diagnostics, Energy Metering, Gas Metering, Water Metering, Heating Meter, Network Control, Industrial Metering, Consumer Devices, Digital Photo Frame, Digital Camera, Electronic Book

[00103] Applications, services, and solutions may include an MVNO (Mobile Virtual Network Operator) service, an emergency radio communication system, a PBX (Private Branch eXchange) system, a PHS / Wireless Telecommunications System, a POS (Point of Sale) system, an advertising call system, an MBMS (Multimedia Broadcast and Broadcast Service), a V2X (Vehicle-to-Everything) system, a train radio system, a location-related service, a Disaster / Emergency Wireless Communication Service, a community service, a video streaming service, a femto cell application service, a VoLTE (Voice over LTE) service, a billing service, an on-demand radio service, a roaming service, an activity monitoring service, a telecommunications / NW communication carrier selection service, a functional restriction service, a PoC (Proof of Concept) service, a personal information management service,ad-hoc / DTN (Delay Tolerant Network) network service, etc. Furthermore, the UE categories described above are merely examples of applications of the technical ideas and exemplary realizations described in this document. Needless to say, these technical ideas and realizations are not limited to the UE described above, and various modifications may be made to it. 11^1^008851225101893225,451116118:21225,1^0.0..23 / 85 23 / 28

[00104] Figure 3 is a block diagram illustrating the main components of the UE 300. As shown, the UE includes a transceiver circuit 304 that is operable to transmit signals to and receive signals from the connected node(s) via one or more antennas 305. Although not necessarily shown in Figure 3, the UE will certainly have all the usual functionalities of a conventional mobile device (such as a user interface) and this can be provided by any one or any combination of hardware, software and firmware, as appropriate. The software may be pre-installed in memory and / or may be downloaded via the telecommunications network or from a removable data storage device (RMD), for example.

[00105] A controller 301 controls the operation of the UE according to the software stored in a memory 302. For example, the controller may be implemented by the Central Processing Unit (CPU). The software includes, among other things, an operating system and a communication control module 306 having at least one transceiver control module 307. The communication control module 306 (using its transceiver control submodule) is responsible for handling (generating / sending / receiving) signaling data packets and uplink / downlink between the UE and other nodes, such as the base station / (R)AN node, an MME, the AMF (and other core network nodes).This signaling may include, for example, appropriately formatted signaling messages related to establishing and maintaining a connection (e.g., RRC messages), NAS messages, such as messages related to periodic location updates (e.g., tracking area update, paging area updates, location area update), etc.

[00106] Figure 4 is a block diagram that illustrates the principal 11510.00885122510189325.451.116118:21225.1)10...6:8 / / 85 24 / 28 parent components of an exemplary NA (R) node 400, for example, a base station ('eNB' in LTE, 'gNB' in 5G). As shown, the AN (R) node 400 includes a transceiver circuit 407 that is operable to transmit signals and receive signals from the connected UE(s) via one or more antennas 408 and to transmit signals and receive signals from other network nodes (directly or indirectly) via a network interface 406. A controller 401 controls the operation of the AN (R) node according to software stored in a memory 402. For example, the controller may be implemented by the Central Processing Unit (CPU). The software may be pre-installed in memory and / or may be downloaded from the telecommunications network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system and a communication control module having at least one 404 transceiver control module.

[00107] The 403 communication control module (using its transceiver control submodule) is responsible for handling (generating / sending / receiving) signaling between the AN node (R) and other nodes, such as the UE, MME, AMF (e.g., directly or indirectly). Signaling may include, for example, appropriately formatted signaling messages related to a radio connection and location procedures (for a specific UE), and in particular, related to the establishment and maintenance of connections (e.g., RRC connection establishment and other RRC messages), messages related to periodic location updates (e.g., tracking area update, paging area updates, location area update), S1 AP messages and NG AP messages (i.e., messages by the N2 reference point), etc. This signaling may also include, for example, broadcast information (e.g., Key Information and Information). 11:91^00885122510189325,45416118:21225,1)100.01.11 / 8 / 5 25 / 28 System instructions) in a shipping case.

[00108] The controller is also configured (by software or hardware) to handle related tasks, such as, when implemented, UE mobility estimation and / or mobile trajectory estimation.

[00109] Figure 5 is a block diagram illustrating the main components of the AMF 500. The AMF 500 is included in the 5GC. As shown, the AMF 500 includes a transceiver circuit 507 that is operable to transmit signals and receive signals from other nodes (including the UE) via a network interface 506. A controller 501 controls the operation of the AMF 500 according to software stored in memory. For example, the controller may be implemented by the Central Processing Unit (CPU). The software may be pre-installed in memory and / or may be downloaded via the telecommunications network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system and a communication control module 503 having at least one transceiver control module 504.

[00110] The communication control module (using its transceiver control submodule) is responsible for handling (generating / sending / receiving) signaling between the AMF and other nodes, such as UE, base station / node (R)AN (e.g., gNB or eNB) (directly or indirectly). This signaling may include, for example, appropriately formatted signaling messages related to the procedures described in this document, e.g., NG AP message (i.e., a message via reference point N2) to transmit a NAS message to and from the UE, etc.

[00111] As will be appreciated by someone skilled in the art, the present disclosure can be incorporated as a method and a system. Therefore, the present disclosure can take the form of 11:210200885122510189322,45111611821225,1,)010.4 / )1--807 26 / 28 a fully hardware implementation, a software implementation, or an implementation that combines aspects of software and hardware.

[00112] It will be understood that each block of the block diagrams can be implemented by computer program instructions. These computer program instructions can be supplied to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing device to produce a machine, such that the instructions, executed by the computer processor or other programmable data processing device, create means to implement the functions / acts specified in the flowchart and / or block or blocks of the block diagram. A general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, for example, a plurality of microprocessors, one or more microprocessors, or any other such configuration.

[00113] The methods or algorithms described in connection with the examples disclosed herein may be incorporated directly into the hardware, in a software module executed by a processor, or in a combination of both. A software module may reside in RAM, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage known in the art. A storage medium may be coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be an integral part of the processor. The processor Ptáçõmímss^^ 27 / 28 The sensor and the storage medium can reside in an ASIC.

[00114] The preceding description of the examples disclosed is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles set forth herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown in this document, but should be given the broader scope consistent with the principles and new features disclosed in this document.

[00115] This application is based on and claims the benefit of priority of Indian patent applications No. 201811035318, filed on September 19, 2018, the disclosure of which is incorporated herein in its entirety by reference. List of Reference Signs 300 UE 301 controller 302 memory 303 user interface 304 transceiver circuit 305 antenna 306 communication control module 307 transceiver control module 308 operating system 400 node (R)AN 401 controller 402 memory 403 communication control module 404 transceiver control module 405 operating system Ptáçõmímss^^ 28 / 28 406 407 408 500 501 502 503 504 505 506 507 network interface transceiver circuit antenna AMF controller memory communication control module transceiver control module operating system network interface transceiver circuit

Claims

1. Method for main network node, characterized in that it comprises: sending, to a User Equipment, UE, a REGISTRATION ACCEPTANCE message including at least one operator-defined access category definition, ODACD, receiving, from the UE, a COMPLETE REGISTRATION message indicating acknowledgment of at least one operator-defined access category definition.

2. A method according to claim 1, characterized in that at least one operator-defined access category definition includes at least one of the following: Data Network Name, DNN; Operating System ID, OS ID; OS App ID; Simple Network Slice Selection Assistance Information, S-NSSAI.

3. Method according to claim 2, characterized in that it comprises: starting a timer in a case where at least one operator-defined access category definition is included in the RECORD ACCEPTANCE message.

4. Method according to claim 2, characterized in that it comprises: stopping the timer upon receipt of the RECORD ACCEPTANCE message.

5. Method according to claim 1, characterized in that it further comprises: resending the REGISTRATION ACCEPTANCE message if the main network node does not receive the REGISTRATION COMPLETE message before the timer expires. 1491^00885122510189325,45416118:21225,1)100.45 / 8 / 5 2 / 5 6. Main network node, characterized in that it comprises: means for sending, to a User Equipment (UE), a REGISTRATION ACCEPTANCE message including at least one operator-defined access category definition, means for receiving, from the UE, a COMPLETE REGISTRATION message indicating acknowledgment of at least one operator-defined access category definition.

7. Main network node, according to claim 6, characterized in that at least one operator-defined access category definition includes at least one of DNN, OS ID + OS App ID, and S-NSSAI.

8. Main network node, according to claim 7, characterized in that it comprises: means for initiating a timer in a case where at least one operator-defined access category definition is included in the REGISTRATION ACCEPTANCE message.

9. Main network node, according to claim 8, characterized in that it comprises: means for stopping the timer upon receipt of the REGISTRATION ACCEPTANCE message.

10. Main network node, according to claim 6, characterized in that it comprises: means for resending the REGISTRATION ACCEPTANCE message if the main network node does not receive the REGISTRATION COMPLETE message before the timer expires.

11. Method for User Equipment, UE, characterized in that it comprises: receiving, from a main network node, a REGISTRATION ACCEPTANCE message including at least one operator-defined access category definition; storing at least one operator-defined access category definition; and sending, to the main network node, a COMPLETE REGISTRATION message indicating acknowledgment of at least one operator-defined access category definition.

12. Method, according to claim 11, characterized in that at least one operator-defined access category definition includes at least one of DNN, OS id + OS App id, and S-NSSAI.

13. Method according to claim 11, characterized in that it comprises: excluding a second operator-defined access category definition stored before the storage of at least one operator-defined access category definition in a case where the UE has stored the second operator-defined access category definition.

14. Method according to claim 11, characterized in that it comprises: receiving, from the main network, a second REGISTRATION ACCEPTANCE message including at least one operator-defined access category definition in a case where the main network node has not received the REGISTRATION COMPLETE message before a timer expires, wherein the timer starts counting when the main network node sends the REGISTRATION ACCEPTANCE message.

15. Method, according to claim 11, characterized in that it further comprises: sending a first REGISTRATION REQUEST message to the main network node; starting a timer based on the sending of the first REGISTRATION REQUEST message; and sending a second REGISTRATION REQUEST message based on the expiration of the timer.

16. Method, according to claim 15, characterized in that the REGISTRATION REQUEST message indicates that the UE is not configured with an operator-defined access category definition.

17. User Equipment, UE, characterized in that it comprises: means for receiving, from a main network node, a REGISTRATION ACCEPTANCE message including at least one operator-defined access category definition; means for storing the at least one operator-defined access category definition received; and means for sending, to the main network node, a COMPLETE REGISTRATION message indicating acknowledgment of the at least one operator-defined access category definition.

18. EU, according to claim 17, characterized in that at least one operator-defined access category definition includes at least one of DNN, OS ID + OS App ID, and S-NSSAI.

19. UE, according to claim 17, characterized in that it comprises: excluding a second operator-defined access category definition stored before the storage of at least one operator-defined access category definition in a case where the UE has stored the second operator-defined access category definition.

20. The EU, according to claim 17, characterized by the fact that it comprises: receiving, from the main network, a second ACCEPT REGISTRATION message including at least one operator-defined access category definition in a case where the main network node has not received the COMPLETE REGISTRATION message before a timer expires, wherein the timer starts counting when the main network node sends the ACCEPT REGISTRATION message.

21. EU, according to claim 17, characterized in that it comprises: sending a first REGISTRATION REQUEST message to the main network node; starting a timer based on the sending of the first REGISTRATION REQUEST message; and sending a second REGISTRATION REQUEST message based on the expiration of the timer.

22. UE, according to claim 21, characterized in that the REGISTRATION REQUEST message indicates that the UE is not configured with an operator-defined access category definition.

Images