WO2018207837A1 - ユーザ装置 - Google Patents
ユーザ装置 Download PDFInfo
- Publication number
- WO2018207837A1 WO2018207837A1 PCT/JP2018/017974 JP2018017974W WO2018207837A1 WO 2018207837 A1 WO2018207837 A1 WO 2018207837A1 JP 2018017974 W JP2018017974 W JP 2018017974W WO 2018207837 A1 WO2018207837 A1 WO 2018207837A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- pdu session
- identification information
- ladn
- procedure
- message
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/08—Upper layer protocols
- H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/34—Selective release of ongoing connections
Definitions
- the present invention relates to a user device.
- This application claims the benefit of priority to Japanese Patent Application No. 2017-92901 filed in Japan on May 9, 2017. By referring to it, the entire contents of this application are It is included in the application.
- 3GPP (3rd Generation Partnership Project), which conducts standardization activities for mobile communication systems in recent years, is studying SAE (System Architecture Evolution), which is an LTE (Long Term Evolution) system architecture.
- SAE System Architecture Evolution
- LTE Long Term Evolution
- 3GPP has specified EPS (Evolved Packet System) as a communication system for realizing all IP (Internet Protocol).
- EPC Evolved Packet Core
- 5G Next-generation mobile communication system
- 5G System
- LADN Local Area Data Data Network
- 5GS in addition to general DN (Data Network) equivalent to PDN (Packet Data Network) in 4G, LADN (Local Area Data Data Network) which is a DN that user equipment can connect to only at a specific location (See Non-Patent Document 1 and Non-Patent Document 2).
- the control method performed by each device configuring 5GS in order for the user device to establish a PDU session with respect to LADN which is a special DN, is not yet defined. Also, it is not clear whether all user apparatuses may establish a PDU session for LADN or whether a PDU session can be established for LADN.
- the present invention has been made in view of such circumstances, and its purpose is to provide a control method to be performed by each device configuring 5GS in order for a user device to establish a PDU session for LADN, and It is to provide a user device or the like for enabling only a user device connectable to LADN to establish a PDU session to LADN.
- the user apparatus of the present invention transmits a registration request message including information indicating that transmission of LADN (Local Area Data Data Network) information is requested to the AMF in the registration procedure for the core network. And establishes a first PDU session with a DN different from the LADN by executing a PDU session establishment procedure initiated by the user equipment, in an area connectable to the LADN. When moving, a second PDU session with the LADN is established by executing a PDU session establishment procedure initiated by the network.
- LADN Local Area Data Data Network
- the user apparatus of the present invention transmits a first RS (Router Solicitation) in the PDU session establishment procedure for establishing the first PDU session, and the LADN from the apparatus that has received the RS
- a first RA (Router-Advertisement) including information indicating a preference for a different DN is received.
- the user apparatus of the present invention transmits a second RS (Router Solicitation) in a PDU session establishment procedure for establishing the second PDU session, and a preference for the LADN from the apparatus that has received the RS.
- a second RA Raster-Advertisement
- the user apparatus of the present invention compares the value of information indicating the preference for the LADN with the value of information indicating the preference for a DN different from the LADN, and the value of the information indicating the preference for the LADN is the LADN. Is higher than the value of the information indicating the preference for the DN different from the above, the PDU session for the LADN is maintained, the PDU session for the DN different from the LADN is released, and the value of the information indicating the preference for the LADN is When the value is lower than the information indicating the preference for the DN different from the LADN, the PDU session for the DN different from the LADN is maintained and the PDU session for the LADN is released.
- the user apparatus of the present invention compares the value of the information indicating the preference for the LADN with the value of the information indicating the preference for the DN different from the LADN, the value of the information indicating the preference for the LADN, and the LADN
- the value of the information indicating the preference for the DN different from is the same, the PDU session for the LADN is always maintained and the PDU session for the DN different from the LADN is released.
- the user apparatus of the present invention compares the value of the information indicating the preference for the LADN with the value of the information indicating the preference for the DN different from the LADN, the value of the information indicating the preference for the LADN, and the LADN
- the value of the information indicating the preference for the DN different from is the same, the PDU session for the DN different from the LADN is always maintained and the PDU session for the LADN is released.
- only user devices having the ability to connect to LADN among user devices constituting 5GS can acquire LADN information. Further, the user apparatus that has acquired the LADN information can establish connectivity (session) to the LADN only at a specific place where the connection to the LADN is permitted.
- FIG. 2 is a diagram illustrating an example of a configuration of an access network in a mobile communication system.
- FIG. 2 is a diagram illustrating an example of a configuration of a core network in a mobile communication system. It is a figure which shows the apparatus structure of UE. It is a figure which shows the apparatus structure of eNB / NR node / WAG. It is a figure which shows the apparatus structure of AMF. It is a figure which shows the apparatus structure of SMF / UPF. It is a figure which shows an initial procedure. It is a figure which shows a registration procedure. It is a figure which shows the PDU session establishment procedure by UE trigger.
- the mobile communication system 1 (also referred to as 5GS) in the present embodiment includes user equipment (also referred to as a terminal device and a mobile terminal device) UE (User Equipment) _A10, an access network (AN; Access Network) _B. , Core network (CN) _B190, and data network (DN) _A5, DN_B105.
- user equipment also referred to as a terminal device and a mobile terminal device
- UE User Equipment
- AN Access Network
- CN Core network
- DN data network
- UE_A10 can be connected to a network service via 3GPP access (also referred to as 3GPP access or 3GPP access access network) and / or non-3GPP access (also referred to as non-3GPP access or non-3GPP access access network). It may be a simple device.
- the UE_A 10 may include a UICC (UniversalUniversIntegrated Circuit Card) and an eUICC (Embedded UICC).
- UE_A10 may be a wirelessly connectable terminal device, and may be a ME (Mobile Equipment), MS (Mobile Station), CIoT (Cellular Internet of Things) terminal (CIoT UE), or the like.
- UE_A 10 can be connected to an access network and / or a core network. Moreover, UE_A10 can connect with DN_A5 via an access network and / or a core network. UE_A10 transmits / receives (communications) user data to / from DN_A5 using a PDU (Protocol Data Unit or Packet Data Unit) session. Further, user data communication is not limited to IP (Internet Protocol) communication but may be non-IP communication.
- IP Internet Protocol
- IP communication is data communication using IP, and is data communication realized by transmission / reception of an IP packet provided with an IP header.
- the payload part which comprises an IP packet may contain the user data which UE_A10 transmits / receives.
- the non-IP communication is data communication that does not use IP, and is data communication that is realized by transmission / reception of data without an IP header.
- non-IP communication may be data communication realized by transmission / reception of application data to which no IP packet is attached, or another header such as a Mac header or an Ethernet (registered trademark) frame header is attached to UE_A10.
- User data to be transmitted / received may be transmitted / received.
- the PDU session is connectivity established between UE_A10 and DN_A5 and / or DN_B105 in order to provide a PDU connection service. More specifically, the PDU session may be connectivity established between UE_A 10 and the external gateway.
- the external gateway may be a UPF (User Plane Function), a PGW (Packet Data Network Gateway), or the like.
- the PDU session may be a communication path established for transmitting / receiving user data between the UE_A 10 and the core network and / or DN (DN_A5 and / or DN_B105), or a communication path for transmitting / receiving PDUs. Good.
- the PDU session may be a session established between UE_A10 and the core network and / or DN (DN_A5 and / or DN_B105), and transfer of one or more bearers or the like between each device in mobile communication system 1 It may be a logical communication path composed of paths. More specifically, the PDU session may be a connection established by UE_A10 between the core network_B190 and / or an external gateway, and a connection established between UE_A10 and UPF (UPF_A235 and / or UPF_B237). But you can. Further, the PDU session may be connectivity and / or connection between UE_A 10 and UPF (UPF_A235 and / or UPF_B237) via NR node_A122. Further, the PDU session may be identified by a PDU session ID and / or an EPS bearer ID.
- UE_A 10 can execute transmission / reception of user data using a PDU session with a device such as an application server arranged in DN_A 5 and / or DN_B 105.
- the PDU session can transfer user data transmitted and received between UE_A 10 and a device such as an application server arranged in DN_A5 and / or DN_B105.
- each device UE_A10, a device in the access network, and / or a device in the core network
- identification information includes APN (Access Point Name), TFT (Traffic Flow Template), session type, application identification information, DN_A5 and / or DN_B105 identification information, NSI (Network Slice Instance) identification information, and DCN. At least one of (Dedicated Core Core Network) identification information and access network identification information may be included, or other information may be further included. Further, when a plurality of PDU sessions are established, each identification information associated with the PDU session may have the same contents or different contents. Further, the NSI identification information is information for identifying the NSI, and may be NSI ID or Slice Instance ID hereinafter.
- the access network_B may be any of E-UTRAN (Evolved Universal Terrestrial Radio Access Network) _A80, 5G-RAN_A120, and WLAN ANc125.
- E-UTRAN_A80 and / or 5G-RAN_A120 may also be called a 3GPP access network
- WLAN-ANc125 may be called a non-3GPP access network.
- Each radio access network includes devices (for example, base station devices and access points) to which UE_A 10 is actually connected.
- E-UTRAN_A80 is an LTE access network and includes one or more eNB_A45.
- eNB_A45 is a radio base station to which UE_A10 is connected by E-UTRA (Evolved Universal Terrestrial Radio Access).
- E-UTRA Evolved Universal Terrestrial Radio Access
- the eNBs may be connected to each other.
- 5G-RAN_A120 is a 5G access network and includes one or more NR nodes (New Radio Access Technology Nodes) _A122.
- NR node_A 122 is a wireless base station to which UE_A 10 is connected by 5G wireless access (5G Radio Access). Further, when there are a plurality of NR node_A122 in 5G-RAN_A120, each NR node_A122 may be connected to each other.
- the 5G-RAN_A120 may be an access network configured by E-UTRA and / or 5G Radio Access.
- the 5G-RAN_A120 may include eNB_A45, NR node_A122, or both.
- eNB_A45 and NR node_A122 may be the same device. Therefore, NR node_A122 can be replaced with eNB_A45.
- WLAN ANc125 is a wireless LAN access network and includes one or more WAG (WLAN Access Gateway) _A126.
- WAG_A126 is a radio base station to which UE_A10 is connected by wireless LAN access. Further, WAG_A126 may be a gateway between the core network_B190 and WLAN ANc125. In WAG_A 126, the functional unit of the radio base station and the functional unit of the gateway may be configured as different devices.
- UE_A10 being connected to each radio access network means being connected to a base station device or an access point included in each radio access network. In other words, it goes through a base station device or an access point.
- the control message transmitted and received between UE_A10 and core network_B190 may be the same control message regardless of the type of access network. Therefore, UE_A10 and core network_B190 sending and receiving messages via NR node_A122 is the same as UE_A10 and core network_B190 sending messages via eNB_A45 and / or WAG_A126. Good.
- the access network is a wireless network connected to UE_A10 and / or the core network.
- the access network may be a 3GPP access network or a non-3GPP access network.
- the 3GPP access network may be E-UTRAN_A80, 5G-RAN (Radio Access Network) _A120, and the non-3GPP access network may be WLAN ANc125.
- the UE_A 10 may be connected to the access network in order to connect to the core network, or may be connected to the core network via the access network.
- DN_A5 and DN_B105 are data networks that provide communication services to UE_A10, and may be configured as packet data service networks or may be configured for each service. Furthermore, DN_A5 and DN_B105 may include a connected communication terminal. Therefore, the connection with DN_A5 and / or DN_B105 may be a connection with a communication terminal or server device arranged in DN_A5 and / or DN_B105. Furthermore, transmitting / receiving user data to / from DN_A5 and / or DN_B105 may be transmitting / receiving user data to / from a communication terminal or server device arranged in DN_A5 and / or DN_B105. DN_A5 and / or DN_B105 is outside the core network in FIG. 1, but may be inside the core network.
- the core network_B190 may be configured as one or more core network devices.
- the core network device may be a device that executes part or all of the processing or function of each device included in the core network_B190.
- the core network is an IP mobile communication network operated by a mobile communication operator (MNO: Mobile Network Operator) connected to the access network and / or DN_A5.
- the core network may be a core network for a mobile communication operator that operates and manages the mobile communication system 1, or a virtual mobile communication operator such as MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler) or a virtual network. It may be a core network for a mobile communication service provider.
- the core network_B190 may be an EPC (Evolved Packet Core) that constitutes EPS (Evolved Packet System) or 5GC (5G Core Core Network) that constitutes 5GS.
- the core network_B190 may be a core network of a system that provides a 5G communication service.
- the core network_B190 is not limited to this, and may be a network for providing a mobile communication service.
- Core network_B190 includes AUSF (Authentication Server Function), AMF (Access and Mobility Management Function) _A240, SDSF (Structured Data Storage network function), UDSF (Unstructured Data Storage network function), NEF (Network Exposure Function), NRF (NF Repository Function), PCF (Policy Control Function), SMF (Session Management Function) _A230, SMF (Session Management Function) _B232, UDM (Unified Data Management), UPF (User Plane Function) _A235, UPF (User Plane Function) At least one of _B237, AF (Application Function), and N3IWF (Non-3GPP InterWorking Function) may be included. These may be configured as NF (Network Function). The NF may refer to a processing function configured in the network.
- FIG. 3 shows only AMF (AMF_A240), SMF (SMF_A230 and SMF_B232), and UPF (UPF_A235 and UPF_B237). Or NF) is not implied.
- UE_A10 is also referred to as UE
- AMF_A240 is also referred to as AMF
- SMF_A230 and SMF_B232 are also referred to as SMF
- UPF_A235 and UPF_B237 are also referred to as UPF
- DN_A5 and DN_B105 are also referred to as DN.
- FIG. 3 shows an N1 interface (hereinafter also referred to as a reference point), an N2 interface, an N3 interface, an N4 interface, an N6 interface, and an N11 interface.
- N1 interface is an interface between UE and AMF
- N2 interface is an interface between (R) AN (access network) and AMF
- N3 interface is (R) AN (access network).
- the interface between UPF, N4 interface is the interface between SMF and UPF
- N6 interface is the interface between UPF and DN
- N11 interface is the interface between AMF and SMF. .
- each device can communicate.
- FIG. 3 is a system configuration diagram in the case where the UE accesses two DNs simultaneously using a plurality of PDU sessions. Two SMFs have been selected for two different PDU sessions. In FIG. 3, there are two SMF_A230 and two UPF_A235.
- AMF_A240 is connected to other AMF, SMF (SMF_A230 and / or SMF_B232), access network (that is, E-UTRAN_A80 and 5G-RAN_A120 and WLAN-ANc125), UDM, AUSF, and PCF.
- AMF_A240 is registration management, connection management, reachability management, mobility management such as UE_A10, and SM (Session Management) message transfer between UE and SMF.
- AMF_A240 may be arranged in the core network_B190.
- AMF_A240 may be an NF that manages one or more NSIs (Network Slice Instance).
- AMF_A240 may be a shared CP function (CCNF; “Common CPNF (Control Plane Network Function)) shared between a plurality of NSIs.
- the RM state includes an unregistered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state).
- RM-DEREGISTERED state since the UE is not registered in the network, the AMF cannot reach the UE because the UE context in the AMF does not have valid location information or routing information for the UE. is there.
- RM-REGISTERED state since the UE is registered in the network, the UE can receive a service that needs to be registered with the network.
- 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 (NAS signaling connection) established with the AMF via the N1 interface.
- NAS signaling connection NAS signaling connection
- the UE does not have an N2 interface connection (N2 connection) and an N3 interface connection (N3 connection).
- N2 connection N2 connection
- N3 connection N3 interface connection
- the CM-CONNECTED state it has NAS signaling connection (NAS signaling connection) established with AMF via N1 interface.
- the CM-CONNECTED state the UE may have an N2 interface connection (N2Nconnection) and / or an N3 interface connection (N3 connection).
- SMF_A230 is connected to AMF_A240, UPF_A235, UDM, PCF.
- SMF_B232 is connected to AMF_A240, UPF_B237, UDM, and PCF.
- SMF_A230 and SMF_B232 are session management such as PDU session (Session Management), IP address allocation to the UE (IP address allocation), UPF selection and control, UPF setting to route traffic to appropriate destination, downlink A function that notifies the arrival of data (Downlink Data Notification), an identifier of SM information (per AN) that is transmitted to the AN via the N2 interface via AMF, and SSC mode for the session It may be responsible for determining (Session and Service Continuity ⁇ mode), roaming function, etc.
- SMF_A230 and SMF_B232 are described as separate devices or NFs, they may be the same device or function.
- UPF_A235 is connected to DN_A5, SMF_A230, other UPFs, and access networks (that is, E-UTRAN_A80, 5G-RAN_A120, and WLAN ANc125).
- UPF_B237 is connected to DN_B105, SMF_B232, another UPF, and an access network (that is, E-UTRAN_A80, 5G-RAN_A120, and WLAN ANc125).
- UPF_A235 and UPF_B237 are anchors for intra-RAT mobility or inter-RAT mobility, packet routing and forwarding (Packet routing & forwarding), UL CL (Uplink Classifier) that supports routing of multiple traffic flows for one DN Functions, Branching point function that supports multi-homed PDU session, QoS processing for user plane, uplink traffic verification, downlink packet buffering, downlink data notification (Downlink Data Notification) ) Trigger function or the like. Further, UPF_A235 and UPF_B237 may be relay apparatuses that transfer user data as a gateway between DN_A5 and core network_B190 and a gateway between DN_B105 and core network_B190, respectively.
- UPF_A235 and UPF_B237 may be gateways for IP communication and / or non-IP communication. Furthermore, UPF_A235 and UPF_B237 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 may be gateways connecting the core network_B190 and a single DN. Note that UPF_A235 and UPF_B237 may have connectivity with other NFs, and may be connected to each device via other NFs.
- UPF_A235 and UPF_B237 are described as separate devices or NFs, they are different UPF_A235 and UPF_B237 between UPF_A235 and the access network, and between UPF_B237 and the access network, and are common UPF_C239. (also referred to as branching point or uplink classifier). If UPF_C239 is present, the PDU session between UE_A10 and DN_A5 is established via the access network, UPF_C239, UPF_A235, and the PDU session between UE_A10 and DN_B105 is established via the access network, UPF_C239, UPF_B237 Will be.
- U-Plane User Plane
- C-Plane Control Plane
- U-Plane User Plane
- Control Plane may be a communication path for transmitting and receiving control messages, and may be configured by a plurality of bearers.
- AUSF is connected to UDM and AMF_A240. AUSF functions as an authentication server.
- SDSF provides functions for NEF to store and retrieve information as structured data.
- UDSF provides a function for all NFs to store and retrieve information as unstructured data.
- NEF provides a means to securely provide services and capabilities provided by 3GPP networks. Stores information received from other NFs as structured data (structured data).
- an NRF When an NRF receives an NF discovery request (NF Discovery Request) from an NF instance, the NRF provides information on the discovered NF instance to the NF, information on available NF instances, and information on services supported by the instances. Or hold.
- NF Discovery Request NF Discovery Request
- PCF is connected to SMF (SMF_A230, SMF_B232), AF, AMF_A240. Provides policy rules, etc.
- the UDM is connected to AMF_A240, SMF (SMF_A230, SMF_B232), AUSF, and PCF.
- UDM includes UDM FE (application front end) and UDR (User Data Repository).
- UDM FE performs processing such as authentication information (credentials), location management (location management), and subscriber management (subscription management).
- the UDR stores the data required for UDM FE and the policy profiles required by the PCF.
- AF is connected to PCF. AF affects traffic routing and participates in policy control.
- N3IWF establishes an IPsec tunnel with UE, relays NAS (N1) signaling between UE and AMF, processes N2 signaling sent from SMF and relayed by AMF, establishes IPsec Security Association (IPsec SA) Provides functions such as relaying of user plane packets between UE and UPF, AMF selection, etc.
- IPsec SA IPsec Security Association
- UE_A10 includes a control unit_A400, a transmission / reception unit_A420, and a storage unit_A440.
- the transmission / reception unit_A420 and the storage unit_A440 are connected to the control unit_A400 via a bus.
- an external antenna 410 is connected to the transmission / reception unit_A420.
- the storage unit_A440 stores the UE context 442.
- the control unit_A400 is a functional unit for controlling the entire UE_A10, and implements various processes of the entire UE_A10 by reading and executing various types of information and programs stored in the storage unit_A440.
- the transmission / reception unit_A420 is a functional unit for the UE_A10 to connect to an access network by connecting to a base station (E-UTRAN_A80 and 5G-RAN_A120) and / or an access point (WLAN ANc125) in the access network.
- the UE_A 10 can be connected to a base station and / or an access point in the access network via the external antenna 410 connected to the transmission / reception unit_A 420.
- UE_A10 transmits / receives user data and / or control information to / from a base station and / or access point in the access network via external antenna 410 connected to transmission / reception unit_A420. Can do.
- the storage unit_A440 is a functional unit that stores programs and data necessary for each operation of the UE_A10, and includes, for example, a semiconductor memory, an HDD (Hard Disk Drive), an SSD (Solid State Drive), and the like.
- the storage unit_A440 stores identification information, control information, flags, parameters, and the like included in control messages that are transmitted and received in a communication procedure described later.
- the UE context 442 stored in the storage unit _A440 may include a UE context used when connecting to the access network_B80 / 120/125 and a UE context used when connecting to the core network_B190. .
- the UE context 442 may include a UE context stored for each UE, a UE context stored for each PDU session, and a UE context stored for each bearer.
- the UE context stored for each UE may include IMSI, EMMIState, GUTI, and ME Identity.
- the UE context stored for each PDU session may include APN in Use, Assigned Session Type, IP Address (es), and Default Bearer.
- the UE context stored for each bearer may include EPS Bearer ID, TI, and TFT.
- FIG. 5 shows a device configuration example of eNB_A45, NR node_A122, and WAG_A126.
- eNB_A45, NR node_A122, and WAG_A126 are configured by a control unit_B500, a network connection unit_B520, a transmission / reception unit_B530, and a storage unit_B540.
- the network connection unit_B520, the transmission / reception unit_B530, and the storage unit_B540 are connected to the control unit_B500 via a bus.
- an external antenna 510 is connected to the transmission / reception unit_B530.
- the control unit _B500 is a functional unit for controlling the entire eNB_A45, NR node_A122, and WAG_A126, and by reading and executing various information and programs stored in the storage unit_B540, the eNB_A45, NR node_A122 And various processes of the entire WAG_A 126 are realized.
- the network connection unit_B520 is a functional unit for the eNB_A45, NR node_A122, and WAG_A126 to connect to the AMF_A240 and UPF_A235 in the core network.
- eNB_A45, NR node_A122, and WAG_A126 can be connected to AMF_A240 and UPF_A235 in the core network via network connection unit_B520.
- the eNB_A45, the NR node_A122, and the WAG_A126 can transmit / receive user data and / or control information to / from the AMF_A240 and / or UPF_A235 via the network connection unit_B520.
- the transmission / reception unit_B530 is a functional unit for the eNB_A45, NR node_A122, and WAG_A126 to connect to the UE_A10.
- eNB_A45, NR_node_A122, and WAG_A126 can transmit / receive user data and / or control information to / from UE_A10 via transmission / reception unit_B530.
- Storage unit_B540 is a functional unit that stores programs, data, and the like necessary for the operations of eNB_A45, NR node_A122, and WAG_A126.
- the storage unit_B540 is configured by, for example, a semiconductor memory, HDD, SSD, or the like.
- the storage unit_B540 stores identification information, control information, flags, parameters, and the like included in control messages that are transmitted and received within a communication procedure described later.
- the storage unit_B540 may store these pieces of information as contexts for each UE_A10.
- FIG. 6 shows a device configuration example of AMF_A240.
- AMF_A240 includes a control unit_C600, a network connection unit_C620, and a storage unit_C640.
- the network connection unit _C620 and the storage unit _C640 are connected to the control unit _C600 through a bus.
- the storage unit _C640 stores a context 642.
- the control unit_C600 is a functional unit for controlling the entire AMF_A240, and implements various processes of the entire AMF_A240 by reading and executing various information and programs stored in the storage unit_C640.
- Network connection unit _C620 allows AMF_A240 to connect to other AMF_240, SMF_A230, base stations (E-UTRAN_A80 and 5G-RAN_A120) and / or access point (WLAN ANc125), UDM, AUSF, PCF in the access network It is a functional part.
- AMF_A240 can send and receive user data and / or control information to and from the base station and / or access point, UDM, AUSF, and PCF in the access network via the network connection unit _C620. .
- Storage unit_C640 is a functional unit that stores programs and data necessary for each operation of AMF_A240.
- the storage unit_C640 is configured by, for example, a semiconductor memory, HDD, SSD, or the like.
- the storage unit_C640 stores identification information, control information, flags, parameters, and the like included in control messages that are transmitted and received within a communication procedure described later.
- the context 642 stored in the storage unit_C640 may include a context stored for each UE, a context stored for each PDU session, and a context stored for each bearer.
- Contexts stored for each UE include IMSI, MSISDN, MM State, GUTI, ME Identity, UE Radio Access Capability, UE Network Capability, MS Network Capability, Access Restriction, MME F-TEID, SGW F-TEID, eNB Address MME UE S1AP ID, eNB UE S1AP ID, NR node Address, NR node ID, WAG Address, and WAG ID.
- the context stored for each PDU session may include APN in Use, Assigned Session Type, IP Address (es), PGW F-TEID, SCEF ID, and Default bearer.
- the context stored for each bearer is EPS ⁇ Bearer ID, TI, TFT, SGW F-TEID, PGW F-TEID, MME F-TEID, eNB Address, NR node Address, WAG Address, eNB ID, NR node ID and WAG ID may be included.
- FIG. 7 shows device configuration examples of SMF_A230 and SMF_B232.
- the SMF_A 230 includes a control unit_D700, a network connection unit_D720, and a storage unit_D740, respectively.
- the network connection unit _D720 and the storage unit _D740 are connected to the control unit _D700 via a bus.
- the storage unit_D740 stores a context 742.
- the control unit _D700 of the SMF_A230 is a functional unit for controlling the entire SMF_A230. By reading and executing various information and programs stored in the storage unit _D740, various processes of the entire SMF_A230 are realized. To do.
- the network connection part_D720 of SMF_A230 is a functional part for SMF_A230 to connect with AMF_A240, UPF_A235, UDM, PCF.
- the SMF_A 230 can transmit / receive user data and / or control information to / from the AMF_A 240, UPF_A 235, UDM, and PCF through the network connection unit_D720.
- the storage unit_D740 of the SMF_A230 is a functional unit that stores programs and data necessary for each operation of the SMF_A230.
- the storage unit_D740 of the SMF_A230 is configured by, for example, a semiconductor memory, HDD, SSD, or the like.
- the storage unit_D740 of the SMF_A230 stores identification information, control information, flags, parameters, and the like included in control messages that are transmitted and received within a communication procedure described later.
- the context 742 stored in the storage unit_D740 of the SMF_A230 is stored for each bearer, the context stored for each UE, the context stored for each APN, the context stored for each PDU session, and the bearer. There may be contexts.
- the context stored for each UE may include IMSI, ME Identity, MSISDN, and RAT type.
- the context stored for each APN may include APN in use. Note that the context stored for each APN may be stored for each Data ⁇ ⁇ Network Identifier.
- the context stored for each PDU session may include Assigned Session Type, IP Address (es), SGW F-TEID, PGW F-TEID, and Default Bearer.
- the context stored for each bearer may include EPS Bearer ID, TFT, SGW F-TEID, PGW F-TEID.
- SMF_B232 is configured in the same way as SMA_A230.
- FIG. 7 shows a device configuration example of UPF_A235 and UPF_B237.
- UPF_A235 includes a control unit_D700, a network connection unit_D720, and a storage unit_D740, respectively.
- the network connection unit _D720 and the storage unit _D740 are connected to the control unit _D700 via a bus.
- the storage unit_D740 stores a context 742.
- the UPF_A235 control unit_D700 is a functional unit for controlling the entire UPF_A235. By reading and executing various types of information and programs stored in the storage unit_D740, various processes of the UPF_A235 are realized. To do.
- the network connection part_D720 of UPF_A235 has UPF_A235 as DN (i.e., DN_A5 and / or DN_B105), SMF_A230, other UPF_A235, and access network (i.e., E-UTRAN_A80, 5G-RAN_A120 and WLAN ANc125). It is a functional part for connection.
- UPF_A235 is connected via the network connection _D720 via DN (i.e., DN_A5 and / or DN_B105), SMF_A230, other UPF_A235, and access network (i.e., E-UTRAN_A80 and 5G-RAN_A120 and WLAN ANc125).
- User data and / or control information can be transmitted to and received from.
- the storage unit_D740 of the UPF_A235 is a functional unit that stores programs, data, and the like necessary for each operation of the UPF_A235.
- the storage unit_D740 of the UPF_A235 is configured by, for example, a semiconductor memory, HDD, SSD, or the like.
- the storage unit_D740 of the UPF_A235 stores identification information, control information, flags, parameters, and the like included in control messages that are transmitted and received within a communication procedure described later.
- the context 742 stored in the storage unit _D740 of UPF_A235 is stored for each bearer, context stored for each UE, context stored for each APN, context stored for each PDU session, and bearer. There may be contexts.
- the context stored for each UE may include IMSI, ME Identity, MSISDN, and RAT type.
- the context stored for each APN may include APN in use. Note that the context stored for each APN may be stored for each Data ⁇ ⁇ Network Identifier.
- the context stored for each PDU session may include Assigned Session Type, IP Address (es), SGW F-TEID, PGW F-TEID, and Default Bearer.
- the context stored for each bearer may include EPS Bearer ID, TFT, SGW F-TEID, PGW F-TEID.
- UPF_B237 has the same configuration as UPF_A235.
- IMSI International Mobile Subscriber Identity
- MME_A40 / CPF_A140 / AMF_A2400 and SGW_A35 may be equal to the IMSI stored in HSS_A50.
- EMM State / MM State indicates the mobility management state of UE_A10 or MME_A40 / CPF_A140 / AMF_A240.
- the EMM State / MM State may be an EMM-REGISTERED state (registered state) in which UE_A10 is registered in the network and / or an EMM-DEREGISTERD state (unregistered state) in which UE_A10 is not registered in the network.
- EMM State / MM State may be an ECM-CONNECTED state in which the connection between the UE_A 10 and the core network is maintained and / or an ECM-IDLE state in which the connection is released.
- the EMM State / MM State may be information that can distinguish the state in which the UE_A 10 is registered in the EPC and the state in which the UE_A 10 is registered in the NGC or 5GC.
- GUTI Globally Unique Temporary Identity
- MME_A40 / CPF_A140 / AMF_A240 GUMMEI (Globally Unique MME Identifier)
- M-TMSI M-Temporary Mobile Subscriber Identity
- ME Identity is an ID of UE_A10 or ME, and may be, for example, IMEI (International Mobile Equipment Identity) or IMEISV (IMEI Software Version).
- MSISDN represents the basic telephone number of UE_A10.
- the MSISDN stored in MME_A40 / CPF_A140 / AMF_A240 may be information indicated by the storage unit of HSS_A50.
- the GUTI may include information for identifying CPF_140.
- MME F-TEID is information for identifying MME_A40 / CPF_A140 / AMF_A240.
- the MME F-TEID may contain the IP address of MME_A40 / CPF_A140 / AMF_A240, the TEID (Tunnel Endpoint Identifier) of MME_A40 / CPF_A140 / AMF_A240, or both of them. Also good. Further, the IP address of MME_A40 / CPF_A140 / AMF_A240 and the TEID of MME_A40 / CPF_A140 / AMF_A240 may be stored independently. Further, the MME F-TEID may be identification information for user data or identification information for control information.
- SGW F-TEID is information that identifies SGW_A35.
- the SGW F-TEID may include the IP address of SGW_A35, may include the TEID of SGW_A35, or may include both of them. Further, the IP address of SGW_A35 and the TEID of SGW_A35 may be stored independently. Further, the SGWTEF-TEID may be identification information for user data or identification information for control information.
- PGW F-TEID is information for identifying PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235.
- the PGW F-TEID may contain the IP address of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235, the TEGW of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235, or both. Good.
- the IP address of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235 and the TEID of PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235 may be stored independently.
- the PGW F-TEID may be identification information for user data or identification information for control information.
- ENB F-TEID is information that identifies eNB_A45.
- the eNB F-TEID may include the IP address of eNB_A45, may include the TEID of eNB_A45, or may include both. Further, the IP address of eNB_A45 and the TEID of SGW_A35 may be stored independently. Further, the eNB F-TEID may be identification information for user data or identification information for control information.
- the APN may be identification information that identifies the core network and an external network such as a DN. Furthermore, the APN can also be used as information for selecting a gateway such as PGW_A30 / UPGW_A130 / UPF_A235 that connects the core network A_90.
- the APN may be DNN (Data Network Name). Therefore, APN may be expressed as DNN, or DNN may be expressed as APN.
- the APN may be identification information for identifying such a gateway, or identification information for identifying an external network such as a DN.
- identification information for identifying such a gateway or identification information for identifying an external network such as a DN.
- UE Radio Access Capability is identification information indicating the radio access capability of UE_A10.
- UE Network Capability includes security algorithms and key derivation functions supported by UE_A10.
- MS Network Capability is information including one or more pieces of information necessary for SGSN_A 42 for UE_A 10 having the GERAN_A 25 and / or UTRAN_A 20 functions.
- Access Restriction is registration information of access restriction.
- eNB Address is the IP address of eNB_A45.
- MME UE S1AP ID is information for identifying UE_A10 in MME_A40 / CPF_A140 / AMF_A240.
- eNB UE S1AP ID is information for identifying UE_A10 in eNB_A45.
- APNAPin Use is a recently used APN.
- APN in Use can be Data Network Identifier. This APN may be composed of network identification information and default operator identification information. Further, APN in Use may be information for identifying the DN of the establishment destination of the PDU session.
- Assigned Session Type is information indicating the type of PDU session. Assigned Session Type may be Assigned PDN Type. The type of PDU session may be IP or non-IP. Furthermore, when the type of the PDU session is IP, information indicating the type of PDN allocated from the network may be further included. The Assigned Session Type may be IPv4, IPv6, or IPv4v6.
- IP Address is an IP address assigned to the UE.
- the IP address may be an IPv4 address, an IPv6 address, or an IPv6 prefix.
- Assigned Session Type indicates non-IP, the IP Address element need not be included.
- DN ID is identification information that identifies the core network_B190 and an external network such as DN. Further, the DN ID can also be used as information for selecting a gateway such as UPGW_A130 or PF_A235 that connects the core network_B190.
- the DN ID may be identification information for identifying such a gateway, or identification information for identifying an external network such as a DN.
- a plurality of gateways that connect the core network_B190 and the DN there may be a plurality of gateways that can be selected by the DN ID. Further, one gateway may be selected from the plurality of gateways by another method using identification information other than the DN ID.
- the DN ID may be the same information as the APN, or may be information different from the APN. If the DN ID and APN are different information, each device may manage information indicating the correspondence between the DN ID and APN, or perform a procedure for inquiring the APN using the DN ID. Alternatively, a procedure for inquiring about the DN ID using the APN may be performed.
- SCEF IV ID is the SCEF_A46 IP address used in the PDU session.
- Default Bearer is information acquired and / or generated when a PDU session is established, and is EPS bearer identification information for identifying a default bearer associated with a PDU session.
- EPS Bearer ID is the EPS bearer identification information.
- the EPS Bearer ID may be identification information for identifying SRB (SignallingallRadio Bearer) and / or CRB (Control-plane-Radio bearer), or may be identification information for identifying DRB (Data Radio Bearer).
- TI Transaction Identifier
- the EPS Bearer ID may be EPS bearer identification information for identifying a dedicated bearer. Therefore, identification information for identifying an EPS bearer different from the default bearer may be used.
- TFT indicates all packet filters associated with the EPS bearer.
- the TFT is information for identifying a part of user data to be transmitted / received, and the UE_A 10 transmits / receives the user data identified by the TFT using an EPS bearer associated with the TFT.
- UE_A 10 transmits and receives user data identified by the TFT using an RB (RadioRadBearer) associated with the TFT.
- the TFT may associate user data such as application data to be transmitted / received with an appropriate transfer path, or may be identification information for identifying application data.
- UE_A10 may transmit / receive user data that cannot be identified by TFT using a default bearer.
- UE_A10 may memorize
- Default Bearer is EPS bearer identification information that identifies the default bearer associated with the PDU session.
- the EPS bearer may be a logical communication path established between UE_A10 and PGW_A30 / UPGW_A130 / UPF_A235, or may be a communication path constituting a PDN connection / PDU session. Further, the EPS bearer may be a default bearer or a dedicated bearer. Furthermore, the EPS bearer may be configured to include an RB established between the UE_A 10 and a base station and / or access point in the access network. Furthermore, RBs and EPS bearers may be associated one-to-one.
- the RB identification information may be associated with the EPS bearer identification information on a one-to-one basis, or may be the same identification information.
- RB may be SRB and / or CRB or DRB.
- Default Bearer may be information that UE_A10 and / or SGW_A35 and / or PGW_A30 / UPGW_A130 / SMF_A230 / UPF_A235 acquire from the core network when a PDU session is established.
- the default bearer is an EPS bearer that is first established in a PDN connection / PDU session, and is an EPS bearer that can be established only in one PDN connection / PDU session.
- the default bearer may be an EPS bearer that can be used for communication of user data not associated with the TFT.
- a dedicated bearer is an EPS bearer that is established after a default bearer is established in a PDN connection / PDU session, and a plurality of EPS bearers that can be established in one PDN connection / PDU session. is there.
- a dedicated bearer is an EPS bearer that can be used for communication of user data associated with a TFT.
- User Identity is information for identifying a subscriber.
- User Identity may be IMSI or MSISDN. Further, the user identity may be identification information other than IMSI or MSISDN.
- Serving Node Information is information for identifying MME_A40 / CPF_A140 / AMF_A240 used in the PDU session, and may be the IP address of MME_A40 / CPF_A140 / AMF_A240.
- ENB Address is the IP address of eNB_A45.
- the eNB ID is information for identifying the UE in the eNB_A45.
- MME Address is the IP address of MME_A40 / CPF_A140 / AMF_A240.
- the MME ID is information for identifying MME_A40 / CPF_A140 / AMF_A240.
- NR node Address is the IP address of NR node_A122.
- NR node ID is information for identifying NR node_A122.
- WAG Address is the IP address of WAG_A126.
- WAG ID is information for identifying WAG_A126.
- the network refers to at least a part of the access network_B80 / 120/125, the core network_B190, DN_A5, and DN_B105.
- One or more devices included in at least a part of the access network_B80 / 120/125, the core network_B190, DN_A5, and DN_B105 may be referred to as a network or a network device. That is, the fact that the network executes message transmission / reception and / or procedures means that a device (network device) in the network executes message transmission / reception and / or procedures.
- the first DN is a general DN.
- the first DN may be a DN that is not a DN for MEC (MobileDNEdge Computing) (also referred to as LADN in this embodiment), or is not close to the point where UE_A10 is accessing. It may be a DN.
- the service provided by the first DN may be managed and / or operated by a third party, or may be managed and / or operated by an operator. Note that DN_A5 in FIGS. 1 and 3 corresponds to the first DN.
- the second DN is not a general DN but a DN for MEC (that is, LADN). That is, the second DN may be a local DN near the point where UE_A10 is accessing, or may be a DN not far from the point where UE_A10 is accessing. Further, the service provided by the second DN may be managed and / or operated by a third party, or may be managed and / or operated by an operator. Note that DN_B 105 in FIGS. 1 and 3 corresponds to the second DN. However, the second DN may be a general DN like the first DN.
- a session management (SM) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a NAS message used in a procedure for SM, and UE_A10 and SMF_A230 or AMF_A230 or It may be a control message transmitted / received between SMF_B232.
- the SM message includes a PDU session establishment request message, a PDU session establishment acceptance message, a PDU session completion message, a PDU session rejection message, a PDU session change request message, a PDU session change acceptance message, a PDU session change rejection message, and the like. May be.
- the procedure for SM may include a PDU session establishment procedure, a PDU session change procedure, and the like.
- the first state is a state in which UE_A 10 has established a PDU session for the first DN but is not connected to the second DN.
- UE_A 10 may be in a state where user data communication can be performed with respect to the first DN but user data communication cannot be performed with respect to the second DN.
- user data communication can be performed with the AF on the first DN, but user data communication cannot be performed with the AF on the second DN. It may be.
- the second state is a state in which UE_A 10 has established a PDU session for the first DN and has established a PDU session for connecting to the second DN. Further, in the second state, UE_A 10 may be in a state where user data communication can be performed for the first DN and user data communication can be performed for the second DN. In the second state, UE_A 10 can execute user data communication with the AF on the first DN, and user data communication with the AF on the second DN. May be in an executable state.
- the third state is a state in which UE_A 10 has not established a PDU session for the first DN but is connected to the second DN.
- the UE_A 10 may not be able to execute user data communication with respect to the first DN, but may be in a state where user data communication can be performed with respect to the second DN.
- user data communication cannot be executed with the AF on the first DN, but user data communication can be executed with the AF on the second DN. It may be.
- the tracking area (TA; also referred to as “Tracking” Area) is a range that can be represented by the location information of UE_A10 managed by the core network, and may be composed of, for example, one or more cells.
- the TA may be a range where a control message such as a paging message is broadcast, or a range where the UE_A 10 can move without performing a handover procedure.
- the TA list is a list including one or more TAs assigned to UE_A10 by the network.
- UE_A 10 may be able to move without executing the registration procedure while moving in one or more TAs included in the TA list.
- the TA list may be an information group indicating an area where UE_A 10 can move without executing a registration procedure.
- a network slice is a logical network that provides specific network capabilities and network characteristics.
- a network slice instance is composed of a network function (NF) instance (entity) and a set of necessary resources, and forms a network slice to be arranged.
- NF network function
- An NSI is an entity of a network slice (Network Slice) configured by one or more in the core network_B190.
- the NSI may be configured by a virtual NF (Network Function) generated using NST (Network Slice Template).
- NST is a logical expression of one or more NF (Network Function) associated with a resource request for providing a required communication service and capability. That is, the NSI may be an aggregate in the core network_B190 configured by a plurality of NFs.
- the NSI may be a logical network configured to separate user data delivered by services or the like.
- One or more NFs may be configured in the network slice.
- the NF configured in the network slice may or may not be a device shared with other network slices.
- a UE can be assigned to one or more network slices based on registration information and / or APN such as UE usage type and / or one or more network slice type IDs and / or one or more NS IDs.
- SSC Session and Service Continuity
- the mode may indicate a type of service session continuation supported by a PDU session established between UE_A 10 and TUPF (TerminatinginUser-PlanePFunction).
- the TUPF may be UPGW_A130 or UPF_A235.
- the SSC mode may be a mode indicating the type of service session continuation set for each PDU session.
- SSC mode may be configured from three modes, SSC mode 1, SSC mode 2, and SSC mode 3.
- TUPF may be NF (Network Function) for U-Plane (User-Plane). Further, the TUPF may be arranged in the core network or may be arranged in the access network.
- NF Network Function
- U-Plane User-Plane
- the TUPF may be arranged in the core network or may be arranged in the access network.
- SSC mode 1 is a service session continuation mode in which the same TUPF is maintained regardless of access technology such as RAT (Radio Access Technology) and cells used when UE_A10 connects to the network. More specifically, SSC mode 1 may be a mode that realizes service session continuation without changing the TUPF used by the established PDU session even when UE_A10 mobility occurs.
- RAT Radio Access Technology
- SSC mode 2 is a service session continuation mode in which the same TUPF is maintained only within the TUPF serving area. More specifically, SSC mode 2 may be a mode that realizes service session continuation without changing the TUPF used by the established PDU session as long as UE_A10 is in the TUPF serving area. In addition, SSC mode 2 is a mode that realizes service session continuation by changing the TUPF used by the established PDU session when UE_A10 mobility occurs, such as when leaving the TUPF serving area. Good.
- the TUPF serving area may be an area where one TUPF can provide a service session continuation function, or a subset of an access network such as a RAT or a cell used when the UE_A 10 connects to the network. It may be.
- the access network subset may be a network composed of one or more RATs and / or cells, or a TA.
- SSC mode 3 is a PDU session established between UE_A10 and TUPF, and / or a new PDU session via a new TUPF, and / or before disconnecting the communication path, and / or Alternatively, it is a service session continuation mode that permits establishment of a communication path.
- SSC mode 3 may be a service session continuation mode that allows UE_A10 to be multihoming.
- SSC mode 3 may be a mode in which service session continuation using TUPF associated with a plurality of PDU sessions and / or PDU sessions is permitted. In other words, in the case of SSC mode 3, each device may realize service session continuation using a plurality of PDU sessions, or may implement service session continuation using a plurality of TUPFs.
- the selection of a new TUPF may be performed by the network, and the new TUPF is located at the location where UE_A10 is connected to the network. It may be an optimal TUPF.
- UE_A10 immediately associates the communication of applications and / or flows with newly established PDU sessions. It may be implemented based on completion of communication.
- the first identification information is capability information indicating that the UE_A 10 supports connection to the second DN.
- the first identification information may be information indicating that the UE_A 10 supports establishment of a PDU session connected to the second DN.
- the PDU session connected to the second DN may be a PDU session established between the second DN and UE_A10, or UPF_A235 and UE_A10 connecting the core network and the second DN. It may be a PDU session established between the two.
- the PDU session connected to the second DN may be a PDU session for use in user data communication performed between the second DN and UE_A10.
- the first identification information may be a DNN that identifies the second DN.
- the eleventh identification information is capability information indicating that the network supports connection to the second DN.
- the eleventh identification information may be information indicating that the network supports or permits establishment of a PDU session connected to the second DN. May be.
- the twelfth identification information is information indicating a cause value (cause).
- the twelfth identification information may be information indicating that some requests are rejected.
- the twelfth identification information may be information indicating that the establishment of the PDU session connected to the second DN is temporarily prohibited, and the connection destination of the established PDU session is the first It may be information indicating that changing to the DN of 2 is temporarily prohibited.
- the twelfth identification information may be information indicating that establishment of a PDU session connected to the second DN is prohibited in the cell and / or TA to which UE_A10 is currently connected, The information may indicate that changing the connection destination of the established PDU session to the second DN is prohibited.
- the twelfth identification information, the information indicated by the twelfth identification information, and / or each information indicated by the thirteenth identification information may be a single identification information.
- the twelfth identification information may be single identification information including the meaning of each identification information with any one of the thirteenth to thirteenth identification information. Therefore, the twelfth identification information and the thirteenth identification information may be included in the control message as single identification information having both meanings of the two identification information.
- the thirteenth identification information is information indicating the value of the first timer. Based on the reception of the thirteenth identification information, UE_A10 may set the value indicated by the thirteenth identification information in the first timer, or may start the execution of the first timer.
- the 14th identification information is a DNN indicating a DN accessible by the UE_A 10 in the currently connected cell and / or TA. Further, the fourteenth identification information may be a DNN indicating a DN accessible by the UE_A 10 as the second DN in the currently connected cell and / or TA. Note that the 14th identification information may include one or more DNNs. Further, each DNN may be associated with information indicating whether or not it is a second DN.
- the 21st identification information is information indicating a cause value indicating that this procedure has been rejected.
- the 21st identification information may be information indicating that the network does not support connection to the second DN, or information indicating that the connection is not permitted. Further, the 21st identification information may be information indicating that connection to the second DN is temporarily prohibited, or in the cell and / or TA to which UE_A10 is currently connected, It may be information indicating that connection to the second DN is prohibited.
- the 21st identification information, the information indicated by the 21st identification information, and / or each information indicated by the 22nd identification information may be a single identification information.
- the 21st identification information may be a single identification information including the meaning of each identification information with any one of the 22nd to 22nd identification information. Therefore, the 21st identification information and the 22nd identification information may be included in the control message as single identification information having both meanings of the two identification information.
- the 22nd identification information is information indicating the value of the second timer. Based on reception of the 22nd identification information, UE_A10 may set the value indicated by the 22nd identification information in the second timer, or may start the execution of the second timer.
- the thirty-first identification information includes information indicating a request to set a new connection destination of the PDU session established or changed by this procedure as the second DN, and / or each identification information requested together with the thirty-first identification information. This is information indicating a request for setting the second DN as the communication destination of user data communication that can be executed using.
- the thirty-first identification information may be associated with one or more of the thirty-second to thirty-fifth identification information. More specifically, the 31st identification information and the 32nd identification information may be associated with each other to indicate that the DN requested by the 32nd identification information is the second DN. By associating the information with the 33rd identification information, the connection destination of the PDU session requested by the 33rd identification information may be indicated to be the second DN.
- the user data communication is performed between the second DN and the PDU session type and / or address requested by the thirty-fourth identification information by associating the thirty-first identification information with the thirty-fourth identification information. May indicate the PDU session type and / or address used in the.
- the TFT requested by the 35th identification information by associating the 31st identification information with the 35th identification information is a TFT used in user data communication performed with the second DN. May be indicated.
- the 31st identification information, the information indicating the second DN indicated by the 31st identification information, and / or each information indicated by the 32nd to 35th identification information is a single identification information. It's okay.
- the thirty-first identification information may be single identification information including the meaning of each identification information, with any one of the thirty-second to thirty-fifth identification information.
- the thirty-first identification information and the thirty-second identification information may be included in the control message as a single identification information having both meanings of the two identification information, or the thirty-first identification information and the thirty-third identification information. May be included in the control message as single identification information having both meanings of the two identification information. Further, the thirty-first identification information and the thirty-third identification information may be included in the control message as single identification information having both meanings of the two identification information, or the thirty-first identification information and the thirty-fourth identification information. May be included in the control message as single identification information having both meanings of the two identification information.
- the thirty-first identification information may be information indicating a request for establishment or change of a PDU session. Further, the thirty-first identification information may be information indicating a request to establish a PDU session connected to the second DN, or information indicating a request to change the connection destination of the PDU session to the second DN. There may be.
- the thirty-second identification information is information indicating DNN.
- the thirty-second identification information may be information indicating a request for setting the connection destination of the PDU session established or changed by this procedure to the DN identified by the DNN indicated by the identification information. A request to set the connection destination to the second DN may be indicated. Further, the thirty-second identification information may include a plurality of pieces of information indicating DNNs, or may include information indicating whether each DNN is a second DN.
- the thirty-second identification information may be information indicating a request to establish a PDU session connected to the second DN, or information indicating a request to change the connection destination of the PDU session to the second DN. There may be information indicating a request to make a PDU session established or changed by this procedure a PDU session used in user data communication performed for the second DN.
- the 33rd identification information is information indicating a PDU session ID (PDU session ID).
- the thirty-third identification information may be information indicating a request for establishing or changing the PDU session identified by the PDU session ID indicated by the identification information, or may be identified by the PDU session ID indicated by the identification information. A request to change the new connection destination of the PDU session to the second DN may be indicated.
- the thirty-third identification information may be information indicating a request to establish a PDU session connected to the second DN, or information indicating a request to change the connection destination of the PDU session to the second DN. There may be information indicating a request to make a PDU session established or changed by this procedure a PDU session used in user data communication performed for the second DN.
- the thirty-fourth identification information is information indicating a PDU session type (PDU (session Type).
- the thirty-fourth identification information may be information indicating an address.
- the PDU session type may be IPv4, “IPv6”, “Ethernet”, “Unstructured”, or the like.
- the address may be an IPv4 address, an IPv6 address, an IPv6 prefix, or information identifying UE_A10 used in communication such as Ethernet or Unstructured. Good.
- the PDU session type and address are not limited to these.
- the thirty-fourth identification information may be information indicating a request to change the PDU session type of the PDU session established or changed by this procedure to the PDU session type indicated by this identification information, or established by this procedure.
- it may be information indicating a request to make the address associated with the PDU session to be changed the address indicated by the identification information and / or the PDU session type address indicated in the present embodiment.
- the thirty-fourth identification information may be information indicating a request to change the PDU session type of the address used in the user data communication performed for the second DN to the PDU session type indicated by the identification information.
- the thirty-fourth identification information may include a plurality of pieces of information indicating PDU session types and / or addresses, and each PDU session type is used in user data communication performed for the second DN. Information indicating whether each address is an address used in the user data communication performed for the second DN may be included.
- the thirty-fourth identification information may be information indicating a request to establish a PDU session connected to the second DN, or information indicating a request to change the connection destination of the PDU session to the second DN. There may be information indicating a request to make a PDU session established or changed by this procedure a PDU session used in user data communication performed for the second DN.
- the 35th identification information is information indicating TFT.
- the thirty-fifth identification information may be information indicating a request to change the TFT associated with the PDU session established or changed by this procedure to the TFT indicated by this identification information, or for the second DN It may be information indicating a request to make the TFT used in the user data communication performed as the TFT indicated by the identification information.
- the 35th identification information may include a plurality of pieces of information indicating TFTs, or may include information indicating whether or not each TFT is a TFT used in user data communication performed for the second DN. Good.
- the 35th identification information may be information indicating a request to establish a PDU session connected to the second DN, or information indicating a request to change the connection destination of the PDU session to the second DN. There may be information indicating a request to make a PDU session established or changed by this procedure a PDU session used in user data communication performed for the second DN.
- the 41st identification information includes information indicating that the new connection destination of the PDU session established or changed by this procedure is the second DN, and / or identification information transmitted / received together with the 41st identification information. This is information indicating that the destination of user data communication that can be executed using the second DN is the second DN.
- the 41st identification information may be transmitted / received in association with one or more of the 42nd to 45th identification information.
- the DN identified by the DNN indicated by the forty-second identification information by associating the forty-first identification information with the forty-second identification information may indicate that the DN is the second DN
- the 41st identification information and the 43rd identification information may be associated with each other to indicate that the connection destination of the PDU session identified by the PDU session ID indicated by the 43rd identification information is the second DN.
- the address indicated by the 44th identification information and / or the address of the PDU session type indicated by the 44th identification information is the second DN.
- the address is used in user data communication performed between the TFT and the TFT indicated by the forty-fourth identification information by associating the forty-first identification information with the forty-fourth identification information. It may indicate that the TFT is used in user data communication performed between two DNs.
- the 41st identification information, the information indicating the second DN indicated by the 41st identification information, and / or each information indicated by the 42nd to 45th identification information is a single identification information. It's okay.
- the forty-first identification information may be a single identification information including the meaning of each identification information with any one of the forty-second to 45th identification information.
- the 41st identification information and the 42nd identification information may be included in the control message as a single identification information having both meanings of the two identification information, or the 41st identification information and the 43rd identification information. May be included in the control message as single identification information having both meanings of the two identification information. Further, the 41st identification information and the 43rd identification information may be included in the control message as a single identification information having both meanings of the two identification information, or the 41st identification information and the 44th identification information. May be included in the control message as single identification information having both meanings of the two identification information.
- the forty-first identification information may be information indicating that a request for establishing or changing a PDU session has been accepted.
- the 41st identification information may be information indicating that establishment of a PDU session connected to the second DN is permitted, or the connection destination of the PDU session may be changed to the second DN. It may be information indicating that permission has been granted.
- the forty-second identification information is information indicating DNN.
- the forty-second identification information may be information indicating that the connection destination of the PDU session established or changed by this procedure is the DN identified by the DNN indicated by the identification information. It may indicate that the connection destination is the second DN.
- the forty-second identification information may include a plurality of pieces of information indicating DNNs, or may include information indicating whether each DNN is a second DN.
- the forty-second identification information may be information indicating that a PDU session connected to the second DN has been established, or indicates that the connection destination of the PDU session has been changed to the second DN. It may be information, or information indicating that the PDU session established or changed by this procedure is a PDU session used in user data communication performed for the second DN.
- the 43rd identification information is information indicating a PDU session ID.
- the 43rd identification information may be information indicating that the PDU session identified by the PDU session ID indicated by the identification information is established or changed, or identified by the PDU session ID indicated by the identification information. It may indicate that the new connection destination of the PDU session to be performed becomes the second DN.
- the 43rd identification information may be information indicating that a PDU session connected to the second DN has been established, or indicates that the connection destination of the PDU session has been changed to the second DN. It may be information, or information indicating that the PDU session established or changed by this procedure is a PDU session used in user data communication performed for the second DN.
- the 44th identification information is information indicating the PDU session type.
- the 44th identification information may be information indicating an address.
- the 44th identification information may be information indicating that the PDU session type of the PDU session established or changed by this procedure has become the PDU session type indicated by this identification information.
- Information indicating that the address associated with the PDU session to be established or changed is the address indicated by the identification information and / or the address of the PDU session type indicated in the present embodiment.
- the 44th identification information may be information indicating that the PDU session type of the address used in the user data communication performed for the second DN is the PDU session type indicated by the identification information.
- the information used to indicate that the address used in the user data communication performed for the second DN is the address indicated by the identification information and / or the PDU session type address indicated in the present embodiment. There may be.
- the 44th identification information may include a plurality of information indicating the PDU session type and / or address, and the PDU session type used in user data communication in which each PDU session type is performed for the second DN. Information indicating whether each address is an address used in the user data communication performed for the second DN may be included.
- the 44th identification information may be information indicating that a PDU session connected to the second DN is established, or indicates that the connection destination of the PDU session is changed to the second DN. It may be information, or information indicating that the PDU session established or changed by this procedure is a PDU session used in user data communication performed for the second DN.
- the 45th identification information is information indicating TFT.
- the 45th identification information may be information indicating that the TFT associated with the PDU session established or changed by this procedure has become the TFT indicated by this identification information, and for the second DN Information indicating that the TFT used in the user data communication performed in this way has become the TFT indicated by this identification information.
- the 45th identification information may include a plurality of pieces of information indicating TFTs, or may include information indicating whether or not each TFT is a TFT used in user data communication performed for the second DN. Good.
- the 45th identification information may be information indicating that a PDU session connected to the second DN has been established, or indicates that the connection destination of the PDU session has been changed to the second DN. It may be information, or information indicating that the PDU session established or changed by this procedure is a PDU session used in user data communication performed for the second DN.
- the 51st identification information is information indicating a cause value indicating that this procedure is rejected.
- the 51st identification information may be information indicating that a request to establish a PDU session connected to the second DN is rejected.
- the 51st identification information may be information indicating that the request for establishment of the PDU session connected to the second DN is rejected, and the connection destination of the established PDU session is the second It may be information indicating that the request to change to DN has been rejected. Further, it may be information indicating that a request for setting the second DN as the communication destination of user data communication using each identification information received in the request message is rejected.
- the 51st identification information may be information indicating that establishment of a PDU session connected to the second DN is temporarily prohibited, and the connection destination of the established PDU session It may be information indicating that changing to the DN of 2 is temporarily prohibited.
- the 51st identification information may be information indicating that establishment of a PDU session connected to the second DN is prohibited in the cell and / or TA to which UE_A10 is currently connected, The information may indicate that changing the connection destination of the established PDU session to the second DN is prohibited.
- the 51st identification information may include the meaning of one or more of the 52nd to 56th identification information. Furthermore, the 51st identification information, the information indicated by the 51st identification information, and / or each information indicated by the 52nd to 56th identification information may be a single identification information. In other words, the 51st identification information may be a single identification information including the meaning of each identification information with any one of the 52nd to 56th identification information.
- the 51st identification information and the 52nd identification information may be included in the control message as single identification information having both meanings of the two identification information, or the 51st identification information and the 53rd identification information. May be included in the control message as single identification information having both meanings of the two identification information. Further, the 51st identification information and the 53rd identification information may be included in the control message as single identification information having both meanings of the two identification information, or the 51st identification information and the 54th identification information. May be included in the control message as single identification information having both meanings of the two identification information. Further, the 51st identification information and the 56th identification information may be included in the control message as single identification information having both meanings of the two identification information.
- the 52nd identification information is information indicating DNN.
- the 52nd identification information may be information indicating that the connection destination of the PDU session established or changed by this procedure cannot be the DN identified by the DNN indicated by this identification information. It may indicate that the connection destination of the PDU session cannot be the second DN. Further, the 52nd identification information may include information indicating whether each DNN is the second DN or not.
- the 52nd identification information may be information indicating that a PDU session connected to the second DN cannot be established, or the connection destination of the PDU session may be changed to the second DN.
- the 52nd identification information and the 51st identification information may be single identification information including the meaning of each identification information. Therefore, in this embodiment, when it is described that the 52nd identification information and the 51st identification information are transmitted or included in the control message, the two identification information are transmitted as a single identification information having both meanings. Or may be included in the control message.
- the 53rd identification information is information indicating that the requested PDU session ID is inappropriate.
- the 53rd identification information may be information indicating that the PDU session identified by the PDU session ID indicated by the identification information cannot be established or changed, or the PDU session ID indicated by the identification information. It may be indicated that the new connection destination of the PDU session identified by (2) cannot be the second DN.
- the 53rd identification information may be information indicating that a PDU session connected to the second DN cannot be established, or the connection destination of the PDU session may be changed to the second DN.
- the 53rd identification information and the 51st identification information may be single identification information including the meaning of each identification information. Therefore, in this embodiment, when it is described that the 53rd identification information and the 51st identification information are transmitted or included in the control message, the two identification information are transmitted as a single identification information having both meanings. Or may be included in the control message.
- the 54th identification information is information indicating that the requested PDU session type is inappropriate.
- the 54th identification information may be information indicating that the requested address is inappropriate.
- the 54th identification information may be information indicating that the PDU session type of the PDU session established or changed by this procedure cannot be the PDU session type indicated by this identification information.
- Information indicating that the address associated with the PDU session established or changed by the procedure cannot be the address indicated by this identification information and / or the address of the PDU session type indicated in this embodiment Good.
- the 54th identification information is information indicating that the PDU session type of the address used in the user data communication performed for the second DN cannot be the PDU session type indicated by this identification information.
- the address used in the user data communication performed for the second DN may not be the address indicated by this identification information and / or the PDU session type address indicated in this embodiment. It may be information indicating.
- the 54th identification information may be information indicating that a PDU session connected to the second DN cannot be established, or the connection destination of the PDU session may be changed to the second DN.
- the 54th identification information and the 51st identification information may be single identification information including the meaning of each identification information. Therefore, in this embodiment, when it is described that the 54th identification information and the 51st identification information are transmitted or included in the control message, the two identification information are transmitted as single identification information having both meanings. Or may be included in the control message.
- the 55th identification information is information indicating that the requested TFT is inappropriate.
- the 55th identification information may be information indicating that the TFT associated with the PDU session established or changed by this procedure cannot be the TFT indicated by this identification information, or the second DN It may be information indicating that the TFT used in the user data communication performed for cannot be the TFT indicated by this identification information.
- the 55th identification information may be information indicating that a PDU session connected to the second DN cannot be established, or the connection destination of the PDU session may be changed to the second DN.
- the 55th identification information and the 51st identification information may be single identification information including the meaning of each identification information. Therefore, in this embodiment, when it is described that the 55th identification information and the 51st identification information are transmitted or included in the control message, the two identification information are transmitted as single identification information having both meanings. Or may be included in the control message.
- the 56th identification information is information indicating the value of the first timer. Based on reception of the 56th identification information, UE_A10 may set the value indicated by the 56th identification information in the first timer, or may start the execution of the first timer.
- the 61st identification information is information indicating that transmission of LADN (Local Area Data Data Network) information is requested, and / or when the UE enters a specific place where connection to the LADN is possible.
- UE capability information indicating that the PDU session establishment procedure (PDU session establishment procedure) for UE can be executed under the initiative of the UE.
- the 61st identification information may be LADN DNN for identifying LADN, or S-NSSAI (Single Network Slice Selection Assistance information) for identifying the network slice (NS) used for LADN. It may be.
- LADN is a DN to which a UE can connect only at a specific location, and provides connectivity to a specific DNN (ie, LADN DNN).
- the LADN may be a second DN (that is, DN_B105).
- the 61st identification information is preferably transmitted by being included in the registration request (Registration Request) when transmitted in the registration procedure (Registration Request), but any control message other than Registration Request (for example, it may be transmitted by a NAS message or an RRC message.
- the 61st identification information may be transmitted by an arbitrary control message (for example, a NAS message or an RRC message) at an arbitrary timing even after the registration procedure is completed.
- the 62nd identification information is LADN information indicating a specific LADN that can be used by the UE based on the operator policy and the subscriber information (subscription information).
- the LADN information may include LADN DNN and LADN service area information.
- LADN service area information may be provided for a set of tracking areas.
- the 62nd identification information when the 62nd identification information is transmitted by a registration procedure (Registration Procedure), it is preferable that the 62nd identification information is transmitted by a response to the registration request (Registration Request), for example, registration acceptance (Registration Accept). Further, the 62nd identification information may be transmitted by any control message other than RegistrationRegAccept (for example, NAS message or RRC message). Further, the 62nd identification information may be transmitted by an arbitrary control message (for example, NAS message or RRC message) at an arbitrary timing even after the registration procedure is completed.
- Registration Request registration request
- Registration Accept registration acceptance
- the 62nd identification information may be transmitted by any control message other than RegistrationRegAccept (for example, NAS message or RRC message). Further, the 62nd identification information may be transmitted by an arbitrary control message (for example, NAS message or RRC message) at an arbitrary timing even after the registration procedure is completed.
- the 63rd identification information may be information indicating whether or not to transmit information (priority information) indicating a route preference (Preference: Prf) for the DN.
- the 63rd identification information is preferably included in the registration request (Registration Request) when transmitted in the registration procedure (Registration Request), but any control message other than the Registration Request (for example, it may be transmitted by a NAS message or an RRC message. Further, when the 63rd identification information is transmitted in the PDU session establishment procedure (PDU Session Establishment Procedure), it is preferable that the 63rd identification information is included in the PDU session establishment request (PDU Session Establishment Request). It may be transmitted by an arbitrary control message (for example, NAS message or RRC message) other than Session Establishment Request.
- the 63rd identification information may be transmitted by an arbitrary control message (for example, a NAS message or an RRC message) at an arbitrary timing even after the registration procedure and / or the PDU session establishment procedure is completed.
- the specific route preference information may be the 64th identification information described below.
- the 64th identification information may be information indicating the preference of the route.
- the Preference value can be high, medium, low, or reserved.
- the route preference may be information for selecting a default route. More specifically, it may be information for selecting a default router. For example, when a default router and preference information are stored for each PDU session, data may be transmitted by selecting a default router associated with preference information having a high priority level. Thus, a default route, which is good for selecting a default router, may be selected.
- the preference information may be information associated with a default router and / or a default route and / or an IPv6 network prefix. Accordingly, different priorities may be set for each default router and / or for each default route and / or for each IPv6 network prefix.
- the 64th identification information is preferably transmitted as RA (Router Advertisement) information.
- the 64th identification information may be transmitted in response to a registration request (Registration Request) transmitted in the registration procedure (Registration Procedure), for example, registration acceptance (Registration Accept).
- the 64th identification information may be transmitted by an arbitrary control message (for example, NAS message or RRC message) other than RegistrationRegAccept.
- the 63rd identification information may be transmitted by an arbitrary control message (for example, a NAS message or an RRC message) at an arbitrary timing even after the registration procedure is completed.
- the 65th identification information includes information indicating that a transmission request for LADN information is permitted, and / or a PDU session establishment procedure for the LADN when the UE enters a specific place where connection to the LADN is possible. May be network capability information (network capability information) indicating that UE can be executed under the initiative of the UE. In addition, the 65th identification information may be transmitted as a response to the 61st identification information.
- the 65th identification information is transmitted by a registration procedure, it is preferable that the 65th identification information is transmitted by a response to the registration request (Registration Request), for example, a registration acceptance.
- the 65th identification information may be transmitted by an arbitrary control message (for example, NAS message or RRC message) other than RegistrationRegAccept.
- the 65th identification information may be transmitted by an arbitrary control message (for example, a NAS message or an RRC message) at an arbitrary timing even after the registration procedure is completed.
- the 66th identification information includes information indicating that transmission of LADN (Local Area Data Data Network) information is requested, and / or when the UE enters a specific place where connection to the LADN is possible.
- UE capability information (UE ⁇ capability information) indicating that a PDU ⁇ ⁇ ⁇ ⁇ ⁇ session establishment procedure can be executed under network initiative.
- the 66th identification information may be LADN DNN for identifying LADN, or S-NSSAI (Single Network Slice Selection Assistance information) for identifying the network slice (NS) used for LADN. It may be.
- LADN is a DN to which a UE can connect only at a specific location, and provides connectivity to a specific DNN (ie, LADN DNN).
- the LADN may be a second DN (that is, DN_B105).
- the 66th identification information may include 61st identification information.
- the 66th identification information may be configured as information including both the meanings of the 61st identification information and the 66th identification information.
- the 66th identification information is preferably transmitted by being included in the registration request (Registration Request) when transmitted by the registration procedure (Registration Request), but any control message other than the Registration Request (for example, it may be transmitted by a NAS message or an RRC message.
- the 66th identification information may be transmitted by an arbitrary control message (for example, a NAS message or an RRC message) at an arbitrary timing even after the registration procedure is completed.
- the 67th identification information includes information indicating that a transmission request for LADN information is permitted, and / or a PDU session establishment procedure for the LADN when the UE enters a specific location where connection to the LADN is possible. May be network capability information (network capability information) indicating that the network can be executed under the initiative of the network.
- the 67th identification information may be transmitted as a response to the 66th identification information.
- the 67th identification information is transmitted by a registration procedure (Registration Procedure)
- the 67th identification information is transmitted by a response to the registration request (Registration Request), for example, registration acceptance.
- the 65th identification information may be transmitted by an arbitrary control message (for example, NAS message or RRC message) other than RegistrationRegAccept.
- the 67th identification information may be transmitted by an arbitrary control message (for example, NAS message or RRC message) at an arbitrary timing even after the registration procedure is completed.
- the initial procedure in this embodiment will be described with reference to FIG.
- the initial procedure includes a registration procedure (Registration procedure) and a PDU session establishment procedure (PDU session establishment procedure). Details of the registration procedure and the PDU session establishment procedure will be described later.
- UE_A10 transitions to a state registered in the network (RM-REGISTERED state).
- UE_A10 establishes a PDU session with DN_A5 that provides the PDU connection service via the core network_B190, and the first PDU session establishment procedure (S802) Transition to a state (S804). This procedure is completed by the above.
- Each device may exchange various capability information and / or various request information of each device in the registration procedure and / or the PDU session establishment procedure.
- each device when each device exchanges various information and / or negotiates various requests in the registration procedure, it does not need to perform various information exchange and / or various request negotiations in the PDU session establishment procedure.
- the devices when each device does not exchange various information and / or negotiate various requests in the registration procedure, the devices may exchange various information and / or negotiate various requests in the PDU session establishment procedure.
- each device may perform various information exchange and / or various request negotiations by the PDU session establishment procedure even when various information exchange and / or various request negotiations are performed by the registration procedure.
- Each device may execute the PDU session establishment procedure in the registration procedure or after the registration procedure is completed.
- the PDU session establishment procedure When the PDU session establishment procedure is executed in the registration procedure, the PDU session establishment request message may be transmitted / received by being included in the registration request message, and the PDU session establishment acceptance message may be transmitted / received by being included in the registration acceptance message.
- the PDU session establishment completion message may be transmitted and received in the registration completion message, and the PDU session establishment rejection message may be transmitted and received in the registration rejection message.
- each device may establish a PDU session based on the completion of the registration procedure, or may transition to the first state.
- each device involved in this procedure transmits / receives each control message described in this procedure, thereby transmitting / receiving one or more pieces of identification information included in each control message, and storing each transmitted / received identification information as a context. Also good.
- the registration procedure is a procedure for the UE_A10 to register with the network (access network and / or core network_B190, and / or DN (DN_A5 or DN_B105)). If the UE_A 10 is not registered in the network, the UE_A 10 can execute this procedure at any timing such as when the power is turned on. In other words, the UE_A 10 may start this procedure at an arbitrary timing as long as it is in the unregistered state (RM-DEREGISTERED state). Also, each device may transition to a registered state (RM-REGISTERED state) based on completion of the registration procedure.
- this procedure updates the location registration information of UE_A10 in the network and / or periodically notifies UE_A10 of the status of UE_A10 from the UE_A10 and / or updates specific parameters related to UE_A10 in the network. It may be a procedure.
- UE_A10 may start this procedure when performing mobility across TAs. In other words, the UE_A 10 may start this procedure when moving to a TA that is different from the TA indicated in the held TA list. Furthermore, UE_A10 may start this procedure when the running timer expires. Further, UE_A 10 may start this procedure when the context of each device needs to be updated due to disconnection or invalidation of the PDU session. Furthermore, UE_A10 may start this procedure, when the capability information regarding a PDU session establishment of UE_A10 and / or a preference change arise. Furthermore, UE_A10 may start this procedure periodically. The UE_A 10 is not limited to these, and can execute this procedure at an arbitrary timing as long as the PDU session is established.
- Registration procedure example An example of a procedure for executing the registration procedure will be described with reference to FIG. Hereinafter, this procedure refers to the registration procedure. Hereafter, each step of this procedure will be described.
- UE_A 10 starts a registration procedure by transmitting a registration request message to AMF_A 240 via NR node_A 122 (S900) (S902) (S904). Further, UE_A10 transmits an SM message (for example, a PDU session establishment request message) together with the registration request message by transmitting an SM (Session Management) message (for example, a PDU session establishment request message) in the registration request message. By doing so, the SM procedure such as the PDU session establishment procedure may be started during the registration procedure.
- SM Session Management
- UE_A 10 transmits an RRC message including a registration request message to NR node_A 122 (S900).
- the NR node_A 122 selects AMF_A 240 as the NF or shared CP function as the routing destination of the registration request message (S902).
- the NR node_A 122 extracts the registration request message from the received RRC message, and transmits or forwards the registration request message to the selected AMF_A 240 (S904).
- the NR node_A 122 may select AMF_A 240 based on information included in the RRC message.
- the registration request message may be a NAS (Non-Access-Stratum) message transmitted / received on the N1 interface.
- the RRC message may be a control message transmitted / received between UE_A10 and NR node_A122.
- the NAS message is processed in the NAS layer, the RRC message is processed in the RRC layer, and the NAS layer may be a higher layer than the RRC layer.
- UE_A10 may transmit a registration request message for each NSI, or may transmit a plurality of registration request messages included in one or more RRC messages. Good.
- the plurality of registration request messages may be transmitted as one registration request message included in one or more RRC messages.
- the UE_A 10 may include the first identification information and / or the 61st identification information and / or the 63rd identification information and / or the 66th identification information in the registration request message and / or the RRC message. .
- UE_A10 may indicate that UE_A10 supports and / or permits connection to the second DN by transmitting the first identification information, or connects to the second DN. It may indicate that it supports and / or allows establishment of a PDU session.
- UE_A10 may determine whether or not to include the first identification information in the registration request message based on UE_A10 capability information and / or policies such as UE policy and / or UE_A10 preferences. .
- UE_A10 may indicate that transmission of LADN information is requested by transmitting the 61st identification information, and / or UE_A10 enters a specific place where connection to LADN is possible Sometimes, it may indicate that a PDU session establishment procedure for LADN is feasible (capable of performing).
- UE_A10 may indicate whether or not to transmit the preference of the route for DN_A5 by transmitting the 63rd identification information.
- UE_A10 may indicate that transmission of LADN information is requested by transmitting the 66th identification information, and / or UE_A10 has entered a specific place where connection to LADN is possible Sometimes, it may be indicated that UE_A 10 has the capability to handle a PDU session establishment procedure for LADN initiated by the network.
- UE_A 10 may transmit the identification information included in a control message (for example, NAS message or RRC message) different from the registration request message.
- a control message for example, NAS message or RRC message
- the AMF_A240 receives the registration request message and / or a control message different from the registration request message, and executes the first condition determination.
- the first condition determination is for determining whether or not the network accepts the UE_A10 request.
- the AMF_A 240 starts the procedure (A) in the procedure when the first condition determination is true, and starts the procedure (B) in the procedure when the first condition determination is false.
- AMF_A240 executes the fourth condition determination and starts the procedure (A) in this procedure.
- the fourth condition determination is for determining whether or not the AMF_A 240 performs transmission / reception of an SM message with the SMF_A 230.
- AMF_A240 executes selection of SMF_A230 and transmission / reception of SM messages to / from the selected SMF_A230 when the fourth condition determination is true, and omits them when the fourth condition determination is false. (S906).
- AMF_A240 transmits a registration acceptance (Registration Accept) message to UE_A10 via NR node_A122 based on reception of a registration request message from UE_A10 and / or completion of transmission / reception of an SM message with SMF_A230 ( S908).
- Registration Accept Registration Accept
- AMF_A240 When AMF_A240 receives an SM message indicating rejection from SMF_A230, AMF_A240 may stop the procedure (A) in this procedure and start the procedure (B) in this procedure.
- the registration acceptance message may be transmitted and received by being included in an N2 interface control message and an RRC message. Further, the registration acceptance message may be a NAS message transmitted / received on the N1 interface. The registration acceptance message may be a response message to the registration request message.
- the AMF_A240 transmits a registration acceptance message including an SM message such as a PDU session establishment acceptance message (for example, a PDU session establishment acceptance message), or together with the registration acceptance message.
- An SM message such as a PDU session establishment acceptance message (for example, a PDU session establishment acceptance message) may be transmitted.
- This transmission method may be executed when an SM message (for example, a 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 an SM message (for example, a PDU session establishment request message) is included together with the registration request message and the fourth condition determination is true.
- AMF_A240 may indicate that the procedure for SM has been accepted by performing such a transmission method.
- the AMF_A240 may include the 11th to 14th identification information and / or the 62nd identification information and / or the 65th identification information and / or the 67th identification information in the registration acceptance message. Including these pieces of identification information may indicate that the request of UE_A10 has been accepted.
- the AMF_A240 indicates whether the 11th to 14th identification information and / or the 62nd identification information, the 65th identification information, and / or the 67th identification information is included in the registration acceptance message. It may be determined based on information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information.
- the 62nd identification information and / or the 65th identification information may be information transmitted to the UE_A10 when the 61st identification information is received from the UE_A10.
- the 67th identification information may be information transmitted to UE_A10 when the 66th identification information is received from UE_A10.
- UE_A10 receives the registration acceptance message via NR node_A122 (S908).
- the UE_A 10 recognizes the contents of various types of identification information included in the registration acceptance message by receiving the registration acceptance message.
- UE_A10 recognizes the content of LADN information by including the 62nd identification information in the registration acceptance message, and can execute a PDU session establishment procedure to LADN when moving to a specific location You may recognize that. Also, UE_A10 recognizes that the registration acceptance message does not contain the 62nd identification information, so that when it moves to a specific location, it cannot execute the PDU session establishment procedure to LADN. Good.
- UE_A10 has specified that the network side has permitted the transmission request for LADN information by including the 65th identification information in the registration acceptance message, and / or that the UE can connect to LADN.
- the network side has the ability to perform the PDU session establishment procedure for LADN on the initiative of the UE.
- UE_A10 does not include the 65th identification information in the registration acceptance message, so that the network side did not permit the transmission request for LADN information and / or the UE can connect to the LADN.
- the network side does not have the ability to perform the PDU session establishment procedure for LADN under the initiative of the UE.
- UE_A10 has received the 67th identification information in the registration acceptance message, so that the network side has permitted the transmission request of LADN information and / or the UE can be connected to LADN.
- the network side has the ability to execute the PDU session establishment procedure for LADN on a network initiative.
- UE_A10 does not include the 67th identification information in the registration acceptance message, so that the network side does not permit the transmission request for LADN information and / or the UE can be connected to the LADN.
- the network side does not have the ability to perform the PDU session establishment procedure for LADN on a network initiative.
- UE_A10 may further send a Registration Complete message to AMF_A240 (S910).
- the UE_A10 may transmit an SM message such as a PDU session establishment completion message in the registration completion message.
- the registration completion message may be a NAS message transmitted / received on the N1 interface.
- the registration completion message may be a response message to the registration acceptance message.
- the registration completion message may be transmitted and received by being included in the RRC message and the control message of the N2 interface.
- AMF_A240 receives the registration completion message (S910). Also, each device completes the procedure (A) in this procedure based on transmission / reception of a registration acceptance message and / or a registration completion message.
- the AMF_A 240 transmits a registration rejection (Registration ⁇ ⁇ ⁇ Reject) message to the UE_A 10 via the NR node_A122 (S912), thereby starting the procedure (B) in this procedure. Furthermore, UE_A10 recognizes that the request of UE_A10 has been rejected by receiving a registration rejection message or by not receiving a registration acceptance message. Each device completes the procedure (B) in this procedure based on the transmission / reception of the registration rejection message.
- the AMF_A240 may transmit a registration rejection message including an SM message indicating rejection such as a PDU session establishment rejection message, or an SM message indicating rejection. Inclusion may indicate that the procedure for the SM has been rejected. In that case, UE_A 10 may further receive an SM message indicating rejection such as a PDU session establishment rejection message, or may recognize that the procedure for SM has been rejected.
- an SM message indicating rejection such as a PDU session establishment rejection message
- the registration rejection message may be a NAS message transmitted / received on the N1 interface.
- the registration rejection message may be a response message to the registration request message.
- the registration rejection message transmitted by AMF_A240 is not limited to this as long as it is a message rejecting the request of UE_A10. Further, the registration rejection message may be transmitted and received by being included in the N2 interface control message and the RRC message.
- AMF_A240 may include one or more pieces of identification information among the 21st to 22nd identification information in the registration rejection message, and by including these identification information, it indicates that the request of UE_A10 has been rejected. May be.
- the UE_A10 recognizes the contents of various types of identification information included in the registration rejection message by receiving the registration rejection message.
- the UE_A 10 may recognize that the PDU session establishment procedure to the LADN cannot be performed when moving to a specific location by receiving the registration rejection message.
- AMF_A240 is the identification information received from the 21st to 22nd identification information to be included in the registration rejection message, and / or policies such as network capability information and / or operator policy, And / or based on network conditions.
- Each device completes this procedure (registration procedure) based on completion of the procedure (A) or (B) in this procedure.
- Each device may transition to the state (RM_REGISTERED state) where UE_A10 is registered in the network based on the completion of the procedure (A) in this procedure, or the procedure (B) in this procedure.
- UE_A10 may be maintained in a state (RM_DEREGISTERED state) that is not registered in the network.
- the transition of each device to each state may be performed based on the completion of this procedure, or may be performed based on the establishment of a PDU session.
- each device may perform processing based on the identification information transmitted and received in this procedure based on the completion of this procedure. For example, when receiving the eleventh identification information, the UE_A 10 may recognize that the connection to the second DN is permitted and / or supported. Further, when the UE_A 10 receives the eleventh identification information, the UE_A 10 may start a PDU session establishment procedure in order to establish a PDU session connected to the second DN.
- UE_A10 may recognize that some functions are restricted when receiving the 12th identification information and / or the 13th identification information. For example, when receiving the twelfth identification information, UE_A 10 starts the PDU session establishment procedure to be executed to establish the PDU session connected to the second DN in the currently connected cell and / or TA. Transmission of a PDU session establishment request message indicating a request for establishment of a PDU session connected to the second DN may be prohibited in the currently connected cell and / or TA.
- the UE_A 10 when receiving the twelfth identification information and / or the thirteenth identification information, the UE_A 10 temporarily starts the PDU session establishment procedure executed to establish the PDU session connected to the second DN.
- the transmission of a PDU session establishment request message indicating a request for establishment of a PDU session connected to the second DN may be temporarily prohibited.
- the value indicated by the 13th identification information may be set as the value of the first timer,
- the execution of the timer 1 may be started.
- UE_A10 may be prohibited from starting a PDU session establishment procedure executed to establish a PDU session connected to the second DN until the first timer expires, or the first timer Transmission of a PDU session establishment request message indicating a request for establishment of a PDU session connected to the second DN may be prohibited until the time expires.
- the UE_A10 when the UE_A10 receives a registration acceptance message including the twelfth identification information and / or the thirteenth identification information, the UE_A10 performs a PDU session establishment procedure to be executed to establish a PDU session connected to the second DN. It may not be started, or a PDU session establishment request message indicating a request for establishment of a PDU session connected to the second DN may not be transmitted. In other words, when UE_A10 receives a registration acceptance message that does not include the twelfth identification information and / or the thirteenth identification information, it establishes a PDU session that is executed to establish a PDU session connected to the second DN. The procedure may be started, or a PDU session establishment request message indicating a request for establishment of a PDU session connected to the second DN may be transmitted.
- UE_A10 when UE_A10 receives the 14th identification information, PDU executed to establish a PDU session connected to the second DN using the DNN indicated by the 14th identification information after the completion of this procedure
- the session establishment procedure may be started, or after completion of this procedure, a PDU session establishment request message including the DNN indicated by the 14th identification information may be transmitted to SMF_A230 via AMF_A240.
- UE_A10 may recognize that the request of UE_A10 has been rejected, and further recognize the reason for the rejection of the request. May be.
- UE_A10 when receiving the 21st identification information, UE_A10 may recognize that the network does not support connection to the second DN, and connection to the second DN is not permitted by the network. You may recognize that. In other words, when the 21st identification information is received, the UE_A 10 may be prohibited from starting a PDU session establishment procedure to be executed to establish a PDU session connected to the second DN, or the second DN. Transmission of a PDU session establishment request message indicating a request for establishment of a PDU session connected to the server may be prohibited.
- UE_A10 may be prohibited from starting a new registration procedure executed to connect to the second DN in the currently connected cell and / or TA.
- transmission of a registration request message indicating a request to connect to the second DN may be prohibited in the currently connected cell and / or TA.
- UE_A10 when receiving the 21st identification information and / or the 22nd identification information, UE_A10 may set the value indicated by the 22nd identification information as the value of the second timer, The execution of the second timer may be started. In addition, UE_A10 may be prohibited from starting a new registration procedure to connect to the second DN until the second timer expires, or until the second timer expires. Meanwhile, transmission of a registration request message indicating a request to connect to the second DN may be prohibited.
- the UE_A10 when the UE_A10 receives a registration rejection message including the 21st identification information and / or the 22nd identification information, the UE_A10 does not need to start a new registration procedure to be executed to connect to the second DN. Alternatively, a new registration request message indicating a request to connect to the second DN may not be transmitted. In other words, when UE_A10 receives a registration acceptance message that does not include the 21st identification information and / or the 22nd identification information, it starts a new registration procedure to be executed to connect to the second DN. Alternatively, a new registration request message indicating a request to connect to the second DN may be transmitted.
- UE_A10 when UE_A10 receives one or more pieces of identification information among the eleventh to fourteenth pieces of identification information, UE_A10 stores information indicated by each piece of identification information received together with the registration acceptance message in the context held by UE_A10. Also good. Furthermore, when UE_A10 receives one or more pieces of identification information among the 21st to 22nd pieces of identification information, UE_A10 may update or delete the information in the context held by UE_A10, or received it together with the registration rejection message. Information indicated by each piece of identification information may be further stored in the context held by UE_A10.
- the UE_A10 may recognize the reason why the request of the UE_A10 is rejected. Furthermore, UE_A10 may perform this procedure again based on the reason that the request of UE_A10 has been rejected, or may perform registration procedures for core network_A90 or another cell.
- the first condition determination may be performed based on identification information and / or subscriber information and / or operator policy included in the registration request message. For example, the first condition determination may be true when the network permits the UE_A10 request. Further, the first condition determination may be false when the network does not permit the request of UE_A10. Furthermore, the first condition determination is true if the UE_A10 registration destination network and / or a device in the network supports the function requested by the UE_A10, and false otherwise. Good. Note that the condition for determining the authenticity of the first condition determination is not limited to the above-described condition.
- the fourth condition determination may be performed based on whether the AMF_A 240 has received the SM, or may be performed based on whether the SM message is included in the registration request message. For example, the fourth condition determination may be true if the AMF_A240 receives the SM and / or if the registration request message includes an SM message, the AMF_A240 does not receive the SM, and If the SM message is not included in the registration request message, it may be false. Note that the condition for determining the authenticity of the fourth condition determination is not limited to the above-described condition.
- PDU session establishment procedure (also referred to as a first PDU session establishment procedure) performed for establishing a PDU session for DN_A5 will be described.
- the PDU session establishment procedure is also referred to as this procedure.
- This procedure is a procedure for each device to establish a PDU session.
- Each device may execute this procedure in a state where the registration procedure is completed, or may execute it in the registration procedure.
- Each device may start the procedure in the registration state, or may start the procedure at an arbitrary timing after the registration procedure.
- each device may establish a PDU session based on completion of the PDU session establishment procedure.
- each device may establish a plurality of PDU sessions by executing this procedure a plurality of times.
- UE_A10 starts a PDU session establishment procedure by transmitting a PDU Session Establishment Request message to SMF_A230 via NR node_A122 and AMF_A240 (S1000) (S1002) (S1004).
- UE_A10 transmits a PDU session establishment request message to AMF_A240 via NR node_A122 using the N1 interface (S1000).
- AMF_A240 selects SMF_A230 as the NF to which the PDU session establishment request message is routed (S1002), and transmits the PDU session establishment request message to the selected SMF_A230 using the N11 interface. Transfer (S1004).
- the AMF_A 240 may select the routing destination SMF_A 230 based on the information included in the PDU session establishment request message.
- the AMF_A240 may identify each identification information obtained based on reception of a PDU session establishment request message, and / or subscriber information, and / or network capability information, and / or an operator policy, and / or a network
- the routing destination SMF_A 230 may be selected based on the state and / or the context already held by the AMF_A 240.
- the PDU session establishment request message may be a NAS message.
- the PDU session establishment request message may be a message requesting establishment of a PDU session, and is not limited thereto.
- UE_A10 may include at least one of the 31st to 35th identification information and / or the 63rd identification information in the PDU session establishment request message, or include these identification information. Then, the request for UE_A10 may be indicated.
- UE_A 10 may request establishment of a PDU session connected to the second DN by transmitting one or more pieces of identification information among the 31st to 35th identification information. More specifically, the UE_A 10 transmits a PDU session connected to the second DN by transmitting the 32nd identification information and / or by transmitting the 31st identification information and the 32nd identification information in association with each other. It may be requested to establish, or it may further be requested that the connection destination of the established PDU session is the DN indicated by the 32nd identification information.
- UE_A10 transmits the 33rd identification information and / or associates and transmits the 31st identification information and the 33rd identification information, thereby identifying the PDU session ID indicated by the 33rd identification information.
- the PDU session to be established may be requested, or the connection destination of the established PDU session may be requested to be the second DN.
- UE_A10 establishes a PDU session connected to the second DN by transmitting the thirty-fourth identification information and / or by transmitting the thirty-first identification information and the thirty-fourth identification information in association with each other. May be requested, or the PDU session type of the established PDU session may be further requested to be the PDU session type indicated by the thirty-fourth identification information.
- UE_A10 transmits the 34th identification information and / or associates and transmits the 31st identification information and the 34th identification information to the second DN using the established PDU session. It may be further requested that the address used in the user data communication to be performed is an address of the type indicated by the thirty-fourth identification information, or the address indicated by the thirty-fourth identification information is further You may request.
- UE_A10 establishes a PDU session connected to the second DN by transmitting the 35th identification information and / or transmitting the 31st identification information and the 35th identification information in association with each other. Or may further request that the TFT used in user data communication performed for the second DN using the established PDU session be the TFT indicated by the 35th identification information. May be.
- UE_A10 determines which identification information from among the 31st to 35th identification information is included in the PDU session establishment request message, UE_A10 capability information, and / or UE policy policy, and / or UE_A10 preference. You may decide based on.
- the determination by UE_A10 which identification information is included in the PDU session establishment request message is not limited to this.
- UE_A10 may indicate whether or not to transmit the preference of the route for DN_A5 by transmitting the 63rd identification information.
- the SMF_A230 receives the PDU session establishment request message and executes the first condition determination.
- the first condition determination is for the SMF_A 230 to determine whether or not to accept the UE_A10 request. In the first condition determination, the SMF_A 230 determines whether the first condition determination is true or false.
- the SMF_A 230 starts the procedure (A) in the procedure when the first condition determination is true, and starts the procedure (B) in the procedure when the first condition determination is false. The steps when the first condition determination is false will be described later.
- the SMF_A 230 selects the UPF_A235 that is the establishment destination of the PDU session, transmits a session establishment request (Session Establishment request) message to the selected UPF_A235 (S1006), and starts the procedure (A) in this procedure.
- Session Establishment request Session Establishment request
- SMF_A230 is each identification information obtained based on reception of the PDU session establishment request message, and / or network capability information, and / or subscriber information, and / or operator policy, and / or network status, And / or one or more UPF_A 235 may be selected based on the context already held by SMF_A 230. When a plurality of UPF_A235 are selected, the SMF_A230 may transmit a session establishment request message to each UPF_A235.
- UPF_A235 receives the session establishment request message and creates a context for the PDU session. Further, the UPF_A 235 receives the session establishment request message and / or transmits a session establishment response (Session Establishment response) message to the SMF_A 230 based on the creation of the context for the PDU session (S1008). Furthermore, SMF_A230 receives the session establishment response message.
- the session establishment request message and the session establishment response message may be control messages transmitted / received on the N4 interface. Further, the session establishment response message may be a response message to the session establishment request message.
- the SMF_A 230 may perform address assignment of an address to be assigned to the UE_A 10 based on reception of the PDU session establishment request message and / or selection of the UPF_A 235 and / or reception of the session establishment response message. Furthermore, SMF_A230 may associate the address assigned to UE_A10 with information indicating that it is an address used for communication to the second DN. Note that the SMF_A 230 may perform address assignment of an address to be assigned to the UE_A 10 during the PDU session establishment procedure or after completion of the PDU session establishment procedure.
- SMF_A230 may perform address allocation during the PDU session establishment procedure, or may transmit the allocated address to UE_A10. Furthermore, when SMF_A230 assigns an IPv4 address and / or an IPv6 address and / or an IPv6 prefix using DHCPv4 or DHCPv6 or SLAAC (Stateless Address Autoconfiguration), the address may be assigned after the PDU session establishment procedure, The allocated address may be transmitted to UE_A10. Note that the address assignment performed by the SMF_A 230 is not limited to these.
- the SMF_A230 may transmit the allocated address to the UE_A10 including the allocated address in the 44th identification information based on the completion of the address allocation of the address allocated to the UE_A10. May be transmitted to UE_A10 in association with information indicating whether the allocated address is an address that can be used for user data communication performed with the second DN. .
- UE_A10 is used for 44th identification information transmitted by SMF_A230 and / or information indicating the assigned address and / or user data communication in which the assigned address is performed with the second DN. Information indicating whether or not the address can be received may be received.
- SMF_A230 receives UE_A10 via AMF_A240 based on reception of PDU session establishment request message and / or selection of UPF_A235 and / or reception of session establishment response message and / or completion of address assignment of address assigned to UE_A10.
- a PDU session establishment acceptance (PDU session acceptment accept) message is transmitted (S1010) (S1012).
- the SMF_A230 transmits a PDU session establishment acceptance message to the AMF_A240 using the N11 interface (S1010), and the AMF_A240 that receives the PDU session establishment request message transmits the PDU session establishment acceptance message to the UE_A10 using the N1 interface. Is transmitted (S1012).
- the PDU session establishment acceptance message may be a PDN connection acceptance (PDN connectivity connectivity) message. Further, the PDU session establishment acceptance message may be a NAS message transmitted / received on the N11 interface and the N1 interface.
- the PDU session establishment acceptance message is not limited to this, and may be a message indicating that the establishment of the PDU session is accepted.
- the SMF_A230 may include one or more pieces of identification information from among the 41st to 45th pieces of identification information in the PDU session establishment acceptance message. By including these pieces of identification information, the UE_A10 request has been accepted. You may show that.
- the SMF_A230 may indicate that the network has accepted the request for establishment of the PDU session connected to the second DN by transmitting one or more pieces of identification information among the 41st to 45th identification information. It may also indicate that the establishment of a PDU session connected to the second DN is permitted. More specifically, the SMF_A230 transmits the 42nd identification information and / or associates and transmits the 41st identification information and the 42nd identification information, so that the PDU session connected to the second DN is transmitted. It may indicate that it is established, or may indicate that the connection destination of the established PDU session is the DN indicated by the forty-second identification information.
- the SMF_A230 is identified by the PDU session ID indicated by the 43rd identification information by transmitting the 43rd identification information and / or by transmitting the 41st identification information and the 43rd identification information in association with each other.
- the PDU session to be established may be established, or the connection destination of the established PDU session may be the second DN.
- the SMF_A230 transmits the 44th identification information and / or associates and transmits the 41st identification information and the 44th identification information, thereby establishing a PDU session connected to the second DN.
- the address used in the user data communication performed for the second DN using the established PDU session is the address of the PDU session type indicated by the 44th identification information, and / or Alternatively, the address may be indicated by the 44th identification information.
- the SMF_A230 transmits the 45th identification information and / or associates and transmits the 41st identification information and the 45th identification information, thereby establishing a PDU session connected to the second DN.
- the TFT used in the user data communication performed for the second DN using the established PDU session may be the TFT indicated by the 45th identification information. Good.
- SMF_A230 indicates which identification information among the 41st to 45th identification information is included in the PDU session establishment acceptance message, such as the received identification information and / or network capability information, and / or operator policy. It may be determined based on policies and / or network conditions. The determination by SMF_A230 which identification information is included in the PDU session establishment acceptance message is not limited to this.
- UE_A10 receives the PDU session establishment acceptance message, and further transmits a PDU session establishment completion (PDU session establishment complete) message to SMF_A230 via AMF_A240 (S1014) (S1016). Further, the SMF_A 230 receives the PDU session establishment completion message, and executes the second condition determination.
- PDU session establishment complete PDU session establishment complete
- UE_A10 transmits a PDU session establishment completion message to AMF_A240 using the N1 interface (S1014), and AMF_A240 that has received the PDU session establishment completion message transmits a PDU session establishment completion message to SMF_A230 using the N11 interface. Is transmitted (S1016).
- the PDU session establishment completion message may be a PDN connection complete (PDN Connectivity complete) message or a default EPS bearer context activation acceptance (Activate default EPS EPS bearer context accept) message. Further, the PDU session establishment completion message may be a NAS message transmitted / received on the N1 interface and the N11 interface. The PDU session establishment completion message may be a response message to the PDU session establishment acceptance message, and is not limited to this, and may be a message indicating that the PDU session establishment procedure is completed.
- PDN connection complete PDN Connectivity complete
- Activate default EPS EPS bearer context accept Activate default EPS EPS bearer context accept
- the second condition determination is to determine the type of message on the N4 interface to be transmitted / received. If the second condition determination is true, the SMF_A230 sends a session change request message (Session Modification request) to the UPF_A235 (S1018), and further, the session change acceptance sent by the UPF_A235 that has received the session change request message (Session Modification response) ) A message is received (S1020). If the second condition determination is false, SMF_A230 transmits a session establishment request message to UPF_A235 (S1018), and further receives a session change acceptance message transmitted by UPF_A235 that has received the session establishment request message (S1020). .
- UE_A10 receives the PDU session establishment acceptance message from AMF_A240, and then sets an IPv6 address and / or obtains an IPv6 prefix for the core network and / or RA (Router Advertisement) RS (Router Solicitation) (hereinafter also referred to as the first RS) may be transmitted in order to obtain the first RA).
- RA Route Advertisement
- RS Radio Solicitation
- the first RS transmitted from UE_A10 may be transmitted to SMF_A230 via UPF_A235.
- the UPF_A235 when the UPF_A235 receives the first RS transmitted from the UE_A10, the UPF_A235 selects the SMF_A230 related to the PDU session from among the plurality of SMFs connected to the UPF, and the selected SMF_A230 The first RS may be transmitted.
- This SMF selection in the UPF may be performed using a PDU session ID transmitted from the UE or any NF (including SMF_A230).
- the SMF_A230 that has received the first RS generates a first RA when the PDU type of the UE_A10 is IPv6, and transmits the first RA to the UE_A10 via the N4 interface and UPF_A235.
- the SMF_A 230 may transmit the first RA including the IPv6 prefix and / or the 64th identification information.
- the 64th identification information may be information that is transmitted only when the 63rd identification information is received.
- the first RA may be generated not by SMF_A230 but by UPF_A235.
- SMF selection in the UPF is not performed.
- the UPF_A235 that has received the first RS from the UE_A10 generates a first RA when the PDU type of the UE_A10 is IPv6, and sends the first RA to the UE_A10 via the N3 interface. Send.
- the first RS and the first RA may exchange periodically while the PDU session is established.
- UE_A10 can select UPF_A235 as the default router for DN_A5 by setting the IPv6 address by receiving the first RA by any of the above methods, and further, the preference of the route for DN_A5 Can be recognized.
- each device Based on the transmission / reception of the PDU session establishment completion message and / or the session change response message, and / or the transmission / reception of the session establishment response message, and / or the transmission / reception of RA, each device Complete the procedure.
- UE_A10 When the procedure (A) in this procedure is completed, UE_A10 is in a state where a PDU session for DN_A5 is established, that is, in the first state.
- This PDU session is assumed to be established via the access network, UPF_A235, but is not limited thereto. That is, a UPF (UPF_C239) different from UPF_A235 may exist between UPF_A235 and the access network.
- this PDU session is established via the access network, UPF_C239, UPF_A235.
- SMF_A230 transmits a PDU session establishment rejection (PDU session establishment reject) message to UE_A10 via AMF_A240 (S1022) (S1024), and starts the procedure (B) in this procedure.
- PDU session establishment reject PDU session establishment reject
- the SMF_A230 transmits a PDU session establishment rejection message to the AMF_A240 using the N11 interface (S1022), and the AMF_A240 that received the PDU session establishment request message transmits the PDU session establishment rejection message to the UE_A10 using the N1 interface. Is transmitted (S1024).
- the PDU session establishment rejection message may be a PDN connection rejection (PDN connectivity connectivity) message. Further, the PDU session establishment rejection message may be a NAS message transmitted / received on the N11 interface and the N1 interface.
- the PDU session establishment rejection message is not limited to this, and may be a message indicating that the establishment of the PDU session is rejected.
- the SMF_A230 may include one or more pieces of identification information from among the 51st to 56th identification information in the PDU session establishment rejection message, and the UE_A10 request is rejected by including these identification information. You may show that.
- the SMF_A230 may indicate that the network rejects the request for establishment of the PDU session connected to the second DN by transmitting one or more pieces of identification information among the 51st to 56th identification information. It may indicate that the establishment of the PDU session connected to the second DN is not permitted. Further, the SMF_A 230 may indicate that the PDU session connected to the second DN has not been established by transmitting one or more pieces of identification information among the 51st to 56th identification information.
- SMF_A230 may indicate that connection to the second DN is temporarily prohibited by transmitting the 51st identification information, and / or the cell to which UE_A10 is currently connected and / or TA may indicate that connection to the second DN is prohibited.
- SMF_A230 may indicate that the DNN indicated by the 32nd identification information is inappropriate in establishing the PDU session connected to the second DN by transmitting the 52nd identification information.
- the DNN indicated by the 32nd identification information may not be the DNN indicating the second DN.
- SMF_A230 indicates that the PDU session ID indicated by the 33rd identification information is inappropriate in establishing the PDU session connected to the second DN by transmitting the 53rd identification information.
- the PDU session identified by the PDU session ID indicated by the 33rd identification information may not be established for the second DN, or the PDU indicated by the 33rd identification information may be indicated. It may be indicated that the session ID cannot be used for the PDU session connected to the second DN.
- the SMF_A230 transmits the 54th identification information, so that the PDU session type and / or address indicated by the 34th identification information is inappropriate in the establishment of the PDU session connected to the second DN.
- the PDU session type address indicated by the thirty-fourth identification information and / or the address indicated by the thirty-fourth identification information may be used for user data communication performed for the second DN. You may indicate that you cannot.
- the SMF_A230 may indicate that the TFT indicated by the 35th identification information is inappropriate in establishing the PDU session connected to the second DN by transmitting the 55th identification information.
- the TFT indicated by the 35th identification information may indicate that it cannot be used for user data communication performed for the second DN.
- SMF_A230 may indicate that retransmission of the UE_A10 PDU session establishment request message is prohibited for a certain period by transmitting the 51st identification information and / or the 56th identification information, It may indicate a period during which retransmission of the PDU session establishment request message is prohibited. Further, the SMF_A230 may indicate that the first timer is started by transmitting the 56th identification information, or the value indicated by the 56th identification information is set as the value of the first timer. May be indicated.
- the SMF_A230 indicates which of the 51st to 56th identification information is included in the PDU session establishment rejection message, such as the received identification information and / or network capability information, and / or operator policy. It may be determined based on policies and / or network conditions. The determination by SMF_A230 which identification information is included in the PDU session establishment rejection message is not limited to this.
- Each device completes this procedure based on the completion of the procedure (A) or (B) in this procedure.
- Each device may transition to the state where the PDU session is established based on the completion of the procedure (A) in this procedure, or based on the completion of the procedure (B) in this procedure. , It may be recognized that this procedure is rejected, or a transition to a state in which a PDU session is not established may be made.
- each device may perform processing based on the identification information transmitted and received in this procedure based on the completion of this procedure. For example, when UE_A10 receives one or more pieces of identification information among the 41st to 45th pieces of identification information, UE_A10 may recognize that a PDU session connected to the second DN has been established, or the established PDU It may be recognized that user data communication for the second DN using the session can be executed.
- UE_A 10 may recognize that the DN identified by the forty-second identification information is the second DN based on the reception of the forty-first identification information and / or the forty-second identification information. Furthermore, UE_A10 is used when the PDU session identified by the forty-third identification information performs user data communication for the second DN based on reception of the forty-first identification information and / or forty-third identification information. You may recognize that this is a possible PDU session.
- UE_A10 is identified by the address of the PDU session type identified by the 44th identification information and / or the 44th identification information based on the reception of the 41st identification information and / or the 44th identification information. It may be recognized that the address to be used is an address that can be used when performing user data communication for the second DN. Furthermore, UE_A10 can be used when the TFT identified by the 45th identification information performs user data communication for the second DN based on the reception of the 41st identification information and / or the 45th identification information. You may recognize that this is a TFT.
- UE_A10 may use the PDU session identified by the 43rd identification information when performing user data communication for the second DN, or the address of the PDU session type identified by the 44th identification information May be used, an address identified by the 44th identification information may be used, or a TFT identified by the 45th identification information may be used.
- UE_A10 may perform user data communication for the DN identified by the forty-second identification information after the completion of this procedure
- the user data communication may be performed for the second DN using the PDU session identified by the 43rd identification information, the address of the PDU session type identified by the 44th identification information, and User data communication may be performed for the second DN using the address identified by the 44th identification information, or the second DN using the TFT identified by the 45th identification information.
- User data communication may be performed.
- UE_A10 may recognize that the request of UE_A10 is rejected, or further recognize the reason why the request is rejected. May be. Further, the UE_A 10 may perform this procedure again based on the reason why the request is rejected, or may perform a registration procedure for another cell or TA.
- UE_A10 may recognize that a PDU session connected to the second DN is not established, or establishment of a PDU session connected to the second DN is permitted. You may recognize that it is not.
- UE_A10 may recognize that establishment of a PDU session connected to the second DN is prohibited in the currently connected cell and / or TA. . Furthermore, when the 51st identification information is received, UE_A 10 performs a new PDU session establishment procedure to be executed to establish a PDU session connected to the second DN in the currently connected cell and / or TA. Initiation may be prohibited, or transmission of a PDU session establishment request message indicating a request for establishment of a PDU session connected to the second DN may be prohibited in the currently connected cell and / or TA. .
- UE_A10 executes in order to establish a PDU session connected to the second DN in the currently connected cell and / or TA. It is not necessary to start a new PDU session establishment procedure, and in the currently connected cell and / or TA, a new PDU session establishment request message indicating a request to establish a PDU session connected to the second DN is sent. You do not have to send it.
- UE_A 10 when receiving a PDU session establishment rejection message that does not include the 51st identification information, UE_A 10 establishes a PDU session that connects to the second DN in the currently connected cell and / or TA.
- a new PDU session establishment request message indicating a request for establishment of a PDU session connected to the second DN in the currently connected cell and / or TA may be started. May be sent.
- UE_A10 may recognize that establishment of a PDU session using the DNN indicated by the 32nd identification information is prohibited. Further, when receiving the 52nd identification information, UE_A10 may be prohibited from starting a new PDU session establishment procedure using the identification information indicating the same DNN as the 32nd identification information, or the 32nd identification Transmission of a new PDU session establishment request message including identification information indicating the same DNN as the information may be prohibited.
- UE_A10 when receiving the PDU session establishment rejection message including the 52nd identification information, UE_A10 does not need to start a new PDU session establishment procedure using the identification information indicating the same DNN as the 32nd identification information, it is not necessary to transmit a new PDU session establishment request message including identification information indicating the same DNN as the thirty-second identification information. In other words, when a PDU session establishment rejection message not including the 52nd identification information is received, UE_A10 may start a new PDU session establishment procedure using identification information indicating the same DNN as the 32nd identification information. Alternatively, a new PDU session establishment request message including identification information indicating the same DNN as the thirty-second identification information may be transmitted.
- UE_A10 may recognize that establishment of a PDU session using the PDU session ID indicated by the 33rd identification information is prohibited. Further, when receiving the 53rd identification information, UE_A10 may be prohibited from starting a new PDU session establishment procedure using the identification information indicating the same PDU session ID as the 33rd identification information. The transmission of a new PDU session establishment request message including identification information indicating the same PDU session ID as that of the identification information may be prohibited.
- UE_A10 when receiving the PDU session establishment rejection message including the 53rd identification information, UE_A10 does not start a new PDU session establishment procedure using the identification information indicating the same PDU session ID as the 33rd identification information. Alternatively, a new PDU session establishment request message including identification information indicating the same PDU session ID as the thirty-third identification information may not be transmitted. In other words, when receiving a PDU session establishment rejection message that does not include the 53rd identification information, UE_A10 starts a new PDU session establishment procedure using the identification information indicating the same PDU session ID as the 33rd identification information. Alternatively, a new PDU session establishment request message including identification information indicating the same PDU session ID as the thirty-third identification information may be transmitted.
- UE_A10 may recognize that establishment of a PDU session using the PDU session type and / or address indicated by the 34th identification information is prohibited. . Further, when the 54th identification information is received, UE_A10 may be prohibited from starting a new PDU session establishment procedure using identification information indicating the same PDU session type and / or address as the 34th identification information. Alternatively, transmission of a new PDU session establishment request message including identification information indicating the same PDU session type and / or address as the thirty-fourth identification information may be prohibited.
- UE_A 10 when a PDU session establishment rejection message including the 54th identification information is received, UE_A 10 performs a new PDU session establishment procedure using the same PDU session type and / or identification information indicating the address as the 34th identification information May not be started, and a new PDU session establishment request message including identification information indicating the same PDU session type and / or address as the thirty-fourth identification information may not be transmitted.
- UE_A 10 uses the same PDU session type as the 34th identification information and / or a new PDU session using the identification information indicating the address.
- the establishment procedure may be started, or a new PDU session establishment request message including identification information indicating the same PDU session type and / or address as the thirty-fourth identification information may be transmitted.
- UE_A 10 may recognize that establishment of a PDU session using the TFT indicated by the 35th identification information is prohibited. Further, when receiving the 55th identification information, UE_A10 may be prohibited from starting a new PDU session establishment procedure using identification information indicating the same TFT as the 35th identification information, or the 35th identification Transmission of a new PDU session establishment request message including identification information indicating the same TFT as the information may be prohibited.
- UE_A10 when receiving the PDU session establishment rejection message including the 55th identification information, UE_A10 does not need to start a new PDU session establishment procedure using the identification information indicating the same TFT as the 35th identification information, a new PDU session establishment request message including identification information indicating the same TFT as the 35th identification information may not be transmitted. In other words, when a PDU session establishment rejection message not including the 55th identification information is received, UE_A10 may start a new PDU session establishment procedure using identification information indicating the same TFT as the 35th identification information. Alternatively, a new PDU session establishment request message including identification information indicating the same TFT as the 35th identification information may be transmitted.
- UE_A10 may recognize that establishment of a PDU session connected to the second DN is temporarily prohibited. . Further, when receiving the 51st identification information and / or the 56th identification information, UE_A 10 temporarily starts a new PDU session establishment procedure to be executed to establish a PDU session connected to the second DN. The transmission of the PDU session establishment request message indicating the request for establishment of the PDU session connected to the second DN may be temporarily prohibited.
- the UE_A10 may set the value indicated by the 56th identification information as the value of the first timer, or start the execution of the first timer. Also good. Further, UE_A10 may be prohibited from starting a new PDU session establishment procedure to be executed to establish a PDU session connected to the second DN until the first timer expires. Until the timer expires, transmission of a PDU session establishment request message indicating a request for establishment of a PDU session connected to the second DN may be prohibited.
- UE_A10 when UE_A10 receives a PDU session establishment rejection message including one or more pieces of identification information among the 51st to 56th pieces of identification information, a new PDU to be executed to establish a PDU session connected to the second DN
- the session establishment procedure may not be started, and a new PDU session establishment request message indicating a request for establishment of a PDU session connected to the second DN may not be transmitted.
- UE_A10 executes a new PDU session to be connected to the second DN.
- a new PDU session establishment request may be started, or a new PDU session establishment request message indicating a request for establishment of a PDU session connected to the second DN may be transmitted.
- UE_A10 when UE_A10 receives one or more pieces of identification information among the 41st to 45th pieces of identification information, UE_A10 stores information indicated by each piece of identification information received together with the PDU session establishment acceptance message in the context held by UE_A10. May be. Furthermore, when UE_A10 receives one or more pieces of identification information among the 51st to 56th pieces of identification information, UE_A10 may update or delete information in the context held by UE_A10, and together with a PDU session establishment rejection message Information indicated by each received identification information may be further stored in the context held by UE_A10.
- UE_A10 may transition to the first state based on the reception of the PDU session establishment acceptance message and / or the reception of each identification information included in the PDU session establishment acceptance message, or the PDU session is established. Transition to a normal state or transition to a normal state.
- the normal state may be a state that transitions when this procedure is completed normally. Further, the normal state may be a state in which the PDU session requested by UE_A 10 is established. Note that the transition state based on the completion of this procedure is not limited to these.
- UE_A10 may transition to a state where a PDU session is not established based on reception of the PDU session establishment rejection message and / or reception of each identification information included in the PDU session establishment rejection message, You may transition to a state.
- the abnormal state may be a state that transitions when this procedure is not normally completed.
- the abnormal state may be a state in which the PDU session requested by UE_A 10 is not established. Note that the transition state based on the completion of this procedure is not limited to these.
- AMF_A240 and / or SMF_A230 the state of being associated with the UE_A10 based on the transmission of the PDU session establishment acceptance message and / or the transmission of each identification information included in the PDU session establishment acceptance message, the first state Or a transition to a state in which a PDU session is established, or a transition to a normal state.
- the state in which the state matched with UE_A10 changes is not restricted to these.
- AMF_A240 and / or SMF_A230 establishes a state in which the PDU session is associated with UE_A10 based on transmission of the PDU session establishment rejection message and / or transmission of each identification information included in the PDU session establishment rejection message. You may make it change to the state which is not done, and may make it change to an abnormal state. In addition, based on completion of this procedure, the state in which the state matched with UE_A10 changes is not restricted to these.
- the first condition determination may be performed based on identification information and / or subscriber information and / or operator policy included in the PDU session establishment request message. For example, the first condition determination may be true when the network permits the UE_A10 request. Further, the first condition determination may be false when the network does not permit the request of UE_A10. Furthermore, the first condition determination may be true if the network to which UE_A10 is connected and / or a device in the network supports the function requested by UE_A10, and false otherwise. Good. Note that the condition for determining the authenticity of the first condition determination is not limited to the above-described condition.
- the second condition determination may be performed based on whether or not a session on the N4 interface for the PDU session is established. For example, the second condition determination may be true if the session on the N4 interface for the PDU session is established, and false if not established. Note that the condition for determining the authenticity of the second condition determination is not limited to the above-described condition.
- UE_A10 that has received the 62nd identification information in the registration procedure described above, and for which connectivity to a certain LADN is permitted by the 62nd identification information, is permitted to connect to that LADN.
- Another one is that the network (e.g.
- AMF_A240 detects that UE_A10 is at that particular location and causes UE_A10 to perform a PDU session establishment procedure to establish a PDU session for DN_B105 (below Also referred to as a third PDU session establishment procedure). Yet another one is that the network (e.g. AMF_A240) detects that UE_A10 is in that particular location and causes UE_A10 to perform registration and PDU session establishment procedures in order to establish a PDU session for DN_B105 (Hereinafter also referred to as a fourth PDU session establishment procedure). And the last one is that the network (e.g.
- AMF_A240 detects that UE_A10 is in that particular location and performs a PDU session establishment procedure at the initiative of the network to establish a PDU session for DN_B105. (Hereinafter also referred to as the fifth PDU session establishment procedure).
- the second PDU session establishment procedure is basically the same as the first PDU session establishment procedure, except that the DN that establishes the PDU session is different from the object that exchanges signals (ie, SMF and UPF).
- the same processing flow may be used. That is, the second PDU session establishment procedure is the same as the first PDU session establishment procedure, in which DN_A5 is set to DN_B105, SMF_A230 is set to SMF_B232, and UPF_A235 is set to UPF_B237.
- each message and its contents exchanged between each device and / or NF in the second PDU session establishment procedure, and each message exchanged between each device and / or NF in the first PDU session establishment procedure It may be the same as its contents.
- the second PDU session establishment procedure is completed. Then, based on the completion of the second PDU session establishment procedure, that is, when the procedure of (A) in FIG. 10 is executed, the UE_A 10 can transition to the second state.
- the network e.g., AMF_A240
- the network e.g., AMF_A240
- the network performs the above registration procedure at the specific location, and the UE_A10 location (UE_A10 is the specific location). It may be started by detecting that it has moved to the place.
- AMF_A240 exchanges control messages with UDM, NEF, AF, etc. (S1100).
- the AF may be present in DN_B105. More specifically, AMF_A 240 may notify AF that UE_A 10 is in that particular location. Then, the AF may transmit a device trigger request (Device Trigger Request) message to the AMF_A 240 via the NEF. Note that the exchange of control messages with UDM, NEF, AF, etc. by AMF_A240 may be performed after detecting the position of UE_A10.
- the AMF_A240 transmits a device trigger request message as a NAS message to the UE_A10 (S1102). At this time, if UE_A10 is not connected, AMF_A240 may perform paging on UE_A10.
- UE_A10 when UE_A10 receives a device trigger request message from AMF_A240, UE_A10 notifies its application that it is requested to establish a PDU session.
- UE_A10 may transmit a device trigger response message to AMF_A240. Moreover, UE_A10 may notify that the device trigger request message has been received by this transmission (S1104).
- AMF_A240 may recognize that UE_A10 has accepted and / or that UE_A10 has set the content of the device trigger request message requested by itself. Then, AMF_A 240 exchanges control messages with UDM, NEF, AF, etc. (S1106). More specifically, AMF_A 240 may notify UE_A 10 that the establishment of a PDU session is requested by transmitting a device trigger response message to AF via NEF. The AF may recognize it by receiving a device trigger response message from AMF_A240.
- UE_A10 executes the same processing flow as the second PDU session establishment procedure described above based on reception of a device trigger request message from AMF_A240 and / or transmission of a device trigger response message to AMF_A240. be able to. In that case, that is, when the procedure of FIG. 10A is executed, UE_A 10 can establish a PDU session with DN_B 105.
- the third PDU session establishment procedure is completed. Then, based on the completion of the third PDU session establishment procedure, UE_A10 can transition to the second state.
- the fourth PDU session establishment procedure may be started when the network (for example, AMF_A240) side detects the location of UE_A10 (UE_A10 has moved to that particular location).
- the network for example, AMF_A240
- the fourth PDU session establishment procedure is started when the AMF_A 240 transmits a control message indicating that the UE_A 10 requests execution of the registration procedure described above.
- UE_A10 may transmit an ACK (Acknowledgement) to AMF_A240 to acknowledge the execution of the registration procedure requested by this control message. And UE_A10 can perform a registration procedure.
- the registration procedure executed here is basically the same flow as the above-described registration procedure if SMF_A230 is replaced with SMF_B232, and thus detailed description thereof is omitted.
- AMF_A 240 may be transmitted by including information indicating that the second PDU session establishment procedure is permitted to be executed in the registration acceptance (Registration Accept) message.
- UE_A10 which received the registration acceptance message containing this information can perform the above-mentioned 2nd PDU session establishment procedure.
- UE_A 10 can establish a PDU session with DN_B 105.
- NACK Negative Acknowledgment
- the fourth PDU session establishment procedure is completed. Based on the completion of the fourth PDU session establishment procedure, that is, when the procedure of FIG. 10A is executed, the UE_A 10 can establish a PDU session with the DN_B 105.
- the fifth PDU session establishment procedure is a form of the PDU session establishment procedure executed by the network.
- the fifth PDU session establishment procedure is a processing flow started from SMF selection (S1002) in the second PDU session establishment procedure. That is, in the processing flow shown in FIG. 10, there may be no PDU session establishment request message transmission (S1000) from UE_A10. Also, this SMF selection (S1002) may be started when the (for example, AMF_A240) side detects the location of UE_A10 (UE_A10 has moved to the specific location). Except for the above differences, the fifth PDU session establishment procedure is the same as the second PDU session establishment procedure, and thus detailed description thereof is omitted.
- the fifth PDU session establishment procedure is completed. Based on the completion of the fifth PDU session establishment procedure, that is, when the procedure of FIG. 10A is executed, the UE_A 10 can establish a PDU session with the DN_B 105.
- UE_A10 sets an IPv6 address and / or obtains an IPv6 prefix for the core network. Therefore, and / or to obtain an RA (hereinafter also referred to as a second RA), an RS (hereinafter also referred to as a second RS) may be transmitted.
- the second RS transmitted from UE_A10 may be transmitted to SMF_B232 via UPF_B237.
- UPF_B237 selects SMF_B232 related to the PDU session from among a plurality of SMFs connected to the UPF, and for the selected SMF_B232, The second RS may be transmitted.
- This SMF selection in the UPF may be performed using a PDU session ID transmitted from the UE or any NF (including SMF_B232).
- the SMF_B232 that has received the second RS generates a second RA when the PDU type of the UE_A10 is IPv6, and transmits the second RA to the UE_A10 via the N4 interface and UPF_B237.
- the SMF_B232 may be transmitted by including the IPv6 prefix and / or the 64th identification information in the second RA.
- the 64th identification information may be information that is transmitted only when the 63rd identification information is received.
- the second RS and the second RA may exchange periodically while the PDU session is established.
- UE_A10 can select UPF_B237 as the default router for DN_B105 by setting the IPv6 address by receiving the second RA by any one of the above methods, and further, the preference of the route to DN_B105 Can be recognized.
- SMF_B232 and SMF_A230 are the same (represented as SMF_B232 here)
- SMF_B232 can generate and transmit not only the second RA but also the first RA. That is, when the SMF_B232 receives the second RS transmitted from the UE_A10, the third RA including the first RA and the second RA described above is transmitted to the UE_A10 via the UPF_A235 or the UPF_B237. You may send it.
- the first RA and the second RA are separate RAs, resources can be reduced by transmitting them together by including them in the third RA in this way.
- UE_A10 can recognize the route preference for DN_A5 through the first PDU session establishment procedure, and can determine the route preference for DN_B105 through any of the second to fifth PDU session establishment procedures. Can be recognized.
- UE_A10 compares the route preference value for DN_A5 with the route preference value for DN_B105.
- the PDU session for the DN having the higher preference value may be maintained, and the PDU session for the DN having the lower preference value may be released. That is, if the preference value of the route for DN_A5 is higher, the PDU session for DN_A5 may be maintained and the PDU session for DN_B105 may be released. In this case, UE_A10 may transition to the first state. If the preference value of the route for DN_B105 is higher, the PDU session for DN_B105 may be maintained and the PDU session for DN_A5 may be released. In this case, UE_A10 may transition to the third state.
- the PDU session for DN_B105 may always be prioritized. That is, UE_A10 may maintain the PDU session for DN_B105, release the PDU session for DN_A5, and transition to the third state. Conversely, when the value of the route preference for DN_A5 is the same as the value of the route preference for DN_B105, the PDU session for DN_A5 may always be prioritized. That is, UE_A10 may maintain the PDU session for DN_A5, release the PDU session for DN_B105, and transition to the first state.
- the UE configuration update procedure includes a network initiated UE configuration update procedure initiated by the network side and a UE initiated UE configuration update procedure initiated by the UE side.
- FIG. 12 shows an example of the former
- FIGS. 13 and 14 show an example of the latter.
- AMF_A240 confirms the setting state of UE_A10 and determines whether or not the setting of UE_A10 should be changed (S1200). For example, when AMF_A240 wants to change the UE capability information for UE_A10, or when it wants to change the connectivity to LADN for UE_A10 (i.e., allow or prohibit), AMF_A240 changes the setting of UE_A10. Judge that it should be.
- AMF_A240 determines that UE_A10 It is determined that the setting should not be changed, and this procedure is terminated.
- the determination in S1200 may be performed based on a change in state accompanying the movement of UE_A10, a policy on the network side, a change in registration contents of UE_A10, and the like.
- AMF_A240 may start a network trigger service request (Network (triggered Service Request) procedure. Further, when UE_A 10 is in the CM-CONNECTED state, AMF_A 240 does not have to start the network trigger service request procedure.
- AMF_A240 transmits a UE setting update command (UE Configuration Update command) including the parameters of UE_A10 to UE_A10 (S1202).
- the UE_A10 parameter may be the setting information of the UE_A10 to be updated, and may be Mobility Restrictions, Temporary User ID, TAI list, UE NSSAI information, policy information, and the like. Further, the UE_A10 parameter may be information indicating that connectivity to the LADN for the UE_A10 is permitted, and information indicating that connectivity to the LADN for the UE_A10 is prohibited (not permitted).
- AMF_A240 may request transmission of a response message to this command in the UE setting update command or together with the UE setting update command.
- UE_A10 may transmit a UE setting update completion (UE Configuration ⁇ Update complete) message to AMF_A240 (S1204).
- UE_A10 detects that a response message to the UE setting update command (i.e., a UE setting update completion message) is requested in the UE setting update command
- UE_A10 is a UE setting update completion message. May be sent.
- the UE_A 10 may trigger a registration update procedure (Registration Update procedure) based on information included in the UE setting update command.
- AMF_A240 may recognize that the update of the UE_A10 setting is completed when the UE setting update completion message is received from UE_A10.
- the AMF_A240 does not receive a UE setting update completion message from the UE_A10 within a predetermined period even though it has requested transmission of a response message to the UE setting update command in S1202, the UE_A10 setting is updated. The procedure may be terminated upon recognizing the failure. Alternatively, AMF_A240 may retransmit the UE setting update command in S1202 instead of ending this procedure. In this case, when a UE setting update completion message is received from UE_A10, AMF_A240 does not perform retransmission. Conversely, if the UE setting update completion message cannot be received from UE_A10, retransmission may be repeated a predetermined number of times.
- UE setting update procedure initiated by UE (second UE setting update procedure)
- UE_A10 a UE setting update procedure (also referred to as a second UE setting update procedure) started by UE_A10 will be described with reference to FIG. UE_A10 can start this procedure when it wants to change its settings.
- UE_A10 confirms its own setting state and determines whether or not to change its own setting (S1300). For example, UE_A10 changes its settings when it wants to change its UE capability information or when it wants to change its connectivity to LADN (that is, allow or prohibit). Judge that it should be. Conversely, when UE_A10 thinks that it is not necessary to change its own UE capability information, or when it is considered unnecessary to change its connectivity to its own LADN (i.e., permit or prohibit), UE_A10 is , It is determined that its own setting should not be changed, and this procedure is terminated.
- UE_A10 when UE_A10 is in the CM-IDLE state, UE_A10 may start a UE triggered service request (UE triggered Service Request) procedure. When UE_A10 is in the CM-CONNECTED state, UE_A10 does not have to start a UE-triggered service request (UE triggered Service Request) procedure.
- UE triggered Service Request UE triggered Service Request
- UE_A10 requests the AMF_A240 to change its own setting to the core network (AMF_A240) by transmitting a UE configuration update request (UE Configuration Update Request) message (S1302).
- UE Configuration Update Request UE Configuration Update Request
- the UE setting update request message indicates information requesting connection to the LADN (second DN), and / or a normal DN. This may be notified by including information indicating that a connection to (first DN) is not requested.
- the UE setting update request message indicates information not to request connection to LADN (second DN), and / or normal This may be notified by including information indicating that a connection to the DN (first DN) is requested.
- AMF_A240 receives the UE setting update request message from UE_A10.
- the UE setting update request message includes information indicating that a connection to the LADN is requested and / or information indicating that a connection to the normal DN (first DN) is not requested.
- AMF_A240 permits connection to LADN (second DN)
- AMF_A240 provides information indicating that UE_A10 permits connectivity to LADN and / or a normal DN (second DN). This may be notified by transmitting a UE setting update command including information indicating that connectivity to the DN 1) is not permitted.
- the UE setting update request message includes information indicating that connection to the LADN is not requested and / or information indicating that connection to the normal DN (first DN) is requested.
- AMF_A240 If AMF_A240 permits connection to the normal DN (first DN), AMF_A240 informs UE_A10 that it does not allow connectivity to LADN and / or normal DN This may be notified by transmitting a UE setting update command including information indicating that connectivity to (first DN) is permitted (S1304).
- AMF_A240 may transmit the UE setting update command including the UE_A10 parameter.
- the UE_A10 parameter may be the setting information of the UE_A10 to be updated, and may be Mobility Restrictions, Temporary User ID, TAI list, UE NSSAI information, policy information, and the like.
- AMF_A240 may request transmission of a response message to this command in the UE setting update command or together with the UE setting update command.
- AMF_A240 may transmit a UE setting update failure command (UE Configuration Update Failure command) including information indicating that to UE_A10. This may be notified by transmitting a control message.
- UE Configuration Update Failure command UE Configuration Update Failure command
- the AMF_A240 instructs the UE setting update command including information indicating that the connectivity to the LADN is not permitted to the UE_A10. This may be notified by transmitting.
- the UE setting update request message includes information indicating that connection to the LADN is not requested and / or information indicating that connection to the normal DN (first DN) is requested. If AMF_A240 does not allow connection to the normal DN (first DN), then AMF_A240 indicates that UE_A10 does not allow connectivity to the normal DN (first DN) This may be notified by transmitting a UE setting update command including information (S1304).
- UE_A10 may receive a UE setting update command from AMF_A240, and upon detecting that its request is permitted, UE_A10 may transmit a UE setting update completion message to AMF_A240 (S1306).
- UE_A10 detects that a response message to the UE setting update command (i.e., a UE setting update completion message) is requested in the UE setting update command, UE_A10 is a UE setting update completion message. May be sent.
- the UE_A 10 may trigger a registration update procedure (Registration Update procedure) based on information included in the UE setting update command.
- UE_A10 may terminate this procedure when it detects that its request is not permitted based on the information included in the UE setting update command and UE setting update failure command received from AMF_A240. Then, this procedure may be executed again after a predetermined period has elapsed.
- the AMF_A240 may recognize that the update of the UE_A10 setting has been completed.
- the AMF_A240 does not receive a UE setting update completion message from the UE_A10 within a predetermined period even though it requests transmission of a response message to the UE setting update command in S1304, the UE_A10 setting is updated. The procedure may be terminated upon recognizing the failure. Alternatively, AMF_A240 may retransmit the UE setting update command in S1304 instead of ending this procedure. In this case, when a UE setting update completion message is received from UE_A10, AMF_A240 does not perform retransmission. Conversely, if the UE setting update completion message cannot be received from UE_A10, retransmission may be repeated a predetermined number of times.
- UE setting update procedure (also referred to as a third UE setting update procedure) started by UE_A10 will be described with reference to FIG. UE_A10 can start this procedure when it wants to change its settings.
- UE_A10 confirms its own setting state and determines whether or not to change its own setting (S1400). For example, UE_A10 changes its settings when it wants to change its UE capability information or when it wants to change its connectivity to LADN (that is, allow or prohibit). Judge that it should be. Conversely, when UE_A10 thinks that it is not necessary to change its own UE capability information, or when it is considered unnecessary to change its connectivity to its own LADN (i.e., permit or prohibit), UE_A10 is , It is determined that its own setting should not be changed, and this procedure is terminated.
- UE_A10 when UE_A10 is in the CM-IDLE state, UE_A10 may start a UE triggered service request (UE triggered Service Request) procedure. When UE_A10 is in the CM-CONNECTED state, UE_A10 does not have to start a UE-triggered service request (UE triggered Service Request) procedure.
- UE triggered Service Request UE triggered Service Request
- UE_A10 notifies AMF_A240 that its own settings are to be changed by sending a UE configuration update notification (UE Configuration Update Notification) message (S1402).
- UE Configuration Update Notification UE Configuration Update Notification
- the UE setting update notification message includes information indicating that the connection is made to the LADN (second DN) and / or the normal DN (first DN). This may be notified by including information indicating that the connection is not established.
- the UE setting update notification message includes information indicating that the LADN (second DN) is not connected and / or the normal DN (first DN). This may be notified by including information indicating that the connection is made in (DN 1).
- the AMF_A240 when the AMF_A240 receives the UE setting update notification message from the UE_A10, the AMF_A240 permits the request and performs the setting for the UE_A10.
- AMF_A240 may notify UE_A10 that the setting is completed by transmitting a UE setting update setting message to UE_A10 (S1404).
- UE_A10 recognizes that its setting is completed in AMF_A240 by receiving the UE setting update setting message from AMF_A240.
- the settings related to connectivity to LADN in UE_A10 are changed through any of the above UE setting update procedures.
- UE_A10 is configured for connectivity to LADN based on the content notified by the UE setting update command. Can be changed.
- the UE can change the setting related to the connectivity to the LADN based on the content notified by the UE setting update notification message.
- UE_A10 determines whether or not to include the 61st identification information based on whether or not connection to its own LADN is permitted when sending a registration request message in the registration update procedure to be executed thereafter. May be determined.
- UE_A10 can transmit a registration request message including the 61st identification information when connectivity to LADN is permitted, but UE_A10 is not permitted to connect to LADN. In this case, a registration request message including the 61st identification information cannot be transmitted (only a registration request message not including the 61st identification information can be transmitted).
- the program that operates in the apparatus related to the present invention may be a program that controls the central processing unit (CPU) and the like to function the computer so as to realize the functions of the embodiments related to the present invention.
- a program or information handled by the program is temporarily stored in a volatile memory such as a random access memory (RAM), a nonvolatile memory such as a flash memory, a hard disk drive (HDD), or another storage system.
- RAM random access memory
- HDD hard disk drive
- a program for realizing the functions of the embodiments according to the present invention may be recorded on a computer-readable recording medium.
- the “computer system” here is a computer system built in the apparatus, and includes hardware such as an operating system and peripheral devices.
- the “computer-readable recording medium” refers to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or other recording medium that can be read by a computer. Also good.
- each functional block or various features of the apparatus used in the above-described embodiments can be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits.
- Electrical circuits designed to perform the functions described herein can be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other Programmable logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof.
- a general purpose processor may be a microprocessor or a conventional processor, controller, microcontroller, or state machine.
- the electric circuit described above may be configured by a digital circuit or an analog circuit.
- one or more aspects of the present invention can use a new integrated circuit based on the technology.
- the present invention is not limited to the above-described embodiment.
- one example of the apparatus has been described.
- the present invention is not limited to this, and a stationary or non-movable electronic device that is installed indoors or outdoors, such as an AV device or a kitchen device. It can be applied to terminal devices or communication devices such as cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other daily 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
Description
本実施形態における移動通信システムの概略について、図1、図2、図3を用いて説明する。図2は、図1の移動通信システムのうち、アクセスネットワークの詳細を記載した図である。図3は、図1の移動通信システムのうち、主にコアネットワークの詳細を記載した図である。図1に示すように、本実施形態における移動通信システム1(5GSとも称する)は、ユーザ装置(端末装置、移動端末装置とも称する)UE(User Equipment)_A10、アクセスネットワーク(AN; Access Network)_B、コアネットワーク(CN; Core Network)_B190、及びデータネットワーク(DN; Data Network)_A5、DN_B105により構成されている。
以下、各装置の構成について説明する。尚、下記各装置及び各装置の各部の機能の一部又は全部は、物理的なハードウェア上で動作するものでもよいし、汎用的なハードウェア上に仮想的に構成された論理的なハードウェア上で動作するものでもよい。
まず、UE_A10の装置構成例を、図4に示す。図4に示すように、UE_A10は、制御部_A400、送受信部_A420、記憶部_A440で構成される。送受信部_A420及び記憶部_A440は、制御部_A400とバスを介して接続されている。また、送受信部_A420には、外部アンテナ410が接続されている。また、記憶部_A440は、UEコンテキスト442を記憶している。
次に、eNB_A45、NR node_A122及びWAG_A126の装置構成例を、図5に示す。図5に示すように、eNB_A45、NR node_A122及びWAG_A126は、制御部_B500、ネットワーク接続部_B520、送受信部_B530、記憶部_B540で構成されている。ネットワーク接続部_B520、送受信部_B530及び記憶部_B540は、制御部_B500とバスを介して接続されている。また、送受信部_B530には、外部アンテナ510が接続されている。
次に、AMF_A240の装置構成例を、図6に示す。図6に示すように、AMF_A240は、制御部_C600、ネットワーク接続部_C620、記憶部_C640で構成されている。ネットワーク接続部_C620及び記憶部_C640は、制御部_C600とバスを介して接続されている。また、記憶部_C640は、コンテキスト642を記憶している。
次に、SMF_A230及びSMF_B232の装置構成例を、図7に示す。図7に示すように、SMF_A230は、それぞれ、制御部_D700、ネットワーク接続部_D720、記憶部_D740で構成されている。ネットワーク接続部_D720及び記憶部_D740は、制御部_D700とバスを介して接続されている。また、記憶部_D740は、コンテキスト742を記憶している。
次に、UPF_A235及びUPF_B237の装置構成例を、図7に示す。図7に示すように、UPF_A235は、それぞれ、制御部_D700、ネットワーク接続部_D720、記憶部_D740で構成されている。ネットワーク接続部_D720及び記憶部_D740は、制御部_D700とバスを介して接続されている。また、記憶部_D740は、コンテキスト742を記憶している。
次に、上記各装置の記憶部で記憶される各情報について、説明する。
次に、本実施形態における初期手続きの詳細手順を説明する前に、重複説明を避ける為、本実施形態で特有の用語や、各手続きに用いる主要な識別情報を予め説明する。
まず、登録手続きの概要について説明する。登録手続きは、UE_A10が主導してネットワーク(アクセスネットワーク、及び/又はコアネットワーク_B190、及び/又はDN(DN_A5又はDN_B105))へ登録する為の手続きである。UE_A10は、ネットワークに登録していない状態であれば、電源投入時等の任意のタイミングで本手続きを実行することができる。言い換えると、UE_A10は、非登録状態(RM-DEREGISTERED state)であれば任意のタイミングで本手続きを開始してもよい。また、各装置は、登録手続きの完了に基づいて、登録状態(RM-REGISTERED state)に遷移してもよい。
図9を用いて、登録手続きを実行する手順の例を説明する。以下、本手続きとは登録手続きを指す。以下、本手続きの各ステップについて説明する。
次に、DN_A5に対するPDUセッションを確立するために行うPDUセッション確立手続き(第1のPDUセッション確立手続きとも称する)の概要について説明する。以下、PDUセッション確立手続きは、本手続きとも称する。本手続きは、各装置がPDUセッションを確立する為の手続きである。尚、各装置は、本手続きを、登録手続きを完了した状態で実行してもよいし、登録手続きの中で実行してもよい。また、各装置は、登録状態で本手続きを開始してもよいし、登録手続き後の任意のタイミングで本手続きを開始してもよい。また、各装置は、PDUセッション確立手続きの完了に基づいて、PDUセッションを確立してもよい。さらに、各装置は、本手続きを複数回実行することで、複数のPDUセッションを確立してもよい。
図10を用いて、PDUセッション確立手続き(第1のPDUセッション確立手続き)を実行する手順の例を説明する。以下、本手続きの各ステップについて説明する。まず、UE_A10は、NR node_A122とAMF_A240とを介して、SMF_A230にPDUセッション確立要求(PDU Session Establishment Request)メッセージを送信することにより(S1000) (S1002) (S1004)、PDUセッション確立手続きを開始する。
次に、前述の登録手続きにおいて第62の識別情報を受信したUE_A10であって、第62の識別情報によって、あるLADNへの接続性が認められているものが、そのLADNへの接続が認められている特定の場所に移動した場合に、DN_B105に対するPDUセッションの確立する為の手続きとしては、次の4つがある。1つは、UE_A10がその特定の場所にいることを、UE_A10が検出し、DN_B105に対するPDUセッションの確立するために、PDUセッション確立手続きである(以下、第2のPDUセッション確立手続きとも称する)。別の1つは、UE_A10がその特定の場所にいることを、ネットワーク(例えばAMF_A240)が検出し、DN_B105に対するPDUセッションの確立するために、PDUセッション確立手続きをUE_A10に実行させるものである(以下、第3のPDUセッション確立手続きとも称する)。さらに別の1つは、UE_A10がその特定の場所にいることを、ネットワーク(例えばAMF_A240)が検出し、DN_B105に対するPDUセッションの確立するために、登録手続き及びPDUセッション確立手続きをUE_A10に実行させるものである(以下、第4のPDUセッション確立手続きとも称する)。そして最後の1つは、UE_A10がその特定の場所にいることを、ネットワーク(例えばAMF_A240)が検出し、DN_B105に対するPDUセッションの確立するために、ネットワーク主導でPDUセッション確立手続きを実行するものである(以下、第5のPDUセッション確立手続きとも称する)。
まず、第2のPDUセッション確立手続きについて、説明する。第2のPDUセッション確立手続きは、PDUセッションを確立する対象であるDNと、信号をやり取りする対象(すなわちSMFとUPF)が異なる点を除き、基本的には、第1のPDUセッション確立手続きと同一の処理フローであってよい。すなわち、第2のPDUセッション確立手続きは、第1のPDUセッション確立手続きにおいて、DN_A5をDN_B105とし、SMF_A230をSMF_B232とし、UPF_A235をUPF_B237としたものであるため、その詳細な説明を省略する。また、第2のPDUセッション確立手続きにおいて各装置及び/又はNF間でやりとりされる各メッセージ及びその内容は、第1のPDUセッション確立手続きにおいて各装置及び/又はNF間でやりとりされる各メッセージ及びその内容と同一であってよい。
次に、第3のPDUセッション確立手続きについて、図11を用いて説明する。
次に、第4のPDUセッション確立手続きについて、説明する。第4のPDUセッション確立手続きは、ネットワーク(例えばAMF_A240)側が、UE_A10の場所(UE_A10がその特定の場所に移動してきたこと)を検出することによって、開始されてもよい。
次に、第5のPDUセッション確立手続きについて、説明する。第5のPDUセッション確立手続きは、ネットワーク主導で実行されるPDUセッション確立手続きの一形態である。
尚、第2から第5のPDUセッション確立手続きにおいて、UE_A10は、AMF_A240からPDUセッション確立受諾メッセージを受信した後、コアネットワークに対して、IPv6アドレスの設定をする為、及び/又はIPv6プレフィックスを得る為、及び/又はRA(以下、第2のRAとも称する)をもらう為に、RS(以下、第2のRSとも称する)を送信してもよい。ここで、UE_A10から送信された第2のRSは、UPF_B237を介して、SMF_B232に送信されてもよい。例えば、UPF_B237は、UE_A10から送信された第2のRSを受信すると、そのUPFに接続された複数のSMFの中から、そのPDUセッションに関連するSMF_B232を選択し、選択されたSMF_B232に対して、第2のRSを送信してもよい。このUPFにおけるSMF選択は、UE又はいずれかのNF(SMF_B232を含む)から送信されたPDU session IDを使用して実行されてもよい。
次に、UE設定の更新手続き(UE Configuration Update procedure)について、図12、図13、図14を用いて、説明する。UE設定の更新手続きとしては、ネットワーク側によって開始されるUE設定の更新手続き(Network initiated UE Configuration Update procedure)と、UE側によって開始されるUE設定の更新手続き(UE initiated UE Configuration Update procedure)がある。図12は前者の1例を示しており、図13及び図14は後者の1例を示している。
まず、ネットワーク側によって開始されるUE設定の更新手続き(第1のUE設定の更新手続きとも称する)について、図12を用いて説明する。AMF_A240は、UE_A10の設定を変更したいときに、この手続きを開始することができる。
次に、UE_A10によって開始されるUE設定の更新手続き(第2のUE設定の更新手続きとも称する)について、図13を用いて説明する。UE_A10は、自身の設定を変更したいときに、この手順を開始することができる。
次に、UE_A10によって開始されるUE設定の更新手続き(第3のUE設定の更新手続きとも称する)について、図14を用いて説明する。UE_A10は、自身の設定を変更したいときに、この手順を開始することができる。
本発明に関わる装置で動作するプログラムは、本発明に関わる実施形態の機能を実現するように、Central Processing Unit(CPU)等を制御してコンピュータを機能させるプログラムであっても良い。プログラムあるいはプログラムによって取り扱われる情報は、一時的にRandom Access Memory(RAM)等の揮発性メモリあるいはフラッシュメモリ等の不揮発性メモリやHard Disk Drive(HDD)、あるいはその他の記憶装置システムに格納される。
5 DN_A
10 UE_A
45 eNB_A
80 E-UTRAN_A
105 DN_B
120 5G-RAN_A
122 NR node_A
125 WLAN ANc
126 WAG_A
190 コアネットワーク_B
230 SMF_A
232 SMF_B
235 UPF_A
237 UPF_B
240 AMF_A
Claims (6)
- ユーザ装置であって、
コアネットワークに対する登録手続きにおいて、AMF(Access and Mobility Management Function)に対して、LADN(Local Area Data Network)情報の送信を要求することを示す情報を含む登録要求メッセージを送信し、
前記AMFからLADN情報を受信し、
前記ユーザ装置によって開始されるPDU(Protocol Data Unit / Packet Data Unit)セッション確立手続きを実行することによって
、前記LADNとは異なるDN(Data Network)との間の第1のPDUセッションを確立し、
前記LADNに対して接続可能なエリアに移動した場合に、ネットワークによって開始されるPDUセッション確立手続きを実行することによって、前記LADNとの間の第2のPDUセッションを確立する、
ことを特徴とするユーザ装置。 - 前記ユーザ装置は、
前記第1のPDUセッションを確立する為のPDUセッション確立手続きにおいて、第1のRS(Router Solicitation)を送信し、
前記RSを受信した装置から、前記LADNとは異なるDNに対するpreferenceを示す情報を含む第1のRA(Router Advertisement)を受信する、
ことを特徴とする請求項1に記載のユーザ装置。 - 前記ユーザ装置は、
前記第2のPDUセッションを確立する為のPDUセッション確立手続きにおいて、第2のRS(Router Solicitation)を送信し、
前記RSを受信した装置から、前記LADNに対するpreferenceを示す情報を含む第2のRA(Router Advertisement)を受信する、
ことを特徴とする請求項1又は2に記載のユーザ装置。 - 前記ユーザ装置は、
前記LADNに対するpreferenceを示す情報の値と、前記LADNとは異なるDNに対するpreferenceを示す情報の値を比較し、
前記LADNに対するpreferenceを示す情報の値が、前記LADNとは異なるDNに対するpreferenceを示す情報の値よりも高い場合は、前記LADNに対するPDUセッションを維持して、前記LADNとは異なるDNに対するPDUセッションを解放し、
前記LADNに対するpreferenceを示す情報の値が、前記LADNとは異なるDNに対するpreferenceを示す情報の値よりも低い場合は、前記LADNとは異なるDNに対するPDUセッションを維持して、前記LADNに対するPDUセッションを解放する、
ことを特徴とする請求項3に記載のユーザ装置。 - 前記ユーザ装置は、
前記LADNに対するpreferenceを示す情報の値と、前記LADNとは異なるDNに対するpreferenceを示す情報の値を比較し、
前記LADNに対するpreferenceを示す情報の値と、前記LADNとは異なるDNに対するpreferenceを示す情報の値とが同一である場合は、常に、LADNに対するPDUセッションを維持して、前記LADNとは異なるDNに対するPDUセッションを解放する、
ことを特徴とする請求項3に記載のユーザ装置。 - 前記ユーザ装置は、
前記LADNに対するpreferenceを示す情報の値と、前記LADNとは異なるDNに対するpreferenceを示す情報の値を比較し、
前記LADNに対するpreferenceを示す情報の値と、前記LADNとは異なるDNに対するpreferenceを示す情報の値とが同一である場合は、常に、前記LADNとは異なるDNに対するPDUセッションを維持して、LADNに対するPDUセッションを解放する、
ことを特徴とする請求項3に記載のユーザ装置。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP18797919.0A EP3637860B1 (en) | 2017-05-09 | 2018-05-09 | User device |
CA3063020A CA3063020A1 (en) | 2017-05-09 | 2018-05-09 | User equipment (ue) |
DK18797919.0T DK3637860T3 (da) | 2017-05-09 | 2018-05-09 | Brugeranordning |
US16/612,310 US11083043B2 (en) | 2017-05-09 | 2018-05-09 | Method and system for user equipment (UE) registration |
CN201880030905.XA CN110622572B (zh) | 2017-05-09 | 2018-05-09 | 用户装置 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2017-092901 | 2017-05-09 | ||
JP2017092901A JP2020113807A (ja) | 2017-05-09 | 2017-05-09 | ユーザ装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018207837A1 true WO2018207837A1 (ja) | 2018-11-15 |
Family
ID=64102726
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2018/017974 WO2018207837A1 (ja) | 2017-05-09 | 2018-05-09 | ユーザ装置 |
Country Status (7)
Country | Link |
---|---|
US (1) | US11083043B2 (ja) |
EP (1) | EP3637860B1 (ja) |
JP (1) | JP2020113807A (ja) |
CN (1) | CN110622572B (ja) |
CA (1) | CA3063020A1 (ja) |
DK (1) | DK3637860T3 (ja) |
WO (1) | WO2018207837A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020105548A1 (ja) * | 2018-11-19 | 2020-05-28 | シャープ株式会社 | ユーザ装置、制御装置、及び通信制御方法 |
CN114586392A (zh) * | 2019-11-01 | 2022-06-03 | 夏普株式会社 | 用户设备ue以及通信控制方法 |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3569034A1 (en) * | 2017-01-16 | 2019-11-20 | Telefonaktiebolaget LM Ericsson (PUBL) | Tracking area update in rrc_inactive |
US11368254B2 (en) * | 2017-10-16 | 2022-06-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Avoiding multiple retransmissions of signalling transported by 5G NAS transport |
US11330642B2 (en) * | 2017-11-15 | 2022-05-10 | Lg Electronics Inc. | Method for supporting and providing LADN service in wireless communication system and apparatus therefor |
CN109862581B (zh) * | 2017-11-30 | 2022-05-17 | 华为技术有限公司 | 一种通信方法及装置 |
US10986602B2 (en) | 2018-02-09 | 2021-04-20 | Intel Corporation | Technologies to authorize user equipment use of local area data network features and control the size of local area data network information in access and mobility management function |
WO2019190166A1 (ko) * | 2018-03-29 | 2019-10-03 | 엘지전자 주식회사 | Ladn을 위한 pdu 세션 수립 절차를 수행하는 방법, 사용자 장치 및 네트워크 노드 |
CN112567811A (zh) * | 2018-08-09 | 2021-03-26 | 日本电气株式会社 | 允许区域或不允许区域中的ue行为 |
BR112020025742A2 (pt) * | 2018-08-10 | 2021-03-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Métodos em um primeiro e um segundo nó para facilitar um procedimento de sessão de unidade de dados de protocolo para um equipamento de usuário, primeiro e segundo nós, e, meio legível por máquina |
US11201804B2 (en) * | 2019-04-26 | 2021-12-14 | Verizon Patent And Licensing Inc. | Systems and methods for detecting control plane node availability |
WO2021155552A1 (en) * | 2020-02-07 | 2021-08-12 | Qualcomm Incorporated | High level operating system (hlos) interface for local area data network (ladn) service |
CN111935738B (zh) * | 2020-07-17 | 2022-07-26 | 网络通信与安全紫金山实验室 | 一种用于多运营商核心网对接mec的方法及系统 |
TWI793697B (zh) * | 2021-08-03 | 2023-02-21 | 緯創資通股份有限公司 | 恆在協定資料單元會話之增強信令方法及使用者裝置 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2017092901A (ja) | 2015-11-17 | 2017-05-25 | 日本通信機株式会社 | 同期放送システム、送信装置 |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101932121B (zh) * | 2009-06-19 | 2014-12-10 | 中兴通讯股份有限公司 | 移动终端通过家庭基站系统访问本地网络的方法及系统 |
CN101854630A (zh) * | 2010-05-25 | 2010-10-06 | 中兴通讯股份有限公司 | 一种实现卡鉴权的方法、系统及用户设备 |
US9094899B2 (en) * | 2013-05-28 | 2015-07-28 | Rivada Networks, Llc | Cell selection in dynamic spectrum arbitrage system |
US9226193B2 (en) * | 2013-05-28 | 2015-12-29 | Rivada Networks, Llc | Methods and systems for performing dynamic spectrum arbitrage based on eNodeB transition states |
CN104838718B (zh) * | 2013-10-25 | 2019-01-25 | 华为技术有限公司 | 一种通信方法、设备及系统 |
CN105338614B (zh) * | 2014-08-07 | 2019-02-26 | 华为技术有限公司 | 一种网络注册方法及装置 |
WO2016156430A1 (en) * | 2015-03-31 | 2016-10-06 | British Telecommunications Public Limited Company | Wlan-lte interface selection |
EP3490333B1 (en) * | 2016-08-22 | 2023-06-28 | Samsung Electronics Co., Ltd. | Method and system for regional data network configuration in wireless communication network |
US10397892B2 (en) * | 2017-02-06 | 2019-08-27 | Huawei Technologies Co., Ltd. | Network registration and network slice selection system and method |
US10986602B2 (en) | 2018-02-09 | 2021-04-20 | Intel Corporation | Technologies to authorize user equipment use of local area data network features and control the size of local area data network information in access and mobility management function |
-
2017
- 2017-05-09 JP JP2017092901A patent/JP2020113807A/ja active Pending
-
2018
- 2018-05-09 US US16/612,310 patent/US11083043B2/en active Active
- 2018-05-09 EP EP18797919.0A patent/EP3637860B1/en active Active
- 2018-05-09 DK DK18797919.0T patent/DK3637860T3/da active
- 2018-05-09 CN CN201880030905.XA patent/CN110622572B/zh active Active
- 2018-05-09 CA CA3063020A patent/CA3063020A1/en active Pending
- 2018-05-09 WO PCT/JP2018/017974 patent/WO2018207837A1/ja unknown
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2017092901A (ja) | 2015-11-17 | 2017-05-25 | 日本通信機株式会社 | 同期放送システム、送信装置 |
Non-Patent Citations (5)
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020105548A1 (ja) * | 2018-11-19 | 2020-05-28 | シャープ株式会社 | ユーザ装置、制御装置、及び通信制御方法 |
US11265838B2 (en) | 2018-11-19 | 2022-03-01 | Sharp Kabushiki Kaisha | User equipment, control device, and communication control method |
CN114586392A (zh) * | 2019-11-01 | 2022-06-03 | 夏普株式会社 | 用户设备ue以及通信控制方法 |
CN114586392B (zh) * | 2019-11-01 | 2024-01-02 | 夏普株式会社 | 用户设备ue以及通信控制方法 |
Also Published As
Publication number | Publication date |
---|---|
DK3637860T3 (da) | 2023-09-25 |
US20200120751A1 (en) | 2020-04-16 |
EP3637860B1 (en) | 2023-07-05 |
CN110622572B (zh) | 2022-03-18 |
EP3637860A1 (en) | 2020-04-15 |
CN110622572A (zh) | 2019-12-27 |
US11083043B2 (en) | 2021-08-03 |
EP3637860A4 (en) | 2020-08-26 |
CA3063020A1 (en) | 2019-12-03 |
JP2020113807A (ja) | 2020-07-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018207837A1 (ja) | ユーザ装置 | |
AU2018289655B2 (en) | User equipment, communication control method of user equipment, core network device, communication control method of core network, SMF, and communication control method of SMF | |
JP6698587B2 (ja) | Ue及びueの通信制御方法 | |
JP7045808B2 (ja) | Ue及びueの通信制御方法 | |
WO2019098392A1 (ja) | Ue及びueの通信制御方法 | |
JP6884731B2 (ja) | Ue通信制御方法 | |
JP2019004409A (ja) | 端末装置、コアネットワーク内の装置、データネットワーク内の装置、及び通信制御方法 | |
JP6869908B2 (ja) | Ue及びueの通信制御方法 | |
WO2019031433A1 (ja) | 端末装置、コアネットワーク内の装置、及び通信制御方法 | |
JP2019033417A (ja) | 端末装置、コアネットワーク内の装置、及び通信制御方法 | |
WO2020145305A1 (ja) | Ue、及びsmf | |
WO2020100637A1 (ja) | Ueおよびsmf | |
JP7240227B2 (ja) | Ue、及び通信制御方法 | |
JP6884730B2 (ja) | Ue通信制御方法 | |
JP6698618B2 (ja) | Ue及びueの通信制御方法 | |
JP6901413B2 (ja) | Ue及びueの通信制御方法 | |
JP2020170899A (ja) | Ue、及び通信制御方法 | |
WO2021029381A1 (ja) | Ue、及び通信制御方法 | |
WO2019216391A1 (ja) | Ue、及びその通信方法 | |
JP2020170897A (ja) | Ue、及び通信制御方法 | |
JP7362344B2 (ja) | Ue、及び通信制御方法 | |
JP7336239B2 (ja) | Ue、及び通信制御方法 | |
JP2019145935A (ja) | Ue、及び通信制御方法 | |
JP2019186718A (ja) | Ue、制御装置、及び通信制御方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18797919 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 3063020 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref document number: 3063020 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2018797919 Country of ref document: EP Effective date: 20191209 |
|
NENP | Non-entry into the national phase |
Ref country code: JP |