WO2024062941A1 - User equipment (ue) - Google Patents

Abstract

Functions for implementing closed networks, such as non-public networks (NPNs), have been studied. Currently, it has been studied that a UE recognizes a session for a local service by using the identifier of the local service. However, the specific procedure by which the UE obtains the identifier of the local service is not clear. When common DNN and S-NSSAI are used for different local services, the user equipment (UE) receives a registration acceptance message or a configuration update command message, which includes first identification information. The first identification information is the identifier of a local service. The UE recognizes the identifier of an available local service when the first identification information is received, and transmits a PDU session establishment request message including the first identification information.

Description

UE (User Equipment)

The present invention relates to UE (User Equipment).

The 3GPP (3rd Generation Partnership Project) is considering the system architecture of 5GS (5G System), a 5th generation (5G) mobile communication system, and discussions are being held to support new procedures and new functions. (Refer to Non-Patent Documents 1 to 4). In recent years, there has been active discussion about how to use local services in NPN (Non-Public Network) (see Non-Patent Document 5).

In 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered in order to provide a wide variety of services. In addition, in 5GS, non-public networks such as NPN (Non-Public Network), which are defined separately from PLMN (Public Land Mobile Network), which is a public network, can be used by specific users for specific purposes. Functions to provide a public network and realize a private network are also being considered.

Currently, it is being considered that the UE recognizes sessions for local services using local service identifiers. However, the specific procedure by which the UE obtains the local service identifier is not clear.

One embodiment of the present invention has been made in view of the above circumstances. The purpose is to clarify the procedure by which a UE obtains a local service identifier.

User Equipment (UE) according to one aspect of the present invention includes a transmitting/receiving unit and a control unit, and when a common DNN and S-NSSAI are used for different local services, the transmitting/receiving unit 1, wherein the first identification information is an identifier of a local service; Based on the first identification information, the transmitting/receiving unit recognizes an identifier of an available local service, and transmits a PDU session establishment request message including the first identification information.

According to one aspect of the present invention, the procedure by which a UE obtains an identifier for a local service can be clarified.

FIG. 1 is a diagram illustrating an outline of a mobile communication system (EPS/5GS). This is a diagram explaining the detailed configuration of the mobile communication system (EPS/5GS). FIG. 2 is a diagram illustrating the device configuration of a UE. FIG. 2 is a diagram illustrating the configuration of an access network device (gNB) in 5GS. FIG. 2 is a diagram illustrating the configuration of a core network device (AMF/SMF/UPF) in 5GS. It is a figure explaining a registration procedure. FIG. 1 is a diagram illustrating a UE configuration update procedure. FIG. 3 is a diagram showing a PDU session establishment procedure.

Hereinafter, the best mode for carrying out one aspect of the present invention will be described with reference to the drawings. Note that in this embodiment, as an example, an embodiment of a mobile communication system to which one aspect of the present invention is applied will be described.

[1. System overview]
First, FIG. 1 is a diagram for explaining the outline of a mobile communication system 1 used in each embodiment, and FIG. 2 is a diagram for explaining the detailed configuration of the mobile communication system 1.

In Figure 1, the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network)_A5, access network_B120, core network_B190, and DN (Data Network)_A6. It is stated that

In the following, symbols may be omitted for these devices and functions, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc. .

Figure 2 also shows the devices and functions of UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170, etc. Interfaces that connect these devices and functions to each other are described.

The following describes these devices and functions, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc. , symbols may be omitted.

Note that the EPS (Evolved Packet System), which is a 4G system, is configured to include an access network_A and a core network_A, but may also include a UE and/or a PDN. Furthermore, 5GS (5G System), which is a 5G system, includes a UE, an access network_B, and a core network_B, but may further include a DN.

A UE is a device capable of connecting to network services via a 3GPP access (also referred to as a 3GPP access network, 3GPP AN) and/or a non-3GPP access (also referred to as a non-3GPP access network, non-3GPP AN). be. The UE may be a terminal device capable of wireless communication such as a mobile phone or a smartphone, and may be a terminal device connectable to both EPS and 5GS. The UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Note that the UE may be expressed as a user device or a terminal device.

Additionally, the access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and/or a wireless LAN access network. One or more eNB (evolved Node B) 45 is arranged in E-UTRAN. Note that in the following, eNB45 may be written with the symbol omitted, such as eNB. Further, when there are multiple eNBs, each eNB is connected to each other by, for example, an X2 interface. Furthermore, one or more access points are arranged in the wireless LAN access network.

Additionally, access network_B corresponds to 5G access network (5G AN). 5G AN consists of NG-RAN (NG Radio Access Network) and/or non-3GPP access network. One or more gNBs (NR NodeBs) 122 are arranged in the NG-RAN. Note that in the following, gNB122 may be written with the symbol omitted, such as gNB. gNB is a node that provides an NR (New Radio) user plane and a control plane to UE, and is a node that connects to 5GCN via an NG interface (including an N2 interface or an N3 interface). That is, gNB is a base station device newly designed for 5GS, and has different functions from the base station device (eNB) used in EPS, which is a 4G system. Furthermore, when there are multiple gNBs, each gNB is connected to each other by, for example, an Xn interface.

Additionally, the non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network may be a non-3GPP access network that does not perform security management within the access network, such as a public wireless LAN. On the other hand, the trusted non-3GPP access network may be an access network defined by 3GPP, and may include a TNAP (trusted non-3GPP access point) and a TNGF (trusted non-3GPP gateway function).

Furthermore, in the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. Furthermore, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. Furthermore, nodes placed in access network_B may be collectively referred to as NG-RAN nodes.

In addition, in the following, access network_A and/or access network_B and/or devices included in access network_A and/or devices included in access network_B are referred to as access networks or access network devices. It is sometimes called.

Additionally, core network_A corresponds to EPC (Evolved Packet Core). EPC includes, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc. Placed.

Additionally, Core Network_B corresponds to 5GCN (5G Core Network). For example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), UDM (Unified Data Management), etc. are arranged in 5GCN. Here, 5GCN may be expressed as 5GC.

In addition, in the following, core network_A and/or core network_B, devices included in core network_A, and/or devices included in core network_B are referred to as core networks, core network devices, or core networks. Sometimes referred to as an internal device.

A core network (core network_A and/or core network_B) is a mobile communication carrier (Mobile It may be an IP mobile communication network operated by a Mobile Virtual Network Operator (MNO), a core network for a mobile communication carrier that operates and manages a mobile communication system, ), or a core network for virtual mobile communication carriers or virtual mobile communication service providers such as MVNE (Mobile Virtual Network Enabler).

Further, although FIG. 1 shows a case where the PDN and DN are the same, they may be different. The PDN may be a DN (Data Network) that provides communication services to the UE. Note that the DN may be configured as a packet data service network or may be configured for each service. Additionally, the PDN may include connected communication terminals. Therefore, connecting to the PDN may mean connecting to a communication terminal or server device located in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may mean transmitting and receiving user data to and from a communication terminal and a server device located in the PDN. Note that a PDN may be expressed as a DN, or a DN may be expressed as a PDN.

In addition, in the following, at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN, and/or one or more devices included therein are referred to as networks or network devices. It is sometimes called. In other words, the network and/or network equipment sends and receives messages and/or performs procedures in the access network_A, core network_A, PDN, access network_B, core network_B, DN. means that at least some of them and/or one or more of the devices included therein send and receive messages and/or perform procedures.

Also, the UE can connect to the access network. Furthermore, the UE can connect to the core network via the access network. Furthermore, the UE can connect to the PDN or DN via the access network and core network. That is, the UE can transmit and receive (communicate) user data with the PDN or DN. When transmitting and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication may be used.

Here, IP communication refers to data communication using IP, and data is sent and received using IP packets. An IP packet consists of an IP header and a payload part. The payload portion may include data transmitted and received by devices and functions included in EPS and devices and functions included in 5GS. Furthermore, non-IP communication refers to data communication that does not use IP, and data is sent and received using a format different from the IP packet structure. For example, non-IP communication may be data communication realized by sending and receiving application data to which no IP header is attached, or it may be data communication realized by sending and receiving application data to which no IP header is attached, or the UE may attach another header such as a Mac header or an Ethernet (registered trademark) frame header. User data to be transmitted and received may also be transmitted and received.

Additionally, devices not shown in FIG. 2 may be configured in the access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A. For example, the core network_A and/or the core network_B may include an Authentication Server Function (AUSF) or an Authentication, Authorization, and Accounting (AAA) server (AAA-S).

Here, the AUSF is a core network device equipped with an authentication function for 3GPP access and non-3GPP access. Specifically, it is a network function unit that receives an authentication request for 3GPP access and/or non-3GPP access from the UE and executes an authentication procedure.

The AAA server is a device that has authentication, authorization, and billing functions and is connected to the AUSF directly or indirectly via another network device. The AAA server may be a network device within the core network. The AAA server may not be included in core network_A and/or core network_B, but may be included in the PLMN. In other words, the AAA server may be a core network device, or a device outside the core network. For example, the AAA server may be a server device within the PLMN managed by a 3rd Party.

Note that in FIG. 2, each device/function is shown one by one to simplify the diagram, but the mobile communication system 1 may include a plurality of similar devices/functions. Specifically, the mobile communication system 1 includes multiple UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and/or UDM150. Devices and functions such as the above may be configured.

UPF_A235 is connected to DN, SMF, other UPFs, and access networks. UPF_A235 supports anchoring for intra-RAT mobility or inter-RAT mobility, packet routing & forwarding, UL CL (Uplink Classifier) functionality that supports routing of multiple traffic flows to one DN, Branching point function that supports multi-homed PDU sessions, QoS processing for user plane, uplink traffic verification, downlink packet buffering, and downlink data notification. It may also play a role such as a trigger function. Moreover, UPF_A235 may be a relay device that transfers user data as a gateway between the DN and core network_B190. Note that the UPF_A 235 may be a gateway for IP communication and/or non-IP communication. Furthermore, UPF_A235 may have a function of transferring IP communication, or may have a function of converting non-IP communication and IP communication. Furthermore, the plurality of gateways may be a gateway that connects the core network_B190 and a single DN. Note that the UPF_A 235 may have connectivity with other NFs, and may be connected to each device via other NFs.

Note that a UPF different from UPF_A 235, UPF_C 239 (also referred to as branching point or uplink classifier), may exist as a device or NF between UPF_A 235 and the access network. If UPF_C239 exists, the PDU session between the UE and the DN will be established via the access network, UPF_C239, UPF_A235.

Additionally, the UPF 130 may be a device similar to the UPF_A 235. Note that UPF130 and UPF_A235 may be written without symbols, like UPF.

[2. Configuration of each device]
Next, the configuration of each device (UE, access network device, and/or core network device) used in each embodiment will be described using diagrams. Note that each device may be configured as physical hardware, logical (virtual) hardware configured on general-purpose hardware, or configured as software. It's okay to be. Further, at least some (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

In addition, each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) in each device/function mentioned below is composed of, for example, a semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each memory unit can store not only information that was originally set at the time of shipment, but also various information transmitted and received between the device/function other than the device/function itself (for example, UE, and/or access network device, and/or core network device, and/or PDN, and/or DN). In addition, each memory unit can store identification information, control information, flags, parameters, etc. contained in control messages transmitted and received within various communication procedures described below. In addition, each memory unit may store this information for each UE. In addition, when interworking is performed between 5GS and EPS, each memory unit can store control messages and user data transmitted and received between 5GS and/or devices/functions included in EPS. At this time, it is possible to store not only those sent and received via the N26 interface, but also those sent and received without going through the N26 interface.

[2.1. UE device configuration]
First, an example of the configuration of a UE (User Equipment) will be described using FIG. 3. The UE includes a control unit_A300, an antenna 310, a transmitting/receiving unit_A320, and a storage unit_A340. The control unit_A300, the transmitting/receiving unit_A320, and the storage unit_A340 are connected via a bus. The transmitting/receiving unit_A320 is connected to the antenna 310.

The control unit_A300 is a functional unit that controls the operations and functions of the entire UE. The control unit_A300 implements various processes in the UE by reading and executing various programs stored in the storage unit_A340 as necessary.

The transmitting/receiving unit_A320 is a functional unit for wirelessly communicating with a base station device (eNB or gNB) in the access network via an antenna. That is, the UE can transmit and receive user data and/or control information between the access network device and/or the core network device and/or the PDN and/or the DN using the transmitter/receiver_A320. can.

To explain in detail with reference to FIG. 2, the UE can communicate with the base station apparatus (eNB) in the E-UTRAN via the LTE-Uu interface by using the transmitting/receiving unit_A320. In addition, the UE can communicate with a base station device (gNB) within the 5G AN by using the transceiver unit_A320. Furthermore, by using the transmitter/receiver unit_A320, the UE can transmit and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface. However, since the N1 interface is logical, in reality, communication between the UE and AMF takes place via 5G AN.

The storage unit_A340 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UE.

[2.2. gNB device configuration]
Next, an example of the gNB device configuration will be described using FIG. 4. gNB is composed of a control unit_B500, an antenna 510, a network connection unit_B520, a transmitting/receiving unit_B530, and a storage unit_B540. The control unit_B500, network connection unit_B520, transmission/reception unit_B530, and storage unit_B540 are connected via a bus. The transmitting/receiving unit_B530 is connected to the antenna 510.

The control unit_B500 is a functional unit that controls the operations and functions of the entire gNB. The control unit_B500 implements various processes in the gNB by reading and executing various programs stored in the storage unit_B540 as necessary.

The network connection unit_B520 is a functional unit for gNB to communicate with AMF and/or UPF. That is, the gNB can send and receive user data and/or control information to and from the AMF and/or UPF using the network connection unit_B520.

The transmitting/receiving unit_B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can transmit and receive user data and/or control information to and from the UE using the transmitting and receiving unit_B530.

Explaining in more detail with reference to Figure 2, a gNB in a 5G AN can communicate with the AMF via the N2 interface by using the network connection unit_B520, and can communicate with the UPF via the N3 interface. The gNB can also communicate with a UE by using the transceiver unit_B530.

The storage unit_B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB.

[2.3. AMF device configuration]
Next, an example of an AMF device configuration will be described using FIG. 5. AMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. AMF may be a node that handles the control plane.

The control unit_B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit_B700 realizes various processes in the AMF by reading and executing various programs stored in the memory unit_B740 as necessary.

The network connection unit_B720 is a functional unit for AMF to connect with the base station device (gNB), and/or SMF, and/or PCF, and/or UDM, and/or SCEF in the 5G AN. In other words, the AMF uses the network connection part_B720 to communicate with the base station equipment (gNB) in the 5G AN, and/or the SMF, and/or the PCF, and/or the UDM, and/or the SCEF. Data and/or control information can be sent and received.

