First communication device, user equipment and methods thereof
The AMF node initiates the PDU session release process when the network slice authorization is revoked, which solves the problem that the network slice associated PDU sessions are not clearly handled in the prior art, realizes the timely recycling of network slice resources and the update of user equipment configuration, and ensures services stability.
Patent Information
- Application Number
- CN202410867300.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2019-12-26
- Filing Date
- 2020-12-18
- Publication Date
- 2024-11-01
AI Technical Summary
In the case where network slice authorization is revoked, the prior art does not specify how to handle the PDU session associated with the network slice, resulting in inconvenience in management.
After receiving the authorization revocation message of the network slice identifier, the AMF node initiates a release process to release the PDU session associated with the network slice identifier, and notifies the session management function (SMF) and user equipment (UE) to update the UE's NSSAI configuration to remove the undocumented network slice identifier from the allowed collection.
When the network slicing authorization is revoked, the associated PDU session can be properly managed and released, ensuring timely recycling of network slicing resources and configuration updates of user equipment, avoiding resource waste and service interruptions.
Smart Images

Figure CN118890624A_ABST
Abstract
Description
[0001] This application is a divisional application of the Chinese invention patent application with application date of December 18, 2020, application number 202080057518.2, and invention name “AMF node and method thereof”. Technical Field
[0002] The present invention relates to cellular networks, and in particular to the management of an association (eg, a Protocol Data Unit (PDU) session) between a radio terminal and a data network. Background Art
[0003] The 5G system (5GS) connects a radio terminal (user equipment (UE)) to a data network (DN). In the 5G architecture, the connection service between the UE and the DN is supported by one or more protocol data unit (PDU) sessions (for example, see non-patent literature 1-3). A PDU session is an association, session or connection between the UE and the DN. The PDU session is used to provide PDU connection services (i.e., the exchange of PDUs between the UE and the DN). A PDU session is established between the user plane function (UPF) to which the DN is connected (i.e., the PDU session anchor) and the UE. In terms of data transmission, a PDU session consists of a tunnel (N9 tunnel) in the 5G core network (5GC), a tunnel (N3 tunnel) between the 5GC and the access network (AN), and one or more radio bearers.
[0004] Non-patent document 2 (3GPP TS23.502) and non-patent document 3 (3GPP TS24.501) specify a PDU session establishment process and a PDU session release process. More specifically, the PDU session establishment process is described, for example, in Section 4.3.2.2 of non-patent document 1 and Section 6.4.1 of non-patent document 2. The PDU session release process is described, for example, in Section 4.3.4.2 of non-patent document 1 and Sections 6.3.3 and 6.4.3 of non-patent document 2.
[0005] 5GS also supports network slicing (for example, see non-patent documents 1 to 3, especially Section 5.15 of non-patent document 1). Network slicing uses network function virtualization (NFV) technology and software defined network (SDN) technology to create multiple virtualized logical networks on a physical network. Each virtualized logical network is called a network slice. Network slices provide specific network capabilities and network characteristics. In order to form a single network slice, a network slice instance (NSI) is defined as a collection of network function (NF) instances, resources (for example, computer processing resources, storage, and network resources), and access networks (ANs) (at least one of the next generation radio access network (NG-RAN) and non-3GPP interworking functions (N3IWF)).
[0006] A network slice is identified by an identifier called Single Network Slice Selection Assistance Information (S-NSSAI). S-NSSAI consists of a Slice / Service Type (SST) and a Slice Differentiator (SD). SST refers to the expected network slice behavior in terms of features and services. SD is optional information and supplements SST to distinguish multiple network slices of the same slice / service type.
[0007] S-NSSAI can have standard values or non-standard values. Currently, standard SST values 1, 2, 3, and 4 are associated with enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), massive Internet of Things (MIoT), and vehicle-to-everything (V2X) slice types, respectively. The non-standard value of S-NSSAI identifies a single network slice within a specific public land mobile network (PLMN). In other words, the non-standard value is a PLMN-specific value and is associated with the PLMN ID of the PLMN to which these values are assigned. Each S-NSSAI ensures network isolation by selecting a specific NSI. NSIs can be selected via different S-NSSAIs. S-NSSAIs can be associated with different NSIs. Network slices can be uniquely identified by S-NSSAI.
[0008] There are two types of S-NSSAI referred to as S-NSSAI and mapped S-NSSAI. The S-NSSAI identifies the network slice served by the public land mobile network (PLMN) with which the UE is registered. The mapped S-NSSAI may be an S-NSSAI of a home PLMN (HPLMN) mapped to (associated with or applicable to) an S-NSSAI that identifies a network slice of a roaming network when the UE is roaming, and may also be an S-NSSAI included in the subscription information of the UE. Hereinafter, in this specification, the S-NSSAI and the mapped S-NSSAI may be simply collectively referred to as the S-NSSAI.
[0009] In one aspect, network slice selection assistance information (NSSAI) means a collection of S-NSSAI. Thus, one or more S-NSSAI may be included in one NSSAI. There are multiple types of NSSAI referred to as configured NSSAI, requested NSSAI, allowed NSSAI, rejected NSSAI, and pending NSSAI.
[0010] The configured NSSAI includes one or more S-NNSAIs, each of which is applicable to one or more PLMNs. For example, the configured NSSAI is configured by the serving PLMN and is applied to the serving PLMN. Alternatively, the configured NSSAI may be a default configured NSSAI. The default configured NSSAI is configured by the home PLMN (HPLMN) and is applied to any PLMN to which a specific configured NSSAI is not provided. For example, the default configured NSSAI is provided to a radio terminal (user equipment (UE)) from the Unified Data Management (UDM) of the HPLMN via the Access and Mobility Management Function (AMF).
[0011] The requested NSSAI is signaled by the UE to the network, for example during a registration procedure, thereby enabling the network to determine a serving AMF, at least one network slice and at least one NSI for the UE.
[0012] The allowed NSSAI is provided by the serving PLMN to the UE and represents one or more S-NSSAIs that the UE can use in the current registration area of the serving PLMN. The allowed NSSAI is determined by the AMF of the serving PLMN, for example during the registration procedure. Therefore, the allowed NSSAI is signaled to the UE by the network (i.e., AMF) and stored in the (non-volatile) memory of both the AMF and the UE.
[0013] The rejected NSSAI includes one or more S-NSSAIs rejected by the current PLMN. The rejected NSSAI may be referred to as a rejected S-NSSAI. The S-NSSAI is rejected in the entire current PLMN or in the current registration area. If the AMF rejects any S-NSSAI in one or more S-NSSAIs included in the requested NSSAI, for example during the registration process of the UE, the AMF includes these S-NSSAIs in the rejected NSSAI. The rejected NSSAI is signaled to the UE by the network (i.e., the AMF) and stored in the (non-volatile) memory of both the AMF and the UE.
[0014] The suspended NSSAI is newly agreed upon in the 3rd Generation Partnership Project (3GPP) (see non-patent document 4). The suspended NSSAI indicates one or more S-NSSAIs that are being suspended by the network slice specific authentication and authorization (NSSAA). The serving PLMN shall perform NSSAA on the S-NSSAI of the HPLMN subject to NSSAA based on the subscription information. In order to perform NSSAA, the AMF invokes an authorization process based on the Extensible Authentication Protocol (EAP). The EAP-based authentication process takes a relatively long time to obtain its results. Therefore, although the AMF determines the allowed NSSAI as described above during the UE's registration process, the AMF does not include the S-NSSAI subject to NSSAA in the allowed NSSAI, but includes these S-NSSAI in the suspended NSSAI. The suspended NSSAI is signaled to the UE by the network (i.e., AMF) and is stored in the (non-volatile) memory of both the AMF and the UE.
[0015] The AMF manages the UE context of the UE in the Registration Management (RM) Registered (RM-REGISTERED) state. The UE context may be referred to as, but not limited to, a Mobility Management (MM) context. The UE context may include one or more of the above-mentioned allowed NSSAI, rejected NSSAI, and suspended NSSAI. Additionally or alternatively, the UE context may include information indicating the status of the S-NSSAI included in one or more of the above-mentioned allowed NSSAI, rejected NSSAI, and suspended NSSAI. Specifically, the information indicating the status of the S-NSSAI may be information indicating whether each S-NSSAI is deactivated or activated. Alternatively, the information indicating the status of the S-NSSAI may be information indicating whether each S-NSSAI is invalid or valid. On the other hand, the UE manages the UE NSSAI configuration, which includes the above-mentioned configured NSSAI, allowed NSSAI, rejected NSSAI, and suspended NSSAI. The UE NSSAI configuration is stored in a non-volatile memory within the UE (Mobile Equipment (ME) other than the Universal Subscriber Identity Module (USIM)). The memory or memory area in which the UE NSSAI configuration is stored is referred to as NSSAI storage.
[0016] Section 5.15.10 of non-patent document 1 (3GPP TS23.501) and Section 4.2.9 of non-patent document 2 (3GPP TS 23.502) specify network slice specific authentication and authorization (NSSAA). More specifically, Section 5.15.10 of non-patent document 1 and Section 4.2.9.2 of non-patent document 2 describe NSSAA. Section 5.15.10 of non-patent document 1 and Section 4.2.9.3 of non-patent document 2 describe re-authentication and re-authorization triggered by an authentication, authorization, and accounting (AAA) server (AAA-S). Section 5.15.10 of non-patent document 1 and Section 4.2.9.4 of non-patent document 2 describe revocation of slice-specific authorization triggered by an AAA server. In addition, non-patent document 5 describes proposed modifications to the revocation of slice-specific authorization as specified in Section 4.2.9.4 of non-patent document 2.
[0017] Prior art literature
[0018] Non-patent literature
[0019] Non-patent document 1: 3GPP TS23.501V16.2.0 (2019-09) "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; SystemArchitecture for the 5G System (5GS); Stage 2 (Release 16)", September 2019
[0020] Non-patent document 2: 3GPP TS23.502V16.2.0 (2019-09) "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16)", September 2019
[0021] Non-patent document 3: 3GPP TS24.501V16.2.0 (2019-09) "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release16)", September 2019
[0022] Non-patent document 4: InterDigital, ZTE, vivo, NEC, "Introduction of pending NSSAI for network slice-specific authentication and authorization", C1-199044, 3GPPTSG-CT WG1 Meeting#121, Reno (NV), USA, 11-15November 2019
[0023] Non-patent document 5: China Mobile, Nokia, Ericsson, Telecom Italia, “Service used for slice-specific re-authentication and revocation”, S2-1912488, 3GPP TSG-SAWG2 Meeting #136, Reno NV, USA, 18-22 November 2019 Summary of the invention
[0024] Problem that the invention aims to solve
[0025] As mentioned above, Section 4.2.9.4 of Non-Patent Document 2 describes the revocation of slice-specific authorization triggered by the AAA server (AAA-S). In this process, the AAA server (AAA-S) requests the revocation of the authorization of the network slice identified by a specific S-NSSAI, and the AMF signals the UE to update the UE NSSAI configuration (NSSAI storage), thereby removing the S-NSSAI from the currently allowed NSSAI.
[0026] However, if there is an established PDU session associated with the network slice for which the slice-specific authorization is being revoked, it is unclear how to handle the PDU session.
[0027] One of the purposes of the embodiments disclosed herein is to provide devices, methods and programs that help properly manage PDU sessions associated with a network slice when the authorization of the network slice is revoked. It should be noted that this purpose is only one of the purposes of the embodiments disclosed herein. Other purposes or problems and novel features will be apparent from the following description and drawings.
[0028] Solutions for solving problems
[0029] In a first aspect, an AMF comprises: at least one memory; and at least one processor coupled to the at least one memory. The at least one processor is configured to initiate a release procedure in response to revocation of authorization of a first network slice identifier used by a UE to release a PDU session associated with the first network slice identifier.
[0030] In a second aspect, the method in the AMF comprises, in response to revocation of authorization of a first network slice identifier used by the UE, initiating a release procedure to release a PDU session associated with the first network slice identifier.
[0031] In a third aspect, a UE comprises: at least one memory; and at least one processor coupled to the at least one memory. The at least one processor is configured to, in response to revoking an authorization of a first network slice identifier used by the UE, request a network to release a PDU session associated with the first network slice identifier.
[0032] In a fourth aspect, the method in the UE includes: in response to revocation of authorization of a first network slice identifier used by the UE, requesting the network to release a PDU session associated with the first network slice identifier.
[0033] In a fifth aspect, the program includes instructions (software codes), which, when loaded into a computer, cause the computer to perform the method according to the second aspect or the fourth aspect described above.
[0034] Effects of the Invention
[0035] According to the above aspects, devices, methods and programs can be provided to help properly manage PDU sessions associated with a network slice when the authorization of the network slice is revoked. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Figure 1 is a diagram showing a structural example of a cellular network according to an embodiment;
[0037] Figure 2 is a flowchart illustrating an example of the operation of the AMF according to an embodiment;
[0038] Figure 3 is a sequence diagram showing an example of operations of a UE, an AMF, an SMF, and an AUSF according to an embodiment;
[0039] Figure 4 is a sequence diagram showing an example of operations of a UE, an AMF, an SMF, and an AUSF according to an embodiment;
[0040] Figure 5 is a sequence diagram showing an example of operations of a UE, an AMF, and an SMF according to an embodiment;
[0041] Figure 6 is a flowchart illustrating an example of the operation of the AMF according to an embodiment;
[0042] Figure 7 is a flowchart showing an example of the operation of a UE according to an embodiment;
[0043] Figure 8 is a sequence diagram showing an example of operations of a UE, an AMF, and an AUSF according to an embodiment;
[0044] Fig. 9 is a block diagram showing a structural example of a UE according to an embodiment; and
[0045] Fig.10 is a block diagram showing a structural example of an AMF according to an embodiment. DETAILED DESCRIPTION
[0046] The specific embodiments will be described in detail below with reference to the accompanying drawings. In the entire drawings, the same or corresponding elements are represented by the same symbols, and for the sake of clarity, repeated descriptions are omitted if necessary.
[0047] Each embodiment described below can be used alone, or two or more of these embodiments can be appropriately combined with each other. These embodiments include novel features that are different from each other. Therefore, these embodiments help to achieve different purposes or solve different problems from each other, and help to obtain different advantages from each other.
[0048] The following description of the embodiments mainly focuses on the 3rd Generation Partnership Project (3GPP) fifth generation mobile communication system (5G system (5GS)). However, these embodiments can be applied to other cellular communication systems that support network slicing similar to that of 5GS.
[0049] First embodiment
[0050] Figure 1 A structural example of a cellular network (i.e., 5GS) according to the present embodiment is shown. Figure 1The various elements shown are network functions and provide interfaces as defined by the 3rd Generation Partnership Project (3GPP). Figure 1 The various elements (network functions) shown may be implemented, for example, as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtual functions instantiated on an application platform.
[0051] Figure 1 The cellular network shown may be provided by a mobile network operator (MNO), or may be a non-public network (NPN) provided by a non-MNO. Figure 1 The cellular network shown is an NPN, the cellular network may be a standalone network denoted as a Standalone Non-Public Network (SNPN), or the cellular network may be an NPN linked to an MNO network denoted as a Public Network Integrated NPN.
[0052] A radio terminal (ie, UE) 1 uses a 5G connection service and communicates with a data network (DN) 7. More specifically, UE 1 is connected to an access network (ie, a 5G access network (5GAN)) 5 and communicates with DN 7 via a user plane function (UPF) 6 in a core network (ie, a 5G core network (5GC)). AN 5 may include a next generation radio access network (NG-RAN) or a non-3GPP AN or both. A non-3GPP AN may be a network that handles wireless LAN (WiFi) communications or a network that handles wired communications (referred to as a wired 5G access network (W-5GAN)). UPF 6 may include a plurality of interconnected UPFs.
[0053] UE 1 establishes one or more PDU sessions between UE 1 and UPF 6 (i.e., PDU session anchor) to which DN 7 is connected. As already explained, a PDU session is an association, session or connection between a UE and a DN. A PDU session is used to provide a PDU connection service (i.e., the exchange of PDUs between UE 1 and DN 7). In terms of data transmission, a PDU session consists of a tunnel in 5GC (N9 tunnel), a tunnel between 5GC and AN 5 (N3 tunnel), and one or more radio bearers. Although in Figure 1 Although not shown in the figure, UE 1 can establish multiple PDU sessions with multiple UPFs (PDU Session Anchors) 6 to access multiple DNs 7 at the same time.
[0054] AMF 2 is one of the network functions in the 5GC control plane. AMF 2 provides termination of the RAN control plane (CP) interface (i.e., N2 interface). AMF 2 terminates a single signaling connection with UE 1 (i.e., N1 NAS signaling connection), and provides registration management, connection management, and mobility management. AMF 2 provides NF services to NF consumers (e.g., other AMFs, session management function (SMF) 3, and authentication server function (AUSF) 4) on a service-based interface (i.e., Namf interface). The NF services provided by AMF 2 include communication services (Namf_Communication). The communication service enables NF consumers (e.g., SMF 3) to communicate with UE 1 or AN 5 via AMF 2.
[0055] SMF 3 is one of the network functions in the 5GC control plane. SMF 3 manages PDU sessions. SMF 3 sends and receives SM signaling messages (NAS-SM messages, N1 SM messages) from the non-access stratum (NAS) session management (SM) layer of UE 1 via the communication service provided by AMF 2. SMF 3 provides NF services to NF consumers (e.g., AMF 2, other SMFs) on a service-based interface (i.e., Nsmf interface). The NF services provided by SMF 3 include PDU session management services (Nsmf_PDUSession), which enable NF consumers (e.g., AMF 2) to handle PDU sessions. SMF 3 can be an intermediate SMF (I-SMF). In the case where UPF 6 belongs to a different SMF service area and cannot be controlled by the original SMF 3, an I-SMF is inserted between AMF 2 and the original SMF 3 as needed.
[0056] AUSF 4 is one of the network functions in the 5GC control plane. AUSF 4 provides NF services to NF consumers (e.g., AMF 2, UDM 8) on a service-based interface (i.e., Nausf interface). The NF services provided by AUSF 4 include UE authentication services (e.g., Nausf_UEAuthentication and Nausf_NSSAA_Authenticate). The Nausf_UEAuthentication service provides UE authentication and related key information (key control material) to the NF consumer (i.e., AMF). More specifically, AUSF 4 collaborates with UDM8 and the Authentication Credential Repository and Processing Function (ARPF) to perform authentication using one of the two authentication methods supported by 5GS (i.e., 5G Authentication and Key Agreement (AKA) and EAP-based authentication). After authentication, AUSF 4 replies to AMF 2 with the authentication result and, if successful, the master key. The master key is used by AMF 2 to derive NAS security keys and (one or more) other security keys. For UE authentication, AUSF 4 works closely with UDM 8. The Nausf_NSSAA_Authenticate service provides network slice specific authentication and authorization services between UE 1 and AAA server to NF consumers (e.g., AMF 2) via AUSF 4.
[0057] UDM 8 is one of the network functions in the 5GC control plane. UDM 8 provides access to a database (i.e., User Data Repository (UDR)) for storing user data (subscription information). UDM 8 provides NF services to NF consumers (e.g., AMF 2, AUSF 4, SMF 3) over a service-based interface (i.e., Nudm interface). The NF services provided by UDM 8 include user data management services, which enable NF consumers (e.g., AMF) to retrieve user data and provide updated user data to NF consumers.
[0058] For ease of explanation, Figure 1 The structural example in FIG. 1 shows only typical NFs. The cellular network according to this embodiment may include Figure 1 Other NFs not shown in the figure, such as Network Slice Selection Function (NSSF) and Policy Control Function (PCF).
[0059] Figure 2is a flow chart showing an example of the operation of AMF 2. In step 201, AMF 2 receives a message from AUSF 4 indicating the revocation of the authorization of a specific S-NSSAI (or a network slice identified thereby) used by UE1. In step 202, AMF 2 initiates a release procedure to release all PDU sessions associated with the specific S-NSSAI in response to the revocation of the authorization of the specific S-NSSAI (or the network slice identified thereby) used by UE1. AMF 2 may initiate a PDU session release procedure in response to receiving a revocation message from AUSF 4.
[0060] If a PDU session for an emergency call (e.g., emergency service) associated with the specific S-NSSAI is established, AMF 2 may be configured to exclude the release of the PDU session for the emergency call from the above-mentioned release process. In other words, in the above-mentioned release process, AMF 2 may initiate a release process to release all PDU sessions associated with the specific S-NSSAI except the PDU session for the emergency call. A PDU session for an emergency call associated with a specific S-NSSAI may mean a PDU session for an emergency call, in which a specific S-NSSAI is set in the AMF emergency configuration data stored by AMF 2, the S-NSSAI is notified from AMF 2 to SMF 3, and the S-NSSAI is used by SMF 3 when establishing the PDU session.
[0061] According to the PDU session release procedure described in Section 4.3.4.2 of Non-Patent Document 2, AMF 2 may perform (or call) a procedure (e.g., Nsmf_PDUSession_UpdateSMContext (or Nsmf_PDUSession_ReleaseSMContext service operation) to release one or more PDU sessions associated with a specific S-NSSAI. In this procedure, AMF 2 may send a message (e.g., Nsmf_PDUSession_UpdateSMContext message) containing a release indication to SMF 3. AMF 2 may notify SMF 3 of the PDU session IDs of one or more PDU sessions associated with the S-NSSAI to invoke the network-requested PDU session release procedure. AMF 2 may include these PDU session IDs in the above message, or may notify SMF 3 of these PDU session IDs through another message. AMF 2 may include the S-NSSAI in the above message, or may notify SMF 3 of the S-NSSAI through another message. Alternatively, AMF 2 may notify SMF 3 of the PDU session IDs of the PDU session associated with the S-NSSAI. 3 Send Nsmf_PDUSession_ReleaseSMContext message. AMF 2 may include the PDU session ID of one or more PDU sessions associated with the S-NSSAI in the Nsmf_PDUSession_ReleaseSMContext message. AMF 2 may include the relevant S-NSSAI in the Nsmf_PDUSession_ReleaseSMContext message.
[0062] AMF 2 may notify SMF 3 of the revocation of authorization of a specific S-NSSAI (or network slice identified thereby) used by UE 1 during the PDU session release process. Specifically, AMF 2 may send a message to SMF 3 containing a cause information element (IE) indicating the revocation of authorization for the S-NSSAI (or network slice). The message may, for example, be an Nsmf_PDUSession_UpdateSMContext message (or Nsmf_PDUSession_ReleaseSMContext message). Alternatively, AMF 2 may notify SMF 3 of the cause IE indicating the revocation of authorization for the S-NSSAI (or network slice) in a separate message different from the above message.
[0063] Figure 2 The operations shown enable AMF 2 to quickly release the PDU Session associated with the network slice whose authorization has been revoked.
[0064] Figure 3An example of a slice-specific authorization revocation process initiated (or triggered) by AAA-S is shown. In step 301, AAA-S 9 requests revocation of authorization of a network slice identified by a specific S-NSSAI (S-NSSAI#1 in this case). Specifically, AAA-S 9 may send a revoke authorization request message (e.g., AAA protocol revoke authorization request message) to AUSF 4. The message indicates S-NSSAI#1 and further indicates the universal public subscription identifier (GPSI) of UE 1. The message may be sent directly from AAA-S 9 to AUSF 4, or may be sent to AUSF 4 via an AAA proxy (AAA-P) not shown.
[0065] In step 303, AUSF 4 notifies AMF 2 of the occurrence of a revocation event of the authorization of S-NSSAI#1 used by UE 1 via the NFS service provided by AUSF 4. Specifically, AUSF 4 obtains the AMFID representing AMF 2 from UDM 8 by calling a procedure (e.g., Nudm_UECM_Get procedure) using the GPSI of UE 1 contained in the message received in step 301 (steps 302A and 302B). AUSF 4 may then send a message (e.g., Nausf_NSSAA_Notify message) to AMF 2 represented by the AMF ID, which indicates that a revocation event of the authorization of S-NSSAI#1 used by UE 1 has occurred. The notification from AUSF 4 to AMF 2 indicates S-NSSAI#1 and further indicates the GPSI of UE 1.
[0066] In step 304, if there are PDU sessions of UE 1 associated with S-NSSAI #1 whose authorization is revoked, AMF 2 performs (or calls) Nsmf_PDUSession_UpdateSMContext (or Nsmf_PDUSession_ReleaseSMContext) service operations to release all PDU sessions of UE 1 associated with S-NSSAI #1. In this process, AMF 2 sends a message (e.g., Nsmf_PDUSession_UpdateSMContext message) containing a release indication to SMF 3. AMF 2 may notify SMF 3 of the PDU session IDs of one or more PDU sessions associated with the S-NSSAI to invoke the network requested PDU session release procedure. AMF 2 may include these PDU session IDs in the above message, or may notify SMF 3 of these PDU session IDs through another message. AMF 2 may include the S-NSSAI in the above message, or may notify SMF 3 of the S-NSSAI through another message. Alternatively, AMF 2 may send a Nsmf_PDUSession_ReleaseSMContext message to SMF 3. AMF 2 may include the PDU session IDs of one or more PDU sessions associated with the S-NSSAI in the Nsmf_PDUSession_ReleaseSMContext message. AMF 2 may include the S-NSSAI in the Nsmf_PDUSession_ReleaseSMContext message. As described above, the message may include a cause IE indicating the revocation of authorization of the S-NSSAI (or network slice) (e.g., REL_DUE_TO_SLICE_REVOCATION). Alternatively, the cause IE indicating the revocation of authorization of the S-NSSAI (or network slice) (e.g., REL_DUE_TO_SLICE_REVOCATION) may be sent to SMF 3 via a message separate from the above message.
[0067] In step 305, AMF 2 signals UE 1 to update the UE NSSAI configuration (NSSAI storage) so as to remove the S-NSSAI #1 whose authorization is revoked from the currently allowed NSSAI. Specifically, AMF 2 sends a UE configuration update command message to UE 1, which indicates that S-NSSAI #1 will be removed from the allowed NSSAI and S-NSSAI #1 will be included in the rejected NSSAI. In response to the reception of the UE configuration update command message, UE 1 updates its own UE NSSAI configuration (NSSAI storage) stored in the (non-volatile) memory of UE 1. Specifically, UE 1 removes S-NSSAI #1 from the allowed NSSAI within the UE NSSAI configuration (NSSAI storage) and stores S-NSSAI #1 in the rejected NSSAI. The UE configuration update command message may include a reason IE indicating the revocation of the S-NSSAI (or network slice) authorization. The Cause IE could be, for example, "S-NSSAI is unavailable due to network slice specific authorization and authentication failure or revocation."
[0068] In response to receiving the UE configuration update command message, UE 1 manages to include S-NSSAI #1 as a rejected S-NSSAI in the rejected NSSAI. UE 1 may also store a cause value indicating the reason for the rejection (i.e., revocation of authorization) in association with S-NSSAI #1. The cause value may be "network slice specific authorization and authentication failure" or "network slice specific authorization and authentication revocation".
[0069] After resolving the cause of the network slice-specific authorization and authentication failure or resolving the cause of the revocation, UE 1 may include the requested NSSAI including S-NSSAI#1 in a registration request message and send the message to AMF 2 in order to enjoy the services provided by S-NSSAI#1 again.
[0070] Sometimes UE 1 or the user of UE 1 is able to know the reason for the revocation of the network slice specific authorization and authentication. Therefore, UE 1 or the user of UE 1 can take measures on the network to solve the reason. After that, UE 1 can include the requested NSSAI including S-NSSAI#1 in the registration request message and send the message to AMF 2 in order to enjoy the service provided by S-NSSAI#1 again.
[0071] Can be modified appropriately Figure 3 For example, AMF 2 may request SMF 3 to release the PDU session after the UE configuration update procedure (step 304). Figure 3Before, after, or during the process of revoking the authorization of S-NSSAI#1, AMF 2 may notify UDM 8 of the revoked authorization of S-NSSAI#1. In this case, AMF 2 may include information of the revoked authorization of S-NSSAI#1 in a Nudm_SDM_Info message or a Nudm_SDM_Update message or a UEAuthentication_ResultConfirmation message, and send the information to UDM 8. UDM 8 updates the subscriber data with the information about the revoked authorization of S-NSSAI#1, and sends a reply message to AMF 2.
[0072] Figure 4 Another example of a slice-specific authorization revocation procedure initiated (or triggered) by AAA-S is shown. Figure 4 In the embodiment, AMF 2 requests SMF 3 to release the PDU session (step 405) after the UE configuration update process (step 403).
[0073] Figure 4 Steps 401-403 and Figure 3 The steps 301-303 are similar. In step 404, AMF 2 performs a UE configuration update procedure to remove the S-NSSAI#1 whose authorization is revoked from the currently allowed NSSAI. During the UE configuration update procedure, AMF2 sends a UE configuration update command message to UE 1, which indicates that S-NSSAI#1 will be removed from the allowed NSSAI and S-NSSAI#1 will be included in the rejected NSSAI. The UE configuration update command message may include a reason IE indicating the revocation of the S-NSSAI (or network slice) authorization. The reason IE may be, for example, "S-NSSAI is unavailable due to network slice specific authorization and authentication failure or revocation."
[0074] If there are one or more PDU Sessions of UE 1 associated with S-NSSAI #1, AMF 2 includes an information element indicating a grace period before releasing these PDU Sessions in the UE Configuration Update Command message. The information element may be the value of a timer for determining the expiration of the grace period. AMF 2 may start a timer when triggered by the transmission of the UE Configuration Update Command message. Alternatively, AMF 2 may start a timer when triggered by the reception of a response message (e.g., a UE Configuration Update Complete message) to the UE Configuration Update Command message.
[0075] If the timer for measuring the grace period expires (step 405), AMF 2 calls the Nsmf_PDUSession_UpdateSMContext or (Nsmf_PDUSession_ReleaseSMContext) service operation to release all PDU sessions of UE 1 associated with S-NSSAI#1 (step 406). More specifically, AMF 2 sends a Nsmf_PDUSession_UpdateSMContext message (or Nsmf_PDUSession_ReleaseSMContext message) to SMF 3. As described above, the message may include a cause IE indicating the revocation of the S-NSSAI (or network slice) authorization (e.g., REL_DUE_TO_SLICE_REVOCATION). If AMF 2 receives a start of a procedure to release a PDU session from UE 1 before the timer for measuring the grace period expires, AMF 2 may stop the timer and terminate the network-requested PDU session release procedure.
[0076] Figure 4 The procedure enables AMF 2 to inform UE 1 that the PDU session associated with the network slice whose authorization was revoked will be released after a grace period has passed.
[0077] Figure 5 An example of a PDU session release procedure is shown. In step 501, AMF 2 sends a message (e.g., Nsmf_PDUSession_UpdateSMContext message or Nsmf_PDUSession_ReleaseSMContext message) to SMF 3 to request the release of a PDU session associated with a network slice whose authorization is revoked. The message contains a release indication, and a reason IE indicating the revocation of the S-NSSAI (or network slice) authorization (e.g., REL_DUE_TO_SLICE_REVOCATION). AMF 2 may notify SMF 3 of the PDU session IDs of one or more PDU sessions associated with the S-NSSAI to invoke the network requested PDU session release procedure. AMF 2 may include these PDU session IDs in the above message, or may notify SMF 3 of these PDU session IDs via a separate message. AMF 2 may include the S-NSSAI in the above message, or may notify SMF 3 of the S-NSSAI via a separate message. Step 501 and Figure 3 Step 304 or Figure 4 Corresponding to step 406.
[0078] In step 502, SMF 3 sends a response message to AMF 2. For example, SMF 3 may respond to AMF 2 with a Nsmf_PDUSession_UpdateSMContext response message or a Nsmf_PDUSession_ReleaseSMContext Response message response message. The message includes an N1 SM container containing a PDU session release command. The message may also include a cause IE indicating a revocation of S-NSSAI (or network slice) authorization (e.g., REL_DUE_TO_SLICE_REVOCATION). Additionally or alternatively, the PDU session release command may include a 5GSM cause IE indicating a revocation of S-NSSAI (or network slice) authorization (or the S-NSSAI is not available).
[0079] In step 503, AMF 2 sends a NAS message including an N1 SM container containing a PDU Session Release Command to UE 1 via AN5. The PDU Session Release Command may include a 5GSM Cause IE indicating revocation of S-NSSAI (or network slice) authorization (or the S-NSSAI is not available).
[0080] In step 504, UE 1 sends a NAS message containing a PDU Session Release Complete to AMF 2 to confirm the PDU Session Release command. The PDU Session Release Complete may contain a 5GSM Cause IE indicating the revocation of the S-NSSAI (or network slice) authorization (or the S-NSSAI is not available).
[0081] In step 505, AMF 2 performs (or calls) the Nsmf_PDUSession_UpdateSMContext service operation and forwards the N1 SM container (PDU session release complete) to SMF 3.
[0082] Second embodiment
[0083] The structure example of the cellular network of this embodiment can be Figure 1 The example shown is the same. This embodiment provides another example of the operation of AMF 2 where the authorization of a network slice is revoked.
[0084] Figure 6 is a flowchart showing an example of the operation of AMF 2. Step 601 and Figure 2The AMF 2 receives a message from the AUSF 4 indicating the revocation of the authorization of the specific S-NSSAI (or the network slice identified thereby) used by the UE. In step 602, the AMF 2 notifies the SMF 3 of the revocation of the authorization of the specific S-NSSAI (or the network slice identified thereby) used by the UE. Upon receiving the notification message from the AMF 2 (step 602), the SMF 3 decides to release the PDU session associated with the specific S-NSSAI.
[0085] If a PDU session for emergency calls (e.g., emergency services) associated with a specific S-NSSAI is established, AMF2 may be configured to exclude the release of the PDU session for emergency calls from the above-mentioned release process. In other words, in the above-mentioned release process, AMF 2 may initiate a release process to release all PDU sessions associated with the specific S-NSSAI except the PDU session for emergency calls. A PDU session for emergency calls associated with a specific S-NSSAI may mean a PDU session for emergency calls, in which a specific S-NSSAI is set in the AMF emergency configuration data stored by AMF 2, the S-NSSAI is notified from AMF 2 to SMF 3, and the S-NSSAI is used by SMF 3 when establishing a PDU session.
[0086] Figure 6 The operations shown enable AMF 2 to notify SMF 3 of the revocation of the authorization of the network slice, thereby assisting SMF 3 in releasing the PDU session associated with the network slice whose authorization was revoked.
[0087] Third embodiment
[0088] An example of the structure of the cellular network according to this embodiment can be Figure 1 The examples shown are the same. This embodiment provides an example of the operation of UE 1 in the case where the authorization of the network slice is revoked.
[0089] Figure 7is a flow chart illustrating an example of the operation of UE 1. In step 701, UE 1 detects (or identifies) the revocation of authorization of a specific S-NSSAI (or a network slice identified thereby) used by UE 1. For example, if UE 1 receives a UE configuration update command message from AMF 2 indicating that a specific S-NSSAI will be removed from allowed NSSAIs and will be included in rejected NSSAIs, UE 1 may detect (or identify) the revocation of authorization of the specific S-NSSAI. Additionally or alternatively, if UE 1 receives a NAS message from AMF 2 containing an information element indicating the revocation of authorization of a specific S-NSSAI, UE 1 may detect (or identify) the revocation of authorization of the specific S-NSSAI.
[0090] In step 702, in response to the revocation of authorization of a specific S-NSSAI (or the network slice identified thereby) used by UE 1, UE 1 requests the network to release (one or more) PDU sessions associated with the specific S-NSSAI. Specifically, UE 1 sends a NAS message to AMF 2 to request the release of (one or more) PDU sessions associated with the specific S-NSSAI. More specifically, the NAS-MM layer of UE 1 notifies the NAS-SM layer of UE 1 of the revocation of authorization for a specific S-NSSAI. In response to the notification from the lower layer (NAS-MM layer), the NAS-SM layer of UE 1 generates a PDU session release request for the PDU session associated with the specific S-NSSAI whose authorization is revoked. The NAS-SM layer of UE 1 passes the generated PDU session release request together with the PDU session ID to the NAS-MM layer. The NAS-MM layer of UE 1 sends a NAS message containing the PDU Session ID and the N1 SM container (PDU Session Release Request) to AMF 2. One or both of the NAS message and the PDU Session Release Request may contain a cause information element indicating the revocation of the S-NSSAI authorization.
[0091] Figure 7 The operations shown enable UE 1 to quickly release (one or more than one) PDU sessions associated with the network slice whose authorization is revoked.
[0092] Figure 8 An example of a slice-specific authorization revocation process initiated (or triggered) by AAA-S is shown. Steps 801-804 may be the same as the steps in the existing process. The existing slice-specific authorization revocation process initiated (or triggered) by AAA-S is described in Section 4.2.9.4 of Non-Patent Document 2 (or in Non-Patent Document 5).
[0093] In step 801, the AAA-S 9 sends a Revoke Authorization Request message (e.g., AAA protocol Revoke Authorization Request message) to the AUSF 4 to request the revocation of authorization for the network slice identified by a specific S-NSSAI (S-NSSAI #1 in this case). The message indicates S-NSSAI #1 and further indicates a General Public Subscription Identifier (GPSI) of the UE 1. The message may be sent directly from the AAA-S 9 to the AUSF 4, or may be sent to the AUSF 4 via an AAA proxy (AAA-P) not shown.
[0094] In step 803, AUSF 4 notifies AMF 2 of the occurrence of a revocation event of the authorization of S-NSSAI#1 used by UE 1 via the NF service provided by AUSF 4. Specifically, AUSF 4 obtains the AMF ID representing AMF 2 from UDM 8 by calling a procedure (e.g., Nudm_UECM_Get procedure) using the GPSI of UE 1 contained in the message received in step 801 (steps 802A and 802B). Then, AUSF 4 may send the following message (e.g., Nausf_NSSAA_Notify message) to AMF 2 represented by the AMF ID, which indicates that a revocation event of the authorization of S-NSSAI#1 used by UE 1 has occurred. The notification message from AUSF 4 to AMF 2 indicates S-NSSAI#1 and further indicates the GPSI of UE 1.
[0095] In step 804, AMF 2 signals UE 1 to update the UE NSSAI configuration (NSSAI storage) to remove the S-NSSAI #1 whose authorization is revoked from the currently allowed NSSAI. Specifically, AMF 2 sends a UE configuration update command message to UE 1, which indicates that S-NSSAI #1 will be removed from the allowed NSSAI and S-NSSAI #1 will be included in the rejected NSSAI. In response to the reception of the UE configuration update command message, UE 1 updates its own UE NSSAI configuration (NSSAI storage) stored in the (non-volatile) memory of UE 1. Specifically, UE 1 removes S-NSSAI #1 from the allowed NSSAI within the UE NSSAI configuration (NSSAI storage) and stores S-NSSAI #1 in the rejected NSSAI. The UE configuration update command message may include a reason IE indicating the revocation of the authorization of the S-NSSAI (or network slice). The Cause IE could be, for example, "S-NSSAI is unavailable due to network slice specific authorization and authentication failure or revocation."
[0096] In step 805, in response to detecting the revocation of the authorization of S-NSSAI#1, UE 1 requests the network to release the (one or more) PDU sessions associated with S-NSSAI#1. Specifically, UE 1 sends a NAS message to AMF 2, the NAS message including the (one or more) PDU session IDs of the (one or more) PDU sessions associated with S-NSSAI#1, and the N1 SM container (PDU session release request). As described above, one or both of the NAS message and the PDU session release request may include a reason IE indicating the revocation of the S-NSSAI authorization.
[0097] In step 806, AMF 2 calls the Nsmf_PDUSession_UpdateSMContext service operation and forwards the N1 SM container (PDU session release request) to SMF 3.
[0098] The following provides a structural example of UE 1, AMF 2 and SMF 3 according to the above embodiment. Fig. 9 is a block diagram showing a structural example of UE 1. A radio frequency (RF) transceiver 901 performs analog RF signal processing to communicate with an NG-RAN node. The RF transceiver 901 may include a plurality of transceivers. The analog RF signal processing performed by the RF transceiver 901 includes up-conversion, down-conversion, and amplification. The RF transceiver 901 is coupled to an antenna array 902 and a baseband processor 903. The RF transceiver 901 receives modulation symbol data (or OFDM symbol data) from the baseband processor 903, generates a transmit RF signal, and supplies the transmit RF signal to the antenna array 902. In addition, the RF transceiver 901 generates a baseband receive signal based on the receive RF signal received by the antenna array 902, and supplies the baseband receive signal to the baseband processor 903. The RF transceiver 901 may include an analog beamformer circuit for beamforming. The analog beamformer circuit includes, for example, a plurality of phase shifters and a plurality of power amplifiers.
[0099] The baseband processor 903 performs digital baseband signal processing (i.e., data plane processing) and control plane processing for radio communication. Digital baseband signal processing includes (a) data compression / decompression, (b) data segmentation / concatenation, (c) formation / decomposition of a transmission format (i.e., a transmission frame), (d) channel coding / decoding, (e) modulation (i.e., symbol mapping) / demodulation, and (f) generation of OFDM symbol data (i.e., baseband OFDM signal) using an inverse fast Fourier transform (IFFT). On the other hand, control plane processing includes communication management of layer 1 (e.g., transmit power control), layer 2 (e.g., radio resource management and hybrid automatic repeat request (HARQ) processing), and layer 3 (e.g., signal notification related to attachment, mobility, and call management).
[0100] The digital baseband signal processing performed by the baseband processor 903 may include, for example, signal processing of a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, and a physical (PHY) layer. In addition, the control plane processing performed by the baseband processor 903 may include processing of a non-access stratum (NAS) protocol, a radio resource control (RRC) protocol, and a MAC control element (CE).
[0101] The baseband processor 903 may perform multiple-input multiple-output (MIMO) encoding and precoding for beamforming.
[0102] The baseband processor 903 may include a modem processor (e.g., a digital signal processor (DSP)) for performing digital baseband signal processing and a protocol stack processor (e.g., a central processing unit (CPU) or a microprocessing unit (MPU)) for performing control plane processing. In this case, the protocol stack processor for performing control plane processing may be integrated with the application processor 904 described below.
[0103] The application processor 904 is also referred to as a CPU, an MPU, a microprocessor, or a processor core. The application processor 904 may include a plurality of processors (or processor cores). The application processor 904 loads a system software program (operating system (OS)) and various application programs (e.g., a call application, a WEB browser, a mail program, a camera operation application, and a music player application) from the memory 906 or from other memories (not shown), and executes these programs, thereby providing various functions of the UE 1.
[0104] In some implementations, such as Fig. 9 As shown by the dotted line (905) in FIG. 1 , the baseband processor 903 and the application processor 904 may be integrated on a single chip. In other words, the baseband processor 903 and the application processor 904 may be implemented on a single system on chip (SoC) device 905. The SoC device may be referred to as a large scale integration (LSI) or a chipset.
[0105] The memory 906 is a volatile memory, a non-volatile memory, or a combination thereof. The memory 906 may include a plurality of memory devices that are physically independent of each other. The volatile memory is, for example, a static random access memory (SRAM), a dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is, for example, a mask read-only memory (MROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a hard disk drive, or any combination thereof. The memory 906 may, for example, include an external memory device that can be accessed from the baseband processor 903, the application processor 904, and the SoC 905. The memory 906 may include an internal memory device integrated in the baseband processor 903, the application processor 904, or the SoC 905. In addition, the memory 906 may include a memory in a universal integrated circuit card (UICC).
[0106] The memory 906 may store one or more software modules (computer programs) 907, which include instructions and data for performing the processing performed by the UE 1 described in the above embodiments. In some implementations, the baseband processor 903 or the application processor 904 may load these software modules 907 from the memory 906 and execute the loaded software modules, thereby performing the processing of the UE 1 described in the above embodiments with reference to the drawings.
[0107] The control plane processing and operation performed by UE 1 described in the above embodiment can be implemented by elements other than the RF transceiver 901 and the antenna array 902, that is, by at least one of the baseband processor 903 and the application processor 904 and the memory 906 storing the software module 907.
[0108] Fig.10 An example of the structure of AMF 2 is shown. SMF 3 can also be Fig.10 Configuration shown. Reference Fig.10 , AMF 2 includes a network interface 1001, a processor 1002, and a memory 1003. The network interface 1001 is used to communicate with, for example, a RAN node and other network functions (NFs) or nodes in the 5GC. Other NFs or nodes in the 5GC include, for example, UDM, AUSF, SMF, and PCF. The network interface 1001 may include, for example, a network interface card compliant with the IEEE 802.3 series.
[0109] The processor 1002 may be, for example, a microprocessor, a microprocessing unit (MPU), or a central processing unit (CPU). The processor 1002 may include a plurality of processors.
[0110] The memory 1003 is composed of a volatile memory and a non-volatile memory. The volatile memory is, for example, a static random access memory (SRAM), a dynamic RAM (DRAM) or a combination thereof. The non-volatile memory is, for example, a mask read-only memory (MROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a hard disk drive or any combination thereof. The memory 1003 may include a storage device located at a location separate from the processor 1002. In this case, the processor 1002 can access the memory 1003 via the network interface 1001 or an I / O interface (not shown).
[0111] The memory 1003 may store one or more software modules (computer programs) 1004, which include instructions and data for performing the processing of the AMF 2 described in the above embodiments. In some implementations, the processor 1002 may be configured to load one or more software modules 1004 from the memory 1003 and execute the loaded software modules, thereby performing the processing of the AMF 2 described in the above embodiments.
[0112] As mentioned above Fig. 9 and Fig.10 As described, the processors included in UE 1, AMF 2 and SMF 3 according to the above embodiment execute one or more programs including instructions, which are used to make the computer execute the algorithm described with reference to the accompanying drawings. Any type of non-transitory computer-readable medium can be used to store these programs and provide them to the computer. Non-transitory computer-readable media include any type of tangible storage media. Examples of non-transitory computer-readable media include: magnetic storage media (such as floppy disks, tapes, hard disk drives, etc.), optical magnetic storage media (for example, magneto-optical disks), compact disk read-only memories (CD-ROMs), CD-Rs, CD-R / Ws, and semiconductor memories (such as mask ROMs, programmable ROMs (PROMs), erasable PROMs (EPROMs), flash ROMs, and random access memories (RAMs), etc.). Any type of temporary computer-readable medium can be used to provide these programs to the computer. Examples of temporary computer-readable media include electrical signals, optical signals, and electromagnetic waves. Temporary computer-readable media can provide programs to the computer via wired communication lines (for example, wires and optical fibers) or wireless communication lines.
[0113] The user equipment (UE) in the present invention is an entity connected to the network via a wireless interface. It should be noted that the radio terminal (UE) in the present invention is not limited to a dedicated communication device, and the radio terminal (UE) can be any device having the communication function explained herein as follows.
[0114] The terms "user equipment (UE)" (as the terminology used by 3GPP), "mobile station", "mobile terminal", "mobile device" and "radio terminal (wireless device)" are generally intended to be synonymous with each other. UE may include standalone mobile stations such as terminals, cellular phones, smart phones, tablets, cellular IoT (Internet of Things) terminals and IoT devices. It should be understood that the terms "UE" and "radio terminal" also cover devices that remain stationary for a long time.
[0115] UE can be, for example, equipment and / or energy-related machinery used for production or manufacturing (for example, equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal generators; nuclear power generators; batteries; nuclear systems and / or related equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil pressure equipment; pneumatic equipment; metal processing machinery; manipulators; robots and / or their application systems; tools; extrusion dies or die-casting dies; reels; conveying equipment; lifting equipment; material handling equipment; textile machinery; sewing machines; printing and / or related machinery; papermaking machinery; chemical machinery; mining and / or construction machinery and / or related equipment; agricultural, forestry and / or fishery machinery and / or tools; safety and / or environmental protection equipment; tractors; bearings; precision bearings; chains; gears; power transmission equipment; lubricators; valves; pipe fittings; and / or application systems of any of the aforementioned equipment or machinery, etc.).
[0116] A UE may be, for example, a transportation device (e.g., a transportation device such as: a rolling stock; a motor vehicle; a motorcycle; a bicycle; a train; a bus; a cart; a rickshaw; a ship and other watercraft; an airplane; a rocket; a satellite; a drone; a balloon, etc.).
[0117] UE may be, for example, information and communication equipment (eg, information and communication equipment such as: electronic computers and related equipment; communication and related equipment; electronic components, etc.).
[0118] UE can be, for example, refrigeration equipment, refrigeration application products and equipment, trade and / or service industry equipment, vending machines, automatic service machines, office machines or equipment, consumer electronics and electronic equipment (for example, consumer electronic devices such as: audio equipment; speakers; radios; video equipment; televisions; ovens; rice cookers; coffee machines; dishwashers; washing machines; dryers, fans, exhaust fans and related products, vacuum cleaners, etc.).
[0119] The UE may be, for example, an electrical application system or device (eg, an electrical application system or device such as: an x-ray system; a particle accelerator; a radioisotope device; an audio device; an electromagnetic application device; an electronic power application device, etc.).
[0120] The UE may be, for example, an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a measuring or sensing instrument (e.g., a measuring or sensing instrument such as: a smoke alarm; a human 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, a cutlery, a hand tool, or the like.
[0121] A UE may be, for example, a wirelessly equipped personal digital assistant or related equipment such as a wireless card or module designed to be attached to or inserted into another electronic device (eg, a personal computer, an electrical measuring machine, etc.).
[0122] UE can be a part of a device or system that provides the applications, services and solutions described below for the "Internet of Things (IoT)" using various wired and / or wireless communication technologies. IoT devices (or "things") can be equipped with appropriate electronic devices, software, sensors, network connections and / or equivalents, which enable these devices to collect data and exchange data with each other and with other communication devices. IoT devices may include automated devices that follow software instructions stored in internal memory. IoT devices can work without human supervision or interaction. IoT devices can also remain stationary and / or inactive for a long time. IoT devices can be implemented as part of (usually) fixed equipment. IoT devices can also be embedded in non-stationary equipment (e.g., vehicles), or attached to animals or people to be monitored / tracked. It should be understood that IoT technology can be implemented on any communication device that can be connected to a communication network for sending / receiving data, regardless of whether such communication devices are controlled by human input or by software instructions stored in memory. It should be understood that IoT devices are sometimes also referred to as machine type communication (MTC) devices, machine-to-machine (M2M) communication devices, or narrowband-IoT (NB-IoT) UEs.
[0123] It should be understood that a UE may support one or more than one IoT or MTC application.
[0124] Some examples of MTC applications are listed in 3GPP TS 22.368 V13.2.0 (2017-01-13) Appendix B (the contents of which are incorporated herein by reference). This list is not exhaustive and is intended to represent some examples of MTC applications. In this list, the service areas of MTC applications include security, tracking and tracing, payment, health, remote maintenance / control, metering, and consumer devices.
[0125] Examples of safety-related MTC applications include surveillance systems, fixed-line backup, control of physical access (eg, to a building), and car / driver safety.
[0126] Examples of MTC applications related to tracking and tracing include queue management, order management, connected car insurance: pay-as-you-go (PAYD), asset tracking, navigation, traffic information, road pricing, and road traffic optimization / diversion.
[0127] Examples of payment-related MTC applications include point of sale (POS), vending machines, and gaming machines.
[0128] Examples of health-related MTC applications include monitoring vital signs, supporting the elderly or disabled, Web-accessed remote medical points of care, and remote diagnostics.
[0129] Examples of MTC applications related to remote maintenance / control include sensors, lighting, pumps, valves, elevator control, vending machine control, and vehicle diagnostics.
[0130] Examples of metering-related MTC applications include electricity, gas, water, heating, grid control and industrial metering.
[0131] Examples of MTC applications related to consumer devices include digital photo frames, digital cameras, and electronic books (eBooks).
[0132] The applications, services and solutions may be mobile virtual network operator (MVNO) services / systems, emergency radio communication services / systems, private branch exchange (PBX) services / systems, PHS / digital cordless telecommunication services / systems, point of sale (POS) services / systems, advertising call services / systems, multimedia broadcast and multicast services (MBMS) services / systems, vehicle-to-everything (V2X) services / systems, train radio services / systems, location-related services / systems, disaster / emergency wireless communication services / systems, Internet of Things (IoT) services / systems, community services / systems, video streaming services / systems, femtocell application services / systems, voice over LTE (VoLTE) services / systems, radio tag services / systems, billing services / systems, audio on demand services / systems, roaming services / systems, activity monitoring services / systems, telecom operator / communication NW selection services / systems, functional restriction services / systems, proof of concept (PoC) services / systems, personal information management services / systems, display video services / systems, non-communication services / systems, self-organizing networks / delay tolerant networks (DTN) services / systems, and the like.
[0133] The above UE categories are only examples of application of the technical ideas and embodiments described in the present invention. The UE described in the present invention is not limited to these examples, and various modifications may be made thereto by those skilled in the art.
[0134] The above-described embodiments are merely examples of application of the technical ideas obtained by the inventors. These technical ideas are not limited to the above-described embodiments, and various modifications may be made thereto.
[0135] The whole or part of the above-mentioned embodiments may be described as, but not limited to, the following supplementary descriptions.
[0136] (Supplementary Note 1)
[0137] An access and mobility management function node, namely an AMF node, includes:
[0138] at least one memory; and
[0139] at least one processor coupled to the at least one memory and configured to:
[0140] In response to the revocation of the authorization of a first network slice identifier used by a user equipment, i.e., a UE, a release process is initiated to release a protocol data unit session, i.e., a PDU session, associated with the first network slice identifier.
[0141] (Supplementary Note 2)
[0142] An AMF node according to Supplementary Note 1, wherein the at least one processor is configured to notify a session management function, i.e., SMF, of the revocation of authorization of the first network slice identifier used by the UE during the release process.
[0143] (Supplementary Note 3)
[0144] The AMF node according to Supplementary Note 2, wherein the at least one processor is configured to send a message to the SMF during the release process to request the release of the session management context used by the PDU session, that is, the SM context,
[0145] The message includes an information element indicating a reason for the revocation of the authorization.
[0146] (Supplementary Note 4)
[0147] An AMF node according to any one of Supplementary Notes 1 to 3, wherein the at least one processor is configured to, in response to the revocation of the authorization, send a non-access stratum message (NAS message) to the UE instructing the UE to update the UE configuration,
[0148] wherein the NAS message indicates that the first network slice identifier will be removed from an allowed network slice identifier set and the first network slice identifier will be included in a rejected network slice identifier set, the allowed network slice identifier set indicating one or more network slice identifiers currently allowed for the UE, and
[0149] The NAS message also indicates a grace period before releasing the PDU session.
[0150] (Supplementary Note 5)
[0151] An AMF node according to Supplementary Note 4, wherein the at least one processor is configured to initiate the release process after the grace period expires.
[0152] (Supplementary Note 6)
[0153] An AMF node according to any one of Supplementary Notes 1 to 5, wherein the at least one processor is configured to initiate the release process in response to receiving a message indicating the revocation of the authorization from an authentication server function, i.e., AUSF.
[0154] (Supplementary Note 7)
[0155] An AMF node according to any one of Supplementary Notes 1 to 6, wherein the first network slice identifier is single network slice selection auxiliary information, namely S-NSSAI.
[0156] (Supplementary Note 8)
[0157] A method in an access and mobility management function node, i.e., an AMF node, the method comprising:
[0158] In response to the revocation of the authorization of a first network slice identifier used by a user equipment, i.e., a UE, a release process is initiated to release a protocol data unit session, i.e., a PDU session, associated with the first network slice identifier.
[0159] (Supplementary Note 9) A program for causing a computer to perform a method in an access and mobility management function node (AMF node), the method comprising:
[0160] In response to the revocation of the authorization of a first network slice identifier used by a user equipment, i.e., a UE, a release process is initiated to release a protocol data unit session, i.e., a PDU session, associated with the first network slice identifier.
[0161] (Supplementary Note 10)
[0162] A user equipment, namely, UE, includes:
[0163] at least one memory; and
[0164] at least one processor coupled to the at least one memory and configured to:
[0165] In response to the revocation of the authorization of the first network slice identifier used by the UE, request the network to release the PDU session associated with the first network slice identifier.
[0166] (Supplementary Note 11)
[0167] The UE according to Supplementary Note 10, wherein the at least one processor is configured to send a first non-access stratum message, i.e., a first NAS message, to an access and mobility management function, i.e., an AMF, to request the release of the PDU session,
[0168] The first NAS message includes an information element indicating a reason for revocation of the authorization.
[0169] (Supplementary Note 12)
[0170] The UE according to Supplementary Note 10 or 11, wherein:
[0171] The at least one processor is configured to receive a second non-access stratum message (a second NAS message) representing an update of the UE configuration from an access and mobility management function (an AMF),
[0172] The second NAS message indicates that the first network slice identifier is to be removed from an allowed set of network slice identifiers and that the first network slice identifier is to be included in a rejected set of network slice identifiers, the allowed set of network slice identifiers representing one or more network slice identifiers currently allowed for the UE, and
[0173] The at least one processor is configured to detect revocation of the authorization based on the second NAS message.
[0174] (Supplementary Note 13)
[0175] A method in a user equipment (UE), the method comprising:
[0176] In response to the revocation of the authorization of the first network slice identifier used by the UE, request the network to release the PDU session associated with the first network slice identifier.
[0177] (Supplementary Note 14)
[0178] A program for causing a computer to perform a method in a user equipment (UE), the method comprising:
[0179] In response to the revocation of the authorization of the first network slice identifier used by the UE, request the network to release the PDU session associated with the first network slice identifier.
[0180] This application is based upon and claims the benefit of priority from Japanese patent application No. 2019-237392, filed on December 26, 2019, the entire contents of which are incorporated herein by reference.
[0181] Reference numerals list
[0182] 1UE
[0183] 2AMF
[0184] 3SMF
[0185] 4AUSF
[0186] 5AN
[0187] 6UPF
[0188] 7DN
[0189] 8UDM
[0190] 9AAA-S
[0191] 903 Baseband Processor
[0192] 904 Application Processor
[0193] 906 Memory
[0194] 907 Module
[0195] 1002 Processor
[0196] 1003 Memory
[0197] 1004 Module
Claims
1. A first communication device, include: means for receiving a first message from a second communications device, the first message indicating revocation of authorization of a first single network slice selection assistance information, i.e., a first S-NSSAI, for use by a user equipment, i.e., a UE; A component for sending a second message to a third communication device after the first communication device receives the first message, wherein the second message requests to release a protocol data unit session, i.e., a PDU session; as well as means for sending a UE configuration update command message to the UE in case the authorization is revoked, wherein the second message includes a first reason information element indicating the revocation of the authorization, and The UE configuration update command message includes a second reason information element indicating the revocation of the authorization.
2. The first communication device according to claim 1, in, The UE configuration update command message includes a timer, where the timer represents a time period for controlling a protocol data unit session, ie, a PDU session, used by the first S-NSSAI.
3. A user equipment, namely UE, include: means for receiving a UE configuration update command message from an access and mobility management function, i.e., an AMF, when authorization of a first single network slice selection assistance information, i.e., a first S-NSSAI, used by the UE is revoked; as well as means for removing the first S-NSSAI from the allowed NSSAI in the UE in case the first S-NSSAI is included in rejected network slice selection assistance information, i.e. rejected NSSAI, The UE configuration update command message includes an information element indicating the reason why the authorization is revoked, and The UE configuration update command message indicates that the first S-NSSAI is included in the rejected NSSAI.
4. The UE according to claim 3, in, The UE configuration update command message includes a timer, where the timer represents a time period for controlling a protocol data unit session, ie, a PDU session, used by the first S-NSSAI.
5. A method of a first communication device, include: receiving a first message from a second communication device, the first message indicating revocation of authorization of a first single network slice selection assistance information (first S-NSSAI) used by a user equipment (UE); After the first communication device receives the first message, the second message is sent to the third communication device, where the second message requests to release a protocol data unit session, that is, a PDU session; as well as In case the authorization is revoked, sending a UE configuration update command message to the UE, wherein the second message includes a first reason information element indicating the revocation of the authorization, and The UE configuration update command message includes a second reason information element indicating the revocation of the authorization.
6. The method according to claim 5, in, The UE configuration update command message includes a timer, where the timer represents a time period for controlling a protocol data unit session, ie, a PDU session, used by the first S-NSSAI.
7. A method of a user equipment, namely a UE, include: receiving a UE configuration update command message from an access and mobility management function, i.e., an AMF, in a case where authorization of a first single network slice selection assistance information, i.e., a first S-NSSAI, used by the UE is revoked; as well as In case the first S-NSSAI is included in rejected network slice selection assistance information, i.e. rejected NSSAI, removing the first S-NSSAI from allowed NSSAI in the UE, The UE configuration update command message includes an information element indicating the reason why the authorization is revoked, and The UE configuration update command message indicates that the first S-NSSAI is included in the rejected NSSAI.
8. The method according to claim 7, in, The UE configuration update command message includes a timer, where the timer represents a time period for controlling a protocol data unit session, ie, a PDU session, used by the first S-NSSAI.
