USER EQUIPMENT AND COMMUNICATION METHOD PERFORMED BY USER EQUIPMENT

Abstract

The present invention relates to a communication procedure for transmitting and receiving data, suitable for network slicing and a decor function. One or more of a plurality of network slices are included in a core network managed by the network operator, wherein the network slice is formed by one or more of a plurality of network functions, and based on registration information from a terminal device or a request from the terminal device, the terminal device performs processing to connect to one or more of the plurality of network slices corresponding to a service or application. Furthermore, based on an authentication result from the network, the terminal device performs processing to connect to an additional network slice.

Description

Descriptive Report of the Invention Patent for USER EQUIPMENT AND COMMUNICATION METHOD PERFORMED BY USER EQUIPMENT. TECHNICAL FIELD

[001] The present invention relates to a terminal device, a base station device, a Mobility Management Entity (MME), and a communication control method. BACKGROUND OF THE TECHNIQUE

[002] The Third Generation Partnership Project (3GPP - 3rd The Generation Partnership Project, which performs activities to standardize recent mobile communication systems, discusses System Architecture Enhancement (SAE), which is the system architecture of Long Term Evolution (LTE). 3GPP is in the process of creating specifications for the Evolved Packet System (EPS) as a communication system that implements an all-IP architecture. It should be noted that a core network that configures EPS is called an Evolved Packet Core (EPC).

[003] In addition, 3GPP addresses the recent study on new services and markets technology (SMARTER - New Services and Markets Technology) and an architecture for the next generation system (NextGen - Next Generation System) as a discussion of a next-generation communication technology for various types of terminals.

[004] SMARTER is in the process of extracting requirements based on diversifying service use cases, and NextGen extracts technical problems for connecting various types of terminals to a cellular network and creates solution specifications. Petition 870240027939, dated 01 / 04 / 2024, page 6 / 137 2 / 121

[005] For example, in SMARTER and NextGen, since each of the diversification services or terminals requires different communication performance, Network Slicing, in which a single main PLMN network is logically divided into multiple slices, was discussed. LIST OF REFERENCES Non-patent literature

[006] NPL 1: 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Feasibility Study on New Services and Markets Technology Enablers; Stage 1 (Disclosure 14)

[007] NPL 2: 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Disclosure 14) SUMMARY OF THE INVENTION Technical Problem

[008] In 3GPP, as part of SMARTER and NextGen, network slicing was discussed in which a core network is logically sliced.

[009] However, a specific definition of network slice and a procedure for a method of connecting to a core network divided by the network slice are not yet clear.

[0010] The present invention was developed in view of the situations described above, and an objective of the invention is to provide a technique, or similar, for controlling communication for data transmission and / or reception suitable for network slicing. Solution to the problem

[0011] To solve the problems described above, a method for controlling communication of a terminal device according to the present invention includes the steps of: initiating a procedure of Petition 870240027939, dated 01 / 04 / 2024, page 7 / 137 3 / 121 connection by transmitting a connection request message to a base station device; receiving a connection request message including at least one first identification information and / or one second identification information and / or one third identification information from a Mobility Management Entity (MME) in the connection procedure, wherein the first identification information is information configured to indicate a network slice type for which a terminal device connection is approved, the second identification information is information configured to identify a network slice for which a terminal device connection is approved, and the third identification information is information configured to indicate an MME isolation level; and connecting to a network slice based on the completion of the connection procedure.

[0012] A method for controlling the communication of a base station device according to the present invention includes the steps of: receiving a connection request message including at least one first identification information and / or one second identification information and one third identification information, wherein the first identification information is information configured to indicate a type of network slice that a terminal device requests a connection to, the second identification information is information configured to identify a network slice that the terminal device requests a connection to, and the third identification information is information configured to indicate an isolation level that the terminal device requests an MME to be connected to, from the terminal device; selecting a network slice based on the first identification information and / or the second identification information; selecting a network slice entity of Petition 870240027939, dated 01 / 04 / 2024, page 8 / 137 4 / 121 Mobility Management (MME) included in the network slice based on the third identification information; and transmit the connection request message to the MME.

[0013] A method for controlling communication of a mobility management entity (MME) according to the present invention includes the step of: transmitting a connection request message including at least one first identification information and / or one second identification information and / or one third identification information, wherein the first identification information is information configured to indicate a type of network slice for which a connection from the terminal device is approved, the second identification information is information configured to identify a network slice for which a connection from the terminal device is approved, and the third identification information is information configured to indicate an isolation level of the MME, for the terminal device.

[0014] A terminal device according to the present invention includes: a controller configured to initiate a connection procedure by transmitting a connection request message to a base station device; and a transmission and / or reception unit configured to receive a connection request message including at least one first identification information and / or one second identification information and / or one third identification information from a mobility management entity (MME) in the connection procedure, wherein the first identification information is information configured to indicate a type of network slice for which a connection from the terminal device is approved, the second identification information is information configured to identify a network slice for which a Petition 870240027939, dated 01 / 04 / 2024, page 9 / 137 5 / 121 The terminal device connection is approved, the third identification information is configured to indicate an MME isolation level, and the controller is configured to connect to a network slice based on the completion of the connection procedure.

[0015] A base station device according to the present invention includes: a transmitting and / or receiving unit configured to receive a connection request message including at least one first identification information and / or a second identification information and a third identification information, wherein the first identification information is information configured to indicate a type of network slice that a terminal device requests a connection to, the second identification information is information configured to identify a network slice that the terminal device requests a connection to, and the third identification information is information configured to indicate an isolation level that the terminal device requests an MME to be connected to, from the terminal device;and a controller configured to select a network slice based on the first identification information and / or the second identification information, wherein the controller selects a mobility management entity (MME) included in the network slice based on the third identification information; and the transmission and / or reception unit transmits the connection request message to the MME.

[0016] A mobility management entity (MME) according to the present invention includes: a transmission and / or reception unit configured to transmit a connection request message including at least one first identification information and / or a second identification information and / or a third identification information, wherein the first Petition 870240027939, dated 01 / 04 / 2024, page 10 / 137 6 / 121 identification information is information configured to indicate a network slice type for which a terminal device connection is approved, the second identification information is information configured to identify a network slice for which a terminal device connection is approved, and the third identification information is information configured to indicate an MME isolation level for the terminal device. Advantageous effects of the invention

[0017] According to the present invention, a terminal can connect to a network slice based on the terminal's performance, an application or a service, and is able to communicate. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a diagram illustrating an overview of a mobile communication system.

[0019] Figures 2A and 2B are diagrams illustrating an example of a mobile IP communication network configuration, and similar configurations.

[0020] Figure 3 is a diagram illustrating a UE device configuration.

[0021] Figures 4A and 4B are diagrams illustrating a UE storage unit.

[0022] Figures 5A and 5B are diagrams illustrating a device configuration of an eNB.

[0023] Figures 6A to 6D are diagrams illustrating a device configuration of an MME.

[0024] Figure 7 is a diagram illustrating a notification procedure for a type of network slice.

[0025] Figure 8 is a diagram illustrating a connection procedure.

[0026] Figure 9 is a diagram illustrating a first Petition 870240027939, dated 01 / 04 / 2024, page 11 / 137 7 / 121 Tracking Area Update (TAU) procedure.

[0027] Figure 10 is a diagram illustrating a second TAU procedure.

[0028] Figure 11 is a diagram illustrating a trigger of TAU.

[0029] Figure 12 is a diagram illustrating a connection procedure.

[0030] Figure 13 is a diagram illustrating a first PDN (Packet Data Network) connectivity procedure.

[0031] Figure 14 is a diagram illustrating a second PDN connectivity procedure. DESCRIPTION OF THE MODALITIES

[0032] From this point onward in this document, a preferred embodiment for carrying out the present invention will be described with reference to the drawings. It should be noted that, as an example, the present embodiment describes a type of mobile communication system to which the present invention applies. 1. First option 1.1. System Overview

[0033] Figure 1 is a diagram illustrating an overview of a mobile communication system according to the present embodiment. A mobile communication system can be configured to include one or more network slices. For example, as illustrated in the drawing, mobile communication system 1 can be formed by a network slice_A 101, a network slice_B 102, a network slice_C 103, an evolved node B eNB_A of base station 45 and a user equipment UE_A of terminal device 10.

[0034] Additionally, in the mobile communication system, one or Petition 870240027939, dated 01 / 04 / 2024, page 12 / 137 8 / 121 more network functions (NF - Network Function) can be configured. Here, the NF is a function unit in a network, the hardware can be independent for each NF, and multiple software-implemented NFs can configure a single hardware component.

[0035] Here, the network slice can be configured to include one or more network functions (NFs). Furthermore, the configuration NFs can be different for the respective network slices.

[0036] Alternatively, a network slice is a network that is customized so that an operator can provide an optimized solution for different business market scenarios. In other words, a network slice is a network obtained by dividing an operator's network into multiple slices to address a functional request that is different for each scenario or service. In other words, a network slice can be a network obtained through slicing functions included in a public terrestrial mobile network (PLMN) based on the service and / or terminal characteristics and performance. The network slice can be linked to an application ID and / or service performance. In other words, the operator can configure one or more network slices.

[0037] Additionally, a network slice can be a network obtained by dividing a core network_A 90 into several slices, and in other words, the core network_A 90 can be formed by network slice_A 101, network slice_B 102 and network slice_C 103.

[0038] Here, requests made by the scenarios of different business markets and functional requests that differ for the respective scenarios are requests within a range of functionality, performance, and independence. For example, a pricing request, a policy control request, a move request, or similar, are included. Alternatively, Petition 870240027939, dated 01 / 04 / 2024, page 13 / 137 9 / 121 may include a request for a communication rate, reliability of data transmission and / or reception, or similar.

[0039] For example, network slice_A 101 could be a network slice for an IoT (Internet of Things) device that has a secondary function as a sensor, and network slice_B 102 could be a network slice for communication of a vehicle-related service. However, network slices are not limited to these types and can be configured based on requested requirements.

[0040] It should be noted that the network slice can be managed as a network slice instance. In other words, the information to identify the network slice can be an identifying information on the network slice instance, such as a network slice instance ID.

[0041] In addition, a network slice type can be allocated to each of these network slices. Specifically, a network slice type_A can be allocated to network slice_A 101, a network slice type_B can be allocated to network slice_B 102, and a network slice type_C can be allocated to network slice_C 103.

[0042] Here, the network slice type can be an identifying piece of information indicating the network slice's performance. Specifically, the network slice type_A can be an identifying piece of information indicating that the network slice is intended for an IoT device that has a secondary function as a sensor.

[0043] The network slice type can be common among operators. Alternatively, the network slice type can be independent for each operator. For example, network slice types can be used in such a way that some are common among operators and some are independent for each operator.

[0044] It should be noted that the operator can configure one or Petition 870240027939, dated 01 / 04 / 2024, page 14 / 137 10 / 121 more network slices for each of the network slice types. In other words, for example, network slices classified as network slice type_A could be network slice_A and network slice_B, and the network slice classified as network slice type_B could be network slice_C.

[0045] Alternatively, the operator can configure one or more network slice types for each of the network slices. In other words, for example, network slice_A can be included in network slice type_A and network slice type_B, and network slice_B can only be included in network slice type_C.

[0046] Additionally, as illustrated in the drawing, a MME_A 104 and an MME_D 105 mobility management device are configured on network slice_A 101. Several other MMEs can be included on network slice_A 101.

[0047] On the other hand, in network slice_B 102, the following are configured MME_D 105 and an MME_B 106. Additionally, in network slice_C 103, an MME_C 107 is configured.

[0048] In other words, MME_A 104 supports only one terminal device (UE) connected to network slice_A 101, and MME_D 105 can support the terminal device connected to network slice_A 101 and a terminal device connected to network slice_B 102. In other words, MME_D 105 is shared by network slice_A 101 and network slice_B 102.

[0049] In other words, in network slice_A 101, MME_A 104 which is independent in network slice_A 101 and MME_D 105 which is not independent in network slice_A are included and configured.

[0050] It should be noted that in the diagram, although only MMEs are illustrated in their respective network slices, functional units such as a gateway (link port or bridge) or similar are illustrated in Figures 2A and 2B, such as a Service Gateway (SGW). Petition 870240027939, dated 01 / 04 / 2024, p. 15 / 137 11 / 121 Gateway), a Packet Data Network Gateway (PGW), or similar, may be included.

[0051] In other words, in network slice_A 101, an SGW_A that is independent of other network slices and an SGW_B that is not independent of other network slices can be configured, and, in the same way, a PGW_A that is independent for each of the network slices and a PGW_B that is not independent of each of the network slices can be configured.

[0052] Additionally, all function units such as MME, SGW, PGW and similar included in the core network can be network function (NF).

[0053] The eNB_A 45 is an LTE base station device connected to the sliced ​​core network. As illustrated in the drawing, the eNB_A 45 can be the LTE base station device that connects to multiple network slices.

[0054] Additionally, UE_A 10 can be any wirelessly connectable terminal device, and can be a user equipment (UE), a mobile equipment (ME), or a mobile station (MS).

[0055] Additionally, the UE_A 10 can be a radio communication terminal to provide communication regarding a vehicle or a vehicle connected to a vehicle, it can be a measuring device, such as a sensor, a meter or a radio communication terminal connected to the device, or it can be a smartphone.

[0056] In the drawing, although only UE_A 10 is included in mobile communication system 1, multiple terminal devices can be included in mobile communication system 1.

[0057] Additionally, it is sufficient that the MME be a functional unit that handles control information with the UE, whereby Petition 870240027939, dated 01 / 04 / 2024, p. 16 / 137 12 / 121 MME can be used as the network function.

[0058] Below, Figures 2A and 2B illustrate an example of a core_A 90 network configuration. Figures 2A and 2B are only illustrations, and in the core_A 90 network each of the function units is configured at least one by one. In other words, in the core_A 90 network in Figures 2A and 2B, although only MME_A 104 is configured as the MME, MME_B 106, MME_C 107 and MME_D 105 in Figure 1 can still be configured.

[0059] The core network_A 90 in Figure 2A consists of a Home Subscriber Server (HSS) HSS_A 50, an Authentication, Authorization, Accounting (AAA) AAA_A 55, a Policy and Charging Rules Function (PCRF) PCRF_A 60, a PGW_A 30, an Enhanced Packet Data Gateway (ePDG) ePDG_A 65, an SGW_A 35, the MME_A 104 and a Serving GPRS Support Node (SGSN) SGSN_A 42.

[0060] It should be noted that one or more function units configured in the core_A 90 network can be configured as a single function unit. Alternatively, each of the function units can be divided into multiple function units for each requested function. Each of these function units can be a network function (NF).

[0061] In addition, the core network_A 90 can connect to multiple radio access networks (an LTE access network (AN) AN_A 80, a WLAN access network ANb 75, a WLAN access network ANa 70, a universal terrestrial radio access network UTRAN_A 20 and a GSM EDGE radio access network, GERAN_A 25).

[0062] Such a radio access network can be configured Petition 870240027939, dated 01 / 04 / 2024, page 17 / 137 13 / 121 by connecting to multiple different access networks, or it can be configured by connecting to any of the access networks. Additionally, the UE_A 10 can connect wirelessly to the radio access network.

[0063] In addition, a WLAN access network b (WLAN ANb) 75) that connects to the core network via gateway ePDG_A 65 and a WLAN access network (WLAN ANa 75) that connects to gateway PGW_A, PCRF_A 60 and AAA_A 55 can be configured as pluggable access networks in a WLAN access system.

[0064] It should be noted that each device has a configuration similar to that of the related art devices in a mobile communication system that uses EPS, and, therefore, detailed descriptions of them will be omitted. Each device will be briefly described later in this document.

[0065] PGW_A 30 is connected to PDN_A 5, SGW_A 35, ePDG_A 65, WLAN ANa 70, PCRF_A 60 and AAA_A 55 and serves as a relay device configured to transfer user data while functioning as a gateway device between PDN_A 5 and the core network_A 90.

[0066] SGW_A 35 is connected to PGW 30, to MME_A 104, to LTE AN 80, to SGSN_A 42, and to UTRAN_A 20, and serves as a relay device configured to transfer user data while functioning as a gateway device between the core_A 90 network and the 3GPP access network (UTRAN_A 20, GERAN_A 25, LTE AN_A 80).

[0067] MME_A 104 is connected to SGW_A 35, LTE AN 80, and HSS_A 50, and serves as an access control device configured to perform location information management and access control for UE_A 10 via LTE AN. Petition 870240027939, dated 01 / 04 / 2024, page 18 / 137 14 / 121 80. In addition, the core network_A 90 can include multiple location management devices. For example, a location management device other than MME_A 104 can be configured. Just as with MME_A 104, the location management device other than MME_A 104 can be connected to SGW_A 35, LTE AN 80, and HSS_A 50.

[0068] Furthermore, if multiple MMEs are included in the core_A 90 network, the MMEs can be connected to each other. With this configuration, the UE_A 10 context can be transmitted and / or received between the MMEs.

[0069] HSS_A 50 is connected to MME_A 104 and AAA_A 55 and serves as a management node that manages subscriber information. Subscriber information from HSS_A 50 is queried during access control from MME_A 104, for example. Additionally, HSS_A 50 can be connected to a location management device other than MME_A 104.

[0070] AAA_A 55 is connected to PGW 30, to HSS_A 50, to PCRF_A 60 and WLAN ANa 70 are configured to perform access control for UE_A 10 connected via WLAN ANa 70.

[0071] PCRF_A 60 is connected to PGW_A 30, to WLAN ANa 75, to AAA_A 55 and to PDN_A 5, and is configured to perform QoS (quality of service) management on data delivery. For example, PCRF_A 60 manages the QoS of a communication path between UE_A 10 and PDN_A 5.

[0072] The ePDG_A 65 is connected to PGW 30 and WLAN ANb 75 and is configured to provide user data when functioning as a gateway device between the core_A 90 network and WLAN ANb 75.

[0073] SGSN_A 42 is connected to UTRAN_A 20, GERAN_A and SGW_A 35, and is a control device for the Petition 870240027939, dated 01 / 04 / 2024, page 19 / 137 15 / 121 location management between a 3G / 2G access network (UTRAN / GERAN) and the LTE access network (E-UTRAN). In addition, SGSN_A 42 has the following functions: selecting the PGW and SGW; managing an UE time zone; and selecting the MME at the time of transfer to E-UTRAN.

[0074] Additionally, as illustrated in Figure 2B, each radio access network includes devices to which UE_A 10 is actually connected (such as a base station handset and an access point device), and the like. One can think of the devices used in these connections as devices adapted to radio access networks.

[0075] In this embodiment, LTE AN_A 80 includes eNB_A 45. The eNB_A 45 is a radio base station to which the UE_A 10 connects in an LTE access system, and the LTE AN_A 80 may include one or more radio base stations. It should be noted that the LTE AN_A 80 may be an access network not only for LTE but also for 5G or later radio communication.

[0076] The WLAN ANa 70 includes a WLAN access point (AP), WLAN APa 72, and a Trusted Wireless Access Gateway (TWAG_A 74). WLAN APa 72 is a radio base station to which UE_A 10 connects in the carrier's trusted WLAN access system running core network_A 90, and WLAN AN 70 may include one or more radio base stations. TWAG_A 74 serves as a gateway device between core network_A 90 and WLAN AN 70. WLAN APa 72 and TWAG_A 74 can be configured as a single device.

[0077] Even in the case where the operator running the core network_A 90 and the operator running the WLAN ANa 70 are different, such a configuration can be implemented through contracts and agreements between the operators. Petition 870240027939, dated 01 / 04 / 2024, p. 20 / 137 16 / 121

[0078] In addition, WLAN ANb 75 is configured to include a WLAN APb 76. WLAN APb 76 is a radio base station to which UE_A 10 connects in the WLAN access system if a trust relationship is not established with the operator running the core network_A 90, and WLAN ANb 75 may include one or more radio base stations.

[0079] In this way, WLAN ANb 75 is connected to the core_A 90 network through the ePDG_A 65, which is a device included in the core_A 90 network, serving as a gateway. The ePDG_A 65 has a security function to ensure security.

[0080] UTRAN_A 20 includes a Radio Network Controller (RNC) RNC_A 24 and an eNB (UTRAN)_A 45. The eNB (UTRAN)_A 45 is a radio base station to which UE_A 10 connects via a UTRA (Universal Terrestrial Radio Access Network) of a UMTS (Universal Mobile Telecommunications System), and UTRAN_A 20 may include one or more radio base stations. Additionally, the RNC_A 24 is a controller configured to connect the core_A 90 networks and the eNB (UTRAN)_A 45, and UTRAN_A 20 may include one or more RNCs. Furthermore, the RNC_A 24 can be connected to one or more eNBs (UTRANs)_A 45. Additionally, the RNC_A 24 can be connected to a radio base station (base station subsystem (BSS)_A 26) included in GERAN_A 25.