To explain in detail with reference to Figure 2, AMF in 5GCN can communicate with gNB via N2 interface by using network connection_A620, and communicate with UDM via N8 interface. Through the N11 interface, it can communicate with the SMF, and through the N15 interface, it can communicate with the PCF. Furthermore, by using the network connection unit_A620, the AMF can send and receive NAS messages to and from the UE via the N1 interface. However, since the N1 interface is logical, in reality, communication between the UE and AMF takes place via 5G AN. Furthermore, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit_A620.

The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the AMF.

AMF has a function to exchange control messages with the RAN using the N2 interface, a function to exchange NAS messages with the UE using the N1 interface, a function to perform encryption and integrity protection of NAS messages, and registration management. (Registration management; RM) function, Connection management (CM) function, Reachability management function, Mobility management function for UE etc., SM (Session Management) between UE and SMF N2 for message forwarding function, access authentication (Access Authentication, Access Authorization) function, Security Anchor Functionality (SEA), Security Context Management (SCM) function, N3IWF (Non-3GPP Interworking Function) It has a function to support the interface, a function to support transmission and reception of NAS signals with the UE via N3IWF, a function to authenticate the UE connected via N3IWF, etc.

Additionally, in registration management, the RM status of each UE is managed. The RM state may be synchronized between the UE and the AMF. The RM state includes a non-registered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered in the network, and the UE context in the AMF does not have valid location information or routing information for the UE, so the AMF cannot reach the UE. Furthermore, in the RM-REGISTERED state, the UE is registered with the network, so the UE can receive services that require registration with the network. Note that the RM state may be expressed as a 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as a 5GMM-REGISTERED state.

In other words, 5GMM-REGISTERED may be a state where each device has established a 5GMM context or a state where a PDU session context has been established. Note that when each device is 5GMM-REGISTERED, UE_A10 may start transmitting and receiving user data and control messages, or may respond to paging. Furthermore, if each device is 5GMM-REGISTERED, the UE_A10 may execute a registration procedure other than the registration procedure for initial registration and/or a service request procedure.

Furthermore, 5GMM-DEREGISTERED may be a state where each device has not established a 5GMM context, a state where the location information of UE_A10 is not known to the network, or a state where the network has reached UE_A10. It may be in a state where it is impossible. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may start a registration procedure, or may establish a 5GMM context by executing the registration procedure.

Additionally, in connection management, the CM status of each UE is managed. The CM state may be synchronized between the UE and the AMF. The CM states include a disconnected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection established with the AMF via the N1 interface. Furthermore, in the CM-IDLE state, the UE does not have an N2 interface connection (N2 connection) or an N3 interface connection (N3 connection). On the other hand, in the CM-CONNECTED state, it has a NAS signaling connection established with AMF via the N1 interface. Furthermore, in the CM-CONNECTED state, the UE may have an N2 interface connection and/or an N3 interface connection.

Furthermore, in connection management, the CM status in 3GPP access and the CM status in non-3GPP access may be managed separately. In this case, the CM state in 3GPP access may include a disconnected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over 3GPP access). Furthermore, the CM states in non-3GPP access include the disconnected state (CM-IDLE state over non-3GPP access) and the connected state (CM-CONNECTED state over non-3GPP access) in non-3GPP access. ) is fine. Note that the disconnected state may be expressed as an idle mode, and the connected state mode may be expressed as a connected mode.

Note that the CM state may also be expressed as 5GMM mode. In this case, the disconnected state may be expressed as 5GMM-IDLE mode, and the connected state may be expressed as 5GMM-CONNECTED mode. Furthermore, the disconnected state in 3GPP access may be expressed as 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access may be expressed as 5GMM-IDLE mode over 3GPP access. CONNECTED mode over 3GPP access). Furthermore, the disconnected state in non-3GPP access may be expressed as 5GMM disconnected mode (5GMM-IDLE mode over non-3GPP access) in non-3GPP access, and the connected state in non-3GPP access is - It may be expressed as 5GMM-CONNECTED mode over non-3GPP access. Note that the 5GMM unconnected mode may be expressed as an idle mode, and the 5GMM connected mode may be expressed as a connected mode.

Furthermore, one or more AMFs may be placed within the core network_B. Furthermore, the AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). Furthermore, the AMF may be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among multiple NSIs.

Note that N3IWF is a device and/or function placed between non-3GPP access and 5GCN when UE connects to 5GS via non-3GPP access.

[2.4. SMF device configuration]
Next, an example of the SMF device configuration will be described using FIG. 5. The SMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF may be a node that handles the control plane.

The control unit_B700 is a functional unit that controls the operations and functions of the entire SMF. The control unit_B700 implements various processes in the SMF by reading and executing various programs stored in the storage unit_B740 as necessary.

The network connection unit_B720 is a functional unit for SMF to connect with AMF, and/or UPF, and/or PCF, and/or UDM. That is, the SMF can send and receive user data and/or control information to and from the AMF and/or the UPF and/or the PCF and/or the UDM using the network connection_B720.

To explain in detail with reference to Figure 2, the SMF in 5GCN can communicate with AMF through N11 interface by using network connection_A620, and can communicate with UPF through N4 interface. Through the N7 interface, it can communicate with the PCF, and through the N10 interface, it can communicate with the UDM.

The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the SMF.

SMF has session management functions such as establishing, modifying, and releasing PDU sessions, IP address allocation and management functions for UEs, UPF selection and control functions, and appropriate destination (transmission destination) functions. ) function to configure UPF to route traffic to It has the function of providing AN-specific (for each AN) SM information sent to the network, the function of determining the SSC mode (Session and Service Continuity mode) for the session, the roaming function, etc.

[2.5. UPF device configuration]
Next, an example of a UPF device configuration will be described using FIG. 5. The UPF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The UPF may be a node that handles the control plane.

The control unit_B700 is a functional unit that controls the operations and functions of the entire UPF. The control unit_B700 implements various processes in the UPF by reading and executing various programs stored in the storage unit_B740 as necessary.

The network connection unit_B720 is a functional unit for UPF to connect to the base station device (gNB) and/or SMF and/or DN in the 5G AN. In other words, the UPF uses the network connection part_B720 to transmit and receive user data and/or control information between the base station equipment (gNB) and/or SMF and/or DN in the 5G AN. Can be done.

To explain in detail with reference to Figure 2, the UPF in 5GCN can communicate with the gNB through the N3 interface by using the network connection part_A620, and can communicate with the SMF through the N4 interface. Through the N6 interface, it can communicate with the DN, and through the N9 interface, it can communicate with other UPFs.

The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UPF.

The UPF functions as an anchor point for intra-RAT mobility or inter-RAT mobility, as an external PDU session point for interconnecting to the DN (i.e., as a gateway between the DN and core network packet routing and forwarding functions, UL CL (Uplink Classifier) function that supports routing of multiple traffic flows to one DN, and multi-homed PDU sessions. It has branching point function, QoS (Quality of Service) processing function for user plane, uplink traffic verification function, downlink packet buffering, downlink data notification trigger function, etc.

Additionally, the UPF may be a gateway for IP communication and/or non-IP communication. Further, the UPF may have a function of transferring IP communication, or may have a function of converting between non-IP communication and IP communication. Furthermore, the plurality of gateways may be a gateway that connects core network_B and a single DN. Note that the UPF may have connectivity with other NFs, and may be connected to each device via other NFs.

Note that the user plane refers to user data that is transmitted and received between the UE and the network. The user plane may be sent and received using a PDN connection or a PDU session. Furthermore, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface and/or the S1-U interface and/or the S5 interface and/or the S8 interface and/or the SGi interface. Furthermore, in the case of 5GS, the user plane may be transmitted and received via the interface between the UE and the NG RAN, and/or the N3 interface, and/or the N9 interface, and/or the N6 interface. Hereinafter, the user plane may be expressed as U-Plane.

Furthermore, the control plane is a control message that is sent and received to control communication of the UE. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and the MME. Furthermore, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Furthermore, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and the NG RAN, and the N2 interface. Hereinafter, the control plane may be expressed as a control plane or as a C-Plane.

Further, the U-Plane (User Plane; UP) may be a communication path for transmitting and receiving user data, and may be composed of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may be a communication path for transmitting and receiving control messages, and may be composed of a plurality of bearers.

[2.6. Description of other equipment and/or functions]
Next, other devices and/or functions will be explained.

The network refers to at least part of the access network_B, core network_B, and DN. Further, one or more devices included in at least a portion of the access network_B, core network_B, and DN may be referred to as a network or a network device. In other words, the fact that the network sends, receives, and/or processes messages may mean that devices within the network (network devices and/or control devices) send, receive, and/or process messages. . Conversely, a device within a network may send, receive, and/or process messages, which may mean that the network sends, receives, and/or processes messages. Also, the network may be referred to as NW.

Furthermore, the network may refer to a PLMN (Public Land Mobile Network) or may refer to an NPN (Non-Public Network), which will be described later. Furthermore, network selection may refer to PLMN selection or SNPN selection.

NWDAF (Network Data Analytics Function) may be an NF that has a function of collecting data from an NF or an application function (also referred to as AF).

A PCF (Policy Control Function) may be an NF that has a function of determining a policy for controlling network behavior.

NRF (Network Repository Function) may be an NF that has a service discovery function. The NRF may be an NF that has a function of providing information on the discovered NF upon receiving a discovery request for another NF from a certain NF.

UDM (Unified Data Management) is an NF that has authentication credential processing functions, user identification processing functions, access authentication functions, registration/mobility management functions, subscription management functions, etc. It's good to be there.

The SM (Session Management) message may be a NAS message used in SM procedures. The SM message may be referred to as a NAS (Non-Access-Stratum) SM message. The SM message may be a control message sent and received between UE_A10 and SMF_A230 via AMF_A240. In addition, SM messages include PDU session establishment request messages, PDU session establishment accept messages, PDU session establishment reject messages, and PDU session change request messages. modification request) message, PDU session modification command message, PDU session modification complete message, PDU session modification command reject message, PDU session modification command reject message, PDU session modification command reject message, PDU session modification command reject message, PDU session modification command reject message, PDU session modification command reject message, PDU session modification command reject message modification reject) message, PDU session release request message, PDU session release reject message, PDU session release command message, PDU session release complete ) messages etc. may be included.

Furthermore, the SM procedure (also referred to as the procedure for SM) may include a PDU session establishment procedure, a PDU session modification procedure, and a PDU session release procedure. Each procedure may be initiated by the UE or the network.

The MM (Mobility management) message may be a NAS message used for procedures for the MM. MM messages may be referred to as NAS MM messages. The MM message may be a control message sent and received between UE_A10 and AMF_A240. Furthermore, MM messages include registration request messages, registration accept messages, registration reject messages, non-registration request messages, and non-registration accept messages. Message, configuration update command message, configuration update complete message, service request message, service accept message, service reject message, notification Messages, notification response messages, etc. may be included.

In addition, MM procedures (also referred to as procedures for MM) include registration procedures, de-registration procedures, generic UE configuration update procedures, authentication/authorization procedures, and services. It may include a request procedure, a paging procedure, and a notification procedure.

The 5GS (5G System) service may be a connection service provided using the core network_B190. Furthermore, the 5GS service may be a service different from the EPS service, or may be a service similar to the EPS service.

A non-5GS service may be a service other than a 5GS service, and may include an EPS service and/or a non-EPS service.

S1 mode is a mode in which UE_A10 is permitted to access EPC via E-UTRAN. In other words, the S1 mode may be a mode in which messages are sent and received using the S1 interface. Note that the S1 interface may be composed of an S1-MME interface and an S1-U interface.

N1 mode is a mode in which UE_A10 is allowed to access 5GC via the 5G access network. In other words, the N1 mode may be a mode in which messages are sent and received using the N1 interface.

APN (Access Point Name) may be identification information that identifies a core network and/or an external network such as a PDN. Furthermore, the APN can also be used as information for selecting a gateway such as PGW_A30/UPF_A235 to connect core network A_90.

The PDN (Packet Data Network) type indicates the type of PDN connection, and includes IPv4, IPv6, IPv4v6, and non-IP. If IPv4 is specified, it indicates that data is sent and received using IPv4. If IPv6 is specified, it indicates that data is sent and received using IPv6. If IPv4v6 is specified, it indicates that data is sent and received using IPv4 or IPv6. If non-IP is specified, it indicates that communication is not using IP, but using a communication method other than IP.

A PDU (Protocol Data Unit) session, which can be defined as an association between a UE and a DN that provides PDU connectivity services, is a connectivity established between a UE and an external gateway. Good too. In 5GS, by establishing a PDU session via the access network_B and core network_B, the UE can send and receive user data to and from the DN using the PDU session. Here, this external gateway may be UPF, SCEF, etc. The UE can use the PDU session to send and receive user data to and from devices such as application servers located in the DN. Note that each device (UE, access network device, and/or core network device) may manage a PDU session by associating one or more pieces of identification information with it. Note that this identification information may include one or more of DNN, QoS rules, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, or may include other information. It may also be included. Furthermore, when establishing multiple PDU sessions, each piece of identification information associated with the PDU sessions may have the same content or may have different content.

DNN (Data Network Name) may be identification information that identifies a core network and/or an external network such as a DN. Furthermore, the DNN can also be used as information for selecting a gateway such as PGW/UPF to connect the core network B190. Furthermore, DNN may correspond to APN (Access Point Name).

The PDU (Protocol Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet, and Unstructured. If IPv4 is specified, it indicates that data will be sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Furthermore, Ethernet may indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data will be sent and received to the application server, etc. in the DN using Point-to-Point (P2P) tunneling technology. As the P2P tunneling technology, for example, UDP/IP encapsulation technology may be used. Note that the PDU session type may include IP in addition to the above. IP can be specified if the UE can use both IPv4 and IPv6.

PLMN (Public land mobile network) is a communication network that provides mobile wireless communication services. PLMN is a network managed by an operator, which is a telecommunications carrier, and the operator can be identified by the PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscription Identity) may be the Home PLMN (HPLMN). Furthermore, the UE may maintain an Equivalent PLMN list for identifying one or more EPLMNs (Equivalent PLMNs) in the USIM. A PLMN different from HPLMN and/or EPLMN may be VPLMN (Visited PLMN). The PLMN in which the UE has been successfully registered may be an RPLMN (Registered PLMN).

Additionally, a registered PLMN is a PLMN in which the UE is registered.

In addition, an equivalent PLMN is a PLMN that is treated by the network as if it were the same PLMN as any PLMN. For example, an equivalent PLMN may be one or more PLMNs that are treated the same as a registered PLMN.

