Method, UE, and AMF node
The UE's registration procedures for area restrictions enable voice-centric UEs to access IMS voice services by selecting E-UTRAN cells in disallowed 5G-RAN areas, addressing service restrictions in 5GS.
Patent Information
- Application Number
- JP2024100398
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2018-08-09
- Filing Date
- 2024-06-21
- Publication Date
- 2025-09-02
- Estimated Expiration
- 2039-08-07
AI Technical Summary
Voice-centric UEs in 5G Systems (5GS) cannot establish Protocol Data Unit (PDU) sessions or user plane bearers in disallowed areas, preventing IMS voice calls, and current mechanisms restrict all application services in such areas, which is overly restrictive.
User Equipment (UE) performs registration procedures to receive area restriction information, determining whether to transmit PDU session-related signaling based on authorized or unauthorized areas, enabling selective service access in permitted areas.
Allows voice-centric UEs to maintain IMS voice services by selecting E-UTRAN cells in disallowed 5G-RAN areas and enabling selective service access, overcoming service restrictions in 5GS.
Smart Images

Figure 0007732544000002 
Figure 0007732544000003 
Figure 0007732544000004
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to a method for a UE in a permitted or unpermitted area. [Background technology]
[0002] User Equipment (UE) that supports the 5G System (5GS) and / or the Evolved Packet System (EPS) can be configured as a voice-centric UE or a data-centric UE. A voice-centric UE ensures that the UE can always receive voice services (e.g., IP Multimedia Subsystem (IMS) voice calls). A data-centric UE ensures that the UE can always receive data services. A voice-centric UE may perform a Radio Access Technology (RAT) selection or system selection procedure to receive voice services if the voice service is not available in the current system.
[0003] In 5GS, a UE is provided with either an allowed area or a disallowed area (but not both) during the registration procedure or UE configuration update procedure according to 3GPP TS 26.210.23. Each area is identified by an explicit tracking area identifier and / or other geographic information (e.g., longitude / latitude, postal code, etc.). The UE configures the allowed area information and disallowed area information based on the received allowed area information or disallowed area information. If the UE is in a Tracking Area (TA) present in the allowed area information, the UE can initiate Non Access Stratum (NAS) signaling (5G Mobility Management (5GMM) and 5G Session Management (5GSM)) for any kind of service. If the UE is in a TA present in the disallowed area information, the UE cannot initiate 5GSM or 5GMM signaling related to user plane establishment. [Prior art documents] [Non-patent literature]
[0004] [Non-Patent Document 1] 3GPP TS 23.501 V15.2.0 (2018-6) Summary of the Invention [Problem to be solved by the invention]
[0005] Problem statement 1: When a voice-centric UE enters a TA that is in a disallowed area, the UE cannot establish Protocol Data Unit (PDU) sessions or user plane bearers for any services, including IMS services. Therefore, an IMS voice call cannot be performed as long as the UE is in the disallowed area. A UE that supports S1 mode can receive IMS voice services in an EPS network, but the cell reselection criteria cause the UE to remain in a disallowed TA. Even if an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) cell that provides IMS voice services exists, a voice-centric UE may not be able to receive IMS voice services.
[0006] Problem statement 2: According to the current 5GS standard, if a UE receives a list of disallowed areas, it is not allowed to establish a PDU session or user plane for any type of service (eMBB (IMS voice call, Internet), mIoT, URLCC, V2X, etc.). In other words, all application services (IMS services, Internet, mIoT, URLCC, V2X) are blocked in the disallowed areas in the list. This is a very restrictive requirement for the UE. Therefore, the current mechanism does not provide a way to allow some services (e.g., V2X, IMS) and not allow some services (e.g., IoT) in a TA. [Means for solving the problem]
[0007] A method for User Equipment (UE) relating to a first aspect of the present disclosure includes performing a registration procedure with a 5G System (5GS), receiving at least one area restriction-related information indicating at least one of an authorized area and a unauthorized area, the area restriction-related information being at least one of an S-NSSAI (Single Network Slice Selection Assistance Information) unit, an APN (Access Point Name) unit, and an S-NSSAI and APN unit, determining whether to transmit PDU (Protocol Data Unit) session-related signaling based on the area information, and the UE transmitting the PDU session-related signaling when it enters a Tracking Area (TA) located in an authorized area or when it does not enter a TA located in a unauthorized area.
[0008] A User Equipment (UE) according to a second aspect of the present disclosure has a memory for storing instructions and at least one hardware processor for processing the instructions, wherein the instructions perform a registration procedure with a 5GS (5G System), receive at least one area restriction-related information indicating at least one of an authorized area and a unauthorized area, wherein the area restriction-related information is at least one of an S-NSSAI (Single Network Slice Selection Assistance Information) unit, an APN (Access Point Name) unit, and an S-NSSAI and APN unit, and determines whether to transmit PDU session-related signaling based on the area information, and the UE transmits the PDU session-related signaling when it enters a TA (Tracking Area) located in an authorized area or when it does not enter a TA located in a unauthorized area. [Brief explanation of the drawings]
[0009] [Figure 1] Figure 1 shows the fallback to EPS for receiving IMS services. [Figure 2] Figure 2 shows the UE disabling its 5G-RAN capabilities and selecting an E-UTRAN cell. [Figure 3] Figure 3 shows that IMS services are permitted in a non-permitted area. [Figure 4] FIG. 4 shows permitted area information and non-permitted area information for each service. [Figure 5] FIG. 5 shows a general block diagram of a UE. [Figure 6] FIG. 6 shows a general block diagram of an (R)AN. [Figure 7] Figure 7 shows a general block diagram of an AMF. DETAILED DESCRIPTION OF THE INVENTION
[0010] Abbreviation For the purposes of this document, 3GPP TR 21.905 V15.0.0 (2018-03) and the abbreviations listed below apply. Abbreviations defined in this document take precedence over definitions in 3GPP TR 21.905 V15.0.0 (2018-03) where the same abbreviation exists. 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 Function AN Access Node AS Access Stratum 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 Transmission EPS Evolved Packet System EPC Evolved Packet Core FQDN Fully Qualified Domain Name GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Centre GPSI Generic Public Subscription Identifier GUAMI Globally Unique AMF Identifier HR Home Routed (roaming) I-RNTI I-Radio Network Temporary Identifier LADN Local Area Data Network LBO Local Break Out (roaming) LMF Location Management Function LRF Location Retrieval Function MAC Medium Access Control MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MME Mobility Management Entity N3IWF Non-3GPP Inter Working Function NAI Network Access Identifier NAS Non-Access Stratum NEF Network Exposure Function NF Network Function NG-RAN Next Generation Radio Access Network NR New Radio 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 Policy PCF Policy Control Function PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PLMN Public land mobile network PPD Paging Policy Differentiation PPI Paging Policy Indicator 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 Reflective QoS Attribute RQI Reflective QoS Indication RRC Radio Resource Control SA NR Standalone New Radio SBA Service Based Architecture SBI Service Based Interface SD Slice Differentiator SDAP Service Data Adaptation Protocol SEAF Security Anchor Functionality SEPP Security 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 Concealed Identifier SUPI Subscription Permanent Identifier UDSF Unstructured Data Storage Function UL Uplink UL CL Uplink Classifier UPF User Plane Function UDR Unified Data Repository URSP UE Route Selection Policy SMS Short Message Service SMSF SMS Function MT Mobile Terminated
[0011] definition For the purposes of this document, 3GPP TR 21.905 V15.0.0 (2018-03) and the following terms and definitions apply. Terms defined in this document take precedence over the definitions in 3GPP TR 21.905 V15.0.0 (2018-03) where the same terms exist. In all the solutions below, the allowed area information and allowed area list are the allowed areas defined in 3GPP TS 23.501 V15.2.0 (2018-6) clauses 5.3.4.1.1 and 5.3.4.1.2. In all the solutions below, the prohibited area information and the prohibited area list are the prohibited areas defined in clauses 5.3.4.1.1 and 5.3.4.1.2 of 3GPP TS 23.501 V15.2.0 (2018-6). In all solutions below, 5G-RAN is 5G-AN as defined in 3GPP TS 23.501 V15.2.0 (2018-6).
[0012] First perspective (Solution 1 solves Problem Statement 1) E-UTRAN cell selection by voice-centric UE when entering a forbidden area
[0013] This solution discloses the technical aspects of the 5GS Mobility Restrictions.
[0014] A voice-centric UE that supports S1 and N1 modes successfully performs the registration procedure to 5GS. The UE is provided with the allowed area or non-allowed area information in the Registration Response message during the registration procedure or in the CONFIGURATION UPDATE COMMAND message during the Generic UE Configuration Update procedure. From the received allowed area or non-allowed area information, the UE derives the allowed area information and non-allowed area information as described in clause 5.3.4.1.1 of 3GPP TS 23.501 V15.2.0 (2018-6).
[0015] When a UE enters a disallowed area, it selects an E-UTRAN cell if it is available there and the UE is voice centric. The UE stores information about allowed and disallowed areas.
[0016] The UE performs an attach or tracking area procedure for the EPS. If IMS service is allowed for the UE in the EPS, the UE may stay in an E-UTRAN cell and perform MO and MT IMS voice calls. The UE does not select a 5GS disallowed area. If a 5G-RAN cell belongs to an allowed area, the UE selects the 5G-RAN cell during the cell reselection procedure.
[0017] If the UE configuration is changed to data centric or if the IMS service is disabled on the UE, the UE may select a cell belonging to a disallowed area after a cell selection or reselection procedure.
[0018] Detailed steps for Solution 1: Figure 1 shows the fallback to EPS for receiving IMS services.
[0019] In steps 1 to 4 of Figure 1, a voice-centric UE that supports S1 and N1 modes performs the registration procedure successfully to 5GS. The network may optionally perform authentication, security mode command, or identification procedures during the registration procedure. The UE is provided with allowed area or non-allowed area information in the Registration Response message during the registration procedure or in the CONFIGURATION UPDATE COMMAND message during the Generic UE Configuration Update procedure.
[0020] In step 5 of Figure 1, the UE derives the allowed area information and the disallowed area information described in clauses 5.3.4.1.1 and 5.3.4.1.2 of 3GPP TS 23.501 V15.2.0 (2018-6) from the received allowed area information or disallowed area information.
[0021] In step 6 of Figure 1, if the UE selects or reselects a 5G-RAN cell belonging to a disallowed area, the UE performs a cell selection procedure to select an available E-UTRAN cell at that location, i.e., if the UE is in a TA belonging to the disallowed list and the UE is a voice-centric device, the UE performs a cell selection procedure to select an available E-UTRAN cell at that location.
[0022] Alternatively, if the UE selects or reselects a 5G-RAN cell belonging to a disallowed area, the UE will remain in 5G-RAN unless there is IMS traffic that the UE needs to communicate with the IMS. If the UE needs to send IMS traffic, for example, an MO call over the IMS, the UE will perform a cell selection procedure and select an available E-UTRAN cell for its location.
[0023] The UE selects an available E-UTRAN cell at its location. The UE stores allowed area information and unallowed area information.
[0024] In step 7 of Figure 1, the UE successfully performs the attach procedure or the tracking are update procedure according to the procedure defined in clause 4.11.1.3.1 of 3GPP TS 23.502 V15.2.0 (2018-6).
[0025] The UE performs one of the following two steps:
[0026] In step 8a of Figure 1, if an IMS call is available in the EPS, the UE remains connected to the EPS and makes an MO or MT IMS call. While the UE is connected to the EPS, the UE does not select a 5G-RAN cell in an unauthorised area. The UE may select a 5G-RAN cell in an authorised area through cell reselection.
[0027] In step 8b of Figure 1, if an IMS call is not possible in the EPS, the UE remains connected to the EPS and uses the CSFB function to receive telephone service, or the UE selects a 5G-RAN cell, which may belong to a permitted or unpermitted area.
[0028] In the above scenario, when the UE state changes to EMM CONNECTED, the UE registered with the MME provides the eNB or gNB with allowed area information or disallowed area information. The eNB or gNB does not consider disallowed areas for handover to a gNB or ng-eNB connected to 5GC. Also, when the UE connects to EPS for the first time after powering on, the MME provides the eNB or gNB with allowed area information or disallowed area information when the UE state changes to EMM CONNECTED mode. In one example, the allowed list information or disallowed list information is sent in the handover restriction list IE in the INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST, or DOWNLINK NAS TRANSPORT message, as defined in 3GPP TS 36.413 V15.2.0 (2018-6). In another example, it may be sent in a new S1-AP message or in a new information element of an existing message (e.g., INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST, or DOWNLINK NAS TRANSPORT).
[0029] Second perspective (Solution 2 solves problem statement 1) 5G-RAN capability disabling and E-UTRAN cell selection by voice-centric UE
[0030] This solution discloses the technical aspects of the 5GS Mobility Restrictions.
[0031] A voice-centric UE that supports S1 and N1 modes successfully performs the registration procedure to 5GS. The UE is provided with the allowed area or disallowed area information in the Registration Response message during the registration procedure or in the CONFIGURATION UPDATE COMMAND message during the Generic UE Configuration Update procedure. From the received allowed area or disallowed area information, the UE derives the allowed area information and disallowed area information as described in clause 5.3.4.1.1 of 3GPP TS 23.501 V15.2.0 (2018-6).
[0032] When the UE enters a non-authorized area, it disables its N1 mode function and follows the procedure defined in clause 4.9 of 3GPP TS 24.501 V15.0.0 (2018-06). The UE stores the authorized area and non-authorized area information.
[0033] The UE performs an attach or tracking area procedure to the EPS. If IMS service is allowed for the UE in the EPS, the UE stays in the E-UTRAN cell and performs MO and MT IMS voice calls.
[0034] If the UE configuration is changed to data-centric, and IMS service is disabled on the UE, or IMS voice service is not possible in the E-UTRAN cell, the UE enables 5G-RAN service, and the UE may select a cell belonging to a disallowed area after a cell selection or reselection procedure.
[0035] Detailed steps for Solution 2: Figure 2 shows the UE disabling 5G-RAN functionality and selecting an E-UTRAN cell.
[0036] In steps 1 to 4 of Figure 2, a voice-centric UE that supports S1 and N1 modes performs the registration procedure successfully to 5GS. The network may optionally perform authentication, security mode command, or identification procedures during the registration procedure. The UE is provided with allowed area or non-allowed area information in the Registration Response message during the registration procedure or in the CONFIGURATION UPDATE COMMAND message during the Generic UE Configuration Update procedure.
[0037] In step 5 of Figure 2, the UE derives the allowed area information and the unallowed area information as described in section 5.3.4.1.1 of 3GPP TS 23.501 V15.2.0 (2018-6) from the received allowed area information or unallowed area information.
[0038] In step 6 of Figure 2, if the UE selects a 5G-RAN cell that belongs to a non-allowed area, the UE disables its N1 mode function and follows the procedure defined in clause 4.9 of 3GPP TS 24.501 V15.0.0 (2018-06). The UE selects an available E-UTRAN cell at that location. The UE stores the allowed area information and non-allowed area information.
[0039] Alternatively, if the UE selects or reselects a 5G-RAN cell that belongs to a disallowed area, the UE will stay in 5G-RAN unless there is IMS traffic that needs to be communicated with the IMS. If the UE needs to send IMS traffic, for example an MO call over IMS, the UE will disable its N1 mode capability and follow the procedure defined in clause 4.9 of 3GPP TS 24.501 V15.0.0 (2018-06).
[0040] In step 7 of Figure 2, the UE successfully performs the attach procedure or the tracking area update procedure according to the procedure defined in 4.11.1.3.1 of 3GPP TS 23.502 V15.2.0 (2018-6).
[0041] The UE performs one of the following two steps:
[0042] In step 8a of FIG. 2, if an IMS call is possible in the EPS, the UE remains connected to the EPS and makes an MO or MT IMS call.
[0043] In step 8b of Figure 2, if the IMS call is not possible in the EPS, the UE remains connected to the EPS or the UE enables 5G-RAN functionality and selects a 5G-RAN cell, which may belong to a permitted area or a disallowed area.
[0044] Third Perspective (Solution 3 solves Problem Statement 1.) Allowing IMS voice calls in restricted areas
[0045] This solution discloses the technical aspects of the 5GS Mobility Restrictions.
[0046] A UE that supports S1 and N1 modes performs the registration procedure successfully to 5GS. The network may optionally perform authentication, security mode command, or identification procedures during the registration procedure. The UE is provided with allowed area or non-allowed area information in the Registration Response message during the registration procedure or in the CONFIGURATION UPDATE COMMAND message during the Generic UE Configuration Update procedure.
[0047] The UE derives the allowed area information and the unallowed area information described in section 5.3.4.1.1 of 3GPP TS 23.501 V15.2.0 (2018-6) from the received allowed area information or unallowed area information.
[0048] The UE selects or reselects a 5G-RAN cell belonging to the unauthorised area and performs an IMS voice call in the unauthorised area, i.e., the UE establishes a PDU session related to the IMS voice service in the unauthorised area, and the UE establishes a user plane for the IMS voice call. If a PDU session for the IMS voice service has already been established, the UE establishes a user plane for the IMS voice call, and the IMS voice call is started. The UE does not initiate NAS signaling related to the establishment of a PDU session or user plane for a non-IMS voice call (Internet, IoT, etc.).
[0049] Detailed steps for Solution 3: Figure 3 shows that IMS services are permitted in a non-permitted area.
[0050] In steps 1 to 4 of Figure 3, a voice-centric UE that supports S1 and N1 modes performs the registration procedure successfully to 5GS. The network may optionally perform authentication, security mode command, or identification procedures during the registration procedure. The UE is provided with allowed area or non-allowed area information in the Registration Response message during the registration procedure or in the CONFIGURATION UPDATE COMMAND message during the Generic UE Configuration Update procedure.
[0051] In step 5 of Figure 3, the UE derives the allowed area information and the unallowed area information as described in section 5.3.4.1.1 of 3GPP TS 23.501 V15.2.0 (2018-6) from the received allowed area information or unallowed area information.
[0052] In step 6 of Figure 3, the UE selects or reselects a 5G-RAN cell belonging to the unauthorised area. Even if the UE is in the unauthorised area, if the UE is a voice-centric UE, it is permitted to make an IMS voice call in the unauthorised area, i.e., the UE establishes a PDU session related to the IMS voice service in the unauthorised area, and the UE establishes a user plane for the IMS voice call. If a PDU session for the IMS voice service has already been established, the UE establishes a user plane for the IMS voice call, and the IMS voice call is started.
[0053] If the 5GS recognizes that the UE has entered a disallowed area, the 5GS shall not release the N3 terminating UPF of the PDU session used for IMS services by the CN-initiated selective deactivation of an existing PDU session procedure in clause 4.3.7 of 3GPP TS 23.502 V15.2.0 (2018-6). This allows the UE to maintain its IMS registration so that the IMS can page the UE. When the AMF is requested by the SMF to page the UE for an IMS-MT call, the AMF pages the UE even if the AMF recognizes that the UE is in a disallowed area. This procedure may only apply to voice-centric UEs.
[0054] The UE does not initiate any NAS signaling related to the establishment of a PDU session or user plane for non-IMS voice calls (Internet, IoT, etc.).
[0055] In this solution, the UE can be a voice-centric UE, a data-centric UE, or a UE that is neither voice-centric nor data-centric.
[0056] In the above scenario, if an IMS call is established, the 5G-RAN performs a handover to the unauthorised area; otherwise, the 5G-RAN does not perform a handover to the unauthorised area.
[0057] Fourth embodiment (Solution 4 solves problem statement 2.) Configuration of service units for permitted or non-permitted areas
[0058] This solution discloses the technical aspects of the 5GS Mobility Restrictions.
[0059] Unified Data Management (UDM) has the following subscriber data for each UE: (a) Permitted area / non-permitted area information for each S-NSSAI. (b) Allowed area / non-allowed area information for each APN. (c) Permitted area / non-permitted area information for each S-NSSAI and APN.
[0060] The UE successfully performs the 5GS Registration procedure. The network (e.g., AMF) provides a list of allowed area information or non-allowed area information per S-NSSAI, per DNN, or per S-NSSAI and DNN in the Registration Accept message during the registration procedure or the CONFIGURATION UPDATE COMMAND message during the Generic UE Configuration Update procedure.
[0061] When the UE receives the allowed area information of S-NSSAI, it starts NAS signaling related to the PDU session of S-NSSAI only when the UE enters a TA included in the allowed area information. If the UE enters a TA included in the allowed area information, the UE does not start NAS signaling related to other PDU sessions of S-NSSAI.
[0062] Similarly, when a UE receives the allowed area information of a DNN, the UE initiates NAS signaling related to a PDU session of the DNN only when the UE enters a TA included in the allowed area information. When the UE enters a TA included in the allowed area information, the UE does not initiate any NAS signaling related to other PDU sessions of the DNN.
[0063] Similarly, when the UE receives the S-NSSAI and DNN allowed area information, it initiates NAS signaling related to the S-NSSAI and DNN PDU session only when the UE enters a TA that is included in the allowed area information. If the UE enters a TA that is included in the allowed area information, the UE does not initiate NAS signaling related to other S-NSSAI and DNN PDU sessions.
[0064] When the UE receives the disallowed area information of S-NSSAI, it does not start NAS signaling related to the PDU session of S-NSSAI only when the UE enters a TA included in the disallowed area information. When the UE enters a TA included in the disallowed area information, the UE starts NAS signaling related to other PDU sessions of S-NSSAI.
[0065] Similarly, when a UE receives the disallowed area information of a DNN, the UE does not initiate any NAS signaling related to the PDU session of the DNN only when the UE enters a TA that is included in the disallowed area information. When the UE enters a TA that is included in the disallowed area information, the UE initiates NAS signaling related to other PDU sessions of the DNN.
[0066] Similarly, if the UE receives the S-NSSAI and DNN disallowed area information, it will not initiate NAS signaling related to the S-NSSAI and DNN PDU session only when the UE enters a TA that is included in the disallowed area information. If the UE enters a TA that is included in the disallowed area information, the UE will initiate NAS signaling related to other S-NSSAI and DNN PDU sessions.
[0067] Detailed Steps for Solution 4 FIG. 4 shows that permitted area information and non-permitted area information are provided on a service basis.
[0068] In step 0 of Figure 4, the UDM has the following subscriber data for each UE: (1) Permitted area / non-permitted area information for each S-NSSAI. (2) Allowed area / non-allowed area information for each APN. (3) Permitted area / non-permitted area information for each S-NSSAI and APN.
[0069] In step 1 of Figure 4, the UE sends a Registration Request message to the AMF.
[0070] In steps 2-3 of FIG. 4, the network may optionally perform authentication, security mode command or identification procedures during the registration procedure.
[0071] In step 4 of Figure 4, the AMF obtains the UE's subscriber information, including area restriction related information.
[0072] In step 5 of Figure 4, the network (e.g., AMF) provides allowed area information or non-allowed list per S-NSSAI, per APN, or per S-NSSAI and APN in the Registration Accept message during the registration procedure or in the CONFIGURATION UPDATE COMMAND message during the Generic UE configuration update procedure.
[0073] In step 6a of Figure 4, when the UE receives the allowed area information of the S-NSSAI, it starts NAS signaling related to the PDU session of the S-NSSAI only when the UE enters a TA that exists in the allowed area information. If the UE enters a TA that exists in the allowed area information, the UE does not start any NAS signaling related to other PDU sessions of the S-NSSAI.
[0074] In step 6b of Figure 4, when the UE receives the allowed area information of the APN, it initiates NAS signaling related to the PDU session of the APN only when the UE enters a TA included in the allowed area information. If the UE enters a TA included in the allowed area information, the UE does not initiate any NAS signaling related to the PDU session of other APNs.
[0075] In step 6c of Figure 4, when the UE receives the allowed area information of the S-NSSAI and APN, it initiates NAS signaling related to the PDU session of the S-NSSAI and APN only when the UE enters the TA included in the allowed area information. If the UE enters the TA included in the allowed area information, the UE does not initiate any NAS signaling related to other PDU sessions of the S-NSSAI and APN.
[0076] In step 7a of Figure 4, if the UE receives the disallowed area information of S-NSSAI, it does not initiate NAS signaling related to the PDU session of S-NSSAI only when the UE enters a TA that is included in the disallowed area information. If the UE enters a TA that is included in the disallowed area information, the UE initiates NAS signaling related to other PDU sessions of S-NSSAI.
[0077] In step 7b of Figure 4, when the UE receives the disallowed area information of an APN, the UE does not initiate any NAS signaling related to the PDU session of the APN only when the UE enters a TA included in the disallowed area information. When the UE enters a TA included in the disallowed area information, the UE initiates NAS signaling related to the PDU session of another APN.
[0078] In step 7c of Figure 4, if the UE receives the disallowed area information of the S-NSSAI and APN, it does not initiate NAS signaling related to the PDU session of the S-NSSAI and APN only when the UE enters a TA that is included in the disallowed area information. If the UE enters a TA that is included in the disallowed area information, the UE initiates NAS signaling related to another PDU session of the S-NSSAI and APN.
[0079] In the above scenario, when the UE transitions to the 5GMM-CONNECTED state, the AMF sends the allowed area information or the disallowed area information to the 5G-RAN for each S-NSSAI. The 5G-RAN does not perform a handover to a disallowed area if a user plane bearer related to the S-NSSAI is established. In an emergency (e.g., an IMS emergency voice call) or for Multimedia Priority Service (MPS) or mission critical service (MCS), a handover to a disallowed area is permitted. Once the user plane for the S-NSSAI is established, the 5G-RAN hands over the UE to the allowed area of the S-NSSAI. For example, the allowed area information or the disallowed area information is sent in the Mobility Restriction List IE of the INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST, or DOWNLINK NAS TRANSPORT message defined in 3GPP TS 38.413 V15.0.0 (2018-06). In another example, the allowed area information or the disallowed area information is sent in a new information element of a new NG-AP message or an existing NG-AP message (e.g., INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST, DOWNLINK NAS TRANSPORT).
[0080] In the above scenario, when the UE transitions to the 5GMM-CONNECTED state, the AMF sends allowed area information or disallowed area information to the 5G-RAN on an APN-by-APN basis. If a user plane bearer associated with the APN is established, the 5G-RAN does not perform a handover to a disallowed area. Once the user plane for S-NSSAI is established, the 5G-RAN hands over the UE to the allowed area of the APN. In emergency situations (e.g., IMS emergency voice calls) or for Multimedia Priority Service (MPS) or mission critical service (MCS), handover to a disallowed area is permitted. In one example, the allowed area information or disallowed area information is sent in the Mobility Restriction List IE of the INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST, or DOWNLINK NAS TRANSPORT message, as defined in 3GPP TS 38.413 V15.0.0 (2018-06). In another example, the allowed area information or the disallowed area information is sent in a new information element of a new NG-AP message or an existing NG-AP message (e.g., INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST, DOWNLINK NAS TRANSPORT).
[0081] In the above scenario, when the UE transitions to the 5GMM-CONNECTED state, the AMF sends allowed area information or disallowed area information to the 5G-RAN for each S-NSSAI and APN. If a user plane bearer related to the S-NSSAI and APN is established, the 5G-RAN does not perform a handover to a disallowed area. Once the user plane for the S-NSSAI is established, the 5G-RAN hands over the UE to the allowed area of the APN. In an emergency (e.g., an IMS emergency voice call) or for Multimedia Priority Service (MPS) or mission critical service (MCS), a handover to a disallowed area is permitted. In one example, the allowed area information or disallowed area information is sent in the Mobility Restriction List IE of the INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST, or DOWNLINK NAS TRANSPORT message, as defined in 3GPP TS 38.413 V15.0.0 (2018-06). In another example, the allowed area information or the disallowed area information is sent in a new information element of a new NG-AP message or an existing NG-AP message (e.g., INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST, DOWNLINK NAS TRANSPORT).
[0082] In one example of the above scenario, the APN is a DNN.
[0083] Another embodiment The above-mentioned NAS message may be transmitted between the UE and the AMF via an NGRAN node (i.e., a gNB).
[0084] Furthermore, not all of the sequences, steps, or messages described above are necessarily required to identify one or more inventions.
[0085] As used herein, a User Equipment (UE) (or UE, including mobile station, mobile device, or wireless device) is an entity connected to a network via the air interface.
[0086] The UE in this specification is not limited to a dedicated communication device, but may be any device such as the following that has the communication function as the UE described in this specification.
[0087] The terms "User Equipment (UE)" (as used in 3GPP), "mobile station", "mobile terminal", "mobile device" and "wireless terminal" are generally intended to be synonymous with each other and may refer to standalone mobile stations such as terminals, mobile phones, smartphones, tablets, cellular IoT terminals, IoT devices, etc.
[0088] It will be understood that the terms "UE" and "wireless terminal" also encompass devices that are stationary for extended periods of time.
[0089] The UE may also be, for example, production equipment, manufacturing equipment, and / or energy-related machinery (by way of example only, boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal power generators, nuclear generators, batteries, nuclear systems, nuclear-related equipment, heavy electrical equipment, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machinery, manipulators, robots, robot application systems, tools, dies, rolls, conveying equipment, lifting equipment, cargo handling equipment, textile machinery, sewing machinery, printing presses, printing-related machinery, paper-converting machinery, chemical machinery, mining machinery, mining-related machinery, construction machinery, construction-related machinery, agricultural machinery and / or equipment, forestry machinery and / or equipment, fishing machinery and / or equipment, safety and / or environmental protection equipment, tractors, bearings, precision bearings, chains, cogwheels, power transmissions, lubrication systems, valves, pipe fittings, and / or application systems of any of the above-mentioned equipment or machinery).
[0090] The UE may also be, for example, a transportation device (for example, a vehicle, an automobile, a motorcycle, a bicycle, a train, a bus, a handcart, a rickshaw, a ship or other watercraft, an airplane, a rocket, a satellite, a drone, a balloon, etc.).
[0091] Furthermore, the UE may be, for example, an information communication device (for example, an electronic computer and related devices, a communication device and related devices, an electronic component, etc.).
[0092] The UE may also be, for example, a refrigerator, refrigerator-applied products and equipment, commercial and service equipment, vending machines, automatic service machines, office machines and equipment, consumer electrical and electronic machinery and appliances (for example, audio equipment, speakers, radios, video equipment, televisions, oven ranges, rice cookers, coffee makers, dishwashers, washing machines, dryers, fans, ventilation fans and related products, vacuum cleaners, etc.).
[0093] The UE may also be, for example, an electronic application system or electronic application device (for example, an X-ray device, a particle accelerator device, a radioactive material application device, a sonic application device, an electromagnetic application device, a power application device, etc.).
[0094] The UE may also be, for example, a light bulb, lighting, a weighing machine, analytical equipment, testing and measuring equipment (for example, a smoke alarm, a occupancy alarm sensor, a motion sensor, a radio tag, etc.), a watch, a laboratory machine, an optical machine, medical equipment and / or a medical system, a weapon, a sharp tool, or a hand tool.
[0095] The UE may also be, for example, a personal digital assistant or device with wireless communication capabilities (for example, an electronic device (e.g., a personal computer, electronic measuring instrument, etc.) configured to accommodate or insert a wireless card, wireless module, etc.).
[0096] The UE may also be, or be part of, a device that provides the following applications, services, and solutions in the Internet of Things (IoT) using wired and wireless communication technologies:
[0097] IoT devices (or things) are equipped with appropriate electronics, software, sensors, network connectivity, etc. that enable them to collect and exchange data with each other and with other communicating devices. IoT devices may also be automated devices that follow software instructions stored in their internal memory. IoT devices may also operate without the need for human supervision or attention. IoT devices may also be installed and / or remain inactive for extended periods of time. IoT devices may also be implemented as part of a stationary device. IoT devices may also be embedded in non-stationary devices (e.g., vehicles) or attached to animals or people being monitored / tracked.
[0098] It will be appreciated that IoT technology can be implemented on any communication device that can be connected to a communication network to send and receive data, regardless of whether it is controlled by human input or software instructions stored in memory.
[0099] It will be understood that an IoT device may also be referred to as a Machine Type Communication (MTC) device, a Machine to Machine (M2M) communication device, or a Narrow Band-IoT (NB-IoT) UE. It will also be understood that a UE may support one or more IoT or MTC applications. Some examples of MTC applications are listed in the following table (Source: 3GPP TS 22.368 V14.0.1 (2017-08) Annex B, the contents of which are incorporated herein by reference). This list is not exhaustive but rather provides examples of MTC applications.
[0100] [Table 1]
[0101] Examples of applications, services, and solutions include MVNO (Mobile Virtual Network Operator) services / systems, disaster prevention radio services / systems, private branch exchange (PBX) services / systems, PHS / digital cordless telephone services / systems, POS (Point of sale) systems, advertising services / systems, multicast (MBMS (Multimedia Broadcast and Multicast Service)) services / systems, V2X (Vehicle to Everything: vehicle-to-vehicle communication and road-to-vehicle / pedestrian-to-vehicle communication) services / systems, in-train mobile radio services / systems, location information related services / systems, disaster / emergency radio communication services / systems, IoT (Internet of Things) services / systems, community services / systems, video distribution services / systems, Femtocell application services / systems, and VoLTE (Voice over LTE) services / systems. It may also be a LTE (LTE) service / system, wireless TAG service / system, billing service / system, radio on-demand service / system, roaming service / system, user behavior monitoring service / system, communication carrier / communication network selection service / system, function restriction service / system, PoC (Proof of Concept) service / system, personal information management service / system for terminals, display and video service / system for terminals, non-communication service / system for terminals, ad hoc network / DTN (Delay Tolerant Networking) service / system, etc. The above-mentioned UE categories are merely examples of application of the technical concepts and aspects described in this specification, and are not limited to these examples, and various modifications may be made by those skilled in the art.
[0102] Figure 5 is a block diagram illustrating the main components of a UE (500). As shown, the UE includes transceiver circuitry (504) operable to transmit signals to and receive signals from connected nodes via one or more antennas (505). Although not necessarily shown in Figure 5, the UE naturally has all the usual functionality of a conventional mobile device (e.g., a user interface), which may be provided by any one or any combination of hardware, software, and firmware, as appropriate. Software may be pre-installed in memory and / or downloaded, for example, over a telecommunications network or from a removable data storage device (RMD).
[0103] The controller (501) controls the operation of the UE in accordance with software stored in the memory (502). For example, the controller may be realized by a central processing unit (CPU). The software includes, among other things, an operating system and a communications control module (506) having at least a transceiver control module (507). The communications control module (506) (using its transceiver control submodule) is responsible for processing (generating / sending / receiving) signaling and uplink / downlink data packets between the UE 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 messages related to periodic location updates (e.g., tracking area updates, paging area update information, location area updates), etc.
[0104] FIG. 6 is a block diagram illustrating the main components of an exemplary (R)AN node (600), e.g., a base station (eNB in LTE, gNB in 5G). As shown, the (R)AN node (600) includes transceiver circuitry (607) operable to transmit signals to and receive signals from connected UEs via one or more antennas (608), and to transmit signals to and receive signals from other network nodes (directly or indirectly) via a network interface. A controller (601) controls operation of the (R)AN node in accordance with software stored in memory (602). For example, the controller may be implemented by a central processing unit (CPU). The software may be pre-installed in the memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system and a communications control module having at least a transceiver control module (604).
[0105] The communication control module (603) (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signaling (e.g., directly or indirectly) between the (R)AN node and other nodes, e.g., UEs, MMEs, AMFs, etc. Signaling may include, for example, appropriately formatted signaling messages related to radio connectivity and location procedures (for a particular UE), in particular connection establishment and maintenance (e.g., RRC connection establishment and other RRC messages), messages related to periodic location updates (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), etc. Such signaling may also include, for example, broadcast information (e.g., master information and system information), if sent.
[0106] When implemented, the controller is also configured (by software or hardware) to handle related tasks such as UE mobility estimation and / or movement trajectory estimation.
[0107] FIG. 7 is a block diagram illustrating the main components of the AMF (700). The AMF (700) is included in the 5GC. As shown, the AMF (700) includes a transceiver circuit (707) operable to transmit signals to and receive signals from other nodes (including UEs) via a network interface. The controller (701) controls the operation of the AMF (700) in accordance with software stored in memory. For example, the controller may be implemented by a central processing unit (CPU). The software may be pre-installed in the memory and / or downloaded, for example, via a telecommunications network or from a removable data storage device (RMD). The software includes, among other things, an operating system and a communications control module (703) having at least a transceiver control module (704).
[0108] The Communications Control module (using its Transceiver Control sub-module) is responsible for handling (generating / sending / receiving) signaling (directly or indirectly) between the AMF and other nodes, e.g., UEs, base stations / (R)AN nodes (e.g., "gNBs" or "eNBs"), etc. Such signaling may include, e.g., appropriately formatted signaling messages related to the procedures described herein, e.g., NG AP messages (i.e., messages over the N2 reference point) for conveying NAS messages to and from the UE, etc.
[0109] As will be appreciated by those skilled in the art, the present disclosure may be embodied as a method and system, and thus may take the form of an entirely hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects.
[0110] It will be understood that each block of the block diagrams can be implemented by computer program instructions. These computer program instructions are provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to create a machine, whereby the instructions, executed by the processor of the computer or other programmable data processing apparatus, produce means for implementing the functions / acts identified in the flowcharts and / or one or more blocks of the block diagrams. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a computing device, e.g., multiple microprocessors, one or more microprocessors, or any other such combination of configurations.
[0111] The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.
[0112] The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of the present disclosure. Thus, the present disclosure 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.
[0113] This application claims the benefit of priority to Indian Patent Application No. 201811029944, filed on August 9, 2018, the disclosure of which is incorporated herein by reference in its entirety. [Explanation of symbols]
[0114] 500 UE 501 Controller 502 memory 503 User Interface 504 Transceiver Circuit 505 Antenna 506 Communication Control Module 507 Transceiver Control Module 508 Operating System 600 (R) AN node 601 Controller 602 memory 603 communication control module 604 Transceiver Control Module 605 Operating System 606 Network Interface 607 Transceiver Circuit 608 Antenna 700 AMF 701 Controller 702 memory 703 communication control module 704 Transceiver Control Module 705 Operating System 706 Network Interface 707 Transceiver Circuit
Claims
1. 1. A method for User Equipment (UE), comprising: Sends a registration request message to the Access and Mobility Management Function (AMF) node, receiving a registration accept message from the AMF node during the registration procedure, the registration accept message including area information per Data Network Name (DNN) and Single Network Slice Selection Assistance Information (S-NSSAI); A Protocol Data Unit (PDU) Session for the DNN and the S-NSSAI is started only when the UE enters an area for each of the DNN and the S-NSSAI. method.
2. The method of claim 1 , wherein the AMF node receives the area information from a Unified Data Management (UDM) node.
3. 1. A method for an Access and Mobility Management Function (AMF) node, comprising: receiving a registration request message from User Equipment (UE); sending a registration accept message to the UE during a registration procedure, the registration accept message including a Data Network Name (DNN) and area information per Single Network Slice Selection Assistance Information (S-NSSAI); Controlling to start a Protocol Data UNIT (PDU) Session of the DNN and the S-NSSAI only when the UE enters an area for each of the DNN and the S-NSSAI; method.
4. The method of claim 3 , wherein the AMF node receives the area information from a Unified Data Management (UDM) node.
5. A User Equipment (UE), sending means for sending a registration request message to an Access and Mobility Management Function (AMF) node; A receiving means for receiving a registration accept message from the AMF node during a registration procedure, the registration accept message including a Data Network Name (DNN) and area information per Single Network Slice Selection Assistance Information (S-NSSAI); A control means for starting a Protocol Data Unit (PDU) session for the DNN and the S-NSSAI only when the UE enters an area for each of the DNN and the S-NSSAI; A UE having:
6. an Access and Mobility Management Function (AMF) node, receiving means for receiving a registration request message from a User Equipment (UE); a sending means for sending, to the UE, a registration accept message including a Data Network Name (DNN) and area information per Single Network Slice Selection Assistance Information (S-NSSAI) during a registration procedure; A control means for controlling the UE to start a Protocol Data Unit (PDU) Session for the DNN and the S-NSSAI only when the UE enters an area for each of the DNN and the S-NSSAI; An AMF node having:
Citation Information
Patent Citations
Method and system for regional data network configuration in wireless communication network
WO2018038490A1
Method and apparatus for selecting an access and mobility management function in a mobile communication system
WO2018128499A1