阅读说明：本技术 用于更新与统一接入控制相关的参数的过程 (Procedure for updating parameters related to unified access control ) 是由 昆丹·提瓦利 田村利之 于 2019-10-04 设计创作，主要内容包括：UE在非3GPP接入上处于连接模式并且在3GPP接入上处于空闲模式。UE在非3GPP接入上从核心网络节点接收通知消息。在进行服务请求过程的情况下,在接收到通知消息时,UE将MT-acc＝0确定为与服务请求过程相关联的接入类别。UE检查是禁止还是允许针对接入类别的接入尝试。在允许接入类别的情况下,UE向基站发送RRC连接设置请求,并在建立RRC连接之后向核心网络节点发送服务请求消息。(The UE is in connected mode on a non-3 GPP access and in idle mode on a 3GPP access. The UE receives a notification message from a core network node over a non-3 GPP access. In case of performing the service request procedure, upon receiving the notification message, the UE determines MT _ acc of 0 as an access category associated with the service request procedure. The UE checks whether to prohibit or allow access attempts for the access category. In case of allowing the access category, the UE transmits an RRC connection setup request to the base station and transmits a service request message to the core network node after establishing the RRC connection.)

1.A method for a User Equipment (UE), comprising:

receiving a notification message from a core network node over a non-3 GPP access in a case where the UE is in a connected mode over the non-3 GPP access and is in an idle mode over the 3GPP access;

in case of performing a service request procedure, upon receiving the notification message, determining MT _ acc of 0 as an access category associated with the service request procedure;

checking whether to prohibit or allow an access attempt for the access category; and

in case the access category is allowed, a radio resource control, RRC, connection setup request is sent to the base station and a service request message is sent to the core network node after establishing the RRC connection.

2. The method of claim 1, further comprising:

sending a notification response message to the core network node over a non-3 GPP access with the access category barred, and not initiating the service request procedure to re-establish a user plane for one or more protocol data unit sessions, PDU sessions, associated with the 3GPP access.

3. The method of claim 1, wherein,

the RRC connection setup request includes an establishment cause associated with the access category.

4. A User Equipment (UE), comprising:

a transceiver circuit and a controller;

wherein the controller is configured to:

receive, via the transceiver circuitry, a notification message from a core network node over a non-3 GPP access if the UE is in a connected mode over the non-3 GPP access and is in an idle mode over a 3GPP access;

in case of performing a service request procedure, upon receiving the notification message, determining MT _ acc of 0 as an access category associated with the service request procedure;

checking whether to prohibit or allow an access attempt for the access category;

in case the access category is allowed, a radio resource control, RRC, connection setup request is sent to a base station via the transceiver circuitry, and a service request message is sent to the core network node via the transceiver circuitry after establishing an RRC connection.

5.A communication system, comprising:

user Equipment (UE); and

a Base Station (BS) is provided,

wherein the UE includes:

a transceiver circuit and a controller;

wherein the controller is configured to:

receive, via the transceiver circuitry, a notification message from a core network node over a non-3 GPP access if the UE is in a connected mode over the non-3 GPP access and is in an idle mode over a 3GPP access;

in case of performing a service request procedure, upon receiving the notification message, determining MT _ acc of 0 as an access category associated with the service request procedure;

checking whether to prohibit or allow an access attempt for the access category; and

in case the access category is allowed, transmitting a radio resource control, RRC, connection setup request, to the base station via the transceiver circuitry, and transmitting a service request message to the core network node via the transceiver circuitry after establishing an RRC connection.

6.A method for a User Equipment (UE), comprising:

receiving a notification message from a 5 th generation core network, 5GC, over a non-3 GPP access, in a case where the UE is in a connected state over the non-3 GPP access and is in an idle state over the 3GPP access;

in case of performing a service request procedure, associating one of an access category MT _ acc of 0, an access category MO _ data of 7 and a new access category with the service request procedure;

checking whether to prohibit or allow an access attempt for the access category;

transmitting a notification response message to the 5GC without initiating the service request procedure to re-establish a user plane for one or more Protocol Data Unit (PDU) sessions associated with the 3GPP access, if the access category is barred; and

in case the access category is allowed, a radio resource control setup request, i.e. an RRC setup request, is sent to the base station in the 5 th generation system, i.e. the 5GS, and a service request message is sent after establishing an RRC connection.

Technical Field

The invention relates to a UE, a method used by the UE and a wireless communication system.

Background

The 5GS includes 5GC and NG-RAN. In 5GS, Unified Access Control (UAC) is defined as access control to signaling from a UE under various conditions (e.g., congestion, network maintenance, etc.). The UAC may be implemented by the NG-RAN to broadcast the access control information on a broadcast channel, i.e., a Broadcast Control Channel (BCCH). Based on the access control information on the broadcast channel that the UE listens to, the UE may decide whether the UE may be allowed to access the 5 GS. For example, if access restrictions to mobile originated data are indicated in the broadcast channel, the UE cannot initiate a service request to the 5GS despite the UE having pending UL packets to send.

The UE is configured with an access identity and an event classified into an access category. The access categories are further classified into standard access categories and operator defined access categories. In the following, the operator defined access category is also denoted "PLMN operator defined access category". The PLMN operator defines the access category to be sent to the UE in a NAS message. The current operator defines access categories as 1) DNN, 2)5G QoS ID, 3) OS ID + APP ID and 4) S-NSSAI. The operator defined access categories are on a per PLMN basis.

In the case where the UE needs to access the network, the NAS layer of the UE determines the access type and access category of the event. The NAS layer of the UE provides the parameters to the access layer (e.g., RRC layer, SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer) of the UE for use in the access control procedure. An Access Stratum (AS) layer determines whether to allow access to the network based on the access category and the access type. If access to the network is allowed, the UE establishes an RRC connection and then sends an initial NAS message. If access to the network is not allowed for the event, the AS layer of the UE notifies the NAS layer of the UE that access is not allowed for the event. In this case, the NAS layer neither establishes NAS signaling connections nor sends NAS messages until access to the network is allowed.

Further, the UE may register to the same AMF via the 3GPP access and the non-3 GPP access in case the PLMN selected for the 3GPP access and the non-3 GPP access is the same. In this case, the AMF assigns a single temporary identity 5G-GUTI for both 3GPP and non-3 GPP accesses. The UE maintains a 5GMM state, 5GMM parameters, 5GMM status, connection management state separately and independently for both 3GPP and non-3 GPP accesses.

In case the UE is in CM-CONNECTED (CM CONNECTED) mode on 3GPP access and CM-IDLE (CM IDLE) mode on non-3 GPP access, and the 5GC has Mobile Terminated (MT) data for PDU sessions associated with non-3 GPP access, the AMF sends a NOTIFICATION message on 3GPP access. In case the UE receives the NOTIFICATION message over the 3GPP access, the UE sends a service request message containing a PDU session identity for which the user plane is allowed to be established over the 3GPP access. The network establishes a user plane for the PDU session indicated in the service request message and user data is pending for the PDU session.