PLMN selection may be a procedure for the UE to select a PLMN. Here, PLMN selection may be performed when the UE connects to the PLMN. Here, the PLMN selection may be referred to as a PLMN selection process or a PLMN selection procedure.

Here, the UE that is not operating in the SNPN access mode or the SNPN access operation mode may perform PLMN selection. Also, a UE operating in SNPN access mode or SNPN access operation mode does not need to perform PLMN selection. Also, PLMN selection may be performed without registration. In other words, PLMN selection may be performed when the UE has not completed registration with the network. PLMN selection may include an automatic PLMN selection mode and a manual PLMN selection mode. Note that PLMN selection may refer to automatic PLMN selection mode or manual PLMN selection mode.

A tracking area is a single or multiple range managed by the core network that can be represented by the location information of UE_A10. Note that the tracking area may be composed of a plurality of cells. Further, the tracking area may be a range where control messages such as paging are broadcast, or a range where UE_A10 can move without performing a handover procedure. Furthermore, the tracking area may be a routing area, a location area, or anything similar thereto. Hereinafter, the tracking area may be a TA (Tracking Area). A tracking area may be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking Area Code) and a PLMN.

A registration area is a collection of one or more TAs assigned to a UE by the AMF. Note that while the UE_A10 is moving within one or more TAs included in the registration area, it may be possible to move without transmitting or receiving a signal for updating the tracking area. In other words, the registration area may be a group of information indicating an area to which the UE_A10 can move without executing a tracking area update procedure. A registration area may be identified by a TAI list comprised of one or more TAIs.

UE ID is information for identifying the UE. For example, the UE ID may be SUCI, SUPI, IMSI, GUTI, 5G-GUTI, IMEI, IMEISV, TMSI, or 5G-S-TMSI. Alternatively, the UE ID may be other information configured within the application or network. Furthermore, the UE ID may be information for identifying a user.

The SUCI (Subscription Concealed Identifier) may be a privacy preserving identifier that includes a concealed SUPI. Further, the SUCI may be composed of SUPI Type, Home Network Identifier, Routing Indicator, Protection Scheme Id, Home Network Public Key Identifier, and Scheme Output.

SUPI (Subscription Permanent Identifier) may be a globally unique identifier assigned to each subscriber in the 5G system. SUPI may be defined as SUPI type and IMSI or NSI or GCI (Global Cable Identifier) or GLI (Global Line Identifier). Additionally, the SUPI type may indicate IMSI, NSI, GCI, or GLI. That is, when the SUPI type indicates IMSI, SUPI may be composed of the SUPI type indicating IMSI and IMSI. Similarly, when the SUPI type indicates NSI, SUPI may be composed of the SUPI type indicating NSI and NSI. Furthermore, when the SUPI type indicates GCI, SUPI may be composed of the SUPI type indicating GCI and GCI. Further, when the SUPI type indicates GLI, SUPI may be composed of the SUPI type indicating GLI and GLI.

IMSI (International Mobile Subscription Identity) may be composed of MCC (Mobile Country Code), MNC (Mobile Network Code), and MSIN (Mobile Subscriber Identification Number).

5G-GUTI (5G Globally Unique Temporary Identifier) may be information for providing an unambiguous UE identifier that does not reveal the UE or user's permanent identity. Furthermore, 5G-GUTI may be information that can also identify the AMF and network. 5G-GUTI may also be information used by the network and the UE to establish the identity of the UE. Furthermore, the 5G-GUTI may be composed of two elements: one that identifies the AMF that allocated the 5G-GUTI, and one that uniquely identifies the UE within the AMF that allocated the 5G-GUTI. The former may be GUAMI (Globally Unique AMF Identifier), and the latter may be 5G-TMSI (5G-Temporary Mobile Subscriber Identity). That is, 5G-GUTI may be composed of GUAMI and 5G-TMSI.

IMEI (International Mobile station Equipment Identity) may be composed of TAC (Type Allocation Code), SNR (Serial Number), and CD (Check Digit)/SD (Spare Digit).

IMEISV (International Mobile station Equipment Identity and Software Version number) may be composed of TAC (Type Allocation Code), SNR (Serial Number), and SVN (Software Version Number).

5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) may be an abbreviation of 5G-GUTI. Furthermore, 5G-S-TMSI may enable more efficient radio signaling procedures (for example, paging (also referred to as paging procedure) and service request (also referred to as service request procedure)). Also, for paging, the UE may be paged using 5G-S-TMSI. 5G-S-TMSI may be composed of AMF Set ID, AMF Pointer, and 5G-TMSI.

The MAC address (Media Access Control address) may be the hardware address of a device connected to the shared media. Further, the MAC address may be a unique identification number given to the UE or network device.

EUI-64 (IEEE Extended Unique Identifier) may be a 64-bit long identifier standardized by the IEEE. Furthermore, EUI-64 may be used when automatically generating an IPv6 address.

PEI (Permanent Equipment Identifier) may be information for identifying the UE. Additionally, PEI may be defined as PEI type, IMEI or IMEISV, MAC address or EUI-64. Here, the PEI type may indicate IMEI or IMEISV or MAC address or EUI-64. That is, when the PEI type indicates an IMEI, the PEI may be composed of the PEI type indicating the IMEI and the IMEI. Similarly, when the PEI type indicates IMEISV, the PEI may be composed of the PEI type indicating IMEISV and IMEISV. Further, when the PEI type indicates a MAC address, the PEI may be composed of the PEI type indicating the MAC address and the MAC address. Furthermore, when the PEI type indicates EUI-64, the PEI may be composed of the PEI type indicating EUI-64 and EUI-64.

5GS mobile identity may be SUCI or 5G-GUTI or IMEI or IMEISV or 5G-S-TMSI or MAC address or IE to provide EUI-64. Furthermore, 5GS mobile identity may be referred to as a 5GS mobile identity information element (5GS mobile identity IE (information element)).

Additionally, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying the NS. S-NSSAI may be configured only with SST (Slice/Service type), or may be configured with both SST and SD (Slice Differentiator). Here, SST is information indicating the expected behavior of the NS in terms of functions and services. Further, the SD may be information for interpolating the SST when selecting one NSI from a plurality of NSIs indicated by the SST. The S-NSSAI may be information specific to each PLMN or SNPN, or may be standard information shared between PLMNs or SNPNs.

NPN (Non-Public Network) is a private network used by specific users for specific purposes. There are two types of NPN: SNPN (Stand-alone Non-Public Network) and PNI-NPN (Public Network Integrated NPN). Note that NPN may refer to SNPN, PNI-NPN, or both.

SNPN is a network operated by an NPN operator and unaffected by the functional units provided by PLMN. In other words, SNPN is an NPN-only network that is independent of PLMN, which is open to the public. An SNPN may be a network identified by an SNPN ID (SNPN identity). Note that the SNPN ID may be information that is a combination of the PLMN ID and the NID (Network identifier). Note that the PLMN ID used as the SNPN ID may be information reserved for the private network. For example, the MCC included in the PLMN ID may be 999. Furthermore, if the UE is registered with an SNPN, the registered SNPN may be referred to as a registered SNPN or RSNPN.

The NID is information that identifies a network. The SNPN may be identified by a combination of the PLMN ID and the NID. The NID may be information that is unique within the SNPN, or may be information that is unique worldwide.

PNI-NPN is a network realized using the functional parts of PLMN. In other words, PNI-NPN is an NPN that is virtually realized within the PLMN. Furthermore, PNI-NPN is an NPN that can be created via PLMN. Note that PNI-NPN may be realized using a network slice function. Specifically, PNI-NPN may be a network that can be realized by using network slices allocated for NPN. In this case, the PNI-NPN may be identified by S-NSSAI or by a combination of S-NSSAI and CAG ID. Furthermore, PNI-NPN may be implemented using DN. Specifically, PNI-NPN may be a network that can be realized by using a DN for NPN. In this case, the PNI-NPN may be identified by a DNN or by a combination of a DNN and a CAG ID.

CAG (Closed Access Groups) is a group used when realizing PNI-NPN. Further, a CAG may be a group identified by a CAG ID. The CAG may also be used to prevent UEs that are not authorized for NPN from attempting to access network slices allocated for NPN.

CAG ID is information that identifies the CAG within the PLMN. Additionally, the CAG ID is a unique identifier within the PLMN.

An SNPN-enabled UE may be a UE that can use an SNPN. An SNPN-enabled UE may store at least one piece of information related to an SNPN. In other words, the configuration information of an SNPN-enabled UE may include information indicating that the use of an SNPN is possible. Furthermore, an SNPN-enabled UE may support an SNPN access mode or an SNPN access operation mode. In other words, an SNPN-enabled UE may operate in an SNPN access mode or an SNPN access operation mode.

The SNPN access mode may be a mode for the UE to select an SNPN. Further, the SNPN access mode may be a mode in which the UE is registered with the SNPN. Furthermore, the SNPN access mode may be a mode in which the UE is connected to the SNPN. In other words, a UE operating in SNPN access mode may select only SNPN when selecting a network. More specifically, a UE operating in SNPN access mode may only select SNPN over the Uu interface during network selection. In other words, a UE operating in SNPN access mode may select SNPN without selecting PLMN when selecting a network. Here, the UE operating in SNPN access mode may be expressed as UE in SNPN access mode. Furthermore, the UE in SNPN access mode may be an SNPN enabled UE.

SNPN access operation mode is a mode for connecting to SNPN via SNPN access mode or non-3GPP access. Here, "non-3GPP access" in the SNPN may refer to a case where the UE is connected to the SNPN via the PLMN. Additionally, when operating in the SNPN access mode, the UE may operate in the SNPN access operation mode. Also, if the UE does not operate in the SNPN access mode, it may not operate in the SNPN access operation mode. Furthermore, the UE in SNPN access mode may be a UE in SNPN access operation mode. Note that SNPN access operation mode may be read as SNPN access mode.

SNPN selection may be a procedure for the UE to select an SNPN. Furthermore, SNPN selection may be a procedure performed when the UE connects to the SNPN. Further, SNPN selection may be referred to as an SNPN selection process or an SNPN selection procedure. Furthermore, SNPN selection may be a process for the UE to select an SNPN. Additionally, SNPN selection may be a process performed when a UE connects to an SNPN.

Here, the UE operating in the SNPN access mode or the SNPN access operation mode may perform SNPN selection. Furthermore, a UE that is not operating in the SNPN access mode or the SNPN access operation mode may not perform SNPN selection. Further, the SNPN selection may include an automatic SNPN selection mode and a manual SNPN selection mode. Also, SNPN selection may be performed without registration. In other words, SNPN selection may be performed when the UE has not completed registration with the network. Note that SNPN selection may refer to automatic SNPN selection mode or manual SNPN selection mode.

An equivalent SNPN (equivalent PLMN) may be an SNPN that is treated as the same SNPN as any other SNPN. For example, an equivalent SNPN may be one or more SNPNs that are treated the same as registered SNPNs. Further, an equivalent SNPN may be a PLMN that is treated as if it were the same SNPN as any SNPN. For example, an equivalent SNPN may be one or more PLMNs that are treated the same as registered SNPNs.

Further, the equal SNPN may be one or more SNPNs identified by the same PLMN ID as any SNPN, or may be a PLMN. For example, the equivalent SNPN may be one or more SNPNs identified by the same PLMN ID as the registered SNPN, or may be a PLMN. Further, the equivalent SNPN may be a PLMN identified by the same PLMN ID as the registered SNPN, and an equivalent PLMN of said PLMN.

Localized services may be services provided in a specific/restricted area. Local services may also be limited in time. A local service may be referred to as a local service. Localized services may also be implemented via applications such as live or on-demand audio or video streams, or video games, or IMS. Also, localized services may be realized via connectivity such as UE to UE or UE to DN.

Also, local services may be read as a hosting network. Local services may be provided by a hosting network. Local services are supported may be read as a hosting network is supported.

A localized service provider may be an application provider or network operator that localizes and provides services to end users via a hosting network. A local service provider may also be an application provider or a network operator that provides local services. The local service provider may also be a DN. The local service provider may also be a core network.

A hosting network may be a network that provides connectivity to local services. Further, the hosting network may be NPN. Here, NPN may be SNPN or PNI-NPN.

Also, hosting network may be read as local service. In addition, "hosting network is supported" may be read as "local services are supported."

The home network may be the network that owns the subscription or credentials of the UE currently in use. The home network may be a PLMN or an NPN. Here, the NPN may be an SNPN or a PNI-NPN.

A home network service may be a service provided to a UE based on a subscription agreed with a home network operator. Further, the home network service may be a service provided by a home network.

[2.7. Description of Identification Information in the Present Embodiment]
Next, the identification information transmitted, received, stored, and/or managed by each device in this embodiment will be described.

First, the first identification information is DNN. Further, the first identification information may be a DNN related to a local service. Further, the first identification information may be a DNN related to the third identification information. Further, the first identification information may be the same as the tenth identification information.

Next, the second identification information is S-NSSAI. Additionally, the second identification information may be an S-NSSAI related to a local service. Further, the second identification information may be S-NSSAI related to the third identification information. Furthermore, the second identification information may be the same as the eleventh identification information.

Next, the third identification information may be an identifier of a local service. Further, the third identification information may be a service identifier indicating a local service. Further, the third identification information may indicate an identifier of a local service used by the UE. Furthermore, the third identification information may also indicate an identifier of a local service requested by the UE. Here, the third identification information may be the same as the twelfth identification information. Here, the third identification information may be an identifier of one or more local services indicated by the twelfth identification information. Here, the third identification information may be associated with the first identification information and/or the second identification information.

Additionally, the third identification information may be an identifier selected from one or more local service identifiers stored in the UE. Furthermore, the third identification information may be an identifier selected from the twelfth identification information.

Next, the fourth identification information may be information indicating whether or not local services are supported. Further, the fourth identification information may be information indicating that a local service is supported. Further, the fourth identification information may be information indicating that local services are not supported.

Additionally, the fourth information may be indicated using the 5GSM capability IE or the 5GMM capability IE.

Next, the tenth identification information is a DNN. The tenth identification information may also be a DNN associated with a local service. The tenth identification information may also be a DNN associated with the twelfth identification information. The tenth identification information may also be the same as the first identification information.

Next, the eleventh identification information is S-NSSAI. Further, the eleventh identification information may be an S-NSSAI related to a local service. Further, the eleventh identification information may be S-NSSAI related to the twelfth identification information. Furthermore, the eleventh identification information may be the same as the second identification information.

Next, the twelfth identification information may be an identifier of a local service. Further, the twelfth identification information may be a service identifier indicating a local service. Further, the twelfth identification information may be an identifier of an available local service. Furthermore, the twelfth identification information may be an identifier of a local service available to the UE and/or the network. Further, the twelfth identification information may be the same as the third identification information.

