WO2022097623A1 - Équipement utilisateur (ue) - Google Patents

Équipement utilisateur (ue) Download PDF

Info

Publication number
WO2022097623A1
WO2022097623A1 PCT/JP2021/040340 JP2021040340W WO2022097623A1 WO 2022097623 A1 WO2022097623 A1 WO 2022097623A1 JP 2021040340 W JP2021040340 W JP 2021040340W WO 2022097623 A1 WO2022097623 A1 WO 2022097623A1
Authority
WO
WIPO (PCT)
Prior art keywords
nssai
identification information
ims service
pdu session
information
Prior art date
Application number
PCT/JP2021/040340
Other languages
English (en)
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 JP2022560776A priority Critical patent/JPWO2022097623A1/ja
Publication of WO2022097623A1 publication Critical patent/WO2022097623A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • 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

Definitions

  • the present invention relates to UE (User Equipment).
  • UE User Equipment
  • 3GPP TS 23.501 V16.6.0 (2020-09); 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.6.0 (2020-09); 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.6.0 (2020-09); 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 it is clear how to select S-NSSAI used for communication for IMS (hereinafter, also referred to as IMS service) using SIP (Session Initiation Protocol). It has not become.
  • SIP Session Initiation Protocol
  • An object of one aspect of the present invention has been made in view of the above circumstances, and in 5GS, one or more IMS services are connected to one or more IMS networks via one or more network slices. It is to provide an efficient selection method of S-NSSAI necessary for doing so.
  • the UE of one aspect of the present invention is a UE (User Equipment) including a transmission / reception unit and a control unit, and the transmission / reception unit is used from AMF (Access and Mobility Management Function) to Allowed NSSAI (Network Slice) in the registration procedure.
  • AMF Access and Mobility Management Function
  • Allowed NSSAI Network Slice
  • the Allowed NSSAI is a first S-NSSAI (Single Network Slice Selection Assistance Information) for SIP signaling for the first IMS service and a second S- for media for the first IMS service.
  • the URSP includes the first S-NSSAI, the second S-NSSAI, and the first information, and the first information includes the first S-NSSAI and the first information.
  • the first information includes the first S-NSSAI and the first information.
  • information indicating a registration area where the second S-NSSAI can be used based on the URSP when the control unit requests the establishment of a PDU session for the first IMS service.
  • the first S-NSSAI is used for the first IMS service. It is characterized by selecting NSSAI and the second S-NSSAI.
  • the UE of another aspect of the present invention is a UE (User Equipment) including a transmission / reception unit and a control unit, and the transmission / reception unit is changed from AMF (Access and Mobility Management Function) to Allowed NSSAI in the registration procedure.
  • URSP User Radio Selection Policy
  • PCF Policy Control Function
  • the Allowed NSSAI is the first S-NSSAI (Single Network Slice Selection Assistance Information) for SIP signaling for the first IMS service and the first for voice media for the first IMS service.
  • the URSP includes the first S-NSSAI and the third S-NSSAI for the video media for the first IMS service, the URSP being the first S-NSSAI and the second S-NSSAI. And / or the first S-NSSAI and / or the second S-NSSAI and / or the third information, including the third S-NSSAI and the first information.
  • Information indicating a registration area in which S-NSSAI can be used, and when the control unit requests the establishment of a PDU session for the first IMS service, the first is based on the URSP.
  • the first IMS service may be used. It is characterized in that S-NSSAI and the second S-NSSAI and the third S-NSSAI are selected.
  • the UE of still another aspect of the present invention is a UE (User Equipment) including a transmission / reception unit and a control unit, and the transmission / reception unit is Allowed from AMF (Access and Mobility Management Function) in the registration procedure.
  • AMF Access and Mobility Management Function
  • URSP User Equipment
  • PCF Policy Control Function
  • said URSP includes said first S-NSSAI, said second S-NSSAI, and first information, the first information being said first S-NSSAI and / or said.
  • the first S-NSSAI is selected for the first IMS service and the second IMS service is selected.
  • the second S-NSSAI contained in the Allowed NSSAI is available in the current registration area when requesting the establishment of a PDU session for the above. It is characterized in that the second S-NSSAI is selected for the second IMS service.
  • an efficient selection method for S-NSSAI required to connect one or more IMS services to one or more IMS networks via one or more network slices in 5GS. Can be provided.
  • 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. It is a figure explaining the PDU session establishment 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 a 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 / receive user data and / or control information to / from the access network device and / or the core network device and / or the PDN and / or DN by 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 part_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 includes registration procedure (Registration procedure), non-registration procedure (De-registration procedure), and generic UE configuration update procedure (hereinafter referred to as UE configuration update procedure).
  • Registration procedure Registration procedure
  • De-registration procedure non-registration procedure
  • UE configuration update procedure UE configuration update procedure
  • authentication / approval procedure authentication / approval procedure
  • service request procedure Service request procedure
  • paging procedure Paging procedure
  • notification procedure Notification procedure
  • 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 technique.
  • 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 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 also refers to the network slice corresponding to IMS (hereinafter, also referred to as IMS service, or IMS session, or SIP session, or PDU session for IMS, or service provided by IMS). Information to identify.
  • 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 is valid (usable) in the first registration area (hereinafter also referred to as the registration area and RA) for the IMS service, but it is not valid in the second registration area. It may be no S-NSSAI. 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. May be.
  • the 3rd S-NSSAI, the 4th S-NSSAI, the 5th S-NSSAI, the 6th S-NSSAI, the 7th S-NSSAI, and the 8th S-NSSAI, and The ninth S-NSSAI, the tenth S-NSSAI, the eleventh S-NSSAI, the twelfth S-NSSAI, and the thirteenth S-NSSAI each identify the network slice corresponding to the IMS. Information to be done.
  • the third S-NSSAI may be information that identifies a network slice for SIP signaling for the first IMS service.
  • the fourth S-NSSAI may be information for identifying a network slice for media (for example, audio and video) for the first IMS service.
  • the ninth S-NSSAI may be information for identifying a network slice for media (for example, voice) for the first IMS service.
  • the tenth S-NSSAI may be information for identifying a network slice for media (for example, video) for the first IMS service.
  • audio and video are assumed as the media for the first IMS service, and the case where audio and video are treated as one is expressed as the fourth S-NSSAI, and audio.
  • the fourth S-NSSAI may be associated with the ninth S-NSSAI and the tenth S-NSSAI.
  • the fourth S-NSSAI may be a concept including the ninth S-NSSAI and the tenth S-NSSAI.
  • the description regarding the fourth S-NSSAI may be read as the description regarding the ninth S-NSSAI and the tenth S-NSSAI, and the description regarding the ninth S-NSSAI and the tenth S-NSSAI. The description may be read as the description regarding the fourth S-NSSAI.
  • the fifth S-NSSAI may be information that identifies a network slice for SIP signaling for the second IMS service.
  • the sixth S-NSSAI may be information identifying a network slice for media (eg, audio and video) for the second IMS service.
  • the eleventh S-NSSAI may be information identifying a network slice for media (eg, voice) for the second IMS service.
  • the twelfth S-NSSAI may be information for identifying a network slice for media (for example, video) for the second IMS service.
  • audio and video are assumed as media for the second IMS service, and the case where audio and video are treated as one is expressed as the sixth S-NSSAI, and audio.
  • the sixth S-NSSAI may be associated with the eleventh S-NSSAI and the twelfth S-NSSAI.
  • the sixth S-NSSAI may be a concept including the eleventh S-NSSAI and the twelfth S-NSSAI.
  • the description regarding the sixth S-NSSAI may be read as the description regarding the eleventh S-NSSAI and the twelfth S-NSSAI, and the description regarding the eleventh S-NSSAI and the twelfth S-NSSAI. May be read as the description regarding the sixth S-NSSAI.
  • the third S-NSSAI, the fourth S-NSSAI, the fifth S-NSSAI, the sixth S-NSSAI, the ninth S-NSSAI, and the tenth S-NSSAI, and At least a part of the eleventh S-NSSAI and the twelfth S-NSSAI may have the same value or may all have different values.
  • the fact that the values of S-NSSAI are the same may mean that the network slices identified by S-NSSAI are the same.
  • different values of S-NSSAI may mean that the network slices identified by S-NSSAI are different.
  • the seventh S-NSSAI may be information that identifies the network slice of the first IMS service.
  • the eighth S-NSSAI may be information for identifying the network slice of the second IMS service.
  • the 7th S-NSSAI may be associated with the 3rd S-NSSAI and the 4th S-NSSAI.
  • the 7th S-NSSAI may be a concept including the 3rd S-NSSAI and the 4th S-NSSAI.
  • the description regarding the 7th S-NSSAI may be read as the description regarding the 3rd S-NSSAI and the 4th S-NSSAI, and the description regarding the 3rd S-NSSAI and the 4th S-NSSAI. May be read as the description regarding the 7th S-NSSAI.
  • the 7th S-NSSAI may be associated with the 3rd S-NSSAI, the 9th S-NSSAI, and the 10th S-NSSAI.
  • the seventh S-NSSAI may be a concept including the third S-NSSAI and the ninth S-NSSAI and the tenth S-NSSAI.
  • the description regarding the 7th S-NSSAI may be read as the description regarding the 3rd S-NSSAI and the 9th S-NSSAI and the 10th S-NSSAI, and may be read as the description regarding the 3rd S-NSSAI and the 3rd S-NSSAI.
  • the description regarding the 9th S-NSSAI and the 10th S-NSSAI may be read as the description regarding the 7th S-NSSAI.
  • the 8th S-NSSAI may be associated with the 5th S-NSSAI and the 6th S-NSSAI.
  • the eighth S-NSSAI may be a concept including the fifth S-NSSAI and the sixth S-NSSAI.
  • the description regarding the 8th S-NSSAI may be read as the description regarding the 5th S-NSSAI and the 6th S-NSSAI, and the description regarding the 5th S-NSSAI and the 6th S-NSSAI. May be read as the description regarding the 8th S-NSSAI.
  • the 8th S-NSSAI may be associated with the 5th S-NSSAI, the 11th S-NSSAI, and the 12th S-NSSAI.
  • the eighth S-NSSAI may be a concept including the fifth S-NSSAI and the eleventh S-NSSAI and the twelfth S-NSSAI.
  • the description regarding the 8th S-NSSAI may be read as the description regarding the 5th S-NSSAI and the 11th S-NSSAI and the 12th S-NSSAI, and may be read as the description regarding the 5th S-NSSAI and the 5th S-NSSAI.
  • the description regarding the 11th S-NSSAI and the 12th S-NSSAI may be read as the description regarding the 8th S-NSSAI.
  • the 7th S-NSSAI and the 8th S-NSSAI may have the same value or different values.
  • the same value of the 7th S-NSSAI and the 8th S-NSSAI means that the 3rd S-NSSAI, the 4th S-NSSAI, the 5th S-NSSAI, and the 6th It may mean that the values of S-NSSAI in are all the same.
  • the values of the 7th S-NSSAI and the 8th S-NSSAI are different from each other, that is, the 3rd S-NSSAI, the 9th S-NSSAI, the 10th S-NSSAI, and the 5th S.
  • -It may mean that at least some of the values of NSSAI, 11th S-NSSAI, and 12th S-NSSAI are different.
  • the thirteenth S-NSSAI is the first S-NSSAI and / or the second S-NSSAI, and / or the third S-NSSAI, and / or the fourth S-NSSAI, and /. Or the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 7th S-NSSAI and / or the 8th S-NSSAI and / or the 9th S-NSSAI, and / Or as meaning the tenth S-NSSAI and / or the eleventh S-NSSAI and / or the twelfth S-NSSAI, as defined herein.
  • the thirteenth S-NSSAI is used as a general term for all combinations of the first to twelfth identification information for the sake of simplification of explanation.
  • the thirteenth S-NSSAI may refer to the first S-NSSAI, and in another part, the thirteenth S-NSSAI may refer to the third S.
  • -It can also refer to NSSAI and the 4th S-NSSAI, and elsewhere, the 13th S-NSSAI is the 3rd S-NSSAI and the 9th S-NSSAI and the 10th S.
  • the thirteenth S-NSSAI may have one or more meanings, not just a single meaning, as it may refer to NSSAI.
  • the PDU session establishment procedure when executed using S-NSSAI with the same value, it may mean that the network slices used by the established PDU session are the same. Also, when the PDU session establishment procedure is executed using S-NSSAI with different values, it may mean that the network slice used by the established PDU session is different.
  • the IMS network is composed of each device and / or function that provides the IMS service, and may exist in the DN. Further, when a plurality of IMS services exist, each device and / or a function and / or a network that provides each IMS service may exist in the same DN or exist in different DNs. May be good. In other words, a PDU session for each IMS service may be established for the same or different DNs via the same or different network slices.
  • a PDU session for the IMS service may be established on a slice-by-slice basis. Specifically, a PDU session for SIP signaling and a PDU session for media for IMS services may be established for each slice. Conversely, for each slice, one PDU session for the IMS service may be established, or the PDU session for the IMS service may be used for SIP signaling and data for media for the IMS service. And may be sent and received.
  • the 3rd S-NSSAI, the 4th S-NSSAI, the 5th S-NSSAI, the 6th S-NSSAI, the 7th S-NSSAI, and the 8th S-NSSAI, and / Or the 9th S-NSSAI and / or the 10th S-NSSAI, and / or the 11th S-NSSAI, and / or the 12th S-NSSAI are Allowed NSSAI and default NSSAI (hereinafter, default NSSAI). Also referred to as).
  • 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 containing the default S-NSSAI that supports communication using IMS.
  • the default S-NSSAI may be one or more S-NSSAIs constituting the thirteenth 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 IMS service is SIP signaling (hereinafter, may be simply referred to as signaling) corresponding to a control signal (also referred to as control information) in the SIP layer, and / or user data (also referred to as a non-control signal) in the SIP layer. It may mean a medium corresponding to (referred to).
  • the IMS service may mean a service provided by IMS.
  • the IMS service may be an MMTEL (Multimedia Telephony) communication service.
  • the IMS service may be an MMTEL video service and / or an MMTEL audio service, and / or other services using MMTEL communication.
  • IMS services are voice services (also referred to as IMS Voice services) and / or video services (also referred to as IMS Video services), and / or RCS (Rich Communication Services), and / or other services. May be good.
  • 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 the thirteenth 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. Further, the first identification information may be at least one of the S-NSSAI represented by the third 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 thirteenth 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 or different from the S-NSSAI included in the 25th identification information. Further, the third identification information may be the same as the 36th identification information.
  • the fourth identification information is UE ability information.
  • the fourth identification information may be 5 GMM capability. Further, the fourth identification information may indicate whether or not the UE supports a certain function. Further, the fourth identification information may be capability information indicating whether or not it is possible to provide a service by IMS via a plurality of slices. Further, the fourth identification information may be capability information indicating that communication using a PDU session for media using a network slice different from the network slice used for the PDU session for SIP signaling is possible. ..
  • the fifth identification information is information indicating that the provision of services by IMS is requested via a plurality of slices.
  • the fifth identification information indicates that the establishment of a PDU session for SIP signaling for the IMS service is requested, and / or the establishment of a PDU session for the media for the IMS service is requested. It may be information indicating and / or requesting the establishment of a PDU session for the IMS service.
  • the sixth identification information is information including at least a part of the first to fifth 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. Further, the eleventh identification information may be at least one of the S-NSSAI represented by the sixteenth 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 thirteenth S-NSSAI is valid in the registration area and / or information indicating whether or not the thirteenth S-NSSAI is valid in the current registration area. And / or even information indicating whether the 13th S-NSSAI is valid within the current PLMN, and / or information indicating whether the 13th S-NSSAI is valid in all PLMNs. good.
  • the twelfth identification information may be configured as information for each S-NSSAI. .. In other words, the twelfth identification information may be configured and transmitted as many as the number of S-NSSAI contained in the fifteenth identification information.
  • 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 thirteenth 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, and / or information indicating whether the 13th S-NSSAI is valid in the current PLMN (Public Land Mobile Network), and / or whether the 13th 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 thirteenth S-NSSAI is valid in the current registration area for each access type, and / or the thirteenth 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 thirteenth 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 thirteenth 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 thirteenth 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 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.
  • 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.
  • the nth S-NSSAI from the beginning 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 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 fifteenth identification information may include one or more S-NSSAIs that do not support the IMS service.
  • the 16th identification information is the 13th 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 is network capability information.
  • the 17th identification information may be 5GS network feature support.
  • the 17th identification information may indicate whether or not the network supports a certain function.
  • the 17th identification information may be capability information indicating whether or not it is possible to provide a service by IMS via a plurality of slices.
  • the 18th identification information is information indicating that the provision of services by IMS is permitted via a plurality of slices. Also, the 18th identification information indicates that the establishment of a PDU session for SIP signaling for the IMS service is permitted, and / or the establishment of a PDU session for the media for the IMS service is permitted. It may be the information to indicate and / or the information to allow the establishment of a PDU session for the IMS service.
  • the 19th identification information may be information including at least a part of the 11th to 18th 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. Further, the 21st identification information may be at least one of the S-NSSAI indicated by the 26th identification information.
  • the 22nd identification information is information indicating whether the 13th S-NSSAI is valid in the registration area and / or information indicating whether or not the 13th S-NSSAI is valid in the current registration area. And / or information indicating whether the thirteenth S-NSSAI is valid in the current PLMN, and / or information indicating whether the thirteenth S-NSSAI is valid in all PLMNs.
  • the 22nd identification information may be configured as information for each S-NSSAI. .. In other words, the 22nd identification information may be configured and transmitted as many as the number of S-NSSAI contained in the 25th identification information.
  • 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 13th 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, and / or information indicating whether the 13th S-NSSAI is valid in the current PLMN (Public Land Mobile Network), and / or whether the 13th 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 13th S-NSSAI is valid in the current registration area for each access type, and / or the 13th 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 thirteenth 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 13th 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 thirteenth 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. 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). Also, the fifteenth identification information may include one or more S-NSSAIs that do not support the IMS service.
  • the 26th identification information is the 13th 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. Further, the 31st identification information may be at least one of the S-NSSAI indicated by the 36th identification information.
  • the 32nd identification information is information indicating whether the 13th S-NSSAI is valid in the registration area and / or information indicating whether or not the 13th S-NSSAI is valid in the current registration area. And / or information indicating whether the thirteenth S-NSSAI is valid in the current PLMN, and / or information indicating whether the thirteenth S-NSSAI is valid in all PLMNs.
  • the 32nd identification information may be configured as information for each S-NSSAI. .. In other words, the 32nd identification information may be configured and transmitted as many as the number of S-NSSAI contained in the 33rd identification information.
  • 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 13th 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, and / or information indicating whether the 13th S-NSSAI is valid in the current PLMN (Public Land Mobile Network), and / or whether the 13th 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 13th S-NSSAI is valid in the current registration area for each access type, and / or the 13th 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 thirteenth 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 13th 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 thirteenth 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. Also, the 33rd identification information may include one or more S-NSSAIs that do not support the IMS service.
  • 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 13th 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, when the PCF receives the information about the Allowed NSSAI received from the AMF, the 36th identification information is at least the 13th S-NSSAI selected from one or more S-NSSAI included in the Allowed NSSAI. It may be a part.
  • the 36th identification may be at least part of the 13th 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 13th 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.
  • 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.
  • 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).
  • the 51st identification information is the PDU session ID that identifies the PDU session. Further, the 51st identification information may be a PDU session ID that identifies the PDU session requesting establishment.
  • the 52nd identification information is a PDU session type that identifies the type of PDU session. Further, the 52nd identification information may be the PDU session type requested by the UE for the PDU session. Further, the 52nd identification information may indicate any one of IPv4, IPv6, IPv4v6, Unstructured, and Ethernet (registered trademark).
  • the 53rd identification information is in SSC mode. Further, the 53rd identification information may be the SSC mode requested by the UE for the PDU session. Further, the 53rd identification information may indicate any one of SSC mode 1, SSC mode 2, and SSC mode 3.
  • the 54th identification information is UE ability information.
  • the 54th identification information may be 5 GSM capability. Further, the 54th identification information may indicate whether or not the UE supports a certain function. Further, the 54th identification information may be capability information indicating whether or not it is possible to provide a service by IMS via a plurality of slices.
  • the 55th identification information is information indicating that the provision of services by IMS is requested via a plurality of slices. Also, the 55th identification information indicates that it requests the establishment of a PDU session for SIP signaling for the IMS service and / or requests the establishment of a PDU session for the media for the IMS service. It may be information indicating and / or requesting the establishment of a PDU session for the IMS service.
  • the 56th identification information is 1 or more S-NSSAI. Further, the 56th identification information may be one or more S-NSSAI required by the UE for the PDU session to be established. Further, the 56th identification information may be at least one of the 1st to 12th S-NSSAI.
  • the 57th identification information is DNN. Further, the 57th identification information may be a DNN that identifies the DN to which the PDU session requested to be established by the UE is connected.
  • the 58th identification information is the PDU session ID that identifies the PDU session. Further, the 58th identification information may be a PDU session ID that identifies an already established PDU session. For example, the 58th identification information may be a PDU session ID for identifying PDU sessions for IMS services if they have already been established.
  • the 59th identification information is identification information including at least two of the 51st to 58th identification information.
  • the 61st identification information is the PDU session ID that identifies the PDU session. It may be a PDU session ID that identifies the PDU session that is allowed to be established by the network.
  • the 62nd identification information is a PDU session type that identifies the type of PDU session. Also, the 62nd identification information may be the PDU session type selected by the network. Further, the 62nd identification information may indicate any one of IPv4, IPv6, IPv4v6, Unstructured, and Ethernet (registered trademark).
  • the 63rd identification information is in SSC mode. Also, the 63rd identification information may be the SSC mode selected by the network for the PDU session. Further, the 63rd identification information may indicate any one of SSC mode 1, SSC mode 2, and SSC mode 3.
  • the 64th identification information is network capability information.
  • the 64th identification information may be 5GSM network feature support.
  • the 64th identification information may indicate whether or not the network supports a certain function.
  • the 64th identification information may be capability information indicating whether or not it is possible to provide a service by IMS via a plurality of slices.
  • the 65th identification information is information indicating that the provision of services by IMS is permitted via a plurality of slices.
  • the 65th identification information indicates that the establishment of a PDU session for SIP signaling for the IMS service is permitted, and / or the establishment of a PDU session for the media for the IMS service is permitted. It may be the information to indicate and / or the information to allow the establishment of a PDU session for the IMS service.
  • the 66th identification information is 1 or more S-NSSAI.
  • the 67th identification information is DNN. Further, the 67th identification information may be a DNN that identifies the DN to which the PDU session is connected.
  • the 68th identification information is identification information including at least two of the 61st to 67th identification information.
  • the procedures used in the first embodiment include the registration procedure in Chapter 3.2 and / or the generic UE setting update procedure (UE setting update procedure) in Chapter 3.3, and / or the UE policy update procedure in Chapter 3.4 (UE policy management). procedure) and / or the procedure for establishing a PDU session in Chapter 3.5 is included.
  • 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 completes the registration procedure in Chapter 3.2, the generic UE setting update procedure in Chapter 3.3, the UE policy management procedure in Chapter 3.4, or the procedure for SM (for example, establishing a PDU session in Chapter 3.5).
  • the registration procedure may be started based on the completion of (including 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 identification information out of the identification information 1 to 6 by including it in the registration request message and / or the RRC message.
  • the identification information of Nos. 1 to 6 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.
  • 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 sixth to the network, the capability 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 sixth.
  • 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 obtained from the Allowed NSSAI by the PCF.
  • the 13th S-NSSAI is selected, the 13th S-NSSAI indicated by the 36th identification information is used as the 3rd identification information for the IMS service based on the 33rd identification information. You may choose to send a third identification.
  • the UE 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. In addition, the UE 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 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.
  • you have not received a valid 13th S-NSSAI (16th Identification and / or 26th Identification and / or 36th Identification) that is valid for the IMS service it is new.
  • 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 that is different from the current registration area, and the UE is valid in the new registration area.
  • 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. You can do it.
  • the eleventh 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 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 For the IMS service, select the 13th S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) as the third identification information, 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 that is different from the current registration area, and the UE is the new registration area.
  • you have not received a valid 13th S-NSSAI (16th Identification and / or 26th Identification and / or 36th Identification) that is valid for the IMS service it is new.
  • 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.
  • 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. Has not received the 13th S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service) 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. You can do it.
  • the UE may not select the default S-NSSAI indicated by the 21st identification information as the 1st identification information for the IMS service. At this time, the UE does not have to transmit the first identification information.
  • the UE When receiving the 13th S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall For the IMS service, select the 13th S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) as the third identification information, 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 that is different from the current registration area, and the UE is the new registration area.
  • you have not received a valid 13th S-NSSAI (16th Identification and / or 26th Identification and / or 36th Identification) that is valid for the IMS service it is new.
  • 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. Has not received the 13th S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service) 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. You can do it.
  • the UE may not select the default S-NSSAI indicated by the 31st identification information as the 1st identification information for the IMS service. At this time, the UE does not have to transmit the first identification information.
  • the UE When receiving the 13th S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall For the IMS service, select the 13th S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) as the third identification information, and the third identification information. Identification information may be transmitted.
  • the UE when the UE wants to know the effective range of the registration area of the 13th S-NSSAI that supports the IMS service when communicating using the IMS service, in other words, the 13th that supports the IMS service.
  • the second identification information may be transmitted.
  • 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 thirteenth 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 communicating 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 may configure the SST or SST included in the 15th identification information. If the value of SD is S-NSSAI such as indicating the IMS service, that S-NSSAI may be selected as the third identification information and the third identification information may be transmitted.
  • S-NSSAI such as indicating 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 such as indicating 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 15th identification information from the core network and is included in the 15th 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 you select the 13th S-NSSAI that supports the IMS service from the 1 or more S-NSSAI included and send the 13th S-NSSAI as the 3rd identification information based on that information. good.
  • the UE knows the position of the thirteenth 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 thirteenth S-NSSAI may be identified without receiving information that explicitly indicates the correspondence between the IMS service and the thirteenth 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 you select the 13th S-NSSAI that supports the IMS service from the 1 or more S-NSSAI included and send the 13th S-NSSAI as the 3rd identification information based on that information. good.
  • the UE knows the position of the thirteenth 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 thirteenth S-NSSAI may be identified without receiving information that explicitly indicates the correspondence between the IMS service and the thirteenth S-NSSAI, such as the identification information of 34.
  • the UE communicates using the IMS service
  • 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.
  • the 13th S-NSSAI (which supports IMS) is selected from the 1 or more S-NSSAI included in the 15th identification information, and the 13th S-NSSAI is used as the 3rd 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 13th S-NSSAI (which supports IMS) is selected from the 1 or more S-NSSAI included in the 25th identification information, and the 13th S-NSSAI is used as the 3rd 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 thirteenth 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 6, 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, 5GAN (or gNB) may select new AMF to which the registration request message is sent based on at least one identification information among the identification information 1 to 6.
  • 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 new 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 determined regardless of whether the NSSAI includes the 13th S-NSSAI that supports IMS. It may be true.
  • new AMF has an NSSAI (Allowed NSSAI) allowed for the UE and there is a thirteenth S-NSSAI that supports IMS allowed for the UE, the first condition determination is true. You may.
  • new AMF has NSSAI (Allowed NSSAI) allowed for UE and there is no 13th 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 AMF indicated by 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 19th identification information.
  • the identification information of Chapters 11 to 19 may be as described in Chapter 2.7.
  • the new AMF may indicate that the network supports each function by sending these identification information and / or control messages, or may indicate that the UE request has been accepted. 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.
  • new AMF will indicate which of the 11th to 19th identification information is included in the control message, each identification information received, and / or subscriber information, and / or network capability information, and /. Alternatively, it may be selected and determined based on the operator policy, / or the network status, and / or the user's registration information, and / or the context held by new AMF.
  • the new AMF when new AMF receives at least one of the identification information of the first to the sixth from the UE, the new AMF sends at least one of the identification information of the eleventh to the nineteenth identification information by including the identification information in the control message. good.
  • new AMF receives at least one of the identification information 1 to 6 from the UE, and when the setting information of the UE is updated from the previous registration procedure, the 11th to 19th The identification information may be sent including the updated information.
  • new AMF will receive 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 /.
  • the UE request has been accepted by sending a registration acceptance message based on the context held by AMF, or the UE request has been rejected by sending a registration refusal message. You may show that.
  • 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 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 19th 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 when the UE receives fifteen identification information from the core network, including a third S-NSSAI and a fourth S-NSSAI, it requests the establishment of a PDU session for the first IMS service. Selects the 3rd S-NSSAI and the 4th S-NSSAI from the 15th identification information for the 1st IMS service, and uses the 3rd S-NSSAI in Chapter 3.5.
  • PDU session establishment procedure (hereinafter referred to simply as PDU session establishment procedure) is executed to establish a PDU session for SIP signaling for the first IMS service, and PDU using the fourth S-NSSAI. You may perform a session establishment procedure to establish a PDU session for the media for the first IMS service.
  • the UE receives from the core network the fifteenth identification information, including the third S-NSSAI and the ninth S-NSSAI and the tenth S-NSSAI, the UE also receives a PDU for the first IMS service.
  • the UE When requesting the establishment of a session, select the 3rd S-NSSAI, 9th S-NSSAI and 10th S-NSSAI from the 15th identification information for the 1st IMS service. Execute the PDU session establishment procedure using the third S-NSSAI to establish the PDU session for SIP signaling for the first IMS service, and the PDU session using the ninth S-NSSAI.
  • the first IMS service For, select the 7th S-NSSAI from the 15th identification information, execute the PDU session establishment procedure using the 7th S-NSSAI, and for the 1st IMS service.
  • a PDU session may be established.
  • the UE receives the fifteenth identification information from the core network, including the third S-NSSAI and the fourth S-NSSAI and the seventh S-NSSAI, the UE also receives a PDU for the first IMS service.
  • the third S-NSSAI which is the information that identifies the network slice corresponding to the seventh S-NSSAI from the fifteenth identification information.
  • select the 4th S-NSSAI execute the PDU session establishment procedure using the 3rd S-NSSAI, establish the PDU session for SIP signaling for the 1st IMS service, and the 4th.
  • the PDU session establishment procedure using S-NSSAI may be performed to establish a PDU session for media for the first IMS service.
  • the UE when the UE receives the fifteenth identification information including the third S-NSSAI, the seventh S-NSSAI, the ninth S-NSSAI, and the tenth S-NSSAI from the core network, the first When requesting the establishment of a PDU session for the IMS service of, the information that identifies the network slice corresponding to the 7th S-NSSAI from the 15th identification information for the 1st IMS service. Select a third S-NSSAI, a ninth S-NSSAI, and a tenth S-NSSAI, perform a PDU session establishment procedure using the third S-NSSAI, and perform the first IMS service.
  • the PDU session establishment procedure using the 10th S-NSSAI may be executed to establish the PDU session for the media (video) for the 1st IMS service.
  • the UE when the UE receives fifteen identification information from the core network, including the fifth S-NSSAI and the sixth S-NSSAI, it requests the establishment of a PDU session for the second IMS service. Selects the 5th S-NSSAI and the 6th S-NSSAI from the 15th identification information for the 2nd IMS service, and establishes a PDU session using the 5th S-NSSAI. Perform the procedure to establish a PDU session for SIP signaling for the second IMS service, and perform the PDU session establishment procedure with the sixth S-NSSAI for the second IMS service. You may establish a PDU session for your media.
  • the UE receives the fifteenth identification information from the core network, including the fifth S-NSSAI and the eleventh S-NSSAI and the twelfth S-NSSAI
  • the UE also receives a PDU for the second IMS service.
  • the first IMS service For, select the 8th S-NSSAI from the 15th identification information, execute the PDU session establishment procedure using the 8th S-NSSAI, and for the 2nd IMS service.
  • a PDU session may be established.
  • the UE receives the fifteenth identification information from the core network, including the fifth S-NSSAI and the sixth S-NSSAI and the eighth S-NSSAI, the UE also receives a PDU for the second IMS service.
  • the fifth S-NSSAI which is the information that identifies the network slice corresponding to the eighth S-NSSAI from the fifteenth identification information.
  • select the 6th S-NSSAI perform the PDU session establishment procedure using the 5th S-NSSAI, establish the PDU session for SIP signaling for the 2nd IMS service, and the 6th.
  • the PDU session establishment procedure using S-NSSAI may be performed to establish a PDU session for media for the second IMS service.
  • the second When requesting the establishment of a PDU session for the IMS service of, the information that identifies the network slice corresponding to the 8th S-NSSAI from the 15th identification information for the 2nd IMS service. Select a fifth S-NSSAI, an eleventh S-NSSAI, and a twelfth S-NSSAI, perform a PDU session establishment procedure using the fifth S-NSSAI, and perform a second IMS service.
  • the PDU session establishment procedure using the twelfth S-NSSAI may be executed to establish the PDU session for the media (video) for the second IMS service.
  • each network slice used by each PDU session established for the first IMS service and / or the second IMS service may be at least partially (including all) the same. However, they may all be different. Further, the DNN that identifies the DN to which the PDU session is connected may be at least partially (including all) the same, or may be all different.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 33rd identification information including NSSAI is received and the 15th identification information including the 3rd S-NSSAI and the 4th S-NSSAI is received in this procedure, the 1st IMS
  • the third S-NSSAI and / or the third S-NSSAI contained in the thirteenth identification information and / or the thirty-third identification information is based on the information contained in the thirty-third identification information.
  • the 3rd of the 15th identification information or the 33rd identification information for the 1st IMS service Select S-NSSAI and the 4th S-NSSAI, execute the PDU session establishment procedure using the 3rd S-NSSAI, and establish the PDU session for SIP signaling for the 1st IMS service.
  • a PDU session establishment procedure using the fourth S-NSSAI may be performed to establish a PDU session for the media for the first IMS service.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 15th identification information including the 3rd S-NSSAI, the 9th S-NSSAI and the 10th S-NSSAI is received.
  • it when requesting the establishment of a PDU session for the first IMS service, it is included in the fifteenth identification information and / or the thirty-third identification information based on the information contained in the thirty-third identification information.
  • the 15th identification for the 1st IMS service When it is determined that the 3rd S-NSSAI and 9th S-NSSAI and 10th S-NSSAI are available in the current registration area, the 15th identification for the 1st IMS service. Select the 3rd S-NSSAI, 9th S-NSSAI and 10th S-NSSAI from the information or the 33rd identification information, and execute the PDU session establishment procedure using the 3rd S-NSSAI. Then, the PDU session for SIP signaling for the first IMS service is established, the PDU session establishment procedure using the ninth S-NSSAI is executed, and the media (voice) for the first IMS service is executed. ), And the PDU session establishment procedure using the tenth S-NSSAI may be executed to establish the PDU session for the media (video) for the first IMS service.
  • the UE may already have a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 33rd identification information including NSSAI is received and the 15th identification information including the 7th S-NSSAI is received in this procedure, the PDU session for the 1st IMS service
  • the 7th S-NSSAI contained in the 15th identification information and / or the 33rd identification information is used in the current registration area based on the information contained in the 33rd identification information.
  • the 7th S-NSSAI When it is determined that it is possible, select the 7th S-NSSAI from the 15th identification information or the 33rd identification information for the 1st IMS service, and select the 7th S-NSSAI. You may perform the PDU session establishment procedure you used to establish a PDU session for the first IMS service.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 15th identification information including the 3rd S-NSSAI, the 4th S-NSSAI, and the 7th S-NSSAI.
  • the fifteenth identification information and / or the 33rd identification information is based on the information contained in the 33rd identification information.
  • the 15th identification information or the 33rd identification information for the 1st IMS service is the first.
  • Select the third S-NSSAI and the fourth S-NSSAI which are the information that identifies the network slice corresponding to the 7 S-NSSAI, and execute the PDU session establishment procedure using the third S-NSSAI.
  • Establish a PDU session for SIP signaling for the first IMS service perform a PDU session establishment procedure with the fourth S-NSSAI, and perform a PDU session for media for the first IMS service. May be established.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 3rd S-NSSAI, the 7th S-NSSAI, the 9th S-NSSAI, and the 10th S- When the 15th identification information including NSSAI is received, when requesting the establishment of a PDU session for the 1st IMS service, the 15th identification information and the 15th identification information are based on the information contained in the 33rd identification information.
  • the 15th identification information or the 33rd identification information for the 1st IMS service are selected from the identification information of the third.
  • Execute the PDU session establishment procedure using S-NSSAI establish the PDU session for SIP signaling for the first IMS service, and execute the PDU session establishment procedure using the ninth S-NSSAI.
  • the PDU session for the media (voice) for the first IMS service is established, the PDU session establishment procedure using the tenth S-NSSAI is executed, and the media for the first IMS service ( A PDU session for video) may be established.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the 2nd IMS When requesting the establishment of a PDU session for a service, the fifth S-NSSAI and / or the fifth S-NSSAI contained in the thirteenth identification information and / or the thirty-third identification information is based on the information contained in the thirty-third identification information.
  • the 5th of the 15th or 33rd identification information for the 2nd IMS service Select S-NSSAI and 6th S-NSSAI, perform the PDU session establishment procedure using 5th S-NSSAI, establish the PDU session for SIP signaling for the 2nd IMS service,
  • a PDU session establishment procedure using the sixth S-NSSAI may be performed to establish a PDU session for the media for the second IMS service.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the 15th identification information including the 5th S-NSSAI, the 11th S-NSSAI and the 12th S-NSSAI is received.
  • it is included in the fifteenth identification information and / or the thirty-third identification information based on the information contained in the thirty-third identification information.
  • the 15th identification for the 2nd IMS service When it is determined that the 5th S-NSSAI and the 11th S-NSSAI and the 12th S-NSSAI are available in the current registration area, the 15th identification for the 2nd IMS service. Select the 5th S-NSSAI, the 11th S-NSSAI, and the 12th S-NSSAI from the information or the 33rd identification information, and execute the PDU session establishment procedure using the 5th S-NSSAI. Then, the PDU session for SIP signaling for the second IMS service is established, the PDU session establishment procedure using the eleventh S-NSSAI is executed, and the media (voice) for the second IMS service is executed. ), And the PDU session establishment procedure using the twelfth S-NSSAI may be executed to establish the PDU session for the media (video) for the second IMS service.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the PDU session for the 2nd IMS service When requesting establishment, the 8th S-NSSAI contained in the 15th identification information and / or the 33rd identification information is used in the current registration area based on the information contained in the 33rd identification information.
  • the 8th S-NSSAI When it is determined that it is possible, select the 8th S-NSSAI from the 15th identification information or the 33rd identification information for the 2nd IMS service, and select the 8th S-NSSAI. You may perform the PDU session establishment procedure you used to establish a PDU session for the second IMS service.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the 15th identification information including the 5th S-NSSAI, the 6th S-NSSAI, and the 8th S-NSSAI.
  • the 15th identification information and / or the 33rd identification information is based on the information contained in the 33rd identification information.
  • the 15th identification information or the 33rd identification information for the second IMS service will be the first.
  • Select the 5th S-NSSAI and the 6th S-NSSAI which are the information that identifies the network slice corresponding to the 8 S-NSSAI, and execute the PDU session establishment procedure using the 5th S-NSSAI.
  • Establish a PDU session for SIP signaling for the second IMS service perform a PDU session establishment procedure with the sixth S-NSSAI, and perform a PDU session for media for the second IMS service. May be established.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the 5th S-NSSAI, the 8th S-NSSAI, the 11th S-NSSAI, and the 12th S- When the 15th identification information including NSSAI is received, when requesting the establishment of a PDU session for the 2nd IMS service, the 15th identification information and the 15th identification information are based on the information contained in the 33rd identification information.
  • the 8th S-NSSAI contained in the 33rd identification information is available in the current registration area, then for the 2nd IMS service, the 15th identification information or the 33rd identification information. From the identification information of, select the 5th S-NSSAI, the 11th S-NSSAI, and the 12th S-NSSAI, which are the information for identifying the network slice corresponding to the 8th S-NSSAI, and select the 5th. Execute the PDU session establishment procedure using S-NSSAI, establish the PDU session for SIP signaling for the second IMS service, and execute the PDU session establishment procedure using the eleventh S-NSSAI.
  • the PDU session for the media (voice) for the second IMS service is established, the PDU session establishment procedure using the twelfth S-NSSAI is executed, and the media for the second IMS service ( A PDU session for video) may be established.
  • each network slice used by each PDU session established for the first IMS service and / or the second IMS service may be at least partially (including all) the same. However, they may all be different. Further, the DNN that identifies the DN to which the PDU session is connected may be at least partially (including all) the same, or may be all different.
  • the UE requests the establishment of a PDU session for the IMS service when it receives the fifteenth identification information in this procedure if it has already received the thirty-third 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 not 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 13th S-NSSAI indicated by the 36th identification information and do not send a registration request message containing the 13th S-NSSAI, or send a PDU session establishment request message with the 13th 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 13th 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 thirteenth S-NSSAI indicated by the thirty-six 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 sends a registration request message containing the thirteenth 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 thirteenth S-NSSAI indicated by the thirty-six 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 thirteenth S-NSSAI indicated by the identification information may be sent, or a PDU session establishment request message may be sent together with the thirteenth S-NSSAI indicated by the thirty-six 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 13th S-NSSAI indicated by the 36th identification information for the IMS service and includes the 13th S-NSSAI. It is not necessary to send the registration request message or send the PDU session establishment request message together with the 13th 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 that is different from the current registration area, and the UE is the new registration area. If you have not received a valid 13th S-NSSAI (16th Identification and / or 26th Identification and / or 36th Identification) that is valid for the IMS service, it is new. 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 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 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 13th S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall The thirteenth 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 thirteenth S-NSSAI, or along with the selected default S-NSSAI or thirteenth 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 13th S-NSSAI, or the selected default S-NSSAI or 13th 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 13th 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 13th S-NSSAI for the IMS service in the 1st registration area, and the 13th S-NSSAI is the 1st 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 thirteenth 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.
  • the UE will base the receipt of the 14th and 16th identification information (IMS in the 2nd registration area).
  • IMS 14th and 16th identification information
  • the UE After initiating the PDU session establishment procedure for the IMS service with the second S-NSSAI (which supports the service), use the 13th 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 13th 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 thirteenth 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 resist. 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 when communicating using the IMS service, and the thirteenth S- (supporting IMS) included in the fifteenth identification information. 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 contained in the fifteenth identification information. Select the thirteenth S-NSSAI that supports the IMS service from among them, based on its location and order, and send a registration request message containing the thirteenth S-NSSAI, or the thirteenth S-NSSAI. At the same time, a PDU session establishment request message may be sent.
  • the UE knows the position of the thirteenth S-NSSAI in Allowed NSSAI in advance, the thirteenth identification information and / or the fourteenth identification information and / or the thirth from the core network.
  • the thirteenth 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 13th S-NSSAI (which supports IMS) from the 1 or more S-NSSAI contained in the 15th identification information and send a registration request message containing the 13th S-NSSAI. Alternatively, a PDU session establishment request message may be sent together with the thirteenth S-NSSAI.
  • the UE may use the IMS service for communication.
  • Select default S-NSSAI or 13th S-NSSAI and send a registration request message containing default S-NSSAI or 13th S-NSSAI, or with default S-NSSAI or 13th 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 thirteenth S-NSSAI shown and send a registration request message containing the thirteenth S-NSSAI, or you may send a PDU session establishment request message with the thirteenth 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.
  • 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. Procedures for (eg, including the procedure for establishing a PDU session in Chapter 3.5) may be initiated.
  • 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 completes the registration procedure in Chapter 3.2, the generic UE setting update procedure in Chapter 3.3, the UE policy management procedure in Chapter 3.4, or the procedure for SM (for example, establishing a PDU session in Chapter 3.5).
  • the generic UE setting update procedure may be started based on the completion of (including the 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 16 and 19, but it does not have to be updated.
  • 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 when it receives a 25th identification from the core network, including a 3rd S-NSSAI and a 4th S-NSSAI, it requests the establishment of a PDU session for the 1st IMS service. Selects the 3rd S-NSSAI and the 4th S-NSSAI from the 25th identification information for the 1st IMS service, and uses the 3rd S-NSSAI in Chapter 3.5.
  • PDU session establishment procedure (hereinafter referred to simply as PDU session establishment procedure) is executed to establish a PDU session for SIP signaling for the first IMS service, and PDU using the fourth S-NSSAI. You may perform a session establishment procedure to establish a PDU session for the media for the first IMS service.
  • the UE when the UE receives the 25th identification information including the 3rd S-NSSAI and the 9th S-NSSAI and the 10th S-NSSAI from the core network, it receives the PDU for the 1st IMS service.
  • the 3rd S-NSSAI, 9th S-NSSAI and 10th S-NSSAI When requesting the establishment of a session, select the 3rd S-NSSAI, 9th S-NSSAI and 10th S-NSSAI from the 25th identification information for the 1st IMS service. Execute the PDU session establishment procedure using the third S-NSSAI to establish the PDU session for SIP signaling for the first IMS service, and the PDU session using the ninth S-NSSAI.
  • the 1st IMS service For, select the 7th S-NSSAI from the 25th identification information, execute the PDU session establishment procedure using the 7th S-NSSAI, and for the 1st IMS service.
  • a PDU session may be established.
  • the UE when the UE receives the 25th identification information including the 3rd S-NSSAI and the 4th S-NSSAI and the 7th S-NSSAI from the core network, the UE receives the PDU for the 1st IMS service.
  • the third S-NSSAI which is the information that identifies the network slice corresponding to the seventh S-NSSAI from the 25th identification information for the first IMS service.
  • select the 4th S-NSSAI execute the PDU session establishment procedure using the 3rd S-NSSAI, establish the PDU session for SIP signaling for the 1st IMS service, and the 4th.
  • the PDU session establishment procedure using S-NSSAI may be performed to establish a PDU session for media for the first IMS service.
  • the first When requesting the establishment of a PDU session for the IMS service of, the information that identifies the network slice corresponding to the 7th S-NSSAI from the 25th identification information for the 1st IMS service. Select a third S-NSSAI, a ninth S-NSSAI, and a tenth S-NSSAI, perform a PDU session establishment procedure using the third S-NSSAI, and perform the first IMS service.
  • the PDU session establishment procedure using the tenth S-NSSAI may be executed to establish the PDU session for the media (video) for the first IMS service.
  • the UE when it receives a 25th identification from the core network, including a 5th S-NSSAI and a 6th S-NSSAI, it requests the establishment of a PDU session for the 2nd IMS service. Selects the 5th S-NSSAI and the 6th S-NSSAI from the 25th identification information for the 2nd IMS service, and establishes a PDU session using the 5th S-NSSAI. Perform the procedure to establish a PDU session for SIP signaling for the second IMS service, and perform the PDU session establishment procedure with the sixth S-NSSAI for the second IMS service. You may establish a PDU session for your media.
  • the UE receives the 25th identification information from the core network, including the 5th S-NSSAI and the 11th S-NSSAI and the 12th S-NSSAI
  • the UE receives a PDU for the second IMS service.
  • the 1st IMS service For, select the 8th S-NSSAI from the 25th identification information, execute the PDU session establishment procedure using the 8th S-NSSAI, and for the 2nd IMS service.
  • a PDU session may be established.
  • the UE receives the 25th identification information from the core network, including the 5th S-NSSAI and the 6th S-NSSAI and the 8th S-NSSAI
  • the UE also receives a PDU for the second IMS service.
  • the fifth S-NSSAI which is the information that identifies the network slice corresponding to the eighth S-NSSAI from the 25th identification information.
  • select the 6th S-NSSAI perform the PDU session establishment procedure using the 5th S-NSSAI, establish the PDU session for SIP signaling for the 2nd IMS service, and the 6th.
  • the PDU session establishment procedure using S-NSSAI may be performed to establish a PDU session for media for the second IMS service.
  • the second When requesting the establishment of a PDU session for the IMS service of, the information that identifies the network slice corresponding to the 8th S-NSSAI from the 25th identification information for the 2nd IMS service. Select a fifth S-NSSAI, an eleventh S-NSSAI, and a twelfth S-NSSAI, perform a PDU session establishment procedure using the fifth S-NSSAI, and perform a second IMS service.
  • the PDU session establishment procedure using the twelfth S-NSSAI may be executed to establish the PDU session for the media (video) for the second IMS service.
  • each network slice used by each PDU session established for the first IMS service and / or the second IMS service may be at least partially (including all) the same. However, they may all be different. Further, the DNN that identifies the DN to which the PDU session is connected may be at least partially (including all) the same, or may be all different.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 33rd identification information including NSSAI is received and the 25th identification information including the 3rd S-NSSAI and the 4th S-NSSAI is received in this procedure
  • the 1st IMS When requesting the establishment of a PDU session for a service, the third S-NSSAI and / or the third S-NSSAI contained in the 25th identification information and / or the 33rd identification information is based on the information contained in the 33rd identification information.
  • the 3rd of the 25th or 33rd identification information for the 1st IMS service Select S-NSSAI and the 4th S-NSSAI, execute the PDU session establishment procedure using the 3rd S-NSSAI, and establish the PDU session for SIP signaling for the 1st IMS service.
  • a PDU session establishment procedure using the fourth S-NSSAI may be performed to establish a PDU session for the media for the first IMS service.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 25th identification information including the 3rd S-NSSAI, the 9th S-NSSAI and the 10th S-NSSAI is received.
  • it is included in the 25th identification information and / or the 33rd identification information based on the information contained in the 33rd identification information.
  • the 25th identification for the 1st IMS service When it is determined that the 3rd S-NSSAI and 9th S-NSSAI and 10th S-NSSAI are available in the current registration area, the 25th identification for the 1st IMS service. Select the 3rd S-NSSAI, 9th S-NSSAI and 10th S-NSSAI from the information or the 33rd identification information, and execute the PDU session establishment procedure using the 3rd S-NSSAI. Then, the PDU session for SIP signaling for the first IMS service is established, the PDU session establishment procedure using the ninth S-NSSAI is executed, and the media (voice) for the first IMS service is executed. ), And the PDU session establishment procedure using the tenth S-NSSAI may be executed to establish the PDU session for the media (video) for the first IMS service.
  • the UE may already have a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 33rd identification information including NSSAI is received and the 25th identification information including the 7th S-NSSAI is received in this procedure, the PDU session for the 1st IMS service
  • the 7th S-NSSAI contained in the 25th identification information and / or the 33rd identification information is used in the current registration area based on the information contained in the 33rd identification information.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 25th identification information including the 3rd S-NSSAI, the 4th S-NSSAI, and the 7th S-NSSAI.
  • the 25th identification information and / or the 33rd identification information is based on the information contained in the 33rd identification information.
  • the 25th or 33rd identification information will be available for the 1st IMS service.
  • Select the third S-NSSAI and the fourth S-NSSAI which are the information that identifies the network slice corresponding to the 7 S-NSSAI, and execute the PDU session establishment procedure using the third S-NSSAI.
  • Establish a PDU session for SIP signaling for the first IMS service perform a PDU session establishment procedure with the fourth S-NSSAI, and perform a PDU session for media for the first IMS service. May be established.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 33rd identification information including NSSAI is received, the 3rd S-NSSAI, the 7th S-NSSAI, the 9th S-NSSAI, and the 10th S-
  • the 25th identification information including NSSAI is received, when requesting the establishment of a PDU session for the 1st IMS service, the 25th identification information and the 25th identification information are based on the information contained in the 33rd identification information.
  • the third S-NSSAI, the ninth S-NSSAI, and the tenth S-NSSAI which are the information for identifying the network slice corresponding to the seventh S-NSSAI, are selected from the identification information of the third. Execute the PDU session establishment procedure using S-NSSAI, establish the PDU session for SIP signaling for the first IMS service, and execute the PDU session establishment procedure using the ninth S-NSSAI. Then, the PDU session for the media (voice) for the first IMS service is established, the PDU session establishment procedure using the tenth S-NSSAI is executed, and the media for the first IMS service ( A PDU session for video) may be established.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the 2nd IMS When requesting the establishment of a PDU session for a service, based on the information contained in the 33rd identification information, the 25th identification information and / or the 5th S-NSSAI and / or the 5th S-NSSAI contained in the 33rd identification information.
  • the 5th of the 25th or 33rd identification information for the 2nd IMS service Select S-NSSAI and 6th S-NSSAI, perform the PDU session establishment procedure using 5th S-NSSAI, establish the PDU session for SIP signaling for the 2nd IMS service,
  • a PDU session establishment procedure using the sixth S-NSSAI may be performed to establish a PDU session for the media for the second IMS service.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the 25th identification information including the 5th S-NSSAI, the 11th S-NSSAI and the 12th S-NSSAI is received.
  • it is included in the 25th identification information and / or the 33rd identification information based on the information contained in the 33rd identification information.
  • the 25th identification for the 2nd IMS service When it is determined that the 5th S-NSSAI and the 11th S-NSSAI and the 12th S-NSSAI are available in the current registration area, the 25th identification for the 2nd IMS service. Select the 5th S-NSSAI, the 11th S-NSSAI, and the 12th S-NSSAI from the information or the 33rd identification information, and execute the PDU session establishment procedure using the 5th S-NSSAI. Then, the PDU session for SIP signaling for the second IMS service is established, the PDU session establishment procedure using the eleventh S-NSSAI is executed, and the media (voice) for the second IMS service is executed. ), And the PDU session establishment procedure using the twelfth S-NSSAI may be executed to establish the PDU session for the media (video) for the second IMS service.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the PDU session for the 2nd IMS service When requesting establishment, the 8th S-NSSAI contained in the 25th identification information and / or the 33rd identification information is used in the current registration area based on the information contained in the 33rd identification information.
  • the 8th S-NSSAI When it is determined that it is possible, select the 8th S-NSSAI from the 25th identification information or the 33rd identification information for the 2nd IMS service, and select the 8th S-NSSAI. You may perform the PDU session establishment procedure you used to establish a PDU session for the second IMS service.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the 25th identification information including the 5th S-NSSAI, the 6th S-NSSAI, and the 8th S-NSSAI in this procedure.
  • the 25th identification information and / or the 33rd identification information is based on the information contained in the 33rd identification information.
  • the 25th or 33rd identification information will be available for the 2nd IMS service.
  • Select the 5th S-NSSAI and the 6th S-NSSAI which are the information that identifies the network slice corresponding to the 8 S-NSSAI, and execute the PDU session establishment procedure using the 5th S-NSSAI.
  • Establish a PDU session for SIP signaling for the second IMS service perform a PDU session establishment procedure with the sixth S-NSSAI, and perform a PDU session for media for the second IMS service. May be established.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the 5th S-NSSAI, the 8th S-NSSAI, the 11th S-NSSAI, and the 12th S When the 25th identification information including NSSAI is received, when requesting the establishment of a PDU session for the 2nd IMS service, the 25th identification information and the 25th identification information are based on the information contained in the 33rd identification information.
  • the 8th S-NSSAI contained in the 33rd identification information is available in the current registration area, then for the 2nd IMS service, the 25th identification information or the 33rd From the identification information of, select the 5th S-NSSAI, the 11th S-NSSAI, and the 12th S-NSSAI, which are the information for identifying the network slice corresponding to the 8th S-NSSAI, and select the 5th. Execute the PDU session establishment procedure using S-NSSAI, establish the PDU session for SIP signaling for the second IMS service, and execute the PDU session establishment procedure using the eleventh S-NSSAI.
  • the PDU session for the media (voice) for the second IMS service is established, the PDU session establishment procedure using the twelfth S-NSSAI is executed, and the media for the second IMS service ( A PDU session for video) may be established.
  • each network slice used by each PDU session established for the first IMS service and / or the second IMS service may be at least partially (including all) the same. However, they may all be different. Further, the DNN that identifies the DN to which the PDU session is connected may be at least partially (including all) the same, or may be all different.
  • 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 13th S-NSSAI (16th Identification and / or 26th Identification and / or 36th Identification) that is valid for the IMS service, it is new. 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 UE may choose the default S-NSSAI indicated by the 21st identification 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 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 13th S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall The thirteenth 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 thirteenth S-NSSAI, or along with the selected default S-NSSAI or thirteenth 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 13th S-NSSAI, or the selected default S-NSSAI or 13th 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 13th S-NSSAI for the IMS service in the 1st registration area, and the 13th S-NSSAI is the 1st 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 thirteenth 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 13th S-NSSAI in this procedure, and further in this procedure, the second 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 13th S-NSSAI (which does not support the IMS service in the second registration area).
  • the UE may use the thirteenth 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 resist. 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 when communicating using the IMS service, and the 13th S- (supports IMS) included in the 25th identification information. 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 thirteenth S-NSSAI that supports the IMS service from among them, based on its location and order, and send a registration request message containing the thirteenth S-NSSAI, or the thirteenth S-NSSAI. At the same time, a PDU session establishment request message may be sent.
  • the UE knows the position of the thirteenth S-NSSAI in Allowed NSSAI in advance, the thirteenth identification information and / or the fourteenth identification information and / or the thirth from the core network.
  • the thirteenth 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 13th S-NSSAI (which supports IMS) from the 1 or more S-NSSAI contained in the 25th identification information and send a registration request message containing the 13th S-NSSAI.
  • a PDU session establishment request message may be sent together with the thirteenth S-NSSAI.
  • the UE may use the IMS service for communication.
  • Select default S-NSSAI or 13th S-NSSAI and send a registration request message containing default S-NSSAI or 13th S-NSSAI, or with default S-NSSAI or 13th 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 use 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 configuration update command and / or the configuration update command.
  • the procedure for SM (including, for example, the procedure for establishing a PDU session in Chapter 3.5) may be started.
  • the PCF sends a control message (hereinafter also referred to as a container) containing the UE policy management command in Chapter 3.4 to AMF, and the AMF that receives the control message (container) is the book. You may start the procedure.
  • the AMF may send configuration update commands to the UE, including UE policy management commands (S800).
  • 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 completes the registration procedure in Chapter 3.2, the generic UE setting update procedure in Chapter 3.3, the UE policy management procedure in Chapter 3.4, or the procedure for SM (for example, establishing a PDU session in Chapter 3.5).
  • the UE policy management procedure may be started based on the completion of (including the 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 if it has not yet stored the identification information.
  • 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 UE policy management command. The UE may execute these processes during this procedure or after the procedure is completed.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 33rd identification information including the 3rd S-NSSAI and the 4th S-NSSAI when the 15th identification information and / or the 25th identification information including NSSAI is received.
  • the 1st PDU session establishment procedure using the third S-NSSAI by selecting the third S-NSSAI and the fourth S-NSSAI from the 15 identification information, the 25th identification information, or the 33rd identification information.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S. -In this procedure, the 3rd S-NSSAI and the 9th S-NSSAI and the 10th S-NSSAI when the 15th identification information and / or the 25th identification information including NSSAI is received.
  • S-NSSAI is selected, the PDU session establishment procedure using the third S-NSSAI is executed, the PDU session for SIP signaling for the first IMS service is established, and the ninth S-NSSAI Execute the PDU session establishment procedure using S-NSSAI to establish the PDU session for media (voice) for the first IMS service, and execute the PDU session establishment procedure using the tenth S-NSSAI.
  • a PDU session for media (video) for the first IMS service may be established.
  • the UE may already have a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 1st When the 15th identification information including NSSAI and / or the 25th identification information is received and the 33rd identification information including the 7th S-NSSAI is received in this procedure, the 1st When requesting the establishment of a PDU session for the IMS service of, based on the information contained in the 33rd identification information, the 15th identification information and / or the 25th identification information and / or the 33rd identification information When it is determined that the 7th S-NSSAI contained in the current registration area is available, the 15th identification information or the 25th identification information or the 33rd identification information is used for the 1st IMS service.
  • the 7th S-NSSAI may be selected from the identification information and the PDU session establishment procedure using the 7th S-NSSAI may be executed to establish the PDU session for the 1st IMS service.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S.
  • the 3rd S-NSSAI, the 4th S-NSSAI, and the 7th S when the 15th identification information and / or the 25th identification information including NSSAI is received.
  • the 15th identification information is based on the information contained in the 33rd identification information.
  • the 7th S-NSSAI contained in the 25th identification information and / or the 33rd identification information is available in the current registration area, for the 1st IMS service.
  • 15th identification information, 25th identification information, or 33rd identification information, the third S-NSSAI and the fourth S which are information for identifying the network slice corresponding to the seventh S-NSSAI.
  • the UE already has a third S-NSSAI and / or a fourth S-NSSAI and / or a seventh S-NSSAI and / or a ninth S-NSSAI and / or a tenth S. -In this procedure, the 3rd S-NSSAI, the 7th S-NSSAI, and the 9th S when the 15th identification information and / or the 25th identification information including NSSAI is received.
  • the information contained in the 33rd identification information Based on this, when it is determined that the 7th S-NSSAI contained in the 15th identification information and / or the 25th identification information and / or the 33rd identification information can be used in the current registration area, A third piece of information that identifies the network slice corresponding to the seventh S-NSSAI from the fifteenth identification information, the 25th identification information, or the 33rd identification information for the first IMS service.
  • Select S-NSSAI, 9th S-NSSAI and 10th S-NSSAI execute the PDU session establishment procedure using the 3rd S-NSSAI, and for SIP signaling for the 1st IMS service.
  • Establish a PDU session for the 9th S-NSSAI perform a PDU session establishment procedure using the 9th S-NSSAI, establish a PDU session for media (voice) for the 1st IMS service, and 10th S-
  • a PDU session establishment procedure using NSSAI may be performed to establish a PDU session for media (video) for the first IMS service.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S. -In this procedure, the 33rd identification information including the 5th S-NSSAI and the 6th S-NSSAI when the 15th identification information and / or the 25th identification information including NSSAI is received.
  • the 1st PDU session establishment procedure using the 5th S-NSSAI by selecting the 5th S-NSSAI and the 6th S-NSSAI from the 15 identification information, the 25th identification information, or the 33rd identification information.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the 5th S-NSSAI and the 11th S-NSSAI and the 12th S-NSSAI when the 15th identification information and / or the 25th identification information including NSSAI is received.
  • the 5th S-NSSAI and the 11th S-NSSAI and the 12th S-NSSAI contained in the 25th identification information and / or the 33rd identification information can be used in the current registration area. Then, for the second IMS service, the fifth S-NSSAI, the eleventh S-NSSAI, and the twelfth from the fifteenth identification information, the 25th identification information, or the 33rd identification information. Select S-NSSAI, perform the PDU session establishment procedure using the 5th S-NSSAI, establish the PDU session for SIP signaling for the 2nd IMS service, and 11th S-NSSAI.
  • a PDU session for media (video) for the second IMS service may be established.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the second When requesting the establishment of a PDU session for the IMS service of, based on the information contained in the 33rd identification information, the 15th identification information and / or the 25th identification information and / or the 33rd identification information
  • the 15th identification information or the 25th identification information or the 33rd identification information is used for the second IMS service.
  • the eighth S-NSSAI may be selected from the identification information and the PDU session establishment procedure using the eighth S-NSSAI may be executed to establish the PDU session for the second IMS service.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S.
  • the 5th S-NSSAI, the 6th S-NSSAI, and the 8th S when the 15th identification information and / or the 25th identification information including NSSAI is received.
  • the 15th identification information is based on the information contained in the 33rd identification information.
  • the UE has already sent the 5th S-NSSAI and / or the 6th S-NSSAI and / or the 8th S-NSSAI and / or the 11th S-NSSAI and / or the 12th S. -In this procedure, the 5th S-NSSAI, the 8th S-NSSAI, and the 11th S when the 15th identification information and / or the 25th identification information including NSSAI is received.
  • the information contained in the 33rd identification information Based on this, when it is determined that the 8th S-NSSAI contained in the 15th identification information and / or the 25th identification information and / or the 33rd identification information can be used in the current registration area, For the second IMS service, the fifth identification information that identifies the network slice corresponding to the eighth S-NSSAI from the fifteenth identification information, the 25th identification information, or the 33rd identification information.
  • Select S-NSSAI and 11th S-NSSAI and 12th S-NSSAI execute the PDU session establishment procedure using 5th S-NSSAI, and use it for SIP signaling for the 2nd IMS service.
  • Establish a PDU session for the 11th S-NSSAI perform a PDU session establishment procedure using the 11th S-NSSAI, establish a PDU session for media (voice) for the 2nd IMS service, and perform a 12th S-
  • a PDU session establishment procedure using NSSAI may be performed to establish a PDU session for media (video) for the second IMS service.
  • each network slice used by each PDU session established for the first IMS service and / or the second IMS service may be at least partially (including all) the same. However, they may all be different. Further, the DNN that identifies the DN to which the PDU session is connected may be at least partially (including all) the same, or may be all different.
  • the UE requests the establishment of a PDU session for the IMS service when it receives the 33rd identification information in this procedure if it has already received the 15th 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 not 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 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 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 13th S-NSSAI indicated by the 36th identification information and do not send a registration request message containing the 13th S-NSSAI, or send a PDU session establishment request message with the 13th 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 13th 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 thirteenth S-NSSAI indicated by the thirty-six identification information.
  • 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 thirteenth 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 thirteenth S-NSSAI indicated by the thirty-six 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 thirteenth S-NSSAI indicated by the identification information may be sent, or a PDU session establishment request message may be sent together with the thirteenth S-NSSAI indicated by the thirty-six identification information. In this case, the UE does not have to send a UE policy management command rejection message containing the 41st identification information.
  • 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 13th S-NSSAI indicated by the 36th identification information for the IMS service and includes the 13th S-NSSAI. It is not necessary to send the registration request message or send the PDU session establishment request message together with the 13th 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 is 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 13th S-NSSAI (16th Identification and / or 26th Identification and / or 36th Identification) that is valid for the IMS service, it is new. 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 different from the current registration area, and the UE is valid in the new registration area.
  • 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 13th S-NSSAI (16th identification information and / or 26th identification information and / or 36th identification information) (which supports the IMS service), the UE shall The thirteenth 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 thirteenth S-NSSAI, or a PDU session establishment request message with the selected default S-NSSAI or the thirteenth S-NSSAI. good.
  • -NSSAI may be associated and stored.
  • the UE may store the 33rd identification information.
  • the S-NSSAI and S-NSSAI included 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 13th S-NSSAI for the IMS service in the 1st registration area, and the 13th S-NSSAI is the 1st 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 thirteenth 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 13th 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 identification information.
  • the UE may use the thirteenth 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 13th S-NSSAI and send a registration request message containing default S-NSSAI or 13th S-NSSAI, or with default S-NSSAI or 13th 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 can 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.
  • Policy management procedures, or procedures for SM may be initiated.
  • the PCF may send a control message (container) containing the UE policy management command
  • the AMF that receives the control message (container) may start the generic UE setting update procedure in Chapter 3.3. That is, the AMF that receives the policy management command from the PCF may send the setting update command including the UE policy management command to the UE.
  • the UE policy management procedure in this chapter may be referred to as the UE setting update procedure. That is, the UE policy management procedure in this chapter may be executed as a UE setting update procedure.
  • the PDU session establishment procedure that the UE initiates to establish a PDU session will be described with reference to FIG.
  • the PDU session establishment procedure is also referred to as this procedure.
  • the UE completes the registration procedure in Chapter 3.2, the generic UE setting update procedure in Chapter 3.3, the UE policy management procedure in Chapter 3.4, or the procedure for SM (including, for example, the procedure for establishing a PDU session in this chapter). ) May be completed, and this procedure may be started.
  • this procedure may be executed as a procedure for establishing a PDU session for the IMS service, and may be executed multiple times depending on the number of IMS services requested or required by the user and / or the application. May be good. More specifically, this procedure may establish a PDU session for the IMS service used by the UE. In addition, multiple PDU sessions for the IMS service established by this procedure are associated with each IMS signaling (SIP signaling for the IMS service) and / or send / receive media for the IMS service described later. May be used for each.
  • SIP signaling for the IMS service
  • the UE establishes a PDU session by sending a NAS message containing an N1SM container containing a PDU session establishment request message to AMF via the access network_B (3GPP access or non-3GPP access) (S1000).
  • the access network may include a base station device. That is, the UE sends a NAS message to the AMF via the base station device.
  • the NAS message is, for example, a message transmitted via the N1 interface and may be an uplink NAS transport (UL NAS TRANSPORT) message.
  • the UE also requests the PDU session establishment request message and / or the N1SM container and / or the NAS message by including at least one of the identification information of 51st to 59th. This can be notified to the network side.
  • the UE determines which of the 51st to 59th identification information is transmitted to the network, the UE capability information and / or the UE policy, and / or the UE status, and / or the user. It may be decided based on the registration information of the above and / or the context held by the UE.
  • the new PDU session ID may be included in the PDU session establishment request message and / or the N1SM container and / or the NAS message.
  • the UE has already established a PDU session for a (first or second) IMS service and requests the establishment of the remaining PDU sessions associated with that IMS service, it has already established it.
  • the 51st identification information indicating the PDU session ID different from the PDU session ID being used may be included in the PDU session establishment request message and / or the N1SM container and / or the NAS message.
  • the 52nd identification information And the content of the 53rd identification information is set by the UE, and the 52nd identification information and the 53rd identification information are included in the PDU session establishment request message and / or the N1SM container and / or the NAS message. good.
  • the UE may request the establishment of the remaining PDU sessions associated with that IMS service.
  • the information indicated by the 62nd identification information and the 63rd identification information set for the already established PDU session is set to the 52nd identification information and the 53rd identification information, respectively.
  • the 52 identification information and the 53rd identification information may be included in the PDU session establishment request message and / or the N1SM container and / or the NAS message.
  • the UE may include the 54th identification information in the PDU session establishment request message and / or the N1SM container and / or the NAS message. ..
  • the UE also requests the establishment of a PDU session for SIP signaling for some (first or second) IMS service, or for media for some (first or second) IMS service.
  • a PDU session or when requesting the establishment of a PDU session for media (voice) for some (first or second) IMS service, or one (first or second) IMS
  • the 55th identification information is used.
  • PDU session establishment request message and / or N1SM container, and / or NAS message.
  • the UE also includes the 56th and 57th identification information included when requesting the establishment of a PDU session for SIP signaling for the first IMS service, and the media for the first IMS service. Included when requesting the establishment of a PDU session for media (voice) for the first IMS service, with the 56th and 57th identifications included when requesting the establishment of a PDU session for 56th and 57th identification information and the 56th and 57th identification information included when requesting the establishment of a PDU session for media (video) for the first IMS service. And the 56th and 57th identifications included when requesting the establishment of a PDU session for the first IMS service, and the establishment of a PDU session for SIP signaling for the second IMS service.
  • 56th and 57th identifications included when requesting and 56th and 57th identifications included when requesting the establishment of a PDU session for media for the second IMS service.
  • the 56th identification information and the 57th identification information may be the same as or different from each other.
  • the 58th identification information Does not have to be included in the PDU session establishment request message and / or the N1SM container and / or the NAS message.
  • the UE has already established some PDU sessions for a (first or second) IMS service, the remaining PDUs associated with the (first or second) IMS service.
  • the 58th identification information indicating the already established PDU session ID may be included in the PDU session establishment request message and / or the N1SM container and / or the NAS message.
  • the UE uses these identification information as a control message different from these, for example, a control message of a layer lower than the NAS layer (for example, RRC layer, MAC layer, RLC layer, PDCP layer, SDAP layer, etc.). It may be included in a control message of a layer higher than the NAS layer (for example, a transport layer, a session layer, a presentation layer, an application layer, etc.) and transmitted.
  • a control message of a layer lower than the NAS layer for example, RRC layer, MAC layer, RLC layer, PDCP layer, SDAP layer, etc.
  • a control message of a layer higher than the NAS layer for example, a transport layer, a session layer, a presentation layer, an application layer, etc.
  • the AMF when the AMF receives the NAS message, it can recognize what the UE is requesting and / or the content of the information (message, container, information) contained in the NAS message.
  • AMF selects SMF as the transfer destination of at least a part of the information (messages, containers, information) contained in the NAS message received from the UE (S1002).
  • AMF may include information (messages, containers, information) contained in NAS messages, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or.
  • the transfer destination SMF may be selected based on the network status and / or the user's registration information and / or the context held by the AMF.
  • the AMF sends at least a part of the information (message, container, information) contained in the NAS message received from the UE to the selected SMF, for example, via the N11 interface (S1004).
  • the SMF receives the information etc. (message, container, information) transmitted from the AMF, what the UE requests and / or the content of the information etc. (message, container, information) received from the AMF. Can be recognized.
  • the SMF may determine the second condition. Further, the second condition determination may be for determining whether or not the network accepts the UE request. If the SMF determines that the second condition determination is true, the procedure (A) in FIG. 9 may be started, and if the second condition determination is determined to be false, the procedure (B) in FIG. 9 may be started. You may start.
  • the second condition determination is information received from AMF (messages, containers, information) and / or subscriber information (subscription information) and / or network capability information, and / or UE policy, and /. Alternatively, it may be executed 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 SMF.
  • the second condition determination may be determined to be true, and if the network does not allow the UE request, the second condition determination may be determined to be false. Also, if the network to which the UE is connected and / or the devices in the network support the functions required by the UE, the second condition determination may be determined to be true, and the functions required by the UE are supported. If not, the second condition determination may be determined to be false. Further, if the transmitted / received identification information is permitted, the second condition determination may be determined to be true, and if the transmitted / received identification information is not permitted, the second condition determination may be determined to be false.
  • the condition for determining the truth of the second condition determination is not limited to the above-mentioned condition.
  • the SMF may select the UPF for the PDU session to be established and send an N4 session establishment request message to the selected UPF, for example, via the N4 interface (S1008).
  • the N4 session establishment request message may contain at least a portion of the URSP received from the PCF.
  • the SMF is the information received from the AMF (messages, containers, information) and / or the information contained in the URSP received from the PCF, and / or the subscriber information, and / or the network capability information, and /.
  • one or more UPFs may be selected based on the UE policy and / or the operator policy and / or the network status and / or the user's registration information and / or the context held by the SMF.
  • the SMF may send an N4 session establishment request message to each UPF.
  • the UPF when the UPF receives the N4 session establishment request message (S1008), it can recognize the content of the information received from the SMF.
  • the UPF may also send an N4 session establishment response message to the SMF, eg, via the N4 interface, based on the receipt of the N4 session establishment request message (S1010).
  • the SMF when the SMF receives the N4 session establishment response message as the response message to the N4 session establishment request message, the SMF can recognize the content of the information received from the UPF.
  • the SMF then receives the PDU session establishment request message and / or the UPF selection and / or the N1 SM container and / or the N1 SM container and / or based on the reception of the N4 session establishment response message, for example, via the N11 interface.
  • the N1SM container may contain a PDU session establishment acceptance message.
  • the AMF that receives the N1SM container and / or the N2SM information and / or the PDU session ID sends a NAS message to the UE via the base station device included in the access network (S1014) (S1016).
  • the NAS message is transmitted, for example, via the N1 interface.
  • the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.
  • the AMF sends an N2 PDU session request message to the base station device included in the access network (S1014)
  • the base station device that receives the N2 PDU session request message sends an N2 PDU session request message to the UE.
  • Send a NAS message (S1016).
  • the N2 PDU session request message may include a NAS message and / or N2 SM information.
  • the NAS message may also include a PDU session ID and / or an N1SM container.
  • the PDU session establishment acceptance message may be a response message to the PDU session establishment request. Also, the PDU session establishment acceptance message may indicate that the PDU session establishment has been accepted.
  • the SMF and / or AMF are the PDU session establishment acceptance message and / or the N1 SM container and / or the PDU session ID and / or the NAS message, and / or the N2 SM information and / or the N2 PDU session request.
  • the SMF and / or AMF are the PDU session establishment acceptance message and / or the N1 SM container and / or the PDU session ID and / or the NAS message, and / or the N2 SM information and / or the N2 PDU session request.
  • the SMF and / or AMF may send the PDU session establishment acceptance message and / or the N1 SM container and / or NAS message, and / or the N2 SM information, and / or the N2 PDU session request message to the 61st to 68th. It may be transmitted including at least one of the identification information of.
  • the identification information of the 61st to 63rd may be the same as or different from the identification information of the 51st to 53rd of this procedure.
  • the SMF may indicate that the network supports each function by sending these identification information and / or the PDU session establishment acceptance message, and indicate that the UE request has been accepted. 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 request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.
  • SMF and / or AMF can notify the UE of the content of these identification information by transmitting at least one of these identification information.
  • identification information should SMF and / or AMF include in the PDU session establishment acceptance message and / or the N1 SM container and / or NAS message, and / or the N2 SM information and / or the N2 PDU session request message?
  • Each received identification information and / or subscriber information and / or network capability information and / or UE policy and / or operator policy and / or network status and / or user registration information, And / or the decision may be made based on the context held by SMF and / or AMF.
  • the SMF and / or AMF may use the 61st identification information, which has the same content as the 51st identification information, in the PDU session establishment acceptance message and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information. , And / or may be included in the N2PDU session request message.
  • the SMF and / or AMF will use the 62nd and 63rd identification information selected by the SMF for the PDU session establishment acceptance message and / or the N1 SM container, and / or the NAS message, and / or N2. It may be included in SM information and / or N2 PDU session request messages.
  • the content of the 62nd identification information may be the same as or different from the content of the 52nd identification information.
  • the content of the 63rd identification information may be the same as or different from the content of the 53rd identification information.
  • the SMF and / or AMF will only receive the 54th identification information from the UE for the 64th identification information in the PDU session establishment acceptance message and / or the N1 SM container, and / or the NAS message, and / or. It may be included in N2SM information and / or N2PDU session request messages.
  • the SMF and / or AMF may use the 64th identification information as the PDU session establishment acceptance message and / or the N1SM container and / or NAS message regardless of whether or not the 54th identification information has been received from the UE.
  • SMF and / or AMF allow the establishment of a PDU session for SIP signaling for a (first or second) IMS service, or a PDU session for media for a first IMS service.
  • a PDU session for media voice
  • a PDU session for media video
  • the 65th identification information is used for the PDU session establishment acceptance message and / or the N1SM container, and / or the NAS message. And / or may be included in N2SM information and / or N2PDU session request messages.
  • the UE also includes the 66th and 67th identification information included when allowing the establishment of a PDU session for SIP signaling for the 1st IMS service, and the media for the 1st IMS service. Included when allowing the establishment of PDU sessions for media (voice) for the first IMS service, with the 66th and 67th identifications included when allowing the establishment of PDU sessions for 66th and 67th identification information and the 66th and 67th identification information included when permitting the establishment of a PDU session for media (video) for the first IMS service.
  • the 66th and 67th identifications included when allowing the establishment of a PDU session for the first IMS service, and the establishment of a PDU session for SIP signaling for the second IMS service.
  • 66th identification information and 67th identification information included when permitting, and 66th identification information and 67th identification information included when permitting the establishment of a PDU session for media for the second IMS service.
  • the 66th and 67th identifications that are included when requesting the establishment of a PDU session for media (voice) for the second IMS service, and for the second IMS service. Included when requesting the establishment of a PDU session for the media (video) of the 66th and 67th identification information and when requesting the establishment of a PDU session for the second IMS service.
  • the 66th identification information and the 67th identification information may be the same as or different from each other.
  • the content of the 66th identification information may be the same as or different from the content of the 56th identification information. Further, the content of the 67th identification information may be the same as or different from the content of the 57th identification information.
  • the UE when the UE receives the NAS message via, for example, the N1 interface (S1016), the UE's request by the PDU session establishment request message is accepted, and / or the information contained in the NAS message, etc. (message, Can recognize the contents of containers (containers, information).
  • the UE may recognize the PDU session type and SSC mode set for the PDU session identified by the 31st identification information based on the received identification information of the 61st, 62nd, and 63rd.
  • the UE may also recognize the functions supported by the network based on the received 64th identification information.
  • the UE may also recognize that the network has granted the UE's request based on the 65th identification information received.
  • Each device may establish a PDU session based on the transmission / reception of the PDU session establishment acceptance message, and may complete this procedure. That is, each device may transition to a state in which it can communicate with the DN using the established PDU session.
  • the UE When the UE establishes a part of the PDU session for a certain (first or second) IMS service by completing this procedure, the UE establishes the remaining PDU session for that IMS service. You may carry out this procedure.
  • the SMF sends the N1 SM container and / or the PDU session ID to the AMF based on the reception of the PDU session establishment request message, for example, via the N11 interface (S1018).
  • the N1SM container may contain a PDU session establishment refusal message.
  • the AMF that received the N1SM container and / or the PDU session ID sends a NAS message to the UE via the first base station device included in the access network (S1020) (S1022).
  • the NAS message is transmitted, for example, via the N1 interface.
  • the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.
  • the NAS message may also include a PDU session ID and / or an N1SM container.
  • the PDU session establishment refusal message may be a response message to the PDU session establishment request. Also, the PDU session establishment refusal message may indicate that the establishment of the PDU session has been rejected.
  • the SMF and / or AMF sends a PDU session establishment refusal message and / or an N1SM container and / or a PDU session ID and / or a NAS message to request the UE by the PDU session establishment request message. May indicate that was rejected.
  • the SMF may indicate that the network does not support each function by sending a PDU session establishment refusal message, or may indicate that the UE request has been rejected, or the UE may indicate that the request has been rejected. It may indicate that the request 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 request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.
  • SMF and / or AMF can notify the UE of the content of these identification information by transmitting at least one of these identification information.
  • the UE receives the NAS message via, for example, the N1 interface (S1022)
  • the UE's request by the PDU session establishment request message is rejected, and / or the information contained in the NAS message, etc. (message,).
  • Each device may complete this procedure based on the transmission and reception of the PDU session establishment refusal message. At this time, since each device cannot establish a PDU session by this procedure, it cannot communicate with the DN if there is no already established PDU session, and if there is already an established PDU session, it cannot communicate with the DN. Communication with the DN using a PDU session is possible.
  • each process that the UE shown above executes based on the reception of each identification information may be executed during this procedure or after the completion of this procedure, or may be executed based on the completion of this procedure after the completion of this procedure. good.
  • each device may store the information transmitted / received in this procedure in association with each other.
  • the program that operates in the apparatus according to one aspect of the present invention may be a program that controls a Central Processing Unit (CPU) or the like to operate a computer so as to realize the functions of the embodiments according to the present invention.
  • 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.
  • volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, Hard Disk Drive (HDD), or other storage device system.
  • 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.
  • the invention of the present application is not limited to the above-described embodiment.
  • one 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