Similarly, in case the UE is in CM-CONNECTED mode over non-3 GPP access and CM-IDLE mode over 3GPP access, and the 5GC has MT data for PDU sessions associated with 3GPP access, the AMF pages the UE via the 3GPP access or sends a NOTIFICATION message over the non-3 GPP access. In the case where the UE receives the NOTIFICATION message over the non-3 GPP access, the UE sends a service request message to establish the user plane over the 3GPP access. The 5GC establishes a user plane for a PDU session associated with the 3GPP access for which the 5GC has MT user data to process.

Reference list

Non-patent document

Non-patent document 1:3GPP TR 21.905: "Vocabulariy for 3GPP specificities". V15.0.0 (2018-03).

Non-patent document 23 GPP TS 23.501: "System Architecture for the 5G System; stage 2'. V15.2.0 (2018-06).

Non-patent document 3:3GPP TS 23.502: "Procedures for the 5G System; stage 2"V15.2.0 (2018-06).

Non-patent document 4:3GPP TS 24.501: "Non-Access-stratum (NAS) protocol Stage 3" V15.0.0 (2018-06).

Non-patent document 5:3GPP TS 38.413: "NG Application Protocol (NGAP)" V15.0.0 (2018-06).

Non-patent document 63 GPP TS 38.331": Radio Resource Control (RRC) protocol specification" V15.3.0 (2018-09).

Disclosure of Invention

Problems to be solved by the invention

Problem statement 1:

in case the 5GC decides to start access control to alleviate congestion related to DNN or OS ID + APP ID or 5G QoS, there is no procedure defined between NG-RAN and 5GC to invoke UAC for DNN, APP ID + OS ID or 5G QoS. As a result, the 5GS may be out of service due to a large amount of traffic from the UE because the NG-RAN cannot have any access control over DNN, APP ID + OS ID, or 5G QoS.

Problem statement 2:

in the case where the 5GS experiences congestion due to the signaling related to the combination of S-NSSAI and DNN, the 5GS cannot protect itself from the signaling related to the combination of S-NSSAI and DNN, and cannot alleviate the congestion related to the combination of S-NSSAI and DNN due to the lack of specifications in 3 GPP. As a result, 3GPP operators may not have UAC mechanisms for signal suppression on specific S-NSSAI and DNN combinations.

Problem statement 3:

in the operator defined access category definition, a maximum of 32 access category numbers may be provided for the operator defined access category numbers. In addition, 32 access class spaces must be shared with the UAC based on S-NSSAI, DNN, APP ID and OSS ID combinations and 5G QoS. However, S-NSSAI is 4 bytes, i.e., it has a much higher value than 32. Therefore, it is not feasible to assign a unique operator defined access class number for each S-NSSAI value. As a result, the 3GPP operator may not use UAC for the operator to define access classes for all required modes of S-NSSAI, DNN, APP ID and OSS ID combinations and 5G QoS.

Problem statement 4:

the operator defined access category definition is sent to the UE using NAS messages and stored if the UE is switched off and reused if the UE is switched on again. However, it is not clear whether the UE will reuse the operator defined access category definition in case of USIM change. For example, if the USIM changes during UE shutdown, the operator defined access class definitions may be stored as mentioned above. However, it is not clear whether the UE can reuse the operator defined access category definition if the USIM changes from the previous USIM in case the UE is switched on. Sui or SUPI or both sui and SUPI may change due to USIM changes. Sui or SUPI or both may not change due to USIM changes.

Further, a USIM change may occur during the UE turn-on. For example, the USIM is changed by removing and inserting the USIM during the time the UE is turned on by the SIM toolkit function. Thus, such undefined UE behavior will result in different implementations in different UEs, and thus in this scenario the operator cannot control the UE behavior that will result in more congestion in the network.

Problem statement 5:

the 3GPP standard defines protection of temporary identities from intruders, and thus protects users from being identified and located by intruders. In the same way, it may be desirable to define the protection of ODACD in the standard. More specifically, ODACD is sent in a NAS message. ODACD contains information related to unified access control, and these parameters may be changed over the air by an intruder. If the UE receives the modified ODACD parameter and uses the received ODACD for access control, the UE applies the wrong ODACD and thus access control may not work. The operator cannot use the UAC to control the UE's access to the network, and therefore cannot protect its network in a congested scenario or other situations where the operator invokes the UAC.

Problem statement 6:

in case the UE receives the NOTIFICATION message as described above on a non-3 GPP access or on a 3GPP access, the UE initiates a service request procedure. However, it is unclear what the access category of the service request procedure is. This will result in different UE implementations between UE vendors for this scenario. As a result, for this scenario, the network operator may not control the UE's access attempt behavior to the 5 GS.

Further, in case the UE receives the NOTIFICATION message, the UE initiates a service request procedure. If access to the access category associated with the service request procedure is barred, the UE behavior is unclear. In the absence of clear UE behavior, the network cannot use the UAC to control the UE's access attempt to the 5 GS.

In view of the above problems, the present invention aims to provide a solution to solve at least one of the various problems.

Means for solving the problems

In an aspect of the present invention, there is provided a method for a User Equipment (UE), the method comprising: receiving a notification message from a core network node over a non-3 GPP access in a case where the UE is in a connected mode over the non-3 GPP access and is in an idle mode over the 3GPP access; in case of performing a service request procedure, upon receiving the notification message, determining MT _ acc of 0 as an access category associated with the service request procedure; checking whether to prohibit or allow an access attempt for the access category; and in case the access category is allowed, transmitting a radio resource control, RRC, connection setup request to the base station and transmitting a service request message to the core network node after establishing the RRC connection.

In another aspect of the present invention, a User Equipment (UE) is provided, the UE comprising: a transceiver circuit and a controller; wherein the controller is configured to: receive, via the transceiver circuitry, a notification message from a core network node over a non-3 GPP access if the UE is in a connected mode over the non-3 GPP access and is in an idle mode over a 3GPP access; in case of performing a service request procedure, upon receiving the notification message, determining MT _ acc of 0 as an access category associated with the service request procedure; checking whether to prohibit or allow an access attempt for the access category; in case the access category is allowed, a radio resource control, RRC, connection setup request is sent to a base station via the transceiver circuitry, and a service request message is sent to the core network node via the transceiver circuitry after establishing an RRC connection.