Additionally, the twelfth identification information may be a list composed of one or more local service identifiers. Further, the twelfth identification information may be a list composed of identifiers of one or more available local services. Further, the twelfth identification information may be a list composed of one or more identifiers of local services that can be used by the UE and/or the network.

Additionally, the twelfth identification information may be information associated with the tenth identification information and/or the eleventh identification information.

Next, the thirteenth identification information may be information indicating that the local service is authenticated and/or approved. Further, the thirteenth identification information may be information indicating that the local service is not authenticated and/or approved. Furthermore, the thirteenth identification information may be information indicating whether or not to authenticate and/or approve the local service.

Additionally, the thirteenth identification information may be information indicating that local services are permitted. Further, the thirteenth identification information may be information indicating that local services are not permitted. Furthermore, the thirteenth identification information may be information indicating whether or not local services are permitted.

Furthermore, the thirteenth identification information may be information associated with one or more identification information among the first to fourth identification information. Further, the thirteenth identification information may be information associated with one or more of the tenth to twelfth and fourteenth identification information.

Further, the thirteenth identification information may include identification information received by the network, and/or information associated with the NSI, and/or network capability information, and/or operator policy, and/or network status; /Or the information may be selected or determined based on the user's registered information or the like.

Next, the fourteenth identification information may be a reason value indicating that the local service is unavailable. Further, the fourteenth identification information may be a reason value indicating that the local service requested by the UE is not available. Further, the fourteenth identification information may be a reason value indicating that the local service indicated by the third identification information cannot be used. The fourteenth identification information may be a 5GSM (5GS Session Management) reason value.

Additionally, the fourteenth identification information may be a reason value indicating that the local service is not available at the time. Further, the fourteenth identification information may be a reason value indicating that the local service requested by the UE is not available at a time. Further, the fourteenth identification information may be a reason value indicating that the local service indicated by the third identification information is not available at a time.

Additionally, the fourteenth identification information may be a reason value indicating that authentication and/or approval of the local service is to be revoked. Furthermore, the fourteenth identification information may be a reason value indicating that the authentication and/or approval of the local service indicated by the thirteenth identification information is to be cancelled.

The 14th identification information may also be a reason value indicating that permission for the local service is to be revoked. The 14th identification information may also be a reason value indicating that permission for the local service indicated by the 13th identification information is to be revoked.

Additionally, the fourteenth identification information may be a reason value indicating that the local service corresponding to the service identifier is unavailable. Further, the fourteenth identification information may be a reason value indicating that the local service indicated by the service identifier is unavailable. Here, the service identifier may be a service identifier indicated by the third identification information and/or the twelfth identification information.

Furthermore, the fourteenth identification information may include identification information received by the network, and/or information associated with the NSI, and/or network capability information, and/or operator policy, and/or network status; /Or the information may be selected or determined based on the user's registered information or the like.

[3. Description of procedures used in each embodiment]
Next, procedures used in each embodiment will be explained. Each procedure will be explained below.

In each embodiment, as shown in FIG. An example will be explained in which they are configured as hardware, the same logical hardware, or the same software. However, what is described in this embodiment is also applicable when these are configured as different devices (ie, different physical hardware, different logical hardware, or different software). For example, data may be sent and received directly between them, data may be sent and received via the N26 interface between the AMF and MME, or data may be sent and received via the UE.

[3.1. Registration procedure]
First, the registration procedure will be explained using FIG. 6. The registration procedure is a procedure in 5GS. In this chapter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the lead in registering with the access network_B and/or the core network_B and/or the DN. As long as the UE is not registered with the network, it can execute this procedure at any timing, such as when turning on the power, for example. In other words, the UE can start this procedure at any timing if it is in the unregistered state (RM-DEREGISTERED state). Furthermore, each device (particularly the UE and AMF) can transition to a registered state (RM-REGISTERED state) based on the completion of the registration procedure. Note that the registration status may be managed by each device for each access. Specifically, each device may independently manage the registration state for 3GPP access (registered state or unregistered state) and the registration state for non-3GPP access.

The registration procedure may also be a registration procedure for initial registration. The registration procedure may also be a registration procedure for mobility and periodic registration update.

Furthermore, the registration procedure may be used to update the location registration information of the UE in the network, and/or to periodically notify the UE status from the UE to the network, and/or to update certain parameters regarding the UE in the network. This procedure may be used.

Additionally, this procedure may be a registration procedure for a local service or a registration procedure for a hosting network.

The UE may initiate the registration procedure when it performs cross-TA mobility. In other words, the UE may start the registration procedure when it moves to a TA different from the TA indicated in the TA list it maintains. Additionally, the UE may initiate a registration procedure when the context of each device needs to be updated due to disconnection or invalidation of a PDU session. Additionally, the UE may initiate a registration procedure if there is a change in the capability information and/or preferences regarding the UE's PDU session establishment. Furthermore, the UE may periodically initiate a registration procedure. Furthermore, the UE may initiate a registration procedure based on the completion of the UE configuration update procedure. Note that the UE is not limited to these, and can execute the registration procedure at any timing.

Additionally, the UE may start registration procedures periodically even in the registered state.

Note that the registration procedure executed based on the mobility of the UE and the registration procedure executed periodically may be expressed as a registration procedure for mobility and registration update. In other words, the registration procedure for mobility and registration update may be a registration procedure performed based on the mobility of the UE, or may be a registration procedure performed periodically. Furthermore, the registration procedure for mobility and registration updates may be a registration procedure performed based on a configuration update of the UE. Furthermore, the registration procedure for mobility and registration updates may be a registration procedure performed to establish a communication path for transmitting and receiving user data. Furthermore, the registration procedure for mobility and registration update may be a registration procedure performed based on a request from the network. Furthermore, in other words, the registration procedure for mobility and registration renewal may be a registration procedure other than the registration procedure for initial registration.

Next, we will explain each step of the registration procedure. Note that the registration procedure described below may be a registration procedure for initial registration, or may be a registration procedure for mobility and registration update.

First, the UE starts the registration procedure by sending a registration request message to the AMF (S800) (S802) (S804). Specifically, the UE sends an RRC message including a registration request message to the 5G AN (or gNB) (S800). The registration request message is a NAS message. The RRC message may be a control message transmitted and received between the UE and the 5G AN (or gNB). The NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.

Here, the UE may transmit one or more of the third to fourth identification information in a registration request message and/or an RRC message. More specifically, the UE may transmit one or more of the third to fourth identification information in a registration request message and/or an RRC message, or may transmit one or more of the third to fourth identification information in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, a MAC layer, an RLC layer, a PDCP layer).

Specifically, the UE may indicate to the network an identifier of the requested local service by transmitting a third identification, where the third identification may be the same as the twelfth identification. Here, the third identification may be an identifier of one or more local services indicated by the twelfth identification. Here, the third identification may be associated with the first identification and/or the second identification.

The UE may also indicate to the network that it supports local services by transmitting the fourth identification information. The UE may also indicate to the network whether it supports local services by transmitting the fourth identification information.

Note that by transmitting these identification information, the UE may indicate to the network that the UE supports each function, or may indicate the UE's request. Furthermore, when a plurality of pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

Furthermore, by transmitting one or more pieces of identification information among the third to fourth pieces of identification information in the registration request message, the UE indicates to the network the content indicated by the identification information included in the registration request message. Good too.

Note that the UE determines whether to include one or more of the third to fourth pieces of identification information in the registration request message based on subscriber information, network status, and/or user registration information. Alternatively, it may be selected and determined based on the context held by the UE.

Note that the UE may include identification information other than the third to fourth identification information in the registration request message and transmit it.

When the 5G AN (or gNB) receives the RRC message including the registration request message, it selects an AMF to which to transfer the registration request message (S802). Note that the 5G AN (or gNB) can select an AMF based on information included in the registration request message and/or the RRC message. The 5G AN (or gNB) extracts the registration request message from the received RRC message and transfers the registration request message to the selected AMF (S804).

The AMF may perform the first condition determination when receiving the registration request message. The first condition determination is for determining whether the network (or AMF) accepts the UE request. If the first condition determination is true, the AMF starts the procedure in (A) of FIG. 6, whereas if the first condition determination is false, it starts the procedure in FIG. 6 (B).

Note that the first condition determination is based on reception of a registration request message, and/or each identification information included in the registration request message, subscriber information, and/or network capability information, and/or operator policy, and/or each identification information included in the registration request message. It may be executed based on the state of the network, the user's registration information, the context held by the AMF, and/or the like. For example, the first condition determination may be true if the network grants the UE's request, and false if the network does not grant the UE's request. Furthermore, if the network to which the UE is registered and/or the equipment within the network supports the function requested by the UE, the first condition determination is true, and the function requested by the UE is not supported. , the first conditional determination may be false. Furthermore, if the identification information to be transmitted and received is permitted, the first condition determination may be true, and if the identification information to be transmitted and received is not permitted, the first condition determination may be false. Note that the conditions for determining the truth of the first condition determination are not limited to the conditions described above.

First, the case where the first condition determination is true will be explained. In the procedure of (A) in FIG. 6, the AMF transmits a registration accept message to the UE via the 5G AN (or gNB) as a response message to the registration request message (S806). Note that the registration acceptance message is a NAS message sent and received on the N1 interface, but is included in the RRC message and sent and received between the UE and 5G AN (gNB).

The AMF may send the registration acceptance message including one or more of the 12th to 14th pieces of identification information. Note that by transmitting these identification information, the AMF may indicate that the network supports each function, or may indicate that the UE's request has been accepted. Furthermore, when a plurality of pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

Furthermore, the AMF may indicate to the UE what these pieces of identification information indicate by including and transmitting one or more pieces of identification information among the twelfth to fourteenth pieces of identification information in the registration acceptance message. The AMF may also indicate the contents of these identification information to the UE by sending a registration acceptance message.

Specifically, the network may indicate the local service identifier to the UE by transmitting the twelfth identification information. The network may also indicate to the UE a list comprised of identifiers of one or more local services by transmitting the twelfth identification information.

The network may also indicate to the UE whether to authenticate and/or authorize the local service by transmitting the thirteenth identification information.

The network may also indicate to the UE that the local service is unavailable by transmitting the fourteenth identification information.

The AMF shall determine whether to include one or more of the 12th to 14th identification information in the registration acceptance message based on each received identification information and/or subscriber information and/or network capability information. , and/or operator policy, and/or network status, and/or user registration information, and/or context held by the AMF.

In addition, the AMF may also include identification information other than identification information 12 to 14 in the registration acceptance message.

The AMF may also collect each received identification information, and/or subscriber information, and/or network capability information, and/or operator policy, and/or network status, and/or user registration information, and/or It may be indicated that the UE's request has been accepted by transmitting a registration acceptance message based on the context held by the AMF.

Additionally, the AMF may include and send information indicating that some of the UE's requests have been rejected in the registration acceptance message, or may send information indicating that some of the UE's requests have been rejected. may indicate why some requests of the UE were rejected. Further, the UE may recognize the reason why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. Note that the reason for rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

Next, the UE receives a registration acceptance message from the AMF via the 5G AN (gNB) (S806). By receiving the registration acceptance message, the UE can recognize that the UE's request based on the registration request message has been accepted, and the contents of various types of identification information included in the registration acceptance message.

Specifically, the UE may recognize the local service identifier when receiving the twelfth identification information. The UE may also recognize the available local service identifier when receiving the twelfth identification information. The UE may also recognize the identifier of a local service available to the UE and/or the network when receiving the twelfth identification information.

Additionally, when the UE receives the twelfth identification information, the UE may store the local service identifier. Additionally, when the UE receives the twelfth identification information, it may store the identifier of the available local service. Additionally, when the UE receives the twelfth identification information, it may store an identifier of a local service available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, it may recognize a list made up of one or more local service identifiers. Additionally, when the UE receives the twelfth identification information, it may recognize a list comprised of identifiers of one or more available local services. The UE may also recognize, when receiving the twelfth identification information, a list comprised of identifiers of one or more local services available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, the UE may store a list composed of one or more local service identifiers. Further, when the UE receives the twelfth identification information, the UE may store a list consisting of identifiers of one or more available local services. The UE may also store a list comprised of identifiers of one or more local services available to the UE and/or the network when receiving the twelfth identification information.

Furthermore, when the UE receives the 12th identification information, it may associate it with the first identification information and/or the second identification information.Furthermore, when the UE receives the 12th identification information, it may store it in association with the first identification information and/or the second identification information.

The UE may also recognize that the local service has been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize that the local service has not been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize whether the local service is authenticated and/or authorized if it receives the thirteenth identification information.

Additionally, if the UE receives the thirteenth identification information, it may recognize that the local service has been granted. The UE may also recognize that the local service is not authorized if it receives the thirteenth identification information. Additionally, the UE may recognize whether local service is authorized or not when receiving the thirteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may associate it with one or more of the first to fourth identification information. Furthermore, when the UE receives the thirteenth identification information, it may associate it with the twelfth identification information and/or the fourteenth identification information.

Furthermore, when the UE receives the 13th identification information, it may store it in association with one or more of the first to fourth identification information.Furthermore, when the UE receives the 13th identification information, it may store it in association with the 12th identification information and/or the 14th identification information.

Additionally, if the UE receives the fourteenth identification information, it may recognize that the local service is not available. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available.

Furthermore, when the UE receives the 14th identification information, the UE may recognize that the local service is not available at that time.Furthermore, when the UE receives the 14th identification information, the UE may recognize that the local service requested by the UE is not available at that time.

Furthermore, when the UE receives the 14th identification information, the UE may recognize that authentication and/or authorization of the local service has been revoked.Furthermore, when the UE receives the 14th identification information, the UE may recognize that authentication and/or authorization of the local service indicated by the 13th identification information has been revoked.

Additionally, if the UE receives the fourteenth identification information, the UE may recognize that the local service authorization has been revoked. Further, when the UE receives the fourteenth identification information, the UE may recognize that permission for the local service indicated by the thirteenth identification information has been revoked.

Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service corresponding to the service identifier is unavailable. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service indicated by the service identifier is unavailable. Here, the service identifier may be a service identifier indicated by the third identification information and/or the twelfth identification information.

Note that the above behavior of the UE may be performed after receiving the registration acceptance message. Furthermore, the behavior of the UE may be performed after receiving one or more pieces of identification information among the twelfth to fourteenth pieces of identification information.

Furthermore, when the UE receives the registration acceptance message, the UE may perform the behavior when receiving each piece of identification information included in the registration acceptance message.

Next, the UE may or may not send a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S808). Here, the registration completion message is a NAS message sent and received on the N1 interface, but is included in an RRC message and sent and received between the UE and 5G AN (gNB).

Next, the AMF may or may not receive a registration completion message via the 5G AN (gNB) (S808).

