WO2020204092A1 - User device, control device, and communication control method - Google Patents
User device, control device, and communication control method Download PDFInfo
- Publication number
- WO2020204092A1 WO2020204092A1 PCT/JP2020/015075 JP2020015075W WO2020204092A1 WO 2020204092 A1 WO2020204092 A1 WO 2020204092A1 JP 2020015075 W JP2020015075 W JP 2020015075W WO 2020204092 A1 WO2020204092 A1 WO 2020204092A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- npn
- information
- network
- message
- procedure
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/02—Access restriction performed under specific conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
Definitions
- This application relates to a user device, a control device, and a communication control method.
- This application claims the benefit of priority to Japanese Patent Application No. 2019-70073, which is a Japanese patent application filed on April 1, 2019, and by referring to it, the content of the application is claimed. All are included in this application.
- 3GPP 3rd Generation Partnership Project
- SAE System Architecture Evolution
- LTE Long Term Evolution
- 5G Next-generation mobile communication systems
- 5GS 5th Generation
- 5GS is a system that realizes 5G mobile communication systems.
- 5G System is being specified (see Non-Patent Document 1 and Non-Patent Document 2).
- 5GS extracts technical issues for connecting a wide variety of terminals to cellular networks and specifies solutions.
- 5GS 5G System
- 5GCN 5G Core Network
- 5GS is considering Vertical LAN as a new function.
- NPN Non-public network
- NPN Non-public network
- NPN Non-public network
- NPN Non-public network
- NPN is a private network that is not intended for general use but for private use by companies.
- NPN is a private network used by specific users for specific purposes.
- NPN Stand-alone Non-Public Network
- 3GPP it is specified that Public network integrated NPN supports NPN by using the function of network slice.
- a UE configured for high priority access in selected PLMN
- PLMN Public Land Mobile Network
- the UE identification method set as the UE to connect with high priority in PLMN is identified based on one or more access identification information stored in each device of the UE and the device in the core network.
- the present invention has been made in view of the above circumstances, and an object of the present invention is to provide a method for realizing a function for NPN in 5GS.
- the user device is a user device that can be connected to an NPN (Non Public Network), and receives the value of the backoff timer from the storage unit that stores the first information and the NPN. Based on the first information, the back-off timer is provided with a transmitter / receiver for transmitting a request message while the backoff timer is being executed, and the first information has a high priority within the NPN by the user device. It is information indicating that the connection is possible, and the NPN is a network slice.
- NPN Non Public Network
- the control device is a control device in PLMN (Public land mobile network) including a network slice created as an NPN (Non Public Network), and is a memory for storing the first identification information.
- PLMN Public land mobile network
- NPN Non Public Network
- the control device of the embodiment of the present invention is a control device in the PLMN including a network slice created as a Non Public Network (NPN), and is backed to a user device that can be connected with a high priority in the NPN. It is characterized by having a transmission / reception unit for transmitting a PDU (Protocol Data Unit or Packet Data Unit) session deletion command message or a PDU session establishment rejection message or a PDU session change rejection message that does not include an off-timer.
- PDU Protocol Data Unit or Packet Data Unit
- NPN support is possible, and UE registration, session establishment, session management, and UE support for UEs that connect with high priority within the NPN. Settings can be changed / updated.
- 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 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) in 5GS. It is a figure explaining the registration procedure. It is a figure explaining the service request procedure. It is a figure explaining the PDU session establishment procedure. It is a figure explaining the change / update procedure of a UE setting.
- gNB access network apparatus
- AMF / SMF / UPF core network apparatus
- PDU session establishment procedure It is a figure explaining the change / update procedure of a UE setting.
- 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, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, etc. Interfaces that connect devices and functions to each other are described.
- these devices / functions are referred to as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5GAN, AMF, UPF, SMF, PCF, UDM, etc. May be omitted.
- the EPS Evolved Packet System
- 4G system is configured to include the access network_A and the core network_A, but may further include the UE and / or 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 3GPP AN) and / or non-3GPP access (non-3GPP access network, also called non-3GPP AN). is there.
- 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 provided with UICC (Universal Integrated Circuit Card) or 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.
- 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 (5G AN).
- 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 symbols such as eNB.
- the gNB is a node that provides the NR (New Radio) user plane and 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 function different from that of the base station device (eNB) used in EPS, which is a 4G system.
- eNB base station device
- EPS which is a 4G system.
- each gNB is connected to each other by, for example, an Xn interface.
- 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 located in the access network_B may be collectively referred to as NG-RAN nodes.
- the devices included in the access network_A and / or the access network_B and / or the access network_A, and / or the devices included in the access network_B are the access network or the access network device. It 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 referred to as a core network or a core network device. There is.
- 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), etc. may be a core network for virtual mobile communication operators and virtual mobile communication service providers.
- MNO IP mobile communication network operated by Network Operator
- MNO Mobile Virtual Network Operator
- MVNE Mobile Virtual Network Enabler
- the PDN may be a DN (Data Network) that provides a communication service to the UE.
- the DN may be configured as a packet data service network or may be configured for each service.
- the PDN may include a connected communication terminal. Therefore, connecting to the PDN may be connecting to a communication terminal or server device arranged in the PDN. Further, sending and receiving user data to and from the PDN may be sending and receiving user data to and from a communication terminal or server device arranged in the PDN.
- PDN may be expressed as DN
- DN may be expressed as PDN.
- access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included in these are referred to as a network or network device. It 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 It means that at least a part and / or one or more devices included therein send and 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 and 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 can 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.
- 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 (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) in each device / function appearing below is, for example, a semiconductor memory, SSD ( It is composed 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 PDN and / or DN), various information sent and received 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.
- each storage unit may store such information for each UE.
- each storage unit can store control messages and user data sent and received between 5GS and / or devices / functions included in EPS when interwork is performed between 5GS and EPS. it 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 transmitter / receiver_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 can send and receive user data and / or control information to and from the access network device and / or the core network device and / or PDN and / or DN using the transmitter / receiver_A320. it 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 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 the 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 between the AMF and / or the UPF by using the network connection unit_B520.
- the transmitter / receiver_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.
- the gNB in the 5GAN can communicate with the AMF via the N2 interface by using the network connection _B520, and the UPF via the N3 interface. Can communicate with.
- 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 part_B720 is a functional part for AMF to connect to the base station device (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 communicate with the base station equipment (gNB) in 5GAN and / or SMF and / or PCF, and / or UDM, and / or 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.
- AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection part_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 the N2 interface, a function to exchange NAS messages with UE using the 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, so 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 (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 PDU session context.
- 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 position 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 the 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) and 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 (NAS signaling connection) established with AMF via the N1 interface.
- NAS signaling connection NAS signaling connection
- 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-connection 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. ) May be there.
- 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 disconnected state in 3GPP access may be expressed as 5GMM non-connection mode (5GMM-IDLE mode over 3GPP access) in 3GPP access
- the connection state in 3GPP access is 5GMM connection mode (5GMM-) in 3GPP access. It may be expressed as CONNECTED mode over 3GPP access).
- non-connection state in non-3GPP access may be expressed as 5GMM non-connection mode (5GMM-IDLE mode over non-3GPP access) in non-3GPP access, and the connection state in non-3GPP access is non. It may be expressed as 5GMM connection mode (5GMM-CONNECTED mode over non-3GPP access) in -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 part_B720.
- the SMF in 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 the 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) sent 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 part_B720 is a functional part for the UPF to connect to the base station device (gNB) in 5GAN and / or SMF and / or DN. That is, the UPF uses the network connection _B720 to send and receive user data and / or control information between the base station equipment (gNB) in 5GAN and / or SMF and / or DN. Can be done.
- the UPF in 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, can communicate with DN via N6 interface, and can communicate with other UPFs via 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 transfer function ), packet routing and transfer function, UL CL (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 the user plane, 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 non-IP communication and IP communication.
- the plurality of gateways to be arranged 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 the other NFs.
- the user plane is user data sent 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 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 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 and 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.
- PCF has a function to provide policy rules.
- UDM has authentication information processing (Authentication credential processing) function, user identification processing function, access authentication function, registration / mobility management function, subscriber information management (subscription management) function, and the like.
- authentication credential processing Authentication credential processing
- user identification processing user identification processing
- access authentication function access authentication function
- registration / mobility management function registration / mobility management function
- subscriber information management (subscription management) function and the like.
- PCRF is connected to PGW and / or PDN, and has a function of performing QoS management for data delivery. For example, it manages the QoS of the communication path between UE_A10 and PDN.
- the PCRF may be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules that each device uses when transmitting and receiving user data.
- PCC Policy and Charging Control
- HSS is connected to MME and / or SCEF and has a function to manage subscriber information.
- HSS subscriber information is referred to, for example, when controlling access to MME.
- the HSS may be connected to a position management device different from the MME.
- SCEF is connected to DN and / or PDN, MME and HSS, and has a function as a relay device that transfers user data as a gateway connecting DN and / or PDN and core network_A. .. SCEF may be a gateway for non-IP communication. In addition, SCEF may have the ability to convert between non-IP communication and IP communication. In addition, a plurality of such gateways may be arranged in the core network_A. The SCEF may be configured outside or inside the core network.
- 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, core network_B, and DN may be referred to as a network or a network device. That is, the fact that the network executes the transmission / reception and / or processing of messages may mean that the devices (network devices and / or control devices) in the network execute the transmission / reception and / or processing of messages. .. Conversely, the fact that a device in the network executes message transmission / reception and / or processing may mean that the network executes message transmission / reception and / or processing.
- SM session management
- NAS Non-Access-Stratum
- SM messages may be NAS messages used in procedures for SM, and are sent and received between UE_A10 and SMF_A230 via AMF_A240. It may be a control message to be executed.
- SM messages include PDU session establishment request messages, PDU session establishment acceptance messages, PDU session completion messages, PDU session rejection messages, PDU session change request messages, PDU session change acceptance messages, PDU session change response messages, and the like. You may.
- the procedure for SM may include a PDU session establishment 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.
- non 5GS 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 the relationship between the DN that provides the PDU connectivity service and the UE, but it is established between the UE and the 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 in the DN.
- each device may manage one or more identification information in association with each other for the 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 that connects 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 indicates that data is sent and received using IPv4.
- IPv6 indicates that data is sent and received using IPv6.
- Ethernet indicates that Ethernet frames are sent and received. Further, Ethernet may indicate that communication using IP is not performed.
- Unstructured indicates that data is sent and received to the application server etc. in the DN by using the point-to-point (P2P) tunneling technology.
- P2P point-to-point
- the PDU session type may include an IP in addition to the above. IP can be specified if the UE can use both IPv4 and IPv6.
- 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.
- 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 a network and is adopted or defined in 3GPP.
- NSI is an entity of NS that consists of one or more in core network_B.
- NSI may be composed of 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 divide user data delivered by services or 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 the NS of.
- 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.
- SD may be information for interpolating SST when selecting one NSI from a plurality of NSIs represented by SST.
- 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 UE registration information 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 from the network for each PLMN. Also, NSSAI may be the information used to select AMF.
- requested NSSAI is information including one or more S-NSSAI indicating one or more network slices that the UE wants to register.
- S-NSSAI included in requested NSSAI may be expressed as requested S-NSSAI.
- allowed NSSAI is information that includes one or more S-NSSAIs indicating one or more network slices allowed by the UE.
- the UE and the network each store and manage allowed NSSAI as UE information.
- S-NSSAI included in allowed NSSAI may be expressed as allowed S-NSSAI.
- rejected NSSAI includes one or more S-NSSAI indicating one or more network slices that the network does not allow among S-NSSAI (s) included in requested NSSAI transmitted from the UE to the network. Further, for each S-NSSAI included in the rejected NSSAI, a reason value (cause) indicating the reason for refusal may be included in the rejected NSSAI. S-NSSAI included in rejected NSSAI may be expressed as rejected S-NSSAI.
- 5GMM-CONNECTED mode with RRC inactive indication is a state indicating that the state of the NAS layer is in the connected state even though the RRC layer is inactive (inactive).
- 5GMM-CONNECTED mode with RRC inactive indication is a state in which the wireless bearer is released while maintaining the context of the NAS signaling connection and / or the NAS signaling connection.
- support for 5GMM-CONNECTED mode with RRC inactive indication means that the state of the NAS layer can be maintained in the connected state even when a notification indicating that the RRC layer has been disabled is received from the lower layer. It may mean that it is supported.
- use of 5GMM-CONNECTED mode with RRC inactive indication means that the state of the NAS layer is maintained in the connected state even when the notification indicating that the RRC layer has been disabled is received from the lower layer. It may mean.
- the tracking area 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. Hereinafter, the tracking area may be TA (Tracking Area).
- the TA list is a list that includes one or more TAs assigned to UE_A10 by the network.
- UE_A10 may be able to move without executing the tracking area update procedure while moving within one or more TAs included in the TA list.
- the UE_A10 may be a group of information indicating the area in which the TA list can be moved without performing the tracking area update procedure.
- the TA list may be expressed as a TAI list composed of a plurality of TAIs (Tracking area identities).
- the TAI list may refer to a TA list.
- the UE ID is information for identifying the UE.
- the UE ID is SUCI (SUbscription Concealed Identifier), SUPI (Subscription Permanent Identifier), GUTI (Globally Unique Temporary Identifier), IMEI (International Mobile Subscriber Identity), or IME ISV (IMEI Software Version).
- SUCI SUbscription Concealed Identifier
- SUPI Subscribe Permanent Identifier
- GUTI Globally Unique Temporary Identifier
- IMEI International Mobile Subscriber Identity
- IME ISV IMEI Software Version
- the UE ID may be other information set in the application or network.
- the UE ID may be information for identifying the user.
- Non-Public Network is a private network that is used by specific users for specific purposes, such as private use such as companies, not for general use.
- NPN Non-Public Network
- SNPN is operated by the NPN operator and is unaffected by the functional parts provided by PLMN.
- SNPN is an NPN-only network that is independent of PLMN, which is open to the public.
- Public network integrated NPN is executed by using the functional part of PLMN.
- the Public network integrated NPN is an NPN that is virtually realized within PLMN.
- Public network integrated NPN is an NPN that can be created via PLMN.
- the public network integrated NPN may be realized by using, for example, the network slice function. Specifically, this can be achieved by using the network slices assigned for the NPN.
- the public network integrated NPN may be identified by S-NSSAI or by a combination of S-NSSAI and CAG ID.
- the CAG (Closed Access Groups) ID is information that identifies a group of subscribers who are allowed to connect to one or more cells associated with the CAG, and the CAG is identified by the CAG ID. It is a group.
- CAG is a group used to realize Public network integrated NPN with network slices.
- CAG is used to prevent network slices assigned for NPN from attempting access from UEs that do not allow NPN.
- the CAG ID is unique information within PLMN.
- NID Network identifier
- PLMN Packet Management Entity
- NID Network identifier
- the NID may be unique information within the SNPN or may be globally unique information.
- the information indicating NPN is information identified by one or more of S-NSSAI and / or NID, and / or CAGID, and / or NID, and / or DNN, and / or PLMNID. It may be.
- the information indicating NPN may be information identified by S-NSSAI and CAGID, information identified by PLMNID and NID, or S-.
- the information may be identified by NSSAI and NID, or may be information identified by S-NSSAI and DNN.
- the information indicating the NPN may be S-NSSAI.
- "when the information indicating NPN includes the above information” includes "when the information indicating NPN is the above information”.
- "when the information indicating NPN includes S-NSSAI” includes "when the information indicating NPN is S-NSSAI".
- a UE that can be connected with a high priority within the NPN is a UE that can preferentially request a connection within a specific NPN as a target of access control and is not restricted in sending and receiving control messages.
- UEs that can be connected with high priority within the NPN are AMF and / or SMF based on MM (Mobility Management) signal congestion or DNN (Data Network Name) -based congestion and / or network slice-based. Even in the state where congestion is detected and the congestion control procedure is started, the UE may be a UE whose request is not rejected because of congestion.
- UEs that can be connected with high priority in NPN are UEs that are allowed to connect with high priority in NPN, UEs that can be connected with high priority in NPN, and UEs in NPN.
- UE set with high priority in UE registered with high priority in NPN
- UE set as high priority UE in NPN UE with high priority in NPN
- UE with high priority in NPN It may be expressed as UE, which is registered as.
- this NPN may be referred to as an NPN where the UE is allowed to connect with a higher priority.
- the first information may be information indicating one or more required NPNs.
- the first information is identified by one or more of S-NSSAI and / or S-NSSAI and / or NID contained in requested NSSAI, and / or CAGID and / or NID, and / or DNN. Information may be used.
- the first identification information may be an information group including a plurality of sets of combinations of a plurality of identification information. Specifically, for example, the first identification information may be a combination of a plurality of S-NSSAI and CAG ID. It may be a group of information including.
- the first information may be information indicating that the S-NSSAI requested by the UE is a slice for NPN.
- the second information requires information indicating that the UE is a high priority UE within the NPN required by the UE and / or being registered as a high priority UE within the NPN required by the UE. It may be information indicating that.
- the second identification information is registered as information indicating whether or not the UE has a higher priority in the NPN required by the UE, and / or as a UE with a higher priority in the NPN requested by the UE. It may be information indicating whether or not to request that.
- the second information may be associated with the first information.
- the first information is information indicating a plurality of NPNs
- the second identification information may be associated with each NPN included in the first identification information.
- each S-NSSAI may indicate whether or not the UE is allowed to connect within the S-NSSAI with a high priority.
- a UE having a high priority in the NPN may be synonymous with a UE that can be connected with a high priority in the NPN.
- the third identification information may be information indicating that the UE requests an NPN connection.
- the third identification information may be information indicating the NPN required by the UE, and may be, for example, the first identification information.
- the third identification information may be information indicating a network slice for the NPN for which the UE requests a connection, and may be S-NSSAI included in requested NSSAI.
- the third identification information may be information indicating that the UE is permitted to connect to the NPN, and may be, for example, the fourth identification information.
- the third identification information may also be a flag indicating that the UE requests a connection to the NPN.
- the third identification information may be information obtained by combining a plurality of these pieces of information.
- the fourth identification information may be UE capability information (UE capability).
- the fourth identification information may be information indicating that the UE is permitted to connect to the NPN, and may be information indicating one or more NPNs to which the UE is permitted to connect. Further, the fourth identification information may be information indicating that the UE can operate as a UE that is allowed to connect with a high priority within the requested NPN.
- the fourteenth identification information may be information indicating that the UE supports functions related to NPN.
- the eleventh identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the eleventh identification information may be a list composed of information indicating one or more NPNs. The eleventh identification may be the information contained in the UE context. The eleventh identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The eleventh identification information may be information indicating that the connection is permitted with a high priority within the NPN requested by the UE.
- the twelfth identification information may be information indicating rejected NSSAI and a reason value (cause value) indicating rejection due to congestion.
- the twelfth identification information may be identification information different from the information indicating rejected NSSAI, in which case the twelfth identification information may be a reason value (cause) indicating rejection due to congestion, and is rejected. It may be associated with S-NSSAI included in NSSAI.
- the thirteenth identification information is information indicating the value of the back off timer.
- the AMF may store the thirteenth identification information in association with the UE and the network slice.
- the thirteenth identification information may be stored in association with rejected NSSAI.
- the 14th identification information is information indicating that the UE is permitted to connect to the NPN.
- the fourteenth identification information may be information indicating the NPN for which the UE is permitted.
- the 14th identification information may be further information indicating that S-NSSAI contained in allowed NSSAI is S-NSSAI for NPN.
- the 14th identification information may be SST or SD included in S-NSSAI, or may be S-NSSAI included in allowed NSSAI.
- the 14th identification information may be information associated with S-NSSAI included in allowed NSSAI.
- the fifteenth identification information may be network capability information (UE capability).
- the fifteenth identification information may be information indicating that the network supports the connection to the NPN. For example, if the NPN is identified by S-NSSAI, the fifteenth identification information indicates that the network does not support connecting to S-NSSAI for NPN.
- the fifteenth identification information may be a reason value (cause) included in rejected NSSAI.
- the 21st identification information is information indicating that the UE is not a UE that can be connected with a high priority in the NPN requested by the UE.
- the 21st identification information may be a reason value (Cause value) indicating the reason for refusal.
- the 21st identification information may include information indicating the NPN to be rejected.
- the 22nd identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the 22nd identification information may be a list composed of information indicating one or more NPNs. The 22nd identification may be the information contained in the UE context. The 22nd identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The 22nd identification information may be information indicating that the connection with high priority is refused within the NPN requested by the UE.
- the 31st identification information is the NPN requested by the UE and is information indicating that the UE can be connected with a high priority.
- the thirty-first identification information may include information indicating one or more required NPNs.
- the thirty-first identification information may be information indicating a service type. Specifically, the 31st identification information may be a service type meaning that the UE is a UE that can be connected with a high priority.
- the 41st identification information is information indicating the required NPN.
- the 41st identification information may be information indicating that the UE requests the establishment of a PDU session to the NPN.
- the 41st identification information may be information for requesting the network to perform an additional authentication / approval procedure for the NPN for each requested NPN.
- the information indicating the required NPN and the information for requesting the network to execute an additional authentication / approval procedure for the NPN for each requested NPN are used as different information. May be good.
- the 42nd identification information is information indicating that the UE is a UE set and / or registered as a UE that can be connected with a high priority within the requested NPN.
- the 42nd identification information may be associated with the 41st identification information.
- the 42nd identification information may be information for requesting the network to execute an authentication / approval procedure for NPN.
- the 51st identification information is information indicating the NPN for which the establishment of a PDU session is permitted.
- the 51st identification information may be information indicating that the established PDU session is a PDU session established to the NPN and / or a PDU session established via the NPN.
- the 51st identification information may be information indicating NPN.
- the 52nd identification information may be the result of performing additional authentication / approval procedures for NPN.
- the 52nd identification information may be information indicating that the connection to the NPN has been permitted as a result of the additional authentication / approval procedure for the NPN requested by the UE.
- the 61st identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the 61st identification information may be a list composed of information indicating one or more NPNs. The 61st identification may be the information contained in the UE context. The 61st identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The 61st identification information may be information indicating that the UE is not a UE that can be connected with a high priority within the NPN requested by the UE. The 61st identification information may be a reason value (Cause value) indicating the reason for refusal.
- a reason value (Cause value) indicating the reason for refusal.
- the 62nd identification information indicates that the additional authentication / approval procedure for the NPN required by the UE does not allow the connection to the NPN as a result of the additional authentication / approval procedure for the NPN requested by the UE.
- the 62nd identification information may be a cause value indicating that the UE's request is rejected because the connection to the NPN is not permitted.
- the 71st identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the 71st identification information may be a list composed of information indicating one or more NPNs. The 71st identification may be the information contained in the UE context. The 61st identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The 71st identification information may be information notifying that an addition and / or deletion and / or change has occurred to the list of NPNs set as UEs to which the UE connects to the UE with high priority.
- each device exchanges various capability information and / or various request information of each device in the notification information and / or RRC procedure and / or the registration procedure in the core network and / or the service request procedure for emergency call. / Or may be obtained.
- each device involved in this procedure sends and receives one or more identification information included in each control message by transmitting and receiving each control message described in this procedure, and stores each transmitted and received identification information as a context. May be good.
- the service request procedure and / or the PDU session establishment procedure and / or the IMS registration procedure and / or the IMS emergency call connection procedure may be referred to as the emergency call connection process.
- the procedures used in each embodiment include a registration procedure, a service request procedure, a PDU session establishment procedure, a PDU session management procedure, and a PDU session management procedure. Includes the Generic UE configuration update procedure. Each procedure will be explained below.
- HSS and UDM, PCF and PCRF, SMF and PGW-C, UPF and PGW-U are the same device (that is, the same physical device).
- the case where it is configured as 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).
- 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.
- the UE can start this procedure at any time if it is in the unregistered state (RM-DEREGISTERED state).
- each device particularly UE and AMF
- the registration procedure is to update the UE location registration information in the network and / or to periodically notify the network of the UE status from the UE and / or to update 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 start this procedure when the running timer expires. 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 the ability 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 may be based on the completion of the UE configuration update procedure, or on the basis of the completion of the registration procedure, or on the basis of the completion of the PDU session establishment procedure, or on the basis of the completion of the PDU session management procedure, or in each procedure.
- the registration procedure may be initiated based on the information received from the network.
- the UE is not limited to these, and can execute the registration procedure at any timing.
- 5GAN120 (or gNB_A122) sends broadcast information to neighboring UEs (S601).
- the broadcast information may be SIB (System Information Block).
- 5GAN120 (or gNB_A122) may transmit the broadcast information including PLMNID and / or CAGID and / or NID.
- the CAG ID and NID may be associated with the PLMN ID.
- 5GAN120 (or gNB_A122) is a device in the access network for SNPN
- 5GAN120 (or gNB_A122) includes the PLMN ID for NPN and one or more NIDs in the broadcast information.
- 5GAN120 (or gNB_A122) may be sent to the UE in the cell.
- 5GAN120 (or gNB_A122) is a device in the access network for Public network integrated NPN
- gNB_A122 or eNB_B145 broadcasts PLMN ID indicating PLMN including Public network integrated NPN and one or more CAG IDs. May be sent to the UE in the cell of 5GAN120 (or gNB_A122) included in.
- the 5GAN120 (or gNB_A122) is not an NPN-only access network, that is, if the NPN and another PLMN share an access network, the 5GAN120 (or gNB_A122) will include the CAG ID and / in the broadcast information. Alternatively, it may be sent to the UE in the cell of 5GAN120 (or gNB_A122) without including the NID.
- UE_A10 may decide to request registration with NPN and / or PLMN based on the received broadcast information and / or one or more pieces of information contained in the broadcast information, and may start the following registration procedure.
- the UE starts the registration procedure by sending a registration request message to 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 at the NAS layer, and RRC messages are processed at the RRC layer.
- the NAS layer is a higher layer than the RRC layer.
- the UE can transmit at least one of the identification information of the first to the fourth identification information by including it in the registration request message and / or the RRC message, but a control message different from these. For example, it may be included in a control message of a layer lower than the RRC layer (for example, MAC layer, RLC layer, PDCP 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 first You may send 1 request.
- the UE may send the first identification information to the network without recognizing that the requesting network is NPN.
- the UE can initiate the authentication / approval procedure for the connection to the NPN shown in the first identification information by using the UE ID included in the registration request message to AMF. Good.
- the UE may have the AMF confirm the setting information of the UE. Specifically, the AMF may confirm whether or not the connection is permitted with a high priority in association with the UE and the requested NPN based on the reception of the first identification information.
- the UE requests a connection to an NPN and / or is configured as a UE that is allowed to connect with a higher priority within the NPN requested by the UE, and / or within the NPN requested by the UE. If you request to be registered as a UE that allows connections with high priority, you may send a second identification. If the UE requests connection to the NPN but does not require registration as a UE that connects with a high priority within the requested NPN, it is not necessary to transmit the second identification information. By transmitting the second identification information, the UE may have the AMF confirm whether the connection is permitted with a high priority within the NPN requested by the UE.
- the UE may send a third identification information when requesting an NPN connection.
- the UE may indicate to the network that the network requested by the UE is an NPN by transmitting a third identification information.
- the UE may have the AMF confirm that the network slice requested by the UE is a network slice for NPN.
- the UE may send a fourth identification information if it requests a connection to the NPN and / or if the UE supports the ability to connect to the NPN.
- the UE may have the AMF confirm the network capability information (Network capability).
- the first to fourth identification information stored by the UE is the information acquired by the UE in the procedure before this procedure and / or the information generated by the UE based on the information acquired in the procedure before this procedure. You can. Specifically, for example, when S-NSSAI is included in the first identification information, the UE has received allowed NSSAI from the network in the procedure before this procedure, and the S-NSSAI included in the first identification information is , It may be S-NSSAI included in allowed NSSAI to be memorized.
- the procedure before this procedure is, for example, that this procedure updates the location registration information of the UE and / or periodically notifies the network of the status of the UE from the UE, and / or relates to the UE in the network. If it is a registration procedure for updating a specific parameter, it may be a registration procedure that has occurred before this procedure.
- the UE may include other than the identification information 1 to 4 in the registration request message and / or the RRC message including the registration request message, for example, UE ID and / or PLMN ID and / or requested NSSAI and / or CAG ID. And / or NID may be included in the transmission.
- the UE may also include the SM message (eg, PDU session establishment request message) in the registration request message, or send the SM message (eg, PDU session establishment request message) together with the registration request message.
- the PDU session establishment procedure may be started during the registration procedure.
- 5GAN When 5GAN (or gNB) receives an RRC message including a registration request message, it selects the AMF to which the registration request message is forwarded (S602). Note that 5GAN (or gNB) can select AMF based on the information contained in the registration request message and / or RRC message. Specifically, 5GAN (or gNB) may select the AMF in the NPN required by the UE based on at least one of the identification information of the first to the fourth identification information. For example, 5GAN (or gNB) may select the AMF included in the NPN shown in the first identification information based on the first identification information, or support the NPN shown in the first identification information. You may select the AMF to be used. In that case, the exchange of information on NPN including AMF and / or supported by AMF occurs in advance between 5GAN (or gNB) and AMF, or notification from AMF to 5GAN (or gNB) occurs. There is.
- the selection method of AMF is not limited to this, and 5GAN (or gNB) may select AMF based on other conditions. 5GAN (or gNB) extracts the registration request message from the received RRC message and forwards the registration request message to the selected AMF (S604). If at least one of the identification information 1 to 4 is not included in the registration request message but is included in the RRC message, the identification information included in the RRC message is requested to be registered in the selected AMF. It may be forwarded with the message (S604).
- the AMF When AMF receives the registration request message, it can execute the first condition determination.
- the first conditional determination is for determining whether or not the network (or AMF) accepts the UE request.
- the AMF starts the procedure (A) in FIG. 6 when the first condition determination is true, whereas it starts the procedure (B) in FIG. 6 when the first condition determination is false.
- the first condition determination is the reception of the registration request message and / or each identification information contained in the registration request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and It may be executed based on / or the state of the network and / or the user's registration information and / or the context held by AMF. For example, if the network allows the UE request, the first condition determination is true, and if the network does not allow the UE request, the first condition determination may be false. Also, if the network to which the UE is registered and / or the devices in the network support the functions required by the UE, the first condition determination is true and does not support the functions required by the UE. In this case, the first condition determination may be false.
- 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 AMF restricts the transmission and reception of mobility management messages such as registration procedures based on congestion, the UE will also give higher priority within the network (PLMN and / or NPN) to which the AMF belongs. If the UE is not allowed to connect, the first condition is false and the UE is a UE that is allowed to connect with high priority within the network (PLMN and / or NPN) to which AMF belongs. , The first condition determination may be true.
- the condition for determining the truth of the first condition determination does not have to be limited to the above-mentioned condition.
- the AMF can first execute the fourth condition determination in the procedure (A) of FIG.
- the fourth condition determination is for determining whether or not the AMF sends and receives SM messages to and from the SMF.
- the fourth condition determination may be executed based on whether or not the AMF has received the SM message. Further, the fourth condition determination may be executed based on whether the registration request message includes the SM message. For example, if the AMF received the SM message and / or if the registration request message contained the SM message, the fourth condition may be true and if the AMF did not receive the SM message. And / or if the registration request message does not include the SM message, the fourth condition determination may be false.
- the condition for determining the truth of the fourth condition determination does not have to be limited to the above-mentioned condition.
- AMF selects SMF when the fourth condition determination is true and sends and receives SM messages to and from the selected SMF, whereas when the fourth condition determination is false, AMF sends and receives SM messages. , Do not execute them (S606). Further, even if the fourth condition determination is true, the AMF may cancel the procedure (A) in FIG. 6 when receiving an SM message indicating rejection from the SMF. At this time, the AMF can start the procedure (B) in FIG.
- AMF can notify SMF of the identification information received in the registration request message when sending and receiving SM messages to and from SMF.
- the SMF can acquire the identification information received from the AMF by sending and receiving SM messages to and from the AMF.
- the AMF then sends the UE via 5G AN (or gNB) as a response message to the registration request message based on the receipt of the registration request message and / or the completion of sending and receiving the SM message to and from the SMF.
- Send a Registration accept message (S608).
- the AMF may send a registration acceptance message based on the receipt of the registration request message from the UE.
- the AMF may send a registration acceptance message based on the completion of sending and receiving the SM message to and from the SMF.
- the registration acceptance message is a NAS message sent and received on the N1 interface, but it is included in the RRC message and sent and received between the UE and 5GAN (gNB).
- AMF may send the registration acceptance message including at least one or more of the identification information of the 11th to 15th identification information.
- the AMF may indicate that the network supports each function by sending these identification information and / or the registration acceptance message, or may indicate that the UE request has been accepted. Alternatively, information that combines these may be shown. 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.
- the AMF receives at least one of the first to fourth identification information from the UE, and / or when the UE setting information is updated, at least one of the eleventh to fifteenth identification information. May be sent.
- the UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the eleventh identification information.
- the high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority.
- the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list.
- the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority.
- Allowed NSSAI or Configured NSSAI or rejected NSSAI even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.
- the UE may update the NSSAI information when it receives the twelfth identification information. Specifically, the UE may manage the S-NSSAI included in the received rejected NSSAI as a congested state based on the reason value. Further, the UE may start counting the backoff timer based on the reception of the twelfth identification information.
- the backoff timer may be a value received from the network or information held in advance by the UE.
- the twelfth It is not necessary to start the back-off timer even if the identification information of is received.
- the UE may start counting the backoff timer by receiving the thirteenth identification information. If S-NSSAI is included in the information indicating the NPN, and if the UE is a UE that is allowed to connect with high priority within the NPN supported by the rejected S-NSSAI, the 13th It is not necessary to start the back-off timer even if the identification information of is received.
- the UE may update the setting information of the UE by receiving the 14th identification information. Specifically, the UE stores information that identifies the NPN that the UE is authorized to use, based on the 14th identification information. If S-NSSAI is included in the information that identifies the NPN, the memory related to NSSAI may be updated. Specifically, the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN, or the NPN is indicated by the corresponding S-NSSAI in the list of allowed NSSAI, Configured NSSAI, or rejected NSSAI. A flag indicating that it is S-NSSAI may be associated and stored.
- the UE may detect and store that the network supports the connection to the NPN based on the reception of the fifteenth identification information.
- the UE may initiate the registration process with the NPN based on the receipt of the fifteenth identification information, or to transition to a state in which the establishment of a PDU session via (or to the NPN) is permitted via the NPN. You may start the registration procedure.
- each process that the UE shown above executes based on the reception of each identification information may be executed during 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.
- AMF indicates which of the 11th to 15th identification information should be included in the registration acceptance message, each received identification information and / or subscriber information, and / or network capability information, and / Alternatively, it may be selected and determined based on the operator policy and / or the network status and / or the user's registration information and / or the context held by the AMF.
- the AMF may send the eleventh identity when the UE changes the list of NPNs that are allowed to connect with a high priority, that is, when the context held by the AMF is updated. Good.
- the AMF may transmit the twelfth identification information. For example, the AMF may transmit the fifteenth identification information when it receives the fourth identification information from the UE.
- the AMF can send the registration acceptance message including the SM message (for example, the PDU session establishment acceptance message), or send the SM message (for example, the PDU session establishment acceptance message) together with the registration acceptance message.
- this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included in the registration request message and the fourth condition determination is true. Further, this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included together with the registration request message and the fourth condition determination is true.
- AMF can indicate that the procedure for SM has been accepted in the registration procedure.
- AMF also receives each identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user registration information and / or It may be shown that the UE request has been accepted by sending the registration acceptance message based on the context held by the AMF.
- the UE receives the registration acceptance message via 5GAN (gNB) (S608).
- gNB 5GAN
- the UE can recognize that the UE request by the registration request message has been accepted and the contents of various identification information contained in the registration acceptance message.
- the UE can also send a registration completion message to AMF via 5GAN (gNB) as a response message to the registration acceptance message (S610).
- gNB 5GAN
- the UE may send the registration completion message including the SM message such as the PDU session establishment completion message, or by including the SM message. , May indicate that the procedure for SM has been completed.
- 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 5G AN (gNB) (S610).
- each device completes the procedure (A) in FIG. 6 based on the transmission / reception of the registration acceptance message and / or the registration completion message.
- the AMF sends a registration rejection message to the UE via 5GAN (gNB) as a response message to the registration request message (S612).
- the registration refusal 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).
- the AMF may indicate that the UE request by the registration request message has been rejected by sending the registration refusal message.
- the AMF may send at least one of the 21st to 22nd identification information by including it in the registration refusal message and / or NAS message and / or RRC message.
- the AMF may transmit at least one of the 21st to 22nd identification information based on the reception of at least one of the 1st to 4th identification information.
- AMF may include the value of the backoff timer in the registration refusal message and send it. Note that the AMF may send a registration refusal message without including the value of the backoff timer when the UE is allowed to connect with a high priority within the NPN requested by the UE.
- the UE may detect that the connection is not permitted within the NPN requested by the UE with a high priority based on the reception of the 21st identification information. Further, the UE may update the memory of the information indicating the NPN based on the reception of the 21st identification information. Specifically, based on the reception of the 21st identification information, the UE may associate the information indicating the rejected NPN with the information indicating that the connection is not permitted with a high priority, or the UE may be rejected. If the information indicating NPN is linked to the information indicating that connection is permitted with high priority, even if the information indicating that connection is permitted with high priority is released from the information indicating NPN. Good.
- the UE may delete the rejected S-NSSAI from the list of possible high priority connections and store it.
- the flag indicating that the connection is possible with a high priority to be remembered in association with the rejected S-NSSAI may be removed.
- the UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the 22nd identification information.
- the high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority.
- the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list.
- the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority.
- Allowed NSSAI or Configured NSSAI or rejected NSSAI even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.
- each process that the UE shown above executes based on the reception of each identification information may be executed during 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. The UE receives a registration refusal message via 5GAN (gNB) (S612). By receiving the registration refusal message, the UE can recognize that the UE request by the registration request message has been rejected and the contents of various identification information included in the registration refusal message. In addition, the UE may recognize that the request of the UE has been rejected if the registration acceptance message or the registration refusal message is not received within a predetermined period after sending the registration request message. .. Each device completes the procedure (B) during this procedure based on the transmission and reception of the registration refusal message.
- the procedure (B) in Fig. 6 may be started when the procedure in (A) in Fig. 6 is canceled.
- the AMF may send the registration refusal message including the SM message indicating rejection such as the PDU session establishment refusal message.
- the SM message which means refusal, may be included to indicate that the procedure for SM has been rejected.
- the UE may further receive an SM message indicating rejection such as a PDU session establishment refusal message, or may recognize that the procedure for SM has been rejected.
- Each device completes the registration procedure based on the completion of the procedure (A) or (B) in Fig. 6.
- each device may transition to the state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure (A) in FIG. 6, or the procedure in (B) in FIG. 6 is completed.
- the UE may remain unregistered in the network (RM_DEREGISTERED state), or the UE may transition to a state in which it is not registered in the network.
- the transition of each device to each state may be performed based on the completion of the registration procedure, or may be performed based on the establishment of the PDU session.
- each device may perform processing based on the information sent and received in the registration procedure based on the completion of the registration procedure. For example, when sending and receiving information indicating that a part of the UE's request is rejected, the reason why the UE's request is rejected may be recognized. Further, each device may perform this procedure again based on the reason why the UE request is rejected, or may perform the registration procedure for the core network_A or another cell.
- the UE may store the identification information received with the registration acceptance message and / or the registration refusal message based on the completion of the registration procedure, or may recognize the network decision.
- the rejected S-NSSAI shown in the twelfth identification information is allowed to connect with the UE having a high priority. If it is not included in the information indicating the NPN, the UE may start the backoff timer, and while the backoff timer is counting, the transmission of the registration request message including the rejected S-NSSAI may be stopped. Alternatively, the UE manages the rejected S-NSSAI as the rejected S-NSSAI while counting the backoff timer, and stores the rejected S-NSSAI as the configured NSSAI after the count of the backoff timer ends. May be good.
- the rejected S-NSSAI further shown in the twelfth identification information allows the UE to connect with a high priority. If it is included in the information indicating the NPN to be used, the UE does not start counting the backoff timer, but then starts the registration procedure again by sending a registration request message containing the rejected S-NSSAI. May be good. Or, in that case, the UE starts counting the backoff timer, but based on the fact that the UE is a UE that is allowed to connect with high priority in the NPN even while the backoff timer is counting. , You may start the registration procedure.
- the UE will have a PDU session to establish a PDU session to the authorized NPN.
- the establishment procedure may be initiated.
- the UE when the UE receives the registration acceptance message and / or the 11th identification information and / or the 14th identification information and / or the 15th identification information, the UE further transitions from the connected state to the idle state. If so, the service request procedure for resuming the connection to the NPN may be initiated.
- the service request procedure is a procedure for the UE to transition from the idle state (5GMM-IDLE) to the connected state (CONNECTED mode).
- the UE may initiate a service request triggered by retention of user data or paging or notification from the network.
- the UE may be in a state where it has received the registration acceptance message and completed the registration procedure before starting the service request.
- the UE sends a service request message to AMF (S700).
- the service request message is a NAS message sent and received on the N1 interface, but it is included in the RRC message and sent and received between the UE and 5GAN (gNB).
- the UE may send the 31st identification information by including it in the service request message and / or the RRC message including the service request message.
- 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 If the UE is a UE that is allowed to connect with a high priority within the requesting NPN, it will send a service request message and / or the 31st identification information even while the backoff timer is counting. May be good.
- the UE may indicate that it requests the AMF to connect to the NPN by sending the 31st identification information, and further, on the UE that is allowed to connect with a high priority within the NPN requested by the UE. It may be shown that there is.
- the AMF When the AMF receives the service request message, it executes the first process (S702). In the first process, the AMF decides whether to accept the UE's service request. In the first process, the AMF executes the procedure (A) in FIG. 7 when accepting the service request of the UE. On the other hand, when the AMF rejects the UE service request in the first process, it executes the procedure (B) in FIG. 7.
- the method of determining whether or not to accept the service request from the UE by the first process is to receive the service request message and / or each identification information contained in the service request message and / or the subscriber information and /. Alternatively, it may be determined based on network capability information and / or operator policy and / or network status and / or user registration information and / or context held by AMF.
- AMF is performing mobility management congestion control and / or DNN-based congestion control and / or S-NSSAI-based congestion control based on the 31st identification information of the UE. The request does not have to be rejected due to congestion.
- AMF does not send a rejection message including a backoff timer to the UE even if congestion control is active.
- the determination of whether or not to accept the UE service request is not limited to the method described above.
- the AMF receives the service request message and / or sends a service acceptance message to the UE based on the first process (S704).
- the AMF receives the service request message and / or sends a service rejection message to the UE based on the first process (S706).
- Each device completes the service request procedure based on the completion of the procedure (A) or (B) in Fig. 7.
- each device is connected from the state where the N1 interface used for sending and receiving NAS messages is not connected (CM-IDLE) to the state where it is connected (CM-CONNECTED) based on the completion of the procedure (A) in FIG. May transition to.
- each device may maintain a state in which the N1 interface used for sending and receiving NAS messages is not connected (CM-IDLE) based on the completion of the procedure (B) in FIG.
- each device may perform processing based on the information sent and received in the service request procedure based on the completion of the service procedure. Further, each device may perform this procedure again based on the reason why the UE request is rejected, or may perform the registration procedure for the core network_A or another cell.
- the UE may store the identification information received along with the service acceptance message and / or the service rejection message based on the completion of the service procedure, or may recognize the network decision.
- the UE may start the registration procedure based on the receipt of the service acceptance message.
- the PDU session establishment procedure is a procedure in 5GS.
- this procedure refers to the procedure for establishing a PDU session.
- the PDU session establishment procedure is a procedure for each device to establish a PDU session.
- each device can start the PDU session establishment procedure at an arbitrary timing when the registration procedure is completed and the registration state is reached.
- each device may be able to execute the PDU session establishment procedure in the registration procedure.
- each device may establish a PDU session based on the completion of the PDU session establishment procedure.
- the PDU session establishment procedure may be a procedure initiated by the UE, or may be a procedure requested and initiated by the UE.
- Each device can establish a plurality of PDU sessions by executing the PDU session establishment procedure a plurality of times. For example, if the UE requires that a PDU session be established through multiple NPNs, the UE may initiate a PDU session establishment procedure for each requested NPN.
- the UE may start the PDU session establishment procedure based on the identification information received in the registration procedure. For example, in the registration procedure, if the UE receives information indicating NPN, the UE may start this procedure.
- the UE sends a NAS message including a PDU session establishment request message to the SMF via 5GAN (gNB) and AMF (S800) (S802) (S804), and the PDU session. Start the establishment procedure.
- 5GAN gNB
- AMF S800
- S802 S804
- the UE sends a NAS message including a PDU session establishment request message to AMF via 5GAN (gNB) via the N1 interface (S800).
- gNB 5GAN
- S800 the N1 interface
- the UE can transmit one or more of the identification information of at least the 41st to 42nd including the identification information in the PDU session establishment request message and / or the NAS message, but the control is different from these.
- the message may be included in the control message of a layer lower than the RRC layer (for example, MAC layer, RLC layer, PDCP layer) and transmitted. These identifications may be included in these messages to indicate the UE's request. Further, two or more identification information of these identification information may be configured as one or more identification information.
- the UE includes the UE ID and / or PLMN ID and / or requested S-NSSAI and / or CAG ID and / or NID in the PDU session establishment request message and / or RRC message. May be sent.
- the UE may indicate that it requests a connection to the NPN by transmitting the 41st identification information.
- the UE may transmit the 41st identification information if it is allowed to connect to the NPN and / or if it remembers that the UE is a UE that is allowed to connect to the NPN.
- the UE may send the 41st identification information.
- the information indicating the NPN includes a DNN, and the UE requests the establishment of a PDU session to the DNN for the NPN, the UE may transmit the 41st identification information.
- AMF receives a NAS message including a PDU session establishment request message (S800).
- the AMF may be performing DNN-based and / or S-NSSAI-based congestion control.
- DNN-based and / or S-NSSAI-based congestion control is control that starts when AMF and / or SMF detects the congestion state of the Session Management message for DNN and / or S-NSSAI. It may be.
- the AMF determines the fifth condition of whether to transfer the received PDU session establishment request message to the SMF. If the result of the fifth condition determination is true, each device executes the procedure after S802. If the result of the fifth condition determination is false, AMF sends a rejection message to the UE using the NAS message (S801).
- the fifth condition determination is the reception of the registration request message, and / or each identification information contained in the registration request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and It may be executed based on / or the state of the network and / or the user's registration information and / or the context held by AMF.
- the UE when S-NSSAI is included in the information that identifies the NPN, when the UE requests S-NSSAI for NPN, and when the further required S-NSSAI-based congestion control occurs. , Check if the UE is a UE that can connect with a high priority within the NPN or S-NSSAI associated with the S-NSSAI requested by the UE, and the UE has a high priority within the NPN or S-NSSAI. If it is a UE that can be connected with, the fifth condition determination is true, and if it is not a UE that can be connected with high priority within NPN or S-NSSAI, the fifth condition determination is false.
- AMF sends a rejection message (S801).
- the AMF includes the received PDU session establishment request message and the reason value (Cause value) indicating the reason for refusal in the rejection message.
- the AMF may also send the rejection message with the value of the backoff timer included.
- AMF does not need to include the value of the backoff timer when sending a rejection message when the UE remembers that it is a UE that can be connected with high priority within NPN or S-NSSAI.
- the AMF may send a rejection message to the UE containing the value of the backoff timer if the UE is not a UE that can be connected with high priority within NPN or S-NSSAI (S801).
- AMF executes S802 or later if the fifth condition determination is true.
- AMF extracts the PDU session establishment request message from the NAS message and selects SMF as the transfer destination of the PDU session establishment request message (S802).
- AMF indicates each identification information and / or subscriber information contained in the PDU session establishment request message and / or NAS message, and / or network capability information, and / or operator policy, and / or network status.
- / or the transfer destination SMF may be selected based on the user's registration information and / or the context held by the AMF.
- the AMF may select an SMF in the NPN requested by the UE or an SMF supporting the NPN requested by the UE based on the received 41st identification information, or the S-NSSAI indicated by the 41st identification information.
- the SMF contained in may be selected, or the SMF that supports the connection to the DNN indicated by the 41st identification information may be selected.
- AMF forwards the PDU session establishment request message to the selected SMF via the N11 interface (S804).
- the AMF may transfer the received information to the SMF together with the PDU session establishment request message. ..
- the SMF When the SMF receives the PDU session establishment request message (S804), it recognizes various identification information included in the PDU session establishment request message. Then, the SMF executes the third condition determination.
- the third condition determination is for the SMF to determine whether or not to accept the UE request. In the third condition determination, the SMF determines whether the third condition determination is true or false.
- the SMF starts the procedure (A) in FIG. 7 when the third condition determination is true, and starts the procedure (B) in FIG. 8 when the third condition determination is false.
- the third condition determination is the PDU session establishment request message and / or each identification information included in the PDU session establishment request message, and / or the subscriber information, and / or the network capability information, and / or 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, etc. For example, if the network allows the UE request, the third condition may be true. Also, if the network does not allow the UE request, the third condition determination may be false. Furthermore, if the network to which the UE is connected and / or the devices in the network support the functions required by the UE, the third condition determination may be true and does not support the functions required by the UE.
- the third condition determination may be false. Further, if the transmitted / received identification information is permitted, the third condition determination may be true, and if the transmitted / received identification information is not permitted, the third condition determination may be false.
- the condition for determining the truth of the third condition determination is not limited to the above-mentioned condition.
- the SMF selects the UPF to which the PDU session is established, sends a session establishment request message to the selected UPF via the N4 interface (S806), and starts the procedure (A) in FIG.
- the SMF receives each identification information and / or subscriber information and / or network capability information acquired based on the reception of the PDU session establishment request message, and / or the operator policy, and / or the network status. And / or one or more UPFs may be selected based on the user's registration information and / or the context held by the SMF. When a plurality of UPFs are selected, the SMF may send a session establishment request message to each UPF.
- the SMF may select the UPF in the NPN requested by the UE based on the received 41st identification information.
- the UPF selection method is not limited to this, and the SMF may select the UPF based on other conditions.
- the UPF receives the session establishment request message from the SMF (S806) via the N4 interface and creates a context for the PDU session. In addition, the UPF receives the session establishment request message and / or sends a session establishment response message to the SMF via the N4 interface based on creating a context for the PDU session (S808).
- the SMF receives the session establishment response message from the UPF via the N4 interface as a response message to the session establishment request message (S808).
- the SMF may assign an address to the UE based on the reception of the PDU session establishment request message and / or the selection of the UPF and / or the reception of the session establishment response message.
- the SMF may perform additional authentication / approval procedures for the NPN required by the UE based on the receipt of the 41st identification information and / or the 42nd identification information.
- the SMF receives the PDU session establishment request message, and / or selects the UPF, and / or receives the session establishment response message, and / or the UE via the AMF based on the completion of the address assignment of the address assigned to the UE.
- the SMF sends a PDU session establishment acceptance message to the AMF via the N11 interface (S810)
- the AMF that receives the PDU session establishment request message establishes a PDU session to the UE via the N1 interface.
- the PDU session establishment acceptance message may be a NAS message and may be a response message to the PDU session establishment request.
- the PDU session establishment acceptance message can indicate that the PDU session establishment has been accepted.
- the SMF and AMF may indicate that the UE request by the PDU session establishment request has been accepted by transmitting the PDU session establishment acceptance message.
- the SMF and AMF may send the PDU session establishment acceptance message including at least one of the identification information items 51 to 52.
- the SMF and AMF may indicate that the network supports each function by sending these identification information and / or the PDU session establishment acceptance message, and the UE request has been accepted. May be indicated.
- 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 may detect that the PDU session to the NPN requested by the UE has been established by receiving the 51st identification information, and the established PDU session is a PDU session to the NPN. May be detected.
- the UE may detect that the PDU session to the NPN requested by the UE has been established by receiving the 52nd identification information, and the established PDU session is a PDU session to the NPN. May be detected, or it may be detected that authentication / authorization for the requested connection to the NPN has been completed.
- the SMF and AMF include at least which of the 51st to 52nd identification information is included in the PDU session establishment acceptance message of each of the received identification information and / or subscriber information, and / or the network. Selection and determination may be made based on capability information and / or operator policy and / or network status and / or user registration information and / or context held by AMF.
- the SMF may transmit the 52nd identification information based on the reception of the 41st identification information from the UE. Specifically, if the SMF determines that additional authentication / approval is required for the NPN requested by the UE based on the 41st identification information, it executes the authentication / approval procedure, and the 52nd execution result is the execution result.
- the identification information may be sent to the UE.
- the method by which SMF and AMF determine which identification information is included in the PDU session establishment acceptance message is not limited to the above.
- SMF and AMF can include the selected and / or allowed PDU session ID in the PDU session establishment acceptance message.
- the SMF and AMF can also specify a PDU session type that indicates the type of PDU session selected and / or allowed.
- PDU session type any one of IPv4, IPv6, IP, Ethernet, and Unstructured can be specified as described above.
- the SMF and AMF can also include the SSC mode of the selected and / or allowed PDU session in the PDU session establishment acceptance message.
- SMF and AMF can include the approved QoS rules in the PDU session establishment acceptance message.
- the approved QoS rule group may include one or more QoS rules. Further, in this procedure, when a plurality of QoS flows and / or user plane wireless bearers are established, the approved QoS rule group may include a plurality of QoS rules. Conversely, if only one QoS flow and / or user plane radio bearer is established in this procedure, the approved QoS rule group may include one QoS rule.
- the SMF may send the PDU session establishment acceptance message with information indicating that some UE requests have been rejected, or information indicating that some UE requests have been rejected. May indicate why some of the UE's requests were rejected.
- the UE may recognize why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. The reason for rejection may be information indicating that the content indicated by the identification information received by the SMF is not permitted.
- the UE When the UE receives the NAS message including the PDU session establishment acceptance message from the AMF via the N1 interface (S812), the UE sends the PDU session establishment completion message to the SMF via the AMF (S814) (S816).
- the UE can detect that the UE request by the PDU session establishment request has been accepted.
- the UE sends a PDU session establishment completion message to the AMF via the N1 interface (S814).
- the AMF receives the PDU session establishment completion message from the UE, it sends the PDU session establishment completion message to the SMF via the N11 interface (S816).
- the PDU session establishment completion message sent by AMF to SMF may be a response message to the PDU session establishment acceptance message sent from SMF to AMF in S810. Further, the PDU session establishment completion message may be a NAS message. Further, the PDU session establishment completion message may be any message indicating that the PDU session establishment procedure is completed.
- the SMF can execute the second condition determination.
- the second condition determination is for determining the type of message sent / received on the N4 interface. If the second condition determination is true, the SMF sends a session change request message to the UPF via the N4 interface (S818) and receives the session change acceptance message sent by the UPF as its response message (S818). S820). If the second condition determination is false, the SMF sends a session establishment request message to the UPF via the N4 interface (S818) and receives a session change acceptance message sent by the UPF as its response message (S818). S820).
- the second condition determination may be executed based on whether or not a session on the N4 interface for the PDU session has been established. For example, if the session on the N4 interface for the PDU session is established, the second condition determination may be true, and if the session on the N4 interface for the PDU session is not established, the second condition The condition determination of is false.
- the condition for determining the truth of the second condition determination does not have to be limited to the above-mentioned condition.
- Each device sends and receives a PDU session establishment acceptance message and / or sends and receives a PDU session establishment completion message, and / or sends and receives a session change response message, and / or sends and receives a session establishment response message.
- the procedure (A) during this procedure is completed, the UE is in a state where a PDU session for the DN has been established.
- the SMF sends a PDU session establishment reject message to the UE via the AMF (S822) (S824). Specifically, the SMF sends a PDU session establishment refusal message to the AMF via the N11 interface (S822).
- the AMF receives the PDU session establishment request message from the SMF via the N11 interface (S822), it sends a PDU session establishment rejection message to the UE using the N1 interface (S824).
- the PDU session establishment refusal message may be a NAS message. Further, the PDU session establishment refusal message may be any message indicating that the establishment of the PDU session has been rejected.
- the SMF may indicate that the UE request by the PDU session establishment request has been rejected by sending the PDU session establishment refusal message.
- the SMF may send at least one of the 61st to 62nd identifications in the PDU session establishment refusal message.
- the SMF may include the value of the backoff timer in the PDU session establishment rejection message and send it.
- the SMF may transmit at least one of the 61st to 62nd identification information based on the fact that the SMF has received at least one of the 41st to 42nd identification information.
- the UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the 61st identification information.
- the high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority.
- the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list.
- the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority.
- Allowed NSSAI or Configured NSSAI or rejected NSSAI even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.
- the UE may store a setting that does not send a request to establish a PDU session via (or to the NPN) the rejected NPN based on the 61st identification information.
- the UE may recognize that the additional authentication / approval procedure for the NPN requested by the UE has not been completed based on the 62nd identification information, and the UE may recognize that the additional authentication / approval procedure for the NPN requested by the UE has not been completed. You may remember the state in which the procedure has not been completed.
- Each device completes the PDU session establishment procedure based on the completion of the procedure (A) or (B) in FIG. Note that each device may transition to the state in which the PDU session is established based on the completion of the procedure (A) in FIG. 8, or the PDU based on the completion of the procedure (B) in FIG. You may recognize that the session establishment procedure has been rejected, or you may transition to a state where the PDU session has not been established. Furthermore, the UE can communicate with the DN using the established PDU session by completing the procedure (A) in FIG.
- each device may perform processing based on the information transmitted / received in the PDU session establishment procedure based on the completion of the PDU session establishment procedure and the occurrence of each step in the PDU session establishment procedure.
- each device when each device transmits / receives information indicating that a part of the UE's request is rejected, it may recognize the reason why the UE's request is rejected. Further, each device may perform this procedure again based on the reason why the UE request is rejected, or may perform the PDU session establishment procedure for another cell.
- the SMF sends a PDU session establishment acceptance message and / or sends and receives the 51st identification information, and / or sends and receives the 52nd identification information, and / or completes (A) of FIG.
- the management information of the UE may remember that the UE is a UE that is allowed to connect with a high priority in the NPN.
- the SMF sends a PDU session establishment acceptance message and / or ( Based on the completion of A), the backoff timer value is added to the PDU session modification rejection message (PDU session modification reject message) and / or the PDU session deletion command message (PDU session release command message) for the PDU session established by this procedure. Does not include.
- the UE may store the identification information received with the PDU session establishment acceptance message and / or the PDU session establishment rejection message based on the completion of the PDU session establishment procedure, or may recognize the network decision. Good.
- the UE may recognize and remember that the established PDU session is an established PDU session via the NPN based on the receipt of the 51st identification information.
- the UE may recognize and remember that the authentication / approval procedure for the NPN via the established PDU session has been completed based on the reception of the 52nd identification information.
- the UE may store the received identification information, or may execute each procedure after this procedure based on the recognition of the network decision.
- the UE recognizes and remembers that the authentication / approval procedure for the NPN has been completed, or if it wants to establish a PDU session establishment request message via (or to the NPN) the same NPN, No need to require additional certification / approval procedures.
- This procedure is a procedure for the core network to update the UE setting information.
- This procedure may be a procedure for mobility management that the network takes the initiative to execute for the UE registered in the network.
- devices in the core network such as AMF may start this procedure based on the update of network settings and / or the update of operator policy.
- the trigger of this procedure may be the detection of the mobility of the UE, the detection of the state change of the UE and / or the access network and / or the core network, or the state change of the network slice. It may be. Further, the trigger of this procedure may be the reception of a request from the DN and / or the DN application server, a change in network settings, or a change in operator policy. .. Further, the trigger of this procedure may be the expiration of the timer being executed.
- the triggers for the devices in the core network to start this procedure are not limited to these.
- this procedure may be executed at any time after the above-mentioned registration procedure and / or PDU session establishment procedure is completed. Further, this procedure may be executed at any timing as long as each device has established a 5GMM context and / or each device is in the 5GMM connection mode.
- the trigger of this procedure may be a change of state of the UE managed by the network, specifically, even if there is a change in the list of NPNs that the UE is allowed to connect to with high priority. Good.
- the state change of the UE managed by the network may be executed based on the request from the application.
- each device sends and receives a message containing identification information for changing the setting information of the UE and / or identification information for stopping or changing the function executed by the UE during this procedure. May be good. Further, each device may update the setting information to the setting instructed by the network based on the completion of this procedure, or may start the behavior instructed by the network.
- the UE may update the setting information of the UE based on the control information transmitted and received by this procedure. Further, the UE may stop the function being executed or start a new function as the setting information of the UE is updated. In other words, the device in the core network leads this procedure, and further, by transmitting the control message and control information of this procedure to the UE, the setting information of the UE that can be identified by using these control information can be obtained. , UE may update. Further, the device in the core network may stop the function executed by the UE or cause the UE to start a new function by updating the setting information of the UE.
- AMF starts the UE setting update procedure by sending a configuration update command message to the UE via 5GAN (or gNB) (S900).
- AMF may send the setting update command message including at least the 71st identification information.
- the AMF may indicate the new UE setting information by transmitting the 71st identification information, or may request the update of the UE setting 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.
- AMF will include at least the 71st identification information in the configuration update command message for each received identification information and / or subscriber information and / or network capability information and / or operator policy and /. Alternatively, it may be selected and determined based on the state of the network and / or the user's registration information and / or the context held by the AMF.
- AMF also receives each identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user registration information and / or A request for updating the setting information of the UE may be indicated by sending a setting update command message based on the context held by the AMF.
- the UE receives the setting update command message via 5GAN (gNB) (S900).
- the UE may update the UE configuration information based on the configuration update command message and / or the identification information contained in the configuration update command message.
- the UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the 71st identification information.
- the high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority.
- the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list.
- the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority.
- Allowed NSSAI or Configured NSSAI or rejected NSSAI even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.
- each process that the UE shown above executes based on the reception of each identification information may be executed during 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.
- the UE sends a configuration update complete message to the AMF via 5GAN (gNB) as a response message to the configuration update command message based on the identification information contained in the configuration update command message. May (S902).
- AMF receives the setting update completion message via 5GAN (gNB) when the UE sends the setting update completion command message (S902).
- each device completes this procedure based on the transmission / reception of the setting update command message and / or the setting update completion message.
- each device may perform processing based on the information transmitted and received in this procedure based on the completion of this procedure. For example, when the update information for the setting information is transmitted and received, each device may update the setting information. Furthermore, if the UE sends and receives information indicating that the registration procedure needs to be performed, the UE may start the registration procedure based on the completion of this procedure.
- the UE may store the identification information received together with the setting information command message based on the completion of this procedure, or may recognize the network decision.
- the UE may recognize and remember one or more NPNs that the UE is allowed to connect to at a higher priority based on the completion of this procedure and / or the receipt of the 71st Identification Information. You may.
- the UE may perform registration procedures, and / or service request procedures, and / or PDU session establishment request procedures, and / or PDU session establishment request procedures, based on the information of one or more NPNs in which the stored UE is allowed to connect with high priority. / Or the PDU session change procedure may be performed.
- the UE establishes a registration request message, a service request message, and / or a PDU session, which includes information indicating an NPN to which the UE is allowed to connect with a high priority based on the reception of the 71st identification information.
- Each procedure may be started by sending a request message and / or a PDU session modification request message (PDU session modification request message).
- each procedure may be executed based on the stored information.
- a message and / or a PDU session establishment request message and / or a PDU session change request message (PDU session modification request message) can be transmitted.
- the device in the core network can instruct the UE to update the setting information that the UE has already applied, and the UE is executing it. You can instruct to stop or change the function.
- the first embodiment will be described.
- the first embodiment will be referred to as the present embodiment.
- an embodiment in which each device completes registration for the NPN requested by the UE even when the AMF is in congestion control or the UE is counting in the backoff timer will be described. ..
- the initial state of the communication procedure of the present embodiment may be a state in which the AMF detects a congestion state at the NAS level and starts congestion control.
- the first registration procedure may be the registration procedure in Chapter 3.2.
- the UE sends the AMF a first registration request message containing at least one of the first to fourth identifications. In other words, it receives a first registration request message that includes at least one of the first to fourth identifications.
- the UE completes the first registration procedure by receiving a registration refusal message containing at least one of the 21st to 22nd identification information from the AMF.
- the AMF completes the first registration procedure by sending a registration refusal message containing at least one of the 21st to 22nd identification information.
- AMF may include information indicating congestion as a reason value in the registration refusal message.
- the AMF may include the value of the backoff timer in the registration refusal message, or may not include the value of the backoff timer based on the UE information.
- the UE Based on the completion of the first registration procedure and the receipt of the 21st to 22nd identification information, the UE recognizes and remembers that the UE is a UE that is allowed to connect with high priority within the NPN requested by the UE. You may. Furthermore, based on the receipt of the reason value for rejection, the UE recognizes that it has been rejected by AMF for reasons of congestion. Further, the UE may start or execute counting of the backoff timer based on the reception of the value of the backoff timer. Alternatively, the UE may receive the value of the backoff timer or not start counting the backoff timer based on the stored information of the UE.
- the UE may start the second registration procedure even while the backoff timer is counting, based on the stored information of the UE.
- the second registration procedure may be the registration procedure in Chapter 3.2.
- the UE sends the AMF a first registration request message containing at least one of the first to fourth identifications. In other words, it receives a first registration request message that includes at least one of the first to fourth identifications.
- the UE completes the second registration procedure by receiving a registration acceptance message containing at least one of the 11th to 15th identification information from the AMF.
- the AMF completes the second registration process by sending a registration acceptance message containing at least one of the 11th to 15th identifications.
- each device completes the UE registration procedure for the NPN required by the UE even if the AMF is in congestion control.
- completing the UE registration procedure for the NPN requested by the UE may mean transitioning to the registration state for the NPN requested by the UE, or the NPN required by the UE. You may transition to a state where the establishment of a PDU session via (or to the NPN) is allowed.
- each device by executing the first registration procedure and the second registration procedure, each device registers with respect to the NPN requested by the UE even when the AMF is in congestion control.
- each device is not limited to the method of completing the registration for the NPN requested by the UE even when the AMF is in congestion control.
- each device may complete registration for the NPN requested by the UE, even if the AMF is in congestion control, with only a second registration procedure.
- each device after the completion of the second registration procedure, each device performs the service request procedure in Chapter 3.3 and / or the PDU session establishment procedure in Chapter 3.4, and / or the UE in Chapter 3.5 at any time. You may start the setting update procedure.
- each device is allowed to connect with high priority within the NPN, even if the AMF and / or SMF is in congestion control or the UE is counting in the backoff timer.
- the PDU session establishment procedure is executed based on the above.
- the initial state is that each device has completed registration with the NPN.
- Each device may, or is not limited to, transitioned to the initial state according to the first embodiment.
- AMF and / or SMF detects a DNN-based and / or S-NSSAI-based congestion state, and is a DNN-based and / or S-NSSAI-based congestion control state.
- each device executes the first PDU session establishment procedure started from the UE.
- the first PDU session establishment procedure may be the PDU session establishment procedure in Chapter 3.4.
- the UE sends a first PDU session establishment request containing at least one of the 41st to 42nd identification information to the AMF and / or SMF.
- the AMF and / or SMF receives a first PDU session establishment request from the UE that includes at least one of the 41st to 42nd identifiers.
- the UE subsequently receives a PDU session establishment refusal message from the AMF and / or SMF containing at least one of the 61st to 62nd identification information.
- the AMF and / or SMF sends a PDU session establishment refusal message to the UE that contains at least one of the 61st to 62nd identifications.
- AMF and / or SMF may include information indicating congestion as a reason value in the PDU session establishment refusal message. Further, the AMF and / or SMF may include the value of the backoff timer in the registration refusal message, or may not include the value of the backoff timer based on the information of the UE.
- the UE Based on the completion of the first registration procedure and the receipt of the identification information of 41st to 42nd, the UE recognizes and remembers that the UE is a UE that is allowed to connect with a high priority within the NPN requested by the UE. You may. In addition, upon receipt of the reason for refusal value, the UE recognizes that the request has been rejected by the AMF and / or SMF for reasons of congestion. Further, the UE may start or execute counting of the backoff timer based on the reception of the value of the backoff timer. Alternatively, the UE may receive the value of the backoff timer or not start counting the backoff timer based on the stored information of the UE.
- the UE may start the second PDU session establishment procedure even while the backoff timer is counting, based on the stored information of the UE.
- the second PDU session establishment procedure may be the PDU session establishment procedure in Chapter 3.4.
- the UE sends a second PDU session establishment request containing at least one of the 41st to 42nd identification information to the AMF and / or SMF.
- the AMF and / or SMF receives a second PDU session establishment request from the UE that contains at least one of the 41st to 42nd identifiers.
- the UE subsequently receives a PDU session establishment acceptance message from AMF and / or SMF containing at least one of the 51st to 52nd identification information.
- the AMF and / or SMF sends a PDU session establishment acceptance message to the UE that contains at least one of the 51st to 52nd identifications.
- each device can have a PDU session (to NPN) via NPN requested by UE even if AMF and / or SMF is in DNN-based and / or S-NSSAI-based congestion control. Can be established.
- each device can manage the UE as a UE that is allowed to connect with a high priority within the NPN, and the PDU via (or to the NPN) the NPN that the UE is allowed to connect to with a high priority.
- session-related procedures PDU session change procedure and / or PDU session release procedure
- AMF and / SMF do not send a backoff timer to the UE.
- each device can perform the UE even if the AMF and / or the SMF is in congestion control.
- a PDU session (to the NPN) via the NPN requested by the UE requested by the UE has completed the establishment, but each device is requested by the UE requested by the UE even if the AMF and / or SMF is in congestion control. This is not the only way a PDU session (to an NPN) through an NPN can complete its establishment.
- each device only has a second PDU session establishment procedure, and even if the AMF and / or SMF is in congestion control, a PDU session (to the NPN) via the NPN requested by the UE requested by the UE is established. May be completed.
- each device after the second PDU session establishment procedure, each device performs the PUD session change procedure and / or the PUD session release procedure and / or the UE setting update procedure in Chapter 3.5 at an arbitrary timing. You may start.
- the AMF and / or SMF sends the backoff timer value to the UE based on the UE information. You don't have to.
- each device is a PDU session when the UE is stored in the network as a UE that is allowed to connect with a high priority in the NPN even when the AMF and / or SMF is in congestion control.
- the change procedure will be explained.
- the initial state of this procedure is that at least one PDU session has been established via (or to) the NPN.
- the SMF remembers that the UE is a high priority UE allowed to connect within the NPN.
- each device may have transitioned to the initial state according to, for example, the second embodiment, and the method of transitioning to the initial state of each device is not limited to this.
- the AMF and / or SMF detects a DNN-based and / or S-NSSAI-based congestion state, and is a DNN-based and / or S-NSSAI-based congestion control state.
- each device starts the PDU session modification procedure (PDU session modification procedure).
- the PDU session change procedure is a procedure for changing an established PDU session under the initiative of the UE or the network, and is a PDU session change request message (PDU Session modification request message) sent from the UE to the SMF. ), And a PDU session modification rejection message (PDU session modification reject message) sent from the SMF to the UE, or a PDU session modification procedure started from the SMF.
- PDU Session modification request message PDU Session modification request message
- PDU session modification reject message sent from the SMF to the UE, or a PDU session modification procedure started from the SMF.
- the PDU session change procedure started from SMF is a PDU session change command message (PDU session modification command message) sent from SMF to UE and a PDU session change completion message (PDU session modification complete message) sent from UE to SMF. ).
- PDU session modification command message PDU session modification command message
- PDU session change completion message PDU session modification complete message
- the SMF sends a PDU session change command message to the UE within the PDU session change procedure.
- the SMF does not include the value of the backoff timer in the PDU session change command message based on the fact that the UE is a UE that is allowed to connect with high priority in the NPN.
- the UE sends a PDU session change completion message based on receiving a PDU session change command message that does not include the backoff timer value from the SMF, and completes the PDU session change procedure.
- the device is congested. Execute the PDU session change procedure without doing.
- each device may start the PUD session change procedure and / or the PUD session release procedure and / or the UE setting update procedure in Chapter 3.5 at any timing.
- each device releases a PDU session when the UE is stored in the network as a UE that is allowed to connect with a high priority in the NPN even when the AMF and / or SMF is in congestion control. The procedure will be explained.
- the initial state of this procedure is that at least one PDU session has been established via (or to) the NPN.
- the SMF remembers that the UE is a high priority UE allowed to connect within the NPN.
- each device may have transitioned to the initial state according to, for example, the second embodiment, and the method of transitioning to the initial state of each device is not limited to this.
- the AMF and / or SMF detects a DNN-based and / or S-NSSAI-based congestion state, and is a DNN-based and / or S-NSSAI-based congestion control state.
- the PDU session release procedure is a procedure for deleting an established PDU session.
- the PDU session release procedure has a network-led procedure and a UE-led procedure, but in the present embodiment, it means a network-led procedure.
- the network-led PDU session release procedure is based on the PDU session release command message (PDU Session release command message) sent from the SMF to the UE and the PDU session release completion message (PDU session release complete message) sent from the UE to the SMF. It is composed.
- the SMF sends a PDU session release command message within the PDU session release procedure.
- the SMF does not include the value of the backoff timer in the PDU session release command message based on the fact that the UE is a UE that is allowed to connect with high priority in the NPN.
- the UE sends a PDU session release completion message based on receiving a PDU session release command message that does not include the backoff timer value from the SMF, and completes the PDU session release procedure.
- the device is congested. Execute the PDU session change procedure without doing.
- each device may start the PUD session change procedure and / or the PUD session release procedure and / or the UE setting update procedure in Chapter 3.5 at any timing.
- the program that operates in the apparatus according to the present invention may be a program that controls the Central Processing Unit (CPU) or the like to operate the 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 a volatile memory such as Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or another storage device system.
- RAM Random Access Memory
- HDD Hard Disk Drive
- the program for realizing the function of the embodiment according to 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 "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 in an electric circuit, for example, an integrated circuit or a plurality of integrated circuits.
- Electrical circuits designed to perform the functions described herein are 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 a combination thereof may be included.
- 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 use a new integrated circuit according to the technology.
- the invention of the present application is not limited to the above-described embodiment.
- an example of the device has been described, but the present invention is not limited to this, and the present invention is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device or a kitchen device. , 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)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
An embodiment of the present invention provides a communication means for implementing a Vertical LAN and a Non-Public Network (NPN) for 5GS. Provided are UE registration and session establishing procedures and a communication means for implementing a Vertical LAN and a Non-Public Network (NPN) for 5GS. Further provided are: a procedure for modifying the setting of a UE registered in a network; a procedure for managing an established session on the basis of information about a UE which is registered, stored, or set in a network; a procedure for deleting an established session; and a communication means.
Description
本出願は、ユーザ装置、制御装置、及び通信制御方法に関する。本出願は、2019年4月1日に出願された日本国特許出願である特願2019-70073号に対して優先権の利益を主張するものであり、それを参照することにより、その内容の全てが本願に含まれる。
This application relates to a user device, a control device, and a communication control method. This application claims the benefit of priority to Japanese Patent Application No. 2019-70073, which is a Japanese patent application filed on April 1, 2019, and by referring to it, the content of the application is claimed. All are included in this application.
近年の移動通信システムの標準化活動を行う3GPP(3rd Generation Partnership Project)は、LTE(Long Term Evolution)のシステムアーキテクチャであるSAE(System Architecture Evolution)の検討を行っている。
3GPP (3rd Generation Partnership Project), which is engaged in standardization activities for mobile communication systems in recent years, is studying SAE (System Architecture Evolution), which is the system architecture of LTE (Long Term Evolution).
また、近年3GPPでは、次世代移動通信システムである5G (5th Generation) 移動通信システムの次世代通信技術やシステムアーキテクチャの検討も行っており、特に、5G移動通信システムを実現するシステムとして、5GS(5G System)の仕様化を行っている(非特許文献1、及び非特許文献2参照)。5GSでは、多種多様な端末をセルラーネットワークに接続する為の技術課題を抽出し、解決策を仕様化している。
In recent years, 3GPP has also been studying the next-generation communication technology and system architecture of 5G (5th Generation) mobile communication systems, which are next-generation mobile communication systems. In particular, 5GS (5G) is a system that realizes 5G mobile communication systems. 5G System) is being specified (see Non-Patent Document 1 and Non-Patent Document 2). 5GS extracts technical issues for connecting a wide variety of terminals to cellular networks and specifies solutions.
5GS(5G System)では、多種多様なサービスを提供するために、新たなコアネットワークである5GCN(5G Core Network)が検討されている。さらに、5GSでは新たな機能として、Vertical LANの検討がされている。
In 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered in order to provide a wide variety of services. In addition, 5GS is considering Vertical LAN as a new function.
更に、Vertical LANのキーアイテムとして、NPN(Non-public network)のサポートの検討が行われている。NPNは、一般利用を目的とせず、企業など私的利用などを目的とした非公開ネットワークである。また、NPNは特定の利用者が特定の目的で利用する非公開ネットワークである。
Furthermore, support for NPN (Non-public network) is being considered as a key item for Vertical LAN. NPN is a private network that is not intended for general use but for private use by companies. NPN is a private network used by specific users for specific purposes.
NPNにはStand-alone Non-Public Network (SNPN)とPublic network integrated NPNの2種類が検討されている。3GPPでは、Public network integrated NPNは、ネットワークスライスの機能を用いてNPNをサポートすることが仕様化されている。
Two types of NPN are being considered: Stand-alone Non-Public Network (SNPN) and Public network integrated NPN. In 3GPP, it is specified that Public network integrated NPN supports NPN by using the function of network slice.
また、現在5GSでは、PLMN(Public Land Mobile Network)内で高い優先度で接続するUEとして設定されるUE(UE configured for high priority access in selected PLMN)が存在する。PLMN内で高い優先度で接続するUEとして設定されるUEの識別方法は、UE及びコアネットワーク内装置の各装置が記憶する、1又は複数のアクセス識別情報に基づき識別される。
Also, in 5GS, there is a UE (UE configured for high priority access in selected PLMN) that is set as a UE that connects with high priority in PLMN (Public Land Mobile Network). The UE identification method set as the UE to connect with high priority in PLMN is identified based on one or more access identification information stored in each device of the UE and the device in the core network.
しかし、NPN内で高い優先度で接続するUEとして設定されるUEをサポートするための具体的な手段や方法は明確になっていない。
However, the specific means and method for supporting UEs set as UEs that connect with high priority in NPN have not been clarified.
本発明は、以上のような事情を鑑みてなされたものであり、その目的は、5GSにおけるNPNのための機能の実現方法を提供することである。
The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a method for realizing a function for NPN in 5GS.
本発明の一実施形態のユーザ装置は、NPN (Non Public Network)に接続可能なユーザ装置であって、第1の情報を記憶する記憶部と、NPNから、バックオフタイマの値を受信し、第1の情報に基づき、前記バックオフタイマが実行されている間に、要求メッセージを送信する、送受信部と、を備え、第1の情報は、前記ユーザ装置が前記NPN内で高い優先度で接続可能であることを示す情報であり、NPNはネットワークスライスである、ことを特徴とする。
The user device according to the embodiment of the present invention is a user device that can be connected to an NPN (Non Public Network), and receives the value of the backoff timer from the storage unit that stores the first information and the NPN. Based on the first information, the back-off timer is provided with a transmitter / receiver for transmitting a request message while the backoff timer is being executed, and the first information has a high priority within the NPN by the user device. It is information indicating that the connection is possible, and the NPN is a network slice.
本発明の一実施形態の制御装置は、NPN(Non Public Network)として作成されたネットワークスライスを含む、PLMN(Public land mobile network)内の制御装置であって、第1の識別情報を記憶する記憶部と、輻輳を検知する制御部と、ユーザ装置から要求メッセージを受信し、第1の識別情報に基づき、検知をしている状態であっても、要求メッセージの応答として、輻輳を示す理由値を含む拒絶メッセージを送信しない、送受信部、とを備える、ことを特徴とする。
The control device according to the embodiment of the present invention is a control device in PLMN (Public land mobile network) including a network slice created as an NPN (Non Public Network), and is a memory for storing the first identification information. A reason value that indicates congestion as a response to the request message even if the request message is received from the unit, the control unit that detects congestion, and the user device is performing detection based on the first identification information. It is characterized in that it does not transmit a rejection message including, and includes a transmission / reception unit.
本発明の一実施形態の制御装置は、Non Public Network(NPN)として作成されたネットワークスライスを含む、PLMN内の制御装置であって、NPN内で高い優先度で接続可能なユーザ装置に、バックオフタイマを含めないPDU (Protocol Data Unit又はPacket Data Unit)セッション削除コマンドメッセージ又はPDUセッション確立拒絶メッセージ又はPDUセッション変更拒絶メッセージを送信する、送受信部を備える、ことを特徴とする。
The control device of the embodiment of the present invention is a control device in the PLMN including a network slice created as a Non Public Network (NPN), and is backed to a user device that can be connected with a high priority in the NPN. It is characterized by having a transmission / reception unit for transmitting a PDU (Protocol Data Unit or Packet Data Unit) session deletion command message or a PDU session establishment rejection message or a PDU session change rejection message that does not include an off-timer.
本発明の一態様によれば、5GSにおいて、NPNのサポートが可能となり、更にNPN内で高い優先度で接続するUEをサポートするための、UEの登録、セッションの確立、セッションのマネジメント、UEの設定の変更/更新が可能となる。
According to one aspect of the present invention, in 5GS, NPN support is possible, and UE registration, session establishment, session management, and UE support for UEs that connect with high priority within the NPN. Settings can be changed / updated.
以下、図面を参照して本発明を実施する為に最良の形態について説明する。尚、本実施形態では1例として、本発明を適用した場合の移動通信システムの実施形態について説明する。
Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings. In this embodiment, an embodiment of a mobile communication system to which the present invention is applied will be described as an example.
[1. システムの概要]
まず、図1は、各実施形態で使用される移動通信システム1の概略を説明する為の図であり、図2は、その移動通信システム1の詳細構成を説明する為の図である。 [1. System overview]
First, FIG. 1 is a diagram for explaining the outline of themobile communication system 1 used in each embodiment, and FIG. 2 is a diagram for explaining a detailed configuration of the mobile communication system 1.
まず、図1は、各実施形態で使用される移動通信システム1の概略を説明する為の図であり、図2は、その移動通信システム1の詳細構成を説明する為の図である。 [1. System overview]
First, FIG. 1 is a diagram for explaining the outline of the
図1には、移動通信システム1は、UE_A10、アクセスネットワーク_A80、コアネットワーク_A90、PDN(Packet Data Network)_A5、アクセスネットワーク_B120、コアネットワーク_B190、DN(Data Network)_A6により構成されることが記載されている。
In FIG. 1, the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network) _A5, access network _B120, core network _B190, and DN (Data Network) _A6. It is stated that
以下では、これらの装置・機能について、UE、アクセスネットワーク_A、コアネットワーク_A、PDN、アクセスネットワーク_B、コアネットワーク_B、DN等のように、記号を省略して記載する場合がある。
In the following, these devices / functions may be described by omitting symbols such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc. ..
また、図2には、UE_A10、E-UTRAN80、MME40、SGW35、PGW-U30、PGW-C32、PCRF60、HSS50、5G AN120、AMF140、UPF130、SMF132、PCF160、UDM150等の装置・機能、及びこれらの装置・機能を互いに接続するインターフェースが記載されている。
In addition, Fig. 2 shows the devices / functions of UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, etc. Interfaces that connect devices and functions to each other are described.
以下では、これらの装置・機能について、UE、E-UTRAN、MME、SGW、PGW-U、PGW-C、PCRF、HSS、5G AN、AMF、UPF、SMF、PCF、UDM等のように、記号を省略して記載する場合がある。
In the following, these devices / functions are referred to as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5GAN, AMF, UPF, SMF, PCF, UDM, etc. May be omitted.
尚、4GシステムであるEPS(Evolved Packet System)は、アクセスネットワーク_A及びコアネットワーク_Aを含んで構成されるが、さらにUE及び/又はPDNが含まれても良い。また、5Gシステムである5GS(5G System)は、UE、アクセスネットワーク_B及びコアネットワーク_Bを含んで構成されるが、さらにDNが含まれても良い。
The EPS (Evolved Packet System), which is a 4G system, is configured to include the access network_A and the core network_A, but may further include the UE and / or PDN. Further, 5GS (5G System), which is a 5G system, is configured to include a UE, an access network_B, and a core network_B, but may further include a DN.
UEは、3GPPアクセス(3GPPアクセスネットワーク、3GPP ANとも称する)及び/又はnon-3GPPアクセス(non-3GPPアクセスネットワーク、non-3GPP ANとも称する)を介して、ネットワークサービスに対して接続可能な装置である。UEは、携帯電話やスマートフォン等の無線通信が可能な端末装置であってよく、EPSにも5GSにも接続可能な端末装置であってよい。UEは、UICC(Universal Integrated Circuit Card)やeUICC(Embedded UICC)を備えてもよい。尚、UEのことをユーザ装置と表現してもよいし、端末装置と表現してもよい。
UE is a device that can connect to network services via 3GPP access (3GPP access network, also called 3GPP AN) and / or non-3GPP access (non-3GPP access network, also called non-3GPP AN). is there. 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 provided with UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). The UE may be expressed as a user device or a terminal device.
また、アクセスネットワーク_Aは、E-UTRAN(Evolved Universal Terrestrial Radio Access Network)及び/又は無線LANアクセスネットワークに対応する。E-UTRANには、1以上のeNB(evolved Node B)45が配置される。尚、以下では、eNB45は、eNBのように記号を省略して記載する場合がある。また、複数のeNBがある場合は、各eNBは、例えばX2インターフェースにより、互いに接続されている。また、無線LANアクセスネットワークには、1以上のアクセスポイントが配置される。
In addition, the access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or wireless LAN access network. One or more eNB (evolved Node B) 45 are arranged in E-UTRAN. In the following, eNB45 may be described by omitting a symbol like eNB. When there are a plurality of eNBs, each eNB is connected to each other by, for example, an X2 interface. In addition, one or more access points are arranged in the wireless LAN access network.
また、アクセスネットワーク_Bは、5Gアクセスネットワーク(5G AN)に対応する。5G ANは、NG-RAN(NG Radio Access Network)及び/又はnon-3GPP アクセスネットワークで構成される。NG-RANには、1以上のgNB(NR NodeB)122が配置される。尚、以下では、gNB122は、eNBのように記号を省略して記載する場合がある。gNBは、NR(New Radio)ユーザプレーンと制御プレーンをUEに提供するノードであり、5GCNに対してNGインターフェース(N2インターフェース又はN3インターフェースを含む)を介して接続するノードである。すなわち、gNBは、5GSのために新たに設計された基地局装置であり、4GシステムであるEPSで使用されていた基地局装置(eNB)とは異なる機能を有する。また、複数のgNBがある場合は、各gNBは、例えばXnインターフェースにより、互いに接続している。
In addition, access network_B corresponds to 5G access network (5G AN). 5GAN is composed of NG-RAN (NG Radio Access Network) and / or non-3GPP access network. One or more gNB (NR Node B) 122 is arranged in NG-RAN. In the following, gNB122 may be described by omitting symbols such as eNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node that connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). That is, gNB is a base station device newly designed for 5GS and has a function different from that of the base station device (eNB) used in EPS, which is a 4G system. When there are a plurality of gNBs, each gNB is connected to each other by, for example, an Xn interface.
また、以下では、E-UTRANやNG-RANは、3GPPアクセスと称することがある。また、無線LANアクセスネットワークやnon-3GPP ANは、non-3GPPアクセスと称することがある。また、アクセスネットワーク_Bに配置されるノードを、まとめてNG-RANノードとも称することがある。
In the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. In addition, wireless LAN access network and non-3GPP AN may be referred to as non-3GPP access. In addition, the nodes located in the access network_B may be collectively referred to as NG-RAN nodes.
また、以下では、アクセスネットワーク_A、及び/又はアクセスネットワーク_B、及び/又はアクセスネットワーク_Aに含まれる装置、及び/又はアクセスネットワーク_Bに含まれる装置は、アクセスネットワーク、又はアクセスネットワーク装置と称する場合がある。
In the following, the devices included in the access network_A and / or the access network_B and / or the access network_A, and / or the devices included in the access network_B are the access network or the access network device. It may be called.
また、コアネットワーク_Aは、EPC(Evolved Packet Core)に対応する。EPCには、例えば、MME(Mobility Management Entity)、SGW(Serving Gateway)、PGW(Packet Data Network Gateway)-U、PGW-C、PCRF(Policy and Charging Rules Function)、HSS(Home Subscriber Server)等が配置される。
In addition, core network_A corresponds to EPC (Evolved Packet Core). EPC includes, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway) -U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc. Be placed.
また、コアネットワーク_Bは、5GCN(5G Core Network)に対応する。5GCNには、例えば、AMF(Access and Mobility Management Function)、UPF(User Plane Function)、SMF(Session Management Function)、PCF(Policy Control Function)、UDM(Unified Data Management)等が配置される。ここで、5GCNは、5GCと表現されてもよい。
In addition, core network_B corresponds to 5GCN (5G Core Network). For example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), UDM (Unified Data Management), etc. are arranged in 5GCN. Here, 5GCN may be expressed as 5GC.
また、以下では、コアネットワーク_A、及び/又はコアネットワーク_B、コアネットワーク_Aに含まれる装置、及び/又はコアネットワーク_Bに含まれる装置は、コアネットワーク、又はコアネットワーク装置と称する場合がある。
In the following, the core network_A and / or the core network_B, the device included in the core network_A, and / or the device included in the core network_B are referred to as a core network or a core network device. There is.
コアネットワーク(コアネットワーク_A及び/又はコアネットワーク_B)は、アクセスネットワーク(アクセスネットワーク_A及び/又はアクセスネットワーク_B)と、PDN及び/又はDNとを接続した移動体通信事業者(Mobile Network Operator; MNO)が運用するIP移動通信ネットワークの事であってもよいし、移動通信システム1を運用、管理する移動体通信事業者の為のコアネットワークでもよいし、MVNO(Mobile Virtual Network Operator)、MVNE(Mobile Virtual Network Enabler)等の仮想移動通信事業者や仮想移動体通信サービス提供者の為のコアネットワークでもよい。
The core network (core network_A and / or core network_B) is a mobile network operator (Mobile) that connects the access network (access network_A and / or access network_B) with the PDN and / or DN. It may be an IP mobile communication network operated by Network Operator; MNO), it may be a core network for a mobile communication operator that operates and manages mobile communication system 1, or it may be an MVNO (Mobile Virtual Network Operator). ), MVNE (Mobile Virtual Network Enabler), etc. may be a core network for virtual mobile communication operators and virtual mobile communication service providers.
また、図1では、PDNとDNが同一である場合が記載されているが、異なっていても良い。PDNは、UEに通信サービスを提供するDN(Data Network)であってよい。尚、DNは、パケットデータサービス網として構成されてもよいし、サービス毎に構成されてもよい。さらに、PDNは、接続された通信端末を含んでもよい。従って、PDNと接続する事は、PDNに配置された通信端末やサーバ装置と接続する事であってもよい。さらに、PDNとの間でユーザデータを送受信する事は、PDNに配置された通信端末やサーバ装置とユーザデータを送受信する事であってもよい。尚、PDNのことをDNと表現してもよいし、DNのことをPDNと表現してもよい。
Also, in Fig. 1, the case where PDN and DN are the same is described, but they may be different. The PDN may be a DN (Data Network) that provides a communication service to the UE. The DN may be configured as a packet data service network or may be configured for each service. Further, the PDN may include a connected communication terminal. Therefore, connecting to the PDN may be connecting to a communication terminal or server device arranged in the PDN. Further, sending and receiving user data to and from the PDN may be sending and receiving user data to and from a communication terminal or server device arranged in the PDN. In addition, PDN may be expressed as DN, and DN may be expressed as PDN.
また、以下では、アクセスネットワーク_A、コアネットワーク_A、PDN、アクセスネットワーク_B、コアネットワーク_B、DNの少なくとも一部、及び/又はこれらに含まれる1以上の装置を、ネットワーク又はネットワーク装置と呼称する場合がある。つまり、ネットワーク及び/又はネットワーク装置が、メッセージを送受信する、及び/又は手続きを実行するということは、アクセスネットワーク_A、コアネットワーク_A、PDN、アクセスネットワーク_B、コアネットワーク_B、DNの少なくとも一部、及び/又はこれらに含まれる1以上の装置が、メッセージを送受信する、及び/又は手続きを実行することを意味する。
In addition, in the following, at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included in these are referred to as a network or network device. It 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 It means that at least a part and / or one or more devices included therein send and receive messages and / or perform procedures.
また、UEは、アクセスネットワークに接続することができる。また、UEは、アクセスネットワークを介して、コアネットワークと接続する事ができる。さらに、UEは、アクセスネットワーク及びコアネットワークを介して、PDN又はDNに接続する事ができる。すなわち、UEは、PDN又はDNとの間で、ユーザデータを送受信(通信)する事ができる。ユーザデータを送受信する際は、IP(Internet Protocol)通信だけでなく、non-IP通信を用いてもよい。
Also, the UE can connect to the access network. The UE can also connect to the core network via the access network. In addition, the UE can connect to the PDN or DN via the access network and core network. That is, the UE can send and receive (communicate) user data with the PDN or DN. When sending and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication may be used.
ここで、IP通信とは、IPを用いたデータ通信の事であり、IPパケットにより、データの送受信が行われる。IPパケットは、IPヘッダとペイロード部で構成される。ペイロード部には、EPSに含まれる装置・機能や、5GSに含まれる装置・機能が送受信するデータが含まれてよい。また、non-IP通信とは、IPを用いないデータ通信の事であり、IPパケットの構造とは異なる形式により、データの送受信が行われる。例えば、non-IP通信は、IPヘッダが付与されていないアプリケーションデータの送受信によって実現されるデータ通信でもよいし、マックヘッダやEthernet(登録商標)フレームヘッダ等の別のヘッダを付与してUEが送受信するユーザデータを送受信してもよい。
Here, IP communication is data communication using IP, and data is transmitted and received by IP packets. An IP packet is composed of an IP header and a payload part. The payload section may include devices / functions included in EPS and data transmitted / received by devices / functions included in 5GS. In addition, non-IP communication is data communication that does not use IP, and data is transmitted and received in a format different from the structure of IP packets. For example, non-IP communication may be data communication realized by sending and receiving application data to which an IP header is not added, or a UE can 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.
[2. 各装置の構成]
次に、各実施形態で使用される各装置(UE、及び/又はアクセスネットワーク装置、及び/又はコアネットワーク装置)の構成について、図を用いて説明する。尚、各装置は、物理的なハードウェアとして構成されても良いし、汎用的なハードウェア上に構成された論理的な(仮想的な)ハードウェアとして構成されても良いし、ソフトウェアとして構成されても良い。また、各装置の持つ機能の少なくとも一部(全部を含む)が、物理的なハードウェア、論理的なハードウェア、ソフトウェアとして構成されても良い。 [2. Configuration of each device]
Next, the configuration of each device (UE and / or access network device and / or core network device) used in each embodiment will be described with reference to the drawings. Each device may be configured as physical hardware, may be configured as logical (virtual) hardware configured on general-purpose hardware, or may be configured as software. May be done. Further, at least a part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.
次に、各実施形態で使用される各装置(UE、及び/又はアクセスネットワーク装置、及び/又はコアネットワーク装置)の構成について、図を用いて説明する。尚、各装置は、物理的なハードウェアとして構成されても良いし、汎用的なハードウェア上に構成された論理的な(仮想的な)ハードウェアとして構成されても良いし、ソフトウェアとして構成されても良い。また、各装置の持つ機能の少なくとも一部(全部を含む)が、物理的なハードウェア、論理的なハードウェア、ソフトウェアとして構成されても良い。 [2. Configuration of each device]
Next, the configuration of each device (UE and / or access network device and / or core network device) used in each embodiment will be described with reference to the drawings. Each device may be configured as physical hardware, may be configured as logical (virtual) hardware configured on general-purpose hardware, or may be configured as software. May be done. Further, at least a part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.
尚、以下で登場する各装置・機能内の各記憶部(記憶部_A340、記憶部_A440、記憶部_B540、記憶部_A640、記憶部_B740)は、例えば、半導体メモリ、SSD(Solid State Drive)、HDD(Hard Disk Drive)等で構成されている。また、各記憶部は、出荷段階からもともと設定されていた情報だけでなく、自装置・機能以外の装置・機能(例えば、UE、及び/又はアクセスネットワーク装置、及び/又はコアネットワーク装置、及び/又はPDN、及び/又はDN)との間で、送受信した各種の情報を記憶する事ができる。また、各記憶部は、後述する各種の通信手続き内で送受信する制御メッセージに含まれる識別情報、制御情報、フラグ、パラメータ等を記憶することができる。また、各記憶部は、これらの情報をUE毎に記憶してもよい。また、各記憶部は、5GSとEPSとの間のインターワークをした場合には、5GS及び/又はEPS内に含まれる装置・機能との間で送受信した制御メッセージやユーザデータを記憶することができる。このとき、N26インターフェースを介して送受信されたものだけでなく、N26インターフェースを介さずに送受信されたものも記憶することができる。
In addition, each storage unit (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) in each device / function appearing below is, for example, a semiconductor memory, SSD ( It is composed of Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each storage unit has not only the information originally set from the shipping stage, but also devices / functions other than its own device / function (for example, UE and / or access network device, and / or core network device, and / Or PDN and / or DN), various information sent and received can be stored. In addition, each storage unit can store identification information, control information, flags, parameters, and the like included in control messages transmitted and received in various communication procedures described later. Further, each storage unit may store such information for each UE. In addition, each storage unit can store control messages and user data sent and received between 5GS and / or devices / functions included in EPS when interwork is performed between 5GS and EPS. it can. At this time, not only those transmitted / received via the N26 interface but also those transmitted / received without the N26 interface can be stored.
[2.1. UEの装置構成]
まず、UE(User Equipment)の装置構成例について、図3を用いて説明する。UEは、制御部_A300、アンテナ310、送受信部_A320、記憶部_A340で構成されている。制御部_A300、送受信部_A320、記憶部_A340は、バスを介して接続されている。送受信部_A320は、アンテナ310と接続している。 [2.1. UE device configuration]
First, an example of a UE (User Equipment) device configuration will be described with reference to FIG. The UE is composed of a control unit_A300, anantenna 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.
まず、UE(User Equipment)の装置構成例について、図3を用いて説明する。UEは、制御部_A300、アンテナ310、送受信部_A320、記憶部_A340で構成されている。制御部_A300、送受信部_A320、記憶部_A340は、バスを介して接続されている。送受信部_A320は、アンテナ310と接続している。 [2.1. UE device configuration]
First, an example of a UE (User Equipment) device configuration will be described with reference to FIG. The UE is composed of a control unit_A300, an
制御部_A300は、UE全体の動作・機能を制御する機能部である。制御部_A300は、必要に応じて、記憶部_A340に記憶されている各種プログラムを読み出して実行する事により、UEにおける各種の処理を実現する。
Control unit_A300 is a functional unit that controls the operation and functions of the entire UE. The control unit _A300 realizes various processes in the UE by reading and executing various programs stored in the storage unit _A340 as needed.
送受信部_A320は、アンテナを介して、アクセスネットワーク内の基地局装置(eNB又はgNB)と無線通信する為の機能部である。すなわち、UEは、送受信部_A320を用いて、アクセスネットワーク装置、及び/又はコアネットワーク装置、及び/又はPDN、及び/又はDNとの間で、ユーザデータ及び/又は制御情報を送受信することができる。
The transmitter / receiver_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 can send and receive user data and / or control information to and from the access network device and / or the core network device and / or PDN and / or DN using the transmitter / receiver_A320. it can.
図2を参照して詳細に説明すると、UEは、送受信部_A320を用いることにより、LTE-Uuインターフェースを介して、E-UTRAN内の基地局装置(eNB)と通信することができる。また、UEは、送受信部_A320を用いることにより、5G AN内の基地局装置(gNB)と通信することができる。また、UEは、送受信部_A320を用いることにより、N1インターフェースを介してAMFとNAS(Non-Access-Stratum)メッセージの送受信をすることができる。ただし、N1インターフェースは論理的なものであるため、実際には、UEとAMFの間の通信は、5G ANを介して行われる。
Explaining in detail with reference to FIG. 2, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transmission / reception unit_A320. In addition, the UE can communicate with the base station device (gNB) in 5GAN by using the transmission / reception unit_A320. In addition, the UE can send and receive NAS (Non-Access-Stratum) messages to and from the AMF via the N1 interface by using the transmitter / receiver _A320. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN.
記憶部_A340は、UEの各動作に必要なプログラム、ユーザデータ、制御情報等を記憶する為の機能部である。
The storage unit_A340 is a functional unit for storing programs, user data, control information, etc. required for each operation of the UE.
[2.2. gNBの装置構成]
次に、gNBの装置構成例について、図4を用いて説明する。gNB は、制御部_B500、アンテナ510、ネットワーク接続部_B520、送受信部_B530、記憶部_B540で構成されている。制御部_B500、ネットワーク接続部_B520、送受信部_B530、記憶部_B540は、バスを介して接続されている。送受信部_B530は、アンテナ510と接続している。 [2.2. GNB device configuration]
Next, an example of the device configuration of gNB will be described with reference to FIG. The gNB is composed of a control unit_B500, anantenna 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.
次に、gNBの装置構成例について、図4を用いて説明する。gNB は、制御部_B500、アンテナ510、ネットワーク接続部_B520、送受信部_B530、記憶部_B540で構成されている。制御部_B500、ネットワーク接続部_B520、送受信部_B530、記憶部_B540は、バスを介して接続されている。送受信部_B530は、アンテナ510と接続している。 [2.2. GNB device configuration]
Next, an example of the device configuration of gNB will be described with reference to FIG. The gNB is composed of a control unit_B500, an
制御部_B500は、gNB全体の動作・機能を制御する機能部である。制御部_B500は、必要に応じて、記憶部_B540に記憶されている各種プログラムを読み出して実行する事により、gNBにおける各種の処理を実現する。
Control unit_B500 is a functional unit that controls the operation and function of the entire gNB. The control unit_B500 realizes various processes in the gNB by reading and executing various programs stored in the storage unit_B540 as needed.
ネットワーク接続部_B520は、gNBが、AMF及び/又はUPFと通信する為の機能部である。すなわち、gNBは、ネットワーク接続部_B520を用いて、AMF及び/又はUPFとの間で、ユーザデータ及び/又は制御情報を送受信することができる。
The network connection part_B520 is a functional part for gNB to communicate with AMF and / or UPF. That is, the gNB can send and receive user data and / or control information between the AMF and / or the UPF by using the network connection unit_B520.
送受信部_B530は、アンテナ510を介して、UEと無線通信する為の機能部である。すなわち、gNBは、送受信部_B530を用いて、UEとの間で、ユーザデータ及び/又は制御情報を送受信することができる。
The transmitter / receiver_B530 is a functional unit for wireless communication with the UE via the antenna 510. That is, the gNB can transmit / receive user data and / or control information to / from the UE by using the transmission / reception unit_B530.
図2を参照して詳細に説明すると、5G AN内にあるgNBは、ネットワーク接続部_B520を用いることにより、N2インターフェースを介して、AMFと通信することができ、N3インターフェースを介して、UPFと通信することができる。また、gNBは、送受信部_B530を用いることにより、UEと通信することができる。
Explaining in detail with reference to FIG. 2, the gNB in the 5GAN can communicate with the AMF via the N2 interface by using the network connection _B520, and the UPF via the N3 interface. Can communicate with. In addition, gNB can communicate with the UE by using the transmission / reception unit_B530.
記憶部_B540は、gNBの各動作に必要なプログラム、ユーザデータ、制御情報等を記憶する為の機能部である。
The storage unit_B540 is a functional unit for storing programs, user data, control information, etc. required for each operation of gNB.
[2.3. AMFの装置構成]
次に、AMFの装置構成例について、図5を用いて説明する。AMFは、制御部_B700、ネットワーク接続部_B720、記憶部_B740で構成されている。制御部_B700、ネットワーク接続部_B720、記憶部_B740は、バスを介して接続されている。AMFは、制御プレーンを扱うノードであってよい。 [2.3. AMF device configuration]
Next, an example of the AMF device configuration will be described with reference to FIG. The AMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The AMF may be a node that handles the control plane.
次に、AMFの装置構成例について、図5を用いて説明する。AMFは、制御部_B700、ネットワーク接続部_B720、記憶部_B740で構成されている。制御部_B700、ネットワーク接続部_B720、記憶部_B740は、バスを介して接続されている。AMFは、制御プレーンを扱うノードであってよい。 [2.3. AMF device configuration]
Next, an example of the AMF device configuration will be described with reference to FIG. The AMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The AMF may be a node that handles the control plane.
制御部_B700は、AMF全体の動作・機能を制御する機能部である。制御部_B700は、必要に応じて、記憶部_B740に記憶されている各種プログラムを読み出して実行する事により、AMFにおける各種の処理を実現する。
Control unit_B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit_B700 realizes various processes in AMF by reading and executing various programs stored in the storage unit_B740 as needed.
ネットワーク接続部_B720は、AMFが、5G AN内の基地局装置(gNB)、及び/又はSMF、及び/又はPCF、及び/又はUDM、及び/又はSCEFと接続する為の機能部である。すなわち、AMFは、ネットワーク接続部_B720を用いて、5G AN内の基地局装置(gNB)、及び/又はSMF、及び/又はPCF、及び/又はUDM、及び/又はSCEFとの間で、ユーザデータ及び/又は制御情報を送受信することができる。
The network connection part_B720 is a functional part for AMF to connect to the base station device (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 communicate with the base station equipment (gNB) in 5GAN and / or SMF and / or PCF, and / or UDM, and / or SCEF. Data and / or control information can be sent and received.
図2を参照して詳細に説明すると、5GCN内にあるAMFは、ネットワーク接続部_A620を用いることにより、N2インターフェースを介して、gNBと通信することができ、N8インターフェースを介して、UDMと通信することができ、N11インターフェースを介して、SMFと通信することができ、N15インターフェースを介して、PCFと通信することができる。また、AMFは、ネットワーク接続部_A620を用いることにより、N1インターフェースを介して、UEとNASメッセージの送受信をすることができる。ただし、N1インターフェースは論理的なものであるため、実際には、UEとAMFの間の通信は、5G ANを介して行われる。また、AMFは、N26インターフェースをサポートする場合、ネットワーク接続部_A620を用いることにより、N26インターフェースを介して、MMEと通信することができる。
Explained in detail with reference to FIG. 2, the AMF within the 5GCN can communicate with the gNB via the N2 interface by using the network connection_A620 and with the UDM via the N8 interface. It can communicate, it can communicate with the SMF via the N11 interface, and it can communicate with the PCF via the N15 interface. In addition, AMF can send and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, communication between the UE and AMF is actually done via 5GAN. In addition, when AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection part_A620.
記憶部_B740は、AMFの各動作に必要なプログラム、ユーザデータ、制御情報等を記憶する為の機能部である。
The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of AMF.
尚、AMFは、N2インターフェースを用いたRANとの制御メッセージを交換する機能、N1インターフェースを用いたUEとのNASメッセージを交換する機能、NASメッセージの暗号化及び完全性保護を行う機能、登録管理(Registration management; RM)機能、接続管理(Connection management; CM)機能、到達可能性管理(Reachability management)機能、UE等の移動性管理(Mobility management)機能、UEとSMF間のSM(Session Management)メッセージを転送する機能、アクセス認証(Access Authentication、Access Authorization)機能、セキュリティアンカー機能(SEA; Security Anchor Functionality)、セキュリティコンテキスト管理(SCM; Security Context Management)機能、N3IWF(Non-3GPP Interworking Function)に対するN2インターフェースをサポートする機能、N3IWFを介したUEとのNAS信号の送受信をサポートする機能、N3IWFを介して接続するUEの認証する機能等を有する。
AMF has a function to exchange control messages with RAN using the N2 interface, a function to exchange NAS messages with UE using the N1 interface, a function to encrypt and protect the integrity of NAS messages, and registration management. (Registration management; RM) function, connection management (CM) function, reachability management (Reachability management) function, mobility management (Mobility management) function such as UE, SM (Session Management) between UE and SMF Message forwarding function, access authentication (Access Authorization) function, security anchor function (SEA; Security Anchor Functionality), security context management (SCM; Security Context Management) function, N2 for N3IWF (Non-3GPP Interworking Function) It has a function to support an interface, a function to support transmission / reception of NAS signals with a UE via N3IWF, a function to authenticate a UE connected via N3IWF, and the like.
また、登録管理では、UEごとのRM状態が管理される。RM状態は、UEとAMFとの間で同期がとられていてもよい。RM状態としては、非登録状態(RM-DEREGISTERED state)と、登録状態(RM-REGISTERED state)がある。RM-DEREGISTERED状態では、UEはネットワークに登録されていないため、AMFにおけるUEコンテキストが、そのUEに対する有効な位置情報やルーティング情報を持っていない為、AMFはUEに到達できない状態である。また、RM-REGISTERED状態では、UEはネットワークに登録されているため、UEはネットワークとの登録が必要なサービスを受信することができる。尚、RM状態は、5GMM状態(5GMM state)と表現されてもよい。この場合、RM-DEREGISTERED状態は、5GMM-DEREGISTERED状態と表現されてもよいし、RM-REGISTERED状態は、5GMM-REGISTERED状態と表現されてもよい。
Also, in registration management, the RM status for each UE is managed. The RM state may be synchronized between the UE and AMF. The RM state includes a non-registered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered in the network, so the UE context in the AMF does not have valid location information or routing information for the UE, so the AMF cannot reach the UE. Also, in the RM-REGISTERED state, the UE is registered in the network, so the UE can receive services that require registration with the network. The RM state may be expressed as a 5GMM state (5GMM state). In this case, the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state.
言い換えると、5GMM-REGISTEREDは、各装置が、5GMMコンテキストを確立した状態であってもよいし、PDUセッションコンテキストを確立した状態であってもよい。尚、各装置が5GMM-REGISTEREDである場合、UE_A10は、ユーザデータや制御メッセージの送受信を開始してもよいし、ページングに対して応答してもよい。さらに、尚、各装置が5GMM-REGISTEREDである場合、UE_A10は、初期登録のための登録手続き以外の登録手続き、及び/又はサービス要求手続きを実行してもよい。
In other words, 5GMM-REGISTERED may be in a state where each device has established a 5GMM context or a PDU session context. When each device is 5GMM-REGISTERED, UE_A10 may start sending and receiving user data and control messages, or may respond to paging. Further, when each device is 5GMM-REGISTERED, UE_A10 may execute a registration procedure other than the registration procedure for initial registration and / or a service request procedure.
さらに、5GMM-DEREGISTEREDは、各装置が、5GMMコンテキストを確立していない状態であってもよいし、UE_A10の位置情報がネットワークに把握されていない状態であってもよいし、ネットワークがUE_A10に到達不能である状態であってもよい。尚、各装置が5GMM-DEREGISTEREDである場合、UE_A10は、登録手続きを開始してもよいし、登録手続きを実行することで5GMMコンテキストを確立してもよい。
Furthermore, in 5GMM-DEREGISTERED, each device may be in a state where the 5GMM context has not been established, the position 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 the 5GMM context by executing the registration procedure.
また、接続管理では、UEごとのCM状態が管理される。CM状態は、UEとAMFとの間で同期がとられていてもよい。CM状態としては、非接続状態(CM-IDLE state)と、接続状態(CM-CONNECTED state)がある。CM-IDLE状態では、UEはRM-REGISTERED状態にあるが、N1インターフェースを介したAMFとの間で確立されるNASシグナリング接続(NAS signalling connection)を持っていない。また、CM-IDLE状態では、UEはN2インターフェースの接続(N2 connection)、及びN3インターフェースの接続(N3 connection)を持っていない。一方、CM-CONNECTED状態では、N1インターフェースを介したAMFとの間で確立されるNASシグナリング接続(NAS signalling connection)を持っている。また、CM-CONNECTED状態では、UEはN2インターフェースの接続(N2 connection)、及び/又はN3インターフェースの接続(N3 connection)を持っていてもよい。
Also, in connection management, the CM status for each UE is managed. The CM state may be synchronized between the UE and AMF. The CM state includes a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state, but does not have a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-IDLE state, the UE does not have an N2 interface connection (N2 connection) and an N3 interface connection (N3 connection). On the other hand, in the CM-CONNECTED state, it has a NAS signaling connection (NAS signaling connection) established with AMF via the N1 interface. Further, in the CM-CONNECTED state, the UE may have an N2 interface connection (N2 connection) and / or an N3 interface connection (N3 connection).
さらに、接続管理では、3GPPアクセスにおけるCM状態と、non-3GPPアクセスにおけるCM状態とで分けて管理されてもよい。この場合、3GPPアクセスにおけるCM状態としては、3GPPアクセスにおける非接続状態(CM-IDLE state over 3GPP access)と、3GPPアクセスにおける接続状態(CM-CONNECTED state over 3GPP access)とがあってよい。さらに、non-3GPPアクセスにおけるCM状態としては、non-3GPPアクセスにおける非接続状態(CM-IDLE state over non-3GPP access)と、non-3GPPアクセスにおける接続状態(CM-CONNECTED state over non-3GPP access)とがあってよい。尚、非接続状態はアイドルモード表現されてもよく、接続状態モードはコネクテッドモードと表現されてもよい。
Furthermore, in connection management, the CM state in 3GPP access and the CM state in non-3GPP access may be managed separately. In this case, the CM state in 3GPP access may be a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over 3GPP access). Furthermore, the CM state in non-3GPP access includes the non-connection 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. ) May be there. The disconnected state may be expressed as an idle mode, and the connected state mode may be expressed as a connected mode.
尚、CM状態は、5GMMモード(5GMM mode)と表現されてもよい。この場合、非接続状態は、5GMM非接続モード(5GMM-IDLE mode)と表現されてもよいし、接続状態は、5GMM接続モード(5GMM-CONNECTED mode)と表現されてもよい。さらに、3GPPアクセスにおける非接続状態は、3GPPアクセスにおける5GMM非接続モード(5GMM-IDLE mode over 3GPP access)と表現されてもよいし、3GPPアクセスにおける接続状態は、3GPPアクセスにおける5GMM接続モード(5GMM-CONNECTED mode over 3GPP access)と表現されてもよい。さらに、non-3GPPアクセスにおける非接続状態は、non-3GPPアクセスにおける5GMM非接続モード(5GMM-IDLE mode over non-3GPP access)と表現されてもよいし、non-3GPPアクセスにおける接続状態は、non-3GPPアクセスにおける5GMM接続モード(5GMM-CONNECTED mode over non-3GPP access)と表現されてもよい。尚、5GMM非接続モードはアイドルモード表現されてもよく、5GMM接続モードはコネクテッドモードと表現されてもよい。
The CM state may be expressed as 5GMM mode (5GMM mode). In this case, the non-connected state may be expressed as 5GMM non-connected mode (5GMM-IDLE mode), and the connected state may be expressed as 5GMM connected mode (5GMM-CONNECTED mode). Furthermore, the disconnected state in 3GPP access may be expressed as 5GMM non-connection mode (5GMM-IDLE mode over 3GPP access) in 3GPP access, and the connection state in 3GPP access is 5GMM connection mode (5GMM-) in 3GPP access. It may be expressed as CONNECTED mode over 3GPP access). Further, the non-connection state in non-3GPP access may be expressed as 5GMM non-connection mode (5GMM-IDLE mode over non-3GPP access) in non-3GPP access, and the connection state in non-3GPP access is non. It may be expressed as 5GMM connection mode (5GMM-CONNECTED mode over non-3GPP access) in -3GPP access. The 5GMM non-connection mode may be expressed as an idle mode, and the 5GMM connection mode may be expressed as a connected mode.
また、AMFは、コアネットワーク_B内に1以上配置されてもよい。また、AMFは、1以上のNSI(Network Slice Instance)を管理するNFでもよい。また、AMFは、複数のNSI間で共有される共有CPファンクション(CCNF; Common CPNF(Control Plane Network Function))でもよい。
Also, one or more AMFs may be placed in the core network_B. In addition, AMF may be an NF that manages one or more NSIs (Network Slice Instances). Further, the AMF may be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among a plurality of NSIs.
尚、N3IWFは、UEが5GSに対してnon-3GPPアクセスを介して接続する場合に、non-3GPPアクセスと5GCNとの間に配置される装置及び/又は機能である。
Note that N3IWF is a device and / or function that is placed between non-3GPP access and 5GCN when the UE connects to 5GS via non-3GPP access.
[2.4. SMFの装置構成]
次に、SMFの装置構成例について、図5を用いて説明する。SMFは、制御部_B700、ネットワーク接続部_B720、記憶部_B740で構成されている。制御部_B700、ネットワーク接続部_B720、記憶部_B740は、バスを介して接続されている。SMFは、制御プレーンを扱うノードであってよい。 [2.4. SMF device configuration]
Next, an example of the SMF device configuration will be described with reference to FIG. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF may be a node that handles the control plane.
次に、SMFの装置構成例について、図5を用いて説明する。SMFは、制御部_B700、ネットワーク接続部_B720、記憶部_B740で構成されている。制御部_B700、ネットワーク接続部_B720、記憶部_B740は、バスを介して接続されている。SMFは、制御プレーンを扱うノードであってよい。 [2.4. SMF device configuration]
Next, an example of the SMF device configuration will be described with reference to FIG. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF may be a node that handles the control plane.
制御部_B700は、SMF全体の動作・機能を制御する機能部である。制御部_B700は、必要に応じて、記憶部_B740に記憶されている各種プログラムを読み出して実行する事により、SMFにおける各種の処理を実現する。
Control unit_B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit_B700 realizes various processes in the SMF by reading and executing various programs stored in the storage unit_B740 as needed.
ネットワーク接続部_B720は、SMFが、AMF、及び/又はUPF、及び/又はPCF、及び/又はUDMと接続する為の機能部である。すなわち、SMFは、ネットワーク接続部_B720を用いて、AMF、及び/又はUPF、及び/又はPCF、及び/又はUDMとの間で、ユーザデータ及び/又は制御情報を送受信することができる。
The network connection part_B720 is a functional part for SMF to connect with AMF and / or UPF and / or PCF and / or UDM. That is, the SMF can send and receive user data and / or control information between the AMF and / or the UPF, and / or the PCF, and / or the UDM by using the network connection part_B720.
図2を参照して詳細に説明すると、5GCN内にあるSMFは、ネットワーク接続部_A620を用いることにより、N11インターフェースを介して、AMFと通信することができ、N4インターフェースを介して、UPFと通信することができ、N7インターフェースを介して、PCFと通信することができ、N10インターフェースを介して、UDMと通信することができる。
Explained in detail with reference to FIG. 2, the SMF in the 5GCN can communicate with the AMF via the N11 interface by using the network connection_A620 and with the UPF via the N4 interface. It can communicate, it can communicate with the PCF via the N7 interface, and it can communicate with the UDM via the N10 interface.
記憶部_B740は、SMFの各動作に必要なプログラム、ユーザデータ、制御情報等を記憶する為の機能部である。
The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the SMF.
SMFは、PDUセッションの確立・修正・解放等のセッション管理(Session Management)機能、UEに対するIPアドレス割り当て(IP address allocation)及びその管理機能、UPFの選択と制御機能、適切な目的地(送信先)へトラフィックをルーティングする為のUPFの設定機能、NASメッセージのSM部分を送受信する機能、下りリンクのデータが到着したことを通知する機能(Downlink Data Notification)、AMF経由でN2インターフェースを介してANに送信される、AN特有の(ANごとの)SM情報を提供する機能、セッションに対するSSCモード(Session and Service Continuity mode)を決定する機能、ローミング機能等を有する。
SMF has session management functions such as establishment / modification / release of PDU sessions, IP address allocation and management functions for UEs, UPF selection and control functions, and appropriate destinations (destination). ), UPF setting function for routing traffic to), function to send and receive SM part of NAS message, function to notify that downlink data has arrived (Downlink Data Notification), AN via N2 interface via AMF It has a function to provide SM information peculiar to AN (for each AN) sent to, a function to determine the SSC mode (Session and Service Continuity mode) for the session, a roaming function, and the like.
[2.5. UPFの装置構成]
次に、UPFの装置構成例について、図5を用いて説明する。UPFは、制御部_B700、ネットワーク接続部_B720、記憶部_B740で構成されている。制御部_B700、ネットワーク接続部_B720、記憶部_B740は、バスを介して接続されている。UPFは、制御プレーンを扱うノードであってよい。 [2.5. UPF device configuration]
Next, an example of the UPF device configuration will be described with reference to FIG. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The UPF may be a node that handles the control plane.
次に、UPFの装置構成例について、図5を用いて説明する。UPFは、制御部_B700、ネットワーク接続部_B720、記憶部_B740で構成されている。制御部_B700、ネットワーク接続部_B720、記憶部_B740は、バスを介して接続されている。UPFは、制御プレーンを扱うノードであってよい。 [2.5. UPF device configuration]
Next, an example of the UPF device configuration will be described with reference to FIG. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The UPF may be a node that handles the control plane.
制御部_B700は、UPF全体の動作・機能を制御する機能部である。制御部_B700は、必要に応じて、記憶部_B740に記憶されている各種プログラムを読み出して実行する事により、UPFにおける各種の処理を実現する。
Control unit_B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit _B700 realizes various processes in the UPF by reading and executing various programs stored in the storage unit _B740 as needed.
ネットワーク接続部_B720は、UPFが、5G AN内の基地局装置(gNB)、及び/又はSMF、及び/又はDNと接続する為の機能部である。すなわち、UPFは、ネットワーク接続部_B720を用いて、5G AN内の基地局装置(gNB)、及び/又はSMF、及び/又はDNとの間で、ユーザデータ及び/又は制御情報を送受信することができる。
The network connection part_B720 is a functional part for the UPF to connect to the base station device (gNB) in 5GAN and / or SMF and / or DN. That is, the UPF uses the network connection _B720 to send and receive user data and / or control information between the base station equipment (gNB) in 5GAN and / or SMF and / or DN. Can be done.
図2を参照して詳細に説明すると、5GCN内にあるUPFは、ネットワーク接続部_A620を用いることにより、N3インターフェースを介して、gNBと通信することができ、N4インターフェースを介して、SMFと通信することができ、N6インターフェースを介して、DNと通信することができ、N9インターフェースを介して、他のUPFと通信することができる。
Explained in detail with reference to FIG. 2, the UPF in 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, can communicate with DN via N6 interface, and can communicate with other UPFs via N9 interface.
記憶部_B740は、UPFの各動作に必要なプログラム、ユーザデータ、制御情報等を記憶する為の機能部である。
The storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of UPF.
UPFは、intra-RAT mobility又はinter-RAT mobilityに対するアンカーポイントとしての機能、DNに相互接続するための外部PDUセッションポイントとしての機能(つまり、DNとコアネットワーク_Bとの間のゲートウェイとして、ユーザデータを転送する機能)、パケットのルーティング及び転送する機能、1つのDNに対して複数のトラフィックフローのルーティングをサポートするUL CL(Uplink Classifier)機能、マルチホーム(multi-homed)PDUセッションをサポートするBranching point機能、user planeに対するQoS (Quality of Service) 処理機能、上りリンクトラフィックの検証機能、下りリンクパケットのバッファリング、下りリンクデータ通知(Downlink Data Notification)をトリガする機能等を有する。
The UPF acts as an anchor point for intra-RAT mobility or inter-RAT mobility, as an external PDU session point for interconnecting the DN (ie, as a gateway between the DN and the core network_B). Data transfer function), packet routing and transfer function, UL CL (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 the user plane, a function for verifying uplink traffic, a function for buffering downlink packets, and a function for triggering downlink data notification (Downlink Data Notification).
また、UPFは、IP通信及び/又はnon-IP通信の為のゲートウェイでもよい。また、UPFは、IP通信を転送する機能を持ってもよく、non-IP通信とIP通信を変換する機能を持っていてもよい。さらに複数配置されるゲートウェイは、コアネットワーク_Bと単一のDNを接続するゲートウェイでもよい。尚、UPFは、他のNFとの接続性を備えてもよく、他のNFを介して各装置に接続してもよい。
The UPF may also be a gateway for IP communication and / or non-IP communication. In addition, the UPF may have a function of transferring IP communication, or may have a function of converting non-IP communication and IP communication. Further, the plurality of gateways to be arranged 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 the other NFs.
尚、ユーザプレーン(user plane)は、UEとネットワークとの間で送受信されるユーザデータ(user data)のことである。ユーザプレーンは、PDNコネクション、又はPDUセッションを用いて送受信されてもよい。さらに、EPSの場合、ユーザプレーンは、LTE-Uuインターフェース、及び/又はS1-Uインターフェース、及び/又はS5インターフェース、及び/又はS8インターフェース、及び/又はSGiインターフェースを用いて送受信されてもよい。さらに、5GSの場合、ユーザプレーンは、UEとNG RANとの間のインターフェース、及び/又はN3インターフェース、及び/又はN9インターフェース、及び/又はN6インターフェースを介して送受信されてもよい。以下、ユーザプレーンは、U-Planeと表現されてもよい。
The user plane is user data sent and received between the UE and the network. The user plane may be transmitted and received using a PDN connection or a PDU session. Further, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface and / or the S1-U interface and / or the S5 interface and / or the S8 interface and / or the SGi interface. Further, in the case of 5GS, the user plane may be transmitted and received via the interface between the UE and NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. Hereinafter, the user plane may be expressed as U-Plane.
さらに、制御プレーン(control plane)は、UEの通信制御等を行うために送受信される制御メッセージのことである。制御プレーンは、UEとMMEとの間のNAS (Non-Access-Stratum)シグナリングコネクションを用いて送受信されてもよい。さらに、EPSの場合、制御プレーンは、LTE-Uuインターフェース、及びS1-MMEインターフェースを用いて送受信されてもよい。さらに、5GSの場合、制御プレーンは、UEとNG RANとの間のインターフェース、及びN2インターフェースを用いて送受信されてもよい。以下、制御プレーンは、コントロールプレーンと表現されてもよいし、C-Planeと表現されてもよい。
Furthermore, the control plane is a control message sent and received to control the communication of the UE. The control plane may be transmitted and received using a NAS (Non-Access-Stratum) signaling connection between the UE and MME. Further, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Furthermore, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and NG RAN and the N2 interface. Hereinafter, the control plane may be expressed as a control plane or a C-Plane.
さらに、U-Plane(User Plane; UP)は、ユーザデータを送受信する為の通信路でもよく、複数のベアラで構成されてもよい。さらに、C-Plane(Control Plane; CP)は、制御メッセージを送受信する為の通信路でもよく、複数のベアラで構成されてもよい。
Furthermore, the U-Plane (User Plane; UP) may be a communication path for transmitting and receiving user data, and may be composed of a plurality of bearers. Further, the C-Plane (Control Plane; CP) may be a communication path for transmitting and receiving control messages, and may be composed of a plurality of bearers.
[2.6. その他の装置及び/又は機能の説明]
次に、その他の装置及び/又は機能について説明を行う。 [2.6. Description of other devices and / or functions]
Next, other devices and / or functions will be described.
次に、その他の装置及び/又は機能について説明を行う。 [2.6. Description of other devices and / or functions]
Next, other devices and / or functions will be described.
PCFは、ポリシールールを提供する機能等を有する。
PCF has a function to provide policy rules.
また、UDMは、認証情報処理(Authentication credential processing)機能、ユーザ識別処理機能、アクセス認証機能、登録/移動性管理機能、加入者情報の管理(subscription management)機能等を有する。
In addition, UDM has authentication information processing (Authentication credential processing) function, user identification processing function, access authentication function, registration / mobility management function, subscriber information management (subscription management) function, and the like.
また、PCRFは、PGW及び/又はPDNに接続されており、データ配送に対するQoS管理を行う機能等を有する。例えば、UE_A10とPDN間の通信路のQoSの管理を行う。さらに、PCRFは、各装置がユーザデータを送受信する際に用いるPCC(Policy and Charging Control)ルール、及び/又はルーティングルールを作成、及び/又は管理する装置でもよい。
In addition, PCRF is connected to PGW and / or PDN, and has a function of performing QoS management for data delivery. For example, it manages the QoS of the communication path between UE_A10 and PDN. Further, the PCRF may be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules that each device uses when transmitting and receiving user data.
また、HSSは、MME及び/又はSCEFに接続されており、加入者情報の管理を行う機能等を有する。HSSの加入者情報は、例えばMMEのアクセス制御の際に参照される。さらに、HSSは、MMEとは異なる位置管理装置と接続されていてもよい。
In addition, HSS is connected to MME and / or SCEF and has a function to manage subscriber information. HSS subscriber information is referred to, for example, when controlling access to MME. Further, the HSS may be connected to a position management device different from the MME.
また、SCEFは、DN及び/又はPDNとMMEとHSSとに接続されており、DN及び/又はPDNとコアネットワーク_Aとを繋ぐゲートウェイとしてユーザデータの転送を行う中継装置としての機能等を有する。尚、SCEFは、non-IP通信の為のゲートウェイでもよい。さらに、SCEFは、non-IP通信とIP通信を変換する機能を持っていてもよい。また、こうしたゲートウェイはコアネットワーク_Aに複数配置されてよい。SCEFはコアネットワークの外側に構成されてもよいし、内側に構成されてもよい。
In addition, SCEF is connected to DN and / or PDN, MME and HSS, and has a function as a relay device that transfers user data as a gateway connecting DN and / or PDN and core network_A. .. SCEF may be a gateway for non-IP communication. In addition, SCEF may have the ability to convert between non-IP communication and IP communication. In addition, a plurality of such gateways may be arranged in the core network_A. The SCEF may be configured outside or inside the core network.
[3.各実施形態における各種手続き及び用語・識別情報の説明]
次に、本実施形態における各実施形態における各種手続きの詳細手順を説明する前に、重複説明を避ける為、本実施形態で特有の用語や、各手続きに用いる主要な識別情報を予め説明する。以下、各実施形態における各種手続きは、本手続きとも称する。 [3. Explanation of various procedures and terms / identification information in each embodiment]
Next, before explaining the detailed procedures of the various procedures in each of the embodiments in the present embodiment, in order to avoid duplicate explanations, terms specific to the present embodiment and main identification information used in each procedure will be described in advance. Hereinafter, various procedures in each embodiment are also referred to as this procedure.
次に、本実施形態における各実施形態における各種手続きの詳細手順を説明する前に、重複説明を避ける為、本実施形態で特有の用語や、各手続きに用いる主要な識別情報を予め説明する。以下、各実施形態における各種手続きは、本手続きとも称する。 [3. Explanation of various procedures and terms / identification information in each embodiment]
Next, before explaining the detailed procedures of the various procedures in each of the embodiments in the present embodiment, in order to avoid duplicate explanations, terms specific to the present embodiment and main identification information used in each procedure will be described in advance. Hereinafter, various procedures in each embodiment are also referred to as this procedure.
ネットワークとは、アクセスネットワーク_B、コアネットワーク_B、DNのうち、少なくとも一部を指す。また、アクセスネットワーク_B、コアネットワーク_B、DNのうち、少なくとも一部に含まれる1以上の装置を、ネットワーク又はネットワーク装置と称してもよい。つまり、ネットワークがメッセージの送受信及び/又は処理を実行するということは、ネットワーク内の装置(ネットワーク装置、及び/又は制御装置)がメッセージの送受信及び/又は処理を実行することを意味してもよい。逆に、ネットワーク内の装置がメッセージの送受信及び/又は処理を実行するということは、ネットワークがメッセージの送受信及び/又は処理を実行することを意味してもよい。
The network refers to at least a part of the access network_B, core network_B, and DN. Further, one or more devices included in at least a part of the access network_B, core network_B, and DN may be referred to as a network or a network device. That is, the fact that the network executes the transmission / reception and / or processing of messages may mean that the devices (network devices and / or control devices) in the network execute the transmission / reception and / or processing of messages. .. Conversely, the fact that a device in the network executes message transmission / reception and / or processing may mean that the network executes message transmission / reception and / or processing.
また、SM(セッションマネジメント)メッセージ(NAS (Non-Access-Stratum) SMメッセージとも称する)は、SMのための手続きで用いられるNASメッセージであってよく、AMF_A240を介してUE_A10とSMF_A230の間で送受信される制御メッセージであってよい。さらに、SMメッセージには、PDUセッション確立要求メッセージ、PDUセッション確立受諾メッセージ、PDUセッション完了メッセージ、PDUセッション拒絶メッセージ、PDUセッション変更要求メッセージ、PDUセッション変更受諾メッセージ、PDUセッション変更応答メッセージ等が含まれてもよい。また、SMのための手続きには、PDUセッション確立手続きが含まれてもよい。
In addition, SM (session management) messages (also referred to as NAS (Non-Access-Stratum) SM messages) may be NAS messages used in procedures for SM, and are sent and received between UE_A10 and SMF_A230 via AMF_A240. It may be a control message to be executed. In addition, SM messages include PDU session establishment request messages, PDU session establishment acceptance messages, PDU session completion messages, PDU session rejection messages, PDU session change request messages, PDU session change acceptance messages, PDU session change response messages, and the like. You may. In addition, the procedure for SM may include a PDU session establishment procedure.
また、5GS(5G System)サービスは、コアネットワーク_B190を用いて提供される接続サービスでよい。さらに、5GSサービスは、EPSサービスと異なるサービスでもよいし、EPSサービスと同様のサービスでもよい。
Also, the 5GS (5G System) service may be a connection service provided using the core network_B190. Further, the 5GS service may be a service different from the EPS service or a service similar to the EPS service.
また、non 5GSサービスは、5GSサービス以外のサービスでよく、EPSサービス、及び/又はnon EPSサービスが含まれてもよい。
In addition, the non 5GS service may be a service other than the 5GS service, and may include an EPS service and / or a non EPS service.
また、PDN(Packet Data Network)タイプとは、PDNコネクションのタイプを示すものであり、IPv4、IPv6、IPv4v6、non-IPがある。IPv4が指定された場合、IPv4を用いてデータの送受信を行う事を示す。IPv6が指定された場合は、IPv6を用いてデータの送受信を行う事を示す。IPv4v6が指定された場合は、IPv4又はIPv6を用いてデータの送受信を行う事を示す。non-IPが指定された場合は、IPを用いた通信ではなく、IP以外の通信方法によって通信する事を示す。
The PDN (Packet Data Network) type indicates the type of PDN connection, and includes IPv4, IPv6, IPv4v6, and non-IP. When IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is sent and received using IPv6. When IPv4v6 is specified, it indicates that data is sent and received using IPv4 or IPv6. When non-IP is specified, it indicates that communication is performed by a communication method other than IP, not communication using IP.
また、PDU(Protocol Data Unit/Packet Data Unit)セッションとは、PDU接続性サービスを提供するDNとUEとの間の関連性として定義することができるが、UEと外部ゲートウェイとの間で確立される接続性であってもよい。UEは、5GSにおいて、アクセスネットワーク_B及びコアネットワーク_Bを介したPDUセッションを確立することにより、PDUセッションを用いて、DNとの間のユーザデータの送受信を行うことができる。ここで、この外部ゲートウェイとは、UPF、SCEF等であってよい。UEは、PDUセッションを用いて、DNに配置されるアプリケーションサーバー等の装置と、ユーザデータの送受信を実行する事ができる。
In addition, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as the relationship between the DN that provides the PDU connectivity service and the UE, but it is established between the UE and the external gateway. It may be connectivity. By establishing a PDU session via the access network_B and the core network_B in 5GS, the UE can send and receive user data to and from the DN using the PDU session. Here, the external gateway may be UPF, SCEF, or the like. The UE can use the PDU session to send and receive user data to and from devices such as application servers located in the DN.
尚、各装置(UE、及び/又はアクセスネットワーク装置、及び/又はコアネットワーク装置)は、PDUセッションに対して、1以上の識別情報を対応づけて管理してもよい。尚、これらの識別情報には、DNN、QoSルール、PDUセッションタイプ、アプリケーション識別情報、NSI識別情報、アクセスネットワーク識別情報、及びSSC modeのうち1以上が含まれてもよいし、その他の情報がさらに含まれてもよい。さらに、PDUセッションを複数確立する場合には、PDUセッションに対応づけられる各識別情報は、同じ内容でもよいし、異なる内容でもよい。
Note that each device (UE and / or access network device and / or core network device) may manage one or more identification information in association with each other for the PDU session. Note that these identification information may include one or more of DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and other information. It may be further included. Further, when a plurality of PDU sessions are established, the identification information associated with the PDU session may have the same content or different contents.
また、DNN(Data Network Name)は、コアネットワーク及び/又はDN等の外部ネットワークを識別する識別情報でよい。さらに、DNNは、コアネットワークB190を接続するPGW_A30/UPF_A235等のゲートウェイを選択する情報として用いることもできる。さらに、DNNは、APN(Access Point Name)に相当するものでもよい。
Further, DNN (Data Network Name) may be identification information that identifies the core network and / or the external network such as DN. Furthermore, DNN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 that connects the core network B190. Further, the DNN may correspond to an APN (Access Point Name).
また、PDU(Protocol Data Unit/Packet Data Unit)セッションタイプは、PDUセッションのタイプを示すものであり、IPv4、IPv6、Ethernet、Unstructuredがある。IPv4が指定された場合、IPv4を用いてデータの送受信を行うことを示す。IPv6が指定された場合は、IPv6を用いてデータの送受信を行うことを示す。Ethernetが指定された場合は、Ethernetフレームの送受信を行うことを示す。また、Ethernetは、IPを用いた通信を行わないことを示してもよい。Unstructuredが指定された場合は、Point-to-Point(P2P)トンネリング技術を用いて、DNにあるアプリケーションサーバー等にデータを送受信することを示す。P2Pトンネリング技術としては、例えば、UDP/IPのカプセル化技術を用いても良い。尚、PDUセッションタイプには、上記の他にIPが含まれても良い。IPは、UEがIPv4とIPv6の両方を使用可能である場合に指定する事ができる。
Also, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet, and Unstructured. When IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is sent and received using IPv6. When Ethernet is specified, it indicates that Ethernet frames are sent and received. Further, Ethernet may indicate that communication using IP is not performed. When Unstructured is specified, it indicates that data is sent and received to the application server etc. in the DN by using the point-to-point (P2P) tunneling technology. As the P2P tunneling technique, for example, a UDP / IP encapsulation technique may be used. The PDU session type may include an IP in addition to the above. IP can be specified if the UE can use both IPv4 and IPv6.
また、ネットワークスライス(NS)とは、特定のネットワーク能力及びネットワーク特性を提供する論理的なネットワークである。UE及び/又はネットワークは、5GSにおいて、ネットワークスライス(NWスライス; NS)をサポートすることができる。
A network slice (NS) is a logical network that provides specific network capabilities and network characteristics. UEs and / or networks can support network slices (NW slices; NS) in 5GS.
また、ネットワークスライスインスタンス(NSI)とは、ネットワーク機能(NF)のインスタンス(実体)と、必要なリソースのセットで構成され、配置されるネットワークスライスを形成する。ここで、NFとは、ネットワークにおける処理機能であって、3GPPで採用又は定義されたものである。NSIはコアネットワーク_B内に1以上構成される、NSの実体である。また、NSIはNST(Network Slice Template)を用いて生成された仮想的なNF(Network Function)により構成されてもよい。ここで、NSTとは、要求される通信サービスや能力(capability)を提供する為のリソース要求に関連付けられ、1以上のNFの論理的表現である。つまり、NSIとは、複数のNFにより構成されたコアネットワーク_B190内の集合体でよい。また、NSIはサービス等によって配送されるユーザデータを分ける為に構成された論理的なネットワークでよい。NSには、1以上のNFが構成されてよい。NSに構成されるNFは、他のNSと共有される装置であってもよいし、そうでなくてもよい。UE、及び/又ネットワーク内の装置は、NSSAI、及び/又はS-NSSAI、及び/又はUE usage type、及び/又は1以上のNSI ID等の登録情報、及び/又はAPNに基づいて、1以上のNSに割り当てられることができる。尚、UE usage typeは、NSIを識別するための使用される、UEの登録情報に含まれるパラメータ値である。UE usage typeはHSSに記憶されていてよい。AMFはUE usage typeに基づきSMFとUPFを選択してもよい。
In addition, a network slice instance (NSI) is composed of an instance (entity) of a network function (NF) and a set of necessary resources, and forms a network slice to be arranged. Here, NF is a processing function in a network and is adopted or defined in 3GPP. NSI is an entity of NS that consists of one or more in core network_B. Further, NSI may be composed of a virtual NF (Network Function) generated by using NST (Network Slice Template). Here, NST is a logical representation of one or more NFs associated with a resource request to provide the required communication service or capability. In other words, the NSI may be an aggregate in the core network_B190 composed of a plurality of NFs. In addition, NSI may be a logical network configured to divide user data delivered by services or 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 the NS of. The UE usage type is a parameter value included in the UE registration information used to identify the NSI. The UE usage type may be stored in the HSS. AMF may select SMF and UPF based on UE usage type.
また、S-NSSAI(Single Network Slice Selection Assistance Information)は、NSを識別するための情報である。S-NSSAIは、SST(Slice/Service type)のみで構成されてもよいし、SSTとSD(Slice Differentiator)の両方で構成されてもよい。ここで、SSTとは、機能とサービスの面で期待されるNSの動作を示す情報である。また、SDは、SSTで示される複数のNSIから1つのNSIを選択する際に、SSTを補間する情報であってもよい。S-NSSAIは、PLMNごとに特有な情報であってもよいし、PLMN間で共通化された標準の情報であってもよい。また、ネットワークは、デフォルトS-NSSAIとして、UEの登録情報に1以上のS-NSSAIを記憶してもよい。尚、S-NSSAIがデフォルトS-NSSAIである場合において、UEが登録要求メッセージにおいて有効なS-NSSAIをネットワークに送信しないときは、ネットワークは、UEに関係するNSを提供してもよい。
In addition, S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying NS. S-NSSAI may be composed of only SST (Slice / Service type), or may be composed of both SST and SD (Slice Differentiator). Here, SST is information indicating the operation of NS expected in terms of functions and services. Further, SD may be information for interpolating SST when selecting one NSI from a plurality of NSIs represented by SST. S-NSSAI may be information peculiar to each PLMN, or may be standard information shared among PLMNs. In addition, the network may store one or more S-NSSAI in the UE registration information as the default S-NSSAI. If the S-NSSAI is the default S-NSSAI and the UE does not send a valid S-NSSAI to the network in the registration request message, the network may provide the NS related to the UE.
また、NSSAI(Network Slice Selection Assistance Information)は、S-NSSAIの集まりである。NSSAIに含まれる、各S-NSSAIはアクセスネットワーク又はコアネットワークがNSIを選択するのをアシストする情報である。UEはPLMNごとにネットワークから許可されたNSSAIを記憶してもよい。また、NSSAIは、AMFを選択するのに用いられる情報であってよい。
NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in NSSAI is information that assists the access network or core network in selecting NSI. The UE may memorize the NSSAI permitted from the network for each PLMN. Also, NSSAI may be the information used to select AMF.
また、requested NSSAIは、UEが登録したい1又は複数ネットワークスライスを示す1又は複数のS-NSSAIを含む情報である。requested NSSAIに含まれるS-NSSAIはrequested S-NSSAIと表現されてもよい。
Also, requested NSSAI is information including one or more S-NSSAI indicating one or more network slices that the UE wants to register. S-NSSAI included in requested NSSAI may be expressed as requested S-NSSAI.
また、allowed NSSAIは、UEが許可された1又は複数ネットワークスライスを示す1又は複数のS-NSSAIを含む情報である。UEとネットワークはそれぞれ、UEの情報として、allowed NSSAIを記憶、管理する。allowed NSSAIに含まれるS-NSSAIはallowed S-NSSAIと表現されてもよい。
Also, allowed NSSAI is information that includes one or more S-NSSAIs indicating one or more network slices allowed by the UE. The UE and the network each store and manage allowed NSSAI as UE information. S-NSSAI included in allowed NSSAI may be expressed as allowed S-NSSAI.
また、rejected NSSAIは、UEからネットワークに送信されたrequested NSSAIに含まれるS-NSSAI(s)のうち、ネットワークが許可しない1又は複数のネットワークスライスを示す1又は複数のS-NSSAIを含む。さらに、rejected NSSAIに含まれるS-NSSAIごとに、拒絶理由を示す理由値(cause)が、rejected NSSAIに含まれてよい。rejected NSSAIに含まれるS-NSSAIはrejected S-NSSAIと表現されてもよい。
In addition, rejected NSSAI includes one or more S-NSSAI indicating one or more network slices that the network does not allow among S-NSSAI (s) included in requested NSSAI transmitted from the UE to the network. Further, for each S-NSSAI included in the rejected NSSAI, a reason value (cause) indicating the reason for refusal may be included in the rejected NSSAI. S-NSSAI included in rejected NSSAI may be expressed as rejected S-NSSAI.
また、5GMM-CONNECTED mode with RRC inactive indicationは、RRCレイヤが非有効化(inactive)な状態にも関わらず、NASレイヤの状態がコネクティッド状態であることを示す状態である。言い換えると、5GMM-CONNECTED mode with RRC inactive indicationは、NASシグナリングコネクション、及び/又はNASシグナリングコネクションのコンテキストを維持しつつ、無線ベアラが解放された状態である。
In addition, 5GMM-CONNECTED mode with RRC inactive indication is a state indicating that the state of the NAS layer is in the connected state even though the RRC layer is inactive (inactive). In other words, 5GMM-CONNECTED mode with RRC inactive indication is a state in which the wireless bearer is released while maintaining the context of the NAS signaling connection and / or the NAS signaling connection.
尚、5GMM-CONNECTED mode with RRC inactive indicationのサポートとは、RRCレイヤが非有効化になったことを示す通知を下位レイヤから受けた場合でも、NASレイヤの状態をコネクティッド状態に維持することがサポートされていることを意味してもよい。さらに、5GMM-CONNECTED mode with RRC inactive indicationの使用とは、RRCレイヤが非有効化になったことを示す通知を下位レイヤから受けた場合でも、NASレイヤの状態をコネクティッド状態に維持することを意味してもよい。
In addition, support for 5GMM-CONNECTED mode with RRC inactive indication means that the state of the NAS layer can be maintained in the connected state even when a notification indicating that the RRC layer has been disabled is received from the lower layer. It may mean that it is supported. Furthermore, the use of 5GMM-CONNECTED mode with RRC inactive indication means that the state of the NAS layer is maintained in the connected state even when the notification indicating that the RRC layer has been disabled is received from the lower layer. It may mean.
トラッキングエリアは、コアネットワークが管理する、UE_A10の位置情報で表すことが可能な単数又は複数の範囲である。トラッキングエリアは、複数のセルで構成されもよい。さらに、トラッキングエリアは、ページング等の制御メッセージがブロードキャストされる範囲でもよいし、UE_A10がハンドオーバー手続きをせずに移動できる範囲でもよい。さらに、トラッキングエリアは、ルーティングエリアでもよいし、ロケーションエリアでもよいし、これらと同様のものであればよい。以下、トラッキングエリアはTA(Tracking Area)であってもよい。
The tracking area 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. Hereinafter, the tracking area may be TA (Tracking Area).
TAリストは、ネットワークがUE_A10に割り当てた一又は複数のTAが含まれるリストである。なお、UE_A10は、TAリストに含まれる一又は複数のTA内を移動している間は、トラッキングエリア更新手続きを実行することなく移動することができてよい。言い換えると、UE_A10は、TAリストは、UE_A10がトラッキングエリア更新手続きを実行することなく移動できるエリアを示す情報群であってよい。尚、TAリストは、一又複数のTAI (Tracking area identity) で構成されるTAIリストと表現されてもよく、以下、TAIリストは、TAリストを指してもよい。
The TA list is a list that includes one or more TAs assigned to UE_A10 by the network. Note that UE_A10 may be able to move without executing the tracking area update procedure while moving within one or more TAs included in the TA list. In other words, the UE_A10 may be a group of information indicating the area in which the TA list can be moved without performing the tracking area update procedure. The TA list may be expressed as a TAI list composed of a plurality of TAIs (Tracking area identities). Hereinafter, the TAI list may refer to a TA list.
UE IDとは、UEを識別する為の情報である。具体的に、例えば、UE IDは、SUCI(SUbscription Concealed Identifier)、又はSUPI(Subscription Permanent Identifier )、又はGUTI(Globally Unique Temporary Identifier)、又はIMEI(International Mobile Subscriber Identity)、又はIMEISV(IMEI Software Version)又は、TMSI(Temporary Mobile Subscriber Identity )であってもよい。又は、UE IDはアプリケーションまたはネットワーク内で設定されたその他の情報であってもよい。さらに、UE IDは、ユーザを識別する為の情報であってもよい。
UE ID is information for identifying the UE. Specifically, for example, the UE ID is SUCI (SUbscription Concealed Identifier), SUPI (Subscription Permanent Identifier), GUTI (Globally Unique Temporary Identifier), IMEI (International Mobile Subscriber Identity), or IME ISV (IMEI Software Version). Alternatively, it may be TMSI (Temporary Mobile Subscriber Identity). Alternatively, the UE ID may be other information set in the application or network. Further, the UE ID may be information for identifying the user.
また、Non-Public Network(NPN)は、一般利用を目的とせず、企業など私的利用など、特定の利用者が特定の目的で利用する非公開ネットワークである。NPNにはStand-alone Non-Public Network (SNPN)とPublic network integrated NPNの2種類が存在する。なお、以下にNPNと記載した場合、SNPNとPublic network integrated NPNの両方を意味してよい。SNPNは、NPNオペレータにより運用され、PLMNにより提供される機能部からの影響を受けない。つまり、言い換えるとSNPNは一般に公開されるPLMNとは独立したNPN専用のネットワークである。また、Public network integrated NPNはPLMNの機能部を利用して実行される。つまり、言い換えると Public network integrated NPNは、PLMN内で仮想的に実現するNPNである。
In addition, Non-Public Network (NPN) is a private network that is used by specific users for specific purposes, such as private use such as companies, not for general use. There are two types of NPN: Stand-alone Non-Public Network (SNPN) and Public network integrated NPN. When NPN is described below, it may mean both SNPN and Public network integrated NPN. The SNPN is operated by the NPN operator and is unaffected by the functional parts provided by PLMN. In other words, SNPN is an NPN-only network that is independent of PLMN, which is open to the public. In addition, Public network integrated NPN is executed by using the functional part of PLMN. In other words, the Public network integrated NPN is an NPN that is virtually realized within PLMN.
さらに、Public network integrated NPNの詳細な説明をする。Public network integrated NPNは、PLMNを介して作成可能なNPNである。Public network integrated NPNは例えば、ネットワークスライスの機能を用いて実現してもよい。具体的には、NPNのために割り当てられたネットワークスライスを用いることにより実現可能である。Public network integrated NPNは、S-NSSAIで識別されてもよいし、S-NSSAIとCAG IDの組み合わせにより識別されてもよい。
Furthermore, a detailed explanation of Public network integrated NPN will be given. Public network integrated NPN is an NPN that can be created via PLMN. The public network integrated NPN may be realized by using, for example, the network slice function. Specifically, this can be achieved by using the network slices assigned for the NPN. The public network integrated NPN may be identified by S-NSSAI or by a combination of S-NSSAI and CAG ID.
また、CAG(Closed Access Groups) IDは、CAGに関連付けられた1又は複数のセルに接続が許可された登録者(subscriber)のグループを識別する情報であり、CAGは、CAG IDにより識別されるグループである。CAGは、Public network integrated NPNを、ネットワークスライスで実現する際に利用されるグループである。CAGは、NPNの為に割り当てられたネットワークスライスに、NPNが許可されないUEから、アクセスを試みないようにするために使用される。CAG IDは、PLMN内でユニークな情報である。
The CAG (Closed Access Groups) ID is information that identifies a group of subscribers who are allowed to connect to one or more cells associated with the CAG, and the CAG is identified by the CAG ID. It is a group. CAG is a group used to realize Public network integrated NPN with network slices. CAG is used to prevent network slices assigned for NPN from attempting access from UEs that do not allow NPN. The CAG ID is unique information within PLMN.
また、NID(Network identifier)は、ネットワークを識別する情報である。NPNは、PLMNとNIDの組み合わせにより識別されてもよい。NIDは、SNPN内でユニークな情報であってもよいし、世界的にユニークな情報であってもよい。
In addition, NID (Network identifier) is information that identifies the network. NPN may be identified by a combination of PLMN and NID. The NID may be unique information within the SNPN or may be globally unique information.
ここで、NPNを示す情報は、S-NSSAI、及び/又はNID、及び/又はCAG ID、及び/又はNID、及び/又はDNN、及び/又はPLMN IDのうち、1または複数で識別される情報であってよい。具体的には、例えば、NPNを示す情報は、S-NSSAIと、CAG IDで識別される情報であってもよいし、PLMN IDとNIDで識別される情報であってもよいし、S-NSSAIとNIDで識別される情報であってもよいし、S-NSSAIとDNNで識別される情報であってもよい。または、NPNを示す情報は、S-NSSAIであってもよい。なお、「NPNを示す情報に上記の情報が含まれる場合」とは、「NPNを示す情報が上記の情報である場合」を含む。例えば、「NPNを示す情報にS-NSSAIが含まれる場合」とは「NPNを示す情報がS-NSSAIである場合」を含める。
Here, the information indicating NPN is information identified by one or more of S-NSSAI and / or NID, and / or CAGID, and / or NID, and / or DNN, and / or PLMNID. It may be. Specifically, for example, the information indicating NPN may be information identified by S-NSSAI and CAGID, information identified by PLMNID and NID, or S-. The information may be identified by NSSAI and NID, or may be information identified by S-NSSAI and DNN. Alternatively, the information indicating the NPN may be S-NSSAI. In addition, "when the information indicating NPN includes the above information" includes "when the information indicating NPN is the above information". For example, "when the information indicating NPN includes S-NSSAI" includes "when the information indicating NPN is S-NSSAI".
また、NPN内で高い優先度で接続可能なUEとは、特定のNPN内でアクセス制御の対象外として優先的に接続を要求できる、及び制御メッセージの送受信を制限されないUEである。具体的に、例えば、NPN内で高い優先度で接続可能なUEは、AMF及び/又はSMFがMM(Mobility Management)信号の輻輳またはDNN(Data Network Name)ベースの輻輳及び/又はネットワークスライスベースの輻輳を検知し、輻輳制御手続きを開始している状態であっても、輻輳を理由に要求を拒絶されないUEであってよい。
A UE that can be connected with a high priority within the NPN is a UE that can preferentially request a connection within a specific NPN as a target of access control and is not restricted in sending and receiving control messages. Specifically, for example, UEs that can be connected with high priority within the NPN are AMF and / or SMF based on MM (Mobility Management) signal congestion or DNN (Data Network Name) -based congestion and / or network slice-based. Even in the state where congestion is detected and the congestion control procedure is started, the UE may be a UE whose request is not rejected because of congestion.
なお、本稿では、NPN内で高い優先度で接続可能なUEは、NPN内で高い優先度で接続が許可されているUEや、NPN内で高い優先度で接続が可能なUEや、NPN内で高い優先度で設定されているUEや、NPN内で高い優先度で登録されているUEや、NPN内で優先度が高いUEとして設定されているUEや、NPN内で優先度が高いUEとして登録されているUE、と表現される場合がある。さらに、このNPNは、UEが高い優先度で接続が許可されるNPNと表現される場合がある。
In this paper, UEs that can be connected with high priority in NPN are UEs that are allowed to connect with high priority in NPN, UEs that can be connected with high priority in NPN, and UEs in NPN. UE set with high priority in, UE registered with high priority in NPN, UE set as high priority UE in NPN, UE with high priority in NPN It may be expressed as UE, which is registered as. In addition, this NPN may be referred to as an NPN where the UE is allowed to connect with a higher priority.
次に、本実施形態における識別情報について説明する。
Next, the identification information in this embodiment will be described.
第1の情報は、要求する1又は複数のNPNを示す情報であってよい。第1の情報は、S-NSSAI、及び/又はrequested NSSAIに含まれるS-NSSAI、及び/又はNID、及び/又はCAG ID、及び/又はNID、及び/又はDNNのうち、1以上で識別される情報であってよい。さらに、第1の識別情報は、複数の識別情報の組み合わせを、複数組含む情報群であってよく、具体的に例えば、第1の識別情報は、複数のS-NSSAIとCAG IDの組み合わせを含む情報群であってよい。第1の情報は、UEが要求するS-NSSAIがNPNのためのスライスであることを示す情報であってもよい。
The first information may be information indicating one or more required NPNs. The first information is identified by one or more of S-NSSAI and / or S-NSSAI and / or NID contained in requested NSSAI, and / or CAGID and / or NID, and / or DNN. Information may be used. Further, the first identification information may be an information group including a plurality of sets of combinations of a plurality of identification information. Specifically, for example, the first identification information may be a combination of a plurality of S-NSSAI and CAG ID. It may be a group of information including. The first information may be information indicating that the S-NSSAI requested by the UE is a slice for NPN.
第2の情報は、UEにより要求されるNPN内で優先度が高いUEであることを示す情報、及び/又はUEにより要求されるNPN内で優先度が高いUEとして登録されることを要求することを示す情報であってよい。または、第2の識別情報は、UEにより要求されるNPN内で優先度が高いUEであるか否かを示す情報、及び/又はUEにより要求されるNPN内で優先度が高いUEとして登録されることを要求するか否かを示す情報であってよい。第2の情報は、第1の情報と紐づけられていてよい。第1の情報が、複数のNPNを示す情報である場合、第2の識別情報は、第1の識別情報に含まれる、それぞれのNPNに対応づけられていてもよい。例えば、第1の識別情報に、複数のS-NSSAIが含まれる場合、S-NSSAIごとに、UEがS-NSSAI内で高い優先度で接続が許可されているか否かを示してもよい。なお、ここで、NPN内で優先度が高いUEとは、NPN内で高い優先度で接続可能なUEと同義であってよい。第3の識別情報は、UEがNPNの接続を要求することを示す情報であってよい。第3の識別情報は、UEが要求するNPNを示す情報であってよく、例えば、第1の識別情報であってよい。具体的には、第3の識別情報は、UEが接続を要求するNPNのためのネットワークスライスを示す情報であってよく、requested NSSAIに含まれるS-NSSAIであってもよい。また、第3の識別情報は、UEがNPNへの接続が許可されている事を示す情報であってもよく、例えば第4の識別情報であってもよい。また、第3の識別情報は、UEがNPNへの接続を要求することを示すフラグであってもよい。また、第3の識別情報は、これらの情報のうち複数を組み合わせた情報であってもよい。
The second information requires information indicating that the UE is a high priority UE within the NPN required by the UE and / or being registered as a high priority UE within the NPN required by the UE. It may be information indicating that. Alternatively, the second identification information is registered as information indicating whether or not the UE has a higher priority in the NPN required by the UE, and / or as a UE with a higher priority in the NPN requested by the UE. It may be information indicating whether or not to request that. The second information may be associated with the first information. When the first information is information indicating a plurality of NPNs, the second identification information may be associated with each NPN included in the first identification information. For example, when a plurality of S-NSSAIs are included in the first identification information, each S-NSSAI may indicate whether or not the UE is allowed to connect within the S-NSSAI with a high priority. Here, a UE having a high priority in the NPN may be synonymous with a UE that can be connected with a high priority in the NPN. The third identification information may be information indicating that the UE requests an NPN connection. The third identification information may be information indicating the NPN required by the UE, and may be, for example, the first identification information. Specifically, the third identification information may be information indicating a network slice for the NPN for which the UE requests a connection, and may be S-NSSAI included in requested NSSAI. Further, the third identification information may be information indicating that the UE is permitted to connect to the NPN, and may be, for example, the fourth identification information. The third identification information may also be a flag indicating that the UE requests a connection to the NPN. Further, the third identification information may be information obtained by combining a plurality of these pieces of information.
第4の識別情報は、UEの能力情報(UE capability)であってよい。第4の識別情報は、UEがNPNへの接続が許可されている事を示す情報であってよく、UEが接続を許可される1又は複数のNPNを示す情報であってもよい。さらに、第4の識別情報は、要求するNPN内で高い優先度で接続が許可されるUEとして動作可能であることを示す情報であってよい。第14の識別情報は、UEがNPNに関する機能をサポートする事を示す情報であってよい。
The fourth identification information may be UE capability information (UE capability). The fourth identification information may be information indicating that the UE is permitted to connect to the NPN, and may be information indicating one or more NPNs to which the UE is permitted to connect. Further, the fourth identification information may be information indicating that the UE can operate as a UE that is allowed to connect with a high priority within the requested NPN. The fourteenth identification information may be information indicating that the UE supports functions related to NPN.
第11の識別情報は、UEが高い優先度で接続するUEとして設定されている、NPNを示す情報のリストであってよい。具体的には、第11の識別情報は1又は複数のNPNを示す情報により構成されるリストであってよい。第11の識別は、UE contextに含まれる情報であってよい。第11の識別情報は、AMFがUDMから取得した情報、又はAMFがUDMから取得した情報に基づき構成する情報であってよい。第11の識別情報は、UEにより要求されたNPN内で高い優先度で接続する事が許可された事を示す情報であってよい。
The eleventh identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the eleventh identification information may be a list composed of information indicating one or more NPNs. The eleventh identification may be the information contained in the UE context. The eleventh identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The eleventh identification information may be information indicating that the connection is permitted with a high priority within the NPN requested by the UE.
第12の識別情報は、rejected NSSAIを示す情報、及び、輻輳により拒絶する事を示す理由値(cause value)であってよい。第12の識別情報は、rejected NSSAIを示す情報とは別の識別情報であってよく、その場合、第12の識別情報は輻輳により拒絶する事を示す理由値(cause)であってよく、rejected NSSAIに含まれるS-NSSAIと紐づけられていて良い。
The twelfth identification information may be information indicating rejected NSSAI and a reason value (cause value) indicating rejection due to congestion. The twelfth identification information may be identification information different from the information indicating rejected NSSAI, in which case the twelfth identification information may be a reason value (cause) indicating rejection due to congestion, and is rejected. It may be associated with S-NSSAI included in NSSAI.
第13の識別情報は、back off timerの値を示す情報である。AMFは、UEとネットワークスライスとに紐づけて第13の識別情報を記憶していてもよい。第13の識別情報は、rejected NSSAIと紐づいて記憶されてよい。
The thirteenth identification information is information indicating the value of the back off timer. The AMF may store the thirteenth identification information in association with the UE and the network slice. The thirteenth identification information may be stored in association with rejected NSSAI.
第14の識別情報は、UEがNPNへの接続が許可された事を示す情報である。第14の識別情報は、UEが許可されたNPNを示す情報であってよい。NPNを示す情報にS-NSSAIが含まれる場合、第14の識別情報は更に、allowed NSSAIに含まれるS-NSSAIがNPNの為のS-NSSAIであることを示す情報であってもよい。第14の識別情報は、S-NSSAIに含まれるSSTまたはSDであってもよいし、allowed NSSAIに含まれるS-NSSAIであってもよい。第14の識別情報は、allowed NSSAIに含まれるS-NSSAIに紐づけられた情報であってもよい。
The 14th identification information is information indicating that the UE is permitted to connect to the NPN. The fourteenth identification information may be information indicating the NPN for which the UE is permitted. When S-NSSAI is included in the information indicating NPN, the 14th identification information may be further information indicating that S-NSSAI contained in allowed NSSAI is S-NSSAI for NPN. The 14th identification information may be SST or SD included in S-NSSAI, or may be S-NSSAI included in allowed NSSAI. The 14th identification information may be information associated with S-NSSAI included in allowed NSSAI.
第15の識別情報は、ネットワークの能力情報(UE capability)であってよい。第15の識別情報は、ネットワークがNPNへの接続をサポートする事を示す情報であってよい。例えばNPNがS-NSSAIで識別される場合、第15の識別情報は、ネットワークがNPNの為のS-NSSAIへの接続をサポートしない事を示す。第15の識別情報は、rejected NSSAIに含まれる理由値(cause)であってよい。
The fifteenth identification information may be network capability information (UE capability). The fifteenth identification information may be information indicating that the network supports the connection to the NPN. For example, if the NPN is identified by S-NSSAI, the fifteenth identification information indicates that the network does not support connecting to S-NSSAI for NPN. The fifteenth identification information may be a reason value (cause) included in rejected NSSAI.
第21の識別情報は、UEが要求するNPNにおいて、UEが高い優先度で接続が可能なUEではない事を示す情報である。第21の識別情報は、拒絶理由を示す理由値(Cause value)であってよい。第21の識別情報は、拒絶するNPNを示す情報を含めてもよい。
The 21st identification information is information indicating that the UE is not a UE that can be connected with a high priority in the NPN requested by the UE. The 21st identification information may be a reason value (Cause value) indicating the reason for refusal. The 21st identification information may include information indicating the NPN to be rejected.
第22の識別情報は、UEが高い優先度で接続するUEとして設定されている、NPNを示す情報のリストであってよい。具体的には、第22の識別情報は1又は複数のNPNを示す情報により構成されるリストであってよい。第22の識別は、UE contextに含まれる情報であってよい。第22の識別情報は、AMFがUDMから取得した情報、又はAMFがUDMから取得した情報に基づき構成する情報であってよい。第22の識別情報は、UEにより要求されたNPN内で高い優先度で接続する事が拒絶された事を示す情報であってよい。
The 22nd identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the 22nd identification information may be a list composed of information indicating one or more NPNs. The 22nd identification may be the information contained in the UE context. The 22nd identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The 22nd identification information may be information indicating that the connection with high priority is refused within the NPN requested by the UE.
第31の識別情報は、UEが要求するNPNで、高い優先度で接続可能なUEであることを示す情報である。第31の識別情報は、要求する1または複数のNPNを示す情報を含めてもよい。第31の識別情報は、サービスタイプを示す情報であってもよい。具体的には、第31の識別情報は、UEが高い優先度で接続可能なUEであることを意味するサービスタイプであってもよい。
The 31st identification information is the NPN requested by the UE and is information indicating that the UE can be connected with a high priority. The thirty-first identification information may include information indicating one or more required NPNs. The thirty-first identification information may be information indicating a service type. Specifically, the 31st identification information may be a service type meaning that the UE is a UE that can be connected with a high priority.
第41の識別情報は、要求するNPNを示す情報である。第41の識別情報は、UEがNPNへのPDUセッションの確立を要求することを示す情報であってもよい。第41の識別情報は、要求するNPNごとの、ネットワークにNPNの為の追加の認証/承認手続きの実行を要求する為の情報であってもよい。なお、第41の識別情報は、要求するNPNを示す情報と、要求するNPNごとの、ネットワークにNPNの為の追加の認証/承認手続きの実行を要求する為の情報を異なる情報とし使用してもよい。
The 41st identification information is information indicating the required NPN. The 41st identification information may be information indicating that the UE requests the establishment of a PDU session to the NPN. The 41st identification information may be information for requesting the network to perform an additional authentication / approval procedure for the NPN for each requested NPN. For the 41st identification information, the information indicating the required NPN and the information for requesting the network to execute an additional authentication / approval procedure for the NPN for each requested NPN are used as different information. May be good.
第42の識別情報は、UEが、要求するNPN内で高い優先度で接続が可能なUEとして設定及び/又は登録されたUEであることを示す情報である。第42の識別情報は第41の識別情報と紐づけられていてもよい。第42の識別情報は、ネットワークにNPNの為の認証/承認手続きの実行を要求する為の情報であってもよい。
The 42nd identification information is information indicating that the UE is a UE set and / or registered as a UE that can be connected with a high priority within the requested NPN. The 42nd identification information may be associated with the 41st identification information. The 42nd identification information may be information for requesting the network to execute an authentication / approval procedure for NPN.
第51の識別情報は、PDUセッションの確立が許可されたNPNを示す情報である。第51の識別情報は、確立されたPDUセッションがNPNへ確立されたPDUセッション、及び/又はNPNを介して確立されたPDUセッションであることを示す情報であってもよい。第51の識別情報は、NPNを示す情報であってよい。
The 51st identification information is information indicating the NPN for which the establishment of a PDU session is permitted. The 51st identification information may be information indicating that the established PDU session is a PDU session established to the NPN and / or a PDU session established via the NPN. The 51st identification information may be information indicating NPN.
第52の識別情報は、NPNの為の追加の認証/承認手続きの実行の結果であってよい。第52の識別情報は、UEが要求するNPNの為の追加の認証/承認手続きの結果、NPNへの接続が許可された事を示す情報であってよい。
The 52nd identification information may be the result of performing additional authentication / approval procedures for NPN. The 52nd identification information may be information indicating that the connection to the NPN has been permitted as a result of the additional authentication / approval procedure for the NPN requested by the UE.
第61の識別情報は、UEが高い優先度で接続するUEとして設定されている、NPNを示す情報のリストであってよい。具体的には、第61の識別情報は1又は複数のNPNを示す情報により構成されるリストであってよい。第61の識別は、UE contextに含まれる情報であってよい。第61の識別情報は、AMFがUDMから取得した情報、又はAMFがUDMから取得した情報に基づき構成する情報であってよい。第61の識別情報は、UEが要求するNPN内で高い優先度で接続できるUEではない事を示す情報であってもよい。第61の識別情報は、拒絶の理由を示す理由値(Cause value)であってもよい。
The 61st identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the 61st identification information may be a list composed of information indicating one or more NPNs. The 61st identification may be the information contained in the UE context. The 61st identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The 61st identification information may be information indicating that the UE is not a UE that can be connected with a high priority within the NPN requested by the UE. The 61st identification information may be a reason value (Cause value) indicating the reason for refusal.
第62の識別情報は、UEが要求するNPNの為の追加の認証/承認手続きにより、UEが要求するNPNの為の追加の認証/承認手続きの結果、NPNへの接続が許可されないことを示す情報である。第62の識別情報は、NPNへの接続が許可されないことに、UEの要求を拒絶する事を示す理由値(Cause value)であってよい。
The 62nd identification information indicates that the additional authentication / approval procedure for the NPN required by the UE does not allow the connection to the NPN as a result of the additional authentication / approval procedure for the NPN requested by the UE. Information. The 62nd identification information may be a cause value indicating that the UE's request is rejected because the connection to the NPN is not permitted.
第71の識別情報は、UEが高い優先度で接続するUEとして設定されている、NPNを示す情報のリストであってよい。具体的には、第71の識別情報は1又は複数のNPNを示す情報により構成されるリストであってよい。第71の識別は、UE contextに含まれる情報であってよい。第61の識別情報は、AMFがUDMから取得した情報、又はAMFがUDMから取得した情報に基づき構成する情報であってよい。第71の識別情報は、UEへUEが高い優先度で接続するUEとして設定されているNPNのリストに、追加及び/又は削除及び/又は変更が発生した事を通知する情報であってよい。
The 71st identification information may be a list of information indicating NPN, which is set as a UE to which the UE connects with a high priority. Specifically, the 71st identification information may be a list composed of information indicating one or more NPNs. The 71st identification may be the information contained in the UE context. The 61st identification information may be information acquired by AMF from UDM or information configured based on information acquired by AMF from UDM. The 71st identification information may be information notifying that an addition and / or deletion and / or change has occurred to the list of NPNs set as UEs to which the UE connects to the UE with high priority.
尚、各装置は、報知情報及び/又はRRC手続き及び/又はコアネットワークへの登録手続き及び/又は緊急呼のためのサービス要求手続きにおいて、各装置の各種能力情報及び/又は各種要求情報を交換及び/又は取得してもよい。
In addition, each device exchanges various capability information and / or various request information of each device in the notification information and / or RRC procedure and / or the registration procedure in the core network and / or the service request procedure for emergency call. / Or may be obtained.
また、本手続きに関わる各装置は、本手続きで説明する各制御メッセージを送受信することにより、各制御メッセージに含まれる1以上の識別情報を送受信し、送受信した各識別情報をコンテキストとして記憶してもよい。
In addition, each device involved in this procedure sends and receives one or more identification information included in each control message by transmitting and receiving each control message described in this procedure, and stores each transmitted and received identification information as a context. May be good.
尚、簡単化のために、サービス要求手続き及び/又はPDUセッション確立手続き及び/又はIMS登録手続き及び/又はIMS緊急呼接続手続きを含めて緊急呼接続処理と称することがある。
For simplification, the service request procedure and / or the PDU session establishment procedure and / or the IMS registration procedure and / or the IMS emergency call connection procedure may be referred to as the emergency call connection process.
[3.1. 各実施形態で用いられる手続きの説明]
次に、各実施形態で用いられる手続きについて説明する。尚、各実施形態で用いられる手続きには、登録手続き(Registration procedure)、サービス要求手続き(Service request procedure)、PDUセッション確立手続き(PDU session establishment procedure)、PDUセッション変更手続き(PDU session management procedure)、UE設定更新手続き(Generic UE configuration update procedure)が含まれる。以下、各手続きについて説明していく。 [3.1. Explanation of procedures used in each embodiment]
Next, the procedure used in each embodiment will be described. The procedures used in each embodiment include a registration procedure, a service request procedure, a PDU session establishment procedure, a PDU session management procedure, and a PDU session management procedure. Includes the Generic UE configuration update procedure. Each procedure will be explained below.
次に、各実施形態で用いられる手続きについて説明する。尚、各実施形態で用いられる手続きには、登録手続き(Registration procedure)、サービス要求手続き(Service request procedure)、PDUセッション確立手続き(PDU session establishment procedure)、PDUセッション変更手続き(PDU session management procedure)、UE設定更新手続き(Generic UE configuration update procedure)が含まれる。以下、各手続きについて説明していく。 [3.1. Explanation of procedures used in each embodiment]
Next, the procedure used in each embodiment will be described. The procedures used in each embodiment include a registration procedure, a service request procedure, a PDU session establishment procedure, a PDU session management procedure, and a PDU session management procedure. Includes the Generic UE configuration update procedure. Each procedure will be explained below.
尚、各実施形態では、図2に記載されているように、HSSとUDM、PCFとPCRF、SMFとPGW-C、UPFとPGW-Uが、それぞれ同一の装置(つまり、同一の物理的なハードウェア、又は同一の論理的なハードウェア、又は同一のソフトウェア)として構成されている場合を例にとって説明する。しかし、本実施形態に記載される内容は、これらが異なる装置(つまり、異なる物理的なハードウェア、又は異なる論理的なハードウェア、又は異なるソフトウェア)として構成される場合にも適用可能である。例えば、これらの間で、直接データの送受信を行ってもよいし、AMF、MME間のN26インターフェースを介してデータを送受信してもよいし、UEを介してデータを送受信してもよい。
In each embodiment, as shown in FIG. 2, HSS and UDM, PCF and PCRF, SMF and PGW-C, UPF and PGW-U are the same device (that is, the same physical device). The case where it is configured as hardware, the same logical hardware, or the same software) will be described as an example. However, the content described in this embodiment is also applicable when they are configured as different devices (ie, different physical hardware, or different logical hardware, or different software). For example, data may be transmitted / received directly between them, data may be transmitted / received via the N26 interface between AMF and MME, or data may be transmitted / received via UE.
[3.2.登録手続き]
まず、登録手続き(Registration procedure)について、図6を用いて説明する。以下、本手続きとは登録手続きを指す。登録手続きは、UEが主導してアクセスネットワーク_B、及び/又はコアネットワーク_B、及び/又はDNへ登録する為の手続きである。UEは、ネットワークに登録していない状態であれば、例えば、電源投入時等の任意のタイミングで本手続きを実行することができる。言い換えると、UEは、非登録状態(RM-DEREGISTERED state)であれば任意のタイミングで本手続きを開始できる。また、各装置(特にUEとAMF)は、登録手続きの完了に基づいて、登録状態(RM-REGISTERED state)に遷移することができる。 [3.2. Registration procedure]
First, the registration procedure will be described with reference to FIG. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering with the access network_B and / or the core network_B and / or the DN. The UE can execute this procedure at any time, for example, when the power is turned on, as long as it is not registered in the network. In other words, the UE can start this procedure at any time if it is in the unregistered state (RM-DEREGISTERED state). In addition, each device (particularly UE and AMF) can transition to the registration state (RM-REGISTERED state) based on the completion of the registration procedure.
まず、登録手続き(Registration procedure)について、図6を用いて説明する。以下、本手続きとは登録手続きを指す。登録手続きは、UEが主導してアクセスネットワーク_B、及び/又はコアネットワーク_B、及び/又はDNへ登録する為の手続きである。UEは、ネットワークに登録していない状態であれば、例えば、電源投入時等の任意のタイミングで本手続きを実行することができる。言い換えると、UEは、非登録状態(RM-DEREGISTERED state)であれば任意のタイミングで本手続きを開始できる。また、各装置(特にUEとAMF)は、登録手続きの完了に基づいて、登録状態(RM-REGISTERED state)に遷移することができる。 [3.2. Registration procedure]
First, the registration procedure will be described with reference to FIG. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering with the access network_B and / or the core network_B and / or the DN. The UE can execute this procedure at any time, for example, when the power is turned on, as long as it is not registered in the network. In other words, the UE can start this procedure at any time if it is in the unregistered state (RM-DEREGISTERED state). In addition, each device (particularly UE and AMF) can transition to the registration state (RM-REGISTERED state) based on the completion of the registration procedure.
さらに、登録手続きは、ネットワークにおけるUEの位置登録情報を更新する、及び/又は、UEからネットワークへ定期的にUEの状態を通知する、及び/又は、ネットワークにおけるUEに関する特定のパラメータを更新する為の手続きであってもよい。
In addition, the registration procedure is to update the UE location registration information in the network and / or to periodically notify the network of the UE status from the UE and / or to update certain parameters about the UE in the network. It may be the procedure of.
UEは、TAを跨ぐモビリティをした際に、登録手続きを開始してもよい。言い換えると、UEは、保持しているTAリストで示されるTAとは異なるTAに移動した際に、登録手続きを開始してもよい。さらに、UEは、実行しているタイマが満了した際に本手続きを開始してもよい。さらに、UEは、PDUセッションの切断や無効化が原因で各装置のコンテキストの更新が必要な際に登録手続きを開始してもよい。さらに、UEは、UEのPDUセッション確立に関する、能力情報、及び/又はプリファレンスに変化が生じた場合、登録手続きを開始してもよい。さらに、UEは、定期的に登録手続きを開始してもよい。さらに、UEは、UE設定更新手続きの完了に基づいて、又は登録手続きの完了に基づいて、又はPDUセッション確立手続きの完了に基づいて、又はPDUセッションマネジメント手続きの完了に基づいて、又は各手続きでネットワークから受信した情報に基づいて、登録手続きを開始してもよい。尚、UEは、これらに限らず、任意のタイミングで登録手続きを実行することができる。
The UE may start the registration procedure when it has mobility across TAs. In other words, the UE may initiate the registration process when it moves to a TA that is different from the TA shown in the TA list it holds. In addition, the UE may start this procedure when the running timer expires. 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 the ability 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. In addition, the UE may be based on the completion of the UE configuration update procedure, or on the basis of the completion of the registration procedure, or on the basis of the completion of the PDU session establishment procedure, or on the basis of the completion of the PDU session management procedure, or in each procedure. The registration procedure may be initiated based on the information received from the network. The UE is not limited to these, and can execute the registration procedure at any timing.
まず、UE_A10が登録手続きを開始する前に、5GAN120(又はgNB_A122)は、近隣のUEに対してブロードキャスト情報を送信する(S601)。ブロードキャスト情報は、SIB(System Information Block)であってもよい。5GAN120(又はgNB_A122)は、ブロードキャスト情報に、PLMN ID及び/又はCAG ID及び/又はNIDを含めて送信してよい。なお、CAG ID及びNIDは、PLMN IDと対応付けられていてもよい。具体的に、例えば、5GAN120(又はgNB_A122)は、SNPNの為のアクセスネットワーク内の装置である場合、5GAN120(又はgNB_A122)はNPNの為のPLMN IDと、1又は複数のNIDをブロードキャスト情報に含め、5GAN120(又はgNB_A122)のセル内にいるUEに送信してよい。
First, before UE_A10 starts the registration procedure, 5GAN120 (or gNB_A122) sends broadcast information to neighboring UEs (S601). The broadcast information may be SIB (System Information Block). 5GAN120 (or gNB_A122) may transmit the broadcast information including PLMNID and / or CAGID and / or NID. The CAG ID and NID may be associated with the PLMN ID. Specifically, for example, if 5GAN120 (or gNB_A122) is a device in the access network for SNPN, 5GAN120 (or gNB_A122) includes the PLMN ID for NPN and one or more NIDs in the broadcast information. , 5GAN120 (or gNB_A122) may be sent to the UE in the cell.
または、5GAN120(又はgNB_A122)が、Public network integrated NPNの為のアクセスネットワーク内の装置である場合、gNB_A122又はeNB_B145はPublic network integrated NPNを含むPLMNを示すPLMN IDと1又は複数のCAG IDをブロードキャスト情報に含め5GAN120(又はgNB_A122)のセル内にいるUEに送信してよい。
Or, if 5GAN120 (or gNB_A122) is a device in the access network for Public network integrated NPN, gNB_A122 or eNB_B145 broadcasts PLMN ID indicating PLMN including Public network integrated NPN and one or more CAG IDs. May be sent to the UE in the cell of 5GAN120 (or gNB_A122) included in.
また、5GAN120(又はgNB_A122)が、NPN専用のアクセスネットワークではない場合、つまり言い換えれば、NPNと他のPLMNでアクセスネットワークを共有する場合、5GAN120(又はgNB_A122)は、ブロードキャスト情報に、CAG ID及び/又はNIDを含めずに5GAN120(又はgNB_A122)のセル内にいるUEに送信してよい。
Also, if the 5GAN120 (or gNB_A122) is not an NPN-only access network, that is, if the NPN and another PLMN share an access network, the 5GAN120 (or gNB_A122) will include the CAG ID and / in the broadcast information. Alternatively, it may be sent to the UE in the cell of 5GAN120 (or gNB_A122) without including the NID.
UE_A10は、受信したブロードキャスト情報及び/又はブロードキャスト情報に含まれる1又は複数の情報に基づき、NPN及び/又はPLMNへの登録を要求することを決定し、以下の登録手続きを開始してもよい。
UE_A10 may decide to request registration with NPN and / or PLMN based on the received broadcast information and / or one or more pieces of information contained in the broadcast information, and may start the following registration procedure.
まず、UEは、AMFに登録要求(Registration request)メッセージを送信することにより(S600)(S602)(S604)、登録手続きを開始する。具体的には、UEは、登録要求メッセージを含むRRCメッセージを、5G AN(又はgNB)に送信する(S600)。尚、登録要求メッセージは、N1インターフェース上で送受信されるNASメッセージである。また、RRCメッセージは、UEと5G AN(又はgNB)との間で送受信される制御メッセージであってよい。また、NASメッセージはNASレイヤで処理され、RRCメッセージはRRCレイヤで処理される。尚、NASレイヤはRRCレイヤよりも上位のレイヤである。
First, the UE starts the registration procedure by sending a registration request message to AMF (S600) (S602) (S604). Specifically, the UE sends an RRC message including a registration request message to 5GAN (or gNB) (S600). The registration request message is a NAS message sent and received on the N1 interface. Further, the RRC message may be a control message transmitted / received between the UE and 5GAN (or gNB). In addition, NAS messages are processed at the NAS layer, and RRC messages are processed at the RRC layer. The NAS layer is a higher layer than the RRC layer.
ここで、UEは、少なくとも第1から4の識別情報の内、1つ以上の識別情報を、登録要求メッセージ及び/又はRRCメッセージに含めて送信する事ができるが、これらとは異なる制御メッセージ、例えば、RRCレイヤよりも下位のレイヤ(例えば、MACレイヤ、RLCレイヤ、PDCPレイヤ)の制御メッセージに含めて送信してもよい。尚、UEは、これらの識別情報を、送信することで、UEが各機能をサポートしていることを示してもよいし、UEの要求を示してもよいし、これら両方を示してもよい。さらに、複数の識別情報が送受信される場合、これらの識別情報の2以上の識別情報は、1以上の識別情報として構成されてもよい。尚、各機能のサポートを示す情報と、各機能の使用の要求を示す情報は、同じ識別情報として送受信されてもよいし、異なる識別情報として送受信されてもよい。
Here, the UE can transmit at least one of the identification information of the first to the fourth identification information by including it in the registration request message and / or the RRC message, but a control message different from these. For example, it may be included in a control message of a layer lower than the RRC layer (for example, MAC layer, RLC layer, PDCP layer) and transmitted. By transmitting these identification information, the UE may indicate that the UE supports each function, may indicate a request of the UE, or may indicate both of them. .. Further, when a plurality of identification information is transmitted and received, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.
UEは、NPNへの接続を要求する場合及び/又はNPNへの接続を要求することを決定した場合及び/又はアプリケーションレイヤ等の上位レイヤからの要求に基づき接続先をNPNに選択した場合、第1の要求を送信してよい。UEは、要求するネットワークがNPNであることを認識せずに、第1の識別情報をネットワークに送信してもよい。第1の識別情報を送信することにより、UEは、AMFに登録要求メッセージに含まれるUE IDを用いて、第1の識別情報に示されるNPNへの接続の認証/承認手続きを開始させてもよい。また、第1の識別情報を送信することにより、UEは、AMFにUEの設定情報を確認させてもよい。具体的には、AMFは第1の識別情報の受信に基づき、UE及び要求するNPNに紐づいて、高い優先度で接続が許可されているか否かを確認してもよい。
When the UE requests a connection to the NPN and / or decides to request a connection to the NPN and / or selects the connection destination as the NPN based on a request from a higher layer such as the application layer, the first You may send 1 request. The UE may send the first identification information to the network without recognizing that the requesting network is NPN. By transmitting the first identification information, the UE can initiate the authentication / approval procedure for the connection to the NPN shown in the first identification information by using the UE ID included in the registration request message to AMF. Good. Further, by transmitting the first identification information, the UE may have the AMF confirm the setting information of the UE. Specifically, the AMF may confirm whether or not the connection is permitted with a high priority in association with the UE and the requested NPN based on the reception of the first identification information.
さらに、UEは、NPNへの接続を要求する場合、及び/又はUEが要求するNPN内で高い優先度で接続が許可されるUEとして設定されている場合、及び/又はUEが要求するNPN内で高い優先度で接続が許可されるUEとして登録されることを要求する場合、第2の識別情報を送信してもよい。なお、UEは、NPNへの接続を要求するが、要求するNPN内で高い優先度で接続するUEとして登録する事を要求しない場合、第2の識別情報を送信しなくてもよい。第2の識別情報を送信することで、UEは、AMFにUEが要求するNPN内で、高い優先度で接続が許可されているかを確認させてもよい。
In addition, if the UE requests a connection to an NPN and / or is configured as a UE that is allowed to connect with a higher priority within the NPN requested by the UE, and / or within the NPN requested by the UE. If you request to be registered as a UE that allows connections with high priority, you may send a second identification. If the UE requests connection to the NPN but does not require registration as a UE that connects with a high priority within the requested NPN, it is not necessary to transmit the second identification information. By transmitting the second identification information, the UE may have the AMF confirm whether the connection is permitted with a high priority within the NPN requested by the UE.
さらに、UEは、NPNの接続を要求する場合、第3の識別情報を送信してもよい。UEは、第3の識別情報を送信することにより、ネットワークにUEが要求するネットワークはNPNであることを示してもよい。第3の識別情報を送信することで、UEは、AMFに、UEが要求するネットワークスライスがNPNの為のネットワークスライスであるかを確認させてもよい。
Furthermore, the UE may send a third identification information when requesting an NPN connection. The UE may indicate to the network that the network requested by the UE is an NPN by transmitting a third identification information. By transmitting the third identification information, the UE may have the AMF confirm that the network slice requested by the UE is a network slice for NPN.
さらに、UEは、NPNへの接続を要求する場合、及び/又はUEがNPNへ接続する機能をサポートする場合、第4の識別情報を送信してもよい。第4の識別情報を送信することで、UEは、AMFに、ネットワークの能力情報(Network capability)を確認させてもよい。
Furthermore, the UE may send a fourth identification information if it requests a connection to the NPN and / or if the UE supports the ability to connect to the NPN. By transmitting the fourth identification information, the UE may have the AMF confirm the network capability information (Network capability).
なお、UEが記憶する第1から第4の識別情報は、UEが本手続き以前の手続きで取得した情報、及び/又はUEが本手続き以前の手続きで取得した情報に基づき生成された情報であってよい。具体的に、例えば第1の識別情報にS-NSSAIが含まれる場合、UEは本手続き以前の手続きにおいて、ネットワークからallowed NSSAIを受信しており、第1の識別情報に含まれるS-NSSAIは、記憶するallowed NSSAIに含まれるS-NSSAIであってよい。
The first to fourth identification information stored by the UE is the information acquired by the UE in the procedure before this procedure and / or the information generated by the UE based on the information acquired in the procedure before this procedure. You can. Specifically, for example, when S-NSSAI is included in the first identification information, the UE has received allowed NSSAI from the network in the procedure before this procedure, and the S-NSSAI included in the first identification information is , It may be S-NSSAI included in allowed NSSAI to be memorized.
なお、本手続き以前の手続きとは、例えば本手続きが、UEの位置登録情報を更新する、及び/又は、UEからネットワークへ定期的にUEの状態を通知する、及び/又は、ネットワークにおけるUEに関する特定のパラメータを更新する為の登録手続きである場合、本手続きより前に発生している登録手続きであってよい。
The procedure before this procedure is, for example, that this procedure updates the location registration information of the UE and / or periodically notifies the network of the status of the UE from the UE, and / or relates to the UE in the network. If it is a registration procedure for updating a specific parameter, it may be a registration procedure that has occurred before this procedure.
UEは、登録要求メッセージ及び/又は登録要求メッセージが含まれるRRCメッセージに第1から4の識別情報以外も含めてもよく、例えばUE ID及び/又はPLMN ID及び/又はrequested NSSAI及び/又はCAG ID及び/又はNIDを含めて送信してもよい。
The UE may include other than the identification information 1 to 4 in the registration request message and / or the RRC message including the registration request message, for example, UE ID and / or PLMN ID and / or requested NSSAI and / or CAG ID. And / or NID may be included in the transmission.
また、UEは、登録要求メッセージにSMメッセージ(例えば、PDUセッション確立要求メッセージ)を含めて送信することで、又は登録要求メッセージとともにSMメッセージ(例えば、PDUセッション確立要求メッセージ)を送信することで、登録手続き中にPDUセッション確立手続きを開始してもよい。
The UE may also include the SM message (eg, PDU session establishment request message) in the registration request message, or send the SM message (eg, PDU session establishment request message) together with the registration request message. The PDU session establishment procedure may be started during the registration procedure.
5G AN(又はgNB)は、登録要求メッセージを含むRRCメッセージを受信すると、登録要求メッセージを転送するAMFを選択する(S602)。尚、5G AN(又はgNB)は、登録要求メッセージ及び/又はRRCメッセージに含まれる情報に基づいて、AMFを選択することができる。具体的には、5G AN(又はgNB)は、第1から4の識別情報の内、少なくとも1つの識別情報に基づいて、UEが要求するNPN内のAMFを選択してもよい。例えば、5G AN(又はgNB)は、第1の識別情報に基づき、第1の識別情報に示されるNPNに含まれるAMFを選択してもよいし、第1の識別情報に示されるNPNをサポートするAMFを選択してもよい。なお、その場合、5G AN(又はgNB)とAMF間では予め、AMFが含まれる及び/又はAMFがサポートするNPNに関する情報の交換、又はAMFから5G AN(又はgNB)への通知が発生している。
When 5GAN (or gNB) receives an RRC message including a registration request message, it selects the AMF to which the registration request message is forwarded (S602). Note that 5GAN (or gNB) can select AMF based on the information contained in the registration request message and / or RRC message. Specifically, 5GAN (or gNB) may select the AMF in the NPN required by the UE based on at least one of the identification information of the first to the fourth identification information. For example, 5GAN (or gNB) may select the AMF included in the NPN shown in the first identification information based on the first identification information, or support the NPN shown in the first identification information. You may select the AMF to be used. In that case, the exchange of information on NPN including AMF and / or supported by AMF occurs in advance between 5GAN (or gNB) and AMF, or notification from AMF to 5GAN (or gNB) occurs. There is.
なお、AMFの選択方法はこれに限られず、5G AN(又はgNB)はこれ以外の条件に基づきAMFを選択してもよい。5G AN(又はgNB)は、受信したRRCメッセージから登録要求メッセージを取り出し、選択したAMFに、登録要求メッセージを転送する(S604)。なお、第1から4の識別情報の内少なくとも1つの識別情報が、登録要求メッセージには含まれずRRCメッセージに含まれた場合、RRCメッセージに含まれた識別情報を、選択したAMFに、登録要求メッセージと一緒に転送してもよい(S604)。
The selection method of AMF is not limited to this, and 5GAN (or gNB) may select AMF based on other conditions. 5GAN (or gNB) extracts the registration request message from the received RRC message and forwards the registration request message to the selected AMF (S604). If at least one of the identification information 1 to 4 is not included in the registration request message but is included in the RRC message, the identification information included in the RRC message is requested to be registered in the selected AMF. It may be forwarded with the message (S604).
AMFは、登録要求メッセージを受信した場合、第1の条件判別を実行することができる。第1の条件判別とは、ネットワーク(又はAMF)がUEの要求を受諾するか否かを判別するためのものである。AMFは、第1の条件判別が真の場合、図6の(A)の手続きを開始するのに対し、第1の条件判別が偽の場合、図6の(B)の手続きを開始する。
When AMF receives the registration request message, it can execute the first condition determination. The first conditional determination is for determining whether or not the network (or AMF) accepts the UE request. The AMF starts the procedure (A) in FIG. 6 when the first condition determination is true, whereas it starts the procedure (B) in FIG. 6 when the first condition determination is false.
尚、第1の条件判別は、登録要求メッセージの受信、及び/又は登録要求メッセージに含まれる各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、実行されてもよい。例えば、UEの要求をネットワークが許可する場合、第1の条件判別は真であり、UEの要求をネットワークが許可しない場合、第1の条件判別は偽でよい。また、UEの登録先のネットワーク、及び/又はネットワーク内の装置が、UEの要求する機能をサポートしている場合、第1の条件判別は真であり、UEの要求する機能をサポートしていない場合、第1の条件判別は偽でよい。さらに、送受信される識別情報が許可される場合、第1の条件判別は真であり、送受信される識別情報が許可されない場合、第1の条件判別は偽でよい。また、AMFが登録手続き等の移動管理メッセージ(Mobility Management message)の送受信を、輻輳に基づき制限している場合、更にUEが、AMFが属するネットワーク(PLMN及び/又はNPN)内で高い優先度で接続が許可されているUEでない場合、第1の条件判別は偽であり、UEが、AMFが属するネットワーク(PLMN及び/又はNPN)内で高い優先度で接続が許可されているUEである場合、第1の条件判別は真であってよい。尚、第1の条件判別の真偽が決まる条件は前述した条件に限らなくてもよい。
The first condition determination is the reception of the registration request message and / or each identification information contained in the registration request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and It may be executed based on / or the state of the network and / or the user's registration information and / or the context held by AMF. For example, if the network allows the UE request, the first condition determination is true, and if the network does not allow the UE request, the first condition determination may be false. Also, if the network to which the UE is registered and / or the devices in the network support the functions required by the UE, the first condition determination is true and does not support the functions required by the UE. In this case, the first condition determination may be false. Further, if the transmitted / received identification information is permitted, the first conditional determination may be true, and if the transmitted / received identification information is not permitted, the first conditional determination may be false. In addition, if the AMF restricts the transmission and reception of mobility management messages such as registration procedures based on congestion, the UE will also give higher priority within the network (PLMN and / or NPN) to which the AMF belongs. If the UE is not allowed to connect, the first condition is false and the UE is a UE that is allowed to connect with high priority within the network (PLMN and / or NPN) to which AMF belongs. , The first condition determination may be true. The condition for determining the truth of the first condition determination does not have to be limited to the above-mentioned condition.
まず、第1の条件判別が真の場合について説明する。AMFは、図6の(A)の手続きにおいて、まず第4の条件判別を実行することができる。第4の条件判別は、AMFがSMFとの間でSMメッセージの送受信を実施するか否かを判別するためのものである。
First, the case where the first condition discrimination is true will be described. The AMF can first execute the fourth condition determination in the procedure (A) of FIG. The fourth condition determination is for determining whether or not the AMF sends and receives SM messages to and from the SMF.
尚、第4の条件判別は、AMFがSMメッセージを受信したか否かに基づいて実行されてよい。また、第4の条件判別は、登録要求メッセージにSMメッセージが含まれているかに基づいて、実行されてもよい。例えば、AMFがSMメッセージを受信した場合、及び/又は登録要求メッセージにSMメッセージが含まれていた場合、第4の条件判別は真であってよく、AMFがSMメッセージを受信しなかった場合、及び/又は登録要求メッセージにSMメッセージが含まれていなかった場合、第4の条件判別は偽であってよい。尚、第4の条件判別の真偽が決まる条件は前述した条件に限らなくてもよい。
Note that the fourth condition determination may be executed based on whether or not the AMF has received the SM message. Further, the fourth condition determination may be executed based on whether the registration request message includes the SM message. For example, if the AMF received the SM message and / or if the registration request message contained the SM message, the fourth condition may be true and if the AMF did not receive the SM message. And / or if the registration request message does not include the SM message, the fourth condition determination may be false. The condition for determining the truth of the fourth condition determination does not have to be limited to the above-mentioned condition.
AMFは、第4の条件判別が真の場合には、SMFを選択し、選択されたSMFとの間でSMメッセージの送受信を実行するのに対し、第4の条件判別が偽の場合には、それらを実行しない(S606)。また、AMFは、第4の条件判別が真の場合であっても、SMFから拒絶を示すSMメッセージを受信した場合には、図6の(A)の手続きを中止する場合がある。このとき、AMFは、図6の(B)の手続きを開始することができる。
AMF selects SMF when the fourth condition determination is true and sends and receives SM messages to and from the selected SMF, whereas when the fourth condition determination is false, AMF sends and receives SM messages. , Do not execute them (S606). Further, even if the fourth condition determination is true, the AMF may cancel the procedure (A) in FIG. 6 when receiving an SM message indicating rejection from the SMF. At this time, the AMF can start the procedure (B) in FIG.
尚、AMFは、S606において、SMFとの間でSMメッセージの送受信を行う際に、登録要求メッセージで受信した識別情報をSMFに通知することができる。SMFは、AMFとの間で、SMメッセージの送受信によって、AMFから受信した識別情報を取得することができる。
In S606, AMF can notify SMF of the identification information received in the registration request message when sending and receiving SM messages to and from SMF. The SMF can acquire the identification information received from the AMF by sending and receiving SM messages to and from the AMF.
次に、AMFは、登録要求メッセージの受信、及び/又はSMFとの間のSMメッセージの送受信の完了に基づいて、登録要求メッセージに対する応答メッセージとして、5G AN(又はgNB)を介して、UEに登録受諾(Registration accept)メッセージを送信する(S608)。例えば、第4の条件判別が偽の場合、AMFは、UEからの登録要求メッセージの受信に基づいて、登録受諾メッセージを送信してもよい。また、第4の条件判別が真の場合、AMFは、SMFとの間のSMメッセージの送受信の完了に基づいて、登録受諾メッセージを送信してもよい。尚、登録受諾メッセージは、N1インターフェース上で送受信されるNASメッセージであるが、UEと5G AN(gNB)間はRRCメッセージに含まれて送受信される。
The AMF then sends the UE via 5G AN (or gNB) as a response message to the registration request message based on the receipt of the registration request message and / or the completion of sending and receiving the SM message to and from the SMF. Send a Registration accept message (S608). For example, if the fourth condition determination is false, the AMF may send a registration acceptance message based on the receipt of the registration request message from the UE. Further, if the fourth condition determination is true, the AMF may send a registration acceptance message based on the completion of sending and receiving the SM message to and from the SMF. The registration acceptance message is a NAS message sent and received on the N1 interface, but it is included in the RRC message and sent and received between the UE and 5GAN (gNB).
AMFは、登録受諾メッセージに少なくとも第11から15の識別情報の内、1つ以上の識別情報を含めて送信してもよい。尚、AMFは、これらの識別情報及び/又は登録受諾メッセージを送信することで、ネットワークが各機能をサポートしていることを示してもよいし、UEの要求が受諾されたことを示してもよいし、これらを組み合わせた情報を示してもよい。さらに、複数の識別情報が送受信される場合、これらの識別情報の2以上の識別情報は、1以上の識別情報として構成されてもよい。尚、各機能のサポートを示す情報と、各機能の使用の要求を示す情報は、同じ識別情報として送受信されてもよいし、異なる識別情報として送受信されてもよい。
AMF may send the registration acceptance message including at least one or more of the identification information of the 11th to 15th identification information. The AMF may indicate that the network supports each function by sending these identification information and / or the registration acceptance message, or may indicate that the UE request has been accepted. Alternatively, information that combines these may be shown. 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.
AMFは、UEから第1から4の識別情報のうち、少なくともいずれかを受信した場合、及び/又はUEの設定情報の更新があった場合に、第11から15の識別情報の内少なくとも1つを送信してよい。
The AMF receives at least one of the first to fourth identification information from the UE, and / or when the UE setting information is updated, at least one of the eleventh to fifteenth identification information. May be sent.
UEは、第11の識別情報の受信に基づき、UEが記憶するhigh priority NPN listを更新、またはhigh priority NPN listを作成してもよい。なお、ここでUEが記憶するhigh priority NPN listとは、UEが高い優先度で接続が許可されているNPNを識別する為の者である。ここで、NPNを示す情報にS-NSSAIが含まれる場合、UEは、high priority NPN listの更新、又は作成の代わりに、UEが記憶するNSSAI情報(NSSAI storage)の更新を行ってもよい。具体的に、NPNを示す情報にS-NSSAIが含まれる場合、受信したS-NSSAIを、UEが高い優先度で接続が可能であるNPNを示すS-NSSAIのリストとして記憶してもよいし、allowed NSSAI又はConfigured NSSAI又はrejected NSSAIのリスト内の対応するS-NSSAIに、UEが高い優先度で接続が可能であるNPNを示すS-NSSAIであることを示すフラグを関連付けて記憶してもよい。
The UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the eleventh identification information. The high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority. Here, when S-NSSAI is included in the information indicating the NPN, the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list. Specifically, when the information indicating the NPN includes S-NSSAI, the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority. , Allowed NSSAI or Configured NSSAI or rejected NSSAI, even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.
UEは、第12の識別情報を受信した場合、NSSAI情報を更新してよい。具体的には、UEは、受信したrejected NSSAIに含まれるS-NSSAIを、理由値にもとづき、輻輳状態として管理してよい。さらに、UEは、第12の識別情報の受信に基づき、バックオフタイマのカウントを開始してもよい。なお、バックオフタイマはネットワークから受信した値であってもよいし、UEが予め保持する情報であってもよい。
The UE may update the NSSAI information when it receives the twelfth identification information. Specifically, the UE may manage the S-NSSAI included in the received rejected NSSAI as a congested state based on the reason value. Further, the UE may start counting the backoff timer based on the reception of the twelfth identification information. The backoff timer may be a value received from the network or information held in advance by the UE.
なお、NPNを示す情報にS-NSSAIが含まれていた場合、更に、UEが、拒絶されたS-NSSAIがサポートするNPN内で高い優先度で接続が許可されるUEである場合、第12の識別情報を受信してもバックオフタイマを開始しなくてもよい。
If S-NSSAI is included in the information indicating the NPN, and if the UE is a UE that is allowed to connect with a high priority within the NPN supported by the rejected S-NSSAI, the twelfth It is not necessary to start the back-off timer even if the identification information of is received.
UEは第13の識別情報を受信することで、バックオフタイマのカウントを開始してもよい。なお、NPNを示す情報にS-NSSAIが含まれていた場合、更に、UEが、拒絶されたS-NSSAIがサポートするNPN内で高い優先度で接続が許可されるUEである場合、第13の識別情報を受信してもバックオフタイマを開始しなくてもよい。
The UE may start counting the backoff timer by receiving the thirteenth identification information. If S-NSSAI is included in the information indicating the NPN, and if the UE is a UE that is allowed to connect with high priority within the NPN supported by the rejected S-NSSAI, the 13th It is not necessary to start the back-off timer even if the identification information of is received.
UEは第14の識別情報を受信することで、UEの設定情報を更新してもよい。具体的には、UEは第14の識別情報に基づき、UEが許可されたNPNを識別する情報を記憶する。なお、NPNを識別する情報にS-NSSAIが含まれる場合、NSSAIに関する記憶を更新してもよい。具体的には、受信したS-NSSAIを、NPNを示すS-NSSAIのリストとして記憶してもよいし、allowed NSSAI又はConfigured NSSAI又はrejected NSSAIのリスト内の対応するS-NSSAIに、NPNを示すS-NSSAIであることを示すフラグを関連付けて記憶してもよい。
The UE may update the setting information of the UE by receiving the 14th identification information. Specifically, the UE stores information that identifies the NPN that the UE is authorized to use, based on the 14th identification information. If S-NSSAI is included in the information that identifies the NPN, the memory related to NSSAI may be updated. Specifically, the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN, or the NPN is indicated by the corresponding S-NSSAI in the list of allowed NSSAI, Configured NSSAI, or rejected NSSAI. A flag indicating that it is S-NSSAI may be associated and stored.
UEは、第15の識別情報の受信に基づき、ネットワークがNPNへの接続をサポートしていることを検知し、記憶してもよい。UEは、第15の識別情報の受信に基づき、NPNへの登録手続きを開始してもよいし、NPNを介した(又はNPNへの)PDUセッションの確立が許可された状態に遷移するための登録手続きを開始してもよい。
The UE may detect and store that the network supports the connection to the NPN based on the reception of the fifteenth identification information. The UE may initiate the registration process with the NPN based on the receipt of the fifteenth identification information, or to transition to a state in which the establishment of a PDU session via (or to the NPN) is permitted via the NPN. You may start the registration procedure.
なお、上記に示すUEが各識別情報の受信に基づき実行する各処理は、本手続き中、又は本手続き完了後に実行されてもよいし、本手続き完了後に、本手続き完了に基づき実行されてもよい。
In addition, each process that the UE shown above executes based on the reception of each identification information may be executed during 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.
尚、AMFは、第11から15の識別情報の内、どの識別情報を登録受諾メッセージに含めるかを、受信した各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、選択、決定してもよい。
In addition, AMF indicates which of the 11th to 15th identification information should be included in the registration acceptance message, each received identification information and / or subscriber information, and / or network capability information, and / Alternatively, it may be selected and determined based on the operator policy and / or the network status and / or the user's registration information and / or the context held by the AMF.
例えば、AMFは、UEが高い優先度で接続が許可されたNPNのリストの変更が発生した場、つまりAMFが保持するコンテキストの更新が発生した場合に、第11の識別情報を送信してもよい。
For example, the AMF may send the eleventh identity when the UE changes the list of NPNs that are allowed to connect with a high priority, that is, when the context held by the AMF is updated. Good.
例えば、AMFは、UEからrequested NSSAIを受信した場合、更にUEにより要求されたrequested NSSAIに含まれるS-NSSAIをallowed NSSAIに含めない場合、第12の識別情報を送信してもよい。例えば、AMFは、UEから第4の識別情報を受信した場合に第15の識別情報を送信してもよい。
For example, when the AMF receives the requested NSSAI from the UE and does not include the S-NSSAI included in the requested NSSAI requested by the UE in the allowed NSSAI, the AMF may transmit the twelfth identification information. For example, the AMF may transmit the fifteenth identification information when it receives the fourth identification information from the UE.
また、AMFは、登録受諾メッセージにSMメッセージ(例えば、PDUセッション確立受諾メッセージ)を含めて送信するか、又は登録受諾メッセージとともにSMメッセージ(例えば、PDUセッション確立受諾メッセージ)を送信することができる。ただし、この送信方法は、登録要求メッセージの中にSMメッセージ(例えば、PDUセッション確立要求メッセージ)が含められており、かつ、第4の条件判別が真の場合に、実行されてもよい。また、この送信方法は、登録要求メッセージとともにSMメッセージ(例えば、PDUセッション確立要求メッセージ)を含められており、かつ、第4の条件判別が真の場合に、実行されてもよい。AMFは、このような送信方法を行うことにより、登録手続きにおいて、SMのための手続きが受諾されたことを示すことができる。
In addition, the AMF can send the registration acceptance message including the SM message (for example, the PDU session establishment acceptance message), or send the SM message (for example, the PDU session establishment acceptance message) together with the registration acceptance message. However, this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included in the registration request message and the fourth condition determination is true. Further, this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included together with the registration request message and the fourth condition determination is true. By performing such a transmission method, AMF can indicate that the procedure for SM has been accepted in the registration procedure.
また、AMFは、受信した各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、登録受諾メッセージを送信することで、UEの要求が受諾されたことを示してもよい。
In addition, AMF also receives each identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user registration information and / or It may be shown that the UE request has been accepted by sending the registration acceptance message based on the context held by the AMF.
UEは、5G AN(gNB)介して、登録受諾メッセージを受信する(S608)。UEは、登録受諾メッセージを受信することで、登録要求メッセージによるUEの要求が受諾されたこと、及び登録受諾メッセージに含まれる各種の識別情報の内容を認識することができる。
The UE receives the registration acceptance message via 5GAN (gNB) (S608). By receiving the registration acceptance message, the UE can recognize that the UE request by the registration request message has been accepted and the contents of various identification information contained in the registration acceptance message.
UEは、さらに、登録受諾メッセージに対する応答メッセージとして、登録完了メッセージを、5G AN(gNB)介して、AMFに送信することができる(S610)。尚、UEは、PDUセッション確立受諾メッセージ等のSMメッセージを受信した場合は、登録完了メッセージに、PDUセッション確立完了メッセージ等のSMメッセージを含めて送信してもよいし、SMメッセージを含めることで、SMのための手続きが完了したことを示してもよい。ここで、登録完了メッセージは、N1インターフェース上で送受信されるNASメッセージであるが、UEと5G AN(gNB)間はRRCメッセージに含まれて送受信される。
The UE can also send a registration completion message to AMF via 5GAN (gNB) as a response message to the registration acceptance message (S610). When the UE receives an SM message such as a PDU session establishment acceptance message, the UE may send the registration completion message including the SM message such as the PDU session establishment completion message, or by including the SM message. , May indicate that the procedure for SM has been completed. Here, the registration completion message is a NAS message sent and received on the N1 interface, but is included in the RRC message and sent and received between the UE and 5GAN (gNB).
AMFは、5G AN(gNB)介して、登録完了メッセージを受信する(S610)。また、各装置は、登録受諾メッセージ、及び/又は登録完了メッセージの送受信に基づき、図6の(A)の手続きを完了する。
AMF receives a registration completion message via 5G AN (gNB) (S610). In addition, each device completes the procedure (A) in FIG. 6 based on the transmission / reception of the registration acceptance message and / or the registration completion message.
次に、第1の条件判別が偽の場合について説明する。AMFは、図6の(B)の手続きにおいて、登録要求メッセージに対する応答メッセージとして、5G AN(gNB)を介して、UEに登録拒絶(Registration reject)メッセージを送信する(S612)。ここで、登録拒絶メッセージは、N1インターフェース上で送受信されるNASメッセージであるが、UEと5G AN(gNB)間はRRCメッセージに含まれて送受信される。
Next, the case where the first condition determination is false will be described. In the procedure (B) of FIG. 6, the AMF sends a registration rejection message to the UE via 5GAN (gNB) as a response message to the registration request message (S612). Here, the registration refusal 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は、登録拒絶メッセージを送信することで、登録要求メッセージによるUEの要求が拒絶されたことを示してもよい。AMFは、第21から22の識別情報のうち少なくとも1つを登録拒絶メッセージ及び/又はNASメッセージ及び/又はRRCメッセージに含めて送信してよい。AMFは、第1から4の識別情報の内少なくとも1つの受信に基づいて、第21から22の識別情報の内少なくとも1つを送信してよい。
Note that the AMF may indicate that the UE request by the registration request message has been rejected by sending the registration refusal message. The AMF may send at least one of the 21st to 22nd identification information by including it in the registration refusal message and / or NAS message and / or RRC message. The AMF may transmit at least one of the 21st to 22nd identification information based on the reception of at least one of the 1st to 4th identification information.
さらに、AMFは、バックオフタイマの値を登録拒絶メッセージに含めて送信してもよい。なお、AMFは、UEが要求するNPN内で高い優先度で接続が許可されたUEである場合、バックオフタイマの値を含めずに登録拒絶メッセージを送信してもよい。
Furthermore, AMF may include the value of the backoff timer in the registration refusal message and send it. Note that the AMF may send a registration refusal message without including the value of the backoff timer when the UE is allowed to connect with a high priority within the NPN requested by the UE.
UEは第21の識別情報の受信に基づき、UEが要求したNPN内で高い優先度で接続が許可されない事を検知してもよい。更に、UEは第21の識別情報の受信に基づき、NPNを示す情報の記憶を更新してよい。具体的には、UEは第21の識別情報の受信に基づき、拒絶されたNPNを示す情報に高い優先度で接続が許可されていない事を示す情報を紐づけてもよいし、拒絶されたNPNを示す情報に高い優先度で接続が許可されている事を示す情報が紐づいている場合、NPNを示す情報に高い優先度で接続が許可されている事を示す情報を解除してもよい。
The UE may detect that the connection is not permitted within the NPN requested by the UE with a high priority based on the reception of the 21st identification information. Further, the UE may update the memory of the information indicating the NPN based on the reception of the 21st identification information. Specifically, based on the reception of the 21st identification information, the UE may associate the information indicating the rejected NPN with the information indicating that the connection is not permitted with a high priority, or the UE may be rejected. If the information indicating NPN is linked to the information indicating that connection is permitted with high priority, even if the information indicating that connection is permitted with high priority is released from the information indicating NPN. Good.
更に、具体的には、NPNを示す情報に、S-NSSAIが含まれる場合、UEは拒絶されたS-NSSAIを、高い優先度接続が可能であるリストから削除して記憶してもよいし、拒絶されたS-NSSAIと関連付けられて記憶する高い優先度で接続が可能であることを示すフラグを削除してもよい。
Furthermore, specifically, if the information indicating the NPN includes S-NSSAI, the UE may delete the rejected S-NSSAI from the list of possible high priority connections and store it. , The flag indicating that the connection is possible with a high priority to be remembered in association with the rejected S-NSSAI may be removed.
UEは、第22の識別情報の受信に基づき、UEが記憶するhigh priority NPN listを更新、またはhigh priority NPN listを作成してもよい。なお、ここでUEが記憶するhigh priority NPN listとは、UEが高い優先度で接続が許可されているNPNを識別する為の者である。ここで、NPNを示す情報にS-NSSAIが含まれる場合、UEは、high priority NPN listの更新、又は作成の代わりに、UEが記憶するNSSAI情報(NSSAI storage)の更新を行ってもよい。具体的に、NPNを示す情報にS-NSSAIが含まれる場合、受信したS-NSSAIを、UEが高い優先度で接続が可能であるNPNを示すS-NSSAIのリストとして記憶してもよいし、allowed NSSAI又はConfigured NSSAI又はrejected NSSAIのリスト内の対応するS-NSSAIに、UEが高い優先度で接続が可能であるNPNを示すS-NSSAIであることを示すフラグを関連付けて記憶してもよい。
The UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the 22nd identification information. The high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority. Here, when S-NSSAI is included in the information indicating the NPN, the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list. Specifically, when the information indicating the NPN includes S-NSSAI, the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority. , Allowed NSSAI or Configured NSSAI or rejected NSSAI, even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.
なお、上記に示すUEが各識別情報の受信に基づき実行する各処理は、本手続き中、又は本手続き完了後に実行されてもよいし、本手続き完了後に、本手続き完了に基づき実行されてもよい。UEは、5G AN(gNB)介して、登録拒絶メッセージを受信する(S612)。UEは、登録拒絶メッセージを受信することで、登録要求メッセージによるUEの要求が拒絶されたこと、及び登録拒絶メッセージに含まれる各種の識別情報の内容を認識することができる。また、UEは、登録要求メッセージを送信した後、所定の期間が経過しても、登録受諾メッセージ又は登録拒絶メッセージを受信しない場合には、UEの要求が拒絶されたことを認識してもよい。各装置は、登録拒絶メッセージの送受信に基づき、本手続き中の(B)の手続きを完了する。
In addition, each process that the UE shown above executes based on the reception of each identification information may be executed during 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. The UE receives a registration refusal message via 5GAN (gNB) (S612). By receiving the registration refusal message, the UE can recognize that the UE request by the registration request message has been rejected and the contents of various identification information included in the registration refusal message. In addition, the UE may recognize that the request of the UE has been rejected if the registration acceptance message or the registration refusal message is not received within a predetermined period after sending the registration request message. .. Each device completes the procedure (B) during this procedure based on the transmission and reception of the registration refusal message.
尚、図6の(B)の手続きは、図6の(A)の手続きを中止した場合に開始される場合もある。図6の(A)の手続きにおいて、第4の条件判別が真の場合、AMFは、登録拒絶メッセージに、PDUセッション確立拒絶メッセージ等の拒絶を意味するSMメッセージを含めて送信してもよいし、拒絶を意味するSMメッセージを含めることで、SMのための手続きが拒絶されたことを示してもよい。その場合、UEは、さらに、PDUセッション確立拒絶メッセージ等の拒絶を意味するSMメッセージを受信してもよいし、SMのための手続きが拒絶されたことを認識してもよい。
Note that the procedure (B) in Fig. 6 may be started when the procedure in (A) in Fig. 6 is canceled. In the procedure (A) of FIG. 6, if the fourth condition determination is true, the AMF may send the registration refusal message including the SM message indicating rejection such as the PDU session establishment refusal message. , The SM message, which means refusal, may be included to indicate that the procedure for SM has been rejected. In that case, the UE may further receive an SM message indicating rejection such as a PDU session establishment refusal message, or may recognize that the procedure for SM has been rejected.
各装置は、図6の(A)又は(B)の手続きの完了に基づいて、登録手続きを完了する。尚、各装置は、図6の(A)の手続きの完了に基づいて、UEがネットワークに登録された状態(RM_REGISTERED state)に遷移してもよいし、図6の(B)の手続きの完了に基づいて、UEがネットワークに登録されていない状態(RM_DEREGISTERED state)を維持してもよいし、UEがネットワークに登録されていない状態へ遷移してもよい。また、各装置の各状態への遷移は、登録手続きの完了に基づいて行われてもよく、PDUセッションの確立に基づいて行われてもよい。
Each device completes the registration procedure based on the completion of the procedure (A) or (B) in Fig. 6. In addition, each device may transition to the state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure (A) in FIG. 6, or the procedure in (B) in FIG. 6 is completed. The UE may remain unregistered in the network (RM_DEREGISTERED state), or the UE may transition to a state in which it is not registered in the network. Further, the transition of each device to each state may be performed based on the completion of the registration procedure, or may be performed based on the establishment of the PDU session.
さらに、各装置は、登録手続きの完了に基づいて、登録手続きで送受信した情報に基づいた処理を実施してもよい。例えば、UEの一部の要求が拒絶されたことを示す情報を送受信した場合、UEの要求が拒絶された理由を認識してもよい。さらに、各装置は、UEの要求が拒絶された理由に基づいて、再度本手続きを実施してもよいし、コアネットワーク_Aや別のセルに対して登録手続きを実施してもよい。
Furthermore, each device may perform processing based on the information sent and received in the registration procedure based on the completion of the registration procedure. For example, when sending and receiving information indicating that a part of the UE's request is rejected, the reason why the UE's request is rejected may be recognized. Further, each device may perform this procedure again based on the reason why the UE request is rejected, or may perform the registration procedure for the core network_A or another cell.
さらに、UEは、登録手続きの完了に基づいて、登録受諾メッセージ、及び/又は登録拒絶メッセージとともに受信した識別情報を記憶してもよいし、ネットワークの決定を認識してもよい。
Furthermore, the UE may store the identification information received with the registration acceptance message and / or the registration refusal message based on the completion of the registration procedure, or may recognize the network decision.
例えば、UEが、及第12の識別情報、及び/又は第13の識別情報を受信した場合、更に第12の識別情報に示されるrejected S-NSSAIが、UEが高い優先度で接続が許可されるNPNを示す情報に含まれない場合、UEはバックオフタイマを開始し、バックオフタイマのカウント中は、拒絶されたS-NSSAIを含めた登録要求メッセージの送信は停止してもよい。または、UEはバックオフタイマのカウント中は拒絶されたS-NSSAIを拒絶されたS-NSSAIとして管理し、バックオフタイマのカウント終了後に、拒絶されたS-NSSAIを、Configured NSSAIとして記憶してもよい。
For example, when the UE receives the twelfth identification information and / or the thirteenth identification information, the rejected S-NSSAI shown in the twelfth identification information is allowed to connect with the UE having a high priority. If it is not included in the information indicating the NPN, the UE may start the backoff timer, and while the backoff timer is counting, the transmission of the registration request message including the rejected S-NSSAI may be stopped. Alternatively, the UE manages the rejected S-NSSAI as the rejected S-NSSAI while counting the backoff timer, and stores the rejected S-NSSAI as the configured NSSAI after the count of the backoff timer ends. May be good.
また、例えば、UEが、第12の識別情報、及び/又は第13の識別情報を受信した場合、更に第12の識別情報に示されるrejected S-NSSAIが、UEが高い優先度で接続が許可されるNPNを示す情報に含まれる場合、UEはバックオフタイマのカウントを開始せず、続けて、拒絶されたS-NSSAIを含む登録要求メッセージを送信することで、再度登録手続きを開始してもよい。または、その場合、UEは、バックオフタイマのカウントを開始するが、バックオフタイマのカウント中であっても、UEがNPN内で高い優先度で接続が許可されているUEであることに基づき、登録手続きを開始してもよい。
Further, for example, when the UE receives the twelfth identification information and / or the thirteenth identification information, the rejected S-NSSAI further shown in the twelfth identification information allows the UE to connect with a high priority. If it is included in the information indicating the NPN to be used, the UE does not start counting the backoff timer, but then starts the registration procedure again by sending a registration request message containing the rejected S-NSSAI. May be good. Or, in that case, the UE starts counting the backoff timer, but based on the fact that the UE is a UE that is allowed to connect with high priority in the NPN even while the backoff timer is counting. , You may start the registration procedure.
また、例えば、UEが第11の識別情報及び/又は第14の識別情報及び/又は第15の識別情報を受信した場合、UEは許可されたNPNへのPDUセッションを確立するために、PDUセッション確立手続きを開始してもよい。
Also, for example, if the UE receives the eleventh and / or the fourteenth and / or fifteenth identity, the UE will have a PDU session to establish a PDU session to the authorized NPN. The establishment procedure may be initiated.
また、例えば、UEが登録受諾メッセージ、及び/又は第11の識別情報及び/又は第14の識別情報及び/又は第15の識別情報を受信した場合、更にUEが接続状態からアイドル状態に遷移した場合、NPNへの接続を再開するためのサービス要求手続きを開始してもよい。
Further, for example, when the UE receives the registration acceptance message and / or the 11th identification information and / or the 14th identification information and / or the 15th identification information, the UE further transitions from the connected state to the idle state. If so, the service request procedure for resuming the connection to the NPN may be initiated.
[3.3.サービス要求手続きの概要]
次に、サービス要求手続の概要について図7を用いて説明する。以下、サービス要求手続きは、本手続きとも称する。サービス要求手続きは、UEがアイドル状態(5GMM-IDLE)から接続状態(CONNECTED mode)に遷移するための手続きである。UEは、ユーザデータの保持、又はネットワークからのページングまたは通知をトリガとしてサービス要求を開始してもよい。 [3.3. Outline of service request procedure]
Next, the outline of the service request procedure will be described with reference to FIG. Hereinafter, the service request procedure is also referred to as this procedure. The service request procedure is a procedure for the UE to transition from the idle state (5GMM-IDLE) to the connected state (CONNECTED mode). The UE may initiate a service request triggered by retention of user data or paging or notification from the network.
次に、サービス要求手続の概要について図7を用いて説明する。以下、サービス要求手続きは、本手続きとも称する。サービス要求手続きは、UEがアイドル状態(5GMM-IDLE)から接続状態(CONNECTED mode)に遷移するための手続きである。UEは、ユーザデータの保持、又はネットワークからのページングまたは通知をトリガとしてサービス要求を開始してもよい。 [3.3. Outline of service request procedure]
Next, the outline of the service request procedure will be described with reference to FIG. Hereinafter, the service request procedure is also referred to as this procedure. The service request procedure is a procedure for the UE to transition from the idle state (5GMM-IDLE) to the connected state (CONNECTED mode). The UE may initiate a service request triggered by retention of user data or paging or notification from the network.
UEは、サービス要求を開始する前に登録受諾メッセージを受信し、登録手続きを完了している状態であってもよい。
The UE may be in a state where it has received the registration acceptance message and completed the registration procedure before starting the service request.
まず、UEは、AMFにサービス要求メッセージ(Service request message)を送信する(S700)。なお、サービス要求メッセージはN1インターフェース上で送受信されるNASメッセージであるが、UEと5G AN(gNB)間はRRCメッセージに含まれて送受信される。
First, the UE sends a service request message to AMF (S700). The service request message is a NAS message sent and received on the N1 interface, but it is included in the RRC message and sent and received between the UE and 5GAN (gNB).
ここで、UEは第31の識別情報をサービス要求メッセージ、及び/又はサービス要求メッセージが含まれるRRCメッセージに含めて送信してよい。尚、各機能のサポートを示す情報と、各機能の使用の要求を示す情報は、同じ識別情報として送受信されてもよいし、異なる識別情報として送受信されてもよい。
Here, the UE may send the 31st identification information by including it in the service request message and / or the RRC message including the service request message. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.
UEは、要求するNPN内で高い優先度で接続が許可されるUEである場合、バックオフタイマのカウントを実行中であっても、サービス要求メッセージ及び/又は第31の識別情報を送信してもよい。
If the UE is a UE that is allowed to connect with a high priority within the requesting NPN, it will send a service request message and / or the 31st identification information even while the backoff timer is counting. May be good.
UEは第31の識別情報を送信することで、AMFにNPNへの接続を要求することを示してもよいし、更に、UEが要求するNPN内で高い優先度で接続が許可されたUEであることを示してもよい。
The UE may indicate that it requests the AMF to connect to the NPN by sending the 31st identification information, and further, on the UE that is allowed to connect with a high priority within the NPN requested by the UE. It may be shown that there is.
AMFは、サービス要求メッセージを受信した場合、第1の処理を実行する(S702)。AMFは第1の処理において、UEのサービス要求を受諾するか否かを決定する。AMFは、第1の処理において、UEのサービス要求を受諾する場合、図7の(A)の手続きを実行する。一方、AMFは、第1の処理において、UEのサービス要求を拒絶する場合、図7の(B)の手続きを実行する。第1の処理による、UEからのサービス要求を受諾するか否かの決定方法は、サービス要求メッセージの受信、及び/又はサービス要求メッセージに含まれる各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、決定されてよい。
When the AMF receives the service request message, it executes the first process (S702). In the first process, the AMF decides whether to accept the UE's service request. In the first process, the AMF executes the procedure (A) in FIG. 7 when accepting the service request of the UE. On the other hand, when the AMF rejects the UE service request in the first process, it executes the procedure (B) in FIG. 7. The method of determining whether or not to accept the service request from the UE by the first process is to receive the service request message and / or each identification information contained in the service request message and / or the subscriber information and /. Alternatively, it may be determined based on network capability information and / or operator policy and / or network status and / or user registration information and / or context held by AMF.
例えば、AMFは第31の識別情報に基づき、移動管理の輻輳制御、及び/又はDNNベースの輻輳制御、及び/又はS-NSSAIベースの輻輳制御を実行している場合であっても、UEの要求を輻輳に基づき拒絶しなくてもよい。
For example, AMF is performing mobility management congestion control and / or DNN-based congestion control and / or S-NSSAI-based congestion control based on the 31st identification information of the UE. The request does not have to be rejected due to congestion.
言い換えると、AMFは第31の識別情報に基づき、輻輳制御がアクティブであっても、バックオフタイマを含む拒絶メッセージをUEに送信しない。尚、UEのサービス要求の受諾か否かの決定については、前述した方法に限らない。
In other words, based on the 31st identification information, AMF does not send a rejection message including a backoff timer to the UE even if congestion control is active. The determination of whether or not to accept the UE service request is not limited to the method described above.
まず、AMFがUEのサービス要求を受諾する場合について説明する。AMFは、サービス要求メッセージを受信及び/又は第1の処理に基づき、UEにサービス受諾メッセージを送信する(S704)。
First, the case where AMF accepts the UE service request will be described. The AMF receives the service request message and / or sends a service acceptance message to the UE based on the first process (S704).
次に、AMFがUEのサービス要求を拒絶する場合について説明する。AMFは、サービス要求メッセージを受信及び/又は第1の処理に基づき、UEにサービス拒絶メッセージを送信する(S706)。
Next, the case where AMF rejects the UE service request will be described. The AMF receives the service request message and / or sends a service rejection message to the UE based on the first process (S706).
各装置は、図7の(A)又は(B)の手続きの完了に基づいて、サービス要求手続きを完了する。尚、各装置は、図7の(A)の手続きの完了に基づいて、NASメッセージの送受信に使用されるN1インターフェースが接続されない状態(CM-IDLE)から、接続された状態(CM-CONNECTED)に遷移してよい。
Each device completes the service request procedure based on the completion of the procedure (A) or (B) in Fig. 7. In addition, each device is connected from the state where the N1 interface used for sending and receiving NAS messages is not connected (CM-IDLE) to the state where it is connected (CM-CONNECTED) based on the completion of the procedure (A) in FIG. May transition to.
または、各装置は、図7の(B)の手続きの完了に基づいて、NASメッセージの送受信に使用されるN1インターフェースが接続されない状態(CM-IDLE)を維持してもよい。
Alternatively, each device may maintain a state in which the N1 interface used for sending and receiving NAS messages is not connected (CM-IDLE) based on the completion of the procedure (B) in FIG.
さらに、各装置は、サービス手続きの完了に基づいて、サービス要求手続きで送受信した情報に基づいた処理を実施してもよい。さらに、各装置は、UEの要求が拒絶された理由に基づいて、再度本手続きを実施してもよいし、コアネットワーク_Aや別のセルに対して登録手続きを実施してもよい。
Furthermore, each device may perform processing based on the information sent and received in the service request procedure based on the completion of the service procedure. Further, each device may perform this procedure again based on the reason why the UE request is rejected, or may perform the registration procedure for the core network_A or another cell.
さらに、UEは、サービス手続きの完了に基づいて、サービス受諾メッセージ、及び/又はサービス拒絶メッセージとともに受信した識別情報を記憶してもよいし、ネットワークの決定を認識してもよい。
Furthermore, the UE may store the identification information received along with the service acceptance message and / or the service rejection message based on the completion of the service procedure, or may recognize the network decision.
例えば、UEはサービス受諾メッセージの受信に基づき、登録手続きを開始してもよい。
For example, the UE may start the registration procedure based on the receipt of the service acceptance message.
[3.4.PDUセッション確立手続き]
次に、DNに対してPDUセッションを確立するために行うPDUセッション確立手続き (PDU session establishment procedure) の概要について、図8を用いて説明する。PDUセッション確立手続きは、5GSにおける手続きである。以下、本手続きとはPDUセッション確立手続きを指す。PDUセッション確立手続きは、各装置がPDUセッションを確立する為の手続きである。尚、各装置は、PDUセッション確立手続きを、登録手続きが完了して登録状態となった任意のタイミングで開始することができる。また、各装置は、PDUセッション確立手続きを、登録手続きの中で実行することができてもよい。また、各装置は、PDUセッション確立手続きの完了に基づいて、PDUセッションを確立してもよい。尚、PDUセッション確立手続きは、UEが主導して開始される手続きであってよいし、UEが要求して開始される手続きであってよい。各装置は、PDUセッション確立手続きを複数回実行することにより、複数のPDUセッションを確立することができる。例えば、UEが複数のNPNを介したPDUセッションを確立する事を要求する場合、UEは要求するNPNごとにPDUセッション確立手続きを開始してもよい。 [3.4. PDU session establishment procedure]
Next, an outline of the PDU session establishment procedure performed to establish a PDU session for a DN will be described with reference to FIG. The PDU session establishment procedure is a procedure in 5GS. Hereinafter, this procedure refers to the procedure for establishing a PDU session. The PDU session establishment procedure is a procedure for each device to establish a PDU session. In addition, each device can start the PDU session establishment procedure at an arbitrary timing when the registration procedure is completed and the registration state is reached. In addition, each device may be able to execute the PDU session establishment procedure in the registration procedure. In addition, each device may establish a PDU session based on the completion of the PDU session establishment procedure. The PDU session establishment procedure may be a procedure initiated by the UE, or may be a procedure requested and initiated by the UE. Each device can establish a plurality of PDU sessions by executing the PDU session establishment procedure a plurality of times. For example, if the UE requires that a PDU session be established through multiple NPNs, the UE may initiate a PDU session establishment procedure for each requested NPN.
次に、DNに対してPDUセッションを確立するために行うPDUセッション確立手続き (PDU session establishment procedure) の概要について、図8を用いて説明する。PDUセッション確立手続きは、5GSにおける手続きである。以下、本手続きとはPDUセッション確立手続きを指す。PDUセッション確立手続きは、各装置がPDUセッションを確立する為の手続きである。尚、各装置は、PDUセッション確立手続きを、登録手続きが完了して登録状態となった任意のタイミングで開始することができる。また、各装置は、PDUセッション確立手続きを、登録手続きの中で実行することができてもよい。また、各装置は、PDUセッション確立手続きの完了に基づいて、PDUセッションを確立してもよい。尚、PDUセッション確立手続きは、UEが主導して開始される手続きであってよいし、UEが要求して開始される手続きであってよい。各装置は、PDUセッション確立手続きを複数回実行することにより、複数のPDUセッションを確立することができる。例えば、UEが複数のNPNを介したPDUセッションを確立する事を要求する場合、UEは要求するNPNごとにPDUセッション確立手続きを開始してもよい。 [3.4. PDU session establishment procedure]
Next, an outline of the PDU session establishment procedure performed to establish a PDU session for a DN will be described with reference to FIG. The PDU session establishment procedure is a procedure in 5GS. Hereinafter, this procedure refers to the procedure for establishing a PDU session. The PDU session establishment procedure is a procedure for each device to establish a PDU session. In addition, each device can start the PDU session establishment procedure at an arbitrary timing when the registration procedure is completed and the registration state is reached. In addition, each device may be able to execute the PDU session establishment procedure in the registration procedure. In addition, each device may establish a PDU session based on the completion of the PDU session establishment procedure. The PDU session establishment procedure may be a procedure initiated by the UE, or may be a procedure requested and initiated by the UE. Each device can establish a plurality of PDU sessions by executing the PDU session establishment procedure a plurality of times. For example, if the UE requires that a PDU session be established through multiple NPNs, the UE may initiate a PDU session establishment procedure for each requested NPN.
さらに、UEは、登録手続きで受信した識別情報を基に、PDUセッション確立手続きを開始してもよい。例えば、登録手続きにおいて、UEがNPNを示す情報を受信した場合、UEは本手続きを開始してもよい。
Furthermore, the UE may start the PDU session establishment procedure based on the identification information received in the registration procedure. For example, in the registration procedure, if the UE receives information indicating NPN, the UE may start this procedure.
まず、UEは、5G AN(gNB)及びAMFを介して、SMFにPDUセッション確立要求(PDU session establishment request)メッセージを含むNASメッセージを送信することにより(S800)(S802)(S804)、PDUセッション確立手続きを開始する。
First, the UE sends a NAS message including a PDU session establishment request message to the SMF via 5GAN (gNB) and AMF (S800) (S802) (S804), and the PDU session. Start the establishment procedure.
具体的には、UEは、N1インターフェースを介して、5G AN(gNB)を介して、AMFに、PDUセッション確立要求メッセージを含むNASメッセージを送信する(S800)。
Specifically, the UE sends a NAS message including a PDU session establishment request message to AMF via 5GAN (gNB) via the N1 interface (S800).
ここで、UEは、少なくとも第41から42の識別情報の内、1つ以上の識別情報を、PDUセッション確立要求メッセージ及び/又はNASメッセージに含めて送信することができるが、これらとは異なる制御メッセージ、例えば、RRCレイヤよりも下位のレイヤ(例えば、MACレイヤ、RLCレイヤ、PDCPレイヤ)の制御メッセージに含めて送信してもよい。これらの識別情報は、これらのメッセージに含められることで、UEの要求を示してもよい。また、これらの識別情報の2以上の識別情報は、1以上の識別情報として構成されてもよい。
Here, the UE can transmit one or more of the identification information of at least the 41st to 42nd including the identification information in the PDU session establishment request message and / or the NAS message, but the control is different from these. The message may be included in the control message of a layer lower than the RRC layer (for example, MAC layer, RLC layer, PDCP layer) and transmitted. These identifications may be included in these messages to indicate the UE's request. Further, two or more identification information of these identification information may be configured as one or more identification information.
なお、UEは第41から42の識別情報以外に、UE ID及び/又はPLMN ID及び/又はrequested S-NSSAI及び/又はCAG ID及び/又はNIDをPDUセッション確立要求メッセージ及び/又はRRCメッセージに含めて送信してもよい。
In addition to the identification information of Nos. 41 to 42, the UE includes the UE ID and / or PLMN ID and / or requested S-NSSAI and / or CAG ID and / or NID in the PDU session establishment request message and / or RRC message. May be sent.
UEは第41の識別情報を送信することで、NPNへの接続を要求することを示してもよい。UEは、NPNへの接続が許可されている場合、及び/又はUEがNPNへの接続が許可されたUEであると記憶する場合、第41の識別情報を送信してよい。具体的に、例えばNPNを示す情報にS-NSSAIが含まれる場合、UEが記憶するallowed NSSAIに、NPNの為のS-NSSAIが含まれる場合、UEは第41の識別情報を送信してもよい。また、例えば、NPNを示す情報にDNNが含まれる場合、UEがNPNの為のDNNへのPDUセッションの確立を要求する場合、UEは第41の識別情報を送信してよい。
The UE may indicate that it requests a connection to the NPN by transmitting the 41st identification information. The UE may transmit the 41st identification information if it is allowed to connect to the NPN and / or if it remembers that the UE is a UE that is allowed to connect to the NPN. Specifically, for example, if the information indicating NPN includes S-NSSAI, and if the allowed NSSAI stored by the UE includes S-NSSAI for NPN, the UE may send the 41st identification information. Good. Also, for example, if the information indicating the NPN includes a DNN, and the UE requests the establishment of a PDU session to the DNN for the NPN, the UE may transmit the 41st identification information.
AMFは、PDUセッション確立要求メッセージを含むNASメッセージを受信する(S800)。この時、AMFはDNNベース及び/又はS-NSSAIベースの輻輳制御を実行していてもよい。なお、DNNベース及び/又はS-NSSAIベースの輻輳制御とは、AMF及び/又はSMFがDNN及び/又はS-NSSAIに対するセッション管理(Session Management)メッセージの輻輳状態を検知したことに基づき開始する制御であってよい。
AMF receives a NAS message including a PDU session establishment request message (S800). At this time, the AMF may be performing DNN-based and / or S-NSSAI-based congestion control. Note that DNN-based and / or S-NSSAI-based congestion control is control that starts when AMF and / or SMF detects the congestion state of the Session Management message for DNN and / or S-NSSAI. It may be.
AMFは、PDUセッション確立要求メッセージ及び/又はNASメッセージの受信に基づき、受信したPDUセッション確立要求メッセージをSMFに転送するかの第5の条件判別を行う。第5の条件判別の結果が真である場合、各装置は、S802以降の手続きを実行する。第5の条件判別の結果が偽である場合、AMFはNASメッセージを用いて、UEに拒絶メッセージを送信する(S801)。
Based on the reception of the PDU session establishment request message and / or the NAS message, the AMF determines the fifth condition of whether to transfer the received PDU session establishment request message to the SMF. If the result of the fifth condition determination is true, each device executes the procedure after S802. If the result of the fifth condition determination is false, AMF sends a rejection message to the UE using the NAS message (S801).
尚、第5の条件判別は、登録要求メッセージの受信、及び/又は登録要求メッセージに含まれる各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、実行されてもよい。
The fifth condition determination is the reception of the registration request message, and / or each identification information contained in the registration request message, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and It may be executed based on / or the state of the network and / or the user's registration information and / or the context held by AMF.
具体的には、NPNを識別する情報にS-NSSAIが含まれる場合、更にNPNの為のS-NSSAIをUEが要求する場合、更に要求するS-NSSAIベースの輻輳制御が発生している場合、UEが要求するS-NSSAIに関連付けられたNPN又はS-NSSAI内で高い優先度で接続が可能であるUEであるか否かを確認し、UEがNPN又はS-NSSAI内で高い優先度で接続が可能であるUEである場合には第5の条件判別は真、NPN又はS-NSSAI内で高い優先度で接続が可能であるUEでない場合は第5の条件判別は偽とする。
Specifically, when S-NSSAI is included in the information that identifies the NPN, when the UE requests S-NSSAI for NPN, and when the further required S-NSSAI-based congestion control occurs. , Check if the UE is a UE that can connect with a high priority within the NPN or S-NSSAI associated with the S-NSSAI requested by the UE, and the UE has a high priority within the NPN or S-NSSAI. If it is a UE that can be connected with, the fifth condition determination is true, and if it is not a UE that can be connected with high priority within NPN or S-NSSAI, the fifth condition determination is false.
まず、第5の条件判別が偽である場合について説明する。第5の条件判別が偽である場合、AMFは、拒絶メッセージを送信する(S801)。AMFは拒絶メッセージに、受信したPDUセッション確立要求メッセージと、拒絶理由を示す理由値(Cause value)とを含める。AMFは更に、拒絶メッセージに、バックオフタイマの値を含めて送信してもよい。
First, the case where the fifth condition determination is false will be described. If the fifth condition determination is false, AMF sends a rejection message (S801). The AMF includes the received PDU session establishment request message and the reason value (Cause value) indicating the reason for refusal in the rejection message. The AMF may also send the rejection message with the value of the backoff timer included.
ただし、AMFは、UEがNPN又はS-NSSAI内で高い優先度で接続が可能であるUEであると記憶する場合で、拒絶メッセージを送信する場合、バックオフタイマの値は含めなくてよい。言い換えると、AMFはUEがNPN又はS-NSSAI内で高い優先度で接続が可能であるUEでない場合には、バックオフタイマの値を含む拒絶メッセージをUEに送信してよい(S801)。
However, AMF does not need to include the value of the backoff timer when sending a rejection message when the UE remembers that it is a UE that can be connected with high priority within NPN or S-NSSAI. In other words, the AMF may send a rejection message to the UE containing the value of the backoff timer if the UE is not a UE that can be connected with high priority within NPN or S-NSSAI (S801).
次に、第5の条件判別が真である場合について説明する。AMFは、第5の条件判別が真の場合、S802以降を実行する。
Next, the case where the fifth condition determination is true will be described. AMF executes S802 or later if the fifth condition determination is true.
まず、AMFは、NASメッセージからPDUセッション確立要求メッセージを取り出すとともに、PDUセッション確立要求メッセージの転送先としてSMFを選択する(S802)。尚、AMFは、PDUセッション確立要求メッセージ及び/又はNASメッセージに含まれる各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、転送先のSMFを選択してもよい。
First, AMF extracts the PDU session establishment request message from the NAS message and selects SMF as the transfer destination of the PDU session establishment request message (S802). In addition, AMF indicates each identification information and / or subscriber information contained in the PDU session establishment request message and / or NAS message, and / or network capability information, and / or operator policy, and / or network status. And / or the transfer destination SMF may be selected based on the user's registration information and / or the context held by the AMF.
例えば、AMFは受信した第41の識別情報に基づき、UEが要求するNPN内のSMF又はUEが要求するNPNをサポートするSMFを選択してもよいし、第41の識別情報が示すS-NSSAIに含まれるSMFを選択してもよいし、第41の識別情報が示すDNNへの接続をサポートするSMFを選択してもよい。
For example, the AMF may select an SMF in the NPN requested by the UE or an SMF supporting the NPN requested by the UE based on the received 41st identification information, or the S-NSSAI indicated by the 41st identification information. The SMF contained in may be selected, or the SMF that supports the connection to the DNN indicated by the 41st identification information may be selected.
AMFは、選択したSMFに、N11インターフェースを介して、PDUセッション確立要求メッセージを転送する(S804)。なお、AMFは、第41から42の識別情報の内1つ以上を、PDUセッション確立要求メッセージではなくRRCメッセージで受信した場合、受信した情報をPDUセッション確立要求メッセージと共にSMFに転送してもよい。
AMF forwards the PDU session establishment request message to the selected SMF via the N11 interface (S804). When AMF receives one or more of the identification information of Nos. 41 to 42 in the RRC message instead of the PDU session establishment request message, the AMF may transfer the received information to the SMF together with the PDU session establishment request message. ..
SMFは、PDUセッション確立要求メッセージを受信(S804)すると、PDUセッション確立要求メッセージに含まれる各種の識別情報を認識する。そして、SMFは、第3の条件判別を実行する。第3の条件判別は、SMFが、UEの要求を受諾するか否かを判断する為のものである。第3の条件判別において、SMFは第3の条件判別が真であるか偽であるかを判定する。SMFは、第3の条件判別が真の場合、図7の(A)の手続きを開始し、第3の条件判別が偽の場合、図8の(B)の手続きを開始する。
When the SMF receives the PDU session establishment request message (S804), it recognizes various identification information included in the PDU session establishment request message. Then, the SMF executes the third condition determination. The third condition determination is for the SMF to determine whether or not to accept the UE request. In the third condition determination, the SMF determines whether the third condition determination is true or false. The SMF starts the procedure (A) in FIG. 7 when the third condition determination is true, and starts the procedure (B) in FIG. 8 when the third condition determination is false.
尚、第3の条件判別は、PDUセッション確立要求メッセージ、及び/又はPDUセッション確立要求メッセージに含まれる各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はSMFが保持するコンテキスト等に基づいて、実行されてもよい。例えば、UEの要求をネットワークが許可する場合、第3の条件判別は真でよい。また、UEの要求をネットワークが許可しない場合、第3の条件判別は偽でよい。さらに、UEの接続先のネットワーク、及び/又はネットワーク内の装置が、UEが要求する機能をサポートしている場合、第3の条件判別は真でよく、UEが要求する機能をサポートしていない場合、第3の条件判別は偽でよい。さらに、送受信される識別情報が許可される場合、第3の条件判別は真であり、送受信される識別情報が許可されない場合、第3の条件判別は偽でよい。尚、第3の条件判別の真偽が決まる条件は前述した条件に限らなくてもよい。
The third condition determination is the PDU session establishment request message and / or each identification information included in the PDU session establishment request message, and / or the subscriber information, and / or the network capability information, and / or 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, etc. For example, if the network allows the UE request, the third condition may be true. Also, if the network does not allow the UE request, the third condition determination may be false. Furthermore, if the network to which the UE is connected and / or the devices in the network support the functions required by the UE, the third condition determination may be true and does not support the functions required by the UE. In this case, the third condition determination may be false. Further, if the transmitted / received identification information is permitted, the third condition determination may be true, and if the transmitted / received identification information is not permitted, the third condition determination may be false. The condition for determining the truth of the third condition determination is not limited to the above-mentioned condition.
次に、第3の条件判別が真の場合のステップ、すなわち図8の(A)の手続きの各ステップを説明する。SMFは、PDUセッションの確立先のUPFを選択し、選択したUPFに、N4インターフェースを介して、セッション確立要求メッセージを送信し(S806)、図8の(A)の手続きを開始する。
Next, the steps when the third condition determination is true, that is, each step of the procedure (A) in FIG. 8 will be described. The SMF selects the UPF to which the PDU session is established, sends a session establishment request message to the selected UPF via the N4 interface (S806), and starts the procedure (A) in FIG.
ここで、SMFは、PDUセッション確立要求メッセージの受信に基づいて取得した各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はSMFが保持するコンテキスト等に基づいて、1以上のUPFを選択してもよい。尚、複数のUPFが選択された場合、SMFは、各々のUPFに対してセッション確立要求メッセージを送信してもよい。
Here, the SMF receives each identification information and / or subscriber information and / or network capability information acquired based on the reception of the PDU session establishment request message, and / or the operator policy, and / or the network status. And / or one or more UPFs may be selected based on the user's registration information and / or the context held by the SMF. When a plurality of UPFs are selected, the SMF may send a session establishment request message to each UPF.
例えば、SMFは受信した第41の識別情報に基づき、UEが要求するNPN内のUPFを選択してもよい。なお、UPFの選択方法はこれに限られず、SMFはこれ以外の条件に基づきUPFを選択してもよい。
For example, the SMF may select the UPF in the NPN requested by the UE based on the received 41st identification information. The UPF selection method is not limited to this, and the SMF may select the UPF based on other conditions.
UPFは、N4インターフェースを介して、SMFからセッション確立要求メッセージを受信し(S806)、PDUセッションのためのコンテキストを作成する。さらに、UPFは、セッション確立要求メッセージを受信、及び/又はPDUセッションのためのコンテキストの作成に基づいて、N4インターフェースを介して、SMFにセッション確立応答メッセージを送信する(S808)。
The UPF receives the session establishment request message from the SMF (S806) via the N4 interface and creates a context for the PDU session. In addition, the UPF receives the session establishment request message and / or sends a session establishment response message to the SMF via the N4 interface based on creating a context for the PDU session (S808).
SMFは、セッション確立要求メッセージに対する応答メッセージとして、N4インターフェースを介して、UPFからセッション確立応答メッセージを受信する(S808)。SMFは、PDUセッション確立要求メッセージの受信、及び/又はUPFの選択、及び/又はセッション確立応答メッセージの受信に基づいて、UEに割り当てるアドレスのアドレス割り当てを行ってよい。
The SMF receives the session establishment response message from the UPF via the N4 interface as a response message to the session establishment request message (S808). The SMF may assign an address to the UE based on the reception of the PDU session establishment request message and / or the selection of the UPF and / or the reception of the session establishment response message.
SMFは、第41の識別情報及び/又は第42の識別情報の受信に基づき、UEが要求するNPNの為の追加の認証/承認手続きを実行してもよい。
The SMF may perform additional authentication / approval procedures for the NPN required by the UE based on the receipt of the 41st identification information and / or the 42nd identification information.
SMFは、PDUセッション確立要求メッセージの受信、及び/又はUPFの選択、及び/又はセッション確立応答メッセージの受信、及び/又はUEに割り当てるアドレスのアドレス割り当ての完了に基づいて、AMFを介して、UEにPDUセッション確立受諾(PDU session establishment accept)メッセージを送信する(S810)(S812)。
The SMF receives the PDU session establishment request message, and / or selects the UPF, and / or receives the session establishment response message, and / or the UE via the AMF based on the completion of the address assignment of the address assigned to the UE. Sends a PDU session establishment accept message to (S810) (S812).
具体的には、SMFは、N11インターフェースを介して、AMFにPDUセッション確立受諾メッセージを送信すると(S810)、PDUセッション確立要求メッセージを受信したAMFは、N1インターフェースを介して、UEにPDUセッション確立受諾メッセージを含むNASメッセージを送信する(S812)。尚、PDUセッション確立受諾メッセージは、NASメッセージであり、PDUセッション確立要求に対する応答メッセージであってよい。また、PDUセッション確立受諾メッセージは、PDUセッションの確立が受諾されたことを示すことができる。
Specifically, when the SMF sends a PDU session establishment acceptance message to the AMF via the N11 interface (S810), the AMF that receives the PDU session establishment request message establishes a PDU session to the UE via the N1 interface. Send a NAS message containing an acceptance message (S812). The PDU session establishment acceptance message may be a NAS message and may be a response message to the PDU session establishment request. In addition, the PDU session establishment acceptance message can indicate that the PDU session establishment has been accepted.
ここで、SMF及びAMFは、PDUセッション確立受諾メッセージを送信することで、PDUセッション確立要求によるUEの要求が受諾されたことを示してもよい。
Here, the SMF and AMF may indicate that the UE request by the PDU session establishment request has been accepted by transmitting the PDU session establishment acceptance message.
SMF及びAMFは、PDUセッション確立受諾メッセージに、少なくとも第51から52の識別情報の内、1つ以上の識別情報を含めて送信してもよい。尚、SMF及びAMFは、これらの識別情報及び/又はPDUセッション確立受諾メッセージを送信することで、ネットワークが各機能をサポートしていることを示してもよいし、UEの要求が受諾されたことを示してもよい。さらに、これらの識別情報の2以上の識別情報は、1以上の識別情報として構成されてもよい。尚、各機能のサポートを示す情報と、各機能の使用の要求を示す情報は、同じ識別情報として送受信されてもよいし、異なる識別情報として送受信されてもよい。
The SMF and AMF may send the PDU session establishment acceptance message including at least one of the identification information items 51 to 52. Note that the SMF and AMF may indicate that the network supports each function by sending these identification information and / or the PDU session establishment acceptance message, and the UE request has been accepted. May be indicated. Further, two or more identification information of these identification information may be configured as one or more identification information. The information indicating the support of each function and the information indicating the request for using each function may be transmitted / received as the same identification information or may be transmitted / received as different identification information.
UEは、第51の識別情報を受信することで、UEが要求したNPNへのPDUセッションが確立できたことを検知してもよいし、確立されたPDUセッションがNPNへのPDUセッションであることを検知してもよい。
The UE may detect that the PDU session to the NPN requested by the UE has been established by receiving the 51st identification information, and the established PDU session is a PDU session to the NPN. May be detected.
UEは、第52の識別情報を受信することで、UEが要求したNPNへのPDUセッションが確立できたことを検知してもよいし、確立されたPDUセッションがNPNへのPDUセッションであることを検知してもよいし、要求するNPNへの接続に対する認証/承認が完了したことを検知してもよい。
The UE may detect that the PDU session to the NPN requested by the UE has been established by receiving the 52nd identification information, and the established PDU session is a PDU session to the NPN. May be detected, or it may be detected that authentication / authorization for the requested connection to the NPN has been completed.
尚、SMF及びAMFは、少なくとも第51から52の識別情報の内、どの識別情報をPDUセッション確立受諾メッセージに含めるかを、受信した各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、選択、決定してもよい。
It should be noted that the SMF and AMF include at least which of the 51st to 52nd identification information is included in the PDU session establishment acceptance message of each of the received identification information and / or subscriber information, and / or the network. Selection and determination may be made based on capability information and / or operator policy and / or network status and / or user registration information and / or context held by AMF.
例えば、SMFはUEから第41の識別情報の受信に基づき、第52の識別情報を送信してもよい。具体的には、SMFは第41の識別情報に基づき、UEから要求するNPNの為の追加の認証/承認を要すると判断した場合、認証/承認手続きを実行し、実行結果である第52の識別情報をUEに送信してもよい。
For example, the SMF may transmit the 52nd identification information based on the reception of the 41st identification information from the UE. Specifically, if the SMF determines that additional authentication / approval is required for the NPN requested by the UE based on the 41st identification information, it executes the authentication / approval procedure, and the 52nd execution result is the execution result. The identification information may be sent to the UE.
なお、SMF及びAMFが、どの識別情報をPDUセッション確立受諾メッセージに含めるかの決定方法は、上記に限らない。
The method by which SMF and AMF determine which identification information is included in the PDU session establishment acceptance message is not limited to the above.
また、SMF及びAMFは、選択した、及び/又は許可したPDUセッションIDをPDUセッション確立受諾メッセージに含めることができる。また、SMF及びAMFは、選択した、及び/又は許可したPDUセッションのタイプを示すPDUセッションタイプを指定することができる。PDUセッションタイプとしては、上述の通り、IPv4、IPv6、IP、Ethernet、Unstructuredのいずれかを指定することができる。また、SMF及びAMFは、選択した、及び/又は許可したPDUセッションのSSCモードをPDUセッション確立受諾メッセージに含めることができる。
Also, SMF and AMF can include the selected and / or allowed PDU session ID in the PDU session establishment acceptance message. The SMF and AMF can also specify a PDU session type that indicates the type of PDU session selected and / or allowed. As the PDU session type, any one of IPv4, IPv6, IP, Ethernet, and Unstructured can be specified as described above. The SMF and AMF can also include the SSC mode of the selected and / or allowed PDU session in the PDU session establishment acceptance message.
さらに、SMF及びAMFは、承認されたQoSルール群をPDUセッション確立受諾メッセージに含めることができる。尚、承認されたQoSルール群には一又は複数のQoSルールが含まれてよい。さらに、本手続きにおいて、QoSフロー、及び/又はユーザプレーン無線ベアラが複数確立される場合、承認されたQoSルール群には複数のQoSルールが含まれてもよい。逆に本手続きにおいて、QoSフロー、及び/又はユーザプレーン無線ベアラが1つのみ確立される場合、承認されたQoSルール群には1つのQoSルールが含まれてもよい。
Furthermore, SMF and AMF can include the approved QoS rules in the PDU session establishment acceptance message. The approved QoS rule group may include one or more QoS rules. Further, in this procedure, when a plurality of QoS flows and / or user plane wireless bearers are established, the approved QoS rule group may include a plurality of QoS rules. Conversely, if only one QoS flow and / or user plane radio bearer is established in this procedure, the approved QoS rule group may include one QoS rule.
さらに、SMFは、PDUセッション確立受諾メッセージに、UEの一部の要求が拒絶されたことを示す情報を含めて送信してもよいし、UEの一部の要求が拒絶されたことを示す情報を送信することで、UEの一部の要求が拒絶された理由を示してもよい。さらに、UEは、UEの一部の要求が拒絶されたことを示す情報を受信することで、UEの一部の要求が拒絶された理由を認識してもよい。尚、拒絶された理由は、SMFが受信した識別情報が示す内容が許可されていないことを示す情報であってもよい。
In addition, the SMF may send the PDU session establishment acceptance message with information indicating that some UE requests have been rejected, or information indicating that some UE requests have been rejected. May indicate why some of the UE's requests were rejected. In addition, the UE may recognize why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. The reason for rejection may be information indicating that the content indicated by the identification information received by the SMF is not permitted.
UEは、N1インターフェースを介して、AMFからPDUセッション確立受諾メッセージを含むNASメッセージを受信(S812)すると、AMFを介してSMFにPDUセッション確立完了メッセージを送信する(S814)(S816)。UEは、PDUセッション確立受諾メッセージを受信することで、PDUセッション確立要求によるUEの要求が受諾されたことを検出することができる。
When the UE receives the NAS message including the PDU session establishment acceptance message from the AMF via the N1 interface (S812), the UE sends the PDU session establishment completion message to the SMF via the AMF (S814) (S816). By receiving the PDU session establishment acceptance message, the UE can detect that the UE request by the PDU session establishment request has been accepted.
具体的には、UEは、N1インターフェースを介して、AMFにPDUセッション確立完了メッセージを送信する(S814)。AMFは、UEからPDUセッション確立完了メッセージを受信すると、N11インターフェースを介して、SMFにPDUセッション確立完了メッセージを送信する(S816)。
Specifically, the UE sends a PDU session establishment completion message to the AMF via the N1 interface (S814). When the AMF receives the PDU session establishment completion message from the UE, it sends the PDU session establishment completion message to the SMF via the N11 interface (S816).
尚、AMFがSMFに送信するPDUセッション確立完了メッセージは、S810でSMFからAMFに送信されたPDUセッション確立受諾メッセージに対する応答メッセージであってよい。また、PDUセッション確立完了メッセージは、NASメッセージであってよい。また、PDUセッション確立完了メッセージは、PDUセッション確立手続きが完了することを示すメッセージであればよい。
The PDU session establishment completion message sent by AMF to SMF may be a response message to the PDU session establishment acceptance message sent from SMF to AMF in S810. Further, the PDU session establishment completion message may be a NAS message. Further, the PDU session establishment completion message may be any message indicating that the PDU session establishment procedure is completed.
SMFは、N11インターフェースを介して、AMFからPDUセッション確立完了メッセージを受信すると(S816)、第2の条件判別を実行することができる。第2の条件判別は、送受信されるN4インターフェース上のメッセージの種類を決定する為ものである。第2の条件判別が真の場合、SMFは、N4インターフェースを介して、UPFにセッション変更要求メッセージを送信すると(S818)、その応答メッセージとして、UPFから送信されるセッション変更受諾メッセージを受信する(S820)。第2の条件判別が偽の場合、SMFは、N4インターフェースを介して、UPFにセッション確立要求メッセージを送信すると(S818)、その応答メッセージとして、UPFから送信されるセッション変更受諾メッセージを受信する(S820)。
When the SMF receives the PDU session establishment completion message from the AMF via the N11 interface (S816), the SMF can execute the second condition determination. The second condition determination is for determining the type of message sent / received on the N4 interface. If the second condition determination is true, the SMF sends a session change request message to the UPF via the N4 interface (S818) and receives the session change acceptance message sent by the UPF as its response message (S818). S820). If the second condition determination is false, the SMF sends a session establishment request message to the UPF via the N4 interface (S818) and receives a session change acceptance message sent by the UPF as its response message (S818). S820).
尚、第2の条件判別は、PDUセッションのためのN4インターフェース上のセッションが確立されているか否かに基づいて、実行されてもよい。例えば、PDUセッションのためのN4インターフェース上のセッションが確立されている場合、第2の条件判別は真であってよく、PDUセッションのためのN4インターフェース上のセッションが確立されていない場合、第2の条件判別は偽であってよい。尚、第2の条件判別の真偽が決まる条件は前述した条件に限らなくてもよい。
Note that the second condition determination may be executed based on whether or not a session on the N4 interface for the PDU session has been established. For example, if the session on the N4 interface for the PDU session is established, the second condition determination may be true, and if the session on the N4 interface for the PDU session is not established, the second condition The condition determination of is false. The condition for determining the truth of the second condition determination does not have to be limited to the above-mentioned condition.
各装置は、PDUセッション確立受諾メッセージの送受信、及び/又はPDUセッション確立完了メッセージの送受信、及び/又はセッション変更応答メッセージの送受信、及び/又はセッション確立応答メッセージの送受信に基づいて、PDUセッション確立手続き中の(A)の手続きを完了する。本手続中の(A)の手続きが完了したとき、UEは、DNに対するPDUセッションが確立している状態にいる。
Each device sends and receives a PDU session establishment acceptance message and / or sends and receives a PDU session establishment completion message, and / or sends and receives a session change response message, and / or sends and receives a session establishment response message. Complete the procedure (A) inside. When the procedure (A) during this procedure is completed, the UE is in a state where a PDU session for the DN has been established.
次に、PDUセッション確立手続き中の(B)の手続きの各ステップを説明する。SMFは、AMFを介して、UEにPDUセッション確立拒絶(PDU session establishment reject)メッセージを送信する(S822)(S824)。具体的には、SMFは、N11インターフェースを介して、AMFにPDUセッション確立拒絶メッセージを送信する(S822)。AMFは、N11インターフェースを介して、SMFからPDUセッション確立要求メッセージを受信すると(S822)、N1インターフェースを用いて、UEにPDUセッション確立拒絶メッセージを送信する(S824)。
Next, each step of procedure (B) during the PDU session establishment procedure will be described. The SMF sends a PDU session establishment reject message to the UE via the AMF (S822) (S824). Specifically, the SMF sends a PDU session establishment refusal message to the AMF via the N11 interface (S822). When the AMF receives the PDU session establishment request message from the SMF via the N11 interface (S822), it sends a PDU session establishment rejection message to the UE using the N1 interface (S824).
尚、PDUセッション確立拒絶メッセージは、NASメッセージであってよい。また、PDUセッション確立拒絶メッセージは、PDUセッションの確立が拒絶されたことを示すメッセージであればよい。
The PDU session establishment refusal message may be a NAS message. Further, the PDU session establishment refusal message may be any message indicating that the establishment of the PDU session has been rejected.
ここで、SMFは、PDUセッション確立拒絶メッセージを送信することで、PDUセッション確立要求によるUEの要求が拒絶されたことを示してもよい。さらに、SMFは、PDUセッション確立拒絶メッセージに第61から62の識別情報の内少なくとも1つを送信してもよい。さらに、SMFは、バックオフタイマの値をPDUセッション確立拒絶メッセージに含めて送信してもよい。なお、SMFは第41から42の識別情報の内少なくとも1つを受信した事に基づき、第61から62の識別情報の内少なくとも1つを送信してもよい。
Here, the SMF may indicate that the UE request by the PDU session establishment request has been rejected by sending the PDU session establishment refusal message. In addition, the SMF may send at least one of the 61st to 62nd identifications in the PDU session establishment refusal message. In addition, the SMF may include the value of the backoff timer in the PDU session establishment rejection message and send it. The SMF may transmit at least one of the 61st to 62nd identification information based on the fact that the SMF has received at least one of the 41st to 42nd identification information.
UEは、第61の識別情報の受信に基づき、UEが記憶するhigh priority NPN listを更新、またはhigh priority NPN listを作成してもよい。なお、ここでUEが記憶するhigh priority NPN listとは、UEが高い優先度で接続が許可されているNPNを識別する為の者である。ここで、NPNを示す情報にS-NSSAIが含まれる場合、UEは、high priority NPN listの更新、又は作成の代わりに、UEが記憶するNSSAI情報(NSSAI storage)の更新を行ってもよい。具体的に、NPNを示す情報にS-NSSAIが含まれる場合、受信したS-NSSAIを、UEが高い優先度で接続が可能であるNPNを示すS-NSSAIのリストとして記憶してもよいし、allowed NSSAI又はConfigured NSSAI又はrejected NSSAIのリスト内の対応するS-NSSAIに、UEが高い優先度で接続が可能であるNPNを示すS-NSSAIであることを示すフラグを関連付けて記憶してもよい。
The UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the 61st identification information. The high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority. Here, when S-NSSAI is included in the information indicating the NPN, the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list. Specifically, when the information indicating the NPN includes S-NSSAI, the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority. , Allowed NSSAI or Configured NSSAI or rejected NSSAI, even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.
UEは、第61の識別情報に基づき、拒絶されたNPNを介する(又はNPNへの)PDUセッションの確立要求を送信しない設定を記憶してよい。
The UE may store a setting that does not send a request to establish a PDU session via (or to the NPN) the rejected NPN based on the 61st identification information.
UEは第62の識別情報に基づき、UEが要求するNPNの為の追加の認証/承認手続が完了していないことを認識してよいし、UEが要求するNPNの為の追加の認証/承認手続が完了していない状態を記憶してよい。
The UE may recognize that the additional authentication / approval procedure for the NPN requested by the UE has not been completed based on the 62nd identification information, and the UE may recognize that the additional authentication / approval procedure for the NPN requested by the UE has not been completed. You may remember the state in which the procedure has not been completed.
各装置は、図8の(A)又は(B)の手続きの完了に基づいて、PDUセッション確立手続きを完了する。尚、各装置は、図8の(A)の手続きの完了に基づいて、PDUセッションが確立された状態に遷移してもよいし、図8の(B)の手続きの完了に基づいて、PDUセッション確立手続きが拒絶されたことを認識してもよいし、PDUセッションが確立されていない状態に遷移してもよい。さらに、UEは、図8の(A)の手続きが完了することで、確立したPDUセッションを用いて、DNと通信することができる。
Each device completes the PDU session establishment procedure based on the completion of the procedure (A) or (B) in FIG. Note that each device may transition to the state in which the PDU session is established based on the completion of the procedure (A) in FIG. 8, or the PDU based on the completion of the procedure (B) in FIG. You may recognize that the session establishment procedure has been rejected, or you may transition to a state where the PDU session has not been established. Furthermore, the UE can communicate with the DN using the established PDU session by completing the procedure (A) in FIG.
さらに、各装置は、PDUセッション確立手続きの完了に基づいて及びPDUセッション確立手続き内の各ステップの発生に基づいて、PDUセッション確立手続きで送受信した情報に基づいた処理を実施してもよい。
Further, each device may perform processing based on the information transmitted / received in the PDU session establishment procedure based on the completion of the PDU session establishment procedure and the occurrence of each step in the PDU session establishment procedure.
例えば、各装置は、UEの一部の要求が拒絶されたことを示す情報を送受信した場合、UEの要求が拒絶された理由を認識してもよい。さらに、各装置は、UEの要求が拒絶された理由に基づいて、再度本手続きを実施してもよいし、別のセルに対してPDUセッション確立手続きを実施してもよい。
For example, when each device transmits / receives information indicating that a part of the UE's request is rejected, it may recognize the reason why the UE's request is rejected. Further, each device may perform this procedure again based on the reason why the UE request is rejected, or may perform the PDU session establishment procedure for another cell.
例えば、各装置は、SMFは、PDUセッション確立受諾メッセージの送信、及び/又は第51の識別情報の送受信、及び/又は第52の識別情報の送受信、及び/又は図8の(A)の完了に基づき、UEの管理情報(例えば、UEコンテキスト)に、UEがNPN内で高い優先度で接続が許可されたUEであることを記憶してもよい。
For example, in each device, the SMF sends a PDU session establishment acceptance message and / or sends and receives the 51st identification information, and / or sends and receives the 52nd identification information, and / or completes (A) of FIG. Based on, the management information of the UE (for example, the UE context) may remember that the UE is a UE that is allowed to connect with a high priority in the NPN.
更に、例えば、コアネットワーク内の装置によりUEがNPN内で高い優先度で接続が許可されたUEと記憶されている場合、SMFは、PDUセッション確立受諾メッセージの送信、及び/又は図8の(A)の完了に基づき、本手続きにより確立したPDUセッションに対する、PDUセッション変更拒絶メッセージ(PDU session modification reject message)、及び/又はPDUセッション削除コマンドメッセージ(PDU session release command message)に、バックオフタイマ値を含まない。
Further, for example, if a device in the core network remembers the UE as a UE that is allowed to connect in the NPN with high priority, the SMF sends a PDU session establishment acceptance message and / or ( Based on the completion of A), the backoff timer value is added to the PDU session modification rejection message (PDU session modification reject message) and / or the PDU session deletion command message (PDU session release command message) for the PDU session established by this procedure. Does not include.
さらに、UEは、PDUセッション確立手続きの完了に基づいて、PDUセッション確立受諾メッセージ、及び/又はPDUセッション確立拒絶メッセージとともに受信した識別情報を記憶してもよいし、ネットワークの決定を認識してもよい。
In addition, the UE may store the identification information received with the PDU session establishment acceptance message and / or the PDU session establishment rejection message based on the completion of the PDU session establishment procedure, or may recognize the network decision. Good.
例えば、UEは第51の識別情報の受信に基づき、確立されPDUセッションはNPNを介して確立されたPDUセッションであることを認識、及び記憶してよい。
For example, the UE may recognize and remember that the established PDU session is an established PDU session via the NPN based on the receipt of the 51st identification information.
例えば、UEは第52の識別情報の受信に基づき、確立されたPDUセッションが介するNPNの為の認証/承認手続きが完了している事を認識、記憶してもよい。
For example, the UE may recognize and remember that the authentication / approval procedure for the NPN via the established PDU session has been completed based on the reception of the 52nd identification information.
さらに、UEは受信した識別情報を記憶してもよいし、ネットワークの決定を認識に基づき、本手続き以降の各手続きを実行してもよい。
Furthermore, the UE may store the received identification information, or may execute each procedure after this procedure based on the recognition of the network decision.
例えば、UEがNPNの為の認証/承認手続きが完了している事を認識、記憶している場合、同じNPNを介した(又はNPNへの)PDUセッション確立要求メッセージを確立する場合には、追加の認証/承認手続きを要求しなくてよい。
For example, if the UE recognizes and remembers that the authentication / approval procedure for the NPN has been completed, or if it wants to establish a PDU session establishment request message via (or to the NPN) the same NPN, No need to require additional certification / approval procedures.
[3.5.UE設定更新手続き]
次に、UE設定更新手続き (Generic UE configuration update procedure)について、図9を用いて説明する。以下、UE設定更新手続きは本手続きとも称する。本手続きは、コアネットワークが、UEの設定情報を更新するための手続きである。本手続きは、ネットワークに登録されたUEに対してネットワークが主導して実行するモビリティマネジメントのための手続きであってよい。 [3.5. UE setting update procedure]
Next, the UE configuration update procedure will be described with reference to FIG. Hereinafter, the UE setting update procedure is also referred to as this procedure. This procedure is a procedure for the core network to update the UE setting information. This procedure may be a procedure for mobility management that the network takes the initiative to execute for the UE registered in the network.
次に、UE設定更新手続き (Generic UE configuration update procedure)について、図9を用いて説明する。以下、UE設定更新手続きは本手続きとも称する。本手続きは、コアネットワークが、UEの設定情報を更新するための手続きである。本手続きは、ネットワークに登録されたUEに対してネットワークが主導して実行するモビリティマネジメントのための手続きであってよい。 [3.5. UE setting update procedure]
Next, the UE configuration update procedure will be described with reference to FIG. Hereinafter, the UE setting update procedure is also referred to as this procedure. This procedure is a procedure for the core network to update the UE setting information. This procedure may be a procedure for mobility management that the network takes the initiative to execute for the UE registered in the network.
さらに、AMF等のコアネットワーク内の装置は、ネットワークの設定の更新、及び/又はオペレータポリシーの更新に基づいて本手続きを開始してもよい。尚、本手続きのトリガは、UEのモビリティの検出であってもよいし、UE、及び/又はアクセスネットワーク、及び/又はコアネットワークの状態変化の検出であってもよいし、ネットワークスライスの状態変化であってもよい。さらに、本手続きのトリガは、DN、及び/又はDNのアプリケーションサーバーからの要求の受信であってもよいし、ネットワークの設定の変化であってもよいし、オペレータポリシーの変化であってもよい。さらに、本手続きのトリガは、実行しているタイマの満了であってもよい。尚、コアネットワーク内の装置が本手続きを開始するトリガはこれらに限らない。言い換えると、本手続きは、前述の登録手続き及び/又はPDUセッション確立手続きが完了した後の任意のタイミングで実行されてよい。さらに、本手続きは、各装置が5GMMコンテキストを確立した状態、及び/又は各装置が5GMM接続モードである状態であれば、任意のタイミングで実行されてよい。
Furthermore, devices in the core network such as AMF may start this procedure based on the update of network settings and / or the update of operator policy. The trigger of this procedure may be the detection of the mobility of the UE, the detection of the state change of the UE and / or the access network and / or the core network, or the state change of the network slice. It may be. Further, the trigger of this procedure may be the reception of a request from the DN and / or the DN application server, a change in network settings, or a change in operator policy. .. Further, the trigger of this procedure may be the expiration of the timer being executed. The triggers for the devices in the core network to start this procedure are not limited to these. In other words, this procedure may be executed at any time after the above-mentioned registration procedure and / or PDU session establishment procedure is completed. Further, this procedure may be executed at any timing as long as each device has established a 5GMM context and / or each device is in the 5GMM connection mode.
さらに、本手続きのトリガは、ネットワークが管理するUEの状態変化であってよく、具体的には、UEが高い優先度で接続が許可されるNPNのリストに変更があった場合であってもよい。さらに、ネットワークが管理するUEの状態変化はアプリケーションからの要求に基づいて実行されてもよい。
Furthermore, the trigger of this procedure may be a change of state of the UE managed by the network, specifically, even if there is a change in the list of NPNs that the UE is allowed to connect to with high priority. Good. Furthermore, the state change of the UE managed by the network may be executed based on the request from the application.
また、各装置は、本手続き中に、UEの設定情報を変更するための識別情報、及び/又はUEが実行している機能を停止又は変更するための識別情報を含んだメッセージを送受信してもよい。さらに、各装置は、本手続きの完了に基づいて、ネットワークが指示する設定に、設定情報を更新してもよいし、ネットワークが指示する挙動を開始してもよい。
In addition, each device sends and receives a message containing identification information for changing the setting information of the UE and / or identification information for stopping or changing the function executed by the UE during this procedure. May be good. Further, each device may update the setting information to the setting instructed by the network based on the completion of this procedure, or may start the behavior instructed by the network.
UEは、本手続きによって送受信される制御情報を基に、UEの設定情報を更新してもよい。さらに、UEは、UEの設定情報の更新に伴って、実行している機能を停止してもよいし、新たな機能を開始してもよい。言い換えると、コアネットワーク内の装置は、本手続きを主導すること、さらには本手続きの制御メッセージ及び制御情報をUEに送信することより、これらの制御情報を用いて識別可能なUEの設定情報を、UEに更新させてもよい。さらに、コアネットワーク内の装置は、UEの設定情報を更新させることで、UEが実行している機能を停止させてもよいし、UEに新たな機能を開始させてもよい。
The UE may update the setting information of the UE based on the control information transmitted and received by this procedure. Further, the UE may stop the function being executed or start a new function as the setting information of the UE is updated. In other words, the device in the core network leads this procedure, and further, by transmitting the control message and control information of this procedure to the UE, the setting information of the UE that can be identified by using these control information can be obtained. , UE may update. Further, the device in the core network may stop the function executed by the UE or cause the UE to start a new function by updating the setting information of the UE.
まず、AMFは、5G AN(又はgNB)を介してUEに、設定更新コマンド(Configuration update command)メッセージを送信することにより(S900)、UE設定更新手続きを開始する。
First, AMF starts the UE setting update procedure by sending a configuration update command message to the UE via 5GAN (or gNB) (S900).
AMFは、設定更新コマンドメッセージに少なくとも第71の識別情報を含めて送信してもよい。尚、AMFは、第71の識別情報を送信することで、新しいUEの設定情報を示してもよいし、UEの設定情報の更新を要求してもよい。尚、各機能のサポートを示す情報と、各機能の使用の要求を示す情報は、同じ識別情報として送受信されてもよいし、異なる識別情報として送受信されてもよい。
AMF may send the setting update command message including at least the 71st identification information. The AMF may indicate the new UE setting information by transmitting the 71st identification information, or may request the update of the UE setting 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.
尚、AMFは、少なくとも第71の識別情報を設定更新コマンドメッセージに含めるかを、受信した各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、選択、決定してもよい。
Note that AMF will include at least the 71st identification information in the configuration update command message for each received identification information and / or subscriber information and / or network capability information and / or operator policy and /. Alternatively, it may be selected and determined based on the state of the network and / or the user's registration information and / or the context held by the AMF.
また、AMFは、受信した各識別情報、及び/又は加入者情報、及び/又はネットワークの能力情報、及び/又はオペレータポリシー、及び/又はネットワークの状態、及び/又はユーザの登録情報、及び/又はAMFが保持するコンテキスト等に基づいて、設定更新コマンドメッセージを送信することで、UEの設定情報の更新の要求を示してもよい。
In addition, AMF also receives each identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user registration information and / or A request for updating the setting information of the UE may be indicated by sending a setting update command message based on the context held by the AMF.
UEは、5G AN(gNB)介して、設定更新コマンドメッセージを受信する(S900)。UEは、設定更新コマンドメッセージ、及び/又は設定更新コマンドメッセージに含まれる識別情報に基づいて、UEの設定情報を更新してもよい。
The UE receives the setting update command message via 5GAN (gNB) (S900). The UE may update the UE configuration information based on the configuration update command message and / or the identification information contained in the configuration update command message.
UEは、第71の識別情報の受信に基づき、UEが記憶するhigh priority NPN listを更新、またはhigh priority NPN listを作成してもよい。なお、ここでUEが記憶するhigh priority NPN listとは、UEが高い優先度で接続が許可されているNPNを識別する為の者である。ここで、NPNを示す情報にS-NSSAIが含まれる場合、UEは、high priority NPN listの更新、又は作成の代わりに、UEが記憶するNSSAI情報(NSSAI storage)の更新を行ってもよい。具体的に、NPNを示す情報にS-NSSAIが含まれる場合、受信したS-NSSAIを、UEが高い優先度で接続が可能であるNPNを示すS-NSSAIのリストとして記憶してもよいし、allowed NSSAI又はConfigured NSSAI又はrejected NSSAIのリスト内の対応するS-NSSAIに、UEが高い優先度で接続が可能であるNPNを示すS-NSSAIであることを示すフラグを関連付けて記憶してもよい。
The UE may update the high priority NPN list stored in the UE or create a high priority NPN list based on the reception of the 71st identification information. The high priority NPN list stored in the UE here is a person for identifying the NPN in which the UE is permitted to connect with a high priority. Here, when S-NSSAI is included in the information indicating the NPN, the UE may update the NSSAI information (NSSAI storage) stored in the UE instead of updating or creating the high priority NPN list. Specifically, when the information indicating the NPN includes S-NSSAI, the received S-NSSAI may be stored as a list of S-NSSAI indicating the NPN to which the UE can connect with a high priority. , Allowed NSSAI or Configured NSSAI or rejected NSSAI, even if the corresponding S-NSSAI in the list is associated with a flag indicating that the UE is an S-NSSAI indicating an NPN that can be connected with high priority. Good.
なお、上記に示すUEが各識別情報の受信に基づき実行する各処理は、本手続き中、又は本手続き完了後に実行されてもよいし、本手続き完了後に、本手続き完了に基づき実行されてもよい。さらに、UEは、設定更新コマンドメッセージに含まれる識別情報に基づいて、設定更新コマンドメッセージに対する応答メッセージとして、設定更新完了(Configuration update complete)メッセージを、5G AN(gNB)を介して、AMFに送信してもよい(S902)。
In addition, each process that the UE shown above executes based on the reception of each identification information may be executed during 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. Furthermore, the UE sends a configuration update complete message to the AMF via 5GAN (gNB) as a response message to the configuration update command message based on the identification information contained in the configuration update command message. May (S902).
AMFは、UEが設定更新完了コマンドメッセージを送信した場合、5G AN(gNB)を介して、設定更新完了メッセージを受信する(S902)。また、各装置は、設定更新コマンドメッセージ、及び/又は設定更新完了メッセージの送受信に基づき、本手続きを完了する。
AMF receives the setting update completion message via 5GAN (gNB) when the UE sends the setting update completion command message (S902). In addition, each device completes this procedure based on the transmission / reception of the setting update command message and / or the setting update completion message.
さらに、各装置は、本手続きの完了に基づいて、本手続きで送受信した情報に基づいた処理を実施してもよい。例えば、設定情報に対する更新情報を送受信した場合、各装置は、設定情報を更新してもよい。さらに、登録手続きの実行が必要であることを示す情報を送受信した場合、UEは、本手続きの完了に基づいて、登録手続きを開始してもよい。
Furthermore, each device may perform processing based on the information transmitted and received in this procedure based on the completion of this procedure. For example, when the update information for the setting information is transmitted and received, each device may update the setting information. Furthermore, if the UE sends and receives information indicating that the registration procedure needs to be performed, the UE may start the registration procedure based on the completion of this procedure.
さらに、UEは、本手続きの完了に基づいて、設定情報コマンドメッセージとともに受信した識別情報を記憶してもよいし、ネットワークの決定を認識してもよい。
Furthermore, the UE may store the identification information received together with the setting information command message based on the completion of this procedure, or may recognize the network decision.
例えば、UEは本手続きの完了、及び/又は第71の識別情報の受信に基づき、UEが高い優先度で接続が許可される1または複数のNPNを認識してもよいし、それらを記憶してもよい。
For example, the UE may recognize and remember one or more NPNs that the UE is allowed to connect to at a higher priority based on the completion of this procedure and / or the receipt of the 71st Identification Information. You may.
更に、例えばUEは、記憶したUEが高い優先度で接続が許可される1または複数のNPNの情報に基づいて、登録手続き、及び/又はサービス要求手続き、及び/又はPDUセッション確立要求手続き、及び/又はPDUセッション変更手続きを実行してもよい。
Further, for example, the UE may perform registration procedures, and / or service request procedures, and / or PDU session establishment request procedures, and / or PDU session establishment request procedures, based on the information of one or more NPNs in which the stored UE is allowed to connect with high priority. / Or the PDU session change procedure may be performed.
具体的には、UEは、第71の識別情報の受信に基づき、UEが高い優先度で接続が許可されるNPNを示す情報を含む、登録要求メッセージ、サービス要求メッセージ、及び/又はPDUセッション確立要求メッセージ、及び/又はPDUセッション変更要求メッセージ(PDU session modification request message)を送信することで、各手続きを開始してもよい。
Specifically, the UE establishes a registration request message, a service request message, and / or a PDU session, which includes information indicating an NPN to which the UE is allowed to connect with a high priority based on the reception of the 71st identification information. Each procedure may be started by sending a request message and / or a PDU session modification request message (PDU session modification request message).
また、本手続き完了に基づき、記憶した情報に基づいて、各手続きを実行してもよい。具体的には、UEが記憶する、UEが高い優先度で接続が許可されるNPNを介する(又はNPNへの)PDUセッションの確立手続き、及び/又はPDUセッション変更手続き、及び/又はPDUセッション削除手続きにおいて、ネットワークからバックオフタイマの値を受信した場合であっても、バックオフタイマのカウントを開始しなくてもよく、またはバックオフタイマのカウント中であっても、登録要求メッセージ、サービス要求メッセージ、及び/又はPDUセッション確立要求メッセージ、及び/又はPDUセッション変更要求メッセージ(PDU session modification request message)を送信する事ができる。
Also, based on the completion of this procedure, each procedure may be executed based on the stored information. Specifically, the procedure for establishing a PDU session via (or to) an NPN that allows the UE to connect with a high priority, and / or the procedure for changing the PDU session, and / or deleting the PDU session, which the UE remembers. Registration request message, service request even when the backoff timer value is received from the network in the procedure, the backoff timer does not have to start counting, or the backoff timer is being counted. A message and / or a PDU session establishment request message and / or a PDU session change request message (PDU session modification request message) can be transmitted.
以上の手続きにおいて、設定更新コマンドメッセージの送受信により、コアネットワーク内の装置は、UEに対して、UEが既に適用している設定情報の更新を指示することができるし、UEが実行している機能の停止又は変更を指示することができる。
In the above procedure, by sending and receiving the setting update command message, the device in the core network can instruct the UE to update the setting information that the UE has already applied, and the UE is executing it. You can instruct to stop or change the function.
[4.各実施形態]
以下に本発明における各実施形態についてそれぞれ説明する。 [4. Each embodiment]
Each embodiment of the present invention will be described below.
以下に本発明における各実施形態についてそれぞれ説明する。 [4. Each embodiment]
Each embodiment of the present invention will be described below.
[4.1.第1の実施形態]
次に、第1の実施形態について説明する。以下、第1の実施形態を、本実施形態と称する。本実施形態では、各装置が、AMFが輻輳制御中であっても、またはUEがバックオフタイマのカウント中であっても、UEが要求するNPNに対して登録を完了する実施形態について説明する。 [4.1. First Embodiment]
Next, the first embodiment will be described. Hereinafter, the first embodiment will be referred to as the present embodiment. In this embodiment, an embodiment in which each device completes registration for the NPN requested by the UE even when the AMF is in congestion control or the UE is counting in the backoff timer will be described. ..
次に、第1の実施形態について説明する。以下、第1の実施形態を、本実施形態と称する。本実施形態では、各装置が、AMFが輻輳制御中であっても、またはUEがバックオフタイマのカウント中であっても、UEが要求するNPNに対して登録を完了する実施形態について説明する。 [4.1. First Embodiment]
Next, the first embodiment will be described. Hereinafter, the first embodiment will be referred to as the present embodiment. In this embodiment, an embodiment in which each device completes registration for the NPN requested by the UE even when the AMF is in congestion control or the UE is counting in the backoff timer will be described. ..
本実施形態の通信手続きの初期状態は、AMFは、NASレベルでの輻輳状態を検知し、輻輳制御を開始している状態であってよい。
The initial state of the communication procedure of the present embodiment may be a state in which the AMF detects a congestion state at the NAS level and starts congestion control.
初期状態の各装置は、UEにより開始された第1の登録手続きを実行する。第1の登録手続きは、3.2章の登録手続きであってよい。第1の登録手続きにおいて、UEはAMFへ第1から4の識別情報の内少なくとも1つを含める第1の登録要求メッセージを送信する。言い換えると、第1から4の識別情報の内少なくとも1つを含める第1の登録要求メッセージを受信する。
Each device in the initial state executes the first registration procedure started by the UE. The first registration procedure may be the registration procedure in Chapter 3.2. In the first registration procedure, the UE sends the AMF a first registration request message containing at least one of the first to fourth identifications. In other words, it receives a first registration request message that includes at least one of the first to fourth identifications.
続けて、UEは、AMFから、第21から22の識別情報の内少なくとも1つ以上を含む登録拒絶メッセージを受信することにより、第1の登録手続きを完了する。言い換えると、AMFは、第21から22の識別情報の内少なくとも1つ以上を含む登録拒絶メッセージを送信することにより、第1の登録手続きを完了する。なお、AMFは、登録拒絶メッセージに理由値として、輻輳を示す情報を含めてもよい。更に、AMFは、登録拒絶メッセージにバックオフタイマの値を含めてもよいし、UEの情報に基づき、バックオフタイマの値を含めなくてもよい。
Subsequently, the UE completes the first registration procedure by receiving a registration refusal message containing at least one of the 21st to 22nd identification information from the AMF. In other words, the AMF completes the first registration procedure by sending a registration refusal message containing at least one of the 21st to 22nd identification information. In addition, AMF may include information indicating congestion as a reason value in the registration refusal message. Further, the AMF may include the value of the backoff timer in the registration refusal message, or may not include the value of the backoff timer based on the UE information.
第1の登録手続きの完了、第21から22の識別情報の受信に基づき、UEは、UEが要求するNPN内でUEは高い優先度で接続が許可されたUEであることを認識、及び記憶してもよい。更に、拒絶の理由値の受信に基づき、UEはAMFから輻輳の理由に基づき拒絶された事を認識する。更に、バックオフタイマの値の受信に基づき、UEはバックオフタイマのカウントを開始又は実行してもよい。または、UEは、UEの記憶情報に基づき、バックオフタイマの値を受信しても、バックオフタイマのカウントを開始しなくてもよい。
Based on the completion of the first registration procedure and the receipt of the 21st to 22nd identification information, the UE recognizes and remembers that the UE is a UE that is allowed to connect with high priority within the NPN requested by the UE. You may. Furthermore, based on the receipt of the reason value for rejection, the UE recognizes that it has been rejected by AMF for reasons of congestion. Further, the UE may start or execute counting of the backoff timer based on the reception of the value of the backoff timer. Alternatively, the UE may receive the value of the backoff timer or not start counting the backoff timer based on the stored information of the UE.
UEは、UEの記憶情報に基づき、バックオフタイマのカウント中であっても、第2の登録手続きを開始してもよい。第2の登録手続きは、3.2章の登録手続きであってよい。第2の登録手続きにおいて、UEはAMFへ第1から4の識別情報の内少なくとも1つを含める第1の登録要求メッセージを送信する。言い換えると、第1から4の識別情報の内少なくとも1つを含める第1の登録要求メッセージを受信する。
The UE may start the second registration procedure even while the backoff timer is counting, based on the stored information of the UE. The second registration procedure may be the registration procedure in Chapter 3.2. In the second registration procedure, the UE sends the AMF a first registration request message containing at least one of the first to fourth identifications. In other words, it receives a first registration request message that includes at least one of the first to fourth identifications.
続けて、UEは、AMFから、第11から15の識別情報の内少なくとも1つ以上を含む登録受諾メッセージを受信することにより、第2の登録手続きを完了する。言い換えると、AMFは、第11から15の識別情報の内少なくとも1つ以上を含む登録受諾メッセージを送信することにより、第2の登録手続きを完了する。
Subsequently, the UE completes the second registration procedure by receiving a registration acceptance message containing at least one of the 11th to 15th identification information from the AMF. In other words, the AMF completes the second registration process by sending a registration acceptance message containing at least one of the 11th to 15th identifications.
以上の手続きにより、各装置は、AMFが輻輳制御中であっても、UEが要求するNPNに対してUEの登録手続きを完了する。なお、UEが要求するNPNに対してUEの登録手続きを完了するとは、言い換えると、UEが要求するNPNに対して登録状態に遷移する事を意味してもよいし、UEが要求するNPNを介した(又はNPNへの)PDUセッションの確立が許可された状態に遷移してもよい。
By the above procedure, each device completes the UE registration procedure for the NPN required by the UE even if the AMF is in congestion control. In addition, completing the UE registration procedure for the NPN requested by the UE may mean transitioning to the registration state for the NPN requested by the UE, or the NPN required by the UE. You may transition to a state where the establishment of a PDU session via (or to the NPN) is allowed.
なお、第1の実施形態では、第1の登録手続きと第2の登録手続きが実行されることで、各装置は、AMFが輻輳制御中であっても、UEが要求するNPNに対して登録を完了したが、各装置は、AMFが輻輳制御中であっても、UEが要求するNPNに対して登録を完了する方法はこれに限らない。例えば、各装置は第2の登録手続きのみで、AMFが輻輳制御中であっても、UEが要求するNPNに対して登録を完了してもよい。
In the first embodiment, by executing the first registration procedure and the second registration procedure, each device registers with respect to the NPN requested by the UE even when the AMF is in congestion control. However, each device is not limited to the method of completing the registration for the NPN requested by the UE even when the AMF is in congestion control. For example, each device may complete registration for the NPN requested by the UE, even if the AMF is in congestion control, with only a second registration procedure.
なお、第1の実施形態において、第2の登録手続き完了後に、各装置は任意のタイミングにより、3.3章のサービス要求手続き、及び/又は3.4章のPDUセッション確立手続き、及び/又は3.5章のUE設定更新手続きを開始してもよい。
In the first embodiment, after the completion of the second registration procedure, each device performs the service request procedure in Chapter 3.3 and / or the PDU session establishment procedure in Chapter 3.4, and / or the UE in Chapter 3.5 at any time. You may start the setting update procedure.
[4.2.第2の実施形態]
次に、第2の実施形態について説明する。以下、第2の実施形態を、本実施形態と称する。本実施形態では、各装置は、AMF及び/又はSMFが輻輳制御中であっても、又はUEがバックオフタイマのカウント中であっても、UEがNPN内で高い優先度で接続が許可されていることに基づき、PDUセッション確立手続きを実行する事を説明する。 [4.2. Second Embodiment]
Next, the second embodiment will be described. Hereinafter, the second embodiment will be referred to as the present embodiment. In the present embodiment, each device is allowed to connect with high priority within the NPN, even if the AMF and / or SMF is in congestion control or the UE is counting in the backoff timer. Explain that the PDU session establishment procedure is executed based on the above.
次に、第2の実施形態について説明する。以下、第2の実施形態を、本実施形態と称する。本実施形態では、各装置は、AMF及び/又はSMFが輻輳制御中であっても、又はUEがバックオフタイマのカウント中であっても、UEがNPN内で高い優先度で接続が許可されていることに基づき、PDUセッション確立手続きを実行する事を説明する。 [4.2. Second Embodiment]
Next, the second embodiment will be described. Hereinafter, the second embodiment will be referred to as the present embodiment. In the present embodiment, each device is allowed to connect with high priority within the NPN, even if the AMF and / or SMF is in congestion control or the UE is counting in the backoff timer. Explain that the PDU session establishment procedure is executed based on the above.
本実施形態の通信手続きでは、初期状態は、各装置は、NPNに対して登録を完了している状態である。各装置は第1の実施形態により、初期状態に遷移していてもよいし、これに限らない。
In the communication procedure of this embodiment, the initial state is that each device has completed registration with the NPN. Each device may, or is not limited to, transitioned to the initial state according to the first embodiment.
更に、初期状態は、AMF及び/又はSMFはDNNベース及び/又はS-NSSAIベースの輻輳状態を検知し、DNNベース及び/又はS-NSSAIベースの輻輳制御状態である。
Furthermore, in the initial state, AMF and / or SMF detects a DNN-based and / or S-NSSAI-based congestion state, and is a DNN-based and / or S-NSSAI-based congestion control state.
初期状態から、各装置は、UEから開始される第1のPDUセッション確立手続きを実行する。なお、第1のPDUセッション確立手続きとは、3.4章のPDUセッション確立手続きであってよい。
From the initial state, each device executes the first PDU session establishment procedure started from the UE. The first PDU session establishment procedure may be the PDU session establishment procedure in Chapter 3.4.
具体的には、UEは、第41から42の識別情報の内少なくとも1つ以上を含める第1のPDUセッション確立要求をAMF及び/又はSMFへ送信する。言い換えると、AMF及び/又はSMFはUEから第41から42の識別情報の内少なくとも1つ以上を含める第1のPDUセッション確立要求を受信する。
Specifically, the UE sends a first PDU session establishment request containing at least one of the 41st to 42nd identification information to the AMF and / or SMF. In other words, the AMF and / or SMF receives a first PDU session establishment request from the UE that includes at least one of the 41st to 42nd identifiers.
更に、続けて、UEは、第61から62の識別情報の内少なくとも1つを含めるPDUセッション確立拒絶メッセージをAMF及び/又はSMFから受信する。言い換えると、AMF及び/又はSMFは第61から62の識別情報の内少なくとも1つを含めるPDUセッション確立拒絶メッセージをUEに送信する。
Further, the UE subsequently receives a PDU session establishment refusal message from the AMF and / or SMF containing at least one of the 61st to 62nd identification information. In other words, the AMF and / or SMF sends a PDU session establishment refusal message to the UE that contains at least one of the 61st to 62nd identifications.
なお、AMF及び/又はSMFは、PDUセッション確立拒絶メッセージに理由値として、輻輳を示す情報を含めてもよい。更に、AMF及び/又はSMFは、登録拒絶メッセージにバックオフタイマの値を含めてもよいし、UEの情報に基づき、バックオフタイマの値を含めなくてもよい。
Note that AMF and / or SMF may include information indicating congestion as a reason value in the PDU session establishment refusal message. Further, the AMF and / or SMF may include the value of the backoff timer in the registration refusal message, or may not include the value of the backoff timer based on the information of the UE.
第1の登録手続きの完了、第41から42の識別情報の受信に基づき、UEは、UEが要求するNPN内でUEは高い優先度で接続が許可されたUEであることを認識、及び記憶してもよい。更に、拒絶の理由値の受信に基づき、UEはAMF及び/又はSMFから輻輳の理由に基づき要求を拒絶された事を認識する。更に、バックオフタイマの値の受信に基づき、UEはバックオフタイマのカウントを開始又は実行してもよい。または、UEは、UEの記憶情報に基づき、バックオフタイマの値を受信しても、バックオフタイマのカウントを開始しなくてもよい。
Based on the completion of the first registration procedure and the receipt of the identification information of 41st to 42nd, the UE recognizes and remembers that the UE is a UE that is allowed to connect with a high priority within the NPN requested by the UE. You may. In addition, upon receipt of the reason for refusal value, the UE recognizes that the request has been rejected by the AMF and / or SMF for reasons of congestion. Further, the UE may start or execute counting of the backoff timer based on the reception of the value of the backoff timer. Alternatively, the UE may receive the value of the backoff timer or not start counting the backoff timer based on the stored information of the UE.
UEは、UEの記憶情報に基づき、バックオフタイマのカウント中であっても、第2のPDUセッション確立手続きを開始してもよい。なお、第2のPDUセッション確立手続きとは、3.4章のPDUセッション確立手続きであってよい。
The UE may start the second PDU session establishment procedure even while the backoff timer is counting, based on the stored information of the UE. The second PDU session establishment procedure may be the PDU session establishment procedure in Chapter 3.4.
具体的には、UEは、第41から42の識別情報の内少なくとも1つ以上を含める第2のPDUセッション確立要求をAMF及び/又はSMFへ送信する。言い換えると、AMF及び/又はSMFはUEから第41から42の識別情報の内少なくとも1つ以上を含める第2のPDUセッション確立要求を受信する。
Specifically, the UE sends a second PDU session establishment request containing at least one of the 41st to 42nd identification information to the AMF and / or SMF. In other words, the AMF and / or SMF receives a second PDU session establishment request from the UE that contains at least one of the 41st to 42nd identifiers.
更に、続けて、UEは、第51から52の識別情報の内少なくとも1つを含めるPDUセッション確立受諾メッセージをAMF及び/又はSMFから受信する。言い換えると、AMF及び/又はSMFは第51から52の識別情報の内少なくとも1つを含めるPDUセッション確立受諾メッセージをUEに送信する。
Further, the UE subsequently receives a PDU session establishment acceptance message from AMF and / or SMF containing at least one of the 51st to 52nd identification information. In other words, the AMF and / or SMF sends a PDU session establishment acceptance message to the UE that contains at least one of the 51st to 52nd identifications.
以上の手続きにより、各装置は、AMF及び/又はSMFが、DNNベース及び/又はS-NSSAIベースの輻輳制御中であっても、UEが要求するNPNを介した(NPNへの)PDUセッションが確立できる。更に、各装置は、UEがNPN内で高い優先度で接続が許可されたUEとして管理する事ができ、UEが高い優先度で接続が許可されたNPNを介した(又はNPNへの)PDUセッションに関する手続き(PDUセッション変更手続き、及び又はPDUセッション解放手続き)において、AMF及び/SMFはUEへバックオフタイマを送信しない。
With the above procedure, each device can have a PDU session (to NPN) via NPN requested by UE even if AMF and / or SMF is in DNN-based and / or S-NSSAI-based congestion control. Can be established. In addition, each device can manage the UE as a UE that is allowed to connect with a high priority within the NPN, and the PDU via (or to the NPN) the NPN that the UE is allowed to connect to with a high priority. In session-related procedures (PDU session change procedure and / or PDU session release procedure), AMF and / SMF do not send a backoff timer to the UE.
なお、第2の実施形態では、第1のPDUセッション確立手続きと第2のPDUセッション確立手続きが実行されることで、各装置は、AMF及び/又はSMFが輻輳制御中であっても、UEが要求するUEが要求するNPNを介した(NPNへの)PDUセッションが確立を完了したが、各装置は、AMF及び/又はSMFが輻輳制御中であっても、UEが要求するUEが要求するNPNを介した(NPNへの)PDUセッションが確立を完了する方法はこれに限らない。例えば、各装置は第2のPDUセッション確立手続きのみで、AMF及び/又はSMFが輻輳制御中であっても、UEが要求するUEが要求するNPNを介した(NPNへの)PDUセッションが確立を完了してもよい。
In the second embodiment, by executing the first PDU session establishment procedure and the second PDU session establishment procedure, each device can perform the UE even if the AMF and / or the SMF is in congestion control. A PDU session (to the NPN) via the NPN requested by the UE requested by the UE has completed the establishment, but each device is requested by the UE requested by the UE even if the AMF and / or SMF is in congestion control. This is not the only way a PDU session (to an NPN) through an NPN can complete its establishment. For example, each device only has a second PDU session establishment procedure, and even if the AMF and / or SMF is in congestion control, a PDU session (to the NPN) via the NPN requested by the UE requested by the UE is established. May be completed.
なお、第2の実施形態において、第2のPDUセッション確立手続き後、各装置は任意のタイミングにより、PUDセッション変更手続き、及び/又はPUDセッション解放手続き、及び/又は3.5章のUE設定更新手続きを開始してもよい。
In the second embodiment, after the second PDU session establishment procedure, each device performs the PUD session change procedure and / or the PUD session release procedure and / or the UE setting update procedure in Chapter 3.5 at an arbitrary timing. You may start.
なお、第2のPDUセッション確立手続き後に実行される、PUDセッション変更手続き、及び/又はPUDセッション解放手続きにおいて、AMF及び/又はSMFは、UEの情報に基づき、UEへバックオフタイマの値を送信しなくてよい。
In the PUD session change procedure and / or PUD session release procedure executed after the second PDU session establishment procedure, the AMF and / or SMF sends the backoff timer value to the UE based on the UE information. You don't have to.
[4.3.第3の実施形態]
次に、第3の実施形態について説明する。以下、第3の実施形態を、本実施形態と称する。本実施形態では、各装置は、AMF及び/又はSMFが輻輳制御中であっても、UEがNPN内で高い優先度で接続が許可されたUEとしてネットワーク内で記憶される場合の、PDUセッション変更手続きについて説明する。 [4.3. Third Embodiment]
Next, a third embodiment will be described. Hereinafter, the third embodiment will be referred to as the present embodiment. In the present embodiment, each device is a PDU session when the UE is stored in the network as a UE that is allowed to connect with a high priority in the NPN even when the AMF and / or SMF is in congestion control. The change procedure will be explained.
次に、第3の実施形態について説明する。以下、第3の実施形態を、本実施形態と称する。本実施形態では、各装置は、AMF及び/又はSMFが輻輳制御中であっても、UEがNPN内で高い優先度で接続が許可されたUEとしてネットワーク内で記憶される場合の、PDUセッション変更手続きについて説明する。 [4.3. Third Embodiment]
Next, a third embodiment will be described. Hereinafter, the third embodiment will be referred to as the present embodiment. In the present embodiment, each device is a PDU session when the UE is stored in the network as a UE that is allowed to connect with a high priority in the NPN even when the AMF and / or SMF is in congestion control. The change procedure will be explained.
本手続きの初期状態は、NPNを介した(又はNPNへの)、少なくとも1つのPDUセッションが確立された状態である。さらに、SMFは、UEがNPN内で高い優先度で接続が許可されたUEであることを記憶している。なお、各装置は、例えば第2の実施形態により、初期状態に遷移していてもよいし、各装置の初期状態への遷移方法はこれに限らない。
The initial state of this procedure is that at least one PDU session has been established via (or to) the NPN. In addition, the SMF remembers that the UE is a high priority UE allowed to connect within the NPN. Note that each device may have transitioned to the initial state according to, for example, the second embodiment, and the method of transitioning to the initial state of each device is not limited to this.
本実施形態の初期状態では、AMF及び/又はSMFはDNNベース及び/又はS-NSSAIベースの輻輳状態を検知し、DNNベース及び/又はS-NSSAIベースの輻輳制御状態である。
In the initial state of this embodiment, the AMF and / or SMF detects a DNN-based and / or S-NSSAI-based congestion state, and is a DNN-based and / or S-NSSAI-based congestion control state.
初期状態から、各装置は、PDUセッション変更手続き(PDU session modification procedure)を開始する。
From the initial state, each device starts the PDU session modification procedure (PDU session modification procedure).
なお、ここで、PDUセッション変更手続きとは、UEまたはネットワーク主導により、確立されたPDUセッションを変更する為の手続きであり、UEからSMFに送信されるPDUセッション変更要求メッセージ(PDU Session modification request message)と、SMFからUEに送信されるPDUセッション変更拒絶メッセージ(PDU session modification reject message)又はSMFから開始されるPDUセッション変更手続きにより構成される。
Here, the PDU session change procedure is a procedure for changing an established PDU session under the initiative of the UE or the network, and is a PDU session change request message (PDU Session modification request message) sent from the UE to the SMF. ), And a PDU session modification rejection message (PDU session modification reject message) sent from the SMF to the UE, or a PDU session modification procedure started from the SMF.
また、SMFから開始されるPDUセッション変更手続きはSMFからUEに送信されるPDUセッション変更コマンドメッセージ(PDU session modification command message)とUEからSMFへ送信されるPDUセッション変更完了メッセージ(PDU session modification complete message)により構成される。
In addition, the PDU session change procedure started from SMF is a PDU session change command message (PDU session modification command message) sent from SMF to UE and a PDU session change completion message (PDU session modification complete message) sent from UE to SMF. ).
先に説明したように、PDUセッション変更手続き内で、SMFはUEへPDUセッション変更コマンドメッセージを送信する。ここで、SMFは、UEが、NPN内で高い優先度で接続が許可されたUEであることに基づき、PDUセッション変更コマンドメッセージにバックオフタイマの値を含めない。
As explained earlier, the SMF sends a PDU session change command message to the UE within the PDU session change procedure. Here, the SMF does not include the value of the backoff timer in the PDU session change command message based on the fact that the UE is a UE that is allowed to connect with high priority in the NPN.
UEは、バックオフタイマの値を含まないPDUセッション変更コマンドメッセージをSMFから受信した事に基づき、PDUセッション変更完了メッセージを送信し、PDUセッション変更手続きを完了する。
The UE sends a PDU session change completion message based on receiving a PDU session change command message that does not include the backoff timer value from the SMF, and completes the PDU session change procedure.
以上の手続きにより、各装置は、AMF及び/又はSMFが輻輳制御中であっても、UEがNPN内で高い優先度で接続が許可されたUEとしてネットワーク内で記憶される場合は、輻輳制御をせずにPDUセッション変更手続きを実施する。
According to the above procedure, even if the AMF and / or SMF is in congestion control, if the UE is stored in the network as a UE that is allowed to connect with high priority in the NPN, the device is congested. Execute the PDU session change procedure without doing.
なお、第2の実施形態において、各装置は任意のタイミングにより、PUDセッション変更手続き、及び/又はPUDセッション解放手続き、及び/又は3.5章のUE設定更新手続きを開始してもよい。
In the second embodiment, each device may start the PUD session change procedure and / or the PUD session release procedure and / or the UE setting update procedure in Chapter 3.5 at any timing.
[4.4.第4の実施形態]
次に、第4の実施形態について説明する。以下、第4の実施形態を、本実施形態と称する。本実施形態では、各装置は、AMF及び/又はSMFが輻輳制御中であっても、UEがNPN内で高い優先度で接続が許可されたUEとしてネットワーク内で記憶される場合のPDUセッション解放手続きについて説明する。 [4.4. Fourth Embodiment]
Next, a fourth embodiment will be described. Hereinafter, the fourth embodiment will be referred to as the present embodiment. In the present embodiment, each device releases a PDU session when the UE is stored in the network as a UE that is allowed to connect with a high priority in the NPN even when the AMF and / or SMF is in congestion control. The procedure will be explained.
次に、第4の実施形態について説明する。以下、第4の実施形態を、本実施形態と称する。本実施形態では、各装置は、AMF及び/又はSMFが輻輳制御中であっても、UEがNPN内で高い優先度で接続が許可されたUEとしてネットワーク内で記憶される場合のPDUセッション解放手続きについて説明する。 [4.4. Fourth Embodiment]
Next, a fourth embodiment will be described. Hereinafter, the fourth embodiment will be referred to as the present embodiment. In the present embodiment, each device releases a PDU session when the UE is stored in the network as a UE that is allowed to connect with a high priority in the NPN even when the AMF and / or SMF is in congestion control. The procedure will be explained.
本手続きの初期状態は、NPNを介した(又はNPNへの)、少なくとも1つのPDUセッションが確立された状態である。さらに、SMFは、UEがNPN内で高い優先度で接続が許可されたUEであることを記憶している。なお、各装置は、例えば第2の実施形態により、初期状態に遷移していてもよいし、各装置の初期状態への遷移方法はこれに限らない。
The initial state of this procedure is that at least one PDU session has been established via (or to) the NPN. In addition, the SMF remembers that the UE is a high priority UE allowed to connect within the NPN. Note that each device may have transitioned to the initial state according to, for example, the second embodiment, and the method of transitioning to the initial state of each device is not limited to this.
本実施形態の初期状態では、AMF及び/又はSMFはDNNベース及び/又はS-NSSAIベースの輻輳状態を検知し、DNNベース及び/又はS-NSSAIベースの輻輳制御状態である。
In the initial state of this embodiment, the AMF and / or SMF detects a DNN-based and / or S-NSSAI-based congestion state, and is a DNN-based and / or S-NSSAI-based congestion control state.
初期状態から、PDUセッション解放手続き(PDU session release procedure)を開始する。
From the initial state, start the PDU session release procedure (PDU session release procedure).
なお、ここで、PDUセッション解放手続きとは、確立されたPDUセッションを削除するための手続きである。PDUセッション解放手続きは、ネットワーク主導とUE主導の手続きがあるが、本実施形態ではネットワーク主導の手続きを意味する。
Here, the PDU session release procedure is a procedure for deleting an established PDU session. The PDU session release procedure has a network-led procedure and a UE-led procedure, but in the present embodiment, it means a network-led procedure.
ネットワーク主導のPDUセッション解放手続きは、SMFからUEに送信されるPDUセッション解放コマンドメッセージ(PDU Session release command message)と、UEからSMFに送信されるPDUセッション解放完了メッセージ(PDU session release complete message)により構成される。
The network-led PDU session release procedure is based on the PDU session release command message (PDU Session release command message) sent from the SMF to the UE and the PDU session release completion message (PDU session release complete message) sent from the UE to the SMF. It is composed.
先に示すように、PDUセッション解放手続き内で、SMFはPDUセッション解放コマンドメッセージを送信する。ここで、SMFは、UEが、NPN内で高い優先度で接続が許可されたUEであることに基づき、PDUセッション解放コマンドメッセージにバックオフタイマの値を含めない。
As shown above, the SMF sends a PDU session release command message within the PDU session release procedure. Here, the SMF does not include the value of the backoff timer in the PDU session release command message based on the fact that the UE is a UE that is allowed to connect with high priority in the NPN.
UEは、バックオフタイマの値を含まないPDUセッション解放コマンドメッセージをSMFから受信した事に基づき、PDUセッション解放完了メッセージを送信し、PDUセッション解放手続きを完了する。
The UE sends a PDU session release completion message based on receiving a PDU session release command message that does not include the backoff timer value from the SMF, and completes the PDU session release procedure.
以上の手続きにより、各装置は、AMF及び/又はSMFが輻輳制御中であっても、UEがNPN内で高い優先度で接続が許可されたUEとしてネットワーク内で記憶される場合は、輻輳制御をせずにPDUセッション変更手続きを実施する。
According to the above procedure, even if the AMF and / or SMF is in congestion control, if the UE is stored in the network as a UE that is allowed to connect with high priority in the NPN, the device is congested. Execute the PDU session change procedure without doing.
なお、第2の実施形態において、各装置は任意のタイミングにより、PUDセッション変更手続き、及び/又はPUDセッション解放手続き、及び/又は3.5章のUE設定更新手続きを開始してもよい。
In the second embodiment, each device may start the PUD session change procedure and / or the PUD session release procedure and / or the UE setting update procedure in Chapter 3.5 at any timing.
[5. 変形例]
本発明に関わる装置で動作するプログラムは、本発明に関わる実施形態の機能を実現するように、Central Processing Unit(CPU)等を制御してコンピュータを機能させるプログラムであっても良い。プログラムあるいはプログラムによって取り扱われる情報は、一時的にRandom Access Memory(RAM)等の揮発性メモリあるいはフラッシュメモリ等の不揮発性メモリやHard Disk Drive(HDD)、あるいはその他の記憶装置システムに格納される。 [5. Modification example]
The program that operates in the apparatus according to the present invention may be a program that controls the Central Processing Unit (CPU) or the like to operate the 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 a volatile memory such as Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or another storage device system.
本発明に関わる装置で動作するプログラムは、本発明に関わる実施形態の機能を実現するように、Central Processing Unit(CPU)等を制御してコンピュータを機能させるプログラムであっても良い。プログラムあるいはプログラムによって取り扱われる情報は、一時的にRandom Access Memory(RAM)等の揮発性メモリあるいはフラッシュメモリ等の不揮発性メモリやHard Disk Drive(HDD)、あるいはその他の記憶装置システムに格納される。 [5. Modification example]
The program that operates in the apparatus according to the present invention may be a program that controls the Central Processing Unit (CPU) or the like to operate the 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 a volatile memory such as Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or another storage device system.
尚、本発明に関わる実施形態の機能を実現する為のプログラムをコンピュータが読み取り可能な記録媒体に記録しても良い。この記録媒体に記録されたプログラムをコンピュータシステムに読み込ませ、実行する事によって実現しても良い。ここでいう「コンピュータシステム」とは、装置に内蔵されたコンピュータシステムであって、オペレーティングシステムや周辺機器等のハードウェアを含むものとする。また、「コンピュータが読み取り可能な記録媒体」とは、半導体記録媒体、光記録媒体、磁気記録媒体、短時間動的にプログラムを保持する媒体、あるいはコンピュータが読み取り可能なその他の記録媒体であっても良い。
Note that the program for realizing the function of the embodiment according to 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 "computer system" as used herein is a computer system built into a device, and includes hardware such as an operating system and peripheral devices. Further, the "computer-readable recording medium" is a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another recording medium that can be read by a computer. Is also good.
また、上述した実施形態に用いた装置の各機能ブロック、または諸特徴は、電気回路、たとえば、集積回路あるいは複数の集積回路で実装または実行され得る。本明細書で述べられた機能を実行するように設計された電気回路は、汎用用途プロセッサ、デジタルシグナルプロセッサ(DSP)、特定用途向け集積回路(ASIC)、フィールドプログラマブルゲートアレイ(FPGA)、またはその他のプログラマブル論理デバイス、ディスクリートゲートまたはトランジスタロジック、ディスクリートハードウェア部品、またはこれらを組み合わせたものを含んでよい。汎用用途プロセッサは、マイクロプロセッサでもよいし、従来型のプロセッサ、コントローラ、マイクロコントローラ、またはステートマシンであっても良い。前述した電気回路は、デジタル回路で構成されていてもよいし、アナログ回路で構成されていてもよい。また、半導体技術の進歩により現在の集積回路に代替する集積回路化の技術が出現した場合、本発明の一又は複数の態様は当該技術による新たな集積回路を用いる事も可能である。
Further, each functional block or various features of the device used in the above-described embodiment can be implemented or executed in an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein are 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 a combination thereof may be included. 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 use a new integrated circuit according to the technology.
なお、本願発明は上述の実施形態に限定されるものではない。実施形態では、装置の1例を記載したが、本願発明は、これに限定されるものではなく、屋内外に設置される据え置き型、または非可動型の電子機器、たとえば、AV機器、キッチン機器、掃除・洗濯機器、空調機器、オフィス機器、自動販売機、その他生活機器等の端末装置もしくは通信装置に適用出来る。
The invention of the present application is not limited to the above-described embodiment. In the embodiment, an example of the device has been described, but the present invention is not limited to this, and the present invention is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device or a kitchen device. , Cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices such as living equipment.
以上、この発明の実施形態に関して図面を参照して詳述してきたが、具体的な構成はこの実施形態に限られるものではなく、この発明の要旨を逸脱しない範囲の設計変更等も含まれる。また、本発明は、請求項に示した範囲で種々の変更が可能であり、異なる実施形態にそれぞれ開示された技術的手段を適宜組み合わせて得られる実施形態についても本発明の技術的範囲に含まれる。また、上記各実施形態に記載された要素であり、同様の効果を奏する要素同士を置換した構成も含まれる。
Although the embodiment of the present invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment and includes design changes and the like within a range not deviating from the gist of the present invention. Further, the present invention can be variously modified within the scope of the claims, and the technical scope of the present invention also includes embodiments obtained by appropriately combining the technical means disclosed in the different embodiments. Is done. In addition, the elements described in each of the above-described embodiments include a configuration in which elements having the same effect are replaced with each other.
Claims (14)
- NPN (Non Public Network)に接続可能なユーザ装置であって、
第1の情報を記憶する記憶部と、
前記NPNから、バックオフタイマの値を受信し、
前記第1の情報に基づき、前記バックオフタイマが実行されている間に、要求メッセージを送信する、送受信部と、を備え、
前記第1の情報は、前記ユーザ装置が前記NPN内で高い優先度で接続可能であることを示す情報であり、
前記NPNはネットワークスライスである、
ことを特徴とするユーザ装置。 A user device that can be connected to NPN (Non Public Network)
A storage unit that stores the first information,
Receive the value of the backoff timer from the NPN and
Based on the first information, the transmission / reception unit for transmitting a request message while the backoff timer is being executed is provided.
The first information is information indicating that the user device can be connected within the NPN with high priority.
The NPN is a network slice,
A user device characterized by that. - 前記要求メッセージは、登録要求メッセージまたはサービス要求メッセージまたはPDUセッション確立要求メッセージである、
ことを特徴とする請求項1のユーザ装置。 The request message is a registration request message, a service request message, or a PDU session establishment request message.
The user apparatus according to claim 1. - 前記要求メッセージがサービス要求メッセージである場合、
前記送受信部は、前記サービス要求メッセージに、第2の情報を含め、
前記第2の情報は、高い優先度で前記NPNに接続する事を示す情報である、
ことを特徴とする請求項1又は2記載のユーザ装置。 If the request message is a service request message
The transmitting / receiving unit includes the second information in the service request message.
The second information is information indicating that the NPN is connected with a high priority.
The user apparatus according to claim 1 or 2. - 前記要求メッセージが登録要求メッセージである場合、
前記送受信部は、前記登録要求メッセージに、第3の識別情報を含め、
前記第3の識別情報は、前記ユーザ装置が前記NPNへ高い優先度で接続をするユーザ装置として登録することを希望することを示す情報である、
ことを特徴とする、請求項1又は2記載のユーザ装置。 If the request message is a registration request message
The transmission / reception unit includes the third identification information in the registration request message.
The third identification information is information indicating that the user device wants to be registered as a user device that connects to the NPN with high priority.
The user apparatus according to claim 1 or 2. - NPN(Non Public Network)として作成されたネットワークスライスを含む、PLMN(Public land mobile network)内の制御装置であって、
第1の識別情報を記憶する記憶部と、
輻輳を検知する制御部と、
ユーザ装置から要求メッセージを受信し、
前記第1の識別情報に基づき、前記検知をしている状態であっても、前記要求メッセージの応答として、輻輳を示す理由値を含む拒絶メッセージを送信しない、送受信部、とを備える、
ことを特徴とする制御装置。 A control device in PLMN (Public land mobile network) that includes a network slice created as an NPN (Non Public Network).
A storage unit that stores the first identification information,
A control unit that detects congestion and
Receive a request message from the user device
Based on the first identification information, even in the state of performing the detection, as a response to the request message, a transmission / reception unit that does not transmit a rejection message including a reason value indicating congestion is provided.
A control device characterized by that. - 前記輻輳は、MM(Mobility Management)信号の輻輳またはDNN(Data Network Name)ベースの輻輳及び/又はネットワークスライスベースの輻輳である、
ことを特徴とする請求項5記載の制御装置。 The congestion is MM (Mobility Management) signal congestion or DNN (Data Network Name) -based congestion and / or network slice-based congestion.
5. The control device according to claim 5. - Non Public Network(NPN)として作成されたネットワークスライスを含む、PLMN内の制御装置であって、
前記NPN内で高い優先度で接続可能なユーザ装置に、バックオフタイマを含めないPDU (Protocol Data Unit又はPacket Data Unit)セッション削除コマンドメッセージ又はPDUセッション確立拒絶メッセージ又はPDUセッション変更拒絶メッセージを送信する、送受信部を備える、
ことを特徴とする制御装置。 A controller within PLMN that contains a network slice created as a Non Public Network (NPN).
A PDU (Protocol Data Unit or Packet Data Unit) session deletion command message, a PDU session establishment rejection message, or a PDU session change rejection message that does not include a backoff timer is transmitted to a user device that can be connected with high priority in the NPN. , Equipped with a transmitter / receiver
A control device characterized by that. - 第1の情報を記憶するNPN (Non Public Network)に接続可能なユーザ装置の通信制御方法であって、
前記NPNから、バックオフタイマの値を受信するステップと、
前記第1の情報に基づき、前記バックオフタイマが実行されている間に、要求メッセージを送信ステップと、を備え、
前記第1の情報は、前記ユーザ装置が前記NPN内で高い優先度で接続可能であることを示す情報であり、
前記NPNはネットワークスライスである、
ことを特徴とするユーザ装置の通信制御方法。 It is a communication control method of a user device that can be connected to an NPN (Non Public Network) that stores the first information.
The step of receiving the value of the backoff timer from the NPN and
Based on the first information, the request message is transmitted while the backoff timer is being executed.
The first information is information indicating that the user device can be connected within the NPN with high priority.
The NPN is a network slice,
A communication control method for a user device, characterized in that. - 前記要求メッセージは、登録要求メッセージまたはサービス要求メッセージまたはPDUセッション確立要求メッセージである、
ことを特徴とする請求項8のユーザ装置の通信制御方法。 The request message is a registration request message, a service request message, or a PDU session establishment request message.
The communication control method of the user apparatus according to claim 8. - 前記要求メッセージがサービス要求メッセージである場合、
前記サービス要求メッセージに、第2の情報を含め、
前記第2の情報は、高い優先度で前記NPNに接続する事を示す情報である、
ことを特徴とする請求項8又は9記載のユーザ装置の通信制御方法。 If the request message is a service request message
Include the second information in the service request message
The second information is information indicating that the NPN is connected with a high priority.
The communication control method of the user apparatus according to claim 8 or 9. - 前記要求メッセージが登録要求メッセージである場合、
前記登録要求メッセージに、第3の識別情報を含め、
前記第3の識別情報は、前記ユーザ装置が前記NPNへ高い優先度で接続をするユーザ装置として登録することを希望することを示す情報である、
ことを特徴とする、請求項8又は9記載のユーザ装置の通信制御方法。 If the request message is a registration request message
The registration request message includes the third identification information.
The third identification information is information indicating that the user device wants to be registered as a user device that connects to the NPN with high priority.
The communication control method of the user apparatus according to claim 8 or 9, wherein the method is characterized by the above. - 第1の識別情報を記憶し、NPN(Non Public Network)として作成されたネットワークスライスを含む、PLMN(Public land mobile network)内の制御装置の通信制御方法であって、
輻輳を検知するステップと、
ユーザ装置から要求メッセージを受信するステップと、を備え、
前記制御装置は、前記第1の識別情報に基づき、前記検知をしている状態であっても、前記要求メッセージの応答として、輻輳を示す理由値を含む拒絶メッセージを送信しない、
ことを特徴とする制御装置。 A communication control method for a control device in a PLMN (Public land mobile network) that stores the first identification information and includes a network slice created as an NPN (Non Public Network).
Steps to detect congestion and
With a step to receive a request message from the user device,
Based on the first identification information, the control device does not send a rejection message including a reason value indicating congestion as a response to the request message even in the state of performing the detection.
A control device characterized by that. - 前記輻輳は、MM(Mobility Management)信号の輻輳またはDNN(Data Network Name)ベースの輻輳及び/又はネットワークスライスベースの輻輳である、
ことを特徴とする請求項12記載の制御装置の通信制御方法。 The congestion is MM (Mobility Management) signal congestion or DNN (Data Network Name) -based congestion and / or network slice-based congestion.
12. The communication control method for the control device according to claim 12. - Non Public Network(NPN)として作成されたネットワークスライスを含む、PLMN内の制御装置の通信制御方法であって、
前記NPN内で高い優先度で接続可能なユーザ装置に、バックオフタイマを含めないPDU (Protocol Data Unit又はPacket Data Unit)セッション削除コマンドメッセージ又はPDUセッション確立拒絶メッセージ又はPDUセッション変更拒絶メッセージを送信するステップを備える、
ことを特徴とする制御装置の通信制御方法。 A communication control method for controllers in PLMN, including network slices created as non-public networks (NPNs).
A PDU (Protocol Data Unit or Packet Data Unit) session deletion command message, a PDU session establishment rejection message, or a PDU session change rejection message that does not include a backoff timer is transmitted to a user device that can be connected with high priority in the NPN. With steps,
A communication control method for a control device, characterized in that.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2019-070073 | 2019-04-01 | ||
JP2019070073A JP2020170896A (en) | 2019-04-01 | 2019-04-01 | User device, control device, and communication control method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020204092A1 true WO2020204092A1 (en) | 2020-10-08 |
Family
ID=72668510
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2020/015075 WO2020204092A1 (en) | 2019-04-01 | 2020-04-01 | User device, control device, and communication control method |
Country Status (2)
Country | Link |
---|---|
JP (1) | JP2020170896A (en) |
WO (1) | WO2020204092A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210368434A1 (en) * | 2020-05-21 | 2021-11-25 | Samsung Electronics Co., Ltd. | Method and apparatus for discovering and selecting network providing connectivity for provisioning user subscription data |
CN116114315A (en) * | 2020-11-09 | 2023-05-12 | Oppo广东移动通信有限公司 | Wireless communication method, terminal equipment and network equipment |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20230379810A1 (en) * | 2020-10-16 | 2023-11-23 | Nec Corporation | Ue, core network node, an node, and methods therefor |
CN114389943B (en) * | 2020-10-22 | 2023-08-15 | 中移(成都)信息通信科技有限公司 | Network configuration method, device, equipment and computer storage medium |
WO2023152847A1 (en) * | 2022-02-09 | 2023-08-17 | 株式会社Nttドコモ | Network node and communication method |
WO2023152846A1 (en) * | 2022-02-09 | 2023-08-17 | 株式会社Nttドコモ | Network node and communication method |
-
2019
- 2019-04-01 JP JP2019070073A patent/JP2020170896A/en active Pending
-
2020
- 2020-04-01 WO PCT/JP2020/015075 patent/WO2020204092A1/en active Application Filing
Non-Patent Citations (3)
Title |
---|
NOKIA ET AL.: "Discussion of security solutions for SNPN service access via PLMN and vice versa ", 3GPP TSG SA WG3 #94AH S3-190850, 15 March 2019 (2019-03-15), pages 1 - 4, XP051687601 * |
QUALCOMM INCORPORATED: "PS Data Off status update when congestion control is applied in AMF", 3GPP TSG SA WG2 #130 S2-1901098, 25 January 2019 (2019-01-25), pages 1 - 5, XP051595668 * |
SHARP: "Clarification on S-NSSAI based congestion control upon PLMN change", 3GPP TSG CT WG1 #113 C1-188141, 30 November 2018 (2018-11-30), pages 1 - 22, XP051548316 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20210368434A1 (en) * | 2020-05-21 | 2021-11-25 | Samsung Electronics Co., Ltd. | Method and apparatus for discovering and selecting network providing connectivity for provisioning user subscription data |
CN116114315A (en) * | 2020-11-09 | 2023-05-12 | Oppo广东移动通信有限公司 | Wireless communication method, terminal equipment and network equipment |
Also Published As
Publication number | Publication date |
---|---|
JP2020170896A (en) | 2020-10-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020204092A1 (en) | User device, control device, and communication control method | |
WO2021205955A1 (en) | User equipment (ue) and communication method for ue | |
JP2023018164A (en) | UE (User Equipment) | |
WO2021060383A1 (en) | User device and core network device | |
WO2021015200A1 (en) | User device, intra-core network device, and communication control method | |
WO2021015199A1 (en) | User equipment, device in core network, and communication control method | |
WO2020218537A1 (en) | Ue and control device within core network | |
WO2022097702A1 (en) | User equipment (ue) and communication control method executed by ue | |
WO2022097703A1 (en) | User equipment (ue) and communication control method performed by ue | |
WO2021132288A1 (en) | User Equipment (UE) | |
WO2022071197A1 (en) | User Equipment (UE) AND COMMUNICATION CONTROL METHOD | |
WO2022071198A1 (en) | User Equipment (UE) AND COMMUNICATION CONTROL METHOD | |
WO2021029380A1 (en) | User equipment | |
WO2021085568A1 (en) | Ue (user equipment) | |
WO2021085570A1 (en) | User equipment (ue) | |
WO2021132502A1 (en) | Ue, control device, and communication control method | |
JP2022161416A (en) | UE (User Equipment) | |
JP2021166360A (en) | UE (User Equipment) | |
WO2021235271A1 (en) | User Equipment (UE) AND COMMUNICATION CONTROL METHOD | |
WO2021235270A1 (en) | User Equipment (UE) AND COMMUNICATION CONTROL METHOD | |
WO2021235221A1 (en) | User equipment (ue) and communication control method | |
WO2021235262A1 (en) | User equipment (ue) and communication control method | |
WO2022071199A1 (en) | User Equipment (UE) AND COMMUNICATION CONTROL METHOD | |
WO2022107778A1 (en) | User equipment (ue) and communication control method | |
WO2022215595A1 (en) | User equipment (ue) and communication control method |
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: 20781998 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20781998 Country of ref document: EP Kind code of ref document: A1 |