In other aspects of the present invention, there is provided a communication system including: user Equipment (UE); and a base station, wherein the UE includes: a transceiver circuit and a controller; wherein the controller is configured to: receive, via the transceiver circuitry, a notification message from a core network node over a non-3 GPP access if the UE is in a connected mode over the non-3 GPP access and is in an idle mode over a 3GPP access; in case of performing a service request procedure, upon receiving the notification message, determining MT _ acc of 0 as an access category associated with the service request procedure; checking whether to prohibit or allow an access attempt for the access category; and in the event that the access category is allowed, transmitting a radio resource control, RRC, connection setup request to the base station via the transceiver circuitry, and transmitting a service request message to the core network node via the transceiver circuitry after establishing an RRC connection.

In yet another aspect of the present invention, a method for a User Equipment (UE) is provided, the method comprising: receiving a notification message from a 5 th generation core network, 5GC, over a non-3 GPP access, in a case where the UE is in a connected state over the non-3 GPP access and is in an idle state over the 3GPP access; in case of performing a service request procedure, associating one of an access category MT _ acc of 0, an access category MO _ data of 7 and a new access category with the service request procedure; checking whether to prohibit or allow an access attempt for the access category; transmitting a notification response message to the 5GC without initiating the service request procedure to re-establish a user plane for one or more Protocol Data Unit (PDU) sessions associated with the 3GPP access, if the access category is barred; and transmitting a Radio Resource Control (RRC) setup request to a base station in a 5 th generation system (5 GS) and transmitting a service request message after establishing an RRC connection, in a case where the access category is allowed.

Drawings

Fig. 1 is a flow chart illustrating a signalling flow of a method according to the first aspect of the invention.

Fig. 2 is a flow chart illustrating a signalling flow of a method according to the second aspect of the invention.

Fig. 3 is a flow chart illustrating a signalling flow of a method according to the third aspect of the invention.

Fig. 4 is a flow chart illustrating a signalling flow of a method according to the fourth aspect of the invention.

Fig. 5 is a flow chart illustrating a signalling flow of a method according to the fifth aspect of the invention.

Fig. 6 is a flow chart illustrating a signalling flow of a method according to the fifth aspect of the invention.

Fig. 7 is a block diagram showing a configuration example of the UE.

Fig. 8 is a block diagram showing a configuration example of the (R) AN.

Fig. 9 is a block diagram showing a configuration example of the AMF.

Fig. 10 is a diagram showing information elements related to category values of category types.

Detailed Description

Abbreviations

For the present invention, 3GPP TR 21.905 (non-patent document 1) and abbreviations given below apply. The abbreviations defined in the present invention have precedence over the definitions of the same abbreviations (if present) in 3GPP TR 21.905 (non-patent document 1).

5GC 5G core network

5GS 5G system

5G-AN 5G access network

5G-GUTI 5G globally unique temporary identifier

5G S-TMSI 5G S-temporary Mobile subscription identifier

5QI 5G QoS identifier

AF application function

AMF access and mobility management functions

AN access node

AS access layer

AUSF authentication server function

CM connection management

CP control plane

CSFB Circuit Switched (CS) fallback

DL downlink

DN data network

DNAI DN access identifier

DNN data network name

EDT early data delivery

EPS evolution grouping system

EPC evolved packet core

FQDN full qualified domain name

GFBR guaranteed stream bit rate

GMLC gateway mobile location center

GPSI generic common subscription identifier

GUAMI globally unique AMF identifier

HR home routing (roaming)

I-RNTI I-radio network temporary identifier

LADN local data network

LBO local breakout (roaming)

LMF location management function

LRF location retrieval functionality

MAC medium access control

MFBR maximum stream bit rate

MICRO Mobile-originated-only connectivity

MME mobility management entity

N3IWF non-3 GPP interworking function

NAI network access identifier

NAS non-access stratum

NEF network open function

NF network function

NG-RAN next generation radio access network

NR New air interface

NRF network repository function

NSI ID network slice instance identifier

NSSAI network slice selection assistance information

NSSF network slice selection function

NSSP network slice selection strategy

NWDAF network data analysis function

PCF policy control function

PEI permanent device identifier

PER packet error rate

PFD packet flow description

PLMN public land mobile network

PPD paging policy differentiation

PPI paging policy indication

PSA PDU session anchor

QFI QoS flow identifier

QoE quality of experience

(R) AN (radio) access network

RLC radio link control

RM registration management

RQA reflection QoS attributes

RQI reflection QoS indication

RRC radio resource control

New air interface of SA NR independent networking

SBA service-based architecture

SBI service-based interface

SD slice differentiator

SDAP service data adaptation protocol

SEAF Security Anchor functionality

SEPP secure edge protection proxy

SMF session management function

S-NSSAI Single network slice selection assistance information

SSC session and service continuity

SST slice/service type

SUCI subscription hidden identifier

SUPI subscription permanent identifier

UAC unified access control

UDSF unstructured data storage functionality

UL uplink

UL CL uplink classifier

UPF user plane functionality

UDR unified data repository

URSP UE routing strategy

SMS short message service

SMSF SMS functionality

UAC unified access control

ODACD operator defined access category definition

OS operating system

MO mobile initiation

MT mobility termination

USIM universal subscriber identity module

UICC universal integrated circuit card

Definition of

For the present invention, the terms and definitions given in 3GPP TR 21.905 (non-patent document 1) and non-patent documents 2 to 6 apply. The terms defined in the present invention take precedence over the definition of the same terms (if any) in 3GPP TR 21.905 (non-patent document 1).

First aspect (solution 1 to solve problem statements 1, 2, and 3):

in a first aspect, a NAS message is sent acknowledging receipt of an odadc in a NAS message.

An outline of solution 1 is given below.

1.5GC configures operator defined access category definitions for UEs.

2. In case the 5GC decides to invoke or revoke access barring for a category value of a category type, the 5GC transmits an N2 message containing at least one of the category value, the category type, and an operator defined access category number associated with the category value of the category type, thereby requesting the NG-RAN to invoke or revoke access barring for an access value of an access type.

3. Upon receipt, the N2 message invokes or revokes access barring for category values of category types according to the request received in the N2 message. The NG-RAN broadcasts a system information block containing access barring information associated with the class value of the class type. The access barring information indicates that access is barred for a class value of a class type if the NG-RAN invokes barring of the class value of the class type. The access barring information indicates that access is not barred for a class value of the class type if the NG-RAN revokes barring of the class value of the class type.

Fig. 1 shows a signalling flow of a method according to the first aspect of the invention. The detailed steps of solution 1 are described below.

Figure 1 shows two separate streams. Steps 1 to 4 are performed in case 5GC decides to execute UAC, and steps 5 to 9 are performed in case 5GC decides to stop UAC. These two streams are related to the UAC, but can be considered as independent streams.

The UE successfully registers to the PLMN and the UE is configured with at least one ODACD. Odadc is an operator defined access category defined in 3GPP TS 24.501 (non-patent document 4).