Each device completes the procedure in (A) of FIG. 6 based on the transmission and reception of the registration acceptance message and/or registration completion message.

Next, a case where the first condition determination is false will be explained. In the procedure of (B) in FIG. 6, the AMF transmits a registration reject message to the UE via the 5G AN (gNB) as a response message to the registration request message (S810). Here, the registration rejection message is a NAS message transmitted and received on the N1 interface, but is included in the RRC message and transmitted and received between the UE and the 5G AN (gNB).

Here, the AMF may include one or more identification information among the twelfth to fourteenth identification information in the registration rejection message and send it. Additionally, the AMF may indicate that the UE's request has been rejected or may indicate the reason why the UE's request was rejected by transmitting these identification information.

Furthermore, the AMF may indicate to the UE the contents indicated by the identification information included in the registration rejection message by including one or more of the identification information items 12 to 14 in the registration rejection message and sending the message. The AMF may also indicate to the UE the contents of these identification information items by sending a registration rejection message.

Specifically, the network may indicate the local service identifier to the UE by transmitting the twelfth identification information. The network may also indicate to the UE a list comprised of identifiers of one or more local services by transmitting the twelfth identification information.

The network may also indicate to the UE whether to authenticate and/or authorize the local service by transmitting the thirteenth identification information.

The network may also indicate to the UE that the local service is unavailable by transmitting the fourteenth identification information.

In addition, AMF determines whether to include one or more identification information among the 12th to 14th identification information in the registration rejection message, based on each received identification information, subscriber information, and/or network capability information. , and/or operator policy, and/or network status, and/or user registration information, and/or context held by the AMF.

Furthermore, the AMF may indicate that the UE's request via the registration request message has been rejected by sending a registration rejection message. Furthermore, the AMF may include information indicating the reason for the rejection in the registration rejection message and send it, or may indicate the reason for the rejection by sending the reason for the rejection. Furthermore, the UE may recognize the reason for the rejection of the UE's request by receiving information indicating the reason for the rejection of the UE's request. In addition, the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

Next, the UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S810). By receiving the registration rejection message, the UE can recognize that the UE's request based on the registration request message has been rejected, and the contents of various types of identification information included in the registration rejection message.

Specifically, the UE may recognize the local service identifier when receiving the twelfth identification information. The UE may also recognize the available local service identifier when receiving the twelfth identification information. The UE may also recognize the identifier of a local service available to the UE and/or the network when receiving the twelfth identification information.

Additionally, when the UE receives the twelfth identification information, the UE may store the local service identifier. Additionally, when the UE receives the twelfth identification information, it may store the identifier of the available local service. Additionally, when the UE receives the twelfth identification information, it may store an identifier of a local service available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, it may recognize a list made up of one or more local service identifiers. Additionally, when the UE receives the twelfth identification information, it may recognize a list comprised of identifiers of one or more available local services. The UE may also recognize, when receiving the twelfth identification information, a list comprised of identifiers of one or more local services available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, the UE may store a list composed of one or more local service identifiers. Further, when the UE receives the twelfth identification information, the UE may store a list consisting of identifiers of one or more available local services. The UE may also store a list comprised of identifiers of one or more local services available to the UE and/or the network when receiving the twelfth identification information.

Furthermore, when the UE receives the twelfth identification information, it may associate it with the first identification information and/or the second identification information. Further, when the UE receives the twelfth identification information, the UE may store it in association with the first identification information and/or the second identification information.

The UE may also recognize that the local service has been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize that the local service has not been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize whether the local service is authenticated and/or authorized if it receives the thirteenth identification information.

Additionally, if the UE receives the thirteenth identification information, it may recognize that the local service has been granted. The UE may also recognize that the local service is not authorized if it receives the thirteenth identification information. Additionally, the UE may recognize whether local service is authorized or not when receiving the thirteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may associate it with one or more of the first to fourth identification information. Furthermore, when the UE receives the thirteenth identification information, it may associate it with the twelfth identification information and/or the fourteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may store it in association with one or more of the first to fourth identification information. Further, when the UE receives the thirteenth identification information, the UE may store it in association with the twelfth identification information and/or the fourteenth identification information.

Additionally, if the UE receives the fourteenth identification information, it may recognize that the local service is not available. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available.

Furthermore, when the UE receives the fourteenth identification information, the UE may recognize that the local service is not available at the time. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available at the time.

The UE may also recognize that the local service authentication and/or authorization has been revoked if the UE receives the fourteenth identification information. Further, when the UE receives the fourteenth identification information, the UE may recognize that the authentication and/or authorization of the local service indicated by the thirteenth identification information has been revoked.

Additionally, if the UE receives the fourteenth identification information, the UE may recognize that the local service authorization has been revoked. Further, when the UE receives the fourteenth identification information, the UE may recognize that permission for the local service indicated by the thirteenth identification information has been revoked.

Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service corresponding to the service identifier is unavailable. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service indicated by the service identifier is unavailable. Here, the service identifier may be a service identifier indicated by the third identification information and/or the twelfth identification information.

Note that the above behavior of the UE may be performed after receiving the registration rejection message. Furthermore, the behavior of the UE may be performed after receiving one or more pieces of identification information among the twelfth to fourteenth pieces of identification information.

Furthermore, when the UE receives a registration rejection message, it may perform the behavior when receiving each piece of identification information included in the registration rejection message.

Furthermore, if the UE does not receive the registration rejection message even after a predetermined period has elapsed after transmitting the registration request message, the UE may recognize that the UE's request has been rejected.

Based on the transmission and reception of the registration refusal message, each device completes the procedure (B) in this procedure.

Note that the procedure in (B) of FIG. 6 may be started when the procedure in (A) of FIG. 6 is canceled.

Each device completes the registration procedure based on the completion of the procedure in (A) or (B) of FIG. Note that each device may transition to a state in which the UE is registered with the network (RM_REGISTERED state) based on the completion of the procedure in (A) of FIG. Furthermore, each device may maintain a state in which the UE is not registered in the network (RM_DEREGISTERED state) or a state in which the UE is not registered in the network, based on the completion of the procedure in (B) in Figure 6. You may transition to .

Furthermore, each device may perform processing based on the information transmitted and received in the registration procedure, based on the completion of the registration procedure. For example, if information indicating that some of the UE's requests have been rejected is sent or received, the reason why the UE's requests were rejected may be recognized. Furthermore, each device may perform this procedure again based on the reason why the UE request was rejected, or may perform the registration procedure for core network_B or another cell.

Furthermore, the UE may store the identification information received with the registration acceptance message or the registration rejection message, or may recognize the network's decision, based on the completion of the registration procedure.

[3.2. UE settings update procedure]
Next, the UE configuration update procedure (Generic UE configuration update procedure) will be explained using FIG. 7. Hereinafter, the UE configuration update procedure will also be referred to as this procedure. This procedure is a procedure for the core network to update the configuration information of the UE. This procedure may be a procedure for mobility management that is executed on the initiative of the network for the UE registered in the network. Further, the UE configuration update procedure may be an MM procedure.

Additionally, devices in the core network, such as the AMF, may initiate this procedure based on network configuration updates and/or operator policy updates. Note that the trigger for this procedure may be the detection of UE mobility, the detection of a change in the state of the UE and/or the access network, and/or the core network, or the detection of a change in the state of the network slice. It may be. Further, the trigger for this procedure may be the receipt of a request from the DN and/or the DN's application server, a change in network settings, or a change in operator policy. . Additionally, the trigger for this procedure may be the expiration of a running timer. Note that the trigger for a device in the core network to start this procedure is not limited to these. In other words, this procedure may be performed at any time after the above-mentioned registration procedure and/or PDU session establishment procedure is completed. Furthermore, this procedure may be executed at any timing as long as each device has established a 5GMM context and/or each device is in 5GMM connection mode.

Additionally, during this procedure, each device sends and receives messages containing identification information for changing the configuration information of the UE and/or identification information for stopping or changing the functions that the UE is performing. Good too. Further, based on the completion of this procedure, each device may update its configuration information to the settings instructed by the network, or may start a behavior instructed by the network.

The UE may update its configuration information based on the control information transmitted and received through this procedure. Further, the UE may stop the function it is currently executing or may start a new function as the UE configuration information is updated. In other words, the device in the core network takes the initiative in this procedure, and furthermore, by sending the control message and control information of this procedure to the UE, the device in the core network uses these control information to generate configuration information of the UE that can be identified. , the UE may be updated. Furthermore, by updating the configuration information of the UE, the device in the core network may stop the function that the UE is executing, or may cause the UE to start a new function.

First, the AMF starts the UE configuration update procedure by transmitting a configuration update command message to the UE via the 5G AN (gNB) (S1000).

Further, when the configuration information of the UE is updated, the AMF may include at least one of the 12th to 14th pieces of identification information in a configuration update command message and transmit it.

Specifically, the network may indicate a local service identifier to the UE by transmitting the 12th identification information. Also, the network may indicate a list of one or more local service identifiers to the UE by transmitting the 12th identification information.

The network may also indicate to the UE whether to authenticate and/or authorize the local service by transmitting the thirteenth identification information.

The network may also indicate to the UE that the local service is unavailable by transmitting the fourteenth identification information.

The UE receives a configuration update command message and/or one or more of the twelfth to fourteenth pieces of identification information from the network. More specifically, the UE receives a configuration update command message and/or one or more of the twelfth to fourteenth identification information from the AMF.

The UE may recognize or store the received information based on the reception of at least one piece of information among the twelfth to fourteenth identification information.

Furthermore, when a plurality of pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

The AMF shall decide whether to include each identification information in the configuration update command message based on each received identification information, and/or subscriber information, and/or network capability information, and/or operator policy, and/or network capability information. The selection and determination may be made based on the state, the user's registration information, and/or the context held by the AMF.

The AMF may also collect each received identification information, and/or subscriber information, and/or network capability information, and/or operator policy, and/or network status, and/or user registration information, and/or A request to update the configuration information of the UE may be indicated by transmitting a configuration update command message based on the context held by the AMF.

The UE receives a configuration update command message from the AMF via the 5G AN (gNB) (S1000). The UE may update its configuration information based on the configuration update command message and/or the identification information included in the configuration update command message.

Specifically, the UE may recognize the local service identifier when receiving the twelfth identification information. The UE may also recognize the available local service identifier when receiving the twelfth identification information. The UE may also recognize the identifier of a local service available to the UE and/or the network when receiving the twelfth identification information.

Additionally, when the UE receives the twelfth identification information, the UE may store the local service identifier. Additionally, when the UE receives the twelfth identification information, it may store the identifier of the available local service. Additionally, when the UE receives the twelfth identification information, it may store an identifier of a local service available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, it may recognize a list made up of one or more local service identifiers. Additionally, when the UE receives the twelfth identification information, it may recognize a list comprised of identifiers of one or more available local services. The UE may also recognize, when receiving the twelfth identification information, a list comprised of identifiers of one or more local services available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, the UE may store a list composed of one or more local service identifiers. Further, when the UE receives the twelfth identification information, the UE may store a list consisting of identifiers of one or more available local services. The UE may also store a list comprised of identifiers of one or more local services available to the UE and/or the network when receiving the twelfth identification information.

Furthermore, when the UE receives the twelfth identification information, it may associate it with the first identification information and/or the second identification information. Further, when the UE receives the twelfth identification information, the UE may store it in association with the first identification information and/or the second identification information.

The UE may also recognize that the local service has been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize that the local service has not been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize whether the local service is authenticated and/or authorized if it receives the thirteenth identification information.

Additionally, if the UE receives the thirteenth identification information, it may recognize that the local service has been granted. The UE may also recognize that the local service is not authorized if it receives the thirteenth identification information. Additionally, the UE may recognize whether local service is authorized or not when receiving the thirteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may associate it with one or more of the first to fourth identification information. Furthermore, when the UE receives the thirteenth identification information, it may associate it with the twelfth identification information and/or the fourteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may store it in association with one or more of the first to fourth identification information. Further, when the UE receives the thirteenth identification information, the UE may store it in association with the twelfth identification information and/or the fourteenth identification information.

Additionally, if the UE receives the fourteenth identification information, it may recognize that the local service is not available. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available.

Furthermore, when the UE receives the fourteenth identification information, the UE may recognize that the local service is not available at the time. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available at the time.

The UE may also recognize that the local service authentication and/or authorization has been revoked if the UE receives the fourteenth identification information. Further, when the UE receives the fourteenth identification information, the UE may recognize that the authentication and/or authorization of the local service indicated by the thirteenth identification information has been revoked.

Additionally, if the UE receives the fourteenth identification information, the UE may recognize that the local service authorization has been revoked. Further, when the UE receives the fourteenth identification information, the UE may recognize that permission for the local service indicated by the thirteenth identification information has been revoked.

Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service corresponding to the service identifier is unavailable. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service indicated by the service identifier is unavailable. Here, the service identifier may be a service identifier indicated by the third identification information and/or the twelfth identification information.

Note that the above behavior of the UE may be performed after receiving the configuration update command message. Furthermore, the behavior of the UE may be performed after receiving one or more pieces of identification information among the twelfth to fourteenth pieces of identification information.

Furthermore, when the UE receives the configuration update command message, it may perform the behavior when receiving each piece of identification information included in the configuration update command message.

Furthermore, based on the identification information included in the configuration update command message, the UE sends a configuration update complete message to the AMF via the 5G AN (gNB) as a response message to the configuration update command message. You may do so (S1002).

If the UE transmits the configuration update completion command message, the AMF receives the configuration update completion message via the 5G AN (gNB) (S1002). Furthermore, each device completes this procedure based on sending and receiving the settings update command message and/or the settings update completion message.

Furthermore, each device may perform processing based on the information transmitted and received in this procedure, based on the completion of this procedure. For example, when updating information on configuration information is transmitted and received, each device may update the configuration information. Furthermore, if the UE transmits or receives information indicating that it is necessary to perform the registration procedure, the UE may start the registration procedure based on the completion of this procedure.

Additionally, the UE may store the identification information received with the configuration information command message or may recognize the network's decision based on the completion of this procedure. Further, the UE may execute each procedure based on the stored information based on the completion of this procedure.

In the above procedure, by sending and receiving configuration update command messages, devices in the core network can instruct the UE to update the configuration information that the UE has already applied, and can update the configuration information that the UE is currently applying. It is possible to instruct the suspension or change of functions.

[3.3. PDU session establishment procedure]
Next, the behavior of each device when the UE executes the PDU session establishment procedure will be described using FIG. 8. Hereinafter, the PDU session establishment procedure may be referred to as this procedure. Furthermore, the PDU session establishment procedure may be an SM procedure.

Note that this procedure may be executed after the registration procedure has been executed one or more times.

