WO2022059627A1 - User equipment (ue) - Google Patents

User equipment (ue) Download PDF

Info

Publication number
WO2022059627A1
WO2022059627A1 PCT/JP2021/033438 JP2021033438W WO2022059627A1 WO 2022059627 A1 WO2022059627 A1 WO 2022059627A1 JP 2021033438 W JP2021033438 W JP 2021033438W WO 2022059627 A1 WO2022059627 A1 WO 2022059627A1
Authority
WO
WIPO (PCT)
Prior art keywords
identification information
nssai
information
registration
ims service
Prior art date
Application number
PCT/JP2021/033438
Other languages
French (fr)
Japanese (ja)
Inventor
靖夫 菅原
雄大 河崎
陽子 久下
周一郎 千葉
晶貴 泉
真史 新本
Original Assignee
シャープ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by シャープ株式会社 filed Critical シャープ株式会社
Priority to JP2022550535A priority Critical patent/JPWO2022059627A1/ja
Publication of WO2022059627A1 publication Critical patent/WO2022059627A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • One aspect of the present invention relates to UE (User Equipment).
  • UE User Equipment
  • This application claims priority based on Japanese Patent Application No. 2020-157079 filed on September 18, 2020, the contents of which are incorporated herein by reference.
  • Non-Patent Documents 1 to 3 In 3GPP (3rd Generation Partnership Project), the system architecture of 5GS (5G System), which is a 5th generation (5G) mobile communication system, is being studied, and discussions are being held to support new procedures and new functions. (See Non-Patent Documents 1 to 3). In Release 15, which is the initial release of the 5G standard, the concept of network slices was introduced, and in Release 17, the expansion of network slice functions related to IMS (IP Multimedia Subsystem) is being considered (see Non-Patent Document 4).
  • 5G System 5th generation
  • IMS IP Multimedia Subsystem
  • 3GPP TS 23.501 V16.5.1 2020-08
  • 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects System Architecture for the 5G System; Stage 2 (Release 16) 3GPP TS 23.502 V16.5.1 (2020-08); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16) 3GPP TS 24.501 V16.5.1 (2020-08); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16) 3GPP TR 23.794 V17.0.0 (2019-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhanced IP Multimedia Subsystem (IMS) to 5GC integration (Release 17); Page
  • Non-Patent Document 4 communication for IMS (hereinafter, also referred to as IMS service) using SIP (Session Initiation Protocol) in consideration of the registration area (hereinafter, also referred to as registration area and RA). It is not clear how to select the S-NSSAI to be used for.
  • IMS service communication for IMS (hereinafter, also referred to as IMS service) using SIP (Session Initiation Protocol) in consideration of the registration area (hereinafter, also referred to as registration area and RA).
  • SIP Session Initiation Protocol
  • the object of one aspect of the present invention has been made in view of the above circumstances, and in 5GS, in consideration of the registration area, S-NSSAI used for communication for IMS service is appropriately used. It is to provide a method for selection.
  • the UE of one aspect of the present invention includes a transmission / reception unit and a control unit, and the transmission / reception unit receives a registration acceptance message including Allowed NSSAI (Network Slice Selection Assistance Information) from AMF (Access and Mobility Management Function).
  • Allowed NSSAI Network Slice Selection Assistance Information
  • AMF Access and Mobility Management Function
  • the Allowed NSSAI is the first S-NSSAI (Single Network Slice) for the IMS service. Selection Assistance Information)
  • the URSP includes the first S-NSSAI and the first information
  • the first information includes a registration area where the first S-NSSAI can be used.
  • the first S-NSSAI included in the Allowed NSSAI is the current registration area based on the URSP.
  • the first S-NSSAI is selected for the IMS service.
  • the S-NSSAI used for communication for the IMS service can be appropriately selected in consideration of the registration area.
  • EPS / 5GS It is a figure explaining the outline of the mobile communication system (EPS / 5GS). It is a figure explaining the detailed structure of the mobile communication system (EPS / 5GS). It is a figure explaining the apparatus configuration of a UE. It is a figure explaining the structure of the access network apparatus (gNB) in 5GS. It is a figure explaining the structure of the core network apparatus (AMF / SMF / UPF / PCF, etc.) in 5GS. It is a figure explaining the registration procedure. It is a figure explaining the generic UE setting update procedure. It is a figure explaining the UE policy management procedure.
  • FIG. 1 is a diagram for explaining the outline of the mobile communication system 1 used in each embodiment
  • FIG. 2 is a diagram for explaining a detailed configuration of the mobile communication system 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
  • these devices / functions may be described by omitting symbols such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc. ..
  • Fig. 2 shows the devices / functions of UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5GAN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170, etc. An interface for connecting these devices / functions to each other is described.
  • these devices / functions are described as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5GAN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc. , Symbol may be omitted.
  • the EPS Evolved Packet System
  • 4G system is configured to include an access network_A and a core network_A, but may further include a UE and / or a PDN.
  • 5GS which is a 5G system, is configured to include a UE, an access network_B, and a core network_B, but may further include a DN.
  • the UE is a device that can connect to network services via 3GPP access (3GPP access network, also called 3GPPAN) and / or non-3GPP access (non-3GPP access network, also called non-3GPPAN).
  • 3GPP access network also called 3GPPAN
  • non-3GPP access network also called non-3GPPAN
  • 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 capable of connecting to EPS or 5GS.
  • the UE may be equipped with a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC).
  • UICC Universal Integrated Circuit Card
  • eUICC embedded UICC
  • the UE may be expressed as a user device or a terminal device.
  • the access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or wireless LAN access network.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • eNB evolved Node B
  • eNB45 may be described by omitting a symbol like eNB. If there are a plurality of eNBs, each eNB is connected to each other by, for example, an X2 interface.
  • one or more access points are arranged in the wireless LAN access network.
  • access network_B corresponds to 5G access network (5GAN).
  • 5GAN is composed of NG-RAN (NG Radio Access Network) and / or non-3GPP access network.
  • NG-RAN NG Radio Access Network
  • gNB NR Node B
  • gNB122 may be described by omitting a symbol such as eNB.
  • the gNB is a node that provides the NR (New Radio) user plane and the control plane to the UE, and is a node that connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface).
  • gNB is a base station device newly designed for 5GS and has a different function from the base station device (eNB) used in EPS, which is a 4G system.
  • eNB base station device
  • EPS base station device
  • each gNB is connected to each other by, for example, an Xn interface.
  • the non-3GPP access network may be an untrusted non-3GPP (untrusted non-3GPP) access network or a trusted non-3GPP (trusted non-3GPP) access network.
  • the unreliable non-3GPP access network may be a non-3GPP access network that does not perform security management in the access network, for example, a public wireless LAN.
  • the reliable non-3GPP access network may be an access network defined by 3GPP, and may include TNAP (trusted non-3GPP access point) and TNGF (trusted non-3GPP Gateway function).
  • E-UTRAN and NG-RAN may be referred to as 3GPP access.
  • wireless LAN access network and non-3GPP AN may be referred to as non-3GPP access.
  • the nodes arranged in the access network_B may be collectively referred to as NG-RAN nodes.
  • the device included in the access network_A and / or the access network_B and / or the access network_A, and / or the device included in the access network_B is the access network or the access network device. May be called.
  • 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. Be placed.
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • PGW Packet Data Network Gateway
  • PGW-C Packet Data Network Gateway
  • PCRF Policy and Charging Rules Function
  • HSS Home Subscriber Server
  • core network_B corresponds to 5GCN (5G Core Network).
  • 5GCN 5G Core Network
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • SMF Session Management Function
  • PCF Policy Control Function
  • UDM Unified Data Management
  • 5GCN may be expressed as 5GC.
  • the core network_A and / or the core network_B, the device included in the core network_A, and / or the device included in the core network_B are the core network, or the core network device or the core network. Sometimes referred to as an internal device.
  • the core network is a mobile network operator (Mobile) that connects the access network (access network_A and / or access network_B) with the PDN and / or DN. It may be an IP mobile communication network operated by Network Operator; MNO), it may be a core network for a mobile communication operator that operates and manages mobile communication system 1, or it may be an MVNO (Mobile Virtual Network Operator). ), MVNE (Mobile Virtual Network Enabler), and other virtual mobile communication operators and virtual mobile communication service providers.
  • MNO IP mobile communication network operated by Network Operator
  • MNO Mobile Virtual Network Operator
  • MVNE Mobile Virtual Network Enabler
  • the PDN may be a DN (Data Network) that provides a communication service to the UE.
  • the DN may be configured as a packet data service network or may be configured for each service.
  • the PDN may include a connected communication terminal. Therefore, connecting to the PDN may be connecting to a communication terminal or server device arranged in the PDN. Further, sending and receiving user data to and from the PDN may be sending and receiving user data to and from a communication terminal or server device arranged in the PDN.
  • PDN may be expressed as DN
  • DN may be expressed as PDN.
  • access network_A, core network_A, PDN, access network_B, core network_B, at least a part of DN, and / or one or more devices included in these are referred to as a network or network device. May be called. That is, the fact that the network and / or the network device sends and receives messages and / or executes the procedure means that the access network_A, core network_A, PDN, access network_B, core network_B, and DN are used. It means that at least a part and / or one or more devices contained therein send / receive messages and / or perform procedures.
  • the UE can connect to the access network.
  • the UE can also connect to the core network via the access network.
  • the UE can connect to the PDN or DN via the access network and core network. That is, the UE can send / receive (communicate) user data with the PDN or DN.
  • IP Internet Protocol
  • non-IP communication may be used.
  • IP communication is data communication using IP, and data is transmitted and received by IP packets.
  • An IP packet is composed of an IP header and a payload part.
  • the payload section may include devices / functions included in EPS and data transmitted / received by devices / functions included in 5GS.
  • non-IP communication is data communication that does not use IP, and data is transmitted and received in a format different from the structure of IP packets.
  • non-IP communication may be data communication realized by sending and receiving application data to which an IP header is not added, or a UE may add another header such as a Mac header or an Ethernet (registered trademark) frame header. User data to be sent and received may be sent and received.
  • the access network_A, the core network_A, the access network_B, the core network_B, the PDN_A, and the DN_A may be configured with devices not shown in FIG.
  • the core network_A and / or the core network_B may include an AUSF (Authentication Server Function) or a AAA (Authentication, authorization, and accounting) server (AAA-S).
  • AUSF Authentication Server Function
  • AAA Authentication, authorization, and accounting server
  • 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 the authentication procedure.
  • the AAA server is a device that has authentication, approval, and billing functions that directly or indirectly connects to AUSF via other network devices.
  • the AAA server may be a network device in the core network.
  • the AAA server may not be included in the core network_A and / or the core network_B, but may be included in the PLMN. That is, the AAA server may be a core network device or a device outside the core network.
  • the AAA server may be a server device in PLMN managed by 3rd Party.
  • each device / function is described one by one in FIG. 2 for the sake of simplification of the figure, a plurality of similar devices / functions may be configured in the mobile communication system 1.
  • the mobile communication system 1 has multiple UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5GAN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150.
  • Devices / functions such as the above may be configured.
  • each device may be configured as physical hardware, may be configured as logical (virtual) hardware configured on general-purpose hardware, or may be configured as software. May be done. Further, at least a part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.
  • each storage unit in each device / function appearing below may be, for example, a semiconductor memory or SSD (semiconductor memory unit). It consists of Solid State Drive), HDD (Hard Disk Drive), etc.
  • each storage unit has not only the information originally set from the shipping stage, but also devices / functions other than its own device / function (for example, UE and / or access network device, and / or core network device, and /. Or, various information transmitted / received to / from PDN and / or DN) can be stored.
  • each storage unit can store identification information, control information, flags, parameters, and the like included in control messages transmitted and received in various communication procedures described later. Further, each storage unit may store such information for each UE. In addition, each storage unit may store control messages and user data transmitted / received between 5GS and / or the devices / functions included in EPS when an interwork is performed between 5GS and EPS. can. At this time, not only those transmitted / received via the N26 interface but also those transmitted / received without the N26 interface can be stored.
  • the UE is composed of a control unit_A300, an antenna 310, a transmission / reception unit_A320, and a storage unit_A340.
  • the control unit_A300, the transmission / reception unit_A320, and the storage unit_A340 are connected via a bus.
  • the transmitter / receiver_A320 is connected to the antenna 310.
  • Control unit_A300 is a functional unit that controls the operation and functions of the entire UE.
  • the control unit_A300 realizes various processes in the UE by reading and executing various programs stored in the storage unit_A340 as needed.
  • the transmission / reception unit_A320 is a functional unit for wireless communication with the base station device (eNB or gNB) in the access network via the antenna. That is, the UE may send 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 transmission / reception unit_A320. can.
  • the base station device eNB or gNB
  • the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transmission / reception unit_A320.
  • the UE can communicate with the base station device (gNB) in the 5GAN by using the transmission / reception unit_A320.
  • the UE can send and receive NAS (Non-Access-Stratum) messages to and from the AMF via the N1 interface by using the transmitter / receiver _A320.
  • NAS Non-Access-Stratum
  • the storage unit_A340 is a functional unit for storing programs, user data, control information, etc. required for each operation of the UE.
  • the gNB is composed of a control unit_B500, an antenna 510, a network connection unit_B520, a transmission / reception 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 transmitter / receiver_B530 is connected to the antenna 510.
  • Control unit_B500 is a functional unit that controls the operation and function of the entire gNB.
  • the control unit_B500 realizes various processes in gNB by reading and executing various programs stored in the storage unit_B540 as needed.
  • the network connection part_B520 is a functional part 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 the UPF using the network connection unit_B520.
  • the transmission / reception unit_B530 is a functional unit for wireless communication with the UE via the antenna 510. That is, the gNB can transmit / receive user data and / or control information to / from the UE by using the transmission / reception unit_B530.
  • gNB in 5GAN can communicate with AMF via the N2 interface by using the network connection part_B520, and UPF via the N3 interface. Can communicate with. Further, the gNB can communicate with the UE by using the transmission / reception unit_B530.
  • the storage unit_B540 is a functional unit for storing programs, user data, control information, etc. required for each operation of gNB.
  • the AMF consists 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 AMF may be a node that handles the control plane.
  • 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 AMF by reading and executing various programs stored in the storage unit_B740 as needed.
  • the network connection unit_B720 is a functional unit for AMF to connect to the base station equipment (gNB) in 5GAN and / or SMF, and / or PCF, and / or UDM, and / or SCEF. That is, the AMF uses the network connection _B720 to the user between the base station equipment (gNB) in 5GAN 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.
  • the AMF within the 5GCN can communicate with the gNB via the N2 interface by using the network connection _A620 and with the UDM via the N8 interface. It can communicate, it can communicate with the SMF via the N11 interface, and it can communicate with the PCF via the N15 interface.
  • AMF can send and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620.
  • the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN.
  • 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. required for each operation of AMF.
  • AMF has a function to exchange control messages with RAN using N2 interface, a function to exchange NAS messages with UE using N1 interface, a function to encrypt and protect the integrity of NAS messages, and registration management.
  • the RM status for each UE is managed.
  • the RM state may be synchronized between the UE and AMF.
  • the RM state includes a non-registered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state).
  • 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.
  • the RM-REGISTERED state the UE is registered in the network, so the UE can receive services that require registration with the network.
  • the RM state may be expressed as a 5GMM state.
  • the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state
  • the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state.
  • 5GMM-REGISTERED may be in a state where each device has established a 5GMM context or a state in which a PDU session context has been established.
  • UE_A10 may start sending and receiving user data and control messages, or may respond to paging. Further, when each device is 5GMM-REGISTERED, UE_A10 may execute a registration procedure other than the registration procedure for initial registration and / or a service request procedure.
  • each device may be in a state where the 5GMM context has not been established, the location information of UE_A10 may not be known to the network, or the network reaches UE_A10. It may be in an impossible state. If each device is 5GMM-DEREGISTERED, UE_A10 may start the registration procedure or establish a 5GMM context by executing the registration procedure.
  • the CM status for each UE is managed.
  • the CM state may be synchronized between the UE and AMF.
  • the CM state includes a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state).
  • 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.
  • the CM-IDLE state the UE does not have an N2 interface connection (N2 connection) or an N3 interface connection (N3 connection).
  • N2 connection N2 interface connection
  • N3 connection N3 interface connection
  • the CM-CONNECTED state it has a NAS signaling connection established with AMF via the N1 interface.
  • the CM-CONNECTED state the UE may have an N2 interface connection (N2 connection) and / or an N3 interface connection (N3 connection).
  • the CM state in 3GPP access and the CM state in non-3GPP access may be managed separately.
  • the CM state in 3GPP access may be a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over 3GPP access).
  • the CM state in non-3GPP access includes the non-connected state (CM-IDLE state over non-3GPP access) in non-3GPP access and the connection state (CM-CONNECTED state over non-3GPP access) in non-3GPP access. ) And so on.
  • the disconnected state may be expressed as an idle mode
  • the connected state mode may be expressed as a connected mode.
  • the CM state may be expressed as 5GMM mode (5GMM mode).
  • the non-connected state may be expressed as 5GMM non-connected mode (5GMM-IDLE mode)
  • the connected state may be expressed as 5GMM connected mode (5GMM-CONNECTED mode).
  • the non-connected state in 3GPP access may be expressed as 5GMM non-connected mode (5GMM-IDLE mode over 3GPP access) in 3GPP access
  • the connected state in 3GPP access may be expressed as 5GMM connection mode (5GMM-) in 3GPP access. It may be expressed as CONNECTED mode over 3GPP access).
  • non-connected state in non-3GPP access may be expressed as 5GMM non-connected mode (5GMM-IDLE mode over non-3GPP access) in non-3GPP access, and the connected state in non-3GPP access is non.
  • -3GPP access may be expressed as 5GMM connection mode (5GMM-CONNECTED mode over non-3GPP access).
  • the 5GMM non-connection mode may be expressed as an idle mode, and the 5GMM connection mode may be expressed as a connected mode.
  • AMF may be placed in the core network_B.
  • AMF may be an NF that manages one or more NSIs (Network Slice Instances).
  • the AMF may be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among a plurality of NSIs.
  • CCNF Common CPNF (Control Plane Network Function)
  • N3IWF is a device and / or function that is placed between non-3GPP access and 5GCN when the UE connects to 5GS via non-3GPP access.
  • the SMF consists 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.
  • Control unit_B700 is a functional unit that controls the operation and functions of the entire SMF.
  • the control unit_B700 realizes various processes in the SMF by reading and executing various programs stored in the storage unit_B740 as needed.
  • the network connection part_B720 is a functional part 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 between the AMF and / or the UPF, and / or the PCF, and / or the UDM by using the network connection unit_B720.
  • the SMF within the 5GCN can communicate with the AMF via the N11 interface by using the network connection _A620 and with the UPF via the N4 interface. It can communicate, it can communicate with the PCF via the N7 interface, and it can communicate with the UDM via the N10 interface.
  • the storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of SMF.
  • SMF has session management functions such as establishment / modification / release of PDU sessions, IP address allocation and management functions for UEs, UPF selection and control functions, and appropriate destinations (destination). ), UPF setting function for routing traffic to), function to send and receive SM part of NAS message, function to notify that downlink data has arrived (Downlink Data Notification), AN via N2 interface via AMF It has a function to provide SM information peculiar to AN (for each AN) transmitted to, a function to determine the SSC mode (Session and Service Continuity mode) for the session, a roaming function, and the like.
  • SSC mode Session and Service Continuity mode
  • the UPF consists 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.
  • Control unit_B700 is a functional unit that controls the operation and functions of the entire UPF.
  • the control unit_B700 realizes various processes in the UPF by reading and executing various programs stored in the storage unit_B740 as needed.
  • the network connection unit_B720 is a functional unit for the UPF to connect to the base station device (gNB) in 5GAN and / or the SMF and / or the DN. That is, the UPF uses the network connection _B720 to send and receive user data and / or control information between the base station equipment (gNB) in 5GAN and / or the SMF and / or the DN. Can be done.
  • the UPF within the 5GCN can communicate with the gNB via the N3 interface by using the network connection _A620 and with the SMF via the N4 interface. It can communicate, it can communicate with the DN via the N6 interface, and it can communicate with other UPFs via the N9 interface.
  • the storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of UPF.
  • the UPF acts as an anchor point for intra-RAT mobility or inter-RAT mobility, as an external PDU session point for interconnecting the DN (ie, as a gateway between the DN and the core network_B).
  • Data forwarding function ), packet routing and forwarding function, ULCL (Uplink Classifier) function that supports routing of multiple traffic flows to one DN, and multi-homed PDU session support.
  • It has a branching point function, a QoS (Quality of Service) processing function for userplane, a function for verifying uplink traffic, a function for buffering downlink packets, and a function for triggering downlink data notification (Downlink Data Notification).
  • QoS Quality of Service
  • the UPF may also be a gateway for IP communication and / or non-IP communication.
  • the UPF may have a function of transferring IP communication, or may have a function of converting between non-IP communication and IP communication.
  • the multiple gateways may be a gateway connecting the core network_B and a single DN.
  • the UPF may have connectivity with other NFs, or may be connected to each device via other NFs.
  • the user plane is user data transmitted and received between the UE and the network.
  • the user plane may be transmitted and received using a PDN connection or a PDU session.
  • 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.
  • the user plane may be transmitted and received via the interface between the UE and NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface.
  • the user plane may be expressed as a U-Plane.
  • control plane is a control message sent and received to control the 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.
  • NAS Non-Access-Stratum
  • the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface.
  • the control plane may be transmitted / received using the interface between the UE and NG RAN and the N2 interface.
  • the control plane may be expressed as a control plane or a C-Plane.
  • the U-Plane (User Plane; UP) may be a communication path for transmitting and receiving user data, and may be composed of a plurality of bearers.
  • 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.
  • the PCF consists of a control unit_700, a network connection unit_720, and a storage unit_740.
  • the control unit_700, network connection unit_720, and storage unit_740 are connected via a bus.
  • Control unit_700 is a functional unit that controls the operation and functions of the entire PCF.
  • the control unit_700 may process all the functions that the other functional units (network connection unit_720, storage unit_740) in the PCF do not have.
  • the control unit _700 realizes various processes in the PCF by reading and executing various programs stored in the storage unit _740 as needed.
  • the network connection part_720 is a functional part for the PCF to connect with AMF and / or SMF and / or AF (Application Function). That is, the PCF can send and receive control information to and from the AMF and / or the SMF and / or the AF by using the network connection unit_720.
  • the PCF can communicate with the AMF via the N15 interface and with the SMF via the N7 interface by using the network connection _720, and can communicate with the N5 interface (interface between PCF and AF). ) Can communicate with AF.
  • the storage unit_740 is a functional unit for storing programs, user data, control information, etc. required for each operation of UPF.
  • PCF has a function to support a unified policy framework, a function to provide policy rules to the control function (control plane function) to enforce them, a function to access registration information (subscription information), etc. have.
  • the PCF also has a function to generate URSP (UERoute Selection Policy) rules and the like. All of these functions may be controlled by the control unit_700.
  • the network refers to at least a part of the access network_B, core network_B, and DN. Further, one or more devices included in at least a part of the access network_B, the core network_B, and the DN may be referred to as a network or a network device. That is, the fact that the network performs transmission / reception and / or processing of messages may mean that devices (network devices and / or control devices) in the network execute message transmission / reception and / or processing. .. Conversely, the fact that a device in the network performs transmission / reception and / or processing of a message may mean that the network executes transmission / reception and / or processing of a message.
  • the SM (session management) message (also referred to as NAS (Non-Access-Stratum) SM message) may be a NAS message used in a procedure for SM (hereinafter, also referred to as SM procedure), and AMF_A240 may be used. It may be a control message sent and received between UE_A10 and SMF_A230 via. Further, the SM message includes a PDU session establishment request message, a PDU session establishment acceptance message, a PDU session establishment reject message, and a PDU session modification request (PDU session modification).
  • PDU session modification PDU session modification
  • PDU session modification command PDU session modification command
  • PDU session modification completion message PDU session modification complete
  • PDU session change command rejection PDU session modification command reject
  • PDU session modification rejection PDU session modification reject message
  • PDU session release request message PDU session release reject message
  • PDU session release command message PDU session release complete (PDU session release complete)
  • PDU session release complete PDU session release complete
  • each procedure may be a procedure started from UE or a procedure started from NW.
  • the MM (Mobility management) message (also referred to as NAS MM message) may be a NAS message used for the procedure for MM, and may be a control message sent / received between UE_A10 and AMF_A240.
  • the MM messages include Registration request messages, Registration accept messages, Registration reject messages, De-registration request messages, and De-registration accept messages. ) Messages, configuration update command messages, configuration update complete messages, service request messages, service accept messages, service reject messages, notifications ) Messages, Notification response messages, etc. may be included.
  • the procedure for MM or MM procedure is registration procedure (Registration procedure), non-registration procedure (De-registration procedure), generic UE configuration update procedure, authentication / approval procedure, service request procedure ( Service request procedure), paging procedure (Paging procedure), notification procedure (Notification procedure) may be included.
  • the 5GS (5G System) service may be a connection service provided using the core network_B190. Further, the 5GS service may be a service different from the EPS service or a service similar to the EPS service.
  • non5GS service may be a service other than the 5GS service, and may include an EPS service and / or a non-EPS service.
  • the PDN (Packet Data Network) type indicates the type of PDN connection, and includes IPv4, IPv6, IPv4v6, and non-IP.
  • IPv4 When IPv4 is specified, it indicates that data is sent and received using IPv4.
  • IPv6 When IPv6 is specified, it indicates that data is sent and received using IPv6.
  • IPv4v6 When IPv6 is specified, it indicates that data is sent and received using IPv4 or IPv6.
  • non-IP it indicates that communication is performed by a communication method other than IP, not communication using IP.
  • a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as a relationship between a DN that provides a PDU connectivity service and a UE, but it is established between the UE and an external gateway. It may be connectivity.
  • the UE can send and receive user data to and from the DN using the PDU session.
  • the external gateway may be UPF, SCEF, or the like.
  • the UE can use the PDU session to send and receive user data to and from devices such as application servers located on the DN.
  • each device may manage one or more identification information in association with each PDU session.
  • these identification information may include one or more of DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and other information. It may be further included. Further, when a plurality of PDU sessions are established, the identification information associated with the PDU session may have the same content or different contents.
  • DNN Data Network Name
  • DNN may be identification information that identifies the core network and / or the external network such as DN.
  • DNN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 to connect the core network B190.
  • the DNN may correspond to an APN (Access Point Name).
  • the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet, and Unstructured.
  • IPv4 When IPv4 is specified, it indicates that data is sent and received using IPv4.
  • IPv6 When IPv6 is specified, it indicates that data is sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Further, Ethernet may indicate that communication using IP is not performed.
  • Unstructured it indicates that data is sent / received to the application server etc. in the DN by using the point-to-point (P2P) tunneling technology.
  • P2P point-to-point
  • the PDU session type may include an IP in addition to the above. IP can be specified if the UE can use both IPv4 and IPv6.
  • PLMN Public land mobile network
  • PLMN is a communication network that provides mobile wireless communication services.
  • PLMN is a network managed by an operator who is a telecommunications carrier, and the operator can be identified by the PLMN ID.
  • the PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the IMSI (International Mobile Subscriber Identity) of the UE may be Home PLMN (HPLMN).
  • the UE may have an Equivalent HPLMN list for identifying one or more EPLMNs (Equivalent HPLMNs) in the USIM.
  • the PLMN different from HPLMN and / or EPLMN may be VPLMN (Visited PLMN).
  • the PLMN successfully registered by the UE may be an RPLMN (Registered PLMN).
  • a network slice is a logical network that provides specific network capabilities and network characteristics.
  • UEs and / or networks can support network slices (NW slices; NS) in 5GS.
  • Network slices may also be referred to simply as slices.
  • a network slice instance is composed of an instance (entity) of a network function (NF) and a set of necessary resources, and forms a network slice to be arranged.
  • NF is a processing function in the network and is adopted or defined in 3GPP.
  • NSI is an entity of NS composed of one or more in core network_B.
  • NSI may be configured by a virtual NF (Network Function) generated by using NST (Network Slice Template).
  • NST Network Slice Template
  • NST Network Slice Template
  • the NSI may be an aggregate in the core network_B190 composed of a plurality of NFs.
  • NSI may be a logical network configured to separate user data delivered by services and the like.
  • One or more NFs may be configured in NS.
  • the NF configured in NS may or may not be a device shared with other NS.
  • UE and / or devices in the network are 1 or more based on NSSAI and / or S-NSSAI and / or UE usage type and / or registration information such as 1 or more NSI IDs and / or APN. Can be assigned to NS.
  • the UE usage type is a parameter value included in the UE registration information used to identify the NSI.
  • the UE usage type may be stored in the HSS.
  • AMF may select SMF and UPF based on UE usage type.
  • S-NSSAI Single Network Slice Selection Assistance Information
  • S-NSSAI may be composed of only SST (Slice / Service type) or may be composed of both SST and SD (Slice Differentiator).
  • SST is information indicating the operation of NS expected in terms of functions and services.
  • the SD may be information that interpolates the SST when selecting one NSI from a plurality of NSIs represented by the SST.
  • the S-NSSAI may be information peculiar to each PLMN, or may be standard information shared among PLMNs.
  • the network may store one or more S-NSSAI in the registration information of the UE as the default S-NSSAI. If the S-NSSAI is the default S-NSSAI and the UE does not send a valid S-NSSAI to the network in the registration request message, the network may provide the NS related to the UE.
  • NSSAI Network Slice Selection Assistance Information
  • S-NSSAI Network Slice Selection Assistance Information
  • the UE may memorize the NSSAI permitted by the network for each PLMN. Also, NSSAI may be the information used to select AMF.
  • requested NSSAI (hereinafter, also referred to as Requested NSSAI, Requested NSSAI) is NSSAI provided from the UE to the network during the registration procedure.
  • the requested NSSAI may be an allowed NSSAI or a configured NSSAI stored in the UE.
  • requested NSSAI may be information indicating a network slice that the UE wants to access.
  • the S-NSSAI included in the requested NSSAI may be expressed as requested S-NSSAI.
  • requested NSSAI is included in an RRC (Radio Resource Control) message that includes a NAS message or NAS (Non-Access-Stratum) message sent from the UE to the network, such as a registration request message or a PDU session establishment request message. Will be done.
  • RRC Radio Resource Control
  • NAS Non-Access-Stratum
  • allowed NSSAI (hereinafter, also referred to as permitted NSSAI and Allowed NSSAI) is information indicating one or more network slices to which a UE is permitted.
  • allowed NSSAI is information that identifies the network slice that the network has allowed to connect to the UE.
  • the UE and the network each store and manage allowed NSSAI for each access (3GPP access or non-3GPP access) as UE information.
  • S-NSSAI included in allowed NSSAI may be expressed as allowed S-NSSAI.
  • the allowed S-NSSAI may be configured to include S-NSSAI and mapped S-NSSAI. Further, the SST or SD constituting the S-NSSAI included in the allowed NSSAI may indicate an IMS service.
  • the value of SST or SD that constitutes S-NSSAI included in allowed NSSAI may correspond to the IMS service. That is, the value of SST corresponding to the IMS service may be predetermined, or the value of SD corresponding to the IMS service may be predetermined.
  • the first S-NSSAI is information that identifies the network slice corresponding to IMS (hereinafter, also referred to as IMS service).
  • the first S-NSSAI may be information that identifies a network slice that supports communication using IMS.
  • the first S-NSSAI may be included in Allowed NSSAI and default NSSAI (hereinafter, also referred to as default NSSAI).
  • the first S-NSSAI may be an S-NSSAI stored in the UE and / or the NW, or may be an S-NSSAI transmitted from the NW to the UE.
  • the first S-NSSAI for IMS services may be pre-defined by specifications or operators.
  • the first S-NSSAI may be an S-NSSAI that is valid (usable) in the first registration area but not valid in the second registration area for the IMS service. Further, the first S-NSSAI is valid (available) in the first registration area for the IMS service, but may be valid in the second registration area for services other than the IMS service. ..
  • the second S-NSSAI is information that identifies the network slice corresponding to IMS.
  • the second S-NSSAI may be information that identifies a network slice that supports communication using IMS.
  • the second S-NSSAI may be included in Allowed NSSAI and default NSSAI.
  • the second S-NSSAI may be an S-NSSAI stored in the UE and / or the NW, or may be an S-NSSAI transmitted from the NW to the UE.
  • a second S-NSSAI for IMS services may be pre-defined by specifications or operators.
  • the second S-NSSAI is valid (available) in the second registration area for the IMS service, but is valid or not valid in the first registration area. It may be.
  • default NSSAI corresponds to IMS (hereinafter, also referred to as supporting IMS service) default S-NSSAI (hereinafter, also referred to as default S-NSSAI).
  • Information including one or more may be information that includes a default S-NSSAI that supports communication using IMS.
  • the default S-NSSAI may be the same as or different from the first S-NSSAI.
  • the default NSSAI and / or the default S-NSSAI may be the S-NSSAI stored in the UE and / or the NW.
  • the default S-NSSAI may be valid in all PLMNs (hereinafter, also referred to as usable or applicable), or may be valid in the current PLMN. Also, the default S-NSSAI for IMS services may be pre-defined by specifications or operators.
  • the tracking area (hereinafter also referred to as TA) is a single or multiple range that can be represented by the location information of UE_A10 managed by the core network.
  • the tracking area may be composed of a plurality of cells. Further, the tracking area may be a range in which a control message such as paging is broadcast, or a range in which UE_A10 can move without performing a handover procedure. Further, the tracking area may be a routing area, a location area, or the same as these.
  • the tracking area may be identified by a TAI (Tracking Area Identity) composed of TAC (Tracking area code) and PLMN.
  • the registration area is a set of one or more TAs assigned to the UE by AMF.
  • UE_A10 may be able to move without transmitting and receiving a signal for updating the tracking area while moving within one or a plurality of TAs included in the registration area.
  • the registration area may be a group of information indicating an area where UE_A10 can move without performing the registration procedure.
  • the registration area may be identified by a TAI list composed of one or more TAIs.
  • the URSP may be composed of one or more URSP rules (UERouteSelectionPolicyRule) paste.
  • each URSP rule may be composed of a rule priority (Rule Precedence) and / or a traffic descriptor (Traffic descriptor) and / or a route selection descriptor list (List of Route Selection Descriptors).
  • the rule priority indicates the order of the URSP rules enforced in the UE.
  • the UE may refer to each rule priority and apply them in order from the URSP rule with the highest priority.
  • Traffic descriptor indicates when to apply the URSP rule.
  • Traffic descriptors include Application descriptors and / or IP descriptors, and / or Domain descriptors, and / or non-IP descriptors, And / or DNN (Data Network Name), and / or connection capabilities (Connection Capabilities).
  • the application descriptor may include the OS ID and the OS application ID.
  • the IP descriptor also indicates information that identifies the destination of the IP traffic and may include, for example, an IP address, an IPv6 network prefix, a port number, a protocol number, and the like. Further, the domain descriptors may indicate the FQDN (Fully Qualified Domain Name) of the destination.
  • the non-IP descriptor may also indicate information that identifies the destination of non-IP traffic (eg, ethernet traffic or unstructured traffic).
  • the DNN may also be information about the DNN provided by the application.
  • the connection capability may also indicate the information provided by the UE's application when the UE requests a connection to the network with some capability. Here, the connection capability may indicate IMS.
  • the route selection descriptor list may be composed of one or more route selection descriptors (Route Selection Descriptor).
  • Each route selection descriptor may be composed of a rule selection descriptor priority (Route Selection Descriptor Precedence) and / or a route selection configuration (Route selection components).
  • the rule selection descriptor priority indicates the order in which the route selection descriptor is applied.
  • the UE receives a route selection descriptor list, that is, it receives one or more route selection descriptors, it refers to the rule selection descriptor priority in each route selection descriptor and describes the route selection with high priority. It may be applied in order from the child.
  • the route selection configuration includes SSC mode selection (SSC Mode Selection) and / or network slice selection (Network Slice Selection) and / or DNN selection (DNN Selection) and / or PDU session type selection (PDU Session Type Selection). ), And / or a non-seamless Offload indication, and / or an Access Type preference.
  • the SSC mode selection may indicate that the application traffic is routed through the specified SSC mode PDU session.
  • the network slice selection may also indicate that the application traffic is routed using the indicated PDU session that supports one or more S-NSSAI.
  • the network slice selection may indicate a first S-NSSAI that supports IMS.
  • DNN selection may also indicate routing application traffic with a PDU session that supports one or more of the indicated DNNs.
  • the PDU session type selection may indicate that the traffic of the application is routed using a PDU session that supports the indicated PDU session type.
  • the non-seamless offload instruction may also indicate that the application traffic is offloaded for non-3GPP access.
  • the access type preference may also indicate the access type that establishes the PDU session if the UE needs to establish the PDU session.
  • the access type may indicate 3GPP, non-3GPP, or multi-access.
  • the first identification information is default S-NSSAI (hereinafter, also referred to as default S-NSSAI). Further, the first identification information may be the same as the eleventh identification information and / or the 21st identification information and / or the 31st identification information. Further, the first identification information may be selected from the eleventh identification information and / or the 21st identification information and / or the 31st identification information.
  • the second identification information is information indicating a request for information on the registration area where S-NSSAI can be used.
  • the second identification information may be information indicating a request for information on a registration area in which S-NSSAI supporting IMS can be used.
  • the third identification information is the first S-NSSAI that supports IMS. Further, the third identification information may be the same as or different from the S-NSSAI included in the fifteenth identification information. Further, the third identification information may be the same as the sixteenth identification information. Further, the third identification information may be the same as or different from the S-NSSAI included in the 25th identification information. Further, the third identification information may be the same as the 26th identification information. Further, the third identification information may be the same as the 36th identification information.
  • the fourth identification information is information including at least a part of the first to third identification information.
  • the 11th identification information is the default S-NSSAI. Further, the eleventh identification information may be the same as or different from the first identification information and / or the 21st identification information and / or the 31st identification information.
  • the twelfth identification information indicates the registration area in which S-NSSAI contained in Allowed NSSAI is valid, and / or whether S-NSSAI contained in Allowed NSSAI is valid in the current registration area. And / or information indicating whether S-NSSAI contained in Allowed NSSAI is valid in the current PLMN, and / or whether S-NSSAI contained in Allowed NSSAI is valid in all PLMNs. It may be information indicating whether or not.
  • the twelfth identification information is information indicating whether the first S-NSSAI is valid in the registration area and / or information indicating whether or not the first S-NSSAI is valid in the current registration area. And / or even information indicating whether the first S-NSSAI is valid within the current PLMN and / or information indicating whether the first S-NSSAI is valid in all PLMNs. good.
  • the twelfth identification information may be configured as information for each access type for the registration area. That is, the twelfth identification information indicates whether the first S-NSSAI is valid in the current registration area for 3GPP access, and / or is it valid in the current registration area for non-3GPP access. Information indicating whether or not the first S-NSSAI is valid in the current PLMN (Public Land Mobile Network), and / or whether the first S-NSSAI is valid in all PLMNs. It may be information indicating.
  • PLMN Public Land Mobile Network
  • the twelfth identification information includes information on the access type, and may be configured as information associated with the access type for the registration area. That is, the twelfth identification information is information indicating whether or not the first S-NSSAI is valid in the current registration area for each access type, and / or the first S-NSSAI is the current PLMN. It may be information indicating whether it is valid in (Public Land Mobile Network) and / or information indicating whether the first S-NSSAI is valid in all PLMNs.
  • the information regarding the access type may be information indicating 3GPP access or non-3GPP access as described above.
  • the twelfth identification information may be configured as a plurality of individual information for each access unit associated with the access type.
  • the twelfth identification information #A may be information indicating whether or not the first S-NSSAI is valid in the current registration area in 3GPP access, or the twelfth identification information #B. May be information indicating whether or not the first S-NSSAI is valid in the current registration area in non-3GPP access.
  • the thirteenth identification information is that Allowed NSSAI contains S-NSSAI for IMS service and / or the first S-NSSAI contained in Allowed NSSAI is S-NSSAI for IMS service. , And / or information indicating that the last S-NSSAI contained in Allowed NSSAI is the S-NSSAI for the IMS service. Further, the thirteenth identification information may be information indicating the position of the S-NSSAI for the IMS service included in the Allowed NSSAI.
  • the 14th identification information is information that identifies the IMS service. Further, the 14th identification information may be associated with S-NSSAI that supports IMS.
  • the 15th identification information is Allowed NSSAI.
  • the fifteenth identification information may also include a first S-NSSAI that supports the IMS service.
  • all S-NSSAI included in the fifteenth identification information may not support the IMS service.
  • the fifteenth identification information may include the eleventh identification information and / or the fourteenth identification information and / or the sixteenth identification information.
  • the position and order of one or more S-NSSAI included in the fifteenth identification information and the IMS service may be predetermined by the specifications or by the operator.
  • the first S-NSSAI may be pre-defined as the S-NSSAI corresponding to the IMS service.
  • the last S-NSSAI among the one or more S-NSSAI included in the fifteenth identification information is the S-NSSAI corresponding to the IMS service.
  • the nth S-NSSAI from the beginning (where n is a value larger than 1) is the S-NSSAI corresponding to the IMS service. It may be specified in advance that there is.
  • the nth S-NSSAI from the end (where n is a value larger than 1) is the S-NSSAI corresponding to the IMS service. It may be specified in advance that there is.
  • the S-NSSAI included in the fifteenth identification information may be an S-NSSAI composed of SST (Slice / Service type) and / or SD (Slice Differentiator).
  • the 16th identification information is the first S-NSSAI and / or the second S-NSSAI that supports IMS. Further, the 16th identification information may be the same as or different from the S-NSSAI included in the 15th identification information. Further, the 16th identification information may be the same as or different from the S-NSSAI included in the 25th identification information. Further, the 16th identification information may be the same as or different from the 26th identification information. Further, the 16th identification information may be the same as or different from the 36th identification information. Further, the 16th identification information may be S-NSSAI composed of SST (Slice / Service type) and / or SD (Slice Differentiator).
  • the 17th identification information may be information including at least a part of the 11th to 16th identification information.
  • the 21st identification information is the default S-NSSAI. Further, the 21st identification information may be the same as or different from the 1st identification information and / or the 11th identification information and / or the 31st identification information.
  • the 22nd identification information is information indicating whether the first S-NSSAI is valid in the registration area and / or information indicating whether or not the first S-NSSAI is valid in the current registration area. And / or information indicating whether the first S-NSSAI is valid in the current PLMN, and / or information indicating whether the first S-NSSAI is valid in all PLMNs.
  • the 22nd identification information may be configured as information for each access type for the registration area. That is, the 22nd identification information indicates whether the 1st S-NSSAI is valid in the current registration area for 3GPP access, and / or is it valid in the current registration area for non-3GPP access. Information indicating whether or not the first S-NSSAI is valid in the current PLMN (Public Land Mobile Network), and / or whether the first S-NSSAI is valid in all PLMNs. It may be information indicating.
  • PLMN Public Land Mobile Network
  • the 22nd identification information includes information regarding the access type, and may be configured as information associated with the access type for the registration area. That is, the 22nd identification information is information indicating whether or not the 1st S-NSSAI is valid in the current registration area for each access type, and / or the 1st S-NSSAI is the current PLMN. It may be information indicating whether it is valid in (Public Land Mobile Network) and / or information indicating whether the first S-NSSAI is valid in all PLMNs.
  • the information regarding the access type may be information indicating 3GPP access or non-3GPP access as described above.
  • the 22nd identification information may be configured as a plurality of individual information for each access unit associated with the access type.
  • the 22nd identification information #A may be information indicating whether or not the 1st S-NSSAI is valid in the current registration area in 3GPP access, or the 22nd identification information #B. May be information indicating whether or not the first S-NSSAI is valid in the current registration area in non-3GPP access.
  • the 23rd identification information is that Allowed NSSAI contains S-NSSAI for IMS service and / or the first S-NSSAI included in Allowed NSSAI is S-NSSAI for IMS service. , And / or information indicating that the last S-NSSAI contained in Allowed NSSAI is the S-NSSAI for the IMS service. Further, the 23rd identification information may be information indicating the position of the S-NSSAI for the IMS service included in the Allowed NSSAI.
  • the 24th identification information is information that identifies the IMS service. Further, the 24th identification information may be associated with S-NSSAI that supports IMS.
  • the 25th identification information is Allowed NSSAI.
  • the 25th identification information may also include a first S-NSSAI that supports the IMS service.
  • all S-NSSAI included in the 25th identification information may not support the IMS service.
  • the 25th identification information may include the 21st identification information and / or the 24th identification information and / or the 26th identification information.
  • the S-NSSAI included in the 25th identification information may be an S-NSSAI composed of SST (Slice / Service type) and / or SD (Slice Differentiator).
  • the 26th identification information is the first S-NSSAI and / or the second S-NSSAI that supports IMS. Further, the 26th identification information may be the same as or different from the S-NSSAI included in the 15th identification information. Further, the 26th identification information may be the same as or different from the 16th identification information. Further, the 26th identification information may be the same as or different from the S-NSSAI included in the 25th identification information. Further, the 26th identification information may be the same as or different from the 36th identification information. Further, the 26th identification information may be S-NSSAI composed of SST (Slice / Service type) and / or SD (Slice Differentiator).
  • the 27th identification information may be information including at least a part of the 21st to 26th identification information.
  • the 31st identification information is the default S-NSSAI. Further, the 31st identification information may be the same as or different from the 1st identification information and / or the 11th identification information and / or the 21st identification information. Further, the 31st identification information may be included in Allowed NSSAI.
  • the 32nd identification information is information indicating whether the first S-NSSAI is valid in the registration area and / or information indicating whether or not the first S-NSSAI is valid in the current registration area. And / or information indicating whether the first S-NSSAI is valid in the current PLMN, and / or information indicating whether the first S-NSSAI is valid in all PLMNs.
  • the 32nd identification information may be configured as information for each access type for the registration area. That is, the 32nd identification information indicates whether the 1st S-NSSAI is valid in the current registration area for 3GPP access, and / or is it valid in the current registration area for non-3GPP access. Information indicating whether or not the first S-NSSAI is valid in the current PLMN (Public Land Mobile Network), and / or whether the first S-NSSAI is valid in all PLMNs. It may be information indicating.
  • PLMN Public Land Mobile Network
  • the 32nd identification information includes information regarding the access type, and may be configured as information associated with the access type for the registration area. That is, the 32nd identification information is information indicating whether or not the 1st S-NSSAI is valid in the current registration area for each access type, and / or the 1st S-NSSAI is the current PLMN. It may be information indicating whether it is valid in (Public Land Mobile Network) and / or information indicating whether the first S-NSSAI is valid in all PLMNs.
  • the information regarding the access type may be information indicating 3GPP access or non-3GPP access as described above.
  • the 32nd identification information may be configured as a plurality of individual information for each access unit associated with the access type.
  • the 32nd identification information #A may be information indicating whether or not the 1st S-NSSAI is valid in the current registration area in 3GPP access, or the 32nd identification information #B. May be information indicating whether or not the first S-NSSAI is valid in the current registration area in non-3GPP access.
  • the 33rd identification information is URSP.
  • the 33rd identification information may be configured to include at least one of the 32nd, 34th to 36th identification information.
  • the 34th identification information may be mapping information with the 32nd identification information and / or the 35th identification information and / or the 36th identification information.
  • the 34th identification information may be information that explicitly indicates that the 32nd identification information and / or the 35th identification information and / or the 36th identification information correspond to each other.
  • the 35th identification information is information indicating the service type. Further, the 35th identification information may indicate IMS or IMS service. Further, the 35th identification information may be information indicating whether or not S-NSSAI can be used for the IMS service. Further, the 35th identification information may be IMS or Connection Capabilities indicating the IMS service. Further, the 35th identification information may be a connection capability indicating whether or not S-NSSAI can be used for the IMS service. Further, the 35th identification information may be associated with S-NSSAI that supports IMS.
  • the 36th identification information is the first S-NSSAI and / or the second S-NSSAI that supports IMS. Further, the 36th identification information may be the same as or different from the S-NSSAI included in the 15th identification information. Further, the 36th identification information may be the same as or different from the 16th identification information. Further, the 36th identification information may be the same as or different from the S-NSSAI included in the 25th identification information. Further, the 36th identification information may be the same as or different from the 26th identification information. Further, the 36th identification information is the first S-NSSAI selected from one or more S-NSSAI included in the Allowed NSSAI when the PCF receives the information about the Allowed NSSAI received from the AMF. You may.
  • the 36th identification information may be the first S-NSSAI that supports the IMS service, which is valid (available) in the new registration area. Further, the 36th identification information may be included in Allowed NSSAI. Further, the 36th identification information may be S-NSSAI composed of SST (Slice / Service type) and / or SD (Slice Differentiator).
  • the 37th identification information may be information including at least a part of the 31st to 36th identification information.
  • the 41st identification information is a reason value indicating the reason for refusal. Further, the 41st identification information may be a reason value indicating that it cannot be used in the current registration area (unavailable at current registration area). In addition, the 41st identification information is a reason value indicating that the provided S-NSSAI (including the first S-NSSAI) is not available in the current registration area (S-NSSAI unavailable at current registration area). It may be. Also, the 41st identification information may be associated with 3GPP access and / or non-3GPP access. That is, the 41st identification information indicates that it cannot be used in the current registration area for 3GPP access and / or non-3GPP access (unavailable at current registration area for 3GPP access and / or non-3GPP access).
  • the 41st identification information is that the provided S-NSSAI cannot be used in the current registration area for 3GPP access and / or non-3GPP access (S-NSSAI unavailable at current registration area for 3GPP. It may be a reason value indicating access and / or non-3GPP access).
  • HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are each the same device (that is, the same physics).
  • the case where the hardware is configured as the same hardware, the same logical hardware, or the same software) will be described as an example. However, the content described in this embodiment is also applicable when they are configured as different devices (ie, different physical hardware, or different logical hardware, or different software). For example, data may be transmitted / received directly between them, data may be transmitted / received via the N26 interface between AMF and MME, or data may be transmitted / received via UE.
  • the registration procedure is a procedure for the UE to take the initiative in registering with the access network_B and / or the core network_B and / or the DN.
  • the UE can execute this procedure at any time, for example, when the power is turned on, as long as it is not registered in the network. In other words, the UE can start this procedure at any time if it is in the unregistered state (5GMM-DEREGISTERED state).
  • each device (especially UE and AMF) can transition to the registration state (5GMM-REGISTEDED state) based on the completion of the registration procedure.
  • each registration state may be managed by each device for each access. Specifically, each device may independently manage the registration status (registered or unregistered status) for 3GPP access and the registration status for non-3GPP access.
  • the registration procedure updates the location registration information of the UE in the network and / or periodically notifies the network of the status of the UE from the UE and / or updates certain parameters about the UE in the network. It may be the procedure of.
  • the UE may start the registration procedure when it has mobility across TAs. In other words, the UE may initiate the registration process when it moves to a TA that is different from the TA shown in the TA list it holds. In addition, the UE may initiate this procedure when the running backoff timer, or other timer, has expired. In addition, the UE may initiate the registration process when the context of each device needs to be updated due to disconnection or invalidation of the PDU session. In addition, the UE may initiate the registration process if there is a change in capability information and / or preferences regarding the establishment of the UE's PDU session. In addition, the UE may initiate the registration process on a regular basis.
  • the UE will be registered based on the completion of the registration procedure in Chapter 3.2, the completion of the generic UE setting update procedure in Chapter 3.3, the completion of the UE policy management procedure in Chapter 3.4, or the completion of the procedure for SM. You may start the procedure.
  • the UE is not limited to these, and can execute the registration procedure at any timing.
  • the procedure for transitioning from the above-mentioned UE not registered in the network (unregistered state) to the registered state (registered state) is the initial registration procedure or registration for initial registration. It may be a procedure (registration procedure for initial registration).
  • the registration procedure executed in the state where the UE is registered in the network (registration state) can be changed to the registration procedure (registration procedure for mobility and periodic registration update) or the move and periodic update. It may be a registration procedure (mobility and periodic registration procedure).
  • the new AMF (hereinafter, also simply referred to as AMF) in Fig. 6 indicates the AMF in which the UE is registered by this procedure, and the old AMF means the AMF in which the UE was registered by the registration procedure prior to this procedure. If the AMF is not changed in this procedure, the interface between the old AMF and the new AMF and the procedure between the old AMF and the new AMF do not occur, and the new AMF may be the same device as the old AMF. In the present embodiment, when AMF is described, it may mean new AMF, old AMF, or both.
  • the UE starts the registration procedure by sending a registration request message to new AMF (S600) (S602) (S604). Specifically, the UE sends an RRC message including a registration request message to 5GAN (or gNB) (S600).
  • the registration request message is a NAS message sent and received on the N1 interface. Further, the RRC message may be a control message transmitted / received between the UE and 5GAN (or gNB).
  • NAS messages are processed in the NAS layer, and RRC messages are processed in the RRC layer.
  • the NAS layer is a layer higher than the RRC layer.
  • the UE can send one or more of the identification information of the first to the fourth identification information by including it in the registration request message and / or the RRC message.
  • the identification information of the first to the fourth may be as described in Chapter 2.7.
  • the UE may send the registration request message and / or the RRC message with identification information indicating the type of this procedure.
  • the identification information indicating the type of this procedure may be 5GS registration type IE, and this procedure is for initial registration (initial registration), or for updating registration information (mobility registration update) due to movement, or. It may be information indicating that the registration procedure is for periodic registration information update (periodic registration updating) or for emergency registration (emergency registration). In particular, if this procedure is executed when the registration area is changed due to the movement of the UE, the UE may set this 5GS registration type IE to mobility registration updating.
  • the UE may include the UE capability information in a registration request message in order to notify the network of the functions supported by the UE.
  • the capability information of the UE may be 5GMM capability of 5GS.
  • these identification information is different from the control message, for example, a layer lower than the RRC layer (Radio Resource Control) (for example, MAC (Medium Access Control) layer, RLC (Radio Link Control) layer, PDCP ( It may be included in the control message of the Packet Data Convergence Protocol) layer) and transmitted.
  • the UE may indicate that the UE supports each function, may indicate a request of the UE, or may indicate both of them.
  • two or more identification information of these identification information may be configured as one or more identification information.
  • the information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.
  • the UE determines whether or not to transmit the identification information of the first to the fourth to the network, the ability information of the UE and / or the UE policy, and / or the state of the UE, and / or the registration information of the user, and /. Alternatively, it may be selected and determined based on the context held by the UE.
  • the UE may execute the following processing when deciding whether or not to transmit at least one or more of the identification information of the first to the fourth.
  • the UE For example, if the UE has already received the fifteenth and thirty-third identifications from the core network, it will be based on the fifteenth and thirty-third identifications for the IMS service. , 1 or more S-NSSAI contained in the 15th identification information and S-NSSAI indicated by the 36th identification information contained in the 33rd identification information, which is valid (available in the current registration area). N) S-NSSAI may be selected as the third identification information and the third identification information may be transmitted.
  • the 33rd identification information is included. It is determined that the S-NSSAI indicated by the 36th identification information contained in the current registration area is valid in the current registration area, is valid in the current PLMN, or is valid in all PLMNs. Based on the 15 identification information and the 33rd identification information, for the IMS service, one or more S-NSSAI contained in the 15th identification information and the 36th identification information contained in the 33rd identification information. From the S-NSSAI shown, the S-NSSAI valid (available) in the current registration area may be selected as the third identification information and the third identification information may be transmitted.
  • the 36th identification information included in the 33rd identification information is stored in the Allowed NSSAI by the PCF.
  • the first S-NSSAI indicated by the 36th identification information is used as the third identification information for the IMS service based on the 33rd identification information. You may choose to send a third identification.
  • the 36th identification information included in the 33rd identification information is included in the 15th identification information. If the 36th identification information is included in the 15th identification information, select the 36th identification information as the 3rd identification information and select the 3rd identification information for the IMS service. Information may be sent. The UE also checks whether the 36th identification information is included in the 15th identification information, and if the 36th identification information is not included in the 15th identification information, for the IMS service, It is not necessary to select the 36th identification information as the third identification information. In this case, the UE does not have to transmit the third identification information.
  • the UE may confirm whether or not the 36th identification information included in the 33rd identification information is included in the 15th identification information for each access. That is, the UE may confirm whether or not the 36th identification information contained in the 33rd identification information is included in the 15th identification information for each of the 3GPP access and the non-3GPP access. .. For example, for 3GPP access, the 36th identification information contained in the 33rd identification information is included in the 15th identification information, but for non-3GPP access, the 36th identification information included in the 33rd identification information is included.
  • the UE selects the 36th identification information as the 3rd identification information for the IMS service and obtains the 3rd identification information via 3GPP access. You may send it. Also, for 3GPP access, the 36th identification information included in the 33rd identification information is not included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information. If the identification information is included in the 15th identification information, the UE selects the 36th identification information as the third identification information for the IMS service and provides the third identification information via non-3GPP access. You may send it.
  • the 36th identification information included in the 33rd identification information is included in the 15th identification information
  • the 36th identification information included in the 33rd identification information is included. If the identification information is included in the 15th identification information, the UE selects the 36th identification information as the 3rd identification information for the IMS service and sends it from either 3GPP access or non-3GPP access. You may choose to do so and send the third identification information via the selected access.
  • the 36th identification information included in the 33rd identification information is not included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information. If the identification information is not included in the fifteenth identification information, the UE may not select the 36th identification information as the third identification information for the IMS service. In this case, the UE does not have to transmit the third identification information.
  • the UE may store the eleventh identification information in association with the IMS service.
  • the eleventh identification information is valid in all PLMNs, and the UE moves to a new registration area different from the current registration area, and the UE is a new registration area.
  • the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid (supports IMS service) has not been received in the new system.
  • the UE selects the default S-NSSAI indicated by the 11th identification information as the 1st identification information for the IMS service, and the 1st identification information. Identification information may be transmitted.
  • the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE selects the default S-NSSAI indicated by the 11th identification information as the 1st identification information and sends the 1st identification information for the IMS service. It's okay.
  • the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the registration area does not belong to the current PLMN, the UE may not select the default S-NSSAI indicated by the eleventh identifier as the first identifier for the IMS service. At this time, the UE does not have to transmit the first identification information.
  • the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the UE shall Select the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) as the third identification information for the IMS service, and the third identification information. Identification information may be transmitted.
  • the UE may store the 21st identification information in association with the IMS service.
  • the 21st identification information is valid for all PLMNs, and the UE moves to a new registration area different from the current registration area, and the UE is a new registration area.
  • the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid (supports IMS service) has not been received in the new system. Regardless of whether the registration area belongs to the current PLMN, the UE selects the default S-NSSAI indicated by the 21st identification information as the 1st identification information for the IMS service, and the 1st identification information is used.
  • Identification information may be transmitted. Also, if the 21st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE selects the default S-NSSAI indicated by the 21st identification information as the 1st identification information and sends the 1st identification information for the IMS service. It's okay.
  • the 21st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the registration area does not belong to the current PLMN, the UE may not select the default S-NSSAI indicated by the 21st Distinguished Information as the 1st Distinguished Information for the IMS service. At this time, the UE does not have to transmit the first identification information.
  • the UE When receiving the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall Select the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) as the third identification information for the IMS service, and the third identification information. Identification information may be transmitted.
  • the UE may store the 31st identification information in association with the IMS service.
  • the 31st identification information is valid for all PLMNs, and the UE moves to a new registration area different from the current registration area, and the UE is a new registration area.
  • the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid (supports IMS service) has not been received in the new system. Regardless of whether the registration area belongs to the current PLMN, the UE selects the default S-NSSAI indicated by the 31st identification information as the 1st identification information for the IMS service, and the 1st identification information.
  • Identification information may be transmitted. Also, if the 31st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE selects the default S-NSSAI indicated by the 31st identification information as the 1st identification information and sends the 1st identification information for the IMS service. It's okay.
  • the UE may not select the default S-NSSAI indicated by the 31st Distinguished Information as the 1st Distinguished Information for the IMS service. At this time, the UE does not have to transmit the first identification information.
  • the UE When receiving the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall Select the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) as the third identification information for the IMS service, and the third identification information. Identification information may be transmitted.
  • the UE wants to know the effective range of the registration area of the first S-NSSAI that supports the IMS service when communicating using the IMS service, in other words, the first that supports the IMS service.
  • the first that supports the IMS service.
  • the UE stores the thirty-third identification information, and further, the twelfth identification information is stored.
  • the identification information of the above and the fifteenth identification information or the S-NSSAI included in the fifteenth identification information may be stored in association with each other.
  • the UE uses the S-NSSAI and the 36th identification information contained in the 15th identification information based on the 12th identification information, the 15th identification information, and the 33rd identification information. From the first S-NSSAI shown, the S-NSSAI valid (available) in the current registration area may be selected as the third identification information and the third identification information may be transmitted.
  • the UE when the UE has already received the 14th identification information, the 15th identification information and / or the 16th identification information from the core network when communicating using the IMS service, the UE has received the 14th identification information and / or the 16th identification information. , UE stores the S-NSSAI indicated by the 15th identification information and / or the 16th identification information in association with the IMS service, and is based on the current registration area and the stored S-NSSAI. Then, the requested S-NSSAI (hereinafter, also referred to as Requested S-NSSAI) may be selected and the S-NSSAI may be transmitted.
  • Requested S-NSSAI hereinafter, also referred to as Requested S-NSSAI
  • the UE when communicating using the IMS service, the UE has already received the 12th identification information, the 14th identification information, the 15th identification information, and / or the 16th identification information from the core network.
  • the UE stores the S-NSSAI indicated by the 15th identification information and / or the 16th identification information, the IMS service, and the 12th identification information in association with each other. Based on the current registration area and the stored S-NSSAI, the requested S-NSSAI may be selected and the S-NSSAI may be transmitted.
  • the UE when the UE has already received the 24th identification information, the 25th identification information, and / or the 26th identification information from the core network when performing communication using the IMS service, the UE has received the 24th identification information and / or the 26th identification information. , UE stores the S-NSSAI indicated by the 25th identification information and / or the 26th identification information in association with the IMS service, and is based on the current registration area and the stored S-NSSAI. Then, you may select the requested S-NSSAI and send the S-NSSAI.
  • the UE when communicating using the IMS service, the UE has already received the 22nd identification information, the 24th identification information, the 25th identification information, and / or the 26th identification information from the core network.
  • the UE stores the S-NSSAI indicated by the 25th identification information and / or the 26th identification information, the IMS service, and the 22nd identification information in association with each other. Based on the current registration area and the stored S-NSSAI, the requested S-NSSAI may be selected and the S-NSSAI may be transmitted.
  • the UE when the UE communicates using the IMS service and has already received the 15th identification information from the core network, the UE is an SST or SST that constitutes S-NSSAI included in the 15th identification information. If the value of SD is S-NSSAI that indicates the IMS service, that S-NSSAI may be selected as the third identification information and the third identification information may be transmitted.
  • the UE may use the SST or SST that constitutes the S-NSSAI included in the 25th identification information. If the value of SD is S-NSSAI that indicates the IMS service, that S-NSSAI may be selected as the third identification information and the third identification information may be transmitted.
  • the UE when communicating using the IMS service, the UE has already received the fifteenth identification information from the core network and is included in the fifteenth identification information (supports IMS). If the UE knows that the location and order of the S-NSSAI in the S-NSSAI and its association with the IMS service is pre-specified by the specification or pre-specified by the operator, the UE will use the fifteenth identification information. Even if the first S-NSSAI that supports the IMS service is selected from among one or more S-NSSAI included and the first S-NSSAI is sent as the third identification information based on that information. good.
  • the UE knows the position of the first S-NSSAI in Allowed NSSAI in advance, the 14th identification information and / or the 24th identification information and / or the first from the core network.
  • the first S-NSSAI may be identified without receiving information that explicitly indicates the correspondence between the IMS service and the first S-NSSAI, such as the identification information of 34.
  • the UE when communicating using the IMS service, the UE has already received the 25th identification information from the core network and is included in the 25th identification information (supports IMS). If the UE knows that the location and order of the S-NSSAI in the S-NSSAI and its association with the IMS service is pre-specified by the specification or pre-specified by the operator, the UE will use the 25th identification information. Even if the first S-NSSAI that supports the IMS service is selected from among one or more S-NSSAI included and the first S-NSSAI is sent as the third identification information based on that information. good.
  • the UE knows the position of the first S-NSSAI in Allowed NSSAI in advance, the 14th identification information and / or the 24th identification information and / or the first from the core network.
  • the first S-NSSAI may be identified without receiving information that explicitly indicates the correspondence between the IMS service and the first S-NSSAI, such as the identification information of 34.
  • the UE communicates using the IMS service
  • the information indicated by the 13th identification information is used.
  • the first S-NSSAI (which supports IMS) is selected from the one or more S-NSSAI contained in the fifteenth identification information, and the first S-NSSAI is used as the third identification information. You may send it.
  • the UE when the UE communicates using the IMS service, if it has already received the 23rd identification information and the 25th identification information from the core network, it will be the information indicated by the 23rd identification information. Based on this, the first S-NSSAI (which supports IMS) is selected from among one or more S-NSSAIs included in the 25th identification information, and the first S-NSSAI is used as the third identification information. You may send it.
  • the UE may use the IMS service for communication.
  • the first identification information and / or the third identification information may be transmitted.
  • the UE communicates using the IMS service, if the UE has already received the 15th identification information including the 16th identification information and the 14th identification information from the core network, the 16th identification information is used.
  • the first S-NSSAI indicated by the identification information may be transmitted as the third identification information.
  • the UE When the UE transmits the selected S-NSSAI and / or the first identification information and / or the selected third identification information, the S-NSSAI and / or the first identification information and / or the third identification information. You may send a requested NSSAI containing the identification information.
  • one or more third identification information may be transmitted.
  • a requested NSSAI containing one or more third identification information may be transmitted.
  • transmitting at least one of the first to third identification information may mean transmitting the fourth identification information.
  • the UE may include registration request messages and / or RRC messages containing registration request messages other than the identification information of 1 to 4, for example, including UEID and / or PLMNID and / or AMF identification information. You may send it.
  • the AMF identification information may be AMF or information that identifies a set of AMF, for example, 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) or GUAMI (Globally Unique AMF Identifier). It's okay.
  • 5GAN when 5GAN (or gNB) receives the RRC message including the registration request message, it selects the AMF to which the registration request message is forwarded (S602).
  • the 5GAN can select AMF based on one or more identification information contained in the registration request message and / or the RRC message. Specifically, the 5GAN (or gNB) may select the new AMF to which the registration request message is sent based on at least one of the identification information of the first to the fourth identification information.
  • 5GAN (or gNB) forwards the identification information and / or the registration request message contained in the registration request message and / or the RRC message to the selected new AMF (S604).
  • the new AMF when it receives the registration request message, it can execute the first condition determination.
  • the first conditional determination is for determining whether or not the network (or new AMF) accepts the UE request.
  • new AMF executes the procedure from S606 to S612 if the first condition determination is true.
  • new AMF may execute the procedure of S610 without executing the procedure of S606 to S608 when the first condition determination is false.
  • the new AMF may request the UE context from the old AMF and may determine the first condition after receiving the UE context from the old AMF (S606, S608). In that case, new AMF executes S610 and S612 if the first condition determination is true. On the other hand, new AMF may execute S610 when the first condition determination is false.
  • control message transmitted and received by the S610 may be a registration acceptance message, and if the first condition determination is false, the control message is transmitted by the S610. And the control message received may be a Registration reject message.
  • the first condition determination is the reception of the registration request message and / or each identification information contained in the registration request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and It may be executed based on / or the state of the network and / or the user's registration information and / or the context held by AMF.
  • the first condition determination is true, and if the network does not allow the UE request, the first condition determination may be false. Also, if the network to which the UE is registered and / or the devices in the network support the functions required by the UE, the first condition determination is true and does not support the functions required by the UE. In this case, the first condition determination may be false. Further, if the transmitted / received identification information is permitted, the first conditional determination may be true, and if the transmitted / received identification information is not permitted, the first conditional determination may be false.
  • the first condition determination may be true.
  • the first condition determination is performed regardless of whether or not the NSSAI includes the first S-NSSAI that supports IMS. It may be true.
  • the first condition determination is true. You may.
  • new AMF has NSSAI (Allowed NSSAI) allowed for UE and there is no first S-NSSAI that supports IMS allowed for UE, the first condition determination is false. You may.
  • the new AMF executes the procedures of S606 and S608, and the new AMF is included in the message received from the UE. If it is the same as the AMF shown in the identification information, the procedure of S606 and S608 is not executed. In other words, if the AMF change occurs due to this procedure, the S606 and S608 procedures are executed, and if the AMF change does not occur, the S606 and S608 procedures are skipped.
  • new AMF sends a UE context request message to old AMF with the AMF shown in the AMF identification information as old AMF (S606).
  • the old AMF sends the UE context to the new AMF based on the received UE context request message.
  • New AMF creates a UE context based on the received UE context.
  • the UE context sent from new AMF to old AMF may include UE ID and allowed NSSAI.
  • the UE context may include configured NSSAI and / or rejected NSSAI, NSSAI and / or pending NSSAI, and / or a first NSSAI.
  • allowed NSSAI and / or configured NSSAI and / or rejected NSSAI and / or pending NSSAI and / or the first NSSAI and / or S-NSSAI included in each NSSAI included in the UE context are sent to the UE.
  • Information on whether or not the notification has been completed may be linked.
  • the new AMF sends a control message to the UE based on the determination of the first condition determination and / or the reception of the UE context from the old AMF (S610).
  • the control message may be a registration acceptance message or a registration refusal message.
  • the new AMF may send the control message including at least one identification information out of the 11th to 17th identification information.
  • the identification information of Chapters 11 to 17 may be as described in Chapter 2.7.
  • the AMF may indicate that the network supports each function by transmitting these identification information and / or a control message, or may indicate that the request of the UE has been accepted. However, it may indicate that the request from the UE is not permitted, or it may indicate information that combines these. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information.
  • the information indicating the support of each function and the information indicating the permission to use each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.
  • AMF shall indicate which of the 11th to 17th identification information is included in the control message, each identification information received, and / or subscriber information, and / or network capability information, and / or. Selections and decisions may be made based on operator policy and / or network status and / or user registration information and / or context held by AMF.
  • the new AMF when new AMF receives at least one of the identification information of the first to the fourth from the UE, the new AMF sends at least one of the identification information of the eleventh to the 17th by including the identification information in the control message. good.
  • new AMF receives at least one of the identification information 1 to 4 from the UE, and when the setting information of the UE is updated from the previous registration procedure, the 11th to 17th The identification information may be sent including the updated information.
  • AMF also receives each 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.
  • the registration acceptance message may be sent to indicate that the UE request has been accepted, or the registration refusal message has been sent to indicate that the UE request has been rejected, based on the context held by the AMF. May be shown.
  • the UE may recognize the content of the control message and / or the received information when the control message is received (S610) via 5GAN (gNB).
  • gNB 5GAN
  • the UE when the control message is a registration acceptance message, the UE receives the registration acceptance message so that the UE's request by the registration request message is accepted, and the contents of various identification information contained in the registration acceptance message. Can be recognized. Further, when the control message is a registration refusal message, the UE receives the registration refusal message, so that the UE's request by the registration request message is rejected, and the contents of various identification information included in the registration refusal message. Can be recognized. Further, the UE may recognize that the request of the UE has been rejected if the control message is not received within a predetermined period after the registration request message is transmitted.
  • the UE may execute the following processing based on the reception of at least one or more of the identification information of the 11th to 17th and / or the reception of the control message. The UE may execute these processes during this procedure or after the procedure is completed.
  • the UE requests the establishment of a PDU session for the IMS service when it receives the 15th identification information in this procedure when it has already received the 33rd identification information from the core network.
  • it is indicated by one or more S-NSSAI contained in the 15th identification information and the 36th identification information contained in the 33rd identification information based on the 15th identification information and the 33rd identification information.
  • a session establishment request message may be sent.
  • the 33rd identification information is included. It is determined that the S-NSSAI indicated by the 36th identification information contained in the current registration area is valid in the current registration area, is valid in the current PLMN, or is valid in all PLMNs. Based on the 15 identification information and the 33rd identification information, for the IMS service, one or more S-NSSAI contained in the 15th identification information and the 36th identification information contained in the 33rd identification information. From the S-NSSAI shown, select a valid (available) S-NSSAI in the current registration area and send a registration request message containing that S-NSSAI, or with that S-NSSAI. A PDU session establishment request message may be sent.
  • the UE may store the fifteenth identification information or the S-NSSAI included in the fifteenth identification information. Then, when the UE requests the establishment of a PDU session for the IMS service after receiving the 33rd identification information, the 15th identification information and the 15th identification information based on the 33rd identification information are used. Among the one or more S-NSSAI contained in the S-NSSAI and the S-NSSAI indicated by the 36th identification information contained in the 33rd identification information, the S-NSSAI valid (usable) in the current registration area is selected.
  • the UE when the UE has already received the 33rd identification information from the core network, the UE receives the 15th identification information in this procedure, and the 36th identification information included in the 33rd identification information is the PCF.
  • the UE requests the establishment of a PDU session for the IMS service when the 15th identification information is received in this procedure when the 33rd identification information has already been received from the core network.
  • the UE also checks whether the 36th identification information is included in the 15th identification information, and if the 36th identification information is not included in the 15th identification information, for the IMS service, Do not select the first S-NSSAI indicated by the 36th identification information and do not send a registration request message containing the first S-NSSAI, or send a PDU session establishment request message with the first S-NSSAI. You don't have to send it.
  • the UE may confirm whether or not the 36th identification information included in the 33rd identification information is included in the 15th identification information for each access. That is, the UE may confirm whether or not the 36th identification information contained in the 33rd identification information is included in the 15th identification information for each of the 3GPP access and the non-3GPP access. .. For example, for 3GPP access, the 36th identification information contained in the 33rd identification information is included in the 15th identification information, but for non-3GPP access, the 36th identification information included in the 33rd identification information is included.
  • the UE sends a registration request message containing the 1st S-NSSAI indicated by the 36th identification information via 3GPP access for the IMS service.
  • a PDU session establishment request message may be sent via 3GPP access, either sent or with the first S-NSSAI indicated by the 36th identification.
  • the 36th identification information included in the 33rd identification information is not included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information.
  • the UE sends a registration request message containing the first S-NSSAI indicated by the thirty-sixth identification information via non-3GPP access for the IMS service.
  • a PDU session establishment request message may be sent via non-3GPP access, either by sending or with the first S-NSSAI indicated by the 36th identification information.
  • the 36th identification information included in the 33rd identification information is included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information is included.
  • the UE chooses whether to send from 3GPP access or non-3GPP access for the IMS service, and via the selected access, the 36th.
  • a registration request message containing the first S-NSSAI indicated by the identification information may be sent, or a PDU session establishment request message may be sent together with the first S-NSSAI indicated by the 36th identification information.
  • the 36th identification information included in the 33rd identification information is not included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information.
  • the UE does not select the 1st S-NSSAI indicated by the 36th identification information for the IMS service and includes the 1st S-NSSAI. It is not necessary to send the registration request message or send the PDU session establishment request message together with the first S-NSSAI.
  • the UE may store the eleventh identification information in association with the IMS service.
  • the eleventh identification information is valid for all PLMNs, and the UE moves to a new registration area different from the current registration area, and the UE is the new registration area. If you have not received a valid first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid in Whether or not the registration area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the eleventh identification for the IMS service.
  • the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the eleventh identification for the IMS service. Also, if the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the registration area does not belong to the current PLMN, the UE may not select the default S-NSSAI indicated by the eleventh identification for the IMS service. Also, if the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the UE When receiving the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall The first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) may be selected for the IMS service. The UE then sends a registration request message containing the selected default S-NSSAI or the first S-NSSAI, or along with the selected default S-NSSAI or the first S-NSSAI, a PDU session establishment request message. May be sent.
  • the UE selects S-NSSAI, it sends a registration request message containing the selected default S-NSSAI or the first S-NSSAI, or the selected default S-NSSAI or the first S. - May send a PDU session establishment request message with NSSAI. If the UE does not select S-NSSAI, the UE may send a registration request message that does not include S-NSSAI. Also, if the UE does not select S-NSSAI, it does not have to send the registration request message.
  • the UE may store the 33rd identification information.
  • the UE when the UE receives the twelfth identification information and the fifteenth identification information from the core network, the UE shall receive the twelfth identification information and the fifteenth identification information, or the fifteenth identification information. It may be stored in association with S-NSSAI included in. Then, when the UE requests the establishment of a PDU session for the IMS service, the S included in the fifteenth identification information is based on the twelfth identification information, the fifteenth identification information, and the thirty-third identification information.
  • the UE when the UE receives the twelfth identification information and the fifteenth identification information from the core network, the UE includes the twelfth identification information and the fifteenth identification information or the fifteenth identification information.
  • S-NSSAI may be associated with and stored. Then, when the UE requests the establishment of a PDU session for the IMS service after receiving the 33rd identification information, it is based on the 12th identification information, the 15th identification information, and the 33rd identification information. Select a valid (available) S-NSSAI in the current registration area from the S-NSSAI contained in the 15th identification information and the 1st S-NSSAI indicated by the 36th identification information.
  • a registration request message containing the S-NSSAI may be sent, or a PDU session establishment request message may be sent together with the S-NSSAI. Whether or not the selected S-NSSAI is valid (usable) in the current registration area may be determined based on the 32nd identification information.
  • the UE has established a PDU session using the first S-NSSAI for the IMS service in the first registration area, and the first S-NSSAI is the first for the IMS service. If it is valid (available) in the registration area but not in the second registration area, the UE will send the first S-NSSAI from the core network in the second registration area.
  • the 15th identification information including, the 16th identification information indicating the second S-NSSAI, and the 14th identification information indicating the IMS service corresponding to the second S-NSSAI are received, and the second identification information is received. If S-NSSAI is enabled in the second registration area for the IMS service, the UE will base the receipt of the 14th and 16th identification information (IMS in the 2nd registration area).
  • the UE After initiating the PDU session establishment procedure for the IMS service with the second S-NSSAI (which supports the service), use the first S-NSSAI (which does not support the IMS service in the second registration area). Start the PDU session release procedure to release the existing PDU session, or start the PDU session release procedure to release the PDU session using the first S-NSSAI, and then start the second S-NSSAI. It may be used to initiate the PDU session establishment procedure for the IMS service. In this case, the UE may use the first S-NSSAI indicated by the fifteenth identification information in the second registration area to perform communication other than the IMS service.
  • the UE when the UE receives the 14th identification information, the 15th identification information and / or the 16th identification information from the core network when communicating using the IMS service, the UE receives the 14th identification information and / or the 16th identification information.
  • the 15th identification information and / or the S-NSSAI indicated by the 16th identification information is stored in association with the IMS service, and the request is made based on the current registration area and the stored S-NSSAI. You may select the S-NSSAI to be used and send a registration request message containing the S-NSSAI, or send a PDU session establishment request message together with the S-NSSAI.
  • the twelfth identification information, the twelfth identification information, the fifteenth identification information, and / or the sixteenth identification information are obtained from the core network.
  • the UE stores the S-NSSAI indicated by the 15th identification information and / or the 16th identification information, the IMS service, and the 12th identification information in association with each other, and also stores the current registration. Select the requested S-NSSAI based on the relation area and the stored S-NSSAI and send a registration request message containing the S-NSSAI, or send a PDU session establishment request message with the S-NSSAI. You can do it.
  • the UE when the UE receives the 15th identification information from the core network when communicating using the IMS service, the value of SST or SD that constitutes S-NSSAI included in the 15th identification information. If is an S-NSSAI that indicates an IMS service, select that S-NSSAI and send a registration request message containing that S-NSSAI, or send a PDU session establishment request message with that S-NSSAI. You may.
  • the UE receives the fifteenth identification information from the core network and is included in the fifteenth identification information (supports IMS) when communicating using the IMS service.
  • the UE shall be one or more S-NSSAI included in the fifteenth identification information. Select the first S-NSSAI that supports the IMS service from among them, based on its location and order, and send a registration request message containing the first S-NSSAI, or the first S-NSSAI.
  • a PDU session establishment request message may be sent.
  • the UE knows the position of the first S-NSSAI in Allowed NSSAI in advance, the 13th identification information and / or the 14th identification information and / or the first from the core network. You have not received information that explicitly indicates the correspondence between the IMS service and the first S-NSSAI, such as the 23 identification information and / or the 24th identification information and / or the 34th identification information. However, the first S-NSSAI may be identified.
  • the UE when the UE receives the thirteenth identification information and the fifteenth identification information from the core network when communicating using the IMS service, the UE is based on the information indicated by the thirteenth identification information. Select the first S-NSSAI (which supports IMS) from one or more S-NSSAIs contained in the fifteenth identification information and send a registration request message containing the first S-NSSAI. Alternatively, a PDU session establishment request message may be sent together with the first S-NSSAI.
  • the UE may use the IMS service for communication.
  • Select default S-NSSAI or 1st S-NSSAI and send a registration request message containing default S-NSSAI or 1st S-NSSAI, or with default S-NSSAI or 1st S-NSSAI.
  • a PDU session establishment request message may be sent.
  • the UE receives the 15th identification information including the 16th identification information and the 14th identification information from the core network when communicating using the IMS service.
  • the UE receives the 16th identification information. You may select the first S-NSSAI shown and send a registration request message containing the first S-NSSAI, or you may send a PDU session establishment request message with the first S-NSSAI.
  • the UE can further send a registration completion message to AMF via 5GAN (gNB) as a response message to the registration acceptance message (S612).
  • the registration completion 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 5GAN (gNB).
  • AMF receives a registration completion message via 5GAN (gNB) (S612).
  • gNB 5GAN
  • each device completes this procedure based on the transmission / reception of the registration acceptance message and / or the registration completion message.
  • each device may complete this procedure based on the transmission / reception of the registration refusal message.
  • each device may transition or maintain the state in which the UE is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission / reception of the registration acceptance message and / or the registration completion message. , Transition or maintenance to the state where the UE is not registered in the network (RM_DEREGISTERED state, or 5GMM-DEREGISTERED state) on the access that received the registration refusal message to the current PLMN based on the transmission and reception of the registration refusal message. You may. Further, the transition to each state of each device may be performed based on the transmission / reception of the registration acceptance message and / or the registration completion message and / or the registration refusal message, or the completion of this procedure.
  • each device stores the information sent / received in these messages based on the transmission / reception of the registration request message and / or the registration acceptance message and / or the registration completion message and / or the registration refusal message, or the completion of this procedure. You may be aware of your network decisions.
  • each device may determine the next behavior based on the updated and / or stored stored information based on the completion of this procedure.
  • each device After completing this procedure, if the state transitions to the state registered on the current access of the current PLMN, each device establishes a PDU session on the current access of the current PLMN.
  • the establishment procedure may be started.
  • the UE may transmit the third identification information in the PDU session establishment procedure.
  • the selection method of S-NSSAI to be transmitted as the third identification information the selection method when being included in the registration request message and / or RRC message of this procedure may be used.
  • the selected S-NSSAI may be used as requested NSSAI in the PDU session establishment procedure.
  • the UE may select the S-NSSAI requested by the following method.
  • the UE shall be included in one or more S-NSSAIs contained in the 15th identification information and the 36th identification information contained in the 33rd identification information for the IMS service based on the 15th identification information and the 33rd identification information. From the S-NSSAI indicated by the identification information of, a valid (available) S-NSSAI in the current registration area may be selected and requested.
  • the UE confirms from the core network whether or not the 36th identification information included in the 33rd identification information is included in the 15th identification information, and the 36th identification information becomes the 15th identification information. If included, the 36th identification may be selected and requested as the third identification for the IMS service.
  • the UE also checks whether the 36th identification information is included in the 15th identification information, and if the 36th identification information is not included in the 15th identification information, for the IMS service, It is not necessary to select the 36th identification information as the third identification information. In this case, the UE does not have to initiate the PDU session establishment procedure for the IMS service.
  • the UE also stores the default S-NSSAI for the IMS service received and / or preset in the UE as the 11th identification information and / or the 21st identification information in association with the IMS service. However, if it is valid in the current registration area, the first S-NSSAI (16th identification information and / or 26th identification information) that is also valid in the current registration area (supporting IMS service). , And / or the 36th identification information) is not received or stored, the S-NSSAI shown in the 11th identification information may be selected and requested.
  • the UE Based on the twelfth identification information, the fifteenth identification information, and the thirty-third identification information, the UE performs the S-NSSAI contained in the fifteenth identification information and the first S-NSSAI indicated by the thirty-sixth identification information. Among them, S-NSSAI valid (available) in the current registration area may be selected and requested as the third identification information.
  • the valid (usable) S-NSSAI in the current registration area is used as the third identification information based on the remembered Allowed NSSAI. You may choose and request.
  • the UE is an S-NSSAI whose SST or SD value that constitutes the S-NSSAI included in the Allowed NSSAI is an S-NSSAI that indicates an IMS service, even if that S-NSSAI is selected and requested. good.
  • the UE may select and request the S-NSSAI for the IMS service based on the location and order of the S-NSSAI included in the Allowed NSSAI.
  • the registration procedure described in this chapter may be a registration procedure for initial registration, or may be a registration procedure for movement and regular registration.
  • the UE shall, based on the receipt of the control message and / or the identification information contained in the control message, the registration procedure in Chapter 3.2, the generic UE setting update procedure in Chapter 3.3, or the UE policy management procedure in Chapter 3.4, or SM. You may start the procedure for.
  • This procedure may be initiated when the AMF updates the UE settings for access and mobility management-related parameters.
  • this procedure requires the UE to execute the registration procedure (registration procedure for mobility and periodic registration update) for movement and periodic registration update. It may be started when requested.
  • the UE is generic based on the completion of the registration procedure in Chapter 3.2, the completion of the generic UE setting update procedure in Chapter 3.3, the completion of the UE policy management procedure in Chapter 3.4, or the completion of the procedure for SM. You may start the UE setting update procedure.
  • This procedure is started by AMF sending a configuration update command to the UE via the access network (S800).
  • the setting update command may include at least a part of the identification information of the 21st to 27th.
  • the identification information of Chapters 21 to 27 may be as described in Chapter 2.7.
  • at least one of the information indicated by the identification information of 21 to 27 included in the setting update command is sent and received in the control message (registration acceptance message or registration refusal message) in the registration procedure of Chapter 3.2, respectively. It is preferable that the information is updated from the information indicated by the identification information of the eleventh to the seventeenth, but it may be the same as the information indicated by the identification information of the eleventh to the seventeenth.
  • the UE may be able to understand the meaning of each identification information included in the setting update command and / or the meaning indicated by the combination of each identification information.
  • the UE may update the already stored identification information by receiving the setting update command, or may store the received identification information when the identification information is not yet stored.
  • the UE may execute the following processing based on the reception of at least one or more of the identification information of the 21st to 27th and / or the reception of the setting update command. The UE may execute these processes during this procedure or after the procedure is completed.
  • the UE may store the 21st identification information in association with the IMS service.
  • the 21st identification information is valid for all PLMNs, and the UE moves to a new registration area that is different from the current registration area, and the UE is the new registration area. If you have not received a valid first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid in Whether or not the registration area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the 21st Distinguished Information for the IMS service.
  • the 21st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the 21st identification for the IMS service. Also, if the 21st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the registration area does not belong to the current PLMN, the UE may not select the default S-NSSAI indicated by the 21st identification for the IMS service. Also, if the 21st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the UE When receiving the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall The first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) may be selected for the IMS service. The UE then sends a registration request message containing the selected default S-NSSAI or the first S-NSSAI, or along with the selected default S-NSSAI or the first S-NSSAI, a PDU session establishment request message. May be sent.
  • the UE selects S-NSSAI, it sends a registration request message containing the selected default S-NSSAI or the first S-NSSAI, or the selected default S-NSSAI or the first S. - May send a PDU session establishment request message with NSSAI. If the UE does not select S-NSSAI, the UE may send a registration request message that does not include S-NSSAI. Also, if the UE does not select S-NSSAI, it does not have to send the registration request message.
  • the UE has established a PDU session using the first S-NSSAI for the IMS service in the first registration area, and the first S-NSSAI is the first for the IMS service. If it is valid (available) in the registration area but not in the second registration area, the UE has already issued the first S-NSSAI from the core network in the second registration area. Received the 15th identification information or the 25th identification information including, or received the 25th identification information including the 1st S-NSSAI in this procedure, and further, in this procedure, the 2nd S-NSSAI.
  • the 26th identification information indicating the second S-NSSAI and the 24th identification information indicating the IMS service corresponding to the second S-NSSAI are received, and the second S-NSSAI receives the second registration for the IMS service.
  • the UE uses a second S-NSSAI (supporting IMS services in the second registration area) based on the receipt of the 24th and 26th identifications.
  • start the PDU session release procedure to release the PDU session with the first S-NSSAI (which does not support the IMS service in the second registration area).
  • the UE may use the first S-NSSAI indicated by the fifteenth identification information in the second registration area to perform communication other than the IMS service.
  • the UE when the UE receives the 24th identification information, the 25th identification information and / or the 26th identification information from the core network when communicating using the IMS service, the UE receives the 24th identification information and / or the 26th identification information.
  • the 25th identification information and / or the S-NSSAI indicated by the 26th identification information is stored in association with the IMS service, and the request is made based on the current registration area and the stored S-NSSAI. You may select the S-NSSAI to be used and send a registration request message containing the S-NSSAI, or send a PDU session establishment request message together with the S-NSSAI.
  • the UE when communicating using the IMS service, the UE obtains the 22nd identification information, the 24th identification information, the 25th identification information, and / or the 26th identification information from the core network. Upon receipt, the UE stores the S-NSSAI indicated by the 25th identification information and / or the 26th identification information, the IMS service, and the 22nd identification information in association with each other, and also stores the current registration. Select the requested S-NSSAI based on the relation area and the stored S-NSSAI and send a registration request message containing the S-NSSAI, or send a PDU session establishment request message with the S-NSSAI. You can do it.
  • the UE when the UE receives the 25th identification information from the core network when communicating using the IMS service, the value of SST or SD that constitutes S-NSSAI included in the 25th identification information. If is an S-NSSAI that indicates an IMS service, select that S-NSSAI and send a registration request message containing that S-NSSAI, or send a PDU session establishment request message with that S-NSSAI. You may.
  • the UE receives the 25th identification information from the core network and is included in the 25th identification information (supports IMS) when communicating using the IMS service. If the location or order of the NSSAI and its association with the IMS service is pre-specified by the specification or pre-specified by the operator, the UE shall be one or more S-NSSAI included in the 25th identification information. Select the first S-NSSAI that supports the IMS service from among them, based on its location and order, and send a registration request message containing the first S-NSSAI, or the first S-NSSAI. At the same time, a PDU session establishment request message may be sent.
  • the UE knows the position of the first S-NSSAI in Allowed NSSAI in advance, the 13th identification information and / or the 14th identification information and / or the first from the core network. You have not received information that explicitly indicates the correspondence between the IMS service and the first S-NSSAI, such as the 23 identification information and / or the 24th identification information and / or the 34th identification information. However, the first S-NSSAI may be identified.
  • the UE when the UE receives the 23rd identification information and the 25th identification information from the core network when communicating using the IMS service, the UE is based on the information indicated by the 23rd identification information. Select the first S-NSSAI (which supports IMS) from one or more S-NSSAIs contained in the 25th identification information and send a registration request message containing the first S-NSSAI. Alternatively, a PDU session establishment request message may be sent together with the first S-NSSAI.
  • the UE may use the IMS service for communication.
  • Select default S-NSSAI or 1st S-NSSAI and send a registration request message containing default S-NSSAI or 1st S-NSSAI, or with default S-NSSAI or 1st S-NSSAI.
  • a PDU session establishment request message may be sent.
  • each device completes this procedure based on the transmission and reception of the setting update command.
  • the UE may perform the registration procedure in Chapter 3.2, the generic UE setting update procedure in Chapter 3.3, or the UE policy management procedure in Chapter 3.4, based on the receipt of the identification information contained in the setting update command and / or the setting update command.
  • the procedure for SM may be started.
  • This procedure is used by the PCF to provide one or more UE policies to the UE.
  • the network may perform this procedure to add one or more new UE policies to the UE.
  • the network may also perform this procedure to modify or delete one or more UE policies stored in the UE.
  • the UE will be based on the completion of the registration procedure in Chapter 3.2, the completion of the generic UE setting update procedure in Chapter 3.3, the completion of the UE policy management procedure in Chapter 3.4, the completion of the procedure for SM, etc. You may start the policy management procedure.
  • This procedure is started when the PCF sends a UE policy management command (MANAGE UE POLICY COMMAND) to the UE via AMF (S900).
  • MANAGE UE POLICY COMMAND MANAGE UE POLICY COMMAND
  • the UE policy management command may include at least a part of the identification information of the 31st to 37th.
  • the identification information of Chapters 31 to 37 may be as described in Chapter 2.7.
  • the PCF determines which of the 31st to 37th identification information is included in the control message, each of the received identification information and / or the subscriber information, and / or the network capability information, and / or. It may be selected and determined based on the operator policy and / or the state of the network and / or the user's registration information and / or the context held by the PCF.
  • the UE can understand the meaning of each identification information contained in the UE policy management command and / or the meaning indicated by the combination of each identification information by receiving the UE policy management command from the PCF (S900). You can do it.
  • the UE may update the already stored identification information by receiving the UE policy management command, or may store the received identification information when the identification information is not yet stored.
  • the UE may execute the following processing based on the reception of at least one or more of the identification information of the 31st to 37th and / or the reception of the setting update command. The UE may execute these processes during this procedure or after the procedure is completed.
  • the UE requests the establishment of a PDU session for the IMS service when the fifteenth identification information has already been received from the core network and the thirty-third identification information is received in this procedure.
  • it is indicated by one or more S-NSSAI contained in the 15th identification information and the 36th identification information contained in the 33rd identification information based on the 15th identification information and the 33rd identification information.
  • a session establishment request message may be sent.
  • the 33rd identification information is included. It is determined that the S-NSSAI indicated by the 36th identification information contained in the current registration area is valid in the current registration area, is valid in the current PLMN, or is valid in all PLMNs. Based on the 15 identification information and the 33rd identification information, for the IMS service, one or more S-NSSAI contained in the 15th identification information and the 36th identification information contained in the 33rd identification information. From the S-NSSAI shown, select a valid (available) S-NSSAI in the current registration area and send a registration request message containing that S-NSSAI, or with that S-NSSAI. A PDU session establishment request message may be sent.
  • the UE receives the 33rd identification information in this procedure, and the 36th identification information included in the 33rd identification information is the PCF.
  • the first S-NSSAI selected from Allowed NSSAI by, and when requesting the establishment of a PDU session for the IMS service, the first S-NSSAI is based on the 33rd identification information. Select (36th identification information contained in the 33rd identification information) and send a registration request message containing the first S-NSSAI, or send a PDU session establishment request message with the first S-NSSAI. You may send it.
  • the UE requests the establishment of a PDU session for the IMS service when the 15th identification information has already been received from the core network and the 33rd identification information is received in this procedure.
  • the UE also checks whether the 36th identification information is included in the 15th identification information, and if the 36th identification information is not included in the 15th identification information, for the IMS service, Do not select the first S-NSSAI indicated by the 36th identification information and do not send a registration request message containing the first S-NSSAI, or send a PDU session establishment request message with the first S-NSSAI. You don't have to send it. Further, in this case, the UE may send a UE policy management command rejection message containing the 41st identification information (S902).
  • the UE may confirm whether or not the 36th identification information included in the 33rd identification information is included in the 15th identification information for each access. That is, the UE may confirm whether or not the 36th identification information contained in the 33rd identification information is included in the 15th identification information for each of the 3GPP access and the non-3GPP access. ..
  • the 36th identification information contained in the 33rd identification information is included in the 15th identification information, but for non-3GPP access, the 36th identification information included in the 33rd identification information is included.
  • the UE sends a registration request message containing the 1st S-NSSAI indicated by the 36th identification information via 3GPP access for the IMS service.
  • a PDU session establishment request message may be sent via 3GPP access, either sent or with the first S-NSSAI indicated by the 36th identification.
  • the UE contains a 41st identification for non-3GPP access indicating that it is not available in the current registration area or that the provided S-NSSAI is not available in the current registration area.
  • a policy management command rejection message may be sent (S902).
  • the 36th identification information included in the 33rd identification information is not included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information. If the identification information is included in the fifteenth identification information, the UE sends a registration request message containing the first S-NSSAI indicated by the thirty-sixth identification information via non-3GPP access for the IMS service.
  • a PDU session establishment request message may be sent via non-3GPP access, either by sending or with the first S-NSSAI indicated by the 36th identification information.
  • the UE provides UE policy management for 3GPP access with a 41st identification that indicates that it is not available in the current registration area or that the provided S-NSSAI is not available in the current registration area.
  • a command rejection message may be sent (S902).
  • the 36th identification information included in the 33rd identification information is included in the 15th identification information
  • the 36th identification information included in the 33rd identification information is included. If the identification information is included in the 15th identification information, the UE chooses whether to send from 3GPP access or non-3GPP access for the IMS service, and via the selected access, the 36th.
  • a registration request message containing the first S-NSSAI indicated by the identification information may be sent, or a PDU session establishment request message may be sent together with the first S-NSSAI indicated by the 36th identification information. In this case, the UE does not have to send a UE policy management command rejection message containing the 41st identification.
  • the 36th identification information included in the 33rd identification information is not included in the 15th identification information
  • the 36th identification information included in the 33rd identification information is not included in the 15th identification information
  • the UE does not select the 1st S-NSSAI indicated by the 36th identification information for the IMS service and includes the 1st S-NSSAI. It is not necessary to send the registration request message or send the PDU session establishment request message together with the first S-NSSAI.
  • the UE is the 41st identification information indicating that the S-NSSAI provided is not available in the current registration area for 3GPP access and non-3GPP access.
  • a UE policy management command rejection message containing may be sent (S902).
  • the UE may store the 31st identification information in association with the IMS service.
  • the 31st identification information is valid for all PLMNs, and the UE moves to a new registration area that is different from the current registration area, and the UE is the new registration area. If you have not received a valid first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid in Whether or not the registration area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the 31st Distinguished Information for the IMS service.
  • the UE may choose the default S-NSSAI indicated by the 31st identification for the IMS service. Also, if the 31st identification information is valid in the current PLMN and the UE moves to a new registration area that is different from the current registration area, and the UE is valid in the new registration area.
  • the first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the 31st identification for the IMS service. Also, if the 31st identification information is valid in the current PLMN and the UE moves to a new registration area that is different from the current registration area, and the UE is valid in the new registration area.
  • the first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the registration area does not belong to the current PLMN, the UE may not select the default S-NSSAI indicated by the 31st identification for the IMS service. Also, if the 31st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area.
  • the UE When receiving the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall The first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) may be selected for the IMS service. The UE then sends a registration request message containing the selected default S-NSSAI or the first S-NSSAI, or a PDU session establishment request message with the selected default S-NSSAI or the first S-NSSAI. good.
  • -NSSAI may be associated and stored.
  • the UE may store the 33rd identification information.
  • the S-NSSAI and S-NSSAI contained in the 15th identification information are based on the 12th identification information, the 15th identification information, and the 33rd identification information.
  • the UE has established a PDU session using the first S-NSSAI for the IMS service in the first registration area, and the first S-NSSAI is the first for the IMS service. If it is valid (available) in the registration area but not in the second registration area, the UE has already issued the first S-NSSAI from the core network in the second registration area. Received the 15th identification information or the 25th identification information or the 36th identification information including, or received the 36th identification information including the 1st S-NSSAI in this procedure, and further in this procedure. The 36th identification information indicating the second S-NSSAI and the 35th identification information indicating the IMS service corresponding to the second S-NSSAI are received, and the second S-NSSAI regarding the IMS service.
  • the UE will support the IMS service in the second registration area based on the receipt of the 35th and 36th identifications.
  • the UE may start the session establishment procedure. In this case, the UE may use the first S-NSSAI indicated by the fifteenth identification information in the second registration area to perform communication other than the IMS service.
  • the UE may use the IMS service for communication.
  • Select default S-NSSAI or 1st S-NSSAI and send a registration request message containing default S-NSSAI or 1st S-NSSAI, or with default S-NSSAI or 1st S-NSSAI.
  • a PDU session establishment request message may be sent.
  • each device completes this procedure based on the transmission / reception of the UE policy management command and / or the UE policy management command rejection message.
  • the UE may use the registration procedure in Chapter 3.2, the generic UE setting update procedure in Chapter 3.3, or the UE in Chapter 3.4 based on the receipt of the identification information contained in the UE policy management command message and / or the UE policy management command message. You may initiate a policy management procedure or a procedure for SM.
  • the program that operates on the apparatus according to one aspect of the present invention is a program that controls a Central Processing Unit (CPU) or the like to operate a computer so as to realize the functions of the embodiment according to one aspect of the present invention. Is also good.
  • the program or the information handled by the program is 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 device system.
  • RAM Random Access Memory
  • HDD Hard Disk Drive
  • the program for realizing the function of the embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. It may be realized by loading the program recorded on this recording medium into a computer system and executing it.
  • the term "computer system” as used herein is a computer system built into a device and includes hardware such as an operating system and peripheral devices.
  • the "computer-readable recording medium” is a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another recording medium that can be read by a computer. Is also good.
  • each functional block or various features of the device used in the above-described embodiment can be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits.
  • Electrical circuits designed to perform the functions described herein can be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or others.
  • Programmable Logic Devices Discrete Gate or Transistor Logic, Discrete Hardware Components, or Combinations thereof.
  • the general purpose processor may be a microprocessor, a conventional processor, a controller, a microcontroller, or a state machine.
  • the electric circuit described above may be composed of a digital circuit or an analog circuit. Further, when an integrated circuit technology that replaces the current integrated circuit appears due to the progress of semiconductor technology, one or a plurality of aspects of the present invention can also use a new integrated circuit according to the technology.
  • one aspect of the present invention is not limited to the above-described embodiment.
  • an example of the device has been described, but one aspect of the present invention is not limited to this, and is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device. , Kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices such as living equipment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Provided is user equipment (UE) comprising a transceiver and a control unit. The transceiver receives a registration acceptance message including Allowed NSSAI from an AMF, and receives a UE policy management command message including URSP from a PCF, the Allowed NSSAI including first S-NSSAI for IMS services, the URSP including first S-NSSAI and first information, and the first information indicating a registration area in which the first S-NSSAI can be used. The control unit selects the first S-NSSAI for IMS services when, during a request for establishment of a PDU session for IMS services, it is determined on the basis of the URSP that the first S-NSSAI included in the Allowed NSSAI can be used in the current registration area.

Description

ＵＥ（Ｕｓｅｒ　Ｅｑｕｉｐｍｅｎｔ）UE (User Equipment)
　本発明の一態様は、UE(User Equipment)に関する。本出願は、２０２０年９月１８日に出願された特願２０２０－１５７０７９号に基づき優先権を主張し、その内容をここに援用する。 One aspect of the present invention relates to UE (User Equipment). This application claims priority based on Japanese Patent Application No. 2020-157079 filed on September 18, 2020, the contents of which are incorporated herein by reference.
　3GPP(3rd Generation Partnership Project)では、第5世代(5G)の移動通信システムである5GS(5G System)のシステムアーキテクチャが検討されており、新しい手続きや新しい機能のサポートするための議論が行われている(非特許文献1～3を参照)。5G規格の初期リリースであるRelease 15において、ネットワークスライスという概念が導入され、Release 17では、IMS(IP Multimedia Subsystem)に関連したネットワークスライスの機能拡張が検討されている(非特許文献4を参照) In 3GPP (3rd Generation Partnership Project), the system architecture of 5GS (5G System), which is a 5th generation (5G) mobile communication system, is being studied, and discussions are being held to support new procedures and new functions. (See Non-Patent Documents 1 to 3). In Release 15, which is the initial release of the 5G standard, the concept of network slices was introduced, and in Release 17, the expansion of network slice functions related to IMS (IP Multimedia Subsystem) is being considered (see Non-Patent Document 4).
　しかしながら、非特許文献4では、レジストレーションエリア(以後、登録エリア、RAとも呼称する)を考慮して、SIP(Session Initiation Protocol)を用いたIMS(以下、IMSサービスとも呼称する)のための通信に使用するS-NSSAIを、どのように選択するべきかについては、明確になっていない。 However, in Non-Patent Document 4, communication for IMS (hereinafter, also referred to as IMS service) using SIP (Session Initiation Protocol) in consideration of the registration area (hereinafter, also referred to as registration area and RA). It is not clear how to select the S-NSSAI to be used for.
　本発明の一態様の目的は、以上のような事情を鑑みてなされたものであり、5GSにおいて、レジストレーションエリアを考慮して、IMSサービスのための通信に使用するS-NSSAIを、適切に選択するための手法を提供することにある。 The object of one aspect of the present invention has been made in view of the above circumstances, and in 5GS, in consideration of the registration area, S-NSSAI used for communication for IMS service is appropriately used. It is to provide a method for selection.
　また、本発明の一態様のUEは、送受信部と制御部とを備え、前記送受信部は、AMF(Access and Mobility Management Function)から、Allowed NSSAI(Network Slice Selection Assistance Information)を含む登録受諾メッセージを受信し、PCF(Policy Control Function)から、URSP(UE Route Selection Policy)を含む、UEポリシー管理コマンドメッセージを受信し、前記Allowed NSSAIは、IMSサービスのための第1のS-NSSAI(Single Network Slice Selection Assistance Information)を含み、前記URSPは、前記第1のS-NSSAIと、第1の情報とを含み、前記第1の情報は、前記第1のS-NSSAIを使用可能なレジストレーションエリアを示す情報であり、前記制御部は、IMSサービスのためのPDUセッションの確立を要求する場合に、前記URSPに基づいて、前記Allowed NSSAIに含まれる前記第1のS-NSSAIが現在のレジストレーションエリアで使用可能であると判断したときは、IMSサービスのために、前記第1のS-NSSAIを選択する、ことを特徴とする。 Further, the UE of one aspect of the present invention includes a transmission / reception unit and a control unit, and the transmission / reception unit receives a registration acceptance message including Allowed NSSAI (Network Slice Selection Assistance Information) from AMF (Access and Mobility Management Function). Received and received a UE policy management command message including URSP (UERoute Selection Policy) from PCF (Policy Control Function), and the Allowed NSSAI is the first S-NSSAI (Single Network Slice) for the IMS service. Selection Assistance Information), the URSP includes the first S-NSSAI and the first information, and the first information includes a registration area where the first S-NSSAI can be used. The information is shown, and when the control unit requests the establishment of a PDU session for the IMS service, the first S-NSSAI included in the Allowed NSSAI is the current registration area based on the URSP. When it is determined that it can be used in, the first S-NSSAI is selected for the IMS service.
　本発明の一態様によれば、5GSにおいて、レジストレーションエリアを考慮して、IMSサービスのための通信に使用するS-NSSAIを、適切に選択することができる。 According to one aspect of the present invention, in 5GS, the S-NSSAI used for communication for the IMS service can be appropriately selected in consideration of the registration area.
移動通信システム(EPS/5GS)の概略を説明する図である。It is a figure explaining the outline of the mobile communication system (EPS / 5GS). 移動通信システム(EPS/5GS)の詳細構成を説明する図である。It is a figure explaining the detailed structure of the mobile communication system (EPS / 5GS). UEの装置構成を説明する図である。It is a figure explaining the apparatus configuration of a UE. 5GSにおけるアクセスネットワーク装置(gNB)の構成を説明する図である。It is a figure explaining the structure of the access network apparatus (gNB) in 5GS. 5GSにおけるコアネットワーク装置(AMF/SMF/UPF/PCF等)の構成を説明する図である。It is a figure explaining the structure of the core network apparatus (AMF / SMF / UPF / PCF, etc.) in 5GS. 登録手続きを説明する図である。It is a figure explaining the registration procedure. ジェネリックUE設定更新手続きを説明する図である。It is a figure explaining the generic UE setting update procedure. UEポリシー管理手続きを説明する図である。It is a figure explaining the UE policy management procedure.
　以下、図面を参照して本発明の一態様を実施する為に最良の形態について説明する。尚、本実施形態では1例として、本発明の一態様を適用した場合の移動通信システムの実施形態について説明する。 Hereinafter, the best mode for carrying out one aspect of the present invention will be described with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system when one aspect of the present invention is applied will be described.
　[1. システムの概要]
　まず、図1は、各実施形態で使用される移動通信システム1の概略を説明する為の図であり、図2は、その移動通信システム1の詳細構成を説明する為の図である。 [1. System overview]
First, FIG. 1 is a diagram for explaining the outline of the mobile communication system 1 used in each embodiment, and FIG. 2 is a diagram for explaining a detailed configuration of the mobile communication system 1.
　図1には、移動通信システム1は、UE_A10、アクセスネットワーク_A80、コアネットワーク_A90、PDN(Packet Data Network)_A5、アクセスネットワーク_B120、コアネットワーク_B190、DN(Data Network)_A6により構成されることが記載されている。 In FIG. 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
　以下では、これらの装置・機能について、UE、アクセスネットワーク_A、コアネットワーク_A、PDN、アクセスネットワーク_B、コアネットワーク_B、DN等のように、記号を省略して記載する場合がある。 In the following, these devices / functions may be described by omitting symbols such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc. ..
　また、図2には、UE_A10、E-UTRAN80、MME40、SGW35、PGW-U30、PGW-C32、PCRF60、HSS50、5G AN120、AMF140、UPF130、SMF132、PCF160、UDM150、N3IWF170等の装置・機能、及びこれらの装置・機能を互いに接続するインターフェースが記載されている。 In addition, Fig. 2 shows the devices / functions of UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5GAN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170, etc. An interface for connecting these devices / functions to each other is described.
　以下では、これらの装置・機能について、UE、E-UTRAN、MME、SGW、PGW-U、PGW-C、PCRF、HSS、5G AN、AMF、UPF、SMF、PCF、UDM、N3IWF等のように、記号を省略して記載する場合がある。 In the following, these devices / functions are described as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5GAN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc. , Symbol may be omitted.
　尚、4GシステムであるEPS(Evolved Packet System)は、アクセスネットワーク_A及びコアネットワーク_Aを含んで構成されるが、さらにUE及び/又はPDNが含まれても良い。また、5Gシステムである5GS(5G System)は、UE、アクセスネットワーク_B及びコアネットワーク_Bを含んで構成されるが、さらにDNが含まれても良い。 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 further include a UE and / or a PDN. Further, the 5GS (5G System), which is a 5G system, is configured to include a UE, an access network_B, and a core network_B, but may further include a DN.
　UEは、3GPPアクセス(3GPPアクセスネットワーク、3GPP ANとも称する)及び/又はnon-3GPPアクセス(non-3GPPアクセスネットワーク、non-3GPP ANとも称する)を介して、ネットワークサービスに対して接続可能な装置である。UEは、携帯電話やスマートフォン等の無線通信が可能な端末装置であってよく、EPSにも5GSにも接続可能な端末装置であってよい。UEは、UICC(Universal Integrated Circuit Card)やeUICC(Embedded UICC)を備えてもよい。尚、UEのことをユーザ装置と表現してもよいし、端末装置と表現してもよい。 UE is a device that can connect to network services via 3GPP access (3GPP access network, also called 3GPPAN) and / or non-3GPP access (non-3GPP access network, also called non-3GPPAN). 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 capable of connecting to EPS or 5GS. The UE may be equipped with a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). The UE may be expressed as a user device or a terminal device.
　また、アクセスネットワーク_Aは、E-UTRAN(Evolved Universal Terrestrial Radio Access Network)及び/又は無線LANアクセスネットワークに対応する。E-UTRANには、1以上のeNB(evolved Node B)45が配置される。尚、以下では、eNB45は、eNBのように記号を省略して記載する場合がある。また、複数のeNBがある場合は、各eNBは、例えばX2インターフェースにより、互いに接続されている。また、無線LANアクセスネットワークには、1以上のアクセスポイントが配置される。 In addition, the access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or wireless LAN access network. One or more eNB (evolved Node B) 45 are arranged in E-UTRAN. In the following, eNB45 may be described by omitting a symbol like eNB. If there are a plurality of eNBs, each eNB is connected to each other by, for example, an X2 interface. In addition, one or more access points are arranged in the wireless LAN access network.
　また、アクセスネットワーク_Bは、5Gアクセスネットワーク(5G AN)に対応する。5G ANは、NG-RAN(NG Radio Access Network)及び/又はnon-3GPP アクセスネットワークで構成される。NG-RANには、1以上のgNB(NR NodeB)122が配置される。尚、以下では、gNB122は、eNBのように記号を省略して記載する場合がある。gNBは、NR(New Radio)ユーザプレーンと制御プレーンをUEに提供するノードであり、5GCNに対してNGインターフェース(N2インターフェース又はN3インターフェースを含む)を介して接続するノードである。すなわち、gNBは、5GSのために新たに設計された基地局装置であり、4GシステムであるEPSで使用されていた基地局装置(eNB)とは異なる機能を有する。また、複数のgNBがある場合は、各gNBは、例えばXnインターフェースにより、互いに接続している。 In addition, access network_B corresponds to 5G access network (5GAN). 5GAN is composed of NG-RAN (NG Radio Access Network) and / or non-3GPP access network. One or more gNB (NR Node B) 122 is placed in NG-RAN. In the following, gNB122 may be described by omitting a symbol such as eNB. The gNB is a node that provides the NR (New Radio) user plane and the control plane to the UE, and is a node that connects to the 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 a different function from the base station device (eNB) used in EPS, which is a 4G system. When there are a plurality of gNBs, each gNB is connected to each other by, for example, an Xn interface.
　また、non-3GPP アクセスネットワークは、信頼できない非3GPP(untrusted non-3GPP)アクセスネットワークであってもよいし、信頼できる非3GPP(trusted non-3GPP)アクセスネットワークであってもよい。ここで、信頼できない非3GPPアクセスネットワークは、例えば公衆無線LANなど、アクセスネットワーク内でセキュリティ管理を行わないnon-3GPPアクセスネットワークであってよい。一方で、信頼できる非3GPPアクセスネットワークは、3GPPが規定するアクセスネットワークであってよく、TNAP(trusted non-3GPP access point)とTNGF(trusted non-3GPP Gateway function)を備えていてもよい。 Further, the non-3GPP access network may be an untrusted non-3GPP (untrusted non-3GPP) access network or a trusted non-3GPP (trusted non-3GPP) access network. Here, the unreliable non-3GPP access network may be a non-3GPP access network that does not perform security management in the access network, for example, a public wireless LAN. On the other hand, the reliable non-3GPP access network may be an access network defined by 3GPP, and may include TNAP (trusted non-3GPP access point) and TNGF (trusted non-3GPP Gateway function).
　また、以下では、E-UTRANやNG-RANは、3GPPアクセスと称することがある。また、無線LANアクセスネットワークやnon-3GPP ANは、non-3GPPアクセスと称することがある。また、アクセスネットワーク_Bに配置されるノードを、まとめてNG-RANノードとも称することがある。 In the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. In addition, wireless LAN access network and non-3GPP AN may be referred to as non-3GPP access. In addition, the nodes arranged in the access network_B may be collectively referred to as NG-RAN nodes.
　また、以下では、アクセスネットワーク_A、及び/又はアクセスネットワーク_B、及び/又はアクセスネットワーク_Aに含まれる装置、及び/又はアクセスネットワーク_Bに含まれる装置は、アクセスネットワーク、又はアクセスネットワーク装置と称する場合がある。 In the following, the device included in the access network_A and / or the access network_B and / or the access network_A, and / or the device included in the access network_B is the access network or the access network device. May be called.
　また、コアネットワーク_Aは、EPC(Evolved Packet Core)に対応する。EPCには、例えば、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)等が配置される。 In addition, 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. Be placed.
　また、コアネットワーク_Bは、5GCN(5G Core Network)に対応する。5GCNには、例えば、AMF(Access and Mobility Management Function)、UPF(User Plane Function)、SMF(Session Management Function)、PCF(Policy Control Function)、UDM(Unified Data Management)等が配置される。ここで、5GCNは、5GCと表現されてもよい。 In addition, 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) and the like are arranged in 5GCN. Here, 5GCN may be expressed as 5GC.
　また、以下では、コアネットワーク_A、及び/又はコアネットワーク_B、コアネットワーク_Aに含まれる装置、及び/又はコアネットワーク_Bに含まれる装置は、コアネットワーク、又はコアネットワーク装置又はコアネットワーク内装置と称する場合がある。 In the following, the core network_A and / or the core network_B, the device included in the core network_A, and / or the device included in the core network_B are the core network, or the core network device or the core network. Sometimes referred to as an internal device.
　コアネットワーク(コアネットワーク_A及び/又はコアネットワーク_B)は、アクセスネットワーク(アクセスネットワーク_A及び/又はアクセスネットワーク_B)と、PDN及び/又はDNとを接続した移動体通信事業者(Mobile Network Operator; MNO)が運用するIP移動通信ネットワークの事であってもよいし、移動通信システム1を運用、管理する移動体通信事業者の為のコアネットワークでもよいし、MVNO(Mobile Virtual Network Operator)や、MVNE(Mobile Virtual Network Enabler)等の仮想移動通信事業者や仮想移動体通信サービス提供者の為のコアネットワークでもよい。 The core network (core network_A and / or core network_B) is a mobile network operator (Mobile) that connects the access network (access network_A and / or access network_B) with the PDN and / or DN. It may be an IP mobile communication network operated by Network Operator; MNO), it may be a core network for a mobile communication operator that operates and manages mobile communication system 1, or it may be an MVNO (Mobile Virtual Network Operator). ), MVNE (Mobile Virtual Network Enabler), and other virtual mobile communication operators and virtual mobile communication service providers.
　また、図1では、PDNとDNが同一である場合が記載されているが、異なっていても良い。PDNは、UEに通信サービスを提供するDN(Data Network)であってよい。尚、DNは、パケットデータサービス網として構成されてもよいし、サービス毎に構成されてもよい。さらに、PDNは、接続された通信端末を含んでもよい。従って、PDNと接続する事は、PDNに配置された通信端末やサーバ装置と接続する事であってもよい。さらに、PDNとの間でユーザデータを送受信する事は、PDNに配置された通信端末やサーバ装置とユーザデータを送受信する事であってもよい。尚、PDNのことをDNと表現してもよいし、DNのことをPDNと表現してもよい。 Also, in Fig. 1, the case where PDN and DN are the same is described, but they may be different. The PDN may be a DN (Data Network) that provides a communication service to the UE. The DN may be configured as a packet data service network or may be configured for each service. Further, the PDN may include a connected communication terminal. Therefore, connecting to the PDN may be connecting to a communication terminal or server device arranged in the PDN. Further, sending and receiving user data to and from the PDN may be sending and receiving user data to and from a communication terminal or server device arranged in the PDN. Note that PDN may be expressed as DN, and DN may be expressed as PDN.
　また、以下では、アクセスネットワーク_A、コアネットワーク_A、PDN、アクセスネットワーク_B、コアネットワーク_B、DNの少なくとも一部、及び/又はこれらに含まれる1以上の装置を、ネットワーク又はネットワーク装置と呼称する場合がある。つまり、ネットワーク及び/又はネットワーク装置が、メッセージを送受信する、及び/又は手続きを実行するということは、アクセスネットワーク_A、コアネットワーク_A、PDN、アクセスネットワーク_B、コアネットワーク_B、DNの少なくとも一部、及び/又はこれらに含まれる1以上の装置が、メッセージを送受信する、及び/又は手続きを実行することを意味する。 In the following, access network_A, core network_A, PDN, access network_B, core network_B, at least a part of DN, and / or one or more devices included in these are referred to as a network or network device. May be called. That is, the fact that the network and / or the network device sends and receives messages and / or executes the procedure means that the access network_A, core network_A, PDN, access network_B, core network_B, and DN are used. It means that at least a part and / or one or more devices contained therein send / receive messages and / or perform procedures.
　また、UEは、アクセスネットワークに接続することができる。また、UEは、アクセスネットワークを介して、コアネットワークと接続する事ができる。さらに、UEは、アクセスネットワーク及びコアネットワークを介して、PDN又はDNに接続する事ができる。すなわち、UEは、PDN又はDNとの間で、ユーザデータを送受信(通信)する事ができる。ユーザデータを送受信する際は、IP(Internet Protocol)通信だけでなく、non-IP通信を用いてもよい。 Also, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the PDN or DN via the access network and core network. That is, the UE can send / receive (communicate) user data with the PDN or DN. When sending and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication may be used.
　ここで、IP通信とは、IPを用いたデータ通信の事であり、IPパケットにより、データの送受信が行われる。IPパケットは、IPヘッダとペイロード部で構成される。ペイロード部には、EPSに含まれる装置・機能や、5GSに含まれる装置・機能が送受信するデータが含まれてよい。また、non-IP通信とは、IPを用いないデータ通信の事であり、IPパケットの構造とは異なる形式により、データの送受信が行われる。例えば、non-IP通信は、IPヘッダが付与されていないアプリケーションデータの送受信によって実現されるデータ通信でもよいし、マックヘッダやEthernet(登録商標)フレームヘッダ等の別のヘッダを付与してUEが送受信するユーザデータを送受信してもよい。 Here, IP communication is data communication using IP, and data is transmitted and received by IP packets. An IP packet is composed of an IP header and a payload part. The payload section may include devices / functions included in EPS and data transmitted / received by devices / functions included in 5GS. In addition, non-IP communication is data communication that does not use IP, and data is transmitted and received in a format different from the structure of IP packets. For example, non-IP communication may be data communication realized by sending and receiving application data to which an IP header is not added, or a UE may add another header such as a Mac header or an Ethernet (registered trademark) frame header. User data to be sent and received may be sent and received.
　また、アクセスネットワーク_A、コアネットワーク_A、アクセスネットワーク_B、コアネットワーク_B、PDN_A、DN_Aには、図2に記載されない装置が構成されていてもよい。例えば、コアネットワーク_A及び/又はコアネットワーク_Bには、AUSF(Authentication Server Function)やAAA(Authentication, authorization, and accounting)サーバ(AAA-S)が含まれてもよい。 Further, the access network_A, the core network_A, the access network_B, the core network_B, the PDN_A, and the DN_A may be configured with devices not shown in FIG. For example, the core network_A and / or the core network_B may include an AUSF (Authentication Server Function) or a AAA (Authentication, authorization, and accounting) server (AAA-S).
　ここで、AUSFは、3GPPアクセス及びnon-3GPPアクセスに対する認証機能を備える、コアネットワーク装置である。具体的には、3GPPアクセス及び/又はnon-3GPPアクセスに対する認証の要求をUEから受信し、認証手続きを実行するネットワーク機能部である。 Here, 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 the authentication procedure.
　また、AAAサーバは、AUSFと直接的又は他のネットワーク装置を介して間接的に接続する、認証及び承認及び課金機能を備える、装置である。AAAサーバはコアネットワーク内のネットワーク装置であってもよい。なお、AAAサーバは、コアネットワーク_A及び/又はコアネットワーク_Bに含まれず、PLMNに含まれてもよい。つまり、AAAサーバはコアネットワーク装置であってもよいし、コアネットワークの外にある装置であってよい。例えば、AAAサーバは3rd Partyが管理する、PLMN内のサーバ装置であってもよい。 Also, the AAA server is a device that has authentication, approval, and billing functions that directly or indirectly connects to AUSF via other network devices. The AAA server may be a network device in the core network. The AAA server may not be included in the core network_A and / or the core network_B, but may be included in the PLMN. That is, 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 in PLMN managed by 3rd Party.
　なお、図2では、図の簡略化のため、各装置・機能は1つずつ記載したが、移動通信システム1には複数の同様の装置・機能が構成されてもよい。具体的には、移動通信システム1には複数のUE_A10、E-UTRAN80、MME40、SGW35、PGW-U30、PGW-C32、PCRF60、HSS50、5G AN120、AMF140、UPF130、SMF132、PCF160、及び/又はUDM150等の装置・機能が構成されていてもよい。 Although each device / function is described one by one in FIG. 2 for the sake of simplification of the figure, a plurality of similar devices / functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 has multiple UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5GAN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150. Devices / functions such as the above may be configured.
　[2. 各装置の構成]
　次に、各実施形態で使用される各装置(UE、及び/又はアクセスネットワーク装置、及び/又はコアネットワーク装置)の構成について、図を用いて説明する。尚、各装置は、物理的なハードウェアとして構成されても良いし、汎用的なハードウェア上に構成された論理的な(仮想的な)ハードウェアとして構成されても良いし、ソフトウェアとして構成されても良い。また、各装置の持つ機能の少なくとも一部(全部を含む)が、物理的なハードウェア、論理的なハードウェア、ソフトウェアとして構成されても良い。 [2. Configuration of each device]
Next, the configuration of each device (UE and / or access network device and / or core network device) used in each embodiment will be described with reference to the drawings. Each device may be configured as physical hardware, may be configured as logical (virtual) hardware configured on general-purpose hardware, or may be configured as software. May be done. Further, at least a part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.
　尚、以下で登場する各装置・機能内の各記憶部(記憶部_A340、記憶部_A440、記憶部_B540、記憶部_A640、記憶部_B740)は、例えば、半導体メモリ、SSD(Solid State Drive)、HDD(Hard Disk Drive)等で構成されている。また、各記憶部は、出荷段階からもともと設定されていた情報だけでなく、自装置・機能以外の装置・機能(例えば、UE、及び/又はアクセスネットワーク装置、及び/又はコアネットワーク装置、及び/又はPDN、及び/又はDN)との間で、送受信した各種の情報を記憶する事ができる。また、各記憶部は、後述する各種の通信手続き内で送受信する制御メッセージに含まれる識別情報、制御情報、フラグ、パラメータ等を記憶することができる。また、各記憶部は、これらの情報をUE毎に記憶してもよい。また、各記憶部は、5GSとEPSとの間のインターワークをした場合には、5GS及び/又はEPS内に含まれる装置・機能との間で送受信した制御メッセージやユーザデータを記憶することができる。このとき、N26インターフェースを介して送受信されたものだけでなく、N26インターフェースを介さずに送受信されたものも記憶することができる。 In addition, each storage unit (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) in each device / function appearing below may be, for example, a semiconductor memory or SSD (semiconductor memory unit). It consists of Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each storage unit has not only the information originally set from the shipping stage, but also devices / functions other than its own device / function (for example, UE and / or access network device, and / or core network device, and /. Or, various information transmitted / received to / from PDN and / or DN) can be stored. In addition, each storage unit can store identification information, control information, flags, parameters, and the like included in control messages transmitted and received in various communication procedures described later. Further, each storage unit may store such information for each UE. In addition, each storage unit may store control messages and user data transmitted / received between 5GS and / or the devices / functions included in EPS when an interwork is performed between 5GS and EPS. can. At this time, not only those transmitted / received via the N26 interface but also those transmitted / received without the N26 interface can be stored.
　[2.1. UEの装置構成]
　まず、UE(User Equipment)の装置構成例について、図3を用いて説明する。UEは、制御部_A300、アンテナ310、送受信部_A320、記憶部_A340で構成されている。制御部_A300、送受信部_A320、記憶部_A340は、バスを介して接続されている。送受信部_A320は、アンテナ310と接続している。 [2.1. UE device configuration]
First, an example of a UE (User Equipment) device configuration will be described with reference to FIG. The UE is composed of a control unit_A300, an antenna 310, a transmission / reception unit_A320, and a storage unit_A340. The control unit_A300, the transmission / reception unit_A320, and the storage unit_A340 are connected via a bus. The transmitter / receiver_A320 is connected to the antenna 310.
　制御部_A300は、UE全体の動作・機能を制御する機能部である。制御部_A300は、必要に応じて、記憶部_A340に記憶されている各種プログラムを読み出して実行する事により、UEにおける各種の処理を実現する。 Control unit_A300 is a functional unit that controls the operation and functions of the entire UE. The control unit_A300 realizes various processes in the UE by reading and executing various programs stored in the storage unit_A340 as needed.
　送受信部_A320は、アンテナを介して、アクセスネットワーク内の基地局装置(eNB又はgNB)と無線通信する為の機能部である。すなわち、UEは、送受信部_A320を用いて、アクセスネットワーク装置、及び/又はコアネットワーク装置、及び/又はPDN、及び/又はDNとの間で、ユーザデータ及び/又は制御情報を送受信することができる。 The transmission / reception unit_A320 is a functional unit for wireless communication with the base station device (eNB or gNB) in the access network via the antenna. That is, the UE may send 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 transmission / reception unit_A320. can.
　図2を参照して詳細に説明すると、UEは、送受信部_A320を用いることにより、LTE-Uuインターフェースを介して、E-UTRAN内の基地局装置(eNB)と通信することができる。また、UEは、送受信部_A320を用いることにより、5G AN内の基地局装置(gNB)と通信することができる。また、UEは、送受信部_A320を用いることにより、N1インターフェースを介してAMFとNAS(Non-Access-Stratum)メッセージの送受信をすることができる。ただし、N1インターフェースは論理的なものであるため、実際には、UEとAMFの間の通信は、5G ANを介して行われる。 Explaining in detail with reference to FIG. 2, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transmission / reception unit_A320. In addition, the UE can communicate with the base station device (gNB) in the 5GAN by using the transmission / reception unit_A320. In addition, the UE can send and receive NAS (Non-Access-Stratum) messages to and from the AMF via the N1 interface by using the transmitter / receiver _A320. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN.
　記憶部_A340は、UEの各動作に必要なプログラム、ユーザデータ、制御情報等を記憶する為の機能部である。 The storage unit_A340 is a functional unit for storing programs, user data, control information, etc. required for each operation of the UE.
　[2.2. gNBの装置構成]
　次に、gNBの装置構成例について、図4を用いて説明する。gNB は、制御部_B500、アンテナ510、ネットワーク接続部_B520、送受信部_B530、記憶部_B540で構成されている。制御部_B500、ネットワーク接続部_B520、送受信部_B530、記憶部_B540は、バスを介して接続されている。送受信部_B530は、アンテナ510と接続している。 [2.2. Equipment configuration of gNB]
Next, an example of the device configuration of gNB will be described with reference to FIG. The gNB is composed of a control unit_B500, an antenna 510, a network connection unit_B520, a transmission / reception 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 transmitter / receiver_B530 is connected to the antenna 510.
　制御部_B500は、gNB全体の動作・機能を制御する機能部である。制御部_B500は、必要に応じて、記憶部_B540に記憶されている各種プログラムを読み出して実行する事により、gNBにおける各種の処理を実現する。 Control unit_B500 is a functional unit that controls the operation and function of the entire gNB. The control unit_B500 realizes various processes in gNB by reading and executing various programs stored in the storage unit_B540 as needed.
　ネットワーク接続部_B520は、gNBが、AMF及び/又はUPFと通信する為の機能部である。すなわち、gNBは、ネットワーク接続部_B520を用いて、AMF及び/又はUPFとの間で、ユーザデータ及び/又は制御情報を送受信することができる。 The network connection part_B520 is a functional part 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 the UPF using the network connection unit_B520.
　送受信部_B530は、アンテナ510を介して、UEと無線通信する為の機能部である。すなわち、gNBは、送受信部_B530を用いて、UEとの間で、ユーザデータ及び/又は制御情報を送受信することができる。 The transmission / reception unit_B530 is a functional unit for wireless communication with the UE via the antenna 510. That is, the gNB can transmit / receive user data and / or control information to / from the UE by using the transmission / reception unit_B530.
　図2を参照して詳細に説明すると、5G AN内にあるgNBは、ネットワーク接続部_B520を用いることにより、N2インターフェースを介して、AMFと通信することができ、N3インターフェースを介して、UPFと通信することができる。また、gNBは、送受信部_B530を用いることにより、UEと通信することができる。 To explain in detail with reference to FIG. 2, gNB in 5GAN can communicate with AMF via the N2 interface by using the network connection part_B520, and UPF via the N3 interface. Can communicate with. Further, the gNB can communicate with the UE by using the transmission / reception unit_B530.
　記憶部_B540は、gNBの各動作に必要なプログラム、ユーザデータ、制御情報等を記憶する為の機能部である。 The storage unit_B540 is a functional unit for storing programs, user data, control information, etc. required for each operation of gNB.
　[2.3. AMFの装置構成]
　次に、AMFの装置構成例について、図5を用いて説明する。AMFは、制御部_B700、ネットワーク接続部_B720、記憶部_B740で構成されている。制御部_B700、ネットワーク接続部_B720、記憶部_B740は、バスを介して接続されている。AMFは、制御プレーンを扱うノードであってよい。 [2.3. AMF equipment configuration]
Next, an example of the AMF device configuration will be described with reference to FIG. The AMF consists 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 AMF may be a node that handles the control plane.
　制御部_B700は、AMF全体の動作・機能を制御する機能部である。制御部_B700は、必要に応じて、記憶部_B740に記憶されている各種プログラムを読み出して実行する事により、AMFにおける各種の処理を実現する。 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 AMF by reading and executing various programs stored in the storage unit_B740 as needed.
　ネットワーク接続部_B720は、AMFが、5G AN内の基地局装置(gNB)、及び/又はSMF、及び/又はPCF、及び/又はUDM、及び/又はSCEFと接続する為の機能部である。すなわち、AMFは、ネットワーク接続部_B720を用いて、5G AN内の基地局装置(gNB)、及び/又はSMF、及び/又はPCF、及び/又はUDM、及び/又はSCEFとの間で、ユーザデータ及び/又は制御情報を送受信することができる。 The network connection unit_B720 is a functional unit for AMF to connect to the base station equipment (gNB) in 5GAN and / or SMF, and / or PCF, and / or UDM, and / or SCEF. That is, the AMF uses the network connection _B720 to the user between the base station equipment (gNB) in 5GAN 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.
　図2を参照して詳細に説明すると、5GCN内にあるAMFは、ネットワーク接続部_A620を用いることにより、N2インターフェースを介して、gNBと通信することができ、N8インターフェースを介して、UDMと通信することができ、N11インターフェースを介して、SMFと通信することができ、N15インターフェースを介して、PCFと通信することができる。また、AMFは、ネットワーク接続部_A620を用いることにより、N1インターフェースを介して、UEとNASメッセージの送受信をすることができる。ただし、N1インターフェースは論理的なものであるため、実際には、UEとAMFの間の通信は、5G ANを介して行われる。また、AMFは、N26インターフェースをサポートする場合、ネットワーク接続部_A620を用いることにより、N26インターフェースを介して、MMEと通信することができる。 More specifically with reference to Figure 2, the AMF within the 5GCN can communicate with the gNB via the N2 interface by using the network connection _A620 and with the UDM via the N8 interface. It can communicate, it can communicate with the SMF via the N11 interface, and it can communicate with the PCF via the N15 interface. In addition, AMF can send and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN. In addition, when the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit_A620.
　記憶部_B740は、AMFの各動作に必要なプログラム、ユーザデータ、制御情報等を記憶する為の機能部である。 The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of AMF.
　尚、AMFは、N2インターフェースを用いたRANとの制御メッセージを交換する機能、N1インターフェースを用いたUEとのNASメッセージを交換する機能、NASメッセージの暗号化及び完全性保護を行う機能、登録管理(Registration management; RM)機能、接続管理(Connection management; CM)機能、到達可能性管理(Reachability management)機能、UE等の移動性管理(Mobility management)機能、UEとSMF間のSM(Session Management)メッセージを転送する機能、アクセス認証(Access Authentication、Access Authorization)機能、セキュリティアンカー機能(SEA; Security Anchor Functionality)、セキュリティコンテキスト管理(SCM; Security Context Management)機能、N3IWF(Non-3GPP Interworking Function)に対するN2インターフェースをサポートする機能、N3IWFを介したUEとのNAS信号の送受信をサポートする機能、N3IWFを介して接続するUEの認証する機能等を有する。 AMF has a function to exchange control messages with RAN using N2 interface, a function to exchange NAS messages with UE using N1 interface, a function to encrypt and protect the integrity of NAS messages, and registration management. (Registration management; RM) function, connection management (CM) function, reachability management (Reachability management) function, mobility management (Mobility management) function such as UE, SM (Session Management) between UE and SMF N2 for message forwarding function, access authentication (Access Authorization, Access Authorization) function, security anchor function (SEA; Security Anchor Functionality), security context management (SCM; Security Context Management) function, N3IWF (Non-3GPP Interworking Function) It has a function to support an interface, a function to support transmission / reception of NAS signals with a UE via N3IWF, a function to authenticate a UE connected via N3IWF, and the like.
　また、登録管理では、UEごとのRM状態が管理される。RM状態は、UEとAMFとの間で同期がとられていてもよい。RM状態としては、非登録状態(RM-DEREGISTERED state)と、登録状態(RM-REGISTERED state)がある。RM-DEREGISTERED状態では、UEはネットワークに登録されていないため、AMFにおけるUEコンテキストが、そのUEに対する有効な位置情報やルーティング情報を持っていない為、AMFはUEに到達できない状態である。また、RM-REGISTERED状態では、UEはネットワークに登録されているため、UEはネットワークとの登録が必要なサービスを受信することができる。尚、RM状態は、5GMM状態(5GMM state)と表現されてもよい。この場合、RM-DEREGISTERED状態は、5GMM-DEREGISTERED状態と表現されてもよいし、RM-REGISTERED状態は、5GMM-REGISTERED状態と表現されてもよい。 Also, in registration management, the RM status for each UE is managed. The RM state may be synchronized between the UE and 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. Also, in the RM-REGISTERED state, the UE is registered in the network, so the UE can receive services that require registration with the network. The RM state may be expressed as a 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state.
　言い換えると、5GMM-REGISTEREDは、各装置が、5GMMコンテキストを確立した状態であってもよいし、PDUセッションコンテキストを確立した状態であってもよい。尚、各装置が5GMM-REGISTEREDである場合、UE_A10は、ユーザデータや制御メッセージの送受信を開始してもよいし、ページングに対して応答してもよい。さらに、尚、各装置が5GMM-REGISTEREDである場合、UE_A10は、初期登録のための登録手続き以外の登録手続き、及び/又はサービス要求手続きを実行してもよい。 In other words, 5GMM-REGISTERED may be in a state where each device has established a 5GMM context or a state in which a PDU session context has been established. When each device is 5GMM-REGISTERED, UE_A10 may start sending and receiving user data and control messages, or may respond to paging. Further, when each device is 5GMM-REGISTERED, UE_A10 may execute a registration procedure other than the registration procedure for initial registration and / or a service request procedure.
　さらに、5GMM-DEREGISTEREDは、各装置が、5GMMコンテキストを確立していない状態であってもよいし、UE_A10の位置情報がネットワークに把握されていない状態であってもよいし、ネットワークがUE_A10に到達不能である状態であってもよい。尚、各装置が5GMM-DEREGISTEREDである場合、UE_A10は、登録手続きを開始してもよいし、登録手続きを実行することで5GMMコンテキストを確立してもよい。 Furthermore, in 5GMM-DEREGISTERED, each device may be in a state where the 5GMM context has not been established, the location information of UE_A10 may not be known to the network, or the network reaches UE_A10. It may be in an impossible state. If each device is 5GMM-DEREGISTERED, UE_A10 may start the registration procedure or establish a 5GMM context by executing the registration procedure.
　また、接続管理では、UEごとのCM状態が管理される。CM状態は、UEとAMFとの間で同期がとられていてもよい。CM状態としては、非接続状態(CM-IDLE state)と、接続状態(CM-CONNECTED state)がある。CM-IDLE状態では、UEはRM-REGISTERED状態にあるが、N1インターフェースを介したAMFとの間で確立されるNASシグナリング接続(NAS signaling connection)を持っていない。また、CM-IDLE状態では、UEはN2インターフェースの接続(N2 connection)、及びN3インターフェースの接続(N3 connection)を持っていない。一方、CM-CONNECTED状態では、N1インターフェースを介したAMFとの間で確立されるNASシグナリング接続(NAS signaling connection)を持っている。また、CM-CONNECTED状態では、UEはN2インターフェースの接続(N2 connection)、及び/又はN3インターフェースの接続(N3 connection)を持っていてもよい。 Also, in connection management, the CM status for each UE is managed. The CM state may be synchronized between the UE and AMF. The CM state includes a non-connected 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. Also, 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. Further, in the CM-CONNECTED state, the UE may have an N2 interface connection (N2 connection) and / or an N3 interface connection (N3 connection).
　さらに、接続管理では、3GPPアクセスにおけるCM状態と、non-3GPPアクセスにおけるCM状態とで分けて管理されてもよい。この場合、3GPPアクセスにおけるCM状態としては、3GPPアクセスにおける非接続状態(CM-IDLE state over 3GPP access)と、3GPPアクセスにおける接続状態(CM-CONNECTED state over 3GPP access)とがあってよい。さらに、non-3GPPアクセスにおけるCM状態としては、non-3GPPアクセスにおける非接続状態(CM-IDLE state over non-3GPP access)と、non-3GPPアクセスにおける接続状態(CM-CONNECTED state over non-3GPP access)とがあってよい。尚、非接続状態はアイドルモード表現されてもよく、接続状態モードはコネクテッドモードと表現されてもよい。 Furthermore, in connection management, the CM state in 3GPP access and the CM state in non-3GPP access may be managed separately. In this case, the CM state in 3GPP access may be a non-connected 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 state in non-3GPP access includes the non-connected state (CM-IDLE state over non-3GPP access) in non-3GPP access and the connection state (CM-CONNECTED state over non-3GPP access) in non-3GPP access. ) And so on. The disconnected state may be expressed as an idle mode, and the connected state mode may be expressed as a connected mode.
　尚、CM状態は、5GMMモード(5GMM mode)と表現されてもよい。この場合、非接続状態は、5GMM非接続モード(5GMM-IDLE mode)と表現されてもよいし、接続状態は、5GMM接続モード(5GMM-CONNECTED mode)と表現されてもよい。さらに、3GPPアクセスにおける非接続状態は、3GPPアクセスにおける5GMM非接続モード(5GMM-IDLE mode over 3GPP access)と表現されてもよいし、3GPPアクセスにおける接続状態は、3GPPアクセスにおける5GMM接続モード(5GMM-CONNECTED mode over 3GPP access)と表現されてもよい。さらに、non-3GPPアクセスにおける非接続状態は、non-3GPPアクセスにおける5GMM非接続モード(5GMM-IDLE mode over non-3GPP access)と表現されてもよいし、non-3GPPアクセスにおける接続状態は、non-3GPPアクセスにおける5GMM接続モード(5GMM-CONNECTED mode over non-3GPP access)と表現されてもよい。尚、5GMM非接続モードはアイドルモード表現されてもよく、5GMM接続モードはコネクテッドモードと表現されてもよい。 The CM state may be expressed as 5GMM mode (5GMM mode). In this case, the non-connected state may be expressed as 5GMM non-connected mode (5GMM-IDLE mode), and the connected state may be expressed as 5GMM connected mode (5GMM-CONNECTED mode). Further, the non-connected state in 3GPP access may be expressed as 5GMM non-connected mode (5GMM-IDLE mode over 3GPP access) in 3GPP access, and the connected state in 3GPP access may be expressed as 5GMM connection mode (5GMM-) in 3GPP access. It may be expressed as CONNECTED mode over 3GPP access). Further, the non-connected state in non-3GPP access may be expressed as 5GMM non-connected mode (5GMM-IDLE mode over non-3GPP access) in non-3GPP access, and the connected state in non-3GPP access is non. -3GPP access may be expressed as 5GMM connection mode (5GMM-CONNECTED mode over non-3GPP access). The 5GMM non-connection mode may be expressed as an idle mode, and the 5GMM connection mode may be expressed as a connected mode.
　また、AMFは、コアネットワーク_B内に1以上配置されてもよい。また、AMFは、1以上のNSI(Network Slice Instance)を管理するNFでもよい。また、AMFは、複数のNSI間で共有される共有CPファンクション(CCNF; Common CPNF(Control Plane Network Function))でもよい。 Also, one or more AMFs may be placed in the core network_B. In addition, AMF may be an NF that manages one or more NSIs (Network Slice Instances). Further, the AMF may be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among a plurality of NSIs.
　尚、N3IWFは、UEが5GSに対してnon-3GPPアクセスを介して接続する場合に、non-3GPPアクセスと5GCNとの間に配置される装置及び/又は機能である。 Note that N3IWF is a device and / or function that is placed between non-3GPP access and 5GCN when the UE connects to 5GS via non-3GPP access.
　[2.4. SMFの装置構成]
　次に、SMFの装置構成例について、図5を用いて説明する。SMFは、制御部_B700、ネットワーク接続部_B720、記憶部_B740で構成されている。制御部_B700、ネットワーク接続部_B720、記憶部_B740は、バスを介して接続されている。SMFは、制御プレーンを扱うノードであってよい。 [2.4. SMF device configuration]
Next, an example of the SMF device configuration will be described with reference to FIG. The SMF consists 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.
　制御部_B700は、SMF全体の動作・機能を制御する機能部である。制御部_B700は、必要に応じて、記憶部_B740に記憶されている各種プログラムを読み出して実行する事により、SMFにおける各種の処理を実現する。 Control unit_B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit_B700 realizes various processes in the SMF by reading and executing various programs stored in the storage unit_B740 as needed.
　ネットワーク接続部_B720は、SMFが、AMF、及び/又はUPF、及び/又はPCF、及び/又はUDMと接続する為の機能部である。すなわち、SMFは、ネットワーク接続部_B720を用いて、AMF、及び/又はUPF、及び/又はPCF、及び/又はUDMとの間で、ユーザデータ及び/又は制御情報を送受信することができる。 The network connection part_B720 is a functional part 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 between the AMF and / or the UPF, and / or the PCF, and / or the UDM by using the network connection unit_B720.
　図2を参照して詳細に説明すると、5GCN内にあるSMFは、ネットワーク接続部_A620を用いることにより、N11インターフェースを介して、AMFと通信することができ、N4インターフェースを介して、UPFと通信することができ、N7インターフェースを介して、PCFと通信することができ、N10インターフェースを介して、UDMと通信することができる。 More specifically with reference to Figure 2, the SMF within the 5GCN can communicate with the AMF via the N11 interface by using the network connection _A620 and with the UPF via the N4 interface. It can communicate, it can communicate with the PCF via the N7 interface, and it can communicate with the UDM via the N10 interface.
　記憶部_B740は、SMFの各動作に必要なプログラム、ユーザデータ、制御情報等を記憶する為の機能部である。 The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of SMF.
　SMFは、PDUセッションの確立・修正・解放等のセッション管理(Session Management)機能、UEに対するIPアドレス割り当て(IP address allocation)及びその管理機能、UPFの選択と制御機能、適切な目的地(送信先)へトラフィックをルーティングする為のUPFの設定機能、NASメッセージのSM部分を送受信する機能、下りリンクのデータが到着したことを通知(Downlink Data Notification)する機能、AMF経由でN2インターフェースを介してANに送信されるAN特有の(ANごとの)SM情報を提供する機能、セッションに対するSSCモード(Session and Service Continuity mode)を決定する機能、ローミング機能等を有する。 SMF has session management functions such as establishment / modification / release of PDU sessions, IP address allocation and management functions for UEs, UPF selection and control functions, and appropriate destinations (destination). ), UPF setting function for routing traffic to), function to send and receive SM part of NAS message, function to notify that downlink data has arrived (Downlink Data Notification), AN via N2 interface via AMF It has a function to provide SM information peculiar to AN (for each AN) transmitted to, a function to determine the SSC mode (Session and Service Continuity mode) for the session, a roaming function, and the like.
　[2.5. UPFの装置構成]
　次に、UPFの装置構成例について、図5を用いて説明する。UPFは、制御部_B700、ネットワーク接続部_B720、記憶部_B740で構成されている。制御部_B700、ネットワーク接続部_B720、記憶部_B740は、バスを介して接続されている。UPFは、制御プレーンを扱うノードであってよい。 [2.5. UPF equipment configuration]
Next, an example of the UPF device configuration will be described with reference to FIG. The UPF consists 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.
　制御部_B700は、UPF全体の動作・機能を制御する機能部である。制御部_B700は、必要に応じて、記憶部_B740に記憶されている各種プログラムを読み出して実行する事により、UPFにおける各種の処理を実現する。 Control unit_B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit_B700 realizes various processes in the UPF by reading and executing various programs stored in the storage unit_B740 as needed.
　ネットワーク接続部_B720は、UPFが、5G AN内の基地局装置(gNB)、及び/又はSMF、及び/又はDNと接続する為の機能部である。すなわち、UPFは、ネットワーク接続部_B720を用いて、5G AN内の基地局装置(gNB)、及び/又はSMF、及び/又はDNとの間で、ユーザデータ及び/又は制御情報を送受信することができる。 The network connection unit_B720 is a functional unit for the UPF to connect to the base station device (gNB) in 5GAN and / or the SMF and / or the DN. That is, the UPF uses the network connection _B720 to send and receive user data and / or control information between the base station equipment (gNB) in 5GAN and / or the SMF and / or the DN. Can be done.
　図2を参照して詳細に説明すると、5GCN内にあるUPFは、ネットワーク接続部_A620を用いることにより、N3インターフェースを介して、gNBと通信することができ、N4インターフェースを介して、SMFと通信することができ、N6インターフェースを介して、DNと通信することができ、N9インターフェースを介して、他のUPFと通信することができる。 More specifically with reference to Figure 2, the UPF within the 5GCN can communicate with the gNB via the N3 interface by using the network connection _A620 and with the SMF via the N4 interface. It can communicate, it can communicate with the DN via the N6 interface, and it can communicate with other UPFs via the N9 interface.
　記憶部_B740は、UPFの各動作に必要なプログラム、ユーザデータ、制御情報等を記憶する為の機能部である。 The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of UPF.
　UPFは、intra-RAT mobility又はinter-RAT mobilityに対するアンカーポイントとしての機能、DNに相互接続するための外部PDUセッションポイントとしての機能(つまり、DNとコアネットワーク_Bとの間のゲートウェイとして、ユーザデータを転送する機能)、パケットのルーティング及び転送する機能、1つのDNに対して複数のトラフィックフローのルーティングをサポートするUL CL(Uplink Classifier)機能、マルチホーム(multi-homed)PDUセッションをサポートするBranching point機能、user planeに対するQoS (Quality of Service) 処理機能、上りリンクトラフィックの検証機能、下りリンクパケットのバッファリング、下りリンクデータ通知(Downlink Data Notification)をトリガする機能等を有する。 The UPF acts as an anchor point for intra-RAT mobility or inter-RAT mobility, as an external PDU session point for interconnecting the DN (ie, as a gateway between the DN and the core network_B). Data forwarding function), packet routing and forwarding function, ULCL (Uplink Classifier) function that supports routing of multiple traffic flows to one DN, and multi-homed PDU session support. It has a branching point function, a QoS (Quality of Service) processing function for userplane, a function for verifying uplink traffic, a function for buffering downlink packets, and a function for triggering downlink data notification (Downlink Data Notification).
　また、UPFは、IP通信及び/又はnon-IP通信の為のゲートウェイでもよい。また、UPFは、IP通信を転送する機能を持ってもよく、non-IP通信とIP通信を変換する機能を持っていてもよい。さらに複数配置されるゲートウェイは、コアネットワーク_Bと単一のDNを接続するゲートウェイでもよい。尚、UPFは、他のNFとの接続性を備えてもよく、他のNFを介して各装置に接続してもよい。 The UPF may also be a gateway for IP communication and / or non-IP communication. In addition, the UPF may have a function of transferring IP communication, or may have a function of converting between non-IP communication and IP communication. Further, the multiple gateways may be a gateway connecting the core network_B and a single DN. The UPF may have connectivity with other NFs, or may be connected to each device via other NFs.
　尚、ユーザプレーン(user plane)は、UEとネットワークとの間で送受信されるユーザデータ(user data)のことである。ユーザプレーンは、PDNコネクション、又はPDUセッションを用いて送受信されてもよい。さらに、EPSの場合、ユーザプレーンは、LTE-Uuインターフェース、及び/又はS1-Uインターフェース、及び/又はS5インターフェース、及び/又はS8インターフェース、及び/又はSGiインターフェースを用いて送受信されてもよい。さらに、5GSの場合、ユーザプレーンは、UEとNG RANとの間のインターフェース、及び/又はN3インターフェース、及び/又はN9インターフェース、及び/又はN6インターフェースを介して送受信されてもよい。以下、ユーザプレーンは、U-Planeと表現されてもよい。 Note that the user plane is user data transmitted and received between the UE and the network. The user plane may be transmitted and received using a PDN connection or a PDU session. Further, 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. Further, in the case of 5GS, the user plane may be transmitted and received via the interface between the UE and 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 a U-Plane.
　さらに、制御プレーン(control plane)は、UEの通信制御等を行うために送受信される制御メッセージのことである。制御プレーンは、UEとMMEとの間のNAS (Non-Access-Stratum)シグナリングコネクションを用いて送受信されてもよい。さらに、EPSの場合、制御プレーンは、LTE-Uuインターフェース、及びS1-MMEインターフェースを用いて送受信されてもよい。さらに、5GSの場合、制御プレーンは、UEとNG RANとの間のインターフェース、及びN2インターフェースを用いて送受信されてもよい。以下、制御プレーンは、コントロールプレーンと表現されてもよいし、C-Planeと表現されてもよい。 Furthermore, the control plane is a control message sent and received to control the 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. Further, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Further, in the case of 5GS, the control plane may be transmitted / received using the interface between the UE and NG RAN and the N2 interface. Hereinafter, the control plane may be expressed as a control plane or a C-Plane.
　さらに、U-Plane(User Plane; UP)は、ユーザデータを送受信する為の通信路でもよく、複数のベアラで構成されてもよい。さらに、C-Plane(Control Plane; CP)は、制御メッセージを送受信する為の通信路でもよく、複数のベアラで構成されてもよい。 Further, the U-Plane (User Plane; UP) may be a communication path for transmitting and receiving user data, and may be composed of a plurality of bearers. Further, 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. PCFの装置構成]
　次に、各実施形態で使用されるPCFの装置構成例について、図5を用いて説明する。PCFは、制御部_700、ネットワーク接続部_720、記憶部_740で構成されている。制御部_700、ネットワーク接続部_720、記憶部_740は、バスを介して接続されている。 [2.6. PCF device configuration]
Next, an example of the device configuration of the PCF used in each embodiment will be described with reference to FIG. The PCF consists of a control unit_700, a network connection unit_720, and a storage unit_740. The control unit_700, network connection unit_720, and storage unit_740 are connected via a bus.
　制御部_700は、PCF全体の動作・機能を制御する機能部である。尚、制御部_700は、PCFにおける他の機能部(ネットワーク接続部_720、記憶部_740)が有さない全ての機能を処理してもよい。制御部_700は、必要に応じて、記憶部_740に記憶されている各種プログラムを読み出して実行する事により、PCFにおける各種の処理を実現する。 Control unit_700 is a functional unit that controls the operation and functions of the entire PCF. The control unit_700 may process all the functions that the other functional units (network connection unit_720, storage unit_740) in the PCF do not have. The control unit _700 realizes various processes in the PCF by reading and executing various programs stored in the storage unit _740 as needed.
　ネットワーク接続部_720は、PCFが、AMF、及び/又はSMF、及び/又はAF(Application Function)と接続する為の機能部である。すなわち、PCFは、ネットワーク接続部_720を用いて、AMF、及び/又はSMF、及び/又はAFとの間で、制御情報を送受信することができる。 The network connection part_720 is a functional part for the PCF to connect with AMF and / or SMF and / or AF (Application Function). That is, the PCF can send and receive control information to and from the AMF and / or the SMF and / or the AF by using the network connection unit_720.
　PCFは、ネットワーク接続部_720を用いることにより、N15インターフェースを介して、AMFと通信することができ、N7インターフェースを介して、SMFと通信することができ、N5インターフェース(PCFとAF間のインターフェース)を介して、AFと通信することができる。 The PCF can communicate with the AMF via the N15 interface and with the SMF via the N7 interface by using the network connection _720, and can communicate with the N5 interface (interface between PCF and AF). ) Can communicate with AF.
　記憶部_740は、UPFの各動作に必要なプログラム、ユーザデータ、制御情報等を記憶する為の機能部である。 The storage unit_740 is a functional unit for storing programs, user data, control information, etc. required for each operation of UPF.
　尚、PCFは、統一されたポリシーフレームワークをサポートする機能、それらを強制するために制御機能(control plane function)に対してポリシールールを提供する機能、登録情報(subscription information)にアクセスする機能などを有している。また、PCFは、URSP(UE Route Selection Policy)ルール等を生成する機能も有している。これらの機能は、全て制御部_700によって制御されてよい。 In addition, PCF has a function to support a unified policy framework, a function to provide policy rules to the control function (control plane function) to enforce them, a function to access registration information (subscription information), etc. have. The PCF also has a function to generate URSP (UERoute Selection Policy) rules and the like. All of these functions may be controlled by the control unit_700.
　[2.7. 本実施形態における技術用語及び識別情報の説明]
　次に、本実施形態において使用する技術用語について説明する。 [2.7. Explanation of technical terms and identification information in this embodiment]
Next, the technical terms used in the present embodiment will be described.
　ネットワークとは、アクセスネットワーク_B、コアネットワーク_B、DNのうち、少なくとも一部を指す。また、アクセスネットワーク_B、コアネットワーク_B、DNのうち、少なくとも一部に含まれる1以上の装置を、ネットワーク又はネットワーク装置と称してもよい。つまり、ネットワークがメッセージの送受信及び/又は処理を実行するということは、ネットワーク内の装置(ネットワーク装置、及び/又は制御装置)がメッセージの送受信及び/又は処理を実行することを意味してもよい。逆に、ネットワーク内の装置がメッセージの送受信及び/又は処理を実行するということは、ネットワークがメッセージの送受信及び/又は処理を実行することを意味してもよい。 The network refers to at least a part of the access network_B, core network_B, and DN. Further, one or more devices included in at least a part of the access network_B, the core network_B, and the DN may be referred to as a network or a network device. That is, the fact that the network performs transmission / reception and / or processing of messages may mean that devices (network devices and / or control devices) in the network execute message transmission / reception and / or processing. .. Conversely, the fact that a device in the network performs transmission / reception and / or processing of a message may mean that the network executes transmission / reception and / or processing of a message.
　また、SM(セッションマネジメント)メッセージ(NAS (Non-Access-Stratum) SMメッセージとも称する)は、SMのための手続き(以下、SM手続きとも呼称する)で用いられるNASメッセージであってよく、AMF_A240を介してUE_A10とSMF_A230の間で送受信される制御メッセージであってよい。さらに、SMメッセージには、PDUセッション確立要求(PDU session establishment request)メッセージ、PDUセッション確立受諾(PDU session establishment accept)メッセージ、PDUセッション拒絶(PDU session establishment reject)メッセージ、PDUセッション変更要求(PDU session modification request)メッセージ、PDUセッション変更コマンド(PDU session modification command)メッセージ、PDUセッション変更完了メッセージ(PDU session modification complete)、PDUセッション変更コマンド拒絶(PDU session modification command reject)メッセージ、PDUセッション変更拒絶(PDU session modification reject)メッセージ、PDUセッション解放要求(PDU session release request)メッセージ、PDUセッション解放拒絶(PDU session release reject)メッセージ、PDUセッション解放コマンド(PDU session release command)メッセージ、PDUセッション解放完了(PDU session release complete)メッセージ等が含まれてもよい。 The SM (session management) message (also referred to as NAS (Non-Access-Stratum) SM message) may be a NAS message used in a procedure for SM (hereinafter, also referred to as SM procedure), and AMF_A240 may be used. It may be a control message sent and received between UE_A10 and SMF_A230 via. Further, the SM message includes a PDU session establishment request message, a PDU session establishment acceptance message, a PDU session establishment reject message, and a PDU session modification request (PDU session modification). request) message, PDU session modification command (PDU session modification command) message, PDU session modification completion message (PDU session modification complete), PDU session change command rejection (PDU session modification command reject) message, PDU session modification rejection (PDU session modification) reject message, PDU session release request message, PDU session release reject message, PDU session release command message, PDU session release complete (PDU session release complete) A message or the like may be included.
　また、SMのための手続きには、PDUセッション確立手続き(PDU session establishment procedure)、PDUセッション変更手続き(PDU session modification procedure)、PDUセッション解放手続き(UE-requested PDU session release procedure)が含まれてもよい。なお、各手続きは、UEから開始される手続きであってもよいし、NWから開始される手続きであってもよい。 In addition, even if the procedure for SM includes a PDU session establishment procedure (PDU session establishment procedure), a PDU session modification procedure (PDU session modification procedure), and a PDU session release procedure (UE-requested PDU session release procedure). good. In addition, each procedure may be a procedure started from UE or a procedure started from NW.
　また、MM(Mobility management)メッセージ(NAS MMメッセージとも称する)は、MMのための手続きに用いられるNASメッセージであってよく、UE_A10とAMF_A240の間で送受信される制御メッセージであってよい。さらに、MMメッセージには、登録要求(Registration request)メッセージ、登録受諾(Registration accept)メッセージ、登録拒絶(Registration reject)メッセージ、非登録要求(De-registration request)メッセージ、非登録受諾(De-registration accept)メッセージ、設定更新コマンド(configuration update command)メッセージ、設定更新完了(configuration update complete)メッセージ、サービス要求(Service request)メッセージ、サービス受諾(Service accept)メッセージ、サービス拒絶(Service reject)メッセージ、通知(Notification)メッセージ、通知応答(Notification response)メッセージ等が含まれてよい。 Further, the MM (Mobility management) message (also referred to as NAS MM message) may be a NAS message used for the procedure for MM, and may be a control message sent / received between UE_A10 and AMF_A240. In addition, the MM messages include Registration request messages, Registration accept messages, Registration reject messages, De-registration request messages, and De-registration accept messages. ) Messages, configuration update command messages, configuration update complete messages, service request messages, service accept messages, service reject messages, notifications ) Messages, Notification response messages, etc. may be included.
　また、MMのための手続き又はMM手続きは、登録手続き(Registration procedure)、非登録手続き(De-registration procedure)、ジェネリックUE設定更新(Generic UE configuration update)手続き、認証・承認手続き、サービス要求手続き(Service request procedure)、ページング手続き(Paging procedure)、通知手続き(Notification procedure)が含まれてよい。 In addition, the procedure for MM or MM procedure is registration procedure (Registration procedure), non-registration procedure (De-registration procedure), generic UE configuration update procedure, authentication / approval procedure, service request procedure ( Service request procedure), paging procedure (Paging procedure), notification procedure (Notification procedure) may be included.
　また、5GS(5G System)サービスは、コアネットワーク_B190を用いて提供される接続サービスでよい。さらに、5GSサービスは、EPSサービスと異なるサービスでもよいし、EPSサービスと同様のサービスでもよい。 Also, the 5GS (5G System) service may be a connection service provided using the core network_B190. Further, the 5GS service may be a service different from the EPS service or a service similar to the EPS service.
　また、non 5GSサービスは、5GSサービス以外のサービスでよく、EPSサービス、及び/又はnon EPSサービスが含まれてもよい。 Further, the non5GS service may be a service other than the 5GS service, and may include an EPS service and / or a non-EPS service.
　また、PDN(Packet Data Network)タイプとは、PDNコネクションのタイプを示すものであり、IPv4、IPv6、IPv4v6、non-IPがある。IPv4が指定された場合、IPv4を用いてデータの送受信を行う事を示す。IPv6が指定された場合は、IPv6を用いてデータの送受信を行う事を示す。IPv4v6が指定された場合は、IPv4又はIPv6を用いてデータの送受信を行う事を示す。non-IPが指定された場合は、IPを用いた通信ではなく、IP以外の通信方法によって通信する事を示す。 The PDN (Packet Data Network) type indicates the type of PDN connection, and includes IPv4, IPv6, IPv4v6, and non-IP. When IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is sent and received using IPv6. When IPv4v6 is specified, it indicates that data is sent and received using IPv4 or IPv6. When non-IP is specified, it indicates that communication is performed by a communication method other than IP, not communication using IP.
　また、PDU(Protocol Data Unit/Packet Data Unit)セッションとは、PDU接続性サービスを提供するDNとUEとの間の関連性として定義することができるが、UEと外部ゲートウェイとの間で確立される接続性であってもよい。UEは、5GSにおいて、アクセスネットワーク_B及びコアネットワーク_Bを介したPDUセッションを確立することにより、PDUセッションを用いて、DNとの間のユーザデータの送受信を行うことができる。ここで、この外部ゲートウェイとは、UPF、SCEF等であってよい。UEは、PDUセッションを用いて、DNに配置されるアプリケーションサーバー等の装置と、ユーザデータの送受信を実行する事ができる。 In addition, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as a relationship between a DN that provides a PDU connectivity service and a UE, but it is established between the UE and an external gateway. It may be connectivity. By establishing a PDU session via the access network_B and the core network_B in 5GS, the UE can send and receive user data to and from the DN using the PDU session. Here, the external gateway may be UPF, SCEF, or the like. The UE can use the PDU session to send and receive user data to and from devices such as application servers located on the DN.
　尚、各装置(UE、及び/又はアクセスネットワーク装置、及び/又はコアネットワーク装置)は、PDUセッションに対して、1以上の識別情報を対応づけて管理してもよい。尚、これらの識別情報には、DNN、QoSルール、PDUセッションタイプ、アプリケーション識別情報、NSI識別情報、アクセスネットワーク識別情報、及びSSC modeのうち1以上が含まれてもよいし、その他の情報がさらに含まれてもよい。さらに、PDUセッションを複数確立する場合には、PDUセッションに対応づけられる各識別情報は、同じ内容でもよいし、異なる内容でもよい。 Note that each device (UE and / or access network device and / or core network device) may manage one or more identification information in association with each PDU session. It should be noted that these identification information may include one or more of DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and other information. It may be further included. Further, when a plurality of PDU sessions are established, the identification information associated with the PDU session may have the same content or different contents.
　また、DNN(Data Network Name)は、コアネットワーク及び/又はDN等の外部ネットワークを識別する識別情報でよい。さらに、DNNは、コアネットワークB190を接続するPGW_A30/UPF_A235等のゲートウェイを選択する情報として用いることもできる。さらに、DNNは、APN(Access Point Name)に相当するものでもよい。 Further, DNN (Data Network Name) may be identification information that identifies the core network and / or the external network such as DN. Furthermore, DNN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 to connect the core network B190. Further, the DNN may correspond to an APN (Access Point Name).
　また、PDU(Protocol Data Unit/Packet Data Unit)セッションタイプは、PDUセッションのタイプを示すものであり、IPv4、IPv6、Ethernet、Unstructuredがある。IPv4が指定された場合、IPv4を用いてデータの送受信を行うことを示す。IPv6が指定された場合は、IPv6を用いてデータの送受信を行うことを示す。Ethernetが指定された場合は、Ethernetフレームの送受信を行うことを示す。また、Ethernetは、IPを用いた通信を行わないことを示してもよい。Unstructuredが指定された場合は、Point-to-Point(P2P)トンネリング技術を用いて、DNにあるアプリケーションサーバー等にデータを送受信することを示す。P2Pトンネリング技術としては、例えば、UDP/IPのカプセル化技術を用いても良い。尚、PDUセッションタイプには、上記の他にIPが含まれても良い。IPは、UEがIPv4とIPv6の両方を使用可能である場合に指定する事ができる。 The PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet, and Unstructured. When IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Further, Ethernet may indicate that communication using IP is not performed. When Unstructured is specified, it indicates that data is sent / received to the application server etc. in the DN by using the point-to-point (P2P) tunneling technology. As the P2P tunneling technique, for example, a UDP / IP encapsulation technique may be used. The PDU session type may include an IP in addition to the above. IP can be specified if the UE can use both IPv4 and IPv6.
　また、PLMN(Public land mobile network)は、移動無線通信サービスを提供する通信ネットワークである。PLMNは、通信事業者であるオペレータが管理するネットワークであり、PLMN IDにより、オペレータを識別することができる。UEのIMSI(International Mobile Subscriber Identity)のMCC(Mobile Country Code)とMNC(Mobile Network Code)と一致するPLMNはHome PLMN(HPLMN)であってよい。さらに、UEは、USIMに1又は複数のEPLMN(Equivalent HPLMN)を識別するための、Equivalent HPLMN listを保持していてもよい。HPLMN、及び/又はEPLMNと異なるPLMNはVPLMN(Visited PLMN)であってよい。UEが登録を成功したPLMNはRPLMN(Registered PLMN)であってよい。 PLMN (Public land mobile network) is a communication network that provides mobile wireless communication services. PLMN is a network managed by an operator who is a telecommunications carrier, and the operator can be identified by the PLMN ID. The PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the IMSI (International Mobile Subscriber Identity) of the UE may be Home PLMN (HPLMN). Further, the UE may have an Equivalent HPLMN list for identifying one or more EPLMNs (Equivalent HPLMNs) in the USIM. The PLMN different from HPLMN and / or EPLMN may be VPLMN (Visited PLMN). The PLMN successfully registered by the UE may be an RPLMN (Registered PLMN).
　また、ネットワークスライス(NS)とは、特定のネットワーク能力及びネットワーク特性を提供する論理的なネットワークである。UE及び/又はネットワークは、5GSにおいて、ネットワークスライス(NWスライス; NS)をサポートすることができる。ネットワークスライスのことを、単にスライスとも呼称する場合がある。 A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. UEs and / or networks can support network slices (NW slices; NS) in 5GS. Network slices may also be referred to simply as slices.
　また、ネットワークスライスインスタンス(NSI)とは、ネットワーク機能(NF)のインスタンス(実体)と、必要なリソースのセットで構成され、配置されるネットワークスライスを形成する。ここで、NFとは、ネットワークにおける処理機能であって、3GPPで採用又は定義されたものである。NSIはコアネットワーク_B内に1以上構成される、NSの実体である。また、NSIはNST(Network Slice Template)を用いて生成された仮想的なNF(Network Function)により構成されてもよい。ここで、NSTとは、要求される通信サービスや能力(capability)を提供する為のリソース要求に関連付けられ、1以上のNFの論理的表現である。つまり、NSIとは、複数のNFにより構成されたコアネットワーク_B190内の集合体でよい。また、NSIはサービス等によって配送されるユーザデータを分ける為に構成された論理的なネットワークでよい。NSには、1以上のNFが構成されてよい。NSに構成されるNFは、他のNSと共有される装置であってもよいし、そうでなくてもよい。UE、及び/又ネットワーク内の装置は、NSSAI、及び/又はS-NSSAI、及び/又はUE usage type、及び/又は1以上のNSI ID等の登録情報、及び/又はAPNに基づいて、1以上のNSに割り当てられることができる。尚、UE usage typeは、NSIを識別するための使用される、UEの登録情報に含まれるパラメータ値である。UE usage typeはHSSに記憶されていてよい。AMFはUE usage typeに基づきSMFとUPFを選択してもよい。 A network slice instance (NSI) is composed of an instance (entity) of a network function (NF) and a set of necessary resources, and forms a network slice to be arranged. Here, NF is a processing function in the network and is adopted or defined in 3GPP. NSI is an entity of NS composed of one or more in core network_B. Further, NSI may be configured by a virtual NF (Network Function) generated by using NST (Network Slice Template). Here, NST is a logical expression of one or more NFs associated with a resource request for providing the required communication service and capability. In other words, the NSI may be an aggregate in the core network_B190 composed of a plurality of NFs. In addition, NSI may be a logical network configured to separate user data delivered by services and the like. One or more NFs may be configured in NS. The NF configured in NS may or may not be a device shared with other NS. UE and / or devices in the network are 1 or more based on NSSAI and / or S-NSSAI and / or UE usage type and / or registration information such as 1 or more NSI IDs and / or APN. Can be assigned to NS. The UE usage type is a parameter value included in the UE registration information used to identify the NSI. The UE usage type may be stored in the HSS. AMF may select SMF and UPF based on UE usage type.
　また、S-NSSAI(Single Network Slice Selection Assistance Information)は、NSを識別するための情報である。S-NSSAIは、SST(Slice/Service type)のみで構成されてもよいし、SSTとSD(Slice Differentiator)の両方で構成されてもよい。ここで、SSTとは、機能とサービスの面で期待されるNSの動作を示す情報である。また、SDは、SSTで示される複数のNSIから1つのNSIを選択する際に、SSTを補間する情報であってもよい。S-NSSAIは、PLMNごとに特有な情報であってもよいし、PLMN間で共通化された標準の情報であってもよい。また、ネットワークは、デフォルトS-NSSAIとして、UEの登録情報に1以上のS-NSSAIを記憶してもよい。尚、S-NSSAIがデフォルトS-NSSAIである場合において、UEが登録要求メッセージにおいて有効なS-NSSAIをネットワークに送信しないときは、ネットワークは、UEに関係するNSを提供してもよい。 In addition, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying NS. S-NSSAI may be composed of only SST (Slice / Service type) or may be composed of both SST and SD (Slice Differentiator). Here, SST is information indicating the operation of NS expected in terms of functions and services. Further, the SD may be information that interpolates the SST when selecting one NSI from a plurality of NSIs represented by the SST. The S-NSSAI may be information peculiar to each PLMN, or may be standard information shared among PLMNs. Further, the network may store one or more S-NSSAI in the registration information of the UE as the default S-NSSAI. If the S-NSSAI is the default S-NSSAI and the UE does not send a valid S-NSSAI to the network in the registration request message, the network may provide the NS related to the UE.
　また、NSSAI(Network Slice Selection Assistance Information)は、S-NSSAIの集まりである。NSSAIに含まれる、各S-NSSAIはアクセスネットワーク又はコアネットワークがNSIを選択するのをアシストする情報である。UEはPLMNごとにネットワークから許可されたNSSAIを記憶してもよい。また、NSSAIは、AMFを選択するのに用いられる情報であってよい。 NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI contained in NSSAI is information that assists the access network or core network in selecting NSI. The UE may memorize the NSSAI permitted by the network for each PLMN. Also, NSSAI may be the information used to select AMF.
　また、requested NSSAI(以下、要求NSSAI、Requested NSSAIとも呼称する)は、登録手続き中にUEからネットワークに提供されるNSSAIである。requested NSSAIは、UEが記憶するallowed NSSAI又はconfigured NSSAIであってよい。具体的には、requested NSSAIは、UEがアクセスしたいネットワークスライスを示す情報であってよい。requested NSSAIに含まれるS-NSSAIはrequested S-NSSAIと表現されてもよい。例えば、requested NSSAIは登録要求メッセージ、又はPDUセッション確立要求メッセージ等のUEからネットワークに送信されるNASメッセージ又はNAS(Non-Access-Stratum)メッセージを含めるRRC(Radio Resource Control)メッセージに含まれて送信される。 Also, requested NSSAI (hereinafter, also referred to as Requested NSSAI, Requested NSSAI) is NSSAI provided from the UE to the network during the registration procedure. The requested NSSAI may be an allowed NSSAI or a configured NSSAI stored in the UE. Specifically, requested NSSAI may be information indicating a network slice that the UE wants to access. The S-NSSAI included in the requested NSSAI may be expressed as requested S-NSSAI. For example, requested NSSAI is included in an RRC (Radio Resource Control) message that includes a NAS message or NAS (Non-Access-Stratum) message sent from the UE to the network, such as a registration request message or a PDU session establishment request message. Will be done.
　また、allowed NSSAI(以下、許可NSSAI、Allowed NSSAIとも呼称する)は、UEが許可された1又は複数ネットワークスライスを示す情報である。言い換えると、allowed NSSAIは、ネットワークがUEへ接続を許可した、ネットワークスライスを識別する情報である。UEとネットワークはそれぞれ、UEの情報として、アクセス(3GPPアクセス又は非3GPPアクセス)ごとに、allowed NSSAIの記憶と管理をする。allowed NSSAIに含まれるS-NSSAIはallowed S-NSSAIと表現されてもよい。allowed S-NSSAIは、S-NSSAIとmapped S-NSSAIを含み構成されてもよい。また、allowed NSSAIに含まれるS-NSSAIを構成するSST又はSDは、IMSサービスを示してもよい。言い換えると、allowed NSSAIに含まれるS-NSSAIを構成するSST又はSDの値は、IMSサービスに対応していてもよい。すなわち、IMSサービスに対応したSSTの値は予め決まっていてもよいし、IMSサービスに対応したSDの値は予め決まっていてもよい。 Also, allowed NSSAI (hereinafter, also referred to as permitted NSSAI and Allowed NSSAI) is information indicating one or more network slices to which a UE is permitted. In other words, allowed NSSAI is information that identifies the network slice that the network has allowed to connect to the UE. The UE and the network each store and manage allowed NSSAI for each access (3GPP access or non-3GPP access) as UE information. S-NSSAI included in allowed NSSAI may be expressed as allowed S-NSSAI. The allowed S-NSSAI may be configured to include S-NSSAI and mapped S-NSSAI. Further, the SST or SD constituting the S-NSSAI included in the allowed NSSAI may indicate an IMS service. In other words, the value of SST or SD that constitutes S-NSSAI included in allowed NSSAI may correspond to the IMS service. That is, the value of SST corresponding to the IMS service may be predetermined, or the value of SD corresponding to the IMS service may be predetermined.
　また、第1のS-NSSAIは、IMS(以下、IMSサービスとも呼称する)に対応するネットワークスライスを識別する情報である。言い換えると、第1のS-NSSAIは、IMSを用いた通信をサポートするネットワークスライスを識別する情報であってよい。また、第1のS-NSSAIは、Allowed NSSAIやdefault NSSAI(以下、デフォルトNSSAIとも呼称する)に含まれてもよい。また、第1のS-NSSAIは、UE及び/又はNWが記憶するS-NSSAIであってよいし、NWからUEへ送信されるS-NSSAIであってよい。また、IMSサービス用の第1のS-NSSAIが、仕様又はオペレータによって、予め規定されていてもよい。 The first S-NSSAI is information that identifies the network slice corresponding to IMS (hereinafter, also referred to as IMS service). In other words, the first S-NSSAI may be information that identifies a network slice that supports communication using IMS. Further, the first S-NSSAI may be included in Allowed NSSAI and default NSSAI (hereinafter, also referred to as default NSSAI). Further, the first S-NSSAI may be an S-NSSAI stored in the UE and / or the NW, or may be an S-NSSAI transmitted from the NW to the UE. Also, the first S-NSSAI for IMS services may be pre-defined by specifications or operators.
　また、第1のS-NSSAIは、IMSサービスに関して、第1のレジストレーションエリアでは有効(使用可能)であるが、第2のレジストレーションエリアで有効ではないS-NSSAIであってもよい。また、第1のS-NSSAIは、IMSサービスに関して、第1のレジストレーションエリアでは有効(使用可能)であるが、IMSサービス以外のサービスに関して、第2のレジストレーションエリアで有効であってもよい。 Further, the first S-NSSAI may be an S-NSSAI that is valid (usable) in the first registration area but not valid in the second registration area for the IMS service. Further, the first S-NSSAI is valid (available) in the first registration area for the IMS service, but may be valid in the second registration area for services other than the IMS service. ..
　また、第2のS-NSSAIは、IMSに対応するネットワークスライスを識別する情報である。言い換えると、第2のS-NSSAIは、IMSを用いた通信をサポートするネットワークスライスを識別する情報であってよい。また、第2のS-NSSAIは、Allowed NSSAIやdefault NSSAIに含まれてもよい。また、第2のS-NSSAIは、UE及び/又はNWが記憶するS-NSSAIであってよいし、NWからUEへ送信されるS-NSSAIであってよい。また、IMSサービス用の第2のS-NSSAIが、仕様又はオペレータによって、予め規定されていてもよい。 The second S-NSSAI is information that identifies the network slice corresponding to IMS. In other words, the second S-NSSAI may be information that identifies a network slice that supports communication using IMS. Further, the second S-NSSAI may be included in Allowed NSSAI and default NSSAI. Further, the second S-NSSAI may be an S-NSSAI stored in the UE and / or the NW, or may be an S-NSSAI transmitted from the NW to the UE. Also, a second S-NSSAI for IMS services may be pre-defined by specifications or operators.
　また、第2のS-NSSAIは、IMSサービスに関して、第2のレジストレーションエリアでは有効(使用可能)であるが、第1のレジストレーションエリアでは有効であるS-NSSAI又は有効ではないS-NSSAIであってもよい。 Also, the second S-NSSAI is valid (available) in the second registration area for the IMS service, but is valid or not valid in the first registration area. It may be.
　また、default NSSAI(以下、デフォルトNSSAI、Default NSSAIとも呼称する)は、IMSに対応する(以下、IMSサービスをサポートする、とも呼称する)default S-NSSAI(以下、デフォルトS-NSSAIとも呼称する)を一又は複数含む情報である。言い換えると、デフォルトNSSAIは、IMSを用いた通信をサポートするデフォルトS-NSSAIを含む情報であってよい。ここで、デフォルトS-NSSAIは、第1のS-NSSAIと同一であってもよいし、異なってもよい。また、デフォルトNSSAI及び/又はデフォルトS-NSSAIは、UE及び/又はNWが記憶するS-NSSAIであってもよい。また、デフォルトS-NSSAIは、全てのPLMNで有効(以下、使用可能や適用可能とも呼称する)であってもよいし、現在のPLMN内で有効であってもよい。また、IMSサービス用のデフォルトS-NSSAIが、仕様又はオペレータによって、予め規定されていてもよい。 In addition, default NSSAI (hereinafter, also referred to as default NSSAI, Default NSSAI) corresponds to IMS (hereinafter, also referred to as supporting IMS service) default S-NSSAI (hereinafter, also referred to as default S-NSSAI). Information including one or more. In other words, the default NSSAI may be information that includes a default S-NSSAI that supports communication using IMS. Here, the default S-NSSAI may be the same as or different from the first S-NSSAI. Further, the default NSSAI and / or the default S-NSSAI may be the S-NSSAI stored in the UE and / or the NW. In addition, the default S-NSSAI may be valid in all PLMNs (hereinafter, also referred to as usable or applicable), or may be valid in the current PLMN. Also, the default S-NSSAI for IMS services may be pre-defined by specifications or operators.
　トラッキングエリア(以下、TAとも呼称する)は、コアネットワークが管理する、UE_A10の位置情報で表すことが可能な単数又は複数の範囲である。トラッキングエリアは、複数のセルで構成されもよい。さらに、トラッキングエリアは、ページング等の制御メッセージがブロードキャストされる範囲でもよいし、UE_A10がハンドオーバー手続きをせずに移動できる範囲でもよい。さらに、トラッキングエリアは、ルーティングエリアでもよいし、ロケーションエリアでもよいし、これらと同様のものであればよい。トラッキングエリアは、TAC(Tracking area code)とPLMNで構成されるTAI(Tracking Area Identityにより識別されてよい。 The tracking area (hereinafter also referred to as TA) is a single or multiple range that can be represented by the location information of UE_A10 managed by the core network. The tracking area may be composed of a plurality of cells. Further, the tracking area may be a range in which a control message such as paging is broadcast, or a range in which UE_A10 can move without performing a handover procedure. Further, the tracking area may be a routing area, a location area, or the same as these. The tracking area may be identified by a TAI (Tracking Area Identity) composed of TAC (Tracking area code) and PLMN.
　レジストレーションエリア(登録エリア)は、AMFがUEに割り当てる1又は複数のTAの集合である。なお、UE_A10は、レジストレーションエリアに含まれる一又は複数のTA内を移動している間は、トラッキングエリア更新のための信号を送受信することなく移動することができてよい。言い換えると、レジストレーションエリアは、UE_A10がト登録手続きを実行することなく移動できるエリアを示す情報群であってよい。レジストレーションエリアは、1又は複数のTAIにより構成されるTAI listにより識別されてよい。 The registration area (registration area) is a set of one or more TAs assigned to the UE by AMF. Note that UE_A10 may be able to move without transmitting and receiving a signal for updating the tracking area while moving within one or a plurality of TAs included in the registration area. In other words, the registration area may be a group of information indicating an area where UE_A10 can move without performing the registration procedure. The registration area may be identified by a TAI list composed of one or more TAIs.
　また、URSP(UE Route Selection Policy)とは、1以上のURSPルール(UE Route Selection Policy Rule)のりストで構成されてよい。また、各URSPルールは、ルール優先度(Rule Precedence)、及び/又はトラフィック記述子(Traffic descriptor)、及び/又はルート選択記述子リスト(List of Route Selection Descriptors)で構成されてよい。 Further, the URSP (UERouteSelectionPolicy) may be composed of one or more URSP rules (UERouteSelectionPolicyRule) paste. Further, each URSP rule may be composed of a rule priority (Rule Precedence) and / or a traffic descriptor (Traffic descriptor) and / or a route selection descriptor list (List of Route Selection Descriptors).
　ここで、ルール優先度は、UEにおいて強制されるURSPルールの順番を示す。UEは、URSPを受信した場合、つまり、1以上のURSPルールを受信した場合、各ルール優先度を参照し、優先度の高いURSPルールから順番に適用してよい。 Here, the rule priority indicates the order of the URSP rules enforced in the UE. When the UE receives URSP, that is, when it receives one or more URSP rules, it may refer to each rule priority and apply them in order from the URSP rule with the highest priority.
　また、トラフィック記述子は、URSPルールをいつ適用するかを示すものである。トラフィック記述子は、アプリケーション記述子(Application descriptors)、及び/又はIP記述子(IP descriptors)、及び/又はドメイン記述子(Domain descriptors)、及び/又はnon-IP記述子(Non-IP descriptors)、及び/又はDNN(Data Network Name)、及び/又は接続能力(Connection Capabilities)で構成されてよい。 Also, the traffic descriptor indicates when to apply the URSP rule. Traffic descriptors include Application descriptors and / or IP descriptors, and / or Domain descriptors, and / or non-IP descriptors, And / or DNN (Data Network Name), and / or connection capabilities (Connection Capabilities).
　ここで、アプリケーション記述子は、OSのIDと、OSのアプリケーションIDを含んでよい。また、IP記述子は、IPトラフィックの送信先(destination)を識別する情報を示し、例えば、IPアドレス、IPv6ネットワークプレフィックス、ポート番号、プロトコル番号などを含んでよい。また、ドメイン記述子(Domain descriptors)は、送信先のFQDN(Fully Qualified Domain Name)を示してよい。また、non-IP記述子は、non-IPトラフィック(例えば、ethernetトラフィックやunstructuredトラフィック)の送信先(destination)を識別する情報を示してよい。また、DNNは、アプリケーションによって提供されるDNNに関する情報であって良い。また、接続能力は、UEがある能力(capability)を用いてネットワークへの接続を要求するときに、UEのアプリケーションによって提供される情報を示してよい。ここで、接続能力は、IMSを示すことができてよい。 Here, the application descriptor may include the OS ID and the OS application ID. The IP descriptor also indicates information that identifies the destination of the IP traffic and may include, for example, an IP address, an IPv6 network prefix, a port number, a protocol number, and the like. Further, the domain descriptors may indicate the FQDN (Fully Qualified Domain Name) of the destination. The non-IP descriptor may also indicate information that identifies the destination of non-IP traffic (eg, ethernet traffic or unstructured traffic). The DNN may also be information about the DNN provided by the application. The connection capability may also indicate the information provided by the UE's application when the UE requests a connection to the network with some capability. Here, the connection capability may indicate IMS.
　また、ルート選択記述子リストは、1以上のルート選択記述子(Route Selection Descriptor)で構成されてよい。各ルート選択記述子は、ルール選択記述子優先度(Route Selection Descriptor Precedence)、及び/又はルート選択構成(Route selection components)で構成されてよい。 Further, the route selection descriptor list may be composed of one or more route selection descriptors (Route Selection Descriptor). Each route selection descriptor may be composed of a rule selection descriptor priority (Route Selection Descriptor Precedence) and / or a route selection configuration (Route selection components).
　ここで、ルール選択記述子優先度は、ルート選択記述子が適用される順番を示す。UEは、ルート選択記述子リストを受信した場合、つまり、1以上のルート選択記述子を受信した場合、各ルート選択記述子におけるルール選択記述子優先度を参照し、優先度の高いルート選択記述子から順番に適用してよい。 Here, the rule selection descriptor priority indicates the order in which the route selection descriptor is applied. When the UE receives a route selection descriptor list, that is, it receives one or more route selection descriptors, it refers to the rule selection descriptor priority in each route selection descriptor and describes the route selection with high priority. It may be applied in order from the child.
　また、ルート選択構成は、SSCモード選択(SSC Mode Selection)、及び/又はネットワークスライス選択(Network Slice Selection)、及び/又はDNN選択(DNN Selection)、及び/又はPDUセッションタイプ選択(PDU Session Type Selection)、及び/又はノンシームレスオフロード指示(Non-Seamless Offload indication)、及び/又はアクセスタイプ嗜好(Access Type preference)で構成されてよい。 In addition, the route selection configuration includes SSC mode selection (SSC Mode Selection) and / or network slice selection (Network Slice Selection) and / or DNN selection (DNN Selection) and / or PDU session type selection (PDU Session Type Selection). ), And / or a non-seamless Offload indication, and / or an Access Type preference.
　ここで、SSCモード選択は、アプリケーションのトラフィックを、指定されたSSCモードのPDUセッションを介して、ルーティングすることを示してよい。また、ネットワークスライス選択は、示された1以上のS-NSSAIをサポートするPDUセッションを使って、アプリケーションのトラフィックをルーティングすることを示してよい。ここで、ネットワークスライス選択は、IMSをサポートする第1のS-NSSAIを示すことができてよい。また、DNN選択は、示された1以上のDNNをサポートするPDUセッションを使って、アプリケーションのトラフィックをルーティングすることを示してよい。また、PDUセッションタイプ選択は、示されたPDUセッションタイプをサポートするPDUセッションを使って、アプリケーションのトラフィックをルーティングすることを示してよい。また、ノンシームレスオフロード指示は、アプリケーションのトラフィックを、non-3GPPアクセスに対するオフロードすることを示してよい。また、アクセスタイプ嗜好は、UEがPDUセッションを確立する必要がある場合、PDUセッションを確立するアクセスタイプを示してよい。ここで、アクセスタイプとは、3GPP、又はnon-3GPP、又はマルチアクセス(Multi-Access)を示してよい。 Here, the SSC mode selection may indicate that the application traffic is routed through the specified SSC mode PDU session. The network slice selection may also indicate that the application traffic is routed using the indicated PDU session that supports one or more S-NSSAI. Here, the network slice selection may indicate a first S-NSSAI that supports IMS. DNN selection may also indicate routing application traffic with a PDU session that supports one or more of the indicated DNNs. Also, the PDU session type selection may indicate that the traffic of the application is routed using a PDU session that supports the indicated PDU session type. The non-seamless offload instruction may also indicate that the application traffic is offloaded for non-3GPP access. The access type preference may also indicate the access type that establishes the PDU session if the UE needs to establish the PDU session. Here, the access type may indicate 3GPP, non-3GPP, or multi-access.
　次に、本実施形態において、各装置により送受信、及び記憶管理される識別情報について説明する。 Next, in the present embodiment, the identification information transmitted / received and stored and managed by each device will be described.
　まず、第1の識別情報は、default S-NSSAI(以下、デフォルトS-NSSAIとも呼称する)である。また、第1の識別情報は、第11の識別情報及び/又は第21の識別情報及び/又は第31の識別情報と同一であってよい。また、第1の識別情報は、第11の識別情報及び/又は第21の識別情報及び/又は第31の識別情報の中から選択されたものであってよい。 First, the first identification information is default S-NSSAI (hereinafter, also referred to as default S-NSSAI). Further, the first identification information may be the same as the eleventh identification information and / or the 21st identification information and / or the 31st identification information. Further, the first identification information may be selected from the eleventh identification information and / or the 21st identification information and / or the 31st identification information.
　また、第2の識別情報は、S-NSSAIを使用することができるレジストレーションエリアの情報の要求を示す情報である。具体的には、第2の識別情報は、IMSをサポートするS-NSSAIを使用可能なレジストレーションエリアの情報の要求を示す情報であってよい。 The second identification information is information indicating a request for information on the registration area where S-NSSAI can be used. Specifically, the second identification information may be information indicating a request for information on a registration area in which S-NSSAI supporting IMS can be used.
　また、第3の識別情報は、IMSをサポートする第1のS-NSSAIである。また、第3の識別情報は、第15の識別情報に含まれるS-NSSAIと同一であってもよいし、異なってもよい。また、第3の識別情報は、第16の識別情報と同一であってもよい。また、第3の識別情報は、第25の識別情報に含まれるS-NSSAIと同一であってもよいし、異なってもよい。また、第3の識別情報は、第26の識別情報と同一であってもよい。また、第3の識別情報は、第36の識別情報と同一であってもよい。 Also, the third identification information is the first S-NSSAI that supports IMS. Further, the third identification information may be the same as or different from the S-NSSAI included in the fifteenth identification information. Further, the third identification information may be the same as the sixteenth identification information. Further, the third identification information may be the same as or different from the S-NSSAI included in the 25th identification information. Further, the third identification information may be the same as the 26th identification information. Further, the third identification information may be the same as the 36th identification information.
　また、第4の識別情報は、第1から3の識別情報のうちの少なくとも一部を含む情報である。 Further, the fourth identification information is information including at least a part of the first to third identification information.
　また、第11の識別情報は、デフォルトS-NSSAIである。また、第11の識別情報は、第1の識別情報及び/又は第21の識別情報及び/又は第31の識別情報と同一であってもよいし、異なってもよい。 Also, the 11th identification information is the default S-NSSAI. Further, the eleventh identification information may be the same as or different from the first identification information and / or the 21st identification information and / or the 31st identification information.
　また、第12の識別情報は、Allowed NSSAIに含まれるS-NSSAIが有効なレジストレーションエリアを示す情報、及び/又は、Allowed NSSAIに含まれるS-NSSAIが現在のレジストレーションエリアで有効か否かを示す情報、及び/又は、Allowed NSSAIに含まれるS-NSSAIが現在のPLMN内で有効か否かを示す情報、及び/又は、Allowed NSSAIに含まれるS-NSSAIが、全てのPLMNで有効か否かを示す情報であってもよい。 In addition, the twelfth identification information indicates the registration area in which S-NSSAI contained in Allowed NSSAI is valid, and / or whether S-NSSAI contained in Allowed NSSAI is valid in the current registration area. And / or information indicating whether S-NSSAI contained in Allowed NSSAI is valid in the current PLMN, and / or whether S-NSSAI contained in Allowed NSSAI is valid in all PLMNs. It may be information indicating whether or not.
　また、第12の識別情報は、第1のS-NSSAIが有効なレジストレーションエリアを示す情報、及び/又は、第1のS-NSSAIが現在のレジストレーションエリアで有効か否かを示す情報、及び/又は、第1のS-NSSAIが現在のPLMN内で有効か否かを示す情報、及び/又は、第1のS-NSSAIが全てのPLMNで有効か否かを示す情報であってもよい。 The twelfth identification information is information indicating whether the first S-NSSAI is valid in the registration area and / or information indicating whether or not the first S-NSSAI is valid in the current registration area. And / or even information indicating whether the first S-NSSAI is valid within the current PLMN and / or information indicating whether the first S-NSSAI is valid in all PLMNs. good.
　また、第12の識別情報は、レジストレーションエリアについて、アクセスタイプごとの情報として構成されてもよい。すなわち、第12の識別情報は、第1のS-NSSAIが、3GPPアクセスについて現在のレジストレーションエリアで有効か否か示す情報、及び/又は、non-3GPPアクセスについて現在のレジストレーションエリアで有効か否か示す情報、及び/又は、第1のS-NSSAIが、現在のPLMN(Public Land Mobile Network)で有効か示す情報、及び/又は、第1のS-NSSAIが、全てのPLMNで有効かを示す情報であってよい。 Further, the twelfth identification information may be configured as information for each access type for the registration area. That is, the twelfth identification information indicates whether the first S-NSSAI is valid in the current registration area for 3GPP access, and / or is it valid in the current registration area for non-3GPP access. Information indicating whether or not the first S-NSSAI is valid in the current PLMN (Public Land Mobile Network), and / or whether the first S-NSSAI is valid in all PLMNs. It may be information indicating.
　また、第12の識別情報は、アクセスタイプに関する情報を含み、レジストレーションエリアについて、アクセスタイプと対応付けた情報として構成されてよい。すなわち、第12の識別情報は、アクセスタイプ毎に、第1のS-NSSAIが、現在のレジストレーションエリアで有効か否か示す情報、及び/又は、第1のS-NSSAIが、現在のPLMN(Public Land Mobile Network)で有効か示す情報、及び/又は、第1のS-NSSAIが、全てのPLMNで有効かを示す情報であってよい。ここで、アクセスタイプに関する情報は、前述のように、3GPPアクセス、又はnon-3GPPアクセスを示す情報であってよい。 Further, the twelfth identification information includes information on the access type, and may be configured as information associated with the access type for the registration area. That is, the twelfth identification information is information indicating whether or not the first S-NSSAI is valid in the current registration area for each access type, and / or the first S-NSSAI is the current PLMN. It may be information indicating whether it is valid in (Public Land Mobile Network) and / or information indicating whether the first S-NSSAI is valid in all PLMNs. Here, the information regarding the access type may be information indicating 3GPP access or non-3GPP access as described above.
　また、第12の識別情報は、アクセスタイプと対応付けたアクセス単位毎の個別の複数の情報として構成されていてもよい。例えば、第12の識別情報#Aは、第1のS-NSSAIが、3GPPアクセスにおいて、現在のレジストレーションエリアで有効か否かを示す情報であってもよいし、第12の識別情報#Bは、第1のS-NSSAIが、non-3GPPアクセスにおいて、現在のレジストレーションエリアで有効か否かを示す情報であってもよい。 Further, the twelfth identification information may be configured as a plurality of individual information for each access unit associated with the access type. For example, the twelfth identification information #A may be information indicating whether or not the first S-NSSAI is valid in the current registration area in 3GPP access, or the twelfth identification information #B. May be information indicating whether or not the first S-NSSAI is valid in the current registration area in non-3GPP access.
　また、第13の識別情報は、Allowed NSSAIにIMSサービスのためのS-NSSAIが含まれること、及び/又はAllowed NSSAIに含まれる最初のS-NSSAIがIMSサービスのためのS-NSSAIであること、及び/又はAllowed NSSAIに含まれる最後のS-NSSAIがIMSサービスのためのS-NSSAIであることを示す情報である。また、第13の識別情報は、Allowed NSSAIに含まれるIMSサービスのためのS-NSSAIが何番目に位置するかを示す情報であってもよい。 The thirteenth identification information is that Allowed NSSAI contains S-NSSAI for IMS service and / or the first S-NSSAI contained in Allowed NSSAI is S-NSSAI for IMS service. , And / or information indicating that the last S-NSSAI contained in Allowed NSSAI is the S-NSSAI for the IMS service. Further, the thirteenth identification information may be information indicating the position of the S-NSSAI for the IMS service included in the Allowed NSSAI.
　また、第14の識別情報は、IMSサービスを識別する情報である。また、第14の識別情報は、IMSをサポートするS-NSSAIと対応づけられていてもよい。 The 14th identification information is information that identifies the IMS service. Further, the 14th identification information may be associated with S-NSSAI that supports IMS.
　また、第15の識別情報は、Allowed NSSAIである。また、第15の識別情報は、IMSサービスをサポートする第1のS-NSSAIを含んでもよい。また、第15の識別情報に含まれる全てのS-NSSAIが、IMSサービスをサポートしない場合もあってよい。また、第15の識別情報は、第11の識別情報及び/又は第14の識別情報及び/又は第16の識別情報を含んでもよい。また、第15の識別情報に含まれる1以上のS-NSSAIの位置や順番と、IMSサービスとが、仕様によって、又はオペレータによって予め規定されていてもよい。例えば、第15の識別情報に含まれる1以上のS-NSSAIのうち、先頭のS-NSSAIは、IMSサービスに対応するS-NSSAIであることが予め規定されていてもよい。また、第15の識別情報に含まれる1以上のS-NSSAIのうち、最後のS-NSSAIは、IMSサービスに対応するS-NSSAIであることが予め規定されていてもよい。また、第15の識別情報に含まれる1以上のS-NSSAIのうち、先頭からｎ番目（但し、ｎは１より大きい値とする）のS-NSSAIは、IMSサービスに対応するS-NSSAIであることが予め規定されていてもよい。また、第15の識別情報に含まれる1以上のS-NSSAIのうち、最後からｎ番目（但し、ｎは１より大きい値とする）のS-NSSAIは、IMSサービスに対応するS-NSSAIであることが予め規定されていてもよい。また、第15の識別情報に含まれるS-NSSAIは、SST(Slice/Service type)及び/又はSD(Slice Differentiator)によって構成されるS-NSSAIであってもよい。 Also, the 15th identification information is Allowed NSSAI. The fifteenth identification information may also include a first S-NSSAI that supports the IMS service. In addition, all S-NSSAI included in the fifteenth identification information may not support the IMS service. Further, the fifteenth identification information may include the eleventh identification information and / or the fourteenth identification information and / or the sixteenth identification information. Further, the position and order of one or more S-NSSAI included in the fifteenth identification information and the IMS service may be predetermined by the specifications or by the operator. For example, among one or more S-NSSAI included in the fifteenth identification information, the first S-NSSAI may be pre-defined as the S-NSSAI corresponding to the IMS service. Further, it may be specified in advance that the last S-NSSAI among the one or more S-NSSAI included in the fifteenth identification information is the S-NSSAI corresponding to the IMS service. Of the 1 or more S-NSSAI included in the 15th identification information, the nth S-NSSAI from the beginning (where n is a value larger than 1) is the S-NSSAI corresponding to the IMS service. It may be specified in advance that there is. Of the 1 or more S-NSSAI included in the 15th identification information, the nth S-NSSAI from the end (where n is a value larger than 1) is the S-NSSAI corresponding to the IMS service. It may be specified in advance that there is. Further, the S-NSSAI included in the fifteenth identification information may be an S-NSSAI composed of SST (Slice / Service type) and / or SD (Slice Differentiator).
　また、第16の識別情報は、IMSをサポートする第1のS-NSSAI及び/又は第2のS-NSSAIである。また、第16の識別情報は、第15の識別情報に含まれるS-NSSAIと同一であってもよいし、異なってもよい。また、第16の識別情報は、第25の識別情報に含まれるS-NSSAIと同一であってもよいし、異なってもよい。また、第16の識別情報は、第26の識別情報と同一であってもよいし、異なってもよい。また、第16の識別情報は、第36の識別情報と同一であってもよいし、異なってもよい。また、第16の識別情報は、SST(Slice/Service type)及び/又はSD(Slice Differentiator)によって構成されるS-NSSAIであってもよい。 Also, the 16th identification information is the first S-NSSAI and / or the second S-NSSAI that supports IMS. Further, the 16th identification information may be the same as or different from the S-NSSAI included in the 15th identification information. Further, the 16th identification information may be the same as or different from the S-NSSAI included in the 25th identification information. Further, the 16th identification information may be the same as or different from the 26th identification information. Further, the 16th identification information may be the same as or different from the 36th identification information. Further, the 16th identification information may be S-NSSAI composed of SST (Slice / Service type) and / or SD (Slice Differentiator).
　また、第17の識別情報は、第11から16の識別情報のうちの少なくとも一部を含む情報であってよい。 Further, the 17th identification information may be information including at least a part of the 11th to 16th identification information.
　また、第21の識別情報は、デフォルトS-NSSAIである。また、第21の識別情報は、第1の識別情報及び/又は第11の識別情報及び/又は第31の識別情報と同一であってもよいし、異なってもよい。 Also, the 21st identification information is the default S-NSSAI. Further, the 21st identification information may be the same as or different from the 1st identification information and / or the 11th identification information and / or the 31st identification information.
　また、第22の識別情報は、第1のS-NSSAIが有効なレジストレーションエリアを示す情報、及び/又は、第1のS-NSSAIが現在のレジストレーションエリアで有効か否かを示す情報、及び/又は、第1のS-NSSAIが現在のPLMN内で有効か否かを示す情報、及び/又は、第1のS-NSSAIが全てのPLMNで有効か否かを示す情報である。 The 22nd identification information is information indicating whether the first S-NSSAI is valid in the registration area and / or information indicating whether or not the first S-NSSAI is valid in the current registration area. And / or information indicating whether the first S-NSSAI is valid in the current PLMN, and / or information indicating whether the first S-NSSAI is valid in all PLMNs.
　また、第22の識別情報は、レジストレーションエリアについて、アクセスタイプごとの情報として構成されてもよい。すなわち、第22の識別情報は、第1のS-NSSAIが、3GPPアクセスについて現在のレジストレーションエリアで有効か否か示す情報、及び/又は、non-3GPPアクセスについて現在のレジストレーションエリアで有効か否か示す情報、及び/又は、第1のS-NSSAIが、現在のPLMN(Public Land Mobile Network)で有効か示す情報、及び/又は、第1のS-NSSAIが、全てのPLMNで有効かを示す情報であってよい。 Further, the 22nd identification information may be configured as information for each access type for the registration area. That is, the 22nd identification information indicates whether the 1st S-NSSAI is valid in the current registration area for 3GPP access, and / or is it valid in the current registration area for non-3GPP access. Information indicating whether or not the first S-NSSAI is valid in the current PLMN (Public Land Mobile Network), and / or whether the first S-NSSAI is valid in all PLMNs. It may be information indicating.
　また、第22の識別情報は、アクセスタイプに関する情報を含み、レジストレーションエリアについて、アクセスタイプと対応付けた情報として構成されてよい。すなわち、第22の識別情報は、アクセスタイプ毎に、第1のS-NSSAIが、現在のレジストレーションエリアで有効か否か示す情報、及び/又は、第1のS-NSSAIが、現在のPLMN(Public Land Mobile Network)で有効か示す情報、及び/又は、第1のS-NSSAIが、全てのPLMNで有効かを示す情報であってよい。ここで、アクセスタイプに関する情報は、前述のように、3GPPアクセス、又はnon-3GPPアクセスを示す情報であってよい。 Further, the 22nd identification information includes information regarding the access type, and may be configured as information associated with the access type for the registration area. That is, the 22nd identification information is information indicating whether or not the 1st S-NSSAI is valid in the current registration area for each access type, and / or the 1st S-NSSAI is the current PLMN. It may be information indicating whether it is valid in (Public Land Mobile Network) and / or information indicating whether the first S-NSSAI is valid in all PLMNs. Here, the information regarding the access type may be information indicating 3GPP access or non-3GPP access as described above.
　また、第22の識別情報は、アクセスタイプと対応付けたアクセス単位毎の個別の複数の情報として構成されていてもよい。例えば、第22の識別情報#Aは、第1のS-NSSAIが、3GPPアクセスにおいて、現在のレジストレーションエリアで有効か否かを示す情報であってもよいし、第22の識別情報#Bは、第1のS-NSSAIが、non-3GPPアクセスにおいて、現在のレジストレーションエリアで有効か否かを示す情報であってもよい。 Further, the 22nd identification information may be configured as a plurality of individual information for each access unit associated with the access type. For example, the 22nd identification information #A may be information indicating whether or not the 1st S-NSSAI is valid in the current registration area in 3GPP access, or the 22nd identification information #B. May be information indicating whether or not the first S-NSSAI is valid in the current registration area in non-3GPP access.
　また、第23の識別情報は、Allowed NSSAIにIMSサービスのためのS-NSSAIが含まれること、及び/又はAllowed NSSAIに含まれる最初のS-NSSAIがIMSサービスのためのS-NSSAIであること、及び/又はAllowed NSSAIに含まれる最後のS-NSSAIがIMSサービスのためのS-NSSAIであることを示す情報である。また、第23の識別情報は、Allowed NSSAIに含まれるIMSサービスのためのS-NSSAIが何番目に位置するかを示す情報であってもよい。 Also, the 23rd identification information is that Allowed NSSAI contains S-NSSAI for IMS service and / or the first S-NSSAI included in Allowed NSSAI is S-NSSAI for IMS service. , And / or information indicating that the last S-NSSAI contained in Allowed NSSAI is the S-NSSAI for the IMS service. Further, the 23rd identification information may be information indicating the position of the S-NSSAI for the IMS service included in the Allowed NSSAI.
　また、第24の識別情報は、IMSサービスを識別する情報である。また、第24の識別情報は、IMSをサポートするS-NSSAIと対応づけられていてもよい。 The 24th identification information is information that identifies the IMS service. Further, the 24th identification information may be associated with S-NSSAI that supports IMS.
　また、第25の識別情報は、Allowed NSSAIである。また、第25の識別情報は、IMSサービスをサポートする第1のS-NSSAIを含んでもよい。また、第25の識別情報に含まれる全てのS-NSSAIが、IMSサービスをサポートしない場合もあってよい。また、第25の識別情報は、第21の識別情報及び/又は第24の識別情報及び/又は第26の識別情報を含んでもよい。また、第25の識別情報に含まれるS-NSSAIは、SST(Slice/Service type)及び/又はSD(Slice Differentiator)によって構成されるS-NSSAIであってもよい。 The 25th identification information is Allowed NSSAI. The 25th identification information may also include a first S-NSSAI that supports the IMS service. In addition, all S-NSSAI included in the 25th identification information may not support the IMS service. Further, the 25th identification information may include the 21st identification information and / or the 24th identification information and / or the 26th identification information. Further, the S-NSSAI included in the 25th identification information may be an S-NSSAI composed of SST (Slice / Service type) and / or SD (Slice Differentiator).
　また、第26の識別情報は、IMSをサポートする第1のS-NSSAI及び/又は第2のS-NSSAIである。また、第26の識別情報は、第15の識別情報に含まれるS-NSSAIと同一であってもよいし、異なってもよい。また、第26の識別情報は、第16の識別情報と同一であってもよいし、異なってもよい。また、第26の識別情報は、第25の識別情報に含まれるS-NSSAIと同一であってもよいし、異なってもよい。また、第26の識別情報は、第36の識別情報と同一であってもよいし、異なってもよい。また、第26の識別情報は、SST(Slice/Service type)及び/又はSD(Slice Differentiator)によって構成されるS-NSSAIであってもよい。 Also, the 26th identification information is the first S-NSSAI and / or the second S-NSSAI that supports IMS. Further, the 26th identification information may be the same as or different from the S-NSSAI included in the 15th identification information. Further, the 26th identification information may be the same as or different from the 16th identification information. Further, the 26th identification information may be the same as or different from the S-NSSAI included in the 25th identification information. Further, the 26th identification information may be the same as or different from the 36th identification information. Further, the 26th identification information may be S-NSSAI composed of SST (Slice / Service type) and / or SD (Slice Differentiator).
　また、第27の識別情報は、第21から26の識別情報のうちの少なくとも一部を含む情報であってよい。 Further, the 27th identification information may be information including at least a part of the 21st to 26th identification information.
　また、第31の識別情報は、デフォルトS-NSSAIである。また、第31の識別情報は、第1の識別情報及び/又は第11の識別情報及び/又は第21の識別情報と同一であってもよいし、異なってもよい。また、第31の識別情報は、Allowed NSSAIに含まれてもよい。 Also, the 31st identification information is the default S-NSSAI. Further, the 31st identification information may be the same as or different from the 1st identification information and / or the 11th identification information and / or the 21st identification information. Further, the 31st identification information may be included in Allowed NSSAI.
　また、第32の識別情報は、第1のS-NSSAIが有効なレジストレーションエリアを示す情報、及び/又は、第1のS-NSSAIが現在のレジストレーションエリアで有効か否かを示す情報、及び/又は、第1のS-NSSAIが現在のPLMN内で有効か否かを示す情報、及び/又は、第1のS-NSSAIが全てのPLMNで有効か否かを示す情報である。 Further, the 32nd identification information is information indicating whether the first S-NSSAI is valid in the registration area and / or information indicating whether or not the first S-NSSAI is valid in the current registration area. And / or information indicating whether the first S-NSSAI is valid in the current PLMN, and / or information indicating whether the first S-NSSAI is valid in all PLMNs.
　また、第32の識別情報は、レジストレーションエリアについて、アクセスタイプごとの情報として構成されてもよい。すなわち、第32の識別情報は、第1のS-NSSAIが、3GPPアクセスについて現在のレジストレーションエリアで有効か否か示す情報、及び/又は、non-3GPPアクセスについて現在のレジストレーションエリアで有効か否か示す情報、及び/又は、第1のS-NSSAIが、現在のPLMN(Public Land Mobile Network)で有効か示す情報、及び/又は、第1のS-NSSAIが、全てのPLMNで有効かを示す情報であってよい。 Further, the 32nd identification information may be configured as information for each access type for the registration area. That is, the 32nd identification information indicates whether the 1st S-NSSAI is valid in the current registration area for 3GPP access, and / or is it valid in the current registration area for non-3GPP access. Information indicating whether or not the first S-NSSAI is valid in the current PLMN (Public Land Mobile Network), and / or whether the first S-NSSAI is valid in all PLMNs. It may be information indicating.
　また、第32の識別情報は、アクセスタイプに関する情報を含み、レジストレーションエリアについて、アクセスタイプと対応付けた情報として構成されてよい。すなわち、第32の識別情報は、アクセスタイプ毎に、第1のS-NSSAIが、現在のレジストレーションエリアで有効か否か示す情報、及び/又は、第1のS-NSSAIが、現在のPLMN(Public Land Mobile Network)で有効か示す情報、及び/又は、第1のS-NSSAIが、全てのPLMNで有効かを示す情報であってよい。ここで、アクセスタイプに関する情報は、前述のように、3GPPアクセス、又はnon-3GPPアクセスを示す情報であってよい。 Further, the 32nd identification information includes information regarding the access type, and may be configured as information associated with the access type for the registration area. That is, the 32nd identification information is information indicating whether or not the 1st S-NSSAI is valid in the current registration area for each access type, and / or the 1st S-NSSAI is the current PLMN. It may be information indicating whether it is valid in (Public Land Mobile Network) and / or information indicating whether the first S-NSSAI is valid in all PLMNs. Here, the information regarding the access type may be information indicating 3GPP access or non-3GPP access as described above.
　また、第32の識別情報は、アクセスタイプと対応付けたアクセス単位毎の個別の複数の情報として構成されていてもよい。例えば、第32の識別情報#Aは、第1のS-NSSAIが、3GPPアクセスにおいて、現在のレジストレーションエリアで有効か否かを示す情報であってもよいし、第32の識別情報#Bは、第1のS-NSSAIが、non-3GPPアクセスにおいて、現在のレジストレーションエリアで有効か否かを示す情報であってもよい。 Further, the 32nd identification information may be configured as a plurality of individual information for each access unit associated with the access type. For example, the 32nd identification information #A may be information indicating whether or not the 1st S-NSSAI is valid in the current registration area in 3GPP access, or the 32nd identification information #B. May be information indicating whether or not the first S-NSSAI is valid in the current registration area in non-3GPP access.
　また、第33の識別情報は、URSPである。第33の識別情報は、第32、34から36の識別情報のうちの少なくとも1つを含んで構成されてよい。 The 33rd identification information is URSP. The 33rd identification information may be configured to include at least one of the 32nd, 34th to 36th identification information.
　また、第34の識別情報は、第32の識別情報、及び/又は第35の識別情報、及び/又は第36の識別情報とのマッピング情報であってよい。第34の識別情報は、第32の識別情報、及び/又は第35の識別情報、及び/又は第36の識別情報が対応していることを明示的に示す情報であって良い。 Further, the 34th identification information may be mapping information with the 32nd identification information and / or the 35th identification information and / or the 36th identification information. The 34th identification information may be information that explicitly indicates that the 32nd identification information and / or the 35th identification information and / or the 36th identification information correspond to each other.
　また、第35の識別情報は、サービスタイプを示す情報である。また、第35の識別情報は、IMS又はIMSサービスを示してよい。また、第35の識別情報は、S-NSSAIをIMSサービスに用いることができるか否かを示す情報であってもよい。また、第35の識別情報は、IMS又はIMSサービスを示す接続能力(Connection Capabilities)であってもよい。また、第35の識別情報は、S-NSSAIをIMSサービスに用いることができるか否かを示す接続能力であってもよい。また、第35の識別情報は、IMSをサポートするS-NSSAIと対応づけられていてもよい。 The 35th identification information is information indicating the service type. Further, the 35th identification information may indicate IMS or IMS service. Further, the 35th identification information may be information indicating whether or not S-NSSAI can be used for the IMS service. Further, the 35th identification information may be IMS or Connection Capabilities indicating the IMS service. Further, the 35th identification information may be a connection capability indicating whether or not S-NSSAI can be used for the IMS service. Further, the 35th identification information may be associated with S-NSSAI that supports IMS.
　また、第36の識別情報は、IMSをサポートする第1のS-NSSAI及び/又は第2のS-NSSAIである。また、第36の識別情報は、第15の識別情報に含まれるS-NSSAIと同一であってもよいし、異なってもよい。また、第36の識別情報は、第16の識別情報と同一であってもよいし、異なってもよい。また、第36の識別情報は、第25の識別情報に含まれるS-NSSAIと同一であってもよいし、異なってもよい。また、第36の識別情報は、第26の識別情報と同一であってもよいし、異なってもよい。また、第36の識別情報は、PCFが、AMFから受信したAllowed NSSAIに関する情報を受信した場合、そのAllowed NSSAIに含まれる1以上のS-NSSAIの中から選択した第1のS-NSSAIであってもよい。また、第36の識別情報は、新たなレジストレーションエリアで有効(使用可能)な、IMSサービスをサポートする第1のS-NSSAIであってもよい。また、第36の識別情報は、Allowed NSSAIに含まれてもよい。また、第36の識別情報は、SST(Slice/Service type)及び/又はSD(Slice Differentiator)によって構成されるS-NSSAIであってもよい。 Also, the 36th identification information is the first S-NSSAI and / or the second S-NSSAI that supports IMS. Further, the 36th identification information may be the same as or different from the S-NSSAI included in the 15th identification information. Further, the 36th identification information may be the same as or different from the 16th identification information. Further, the 36th identification information may be the same as or different from the S-NSSAI included in the 25th identification information. Further, the 36th identification information may be the same as or different from the 26th identification information. Further, the 36th identification information is the first S-NSSAI selected from one or more S-NSSAI included in the Allowed NSSAI when the PCF receives the information about the Allowed NSSAI received from the AMF. You may. Further, the 36th identification information may be the first S-NSSAI that supports the IMS service, which is valid (available) in the new registration area. Further, the 36th identification information may be included in Allowed NSSAI. Further, the 36th identification information may be S-NSSAI composed of SST (Slice / Service type) and / or SD (Slice Differentiator).
　また、第37の識別情報は、第31から36の識別情報のうちの少なくとも一部を含む情報であってよい。 Further, the 37th identification information may be information including at least a part of the 31st to 36th identification information.
　また、第41の識別情報は、拒絶の理由を示す理由値(cause value)である。また、第41の識別情報は、現在のレジストレーションエリアで利用できないこと(unavailable at current registration area)を示す理由値であってもよい。また、第41の識別情報は、提供されたS-NSSAI(第1のS-NSSAIを含む)が、現在のレジストレーションエリアで利用できないこと(S-NSSAI unavailable at current registration area)を示す理由値であってもよい。また、第41の識別情報は、3GPPアクセス及び/又はnon-3GPPアクセスと関連付けられていてもよい。すなわち、第41の識別情報は、3GPPアクセス及び/又はnon-3GPPアクセスに対して、現在のレジストレーションエリアで利用できないこと(unavailable at current registration area for 3GPP access and/or non-3GPP access)を示す理由値であってもよい。また、第41の識別情報は、3GPPアクセス及び/又はnon-3GPPアクセスに対して、提供されたS-NSSAIが、現在のレジストレーションエリアで利用できないこと(S-NSSAI unavailable at current registration area for 3GPP access and/or non-3GPP access)を示す理由値であってもよい。 The 41st identification information is a reason value indicating the reason for refusal. Further, the 41st identification information may be a reason value indicating that it cannot be used in the current registration area (unavailable at current registration area). In addition, the 41st identification information is a reason value indicating that the provided S-NSSAI (including the first S-NSSAI) is not available in the current registration area (S-NSSAI unavailable at current registration area). It may be. Also, the 41st identification information may be associated with 3GPP access and / or non-3GPP access. That is, the 41st identification information indicates that it cannot be used in the current registration area for 3GPP access and / or non-3GPP access (unavailable at current registration area for 3GPP access and / or non-3GPP access). It may be a reason value. In addition, the 41st identification information is that the provided S-NSSAI cannot be used in the current registration area for 3GPP access and / or non-3GPP access (S-NSSAI unavailable at current registration area for 3GPP. It may be a reason value indicating access and / or non-3GPP access).
　[3. 第1の実施形態]
　[3.1. 第1の実施形態で用いられる手続き]
　まず、第1の実施形態で用いられる手続きについて説明する。第1の実施形態で用いられる手続きには、3.2章の登録手続き(Registration procedure)、及び/又は3.3章のジェネリックUE設定更新手続き(Generic UE configuration update procedure)、及び/又は3.4章のUEポリシー更新手続き(UE policy management procedure)が含まれる。 [3. First Embodiment]
[3.1. Procedure used in the first embodiment]
First, the procedure used in the first embodiment will be described. The procedures used in the first embodiment include the registration procedure in Chapter 3.2 and / or the Generic UE configuration update procedure in Chapter 3.3, and / or the UE policy update in Chapter 3.4. Includes a UE policy management procedure.
　尚、第1の実施形態では、図2に記載されているように、HSSとUDM、PCFとPCRF、SMFとPGW-C、UPFとPGW-Uが、それぞれ同一の装置(つまり、同一の物理的なハードウェア、又は同一の論理的なハードウェア、又は同一のソフトウェア)として構成されている場合を例にとって説明する。しかし、本実施形態に記載される内容は、これらが異なる装置(つまり、異なる物理的なハードウェア、又は異なる論理的なハードウェア、又は異なるソフトウェア)として構成される場合にも適用可能である。例えば、これらの間で、直接データの送受信を行ってもよいし、AMF、MME間のN26インターフェースを介してデータを送受信してもよいし、UEを介してデータを送受信してもよい。 In the first embodiment, as shown in FIG. 2, HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are each the same device (that is, the same physics). The case where the hardware is configured as the same hardware, the same logical hardware, or the same software) will be described as an example. However, the content described in this embodiment is also applicable when they are configured as different devices (ie, different physical hardware, or different logical hardware, or different software). For example, data may be transmitted / received directly between them, data may be transmitted / received via the N26 interface between AMF and MME, or data may be transmitted / received via UE.
　[3.2. 登録手続き]
　まず、登録手続き(Registration procedure)について、図6を用いて説明する。以下、本手続きとは登録手続きを指す。登録手続きは、UEが主導してアクセスネットワーク_B、及び/又はコアネットワーク_B、及び/又はDNへ登録する為の手続きである。UEは、ネットワークに登録していない状態であれば、例えば、電源投入時等の任意のタイミングで本手続きを実行することができる。言い換えると、UEは、非登録状態(5GMM-DEREGISTERED state)であれば任意のタイミングで本手続きを開始できる。また、各装置(特にUEとAMF)は、登録手続きの完了に基づいて、登録状態(5GMM-REGISTEDED state)に遷移することができる。尚、各登録状態は、アクセス毎に各装置で管理されてよい。具体的には、各装置は3GPPアクセスに対する登録の状態(登録状態又は非登録状態)と、non-3GPPアクセスに対する登録の状態を独立して管理してよい。 [3.2. Registration procedure]
First, the registration procedure will be described with reference to FIG. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering with the access network_B and / or the core network_B and / or the DN. The UE can execute this procedure at any time, for example, when the power is turned on, as long as it is not registered in the network. In other words, the UE can start this procedure at any time if it is in the unregistered state (5GMM-DEREGISTERED state). In addition, each device (especially UE and AMF) can transition to the registration state (5GMM-REGISTEDED state) based on the completion of the registration procedure. It should be noted that each registration state may be managed by each device for each access. Specifically, each device may independently manage the registration status (registered or unregistered status) for 3GPP access and the registration status for non-3GPP access.
　さらに、登録手続きは、ネットワークにおけるUEの位置登録情報を更新する、及び/又は、UEからネットワークへ定期的にUEの状態を通知する、及び/又は、ネットワークにおけるUEに関する特定のパラメータを更新する為の手続きであってもよい。 In addition, the registration procedure updates the location registration information of the UE in the network and / or periodically notifies the network of the status of the UE from the UE and / or updates certain parameters about the UE in the network. It may be the procedure of.
　UEは、TAを跨ぐモビリティをした際に、登録手続きを開始してもよい。言い換えると、UEは、保持しているTAリストで示されるTAとは異なるTAに移動した際に、登録手続きを開始してもよい。さらに、UEは、実行しているバックオフタイマ、又はその他のタイマが満了した際に、本手続きを開始してもよい。さらに、UEは、PDUセッションの切断や無効化が原因で、各装置のコンテキストの更新が必要な際に、登録手続きを開始してもよい。さらに、UEは、UEのPDUセッション確立に関する、能力情報及び/又はプリファレンスに変化が生じた場合、登録手続きを開始してもよい。さらに、UEは、定期的に登録手続きを開始してもよい。さらに、UEは、3.2章の登録手続きの完了、又は3.3章のジェネリックUE設定更新手続きの完了、又は3.4章のUEポリシー管理手続きの完了、又はSMのための手続きの完了等に基づいて、登録手続きを開始してもよい。尚、UEは、これらに限らず、任意のタイミングで登録手続きを実行することができる。 The UE may start the registration procedure when it has mobility across TAs. In other words, the UE may initiate the registration process when it moves to a TA that is different from the TA shown in the TA list it holds. In addition, the UE may initiate this procedure when the running backoff timer, or other timer, has expired. In addition, the UE may initiate the registration process when the context of each device needs to be updated due to disconnection or invalidation of the PDU session. In addition, the UE may initiate the registration process if there is a change in capability information and / or preferences regarding the establishment of the UE's PDU session. In addition, the UE may initiate the registration process on a regular basis. Furthermore, the UE will be registered based on the completion of the registration procedure in Chapter 3.2, the completion of the generic UE setting update procedure in Chapter 3.3, the completion of the UE policy management procedure in Chapter 3.4, or the completion of the procedure for SM. You may start the procedure. The UE is not limited to these, and can execute the registration procedure at any timing.
　なお、上述したUEがネットワークに登録していない状態(非登録状態)から登録された状態(登録状態)に遷移する為の手続きを、初期登録手続き(initial registration procedure)又は初期登録のための登録手続き(registration procedure for initial registration)であってよい。また、UEがネットワークに登録された状態(登録状態)で実行された登録手続きを、移動及び定期的な登録更新の為の登録手続き(registration procedure for mobility and periodic registration update)又は移動及び定期的な登録手続き(mobility and periodic registration procedure)であってよい。 In addition, the procedure for transitioning from the above-mentioned UE not registered in the network (unregistered state) to the registered state (registered state) is the initial registration procedure or registration for initial registration. It may be a procedure (registration procedure for initial registration). In addition, the registration procedure executed in the state where the UE is registered in the network (registration state) can be changed to the registration procedure (registration procedure for mobility and periodic registration update) or the move and periodic update. It may be a registration procedure (mobility and periodic registration procedure).
　図6のnew AMF(以下、単にAMFとも呼称する)は、本手続きによりUEが登録されるAMFを示し、old AMFは本手続きより前の登録手続きによりUEが登録されていたAMFを意味する。本手続き内で、AMFの変更が発生しない場合、old AMFとnew AMF間のインターフェース、及びold AMFとnew AMF間の手続きは発生せず、new AMFはold AMFと同じ装置であってよい。本実施形態では、AMFと記載した場合、new AMFを意味してもよいし、old AMFを意味してもよいし、またその両方を意味してもよい。 The new AMF (hereinafter, also simply referred to as AMF) in Fig. 6 indicates the AMF in which the UE is registered by this procedure, and the old AMF means the AMF in which the UE was registered by the registration procedure prior to this procedure. If the AMF is not changed in this procedure, the interface between the old AMF and the new AMF and the procedure between the old AMF and the new AMF do not occur, and the new AMF may be the same device as the old AMF. In the present embodiment, when AMF is described, it may mean new AMF, old AMF, or both.
　まず、UEは、new AMFに登録要求(Registration request)メッセージを送信することにより(S600)(S602)(S604)、登録手続きを開始する。具体的には、UEは、登録要求メッセージを含むRRCメッセージを、5G AN(又はgNB)に送信する(S600)。尚、登録要求メッセージは、N1インターフェース上で送受信されるNASメッセージである。また、RRCメッセージは、UEと5G AN(又はgNB)との間で送受信される制御メッセージであってよい。また、NASメッセージはNASレイヤで処理され、RRCメッセージはRRCレイヤで処理される。尚、NASレイヤはRRCレイヤよりも上位のレイヤである。 First, the UE starts the registration procedure by sending a registration request message to new AMF (S600) (S602) (S604). Specifically, the UE sends an RRC message including a registration request message to 5GAN (or gNB) (S600). The registration request message is a NAS message sent and received on the N1 interface. Further, the RRC message may be a control message transmitted / received between the UE and 5GAN (or gNB). In addition, NAS messages are processed in the NAS layer, and RRC messages are processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.
　ここで、UEは、第1から4の識別情報の内、1つ以上の識別情報を、登録要求メッセージ及び/又はRRCメッセージに含めて送信する事ができる。ここで、第1から4の識別情報は、2.7章の通りであってよい。さらに、UEは登録要求メッセージ及び/又はRRCメッセージに、本手続きの種類を示す識別情報を含めて送信してよい。ここで、本手続きの種類を示す識別情報は、5GS registration type IEであってよく、本手続きが初期登録の為(initial registration)、又は移動に伴う登録情報更新(mobility registration updating)の為、又は定期的な登録情報更新(periodic registration updating)の為、又は緊急時の登録(emergency registration)の為、の登録手続きであることを示す情報であってよい。特に、本手続きが、UEの移動に伴い、レジストレーションエリアが変更される場合に実行される場合、UEは、この5GS registration type IEをmobility registration updatingに設定してよい。 Here, the UE can send one or more of the identification information of the first to the fourth identification information by including it in the registration request message and / or the RRC message. Here, the identification information of the first to the fourth may be as described in Chapter 2.7. In addition, the UE may send the registration request message and / or the RRC message with identification information indicating the type of this procedure. Here, the identification information indicating the type of this procedure may be 5GS registration type IE, and this procedure is for initial registration (initial registration), or for updating registration information (mobility registration update) due to movement, or. It may be information indicating that the registration procedure is for periodic registration information update (periodic registration updating) or for emergency registration (emergency registration). In particular, if this procedure is executed when the registration area is changed due to the movement of the UE, the UE may set this 5GS registration type IE to mobility registration updating.
　UEは、UEがサポートする機能をネットワークに通知するために、UEの能力情報を登録要求メッセージ含めてもよい。ここで、UEの能力情報は、5GSの5GMM capabilityであってよい。 The UE may include the UE capability information in a registration request message in order to notify the network of the functions supported by the UE. Here, the capability information of the UE may be 5GMM capability of 5GS.
　UEはこれらの識別情報が、これらとは異なる制御メッセージ、例えば、RRCレイヤ(Radio Resource Control)よりも下位のレイヤ(例えば、MAC(Medium Access Control)レイヤ、RLC(Radio Link Control)レイヤ、PDCP(Packet Data Convergence Protocol)レイヤ)の制御メッセージに含めて送信してもよい。尚、UEは、これらの識別情報を送信することで、UEが各機能をサポートしていることを示してもよいし、UEの要求を示してもよいし、これら両方を示してもよい。さらに、複数の識別情報が送受信される場合、これらの識別情報の2以上の識別情報は、1以上の識別情報として構成されてもよい。尚、各機能のサポートを示す情報と、各機能の使用の要求を示す情報は、同じ識別情報として送受信されてもよいし、異なる識別情報として送受信されてもよい。 In the UE, these identification information is different from the control message, for example, a layer lower than the RRC layer (Radio Resource Control) (for example, MAC (Medium Access Control) layer, RLC (Radio Link Control) layer, PDCP ( It may be included in the control message of the Packet Data Convergence Protocol) layer) and transmitted. By transmitting these identification information, the UE may indicate that the UE supports each function, may indicate a request of the UE, or may indicate both of them. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.
　尚、UEは、第1から4の識別情報をネットワークに送信するか否かを、UEの能力情報、及び/又はUEポリシー、及び/又はUEの状態、及び/又はユーザの登録情報、及び/又はUEが保持するコンテキスト等に基づいて、選択、決定してもよい。 In addition, the UE determines whether or not to transmit the identification information of the first to the fourth to the network, the ability information of the UE and / or the UE policy, and / or the state of the UE, and / or the registration information of the user, and /. Alternatively, it may be selected and determined based on the context held by the UE.
　また、UEは、第1から4の識別情報のうち少なくとも1つ以上の情報を送信するか否かを決定する際に、以下の処理を実行してもよい。 Further, the UE may execute the following processing when deciding whether or not to transmit at least one or more of the identification information of the first to the fourth.
　例えば、UEは、コアネットワークから、すでに第15の識別情報及び第33の識別情報を受信している場合は、第15の識別情報と、第33の識別情報に基づいて、IMSサービスのために、第15の識別情報に含まれる1以上のS-NSSAI及び第33の識別情報に含まれる第36の識別情報で示されるS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを第3の識別情報として選択し、第3の識別情報を送信してよい。 For example, if the UE has already received the fifteenth and thirty-third identifications from the core network, it will be based on the fifteenth and thirty-third identifications for the IMS service. , 1 or more S-NSSAI contained in the 15th identification information and S-NSSAI indicated by the 36th identification information contained in the 33rd identification information, which is valid (available in the current registration area). N) S-NSSAI may be selected as the third identification information and the third identification information may be transmitted.
　また、UEは、コアネットワークから、すでに第15の識別情報及び第33の識別情報を受信している場合であって、第33の識別情報が第32の識別情報を含まないときは、第33に含まれる第36の識別情報で示されるS-NSSAIが、現在のレジストレーションエリアで有効である、又は現在のPLMN内で有効である、又は全てのPLMNで有効であるものと判断し、第15の識別情報と、第33の識別情報に基づいて、IMSサービスのために、第15の識別情報に含まれる1以上のS-NSSAI及び第33の識別情報に含まれる第36の識別情報で示されるS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを第3の識別情報として選択し、第3の識別情報を送信してよい。 Further, when the UE has already received the 15th identification information and the 33rd identification information from the core network and the 33rd identification information does not include the 32nd identification information, the 33rd identification information is included. It is determined that the S-NSSAI indicated by the 36th identification information contained in the current registration area is valid in the current registration area, is valid in the current PLMN, or is valid in all PLMNs. Based on the 15 identification information and the 33rd identification information, for the IMS service, one or more S-NSSAI contained in the 15th identification information and the 36th identification information contained in the 33rd identification information. From the S-NSSAI shown, the S-NSSAI valid (available) in the current registration area may be selected as the third identification information and the third identification information may be transmitted.
　また、UEは、コアネットワークから、すでに第15の識別情報及び第33の識別情報を受信している場合に、第33の識別情報に含まれる第36の識別情報がPCFによってAllowed NSSAIの中から選択された第1のS-NSSAIであるときは、第33の識別情報に基づいて、IMSサービスのために、第36の識別情報で示される第1のS-NSSAIを第3の識別情報として選択し、第3の識別情報を送信してよい。 Further, when the UE has already received the 15th identification information and the 33rd identification information from the core network, the 36th identification information included in the 33rd identification information is stored in the Allowed NSSAI by the PCF. When it is the selected first S-NSSAI, the first S-NSSAI indicated by the 36th identification information is used as the third identification information for the IMS service based on the 33rd identification information. You may choose to send a third identification.
　また、UEは、コアネットワークから、すでに第15の識別情報及び第33の識別情報を受信している場合は、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるか否かを確認し、第36の識別情報が第15の識別情報に含まれる場合は、IMSサービスのために、第36の識別情報を第3の識別情報として選択し、第3の識別情報を送信してよい。また、UEは、第36の識別情報が第15の識別情報に含まれるか否かを確認し、第36の識別情報が第15の識別情報に含まれない場合は、IMSサービスのために、第36の識別情報を第3の識別情報として選択しなくてよい。この場合において、UEは、第3の識別情報を送信しなくてよい。 If the UE has already received the 15th identification information and the 33rd identification information from the core network, the 36th identification information included in the 33rd identification information is included in the 15th identification information. If the 36th identification information is included in the 15th identification information, select the 36th identification information as the 3rd identification information and select the 3rd identification information for the IMS service. Information may be sent. The UE also checks whether the 36th identification information is included in the 15th identification information, and if the 36th identification information is not included in the 15th identification information, for the IMS service, It is not necessary to select the 36th identification information as the third identification information. In this case, the UE does not have to transmit the third identification information.
　さらに、UEは、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるか否かを、アクセスごとに確認してもよい。すなわち、UEは、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるか否かを、3GPPアクセスおよびnon-3GPPアクセスの夫々に対して、確認してもよい。例えば、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるが、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれない場合、UEは、IMSサービスのために、第36の識別情報を第3の識別情報として選択し、3GPPアクセス経由で、第3の識別情報を送信してよい。また、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれず、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれる場合、UEは、IMSサービスのために、第36の識別情報を第3の識別情報として選択し、non-3GPPアクセス経由で、第3の識別情報を送信してよい。また、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれ、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれる場合、UEは、IMSサービスのために、第36の識別情報を第3の識別情報として選択し、3GPPアクセスとnon-3GPPアクセスのどちらのアクセスから送信するかを選択し、選択したアクセス経由で、第3の識別情報を送信してよい。また、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれず、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれない場合、UEは、IMSサービスのために、第36の識別情報を第3の識別情報として選択しなくてよい。この場合において、UEは、第3の識別情報を送信しなくてよい。 Further, the UE may confirm whether or not the 36th identification information included in the 33rd identification information is included in the 15th identification information for each access. That is, the UE may confirm whether or not the 36th identification information contained in the 33rd identification information is included in the 15th identification information for each of the 3GPP access and the non-3GPP access. .. For example, for 3GPP access, the 36th identification information contained in the 33rd identification information is included in the 15th identification information, but for non-3GPP access, the 36th identification information included in the 33rd identification information is included. If the identification information of is not included in the 15th identification information, the UE selects the 36th identification information as the 3rd identification information for the IMS service and obtains the 3rd identification information via 3GPP access. You may send it. Also, for 3GPP access, the 36th identification information included in the 33rd identification information is not included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information. If the identification information is included in the 15th identification information, the UE selects the 36th identification information as the third identification information for the IMS service and provides the third identification information via non-3GPP access. You may send it. Further, for 3GPP access, the 36th identification information included in the 33rd identification information is included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information is included. If the identification information is included in the 15th identification information, the UE selects the 36th identification information as the 3rd identification information for the IMS service and sends it from either 3GPP access or non-3GPP access. You may choose to do so and send the third identification information via the selected access. Also, for 3GPP access, the 36th identification information included in the 33rd identification information is not included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information. If the identification information is not included in the fifteenth identification information, the UE may not select the 36th identification information as the third identification information for the IMS service. In this case, the UE does not have to transmit the third identification information.
　また、UEは、コアネットワークから、すでに第11の識別情報を受信している場合は、第11の識別情報と、IMSサービスとを対応付けて記憶してよい。この場合において、第11の識別情報がすべてのPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信していないときは、新しいレジストレーションエリアが現在のPLMNに属するか否かに関わらず、UEは、IMSサービスのために、第11の識別情報で示されるデフォルトS-NSSAIを第1の識別情報として選択し、第1の識別情報を送信してよい。また、第11の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属する場合は、UEは、IMSサービスのために、第11の識別情報で示されるデフォルトS-NSSAIを第1の識別情報として選択し、第1の識別情報を送信してよい。また、第11の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属さない場合は、UEは、IMSサービスのために、第11の識別情報で示されるデフォルトS-NSSAIを第1の識別情報として選択しなくてよい。このとき、UEは、第1の識別情報は送信しなくてよい。また、第11の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しているときは、UEは、IMSサービスのために、第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を第3の識別情報として選択し、第3の識別情報を送信してよい。 If the UE has already received the eleventh identification information from the core network, the UE may store the eleventh identification information in association with the IMS service. In this case, the eleventh identification information is valid in all PLMNs, and the UE moves to a new registration area different from the current registration area, and the UE is a new registration area. If the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid (supports IMS service) has not been received in the new system. Regardless of whether the registration area belongs to the current PLMN, the UE selects the default S-NSSAI indicated by the 11th identification information as the 1st identification information for the IMS service, and the 1st identification information. Identification information may be transmitted. Also, if the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE selects the default S-NSSAI indicated by the 11th identification information as the 1st identification information and sends the 1st identification information for the IMS service. It's okay. Also, if the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the registration area does not belong to the current PLMN, the UE may not select the default S-NSSAI indicated by the eleventh identifier as the first identifier for the IMS service. At this time, the UE does not have to transmit the first identification information. Also, if the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. When receiving the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall Select the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) as the third identification information for the IMS service, and the third identification information. Identification information may be transmitted.
　また、UEは、コアネットワークから、すでに第21の識別情報を受信している場合は、第21の識別情報と、IMSサービスとを対応付けて記憶してよい。この場合において、第21の識別情報がすべてのPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信していないときは、新しいレジストレーションエリアが現在のPLMNに属するか否かに関わらず、UEは、IMSサービスのために、第21の識別情報で示されるデフォルトS-NSSAIを第1の識別情報として選択し、第1の識別情報を送信してよい。また、第21の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属する場合は、UEは、IMSサービスのために、第21の識別情報で示されるデフォルトS-NSSAIを第1の識別情報として選択し、第1の識別情報を送信してよい。また、第21の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属さない場合は、UEは、IMSサービスのために、第21の識別情報で示されるデフォルトS-NSSAIを第1の識別情報として選択しなくてよい。このとき、UEは、第1の識別情報は送信しなくてよい。また、第21の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しているときは、UEは、IMSサービスのために、第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を第3の識別情報として選択し、第3の識別情報を送信してよい。 If the UE has already received the 21st identification information from the core network, the UE may store the 21st identification information in association with the IMS service. In this case, the 21st identification information is valid for all PLMNs, and the UE moves to a new registration area different from the current registration area, and the UE is a new registration area. If the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid (supports IMS service) has not been received in the new system. Regardless of whether the registration area belongs to the current PLMN, the UE selects the default S-NSSAI indicated by the 21st identification information as the 1st identification information for the IMS service, and the 1st identification information is used. Identification information may be transmitted. Also, if the 21st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE selects the default S-NSSAI indicated by the 21st identification information as the 1st identification information and sends the 1st identification information for the IMS service. It's okay. Also, if the 21st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the registration area does not belong to the current PLMN, the UE may not select the default S-NSSAI indicated by the 21st Distinguished Information as the 1st Distinguished Information for the IMS service. At this time, the UE does not have to transmit the first identification information. Also, if the 21st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. When receiving the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall Select the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) as the third identification information for the IMS service, and the third identification information. Identification information may be transmitted.
　また、UEは、コアネットワークから、すでに第31の識別情報を受信している場合は、第31の識別情報と、IMSサービスとを対応付けて記憶してよい。この場合において、第31の識別情報がすべてのPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信していないときは、新しいレジストレーションエリアが現在のPLMNに属するか否かに関わらず、UEは、IMSサービスのために、第31の識別情報で示されるデフォルトS-NSSAIを第1の識別情報として選択し、第1の識別情報を送信してよい。また、第31の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属する場合は、UEは、IMSサービスのために、第31の識別情報で示されるデフォルトS-NSSAIを第1の識別情報として選択し、第1の識別情報を送信してよい。また、第31の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属さない場合は、UEは、IMSサービスのために、第31の識別情報で示されるデフォルトS-NSSAIを第1の識別情報として選択しなくてよい。このとき、UEは、第1の識別情報は送信しなくてよい。また、第31の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しているときは、UEは、IMSサービスのために、第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を第3の識別情報として選択し、第3の識別情報を送信してよい。 If the UE has already received the 31st identification information from the core network, the UE may store the 31st identification information in association with the IMS service. In this case, the 31st identification information is valid for all PLMNs, and the UE moves to a new registration area different from the current registration area, and the UE is a new registration area. If the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid (supports IMS service) has not been received in the new system. Regardless of whether the registration area belongs to the current PLMN, the UE selects the default S-NSSAI indicated by the 31st identification information as the 1st identification information for the IMS service, and the 1st identification information. Identification information may be transmitted. Also, if the 31st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE selects the default S-NSSAI indicated by the 31st identification information as the 1st identification information and sends the 1st identification information for the IMS service. It's okay. Also, if the 31st identification information is valid in the current PLMN and the UE moves to a new registration area that is different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the registration area does not belong to the current PLMN, the UE may not select the default S-NSSAI indicated by the 31st Distinguished Information as the 1st Distinguished Information for the IMS service. At this time, the UE does not have to transmit the first identification information. Also, if the 31st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. When receiving the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall Select the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) as the third identification information for the IMS service, and the third identification information. Identification information may be transmitted.
　また、UEは、IMSサービスを用いた通信を行う場合に、IMSサービスをサポートする第1のS-NSSAIのレジストレーションエリアの有効範囲を知りたいとき、言い換えると、IMSサービスをサポートする第1のS-NSSAIを使用可能なレジストレーションエリアの情報を取得したいときは、第2の識別情報を送信してよい。 Also, when the UE wants to know the effective range of the registration area of the first S-NSSAI that supports the IMS service when communicating using the IMS service, in other words, the first that supports the IMS service. When you want to get the information of the registration area where S-NSSAI can be used, you may send the second identification information.
　また、UEは、コアネットワークから、すでに第12の識別情報及び第15の識別情報及び第33の識別情報を受信している場合、UEは、第33の識別情報を記憶し、さらに、第12の識別情報と、第15の識別情報、又は第15の識別情報に含まれるS-NSSAIと、を対応付けて記憶してよい。そして、UEは、IMSサービスのために、第12の識別情報と第15の識別情報と第33の識別情報に基づいて、第15の識別情報に含まれるS-NSSAI及び第36の識別情報で示される第1のS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを第3の識別情報として選択し、第3の識別情報を送信してよい。 Further, if the UE has already received the twelfth identification information, the fifteenth identification information, and the thirty-third identification information from the core network, the UE stores the thirty-third identification information, and further, the twelfth identification information is stored. The identification information of the above and the fifteenth identification information or the S-NSSAI included in the fifteenth identification information may be stored in association with each other. Then, for the IMS service, the UE uses the S-NSSAI and the 36th identification information contained in the 15th identification information based on the 12th identification information, the 15th identification information, and the 33rd identification information. From the first S-NSSAI shown, the S-NSSAI valid (available) in the current registration area may be selected as the third identification information and the third identification information may be transmitted.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、すでに第14の識別情報と、第15の識別情報及び/又は第16の識別情報と、を受信しているときは、UEは、第15の識別情報及び/又は第16の識別情報で示されるS-NSSAIと、IMSサービスとを対応付けて記憶するとともに、現在のレジストレーションエリアと、記憶したS-NSSAIに基づいて、要求するS-NSSAI(以下、Requested S-NSSAIとも呼称する)を選択し、そのS-NSSAIを送信してよい。 Further, when the UE has already received the 14th identification information, the 15th identification information and / or the 16th identification information from the core network when communicating using the IMS service, the UE has received the 14th identification information and / or the 16th identification information. , UE stores the S-NSSAI indicated by the 15th identification information and / or the 16th identification information in association with the IMS service, and is based on the current registration area and the stored S-NSSAI. Then, the requested S-NSSAI (hereinafter, also referred to as Requested S-NSSAI) may be selected and the S-NSSAI may be transmitted.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、すでに第12の識別情報と、第14の識別情報と、第15の識別情報及び/又は第16の識別情報と、を受信しているときは、UEは、第15の識別情報及び/又は第16の識別情報で示されるS-NSSAIと、IMSサービスと、第12の識別情報とを対応付けて記憶するとともに、現在のレジストレーションエリアと、記憶したS-NSSAIに基づいて、要求するS-NSSAIを選択し、そのS-NSSAIを送信してよい。 In addition, when communicating using the IMS service, the UE has already received the 12th identification information, the 14th identification information, the 15th identification information, and / or the 16th identification information from the core network. When receiving, the UE stores the S-NSSAI indicated by the 15th identification information and / or the 16th identification information, the IMS service, and the 12th identification information in association with each other. Based on the current registration area and the stored S-NSSAI, the requested S-NSSAI may be selected and the S-NSSAI may be transmitted.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、すでに第24の識別情報と、第25の識別情報及び/又は第26の識別情報と、を受信しているときは、UEは、第25の識別情報及び/又は第26の識別情報で示されるS-NSSAIと、IMSサービスとを対応付けて記憶するとともに、現在のレジストレーションエリアと、記憶したS-NSSAIに基づいて、要求するS-NSSAIを選択し、そのS-NSSAIを送信してよい。 In addition, when the UE has already received the 24th identification information, the 25th identification information, and / or the 26th identification information from the core network when performing communication using the IMS service, the UE has received the 24th identification information and / or the 26th identification information. , UE stores the S-NSSAI indicated by the 25th identification information and / or the 26th identification information in association with the IMS service, and is based on the current registration area and the stored S-NSSAI. Then, you may select the requested S-NSSAI and send the S-NSSAI.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、すでに第22の識別情報と、第24の識別情報と、第25の識別情報及び/又は第26の識別情報と、を受信しているときは、UEは、第25の識別情報及び/又は第26の識別情報で示されるS-NSSAIと、IMSサービスと、第22の識別情報とを対応付けて記憶するとともに、現在のレジストレーションエリアと、記憶したS-NSSAIに基づいて、要求するS-NSSAIを選択し、そのS-NSSAIを送信してよい。 In addition, when communicating using the IMS service, the UE has already received the 22nd identification information, the 24th identification information, the 25th identification information, and / or the 26th identification information from the core network. When receiving, the UE stores the S-NSSAI indicated by the 25th identification information and / or the 26th identification information, the IMS service, and the 22nd identification information in association with each other. Based on the current registration area and the stored S-NSSAI, the requested S-NSSAI may be selected and the S-NSSAI may be transmitted.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、すでに第15の識別情報を受信しているときは、第15の識別情報に含まれるS-NSSAIを構成するSST又はSDの値がIMSサービスを示すようなS-NSSAIである場合、そのS-NSSAIを第3の識別情報として選択し、第3の識別情報を送信してもよい。 In addition, when the UE communicates using the IMS service and has already received the 15th identification information from the core network, the UE is an SST or SST that constitutes S-NSSAI included in the 15th identification information. If the value of SD is S-NSSAI that indicates the IMS service, that S-NSSAI may be selected as the third identification information and the third identification information may be transmitted.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、すでに第25の識別情報を受信しているときは、第25の識別情報に含まれるS-NSSAIを構成するSST又はSDの値がIMSサービスを示すようなS-NSSAIである場合、そのS-NSSAIを第3の識別情報として選択し、第3の識別情報を送信してもよい。 If the UE has already received the 25th identification information from the core network when communicating using the IMS service, the UE may use the SST or SST that constitutes the S-NSSAI included in the 25th identification information. If the value of SD is S-NSSAI that indicates the IMS service, that S-NSSAI may be selected as the third identification information and the third identification information may be transmitted.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、すでに第15の識別情報を受信しており、かつ、第15の識別情報に含まれる(IMSをサポートする)第1のS-NSSAIの位置や順番と、IMSサービスとの対応付けが、仕様によって予め規定されているか又はオペレータによって予め規定されていることを知っているときは、UEは、第15の識別情報に含まれる1以上のS-NSSAIの中から、その情報に基づいて、IMSサービスをサポートする第1のS-NSSAIを選択し、第1のS-NSSAIを第3の識別情報として送信してもよい。このように、UEは、Allowed NSSAIにおける第1のS-NSSAIの位置を予め知っている場合には、コアネットワークから、第14の識別情報、及び/又は第24の識別情報、及び/又は第34の識別情報のような、IMSサービスと第1のS-NSSAIとの対応関係を明示的に示す情報を受信していなくても、第1のS-NSSAIを特定できてよい。 Further, when communicating using the IMS service, the UE has already received the fifteenth identification information from the core network and is included in the fifteenth identification information (supports IMS). If the UE knows that the location and order of the S-NSSAI in the S-NSSAI and its association with the IMS service is pre-specified by the specification or pre-specified by the operator, the UE will use the fifteenth identification information. Even if the first S-NSSAI that supports the IMS service is selected from among one or more S-NSSAI included and the first S-NSSAI is sent as the third identification information based on that information. good. In this way, if the UE knows the position of the first S-NSSAI in Allowed NSSAI in advance, the 14th identification information and / or the 24th identification information and / or the first from the core network. The first S-NSSAI may be identified without receiving information that explicitly indicates the correspondence between the IMS service and the first S-NSSAI, such as the identification information of 34.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、すでに第25の識別情報を受信しており、かつ、第25の識別情報に含まれる(IMSをサポートする)第1のS-NSSAIの位置や順番と、IMSサービスとの対応付けが、仕様によって予め規定されているか又はオペレータによって予め規定されていることを知っているときは、UEは、第25の識別情報に含まれる1以上のS-NSSAIの中から、その情報に基づいて、IMSサービスをサポートする第1のS-NSSAIを選択し、第1のS-NSSAIを第3の識別情報として送信してもよい。このように、UEは、Allowed NSSAIにおける第1のS-NSSAIの位置を予め知っている場合には、コアネットワークから、第14の識別情報、及び/又は第24の識別情報、及び/又は第34の識別情報のような、IMSサービスと第1のS-NSSAIとの対応関係を明示的に示す情報を受信していなくても、第1のS-NSSAIを特定できてよい。 In addition, when communicating using the IMS service, the UE has already received the 25th identification information from the core network and is included in the 25th identification information (supports IMS). If the UE knows that the location and order of the S-NSSAI in the S-NSSAI and its association with the IMS service is pre-specified by the specification or pre-specified by the operator, the UE will use the 25th identification information. Even if the first S-NSSAI that supports the IMS service is selected from among one or more S-NSSAI included and the first S-NSSAI is sent as the third identification information based on that information. good. In this way, if the UE knows the position of the first S-NSSAI in Allowed NSSAI in advance, the 14th identification information and / or the 24th identification information and / or the first from the core network. The first S-NSSAI may be identified without receiving information that explicitly indicates the correspondence between the IMS service and the first S-NSSAI, such as the identification information of 34.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、すでに第13の識別情報及び第15の識別情報を受信している場合は、第13の識別情報で示される情報に基づいて、第15の識別情報に含まれる1以上のS-NSSAIの中から、(IMSをサポートする)第1のS-NSSAIを選択し、第1のS-NSSAIを第3の識別情報として送信してもよい。 In addition, when the UE communicates using the IMS service, if the 13th identification information and the 15th identification information have already been received from the core network, the information indicated by the 13th identification information is used. Based on this, the first S-NSSAI (which supports IMS) is selected from the one or more S-NSSAI contained in the fifteenth identification information, and the first S-NSSAI is used as the third identification information. You may send it.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、すでに第23の識別情報及び第25の識別情報を受信している場合は、第23の識別情報で示される情報に基づいて、第25の識別情報に含まれる1以上のS-NSSAIの中から、(IMSをサポートする)第1のS-NSSAIを選択し、第1のS-NSSAIを第3の識別情報として送信してもよい。 In addition, when the UE communicates using the IMS service, if it has already received the 23rd identification information and the 25th identification information from the core network, it will be the information indicated by the 23rd identification information. Based on this, the first S-NSSAI (which supports IMS) is selected from among one or more S-NSSAIs included in the 25th identification information, and the first S-NSSAI is used as the third identification information. You may send it.
　また、UEが、予め、IMSサービスと、default S-NSSAI及び/又は第1のS-NSSAIと、を対応づけて記憶している場合、UEは、IMSサービスを用いた通信を行う場合は、第1の識別情報及び/又は第3の識別情報を送信してもよい。 If the UE stores the IMS service in advance in association with the default S-NSSAI and / or the first S-NSSAI, the UE may use the IMS service for communication. The first identification information and / or the third identification information may be transmitted.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、すでに第16の識別情報と第14の識別情報とを含む第15の識別情報を受信している場合、第16の識別情報で示される第1のS-NSSAIを第3の識別情報として送信してもよい。 Further, when the UE communicates using the IMS service, if the UE has already received the 15th identification information including the 16th identification information and the 14th identification information from the core network, the 16th identification information is used. The first S-NSSAI indicated by the identification information may be transmitted as the third identification information.
　尚、UEは、選択したS-NSSAI及び/又は第1の識別情報及び/又は選択した第3の識別情報を送信する場合、S-NSSAI及び/又は第1の識別情報及び/又は第3の識別情報を含むrequested NSSAIを送信してもよい。 When the UE transmits the selected S-NSSAI and / or the first identification information and / or the selected third identification information, the S-NSSAI and / or the first identification information and / or the third identification information. You may send a requested NSSAI containing the identification information.
　また、第3の識別情報は、1以上送信できてよい。この場合、1以上の第3の識別情報を含むrequested NSSAIを送信してよい。また、第1から第3の識別情報のうちの少なくとも1つを送信することは、第4の識別情報を送信することを意味してもよい。 Also, one or more third identification information may be transmitted. In this case, a requested NSSAI containing one or more third identification information may be transmitted. Further, transmitting at least one of the first to third identification information may mean transmitting the fourth identification information.
　UEは、登録要求メッセージ及び/又は登録要求メッセージが含まれるRRCメッセージに、第1から4の識別情報以外も含めてもよく、例えばUE ID及び/又はPLMN ID及び/又はAMF識別情報を含めて送信してもよい。ここで、AMF識別情報とは、AMF、又はAMFの集合を識別する情報であってよく、例えば、5G-S-TMSI(5G S-Temporary Mobile Subscription Identifier)やGUAMI(Globally Unique AMF Identifier)であってよい。 The UE may include registration request messages and / or RRC messages containing registration request messages other than the identification information of 1 to 4, for example, including UEID and / or PLMNID and / or AMF identification information. You may send it. Here, the AMF identification information may be AMF or information that identifies a set of AMF, for example, 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) or GUAMI (Globally Unique AMF Identifier). It's okay.
　次に、5G AN(又はgNB)は、登録要求メッセージを含むRRCメッセージを受信すると、登録要求メッセージを転送するAMFを選択する(S602)。尚、5G AN(又はgNB)は、登録要求メッセージ、及び/又はRRCメッセージ、に含まれる1又は複数の識別情報に基づいて、AMFを選択することができる。具体的には、5G AN(又はgNB)は、第1から4の識別情報の内、少なくとも1つの識別情報に基づいて、登録要求メッセージの送信先のnew AMFを選択してもよい。 Next, when 5GAN (or gNB) receives the RRC message including the registration request message, it selects the AMF to which the registration request message is forwarded (S602). The 5GAN (or gNB) can select AMF based on one or more identification information contained in the registration request message and / or the RRC message. Specifically, the 5GAN (or gNB) may select the new AMF to which the registration request message is sent based on at least one of the identification information of the first to the fourth identification information.
　そして、5G AN(又はgNB)は、登録要求メッセージ及び/又はRRCメッセージに含まれる識別情報、及び/又は登録要求メッセージを、選択したnew AMFに転送する(S604)。 Then, 5GAN (or gNB) forwards the identification information and / or the registration request message contained in the registration request message and / or the RRC message to the selected new AMF (S604).
　次に、new AMFは、登録要求メッセージを受信した場合、第1の条件判別を実行することができる。第1の条件判別とは、ネットワーク(又はnew AMF)がUEの要求を受諾するか否かを判別するためのものである。new AMFは、第1の条件判別が真の場合、S606からS612 の手続きを実行する。一方で、new AMFは、第1の条件判別が偽の場合、S606からS608の手続きを実行せず、S610の手続きを実行してもよい。 Next, when the new AMF receives the registration request message, it can execute the first condition determination. The first conditional determination is for determining whether or not the network (or new AMF) accepts the UE request. new AMF executes the procedure from S606 to S612 if the first condition determination is true. On the other hand, new AMF may execute the procedure of S610 without executing the procedure of S606 to S608 when the first condition determination is false.
　また、new AMFは、UEコンテキストをold AMFに要求して、及びUEコンテキストをold AMFから受信(S606、S608)した後に第1の条件判別をしてもよい。その場合、new AMFは、第1の条件判別が真の場合、S610及びS612を実行する。一方で、new AMFは、第1の条件判別が偽の場合、S610を実行してもよい。 Further, the new AMF may request the UE context from the old AMF and may determine the first condition after receiving the UE context from the old AMF (S606, S608). In that case, new AMF executes S610 and S612 if the first condition determination is true. On the other hand, new AMF may execute S610 when the first condition determination is false.
　尚、第1の条件判別が真の場合、S610で送信及び受信される制御メッセージは、登録受諾(Registration accept)メッセージであって良いし、第1の条件判別が偽である場合、S610で送信及び受信される制御メッセージは、登録拒絶(Registration reject)メッセージであってよい。 If the first condition determination is true, the control message transmitted and received by the S610 may be a registration acceptance message, and if the first condition determination is false, the control message is transmitted by the S610. And the control message received may be a Registration reject message.
　また、第1の条件判別は、登録要求メッセージの受信、及び/又は登録要求メッセージに含まれる各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、実行されてもよい。 In addition, the first condition determination is the reception of the registration request message and / or each identification information contained in the registration request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and It may be executed based on / or the state of the network and / or the user's registration information and / or the context held by AMF.
　例えば、UEの要求をネットワークが許可する場合、第1の条件判別は真であり、UEの要求をネットワークが許可しない場合、第1の条件判別は偽でよい。また、UEの登録先のネットワーク、及び/又はネットワーク内の装置が、UEの要求する機能をサポートしている場合、第1の条件判別は真であり、UEの要求する機能をサポートしていない場合、第1の条件判別は偽でよい。さらに、送受信される識別情報が許可される場合、第1の条件判別は真であり、送受信される識別情報が許可されない場合、第1の条件判別は偽でよい。 For example, if the network permits the UE request, the first condition determination is true, and if the network does not allow the UE request, the first condition determination may be false. Also, if the network to which the UE is registered and / or the devices in the network support the functions required by the UE, the first condition determination is true and does not support the functions required by the UE. In this case, the first condition determination may be false. Further, if the transmitted / received identification information is permitted, the first conditional determination may be true, and if the transmitted / received identification information is not permitted, the first conditional determination may be false.
　また、new AMFは、UEに許可するNSSAI(Allowed NSSAI)がある場合、第1の条件判別は真であってよい。また、new AMFは、UEに許可するNSSAI(Allowed NSSAI)がある場合は、そのNSSAIに、IMSをサポートする第1のS-NSSAIが含まれるか否かに関わらず、第1の条件判別は真であってもよい。また、new AMFは、UEに許可するNSSAI(Allowed NSSAI)がある場合であって、UEに許可するIMSをサポートする第1のS-NSSAIがある場合は、第1の条件判別は真であってもよい。また、new AMFは、UEに許可するNSSAI(Allowed NSSAI)がある場合であって、UEに許可するIMSをサポートする第1のS-NSSAIがない場合は、第1の条件判別は偽であってもよい。 Also, for new AMF, if there is NSSAI (Allowed NSSAI) allowed for UE, the first condition determination may be true. In addition, if new AMF has an NSSAI (Allowed NSSAI) allowed for the UE, the first condition determination is performed regardless of whether or not the NSSAI includes the first S-NSSAI that supports IMS. It may be true. Also, if new AMF has an NSSAI (Allowed NSSAI) allowed for the UE and there is a first S-NSSAI that supports IMS allowed for the UE, the first condition determination is true. You may. In addition, if new AMF has NSSAI (Allowed NSSAI) allowed for UE and there is no first S-NSSAI that supports IMS allowed for UE, the first condition determination is false. You may.
　次に、new AMFは、new AMFがUEから受信したメッセージに含まれるAMF識別情報に示されるAMFと異なる場合、S606、S608の手続きを実行し、new AMFがUEから受信したメッセージに含まれるAMF識別情報に示されるAMFと同じ場合、S606、S608の手続きを実行しない。言い換えると、本手続きによりAMFの変更が発生した場合、S606、S608の手続きは実行され、AMFの変更が発生しない場合は、S606、S608の手続きはスキップされる。 Next, if the new AMF is different from the AMF shown in the AMF identification information included in the message received from the UE, the new AMF executes the procedures of S606 and S608, and the new AMF is included in the message received from the UE. If it is the same as the AMF shown in the identification information, the procedure of S606 and S608 is not executed. In other words, if the AMF change occurs due to this procedure, the S606 and S608 procedures are executed, and if the AMF change does not occur, the S606 and S608 procedures are skipped.
　UEコンテキストの転送手続き(S606、S608)について説明する。new AMFは、AMF識別情報に示されるAMFをold AMFとして、old AMFにUEコンテキストの要求メッセージを送信する(S606)。old AMFは受信したUEコンテキストの要求メッセージに基づき、new AMFへUEコンテキストを送信する。New AMFは、受信したUEコンテキストに基づき、UEコンテキストを生成する。 The UE context transfer procedure (S606, S608) will be explained. new AMF sends a UE context request message to old AMF with the AMF shown in the AMF identification information as old AMF (S606). The old AMF sends the UE context to the new AMF based on the received UE context request message. New AMF creates a UE context based on the received UE context.
　ここで、new AMFからold AMFに送信されるUEコンテキストには、UE IDやallowed NSSAIが含まれていてもよい。更に、UEコンテキストには、configured NSSAI及び/又はrejected NSSAI、NSSAI及び/又はpending NSSAI、及び/又は第1のNSSAI、が含まれていてもよい。また、UEコンテキストに含まれるallowed NSSAI、及び/又はconfigured NSSAI、及び/又はrejected NSSAI、及び/又はpending NSSAI、及び/又は第1のNSSAI、 及び各NSSAIに含まれるS-NSSAI、はUEへの通知が完了しているか否かの情報が紐づけられていてもよい。 Here, the UE context sent from new AMF to old AMF may include UE ID and allowed NSSAI. Further, the UE context may include configured NSSAI and / or rejected NSSAI, NSSAI and / or pending NSSAI, and / or a first NSSAI. Also, allowed NSSAI and / or configured NSSAI and / or rejected NSSAI and / or pending NSSAI and / or the first NSSAI and / or S-NSSAI included in each NSSAI included in the UE context are sent to the UE. Information on whether or not the notification has been completed may be linked.
　次に、new AMFは、第1の条件判別の決定に基づいて、及び/又old AMFからUEコンテキストの受信に基づき、UEへ制御メッセージを送信する(S610)。制御メッセージは、登録受諾メッセージ又は登録拒絶メッセージであってよい。 Next, the new AMF sends a control message to the UE based on the determination of the first condition determination and / or the reception of the UE context from the old AMF (S610). The control message may be a registration acceptance message or a registration refusal message.
　ここで、new AMFは、制御メッセージに、少なくとも第11から17の識別情報の内、1つ以上の識別情報を含めて送信してもよい。ここで、第11から17の識別情報は、2.7章の通りであってよい。尚、AMFは、これらの識別情報及び/又は制御メッセージを送信することで、ネットワークが各機能をサポートしていることを示してもよいし、UEの要求が受諾されたことを示してもよいし、UEからの要求を許可していない事を示してもよいし、これらを組み合わせた情報を示してもよい。さらに、複数の識別情報が送受信される場合、これらの識別情報の2以上の識別情報は、1以上の識別情報として構成されてもよい。尚、各機能のサポートを示す情報と、各機能の使用の許可を示す情報は、同じ識別情報として送受信されてもよいし、異なる識別情報として送受信されてもよい。 Here, the new AMF may send the control message including at least one identification information out of the 11th to 17th identification information. Here, the identification information of Chapters 11 to 17 may be as described in Chapter 2.7. It should be noted that the AMF may indicate that the network supports each function by transmitting these identification information and / or a control message, or may indicate that the request of the UE has been accepted. However, it may indicate that the request from the UE is not permitted, or it may indicate information that combines these. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the permission to use each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.
　また、AMFは、第11から17の識別情報の内、どの識別情報を制御メッセージに含めるかを、受信した各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、選択、決定してもよい。 In addition, AMF shall indicate which of the 11th to 17th identification information is included in the control message, each identification information received, and / or subscriber information, and / or network capability information, and / or. Selections and decisions may be made based on operator policy and / or network status and / or user registration information and / or context held by AMF.
　例えば、new AMFは、UEから第1から4の識別情報のうちの少なくとも１つを受信した場合、第11から17の識別情報のうち、少なくとも1つの識別情報を制御メッセージに含めて送信してよい。 For example, when new AMF receives at least one of the identification information of the first to the fourth from the UE, the new AMF sends at least one of the identification information of the eleventh to the 17th by including the identification information in the control message. good.
　また、new AMFは、UEから第1から4の識別情報のうちの少なくとも1つを受信した場合であって、前回の登録手続きから、UEの設定情報を更新した場合に、第11から17の識別情報に更新された情報を含めて送信してよい。 In addition, new AMF receives at least one of the identification information 1 to 4 from the UE, and when the setting information of the UE is updated from the previous registration procedure, the 11th to 17th The identification information may be sent including the updated information.
　また、AMFは、受信した各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、登録受諾メッセージを送信することで、UEの要求が受諾されたことを示してもよいし、登録拒絶メッセージを送信することでUEの要求が拒絶されたことを示してもよい。 AMF also receives each 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. The registration acceptance message may be sent to indicate that the UE request has been accepted, or the registration refusal message has been sent to indicate that the UE request has been rejected, based on the context held by the AMF. May be shown.
　次に、UEは、5G AN(gNB)介して、制御メッセージを受信する(S610)と、制御メッセージ、及び/又は受信した情報の内容を認識してよい。 Next, the UE may recognize the content of the control message and / or the received information when the control message is received (S610) via 5GAN (gNB).
　例えば、制御メッセージが登録受諾メッセージである場合、UEは、登録受諾メッセージを受信することで、登録要求メッセージによるUEの要求が受諾されたこと、及び登録受諾メッセージに含まれる各種の識別情報の内容を認識することができる。また、制御メッセージが登録拒絶メッセージである場合、UEは、登録拒絶メッセージを受信することで、登録要求メッセージによるUEの要求が拒絶されたこと、及び登録拒絶メッセージに含まれる各種の識別情報の内容を認識することができる。また、UEは、登録要求メッセージを送信した後、所定の期間が経過しても、制御メッセージを受信しない場合には、UEの要求が拒絶されたことを認識してもよい。 For example, when the control message is a registration acceptance message, the UE receives the registration acceptance message so that the UE's request by the registration request message is accepted, and the contents of various identification information contained in the registration acceptance message. Can be recognized. Further, when the control message is a registration refusal message, the UE receives the registration refusal message, so that the UE's request by the registration request message is rejected, and the contents of various identification information included in the registration refusal message. Can be recognized. Further, the UE may recognize that the request of the UE has been rejected if the control message is not received within a predetermined period after the registration request message is transmitted.
　また、UEは、第11から17の識別情報のうち少なくとも1つ以上の情報の受信、及び/又は制御メッセージの受信に基づき、以下の処理を実行してもよい。尚、UEは、これらの処理を、本手続き中、又は本手続き完了後に実行してもよい。 Further, the UE may execute the following processing based on the reception of at least one or more of the identification information of the 11th to 17th and / or the reception of the control message. The UE may execute these processes during this procedure or after the procedure is completed.
　例えば、UEは、コアネットワークから、すでに第33の識別情報を受信している場合に、本手続きにおいて第15の識別情報を受信したときであって、IMSサービスのためのPDUセッションの確立を要求するときは、第15の識別情報と、第33の識別情報に基づいて、第15の識別情報に含まれる1以上のS-NSSAI及び第33の識別情報に含まれる第36の識別情報で示されるS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 For example, the UE requests the establishment of a PDU session for the IMS service when it receives the 15th identification information in this procedure when it has already received the 33rd identification information from the core network. When doing so, it is indicated by one or more S-NSSAI contained in the 15th identification information and the 36th identification information contained in the 33rd identification information based on the 15th identification information and the 33rd identification information. Select a valid (available) S-NSSAI in the current registration area from the S-NSSAI and send a registration request message containing the S-NSSAI, or PDU with the S-NSSAI. A session establishment request message may be sent.
　また、UEは、コアネットワークから、すでに第15の識別情報及び第33の識別情報を受信している場合であって、第33の識別情報が第32の識別情報を含まないときは、第33に含まれる第36の識別情報で示されるS-NSSAIが、現在のレジストレーションエリアで有効である、又は現在のPLMN内で有効である、又は全てのPLMNで有効であるものと判断し、第15の識別情報と、第33の識別情報に基づいて、IMSサービスのために、第15の識別情報に含まれる1以上のS-NSSAI及び第33の識別情報に含まれる第36の識別情報で示されるS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 Further, when the UE has already received the 15th identification information and the 33rd identification information from the core network and the 33rd identification information does not include the 32nd identification information, the 33rd identification information is included. It is determined that the S-NSSAI indicated by the 36th identification information contained in the current registration area is valid in the current registration area, is valid in the current PLMN, or is valid in all PLMNs. Based on the 15 identification information and the 33rd identification information, for the IMS service, one or more S-NSSAI contained in the 15th identification information and the 36th identification information contained in the 33rd identification information. From the S-NSSAI shown, select a valid (available) S-NSSAI in the current registration area and send a registration request message containing that S-NSSAI, or with that S-NSSAI. A PDU session establishment request message may be sent.
　また、UEは、コアネットワークから、第15の識別情報を受信したときは、UEは、第15の識別情報、又は第15の識別情報に含まれるS-NSSAIを記憶してよい。そして、UEは、第33の識別情報を受信した後に、IMSサービスのためのPDUセッションの確立を要求するときには、第15の識別情報と、第33の識別情報に基づいて、第15の識別情報に含まれる1以上のS-NSSAI及び第33の識別情報に含まれる第36の識別情報で示されるS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。尚、選択されたS-NSSAIが、現在のレジストレーションエリアで有効(使用可能)であるか否かは、第32の識別情報に基づいて、決定されてもよい。 Further, when the UE receives the fifteenth identification information from the core network, the UE may store the fifteenth identification information or the S-NSSAI included in the fifteenth identification information. Then, when the UE requests the establishment of a PDU session for the IMS service after receiving the 33rd identification information, the 15th identification information and the 15th identification information based on the 33rd identification information are used. Among the one or more S-NSSAI contained in the S-NSSAI and the S-NSSAI indicated by the 36th identification information contained in the 33rd identification information, the S-NSSAI valid (usable) in the current registration area is selected. You may select and send a registration request message containing the S-NSSAI, or send a PDU session establishment request message with the S-NSSAI. Whether or not the selected S-NSSAI is valid (usable) in the current registration area may be determined based on the 32nd identification information.
　また、UEは、コアネットワークから、すでに第33の識別情報を受信している場合に、本手続きにおいて第15の識別情報を受信し、第33の識別情報に含まれる第36の識別情報がPCFによってAllowed NSSAIの中から選択された第1のS-NSSAIであり、かつ、IMSサービスのためのPDUセッションの確立を要求するときは、第33の識別情報に基づいて、第1のS-NSSAI(第33の識別情報に含まれる第36の識別情報)を選択し、第1のS-NSSAIを含む登録要求メッセージを送信するか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 Further, when the UE has already received the 33rd identification information from the core network, the UE receives the 15th identification information in this procedure, and the 36th identification information included in the 33rd identification information is the PCF. The first S-NSSAI selected from Allowed NSSAI by, and when requesting the establishment of a PDU session for the IMS service, the first S-NSSAI is based on the 33rd identification information. Select (36th identification information contained in the 33rd identification information) and send a registration request message containing the first S-NSSAI, or send a PDU session establishment request message with the first S-NSSAI. You may send it.
　また、UEは、コアネットワークから、すでに第33の識別情報を受信している場合に、本手続きにおいて第15の識別情報を受信したときであって、IMSサービスのためのPDUセッションの確立を要求するときは、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるか否かを確認し、第36の識別情報が第15の識別情報に含まれる場合は、第36の識別情報で示される第1のS-NSSAIを選択し、第1のS-NSSAIを含む登録要求メッセージを送信するか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。また、UEは、第36の識別情報が第15の識別情報に含まれるか否かを確認し、第36の識別情報が第15の識別情報に含まれない場合は、IMSサービスのために、第36の識別情報で示される第1のS-NSSAIを選択せず、第1のS-NSSAIを含む登録要求メッセージを送信しないか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信しなくてよい。 In addition, the UE requests the establishment of a PDU session for the IMS service when the 15th identification information is received in this procedure when the 33rd identification information has already been received from the core network. When doing so, check whether the 36th identification information included in the 33rd identification information is included in the 15th identification information, and if the 36th identification information is included in the 15th identification information, Select the first S-NSSAI indicated by the 36th identification and send a registration request message containing the first S-NSSAI, or send a PDU session establishment request message with the first S-NSSAI. You can do it. The UE also checks whether the 36th identification information is included in the 15th identification information, and if the 36th identification information is not included in the 15th identification information, for the IMS service, Do not select the first S-NSSAI indicated by the 36th identification information and do not send a registration request message containing the first S-NSSAI, or send a PDU session establishment request message with the first S-NSSAI. You don't have to send it.
　さらに、UEは、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるか否かを、アクセスごとに確認してもよい。すなわち、UEは、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるか否かを、3GPPアクセスおよびnon-3GPPアクセスの夫々に対して、確認してもよい。例えば、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるが、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれない場合、UEは、IMSサービスのために、第36の識別情報で示される第1のS-NSSAIを含む登録要求メッセージを、3GPPアクセス経由で、送信するか、又は第36の識別情報で示される第1のS-NSSAIとともに、PDUセッション確立要求メッセージを、3GPPアクセス経由で、送信してよい。また、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれず、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれる場合、UEは、IMSサービスのために、第36の識別情報で示される第1のS-NSSAIを含む登録要求メッセージを、non-3GPPアクセス経由で、送信するか、又は第36の識別情報で示される第1のS-NSSAIとともに、PDUセッション確立要求メッセージを、non-3GPPアクセス経由で、送信してよい。また、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれ、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれる場合、UEは、IMSサービスのために、3GPPアクセスとnon-3GPPアクセスのどちらのアクセスから送信するかを選択し、選択したアクセス経由で、第36の識別情報で示される第1のS-NSSAIを含む登録要求メッセージを送信するか、又は第36の識別情報で示される第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。また、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれず、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれない場合、UEは、IMSサービスのために、第36の識別情報で示される第1のS-NSSAIを選択せず、第1のS-NSSAIを含む登録要求メッセージを送信しないか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信しなくてよい。 Further, the UE may confirm whether or not the 36th identification information included in the 33rd identification information is included in the 15th identification information for each access. That is, the UE may confirm whether or not the 36th identification information contained in the 33rd identification information is included in the 15th identification information for each of the 3GPP access and the non-3GPP access. .. For example, for 3GPP access, the 36th identification information contained in the 33rd identification information is included in the 15th identification information, but for non-3GPP access, the 36th identification information included in the 33rd identification information is included. If the identification information of is not included in the 15th identification information, the UE sends a registration request message containing the 1st S-NSSAI indicated by the 36th identification information via 3GPP access for the IMS service. A PDU session establishment request message may be sent via 3GPP access, either sent or with the first S-NSSAI indicated by the 36th identification. Also, for 3GPP access, the 36th identification information included in the 33rd identification information is not included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information. If the identification information is included in the fifteenth identification information, the UE sends a registration request message containing the first S-NSSAI indicated by the thirty-sixth identification information via non-3GPP access for the IMS service. A PDU session establishment request message may be sent via non-3GPP access, either by sending or with the first S-NSSAI indicated by the 36th identification information. Further, for 3GPP access, the 36th identification information included in the 33rd identification information is included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information is included. If the identification information is included in the 15th identification information, the UE chooses whether to send from 3GPP access or non-3GPP access for the IMS service, and via the selected access, the 36th. A registration request message containing the first S-NSSAI indicated by the identification information may be sent, or a PDU session establishment request message may be sent together with the first S-NSSAI indicated by the 36th identification information. Also, for 3GPP access, the 36th identification information included in the 33rd identification information is not included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information. If the identification information is not included in the 15th identification information, the UE does not select the 1st S-NSSAI indicated by the 36th identification information for the IMS service and includes the 1st S-NSSAI. It is not necessary to send the registration request message or send the PDU session establishment request message together with the first S-NSSAI.
　また、UEは、コアネットワークから、第11の識別情報を受信した場合は、第11の識別情報と、IMSサービスとを対応付けて記憶してよい。この場合において、第11の識別情報がすべてのPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信していないときは、新しいレジストレーションエリアが現在のPLMNに属するか否かに関わらず、UEは、IMSサービスのために、第11の識別情報で示されるデフォルトS-NSSAIを選択してよい。また、第11の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属する場合は、UEは、IMSサービスのために、第11の識別情報で示されるデフォルトS-NSSAIを選択してよい。また、第11の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属さない場合は、UEは、IMSサービスのために、第11の識別情報で示されるデフォルトS-NSSAIを選択しなくてよい。また、第11の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しているときは、UEは、IMSサービスのために、第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を選択してよい。そして、UEは、選択したデフォルトS-NSSAI又は第1のS-NSSAIを含む登録要求メッセージを送信するか、又は、選択したデフォルトS-NSSAI又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。言い換えると、UEは、S-NSSAIを選択した場合、選択したデフォルトS-NSSAI又は第1のS-NSSAIを含む登録要求メッセージを送信するか、又は、選択したデフォルトS-NSSAI又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。また、UEは、S-NSSAIを選択しない場合、S-NSSAIを含まない登録要求メッセージを送信してもよい。また、UEは、S-NSSAIを選択しない場合、登録要求メッセージを送信しなくてもよい。 Further, when the UE receives the eleventh identification information from the core network, the UE may store the eleventh identification information in association with the IMS service. In this case, the eleventh identification information is valid for all PLMNs, and the UE moves to a new registration area different from the current registration area, and the UE is the new registration area. If you have not received a valid first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid in Whether or not the registration area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the eleventh identification for the IMS service. Also, if the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the eleventh identification for the IMS service. Also, if the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the registration area does not belong to the current PLMN, the UE may not select the default S-NSSAI indicated by the eleventh identification for the IMS service. Also, if the eleventh identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. When receiving the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall The first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) may be selected for the IMS service. The UE then sends a registration request message containing the selected default S-NSSAI or the first S-NSSAI, or along with the selected default S-NSSAI or the first S-NSSAI, a PDU session establishment request message. May be sent. In other words, if the UE selects S-NSSAI, it sends a registration request message containing the selected default S-NSSAI or the first S-NSSAI, or the selected default S-NSSAI or the first S. -May send a PDU session establishment request message with NSSAI. If the UE does not select S-NSSAI, the UE may send a registration request message that does not include S-NSSAI. Also, if the UE does not select S-NSSAI, it does not have to send the registration request message.
　また、UEは、コアネットワークから、すでに第33の識別情報を受信している場合、UEは、第33の識別情報を記憶してよい。この場合において、UEは、コアネットワークから、第12の識別情報及び第15の識別情報を受信したときは、UEは、第12の識別情報と、第15の識別情報、又は第15の識別情報に含まれるS-NSSAIと、を対応付けて記憶してよい。そして、UEは、IMSサービスのためのPDUセッションの確立を要求するときは、第12の識別情報と第15の識別情報と第33の識別情報に基づいて、第15の識別情報に含まれるS-NSSAI及び第36の識別情報で示される第1のS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 Further, if the UE has already received the 33rd identification information from the core network, the UE may store the 33rd identification information. In this case, when the UE receives the twelfth identification information and the fifteenth identification information from the core network, the UE shall receive the twelfth identification information and the fifteenth identification information, or the fifteenth identification information. It may be stored in association with S-NSSAI included in. Then, when the UE requests the establishment of a PDU session for the IMS service, the S included in the fifteenth identification information is based on the twelfth identification information, the fifteenth identification information, and the thirty-third identification information. -Select a valid (available) S-NSSAI in the current registration area from the NSSAI and the first S-NSSAI indicated by the 36th identification information, and a registration request message containing that S-NSSAI. Or may send a PDU session establishment request message with its S-NSSAI.
　また、UEは、コアネットワークから、第12の識別情報及び第15の識別情報を受信したときは、UEは、第12の識別情報と、第15の識別情報、又は第15の識別情報に含まれるS-NSSAIと、を対応付けて記憶してよい。そして、UEは、第33の識別情報を受信した後に、IMSサービスのためのPDUセッションの確立を要求するときには、第12の識別情報と第15の識別情報と第33の識別情報に基づいて、第15の識別情報に含まれるS-NSSAI及び第36の識別情報で示される第1のS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。尚、選択されたS-NSSAIが、現在のレジストレーションエリアで有効(使用可能)であるか否かは、第32の識別情報に基づいて、決定されてもよい。 Further, when the UE receives the twelfth identification information and the fifteenth identification information from the core network, the UE includes the twelfth identification information and the fifteenth identification information or the fifteenth identification information. S-NSSAI may be associated with and stored. Then, when the UE requests the establishment of a PDU session for the IMS service after receiving the 33rd identification information, it is based on the 12th identification information, the 15th identification information, and the 33rd identification information. Select a valid (available) S-NSSAI in the current registration area from the S-NSSAI contained in the 15th identification information and the 1st S-NSSAI indicated by the 36th identification information. A registration request message containing the S-NSSAI may be sent, or a PDU session establishment request message may be sent together with the S-NSSAI. Whether or not the selected S-NSSAI is valid (usable) in the current registration area may be determined based on the 32nd identification information.
　また、UEが、第1のレジストレーションエリアにおいて、IMSサービスのために第1のS-NSSAIを用いたPDUセッションを確立しており、第1のS-NSSAIは、IMSサービスに関して、第1のレジストレーションエリアでは有効(使用可能)であるが、第2のレジストレーションエリアで有効ではない場合であって、UEが、第2のレジストレーションエリアにおいて、コアネットワークから、第1のS-NSSAIを含む第15の識別情報と、第2のS-NSSAIを示す第16の識別情報と、第2のS-NSSAIに対応するIMSサービスを示す第14の識別情報と、を受信し、第2のS-NSSAIが、IMSサービスに関して、第2のレジストレーションエリアで有効である場合、UEは、第14の識別情報と第16の識別情報の受信に基づいて、(第2のレジストレーションエリアでIMSサービスをサポートする)第2のS-NSSAIを用いてIMSサービスのためのPDUセッション確立手続きを開始した後に、(第2のレジストレーションエリアでIMSサービスをサポートしない)第1のS-NSSAIを用いたPDUセッションを解放するためにPDUセッション解放手続きを開始する、あるいは、第1のS-NSSAIを用いたPDUセッションを解放するためにPDUセッション解放手続きを開始した後に、第2のS-NSSAIを用いてIMSサービスのためのPDUセッション確立手続きを開始してよい。尚、この場合において、UEは、第2のレジストレーションエリアで、第15の識別情報によって示される第1のS-NSSAIをIMSサービス以外の通信を行うために、使用してもよい。 In addition, the UE has established a PDU session using the first S-NSSAI for the IMS service in the first registration area, and the first S-NSSAI is the first for the IMS service. If it is valid (available) in the registration area but not in the second registration area, the UE will send the first S-NSSAI from the core network in the second registration area. The 15th identification information including, the 16th identification information indicating the second S-NSSAI, and the 14th identification information indicating the IMS service corresponding to the second S-NSSAI are received, and the second identification information is received. If S-NSSAI is enabled in the second registration area for the IMS service, the UE will base the receipt of the 14th and 16th identification information (IMS in the 2nd registration area). After initiating the PDU session establishment procedure for the IMS service with the second S-NSSAI (which supports the service), use the first S-NSSAI (which does not support the IMS service in the second registration area). Start the PDU session release procedure to release the existing PDU session, or start the PDU session release procedure to release the PDU session using the first S-NSSAI, and then start the second S-NSSAI. It may be used to initiate the PDU session establishment procedure for the IMS service. In this case, the UE may use the first S-NSSAI indicated by the fifteenth identification information in the second registration area to perform communication other than the IMS service.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、第14の識別情報と、第15の識別情報及び/又は第16の識別情報と、を受信したときは、UEは、第15の識別情報及び/又は第16の識別情報で示されるS-NSSAIと、IMSサービスとを対応付けて記憶するとともに、現在のレジストレーションエリアと、記憶したS-NSSAIに基づいて、要求するS-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 Further, when the UE receives the 14th identification information, the 15th identification information and / or the 16th identification information from the core network when communicating using the IMS service, the UE receives the 14th identification information and / or the 16th identification information. , The 15th identification information and / or the S-NSSAI indicated by the 16th identification information is stored in association with the IMS service, and the request is made based on the current registration area and the stored S-NSSAI. You may select the S-NSSAI to be used and send a registration request message containing the S-NSSAI, or send a PDU session establishment request message together with the S-NSSAI.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、第12の識別情報と、第14の識別情報と、第15の識別情報及び/又は第16の識別情報と、を受信したときは、UEは、第15の識別情報及び/又は第16の識別情報で示されるS-NSSAIと、IMSサービスと、第12の識別情報とを対応付けて記憶するとともに、現在のレジストレーションエリアと、記憶したS-NSSAIに基づいて、要求するS-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 Further, when the UE performs communication using the IMS service, the twelfth identification information, the twelfth identification information, the fifteenth identification information, and / or the sixteenth identification information are obtained from the core network. Upon receipt, the UE stores the S-NSSAI indicated by the 15th identification information and / or the 16th identification information, the IMS service, and the 12th identification information in association with each other, and also stores the current registration. Select the requested S-NSSAI based on the relation area and the stored S-NSSAI and send a registration request message containing the S-NSSAI, or send a PDU session establishment request message with the S-NSSAI. You can do it.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、第15の識別情報を受信したときは、第15の識別情報に含まれるS-NSSAIを構成するSST又はSDの値がIMSサービスを示すようなS-NSSAIである場合、そのS-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してもよい。 In addition, when the UE receives the 15th identification information from the core network when communicating using the IMS service, the value of SST or SD that constitutes S-NSSAI included in the 15th identification information. If is an S-NSSAI that indicates an IMS service, select that S-NSSAI and send a registration request message containing that S-NSSAI, or send a PDU session establishment request message with that S-NSSAI. You may.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、第15の識別情報を受信し、かつ、第15の識別情報に含まれる(IMSをサポートする)第1のS-NSSAIの位置や順番と、IMSサービスとの対応付けが、仕様によって予め規定されているか又はオペレータによって予め規定されているときは、UEは、第15の識別情報に含まれる1以上のS-NSSAIの中から、その位置や順番に基づいて、IMSサービスをサポートする第1のS-NSSAIを選択し、第1のS-NSSAIを含む登録要求メッセージを送信するか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してもよい。このように、UEは、Allowed NSSAIにおける第1のS-NSSAIの位置を予め知っている場合には、コアネットワークから、第13の識別情報、及び/又は第14の識別情報、及び/又は第23の識別情報、及び/又は第24の識別情報、及び/又は第34の識別情報のような、IMSサービスと第1のS-NSSAIとの対応関係を明示的に示す情報を受信していなくても、第1のS-NSSAIを特定できてよい。 In addition, the UE receives the fifteenth identification information from the core network and is included in the fifteenth identification information (supports IMS) when communicating using the IMS service. When the location and order of NSSAI and the correspondence with the IMS service are pre-specified by the specification or pre-specified by the operator, the UE shall be one or more S-NSSAI included in the fifteenth identification information. Select the first S-NSSAI that supports the IMS service from among them, based on its location and order, and send a registration request message containing the first S-NSSAI, or the first S-NSSAI. At the same time, a PDU session establishment request message may be sent. In this way, if the UE knows the position of the first S-NSSAI in Allowed NSSAI in advance, the 13th identification information and / or the 14th identification information and / or the first from the core network. You have not received information that explicitly indicates the correspondence between the IMS service and the first S-NSSAI, such as the 23 identification information and / or the 24th identification information and / or the 34th identification information. However, the first S-NSSAI may be identified.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、第13の識別情報及び第15の識別情報を受信した場合は、第13の識別情報で示される情報に基づいて、第15の識別情報に含まれる1以上のS-NSSAIの中から、(IMSをサポートする)第1のS-NSSAIを選択し、第1のS-NSSAIを含む登録要求メッセージを送信するか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してもよい。 Further, when the UE receives the thirteenth identification information and the fifteenth identification information from the core network when communicating using the IMS service, the UE is based on the information indicated by the thirteenth identification information. Select the first S-NSSAI (which supports IMS) from one or more S-NSSAIs contained in the fifteenth identification information and send a registration request message containing the first S-NSSAI. Alternatively, a PDU session establishment request message may be sent together with the first S-NSSAI.
　また、UEが、予め、IMSサービスと、default S-NSSAI及び/又は第1のS-NSSAIと、を対応づけて記憶している場合、UEは、IMSサービスを用いた通信を行う場合は、default S-NSSAI又は第1のS-NSSAIを選択し、default S-NSSAI又は第1のS-NSSAIを含む登録要求メッセージを送信するか、又はdefault S-NSSAI又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してもよい。 If the UE stores the IMS service in advance in association with the default S-NSSAI and / or the first S-NSSAI, the UE may use the IMS service for communication. Select default S-NSSAI or 1st S-NSSAI and send a registration request message containing default S-NSSAI or 1st S-NSSAI, or with default S-NSSAI or 1st S-NSSAI. A PDU session establishment request message may be sent.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、第16の識別情報と第14の識別情報とを含む第15の識別情報を受信した場合、第16の識別情報で示される第1のS-NSSAIを選択し、第1のS-NSSAIを含む登録要求メッセージを送信するか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してもよい。 Further, when the UE receives the 15th identification information including the 16th identification information and the 14th identification information from the core network when communicating using the IMS service, the UE receives the 16th identification information. You may select the first S-NSSAI shown and send a registration request message containing the first S-NSSAI, or you may send a PDU session establishment request message with the first S-NSSAI.
　次に、UEは、さらに、制御メッセージが登録受諾メッセージである場合、登録受諾メッセージに対する応答メッセージとして、登録完了メッセージを、5G AN(gNB)介して、AMFに送信することができる(S612)。ここで、登録完了メッセージは、N1インターフェース上で送受信されるNASメッセージであるが、UEと5G AN(gNB)間はRRCメッセージに含まれて送受信される。 Next, if the control message is a registration acceptance message, the UE can further send a registration completion message to AMF via 5GAN (gNB) as a response message to the registration acceptance message (S612). Here, the registration completion 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 5GAN (gNB).
　AMFは、5G AN(gNB)介して、登録完了メッセージを受信する(S612)。また、各装置は、登録受諾メッセージ、及び/又は登録完了メッセージの送受信に基づき、本手続きを完了する。 AMF receives a registration completion message via 5GAN (gNB) (S612). In addition, each device completes this procedure based on the transmission / reception of the registration acceptance message and / or the registration completion message.
　また、各装置は、登録拒絶メッセージの送受信に基づいて、本手続きを完了してもよい。 Further, each device may complete this procedure based on the transmission / reception of the registration refusal message.
　尚、各装置は、登録受諾メッセージ及び/又は登録完了メッセージの送受信に基づいて、UEがネットワークに登録された状態(RM_REGISTERED state、又は5GMM-REGISTERED state)への遷移又は維持をしてもよいし、登録拒絶メッセージの送受信に基づいて、UEが現在のPLMNに対して登録拒絶メッセージを受信したアクセス上でネットワークに登録されていない状態(RM_DEREGISTERED state、又は5GMM-DEREGISTERED state)への遷移又は維持をしてもよい。また、各装置の各状態への遷移は、登録受諾メッセージ及び/又は登録完了メッセージ及び/又は登録拒絶メッセージの送受信、又は本手続きの完了に基づいて行われてもよい。 In addition, each device may transition or maintain the state in which the UE is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission / reception of the registration acceptance message and / or the registration completion message. , Transition or maintenance to the state where the UE is not registered in the network (RM_DEREGISTERED state, or 5GMM-DEREGISTERED state) on the access that received the registration refusal message to the current PLMN based on the transmission and reception of the registration refusal message. You may. Further, the transition to each state of each device may be performed based on the transmission / reception of the registration acceptance message and / or the registration completion message and / or the registration refusal message, or the completion of this procedure.
　また、各装置は、登録要求メッセージ及び/又は登録受諾メッセージ及び/又は登録完了メッセージ及び/又は登録拒絶メッセージの送受信、又は本手続きの完了に基づいて、これらのメッセージで送受信した情報を記憶してもよいし、ネットワークの決定を認識してもよい。 In addition, each device stores the information sent / received in these messages based on the transmission / reception of the registration request message and / or the registration acceptance message and / or the registration completion message and / or the registration refusal message, or the completion of this procedure. You may be aware of your network decisions.
　更に、各装置は、本手続き完了に基づき、更新及び/又は記憶された記憶情報に基づき、次の挙動を決定してよい。 Furthermore, each device may determine the next behavior based on the updated and / or stored stored information based on the completion of this procedure.
　具体的には、本手続き完了後、現在のPLMNの現在のアクセス上で登録された状態に遷移した場合、各装置は、現在のPLMNの現在のアクセス上にPDUセッションを確立するためのPDUセッション確立手続きを開始してもよい。 Specifically, after completing this procedure, if the state transitions to the state registered on the current access of the current PLMN, each device establishes a PDU session on the current access of the current PLMN. The establishment procedure may be started.
　ここで、UEは、PDUセッション確立手続きにおいて、第3の識別情報を送信してもよい。第3の識別情報として送信するS-NSSAIの選択方法は、本手続きの登録要求メッセージ及び/又はRRCメッセージに含めて送信する際の選択方法を用いてよい。なお、選択されたS-NSSAIはrequested NSSAIとしてPDUセッション確立手続きで用いられてよい。 Here, the UE may transmit the third identification information in the PDU session establishment procedure. As the selection method of S-NSSAI to be transmitted as the third identification information, the selection method when being included in the registration request message and / or RRC message of this procedure may be used. The selected S-NSSAI may be used as requested NSSAI in the PDU session establishment procedure.
　具体的に、例えば、UEがIMSサービスのためのPDUセッションの確立を要求する場合、UEは、以下の方法で要求するS-NSSAIを選択してよい。 Specifically, for example, when the UE requests the establishment of a PDU session for the IMS service, the UE may select the S-NSSAI requested by the following method.
　UEは、第15の識別情報と、第33の識別情報に基づいて、IMSサービスのために、第15の識別情報に含まれる1以上のS-NSSAI及び第33の識別情報に含まれる第36の識別情報で示されるS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを選択して、要求してよい。 The UE shall be included in one or more S-NSSAIs contained in the 15th identification information and the 36th identification information contained in the 33rd identification information for the IMS service based on the 15th identification information and the 33rd identification information. From the S-NSSAI indicated by the identification information of, a valid (available) S-NSSAI in the current registration area may be selected and requested.
　また、UEは、コアネットワークから、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるか否かを確認し、第36の識別情報が第15の識別情報に含まれる場合は、IMSサービスのために、第36の識別情報を第3の識別情報として選択して、要求してよい。 In addition, the UE confirms from the core network whether or not the 36th identification information included in the 33rd identification information is included in the 15th identification information, and the 36th identification information becomes the 15th identification information. If included, the 36th identification may be selected and requested as the third identification for the IMS service.
　また、UEは、第36の識別情報が第15の識別情報に含まれるか否かを確認し、第36の識別情報が第15の識別情報に含まれない場合は、IMSサービスのために、第36の識別情報を第3の識別情報として選択しなくてよい。この場合において、UEは、IMSサービスのためのPDUセッション確立手続きを開始しなくてもよい。 The UE also checks whether the 36th identification information is included in the 15th identification information, and if the 36th identification information is not included in the 15th identification information, for the IMS service, It is not necessary to select the 36th identification information as the third identification information. In this case, the UE does not have to initiate the PDU session establishment procedure for the IMS service.
　また、UEは、第11の識別情報、及び/又は第21の識別情報として受信した、及び/又は事前にUEに設定された、IMSサービスのためのdefault S-NSSAIとIMSサービスを関連付けて記憶し、現在のレジストレーションエリアで有効である場合、更に現在のレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信又は記憶していないときは、第11の識別情報に示されるS-NSSAIを選択し、要求してもよい。 The UE also stores the default S-NSSAI for the IMS service received and / or preset in the UE as the 11th identification information and / or the 21st identification information in association with the IMS service. However, if it is valid in the current registration area, the first S-NSSAI (16th identification information and / or 26th identification information) that is also valid in the current registration area (supporting IMS service). , And / or the 36th identification information) is not received or stored, the S-NSSAI shown in the 11th identification information may be selected and requested.
　UEは、第12の識別情報と第15の識別情報と第33の識別情報に基づいて、第15の識別情報に含まれるS-NSSAI及び第36の識別情報で示される第1のS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを第3の識別情報として選択し、要求してもよい。 Based on the twelfth identification information, the fifteenth identification information, and the thirty-third identification information, the UE performs the S-NSSAI contained in the fifteenth identification information and the first S-NSSAI indicated by the thirty-sixth identification information. Among them, S-NSSAI valid (available) in the current registration area may be selected and requested as the third identification information.
　または、UEは現在のPLMNに対応づけられたAllowed NSSAIを記憶する場合、記憶するAllowed NSSAIに基づいて、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを第3の識別情報として選択し、要求してもよい。 Alternatively, if the UE remembers the Allowed NSSAI associated with the current PLMN, the valid (usable) S-NSSAI in the current registration area is used as the third identification information based on the remembered Allowed NSSAI. You may choose and request.
　具体的には、例えばUEはAllowed NSSAIに含まれるS-NSSAIを構成するSST又はSDの値がIMSサービスを示すようなS-NSSAIである場合、そのS-NSSAIを選択し、要求してもよい。 Specifically, for example, if the UE is an S-NSSAI whose SST or SD value that constitutes the S-NSSAI included in the Allowed NSSAI is an S-NSSAI that indicates an IMS service, even if that S-NSSAI is selected and requested. good.
　または、UEはAllowed NSSAIに含まれるS-NSSAIの位置や順番に基づき、IMSサービスのためのS-NSSAIを選択し、要求してもよい。 Alternatively, the UE may select and request the S-NSSAI for the IMS service based on the location and order of the S-NSSAI included in the Allowed NSSAI.
　尚、本章に記載した登録手続きは、初期登録のための登録手続きであってもよいし、移動及び定期的な登録のための登録手続きであってもよい。 The registration procedure described in this chapter may be a registration procedure for initial registration, or may be a registration procedure for movement and regular registration.
　さらに、UEは、制御メッセージ及び/又は制御メッセージに含まれる識別情報の受信に基づいて、3.2章の登録手続き、又は3.3章のジェネリックUE設定更新手続き、又は3.4章のUEポリシー管理手続き、又はSMのための手続きを開始してもよい。 In addition, the UE shall, based on the receipt of the control message and / or the identification information contained in the control message, the registration procedure in Chapter 3.2, the generic UE setting update procedure in Chapter 3.3, or the UE policy management procedure in Chapter 3.4, or SM. You may start the procedure for.
　[3.3. ジェネリックUE設定更新手続き]
　次に、ジェネリックUE設定更新手続きを、図7を用いて説明する。 [3.3. Generic UE setting update procedure]
Next, the generic UE setting update procedure will be described with reference to FIG. 7.
　本手続きは、AMFが、アクセス及び移動管理関連のパラメータ(access and mobility management-related parameters)についてのUEの設定を更新する場合に、開始されてもよい。また、本手続きは、アクセス及び移動管理関連のパラメータを更新するため、UEに対して、移動及び定期的な登録更新の為の登録手続き(registration procedure for mobility and periodic registration update)を実行することを要求する場合に、開始されてもよい。さらに、UEは、3.2章の登録手続きの完了、又は3.3章のジェネリックUE設定更新手続きの完了、又は3.4章のUEポリシー管理手続きの完了、又はSMのための手続きの完了等に基づいて、ジェネリックUE設定更新手続きを開始してもよい。 This procedure may be initiated when the AMF updates the UE settings for access and mobility management-related parameters. In addition, in order to update the parameters related to access and movement management, this procedure requires the UE to execute the registration procedure (registration procedure for mobility and periodic registration update) for movement and periodic registration update. It may be started when requested. Furthermore, the UE is generic based on the completion of the registration procedure in Chapter 3.2, the completion of the generic UE setting update procedure in Chapter 3.3, the completion of the UE policy management procedure in Chapter 3.4, or the completion of the procedure for SM. You may start the UE setting update procedure.
　本手続きは、AMFがアクセスネットワークを介してUEに設定更新コマンド(Configuration update command)を送信することによって、開始される(S800)。 This procedure is started by AMF sending a configuration update command to the UE via the access network (S800).
　ここで、設定更新コマンドには、第21から27の識別情報の少なくとも一部が含まれてよい。ここで、第21から27の識別情報は、2.7章の通りであってよい。また、設定更新コマンドに含まれる第21から27の識別情報によって示される情報のうちの少なくとも1つは、それぞれ3.2章の登録手続きにおける制御メッセージ(登録受諾メッセージ又は登録拒絶メッセージ)で送受信した第11から17の識別情報によって示される情報から更新されていることが好ましいが、第11から17の識別情報によって示される情報と同一であってもよい。 Here, the setting update command may include at least a part of the identification information of the 21st to 27th. Here, the identification information of Chapters 21 to 27 may be as described in Chapter 2.7. In addition, at least one of the information indicated by the identification information of 21 to 27 included in the setting update command is sent and received in the control message (registration acceptance message or registration refusal message) in the registration procedure of Chapter 3.2, respectively. It is preferable that the information is updated from the information indicated by the identification information of the eleventh to the seventeenth, but it may be the same as the information indicated by the identification information of the eleventh to the seventeenth.
　また、UEは、設定更新コマンドを受信する(S800)ことで、設定更新コマンドに含まれる各識別情報の意味、及び/又は各識別情報の組み合わせによって示される意味を理解することができてよい。 Further, by receiving the setting update command (S800), the UE may be able to understand the meaning of each identification information included in the setting update command and / or the meaning indicated by the combination of each identification information.
　さらに、UEは、設定更新コマンドを受信することで、すでに記憶している識別情報を更新してよいし、まだ識別情報を記憶していない場合には受信した識別情報を記憶してよい。 Further, the UE may update the already stored identification information by receiving the setting update command, or may store the received identification information when the identification information is not yet stored.
　また、UEは、第21から27の識別情報のうち少なくとも1つ以上の情報の受信、及び/又は設定更新コマンドの受信に基づき、以下の処理を実行してもよい。尚、UEは、これらの処理を、本手続き中、又は本手続き完了後に実行してもよい。 Further, the UE may execute the following processing based on the reception of at least one or more of the identification information of the 21st to 27th and / or the reception of the setting update command. The UE may execute these processes during this procedure or after the procedure is completed.
　例えば、UEは、コアネットワークから、第21の識別情報を受信した場合は、第21の識別情報と、IMSサービスとを対応付けて記憶してよい。この場合において、第21の識別情報がすべてのPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信していないときは、新しいレジストレーションエリアが現在のPLMNに属するか否かに関わらず、UEは、IMSサービスのために、第21の識別情報で示されるデフォルトS-NSSAIを選択してよい。また、第21の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属する場合は、UEは、IMSサービスのために、第21の識別情報で示されるデフォルトS-NSSAIを選択してよい。また、第21の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属さない場合は、UEは、IMSサービスのために、第21の識別情報で示されるデフォルトS-NSSAIを選択しなくてよい。また、第21の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しているときは、UEは、IMSサービスのために、第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を選択してよい。そして、UEは、選択したデフォルトS-NSSAI又は第1のS-NSSAIを含む登録要求メッセージを送信するか、又は、選択したデフォルトS-NSSAI又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。言い換えると、UEは、S-NSSAIを選択した場合、選択したデフォルトS-NSSAI又は第1のS-NSSAIを含む登録要求メッセージを送信するか、又は、選択したデフォルトS-NSSAI又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。また、UEは、S-NSSAIを選択しない場合、S-NSSAIを含まない登録要求メッセージを送信してもよい。また、UEは、S-NSSAIを選択しない場合、登録要求メッセージを送信しなくてもよい。 For example, when the UE receives the 21st identification information from the core network, the UE may store the 21st identification information in association with the IMS service. In this case, the 21st identification information is valid for all PLMNs, and the UE moves to a new registration area that is different from the current registration area, and the UE is the new registration area. If you have not received a valid first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid in Whether or not the registration area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the 21st Distinguished Information for the IMS service. Also, if the 21st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the 21st identification for the IMS service. Also, if the 21st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the registration area does not belong to the current PLMN, the UE may not select the default S-NSSAI indicated by the 21st identification for the IMS service. Also, if the 21st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. When receiving the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall The first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) may be selected for the IMS service. The UE then sends a registration request message containing the selected default S-NSSAI or the first S-NSSAI, or along with the selected default S-NSSAI or the first S-NSSAI, a PDU session establishment request message. May be sent. In other words, if the UE selects S-NSSAI, it sends a registration request message containing the selected default S-NSSAI or the first S-NSSAI, or the selected default S-NSSAI or the first S. -May send a PDU session establishment request message with NSSAI. If the UE does not select S-NSSAI, the UE may send a registration request message that does not include S-NSSAI. Also, if the UE does not select S-NSSAI, it does not have to send the registration request message.
　また、UEが、第1のレジストレーションエリアにおいて、IMSサービスのために第1のS-NSSAIを用いたPDUセッションを確立しており、第1のS-NSSAIは、IMSサービスに関して、第1のレジストレーションエリアでは有効(使用可能)であるが、第2のレジストレーションエリアで有効ではない場合であって、UEが、第2のレジストレーションエリアにおいて、すでにコアネットワークから第1のS-NSSAIを含む第15の識別情報又は第25の識別情報を受信したか、又は本手続きにおいて第1のS-NSSAIを含む第25の識別情報を受信し、さらに、本手続きにおいて、第2のS-NSSAIを示す第26の識別情報と、第2のS-NSSAIに対応するIMSサービスを示す第24の識別情報と、を受信し、第2のS-NSSAIが、IMSサービスに関して、第2のレジストレーションエリアで有効である場合、UEは、第24の識別情報と第26の識別情報の受信に基づいて、(第2のレジストレーションエリアでIMSサービスをサポートする)第2のS-NSSAIを用いてIMSサービスのためのPDUセッション確立手続きを開始した後に、(第2のレジストレーションエリアでIMSサービスをサポートしない)第1のS-NSSAIを用いたPDUセッションを解放するためにPDUセッション解放手続きを開始する、あるいは、第1のS-NSSAIを用いたPDUセッションを解放するためにPDUセッション解放手続きを開始した後に、第2のS-NSSAIを用いてIMSサービスのためのPDUセッション確立手続きを開始してよい。尚、この場合において、UEは、第2のレジストレーションエリアで、第15の識別情報によって示される第1のS-NSSAIをIMSサービス以外の通信を行うために、使用してもよい。 In addition, the UE has established a PDU session using the first S-NSSAI for the IMS service in the first registration area, and the first S-NSSAI is the first for the IMS service. If it is valid (available) in the registration area but not in the second registration area, the UE has already issued the first S-NSSAI from the core network in the second registration area. Received the 15th identification information or the 25th identification information including, or received the 25th identification information including the 1st S-NSSAI in this procedure, and further, in this procedure, the 2nd S-NSSAI. The 26th identification information indicating the second S-NSSAI and the 24th identification information indicating the IMS service corresponding to the second S-NSSAI are received, and the second S-NSSAI receives the second registration for the IMS service. When enabled in the area, the UE uses a second S-NSSAI (supporting IMS services in the second registration area) based on the receipt of the 24th and 26th identifications. After starting the PDU session establishment procedure for the IMS service, start the PDU session release procedure to release the PDU session with the first S-NSSAI (which does not support the IMS service in the second registration area). Or, after starting the PDU session release procedure to release the PDU session using the first S-NSSAI, start the PDU session establishment procedure for the IMS service using the second S-NSSAI. You can do it. In this case, the UE may use the first S-NSSAI indicated by the fifteenth identification information in the second registration area to perform communication other than the IMS service.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、第24の識別情報と、第25の識別情報及び/又は第26の識別情報と、を受信したときは、UEは、第25の識別情報及び/又は第26の識別情報で示されるS-NSSAIと、IMSサービスとを対応付けて記憶するとともに、現在のレジストレーションエリアと、記憶したS-NSSAIに基づいて、要求するS-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 Further, when the UE receives the 24th identification information, the 25th identification information and / or the 26th identification information from the core network when communicating using the IMS service, the UE receives the 24th identification information and / or the 26th identification information. , The 25th identification information and / or the S-NSSAI indicated by the 26th identification information is stored in association with the IMS service, and the request is made based on the current registration area and the stored S-NSSAI. You may select the S-NSSAI to be used and send a registration request message containing the S-NSSAI, or send a PDU session establishment request message together with the S-NSSAI.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、第22の識別情報と、第24の識別情報と、第25の識別情報及び/又は第26の識別情報と、を受信したときは、UEは、第25の識別情報及び/又は第26の識別情報で示されるS-NSSAIと、IMSサービスと、第22の識別情報とを対応付けて記憶するとともに、現在のレジストレーションエリアと、記憶したS-NSSAIに基づいて、要求するS-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 In addition, when communicating using the IMS service, the UE obtains the 22nd identification information, the 24th identification information, the 25th identification information, and / or the 26th identification information from the core network. Upon receipt, the UE stores the S-NSSAI indicated by the 25th identification information and / or the 26th identification information, the IMS service, and the 22nd identification information in association with each other, and also stores the current registration. Select the requested S-NSSAI based on the relation area and the stored S-NSSAI and send a registration request message containing the S-NSSAI, or send a PDU session establishment request message with the S-NSSAI. You can do it.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、第25の識別情報を受信したときは、第25の識別情報に含まれるS-NSSAIを構成するSST又はSDの値がIMSサービスを示すようなS-NSSAIである場合、そのS-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してもよい。 In addition, when the UE receives the 25th identification information from the core network when communicating using the IMS service, the value of SST or SD that constitutes S-NSSAI included in the 25th identification information. If is an S-NSSAI that indicates an IMS service, select that S-NSSAI and send a registration request message containing that S-NSSAI, or send a PDU session establishment request message with that S-NSSAI. You may.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、第25の識別情報を受信し、かつ、第25の識別情報に含まれる(IMSをサポートする)第1のS-NSSAIの位置や順番と、IMSサービスとの対応付けが、仕様によって予め規定されているか又はオペレータによって予め規定されているときは、UEは、第25の識別情報に含まれる1以上のS-NSSAIの中から、その位置や順番に基づいて、IMSサービスをサポートする第1のS-NSSAIを選択し、第1のS-NSSAIを含む登録要求メッセージを送信するか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してもよい。このように、UEは、Allowed NSSAIにおける第1のS-NSSAIの位置を予め知っている場合には、コアネットワークから、第13の識別情報、及び/又は第14の識別情報、及び/又は第23の識別情報、及び/又は第24の識別情報、及び/又は第34の識別情報のような、IMSサービスと第1のS-NSSAIとの対応関係を明示的に示す情報を受信していなくても、第1のS-NSSAIを特定できてよい。 In addition, the UE receives the 25th identification information from the core network and is included in the 25th identification information (supports IMS) when communicating using the IMS service. If the location or order of the NSSAI and its association with the IMS service is pre-specified by the specification or pre-specified by the operator, the UE shall be one or more S-NSSAI included in the 25th identification information. Select the first S-NSSAI that supports the IMS service from among them, based on its location and order, and send a registration request message containing the first S-NSSAI, or the first S-NSSAI. At the same time, a PDU session establishment request message may be sent. In this way, if the UE knows the position of the first S-NSSAI in Allowed NSSAI in advance, the 13th identification information and / or the 14th identification information and / or the first from the core network. You have not received information that explicitly indicates the correspondence between the IMS service and the first S-NSSAI, such as the 23 identification information and / or the 24th identification information and / or the 34th identification information. However, the first S-NSSAI may be identified.
　また、UEは、IMSサービスを用いた通信を行う場合に、コアネットワークから、第23の識別情報及び第25の識別情報を受信した場合は、第23の識別情報で示される情報に基づいて、第25の識別情報に含まれる1以上のS-NSSAIの中から、(IMSをサポートする)第1のS-NSSAIを選択し、第1のS-NSSAIを含む登録要求メッセージを送信するか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してもよい。 In addition, when the UE receives the 23rd identification information and the 25th identification information from the core network when communicating using the IMS service, the UE is based on the information indicated by the 23rd identification information. Select the first S-NSSAI (which supports IMS) from one or more S-NSSAIs contained in the 25th identification information and send a registration request message containing the first S-NSSAI. Alternatively, a PDU session establishment request message may be sent together with the first S-NSSAI.
　また、UEが、予め、IMSサービスと、default S-NSSAI及び/又は第1のS-NSSAIと、を対応づけて記憶している場合、UEは、IMSサービスを用いた通信を行う場合は、default S-NSSAI又は第1のS-NSSAIを選択し、default S-NSSAI又は第1のS-NSSAIを含む登録要求メッセージを送信するか、又はdefault S-NSSAI又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してもよい。 If the UE stores the IMS service in advance in association with the default S-NSSAI and / or the first S-NSSAI, the UE may use the IMS service for communication. Select default S-NSSAI or 1st S-NSSAI and send a registration request message containing default S-NSSAI or 1st S-NSSAI, or with default S-NSSAI or 1st S-NSSAI. A PDU session establishment request message may be sent.
　また、各装置は、設定更新コマンドの送受信に基づいて、本手続きを完了する。 In addition, each device completes this procedure based on the transmission and reception of the setting update command.
　さらに、UEは、設定更新コマンド及び/又は設定更新コマンドに含まれる識別情報の受信に基づいて、3.2章の登録手続き、又は3.3章のジェネリックUE設定更新手続き、又は3.4章のUEポリシー管理手続き、又はSMのための手続きを開始してもよい。 In addition, the UE may perform the registration procedure in Chapter 3.2, the generic UE setting update procedure in Chapter 3.3, or the UE policy management procedure in Chapter 3.4, based on the receipt of the identification information contained in the setting update command and / or the setting update command. Alternatively, the procedure for SM may be started.
　[3.4. UEポリシー管理手続き]
　次に、UEポリシー管理手続きを、図8を用いて説明する。 [3.4. UE Policy Management Procedure]
Next, the UE policy management procedure will be described with reference to FIG.
　本手続きは、PCFが、1以上のUEポリシーを、UEに提供するために使用される。例えば、ネットワークは、UEに対して新しい1以上のUEポリシーを追加するために、本手続きを実行することができる。また、ネットワークは、UEに記憶している1以上のUEポリシーを修正又は削除するために、本手続きを実行することができる。さらに、UEは、3.2章の登録手続きの完了、又は3.3章のジェネリックUE設定更新手続きの完了、又は3.4章のUEポリシー管理手続きの完了、又はSMのための手続きの完了等に基づいて、UEポリシー管理手続きを開始してもよい。 This procedure is used by the PCF to provide one or more UE policies to the UE. For example, the network may perform this procedure to add one or more new UE policies to the UE. The network may also perform this procedure to modify or delete one or more UE policies stored in the UE. In addition, the UE will be based on the completion of the registration procedure in Chapter 3.2, the completion of the generic UE setting update procedure in Chapter 3.3, the completion of the UE policy management procedure in Chapter 3.4, the completion of the procedure for SM, etc. You may start the policy management procedure.
　本手続きは、PCFがUEにAMFを介してUEポリシー管理コマンド(MANAGE UE POLICY COMMAND)を送信することによって、開始される(S900)。 This procedure is started when the PCF sends a UE policy management command (MANAGE UE POLICY COMMAND) to the UE via AMF (S900).
　ここで、UEポリシー管理コマンドには、第31から37の識別情報の少なくとも一部が含まれてよい。ここで、第31から37の識別情報は、2.7章の通りであってよい。また、PCFは、第31から37の識別情報の内、どの識別情報を制御メッセージに含めるかを、受信した各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はPCFが保持するコンテキスト等に基づいて、選択、決定してもよい。 Here, the UE policy management command may include at least a part of the identification information of the 31st to 37th. Here, the identification information of Chapters 31 to 37 may be as described in Chapter 2.7. In addition, the PCF determines which of the 31st to 37th identification information is included in the control message, each of the received identification information and / or the subscriber information, and / or the network capability information, and / or. It may be selected and determined based on the operator policy and / or the state of the network and / or the user's registration information and / or the context held by the PCF.
　また、UEは、PCFからUEポリシー管理コマンドを受信する(S900)ことで、UEポリシー管理コマンドに含まれる各識別情報の意味、及び/又は各識別情報の組み合わせによって示される意味を理解することができてよい。 In addition, the UE can understand the meaning of each identification information contained in the UE policy management command and / or the meaning indicated by the combination of each identification information by receiving the UE policy management command from the PCF (S900). You can do it.
　さらに、UEは、UEポリシー管理コマンドを受信することで、すでに記憶している識別情報を更新してよいし、まだ識別情報を記憶していない場合には受信した識別情報を記憶してよい。 Further, the UE may update the already stored identification information by receiving the UE policy management command, or may store the received identification information when the identification information is not yet stored.
　また、UEは、第31から37の識別情報のうち少なくとも1つ以上の情報の受信、及び/又は設定更新コマンドの受信に基づき、以下の処理を実行してもよい。尚、UEは、これらの処理を、本手続き中、又は本手続き完了後に実行してもよい。 Further, the UE may execute the following processing based on the reception of at least one or more of the identification information of the 31st to 37th and / or the reception of the setting update command. The UE may execute these processes during this procedure or after the procedure is completed.
　例えば、UEは、コアネットワークから、すでに第15の識別情報を受信している場合に、本手続きにおいて第33の識別情報を受信したときであって、IMSサービスのためのPDUセッションの確立を要求するときは、第15の識別情報と、第33の識別情報に基づいて、第15の識別情報に含まれる1以上のS-NSSAI及び第33の識別情報に含まれる第36の識別情報で示されるS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 For example, the UE requests the establishment of a PDU session for the IMS service when the fifteenth identification information has already been received from the core network and the thirty-third identification information is received in this procedure. When doing so, it is indicated by one or more S-NSSAI contained in the 15th identification information and the 36th identification information contained in the 33rd identification information based on the 15th identification information and the 33rd identification information. Select a valid (available) S-NSSAI in the current registration area from the S-NSSAI and send a registration request message containing the S-NSSAI, or PDU with the S-NSSAI. A session establishment request message may be sent.
　また、UEは、コアネットワークから、すでに第15の識別情報及び第33の識別情報を受信している場合であって、第33の識別情報が第32の識別情報を含まないときは、第33に含まれる第36の識別情報で示されるS-NSSAIが、現在のレジストレーションエリアで有効である、又は現在のPLMN内で有効である、又は全てのPLMNで有効であるものと判断し、第15の識別情報と、第33の識別情報に基づいて、IMSサービスのために、第15の識別情報に含まれる1以上のS-NSSAI及び第33の識別情報に含まれる第36の識別情報で示されるS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 Further, when the UE has already received the 15th identification information and the 33rd identification information from the core network and the 33rd identification information does not include the 32nd identification information, the 33rd identification information is included. It is determined that the S-NSSAI indicated by the 36th identification information contained in the current registration area is valid in the current registration area, is valid in the current PLMN, or is valid in all PLMNs. Based on the 15 identification information and the 33rd identification information, for the IMS service, one or more S-NSSAI contained in the 15th identification information and the 36th identification information contained in the 33rd identification information. From the S-NSSAI shown, select a valid (available) S-NSSAI in the current registration area and send a registration request message containing that S-NSSAI, or with that S-NSSAI. A PDU session establishment request message may be sent.
　また、UEは、コアネットワークから、すでに第15の識別情報を受信している場合に、本手続きにおいて第33の識別情報を受信し、第33の識別情報に含まれる第36の識別情報がPCFによってAllowed NSSAIの中から選択された第1のS-NSSAIであり、かつ、IMSサービスのためのPDUセッションの確立を要求するときは、第33の識別情報に基づいて、第1のS-NSSAI(第33の識別情報に含まれる第36の識別情報)を選択し、第1のS-NSSAIを含む登録要求メッセージを送信するか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 Further, when the UE has already received the 15th identification information from the core network, the UE receives the 33rd identification information in this procedure, and the 36th identification information included in the 33rd identification information is the PCF. The first S-NSSAI selected from Allowed NSSAI by, and when requesting the establishment of a PDU session for the IMS service, the first S-NSSAI is based on the 33rd identification information. Select (36th identification information contained in the 33rd identification information) and send a registration request message containing the first S-NSSAI, or send a PDU session establishment request message with the first S-NSSAI. You may send it.
　また、UEは、コアネットワークから、すでに第15の識別情報を受信している場合に、本手続きにおいて第33の識別情報を受信したときであって、IMSサービスのためのPDUセッションの確立を要求するときは、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるか否かを確認し、第36の識別情報が第15の識別情報に含まれる場合は、第36の識別情報で示される第1のS-NSSAIを選択し、第1のS-NSSAIを含む登録要求メッセージを送信するか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。また、UEは、第36の識別情報が第15の識別情報に含まれるか否かを確認し、第36の識別情報が第15の識別情報に含まれない場合は、IMSサービスのために、第36の識別情報で示される第1のS-NSSAIを選択せず、第1のS-NSSAIを含む登録要求メッセージを送信しないか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信しなくてよい。さらに、この場合において、UEは、第41の識別情報を含むUEポリシー管理コマンド拒絶メッセージを送信してもよい(S902)。 In addition, the UE requests the establishment of a PDU session for the IMS service when the 15th identification information has already been received from the core network and the 33rd identification information is received in this procedure. When doing so, check whether the 36th identification information included in the 33rd identification information is included in the 15th identification information, and if the 36th identification information is included in the 15th identification information, Select the first S-NSSAI indicated by the 36th identification and send a registration request message containing the first S-NSSAI, or send a PDU session establishment request message with the first S-NSSAI. You can do it. The UE also checks whether the 36th identification information is included in the 15th identification information, and if the 36th identification information is not included in the 15th identification information, for the IMS service, Do not select the first S-NSSAI indicated by the 36th identification information and do not send a registration request message containing the first S-NSSAI, or send a PDU session establishment request message with the first S-NSSAI. You don't have to send it. Further, in this case, the UE may send a UE policy management command rejection message containing the 41st identification information (S902).
　さらに、UEは、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるか否かを、アクセスごとに確認してもよい。すなわち、UEは、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるか否かを、3GPPアクセスおよびnon-3GPPアクセスの夫々に対して、確認してもよい。 Further, the UE may confirm whether or not the 36th identification information included in the 33rd identification information is included in the 15th identification information for each access. That is, the UE may confirm whether or not the 36th identification information contained in the 33rd identification information is included in the 15th identification information for each of the 3GPP access and the non-3GPP access. ..
　例えば、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれるが、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれない場合、UEは、IMSサービスのために、第36の識別情報で示される第1のS-NSSAIを含む登録要求メッセージを、3GPPアクセス経由で、送信するか、又は第36の識別情報で示される第1のS-NSSAIとともに、PDUセッション確立要求メッセージを、3GPPアクセス経由で、送信してよい。この場合、UEは、non-3GPPアクセスに対して、現在のレジストレーションエリアで利用できない、又は提供されたS-NSSAIが現在のレジストレーションエリアで利用できないことを示す第41の識別情報を含むUEポリシー管理コマンド拒絶メッセージを送信してもよい(S902)。 For example, for 3GPP access, the 36th identification information contained in the 33rd identification information is included in the 15th identification information, but for non-3GPP access, the 36th identification information included in the 33rd identification information is included. If the identification information of is not included in the 15th identification information, the UE sends a registration request message containing the 1st S-NSSAI indicated by the 36th identification information via 3GPP access for the IMS service. A PDU session establishment request message may be sent via 3GPP access, either sent or with the first S-NSSAI indicated by the 36th identification. In this case, the UE contains a 41st identification for non-3GPP access indicating that it is not available in the current registration area or that the provided S-NSSAI is not available in the current registration area. A policy management command rejection message may be sent (S902).
　また、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれず、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれる場合、UEは、IMSサービスのために、第36の識別情報で示される第1のS-NSSAIを含む登録要求メッセージを、non-3GPPアクセス経由で、送信するか、又は第36の識別情報で示される第1のS-NSSAIとともに、PDUセッション確立要求メッセージを、non-3GPPアクセス経由で、送信してよい。この場合、UEは、3GPPアクセスに対して、現在のレジストレーションエリアで利用できない、又は提供されたS-NSSAIが現在のレジストレーションエリアで利用できないことを示す第41の識別情報を含むUEポリシー管理コマンド拒絶メッセージを送信してもよい(S902)。 Also, for 3GPP access, the 36th identification information included in the 33rd identification information is not included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information. If the identification information is included in the fifteenth identification information, the UE sends a registration request message containing the first S-NSSAI indicated by the thirty-sixth identification information via non-3GPP access for the IMS service. A PDU session establishment request message may be sent via non-3GPP access, either by sending or with the first S-NSSAI indicated by the 36th identification information. In this case, the UE provides UE policy management for 3GPP access with a 41st identification that indicates that it is not available in the current registration area or that the provided S-NSSAI is not available in the current registration area. A command rejection message may be sent (S902).
　また、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれ、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれる場合、UEは、IMSサービスのために、3GPPアクセスとnon-3GPPアクセスのどちらのアクセスから送信するかを選択し、選択したアクセス経由で、第36の識別情報で示される第1のS-NSSAIを含む登録要求メッセージを送信するか、又は第36の識別情報で示される第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。この場合、UEは、第41の識別情報を含むUEポリシー管理コマンド拒絶メッセージを送信しなくてよい。 Further, for 3GPP access, the 36th identification information included in the 33rd identification information is included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information is included. If the identification information is included in the 15th identification information, the UE chooses whether to send from 3GPP access or non-3GPP access for the IMS service, and via the selected access, the 36th. A registration request message containing the first S-NSSAI indicated by the identification information may be sent, or a PDU session establishment request message may be sent together with the first S-NSSAI indicated by the 36th identification information. In this case, the UE does not have to send a UE policy management command rejection message containing the 41st identification.
　また、3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれず、non-3GPPアクセスに対して、第33の識別情報に含まれる第36の識別情報が第15の識別情報に含まれない場合、UEは、IMSサービスのために、第36の識別情報で示される第1のS-NSSAIを選択せず、第1のS-NSSAIを含む登録要求メッセージを送信しないか、又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信しなくてよい。この場合、UEは、3GPPアクセス及びnon-3GPPアクセスに対して、現在のレジストレーションエリアで利用できない、又は提供されたS-NSSAIが現在のレジストレーションエリアで利用できないことを示す第41の識別情報を含むUEポリシー管理コマンド拒絶メッセージを送信してもよい(S902)。 Also, for 3GPP access, the 36th identification information included in the 33rd identification information is not included in the 15th identification information, and for non-3GPP access, the 36th identification information included in the 33rd identification information. If the identification information is not included in the 15th identification information, the UE does not select the 1st S-NSSAI indicated by the 36th identification information for the IMS service and includes the 1st S-NSSAI. It is not necessary to send the registration request message or send the PDU session establishment request message together with the first S-NSSAI. In this case, the UE is the 41st identification information indicating that the S-NSSAI provided is not available in the current registration area for 3GPP access and non-3GPP access. A UE policy management command rejection message containing may be sent (S902).
　また、UEは、コアネットワークから、第31の識別情報を受信した場合は、第31の識別情報と、IMSサービスとを対応付けて記憶してよい。この場合において、第31の識別情報がすべてのPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信していないときは、新しいレジストレーションエリアが現在のPLMNに属するか否かに関わらず、UEは、IMSサービスのために、第31の識別情報で示されるデフォルトS-NSSAIを選択してよい。また、第31の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属する場合は、UEは、IMSサービスのために、第31の識別情報で示されるデフォルトS-NSSAIを選択してよい。また、第31の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しておらず、かつ、新しいレジストレーションエリアが現在のPLMNに属さない場合は、UEは、IMSサービスのために、第31の識別情報で示されるデフォルトS-NSSAIを選択しなくてよい。また、第31の識別情報が現在のPLMNで有効であり、かつ、UEが現在のレジストレーションエリアとは異なる新しいレジストレーションエリアに移動する場合であって、かつ、UEが新しいレジストレーションエリアで有効な(IMSサービスをサポートする)第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を受信しているときは、UEは、IMSサービスのために、第1のS-NSSAI(第16の識別情報、及び/又は第26の識別情報、及び/又は第36の識別情報)を選択してよい。そして、UEは、選択したデフォルトS-NSSAI又は第1のS-NSSAIを含む登録要求メッセージ、又は、選択したデフォルトS-NSSAI又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 Further, when the UE receives the 31st identification information from the core network, the UE may store the 31st identification information in association with the IMS service. In this case, the 31st identification information is valid for all PLMNs, and the UE moves to a new registration area that is different from the current registration area, and the UE is the new registration area. If you have not received a valid first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) that is valid in Whether or not the registration area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the 31st Distinguished Information for the IMS service. Also, if the 31st identification information is valid in the current PLMN and the UE moves to a new registration area that is different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the relation area belongs to the current PLMN, the UE may choose the default S-NSSAI indicated by the 31st identification for the IMS service. Also, if the 31st identification information is valid in the current PLMN and the UE moves to a new registration area that is different from the current registration area, and the UE is valid in the new registration area. The first S-NSSAI (which supports the IMS service) (16th identification information and / or 26th identification information and / or 36th identification information) has not been received and is a new resist. If the registration area does not belong to the current PLMN, the UE may not select the default S-NSSAI indicated by the 31st identification for the IMS service. Also, if the 31st identification information is valid in the current PLMN and the UE moves to a new registration area different from the current registration area, and the UE is valid in the new registration area. When receiving the first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall The first S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) may be selected for the IMS service. The UE then sends a registration request message containing the selected default S-NSSAI or the first S-NSSAI, or a PDU session establishment request message with the selected default S-NSSAI or the first S-NSSAI. good.
　また、UEは、コアネットワークから、すでに第12の識別情報及び15の識別情報を受信している場合、第12の識別情報と、第15の識別情報、又は第15の識別情報に含まれるS-NSSAIと、を対応付けて記憶してよい。この場合において、UEは、コアネットワークから、本手続きにおいて、第33の識別情報を受信したときは、第33の識別情報を記憶してよい。そして、IMSサービスのためのPDUセッションの確立を要求するときは、第12の識別情報と第15の識別情報と第33の識別情報に基づいて、第15の識別情報に含まれるS-NSSAI及び第36の識別情報で示される第1のS-NSSAIの中から、現在のレジストレーションエリアで有効な(使用可能な)S-NSSAIを選択し、そのS-NSSAIを含む登録要求メッセージを送信するか、又はそのS-NSSAIとともに、PDUセッション確立要求メッセージを送信してよい。 Further, when the UE has already received the twelfth identification information and the fifteenth identification information from the core network, the twelfth identification information and the fifteenth identification information or the S included in the fifteenth identification information. -NSSAI may be associated and stored. In this case, when the UE receives the 33rd identification information from the core network in this procedure, the UE may store the 33rd identification information. Then, when requesting the establishment of a PDU session for the IMS service, the S-NSSAI and S-NSSAI contained in the 15th identification information are based on the 12th identification information, the 15th identification information, and the 33rd identification information. From the first S-NSSAI indicated by the 36th identification information, select a valid (available) S-NSSAI in the current registration area and send a registration request message containing that S-NSSAI. Or, along with its S-NSSAI, a PDU session establishment request message may be sent.
　また、UEが、第1のレジストレーションエリアにおいて、IMSサービスのために第1のS-NSSAIを用いたPDUセッションを確立しており、第1のS-NSSAIは、IMSサービスに関して、第1のレジストレーションエリアでは有効(使用可能)であるが、第2のレジストレーションエリアで有効ではない場合であって、UEが、第2のレジストレーションエリアにおいて、すでにコアネットワークから第1のS-NSSAIを含む第15の識別情報又は第25の識別情報又は第36の識別情報を受信したか、又は本手続きにおいて第1のS-NSSAIを含む第36の識別情報を受信し、さらに、本手続きにおいて、第2のS-NSSAIを示す第36の識別情報と、第2のS-NSSAIに対応するIMSサービスを示す第35の識別情報と、を受信し、第2のS-NSSAIが、IMSサービスに関して、第2のレジストレーションエリアで有効である場合、UEは、第35の識別情報と第36の識別情報の受信に基づいて、(第2のレジストレーションエリアでIMSサービスをサポートする)第2のS-NSSAIを用いてIMSサービスのためのPDUセッション確立手続きを開始した後に、(第2のレジストレーションエリアでIMSサービスをサポートしない)第1のS-NSSAIを用いたPDUセッションを解放するためにPDUセッション解放手続きを開始する、あるいは、第1のS-NSSAIを用いたPDUセッションを解放するためにPDUセッション解放手続きを開始した後に、第2のS-NSSAIを用いてIMSサービスのためのPDUセッション確立手続きを開始してよい。尚、この場合において、UEは、第2のレジストレーションエリアで、第15の識別情報によって示される第1のS-NSSAIをIMSサービス以外の通信を行うために、使用してもよい。 In addition, the UE has established a PDU session using the first S-NSSAI for the IMS service in the first registration area, and the first S-NSSAI is the first for the IMS service. If it is valid (available) in the registration area but not in the second registration area, the UE has already issued the first S-NSSAI from the core network in the second registration area. Received the 15th identification information or the 25th identification information or the 36th identification information including, or received the 36th identification information including the 1st S-NSSAI in this procedure, and further in this procedure. The 36th identification information indicating the second S-NSSAI and the 35th identification information indicating the IMS service corresponding to the second S-NSSAI are received, and the second S-NSSAI regarding the IMS service. , If enabled in the second registration area, the UE will support the IMS service in the second registration area based on the receipt of the 35th and 36th identifications. To release the PDU session with the first S-NSSAI (which does not support the IMS service in the second registration area) after initiating the PDU session establishment procedure for the IMS service with S-NSSAI PDU for IMS service using the second S-NSSAI after initiating the PDU session release procedure or initiating the PDU session release procedure to release the PDU session using the first S-NSSAI You may start the session establishment procedure. In this case, the UE may use the first S-NSSAI indicated by the fifteenth identification information in the second registration area to perform communication other than the IMS service.
　また、UEが、予め、IMSサービスと、default S-NSSAI及び/又は第1のS-NSSAIと、を対応づけて記憶している場合、UEは、IMSサービスを用いた通信を行う場合は、default S-NSSAI又は第1のS-NSSAIを選択し、default S-NSSAI又は第1のS-NSSAIを含む登録要求メッセージを送信するか、又はdefault S-NSSAI又は第1のS-NSSAIとともに、PDUセッション確立要求メッセージを送信してもよい。 If the UE stores the IMS service in advance in association with the default S-NSSAI and / or the first S-NSSAI, the UE may use the IMS service for communication. Select default S-NSSAI or 1st S-NSSAI and send a registration request message containing default S-NSSAI or 1st S-NSSAI, or with default S-NSSAI or 1st S-NSSAI. A PDU session establishment request message may be sent.
　また、各装置は、UEポリシー管理コマンド、及び/又はUEポリシー管理コマンド拒絶メッセージの送受信に基づいて、本手続きを完了する。 In addition, each device completes this procedure based on the transmission / reception of the UE policy management command and / or the UE policy management command rejection message.
　さらに、UEは、UEポリシー管理コマンドメッセージ及び/又はUEポリシー管理コマンドメッセージに含まれる識別情報の受信に基づいて、3.2章の登録手続き、又は3.3章のジェネリックUE設定更新手続き、又は3.4章のUEポリシー管理手続き、又はSMのための手続きを開始してもよい。 In addition, the UE may use the registration procedure in Chapter 3.2, the generic UE setting update procedure in Chapter 3.3, or the UE in Chapter 3.4 based on the receipt of the identification information contained in the UE policy management command message and / or the UE policy management command message. You may initiate a policy management procedure or a procedure for SM.
　[4. 変形例]
　本発明の一態様に関わる装置で動作するプログラムは、本発明の一態様に関わる実施形態の機能を実現するように、Central Processing Unit(CPU)等を制御してコンピュータを機能させるプログラムであっても良い。プログラムあるいはプログラムによって取り扱われる情報は、一時的にRandom Access Memory(RAM)等の揮発性メモリあるいはフラッシュメモリ等の不揮発性メモリやHard Disk Drive(HDD)、あるいはその他の記憶装置システムに格納される。 [4. Modification example]
The program that operates on the apparatus according to one aspect of the present invention is a program that controls a Central Processing Unit (CPU) or the like to operate a computer so as to realize the functions of the embodiment according to one aspect of the present invention. Is also good. The program or the information handled by the program is 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 device system.
　尚、本発明の一態様に関わる実施形態の機能を実現する為のプログラムをコンピュータが読み取り可能な記録媒体に記録しても良い。この記録媒体に記録されたプログラムをコンピュータシステムに読み込ませ、実行する事によって実現しても良い。ここでいう「コンピュータシステム」とは、装置に内蔵されたコンピュータシステムであって、オペレーティングシステムや周辺機器等のハードウェアを含むものとする。また、「コンピュータが読み取り可能な記録媒体」とは、半導体記録媒体、光記録媒体、磁気記録媒体、短時間動的にプログラムを保持する媒体、あるいはコンピュータが読み取り可能なその他の記録媒体であっても良い。 It should be noted that the program for realizing the function of the embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. It may be realized by loading the program recorded on this recording medium into a computer system and executing it. The term "computer system" as used herein is a computer system built into a device and includes hardware such as an operating system and peripheral devices. Further, the "computer-readable recording medium" is a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another recording medium that can be read by a computer. Is also good.
　また、上述した実施形態に用いた装置の各機能ブロック、または諸特徴は、電気回路、たとえば、集積回路あるいは複数の集積回路で実装または実行され得る。本明細書で述べられた機能を実行するように設計された電気回路は、汎用用途プロセッサ、デジタルシグナルプロセッサ(DSP)、特定用途向け集積回路(ASIC)、フィールドプログラマブルゲートアレイ(FPGA)、またはその他のプログラマブル論理デバイス、ディスクリートゲートまたはトランジスタロジック、ディスクリートハードウェア部品、またはこれらを組み合わせたものを含んでよい。汎用用途プロセッサは、マイクロプロセッサでもよいし、従来型のプロセッサ、コントローラ、マイクロコントローラ、またはステートマシンであっても良い。前述した電気回路は、デジタル回路で構成されていてもよいし、アナログ回路で構成されていてもよい。また、半導体技術の進歩により現在の集積回路に代替する集積回路化の技術が出現した場合、本発明の一又は複数の態様は当該技術による新たな集積回路を用いる事も可能である。 Further, each functional block or various features of the device used in the above-described embodiment can be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein can be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or others. Programmable Logic Devices, Discrete Gate or Transistor Logic, Discrete Hardware Components, or Combinations thereof. The general purpose processor may be a microprocessor, a conventional processor, a controller, a microcontroller, or a state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. Further, when an integrated circuit technology that replaces the current integrated circuit appears due to the progress of semiconductor technology, one or a plurality of aspects of the present invention can also use a new integrated circuit according to the technology.
　なお、本願発明の一態様は上述の実施形態に限定されるものではない。実施形態では、装置の1例を記載したが、本願発明の一態様は、これに限定されるものではなく、屋内外に設置される据え置き型、または非可動型の電子機器、たとえば、AV機器、キッチン機器、掃除・洗濯機器、空調機器、オフィス機器、自動販売機、その他生活機器等の端末装置もしくは通信装置に適用出来る。 Note that one aspect of the present invention is not limited to the above-described embodiment. In the embodiment, an example of the device has been described, but one aspect of the present invention is not limited to this, and is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device. , Kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices such as living equipment.
　以上、この発明の実施形態に関して図面を参照して詳述してきたが、具体的な構成はこの実施形態に限られるものではなく、この発明の要旨を逸脱しない範囲の設計変更等も含まれる。また、本発明は、請求項に示した範囲で種々の変更が可能であり、異なる実施形態にそれぞれ開示された技術的手段を適宜組み合わせて得られる実施形態についても本発明の技術的範囲に含まれる。また、上記各実施形態に記載された要素であり、同様の効果を奏する要素同士を置換した構成も含まれる。 As described above, the embodiment of the present invention has been described in detail with reference to the drawings, but the specific configuration is not limited to this embodiment, and design changes and the like within a range not deviating from the gist of the present invention are also included. Further, the present invention can be variously modified within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in the different embodiments are also included in the technical scope of the present invention. Will be. Further, the elements described in each of the above-described embodiments are included, and a configuration in which elements having the same effect are replaced with each other is also included.

Claims (2)

  1. 送受信部と制御部とを備えるUE(User Equipment)であって、
    　前記送受信部は、
    　　AMF(Access and Mobility Management Function)から、Allowed NSSAI(Network Slice Selection Assistance Information)を含む登録受諾メッセージを受信し、
    　　PCF(Policy Control Function)から、URSP(UE Route Selection Policy)を含む、UEポリシー管理コマンドメッセージを受信し、
    　前記Allowed NSSAIは、IMSサービスのための第1のS-NSSAI(Single Network Slice Selection Assistance Information)を含み、
    　前記URSPは、前記第1のS-NSSAIと、第1の情報とを含み、
    　　前記第1の情報は、前記第1のS-NSSAIを使用可能なレジストレーションエリアを示す情報であり、
    　前記制御部は、IMSサービスのためのPDUセッションの確立を要求する場合に、前記URSPに基づいて、前記Allowed NSSAIに含まれる前記第1のS-NSSAIが現在のレジストレーションエリアで使用可能であると判断したときは、IMSサービスのために、前記第1のS-NSSAIを選択する、
    ことを特徴とするUE。     It is a UE (User Equipment) equipped with a transmission / reception unit and a control unit.
    The transmitter / receiver
    Receive a registration acceptance message including Allowed NSSAI (Network Slice Selection Assistance Information) from AMF (Access and Mobility Management Function).
    Receives UE policy management command messages including URSP (UE Route Selection Policy) from PCF (Policy Control Function).
    The Allowed NSSAI includes a first S-NSSAI (Single Network Slice Selection Assistance Information) for IMS services.
    The URSP includes the first S-NSSAI and the first information.
    The first information is information indicating a registration area in which the first S-NSSAI can be used.
    The first S-NSSAI included in the Allowed NSSAI can be used in the current registration area based on the URSP when the control unit requests the establishment of a PDU session for the IMS service. If so, select the first S-NSSAI for the IMS service.
    UE characterized by that.
  2. UE(User Equipment)によって実行される通信制御方法であって、
    　AMF(Access and Mobility Management Function)から、Allowed NSSAI(Network Slice Selection Assistance Information)を含む登録受諾メッセージを受信し、
    　PCF(Policy Control Function)から、URSP(UE Route Selection Policy)を含む、UEポリシー管理コマンドメッセージを受信し、
    　前記Allowed NSSAIは、IMSサービスのための第1のS-NSSAI(Single Network Slice Selection Assistance Information)を含み、
    　前記URSPは、前記第1のS-NSSAIと、第1の情報とを含み、
    前記第1の情報は、前記第1のS-NSSAI使用可能なレジストレーションエリアを示す情報であり、
    　IMSサービスのためのPDUセッションの確立を要求する場合に、前記URSPに基づいて、前記Allowed NSSAIに含まれる前記第1のS-NSSAIが現在のレジストレーションエリアで使用可能であると判断したときは、IMSサービスのために、前記第1のS-NSSAIを選択する、
    ことを特徴とするUEによって実行される通信制御方法。     It is a communication control method executed by UE (User Equipment).
    Receive a registration acceptance message including Allowed NSSAI (Network Slice Selection Assistance Information) from AMF (Access and Mobility Management Function).
    Receives UE policy management command messages including URSP (UE Route Selection Policy) from PCF (Policy Control Function).
    The Allowed NSSAI includes a first S-NSSAI (Single Network Slice Selection Assistance Information) for IMS services.
    The URSP includes the first S-NSSAI and the first information.
    The first information is information indicating the registration area where the first S-NSSAI can be used.
    When requesting the establishment of a PDU session for the IMS service, based on the URSP, when it is determined that the first S-NSSAI contained in the Allowed NSSAI is available in the current registration area. , Select the first S-NSSAI for IMS service,
    A communication control method performed by a UE that is characterized by that.
PCT/JP2021/033438 2020-09-18 2021-09-13 User equipment (ue) WO2022059627A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2022550535A JPWO2022059627A1 (en) 2020-09-18 2021-09-13

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020-157079 2020-09-18
JP2020157079 2020-09-18

Publications (1)

Publication Number Publication Date
WO2022059627A1 true WO2022059627A1 (en) 2022-03-24

Family

ID=80777025

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/033438 WO2022059627A1 (en) 2020-09-18 2021-09-13 User equipment (ue)

Country Status (2)

Country Link
JP (1) JPWO2022059627A1 (en)
WO (1) WO2022059627A1 (en)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Pseudo-CR on initial version", 3GPP DRAFT; C1-204656, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 12 August 2020 (2020-08-12), XP051918791 *
KDDI, TOYOTA ITC, HUAWEI, INTEL: "Update of TS 23.503 for xBDT", 3GPP DRAFT; S2-1904353_WAS2963_XBDT-KDDI, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 12 April 2019 (2019-04-12), XP051720134 *
SHARP: "Proposal of solution for Key issue X found in C1-206198", 3GPP DRAFT; C1-206199, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 8 October 2020 (2020-10-08), XP051951140 *

Also Published As

Publication number Publication date
JPWO2022059627A1 (en) 2022-03-24

Similar Documents

Publication Publication Date Title
WO2021205955A1 (en) User equipment (ue) and communication method for ue
WO2021215228A1 (en) User equipment (ue) and access and mobility management function (amf)
WO2021241114A1 (en) User equipment (ue), core network device, access and mobility management function (amf), and session management function (smf)
WO2021060383A1 (en) User device and core network device
WO2022097703A1 (en) User equipment (ue) and communication control method performed by ue
WO2021132288A1 (en) User Equipment (UE)
JP2023002850A (en) User device and communication control method
WO2022097702A1 (en) User equipment (ue) and communication control method executed by ue
WO2022004699A1 (en) User equipment (ue) and communication control method for ue
WO2021193937A1 (en) Ue (user equipment)
WO2021132502A1 (en) Ue, control device, and communication control method
WO2021029380A1 (en) User equipment
JP2021166360A (en) UE (User Equipment)
WO2022059627A1 (en) User equipment (ue)
WO2022097623A1 (en) User equipment (ue)
WO2022030474A1 (en) Ue (user equipment)
WO2021132287A1 (en) User Equipment (UE)
WO2023157484A1 (en) User equipment (ue)
WO2023157486A1 (en) User equipment (ue)
WO2021215227A1 (en) Ue (user equipment)
WO2023157485A1 (en) User equipment (ue)
WO2022138731A1 (en) User equipment (ue)
WO2022138730A1 (en) User equipment (ue)
WO2022004700A1 (en) User equipment (ue) and communication method for ue
WO2022097701A1 (en) User equipment (ue) and communication control method performed by ue

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21869314

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022550535

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21869314

Country of ref document: EP

Kind code of ref document: A1