AMF decides to invoke access control for standard values of standard type.

The AMF sends a first N2 message containing at least one of a standard value, a standard type and an operator defined access class number associated with the standard value of the standard type, requesting the NG-RAN to start access control for the standard value of the standard type.

In one example, the first N2 message is an NGAP OVERLOAD START, an existing NGAP message as defined in 3GPP TS 38.413 (non-patent document 5), or a new NGAP message.

3. Upon receiving the first N2 message, the NG-RAN invokes the UAC procedure for the standard value of the standard type by broadcasting system information (e.g., system information block 1, SIB 1) that contains information elements related to the standard value of the standard type. The information element indicates that access to a standard value of a standard type is forbidden.

In one example, the NG-RAN broadcasts an operator defined access category number associated with a standard value of a standard type.

4. In case the UE wants to access the 5GS for events related to standard values of standard type (e.g. via NG-RAN), the UE first checks the broadcast system information and learns if access to events related to standard values of standard type is barred. In case the UE learns that the access is forbidden, the UE does not access the 5GS (i.e. NG-RAN) for events corresponding to the category value of the category type. That is, the UE does not initiate a procedure to establish the RRC connection for an event corresponding to a category value of a category type.

In one example, the UE maps a standard value of the standard type of event to an operator defined access category number according to the operator defined access category definition sent to the UE in step 0, reads broadcast system information (e.g. SIB 1) containing access barring information related to the operator defined access category number, and learns whether access to the operator defined access category number is barred. The UE does not access the 5GS (i.e. NG-RAN) if access to the operator defined access category number is barred.

AMF decides to revoke access control to the standard values of the standard type.

The AMF sends a second N2 message containing at least one of the standard value, the standard type and an operator defined access class number associated with the standard value of the standard type, thereby requesting the NG-RAN to stop access control for the standard value of the standard type.

In one example, the second N2 message is an NGAP OVERLOAD STOP, an existing NGAP message as defined in 3GPP TS 38.413 (non-patent document 5), or a new NGAP message.

7. Upon receiving the second N2 message, the NG-RAN invokes the UAC procedure related to the standard value of the standard type by broadcasting system information that contains an information element related to the standard value of the standard type indicating that the standard value of the standard type is not forbidden.

8. In case the UE wants to access the 5GS (i.e. NG-RAN) for events related to standard values of standard type, the UE first checks the broadcast system information and learns if access to events related to standard values of standard type is barred. In the event that the UE learns that the access is not barred, the UE initiates a procedure to access the network for an event corresponding to a category value of a category type. That is, the UE initiates an RRC connection setup procedure for the event. After the RRC connection is successfully established, a NAS message is sent to the 5GS (i.e., 5 GC).

In one example, the UE maps the standard value of the standard type of event to an operator defined access category number according to the operator defined access category definition sent to the UE in step 0, reads broadcast system information (e.g. SIB 1) containing access barring information related to the operator defined access category number, and learns whether access to the operator defined access category number is barred. The UE accesses the 5GS (i.e. NG-RAN) if access to the operator defined access class number is not barred.

9. Whenever the UE needs to access 5GS (i.e. NG-RAN), the UE will proceed with the same procedure as described in step 8.

In one example, the standard type is S-NSSAI + DNN, i.e., S-NSSAI and DNN together. For this standard type, an 8-bit value is assigned, e.g., 00000100.

In one example, the standard type is S-NSSAI, and the standard value is only the slice type, i.e., not SD.

In one example, the UE and network support an operator defined maximum number of access class numbers above 32. The UE includes the capability of the maximum number of operator defined access class numbers it supports, i.e. whether the UE supports up to 32 or more than 32 operator defined access class numbers in a NAS message (e.g. in a registration request message or a configuration update command message or other existing NAS message during the registration procedure or in a new NAS message to a 5GS (i.e. 5 GC)). Upon receiving the capability to support the maximum operator defined access class number, the 5GS learns whether the UE supports more than 32 operator defined access class numbers. In case the 5GS (i.e. 5GC) learns that the UE supports more than 32 operator defined access category numbers, it may send more than 32 operator defined access category numbers to the UE in the operator defined access category definition if the 5GS (i.e. 5GC) supports a maximum number of more than 32 operator defined access category numbers. The 5GS (i.e. NG-RAN) may also broadcast unified access barring information defining access category numbers for more than 32 operators. In one example, the operator defines the maximum number of access class numbers to be 2^ 32. In the case where the UE cannot understand the extended operator defined access category, the UE may initiate an access request. In this case, the AS-level congestion control mechanism or the NAS-level congestion control mechanism prohibits access attempts by the UE. In UAC, AS-level congestion control and NAS-level congestion control may work together to complement each other to achieve overall system-level access control.

In one example, the 5GC shown in fig. 1 may be an NWDAF.

A standard type, a standard value, and an operator-defined access class number are defined in 3GPP TS 24.501 (non-patent document 4).

In one example, the 5GS configures the UE with the following ODACD.

Access class number 32

Standard type 00000011: S-NSSAI

Standard type values: eMBB is 1.

In one example, in steps 3 and 7, the broadcast information corresponding to the category value of the category type comprises an operator defined access category number associated with the category value of the category type and an information element indicating whether access to the access category number is forbidden.

In one example, in steps 3 and 7, the broadcast information corresponding to the category value of the category type includes the category type and the category value and an information element indicating whether access to the category value of the category type is prohibited.

Fig. 10 illustrates information elements related to category values of category types. In one example, in steps 3 and 7, the information element shown in fig. 10 is broadcast in SIB 1 as defined in 3GPP TS 38.331 (non-patent document 5).

Second aspect (solution 2 to solve problem statement 4)

When the USIM in the UE changes, the UE classifies the access attempt to the 5GS based on the standardized access category and the previously received ODACD for the PLMN of the old USIM until the UE receives a new ODACD from the PLMN for the new USIM.

An overview of the solution is given below.

The UE registers to the PLMN for the first USIM and has received ODACD. The UE associates the access category of the NAS event to a standardized access category or an operator defined access category.

Another USIM is selected in the UE and the UE successfully performs a registration procedure with the PLMN.

Before the UE receives the second ODACD or standardized access category for the second USIM, the UE uses the received ODACD for the first USIM to associate the access category of the NAS event.

Fig. 2 shows a signalling flow of a method according to the second aspect of the invention. The detailed steps of solution 2 are described below.

The UE has the selected first USIM and registers to the AMF of the PLMN. The UE has received a first ODACD from the AMF.

UE defines access categories using standardized access categories and operator as received in ODACD to conduct access control to 5GS (i.e. NG-RAN or 5GC) in case the UE accesses 5GS for NAS events (e.g. requests from upper layers or NAS generated requests or network initiated NAS procedures).