La présente invention concerne un procédé permettant de sélectionner efficacement le S-NSSAI nécessaire pour connecter un ou plusieurs services IMS à un ou plusieurs réseaux IMS via une ou plusieurs tranches de réseau en 5GS. UE qui : reçoit un message d'acceptation d'enregistrement qui inclut un NSSAI autorisé qui inclut un premier S-NSSAI qui est pour la signalisation SIP pour un premier service IMS et un second S-NSSAI qui est pour les médias pour le premier service IMS; reçoit une commande de gestion de politique d'UE qui inclut un URSP qui inclut le premier S-NSSAI, le second S-NSSAI, et des informations qui indiquent les zones d'enregistrement dans lesquelles le premier S-NSSAI et/ou le second S-NSSAI peuvent être utilisés; et, lors de la demande d'établissement d'une session PDU pour le premier service IMS, sélectionne la première S-NSSAI et la seconde S-NSSAI pour le premier service IMS lorsqu'il a été déterminé sur la base de l'URSP que la première S-NSSAI et la seconde S-NSSAI peuvent être utilisées dans la zone d'enregistrement actuelle.
PCT/JP2021/040340 2020-11-05 2021-11-02 Équipement utilisateur (ue) WO2022097623A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2022560776A JPWO2022097623A1 (fr) 2020-11-05 2021-11-02

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020-184768 2020-11-05
JP2020184768 2020-11-05