[0081] GERAN_A 25 includes BSS_A 26. BSS_A 26 is a radio base station to which UE_A 10 connects via a GSM (trade name) / EDGE (GERA) radio access network, and GERAN_A 25 may consist of one or more radio base station BSSs. In addition, multiple BSSs may be connected to each other. Furthermore, BSS_A 26 may be connected to RNC_A 24. Petition 870240027939, dated 01 / 04 / 2024, p. 21 / 137 17 / 121

[0082] It should be noted in the present invention that the UE_A 10 being connected to radio access networks refers to the UE_A 10 that is connected to a base station, access point, or similar device included in each of the radio access networks, and data, signals, and the like being transmitted and / or received also pass through these base station, access point, or similar devices. 1.2. Device configuration

[0083] The configuration of each device will be described below. 1.2.1. EU Configuration

[0084] The configuration of UE_A 10 will be described below. A Figure 3 illustrates a device configuration of the UE_A 10. As illustrated in the drawing, the UE_A 10 includes an antenna_A 300, a transmission and / or reception unit_A 301, a controller_A 302, and a storage unit_A 310.

[0085] In UE_A 10, the transmission and / or reception unit_A 301 and storage unit A310 are connected to controller A302 via a bus.

[0086] Controller_A 302 is a function unit for controlling UE_A 10. Controller_A 302 is a function unit configured to read and execute various types of programs stored in storage unit_A 310.

[0087] The A 301 transmission and / or reception unit is a function unit configured to transmit and / or receive radio communication data. The A 301 transmission and / or reception unit consists of a transmitter and a receiver; the transmitter can transmit control information through a base station, and the receiver can transmit data or control information through the base station.

[0088] The storage unit_A 310 is a unit of Petition 870240027939, dated 01 / 04 / 2024, page 22 / 137 18 / 121 function configured to store programs, data and similar items necessary for each operation of UE_A 10. The storage unit_A 310 consists, for example, of a memory formed by semiconductor devices, a hard disk drive (HDD), or similar.

[0089] In addition, storage unit_A 310 stores a UE 311 context. The UE 311 context can be a group of context information associated with a terminal device. The UE 311 context includes at least one UE context for each UE and one UE context for each PDN connection.

[0090] Figures 4A and 4B illustrate an example of the EU context. 311. Figure 4A illustrates the EU context for each EU. As illustrated in Figure 4A, the EU context for each EU is configured to include at least one IMSI and one ME identity. Additionally, the EU context for each EU can be configured to include an EMM (EPS Mobility Management) state, a GUTI (Globally Unique Temporary Identifier), and an EU usage type.

[0091] The International Mobile Station Equipment Identity (IMSI) is an identification information to be assigned to a user (subscriber) using UE_A 10. The IMSI can be an identification information indicating a line contract, and can be stored on a SIM card.

[0092] The ME identity is an ME ID, and can be the international identity of the mobile station equipment and the software version number (IMEI / IMISVS), for example. Additionally, here, the ME can be the UE.

[0093] The EMM state indicates a management state of Petition 870240027939, dated 01 / 04 / 2024, page 23 / 137 19 / 121 EU mobility. For example, the EMM state can be EMMREGISTERED where the EU is registered with the network (registered state) or EMM-DEREGISTERED where the EU is not registered with the network (unregistered state).

[0094] GUTI is the abbreviation for globally unique temporary identifier, and is temporary identification information in UE_A 10. The GUTI is formed by the identification information (globally unique MME identifier (GUMMEI)) in an MME (e.g., MME_A 104) and the identification information (M-TMSI) in UE_A 10 in a specific MME (e.g., MME_A 104). The UE context for each UE can store multiple GUTIs for each service.

[0095] The UE usage type is an identifying piece of information that is used to select a dedicated core network to which the UE connects and is stored for each UE. The UE or the network can select the dedicated core network to which the UE connects based on this information.

[0096] Additionally, the UE usage type can be an identifying information that is used to select a network slice to which the UE connects and is stored for each UE. The UE and / or the network can select the network slice to which the UE connects based on this information. In this case, multiple UE usage types can be stored in the storage unit. Furthermore, the UE usage type can be stored and simultaneously linked to application identification information or service identification information.

[0097] Figure 4B below illustrates the UE context for each PDN connection. As illustrated in the drawing, the UE context for each PDN connection is configured to include a PDN connection ID, an application ID, an APN (Access Point Name, Petition 870240027939, dated 01 / 04 / 2024, page 24 / 137 20 / 121 or access point name), an IP address, a default carrier, a network slice type, a network slice ID, and an isolation level.

[0098] The PDN connection ID is identifying information used to identify a PDN connection.

[0099] The application ID is information that identifies an application that can be used with this PDN connection. The storage unit can store multiple application IDs.

[00100] The APN indicates a connection destination of UE_A 10. This APN may consist of identification information about the network and identification information about a standard operator.

[00101] The IP address is an IP address assigned to UE_A 10 for the PDN connection, and can be an IPv4 address or an IPv6 prefix.

[00102] The default carrier is EPS carrier identification information used to identify a default carrier in this PDN connection.

[00103] The network slice type is an identifying piece of information used to identify a type of network slice that is connected to this PDN connection, and an identifying piece of information used to select a network slice to which the UE connects, stored for each UE or each PDN connection. The UE can select the network slice to which the UE connects based on this information. The network slice type can be the UE usage type. At this time, multiple network slices can be connected to UE_A 10.

[00104] Alternatively, the network slice type can be included in the UE usage type. At this time, multiple network slice types can be included in one UE usage type.

[00105] Alternatively, the network slice type may be information independent of the EU usage type, and may be a Petition 870240027939, dated 01 / 04 / 2024, page 25 / 137 21 / 121 information to further restrict the network slice to which the UE connects. At this point, multiple network slice types can be linked to a single UE usage type.

[00106] Network slice identification information (network slice ID) is identification information used to identify a network slice that is connected to this PDN connection, and identification information used to select a network slice to which the UE connects, stored for each UE. The UE can select the network slice to which the UE connects based on this information. The network slice ID can be the UE usage type. At this time, multiple network slices can be connected to UE_A 10.

[00107] Alternatively, the network slice ID can be included in the UE usage type. At this time, multiple network slice IDs can be included in a UE usage type.

[00108] Alternatively, the network slice ID can be independent of the UE usage type, and can be used to further restrict the network slice to which the UE connects. Currently, multiple network slice IDs can be linked to a single UE usage type.

[00109] Additionally, multiple network slices can belong to a single network slice type, or a network slice can belong to multiple network slice types. The isolation level can be information indicating a degree of independence of a connection. In other words, the isolation level is information indicating a level of independence with respect to other network slices. Specifically, for example, in a case where network slice_A makes all function units independent of other network slices, the connection between the UE and network slice_A may mean that the UE has established a connection with an isolation level of level 2. Alternatively, a case where some function units of Petition 870240027939, dated 01 / 04 / 2024, p. 26 / 137 22 / 121 network slice_A is shared with other network slices, and a case where the UE uses the shared function unit in network slice_A may mean that the UE has established a connection with isolation level 1.

[00110] For example, in a case where the isolation level of the connection is level 1, the function unit for control information is shared with other network slices. Here, the function unit for control information could be, for example, the MME. Alternatively, if the isolation level is level 1, the SGW and / or the PGW could be shared with other network slices.

[00111] Alternatively, the isolation level can be used to identify whether a radio resource such as a base station or similar is shared. 1.2.2. eNB Configuration

[00112] The configuration of the eNB_A 45 will be described below. Figures 5A and 5B illustrate the device configuration of the eNB_A 45. As illustrated in the drawing, the eNB_A 45 includes an external antenna B 500, a transmit and / or receive unit_B 501, a network connection unit_B 503, a controller_B 502, and a storage unit_B 510. The network connection unit_B 503, the transmit and / or receive unit_B 501, and the storage unit_B 510 are connected to the controller_B 502 via a bus.

[00113] Controller_B 502 is a function unit for controlling eNB_A 45. Controller_B 502 implements various processes by reading and executing various programs stored in storage unit_B 510.

[00114] The network connection unit_B 503 is a function unit through which the eNB_A 45 connects to the MME_A 104 and / or the SGW_A 35 or a C-SGN_A 95 (Cellular Serving Gateway Node, Petition 870240027939, dated 01 / 04 / 2024, page 27 / 137 23 / 121 or cellular service gateway node). In addition, the network connection unit_B 503 is a transmit and / or receive function unit through which the eNB_A 45 transmits and / or receives user data and / or control data to and / or from the MME_A 104 and / or the SGW_A 35 or the C-SGN_A 95.

[00115] The transmission and / or reception unit_B 501 is a function unit through which the eNB_A 45 connects to the UE_A 10. Furthermore, the transmission and / or reception unit_B 501 is a transmission and / or reception function unit for transmitting and / or receiving user data and / or control data to and / or from UE_A 10. Additionally, the external antenna_B 500 is connected to the transmission and / or reception unit_B 501.

[00116] Storage unit_B 510 is a function unit for storing programs, data, and similar items necessary for each operation of the eNB_A 45. Storage unit 640 consists, for example, of a memory formed by semiconductor devices, a hard disk drive (HDD), or similar.

[00117] Storage unit_B 510 includes at least one list of MMEs 511. The list of MMEs 511 is a list of the MME to which eNB_A 45 connects, and may be a group of MMEs.

[00118] Figure 5B illustrates an example of the 511 MME list. As illustrated in the drawing, eNB_A 45 can store a globally unique MME identifier (GUMMEI) as MME identification information. Additionally, eNB_A 45 can store the MME identification information in association with information to identify the network slice type, network slice ID, and isolation level supported by each MME.

[00119] It should be noted that the network slice type supported by MME refers to a network slice type with which the network slice Petition 870240027939, dated 01 / 04 / 2024, page 28 / 137 24 / 121 where MME is included is connected.

[00120] In addition, the network slice supported by MME refers to a network slice in which MME is included.

[00121] Additionally, storage unit_B 510 can store at least the identification information and / or the control information and / or an indicator and / or a parameter included in the control message transmitted and / or received in a communication procedure, which will be described later. 1.2.3. MME Configuration

[00122] The constitution of MME_D 105 will be described below. It should be noted that MME_A 104, MME_B 106 and MME_C 107 may also have the same configuration. Figures 6A to 6D illustrate the device configuration of MME_D 105. As illustrated in the drawings, MME_D 105 includes a network connection unit_C 601, a controller_C 602 and a storage unit_C 610. The network connection unit_C 601 and the storage unit_C 610 are connected to the controller_C 602 via a bus.

[00123] Controller_C 602 is a function unit for controlling MME_D 105. Controller_C 602 implements several processes by reading and executing various programs stored in storage unit_C 610.

[00124] Network connection unit_C 601 is a function unit through which MME_D 105 connects to eNB_A 45 and / or HSS_A 50 and / or SGW_A 35. In addition, network connection unit_B 601 is a transmission and / or reception function unit through which MME_D 105 transmits and / or receives user data and / or control data to and / or from eNB_A 45 and / or HSS_A 50 and / or SGW_A 35.

[00125] The storage unit_C 610 is a unit of Petition 870240027939, dated 01 / 04 / 2024, p. 29 / 137 25 / 121 function to store programs, data and similar items necessary for each operation of the MME_D 105. The storage unit_C 610 consists, for example, of a memory formed by semiconductor devices, a hard disk drive (HDD), or similar.

[00126] Additionally, the storage unit_C 610 can store at least the identification information and / or the control information and / or the indicator and / or the parameter included in the control message transmitted and / or received in the communication procedure, which will be described later.

[00127] Storage unit_C 610 stores, as illustrated in the drawings, an MME context 611, a network slice type 612, and a network slice ID 613. It should be noted that the MME context 611 includes an MM (Mobility Management) context and an EPS carrier context. Alternatively, the MME context may include an EMM context and an ESM (EPS Session Management) context. The MM context may be the EMM context, and the EPS carrier context may be the ESM context.

[00128] The stored MME context for each UE includes an IMSI (International Mobile Station Equipment Identity), an IMSI-unauthenticated indicator, an MSISDN (phone number on the SIM card in a mobile / cell phone), an MM state, a globally unique temporary identifier (GUTI), an ME identity, a tracking area list, a tracking area identifier of the last tracking area update (TAI of last TAU), an E-UTRAN global cell identity (ECGI), an E-UTRAN cell identity age, i.e., the time elapsed since the last E-UTRAN global cell identity was obtained, a Closed Subscriber Group ID (CSG), and a member quality. Petition 870240027939, dated 01 / 04 / 2024, page 30 / 137 26 / 121 CSG, an access mode, an authentication vector, a UE radio access capability, a mobile station class symbol (MS Classmark 2), MS Classmark 3, supported codecs, a UE network capability, a mobile station network capability, UE-specific DRX parameters, a selected non-access layer (NAS) algorithm, an eKSI (key set identifier for E-UTRAN), K_ASME (key access security management entries), a non-access layer key parameter and count (NAS Keys and COUNT), a selected core network carrier ID, a recovery, an access restriction, a carrier-determined lock (ODB) for PS (packet switched) parameters, an APN-OI access point name replacement, an MME IP address for S11, an MME tunnel endpoint identifier (TEID ID) for S11, an S-GW IP address for S11 / S4, a TEID of S-GW for S11 / S4, an SGSN IP address for S3,An SGSN TEID for S3, an eNodeB address in use for S1-MME, an eNB UE S1AP ID, an MME UE S1AP ID, a subscribed UE-AMBR aggregate maximum bit rate, a UE-AMBR, subscribed EPS billing characteristics, a subscribed RFSP index, an RFSP index in use, a trace reference, a trace type, a trigger ID, an operations and maintenance center (OMC) identity, a UE reachability URRP-MME request for MME, CSG subscription data, an allowed local IP access (LIPA), a subscribed periodic RAU / TAU timer, a multimedia priority service (MPS) circuit switching (CS) priority, an MPS EPS priority, a voice support matching indicator, and IMS homogeneous voice support in PS sessions. Petition 870240027939, dated 01 / 04 / 2024, p. 31 / 137 27 / 121

[00129] IMSI (International Mobile Station Equipment Identity) is a user's permanent identification information. The IMSI is identical to the IMSI stored in HSS_A 50.

[00130] The indicator not authenticated by IMSI is an instruction indicating that this IMSI is not authenticated.

[00131] The MSISDN (Mobile Station International Subscriber Directory Number) represents the UE telephone number. The MSISDN is indicated by the HSS_A 50 storage unit.

[00132] The MM State indicates a mobility management state of the MME. This management information indicates an ECM-IDLE state (EPS Connection Management) in which a connection between an eNB and the core network is released, an ECM-CONNECTED state in which the connection between the eNB and the core network is not released, or an EMM-DEREGISTRERED state in which the MME does not store the UE location information and an EMM-REGISTERED state in which the MME stores the UE location information.

[00133] GUTI (Globally Unique Temporary Identity) is temporary identification information about the UE. GUTI includes identification information about the MME (GUMMEI - Globally Unique MME Identifier) ​​and identification information about the UE in a specific MME (M-TMSI - MTemporary Mobile Subscriber Identity).

[00134] ME Identity is an EU ID, and can be the international identity of the mobile station equipment or the Petition 870240027939, dated 01 / 04 / 2024, page 32 / 137 28 / 121 software version number (IMEI / IMISVS), for example.

[00135] Tracking Area List is a list of tracking area identification information that is assigned to the EU.

[00136] TAI of last TAU ​​is tracking area identification information indicated by a recent tracking area update procedure.

[00137] ECGI (E-UTRAN Cell Global Identity) is a recent EU cell identification information known by MME_A 104.

[00138] E-UTRAN Cell Identity Age, or E-UTRAN cell identity age, indicates the time elapsed since the MME obtained the ECGI.

[00139] CSG ID is an identification information for a closed subscriber group (CSG - Closed Subscriber Group), in which UE has recently operated, known as MME.

[00140] CSG membership status is information about recent EU CSG membership known to MME. CSG membership status indicates whether the EU is a member of the CSG.

[00141] Access mode is an access mode of a cell identified by the ECGI, and may be identifying information indicating that the ECGI is a hybrid that allows access to both UEs: that which is the CSG and that which is not the CSG.

[00142] Authentication Vector, or authentication vector, indicates a temporary Authentication and Key Agreement (AKA) of a specific UE followed by the MME. The authentication vector includes a random RAND value used for authentication, an XRES expectation response, a K_ASME key, and a network-authenticated AUTN language (token).

[00143] UE Radio Access Capability, or access capability Petition 870240027939, dated 01 / 04 / 2024, page 33 / 137 29 / 121 by EU radio is an identification number indicating an EU radio access capability.

[00144] MS Classmark 2 is a class mark symbol for a core network of a 3G / 2G CS domain (UTRAN / GERAN). MS Classmark 2 is used in a case where UE supports single radio voice call continuity (SRVCC) for GERAN or UTRAN.

[00145] MS Classmark 3 is a classification symbol (Classmark) for a GERAN CS domain radio network. MS Classmark 3 is used in a case where UE supports single radio voice call continuity (SRVCC) for GERAN.

[00146] Supported Codecs, or supported codecs, are a list of codes supported by the CS domain. This list is used in a case where the UE supports SRVCC for GERAN or UTRAN.

[00147] UE Network Capability, or UE network capability, indicates a function supported by the UE. In other words, it indicates the characteristics of the UE.

[00148] MS Network Capability, or mobile station (MS) network capability, is information that includes at least one type of information required for the SGSN directed to the UE that has the function of GERAN and / or UTRAN.

[00149] UE Specific DRX Parameters, or UE-specific DRX parameters, are parameters used to determine a discontinuous reception (DRX) cycle length of the UE. Here, DRX is a function to switch the UE to a low-power mode if there is no communication for a certain period of time, in order to reduce the power consumption of the UE battery as much as possible.

[00150] Selected NAS Algorithm, or NAS algorithm Petition 870240027939, dated 01 / 04 / 2024, p. 34 / 137 The selected 30 / 121 is a security algorithm chosen for a NAS (Non-Access Stratum).

[00151] eKSI (Key set Identifier for E-UTRAN) is a key set that indicates the key access security management entries, or K_ASME. The eKSI can indicate whether a security key obtained through UTRAN or E-UTRAN security authentication is used.

[00152] K_ASME (Key Access Security Management Entries) is a key for the E-UTRAN key hierarchy generated based on a cipher key (CK) and an integrity key (IK).

[00153] The NAS Keys and COUNT parameter includes a K_NASint key, a K_NASenc key, and a NAS count parameter. The K_NASint key is a key for encryption between the UE and the MME, the K_NASenc key is a key for security protection between the UE and the MME. Additionally, the NAS count is a count that starts when a new key is configured, establishing security between the UE and the MME.

[00154] Selected CN Operator ID, or Selected Core Network Operator (NC) ID, is an identifying piece of information used to share the network between operators, for a selected core network operator.

[00155] Recovery is an identifying information that indicates whether the HSS performs database recovery.

[00156] Access Restriction, or access restriction, is subscriber information for access restriction.