2.A second USIM is selected in the UE. More specifically, the USIM in the UE is changed from a first USIM to a second USIM.

3. The UE with the second USIM successfully performs a registration procedure with the AMF (i.e., PLMN).

4. When a NAS event is triggered in the UE to access a 5GS (e.g., NG-RAN), the UE classifies access attempts to the access category only according to the standardized access category as mentioned in another aspect and the first odadc. The UE evaluates whether access to the access attempt is barred based on the access category of the access attempt and an access identity associated with the access attempt.

The UE receives a second ODACD from the AMF (i.e., PLMN) in a second NAS message.

6. When an event is triggered in the UE to access a 5GS (e.g., NG-RAN), the UE classifies the access attempt to the access category according to the standardized access category and the second odadc. The UE evaluates whether access to the access attempt is barred or allowed based on the access category and an access identity associated with the access attempt.

In one example, when the UE selects a second USIM of the same UICC, the second USIM is selected.

In one example, a second USIM is selected when a user removes a first UICC containing a first USIM and inserts a second UICC containing a second USIM.

In one example, the second USIM is selected when the user switches the USIM from one to another in case the UE supports DSDS (dual SIM dual standby).

In one example, the change of the second USIM may occur during the UE turning on or off.

In one example, a NAS event is a request from an upper layer (operating system (OS), an application above the operating system, or a protocol stack on top of the 5GMM layer) (e.g., Short Message Service (SMS), IP Multimedia Subsystem (IMS), Supplementary Service (SS), location services (LCS), etc.).

In one example, the event is an event generated by the 5GMM itself (e.g., a periodic registration procedure) due to receipt of a NAS or AS message from the 5 GS.

Third aspect (solution 3 to solve problem statement 4)

When another USIM is selected in the UE, the UE does not use the old ODACD of the previous USIM.

An overview of the solution is given below.

The UE registers to the AMF of the PLMN for the first USIM and has received the first ODACD from the AMF. The UE associates the access category of the NAS event to a standardized access category or an operator defined access category according to the first ODACD.

Another USIM is selected in the UE and the UE with the other USIM successfully performs a registration procedure with the PLMN.

The UE associates the access category of the NAS event using only the standardized access category. The UE does not use the first ODACD received for the first USIM. When the UE receives a second ODACD for a second USIM, the UE associates the NAS event to a standardized access category or an operator defined access category according to the second ODACD.

Fig. 3 shows a signalling flow of a method according to the third aspect of the invention. The detailed steps of solution 3 are described below.

The UE selects the first USIM and registers to the AMF of the PLMN. The UE has received a first ODACD from the AMF.

1. In case the UE accesses the 5GS (i.e. NG-RAN or 5GC) for NAS event, the UE uses the standardized access category and the first ODACD for access control.

2.A second USIM is selected in the UE. Upon selection of the second USIM, the UE deletes the first ODACD.

3. The UE with the second USIM performs a registration procedure with a second AMF of a second PLMN for the second USIM.

The UE follows step 4a or 4b.

4a. when an event is triggered in the UE to access a 5GS (e.g. NG-RAN), the UE classifies access attempts to the access class only according to the standardized access class according to rules as defined in another aspect described later. The UE evaluates whether access to the access attempt is barred based on the access category of the access attempt and an access identity associated with the access attempt.

When an event is triggered in the UE to access 5GS (e.g. NG-RAN) and the access attempt is classified as a standard type (e.g. S-NSSAI or DNN, or OS-ID + APP ID or 5QI or S-NSSAI + DNN), the UE does not have access control on the access category. The UE accesses 5GS (e.g., NG-RAN) without access control.

The UE receives the second odadc in a second NAS message.

6. When an event is triggered in the UE to access a 5GS (e.g., NG-RAN), the UE classifies the access attempt to the access category according to the standardized access category and the second odadc. The UE evaluates whether access to the access attempt is barred based on the access category of the access attempt and an access identity associated with the access attempt.

In one example, when the UE selects a second USIM of the same UICC, the second USIM is selected.

In one example, a second USIM is selected when a user removes a first UICC containing a first USIM and inserts a second UICC containing a second USIM.

In one example, the change of the second USIM may occur during the UE turning on or off.

In one example of solutions 2 and 3, in case the USIM in the UE changes from a first USIM having IMSI 1 to a second USIM having IMSI 2 and IMSI 1 and IMSI 2 are different from each other, the UE sends an information element indicating the IMSI change in the UE to the network (e.g., AMF) in a NAS message (e.g., a REGISTRATION REQUEST message or any existing NAS message or a new NAS message). When the network receives an information element indicating an IMSI change in the UE, the network (e.g., AMF) sends the UE an ODACD corresponding to the new IMSI. When the UE receives ODACD from the network, the UE will follow the procedure as described in solutions 2 and 3. Optionally, in this scenario, the UE indicates to the network that the UE does not have ODACD for the IMSI, and the network sends ODACD for the IMSI upon receiving the indication.

In one example of solutions 2 and 3, when the UICC containing the USIM is inserted into the UE for the first time, the UE sends an information element indicating the first time the USIM is inserted to the network (e.g., the AMF) in a NAS message (e.g., a REGISTRATION REQUEST message or any existing NAS message or a new NAS message). When the network receives an information element indicating that a USIM is inserted for the first time, the network (e.g., AMF) sends an odadc corresponding to the new IMSI to the UE. When the UE receives this ODACD from the network, the UE will follow the procedure as described in solutions 2 and 3. When the UICC is inserted into the UE, the UE creates an entry in memory for the UICC containing the USIM. In one example, the entry is based on the IMSI of the USIM. In one case in this scenario, the UE has an ODACD for a PLMN selected by another USIM (another IMSI). Optionally, in this scenario, the UE indicates to the network that the UE does not have an ODACD for the IMSI, and the network sends the ODACD for the IMSI upon receiving the indication.

In one example, when the UE performs a registration procedure with the network (e.g., the AMF) or after the registration procedure is successfully completed, the AMF sends a NAS message (e.g., CONFIGURATION UPDATE COMMAND) or any existing NAS message or new NAS message) requesting the UE to send the current ODACD to the network. Upon receiving the NAS message, the UE sends the current odadc to the network in a NAS message (CONFIGURATION UPDATE COMPLETE). In the event that the network checks that the current odadc received from the UE is not the UE's most recent odadc, the network sends the most recent odadc to the UE in a NAS message (e.g., CONFIGURATION UPDATE COMMAND or any existing NAS message or a new NAS message). The UE will use the latest ODACD according to the procedures defined in solutions 2 and 3.