First, the UE sends a PDU session establishment request message to the SMF (S1200) (S1202) (S1204) to start the PDU session establishment procedure. Then, the SMF receives the PDU session establishment request message from the UE.

Specifically, the UE starts a PDU session establishment procedure by transmitting a NAS message including an N1 SM container including a PDU session establishment request message to the AMF via the access network (S1200). The NAS message is a message sent via the N1 interface, for example, and may be an uplink NAS transport (UL NAS TRANSPORT) message.

Here, the UE may include one or more of the first to fourth pieces of identification information in the PDU session establishment request message or NAS message and transmit it.

Specifically, the UE may indicate the DNN to the network by transmitting the first identification information. The UE may also indicate to the network the DNN associated with the local service by transmitting the first identification information. The UE may also indicate to the network the DNN associated with the third identification information by transmitting the first identification information.

The UE may also indicate to the network an S-NSSAI by transmitting the second identification information. The UE may also indicate to the network an S-NSSAI associated with a local service by transmitting the second identification information. The UE may also indicate to the network an S-NSSAI associated with a third identification information by transmitting the second identification information.

The UE may also indicate to the network the identifier of the local service to be used by transmitting the third identification information. Here, the third identification information may be the same as the twelfth identification information. Here, the third identification information may be an identifier of one or more local services indicated by the twelfth identification information. Here, the third identification information may be associated with the first identification information and/or the second identification information.

The UE may also indicate to the network that it supports local services by transmitting the fourth identification information. The UE may also indicate to the network whether it supports local services by transmitting the fourth identification information.

Note that by transmitting these identification information, the UE may indicate that the UE supports each function, or may indicate the UE's request. Furthermore, when a plurality of pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

Here, the UE may indicate the content of each piece of identification information to the network by transmitting a PDU session establishment request message or a NAS message.

Furthermore, the access network may be a 3GPP access or a non-3GPP access and may include a base station device. That is, the UE transmits a NAS message to the AMF via the base station device.

Note that the UE determines whether to include one or more of the first to fourth pieces of identification information in the PDU session establishment request message based on subscriber information, network status, and/or user registration information. , and/or the context held by the UE.

Note that the UE may include identification information other than the first to fourth identification information in the PDU session establishment request message and transmit it.

Next, upon receiving the NAS message, the AMF can recognize what the UE is requesting and/or the contents of the information (message, container, information) included in the NAS message.

Next, the AMF selects the SMF as the destination for at least part of the information (message, container, information) included in the NAS message received from the UE (S1202). In addition, AMF is responsible for the information contained in the NAS message (message, container, information), and/or subscriber information, and/or network capability information, and/or UE policy, and/or operator policy, and/or A transfer destination SMF may be selected based on the network state, user registration information, and/or context held by the AMF.

Next, the AMF transmits at least part of the information (message, container, information) included in the NAS message received from the UE to the selected SMF, for example, via the N11 interface (S1204).

Next, when the SMF receives information etc. (message, container, information) sent from the AMF, it can recognize what the UE is requesting and/or the contents of the information etc. (message, container, information) received from the AMF.

Specifically, the network may recognize the DNN when receiving the first identification information. The network may also recognize the DNN requested by the UE when receiving the first identification information. The network may also recognize the DNN associated with the local service requested by the UE when receiving the first identification information. The network may also recognize the DNN associated with the third identification information when receiving the first identification information.

Specifically, the network may recognize an S-NSSAI when it receives the second identification information. The network may also recognize an S-NSSAI requested by the UE when it receives the second identification information. The network may also recognize an S-NSSAI related to a local service requested by the UE when it receives the second identification information. The network may also recognize an S-NSSAI related to a third identification information when it receives the second identification information.

Additionally, the network may recognize the identifier of the local service used by the UE by receiving the third identification information. Here, the third identification information may be associated with the first identification information and/or the second identification information.

The network may also recognize that the UE supports local services by receiving the fourth identification information. The network may also recognize whether the UE supports local services by receiving the fourth identification information.

Note that the above network behavior may be performed after receiving the PDU session establishment request message. Furthermore, the network behavior described above may be performed after receiving one or more pieces of identification information among the first to fourth pieces of identification information.

Furthermore, when the network receives a PDU session establishment request message, it may perform the behavior when receiving each piece of identification information included in the PDU session establishment request message.

The network may also forward each received identification information to other NFs.

Here, the SMF may perform a second condition determination. Further, the second condition determination may be for determining whether the network accepts the request from the UE. If the SMF determines that the second condition is true, it may start the procedure in (A) of Figure 8, and if it determines that the second condition is false, it may start the procedure in (B) of Figure 8. You may begin.

The second condition determination may be performed by an NF other than the SMF. The NF may be, for example, an NSSF, an NWDAF, a PCF, or an NRF. When an NF other than the SMF performs the second condition determination, the SMF may provide the NF with information necessary to perform the second condition determination, specifically, at least a portion of the information received from the UE (S1206). Then, when the NF determines whether the second condition determination is true or false based on the information received from the SMF, it may convey information including the result of the second condition determination (i.e., true or false) to the SMF. The SMF may determine the identification information and/or control message to be transmitted to the UE based on the result of the second condition determination received from the NF.

Note that the second condition determination is based on information received from the AMF (message, container, information), and/or subscription information, and/or network capability information, and/or UE policy, and/or Alternatively, it may be executed based on operator policy, and/or network status, and/or user registration information, and/or context held by the SMF.

For example, if the network permits the UE's request, the second condition determination may be determined to be true; if the network does not permit the UE's request, the second condition determination may be determined to be false. Furthermore, if the network to which the UE is connected and/or the equipment within the network supports the function requested by the UE, the second condition determination may be determined to be true, and the device supports the function requested by the UE. If not, the second condition determination may be determined to be false. Furthermore, if the transmitted and received identification information is permitted, the second condition determination may be determined to be true, and if the transmitted and received identification information is not permitted, the second condition determination may be determined to be false.

Note that the conditions for determining the truth of the second condition determination are not limited to the conditions described above.

Next, each step of the procedure in FIG. 8(A) will be explained.

The SMF may select a UPF for the PDU session to be established and send an N4 session establishment request message to the selected UPF, for example, via the N4 interface (S1208). The N4 session establishment request message may include at least a portion of the PCC rule received from the PCF.

The SMF may decide whether or not to approve the C2 communication during this procedure based on information received from the AMF (messages, containers, information), and/or information such as PCC rules received from the PCF, and/or subscriber information, and/or network capability information, and/or UE policies, and/or operator policies, and/or network status, and/or user registration information, and/or context held by the SMF, etc.

Here, the SMF may select one or more UPFs based on information received from the AMF (message, container, information), and/or information such as PCC rules received from the PCF, and/or subscriber information, and/or network capability information, and/or UE policy, and/or operator policy, and/or network status, and/or user registration information, and/or context held by the SMF, etc. Furthermore, if multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF. Here, it is assumed that a UPF is selected.

Next, upon receiving the N4 session establishment request message (S1208), the UPF can recognize the content of the information received from the SMF. Further, based on the reception of the N4 session establishment request message, the UPF may transmit an N4 session establishment response message to the SMF, for example, via the N4 interface (S1210).

Next, when the SMF receives the N4 session establishment response message as a response message to the N4 session establishment request message, it can recognize the content of the information received from the UPF.

Next, the SMF sends a PDU session establishment accept message to the UE based on the reception of the PDU session establishment request message, the selection of the UPF, and/or the reception of the N4 session establishment response message, etc. Then, the UE receives a PDU session establishment acceptance message from the SMF (S1218) (S1220) (S1222).

Specifically, the SMF sends the N1 SM container and Sends/or N2 SM information and/or PDU session ID to AMF (S1212). Here, the N1 SM container may include a PDU session establishment acceptance message. Furthermore, the PDU session ID may be included in the PDU session establishment acceptance message.

Next, the AMF that has received the N1 SM container and/or N2 SM information and/or PDU session ID transmits a NAS message to the UE via the first base station device included in the access network (S1214 )(S1216). Here, the NAS message is sent, for example, via the N1 interface. Additionally, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

Specifically, when the AMF transmits an N2 PDU session request message to the base station device included in the access network (S1214), the base station device that received the N2 PDU session request message requests the UE, Send a NAS message (S1216). Here, the N2 PDU session request message may include a NAS message and/or N2 SM information. The NAS message may also include a PDU session ID and/or an N1 SM container.

Additionally, the PDU session establishment acceptance message may be a response message to the PDU session establishment request. Additionally, the PDU Session Establishment Accept message may indicate that the establishment of the PDU session has been accepted.

Here, the SMF and/or AMF include a PDU session establishment acceptance message, and/or an N1 SM container, and/or a PDU session ID, and/or a NAS message, and/or an N2 SM information, and/or an N2 PDU session request. Sending the message may indicate that at least a portion of the UE's request via the PDU Session Establishment Request message has been accepted.

Here, the SMF and/or AMF include the tenth to fourteenth points in the PDU session establishment acceptance message, and/or the N1 SM container, and/or the NAS message, and/or the N2 SM information, and/or the N2 PDU session request message. One or more of the identification information may be included in the transmission.

Specifically, the network may indicate to the UE the DNN associated with the local service by transmitting the tenth identification information.

The network may also indicate to the UE the S-NSSAI associated with the local service by transmitting the eleventh identification information.

The network may also indicate the local service identifier to the UE by transmitting the twelfth identification information. The network may also indicate to the UE a list comprised of identifiers of one or more local services by transmitting the twelfth identification information.

The network may also indicate to the UE whether to authenticate and/or authorize the local service by transmitting the thirteenth identification information.

The network may also indicate to the UE that the local service is unavailable by transmitting the fourteenth identification information.

Note that the SMF may indicate that the network supports each function by transmitting these identification information and/or a PDU session establishment acceptance message, or may indicate that the UE's request has been accepted. It may indicate that the request from the UE is not permitted, or it may indicate a combination of these information. Furthermore, when a plurality of pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

Here, the network may indicate the content of the identification information to the UE by transmitting a PDU session establishment acceptance message.

In addition, the network may also include identification information other than the 10th to 14th identification information in the PDU session establishment acceptance message.

Additionally, the SMF and/or AMF determines which identification information to include in the PDU session establishment acceptance message, and/or the N1 SM container, and/or the NAS message, and/or the N2 SM information, and/or the N2 PDU session request message. each received identification information and/or subscriber information and/or network capability information and/or UE policy and/or operator policy and/or network status and/or user registration information; And/or the decision may be made based on the context held by the SMF and/or the AMF.

Next, when the UE receives the NAS message, for example via the N1 interface (S1216), the UE confirms that the UE's request via the PDU session establishment request message has been accepted and/or the information included in the NAS message (message, Containers, information) can be recognized.

Specifically, the UE may recognize the DNN associated with the local service when receiving the tenth identification information. The UE may also store the DNN associated with the local service when receiving the tenth identification information.

Specifically, the UE may recognize the S-NSSAI associated with the local service when receiving the eleventh identification information. The UE may also store the S-NSSAI associated with the local service when receiving the eleventh identification information.

The UE may also recognize the local service identifier when receiving the twelfth identification information. The UE may also recognize the available local service identifier when receiving the twelfth identification information. The UE may also recognize the identifier of a local service available to the UE and/or the network when receiving the twelfth identification information.

Additionally, when the UE receives the twelfth identification information, the UE may store the local service identifier. Additionally, when the UE receives the twelfth identification information, it may store the identifier of the available local service. Additionally, when the UE receives the twelfth identification information, it may store an identifier of a local service available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, it may recognize a list made up of one or more local service identifiers. Additionally, when the UE receives the twelfth identification information, it may recognize a list comprised of identifiers of one or more available local services. The UE may also recognize, when receiving the twelfth identification information, a list comprised of identifiers of one or more local services available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, the UE may store a list composed of one or more local service identifiers. Further, when the UE receives the twelfth identification information, the UE may store a list consisting of identifiers of one or more available local services. The UE may also store a list comprised of identifiers of one or more local services available to the UE and/or the network when receiving the twelfth identification information.

Furthermore, when the UE receives the twelfth identification information, it may associate it with the first identification information and/or the second identification information. Further, when the UE receives the twelfth identification information, the UE may store it in association with the first identification information and/or the second identification information.

The UE may also recognize that the local service has been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize that the local service has not been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize whether the local service is authenticated and/or authorized if it receives the thirteenth identification information.

Additionally, if the UE receives the thirteenth identification information, it may recognize that the local service has been granted. The UE may also recognize that the local service is not authorized if it receives the thirteenth identification information. Additionally, the UE may recognize whether local service is authorized or not when receiving the thirteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may associate it with one or more of the first to fourth identification information. Furthermore, when the UE receives the thirteenth identification information, it may associate it with the twelfth identification information and/or the fourteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may store it in association with one or more of the first to fourth identification information. Further, when the UE receives the thirteenth identification information, the UE may store it in association with the twelfth identification information and/or the fourteenth identification information.

Additionally, if the UE receives the fourteenth identification information, it may recognize that the local service is not available. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available.

Furthermore, when the UE receives the fourteenth identification information, the UE may recognize that the local service is not available at the time. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available at the time.

The UE may also recognize that the local service authentication and/or authorization has been revoked if the UE receives the fourteenth identification information. Further, when the UE receives the fourteenth identification information, the UE may recognize that the authentication and/or authorization of the local service indicated by the thirteenth identification information has been revoked.

Additionally, if the UE receives the fourteenth identification information, the UE may recognize that the local service authorization has been revoked. Further, when the UE receives the fourteenth identification information, the UE may recognize that permission for the local service indicated by the thirteenth identification information has been revoked.

Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service corresponding to the service identifier is unavailable. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service indicated by the service identifier is unavailable. Here, the service identifier may be a service identifier indicated by the third identification information and/or the twelfth identification information.

Note that the above behavior of the UE may be performed after receiving the PDU session establishment acceptance message. Furthermore, the behavior of the UE may be performed after receiving one or more pieces of identification information among the twelfth to fourteenth pieces of identification information.

In addition, when the UE receives a PDU session establishment acceptance message and/or a NAS message, the UE may perform the behavior when receiving each piece of identification information contained in the PDU session establishment acceptance message and/or the NAS message.

Next, we explain each step of the procedure in Figure 8 (B).

First, based on the reception of the PDU session establishment request message, the SMF transmits the N1 SM container and/or the PDU session ID to the AMF, for example, via the N11 interface (S1218). Here, the N1 SM container may include a PDU session establishment refusal message. Furthermore, the PDU session ID may be included in the PDU session establishment rejection message.

Next, the AMF that has received the N1 SM container and/or the PDU session ID transmits a NAS message to the UE via the base station device included in the access network (S1220) (S1222). Here, the NAS message is sent, for example, via the N1 interface. Additionally, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. The NAS message may also include a PDU session ID and/or an N1 SM container.