[00157] ODB for PS parameters, or OBD for PS parameters, indicates a state of a lock determined by the operator (ODB Petition 870240027939, dated 01 / 04 / 2024, page 35 / 137 31 / 121 Operator Determined Barring (ODB). Here, ODB is an access rule determined by the network operator (carrier).

[00158] APN-OI Replacement, or APN-Oi Access Point Name Replacement, is a domain name that replaces the APN in a case where the PGW's FQDN (fully qualified domain name) is constructed to perform DNS resolution. This replacement domain name is applied to all APNs.

[00159] MME IP address for S11, or MME IP address for S11, is an MME IP address used for an interface with the SGW.

[00160] MME TEID for S11, or TEID of MME for S11, is a tunnel endpoint identifier (TEID) used for interfacing with the SGW.

[00161] S-GW IP address, or S-GW IP address for S11 / S4, is an SGW IP address used for an interface between the MME and the SGW or between the SGSN and the MME.

[00162] S-GW TEID for S11 / S4, or S-GW TEID for S11 / S4, is an SGW TEID used for the interface between the MME and the SGW or between the SGSN and the MME.

[00163] SGSN IP address for S3, or SGSN IP address for S3, is an SGSN IP address used for the interface between the MME and the SGSN.

[00164] SGSN TEID for S3, or SGSN TEID for S3, is a TEID of the SGSN used for the interface between the MME and the SGSN.

[00165] eNodeB Address in Use for S1-MME, or eNodeB address in use for S1-MME, is an eNB IP address recently used for an interface between the MME and the eNB.

[00166] eNB UE S1AP ID, or eNB UE S1AP ID, is an identification information for the UE in the eNB.

[00167] MME EU S1AP ID, or MME EU S1AP ID, is a Petition 870240027939, dated 01 / 04 / 2024, p. 36 / 137 32 / 121 EU identification information at MME.

[00168] Subscribed UE-AMBR, or subscribed maximum aggregate bit rate, indicates the maximum value of a maximum bit rate (MBR) for uplink communication and downlink communication for sharing all non-guaranteed bit rate (GBR) carriers (non-guaranteed carriers) according to the user's subscriber information.

[00169] UE-AMBR indicates the maximum MBR values ​​for uplink communication and downlink communication that are recently used to share all non-GBR carriers (non-guaranteed carriers).

[00170] EPS Subscribed Charging Characteristics, or EPS subscribed charging characteristics, indicate an EU charging performance. For example, EPS subscribed charging characteristics may indicate subscriber information such as normal, prepaid, a flat rate, real-time billing, or similar.

[00171] Subscribed RFSP Index, or subscribed RFSP index, is an index for a specific RRM configuration in E-UTRAN obtained from HSS.

[00172] RFSP Index in Use, or RFSP index in use, is an index for the specific RRM configuration in E-UTRAN that is recently used.

[00173] Trace reference, or tracking reference, is identifying information used to identify a specific tracking record or set of records.

[00174] Trace type, or trace type, indicates a type of trace. For example, the trace type may indicate a type traced by HSS and / or a type traced by MME, SGW, or PGW. Petition 870240027939, dated 01 / 04 / 2024, p. 37 / 137 33 / 121

[00175] Trigger ID, or Trigger ID, is an identifying piece of information used to identify a constituent element for which tracking begins.

[00176] OMC Identity, or Operations and Maintenance Center (OMC) Identity, is an identifying information used to identify an OMC that receives the tracking record.

[00177] URRP-MME (UE Reachability Request Parameter for the Mobility Management Entity) is an identifying piece of information indicating that the HSS requests notification of UE activity from the MME.

[00178] CSG Subscription Data, or CSG subscription data, is a relevant list of a visited public land mobile network (PLMN) CSG ID (VPLMN) from a roaming destination and an equivalent PLMN from the roaming destination. CSG subscription data may be associated with an expiration date indicating an expiration date for the CSG ID and a missing expiration date indicating that there is no expiration date for each CSG ID. The CSG ID may be used for a specific PDN connection via local IP access (LIPA).

[00179] LIPA Allowed, or LIPA permitted, indicates whether the EU is allowed to use LIPA in this PLMN.

[00180] Subscribed Periodic RAU / TAU Timer, or subscribed periodic RAU / TAU timer, is a timer for a periodic RAU (Routing Area Update) and / or TAU (Tracking Area Update).

[00181] MPS CS priority, or MPS CS priority, indicates that the UE is registered in the eMLPP (enhanced Multi-Level Precedence and Pre-emption service) or a 1x priority RTT service in Petition 870240027939, dated 01 / 04 / 2024, page 38 / 137 34 / 121 CS domain.

[00182] MPS EPS priority, or MPS EPS priority, is an identifying information indicating that the UE is registered with MPS (Multimedia Priority Service) in the EPS domain.

[00183] Voice Support Match Indicator, or a voice support match indicator, indicates whether a UE radio capability is compatible with the network configuration. For example, the voice support match indicator shows whether UE support for SRVCC matches network support for voice calling.

[00184] Homogenous Support of IMS Voice over PS Sessions for MME, or homogeneous support of IMS voice (IP Multimedia Subsystem (IMS) in PS sessions for MME), is a statement indicating, for each UE, whether an IMS voice call in a PS session is supported. Homogenous support of IMS voice in PS sessions for MME includes the option Supported, where an IP Multimedia Subsystem (IMS) voice call is supported in all MME-managed tracking areas (TAs), and the option Not supported, indicating a case where there is no TA in which IMS voice calling in the PS session is supported. Additionally, the MME does not notify the HSS of this instruction information if the IMS voice call in the PS session is not uniformly supported (the TA where support is provided and the TA where support is not provided are both present in the MME) and if it is unclear whether the call is supported.

[00185] In addition, the MME context for each PDN connection includes an APN in use, an APN restriction, a subscribed APN, a PDN type, an IP address, EPS PDN billing characteristics, an APN-OI replacement, SIPTO permissions, a Petition 870240027939, dated 01 / 04 / 2024, page 39 / 137 35 / 121 local home network identification, LIPA permissions, WLAN offload capability, an allowed VPLMN address, a PDN GW address in use (control information), a PDN GW TEID for interface S5 / S8 (control information), an MS information change report, a CSG information report, a presence report area, a subscribed EPS QoS profile, a subscribed APN maximum bit rate (APN-AMBR), a PDN GW generic routing encapsulation key (GRE) for uplink traffic (user data), and a default carrier.

[00186] APN in Use, or APN in use, indicates the APN that has been used recently. This APN includes identifying information about the APN network and identifying information about a default carrier.

[00187] APN Restriction, or APN restriction, indicates a restriction on a combination of an APN type with the APN associated with that carrier context. In other words, the APN restriction is information to restrict the number of APNs and the type of APNs that can be established.

[00188] APN Subscribed, or subscribed APN, refers to a registration APN received from the HSS.

[00189] PDN Type, or PDN type, indicates the type of IP address. The PDN type indicates IPv4, IPv6, or IPv4v6, for example.

[00190] IP Address, or IP address, indicates an IPv4 address or an IPv6 prefix. Note that the IP address can store both IPv4 and IPv6 prefixes.

[00191] EPS PDN Charging Characteristics, or EPS PDN charging characteristics, indicate a charging performance. EPS PDN charging characteristics can indicate, for example, normal, prepaid, a flat rate, or time-based billing. Petition 870240027939, dated 01 / 04 / 2024, page 40 / 137 36 / 121 real.

[00192] APN-OI Replacement, or APN-OI replacement, is an APN proxy domain name that has the same function as the APN-OI replacement, registered for each UE. It should be noted that the APN-OI replacement has a higher priority than the APN-OI replacement for each UE.

[00193] SIPTO permissions, or SIPTO permissions, indicate permission information for a selected IP traffic transfer (SIPTO) using this APN. Specifically, SIPTO permissions identify a prohibition on the use of a SIPTO permission, or the use of SIPTO on the network, excluding the local network, permission to use SIPTO on the network, including the local network, or permission to use SIPTO only on the local network.

[00194] Local Home Network ID, or local home network identification, indicates the identification information of a home network to which the base station belongs, in the case where SIPTO (SIPTO@LN) can be used using the local network.

[00195] LIPA permissions, or LIPA permissions, are identifying information indicating whether this PDN can be accessed via local IP access (LIPA). Specifically, LIPA permissions can be LIPA prohibited, which does not allow LIPA, LIPA only, which only allows LIPA, or a conditional LIPA, which allows LIPA depending on a condition.

[00196] WLAN offload ability, or WLAN offload capability, is an identifying information indicating whether traffic connected through this APN can perform a wireless LAN offload using a cooperative function between the wireless LAN and 3GPP, or whether it maintains the 3GPP connection. WLAN offload capability may vary for each type of radio access technology (RAT). Petition 870240027939, dated 01 / 04 / 2024, p. 41 / 137 37 / 121 Specifically, different WLAN offloading capabilities may be present for LTE (E-UTRA) and 3G (UTRA).

[00197] VPLMN Address Allowed, or Public Mobile Land Network (VPLMN) Address Allowed, indicates whether a connection in which the UE uses this APN is allowed to use only one PGW (IP address) in the HPLMN domain in the PLMN (VPLMN) of the roaming destination or to additionally use the PGW in the VPLMN domain.

[00198] PDN GW Address in Use, or PDN GW address in use (control information), indicates a recent IP address of the PGW. This address is used when a control signal is transmitted.

[00199] PDN GW TEID for S5 / S8, or PDN GW TEID for S5 / S8 interface (control information), is a TEID (tunnel endpoint identifier) ​​used for transmitting and / or receiving control information on an interface (S5 / S8) between the SGW and the PGW.

[00200] MS Info Change Reporting Action, or MS information change report, is an information item indicating that the PGW needs to be notified of changes to the user's location information.

[00201] CSG Information Reporting Action, or CSG information report, is an information item indicating that the PGW needs to be notified of CSG information that is being changed.

[00202] Presence Reporting Area Action, or presence reporting area, indicates the need to notify the change regarding the EU's presence in a presence reporting area. This information item is separated into a presence reporting area identification piece and an element included in the presence reporting area. Petition 870240027939, dated 01 / 04 / 2024, page 42 / 137 38 / 121

[00203] EPS subscribed QoS profile, or EPS subscribed QoS profile, indicates a QoS (quality of service) parameter for a standard carrier at a carrier level.

[00204] Subscribed APN-AMBR, or Subscribed APN Maximum Bit Rate (APN-AMBR), indicates the maximum value of the maximum bit rate (MBR) of the uplink communication and the downlink communication to share all non-guaranteed bit rate (Non-GBR) carriers (non-guaranteed carriers) established for this APN according to the user's subscriber information.

[00205] APN-AMBR, or APN maximum bit rate, indicates the maximum value of the maximum bit rate (MBR) of the uplink communication and the downlink communication to share all non-guaranteed bit rate (NonGBR) carriers (non-guaranteed carriers) established for this APN, which was determined by the PGW.

[00206] PDN GW GRE Key for uplink traffic (user data), or PDN GW Generic Routing Encapsulation (GRE) key for uplink traffic (user data), is a GRE key for uplink communication of user data from the interface between the SGW and the PGW.

[00207] Default Bearer, or default bearer, is, at the time of establishing the PDN connection, information that is obtained and / or generated, and an EPS bearer identification information to identify a default bearer associated with the PDN connection.

[00208] In addition, the stored MME context for each carrier includes an EPS carrier ID, a TI (transaction identifier), an S-GW IP address for S1-u, an S-GW TEID for S1u, a PDN GW TEID for S5 / S8, a PDN GW IP address for S5 / S8, an EPS carrier QoS, and a TFT. Petition 870240027939, dated 01 / 04 / 2024, page 43 / 137 39 / 121 (traffic flow model).

[00209] EPS Bearer ID, or EPS bearer identification, is the unique identifying information to identify the EPS bearer for an EU connection via E-UTRAN.

[00210] It should be noted that the EPS carrier ID may be the EPS carrier identification information that identifies a dedicated carrier. Consequently, the EPS carrier ID may be an identifying information to identify the EPS carrier that is different from the standard carrier.

[00211] It should be noted that, as described above, the EPS carrier may be a communication path established between UE_A 10 and C-SGN_A 95. Furthermore, the EPS carrier may be formed by a radio bearer (RB) established between UE_A 10 and eNB_A 45 and an S1 bearer established between eNB_A 45 and C-SGN_A 95. Here, the radio bearer, RB, and the EPS carrier may be in a one-to-one correspondence. Consequently, the RB's identification information may be in a one-to-one correspondence with the EPS bearer's identification information, or it may be the same identification information.

[00212] Additionally, the EPS carrier can be a logical communication path established between UE_A 10 and PGW_A 30. In this case, the EPS carrier can also be configured to include the radio carrier (RB) established between UE_A 10 and eNB_A 45. Furthermore, the RB and the EPS carrier can be one-to-one matched. Consequently, the RB's identification information can be one-to-one matched with the EPS carrier's identification information, or it can be the same identification information.

[00213] Consequently, an EPS carrier ID that Petition 870240027939, dated 01 / 04 / 2024, p. 44 / 137 40 / 121 identifies the specific carrier; it can be identification information that identifies a Signalling Radio Bearer (SRB) and / or a Control Signalling Radio Bearer (CRB), or it can be identification information that identifies a Data Radio Bearer (DRB).

[00214] Here, as described above, the SRB in this embodiment may originally be the RB established to transmit and / or receive control information, such as a control message, or similar. Here, the CRB in this embodiment may originally be the RB established to transmit and / or receive control information, such as a control message, or similar. It should be noted that in this embodiment, with the use of the RB that is originally used to transmit and / or receive the control message, the transmission and / or reception of user data is performed. Consequently, in this embodiment, with the use of the SRB or the CRB, the control message and user data are transmitted and / or received.

[00215] Additionally, the DRB in this modality may be the RB established for the transmission and / or reception of user data.

[00216] TI is the abbreviation for transaction identifier, and it is an identifying piece of information that identifies a bidirectional flow of messages (transaction).

[00217] The IP address of S-GW for S1-u is an IP address of the SGW used for an interface between the eNB and the SGW.

[00218] Additionally, in a case where user data is transmitted and / or received when included in a message for control information, the IP address of S-GW to S1-u may be an IP address of the SGW used for MME and / or Petition 870240027939, dated 01 / 04 / 2024, p. 45 / 137 41 / 121 is an interface between the SGSN and the SGW, or it could be the IP address of the S-GW for S11 / S4.

[00219] S-GW TEID to S1u, or TEID from S-GW to S1u, is a SGW TEID used for the interface between the eNB and the SGW.

[00220] Additionally, in a case where MME and / or user data are transmitted and / or received when included in the message for control information, the TEID from S-SW to S1u may be a TEID address from the SGW used for the interface between the SGSN and the SGW, or it may be the TEID from S-GW to S11 / S4.

[00221] PDN GW TEID for S5 / S8, or PDN GW TEID for S5 / S8, is a PGW TEID for transmitting user data on the interface between the SGW and the PGW.

[00222] PDN GW IP address for S5 / S8, or PDN GW IP address for S5 / S8, is a PGW IP address for transmitting user data on the interface between the SGW and the PGW.

[00223] EPS bearer QoS, or EPS carrier QoS, includes a QoS class identifier (QCI) and an Allocation and Retention Priority (ARP). The QCI indicates a class to which the QoS belongs. The QoS can be classified according to the presence or absence of bandwidth control, an allowed delay time, a packet loss rate, or similar. The QCI includes information indicating priority. ARP is information representing a priority related to carrier maintenance.

[00224] TFT is short for traffic flow model and indicates all packet filters associated with the EPS carrier.

[00225] Additionally, Figure 6C illustrates the network slice type 612 included in storage unit_C 610, and Figure 6D illustrates the network slice ID 613.

[00226] As illustrated in the drawing, the 612 network slice type is formed by the network slice type and the isolation level. The type of Petition 870240027939, dated 01 / 04 / 2024, page 46 / 137 A 42 / 121 network slice, 612, can contain various network slice types and isolation levels. Additionally, the network slice type and isolation level can be stored while being associated with each other.

[00227] Similarly, network slice ID 613 is formed by the network slice ID and the isolation level. Network slice ID 612 can contain multiple network slice IDs and isolation levels. Additionally, the network slice ID and the isolation level can be stored while being associated with each other.

[00228] As illustrated in the diagram, it can be noted that for the network slice type MME_D 105, a type 1 and a type 2 are supported, and the isolation level of each type is level 2. Similarly, it can be noted that MME_D 105 is included in a network slice ID 1 and a network slice ID 2, and the isolation level of each ID is level 2.

[00229] It should be noted that although Figures 6A to 6D mainly illustrate the configuration of MME_D 105, for example, in the case of MME_A 104, type 1 can be stored for the network slice type and the isolation level of Lv. 2 can be stored in storage unit_C 610.

[00230] Additionally, network slice type 612 can be included in the MME context 611. Specifically, the type can be included in the MME for each PDN connection or in the MME context for each carrier.

[00231] Alternatively, as illustrated in Figures 6A to 6D, MME_D 105 can store the context of MME 611 and the network slice type 612, so that they are independent of each other. 1.3. Processing Example

[00232] An example of processing according to the present embodiment will be described below. Petition 870240027939, dated 01 / 04 / 2024, p. 47 / 137 43 / 121 1.3.1. Network slice type notification procedure

[00233] UE_A 10 can pre-execute a Radio Resource Control (RRC) connection establishment procedure before performing a Non-Access Stratum (NAS) procedure with the network. A method is described below in which UE obtains the network slice type and / or network slice information in the RRC connection establishment procedure to perform the selection of the network slice that is a connection destination established in a connection procedure.

[00234] Figure 7 illustrates an example of a network slice type and / or network slice ID notification procedure. As illustrated in the drawing, each of MME_A 104 and MME_B 106 transmits a notification message to eNB_A 45 managed by each MME (S700, S702). MME_A 104 and MME_B 106 can transmit the notification message based on the completion of the network slice construction, or they can perform the notification periodically. Alternatively, with a change in network slice configuration, the notification message can be transmitted.

[00235] The notification message may be an MME configuration update message.

[00236] The notification message includes a first identifying information and / or a second identifying information and / or a third identifying information and / or a fourth identifying information.

[00237] Here, the first identifying information may be information to identify the type of network slice supported by the MME. Alternatively, the first identifying information may be information to identify the type of network slice supported by the network slice in which the MME is included. In the following description, the type of network slice supported by the MME may have the same meaning as the Petition 870240027939, dated 01 / 04 / 2024, page 48 / 137 44 / 121 network slice type supported by the network slice in which the MME is included. Additionally, the first identification information may also be the UE usage type. Here, the information may identify the network slice type or the UE usage type supported by the MME being a transmission source. In other words, the first identification information transmitted by MME_A 104 and the first identification information transmitted by MME_B 106 to eNB_A 45 may be different from each other.

[00238] Additionally, the second identifying information can be a degree of independence of the network slice. In other words, the second identifying information can be a degree of independence of a NF (network function) included in the network slice.

[00239] For example, the second identifying information could be information indicating a degree of independence (isolation level) of the MME being NF in relation to other network slices. In the present embodiment, since the MME can be included in one or more network slices, the number of network slices in which the MME is included can be managed while being made to correspond to the degree of independence. Specifically, for example, in a case where MME_A 104 belongs to network slice_A 101 and is independent of other network slices, i.e., in a case where MME_A 104 is included in only one network slice, the isolation level can be made to be level 2. On the other hand, in a case where MME_A 104 belongs to network slice_A 101 and network slice_B 102 and MME_A 104 is not independent in the network slices, i.e., in a case where the MME_A 104 is included in several network slices; the isolation level may be level 1. In other words, the second identifying information may indicate a degree of independence of the MME. Here, the information may be for Petition 870240027939, dated 01 / 04 / 2024, p. 49 / 137 45 / 121 indicate the type of network slice identified by each MME, being the transmission source using the first identification information or the isolation level as the network slice indicated by the third identification information.

[00240] The third piece of identifying information may be information to identify the network slice.

[00241] Additionally, the fourth identifying information is information to identify an MME included in the network slice that supports the network slice type that is the same as the MME. Specifically, if the supported network slice types are the same for each group to which the MME belongs, the fourth identifying information can be an MME group ID (MMEGI) or an SGSN group ID. Alternatively, in the case where, using some GUMMEI identifier as a wildcard, the MME belonging to the same network slice can be identified, the fourth identifying information can be a wildcard MME information. Here, the information can be used to identify the MME that supports the network slice type or the UE usage type identified by the first identifying information.

[00242] Each of the MME_A 104 and MME_B 106 can transmit the notification message to eNB_45 for each network slice in which each MME is included, can transmit the notification message for each type of network slice or type of UE use, or can include in one notification several items of information from the first to the fourth identification information.

[00243] In other words, in a case where MME_A 104 supports network slice_A 101 and network slice_B 102, each item of identification information for network slice_A 101 and each item of identification information for network slice_B 102 can be transmitted to eNB_45 while being included in different Petition 870240027939, dated 01 / 04 / 2024, p. 50 / 137 46 / 121 notification messages, respectively, or it can be transmitted to eNB_45 while it is in the same notification message.

[00244] Additionally, MME_A 104 and MME_B 106 can transmit the notification message while including the UE usage type supported by each MME. In other words, MME_A 104 and MME_B 106 can transmit the notification message while including the UE usage type supported by the network slice in each MME included therein. It should be noted that each MME can obtain the UE usage type from the HSS in advance.

[00245] One method of acquiring the type of EU usage obtained from the HSS by each MME could be, for example, a procedure in which the MME periodically transmits a query message to the HSS, and receives from the HSS a reply message corresponding to the query message.

[00246] eNB_A 45 can transmit a reply message for each MME (MME_A 104, MME_B 106) for each notification message received. The reply message can be an acknowledgment or confirmation of an MME configuration update.

[00247] Additionally, if a relative MME capacity is included in the MME configuration update message, at the time of MME re-selection by eNB_A 45, the first identification information and / or the second identification information may be used as priority is given over the information indicated by the relative MME capacity.

[00248] Additionally, the notification message may be a response based on a request originating from eNB_A 45. Specifically, eNB_A 45 may transmit a request message to each MME to request information about the MME, and the notification message may be received as a response. Petition 870240027939, dated 01 / 04 / 2024, page 51 / 137 47 / 121

[00249] The request message can be an S1 configuration request message or an eNB configuration update message, eNB_A 45 can transmit the request message, including eNB_A 45 identification information in the message.

[00250] Additionally, the notification message transmitted from each MME as a response to the request message may be an S1 configuration response message or an eNB configuration update acknowledgment.

[00251] On the other hand, UE_A 10 transmits an RRC message to eNB_A 45 (S704). The RRC message may be an RRC connection request message to establish the RRC connection between UE_A 10 and eNB_A 45. UE_A 10 transmits the RRC message, including at least one fifth piece of identifying information.

[00252] The fifth identifying information may be information indicating that UE_A 10 requests a connection to the network slice, information indicating that UE_A 10 has a function to select the type of network slice and / or the network slice and / or the isolation level, or information obtained by combining these other pieces of information. The fifth identifying information may be UE capability information indicating that the UE_A 10 resource has a function to connect to the network slice.

[00253] The fifth piece of identification information may be information to request from the network an eighth piece of identification information and / or a ninth piece of identification information and / or a twenties piece of identification information. Furthermore, the fifth piece of identification information may be information to request from the network the third piece of identification information.

[00254] Here, the eighth group of identifying information can Petition 870240027939, dated 01 / 04 / 2024, page 52 / 137 48 / 121 is a list of information to identify the type of network slice supported by the network slice in which the MME to which eNB_A 45 connects is included. In other words, as illustrated in the drawing, in a case where eNB_A 45 connects to both MME_A 104 included in network slice_A classified as network slice type_A and MME_B 106 included in network slice_B classified as network slice type_B, the eighth identification information group can be configured to include the first identification information to identify network slice type_A and the first identification information to identify network slice type_B. The eighth identification information group can be formed by one or more items of information from the first identification information that eNB_A 45 obtains from MME_A 104 and MME_B 106.

[00255] Additionally, the ninth identification information group can be a list of information to identify the network slice in which the MME to which eNB_A 45 connects is included. In other words, as illustrated in the drawing, in a case where eNB_A 45 connects to both MME_A 104 included in network slice_A and MME_B 106 included in network slice_B, the ninth identification information group can be configured to include the third identification information to identify network slice_A and the third identification information to identify network slice_B. The ninth identification information group can be formed by one or more items of information from the third identification information that eNB_A 45 obtains from MME_A 104 and MME_B 106.

[00256] Additionally, the 23a identification information group may be a list of information to identify a degree of independence of the network slice in which the MME to which the eNB_A 45 connects is included. In other words, the 23a identification information Petition 870240027939, dated 01 / 04 / 2024, p. 53 / 137 49 / 121 identification can be a list of the degree of independence of the NF (network function) included in the network slice.

[00257] For example, as illustrated in the drawing, in a case where eNB_A 45 connects to both MME_A 104 included in network slice_A and MME_B 106 included in network slice_B, the ninth identification information group can be updated by including a degree of independence with respect to network slice_A and a degree of independence with respect to network slice_B. The second identification information group can be formed by one or more items of information from the second identification information that eNB_A 45 obtains from MME_A 104 and MME_B 106.

[00258] eNB_A 45 receives the RRC message and / or the fifth identification information from UE_A 10.

[00259] Based on the fifth identification information being included in the RRC message received from UE_A 10, eNB_A 45 transmits the RRC message to UE_A 10 (S706) as a reply, including in the message the eighth identification information group and / or the ninth identification information group and / or the 23rd identification information group.

[00260] In a case where the RRC message received by eNB_A 45 from UE_A 10 is the RRC connection request message, the RRC message as a response may be an RRC connection configuration message.

[00261] Additionally, eNB_A 45 may include a tenth piece of identifying information or an eleventh piece of identifying information in the RRC message as a response.

[00262] The tenth piece of identifying information is information to identify a connection mode with the network slice that is authenticated in relation to the UE, and may be identifying information indicating the mode in which the UE connects to only Petition 870240027939, dated 01 / 04 / 2024, p. 54 / 137 50 / 121 a network slice is allowed. In other words, here, the identification information may be to indicate that eNB_A 45 allows UE_A 10 to connect to only one network slice.

[00263] The identification information is information to identify a connection mode with the network slice that is authenticated in relation to the UE, and may be identification information indicating that the mode in which the UE connects to one or more network slices is permitted. In other words, here, the identification information may indicate that eNB_A 45 allows UE_A 10 to connect to multiple network slices.

[00264] UE_A 10 receives, from eNB_A 45, the reply message and / or the eighth group of identification information and / or the ninth group of identification information and / or the 23rd group of identification information.

[00265] Through the procedures described above, eNB_A 45 obtains the network slice type supported by the network slice in which each MME is included from each MME. Additionally, eNB_A 45 can notify UE_A 10, based on the notification from UE_A 10 that supports connection to the network slice and / or that UE_A 10 has a function to select the network slice type, the network slice type supported by eNB_A 45 and / or the network slice ID. It should be noted that the network slice type and / or network slice ID that eNB_A 45 notifies UE_A 10 may be a group of information formed by the various network slice types and / or network slice IDs. 1.3.2. Connection procedure

[00266] A connection procedure will be described below. Figure 8 illustrates an example of the connection procedure according to this embodiment.

[00267] UE_A 10 selects the network slice type and / or network slice based on RRC message reception and / or reception Petition 870240027939, dated 01 / 04 / 2024, page 55 / 137 51 / 121 of the eighth identification information group and / or the ninth identification information group originating from eNB_A 45 (S800). UE_A 10 can select the network slice type and / or the network slice to be requested based on the network slice type or the UE usage type that UE stores.

[00268] UE_A 10 can select the network slice type and / or the network slice, in a case where eNB_A 45 does not support the network slice type and / or the network slice that UE itself stores, among the network slice types notified by eNB_A 45.

[00269] Note that UE_A 10 may not select the network slice type and / or the network slice.

[00270] UE_A 10 transmits a connection request message to eNB_A 45 (S802). UE_A 10 may include a 12th identification piece of information and / or a 13th identification piece of information and / or a 14th identification piece of information in the RRC message with the connection request message and transmit them.

[00271] The 12th identification information may be information to identify the type of network slice requested by the UE. In the case where UE_A 10 selects the type of network slice, the information may be to identify the selected type of network slice from among the various information items of the first identification information included in the eighth identification information group received by UE_A 10 from eNB_A 45. Alternatively, if UE_A 10 does not select the type of network slice in the eighth identification information group notified from the network, the 12th identification information may be information to identify the type of network slice stored in the UE.

[00272] The identification information 13 may be information to identify the network slice requested by the UE. In the case where UE_A 10 selects the network slice, the information may be for Petition 870240027939, dated 01 / 04 / 2024, page 56 / 137 52 / 121 identify the selected network slice from among the various items of information of the third identification information included in the ninth identification information group received by UE_A 10 from eNB_A 45. Alternatively, if UE_A 10 does not select the network slice in the ninth identification information group notified from the network, the 13th identification information may be information to identify the network slice stored in UE.

[00273] The 14th identification information may be the degree of independence of the network slice requested by the UE. In other words, the 14th identification information may be the degree of independence of the NF (network function) included in the network slice requested by the UE.

[00274] For example, the 14a identification information can be information that indicates the degree of independence of the MME in relation to other network slices. In the present embodiment, since the MME can be included in one or more network slices, the number of network slices in which the MME is included can be managed while being made to correspond to the degree of independence. Specifically, for example, in a case where MME_A 104 belongs to network slice_A and is independent of other network slices, the isolation level can be made to be level 2. On the other hand, in a case where MME_A 104 belongs to network slice_A and network slice_B and MME_A 104 is not independent of other network slices (network slice_B in this case), the isolation level can be level 1. In other words, the 14a identification information can be information that indicates the degree of independence of the MME.

[00275] Additionally, UE_A 10 can transmit the connection request message, including in the message at least the IMSI or globally unique temporary identity (GUTI), the UE network capability and an EPS session management (ESM) message container. Petition 870240027939, dated 01 / 04 / 2024, page 57 / 137 53 / 121

[00276] The ESM message container is a message container for transmitting a session management message with a mobility management message, such as a connection request message, or similar. Specifically, for example, UE_A 10 can transmit the ESM message container, including within it a PDN connectivity request message.

[00277] UE_A 10 may include the 12th identification information and / or the 13th identification information and / or the 14th identification information, and / or additionally a sixth identification information or a seventh identification information in the connection request message and transmit them. Specifically, the PDN connectivity request message may include the 12th identification information and / or the 13th identification information and / or the 14th identification information, and the sixth identification information or the seventh identification information.

[00278] The sixth identifying information may be identifying information indicating that the UE requests a mode to connect to only one network slice, and / or that the UE can connect to only one network slice. The sixth identifying information may be UE preference information. It should be noted that the sixth identifying information may be information indicating the mode of connection to only one network slice.

[00279] The seventh identifying information may be identifying information indicating that the UE requests a mode to connect to one or more network slices, and / or that the UE can connect to one or more network slices. The seventh identifying information may also be UE preference information. It should be noted that the seventh identifying information may be information to identify a mode indicating that the connection can Petition 870240027939, dated 01 / 04 / 2024, page 58 / 137 54 / 121 can be made to one or more slices of the network.

[00280] eNB_A 45 receives the RRC message and / or the connection request message transmitted by UE_A 10.

[00281] eNB_A 45 selects the network slice type and / or network slice based on receiving the connection request message and / or the 12aidentification information and / or the 13aidentification information from UE_A 10 (S804).

[00282] Specifically, for example, in a case where the identification information to identify network slice type_A is received as the 12th identification information from UE_A 10, eNB_A 45 determines the selection of the MME from a list of MMEs that support network slice type_A. eNB_A 45 can select the MME based on the MMEGI linked to the network slice type identified by the 12th identification information. Here, the MMEGI can be the fourth identification information.

[00283] Additionally, in a case where the identification information to identify network slice_A is received as the 13th identification information from UE_A 10, eNB_A 45 determines the selection of the MME from a list of MMEs included in network slice_A.

[00284] Additionally, if UE_A 10 does not transmit the 12a identification information and / or the 13a identification information with the connection request message, or if the MME that supports the network slice type identified by the 12a identification information and / or the MME included in the network slice identified by the 13a identification information transmitted by UE_A 10 with the connection request message cannot be selected, eNB_A 45 may select an MME included in a standard network slice.

[00285] In addition, eNB_A 45 selects the isolation level. Petition 870240027939, dated 01 / 04 / 2024, page 59 / 137 55 / 121 based on receipt of the connection request message and / or the identification information from UE_A 10 (S804).

[00286] Specifically, for example, in the case where the identification information indicating that the isolation level is level 2 is received as the 14th identification information from UE_A 10, eNB_A 45 additionally selects the MME whose isolation level is at least level 2 or higher from a list of MMEs selected by the network slice type selection.

[00287] It should be noted that, in the event that the MME that supports the isolation level identified by the identification information received from UE_A 10 cannot be selected from the list of MMEs, eNB_A 45 may select an alternative MME, such as selecting an MME that supports the highest degree of independence, or similar.

[00288] In a case where UE_A 10 does not transmit the 14a identification information with the connection request message, the MME selection made based on the isolation level may not be executed.

[00289] Additionally, besides the selection of the MME based on the 12a, 13a and 14a identification information, eNB_A 45 can select the MME according to a physical location or a load state for each MME resource, as in an existing method.

[00290] Through the procedures described above, eNB_A 45 selects an MME to be a transfer destination for the connection request message. In other words, eNB_A 45 selects a network slice to which UE_A 10 connects. Furthermore, eNB_A 45 can select a degree of independence from the network slice to which UE_A 10 connects. From this point forward in this document, it is assumed that the MME selected by eNB_A 45 is MME_A 104. In other words, it is assumed that eNB_A Petition 870240027939, dated 01 / 04 / 2024, page 60 / 137 56 / 121 selects network slice_A as the network slice, and level 2 as the isolation level.

[00291] Next, eNB_A 45 transmits a connection request message to MME_A 104 (S806). eNB_A 45 can then transfer the received connection request message to MME_A 104.

[00292] The eNB_A 45 can transmit the 12aidentification information and / or the 13aidentification information and / or the 14aidentification information obtained from the UE_A 10 with the connection request message, including this information in a control message.

[00293] MME_A 104 receives the connection request message and / or the control message transmitted by UE_A 10 from eNB_A 45.

[00294] In a case where there is no UE context for UE_A 10, MME_A 104 executes an authentication procedure for HSS_A 50 and UE_A 10 (S808). MME_A 104 generates the UE context for UE_A 10 through the authentication procedure and then stores it.

[00295] At this point, MME_A 104 can obtain, from HSS_A 50, the UE usage type and / or the network slice type and / or the UE_A 10 network slice identification information.

[00296] Alternatively, using a procedure other than the authentication procedure, MME_A 104 can obtain, from the HSS, the UE usage type and / or the network slice type and / or the network slice ID.

[00297] Additionally, if the sixth or seventh identification information is received from eNB_A 45, MME_A 104 can determine a connection mode that is permitted for UE_A 10 in the authentication procedure. Specifically, in a case where MME_A 104 obtains the sixth identification information from Petition 870240027939, dated 01 / 04 / 2024, p. 61 / 137 57 / 121 identification of eNB_A 45, a mode in which only one PDN connection is allowed, can be allocated to UE_A 10 from the registration information and network capacity of UE. Similarly, in a case where MME_A 104 obtains the seventh identification information of eNB_A 45, a mode in which multiple PDN connections can be established through one or more network slices can be allocated to UE_A 10 from the registration information and network capacity of UE.

[00298] The authentication procedure is completed, and then MME_A 104 selects the SGW and PGW and executes a session creation procedure with the SGW and PGW (S810).

[00299] Specifically, for example, MME_A 104 transmits a first session creation message to SGW_A 35, and SGW_A 35 transmits, based on the first session creation request message received, a second session creation request message to PGW_A 30. Additionally, PGW_A 30 transmits a first session creation response message to SGW_A 35, and SGW_A 35 transmits a second session creation response message to MME. Through the procedures described above, a carrier is established between MME_A 104 and SGW_A 35 and PGW_A 30.

[00300] It should be noted that, in the case of obtaining from eNB_A 45 the 12th identification information and / or the 13th identification information and / or the 14th identification information, MME_A 104 may select the SGW and / or the PGW based on said identification information.

[00301] MME_A 104 transmits a connection acceptance message to eNB_A 45 to transmit it to UE_A 10 based on the completion of the session creation procedure (S812).

[00302] MME may include identification information. Petition 870240027939, dated 01 / 04 / 2024, page 62 / 137 58 / 121 and / or identification information and / or identification information in the connection acceptance message and transmit them. In addition, MME_A 104 may additionally transmit identification information and / or identification information and / or identification information separately from the connection acceptance message.

[00303] Here, the 15a identification information may be information to identify the type of network slice to which the network allows the UE to connect. Specifically, the information may be to identify the type of network slice supported by the MME selected by eNB_A 45. Here, the identification information may be to identify the type of network slice through the connection established in this connection procedure. In other words, the 15a identification information may be information to identify the type of network slice for which the connection is authenticated by the network in the connection procedure. The 15a identification information may be information indicating the type of network slice that is identical to that of the 12a identification information.

[00304] The 16th identification information may be information to identify the network slice to which the network allows the UE to connect. Specifically, the information may be to identify the network slice in which the MME selected by eNB_A 45 is included. Here, the identification information may be to identify the network slice through the connection established in this connection procedure. In other words, the 16th identification information may be the identification information to identify the network slice to which the connection is authenticated by the network in the connection procedure. The 16th identification information may be information indicating the network slice that is identical to that of the 13th identification information. Petition 870240027939, dated 01 / 04 / 2024, page 63 / 137 59 / 121

[00305] Additionally, the 17th identification information can be the degree of independence (isolation level) of the network slice. In other words, the 17th identification information can be the degree of independence of the NF (network function) included in the network slice.

[00306] For example, the 17a identification information can be information that indicates the degree of independence of the MME in relation to other network slices. In the present embodiment, since the MME can be included in one or more network slices, the number of network slices in which the MME is included can be managed while being made to correspond to the degree of independence. Specifically, for example, in the case where MME_A 104 belongs to network slice_A 101 and is independent of other network slices, the isolation level can be made to be level 2. On the other hand, in the case where MME_A 104 belongs to network slice_A 101 and network slice_B 102 and MME_A 104 is not independent of other network slices (network slice_B in this case), the isolation level can be level 1. In other words, the 17a identification information can be information that indicates the degree of independence of the MME.

[00307] Here, the information may indicate the degree of independence in the connection established in this connection procedure in relation to the network slice belonging to the network slice type beyond the network slice type identified by the 15th identification information and / or the network slice beyond the network slice identified by the 16th identification information. The degree of independence identified by the 17th identification information may be identical to the degree of independence identified by the 14th identification information. Additionally, the degree of independence identified by the 17th identification information may be a degree of independence that is greater than the degree of independence identified by the 14th identification information. Petition 870240027939, dated 01 / 04 / 2024, page 64 / 137 60 / 121 identification information.

[00308] In addition, MME_A 104 may additionally include the tenth identification information or the 11th identification information in the connection acceptance message.

[00309] The tenth identification information is information to identify the connection mode to the network slice that is authenticated by the network in relation to the UE, and may be an identification information indicating that the mode in which the UE connects to only one network slice is allowed. In other words, here, the identification information may indicate that MME_A 104 allows UE_A 10 to connect to only one network slice.

[00310] The identification information is information to identify the connection mode to the network slice that is authenticated by the network in relation to the UE, and may be identification information indicating that the mode in which the UE connects to one or more network slices is permitted. In other words, here, the identification information may indicate that the MME allows UE_A 10 to connect to multiple network slices.

[00311] It should be noted that MME_A 104 may transmit the tenth identification information or the 11th identification information, including this information in the connection acceptance message based on the sixth identification information or the seventh identification information included in the connection request message received from UE_A 10.

[00312] MME_A 104 may transmit the 15th identification information and / or the 16th identification information and / or the 17th identification information and / or the tenth identification information or the 11th identification information through a message independent of the connection acceptance message. Specifically, for example, MME_A 104 may transmit to Petition 870240027939, dated 01 / 04 / 2024, page 65 / 137 61 / 121 eNB_A 45 an initial context configuration request message in which the connection acceptance message is included, including in the message the 15th identification information and / or the 16th identification information and / or the 17th identification information and / or the tenth identification information or the 11th identification information.

[00313] Alternatively, MME_A 104 may transmit the 15th identification information and / or the 16th identification information and / or the 17th identification information and / or the tenth identification information or the 11th identification information, including such information in a standard EPS carrier context activation request message in the ESM message container included in the connection acceptance message.

[00314] It should be noted that the connection acceptance message may also include the APN, the GUTI, a PDN address (the UE IP address), the EPS carrier ID and the ESM message recipient.

[00315] eNB_A 45 receives the connection acceptance message transmitted by MME_A 104.

[00316] Based on the connection acceptance message received from MME_A 104, eNB_A 45 transmits the connection acceptance message to UE_10 (S814).

[00317] The eNB_A 45 can transmit the 15th identification information and / or the 16th identification information and / or the 17th identification information and / or the tenth identification information or the 11th identification information through a message independent of the connection acceptance message. Specifically, for example, the RRC message transmitted with the connection acceptance message can be transmitted while including the 15th identification information and / or the 16th identification information. Petition 870240027939, dated 01 / 04 / 2024, page 66 / 137 62 / 121 identification and / or the 17th identification information and / or the tenth identification information or the 11th identification information.

[00318] Alternatively, eNB_A 45 may transmit the 15th identification information and / or the 16th identification information and / or the 17th identification information and / or the tenth identification information or the 11th identification information, including such information in the standard EPS carrier context activation request message included in the connection acceptance message.

[00319] UE_A 10 receives the connection acceptance message transmitted by MME_A 104 via eNB_A 45.

[00320] Based on the reception of the connection acceptance message, UE_A 10 reconfigures the RRC connection between eNB_A 45 and UE_A 10, transmits a connection completion message to MME_A 104, and establishes the PDN connection. Specifically, UE_A 10 transmits an RRC connection reconfiguration completion message to eNB_A 45, and eNB_A 45 transmits an initial context response message to MME_A 104. Here, the initial context response message may include the TEID of eNB_A 45 or a downlink address of eNB_A 45. Additionally, UE transmits the connection completion message to MME via eNB_A 45.

[00321] As described above, UE_A 10 can establish the PDN connection through network slice_A. In other words, UE_A 10 can connect to network slice_A. Furthermore, UE_A 10 can determine whether it wants to continue an additional PDN connectivity procedure based on receiving the tenth identification information or the eleventh identification information from the network. Specifically, if UE_A 10 obtains the tenth identification information, it can be determined that it does not Petition 870240027939, dated 01 / 04 / 2024, page 67 / 137 63 / 121 the PDN connectivity request message is transmitted to the network to establish the additional PDN connection, and if UE_A 10 obtains the 11a identification information, it can be determined that UE_A 10 transmits the PDN connectivity request message to the network. 1.3.3. TAU Procedure

[00322] A Tracking Area Update (TAU) procedure will be described below for UE_A that establishes the PDN connection through network slice_A. 1.3.3.1. First TAU ​​procedure

[00323] Figure 9 illustrates a first TAU ​​procedure. In the first TAU ​​procedure, a case will be described in which UE_A 10 can establish the PDN connection through the network slice with the network slice type as requested in the previous connection procedure or the TAU, and, in addition, a case will be described in which the requested network slice type and / or isolation level are not changed in a synchronization of the trace area update.

[00324] UE_A 10 transmits a TAU request message to eNB_A 45 (S900). Along with the TAU request message, UE_A 10 may transmit 18aidentification information and / or 19aidentification information. Specifically, for example, the RRC message in which the TAU request message is included may include the 18aidentification information and / or the 19aidentification information. Alternatively, an RRC parameter transmitted with the TAU request message may be transmitted while the 18aidentification information and / or the 19aidentification information are included in the message.

[00325] The 18 identification information may be information indicating that UE_A 10 requests a connection to the network slice, a Petition 870240027939, dated 01 / 04 / 2024, p. 68 / 137 64 / 121 information indicating that UE_A 10 has a function to select the type of network slice and / or the network slice, or information obtained by combining this information. The 18th identification information may be the UE capacity information. A UE function indicated by the 18th identification information may be identical to the UE function indicated by the fifth identification information.

[00326] Here, the 19a identification information may be information indicating that UE_A 10 does not request a change in the network slice type and / or isolation level. Alternatively, the 19a identification information may be information indicating whether UE_A 10 requests a change in the network slice type and / or isolation level. In other words, the 19a identification information may be information indicating that UE_A 10 requests a change in the network slice type and / or isolation level, or it may be information indicating that there is no request for a change. In this case, in the following descriptions, the 19a identification information may indicate that UE_A 10 does not request a change in the network slice type and / or isolation level.

[00327] Alternatively, the 19a identification information may be the GUMMEI. Based on the 19a identification information, which is identical to the GUMMEI to identify the MME that performs mobility management for UE_A 10, eNB_A 45 can detect that the change in network slice type is not requested.

[00328] In addition, the TAU request message includes at least one old GUTI. The old GUTI is information used to identify the MME to which UE_A 10 connects in the most recent connection procedure.

[00329] UE_A 10 may additionally include the sixth identification information or the seventh identification information in the TAU request message. Petition 870240027939, dated 01 / 04 / 2024, p. 69 / 137 65 / 121

[00330] The sixth identifying information may be identifying information indicating that the UE requests a mode to connect to only one network slice, and / or the UE can connect to only one network slice. The sixth identifying information may be the UE's preference information. Additionally, the sixth identifying information may be information that identifies the mode to connect to only one network slice.

[00331] Additionally, the seventh identifying information may be identifying information indicating that the UE requests a mode to connect to one or more network slices, and / or that the UE may connect to one or more network slices. The seventh identifying information may also be information regarding the UE's preference. Additionally, the seventh identifying information may be information that identifies the mode in which the UE connects to one or more network slices.

[00332] eNB_A 45 receives the TAU request message transmitted by UE_A 10.

[00333] Based on the receipt of the TAU request message and the identification information from UE_A 10, eNB_A 45 may not perform the re-selection of a new MME, and may transfer the TAU request message to MME_A 104 (S902).

[00334] Additionally, in the event that eNB_A 45 cannot use MME_A 104 based on identification information 18 and / or identification information 19, eNB_A 45 may perform MME re-selection and transmit the TAU request message for the selected MME.

[00335] eNB_A 45 can transmit an UPWARD LINK NAS TRANSPORT with the TAU request message. Alternatively, the TAU request message can be Petition 870240027939, dated 01 / 04 / 2024, p. 70 / 137 66 / 121 included in the UPWARD LINK NAS TRANSPORT. The UPWARD LINK NAS TRANSPORT includes at least the MME EU S1AP ID, the eNB EU S1AP ID, the TAU request message, an E-UTRAN CGI, and the TAI.

[00336] Here, the MME UE S1AP ID is information used to identify a connection to the UE in MME.

[00337] Additionally, the eNB UE S1AP ID is information used to identify a connection to the UE on the eNB. The E-UTRAN CGI is information used to identify a cell.

[00338] TAI is information used to identify the tracking area.

[00339] MME_A 104 receives the TAU request message transmitted by UE_A 10 through eNB_A 45.

[00340] MME_A 104 updates the tracking area identifier of the last tracking area update (TAI of last TAU) in the storage unit based on the receipt of the TAU request message. Whether SGW re-selection is necessary is discussed. In case of SGW change, a session creation request message can be transmitted to a new SGW. Furthermore, the newly selected SGW can transmit a bearer modification request message to PGW_A 30, as indicated by the session creation request message. PGW_A 30 transmits a bearer modification reply message to the new SGW, and the new SGW can also transmit a session creation reply message to MME_A 104.

[00341] Additionally, if MME_A 104 decides not to perform the SGW re-selection, or based on the establishment of a connection between MME_A 104 and the SGW / PGW, MME_A 104 may transmit a TAU acceptance message to the UE via eNB_A 45 (S904). Petition 870240027939, dated 01 / 04 / 2024, p. 71 / 137 67 / 121

[00342] MME_A 104 may transmit the TAU acceptance message, including the 15a identification information and / or the 16a identification information and / or the 17a identification information.

[00343] Here, the 15a identification information may be information to identify the type of network slice to which the network allows the UE to connect. Specifically, the information may be to identify the type of network slice supported by the MME selected by eNB_A 45. Here, the identification information may be to identify the type of network slice through the connection established in the TAU procedure. In other words, the 15a identification information may be identification information to identify the type of network slice for which the connection is authenticated by the network in the TAU procedure.

[00344] The 16a identification information may be information to identify the network slice to which the network allows the UE to connect. Specifically, the information may be to identify the network slice in which the MME selected by eNB_A 45 is included. Here, the identification information may be to identify the network slice through the connection established in the TAU procedure. In other words, the 16a identification information may be the identification information to identify the network slice to which the connection is authenticated by the network in the TAU procedure.

[00345] Additionally, the 17th identification information can be the degree of independence of the network slice. In other words, the 17th identification information can be the degree of independence of the NF (network function) included in the network slice.

[00346] For example, the 17th identification information may be information that indicates the degree of independence of the MME in relation to other network slices. In the present embodiment, as the MME may be included in one or more network slices, the number of Petition 870240027939, dated 01 / 04 / 2024, p. 72 / 137 68 / 121 network slices in which the MME is included can be managed while being made to match the degree of independence. Specifically, for example, in the case where MME_A 104 belongs to network slice_A 101 and is independent of other network slices, the isolation level can be set to level 2. On the other hand, in the case where MME_A 104 belongs to network slice_A 101 and network slice_B 102 and MME_A 104 is not independent of other network slices (network slice_B in this case), the isolation level can be set to level 1. In other words, the 17 identification information can be information that indicates the degree of independence of the MME.

[00347] Here, the information may be to indicate the degree of independence in the connection established in the TAU procedure in relation to the network slice with the network slice type in addition to the network slice type identified by the 15th identification information and / or the network slice identified by the 16th identification information.

[00348] Alternatively, MME_A 104 may independently transmit the TAU acceptance message, and the 15a identification information and / or the 16a identification information and / or the 17a identification information.

[00349] Specifically, MME_A 104 may transmit to eNB_A 45 the 15th identification information and / or the 16th identification information and / or the 17th identification information with the TAU acceptance message. eNB_A 45 transmits to UE_A 10, based on the receipt of the TAU acceptance message, the 15th identification information and / or the 16th identification information and / or the 17th identification information with the TAU acceptance message. In other words, eNB_A 45 may include, in the RRC message, the TAU acceptance message and the 15th identification information and / or the 16th identification information and / or the 17th identification information. Petition 870240027939, dated 01 / 04 / 2024, p. 73 / 137 69 / 121 identification and transmit them to UE_A10.

[00350] Additionally, in the case where MME_A 104 is the new MME modified through the TAU procedure, MME_A 104 may transmit the TAU acceptance message, including the GUTI.

[00351] If the new GUTI is included in the TAU acceptance message, UE_A 10 transmits a completed TAU message to MME_A 104.

[00352] As described above, UE_A 10 can execute the TAU procedure in which the network slice type and isolation level are not changed. 1.3.3.2. Second TAU procedure

[00353] A second TAU procedure will be described below. Figure 10 illustrates a second TAU procedure. In the second TAU procedure, a case will be described where UE_A cannot establish the PDN connection through the network slice with the network slice type as requested by UE in the previous connection procedure, and / or a case where the connection is not the connection with the isolation level as requested by UE, or a case where the network slice type and / or the isolation level requested by UE are changed in relation to the previous TAU procedure or the connection procedure.

[00354] UE_A 10 transmits the TAU request message to eNB_A 45 (S1000). The TAU request message includes at least the old GUTI.

[00355] UE_A 10 may transmit the 12th identification information and / or the 13th identification information and / or the 14th identification information and / or the 18th identification information and / or the 20th identification information with the TAU request message. Specifically, for example, UE_A 10 may include the 12th Petition 870240027939, dated 01 / 04 / 2024, p. 74 / 137 70 / 121 identification information and / or 13th identification information and / or 14th identification information and / or 18th identification information and / or 20th identification information in the transmitted RRC message, including the TAU request message. Alternatively, the EU may include 12th identification information and / or 13th identification information and / or 14th identification information and / or 18th identification information and / or 20th identification information in the transmitted RRC parameter with the TAU request message and transmit them.

[00356] In addition, UE_A 10 may include the sixth identification information or the seventh identification information in the RRC message.

[00357] The 12th identification information may be information to identify the type of network slice requested by the UE. In the case where UE_A 10 selects the type of network slice, the information may be to identify the selected type of network slice from among the various information items of the first identification information included in the eighth identification information group received by UE_A 10 from eNB_A 45. Alternatively, if UE_A 10 does not select the type of network slice in the eighth identification information group notified from the network, the 12th identification information may be information to identify the type of network slice stored in the UE.

[00358] The 13th identification information may be information to identify the network slice requested by the UE. In the case where UE_A 10 selects the network slice, the information may be to identify the selected network slice from among the various items of information of the third identification information included in the ninth identification information group received by UE_A 10 from eNB_A 45. Alternatively, if UE_A 10 does not select the slice of Petition 870240027939, dated 01 / 04 / 2024, page 75 / 137 71 / 121 network in the ninth group of identification information notified from the network, the 13th identification information may be information to identify the network slice stored in the EU.

[00359] The 14th identification information may be the degree of independence of the network slice requested by the UE. In other words, the 14th identification information may be the degree of independence of the NF (network function) included in the network slice requested by the UE.

[00360] For example, the 14th identification information can be information that indicates the degree of independence of the MME in relation to other network slices. In the present embodiment, since the MME can be included in one or more network slices, the number of network slices in which the MME is included can be managed while being made to correspond to the degree of independence. Specifically, for example, in the case where MME_A 104 belongs to network slice_A and is independent of other network slices, the isolation level can be made to be level 2. On the other hand, in a case where MME_A 104 belongs to network slice_A and network slice_B and MME_A 104 is not independent of other network slices (network slice_B in this case), the isolation level can be level 1. In other words, the 14th identification information can be information that indicates the degree of independence of the MME.

[00361] The sixth identifying information may be identifying information indicating that the UE requests a mode to connect to only one network slice, and / or the UE can connect to only one network slice. The sixth identifying information may be the UE's preference information. Additionally, the sixth identifying information may be information that identifies the mode in which the UE connects to only one network slice.

[00362] Additionally, the seventh piece of identifying information may be identifying information indicating that the EU requests a Petition 870240027939, dated 01 / 04 / 2024, page 76 / 137 72 / 121 mode for connecting to one or more network slices, and / or that the UE can connect to one or more network slices. The seventh identification information may also be UE preference information. Additionally, the seventh identification information may also be information that identifies the mode in which the UE connects to one or more network slices.

[00363] The 18th identification information may be information indicating that UE_A 10 requests a connection to the network slice, information indicating that UE_A 10 has a function to select the type of network slice and / or the network slice, or information obtained by combining these pieces of information. The 18th identification information may be UE capability information. A UE function indicated by the 18th identification information may be identical to the UE function indicated by the fifth identification information.

[00364] Here, the 20a identification information may be information indicating that UE_A 10 requests a change in the network slice type and / or isolation level. Alternatively, the 20a identification information may be information indicating whether UE_A 10 requests a change in the network slice type and / or isolation level. In other words, the 20a identification information may be information indicating that UE_A 10 requests a change in the network slice type and / or isolation level, or it may be information indicating that there is no request for a change. In this case, in the following descriptions, the 20a identification information may indicate that UE_A 10 requests a change in the network slice type and / or isolation level.

[00365] Alternatively, the 20a identification information may be the GUMMEI. If the 20a identification information is empty, eNB_A 45 may, based on this fact, detect that a change in the network slice type is requested. Petition 870240027939, dated 01 / 04 / 2024, page 77 / 137 73 / 121

[00366] In addition, UE_A 10 may additionally include the 12th identification information and / or the 13th identification information and / or the 14th identification information and / or the 18th identification information and the 20th identification information in the TAU request message and transmit them.

[00367] eNB_A 45 initiates the re-selection of the network slice type and / or network slice based on the receipt of the TAU request message and / or the RRC message originating from UE_A 10 (S1002). Specifically, eNB_A 45 may initiate the re-selection of the network slice type and / or network slice based on the receipt of the 12th identification information and / or the 13th identification information.

[00368] eNB_A 45 reselects the MME by reselecting the network slice type and the network slice. The MME can be selected based on the 14a identification information in the reselect.

[00369] A specific method for selecting MME by eNB_A 45 is the same as the connection procedure and, therefore, detailed descriptions of it will be omitted.

[00370] Next, an example will be described of a case in which MME_D 105 is reselected as a new MME.

[00371] eNB_A 45 transfers the TAU request message to MME_D 105. eNB_A 45 can transmit the uplink NAS transport with the TAU request message. Alternatively, the TAU request message can be included in the uplink NAS transport. The uplink NAS transport includes at least the MME UE S1AP ID, the eNB UE S1AP ID, the TAU request message, an E-UTRAN CGI, and the TAI.

[00372] Here, the MME UE S1AP ID is information used to identify a connection to the UE in MME. Petition 870240027939, dated 01 / 04 / 2024, p. 78 / 137 74 / 121

[00373] Additionally, the eNB UE S1AP ID is information used to identify a connection to the UE on the eNB. The E-UTRAN CGI is information used to identify a cell.

[00374] TAI is information used to identify the tracking area.

[00375] MME_D 105 receives the TAU request message transmitted by UE_A 10 via eNB_A 45.

[00376] Based on the GUTI included in the TAU request message, MME_D 105 transmits a context request message to MME_A 104, and receives a context response message (S1006).

[00377] Based on this, the context response message includes at least the MM context of UE_A 10 and, through the procedure described above, MME_D 105 can obtain the MME context from MME_A 104.

[00378] MME_D 105 discusses whether SGW re-selection is necessary based on obtaining the MME context. In case of SGW change, the session creation request message can be transmitted to a new SGW (S1008). Furthermore, the newly selected SGW can transmit to PGW_A 30 the carrier modification request message, indicated by the session creation request message. PGW_A 30 transmits the carrier modification response message to the new SGW, and in addition, the new SGW can transmit the session creation response message to MME_D 105.

[00379] Additionally, these procedures between MME_D 105 and SGW / PGW may be the session creation procedure.

[00380] MME_D 105 completes the establishment of a connection between MME_D 105 and SGW / PGW with the termination of the session creation procedure. Petition 870240027939, dated 01 / 04 / 2024, page 79 / 137 75 / 121

[00381] MME_D 105 starts a location update procedure upon completion of the session creation procedure (S1010).

[00382] Specifically, MME_D 105 transmits a location update message to HSS_A 50. The location update message may include at least the IMSI and PLMN of UE_A 10. With this, HSS_A 50 detects that the mobility management device of UE_A 10 is changed from MME_A 104 to MME_D 105.

[00383] HSS_A 50 transmits a site cancellation message requesting that MME_A 104 remove the MM context. The site cancellation message includes at least the IMSI.

[00384] In addition, HSS_A 50 transmits a location update acknowledgment to MME_D 105. Based on the receipt of the location update acknowledgment, MME_D 105 is authenticated by HSS_A 50 as the mobility management device for a new UE_A 10.

[00385] Through the procedure described above, MME_D 105, MME_A 104 and HSS_A 50 can complete the location update procedure.

[00386] Based on the completion of the location update procedure, or the determination that the SGW is not changed after S1006, MME_D 105 can transmit the TAU acceptance message to UE_A 10 via eNB_A 45 (S1012).

[00387] MME_D 105 may include the 15th identification information and / or the 16th identification information and / or the 17th identification information in the TAU acceptance message and transmit them.

[00388] Here, the 15a identification information may be information to identify the type of network slice to which the network allows the UE to connect. Specifically, the information may be to identify the type of network slice supported by the MME. Petition 870240027939, dated 01 / 04 / 2024, p. 80 / 137 76 / 121 selected by eNB_A 45. Here, the identification information can be used to identify the type of network slice through the connection established in the TAU procedure. In other words, the identification information can be used to identify the type of network slice for which the connection is authenticated by the network in the TAU procedure.

[00389] The 16a identification information may be information to identify the network slice to which the network allows the UE to connect. Specifically, the information may be to identify the network slice in which the MME selected by eNB_A 45 is included. Here, the identification information may be to identify the network slice through the connection established in this TAU procedure. In other words, the 16a identification information may be the identification information to identify the network slice to which the connection is authenticated by the network in the TAU procedure.

[00390] Additionally, the 17th identification information can be the degree of independence of the network slice. In other words, the 17th identification information can be the degree of independence of the NF (network function) included in the network slice.

[00391] For example, the identification information can be information that indicates the degree of independence of the MME in relation to other network slices. In the present embodiment, since the MME can be included in one or more network slices, the number of network slices in which the MME is included can be managed while being made to correspond to the degree of independence. Specifically, for example, in the case where MME_D 105 belongs to network slice_A 101 and is independent of other network slices, the isolation level can be made to be level 2. On the other hand, in the case where MME_D 105 belongs to network slice_A 101 and network slice_B 102 and MME_D 105 is not independent of others Petition 870240027939, dated 01 / 04 / 2024, page 81 / 137 77 / 121 network slices (network slice_B in this case), the isolation level could be level 1. In other words, the 17th identification information could be information indicating the degree of independence of the MME.

[00392] Here, the information may be to indicate the degree of independence in the connection established in the connection procedure in relation to the network slice with the network slice type in addition to the network slice type identified by the 15th identification information and / or the network slice identified by the 16th identification information.

[00393] In addition, MME_D 105 may additionally include the tenth identification information or the 11th identification information in the TAU acceptance message.

[00394] The tenth identifying information is information to identify the connection mode to the network slice that is authenticated by the network in relation to the UE, and may be identifying information indicating that the mode in which the UE connects to only one network slice is allowed. In other words, here, the identifying information may indicate that MME_D 105 allows UE_A 10 to connect to only one network slice.

[00395] The identification information is information to identify the connection mode to the network slice that is authenticated by the network in relation to the UE, and may be identification information indicating that the mode in which the UE connects to one or more network slices is permitted. In other words, here, the identification information may indicate that the MME allows UE_A 10 to connect to multiple network slices.

[00396] Alternatively, MME_D 105 may independently transmit the TAU acceptance message, and the 15a identification information and / or the 16a identification information and / or the 17a identification information. Petition 870240027939, dated 01 / 04 / 2024, p. 82 / 137 78 / 121

[00397] Specifically, MME_D 105 can transmit to eNB_A 45 the 15a identification information and / or the 16a identification information and / or the 17a identification information with the TAU acceptance message.

[00398] eNB_A 45 receives the TAU acceptance message transmitted by MME_D 105.

[00399] eNB_A 45 transmits to UE_A 10, based on the receipt of the TAU acceptance message, the 15th identification information and / or the 16th identification information and / or the 17th identification information with the TAU acceptance message. In other words, eNB_A 45 can transmit to UE_A 10 the RRC message, including the TAU acceptance message, and the 15th identification information and / or the 16th identification information and / or the 17th identification information.

[00400] Additionally, MME_D 105 can allocate a new GUTI to UE_A 10, and can transmit the TAU acceptance message, including the new GUTI in the message.

[00401] If the new GUTI is included in the TAU acceptance message, UE_A 10 transmits the completed TAU message to MME_A 104.

[00402] As described above, UE_A 10 can execute the TAU procedure with the change in network slice type and / or isolation level. 1.3.3.3. TAU Trigger

[00403] A TAU trigger will be described below using Figure 11.

[00404] It should be noted that UE_A 10 can initiate a periodic TAU procedure separately from a TAU procedure with a trigger, which will be described below, after the connection procedure is completed. Petition 870240027939, dated 01 / 04 / 2024, p. 83 / 137 79 / 121

[00405] Alternatively, as described below, UE_A 10 may initiate the TAU procedure based on receipt of notification from eNB_A 45.

[00406] MME_C 107 transmits a notification message to eNB_A 45 (S1100) if there is an addition or change to the network slice type supported by MME_C 107. The notification message may be an MME configuration update message.

[00407] The notification message includes at least the first identifying information and / or the second identifying information and / or the third identifying information and / or the fourth identifying information.

[00408] Here, the first identification information may be information to identify the type of network slice supported by the MME. Alternatively, the first identification information may be information to identify the type of network slice supported by the network slice in which the MME is included. Additionally, the first identification information may also be the type of UE usage. Here, the information may be to identify the type of network slice or the type of UE usage supported by the MME being a transmission source. In other words, the first identification information transmitted by MME_A 104 and the first identification information transmitted by MME_B 106 to eNB_A 45 may be different from each other.

[00409] Additionally, the second identifying information may be the degree of independence of the network slice. For example, the information may indicate the degree of independence (isolation level) of the MME in relation to other network slices. As the MME may be included in one or more network slices, the number of network slices in which the MME is included can be managed while matching the degree of independence. Specifically, Petition 870240027939, dated 01 / 04 / 2024, p. 84 / 137 80 / 121 for example, in the case where MME_A 104 belongs to network slice_A 101 and is independent of other network slices, i.e., in the case where MME_A 104 is included in only one network slice, the isolation level can be set to level 2. On the other hand, in the case where MME_A 104 belongs to network slice_A 101 and network slice_B 102 and MME_A 104 is not independent in the network slices, i.e., in the case where MME_A 104 is included in several network slices, the isolation level can be level 1. Here, the information can be used to indicate the isolation level as the type of network slice identified by the MME being the transmission source using the first identification information.

[00410] The third piece of identifying information may be information to identify the network slice.

[00411] Additionally, the fourth identifying information is information to identify an MME that supports the same network slice type as the MME. Specifically, if the supported network slice types are the same for each group to which the MME belongs, the fourth identifying information can be the MME group ID (MMEGI) or the SGSN group ID. Alternatively, in the case where, using some GUMMEI identifier as a wildcard, the MME belonging to the same network slice can be identified, the fourth identifying information can be a wildcard MME information. Here, the information can be used to identify the MME that supports the network slice type or the UE usage type identified by the first identifying information.

[00412] MME_C 107 can transmit the notification message to EPI_45 for each network slice and / or the type of network slice supported by MME, or it can include in one notification several items of information from the first to the fourth identification information. Petition 870240027939, dated 01 / 04 / 2024, page 85 / 137 81 / 121

[00413] In other words, MME_C 107 can transmit, in a case where each of network slice_A 101 and network slice_B 102 is supported, each item of identification information for network slice _A 101 and each item of identification information for network slice _B 102 to eNB_45, including the information in different notification messages, respectively, or it can transmit the information to eNB_45, including the information in the same notification message.

[00414] Additionally, MME_C 107 may include, in the notification message, information to identify the request to update and / or add and / or remove the type of network slice supported by MME_C 107 and / or the network slice in which MME_C 107 is included.

[00415] In other words, MME_C 107 may include, in the notification message, information indicating that the network slice type and / or the network slice supported by MME itself are added. Alternatively, MME_C 107 may include, in the notification message, information indicating that the network slice type and / or the network slice supported by MME itself are removed, i.e., support is discontinued. Alternatively, MME_C 107 may include, in the notification message, information indicating that the network slice type and / or the network slice supported by MME itself are updated.

[00416] In the event that MME_C 107 includes, in the notification message, information indicating that the type of network slice and / or the network slice supported by MME itself are added or removed, one or more items of information from the first identification information and / or one or more items of information from the second identification information and / or one or more items of information from the third identification information and / or one or more items of Petition 870240027939, dated 01 / 04 / 2024, p. 86 / 137 82 / 121 information from the fourth piece of identification information included in the notification message may correspond to an addition or removal.

[00417] In other words, for example, in a case where MME_C 107 notifies eNB_A 45 of the addition of network slice type_C, MME_C 107 may transmit the notification message to eNB_A 45, including in it the identification information for the notification of the addition of the supported network slice type and / or the second identification information that identifies the network slice type_C and / or the second identification information indicating the degree of independence of MME_C 107 and / or the third identification information.

[00418] Additionally, MME_A 104 and MME_B 106 can transmit the notification message while including the EU usage type supported by each MME. It should be noted that each MME can obtain the EU usage type from the HSS in advance.

[00419] One method of acquiring the type of EU usage obtained from the HSS of each MME could be, for example, a procedure in which the MME periodically transmits a query message to the HSS, and receives from the HSS a response message corresponding to the query message.

[00420] Additionally, the first identification information and / or the second identification information may be part of the EU usage type.

[00421] In a case where the notification message transmitted from MME_C 107 to eNB_A 45 is the MME configuration update message, eNB_A 45 can transmit to MME_C 107 an MME configuration update acknowledgment message for each MME configuration update message received. Petition 870240027939, dated 01 / 04 / 2024, p. 87 / 137 83 / 121

[00422] eNB_A 45 receives the notification message transmitted by MME_C 107.

[00423] eNB_A 45 can transmit the RRC message to UE_A 10 upon receiving the notification message from MME_C 107, or upon updating the network slice type supported by eNB_A 45 (S1102). Alternatively, based on receiving the RRC message from UE_A 10 and the request to update the network slice type and / or isolation level included in the RRC message, eNB_A 45 can transmit the RRC message as a response to UE_A 10.

[00424] The RRC message transmitted from eNB_A 45 to UE_A 10 includes at least the eighth group of identification information and / or the ninth group of identification information.

[00425] In a case where the RRC message received by eNB_A 45 from UE_A 10 is the RRC connection request message, the RRC message as a response may be the RRC connection configuration message.

[00426] Here, the eighth identification information group can be a list of information to identify the network slice type of the network slice in which the MME to which eNB_A 45 connects is included. In other words, as illustrated in the drawing, in the case where eNB_A 45 connects to both MME_A 104 included in network slice_A classified as network slice type_A and MME_B 106 included in network slice_B classified as network slice type_B, the eighth identification information group can be configured to include the first identification information to identify network slice type_A and the first identification information to identify network slice type_B. The eighth identification information group can be formed by one or more items of information from the first identification information that the Petition 870240027939, dated 01 / 04 / 2024, page 88 / 137 84 / 121 eNB_A 45 obtains from MME_A 104 and MME_B 106.

[00427] Additionally, the ninth identification information group can be the list of information to identify the network slice in which the MME to which eNB_A 45 connects is included. In other words, as illustrated in the drawing, in the case where eNB_A 45 connects to both MME_A 104 included in network slice_A and MME_B 106 included in network slice_B, the ninth identification information group can be configured to include the third identification information to identify network slice_A and the third identification information to identify network slice_B. The ninth identification information group can be formed by one or more items of information from the third identification information that eNB_A 45 obtained from MME_A 104 and MME_B 106.

[00428] UE_A 10 receives the RRC message transmitted by eNB_A 45.

[00429] Through the procedures described above, UE_A 10 can obtain the network slice type supported by eNB_A 45 and determine the start of the TAU procedure (S1104).

[00430] It should be noted that the TAU procedure may be a TAU procedure with an update to the network slice type and / or isolation level illustrated in Figure 10. 1.3.4. PDN Connectivity Procedure

[00431] The establishment of the first PDN connection by UE_A 10 is described in chapter 1.3.1. In the following descriptions, a procedure will be described for UE_A 10 to additionally establish an additional PDN connection to simultaneously connect to multiple network slices after the connection procedure.

[00432] It should be noted that the procedure for establishing the additional PDN connection can also be performed only in the case of, in the initial connection procedure and / or in the procedure of Petition 870240027939, dated 01 / 04 / 2024, p. 89 / 137 85 / 121 RRC connection, the EU will be notified that multiple network slices can be connected from the network.

[00433] Specifically, in a case where UE_A 10 receives the connection acceptance message and / or the RRC message including the identification information from eNB_A 45, UE_A 10 can initiate the procedure for establishing the additional PDN connection. 1.3.4.1. Procedure for the first PDN connectivity

[00434] Figure 13 illustrates an example procedure of the first PDN connectivity. First, an initial state before starting the procedure will be described (S1301). UE_A establishes a communication path 10, as the initial state, with SGW_A 35 and PGW_A 30 through eNB_A 45. At this moment, MME_A 104 performs mobility management for UE_A 10. That is, the state is one in which UE_A 10 establishes a PDN connection through network slice_A 101. Furthermore, MME_A 104 is in a state selected in an initial connection procedure by UE_A 10. In other words, the state may be one in which a NAS signaling connection is established between UE_A 10 and MME_A 104.

[00435] UE_A 10 transmits to MME_A 104 the PDN connectivity request message to additionally establish the PDN connection in the initial state in which the PDN connection is established (S1300).

[00436] The PDN connectivity request message may include the seventh identification information and / or the 21st identification information and / or the 12th identification information and / or the 13th identification information and / or the 14th identification information.

[00437] Here, the seventh piece of identifying information may also be identifying information indicating that the EU requests Petition 870240027939, dated 01 / 04 / 2024, pp. 90 / 137 86 / 121 connections to various network slices. The seventh piece of identifying information may also be EU preference information.

[00438] Additionally, the 21 identification information may be application identification information. Furthermore, the information may be used to identify a service.

[00439] The 12th identification information may be information to identify the type of network slice requested by the UE. In the case where UE_A 10 selects the type of network slice, the information may be to identify the selected type of network slice from among the various information items of the first identification information included in the eighth identification information group received by UE_A 10 from eNB_A 45. Alternatively, if UE_A 10 does not select the type of network slice in the eighth identification information group notified from the network, the 12th identification information may be information to identify the type of network slice stored in the UE.

[00440] The 13th identification information may be information to identify the network slice requested by the UE. In the case where UE_A 10 selects the network slice, the information may be to identify the selected network slice from among the various items of information of the third identification information included in the ninth identification information group received by UE_A 10 from eNB_A 45. Alternatively, if UE_A 10 does not select the network slice in the ninth identification information group notified from the network, the 13th identification information may be information to identify the network slice stored in the UE.

[00441] The 14th identification information may be the degree of independence of the network slice requested by the UE. In other words, the 14th identification information may be the degree of independence of the NF (network function) included in the network slice requested by the UE. Petition 870240027939, dated 01 / 04 / 2024, page 91 / 137 87 / 121

[00442] For example, the 14th identification information can be information that indicates the degree of independence of the MME in relation to other network slices. In the present embodiment, since the MME can be included in one or more network slices, the number of network slices in which the MME is included can be managed while being made to correspond to the degree of independence. Specifically, for example, in the case where MME_A 104 belongs to network slice_A and is independent of other network slices, the isolation level can be made to be level 2. On the other hand, in a case where MME_A 104 belongs to network slice_A and network slice_B and MME_A 104 is not independent of other network slices (network slice_B in this case), the isolation level can be level 1. In other words, the 14th identification information can be information that indicates the degree of independence of the MME.

[00443] The PDN connectivity request message may include the APN. The APN may be information indicating a connection point and a connection function unit between the PDN and the network slice instance.

[00444] MME_A 104 receives the connectivity request from PDN transmitted by UE_A 10.

[00445] MME_A 104 can execute, based on the seventh identification information and / or the 21st identification information included in the PDN connectivity request message, a procedure to acquire UE_A 10 subscriber information from HSS_A 50 (S1302).

[00446] Specifically, for example, MME_A 104 may request the acquisition of subscriber information from UE_A 10 by transmitting a location update request message or an authentication information request message to HSS_A 50. Additionally, HSS_A 50 may transmit to UE_A Petition 870240027939, dated 01 / 04 / 2024, page 92 / 137 88 / 121 10, based on the request received from MME_A 104, a location update acknowledgment or an authentication information response, including in the acknowledgment message the subscriber information requested by UE_A 10. In this case, MME_A 104 may transmit the location update request message or the authentication information request message, including in the message an identification information or an indicator to identify the subscriber information request from UE_A 10.

[00447] In addition, MME_A 104 may include the 21aidentification information in the location update request message or in the authentication information request message.

[00448] If the HSS_A 50 receives the 21a identification information from MME_A 104, it may include the UE_A 10 subscriber information based on an application or service identified by the 21a identification information in the location update acknowledgment or authentication information response.

[00449] Here, the UE_A 10 subscriber information requested by UE_A 10 may be identification information for the UE usage type and / or the network slice type and / or the UE_A 10 network slice. Additionally, the UE_A 10 subscriber information may include MME identification information corresponding to the identification information for the UE usage type and / or the network slice type and / or the UE_A 10 network slice.

[00450] MME_A 104 determines, based on subscriber information UE_A 10 received from HSS_A 50 or information stored in the storage unit MME_A 104, to request that UE_A 10 perform the forwarding of the NAS message received from UE_A 10.

[00451] Here, the NAS message forwarding refers to Petition 870240027939, dated 01 / 04 / 2024, p. 93 / 137 89 / 121 to the retransmission of the NAS message, which has already been transferred once by the EU to the MME, to another MME.

[00452] MME_A 104 transmits a forwarding NAS message to eNB_A 45 (S1304). MME_A 104 transmits the forwarding NAS message, including in the message information to identify the MME as a forwarding destination. Specifically, for example, MME_A 104 may transmit the fourth piece of identifying information while including it in the forwarding NAS message.

[00453] Additionally, MME_A 104 can transmit the forwarding NAS message, including the receiving NAS message. Specifically, the PDN connectivity request message can be included in the forwarding NAS message. Additionally, MME_A 104 can also include the UE_A 10 identification information in the forwarding NAS message.

[00454] eNB_A 45 receives the NAS forwarding message transmitted by MME_A 104.

[00455] eNB_A 45 reselects the MME based on the acquisition of the forwarding NAS message from MME_A 104. eNB_A 45 can reselect the MME based on information received from MME_A 104 to identify the MME as the forwarding destination. A case will be described here where eNB_A 45 selects MME_B 106 as a new MME.

[00456] eNB_A 45 retransmits the PDN connectivity request message to the reselected MME_B 106 (S1306). eNB_A 45 may include the identification information of the MME selected in the initial connection procedure and a UE ID in the transmission message with the PDN connectivity request message. Additionally, eNB_A 45 may include the 22nd Petition 870240027939, dated 01 / 04 / 2024, p. 94 / 137 90 / 121 identification information in the transmission message.

[00457] Here, the 22aidentification information may be information indicating that the transmitted NAS message is transmitted from the UE that has already established the NAS connection with another MME. Additionally, the 22aidentification information may be information to request that MME_B 106 obtain context information from UE_A 10 from MME_A 104 or HSS_A 50.

[00458] MME_B 106 receives connectivity request from PDN that is transferred by eNB_A 45.

[00459] Based on receiving the PDN connectivity request message from eNB_A 45, MME_B 106 can execute an authentication procedure between HSS_A 50 and UE_A 10 (S1307). An authentication procedure between MME_A 104 and HSS_A 50 and an authentication procedure between MME_A 104 and UE_A 10 can be the same as the connection procedure described with reference to Figure 8 and illustrated therein.

[00460] Additionally, based on the receipt of the identification information from eNB_A 45, MME_B 106 can request the EU context from UE_A 10 for MME_A 104 and obtain it before the authentication procedure.

[00461] The authentication procedure is completed, and then MME_B 106 selects the SGW and PGW and executes the session creation procedure with the SGW and PGW (S1308). The method for selecting the SGW and PGW and the session creation procedure may be the same as the procedures illustrated in Figure 8.

[00462] Based on the establishment of a communication path between the SGW and the PGW, MME_B 106 transmits the standard EPS carrier context activation request message for UE_A 10 (S1310). MME_B 106 may include the information Petition 870240027939, dated 01 / 04 / 2024, page 95 / 137 91 / 121 identification and / or 16th identification information and / or 17th identification information in the standard EPS carrier context activation request message.

[00463] Here, the 15a identification information may be information to identify the type of network slice to which the network allows the UE to connect. Specifically, the information may be to identify the type of network slice supported by the MME selected by eNB_A 45. Here, the identification information may be to identify the type of network slice through the connection established in the additional PDN connection establishment procedure. In other words, the 15a identification information may be an identification information to identify the type of network slice to which UE_A 10 is authenticated to connect via the network through the PDN connectivity request message received from UE_A 10. The 15a identification information may be information indicating the type of network slice that is identical to that of the 12a identification information.

[00464] The 16th identification information may be information to identify the network slice to which the network allows the UE to connect. Specifically, the information may be to identify the network slice in which the MME selected by eNB_A 45 is included. Here, the identification information may be to identify the network slice through the connection established in the additional PDN connection establishment procedure. In other words, the 16th identification information may be identification information to identify the network slice to which the connection is authenticated by the network in the additional PDN connection establishment procedure. The 16th identification information may be information indicating the network slice that is identical to that of the 13th identification information. Petition 870240027939, dated 01 / 04 / 2024, pp. 96 / 137 92 / 121

[00465] Additionally, the 17th identification information can be the degree of independence of the network slice. In other words, the 17th identification information can be the degree of independence of the NF (network function) included in the network slice.

[00466] For example, the 17a identification information can be information that indicates the degree of independence of the MME in relation to other network slices. In the present embodiment, since the MME can be included in one or more network slices, the number of network slices in which the MME is included can be managed while being made to correspond to the degree of independence. Specifically, for example, in the case where MME_A 104 belongs to network slice_A 101 and is independent of other network slices, the isolation level can be made to be level 2. On the other hand, in the case where MME_A 104 belongs to network slice_A 101 and network slice_B 102 and MME_A 104 is not independent of other network slices (network slice_B in this case), the isolation level can be level 1. In other words, the 17a identification information can be information that indicates the degree of independence of the MME.

[00467] Here, the information may indicate the degree of independence in the connection established in the additional PDN connection establishment procedure in relation to the network slice that supports the network slice type in addition to the network slice type identified by identification information 15 and / or the network slice in addition to the network slice identified by identification information 16. The degree of independence identified by identification information 17 may be identical to the degree of independence identified by identification information 14. Additionally, the degree of independence identified by identification information 17 may be a degree of independence that is greater than the degree of independence Petition 870240027939, dated 01 / 04 / 2024, pp. 97 / 137 93 / 121 identified by the 14th identification information.

[00468] Additionally, MME_B 106 may additionally include the APN (access point name) in the standard EPS carrier context activation request message.

[00469] The APN can be the information to indicate the connection point and the unit of function for the connection between the network slice instance and the PDN.

[00470] UE_A 10 receives the standard EPS carrier context activation request message transmitted by MME_B 106.

[00471] Based on the reception of the standard EPS carrier context activation request message from MME_B 106, UE_A 10 reconfigures the RRC connection between eNB_A 45 and UE_A 10, transmits a completed PDN connection message to MME_B 106, and completes a procedure to establish the additional PDN connection and / or a carrier establishment procedure. Specifically, UE_A 10 transmits the completed RRC connection reconfiguration message to eNB_A 45, and eNB_A 45 transmits the initial context response message to MME_B 106. Here, the initial context response message may include the TEID of eNB_A 45 or the downlink address of eNB_A 45. Additionally, UE transmits the completed PDN connectivity message to MME via eNB_A 45.

[00472] As described above, based on the indication provided by the network, UE_A 10 can perform the forwarding of the PDN connectivity request message, and a procedure to establish the additional PDN connection through the new network slice. 1.3.4.2. Second PDN connection procedure

[00473] The following will describe a message procedure. Petition 870240027939, dated 01 / 04 / 2024, pp. 98 / 137 94 / 121 request for second PDN connectivity.

[00474] In the PDN first connectivity request message procedure, the procedure was described in which the eNB_A 45 transmits the NAS message including the PDN connectivity request message to the MME selected in the connection procedure as usual, and then performs forwarding to the ideal MME.

[00475] In the PDN secondary connectivity request message procedure, at a point in time upon receiving the PDN connectivity request message from UE_A 10, eNB_A 45 selects the ideal MME and transmits the PDN connectivity request message to the selected MME. In other words, the PDN secondary connectivity request message procedure is the procedure for establishing a PDN connection to an additional network slice that does not require rerouting.

[00476] Figure 14 is a diagram illustrating the PDN secondary connectivity procedure.

[00477] First, UE_A 10 completed, as an initial state, the PDN connection through SGW_A and PGW_A using the connection procedure (S1400).

[00478] This initial state may be the same as the initial state described in chapter 1.3.4.1 and therefore its descriptions will be omitted.

[00479] UE_A 10 transmits to eNB_A 45 the RRC message which includes the PDN connectivity request message to establish the additional PDN connection (S1402).

[00480] UE_A 10 may additionally include identification information 12 and / or identification information 13 and / or identification information 14 corresponding to the PDN connection. Petition 870240027939, dated 01 / 04 / 2024, p. 99 / 137 95 / 121 requested, included in the RRC message.

[00481] The 12th identification information may be information to identify the type of network slice requested by the UE. In the case where UE_A 10 selects the type of network slice, the information may be to identify the selected type of network slice from among the various information items of the first identification information included in the eighth identification information group received by UE_A 10 from eNB_A 45. Alternatively, if UE_A 10 does not select the type of network slice in the eighth identification information group notified from the network, the 12th identification information may be information to identify the type of network slice stored in the UE.

[00482] The 13th identification information may be information to identify the network slice requested by the UE. In the case where UE_A 10 selects the network slice, the information may be to identify the selected network slice from among the various items of information of the third identification information included in the ninth identification information group received by UE_A 10 from eNB_A 45. Alternatively, if UE_A 10 does not select the network slice in the ninth identification information group notified from the network, the 13th identification information may be information to identify the network slice stored in the UE.

[00483] The 14th identification information may be the degree of independence of the network slice requested by the UE. In other words, the 14th identification information may be the degree of independence of the NF (network function) included in the network slice requested by the UE.

[00484] For example, the 14th identification information may be information that indicates the degree of independence of the MME in relation to other network slices. In the present embodiment, as the MME may be included in one or more network slices, the number of Petition 870240027939, dated 01 / 04 / 2024, pp. 100 / 137 96 / 121 network slices in which the MME is included can be managed while being made to match the degree of independence. Specifically, for example, in the case where MME_A 104 belongs to network slice_A and is independent of other network slices, the isolation level can be set to level 2. On the other hand, in a case where MME_A 104 belongs to network slice_A and network slice_B and MME_A 104 is not independent of other network slices (network slice_B in this case), the isolation level can be level 1. In other words, the 14a identification information can be information that indicates the degree of independence of the MME.

[00485] UE_A 10 may also include identification information about the UE in the RRC message.

[00486] The PDN connectivity request message may include the APN. The APN may be the information that indicates the connection point and the connection function unit between the PDN and the network slice instance.

[00487] Additionally, UE_A 10 can transmit the RRC message to eNB_A 45, including an indicator to request the re-selection of MME.

[00488] Additionally, the PDN connectivity request message may include the seventh identification information and / or the 21st identification information.

[00489] Here, the seventh identifying information may also be identifying information indicating that the UE requests connections to multiple network slices. The seventh identifying information may also be UE preference information.

[00490] Additionally, the 21 identification information may be application identification information. Furthermore, the information may be used to identify a service.

[00491] In addition, UE_A 10 may additionally include 12a Petition 870240027939, dated 01 / 04 / 2024, pp. 101 / 137 97 / 121 identification information and / or 13th identification information and / or 14th identification information in the PDN connectivity request message.

[00492] eNB_A 45 receives the RRC message and / or the PDN connectivity request transmitted by UE_A 10.

[00493] eNB_A 45 selects the network slice type and / or the network slice of the new PDN connection based on the reception of the PDN connectivity request message, and the 12aidentification information and / or the 13aidentification information from UE_A 10 (S1403).

[00494] Specifically, for example, in a case where the identification information to identify the network slice type_A is received as the 12aidentification information from UE_A 10, eNB_A 45 determines the selection of the MME from the list of MMEs that support the network slice type_A.

[00495] Additionally, in a case where UE_A 10 does not transmit the 12a identification information and / or the 13a identification information with the PDN connectivity request message, or in a case where the MME that supports the network slice type identified by the 12a identification information and / or the network slice identified by the 13a identification information transmitted by UE_A 10 with the PDN connectivity request message cannot be selected, eNB_A 45 may select the MME from a default network slice.

[00496] In addition, eNB_A 45 selects the isolation level based on receiving the PDN connectivity request message and the 14a identification information from UE_A 10 (S1403).

[00497] Specifically, for example, in the case of identification information indicating that the isolation level is level 2 be Petition 870240027939, dated 01 / 04 / 2024, pp. 102 / 137 98 / 121 received as the 14th identification information from UE_A 10, eNB_A 45 additionally selects the MME whose isolation level is at least level 2 or higher from the list of MMEs selected by the network slice type selection.

[00498] It should be noted that, in the event that the MME that supports the isolation level identified by the identification information received from UE_A 10 cannot be selected from the list of MMEs, eNB_A 45 may select an alternative MME, such as selecting an MME that supports the highest degree of independence, or similar.

[00499] Additionally, besides these selections, eNB_A 45 can select the MME according to the physical location or load state for each MME resource, as in an existing method.

[00500] Additionally, if UE_A 10 does not transmit the 14a identification information with the PDN connectivity request message while including it in the message, the MME selection made based on the isolation level may not be executed.

[00501] Through the procedures described above, eNB_A 45 selects an MME to be a transfer destination for the connection request message. In other words, eNB_A 45 selects a network slice to which UE_A 10 connects. Furthermore, eNB_A 45 can select the degree of independence of the network slice to which UE_A 10 connects. From this point onward in this document, it is assumed that the MME selected by eNB_A 45 is MME_B 106. In other words, it is assumed that eNB_A 45 selects network slice_B as the network slice, and level 2 as the isolation level.

[00502] eNB_A 45 transfers the PDN connectivity request message to the selected MME_B 106 (S1404). eNB_A 45 may include MME_A 104 identification information and Petition 870240027939, dated 01 / 04 / 2024, pp. 103 / 137 99 / 121 the EU ID in the transmission message with the PDN connectivity request message. Additionally, eNB_A 45 may include the 22a identification information in the transmission message.

[00503] Here, the 22aidentification information may be information indicating that the transmitted NAS message is transmitted from the UE that has already established the NAS connection with another MME. Additionally, the 22aidentification information may be information to request that MME_B 106 obtain context information from UE_A 10 from MME_A 104 or HSS_A 50.

[00504] MME_B 106 receives connectivity request from PDN that is transferred by eNB_A 45.

[00505] Based on receiving the PDN connectivity request message from eNB_A 45, MME_B 106 can execute an authentication procedure between HSS_A 50 and UE_A 10 (S1408). An authentication procedure between MME_A 104 and HSS_A 50 and an authentication procedure between MME_A 104 and UE_A 10 can be the same as the connection procedure described with reference to Figure 8 and illustrated therein.

[00506] Additionally, before the authentication procedure, based on the receipt of the identification information from eNB_A 45, MME_B 106 can request the EU context from UE_A 10 for MME_A 104 and obtain it.

[00507] The authentication procedure is completed, and then MME_B 106 selects the SGW and PGW and executes the session creation procedure with the SGW and PGW (S1410).

[00508] The method for selecting the SGW and PGW and the session creation procedure can be the same as the procedures illustrated in Figure 8. Petition 870240027939, dated 01 / 04 / 2024, pp. 104 / 137 100 / 121

[00509] MME_B 106 transmits, based on the establishment of a communication path between the SGW and the PGW, the standard EPS carrier context activation request message for UE_A 10 (S1412). MME_B 106 may include identification information and / or identification information in the standard EPS carrier context activation request message.

[00510] Here, the 15a identification information may be information to identify the type of network slice to which the network allows the UE to connect. Specifically, the information may be to identify the type of network slice supported by the MME selected by eNB_A 45. Here, the identification information may be to identify the type of network slice through the connection established in the additional PDN connection establishment procedure. In other words, the 15a identification information may be an identification information to identify the type of network slice to which UE_A 10 is authenticated to connect via the network through the PDN connectivity request message received from UE_A 10. The 15a identification information may be information indicating the type of network slice that is identical to that of the 12a identification information.

[00511] The 16a identification information may be information to identify the network slice to which the network allows the UE to connect. Specifically, the information may be to identify the network slice in which the MME selected by eNB_A 45 is included. Here, the identification information may be to identify the network slice through the connection established in the additional PDN connection establishment procedure. In other words, the 16a identification information may be identification information to identify the network slice to which the connection is Petition 870240027939, dated 01 / 04 / 2024, pp. 105 / 137 101 / 121 authenticated by the network in the procedure for establishing the additional PDN connection. The 16th identification information may be information indicating the network slice that is identical to that of the 13th identification information.

[00512] Additionally, the 17th identification information can be the degree of independence of the network slice. In other words, the 17th identification information can be the degree of independence of the NF (network function) included in the network slice.

[00513] For example, the 17a identification information can be information that indicates the degree of independence of the MME in relation to other network slices. In the present embodiment, since the MME can be included in one or more network slices, the number of network slices in which the MME is included can be managed while being made to correspond to the degree of independence. Specifically, for example, in the case where MME_A 104 belongs to network slice_A 101 and is independent of other network slices, the isolation level can be made to be level 2. On the other hand, in the case where MME_A 104 belongs to network slice_A 101 and network slice_B 102 and MME_A 104 is not independent of other network slices (network slice_B in this case), the isolation level can be level 1. In other words, the 17a identification information can be information that indicates the degree of independence of the MME.

[00514] Here, the information may indicate the degree of independence in the connection established in the additional PDN connection establishment procedure in relation to the network slice with the network slice type other than the network slice type identified by identification information 15 and / or the network slice identified by identification information 16. The degree of independence identified by identification information 17 may Petition 870240027939, dated 01 / 04 / 2024, pp. 106 / 137 102 / 121 being identical to the degree of independence identified by the 14th identifying information. Additionally, the degree of independence identified by the 17th identifying information may be a degree of independence that is greater than the degree of independence identified by the 14th identifying information.

[00515] Additionally, MME_B 106 may additionally include the APN (access point name) in the standard EPS carrier context activation request message.

[00516] The APN can be the information to indicate the connection point and the unit of function for the connection between the network slice instance and the PDN.

[00517] UE_A 10 receives the standard EPS carrier context activation request message transmitted by MME_B 106.

[00518] Based on the reception of the standard EPS carrier context activation request message from MME_B 106, UE_A 10 reconfigures the RRC connection between eNB_A 45 and UE_A 10, transmits the completed PDN connection message to MME_B 106, and completes the additional PDN connection and / or carrier establishment procedure. Specifically, UE_A 10 transmits the completed RCC connection reconfiguration message to eNB_A 45, and eNB_A 45 transmits the initial context response message to MME_B 106. Here, the initial context response message may include the TEID of eNB_A 45 or the downlink address of eNB_A 45. Additionally, UE transmits the completed RCC connection message to MME_B 106 via eNB_A 45.

[00519] As described above, UE_A 10 can perform the procedure to establish the additional PDN connection through the new network slice without rerouting. 2. Second option Petition 870240027939, dated 01 / 04 / 2024, pp. 107 / 137 103 / 121

[00520] In the first embodiment, the procedure was described in which UE_A 10 establishes a PDN connection through the network slice classified as a specific network slice type using the connection procedure.

[00521] In a network slice operation, the UE is required to connect simultaneously to multiple network slices. The following descriptions will describe a case of establishing a PDN connection across multiple network slices using the connection procedure.

[00522] It should be noted that an overview of the system and a device configuration may be the same as those in the first mode, and therefore their descriptions will be omitted. 2.1. Processing Example

[00523] An example of processing the present embodiment will be described below. It should be noted that a notification procedure of the type of network slice transmitted from the core network to the UE executed before the start of the connection procedure may be the same as the method described in the first embodiment. 2.1.1. Connection procedure

[00524] Figure 12 is a diagram illustrating the connection procedure according to the present embodiment.

[00525] UE_A 10 selects the network slice type and / or network slice based on receiving the RRC message and / or receiving the eighth identification information group and / or the ninth identification information group from eNB_A 45 (S800). UE_A 10 can select the network slice type and / or network slice to be requested based on the network slice type or UE usage type that UE stores.

[00526] UE_A 10 can select the network slice type and / or the network slice, in a case where eNB_A 45 does not support the type of Petition 870240027939, dated 01 / 04 / 2024, pp. 108 / 137 104 / 121 network slice and / or the network slice that the EU itself stores, among the network slice types notified by eNB_A 45.

[00527] At this point, UE_A 10 can select various network slice types and / or network slices. For example, based on UE_A 10 receiving the identification information in the RRC message reply illustrated in Figure 7, UE_A 10 can select various network slice types and / or network slices.

[00528] Here, it is assumed that UE_A 10 selects network slice type_A and network slice type_B.

[00529] UE_A 10 transmits the connection request message to eNB_A 45 (S1200). UE_A 10 may transmit the connection request message, including in the message the 12th identification information and / or the 13th identification information and / or the 14th identification information and / or the seventh identification information.

[00530] The 12th identification information may be information to identify the type of network slice requested by the UE. In the case where UE_A 10 selects the type of network slice, the information may be to identify the selected type of network slice from among the various information items of the first identification information included in the eighth identification information group received by UE_A 10 from eNB_A 45. Alternatively, if UE_A 10 does not select the type of network slice in the eighth identification information group notified from the network, the 12th identification information may be information to identify the type of network slice stored in the UE.

[00531] The identification information 13 may be information to identify the network slice requested by the UE. In the case where UE_A 10 selects the network slice, the information may be for Petition 870240027939, dated 01 / 04 / 2024, pp. 109 / 137 105 / 121 identify the selected network slice from among the various items of information of the third identification information included in the ninth identification information group received by UE_A 10 from eNB_A 45. Alternatively, if UE_A 10 does not select the network slice in the ninth identification information group notified from the network, the 13th identification information may be information to identify the network slice stored in UE.

[00532] The 14th identification information may be the degree of independence of the network slice requested by the UE. In other words, the 14th identification information may be the degree of independence of the NF (network function) included in the network slice requested by the UE.

[00533] For example, the 14th identification information can be information that indicates the degree of independence of the MME in relation to other network slices. In the present embodiment, since the MME can be included in one or more network slices, the number of network slices in which the MME is included can be managed while being made to correspond to the degree of independence. Specifically, for example, in the case where MME_A 104 belongs to network slice_A and is independent of other network slices, the isolation level can be made to be level 2. On the other hand, in a case where MME_A 104 belongs to network slice_A and network slice_B and MME_A 104 is not independent of other network slices (network slice_B in this case), the isolation level can be level 1. In other words, the 14th identification information can be information that indicates the degree of independence of the MME.

[00534] Additionally, the seventh identifying information may also be identifying information indicating that the UE requests connections to multiple network slices. The seventh identifying information may also be UE preference information.

[00535] In a case where UE_A 10 selects the various types Petition 870240027939, dated 01 / 04 / 2024, pp. 110 / 137 106 / 121 of network slices and network slices in S800, UE_A 10 can transmit several items of 12a identification information and / or 13a identification information and / or several items of 14a identification information with the connection request message. Specifically, 12a identification information to identify the type of network slice_A and 12a identification information to identify the type of network slice_B can be transmitted with the connection request message. Additionally, 14a identification information indicating that the isolation level being made to match each item of 12a identification information is level 1 can be transmitted with the connection request message.

[00536] Additionally, UE_A 10 can transmit the connection request message, including in the message at least the IMSI or globally unique temporary identity (GUTI), the UE network capability and an EPS session management (ESM) message container.

[00537] The ESM message container is the message container for transmitting the session management message along with the mobility management message, such as the connection request message, or similar. Specifically, for example, UE_A 10 can transmit the ESM message container, including within it a PDN connectivity request message.

[00538] UE_A 10 can transmit the connection request message, additionally including in the same the 12aidentification information and / or the 13aidentification information and / or the 14aidentification information. Specifically, the PDN connectivity request message can include the 12aidentification information and / or the 13aidentification information and / or the 14aidentification information. Petition 870240027939, dated 01 / 04 / 2024, pp. 111 / 137 107 / 121

[00539] It should be noted that, here, UE_A 10 selects the various network slice types, and if multiple PDN connections are established, UE_A 10 can transmit the multiple ESM message containers or the ESM message container that includes the various PDN connectivity request messages while including them in the connection request message.

[00540] It should be noted that, in this case, each of the various PDN connectivity request messages can be transmitted while the 12aidentification information and / or the 13aidentification information and / or the 14aidentification information are included.

[00541] eNB_A 45 receives the RRC message and / or the connection request message transmitted by UE_A 10.

[00542] eNB_A 45 selects the network slice type and / or network slice based on receiving the connection request message and / or the 12aidentification information and / or the 13aidentification information from UE_A 10 (S1202).

[00543] Specifically, for example, in a case where the identification information to identify network slice type_A and the identification information to identify network slice type_B are received as the 12a identification information from UE_A 10, eNB_A 45 determines the selection of the MME from the list of network MMEs that support network slice type_A and from a list of MMEs that support network slice type_B.

[00544] Alternatively, in the same way, in a case where the identification information to identify network slice_A and the identification information to identify network slice_B are received as the identification information from UE_A, eNB_A determines the selection of the MME from the list of MMEs included in network slice_A and from a list of MMEs included in the slice of Petition 870240027939, dated 01 / 04 / 2024, pp. 112 / 137 108 / 121 network_B.

[00545] In addition, eNB_A 45 selects the isolation level based on receiving the connection request message and the identification information from UE_A 10 (S1202).

[00546] Specifically, for example, if the identification information indicating that the isolation level is level 1 is received as the 14th identification information from UE_A 10, eNB_A 45 additionally selects the MME whose isolation level is at least level 1 or higher from the list of MMEs selected by the network slice type selection.

[00547] It should be noted that, in the event that the MME that supports the isolation level identified by the identification information received from UE_A 10 cannot be selected from the list of MMEs, eNB_A 45 may select an alternative MME, such as selecting an MME that supports the highest degree of independence, or similar.

[00548] Additionally, eNB_A 45 performs the selection of these MMEs based on the network slice type selection and the isolation level selection for each PDN connectivity request message received with the connection request message.

[00549] Additionally, in a case where eNB_A 45 can select the same MME as a result of selecting multiple MMEs, the same MME can be selected.

[00550] Additionally, besides these selections, eNB_A 45 can select the MME according to the physical location or load state for each MME resource, as in an existing method.

[00551] Furthermore, in the case where UE_A 10 transmits the old GUTI to eNB_A 45 with the connection request message, eNB_A 45 can select the MME based on a function of Petition 870240027939, dated 01 / 04 / 2024, pp. 113 / 137 109 / 121 NAS node selection (NNSF) as in an existing method. In this case, eNB_A 45 can prioritize selection based on the NNSF.

[00552] Through the procedure described above, eNB_A 45 selects the MME responsible for a mobility management function of UE_A 10. From this point onward in this document, it is assumed that the MME selected by eNB_A 45 is MME_D 105.

[00553] Next, eNB_A 45 transmits the connection request message to MME_D 105 (S1204). eNB_A 45 can transfer the received connection request message to MME_D 105.

[00554] The eNB_A 45 can transmit the 12th identification information and / or the 13th identification information and / or the 14th identification information with the connection request message.

[00555] In a case where eNB_A 45 selects multiple MMEs for each network slice type, eNB_A 45 can transfer the connection request message for each MME. In this case, eNB_A 45 can transmit the 12a identification information and / or the 13a identification information to identify the corresponding network slice type along with the connection request message. Additionally, the 14a identification information can also be transmitted simultaneously.

[00556] In a case where there is no UE context for UE_A 10, MME_D 105 executes an authentication procedure between HSS_A 50 and UE_A 10 (S1206). MME_D 105 generates the UE context for UE_A 10 through the authentication procedure and then stores it.

[00557] At this point, MME_D 105 can obtain, from HSS_A 50, the UE usage type and / or the UE_A network slice type. Petition 870240027939, dated 01 / 04 / 2024, pp. 114 / 137 110 / 121 10.

[00558] Alternatively, MME_D 105 can obtain, using a procedure that is different from the authentication procedure, from the HSS, the UE usage type and / or the network slice type.

[00559] The authentication procedure is completed and then MME_D 105 selects the SGW and PGW for each PDN connectivity request message, and executes the session creation procedures with the SGW and PGW, respectively (S1208, S1210).

[00560] Specifically, for example, MME_D 105 transmits a first session creation message to SGW_A 35, and SGW_A 35 transmits, based on the first session creation request message received, the second session creation request message to PGW_A 30. Additionally, PGW_A 30 transmits the first session creation response message to SGW_A 35, and SGW_A 35 transmits the second session creation response message to MME. Through the procedures described above, a carrier is established between MME_D 105 and SGW_A 35 and between SGW_A 35 and PGW_A 30.

[00561] Similarly, MME_D 105 can establish a carrier between MME_D 105 and SGW_B and between SGW_B and PGW_B by executing the session creation procedure for SGW_B and PGW_B (S1210).

[00562] MME_D 105 transmits a connection acceptance message to eNB_A 45 to transmit it to UE_A 10 based on the completion of the session creation procedure (S1212).

[00563] MME_D 105 may include the 15th identification information and / or the 16th identification information and / or the 17th identification information in the connection acceptance message.

[00564] Here, the 15th identification information can be a Petition 870240027939, dated 01 / 04 / 2024, pp. 115 / 137 111 / 121 information to identify the type of network slice to which the network allows the UE to connect. Specifically, the information may be to identify the type of network slice supported by the MME selected by eNB_A 45. Here, the identification information may be to identify the type of network slice through the connection established in this connection procedure. In other words, the 15a identification information may be an identification information to identify the type of network slice for which the connection is authenticated by the network in the connection procedure. The 15a identification information may be information indicating the type of network slice that is identical to that of the 12a identification information.

[00565] The 16th identification information may be information to identify the network slice to which the network allows the UE to connect. Specifically, the information may be to identify the network slice in which the MME selected by eNB_A 45 is included. Here, the identification information may be to identify the network slice through the connection established in this connection procedure. In other words, the 16th identification information may be the identification information to identify the network slice to which the connection is authenticated by the network in the connection procedure. The 16th identification information may be information indicating the network slice that is identical to that of the 13th identification information.

[00566] Additionally, the 17th identification information can be the degree of independence of the network slice. In other words, the 17th identification information can be the degree of independence of the NF (network function) included in the network slice.

[00567] For example, the 17th identification information may be information that indicates the degree of independence of the MME in relation to other network slices. In the present embodiment, since Petition 870240027939, dated 01 / 04 / 2024, pp. 116 / 137 112 / 121 The MME can be included in one or more network slices; the number of network slices in which the MME is included can be managed while being made to correspond to the degree of independence. Specifically, for example, in the case where MME_A 104 belongs to network slice_A 101 and is independent of other network slices, the isolation level can be set to level 2. On the other hand, in the case where MME_A 104 belongs to network slice_A 101 and network slice_B 102, and MME_A 104 is not independent of other network slices (network slice_B in this case), the isolation level can be set to level 1. In other words, the identification information can be information that indicates the degree of independence of the MME.

[00568] Here, the information may indicate the degree of independence in the connection established in the connection procedure in relation to the network slice with the network slice type in addition to the network slice type identified by the 15th identification information and / or the network slice identified by the 16th identification information. The degree of independence identified by the 17th identification information may be identical to the degree of independence identified by the 14th identification information. Additionally, the degree of independence identified by the 17th identification information may be a degree of independence that is greater than the degree of independence identified by the 14th identification information.

[00569] MME_D 105 can transmit the 15a identification information and / or the 16a identification information and / or the 17a identification information by means of a message independent of the connection acceptance message. Specifically, for example, MME_A 104 can transmit to eNB_A 45 the initial context configuration request message in which the connection acceptance message is included, including in the message the 15a Petition 870240027939, dated 01 / 04 / 2024, pages 117 / 137 113 / 121 identification information and / or 16th identification information and / or 17th identification information.

[00570] Alternatively, MME_D 105 may transmit the 15aidentification information and / or the 16aidentification information and / or the 17aidentification information, including this information in the standard EPS carrier context activation request message in the ESM message container included in the connection acceptance message.

[00571] In other words, MME_D 105 can transmit to UE_A 10 is the default EPS carrier context activation request message in the ESM message container.

[00572] Note that the connection acceptance message may include the APN, GUTI, PDN address (UE IP address), EPS carrier ID, and ESM message recipient.

[00573] It should be noted that MME_D 105 may transmit to eNB_A 45 one or more items of information from the 15a identification information and / or one or more items of information from the 16a identification information and / or one or more items of information from the 17a identification information. Specifically, in a case where MME_D 105 establishes multiple connections from one connection through SGW_A 35 / PGW_A 30 and one connection through SGW_B / PGW_B, MME_D 105 may notify eNB_A 45 of the 15a identification information to identify the type of network slice connected in each connection and / or of the 16a identification information to identify the network slice and / or of the 17a identification information corresponding to each of the 15a identification information and / or the 16a identification information.

[00574] In this case, MME_D 105 may include one or more ESM message recipients in the connection acceptance message. Furthermore, one or each of the multiple recipients of Petition 870240027939, dated 01 / 04 / 2024, pp. 118 / 137 114 / 121 ESM message can be transmitted to eNB_A 45 while the 15a identification information and / or the 16a identification information and / or the 17a identification information are included.

[00575] Additionally, MME_D 105 may include in the connection acceptance message one or more standard EPS carrier context activation request messages. Furthermore, one or each of the multiple standard EPS carrier context activation request messages may be transmitted to eNB_A 45 while the 15a identification information and / or the 16a identification information and / or the 17a identification information are included.

[00576] Specifically, in the case where eNB_A 45 receives, from UE_A 10, the PDN connectivity request message to request the PDN connection with network slice_A 101 and the PDN connectivity request message to request the PDN connection with network slice_B 102 that are included in the connection request message, MME_A 104 can transmit to UE_A 10, through eNB_A 45, the default EPS carrier context activation request message regarding the PDN connection with network slice_A 101 and the default EPS carrier context activation request message regarding the PDN connection with network slice_B102.

[00577] Additionally, in the case where the 17aidentification information is the MME isolation level, the 17aidentification information included in the standard EPS carrier context activation request message and the 17aidentification information included in the standard EPS carrier context activation request message regarding the PDN connection to network slice_B 102 may be information indicating the same isolation level. Petition 870240027939, dated 01 / 04 / 2024, pp. 119 / 137 115 / 121

[00578] Additionally, in a case where, in the S1208 or S1210 procedure, the bearer can be established in one session creation procedure, and the bearer cannot be established in the other session creation procedure, MME_D 105 may transmit the connection acceptance message in relation to the procedure in which the bearer is successfully established.

[00579] In this case, MME_D 105 may additionally transmit to eNB_A 45, based on the carrier failure, a PDN connectivity rejection message regarding the failure procedure. It should be noted that MME_D 105 may transmit the PDN connectivity rejection message while including it in the ESM message container.

[00580] MME_D 105 can transmit the initial context configuration request message, including standard EPS carrier context activation request messages or PDN connectivity acceptance messages whose number is different from the number of PDN connectivity request messages included in the PDN connectivity request message received from eNB_A 45.

[00581] Specifically, in a case where UE_A 10 transmits to eNB_A 45 the PDN connectivity request message to request a PDN connection to network slice_A 101 and the PDN connectivity request message to request a connection to network slice_B 102, including the messages in the connection request message, in a case where MME_D 105 successfully establishes the carrier to establish a PDN connection through network slice_A 101 and refuses to establish a PDN connection through network slice_B 102, MME_D 105 may transmit the initial context configuration request message, including the connection acceptance message. A Petition 870240027939, dated 01 / 04 / 2024, pp. 120 / 137 The 116 / 121 connection acceptance message can be transmitted while including a standard EPS carrier context activation request message. Additionally, MME_D 105 can independently transmit the PDN connectivity rejection message to eNB_A 45 as a response to the PDN connectivity request message that fails to establish the carrier. Alternatively, MME_D 105 can include the response message to the connection request message in the initial context configuration request message and include a standard EPS carrier context activation request message and the PDN connectivity rejection message in the response message, and then transmit the messages.

[00582] eNB_A 45 receives the connection acceptance message transmitted by MME_D 105.

[00583] Subsequently, eNB_A 45 transmits, based on the connection acceptance message received from MME_D 105, the connection acceptance message to UE_10 (S1214).

[00584] The connection acceptance message may include one or more items of information from the 15a identification information and / or one or more items of information from the 16a identification information and / or one or more items of information from the 17a identification information.

[00585] Alternatively, eNB_A 45 may transmit the 15a identification information and / or the 16a identification information and / or the 17a identification information by means of a message independent of the connection acceptance message. Specifically, for example, the RRC message transmitted with the connection acceptance message may be transmitted including the 15a identification information and / or the 16a identification information and / or the 17a identification information.

[00586] Alternatively, eNB_A 45 can transmit the 15th Petition 870240027939, dated 01 / 04 / 2024, pages 121 / 137 117 / 121 identification information and / or 16a identification information and / or 17a identification information, including this information in the standard EPS carrier context activation request message in the ESM message container included in the connection acceptance message.

[00587] In other words, eNB_A 45 can transmit to UE_A 10 one or more standard EPS carrier context activation request messages.

[00588] UE_A 10 receives the connection acceptance message transmitted by MME_D 105 through eNB_A 45.

[00589] For example, in a case where UE_A 10 transmits to MME_A 104 the PDN connectivity request message to request the PDN connection with network slice_A 101 and the PDN connectivity request message to request the connection with network slice_B 102, including the messages in the connection request message, UE_A 10 can obtain each identification information regarding the PDN connection with network slice_A 101 from MME_A 104. Here, each identification information may include the 15th identification information and / or the 16th identification information and / or the 17th identification information.

[00590] Based on the reception of the connection acceptance message, UE_A 10 reconfigures the RRC connection between eNB_A 45 and UE_A 10, transmits the connection completion message to MME_A 104, and completes the PDN connection. Specifically, UE_A 10 transmits the RRC connection complete reconfiguration message to eNB_A 45, and eNB_A 45 transmits the initial context response message to MME_A 104. Here, the initial context response message may include the TEID of eNB_A 45 or the Petition 870240027939, dated 01 / 04 / 2024, pages 122 / 137 118 / 121 is the downlink address of eNB_A 45. Additionally, the UE transmits the connection completion message to the MME via eNB_A 45.

[00591] As described above, UE_A 10 can establish the PDN connection through network slice_A and network slice_B through the connection procedure. 3. Modification

[00592] A program executed on a device according to the present invention may be a program to control a central processing unit (CPU) and the like, and cause a computer to function in order to implement the functions of the embodiment described above according to the present invention. The programs or the information processed by the programs are temporarily stored in volatile memory, such as random access memory (RAM), non-volatile memory, such as flash memory, a hard disk drive (HDD), or other storage device systems.

[00593] It should be noted that a program to implement the functions of the embodiments according to the present invention may be recorded on a computer-readable recording medium. A computer system may be implemented to read the program recorded on the recording medium for execution. Here, the computer system is assumed to refer to a computer system embedded in the devices, and the computer system includes an operating system and hardware components, such as a peripheral device. Furthermore, the computer-readable recording medium may be a recording medium formed by semiconductor devices, a medium for optical recording, a medium for magnetic recording, a medium that dynamically retains the program for a short period of time, or other readable recording media. Petition 870240027939, dated 01 / 04 / 2024, pp. 123 / 137 119 / 121 by computer.

[00594] In addition, each functional block or several features of the devices used in the embodiment described above may be assembled or implemented in an electrical circuit, for example, an integrated circuit or multiple integrated circuits. An electrical circuit designed to perform the functions described in this descriptive report may include a general-purpose processor, a digital signal processor (PSD), a field-programmable gate array (FPGA), or other programmable logic devices, distinct gates or transistor logic, distinct hardware components, or a combination of these items. The general-purpose processor may be a microprocessor or a processor of a known type, a controller, a microcontroller, or a state machine. The aforementioned electrical circuits may consist of a digital circuit or an analog circuit.Furthermore, if advances in semiconductor technology lead to the emergence of a circuit integration technology that replaces current integrated circuits, it is also possible that the present invention could utilize integrated circuits based on the new technology.

[00595] It should be noted that the invention in this patent application is not limited to the embodiments described above. In the embodiment, the devices were described as an example, but the invention in the present application is not limited to these devices, and is applicable to a terminal apparatus or a communication device of a fixed type or to a stationary type electronic apparatus installed in indoor or outdoor environments, for example, as a video and audio (AV) apparatus, a cleaning or washing machine, an air conditioner, office equipment, a vending machine and other household appliances.

[00596] The embodiments of the present invention have been described. Petition 870240027939, dated 01 / 04 / 2024, pp. 124 / 137 120 / 121 above in detail with reference to the drawings, but the specific configuration is not limited to these embodiments and includes, for example, an amendment to a design that falls within the scope and does not depart from the spirit of the present invention. Furthermore, various modifications are possible within the scope of the present invention as defined by the embodiments, and embodiments produced by the appropriate combination of the technical means disclosed according to the different embodiments are also included within the technical scope of the present invention. In addition, an embodiment in which a constituent element achieving the same effect is replaced by one described in these embodiments is also included within the technical scope of the present invention. List of reference signs 1 Communication System 5 PDN_A 10 UE_A 20 UTRAN_A 22 eNB (UTRAN)_A 24 RNC_A 25 GERAN_A 26 BSS_A 30 PGW_A 35 SGW_A 45 eNB_A 50 HSS_A 55 AARF_A 60 PC_A 70 WLAN TO 72 WLAN TO Petition 870240027939, of 01 / 04 / 2024, p. 125 / 137 121 / 121 TWAG_A WLAN ANb WLAN APb LTE AN_A Network core_A Network slice_A Network slice_B Network slice_C MME_A MME_D MME_B MME C

Claims

CLAIMS 1. User Equipment (UE) characterized in that it comprises: a transmit and receive circuit (301); and a controller (302) configured to control the transmit and receive circuit (301) to: receive a plurality of first information units for Network Slice selection; transmit (S1300) a connectivity request message to establish a data network session on a first Network Slice to a central network (90) via a base station device (45), the connectivity request message including one of the plurality of first information units, wherein: in an initial procedure, the controller is further configured to control the transmit and receive circuits to: transmit (S802) a first Radio Resource Control (RRC) message to the base station device (45), the first RRC message including second information to select a second Network Slice;transmit (S802) a first request message to the central network (90) via the base station device (45), the first request message including the second information to select the second Network Slice; receive (S814) a first acceptance message from the main network (90) via the base station device (45), the first acceptance message including a Temporary Global Unique Identifier (GUTI) and third information to select a third Network Slice allowed by the main network (90); transmit a complete first message to the central network (90) via the base station device (45); and after receiving the first acceptance message from the central network (90) via the base station device (45), connect to the first Network Slice;and in a procedure to update a Tracking Area, the controller is further configured to control the transmission and reception circuits to: transmit (S1000) a second RRC message to the base station device (45), the second RRC message including fourth information to select a fourth Network Slice; transmit (S1000) a second request message to the main network (90) via the base station device (45), the second request message including the GUTI and the fourth information to select the fourth Network Slice; and receive (S1012) a second acceptance message from the main network (90) via the base station device (45), the second acceptance message including fifth information to select a fifth Network Slice allowed by the main network (45).

2. UE (10), according to claim 1, characterized in that the controller (302) is further configured to: connect to the first Network Slice when transmitting the connectivity request message in a state that the UE is connecting to a sixth Network Slice; and Petition 870240027939, dated 04 / 01 / 2024, p. 128 / 137 3 / 7 connect simultaneously to the first Network Slice and the sixth Network Slice.

3. UE (10), according to claim 1 or 2, characterized in that at least one of the first pieces of information, the second pieces of information, the third pieces of information, the fourth pieces of information, and the fifth pieces of information are uniquely identified among at least one of Public Terrestrial Mobile Networks (PLMNs) and Mobile Operators.

4. UE (10), according to claim 1 or 2, characterized in that at least one of the first information, the second information, the third information, the fourth information, and the fifth information are uniquely identified from at least one within Public Terrestrial Mobile Networks (PLMNs) and Mobile Operators.

5. EU (10), according to claim 3, characterized in that at least one of the first information, the second information, the third information, the fourth information, and the fifth information comprise a Network Slice Type for Internet of Things (IoT).

6. UE (10), according to claim 1 or 2, characterized in that, in a case where the second request message is transmitted to a first control device (104) on the main network (45), the GUTI is used for the first control device (104) to obtain a UE context from a second control device (105) to perform Network Slice management based on the second information, and obtaining the UE context is performed in a case where the second request message is not transmitted Petition 870240027939, dated 01 / 04 / 2024, page 129 / 137 4 / 7 periodically.

7. UE (10), according to claim 1 or 2, characterized by further comprising: memory (310) configured to store one or more Application identities, IDs, corresponding to at least one of the first information, the second information, the third information, the fourth information and the fifth information.

8. Communication method performed by a User Equipment (UE) (10), the communication method characterized in that it comprises: receiving a plurality of first information units for Network Slice selection; transmitting (S1300) a connectivity request message to establish a data network session on a first Network Slice to a central network (90) via a base station device (45), the connectivity request message including one of the plurality of first information units; performing an initial procedure including: transmitting (S802) a first Radio Resource Control (RRC) message to the base station device (45), the first RRC message including second information to select a second Network Slice;transmit (S802) a first request message to the central network (90) through the base station device (45), the first request message including the second information to select the second Network Slice; Petition 870240027939, dated 01 / 04 / 2024, page 130 / 137 5 / 7 receive (S814) a first acceptance message from the main network (90) through the base station device (45), the first acceptance message including a Globally Unique Temporary Identifier (GUTI) and third information to select a third Network Slice allowed by the main network (90); transmit a complete first message to the central network (90) through the base station device (45); and after receiving the first acceptance message from the central network (90) through the base station device (45), connect to the first Network Slice;and perform a procedure to update a Tracking Area, the procedure including: transmitting (S1000) a second RRC message to the base station device (45), the second RRC message including fourth information to select a fourth Network Slice; transmitting (S1000) a second request message to the main network (90) through the base station device (45), the second request message including the GUTI and the fourth information to select the fourth Network Slice; and receiving (S1012) a second acceptance message from the main network (90) through the base station device (45), the second acceptance message including fifth information to select a fifth Network Slice allowed by the main network (45).

9. Communication method according to claim 8, characterized in that the communication method further comprises: Petition 870240027939, dated 01 / 04 / 2024, page 131 / 137 6 / 7 connecting to the first Network Slice when transmitting the connectivity request message in a state that the UE (10) is connecting to a sixth Network Slice; and connecting simultaneously to the first Network Slice and the sixth Network Slice.

10. A communication method according to claim 8 or 9, characterized in that at least one of the first, second, third, fourth, and fifth pieces of information is uniquely identified between at least one of the Public Terrestrial Mobile Networks (PLMNs) and Mobile Operators.

11. A communication method according to claim 8 or 9, characterized in that at least one of the first, second, third, fourth, and fifth pieces of information is uniquely identified from at least one within Public Terrestrial Mobile Networks (PLMNs) and Mobile Operators.

12. A communication method according to claim 10, characterized in that at least one of the first, second, third, fourth, and fifth pieces of information comprise a Network Slice Type for the Internet of Things (IoT).

13. Communication method, according to claim 8 or 9, characterized in that, in a case where the second request message is transmitted to a first control device (104) on the main network (45), the GUTI is used for the first control device (104) to obtain a UE context from a second control device (105) to perform Network Slice management based on the second information, and the obtaining of the UE context is performed in a case where the second request message is not transmitted periodically.

14. A communication method according to claim 8 or 9, characterized in that it further comprises: storing one or more Application Identities, IDs, corresponding to at least one of the first pieces of information, the second pieces of information, the third pieces of information, the fourth pieces of information, and the fifth pieces of information.

Images