In one example, if the network detects that a UICC containing a usim (IMSI) is inserted into a new UE (a different IMEI), the network sends ODACD for that IMSI to the new IMSI in a NAS message (e.g., CONFIGURATION UPDATE COMMAND or any existing NAS message or a new NAS message). When the UE registers the IMSI with the network, the network keeps a record of the association of this IMSI and IMEI.

Fourth aspect (solution 4 to solve problem statement 5)

When receiving an odadc without integrity protection, the UE ignores the odadc.

Fig. 4 shows a signalling flow of a method according to the fourth aspect of the invention. The detailed steps of solution 4 are described below.

The UE is registered to the AMF of the PLMN and is not authenticated. That is, the authentication process fails and the EIA0 is activated in the UE (null integrity), or the authentication process is not initiated (e.g., the UE has no UICC or SIM, or adds SA3 text and no 5G subscription due to 4G to 5G).

The UE receives the first odadc from the 5GC in a NAS message, and the NAS message is not integrity protected. The odadc is sent during the registration procedure in step 1 or after the registration procedure in step 1.

The UE performs step 2a or 2b

Ue ignores the first odadc parameter. When a NAS event is triggered in the UE to access a 5GS (e.g., NG-RAN), the UE classifies access attempts to an access class according to only standardized access classes according to rules as defined in another aspect described later. The UE evaluates whether access to the access attempt is barred or allowed based on an access category associated with the access attempt.

2b. when a NAS event is triggered in the UE to access a 5GS (e.g. NG-RAN), the UE classifies access attempts to the access category according to the standardized access category and the first ODACD according to rules as defined in another aspect described later. The UE evaluates whether access to the access attempt is barred based on the access category of the access attempt and an access identity associated with the access attempt. The UE follows this procedure as long as the UE is not authenticated.

3. After successfully performing the initial registration procedure with authentication, the UE ignores the first ODACD and classifies the access attempt using only the standard access category until the UE receives the second ODACD. After receiving the second ODACD, the UE classifies the NAS event as a standardized access category or an operator defined access category as received in the second ODACD.

Fifth aspect (solution 5 to solve problem statement 6)

In a fifth aspect of the invention, a UAC for a UE that has registered to the same AMF for both 3GPP and non-3 GPP accesses is described.

Fig. 5 and 6 show the signalling flow of the method according to the fifth aspect of the invention. The detailed steps of solution 5 are described below.

The UE registers to the same AMF on both 3GPP and non-3 GPP accesses. The UE has received ODACD from the AMF. In this step, the UE is in a 5GMM-CONNECTED (5GMM CONNECTED) state on a non-3 GPP access and in a 5GMM-IDLE (5GMM IDLE) state on a 3GPP access.

The UE receives a NOTIFICATION message from the AMF over a non-3 GPP access. Upon receiving the NOTIFICATION message, the UE performs one of the following sequences of steps:

i) steps 3a and 4a of FIG. 5

ii) Steps 3a and 5a in FIG. 5

iii) Steps 3b and 4b in FIG. 6

iv) steps 3b and 5b in FIG. 6.

The UE decides to proceed with the service request procedure and the UE associates one of the following access categories to the service request procedure.

Access category:

i)MT_acc＝0

ii)MO_data＝7

iii) New Access Categories

In another aspect as described later a mapping table of access categories is mentioned.

In one example, the new access category is a standardized access category. That is, the new access category applies to all PLMNs and has the same functionality in all PLMNs.

In one example, a new RRC establishment cause is assigned for the new access category. The UE and the network treat this new RRC establishment cause differently than the existing RRC establishment causes.

In one example, for an RRC setup request message containing a new RRC establishment cause associated with a new access category, the gNB gives the highest priority to setup the RRC connection.

In one example, for an RRC setup request message containing a new RRC establishment cause associated with the new access category, the gNB gives priority to the same or lower than the establishment cause MT access to setup the RRC connection.

According to the mapping between access categories/access identities in another aspect as described later, the UE selects an RRC establishment cause for the RRC setup request message of the gNB.

The UE checks whether access attempts to the access category are barred or allowed. The UE performs one of steps 4a and 5a depending on whether the access attempt is barred or allowed.

4a. if access attempts to the access category are barred, the UE sends a NOTIFICATION RESPONSE message to the 5GC (i.e. AMF). The UE does not initiate a service request procedure to re-establish the user plane for the PDU session associated with the 3GPP access.

If the access attempt to the access category is not barred, the UE sends an RRC setup request containing the establishment cause to the gNB as described in step 3a. After establishing the RRC connection, the UE sends a SERVICE REQUEST message.

The UE decides to proceed with the registration procedure and the UE associates one of the following access categories to the registration procedure.

Access category:

i)MT_acc＝0，

ii)MO_sig＝3，

iii) new access category.

A new access category is defined in step 3a. The UE and the network follow the procedure for this new access category as defined in step 3a. The UE performs any one of steps 4b and 5b.

The UE selects an RRC establishment cause for the RRC setup request message of the gNB according to a mapping between access categories/access identities in another aspect as described later.

If the access category is barred, the UE sends a NOTIFICATION RESPONSE message.

If the access attempt for the access category is not barred, the UE sends an RRC connection to the NG-RAN with an RRC connection request, wherein the RRC connection request contains a cause associated with the access category selected in step 3a. After the RRC connection is established, the UE sends a REGISTRATION REQUEST message.

In one example, the UE will initiate a service request procedure in the event that the UE is in a CM-CONNECTED mode over a 3GPP access and in a CM-IDLE state over a non-3 GPP access, and the UE receives a NOTIFICATION message over the 3GPP access to establish a user plane over the 3GPP access for a PDU session associated with the non-3 GPP access. The UE associates the service request procedure to one of the access categories defined in step 3a. If access to the access category is not barred, the UE sends a service request message containing a list of PDU sessions associated with non-3 GPP access for which establishment of a user plane is allowed on the 3GPP access.

In one example, the above steps are applicable to a 5GS including ng-eNB and 5 GC. In this case, the UE transmits an RRC connection request with the establishment cause as described above.

On the other hand

The aforementioned odadc may include the following parameters:

a) a priority value indicating an order in which the UE should define class definitions for the matching rating operator;

b) the operator defines an access class number, i.e. an access class number in the range 32 to 63 that uniquely identifies the access class in the PLMN to which the access class is sent to the UE; and

c) one or more access category criteria types and associated access category criteria type values. The access category criteria type may be set to one of:

1) the DNN name;

2)5QI；

3) the OS Id + OS App Id of the application triggering the access attempt; or

4) S-NSSAI; and

d) an optional standardized access category, which is used in conjunction with the access identity to determine the establishment cause.

Here, each operator defined access category definition may have a different priority value. Multiple operator defined access category definitions may have the same operator defined access category number.

In one example, upon receiving a NAS signaling message with one or more operator defined access category definitions, the UE will store the operator defined access category definitions for the registered PLMNs.