Additionally, the PDU session establishment rejection message may be a response message to the PDU session establishment request. Additionally, the PDU session establishment refusal message may indicate that establishment of a PDU session has been rejected.

Here, the SMF and/or AMF requests the UE by means of a PDU session establishment request message by sending a PDU session establishment refusal message, and/or an N1 SM container, and/or a PDU session ID, and/or a NAS message. may indicate that the request was rejected.

Note that by transmitting a PDU session establishment refusal message, the SMF may indicate that the UE's request has been rejected, or may indicate that the request from the UE is not permitted, or may indicate that the request from the UE is not permitted. Combined information may also be shown.

Here, the SMF and/or AMF include the tenth to fourteenth messages in the PDU session establishment refusal message, and/or the N1 SM container, and/or the NAS message, and/or the N2 SM information, and/or the N2 PDU session request message. One or more of the identification information may be included in the transmission.

Specifically, the network may indicate to the UE the DNN associated with the local service by transmitting the tenth identification information.

The network may also indicate to the UE the S-NSSAI associated with the local service by transmitting the eleventh identification information.

The network may also indicate the local service identifier to the UE by transmitting the twelfth identification information. The network may also indicate to the UE a list comprised of identifiers of one or more local services by transmitting the twelfth identification information.

The network may also indicate to the UE whether to authenticate and/or authorize the local service by transmitting the thirteenth identification information.

The network may also indicate to the UE that the local service is unavailable by transmitting the fourteenth identification information.

Additionally, the SMF and/or AMF determines which identification information to include in the PDU session establishment refusal message, and/or N1 SM container, and/or NAS message, and/or N2 SM information, and/or N2 PDU session request message. each received identification information and/or subscriber information and/or network capability information and/or UE policy and/or operator policy and/or network status and/or user registration information; And/or the decision may be made based on the context held by the SMF and/or the AMF.

Additionally, the SMF and/or AMF may include a PDU session establishment refusal message, and/or an N1 SM container, and/or a NAS message, and/or an N2 SM information, and/or an N2 PDU session request message indicating that the UE's request is rejected. The information indicating that the UE request has been rejected may be included in the transmission, or the reason for the rejection of the UE request may be indicated by transmitting information indicating that the UE request has been rejected. Further, the UE may recognize the reason why the UE's request was rejected by receiving information indicating that the UE's request was rejected. Note that the reason for rejection may be information indicating that the content indicated by the identification information received by the SMF and/or AMF is not permitted and/or cannot be used.

Specifically, for example, if the network does not support a local service requested by the UE, the SMF and/or AMF may send a rejection cause value to the UE indicating that the identifier of the local service received from the UE is unavailable, and/or that there are insufficient resources for the local service received from the UE, and/or that the local service received from the UE is not supported, and/or that the local service received from the UE is not found or unknown. The rejection cause value may be a 5GSM cause value.

Next, when the UE receives the NAS message (S1222), for example via the N1 interface, the UE informs the user that the UE's request via the PDU session establishment request message has been rejected and/or the information contained in the NAS message (message, etc.). Containers, information) can be recognized.

Specifically, the UE may recognize the DNN associated with the local service when receiving the tenth identification information. The UE may also store the DNN associated with the local service when receiving the tenth identification information.

Specifically, the UE may recognize the S-NSSAI associated with the local service when receiving the eleventh identification information. The UE may also store the S-NSSAI associated with the local service when receiving the eleventh identification information.

The UE may also recognize the local service identifier when receiving the twelfth identification information. The UE may also recognize the available local service identifier when receiving the twelfth identification information. The UE may also recognize the identifier of a local service available to the UE and/or the network when receiving the twelfth identification information.

Additionally, when the UE receives the twelfth identification information, the UE may store the local service identifier. Additionally, when the UE receives the twelfth identification information, it may store the identifier of the available local service. Additionally, when the UE receives the twelfth identification information, the UE may store an identifier of a local service available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, it may recognize a list made up of one or more local service identifiers. Additionally, when the UE receives the twelfth identification information, it may recognize a list comprised of identifiers of one or more available local services. The UE may also recognize, when receiving the twelfth identification information, a list comprised of identifiers of one or more local services available to the UE and/or the network.

Further, when the UE receives the twelfth identification information, the UE may store a list consisting of one or more local service identifiers. Further, when the UE receives the twelfth identification information, the UE may store a list consisting of one or more local service identifiers available to the UE and/or the network. Further, when the UE receives the twelfth identification information, the UE may store a list consisting of one or more local service identifiers available to the UE and/or the network.

Furthermore, when the UE receives the twelfth identification information, it may associate it with the first identification information and/or the second identification information. Further, when the UE receives the twelfth identification information, the UE may store it in association with the first identification information and/or the second identification information.

The UE may also recognize that the local service has been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize that the local service has not been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize whether the local service is authenticated and/or authorized if it receives the thirteenth identification information.

Additionally, if the UE receives the thirteenth identification information, it may recognize that the local service has been granted. The UE may also recognize that the local service is not authorized if it receives the thirteenth identification information. Additionally, the UE may recognize whether local service is authorized or not when receiving the thirteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may associate it with one or more of the first to fourth identification information. Furthermore, when the UE receives the thirteenth identification information, it may associate it with the twelfth identification information and/or the fourteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may store it in association with one or more of the first to fourth identification information. Further, when the UE receives the thirteenth identification information, the UE may store it in association with the twelfth identification information and/or the fourteenth identification information.

Furthermore, when the UE receives the 14th identification information, the UE may recognize that the local service cannot be used.Furthermore, when the UE receives the 14th identification information, the UE may recognize that the local service requested by the UE cannot be used.

Furthermore, when the UE receives the fourteenth identification information, the UE may recognize that the local service is not available at the time. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available at the time.

The UE may also recognize that the local service authentication and/or authorization has been revoked if the UE receives the fourteenth identification information. Further, when the UE receives the fourteenth identification information, the UE may recognize that the authentication and/or authorization of the local service indicated by the thirteenth identification information has been revoked.

Additionally, if the UE receives the fourteenth identification information, the UE may recognize that the local service authorization has been revoked. Further, when the UE receives the fourteenth identification information, the UE may recognize that permission for the local service indicated by the thirteenth identification information has been revoked.

Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service corresponding to the service identifier is unavailable. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service indicated by the service identifier is unavailable. Here, the service identifier may be a service identifier indicated by the third identification information and/or the twelfth identification information.

Note that the above behavior of the UE may be performed after receiving the PDU session establishment rejection message. Furthermore, the behavior of the UE may be performed after receiving one or more pieces of identification information among the twelfth to fourteenth pieces of identification information.

Furthermore, when the UE receives a PDU session establishment refusal message and/or a NAS message, the UE may implement the behavior when receiving each identification information included in the PDU session establishment refusal message and/or the NAS message. .

Furthermore, when the UE receives one or more of the identification information items 10 to 14, the UE may recognize the content indicated by the received identification information.Furthermore, when the UE receives one or more of the identification information items 10 to 14, the UE may recognize that the content indicated by the identification information included in the NAS message or the PDU session establishment acceptance message or the PDU session establishment rejection message is permitted.

Note that the above behavior of the UE may be performed after receiving the PDU session acceptance message or the PDU session rejection message. Further, the behavior of the UE may be performed after receiving one or more pieces of identification information among the tenth to fourteenth pieces of identification information.

The UE may recognize the content of the identification information by receiving the NAS message, the PDU session establishment acceptance message, or the PDU session establishment rejection message.

Each device may complete this procedure based on sending and receiving the PDU session establishment acceptance message. Furthermore, each device may establish a PDU session based on the completion of this procedure. At this time, each device may transition to a state where it can communicate with the DN using the established PDU session.

Each device may complete this procedure based on the transmission and reception of the PDU session establishment rejection message. At this time, since each device cannot establish a PDU session, it cannot communicate with the DN if there is no already established PDU session.

In addition, each process that the UE executes based on the reception of each identification information shown above may be executed during this procedure, after the completion of this procedure, or after the completion of this procedure, based on the completion of this procedure. good.

[4. Embodiment]
Next, each embodiment will be described.

[4.1. First embodiment]
First, a first embodiment will be described. In this chapter, the first embodiment may be referred to as the present embodiment.

In this embodiment, the network may be a hosting network or a home network. Here, the hosting network may be an SNPN or a PNI-NPN. Also, the home network may be an SNPN or a PNI-NPN.

Additionally, in this embodiment, a registration procedure, a UE configuration update procedure, and/or a PDU session establishment procedure may be implemented.

This embodiment may be the behavior when a common DNN and S-NSSAI are used for different local services. For example, when local service #1 and local service #2 exist, DNN #1 and S-NSSAI #1 are used for local service #1, and DNN #1 and S-NSSAI #1 are also used for local service #2.

Specifically, this embodiment may be a behavior when a common DNN and S-NSSAI are used for different local services, and further, identifiers of different local services are used. . For example, if local service #1 and local service #2 exist, use DNN#1, S-NSSAI #1, and local service identifier #1 for local service #1. , use DNN#1, S-NSSAI#1, and local service identifier #2 for local service #2. Here, the local service identifier may be the same as the third identification information and/or the twelfth identification information.

In this embodiment, the first control message may be a registration acceptance message or a settings update command message.

Furthermore, in this embodiment, the second control message may be a PDU session establishment request message.

Each step of this procedure will be explained below.

First, the network transmits a first control message to the UE. Here, the network may transmit the first control message including one or more of the identification information items 12 to 14.

Here, the network includes one or more pieces of identification information among the 12th to 14th pieces of identification information in the first control message and transmits it, thereby transmitting the content indicated by the identification information included in the first control message. May be indicated to the UE.

Specifically, the network may indicate the local service identifier to the UE by transmitting the twelfth identification information. The network may also indicate to the UE a list comprised of identifiers of one or more local services by transmitting the twelfth identification information.

The network may also indicate to the UE whether to authenticate and/or authorize the local service by transmitting the thirteenth identification information.

The network may also indicate to the UE that the local service is unavailable by transmitting the fourteenth identification information.

Furthermore, the network may indicate to the UE the content of each piece of identification information included in the first control message by transmitting the first control message. The network may also indicate to the UE the content of each identification information by transmitting each identification information.

Note that the network determines whether to include one or more of the 12th to 14th identification information in the first control message based on the state of the UE and/or information received from the local service provider; Selection and determination may be made based on/or information received from UDM and/or information received from AUSF.

The network also sends the first control message and /Or it may be determined whether to transmit each piece of identification information. The network may also send the first control message and/or the respective identification information based on information received from the local service provider and/or UDM. The network may also transmit the first control message and/or the respective identification information based on information received from the AUSF indicating that the local service is to be terminated.

Next, the UE receives the first control message. Further, the UE may receive a first control message including one or more of the twelfth to fourteenth pieces of identification information from the network.

Furthermore, based on the reception of the first control message, the UE may store the identification information received along with the first control message, or may recognize the network's decision. Furthermore, based on reception of the first control message, the UE may recognize the content of the identification information received together with the first control message.

Specifically, the UE may recognize the local service identifier when receiving the twelfth identification information. The UE may also recognize the available local service identifier when receiving the twelfth identification information. The UE may also recognize the identifier of a local service available to the UE and/or the network when receiving the twelfth identification information.

Further, the UE may store an identifier of a local service when it receives the twelfth identification information. Further, the UE may store an identifier of an available local service when it receives the twelfth identification information. Further, the UE may store an identifier of a local service available to the UE and/or the network when it receives the twelfth identification information.

Additionally, when the UE receives the twelfth identification information, it may recognize a list made up of one or more local service identifiers. Additionally, when the UE receives the twelfth identification information, it may recognize a list comprised of identifiers of one or more available local services. The UE may also recognize, when receiving the twelfth identification information, a list comprised of identifiers of one or more local services available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, the UE may store a list composed of one or more local service identifiers. Further, when the UE receives the twelfth identification information, the UE may store a list consisting of identifiers of one or more available local services. The UE may also store a list comprised of identifiers of one or more local services available to the UE and/or the network when receiving the twelfth identification information.

Furthermore, when the UE receives the twelfth identification information, it may associate it with the first identification information and/or the second identification information. Further, when the UE receives the twelfth identification information, the UE may store it in association with the first identification information and/or the second identification information.

The UE may also recognize that the local service has been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize that the local service has not been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize whether the local service is authenticated and/or authorized if it receives the thirteenth identification information.

Additionally, if the UE receives the thirteenth identification information, it may recognize that the local service has been granted. The UE may also recognize that the local service is not authorized if it receives the thirteenth identification information. Additionally, the UE may recognize whether local service is authorized or not when receiving the thirteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may associate it with one or more of the first to fourth identification information. Furthermore, when the UE receives the thirteenth identification information, it may associate it with the twelfth identification information and/or the fourteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may store it in association with one or more of the first to fourth identification information. Further, when the UE receives the thirteenth identification information, the UE may store it in association with the twelfth identification information and/or the fourteenth identification information.

Additionally, if the UE receives the fourteenth identification information, it may recognize that the local service is not available. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available.

Furthermore, when the UE receives the fourteenth identification information, the UE may recognize that the local service is not available at the time. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available at the time.

The UE may also recognize that the local service authentication and/or authorization has been revoked if the UE receives the fourteenth identification information. Further, when the UE receives the fourteenth identification information, the UE may recognize that the authentication and/or authorization of the local service indicated by the thirteenth identification information has been revoked.

Additionally, if the UE receives the fourteenth identification information, the UE may recognize that the local service authorization has been revoked. Further, when the UE receives the fourteenth identification information, the UE may recognize that permission for the local service indicated by the thirteenth identification information has been revoked.

Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service corresponding to the service identifier is unavailable. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service indicated by the service identifier is unavailable. Here, the service identifier may be a service identifier indicated by the third identification information and/or the twelfth identification information.

Note that the above behavior of the UE may be performed after receiving the first control message. Furthermore, the behavior of the UE may be performed after receiving one or more pieces of identification information among the twelfth to fourteenth pieces of identification information.

Furthermore, when the UE receives the first control message, the UE may perform the behavior when receiving each piece of identification information included in the first control message.

Next, the UE sends a second control message to the network. Here, the UE may transmit the second control message including one or more of the first to fourth pieces of identification information.

Here, the UE transmits the second control message by including one or more of the first to fourth pieces of identification information in the second control message, thereby transmitting the content indicated by the identification information included in the second control message. It may also be shown on the network.

Specifically, the UE may indicate the DNN to the network by transmitting the first identification information. The UE may also indicate to the network the DNN associated with the local service by transmitting the first identification information. The UE may also indicate to the network the DNN associated with the third identification information by transmitting the first identification information.