Publications (1)

Publication Number Publication Date
WO2022097623A1 true WO2022097623A1 (fr) 2022-05-12

Family

ID=81457190

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/040340 WO2022097623A1 (fr) 2020-11-05 2021-11-02 Équipement utilisateur (ue)

Country Status (2)

Country Link
JP (1) JPWO2022097623A1 (fr)
WO (1) WO2022097623A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016527822A (ja) * 2013-07-29 2016-09-08 エルジー エレクトロニクス インコーポレイティド Ｉｍｓサービスのためのページング方法及び装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016527822A (ja) * 2013-07-29 2016-09-08 エルジー エレクトロニクス インコーポレイティド Ｉｍｓサービスのためのページング方法及び装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SHARP: "Proposal of solution for Key issue X found in C1-206198", 3GPP DRAFT; C1-206530, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Electronic meeting; 20201015 - 20201023, 22 October 2020 (2020-10-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051940995 *

Also Published As

Publication number Publication date
JPWO2022097623A1 (fr) 2022-05-12

Similar Documents

Publication Publication Date Title
WO2021132505A1 (fr) Équipement utilisateur (ue)
WO2021205955A1 (fr) Équipement utilisateur (ue) et procédé de communication pour un ue
WO2021215228A1 (fr) Équipement utilisateur (ue) et fonction de gestion d'accès et de mobilité (amf)
WO2021261522A1 (fr) Équipement utilisateur (ue) et procédé de commande de communication
WO2021241114A1 (fr) Équipement utilisateur (ue), dispositif de réseau central, fonction de gestion d'accès et de mobilité (amf) et fonction de gestion de sessions (smf)
WO2021060383A1 (fr) Dispositif d'utilisateur et dispositif de réseau central
WO2021193937A1 (fr) Ue (équipement utilisateur)
WO2022004699A1 (fr) Équipement d'utilisateur (ue) et procédé de commande de communication pour ue
WO2021132288A1 (fr) Équipement Utilisateur (UE)
WO2022138730A1 (fr) Équipement utilisateur (eu)
WO2021132502A1 (fr) Ue, dispositif de commande et procédé de commande de communication
WO2021132506A1 (fr) Équipement utilisateur (ue)
WO2022097623A1 (fr) Équipement utilisateur (ue)
WO2022059627A1 (fr) Équipement utilisateur (ue)
WO2021132287A1 (fr) Équipement Utilisateur (UE)
WO2022030474A1 (fr) Ue (équipement d'utilisateur)
WO2023188726A1 (fr) Équipement utilisateur (ue)
WO2023188727A1 (fr) Équipement utilisateur (ue)
WO2023210480A1 (fr) Réseau central et équipement utilisateur (ue)
WO2021029380A1 (fr) Équipement utilisateur
WO2021215227A1 (fr) Ue (équipement utilisateur)
WO2023112771A1 (fr) Équipement utilisateur (ue)
WO2023157484A1 (fr) Équipement utilisateur (ue)
WO2023157486A1 (fr) Équipement utilisateur (ue)
WO2022138731A1 (fr) Équipement utilisateur (eu)

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: 21889176

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022560776

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: 21889176

Country of ref document: EP

Kind code of ref document: A1