In one example, upon receiving a NAS signaling message with a zero operator defined access category definition, the UE will delete the operator defined access category definition stored for the registered PLMN.

In one example, with the UE turned off, the UE will keep the operator defined access category definitions so that they can be used after turning on.

In one example, in the event that the UE selects a new PLMN that is not equivalent to the previously selected PLMN, the UE will cease using the operator defined access category definitions configured for the previously selected PLMN and will retain the operator defined access category definitions configured for the previously selected PLMN.

Any of the NAS messages described above may be sent between the UE and the AMF via a NG-RAN node (e.g., a gNB or NG-eNB).

Moreover, identifying one or more inventions may not always require a portion of the sequence, process, or message described above.

Table 1 is a mapping table of access categories as described above. The rules described above are the rules # (rules 1 to 10) in table 2.

Table 1: mapping table of access categories

Note 1: this includes 5GMM specific procedures when the service is ongoing, and 5GMM connection management procedures required to establish a PDU session of the request type "initial emergency request" or "existing emergency PDU session", or to re-establish user plane resources for such a PDU session. This also includes a SERVICE REQUEST procedure initiated with a SERVICE REQUEST message with the SERVICE type IE set to "emergency SERVICE fallback".

Note 2: for accesses for NAS signaling connection restoration during ongoing service, or for accesses for NAS signaling connection establishment after a fallback indication from lower layers during ongoing service, are mapped to the access category of ongoing service to derive the RRC establishment cause, but for this access attempt the barring check will be skipped.

Note 3: if the UE selects a new PLMN, checking membership using the selected PLMN; otherwise, the UE uses the RLPMN or a PLMN equivalent to the RPLMN.

Note 4: this includes a 5GMM connection management procedure triggered by the UE initiating the NAS transport procedure for transporting the MO SMS.

Note 5: in this specification release, UEs configured for NAS signaling low priority are not supported. If a UE supporting both S1 mode and N1 mode is configured for NAS signaling low priority in S1 mode as specified in 3GPP TS 24.368 or 3GPP TS 31.102, the UE will ignore the NAS signaling low priority configuration if in N1 mode.

Note 6: if the access category applicable for the access attempt is 1, the UE will additionally determine a second access category ranging from 3 to 7. If more than one access category matches, the lowest rule numbered access category will be selected. The UE will use only the second access category to derive the RRC establishment cause of the access attempt.

Note 7: "EAB Override" does not apply if the UE is not configured to allow EAB Override (see 3GPP TS 24.368[17] or "Override extended dAccessferring" page of NAS configuration MO in 3GPP TS 31.102[22 ]), or if the NAS has not received an indication from upper layers to Override EAB and the UE does not have a PDU session established with EAB Override.

Table 2: mapping table of access identification/access category and RRC establishment reason

In one example, all solutions (aspects) apply to 5GMM-IDLE mode or 5GMM-CONNECTED with RRC inactive.

In one example, in all solutions (aspects), when the UE performs the registration procedure with the PLMN for the second time, the UE registers with the first registered PLMN or an equivalent PLMN of the first registered PLMN or a PLMN different from the first registered PLMN.

In one example, in all solutions (aspects), the NAS event is a NAS procedure to access 5GS (i.e., NG-RAN or 5 GC).

In one example, in all solutions (aspects), the UE stores ODACD for each IMSI.

In one example, in all solutions (aspects), the IMSI is SUPI.

The user equipment (or "UE", "mobile station", "mobile device" or "wireless device") in the present invention is an entity connected to a network via a radio interface.

It should be noted that, as explained in the following paragraphs, the UE in the present specification is not limited to a dedicated communication apparatus, and may be applied to any apparatus having a communication function of the UE as described in the present specification.

The terms "user equipment" or "UE" (which term is used by 3 GPP), mobile station, "mobile device," and "wireless device" are generally intended to be synonymous with one another, and include stand-alone mobile stations, such as terminals, handsets, smartphones, tablets, cellular IoT devices, and machinery, and the like.

It should be understood that the terms "UE" and "wireless device" also encompass devices that remain stationary for long periods of time.

For example, the UE may be equipment used for production or manufacturing and/or energy-related machinery (e.g., equipment or machinery such as boilers, engines, turbines, solar panels, wind turbines, hydro generators, thermal generators, nuclear power generators, batteries, nuclear systems and/or related equipment, heavy-duty electric machinery, pumps (including vacuum pumps), compressors, fans, blowers, oil pressure equipment, pneumatic equipment, metal working machinery, manipulators, robots and/or applications thereof, tools, molds or dies, rollers, conveying equipment, lifting equipment, material handling equipment, textile machinery, sewing machines, printing and/or related machinery, paper processing machinery, chemical machinery, mining and/or construction machinery and/or related equipment, machinery and/or equipment used in agriculture, forestry, and/or fisheries, safety and/or environmental protection equipment, tractors, precision bearings, chain processing machinery, and/or equipment used in agriculture, forestry, and/or fisheries, and/or equipment used in safety and/or environmental protection (ii) a strip; a gear; a power transmission device; lubricating the equipment; a valve; a pipe fitting; and/or application systems for any of the foregoing devices or machines, etc.).

For example, the UE may be a transportation device (e.g., such as rail vehicles, motor vehicles, motorcycles, bicycles, trains, buses, carts, tricycles, boats and other watercraft, airplanes, rockets, satellites, drones, balloons, etc.).

For example, a UE may be an information and communication device (e.g., information and communication devices such as electronic computers and related devices; communication and related devices; electronic components, etc.).

For example, a UE may be a refrigerator, a refrigerator appliance, a trade and/or service industry device, a vending machine, an automated service machine, an office machine or device, a consumer electronics, and an electronic appliance (e.g., a consumer electronics appliance such as: an audio device; a video device; a speaker; 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 appliance; a cleaner; etc.).

For example, the UE may be an electrical application system or device (e.g., an electrical application system or device such as an x-ray system, a particle accelerator, a radioisotope device, an acoustic device, an electromagnetic application device, an electronic power application device, etc.).

For example, a UE may be an electronic light fixture, luminaire, measurement instrument, analyzer, tester, or measurement or sensing instrument (e.g., a measurement or sensing instrument such as a smoke alarm, a body alarm sensor, a motion sensor, a wireless tag, etc.), a watch or clock, a laboratory instrument, an optical device, a medical device and/or system, a weapon, tableware, or hand tool, etc.

For example, a UE may be a wirelessly equipped personal digital assistant or related device, such as a wireless card or module designed to be attached to or inserted into another electronic apparatus (e.g., a personal computer, an electrical measurement machine).

The UE may be part of a device or system that uses various wired and/or wireless communication technologies to provide the applications, services, and solutions described below with respect to the internet of things (IoT).