The UE may also indicate the S-NSSAI to the network by transmitting the second identification information. The UE may also indicate to the network the S-NSSAI associated with the local service by transmitting the second identification information. The UE may also indicate to the network the S-NSSAI associated with the third identification information by transmitting the second identification information.

The UE may also indicate to the network the identifier of the local service to be used by transmitting the third identification information. Here, the third identification information may be the same as the twelfth identification information. Here, the third identification information may be an identifier of one or more local services indicated by the twelfth identification information. Here, the third identification information may be associated with the first identification information and/or the second identification information.

The UE may also indicate to the network that it supports local services by transmitting the fourth identification information. The UE may also indicate to the network whether it supports local services by transmitting the fourth identification information.

Furthermore, the UE may indicate to the network the content of each piece of identification information included in the second control message by transmitting the second control message. Furthermore, the UE may indicate the content of each identification information to the network by transmitting each identification information.

The UE may select and determine whether to include one or more of the first to fourth pieces of identification information in the second control message based on the state of the UE and/or each piece of received identification information, etc.

Next, the network receives a second control message. Further, the network may receive a second control message including one or more of the first to fourth pieces of identification information from the UE.

Further, based on the reception of the second control message, the network may store the identification information received with the second control message or may recognize the UE's decision. Additionally, the network may recognize the content of the identification information received along with the second control message based on the reception of the second control message.

Specifically, the network may recognize the DNN when receiving the first identification information. The network may also recognize the DNN requested by the UE when receiving the first identification information. The network may also recognize the DNN associated with the local service requested by the UE when receiving the first identification information. The network may also recognize the DNN associated with the third identification information when receiving the first identification information.

Specifically, the network may recognize the S-NSSAI when receiving the second identification information. Additionally, the network may recognize the S-NSSAI requested by the UE when receiving the second identification information. The network may also recognize the S-NSSAI associated with the local service requested by the UE when receiving the second identification information. The network may also recognize the S-NSSAI associated with the third identification information when receiving the second identification information.

Additionally, the network may recognize the identifier of the local service used by the UE by receiving the third identification information. Here, the third identification information may be associated with the first identification information and/or the second identification information.

The network may also recognize that the UE supports local services by receiving the fourth identification information. The network may also recognize whether the UE supports local services by receiving the fourth identification information.

The network behavior may be implemented after receiving the second control message. The network behavior may be implemented after receiving one or more of the first to fourth pieces of identification information.

Furthermore, when the network receives the second control message, it may perform the behavior when receiving each piece of identification information included in the second control message.

Additionally, the network may forward each received identification information to other NFs.

[4.2. Second embodiment]
First, a second embodiment will be described. In this chapter, the second embodiment may be referred to as the present embodiment.

In this embodiment, the network may be a hosting network or a home network. Here, the hosting network may be an SNPN or a PNI-NPN. Also, the home network may be an SNPN or a PNI-NPN.

Additionally, in this embodiment, a PDU session establishment procedure may be implemented.

Additionally, this embodiment may be implemented after the registration procedure and/or the UE configuration update procedure.

This embodiment may be the behavior when a common DNN and S-NSSAI are used for different local services. For example, if local service #1 and local service #2 exist, use DNN #1 and S-NSSAI #1 for local service #1, and use DNN #1 and S-NSSAI #1 for local service #2. However, use DNN#1 and S-NSSAI#1.

Specifically, this embodiment may be a behavior when a common DNN and S-NSSAI are used for different local services, and further, identifiers of different local services are used. . For example, if local service #1 and local service #2 exist, use DNN#1, S-NSSAI #1, and local service identifier #1 for local service #1. , use DNN#1, S-NSSAI#1, and local service identifier #2 for local service #2. Here, the local service identifier may be the same as the third identification information and/or the twelfth identification information.

In this embodiment, the first control message may be a PDU session establishment request message.

Furthermore, in this embodiment, the second control message may be a PDU session establishment acceptance message or a PDU session establishment rejection message.

Below, we will explain each step of this procedure.

First, the UE transmits a first control message to the network. Here, the UE may transmit the first control message including one or more of the first to fourth pieces of identification information.

Here, the UE transmits the first control message by including one or more of the first to fourth pieces of identification information in the first control message, thereby transmitting the content indicated by the identification information included in the first control message. It may also be shown on the network.

Specifically, the UE may indicate to the network a DNN by transmitting a first identification. The UE may also indicate to the network a DNN associated with a local service by transmitting the first identification. The UE may also indicate to the network a DNN associated with a third identification by transmitting the first identification.

The UE may also indicate the S-NSSAI to the network by transmitting the second identification information. The UE may also indicate to the network the S-NSSAI associated with the local service by transmitting the second identification information. The UE may also indicate to the network the S-NSSAI associated with the third identification information by transmitting the second identification information.

The UE may also indicate to the network an identifier of a local service to be used by transmitting a third identification. Here, the third identification may be the same as the twelfth identification. Here, the third identification may be an identifier of one or more local services indicated by the twelfth identification. Here, the third identification may be associated with the first identification and/or the second identification.

The UE may also indicate to the network that it supports localized services by transmitting the fourth identification information. The UE may also indicate to the network whether it supports localized services or not by transmitting the fourth identification information.

Furthermore, the UE may indicate to the network the content of each piece of identification information included in the first control message by transmitting the first control message. Furthermore, the UE may indicate the content of each identification information to the network by transmitting each identification information.

Note that the UE selects whether to include one or more identification information among the first to fourth identification information in the first control message based on the state of the UE and/or each received identification information. , may be determined.

Next, the network receives the first control message. Further, the network may receive from the UE a first control message including one or more of the first to fourth pieces of identification information.

Further, based on the reception of the first control message, the network may store the identification information received with the first control message or may recognize the UE's decision. Additionally, the network may recognize the content of the identification information received along with the first control message based on the reception of the first control message.

Specifically, the network may recognize the DNN when receiving the first identification information. The network may also recognize the DNN requested by the UE when receiving the first identification information. The network may also recognize the DNN associated with the local service requested by the UE when receiving the first identification information. The network may also recognize the DNN associated with the third identification information when receiving the first identification information.

Specifically, the network may recognize the S-NSSAI when receiving the second identification information. Additionally, the network may recognize the S-NSSAI requested by the UE when receiving the second identification information. The network may also recognize the S-NSSAI associated with the local service requested by the UE when receiving the second identification information. The network may also recognize the S-NSSAI associated with the third identification information when receiving the second identification information.

Additionally, the network may recognize the identifier of the local service used by the UE by receiving the third identification information. Here, the third identification information may be associated with the first identification information and/or the second identification information.

The network may also recognize that the UE supports local services by receiving the fourth identification information. The network may also recognize whether the UE supports local services by receiving the fourth identification information.

Note that the network behavior described above may be implemented after receiving the first control message. Furthermore, the network behavior described above may be performed after receiving one or more pieces of identification information among the first to fourth pieces of identification information.

Furthermore, when the network receives the first control message, it may perform the behavior when receiving each piece of identification information included in the first control message.

Additionally, the network may forward each received identification information to other NFs.

Next, the network sends a second control message to the UE. Here, the network may transmit the second control message including one or more of the twelfth to fourteenth identification information.

Here, the network includes one or more pieces of identification information among the 12th to 14th pieces of identification information in the second control message and transmits it, thereby transmitting the content indicated by the identification information included in the second control message. May be indicated to the UE.

Specifically, the network may indicate a local service identifier to the UE by transmitting the 12th identification information. Also, the network may indicate a list of one or more local service identifiers to the UE by transmitting the 12th identification information.

The network may also indicate to the UE whether to authenticate and/or authorize the local service by transmitting the thirteenth identification information.

The network may also indicate to the UE that the local service is unavailable by transmitting the fourteenth identification information.

Additionally, the network may indicate to the UE the content of each piece of identification information included in the second control message by transmitting the second control message. The network may also indicate to the UE the content of each identification information by transmitting each identification information.

Note that the network determines whether to include one or more of the 12th to 14th identification information in the second control message based on the state of the UE and/or information received from the local service provider; Selection and determination may be made based on/or information received from UDM and/or information received from AUSF.

The network also sends a second control message and /Or it may be determined whether to transmit each piece of identification information. The network may also send the second control message and/or the respective identification information based on information received from the local service provider and/or UDM. The network may also send the second control message and/or the respective identification information based on the information received from the AUSF indicating that the local service is to be terminated.

Next, the UE receives the second control message. Further, the UE may receive a second control message including one or more of the twelfth to fourteenth identification information from the network.

Further, the UE may store the identification information received with the second control message and recognize the network's decision based on receiving the second control message. Also, the UE may recognize the content of the identification information received with the second control message based on receiving the second control message.

Specifically, the UE may recognize the local service identifier when receiving the twelfth identification information. The UE may also recognize the available local service identifier when receiving the twelfth identification information. The UE may also recognize the identifier of a local service available to the UE and/or the network when receiving the twelfth identification information.

Additionally, when the UE receives the twelfth identification information, the UE may store the local service identifier. Additionally, when the UE receives the twelfth identification information, it may store the identifier of the available local service. Additionally, when the UE receives the twelfth identification information, it may store an identifier of a local service available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, it may recognize a list made up of one or more local service identifiers. Additionally, when the UE receives the twelfth identification information, it may recognize a list comprised of identifiers of one or more available local services. The UE may also recognize, when receiving the twelfth identification information, a list comprised of identifiers of one or more local services available to the UE and/or the network.

Additionally, when the UE receives the twelfth identification information, the UE may store a list composed of one or more local service identifiers. Further, when the UE receives the twelfth identification information, the UE may store a list consisting of identifiers of one or more available local services. The UE may also store a list comprised of identifiers of one or more local services available to the UE and/or the network when receiving the twelfth identification information.

Furthermore, when the UE receives the twelfth identification information, it may associate it with the first identification information and/or the second identification information. Further, when the UE receives the twelfth identification information, the UE may store it in association with the first identification information and/or the second identification information.

The UE may also recognize that the local service has been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize that the local service has not been authenticated and/or authorized if it receives the thirteenth identification information. The UE may also recognize whether the local service is authenticated and/or authorized if it receives the thirteenth identification information.

Additionally, if the UE receives the thirteenth identification information, it may recognize that the local service has been granted. The UE may also recognize that the local service is not authorized if it receives the thirteenth identification information. Additionally, the UE may recognize whether local service is authorized or not when receiving the thirteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may associate it with one or more of the first to fourth identification information. Furthermore, when the UE receives the thirteenth identification information, it may associate it with the twelfth identification information and/or the fourteenth identification information.

Furthermore, when the UE receives the thirteenth identification information, it may store it in association with one or more of the first to fourth identification information. Further, when the UE receives the thirteenth identification information, the UE may store it in association with the twelfth identification information and/or the fourteenth identification information.

Additionally, if the UE receives the fourteenth identification information, it may recognize that the local service is not available. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available.

Furthermore, when the UE receives the fourteenth identification information, the UE may recognize that the local service is not available at the time. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service requested by the UE is not available at the time.

Additionally, if the UE receives the fourteenth identification information, it may recognize that the local service authentication and/or authorization has been revoked. Further, when the UE receives the fourteenth identification information, the UE may recognize that the authentication and/or authorization of the local service indicated by the thirteenth identification information has been revoked.

Additionally, if the UE receives the fourteenth identification information, it may recognize that the local service authorization has been revoked. Further, when the UE receives the fourteenth identification information, the UE may recognize that permission for the local service indicated by the thirteenth identification information has been revoked.

Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service corresponding to the service identifier is unavailable. Further, when the UE receives the fourteenth identification information, the UE may recognize that the local service indicated by the service identifier is unavailable. Here, the service identifier may be a service identifier indicated by the third identification information and/or the twelfth identification information.

Note that the above behavior of the UE may be performed after receiving the second control message. Furthermore, the behavior of the UE may be performed after receiving one or more pieces of identification information among the twelfth to fourteenth pieces of identification information.

Furthermore, when the UE receives the second control message, it may perform the behavior when receiving each piece of identification information included in the second control message.

[5. Variations]
A program that runs on a device related to one aspect of the present invention is a program that controls a central processing unit (CPU) or the like to make a computer function so as to realize the functions of the embodiment related to one aspect of the present invention. Also good. Programs or information handled by programs are temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, hard disk drive (HDD), or other storage system.

In addition, a program for realizing the functions of an embodiment relating to one aspect of the present invention may be recorded on a computer-readable recording medium. The program recorded on this recording medium may be read into a computer system and executed to realize the functions. The "computer system" here refers to a computer system built into a device, and includes hardware such as an operating system and peripheral devices. Furthermore, the "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other recording medium that can be read by a computer.

Additionally, each functional block or feature of the device used in the embodiments described above may be implemented or executed in an electrical circuit, such as an integrated circuit or multiple integrated circuits. An electrical circuit designed to perform the functions described herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor or a conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. Furthermore, if an integrated circuit technology that replaces the current integrated circuit emerges due to advances in semiconductor technology, one or more embodiments of the present invention can also use a new integrated circuit based on this technology.

Note that the present invention is not limited to the above-described embodiments. In the embodiment, one example of the device is described, but the present invention is not limited to this, and can be applied to stationary or non-movable electronic equipment installed indoors or outdoors, such as AV equipment, kitchen equipment, etc. It can be applied to terminal devices or communication devices such as cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment.

Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to these embodiments, and may include design changes within the scope of the gist of the present invention. Further, the present invention can be modified in various ways within the scope shown in the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included within the technical scope of the present invention. It will be done. Also included are configurations in which the elements described in each of the above embodiments are replaced with each other and have similar effects.
(Cross reference to related applications)
This application claims priority to the Japanese patent application filed on September 20, 2022: Japanese Patent Application No. 2022-148727. Included in this book.

1 Mobile communication system
10 UE_A
30 PGW-U
32 PGW-C
35 SGW
40MME
45 eNB
50HSS
60 PCRF
80 Access network_A(E-UTRAN)
90 Core network_A
120 Access network_B(5G AN)
122 gNB
130 UPF
132 SMF
140AMF
150UDM
160 PCF
190 Core network_B
235 UPF_A
239 UPF_C

Claims (1)

1. User Equipment (UE),
   The UE includes a transmitting/receiving unit and a control unit,
   When a common DNN and S-NSSAI are used for different local services,
   The transmitting/receiving unit receives a registration acceptance message or a settings update command message including the first identification information from the core network,
   the first identification information is a local service identifier;
   The control unit recognizes an available local service identifier based on the reception of the first identification information,
   The transmitting/receiving unit transmits a PDU session establishment request message including the first identification information to the core network.
   UE characterized by.

Images