Internet of things devices (or "things") may be equipped with appropriate electronics, software, sensors, and/or network connections, among other things, to enable the devices to collect and exchange data with each other and other communication devices. The IoT device may include an automation device that follows software instructions stored in an internal memory. IoT devices may operate without human supervision or interaction. IoT devices may also remain stationary and/or inactive for long periods of time. The IoT devices may be implemented as part of (typically) stationary equipment. IoT devices may also be embedded in non-stationary devices (e.g., vehicles) or attached to animals or humans to be monitored/tracked.

It should be understood that IoT technology may be implemented on any communication device connectable to a communication network to transmit/receive data, whether such communication device is controlled by human input or by software instructions stored in memory.

It should be understood that IoT devices are also sometimes referred to as Machine Type Communication (MTC) devices or machine-to-machine (M2M) communication devices or narrowband-IoT UEs (NB-IoT UEs). It should be understood that a UE may support one or more IoT or MTC applications. Some examples of MTC applications are listed in table 3 (source: 3GPP TS 22.368, annex B, the contents of which are incorporated herein by reference). This list is not exhaustive and is intended to represent some examples of machine type communication applications.

Table 3: some examples of machine type communication applications.

The applications, services and solutions may be MVNO (mobile virtual network operator) services, emergency radio communication systems, PBX (Private Branch eXchange) systems, PHS/digital cordless telecommunications systems, POS (point of sale) systems, advertisement call systems, MBMS (multimedia broadcast and multicast service) systems, V2X (vehicle to all) systems, train radio systems, location related services, disaster/emergency radio communication services, community services, video streaming service, femtocell application service, VoLTE (LTE voice bearer) service, billing service, radio on demand service, roaming service, activity monitoring service, telecom operator/communication NW selection service, function restriction service, PoC (concept verification) service, personal information management service, ad hoc network/DTN (delay tolerant network) service, etc.

Furthermore, the above UE categories are only application examples of the technical concepts and exemplary aspects described in the present invention. Needless to say, these technical concepts and aspects are not limited to the above-described UE, and various modifications may be made thereto.

User Equipment (UE)

Fig. 7 shows the main components of the UE. As shown, the UE 10 includes transceiver circuitry 11, wherein the transceiver circuitry 11 is operable to transmit signals to and receive signals from the connecting node via one or more antennas 12. Although not necessarily shown in fig. 7, the UE will of course have all the usual functions of a conventional mobile device, such as the user interface 13, etc., and this functionality may be provided by any one or any combination of hardware, software and firmware, as appropriate. For example, the software may be pre-installed in memory and/or may be downloaded via a telecommunications network or from a removable data storage device (RMD). It should be noted that the arrows indicated in subsequent block diagrams represent examples of signal flow or data flow, but are not intended to be limited to a particular direction.

The controller 14 controls the operation of the UE 10 in accordance with software stored in the memory 15. For example, the controller 14 may be implemented by a Central Processing Unit (CPU). The software includes an operating system 16 and a communication control module 17 having at least a transceiver control module 18, and the like. The communication control module 17 (using its transceiver control sub-module) is responsible for handling (generating/transmitting/receiving) signalling and uplink/downlink data packets between the UE 10 and other nodes such as base stations/(R) AN nodes, MMEs, AMFs (and other core network nodes) etc. Such signaling may include, for example, appropriately formatted signaling messages related to connection establishment and maintenance (e.g., RRC messages), NAS messages such as periodic location update related messages (e.g., tracking area updates, paging area updates, location area updates), and the like.

(R) AN node

Fig. 8 shows the main components of AN exemplary (R) AN node, e.g., a base station ("eNB" in LTE, "gNB" in 5G). As shown, the (R) AN node 20 includes transceiver circuitry 21, wherein the transceiver circuitry 21 is operable to transmit signals to and receive signals from connected UEs via one or more antennas 22, and to transmit signals to and receive signals from other network nodes (directly or indirectly) via a network interface 23. The controller 24 controls the operation of the (R) AN node 20 according to software stored in the memory 25. For example, the controller 24 may be implemented using a Central Processing Unit (CPU). For example, the software may be pre-installed in the memory 25 and/or may be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 26, a communication control module 27 having at least a transceiver control module 28, and the like.

The communication control module 27 (using its transceiver control sub-module) is responsible for handling (generating/transmitting/receiving) (R) signaling (e.g., directly or indirectly) between the AN node 20 and other nodes such as UEs, MMEs, AMFs, etc. The signaling may include, for example, appropriately formatted signaling messages (e.g., RRC connection setup and other RRC messages) related to radio connection and positioning procedures (for a particular UE), particularly related to connection establishment and maintenance, periodic location update related messages (e.g., tracking area updates, paging area updates, location area updates), S1 AP messages and NG AP messages (i.e., messages over the N2 reference point), and so forth. Such signaling may also include, for example, broadcast information (e.g., primary information and system information) in the case of transmission.

The controller 24 is also configured (by software or hardware) to process related tasks such as (where implemented) UE motion estimation and/or motion trajectory estimation.

AMF

FIG. 9 shows the main components of the AMF. AMF 30 is included in 5 GC. As shown, the AMF 30 includes transceiver circuitry 31, wherein the transceiver circuitry 31 is operable to transmit signals to and receive signals from other nodes (including UEs) via a network interface 32. Controller 33 controls the operation of AMF 30 in accordance with software stored in memory 34. For example, the controller 33 may be implemented using a Central Processing Unit (CPU). For example, the software may be pre-installed in memory and/or may be downloaded via a telecommunications network or from a removable data storage device (RMD). The software includes an operating system 35 and a communication control module 36 having at least a transceiver control module 37, and the like.

The communication control module 37 (using its transceiver control sub-module) is responsible for handling (generating/transmitting/receiving) signaling (e.g., directly or indirectly) between the AMF and other nodes such as UEs, base station/(R) AN nodes (e.g., "gNB" or "eNB"), etc. Such signaling may include, for example, appropriately formatted signaling messages related to the processes described herein, such as NG AP messages (i.e., messages over the N2 reference point) to transmit NAS messages to and receive NAS messages from UEs, and so forth.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

This application is based on and claims the benefit of priority of indian patent application 201811037573 filed on 4.10.2018, the disclosure of which is incorporated herein by reference in its entirety.

List of reference numerals

10 UE

11 transceiver circuit

12 aerial

13 user interface

14 controller

15 memory

16 operating system

17 communication control module

18 transceiver control module

20 (R) AN node

21 transceiver circuit

22 antenna

23 network interface

24 controller

25 memory

26 operating system

27 communication control module

28 transceiver control module

30 AMF

31 transceiver circuit

32 network interface

33 controller

34 memory

35 operating system

36 communication control module

37 transceiver control module