WO2018066234A1 - 端末装置、MME(Mobility Management Entity)、CPF(Control Plane Function)、及び通信制御方法 - Google Patents
端末装置、MME(Mobility Management Entity)、CPF(Control Plane Function)、及び通信制御方法 Download PDFInfo
- Publication number
- WO2018066234A1 WO2018066234A1 PCT/JP2017/029303 JP2017029303W WO2018066234A1 WO 2018066234 A1 WO2018066234 A1 WO 2018066234A1 JP 2017029303 W JP2017029303 W JP 2017029303W WO 2018066234 A1 WO2018066234 A1 WO 2018066234A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- procedure
- identification information
- core network
- cpf
- information
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 101
- 238000000034 method Methods 0.000 title claims description 928
- 230000005540 biological transmission Effects 0.000 claims description 68
- 230000008859 change Effects 0.000 claims description 20
- 230000006870 function Effects 0.000 description 58
- 238000003860 storage Methods 0.000 description 56
- 230000004044 response Effects 0.000 description 50
- 238000007726 management method Methods 0.000 description 29
- 230000007704 transition Effects 0.000 description 29
- 238000012545 processing Methods 0.000 description 22
- 238000010295 mobile communication Methods 0.000 description 21
- 238000012546 transfer Methods 0.000 description 16
- 238000012217 deletion Methods 0.000 description 13
- 230000037430 deletion Effects 0.000 description 13
- 239000004065 semiconductor Substances 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 7
- 238000004321 preservation Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 230000004913 activation Effects 0.000 description 5
- 239000013256 coordination polymer Substances 0.000 description 5
- 238000012508 change request Methods 0.000 description 4
- 238000005457 optimization Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 238000012419 revalidation Methods 0.000 description 2
- 102000018059 CS domains Human genes 0.000 description 1
- 108050007176 CS domains Proteins 0.000 description 1
- 241000700159 Rattus Species 0.000 description 1
- 238000004378 air conditioning Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 238000009795 derivation Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000007420 reactivation Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
-
- 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
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/13—Cell handover without a predetermined boundary, e.g. virtual cells
-
- 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
- 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/06—Registration at serving network Location Register, VLR or user mobility server
- H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server
-
- 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/06—De-registration or detaching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/14—Backbone network devices
Definitions
- the present invention relates to a terminal device, MME (Mobility Management Entity), CPF (Control Plane Function), and a communication control method.
- MME Mobility Management Entity
- CPF Control Plane Function
- 3GPP 3rd Generation Partnership Project
- 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
- next-generation communication technology and system architecture for 5G (5th Generation) mobile communication systems which are next-generation mobile communication systems.
- NextGen Architecture and Security for for Next Generation System
- NextGen extracts technical issues for connecting a wide variety of terminals to cellular networks, and specifies solutions.
- NextGen is studying the optimization of session management in mobile communication services between terminals and network devices.
- the present invention has been made in view of such circumstances, and an object thereof is to provide means for establishing a session, communication control means for realizing communication of various types of user data, and the like. .
- a terminal device performs a detach procedure for a first core network, and after the detach procedure, a transmission / reception unit that executes an attach procedure for a second core network; and the detach Based on completion of the procedure, the control unit changes the connection destination from the first core network to the second core network, and the transmission / reception unit sends a detach request message to the CPF (Control Plane) in the detach procedure.
- the attach request message is transmitted to MME (Mobility Management Entity), and the detach request message includes information indicating that the connection destination is changed, and the attach request message includes It includes information indicating over.
- MME Mobility Management Entity
- a CPF Control Plane Function
- a transmission / reception unit that executes a detach procedure, and a connection destination of a terminal device based on completion of the detach procedure, from the first core network to the second
- a control unit that disconnects from the terminal device is provided, and the transmission / reception unit transmits a detach request message to the terminal device in the detach procedure, and the detach request message is , Including information indicating that the connection destination of the terminal device is changed.
- An MME Mobility Management Entity
- a transmission / reception unit that executes an attach procedure, and a connection destination of a terminal device based on the completion of the attach procedure, from the first core network to the second A control unit that connects to the terminal device in order to change to the core network, wherein the transmission / reception unit receives an attach request message from the terminal device in the attach procedure, and the attach request message is a handover It includes the information which shows.
- a communication control method for a terminal device includes a step of executing a detach procedure for a first core network, and an attach procedure for a second core network after the detach procedure. And a step of changing the connection destination from the first core network to the second core network based on the completion of the detach procedure, and in the detach procedure, a detach request message is sent to the CPF (Control Plane Function) further includes a step of transmitting an attach request message to MME (Mobility Management Entity) in the attach procedure, and the detach request message changes a connection destination. And the attach request message indicates handover. Including broadcast, characterized in that.
- the communication control method of CPF Control Plane Function
- CPF Control Plane Function
- the communication control method of CPF includes a step of executing a detach procedure and, based on completion of the detach procedure, a connection destination of the terminal device from the first core network. Disconnecting the connection with the terminal device to change to the second core network, and the transmitting and receiving unit transmits a detach request message to the terminal device in the detach procedure. And the detach request message includes information indicating that the connection destination is changed.
- An MME (Mobility Management Entity) communication control method includes a step of executing an attach procedure, and a connection destination of a terminal device based on the completion of the attach procedure, from the first core network. Connecting to the terminal device in order to change to the second core network, and further comprising the step of receiving an attach request message from the terminal device in the attach procedure.
- the request message includes information indicating handover.
- the terminal can be simultaneously connected to the core network via a plurality of access networks, and can realize communication of various types of user data.
- the core network can accommodate terminal devices connected to various access networks, and can provide mobile communication services.
- FIG. 3 is a diagram for explaining an example of the configuration of a core network and an access network_A in a mobile communication system.
- FIG. 3 is a diagram for explaining an example of the configuration of a core network and an access network_B in a mobile communication system.
- It is a figure for demonstrating the apparatus structure of UE.
- It is a figure for demonstrating the memory
- It is a figure for demonstrating the apparatus structure of eNB / NR node / WAG.
- FIG. 1 is a diagram for explaining the outline of the mobile communication system in the present embodiment.
- the mobile communication system 1 includes a mobile terminal apparatus UE_A10, an access network_A, an access network_B, a core network_A90, a core network_B190, and a PDN (PacketData Network) _A5.
- UE_A10 may be a terminal device that can be wirelessly connected, and may be a UE (User Equipment), an ME (Mobile Equipment), an MS (Mobile Station), a CIoT (Cellular Internet of Things) terminal (CIoT UE), or the like.
- the core network may be the core network_A90 and / or the core network_B190
- the access network may be the access network_A and / or the access network_B.
- UE_A10 can be connected to the access network and / or the core network. Furthermore, UE_A10 can connect with PDN_A5 via an access network and / or a core network, and further transmits / receives user data to / from PDN_A5.
- the user data may be data transmitted / received between UE_A10 and PDN_A5. Further, transmission / reception (communication) of user data may be performed using a PDU (Protocol Data Unit or Packet Data Unit) session or may be performed using a PDN connection (Packet Data Network Connection). Further, user data communication is not limited to IP (Internet Protocol) communication but may be non-IP communication.
- a PDU session or a PDN connection (hereinafter also referred to as a PDN connection) is established between UE_A10 and PDN_A5 in order to provide a PDU connection service for transmitting and receiving user data between UE_A10 and PDN_A5.
- the PDU session or PDN connection may be connectivity established between UE_A 10 and the external gateway.
- the external gateway may be a device that connects the PDN_A5 and a core network such as PGW (Packet Data Network Gateway) _A30, UPGW (User Plane Gateway) _A130, and SCEF (Service Capability Exposure Function) _A46.
- PGW Packet Data Network Gateway
- UPGW User Plane Gateway
- SCEF Service Capability Exposure Function
- the PDU session or PDN connection may be a communication path established for transmitting / receiving user data between the UE_A 10 and the core network and / or PDN_A5, or may be a communication path for transmitting / receiving PDUs.
- the PDU session or the PDN connection may be a session established between the UE_A 10 and the core network and / or PDN_A5, and is configured by a transfer path such as one or a plurality of bearers between each device in the mobile communication system 1. It may be a logical communication path.
- the PDN connection may be a connection established by the UE_A 10 between the core network_A 90 and the external gateway, or may be a connection established between the UE_A 10 and the PGW_A 30 and / or SCEF_A 46.
- the PDU session may be a connection established by UE_A10 between the core network_B190 and the external gateway, a connection established between UE_A10 and UPGW_A130, a PDN connection (Packet Data Data Network Connection), etc.
- the PDN connection may be connectivity and / or connection between UE_A10 and PGW_A30 via eNB (evolved NodeB) _A45 and / or SGW (Serving Gateway) _A35, and UE_A10 via eNB_A45 and / or MME_A40. It may be connectivity and / or connection with SCEF_A46. Further, the PDU session may be connectivity and / or connection between UE_A 10 and UPGW_A 130 via NR node_A122.
- eNB evolved NodeB
- SGW Serving Gateway
- UE_A 10 can transmit and receive user data using a PDU session or a PDN connection with a device such as an application server arranged in PDN_A 5.
- the PDU session or the PDN connection can transfer user data transmitted and received between devices such as an application server arranged in the UE_A10 and the PDN_A5.
- each device UE_A10, a device in the access network, and / or a device in the core network
- identification information includes APN (AccessPoint Name), TFT (Traffic Flow Template), session type, application identification information, PDN_A5 identification information, NSI (Network Slice Instance) identification information, and DCN (Dedicated Core Core Network). At least one of the identification information and the access network identification information may be included, or other information may be further included. Further, when a plurality of PDU sessions or PDN connections are established, each piece of identification information associated with the PDU session or PDN connection may have the same contents or different contents.
- IP communication is data communication using IP, and is data communication realized by transmission / reception of IP packets with an IP header.
- the payload part which comprises an IP packet may contain 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.
- PDN_A5 may be a DN (Data Network) that provides a communication service to UE_A10.
- the DN may be configured as a packet data service network or may be configured for each service.
- PDN_A5 may include a connected communication terminal. Therefore, connecting to PDN_A5 may be connecting to a communication terminal or server device arranged in PDN_A5. Further, transmitting / receiving user data to / from PDN_A5 may be transmitting / receiving user data to / from a communication terminal or server device arranged in PDN_A5.
- PDN_A5 may be expressed as DN, or DN may be expressed as PDN_A5.
- 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 networks are E-UTRAN (Evolved Universal Terrestrial Radio Access Network) _A80, UTRAN (Universal Terrestrial Radio Access Network) _A20, GERAN (GSM (registered trademark) EDGE Radio Access Network) _A25, NextGenRAN (Next Generation Radio Access Network)
- the non-3GPP access network may be WLAN ANb75, WLAN ANa70, WLAN ANc125.
- 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.
- the core network is an IP mobile communication network operated by a mobile network operator (Mobile Network Operator) connected to the access network and / or PDN_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 provider such as MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler) or a virtual mobile body.
- a core network for a communication service provider may be used.
- the core network_A90 may be an EPC (Evolved Packet Core) that configures EPS (Evolved Packet System)
- the core network _B190 is an NGC (Next Generation System (NextGen Generation System)) that configures NGS (NextGen System (Next Generation System)).
- the EPC may be the core network_A90
- the NGC may be the core network_B190
- 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.
- the core network may be core network_A90, core network_B190, or a combination thereof.
- the core network_A90 may be an EPC, and the core network_B190 may be an NGC (NextGen) Core).
- Fig. 2 shows an example of the core network_A90 configuration.
- Core network_A90 in Figure 2 (a) is HSS (Home Subscriber Server) _A50, AAA (AuthenticationAuthorization Accounting) _A55, PCRF (Policy and Charging Rules Rules) _A60, PGW_A30, ePDG (enhancedPacket Data Data Gateway) _A65, SGW_A35, It consists of Mobility (Management (Entity) _A40, SGSN (ServingGPRS (Support) Node) _A42, and SCEF_A46.
- the core network_A90 can be connected to a plurality of radio access networks (E-UTRAN_A80, WLAN ⁇ ANb75, WLAN ANa70, UTRAN_A20, GERAN_A25).
- the radio access network may be configured to be connected to a plurality of different access networks, or may be configured to be connected to any one access network.
- UE_A10 can be wirelessly connected to the wireless access network.
- the access network that can be connected by the WLAN access system is WLAN access network b (WLAN ANb75) connected to the core network via ePDG_A65, or WLAN access network a (WLAN ANa70) connected to PGW_A30, PCRF_A60, and AAA_A55.
- WLAN access network b WLAN access network b
- ePDG_A65 Wireless AN
- WLAN access network a WLAN ANa70
- PGW_A30 is connected to PDN_A5, SGW_A35, ePDG_A65, WLANANa70, PCRF_A60, and AAA_A55, and is a relay device that transfers user data as a gateway between PDN_A5 and / or DN and core network_A90.
- the PGW_A30 may be a gateway for IP communication and / or non-IP communication.
- PGW_A30 may have a function of transferring IP communication, or may have a function of converting non-IP communication and IP communication.
- a plurality of such gateways may be arranged in the core network_A90. Further, the plurality of gateways may be gateways that connect the core network_A90 and a single DN.
- U-Plane may be a communication path for transmitting and receiving user data, and may be composed of a plurality of bearers.
- C-Plane Control Plane
- PGW_A30 may be connected to the UP function and the Policy function, or may be connected to UE_A10 via the U-Plane. Further, the PGW_A30 may be configured together with the UPGW_A130.
- SGW_A35 is connected to PGW_A30, MME_A40, E-UTRAN_A80, SGSN_A42, and UTRAN_A20, and relays user data as a gateway between core network_A90 and 3GPP access networks (UTRAN_A20, GERAN_A25, E-UTRAN_A80) Device.
- SGW_A35 may be an UP function that transfers user data with a contact point with the access network.
- UPGW (User Plane Gateway) _A130 is a gateway for transferring user data between the access network and the core network. But you can.
- MME_A40 is connected to SGW_A35, the access network, HSS_A50, and SCEF_A46, and is a control device that performs location information management including mobility management of UE_A10 and access control via the access network. Further, the MME_A 40 may include a function as a session management device that manages a session established by the UE_A 10. Further, a plurality of such control devices may be arranged in the core network_A90. For example, a location management device different from the MME_A40 may be configured. A location management device different from MME_A40 may be connected to SGW_A35, an access network, SCEF_A46, and HSS_A50, similarly to MME_A40.
- the MMEs may be connected to each other. Thereby, transmission / reception of the context of UE_A10 may be performed between MMEs.
- the MME_A 40 is a management device that transmits and receives control information related to mobility management and session management with the UE_A 10, and in other words, may be a control device of a control plane (Control-Plane; C-Plane; CP).
- the MME_A40 may be a management device configured in one or more core networks or DCN or NSI, or one or more core networks or A management device connected to DCN or NSI may be used.
- a plurality of DCNs or NSIs may be operated by a single communication carrier, or may be operated by different communication carriers.
- the MME_A40 may be a relay device that transfers user data as a gateway between the core network_A90 and the access network. Note that the user data transmitted / received using the MME_A 40 as a gateway may be small data.
- MME_A40 may be an NF that plays a role of mobility management such as UE_A10, an NF that plays a role of session management such as a PDU session, or an NF that manages one or a plurality of NSIs.
- the MME_A 40 may be an NF that plays one or more of these roles.
- the NF may be one or more devices arranged in the core network_A90, and may be a CP function for control information and / or control messages (hereinafter referred to as CPF (Control Plane Function) or Control Plane Network Function). Or a shared CP function shared among a plurality of network slices.
- CPF Control Plane Function
- Control Plane Network Function Control Plane Network Function
- NF is a processing function configured in the network. That is, the NF may be a functional device such as MME, SGW, PGW, CPF, or UPGW, or may be function or capability capability information such as MM (Mobility Management) or SM (Session Management).
- the NF may be a functional device for realizing a single function or a functional device for realizing a plurality of functions.
- the NF for realizing the MM function and the NF for realizing the SM function may exist separately, and the NF for realizing both the MM function and the SM function exists. May be.
- HSS_A50 is connected to MME_A40, AAA_A55, and SCEF_A46, and is a management node that manages subscriber information.
- the subscriber information of HSS_A50 is referred to at the time of access control of MME_A40, for example.
- the HSS_A50 may be connected to a location management device different from the MME_A40.
- HSS_A50 may be connected to CPF_A140.
- AAA_A55 is connected to PGW_A30, HSS_A50, PCRF_A60, and WLANANa70, and performs access control for UE_A10 connected via WLAN ⁇ ⁇ ANa70.
- PCRF_A60 is connected to PGW_A30, WLAN ANa75, AAA_A55, and PDN_A5, and performs QoS management for data delivery. For example, the QoS of the communication path between UE_A10 and PDN_A5 is managed. Furthermore, the PCRF_A 60 may be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used when each device transmits and receives user data.
- PCC Policy and Charging Control
- PCRF_A60 may be a Policy function that creates and / or manages policies. More specifically, the PCRF_A60 may be connected to the UP function.
- EPDG_A65 is connected to PGW_A30 and WLAN ANb75, and delivers user data as a gateway between core network_A90 and WLAN ANb75.
- SGSN_A42 is connected to UTRAN_A20, GERAN_A25 and SGW_A35, and is a control device for location management between 3G / 2G access network (UTRAN / GERAN) and LTE access network (E-UTRAN). Furthermore, SGSN_A42 has a PGW and SGW selection function, a UE_A10 time zone management function, and an MME_A40 selection function during handover to E-UTRAN.
- SCEF_A46 is connected to PDN_A5, MME_A40, and HSS_A50, and is a relay device that transfers user data as a gateway connecting PDN_A5 and / or DN and core network_A90.
- SCEF_A 46 may be a gateway for non-IP communication. Further, the SCEF_A 46 may have a function of converting non-IP communication and IP communication. A plurality of such gateways may be arranged in the core network_A90. Furthermore, a plurality of gateways connecting the core network_A90 and a single PDN_A5 and / or DN may be arranged.
- SCEF_A 46 may be configured outside the core network or may be configured inside.
- each radio access network includes devices (for example, base station devices and access point devices) to which UE_A 10 is actually connected.
- devices for example, base station devices and access point devices
- a device used for connection a device adapted to a radio access network can be considered.
- E-UTRAN_A80 is an LTE (LongTerm Evolution) access network and includes eNB_A45.
- eNB_A45 is a radio base station to which UE_A10 is connected by E-UTRA (EvolvedvolveUniversal TerrestrialRadio Access), and E-UTRAN_A80 may include one or more eNB_A45.
- a plurality of eNBs may be connected to each other.
- UTRAN_A20 is a 3G access network and includes RNC (Radio Network Controller) _A24 and NB (NodeB) _A22.
- NB_A22 is a radio base station to which UE_A10 is connected by UTRA (Universal Terrestrial Radio Access), and UTRAN_A20 may be configured to include one or a plurality of radio base stations.
- the RNC_A24 is a control unit that connects the core network_A90 and the NB_A22, and the UTRAN_A20 may be configured to include one or a plurality of RNCs.
- the RNC_A24 may be connected to one or a plurality of NB_A22.
- the RNC_A24 may be connected to a radio base station (BSS (Base Station Subsystem) _A26) included in the GERAN_A25.
- BSS Base Station Subsystem
- GERAN_A25 is a 2G access network and includes BSS_A26.
- BSS_A26 is a radio base station to which UE_A10 is connected by GERA (GSM (registered trademark) / EDGE
- a plurality of BSS_A 26 may be connected to each other.
- BSS_A26 may be connected to RNC_A24.
- WLAN ANA70 is a wireless LAN access network and includes WLAN AP (Wireless Local Area Network Access Point) a72 and TWAG (Trusted WLAN Access Gateway) _A74.
- WLAN APa72 is a wireless base station to which UE_A10 connects with a WLAN access system that is reliable to the operator operating the core network_A90
- WLAN ANa70 includes one or more wireless base stations May be.
- TWAG_A74 is a gateway between the core network_A90 and the WLAN ANa70.
- the WLAN APA 72 and the TWAG_A 74 may be configured by a single device. Even if the operator that operates the core network_A90 and the operator that operates the WLAN ANa70 are different, it is possible to realize such a configuration by contracts and contracts between the operators.
- WLAN ANb75 is a wireless LAN access network and includes WLAN APb76.
- WLAN APb76 is a radio base station to which UE_A10 is connected in the WLAN access system when the trust relationship is not established with the operator operating the core network_A90.
- One or a plurality of radio base stations are connected to WLAN ANb75.
- a station may be included.
- WLAN ANb75 is connected to core network_A90 using ePDG_A65, which is a device included in core network_A90, as a gateway.
- ePDG_A65 has a security function to ensure safety.
- FIG. 3 shows an example of the configuration of the core network_B190.
- the core network_B190 in FIG. 3 (a) includes HSS_A50, PCRF_A60, UPGW (User (Plane Gateway) _A130, CPF (Control Plane Function) _A140, and SCEF_A46.
- the core network_B190 can be connected to a plurality of radio access networks (E-UTRAN_A80, NextGen RAN_A120, WLAN ANc125).
- the radio access network may be configured to be connected to a plurality of different access networks, or may be configured to be connected to any one access network.
- UE_A10 can be wirelessly connected to the wireless access network.
- E-UTRAN_A80 and NextGen RAN_A120 can be configured as an access network that can be connected with the 3GPP access system.
- the access network that can be connected by the WLAN access system can be configured as a WLAN access network c (WLANcANc125) connected to CPF_A140 and UPGW_A130.
- WLANcANc125 WLAN access network c
- UPGW_A130 is a device connected to PDN_A5, PCRF_A60, CPF_A140, E-UTRAN_A80, NextGen RAN_A120, and WLAN ANc125, and is a relay device that transfers user data as a gateway between PDN_A5 and / or DN and core network_B190. is there.
- UPGW_A 130 may be a gateway for IP communication and / or non-IP communication. Further, UPGW_A 130 may have a function of transferring IP communication, or may have a function of converting non-IP communication and IP communication. Note that a plurality of such gateways may be arranged in the core network_B190. Further, the plurality of gateways may be gateways connecting the core network_B190 and a single DN.
- the UPGW_A 130 may have connectivity with other NFs and may be connected to each device via other NFs.
- CPF_A140 is a device connected to UPGW_A130, E-UTRAN_A80, NextGen RAN_A120, WLAN ANc125, HSS_A50 and SCEF_A46.
- CPF_A140 may be an NF that plays a role of mobility management such as UE_A10, may be an NF that plays a role of session management such as a PDU session, or may be an NF that manages one or a plurality of NSIs.
- the CPF_A 140 may be an NF that plays one or more of these roles.
- the NF may be one or a plurality of devices arranged in the core network_B190, or may be a CP function (Control Plane ⁇ ⁇ Function or Control PlaneNetwork Function) for control information and / or control messages, and a plurality of network slices. It may be a shared CP function shared between them.
- CPF_A 140 may have connectivity with other NFs, and may be connected to each device via other NFs.
- the CPF may be configured as a control plane device for controlling a Control plane (control plane).
- Each device may be configured in the same manner as the device of the core network_B190, and the configuration and role of the SCEF_A46, HSS_A50, and PCRF_A60 may be the same devices as those described in the core network_A90.
- each radio access network includes a device (for example, a base station device or an access point device) to which UE_A 10 is actually connected.
- a device used for connection a device adapted to a radio access network can be considered.
- NextGen RAN_A120 is a 5G access network, and includes NR node (New Radio Access Technology node) _A122.
- NR node_A122 is a radio base station to which UE_A10 is connected by NextGen RA (Next GenerationRadio Access), and NextGen ⁇ RAN_A120 may include one or more NR node_A122.
- NextGen RAN_A120 may be an access network composed of E-UTRA_A80 and / or NextGen RAN_A120.
- NextGen 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 WAG_A126.
- WAG (WLAN AccessGateway) _A126 is a radio base station to which UE_A10 is connected by wireless LAN access, and WLAN ANc125 may be configured to include one or more WAG_A126.
- WAG_A126 may be a gateway between the core network_B190 and WLAN ANc125.
- the functional unit of the radio base station and the functional unit of the gateway may be configured by different devices.
- the WLAN ANc 125 may have the same configuration as the WLAN ANa 70 and / or the WLAN ANb75, or may have a different configuration.
- UE_A10 being connected to each radio access network means being connected to a base station device, an access point, etc. 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.
- IMSI International Mobile Subscriber Identity
- MME_A40 / CPF_A140, 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.
- 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.
- EMM State / MM State may be information that can distinguish between a state in which UE_A10 is registered in core network_A90 and a state in which UE_A10 is registered in core network_B190.
- GUTI Globally Unique Temporary Identity
- the GUTI includes MME_A40 / CPF_A140 identification information (GUMMEI (Globally UniqueMME Identifier)) and UE_A10 identification information (M-TMSI (M-Temporary MobileSubscriber Identity)) in the specific MME_A40 / CPF_A140.
- ME Identity is the 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 the MME_A40 / CPF_A140 may be information indicated by the storage unit of the HSS_A50. Note that GUTI may include information for identifying CPF_A140.
- MME F-TEID is information that identifies MME_A40 / CPF_A140.
- the MME F-TEID may include the IP address of MME_A40 / CPF_A140, the TEID (TunnelunEndpoint Identifier) of MME_A40 / CPF_A140, or both of them. Further, the IP address of MME_A40 / CPF_A140 and the TEID of MME_A40 / CPF_A140 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.
- the PGW F-TEID may include the IP address of PGW_A30 / UPGW_A130, may include the TEID of PGW_A30 / UPGW_A130, or may include both of them.
- the IP address of PGW_A30 / UPGW_A130 and the TEID of PGW_A30 / UPGW_A130 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 that connects the core network_A90.
- 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
- identification information for identifying an external network such as a DN.
- there may be a plurality of gateways that can be selected by the APN.
- one gateway may be selected from among the plurality of gateways by another method using identification information other than APN.
- UE Radio Access Capability is identification information indicating the radio access capability of UE_A10.
- UENetwork 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 GERAN_A 25 and / or UTRAN_A 20 functions.
- Access Restriction is registration information of access restriction.
- eNBAddress is the IP address of eNB_A45.
- MME UE S1AP ID is information for identifying UE_A10 in MME_A40 / CPF_A140.
- 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 does not have to be included.
- SCEF IV ID is the SCEF_A46 IP address used in the PDU session.
- DefaultBearer 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 TransactionIdentifier
- 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. 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. Therefore, 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.
- DefaultBearer may be information that UE_A10 and / or SGW_A35 and / or PGW_A30 / UPGW_A130 obtain from the core network when a PDU session is established.
- User Identity is information for identifying a subscriber. UserIdentity 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 used in the PDU session, and may be the IP address of MME_A40 / CPF_A140.
- 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.
- the MME ID is information for identifying MME_A40 / CPF_A140.
- 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.
- WAGID is information for identifying WAG_A126.
- each device may operate on physical hardware, or may be logically configured on virtually general-purpose hardware. It may operate on hardware.
- FIG. 4 shows the device configuration of UE_A10.
- the UE_A 10 includes a transmission / reception unit_A420, a control unit_A400, 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.
- Control unit_A400 is a functional unit for controlling UE_A10.
- the control unit _A400 implements various processes by reading and executing various programs stored in the storage unit_A440.
- Transmission / reception unit_A420 is a functional unit for UE_A10 to connect to a base station and / or access point in an access network and connect to the access network.
- an external antenna _A410 is connected to the transmission / reception unit _A420.
- the transmission / reception unit_A420 is a functional unit for the UE_A10 to connect to a base station and / or an access point in the access network.
- the transmission / reception unit_A420 is a transmission / reception function unit in which the UE_A10 transmits / receives user data and / or control information from a base station and / or an access point in the access network.
- Storage unit_A440 is a functional unit that stores programs and data necessary for each operation of UE_A10.
- the storage unit_A440 is configured by, for example, a semiconductor memory, an HDD (Hard Disk Drive), or the like.
- the storage unit_A440 may store at least identification information and / or control information and / or flags and / or parameters included in a control message transmitted and received in a communication procedure described later.
- the storage unit_A440 stores the UE context 442 as shown in the figure.
- the information elements stored in the storage unit_A440 will be described.
- the UE context 442 may include a UE context used when connecting to the core network_A90 and a UE context used when connecting to the core network_B190.
- the UE context used when connecting to the core network_A90 and the UE context used when connecting to the core network_B190 may be stored together or may be stored separately.
- FIG. 5 (b) shows information elements included in the UE context stored for each UE.
- the UE context stored for each UE includes IMSI, EMMState, GUTI, and ME Identity.
- FIG. 5 (c) shows a UE context for each PDU session or PDN connection stored for each PDU session or PDN connection.
- the UE context for each PDU session includes APN in Use, Assigned Session Type, IP Address (es), and Default Bearer.
- FIG. 5 (d) shows a UE context for each bearer stored in the UE storage unit.
- the UE context for each bearer includes EPS Bearer ID, TI, and TFT.
- FIG. 6 shows device configurations of eNB_A45, NR node_A122, and WAG_A126.
- eNB_A45, NR node_A122, and WAG_A126 are configured by a network connection unit_B620, a transmission / reception unit_B630, a control unit_B600, and a storage unit_B640.
- the network connection unit_B620, the transmission / reception unit_B630, and the storage unit_B640 are connected to the control unit_B600 via a bus.
- Control unit_B600 is a functional unit for controlling eNB_A45.
- the control unit_B600 implements various processes by reading and executing various programs stored in the storage unit_B640.
- the network connection unit_B620 is a functional unit for the eNB_A45, NR node_A122, and WAG_A126 to connect to the MME_A40 and / or SGW_A35. Furthermore, the network connection unit_B620 is a transmission / reception unit in which the eNB_A45, NRnode_A122, and WAG_A126 transmit / receive user data and / or control information from the MME_A40 and / or SGW_A35.
- the transmission / reception unit_B630 is a functional unit for the eNB_A45, NR node_A122, and WAG_A126 to connect to the UE_A10. Further, the transmission / reception unit_B630 is a transmission / reception function unit that transmits / receives user data and / or control information from the UE_A10. In addition, an external antenna _B610 is connected to the transmission / reception unit _B630.
- Storage unit_B640 is a functional unit that stores programs, data, and the like necessary for each operation of eNB_A45, NR node_A122, and WAG_A126.
- the storage unit_B640 is configured by, for example, a semiconductor memory, an HDD, or the like.
- the storage unit_B640 may store at least identification information and / or control information and / or flags and / or parameters included in a control message transmitted and received in a communication procedure described later.
- the storage unit_B640 may store these pieces of information as contexts for each UE_A10.
- FIG. 7 shows device configurations of MME_A40 and CPF_A140.
- the MME_A 40 and the CPF_A 140 include a network connection unit_C720, a control unit_C700, and a storage unit_C740.
- the network connection unit_C720 and the storage unit_C740 are connected to the control unit_C700 via a bus.
- the functions of these units may operate on physical hardware, or may operate on logical hardware configured virtually on general-purpose hardware.
- Control unit_C700 is a functional unit for controlling MME_A40 and CPF_A140.
- the control unit_C700 implements various processes by reading and executing various programs stored in the storage unit_C740.
- the network connection unit_C720 is a functional unit for the MME_A 40 to connect to the base station in the access network and / or the access point in the access network, and / or SCEF_A46, and / or HSS_A50 and / or SGW_A35. Further, the network connection unit _C720 may be configured such that the MME_A 40, the base station in the access network, and / or the access point in the access network, and / or the SCEF_A46, and / or the HSS_A50, and / or the SGW_A35, the user data and / or It is a transmission / reception part which transmits / receives control information.
- the network connection unit _C720 is a functional unit for the CPF_A140 to connect to a base station in the access network and / or an access point in the access network, and / or SCEF_A46, and / or HSS_A50 and / or UPGW_A130. is there. Further, the network connection unit _C720 may be configured such that the MME_A 40, the base station in the access network, and / or the access point in the access network, and / or SCEF_A46, and / or HSS_A50, and / or UPGW_A130, user data and / or It is a transmission / reception part which transmits / receives control information.
- Storage unit_C740 is a functional unit that stores programs, data, and the like necessary for each operation of MME_A40 and CPF_A140.
- the storage unit_C740 is configured by, for example, a semiconductor memory, an HDD, or the like.
- the storage unit_C740 may store at least identification information and / or control information and / or flags and / or parameters included in a control message transmitted and received in a communication procedure described later.
- the storage unit_C740 stores the MME context 742 as shown in the figure.
- CPF_A140 may be a storage context for the MME context.
- FIG. 8 (b) shows information elements included in the UE context stored for each UE.
- the MME context stored for each UE is IMSI, MSISDN, MM State, GUTI, ME Identity, UE Radio Access Capability, UE Network Capability, MS Network Capability, Access Restriction, MME F-TEID, SGW F -One or more of TEID, eNB Address, MME UE S1AP ID, eNB UE S1AP ID, NR node Address, NR node ID, WAG Address, and WAG ID are included.
- Fig. 9 (c) shows the MME context for each PDU session or PDN connection stored for each PDU session or PDN connection.
- the MME context for each PDU session includes APN Use, Assigned Session Type, IP Address (es), PGW F-TEID, SCEF ID, and Default bearer.
- Fig. 9 (d) shows the MME context for each bearer stored for each bearer.
- the MME 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 Contains one or more of ID, NRnodeID, and WAG ID.
- the information elements included in the MME context shown in FIGS. 8 and 9 may be included in either the MM context or the EPS bearer context and stored.
- FIG. 10 shows the device configuration of SGW_A35.
- SGW_A35 includes a network connection unit_D1020, a control unit_D1000, and a storage unit_D1040.
- the network connection unit_D1020 and the storage unit_D1040 are connected to the control unit_D1000 via a bus.
- Control unit_D1000 is a functional unit for controlling SGW_A35.
- the control unit_D1000 implements various processes by reading and executing various programs stored in the storage unit_D1040.
- the network connection unit_D1020 is a functional unit for the SGW_A35 to connect to a base station and / or access point in the access network, and / or MME_A40, and / or PGW_A30, and / or SGSN_A42. Further, in the network connection unit _D1020, the SGW_A35 transmits and receives user data and / or control information from the base station and / or access point in the access network, and / or the MME_A40, and / or the PGW_A30, and / or the SGSN_A42. It is a transmission / reception unit.
- Storage unit_D1040 is a functional unit that stores programs and data necessary for each operation of SGW_A35.
- the storage unit_D1040 is configured by, for example, a semiconductor memory, an HDD, or the like.
- the storage unit_D1040 may store at least identification information and / or control information and / or flags and / or parameters included in a control message transmitted and received in a communication procedure described later.
- the storage unit_D1040 stores the EPS bearer context 1042 as shown in the figure.
- the EPS bearer context 1042 includes one stored for each UE, one stored for each PDU session, and one stored for each bearer.
- FIG. 11 (b) shows information elements of EPS bearer context stored for each UE.
- the EPS bearer context stored for each UE includes IMSI, MEIdentity, MSISDN, MME F-TEID, and SGW F-TEID.
- the EPS bearer context includes an EPS bearer context for each PDU session stored for each PDU session.
- FIG. 11 (c) shows an EPS bearer context for each PDU session.
- the EPS bearer context for each PDU session includes APN Use, Assigned Session Type, SGW F-TEID, PGW F-TEID, Default Bearer, and IP Address (es).
- EPS bearer context includes EPS bearer context for each bearer.
- FIG. 11 (d) shows an EPS bearer context for each bearer.
- EPS bearer context for each bearer is EPS Bearer ID, TFT, PGW F-TEID, SGWF-TEID, eNB F-TEID, MME Address, NR node Address, WAG Address, MME ID, NR node ID , Including one or more of WAGID.
- FIG. 10 shows the device configurations of PGW_A30 and UPGW_A130.
- the PGW_A30 and the UPGW_A130 are composed of a network connection unit_D1020, a control unit_D1000, and a storage unit_D1040.
- the network connection unit_D1020 and the storage unit_D1040 are connected to the control unit_D1000 via a bus.
- the functions of these units may operate on physical hardware, or may operate on logical hardware configured virtually on general-purpose hardware.
- Control unit_D1000 is a functional unit for controlling PGW_A30.
- the control unit_D1000 implements various processes by reading and executing various programs stored in the storage unit_D1040.
- the network connection unit_D1020 is a functional unit for connecting the PGW_A30 to the SGW_A35 and / or PCRF_A60 and / or ePDG_A65 and / or AAA_A55 and / or TWAG_A74 and / or PDN_A5.
- the network connection unit _D1020 allows the PGW_A30 to transmit and receive user data and / or control information from the SGW_A35 and / or PCRF_A60, and / or ePDG_A65, and / or AAA_A55, and / or TWAG_A74, and / or PDN_A5. It is a transmission / reception unit.
- the network connection unit_D1020 is a functional unit for UPGW_A130 to connect with PCRF_A60 and / or UPGW_A130 and / or PDN_A5.
- the network connection unit _D1020 allows the PGW_A30 to transmit and receive user data and / or control information from the SGW_A35 and / or PCRF_A60, and / or ePDG_A65, and / or AAA_A55, and / or TWAG_A74, and / or PDN_A5. It is a transmission / reception unit.
- Storage unit_D1040 is a functional unit that stores programs and data required for each operation of PGW_A30.
- the storage unit_D1040 is configured by, for example, a semiconductor memory, an HDD, or the like.
- the storage unit_D1040 may store at least identification information and / or control information and / or flags and / or parameters included in a control message transmitted and received in a communication procedure described later.
- the storage unit_D1040 stores the EPS bearer context 1042 as shown in the figure.
- the EPS bearer context 1042 includes one that is stored for each UE, one that is stored for each APN, one that is stored for each PDU session or PDN connection, and one that is stored for each bearer. May be stored separately. Further, the EPS bearer context may be a context stored in UPGW_A 130.
- FIG. 12 (b) shows information elements included in the EPS bearer context stored for each UE.
- the EPS bearer context stored for each UE includes IMSI, MEIdentity, MSISDN, and RAT type.
- Fig. 12 (c) shows the EPS bearer context stored for each APN.
- the EPS bearer context stored for each APN in the PGW storage unit includes APN in use.
- the EPS bearer context stored for each APN may be stored for each Data ⁇ ⁇ Network Identifier.
- Fig. 12 (d) shows the EPS bearer context for each PDU session or PDN connection stored for each PDU session or PDN connection.
- the EPS bearer context for each PDU session or PDN connection includes Assigned Session Type, IP Address (es), SGW F-TEID, PGW F-TEID, and Default Bearer.
- Fig. 12 (e) shows the EPS bearer context stored for each EPS bearer.
- the EPS bearer context includes EPS Bearer ID, TFT, SGWF-TEID, and PGW F-TEID.
- FIG. 10 shows the device configuration of SCEF_A46.
- the SCEF_A 46 includes a network connection unit_D1020, a control unit_D1000, and a storage unit_D1040.
- the network connection unit_D1020 and the storage unit_D1040 are connected to the control unit_D1000 via a bus.
- Control unit_D1000 is a functional unit for controlling SCEF_A46.
- the control unit_D1000 implements various processes by reading and executing various programs stored in the storage unit_D1040.
- the network connection unit_D1020 is a functional unit for the SCEF_A46 to connect to the core network_A90.
- the network connection unit_D1020 is a functional unit for the SCEF_A46 to connect to the MME_A40.
- the network connection unit_D1020 is a transmission / reception unit in which the SCEF_A46 transmits / receives user data and / or control information from the MME_A40.
- Storage unit_D1040 is a functional unit that stores programs and data necessary for each operation of SCEF_A46.
- the storage unit_D1040 is configured by, for example, a semiconductor memory, an HDD, or the like.
- the storage unit_D1040 may store at least identification information and / or control information and / or flags and / or parameters included in a control message transmitted and received in a communication procedure described later.
- the storage unit_D1040 stores the EPS bearer context 1042 as shown in the figure.
- the information elements stored in the storage unit_D1040 will be described.
- FIG. 13 (b) shows information elements included in the EPS bearer context.
- the EPS bearer context includes User Identity, APN in Use, EPS Bearer ID, and Serving Node Information.
- the first state in the present embodiment is a state in which the procedure for connecting and registering the UE_A10 to the core network_B190 has been completed and each device has established a PDU session. Each device may execute the procedure for registering UE_A10 in the core network_B190 and the procedure for establishing a PDU session at the same time or separately. Furthermore, the first state may be a state in which a procedure for updating the location registration information of UE_A10 is completed.
- the first state in the present embodiment may be a state in which each device has established a PDU session with respect to the core network_B190. More specifically, the first state may be a state in which each device establishes a PDU session between UE_A10 and UPGW_A130 via NRnode_A122. Note that the first state is not limited to these states.
- the EPS service in the present embodiment may be a service provided by the PS domain or a connection service provided using EPC.
- non-EPS service in this embodiment may be a service provided by the CS domain, and may be a service other than the EPS service.
- the NGS service in the present embodiment may be a connection service provided using the core network_B190. Further, the NGS service may be a service different from the EPS service or a service similar to the EPS service. Note that the NGS service is not limited to this, and may be any system for providing a mobile communication service.
- non-NGS service in the present embodiment may be a service other than the NGS service, and may include an EPS service and / or a non-EPS service.
- the session in this embodiment may be a PDU session, a PDN connection, or an EPS bearer.
- the session establishment procedure may be a PDU session establishment procedure or a PDN connection procedure.
- the session disconnection procedure may be a PDU session disconnection procedure or a PDN connection disconnection procedure.
- the information for identifying the session may be a PDU session ID, a PDN connection ID, or an EPS bearer ID. The information for identifying the session may be other identification information.
- the EPS bearer in the present embodiment is a logical communication path established between UE_A10 and PGW_A30.
- the EPS bearer may be a communication path constituting a PDN connection.
- the EPS bearer may be a logical communication path established between UE_A 10 and UPGW_A 130, or may be a communication path that forms a PDU session.
- the NSI Network Slice Instance
- the NSI in the present embodiment may be configured by a virtual NF (Network Function) generated using NST (Network Slice Template).
- NST is a logical expression of one or a plurality of NF (Network Function) associated with a resource request for providing a required communication service and capability.
- the NSI may be an aggregate in the core network_B190 composed of a plurality of NFs.
- the NSI may be a logical network configured to separate user data delivered by services or the like.
- At least 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.
- UE shall 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 Can do.
- APN such as UE usage type and / or one or more network slice type IDs and / or one or more NS IDs Can do.
- the DCN (Dedicated Core Network) is a core network dedicated to a specific subscriber type, which is configured in one or more in the core network_A90.
- a DCN for a UE registered as an M2M function user may be configured in the core network_A90.
- a default DCN for a UE without an appropriate DCN may be configured in the core network_A90.
- At least one or more MME_A40 or SGSN_A42 may be arranged, and at least one or more SGW_A35, PGW_A30 or PCRF_A60 may be arranged.
- a UE can be assigned to one DCN based on registration information such as UE usage type and / or DCNID.
- the UE usage type in this embodiment is a parameter value included in the registration information of the UE used to identify DCN and / or NSI.
- UE usage type may be stored in HSS_50.
- MME_A40 and / or SGSN_A42 may select SGW_A35 and PGW_A30 based on UE usage type.
- CPF_A140 may select UPGW_A130 based on UE usage type.
- the DN ID in the present embodiment is identification information for identifying the core network_B190 and an external network such as a DN. Furthermore, the DN ID can also be used as information for selecting a gateway such as UPGW_A130 connecting 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.
- the tracking area in the present embodiment is a single or a plurality of ranges that can be represented by the location information of UE_A10 managed by the core network.
- the tracking area may be composed of a plurality of cells.
- the tracking area may be a range where a control message such as paging is broadcast, or a range where UE_A 10 can move without performing a handover procedure.
- the tracking area may be a routing area, a location area, or the like.
- SSC Session and Service Continuity
- 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.
- 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 of 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.
- the SSC mode 1 in this embodiment is a service session continuation mode in which the same TUPF is maintained regardless of the access technology such as RAT (Radio Access Technology) and cells used when the UE_A 10 connects to the network. More specifically, SSCmode 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 in the present embodiment is a service session continuation mode in which the same TUPF is maintained only within the TUPF serving area. More specifically, SSCmode 2 may be a mode that realizes service session continuation without changing the TUPF used by the established PDU session as long as UE_A 10 is in the TUPF serving area. Furthermore, 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. Further, the subset of access networks may be a network composed of one or more RATs and / or cells.
- the SSC mode 3 in this embodiment is a PDU session established between UE_A10 and TUPF, and / or a new PDU via a new TUPF for the same DN before disconnecting the communication path.
- a session and / or service session continuation mode that allows establishing a communication path.
- SSCmode 3 may be a service session continuation mode that permits UE_A 10 to be multi-homing.
- / or SSC mode 3 may be a mode in which a service session continuation using TUPF associated with a plurality of PDU sessions and / or PDU sessions is permitted.
- each device may realize service session continuation using a plurality of PDU sessions, or may realize service session continuation using a plurality of TUPFs.
- TUPF when each device establishes a new PDU session and / or channel, the selection of a new TUPF may be performed by the network, and the new TUPF is the location where UE_A10 is connected to the network.
- TUPF may be optimal for
- UE_A10 will immediately perform an association of the application and / or flow communication to the newly established PDU session. It may be implemented based on completion of communication.
- Default SSC mode is the SSC mode used by UE_A10 and / or the network when a specific SSC mode is not determined. Specifically, Default SSC mode is the SSC mode used by UE_A10 when there is no request for SSC mode from the application and / or when there is no UE_A10 policy for determining SSC mode for the application. Also good. And / or SSC mode used by the network when there is no request for SSC mode from UE_A10.
- Default SSC mode may be set for each PDN_A5 based on subscriber information and / or operator policy and / or UE_A10 policy, and may be set for each UE_A10 and / or subscriber. May be. Further, Default SSC mode may be information indicating SSC mode 1, SSC mode 2, or SSC mode 3.
- the first identification information in the present embodiment is information for identifying an external network such as PDN_A5 or DN that UE_A10 requests to connect to core network_B190. Further, the first identification information may be a DN ID. Further, the first identification information may be information composed of a plurality of DN IDs or information composed of DN IDs and APNs.
- the second identification information in the present embodiment is information indicating the type of connection service that UE_A10 requests to use from core network_B190.
- the second identification information may be information indicating that the UE_A10 requests use of only the NGS service, or may be information indicating that the UE_A10 requests use of both the NGS service and the non-NGS service.
- the second identification information may be information indicating that the UE_A10 requests use of the NGS service and the EPS service, or indicates that the UE_A10 requests use of the NGS service, the EPS service, and the nonEPS service. It may be information.
- the second identification information may be information indicating the type of attach procedure requested by UE_A 10 or may be an attach type.
- the second identification information may be information indicating that registration of only the core network_B190 and / or connection is requested, registration to both the core network_B190 and the core network_A90, and / or It may be information indicating that a connection is requested.
- the third identification information in the present embodiment is information indicating the type of connection service that UE_A10 supports use.
- the third identification information may be information indicating that UE_A10 supports the use of only the NGS service, or information indicating that UE_A10 supports the use of both the NGS service and the non-NGS service.
- the third identification information may be information indicating that the UE_A10 supports the use of the NGS service and the EPS service, or the UE_A10 supports the use of the NGS service, the EPS service, and the non-EPS service. It may be the information shown.
- the third identification information may be UE_A10 capability information indicating the type of attach procedure supported by UE_A10.
- the third identification information may be UE_A10 capability information that supports registration and / or connection only to the core network_B190, registration to both the core network_B190 and the core network_A90, and / or Alternatively, it may be UE_A10 capability information that supports connection.
- the fourth identification information in the present embodiment is information indicating the SSC mode requested by the UE_A 10 to the core network_B190. Further, the fourth identification information may be information indicating the SSC mode used when switching the session from the NGS service to the EPS service. In other words, the fourth identification information may be information indicating the SSC mode used when the session is switched and / or reattached from the core network_B190 to the core network_A90. Specifically, the fourth identification information may be information indicating SSC mode 1, information indicating SSC mode 2, or information indicating SSC mode 3.
- the fifth identification information in the present embodiment is information indicating SSC mode supported by UE_A10. Further, the fifth identification information may be information indicating the SSC mode supported when switching the session from the NGS service to the EPS service. In other words, the fifth identification information may be information indicating the SSC mode supported when the session is switched and / or reattached from the core network_B190 to the core network_A90. Specifically, the fifth identification information may be information indicating SSC mode 1, information indicating SSC mode 2, or information indicating SSC mode 3.
- the sixth identification information in the present embodiment is information for identifying an external network such as PDN_A5 or DN to which UE_A10 can be connected. Further, the sixth identification information may be an APN. Further, the sixth identification information may be information composed of a plurality of APNs, or may be information composed of an APN and a DN ID. Further, the sixth identification information may be the same information as the first identification information, or may be included in the first identification information and transmitted / received.
- 7th identification information in this embodiment is information which identifies CPF_A140 from which UE_A10 requests connection to the core network_B190. Further, the seventh identification information may be information indicating CPF_A 140 to which UE_A 10 can be connected, or information for identifying CPF_A 140 to which UE_A 10 has been connected before. Further, the seventh identification information may be information for identifying UE_A10. For example, the seventh identification information may be CPF ID, GUTI, IMSI, NGSmobile identity, or other information.
- the CPF_A140 may be a common CPF that connects the core network_B190 and the UE_A10 and transmits / receives a control message to / from the UE_A10.
- the seventh identification information may be common CPF ID.
- the eighth identification information in the present embodiment may include information for identifying the MME_A 40 to which the UE_A 10 can be connected, or may include information for identifying the MME_A 40 to which the UE_A 10 has previously connected. Further, the eighth identification information may be information for identifying UE_A10. For example, the eighth identification information may be GUTI, IMSI, EPS mobile identity, or other information.
- the ninth identification information in this embodiment is information that identifies and / or indicates the network slice type that UE_A10 requests from the core network_B190.
- the ninth identification information may be information such as an NSD ID that identifies an NSI, a network slice type ID that identifies a network slice type, or the like.
- the ninth identification information may be a UE usage type or a part of the UE usage type.
- the ninth identification information may be APN.
- the ninth identification information may be composed of information for identifying a plurality of NSIs.
- the ninth identification information may be configured to include information for identifying an NF (Network Function) in the core network_B190.
- the ninth identification information may be UE_A10 and / or registration information of UE_A10 held by any device in the network.
- the eleventh identification information in the present embodiment is information for identifying an external network such as a DN that the core network_B190 has permitted to connect to the UE_A10 and / or to which the UE_A10 has connected. Furthermore, the eleventh identification information may be a DN ID. Further, the eleventh identification information may be information composed of a plurality of DN IDs or information composed of DN IDs and APNs.
- the twelfth identification information in the present embodiment is information indicating the type of connection service that the core network_B190 permits the UE_A10 to use.
- the twelfth identification information may be information indicating that the core network_B190 has permitted the UE_A10 to use only the NGS service, or the core network_B190 may use both the NGS service and the non-NGS service. May be information indicating that is permitted.
- the twelfth identification information may be information indicating that the use of the NGS service and the EPS service is permitted by the core network_B190, or the use of the NGS service, the EPS service, and the non-EPS service is determined by the core network_ It may be information indicating that B190 has permitted.
- the twelfth identification information may be information indicating the type of attach procedure permitted by the core network_B190 to the UE_A10, or may be an attach result.
- the twelfth identification information may be information indicating that registration of UE_A10 only to core network_B190 and / or connection is permitted, registration to both core network_B190 and core network_A90, And / or information indicating that the connection is permitted.
- the thirteenth identification information in the present embodiment is information indicating the type of connection service supported by the core network_B190.
- the thirteenth identification information may be information indicating that the core network_B190 supports the use of only the NGS service, or the core network_B190 supports the use of both the NGS service and the non-NGS service. Information indicating this may be used.
- the thirteenth identification information may be information indicating that the core network_B190 supports the use of the NGS service and the EPS service, or the use of the NGS service, the EPS service, and the non-EPS service. It may be information indicating that B190 supports.
- the thirteenth identification information may be capability information of the core network_B190 indicating the type of attach procedure supported by the core network_B190.
- the thirteenth identification information may be capability information of the core network_B190 that supports connection and / or connection only to the core network_B190, and is registered in both the core network_B190 and the core network_A90. And / or capability information of the core network_B190 that supports connection.
- the 14th identification information in the present embodiment is information indicating the SSC mode allowed by the core network_B190 to the UE_A10. Further, the fourteenth identification information may be information indicating SSC mode allowed to be used when switching the session from the NGS service to the EPS service. In other words, the 14th identification information may be information indicating the SSC mode allowed to be used when switching and / or reattaching the session from the core network_B190 to the core network_A90. Specifically, the 14th identification information may be information indicating that SSC mode 1 is permitted, information indicating that SSC mode 2 is permitted, or that SSC mode 3 is permitted. It may be information indicating.
- the fifteenth identification information is information indicating the SSC mode supported by the core network_B190. Further, the fifteenth identification information may be information indicating the SSC mode supported when switching the session from the NGS service to the EPS service. In other words, the fifteenth identification information may be information indicating the SSC mode supported when switching and / or reattaching the session from the core network_B190 to the core network_A90. Specifically, the fifteenth identification information may be information indicating that the core network_B190 supports SSC mode 1, information indicating that SSC mode 2 is supported, or SSC mode 3. Information indicating support may be used.
- the sixteenth identification information in the present embodiment is information for identifying an external network such as a DN to which UE_A10 can connect when connecting to core network_A90, which is permitted by core network_B190 to UE_A10. Further, the sixteenth identification information may be an APN. Further, the sixteenth identification information may be information composed of a plurality of APNs, or may be information composed of an APN and a DN ID. Further, the sixteenth identification information may be the same information as the eleventh identification information, or may be included in the eleventh identification information and transmitted / received.
- the seventeenth identification information in this embodiment is information for identifying CPF_A140 that the core network_B190 has permitted to connect to UE_A10. Further, the seventeenth identification information may be information indicating CPF_A140 connected to UE_A10 or information indicating CPF_A140 to which UE_A10 can be connected. Further, the seventeenth identification information may be information for identifying UE_A10. For example, the 17th identification information may be CPF ID, GUTI, NGS mobile identity, or other information.
- the CPF_A140 may be a common CPF that connects the core network_B190 and the UE_A10 and transmits / receives a control message to / from the UE_A10.
- the 17th identification information may be common CPF ID.
- the 18th identification information in the present embodiment is information for identifying the MME_A40 that the core network_B190 has permitted to connect to the UE_A10. Further, the eighteenth identification information may be information indicating MME_A 40 to which UE_A 10 can be connected. Further, the eighteenth identification information may be information for identifying UE_A10. For example, the eighteenth identification information may be GUTI, IMSI, EPSmobile identity, or other information.
- the nineteenth identification information in the present embodiment is information for identifying and / or indicating the network slice type that the core network_B190 has permitted to connect to the UE_A10. Further, the nineteenth identification information may be information such as an NSD ID for identifying an NSI, a network slice type ID for identifying a network slice type, or the like. Further, the 19th identification information may be UE usage type or may be a part of UE usage type. Further, the 19th identification information may be an APN. Note that the 19th identification information may be composed of information for identifying a plurality of NSIs. Further, the 19th identification information may include information for identifying NF (Network Function) in the core network_B190. Further, the 19th identification information may be registration information of UE_A10 (held by UE_A10 and / or any device in the network).
- NF Network Function
- the 21st identification information in the present embodiment is information indicating that the UE_A10 request is not permitted to the core network_B190. Further, the 21st identification information may be reason information (Reject Cause) indicating the reason why the request of UE_A10 is rejected.
- the 21st identification information may be information indicating that connection to the UE_A10 core network_B190 and / or DN is not permitted, or the UE_A10 connection to the core network_B190 and / or DN has failed. It may be information indicating that this has been done. Furthermore, the 21st identification information may be information indicating that connection and / or registration to the CPF_A 140 for which the UE_A 10 requests connection is not permitted, the information identifying the UE_A 10 is not normal, and / or It may be information indicating that it is not permitted. Furthermore, the 21st identification information may be information indicating that the UE_A 10 is not properly connected due to network congestion, authentication, or the like.
- the 21st identification information may be information indicating that the UE_A 10 is not permitted to use both the NGS service and the non-NGS service, and may be information indicating that the NGS service is not permitted to be used. Furthermore, the 21st identification information may be information indicating that the UE_A10 is not permitted to use both the NGS service and the EPS service, and that the NGS service, the EPS service, and the nonEPS service are not permitted to be used. It may be the information shown.
- the 21st identification information may be information indicating that UE_A10 is connected to an unauthorized PLMN (Public Land Mobile Network), and the service requested by UE_A10 is not allowed in the current PLMN. It may be information indicating that this is the case, or information indicating that an appropriate cell does not exist in the current PLMN.
- PLMN Public Land Mobile Network
- the 21st identification information may be information indicating that UE_A10 is connected to a tracking area that is not permitted, or information indicating that the service requested by UE_A10 is not permitted in the current tracking area. But you can. Further, the 21st identification information may be information indicating that an appropriate cell does not exist in the current tracking area, or information indicating that roaming is not permitted in the current tracking area.
- the 21st identification information may be information indicating that the SSC mode requested by UE_A10 is not permitted or information indicating that the core network_B190 does not support the SSC mode requested by UE_A10.
- the 21st identification information may be information indicating that NSI for which the UE_A10 requests connection is not permitted, or information indicating that the core network_B190 does not support the network slice type requested by the UE_A10. But you can.
- the 22nd identification information is information indicating the type of connection service that the core network_B190 does not permit the UE_A10 to use.
- the 22nd identification information may be information indicating that the core network_B190 does not permit the use of only the NGS service, or the core network_B190 uses both the NGS service and the non-NGS service. It may be information indicating that permission is not granted.
- the 22nd identification information may be information indicating that the use of the NGS service and the EPS service is not permitted by the core network_B190, or the use of the NGS service, the EPS service, and the non-EPS service. Information indicating that the network_B190 did not permit may be used.
- the 22nd identification information may be information indicating the type of attach procedure that the core network_B190 does not permit.
- the 22nd identification information may be information indicating that the registration of only the core network_B190 and / or the connection is not permitted, the registration to both the core network_B190 and the core network_A90, and / or Information indicating that connection is not permitted may be used.
- the 23rd identification information in this embodiment is information indicating the type of connection service that the core network_B190 does not support use.
- the 23rd identification information may be information indicating that the core network_B190 does not support the use of only the NGS service, or the core network_B190 does not support the use of both the NGS service and the non-NGS service. Information indicating this may be used.
- the 23rd identification information may be information indicating that the core network_B190 does not support the use of the NGS service and the EPS service, or the use of the NGS service, the EPS service, and the non-EPS service. Information indicating that B190 is not supported may be used.
- the 23rd identification information may be capability information of the core network_B190 indicating the type of attach procedure that the core network_B190 does not support.
- the 23rd identification information may be registered only in the core network_B190 and / or the capability information of the core network_B190 that does not support connection, and registered in both the core network_B190 and the core network_A90. And / or capability information of the core network_B190 that does not support connection.
- the 24th identification information in the present embodiment is information indicating the SSC mode that the core network_B190 does not permit to the UE_A10. Further, the 24th identification information may be information indicating an SSC mode that is not permitted to be used when switching the session from the NGS service to the EPS service. In other words, the 24th identification information may be information indicating an SSC mode that is not permitted to be used when switching and / or reattaching a session from the core network_B190 to the core network_A90. Specifically, the 24th identification information may be information indicating that SSC mode 1 is not allowed, information indicating that SSC mode 2 is not allowed, or SSC mode 3 is allowed. It may be information indicating that there was no information.
- the 25th identification information in this embodiment is information indicating SSC mode that is not supported by the core network_B190.
- the 25th identification information may be information indicating an SSC mode that is not supported when a session is switched from the NGS service to the EPS service.
- the 25th identification information may be information indicating an SSC mode that is not supported when the session is switched and / or reattached from the core network_B190 to the core network_A90.
- the 25th identification information may be information indicating that the core network_B190 does not support SSC mode 1, information indicating that SSC mode 2 is not supported, or SSC mode 3. It may be information indicating that it is not supported.
- the 26th identification information may be information indicating that connection to the NSI for which UE_A10 requests connection is not permitted, and the core network_B190 supports the network slice type requested by UE_A10. It may be information indicating that it is not.
- the twenty-sixth identification information in the present embodiment may be information for identifying and / or indicating a network slice type that permits connection.
- the network slice type that permits connection may be information different from the network slice type requested by UE_A10.
- the 26th identification information may be information such as an NSD ID for identifying the NSI, a network slice type ID for identifying the type of the network slice, or the like.
- the 26th identification information may be UE usage type or may be a part of UE usage type.
- the 26th identification information may be an APN. Note that the 26th identification information may be composed of information for identifying a plurality of NSIs.
- the twenty-sixth identification information may include information for identifying an NF (Network Function) in the core network_B190. Further, the 26th identification information may be UE_A10 and / or registration information of UE_A10 held by any device in the network.
- NF Network Function
- the thirty-first identification information in the present embodiment is information indicating the type of connection service for which UE_A 10 requests the core network_B190 to update registration information.
- the 31st identification information may be information indicating that the UE_A10 requests to update the registration information of only the NGS service, or the UE_A10 requests to update the registration information of both the NGS service and the non-NGS service. Information indicating this may be used.
- the 31st identification information may be information indicating that the UE_A10 requests to update the registration information of the NGS service and the EPS service, or the registration information of the NGS service, the EPS service, and the non-EPS service is updated. It may be information indicating that UE_A10 requests.
- the thirty-first identification information may be information indicating the type of tracking area update procedure requested by UE_A 10, or may be an update type.
- the thirty-first identification information may be information indicating that registration information update and / or connection of only the core network_B190 is requested, and registration information to both the core network_B190 and the core network_A90. It may be information indicating that the update and / or connection is requested.
- the thirty-first identification information may be information indicating that only the tracking area in the NGS service is requested to be updated, and the tracking area in the NGS service and the tracking area in the non-NGS service and / or the routing area are requested to be updated. It may be information indicating.
- the 31st identification information may be information indicating that the tracking area in the NGS service and the tracking area in the EPS service are requested to be updated, the tracking area in the NGS service, the tracking area in the EPS service, and the routing in the non-EPS service. It may be information indicating that an area update is requested.
- the thirty-second identification information in the present embodiment is the same as the third identification information.
- the thirty-third identification information in the present embodiment is the same as the seventh identification information.
- the thirty-fourth identification information in the present embodiment is the same as the eighth identification information.
- the thirty-fifth identification information in this embodiment is the same as the fourth identification information.
- the thirty-sixth identification information in the present embodiment is the same as the fifth identification information.
- the 37th identification information in this embodiment is the same as the 9th identification information.
- the forty-first identification information in the present embodiment is information indicating the type of connection service that the core network_B190 has allowed the UE_A10 to update registration information.
- the 41st identification information may be information indicating that the core network_B190 has permitted the update of the registration information of only the NGS service, or the registration information of both the NGS service and the non-NGS service may be updated. It may be information indicating that the network_B190 is permitted. In other words, the 41st identification information may be information indicating that the core network_B190 has permitted the update of the registration information of the NGS service and the EPS service, or the registration information of the NGS service, the EPS service, and the non-EPS service. Information indicating that the core network_B190 has permitted the update may be used.
- the forty-first identification information may be information indicating the type of attach procedure permitted by the core network_B190 to the UE_A10, or may be an attach result.
- the 41st identification information may be information indicating that updating and / or connection of the registration information of only the core network_B190 is permitted, and registration information to both the core network_B190 and the core network_A90. Information indicating that the update and / or connection is permitted.
- the 41st identification information may be information indicating that only the tracking area in the NGS service is permitted to be updated, and the tracking area in the NGS service and the tracking area in the non-NGS service and / or the routing area are permitted to be updated. It may be information indicating that. Furthermore, the 41st identification information may be information indicating that updating of the tracking area in the NGS service and the tracking area in the EPS service is permitted, or the tracking area in the NGS service, the tracking area in the EPS service, and the non-EPS service. It may be information indicating that updating of the routing area is permitted.
- the forty-second identification information in this embodiment is the same as the thirteenth identification information.
- the 43rd identification information in this embodiment is the same as the 14th identification information.
- the 44th identification information in this embodiment is the same as the 15th identification information.
- the 45th identification information in this embodiment is the same as the 17th identification information.
- the 46th identification information in this embodiment is the same as the 18th identification information.
- the 47th identification information in this embodiment is the same as the 19th identification information.
- the 51st identification information in the present embodiment is information indicating a detach procedure type requested by the core network_B190 to the UE_A10.
- the information indicating the type of detach procedure may be a detach type.
- the 51st identification information may be information indicating that reattachment of UE_A10 is required or information indicating that it is not required. Note that the reattach may be a re-attach procedure.
- the 52nd identification information in the present embodiment is information indicating whether or not transmission / reception of information indicating a handover is necessary at the time of reattachment. Furthermore, the 52nd identification information may be information indicating whether or not an attach procedure for another core network after the detach procedure is required, or information indicating whether or not the attach procedure is supported.
- the 52nd identification information may be information indicating that the core network_B 190 requests that the UE_A 10 perform the attach procedure to another core network after the detach procedure. Furthermore, the 52nd identification information may be information indicating that an attach procedure after the detach procedure is necessary to switch the session from the core network_B190 to another core network.
- Another core network may be the core network_A90 or a core network identified by the 53rd identification information.
- the 53rd identification information in this embodiment is information indicating a system to be connected at the time of reattachment.
- the connected system may be a system that provides an NGS service, a system that provides EPS, or a system that provides a non-EPS service.
- the 53rd identification information may be information indicating a core network to be connected at the time of reattachment.
- the 53rd identification information may be information indicating the core network_A90 or information indicating the core network_B190.
- the 53rd identification information may be information indicating the type of control message used at the time of reattachment.
- the 53rd identification information may indicate that UE_A10 performs the attach procedure using the EPS control message after the detach procedure, or performs the attach procedure using the NGS control message. You may show that.
- the 53rd identification information may indicate that UE_A10 performs an attach procedure to core network_A90 after a detach procedure, or indicates that an attach procedure to core network_B190 is performed. Good.
- the 54th identification information in this embodiment is reason information (Cause) indicating the reason why the detachment procedure is started. Further, the 54th identification information may be information indicating the reason why the state of UE_A10 is no longer appropriate due to a change in subscriber information or the like.
- the 54th identification information may be information indicating that the UE_A10 is no longer permitted to connect to the core network_B190 and / or the DN. Further, the 54th identification information may be information indicating that the connection and / or registration of UE_A10 to CPF_A140 is no longer permitted, and the information identifying UE_A10 is no longer normal and / or is no longer permitted. It may be information indicating that. Further, the 54th identification information may be information indicating that the connection of the UE_A 10 is not appropriate due to network congestion, authentication, or the like.
- the 54th identification information may be information indicating that the use of both the NGS service and the non-NGS service is no longer permitted for UE_A10, and may also be information indicating that the use of the NGS service is no longer permitted. Good. Further, the 54th identification information may be information indicating that the use of both the NGS service and the EPS service is no longer permitted for the UE_A10, and all the use of the NGS service, the EPS service, and the nonEPS service is permitted. It may be information indicating that it has disappeared.
- the 54th identification information may be information indicating that the service used by UE_A 10 needs to be switched from the NGS service to the non-NGS service.
- the 54th identification information may be information indicating that the session needs to be switched from the core network_B190 to another core network, or the handover from the core network_B190 to another core network may be performed. It may be information indicating that there is.
- the 54th identification information may be information indicating that the PLMN connected to the UE_A10 is no longer permitted, or information indicating that the service used by the UE_A10 is no longer permitted in the current PLMN Alternatively, it may be information indicating that an appropriate cell no longer exists in the current PLMN.
- the 54th identification information may be information indicating that the tracking area to which UE_A10 is connected is no longer permitted, or that the service used by UE_A10 is no longer permitted in the current tracking area. It may be the information shown. Further, the 54th identification information may be information indicating that an appropriate cell no longer exists in the current tracking area, or information indicating that roaming is no longer permitted in the current tracking area. .
- the 54th identification information may be information indicating that the SSC mode used by UE_A10 is no longer permitted or information indicating that it is no longer supported. Furthermore, the 54th identification information may be information indicating that the NSI to which UE_A10 is connected is no longer permitted, or information indicating that the network slice type used by UE_A10 is no longer supported.
- UE_A10 may determine whether to ignore the 54th identification information based on the 51st identification information, or determine whether to reattach based on the 54th identification information. May be. For example, when UE_A10 receives information indicating switching from the core network_B190 to another core network and / or switching from the NGS service to the non-NGS service, the UE_A10 may perform reattachment. Further, when the UE_A10 receives the 54th identification information indicating that the use of the NGS service is not permitted in a state where the EPS service is usable, the UE_A10 may not perform reattachment.
- UE_A10 when UE_A10 receives information indicating that the EPS service cannot be used while the NGS service is usable, UE_A10 may not perform reattachment. Furthermore, UE_A10 does not need to perform reattaching, when the information which shows reasons other than these is received.
- the 55th identification information in the present embodiment is information for identifying the NSI to which the UE_A 10 is connected. Further, the 55th identification information may be information such as an NSD ID for identifying NSI and a network slice type ID for identifying the type of network slice. Further, the 55th identification information may be UE usage type or may be a part of UE usage type. Further, the 55th identification information may be an APN. Note that the 55th identification information may be composed of information for identifying a plurality of NSIs. Further, the 55th identification information may include information for identifying NF (Network Function) in the core network_B190. Furthermore, the 55th identification information may be UE registration information.
- NF Network Function
- the 56th identification information in the present embodiment is information for identifying a DCN to which UE_A 10 should connect next and / or connection is permitted.
- the 56th identification information may be a UE usage type, a DCN ID, or other information.
- the 56th identification information may be information indicating the DCN selected by the CPF_A 140 based on mapping information between the NSI and the DCN, or may be information indicating the default DCN.
- the 56th identification information may be transmitted / received in association with 57th identification information described later. That is, information for identifying a DCN and services that can be provided by connecting to the DCN may be transmitted and received in association with each other.
- the 57th identification information in this embodiment is information indicating whether or not each session can be moved to another system. Further, the 57th identification information may be information for identifying a session that can be switched to another system.
- the 57th identification information may be information that identifies a service and / or session that can be moved from NSI to DCN, and / or APN, and may be information that indicates a correspondence between NSI and DCN.
- a plurality of pieces of information for identifying services may be included. That is, the 57th identification information may be an information group for identifying a plurality of services.
- the identification information of each service may be transmitted / received in association with the DCN included in the 56th identification information for each service.
- the 61st identification information in this embodiment is information indicating the type of session that UE_A 10 requests to establish.
- the information indicating the type of session for which UE_A 10 requests establishment may be a request type.
- the 61st identification information may be information indicating that the requested session establishment procedure is an initial establishment procedure, or from other services and / or other access networks and / or other core networks.
- Information indicating a handover procedure or information indicating a session establishment procedure for an emergency call may be used.
- the 61st identification information may be information indicating a handover from the core network_B190 to the core network_A90. Further, the 61st identification information may be information indicating that a session is established in order to switch the session from the core network_B190 to the core network_A90, and the 61st identification information may be used to switch the session from the NGS service to the EPS service. Information indicating establishment may be used.
- the 62nd identification information in the present embodiment is information for identifying a session moving to another system. Further, the 62nd identification information may be information for identifying a session to be switched from the NGS service to the EPS service, or may be information for identifying a session to be switched from the core network_B190 to the core network_A90.
- the 62nd identification information may be information indicating that a PDN connection and / or EPS bearer requesting establishment is established for switching a session from the NGS service and / or the core network_B190.
- the 63rd identification information in the present embodiment is information for identifying an external network such as a DN to which the UE_A 10 requests connection. Further, the 63rd identification information may be an APN. Further, the 63rd identification information may be information composed of a plurality of APNs, or may be information composed of an APN and a DN ID.
- the 63rd identification information may be an APN based on information received by the UE_A 10 during an attach procedure to the core network_B190 and / or a PDU session establishment procedure.
- the 63rd identification information may be an APN corresponding to the DN ID indicated by the 11th identification information or an APN indicated by the 16th identification information.
- the 64th identification information in the present embodiment is information for identifying MME_A40 for which UE_A10 requests connection. Further, the 64th identification information may be information indicating MME_A40 to which UE_A10 is connectable, or may be information identifying MME_A40 to which UE_A10 was previously connected. Further, the 64th identification information may be information for identifying UE_A10. For example, the 64th identification information may be GUTI, IMSI, EPS mobile identity, or other information.
- the 65th identification information in the present embodiment may include information for identifying CPF_A 140 to which UE_A 10 can be connected, or may include information for identifying CPF_A 140 to which UE_A 10 has previously connected. Further, the 65th identification information may be information for identifying UE_A10. For example, the 65th identification information may be CPF ID, GUTI, IMSI, NGS mobile identity, or other information.
- the CPF_A140 may be a common CPF that connects the core network_B190 and the UE_A10 and transmits / receives a control message to / from the UE_A10. In that case, the 65th identification information may include common CPF ID.
- the 66th identification information in this embodiment is information indicating the type of connection service that UE_A 10 requests to use.
- the 66th identification information may be information indicating that the UE_A10 requests use of only the EPS service, or may be information indicating that the UE_A10 requests use of both the EPS service and the non-EPS service. .
- the 66th identification information may be information indicating that the UE_A10 requests the use of the EPS service and the NGS service, or the UE_A10 requests the use of the EPS service, the NGS service, and the non-EPS service. It may be the information shown.
- the 66th identification information may be information indicating the type of attach procedure requested by UE_A10, or may be an attach type.
- the 66th identification information may be information indicating that registration of only the core network_A90 and / or connection is required, registration to both the core network_A90 and the core network_B190, and / or It may be information indicating that a connection is requested.
- the 67th identification information in this embodiment is information indicating the type of connection service that UE_A10 supports use.
- the 67th identification information may be information indicating that UE_A10 supports the use of only EPS services, or information indicating that UE_A10 supports the use of both EPS services and non-EPS services. .
- the 67th identification information may be information indicating that the UE_A10 supports the use of the EPS service and the NGS service, or the UE_A10 supports the use of the EPS service, the NGS service, and the non-EPS service. It may be the information shown.
- the 67th identification information may be capability information of UE_A10 indicating the type of attach procedure supported by UE_A10.
- the 67th identification information may be UE_A10 capability information that supports registration and / or connection only to the core network_A90, and is registered in both the core network_A90 and the core network_B190, and / or Alternatively, it may be UE_A10 capability information that supports connection.
- the 68th identification information in the present embodiment is information for identifying the DCN requested by the UE_A 10 to the core network_A90. Further, the 68th identification information may be UE usage type or DCN ID. Further, the 68th identification information may be information that is acquired in advance from the network and that identifies the DCN to which UE_A 10 should connect next and / or that connection is permitted.
- the 69th identification information in this embodiment is information for identifying the NSI to which the UE_A 10 is connected.
- the 68th identification information may be information such as an NSD ID for identifying NSI and a network slice type ID for identifying the type of network slice.
- the 68th identification information may be a UE usage type or a part of the UE usage type.
- the 68th identification information may be an APN.
- the 66th identification information may be composed of information for identifying a plurality of NSIs.
- the 68th identification information may be configured to include information for identifying an NF (Network Function) in the core network_B190. Further, the 68th identification information may be UE registration information.
- NF Network Function
- the 71st identification information in the present embodiment is information for identifying a session moving to another system. Further, the 71st identification information may be information for identifying a session to be switched from the NGS service to the EPS service, or may be information for identifying a session to be switched from the core network_B190 to the core network_A90.
- the 72nd identification information in this embodiment is reason information (Cause) indicating the reason why the session disconnection procedure is started. Furthermore, the 72nd identification information may be information indicating the reason why the state of the established session is no longer appropriate due to change of subscriber information or the like.
- the 72nd identification information may be information indicating that the service used by UE_A10 has become unavailable due to the operator policy, or the service used by UE_A10 cannot be provided due to lack of network resources. It may be information indicating that Further, the 72nd identification information may be information indicating that an error has occurred in the network, or information indicating that resource is periodically released.
- the 72nd identification information may be information indicating that session re-establishment and / or session re-validation is necessary. Further, the 72nd identification information may be information indicating that the service used by UE_A 10 needs to be switched from the NGS service to the non-NGS service. In other words, the 72nd identification information may be information indicating that the session needs to be switched from the core network_B190 to another core network, or the handover from the core network_B190 to another core network may be performed. It may be information indicating that there is. Another core network may be the core network_A90, or a core network identified by the 73rd identification information.
- the 72nd identification information may be information indicating that the SSC mode used by UE_A10 is no longer permitted or information indicating that it is no longer supported. Furthermore, the 72nd identification information may be information indicating that the NSI to which UE_A10 is connected is no longer permitted, or information indicating that the network slice type used by UE_A10 is no longer supported.
- UE_A 10 may determine whether to re-establish the session based on the 72nd identification information. For example, when UE_A10 receives information indicating switching from the core network_B190 to another core network and / or switching from the NGS service to the non-NGS service, the UE_A10 may reestablish the session. Furthermore, the UE_A 10 may perform session re-establishment when receiving information indicating that session re-establishment and / or session re-validation is necessary. Moreover, UE_A10 does not need to perform re-establishment of a session, when the information which shows reasons other than this is received.
- the 73rd identification information in this embodiment is information indicating a system to be connected when a session is re-established.
- the connected system may be a system that provides an NGS service, a system that provides EPS, or a system that provides a non-EPS service.
- the 73rd identification information may be information indicating a core network to be connected when a session is re-established.
- the 73rd identification information may be information indicating the core network_A90 or information indicating the core network_B190.
- the 73rd identification information may be information indicating the type of control message used when reestablishing a session.
- the 73rd identification information may indicate that the session establishment procedure is executed using the EPS control message after the session disconnection procedure, or the session establishment procedure is executed using the NGS control message. You may show that.
- the 74th identification information in the present embodiment is information indicating whether or not transmission / reception of information indicating a handover is necessary when a session is re-established. Further, the 74th identification information may be information indicating whether or not a session establishment procedure for another core network after the session disconnection procedure is required, or information indicating whether or not it is supported.
- the 74th identification information may be information indicating that the core network_B 190 requests that the UE_A 10 perform the session establishment procedure for another core network after the session disconnection procedure. Further, the 74th identification information may be information indicating that a session establishment procedure after the session disconnection procedure is necessary to switch the session from the core network_B190 to another core network.
- the 75th identification information in this embodiment is information for identifying the NSI to which UE_A 10 is connected. Further, the 75th identification information may be information such as an NSD ID for identifying NSI and a network slice type ID for identifying the type of network slice. Further, the 75th identification information may be UE usage type or may be a part of UE usage type. Further, the 75th identification information may be an APN. Note that the 75th identification information may be composed of information for identifying a plurality of NSIs. The 75th identification information may include information for identifying NF (Network Function) in the core network_B190. Further, the 75th identification information may be UE registration information.
- NF Network Function
- the 76th identification information in the present embodiment is information for identifying a DCN to which UE_A 10 should connect next and / or connection is permitted.
- the 76th identification information may be UE usage type, DCN ID, or other information.
- the 76th identification information may be information indicating the DCN selected by the CPF_A 140 based on the mapping information between the NSI and the DCN, or may be information indicating the default DCN.
- each device executes an initial procedure for the core network_B190, thereby transiting to the first state, and the UE_A10 establishes a session via the core network_B190.
- this procedure refers to an initial procedure for the core network_A90, and each procedure includes an attach procedure, a PDN connection procedure, and a tracking area update procedure. Details of each procedure will be described later.
- each device first executes an attach procedure (S1400) to the core network_B190, and makes a transition to a state in which UE_A10 is connected to the network.
- each device executes a PDU session establishment procedure (S1402), and transitions to the first state (S1404).
- the tracking area update procedure (S1404) may be further executed before the transition to the first state.
- each device may exchange various capability information and / or various request information of each device in the attach procedure to the core network_B190 and / or the PDU session establishment procedure and / or the tracking area update procedure.
- each device when each device exchanges various information and / or negotiates various requests in the attach procedure to the core network_B190, it performs various information exchange and / or various request negotiations in the PDU session establishment procedure. It does not have to be. Conversely, if each device does not exchange various information and / or negotiate various requests in the attach procedure to the core network _B190, it exchanges various information and / or negotiates various requests with the PDU session establishment procedure. May be implemented. Not limited to this, each device exchanges various information and / or negotiates various requests in the core network_B190 attach procedure, and establishes a PDU session for exchanging various information and / or various requests. You may carry out by procedure.
- attachment procedure to the core network _B190, and the PDU session establishment procedure, UE_A10 is the core network _ B 190, may be replaced one or more identification information among the identification information of the first 9, core network _ B 190 receives one or more identification information among the identification information of the first from 9 to UE_A10, be further transmit one or more identification information among the identification information of the 11 from 26 to UE_A10 Good.
- UE_A10 may transmit one or more pieces of identification information among the first to ninth pieces of identification information to core network_A90 by an attach procedure to core network_B190, and may not transmit by a PDU session establishment procedure.
- one or more identification information among the identification information from the core network _ B 190 11th to UE_A10 26, and sends the attach procedure it may not be transmitted in PDU session establishment procedure.
- each device, UE_A10 is the core network _ B 190, one or more identification information among the identification information of the first from 9 without sending the attach procedure to the core network _B190, with PDU session establishment procedure You may send it.
- the core network _ B 190 is to UE_A10, one or more identification information among the identification information of the 11 to 26 without sending the attach procedure to the core network _ B 190, it may be transmitted with PDU session establishment procedure .
- UE_A10 core network _ B 190 among the identification information of the first 9, may send the identification information that is not transmitted in the attachment procedure to the core network _B190 in PDU session establishment procedure.
- the identification information from the core network _ B 190 11th to UE_A10 26 it may send the identification information that is not transmitted in the attachment procedure to the core network _ B 190 in PDU session establishment procedure.
- each device may send and receive during the attach procedure to the core network_B190, and manage in association with a PDU session and / or EPS bearer.
- the PDU session establishment procedure may be used for transmission / reception.
- each device may execute the PDU session establishment procedure in the procedure for attaching to the core network_B190, or may be executed after the procedure for attaching to the core network_B190 is completed.
- the PDU session establishment procedure is executed in the attach procedure to the core network_B190, each device may establish a PDU session based on the completion of the attach procedure to the core network_B190, You may make a transition to the first state.
- each device executes a tracking area update procedure (S1404).
- the tracking area update procedure may be executed at any timing after the transition to the first state after the PDU session is established or after the transition.
- Each device may exchange various request information in the tracking area update procedure.
- UE_A10 may transmit one or more pieces of identification information among the thirty-first to thirty-seventh pieces of identification information to core network_B190.
- the core network_B190 may transmit one or more pieces of identification information among the 41st to 46th and 21st to 26th identification information to the UE_A10.
- Each device involved in this procedure transmits / receives one or more identification information included in each control message by transmitting / receiving each control message described in this procedure, and stores each transmitted / received identification information as a context. May be. Furthermore, each device may transition to an appropriate state based on the completion of this procedure.
- the attach procedure to the core network_B190 is a procedure for connecting to the network (access network and / or core network_B190 and / or PDN_A5) led by the UE_A10. If the UE_A10 is not connected to the core network_B190, this procedure can be executed at any timing such as when the terminal power is turned on. In other words, UE_A10 may start this procedure at an arbitrary timing as long as it is not registered (EMM-DEREGISTERED). In addition, each device may transition to a registration state (EMM-REGISTERED) based on completion of the attach procedure to the core network_B190.
- This procedure is a procedure for each device to establish a PDU session.
- Each device may execute this procedure in a state in which the procedure for attaching to the core network_B190 is completed, or may be executed in the procedure for attaching to the core network_B190.
- each device may start this procedure at an arbitrary timing after the procedure for attaching to the core network_B190.
- 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 transmits a PDU Session Establishment Request message to CPF_A140 via NR node_A122 (S1500), and starts a PDU session establishment procedure.
- the PDU session is a PDN connection
- the PDU session establishment request message may be a PDN connectivity request message.
- the PDU session establishment request message is not limited to this, and may be a message requesting establishment of a PDU session.
- UE_A10 may include at least one piece of identification information from among the first to ninth pieces of identification information in the PDU session establishment request message, and indicates the request of UE_A10 by including these pieces of identification information. May be.
- each device may indicate a connection service requested and / or supported by UE_A 10 by transmitting and receiving the second identification information and / or the third identification information. Furthermore, each device may indicate the service continuation mode when switching to the EPS service that UE_A10 supports and / or requests by transmitting / receiving the fourth identification information and / or the fifth identification information. Good.
- each device may indicate the type of DN requested by UE_A 10 by transmitting and receiving the first identification information and / or the sixth identification information. Further, each device may indicate the NSI for which UE_A 10 requests connection by transmitting and receiving the ninth identification information. Further, each device may indicate MME_A40 or CPF_A140 that UE_A10 requests to connect by including the seventh identification information and / or the eighth identification information.
- each device transmits / receives one or more pieces of identification information among the first to ninth pieces of identification information, so that the PDU session requesting establishment is the same IP address even when switching the connection destination of the PDU session Whether or not it is possible to maintain the connectivity according to may be indicated.
- the switching of the connection destination of the PDU session may be when the PDU session is switched from the NGS service to the EPS service or when the core network_B190 is switched to the core network_A90.
- CPF_A140 receives the PDU session establishment request message and executes the first condition determination.
- the first condition determination is for the CPF_A 140 to determine whether to accept the UE_A10 request.
- the CPF_A 140 determines whether the first condition is true or false.
- CPF_A140 starts the procedure (A) in the procedure when the first condition is true, and starts the procedure (B) in the procedure when the first condition is false. The steps when the first condition is false will be described later.
- CPF_A140 executes the procedure (C) in this procedure and starts the procedure (A) in this procedure. Furthermore, each step of the procedure (C) in this procedure will be explained.
- the CPF_A 140 transmits a session generation request message to the UPGW_A 130, and starts the procedure (C) in this procedure (S1502).
- the CPF_A 140 may include at least one or more pieces of identification information among the first to ninth pieces of identification information in the session generation request message, or may include information indicating whether the request is an initial request. However, the UE_A10 request may be transmitted by including these pieces of identification information.
- UPGW_A130 receives the session generation request message and executes the third condition determination.
- the third condition determination is for determining whether the UPGW_A 130 accepts the UE_A 10 request.
- the third condition is true when the UE_A10 request is accepted, and when the UE_A10 request is permitted.
- the third condition is false when the UE_A10 request is rejected, and may be when the third condition is not determined to be true.
- the third condition determination may be performed by another device (for example, PCRF_A60) instead of UPGW_A130.
- UPGW_A130 performs an IP-CAN session establishment procedure with PCRF_A60. More specifically, UPGW_A 130 transmits a request message during the IP-CAN session establishment procedure to PCRF_A 60. Further, the PCRF_A 60 receives the request message during the IP-CAN session establishment procedure, determines the third condition, and transmits a response message during the IP-CAN session establishment procedure to the UPGW_A 130. Further, UPGW_A 130 receives the response message during the IP-CAN session establishment procedure, and recognizes the result of the third condition determination.
- UPGW_A130 may include at least one piece of identification information from among the first to ninth pieces of identification information in the request message during the IP-CAN session establishment procedure, or by including these pieces of identification information, The UE_A10 request may be transmitted.
- PCRF_A60 may include at least the third information determination result in the response message during the IP-CAN session establishment procedure, and by including this result, the third condition determination result is notified to UPGW_A130. May be.
- the PCRF_A60 may include one or more pieces of identification information among the eleventh to nineteenth pieces of identification information in the response message during the IP-CAN session establishment procedure, and by including these pieces of identification information, the UE_A10's It may indicate that the request has been granted.
- the PCRF_A60 may include one or more pieces of identification information from among the 21st to 26th pieces of identification information in the response message during the IP-CAN session establishment procedure, and by including these pieces of identification information, the UE_A10 It may indicate that the request has been rejected.
- UPGW_A130 may perform the third condition determination based on the result of the third condition determination received from PCRF_A60. For example, when the PCRF_A60 accepts the UE_A10 request, the PCRF_A60 and UPGW_A130 may set the third condition to be true. When the PCRF_A60 rejects the UE_A10 request, the PCRF_A60 and the UPGW_A130 may set the third condition to be false.
- UPGW_A 130 determines whether the third condition is true or false. If the third condition is true, UPGW_A 130 transmits a session creation response message to CPF_A 140 (S1506). Furthermore, CPF_A140 receives the session creation response message.
- UPGW_A130 may include one or more pieces of identification information among eleventh to nineteenth pieces of identification information, an IP address, or include these pieces of identification information in the session generation response message.
- the UE_A10 request may be permitted.
- UPGW_A 130 transmits a session creation rejection message to CPF_A 140 (S1508).
- the session creation rejection message may be a session creation response message including a rejection reason (Reject cause).
- UPGW_A130 may include one or more pieces of identification information among the 21st to 26th pieces of identification information in the session generation rejection message, and by including these pieces of identification information, it is confirmed that the request of UE_A10 has been rejected. May be shown.
- Each device completes the procedure (C) in this procedure based on transmission / reception of a session creation response message and / or a session creation rejection message.
- CPF_A140 Based on the reception of the session generation response message, CPF_A140 transmits a PDU session establishment acceptance (PDU122session acceptment accept) message to NR node_A122 (S1514).
- PDU session establishment acceptance PDU122session acceptment accept
- CPF_A140 may start the procedure (B) in this procedure without continuing the procedure (A) in this procedure.
- the PDU session establishment acceptance message may be a PDN connection acceptance (PDNPDConnectivity Accept) message or a default EPS bearer context activation request (Activate default EPSbearer context request) message.
- the PDU session establishment acceptance message may be a response message to the PDU session establishment request message, and is not limited to this, and may be a message for accepting a PDU session establishment request.
- NR node_A122 receives the PDU session establishment acceptance message and receives an RRC message (for example, an RRC message such as an RRC Connection Reconfiguration message, an RRC ConnectionSetup message, or an RRC Direct Transfer message) and / or a PDU session establishment acceptance message. Is transmitted (S1516).
- the PDU session establishment acceptance message may be transmitted / received by being included in the RRC message.
- the CPF_A 140 may include at least one or more pieces of identification information among eleventh to nineteenth identification information, an IP address, or these identification information in the PDU session establishment acceptance message. By including, it may indicate that the request of UE_A10 has been accepted.
- each device may indicate a connection service that is permitted and / or supported by the network by transmitting and receiving the twelfth identification information and / or the thirteenth identification information. Furthermore, each device may indicate the service continuation mode when switching to the EPS service that is supported and / or permitted by the network by transmitting and receiving the 14th identification information and / or the 15th identification information. Good.
- each device may indicate the type of DN permitted by the network by transmitting and receiving the eleventh identification information and / or the sixteenth identification information. Further, each device may indicate the NSI that the network permits connection by transmitting and receiving the 19th identification information. Furthermore, each device may indicate MME_A40 or CPF_A140 that the network permits connection by transmitting and receiving the 17th identification information and / or the 18th identification information.
- each device may indicate the reason why the request of UE_A 10 is accepted by transmitting / receiving one or more pieces of identification information among the eleventh to nineteenth identification information. Furthermore, each device may indicate processing to be performed by each device after this procedure based on the reason that the request of UE_A10 has been accepted, may perform this procedure again, or may have other conditions. You may carry out this procedure. For example, the UE_A 10 may execute connection to the core network_A 90 and / or switching of the EPS service based on processing to be performed by each device included in the reason that the PDU session establishment procedure is accepted.
- each device transmits / receives one or more pieces of identification information among the eleventh to nineteenth identification information, so that the established PDU session has the same IP address even when the connection destination of the PDU session is switched. It may indicate whether or not connectivity can be maintained.
- UE_A10 When receiving the RRC message, UE_A10 transmits an RRC message (for example, an RRC message such as an RRC Connection Connection Reconfiguration Complete message, an RRC Connection Connection Setup Complete message, or an RRCDirect Transfer message) to the NR node_A122 (S1518).
- RRC message for example, an RRC message such as an RRC Connection Connection Reconfiguration Complete message, an RRC Connection Connection Setup Complete message, or an RRCDirect Transfer message
- the NRnode_A122 receives the RRC message and transmits a bearer setting message to the CPF_A140 (S1520). Furthermore, CPF_A140 receives a bearer setting message.
- UE_A10 transmits a PDU session establishment completion (PDU session establishmentcomplete) message to CPF_A140 via NR node_A122 (S1522) (S1524). Further, the CPF_A 140 receives the PDU session establishment completion message and executes the second condition determination.
- the PDU session is a PDN connection
- the PDU session establishment completion message may be a PDN connection completion (PDN Connectivity complete) message or a default EPS bearer context activation acceptance (Activate default EPSbearer context accept) message.
- 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.
- the second condition determination is for CPF_A140 to determine whether or not it is necessary to request UPGW_A130 to change the bearer. If the second condition is true, CPF_A140 starts the procedure (D) in this procedure. When the second condition determination is false, CPF_A140 does not execute the procedure (D) in this procedure. Hereinafter, each step of the procedure (D) in this procedure will be described.
- the CPF_A 140 transmits a bearer change request message to the SGW_A 35 (S1526), and starts the procedure (D) in this procedure. Furthermore, SGW_A35 receives the bearer change request message and transmits a bearer change response message to CPF_A140 (S1528).
- CPF_A140 receives the bearer change response message and completes the procedure (D) of this procedure.
- each device is based on the transmission / reception of a PDU session establishment completion message when the second condition determination is false, and / or when the second condition determination is true, Based on this, complete the procedure (A) in this procedure.
- CPF_A140 transmits a PDU session establishment rejection (PDU session establishmentreject) message to UE_A10 via NR node_A122 (S1530), and starts the procedure (B) in this procedure. Furthermore, UE_A10 receives the PDU session establishment rejection message and recognizes that the request for UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission / reception of the PDU session establishment rejection message.
- the PDU session establishment rejection message may include an appropriate rejection reason. If the PDU session is a PDN connection, the PDU session establishment rejection message may be a PDN connection rejection (PDN Connectivity reject) message. Further, the PDU session establishment rejection message may be a response message to the PDU session establishment request message, and is not limited thereto, and may be a message that rejects the request for PDU session establishment.
- PDN Connectivity reject PDN connection rejection
- CPF_A140 may include one or more pieces of identification information among the 21st to 26th pieces of identification information in the PDU session establishment rejection message. By including these pieces of identification information, the UE_A10 request is rejected. You may show things.
- each device may indicate the reason why the PDU session establishment procedure is rejected by transmitting and receiving the 21st identification information, and the processing to be performed by each device after the attach procedure to the core network_B190 May be indicated.
- each device transmits / receives the 22nd identification information and / or the 23rd identification information, so that the network supports connection to the core network_A90 and / or switching of the EPS service, and / or It may indicate that permission is not allowed. Furthermore, each device may indicate the service continuation mode when switching to the EPS service, which is not supported and / or permitted by the network, by transmitting / receiving the 24th identification information and / or the 25th identification information. Good. Furthermore, each device may indicate an NSI that the network does not permit to connect by transmitting and receiving the 26th identification information.
- 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. The user may recognize that this procedure has been rejected, or may transition to a state where a PDU session is not established.
- 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 transmitting or receiving one or more pieces of identification information among the 21st to 26th pieces of identification information, each device may recognize the reason why the UE_A10 request is rejected. Furthermore, each apparatus may perform this procedure again based on the reason why the request of UE_A10 is rejected, or may perform this procedure under different conditions. For example, the UE_A 10 may execute connection to the core network_A 90 and / or switching of the EPS service based on processing to be performed by each device included in the reason that the PDU session establishment procedure is accepted.
- the first to third condition determinations described above may be executed based on identification information and / or subscriber information and / or operator policy included in the PDU session establishment request message. Further, the condition for determining whether the first to third conditions are true or false is not limited to the above-described conditions.
- the first condition and / or the third condition may be true when the UE_A 10 requests session establishment and the network permits the request. Further, the first condition and / or the third condition may be false when the UE_A 10 requests establishment of a session and the network does not permit the request. Furthermore, the first condition and / or the third condition may be false when the network to which the UE_A 10 is connected and / or the device in the network does not support the establishment of the session requested by the UE_A 10.
- UE_A10 may transmit the PDU session establishment request message described above in the attach request message, or by including the PDU session establishment request message, the UE_A10 performs the PDU session establishment procedure during the attach procedure to the core network_B190. You may require that you do it.
- UE_A10 may include at least one piece of identification information among the first to ninth pieces of identification information in the attach request message, or may indicate the request of UE_A10 by including these pieces of identification information. Good.
- each device may indicate a connection service requested and / or supported by UE_A10 by transmitting and receiving the second identification information and / or the third identification information.
- the service continuation mode when switching to the EPS service which is supported and / or requested by the UE_A 10, may be indicated.
- each device may indicate the type of DN requested by UE_A 10 by transmitting and receiving the first identification information and / or the sixth identification information. Further, each device may indicate the NSI for which UE_A 10 requests connection by transmitting and receiving the ninth identification information. Further, each device may indicate MME_A40 or CPF_A140 that UE_A10 requests to connect by including the seventh identification information and / or the eighth identification information.
- each device transmits / receives one or more pieces of identification information among the first to ninth pieces of identification information, so that the PDU session requesting establishment is the same IP address even when switching the connection destination of the PDU session Whether or not it is possible to maintain the connectivity according to may be indicated.
- UE_A 10 may transmit the identification information included in a control message different from the attach request message.
- the CPF_A 140 receives the control message different from the attach request message and / or the attach request message, and executes the first condition determination. CPF_A140 starts the procedure (A) in the procedure when the first condition is true, and starts the procedure (B) in the procedure when the first condition is false.
- CPF_A140 executes the fourth condition determination and starts the procedure (A) in this procedure.
- the CPF_A 140 determines whether the fourth condition is true or false.
- the CPF_A 140 executes the procedure (C) in the UE-driven PDU session establishment procedure by starting when the fourth condition is true, and omits it when the fourth condition is false (S1604 ).
- the CPF_A 140 transmits an attach accept message to the NR node_A 122 based on reception of the attach request message and / or session creation response message and / or completion of the procedure (C) during the PDN connection procedure. (S1606).
- CPF_A140 may start the procedure (B) in this procedure without continuing the procedure (A) in this procedure.
- the NR node_A122 receives the attach acceptance message, and transmits an RRC message (for example, an RRC message such as an RRCConnection Reconfiguration message, an RRC Connection Setup message, or an RRC Direct Transfer message) and / or an attach acceptance message (S1608). ).
- the attach acceptance message may be transmitted and received by being included in the RRC message.
- CPF_A140 may transmit the attach acceptance message including the above-described PDU session establishment acceptance message, or by including the PDU session establishment acceptance message, May indicate that has been accepted.
- the CPF_A 140 may include at least one or more identification information among the eleventh to nineteenth identification information, an IP address, or include these identification information in the attach acceptance message. Then, it may indicate that the request of UE_A10 has been accepted.
- each device may indicate a connection service that is permitted and / or supported by the network by transmitting and receiving the twelfth identification information and / or the thirteenth identification information. Furthermore, each device may indicate the service continuation mode when switching to the EPS service that is supported and / or permitted by the network by transmitting and receiving the 14th identification information and / or the 15th identification information. Good.
- each device may indicate the type of DN permitted by the network by transmitting and receiving the eleventh identification information and / or the sixteenth identification information. Further, each device may indicate the NSI that the network permits connection by transmitting and receiving the 19th identification information. Furthermore, each device may indicate MME_A40 or CPF_A140 that the network permits connection by including the 17th identification information and / or the 18th identification information.
- each device may indicate the reason why the request of UE_A10 is accepted by transmitting / receiving one or more pieces of identification information among the eleventh to nineteenth identification information. Furthermore, each device may indicate processing to be performed by each device after this procedure based on the reason that the request of UE_A10 has been accepted, may perform this procedure again, or may have other conditions. You may carry out this procedure. For example, the UE_A10 executes connection to the core network_A90 and / or switching of the EPS service based on processing to be performed by each device included in the reason that the attachment procedure to the core network_B190 is accepted. Also good.
- each device transmits / receives one or more pieces of identification information among the eleventh to nineteenth identification information, so that the established PDU session has the same IP address even when the connection destination of the PDU session is switched. It may indicate whether or not connectivity can be maintained.
- the first condition determination may be the same as the first condition determination during the PDU session establishment procedure.
- the fourth condition determination is for determining whether the CPF_A 140 performs the PDU session establishment procedure.
- the fourth condition is true when a PDU session establishment request message is received, and may be when the PDU session establishment procedure is also executed during this procedure.
- the fourth condition is false when the PDU session establishment request message has not been received.
- the PDU session establishment procedure may not be executed during this procedure, and the fourth condition is not judged to be true. In case.
- UE_A10 When UE_A10 receives an RRC message from NR node_A122, UE_A10 sends an RRC connection message (for example, an RRC message such as RRCRRConnection Reconfiguration Complete message, RRC Connection Setup Complete message, or RRCDirect Transfer message) to NR ⁇ node_A122 (S1610).
- RRC connection message for example, an RRC message such as RRCRRConnection Reconfiguration Complete message, RRC Connection Setup Complete message, or RRCDirect Transfer message
- the NRnode_A122 receives the RRC message and transmits a bearer setting message to the CPF_A140 (S1612). Furthermore, CPF_A140 receives a bearer setting message.
- UE_A10 When UE_A10 receives an attach acceptance message from CPF_A140 via NR node_A122, UE_A10 transmits an attach complete (Attach complete) message to CPF_A140 via NR node_A122 (S1614) (S1616). Furthermore, CPF_A140 receives the attach completion message. Further, when the fourth condition is true, the CPF_A 140 executes the second condition determination. The second condition determination is for determining whether or not the CPF_A 140 needs to request the UPGW_A 130 to change the bearer. If the second condition is true, the CPF_A 140 starts and executes the procedure (D) in the PDU session establishment procedure (S1618). Each device completes the procedure (A) in this procedure based on the transmission / reception of the attach completion message and / or the completion of the procedure (D) in the PDU session establishment procedure.
- the UE_A10 may transmit the PDU session establishment completion message by including the PDU session establishment completion message described above in the attach completion message. It may indicate that the procedure is complete.
- the CPF_A 140 transmits an attach rejection message to the UE_A 10 via the NR node_A 122 and starts the procedure (B) in this procedure (S1620). Further, UE_A10 receives the attach rejection message and recognizes that the request of UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission / reception of the attach rejection message.
- CPF_A140 may transmit the attach refusal message including the PDU session establishment rejection message described above, or by including the PDU session establishment rejection message, May indicate that was rejected. In that case, UE_A10 may further receive a PDU session establishment rejection message or may authenticate that the PDU session establishment procedure has been rejected.
- the CPF_A140 may include one or more pieces of identification information among the 21st to 26th pieces of identification information in the attach rejection message, and by including these pieces of identification information, the fact that the request of UE_A10 has been rejected. It may be shown.
- each device may recognize the reason why the attach procedure to the core network_B190 is rejected by transmitting / receiving one or more pieces of identification information among the 21st to 26th identification information, or the core network After the attach procedure to _B190, the processing to be performed by each device may be indicated, the present procedure may be performed again, or the present procedure may be performed under different conditions. For example, UE_A10 performs connection to core network_A90 and / or switching of EPS service based on processing to be performed by each device included in the reason why the attachment procedure to core network_B190 is rejected. Also good.
- each device may indicate the reason why the PDN connection procedure is rejected by transmitting and receiving the 21st identification information, and after each attach procedure to the core network_A90, each device performs processing to be performed. May be shown. Furthermore, each device transmits / receives the 22nd identification information and / or the 23rd identification information, so that the network supports connection to the core network_A90 and / or switching of the EPS service, and / or It may indicate that permission is not allowed.
- each device may indicate the service continuation mode when switching to the EPS service, which is not supported and / or permitted by the network, by transmitting / receiving the 24th identification information and / or the 25th identification information. Good. Furthermore, each device may indicate a DCN that the network does not permit to connect by transmitting and receiving the 26th identification information.
- 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 UE_A10 is connected to the network and / or the registration state based on the completion of the procedure (A) in this procedure, or the procedure (B) in this procedure. Based on the completion of the above, it may be recognized that the present procedure has been rejected, or a transition to a state in which it cannot be connected to the network may be made.
- 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 transmitting or receiving one or more pieces of identification information among the 21st to 25th pieces of identification information, each device may recognize the reason why the UE_A10 request is rejected. Furthermore, each device may perform this procedure again based on the reason that the UE_A10 request is rejected, or perform an attach procedure to the core network_B190 for the core network_A90 or another cell. May be.
- first to fourth condition determinations described above may be executed based on identification information and / or subscriber information and / or operator policy included in the attach request message.
- condition for determining whether the first to fourth conditions are true or false is not limited to the above-described conditions.
- the first condition determination and / or the third condition determination may be the same as the above-described PDU session establishment procedure example.
- This procedure updates the location registration information of UE_A10 in the network (access network and / or core network_B190) and / or periodically notifies UE_A10 of the status of UE_A10 from the UE_A10 and / or This is a procedure for updating specific parameters related to UE_A10 in the network.
- UE_A10 can execute this procedure at an arbitrary timing as long as the PDU session is established. Moreover, UE_A10 can perform this procedure regularly.
- UE_A10 transmits a tracking area update request message to CPF_A140 via NR node_A122 (S1700), and starts a tracking area update procedure.
- UE_A10 may include at least one piece of identification information from among the thirty-first to thirty-seventh pieces of identification information in the tracking area update request message, and indicates the request of UE_A10 by including these pieces of identification information. Also good.
- each device may indicate a connection service supported by UE_A10 by transmitting and receiving the 32nd identification information. Furthermore, each device may indicate the service continuation mode when switching to the EPS service, which is supported and / or requested by UE_A10, by transmitting and receiving the 35th identification information and / or the 36th identification information. Good.
- each device may indicate the NSI that UE_A 10 requests to connect by transmitting and receiving the 37th identification information. Furthermore, each device may indicate a connection service to which UE_A 10 requests to update registration information by transmitting and receiving thirty-first identification information. Further, each device may indicate MME_A40 or CPF_A140 that UE_A10 requests connection by including the 33rd identification information and / or the 34th identification information.
- CPF_A140 receives the tracking area update request message and executes the first condition determination. In the first condition determination, the CPF_A 140 determines whether the first condition is true or false. CPF_A140 starts the procedure (A) in the procedure when the first condition is true, and starts the procedure (B) in the procedure when the first condition is false. The steps when the first condition is false will be described later.
- CPF_A140 executes the fourth condition determination and starts the procedure (A) in this procedure.
- the CPF_A 140 determines whether the fourth condition is true or false.
- the CPF_A 140 starts the procedure (C) in this procedure when the fourth condition is true, and omits the procedure when the fourth condition is false (S1703).
- the first condition determination may be the same as the first condition determination during the attach procedure to the core network_B190.
- the fourth condition determination is for determining whether or not a PDU session change and / or addition and / or deletion procedure is necessary.
- CPF_A140 may include at least one or more of the identification information of the thirty-first to thirty-seventh identification information in the message in the procedure (C) in this procedure, or include these identification information.
- the request for UE_A10 may be transmitted to each device.
- CPF_A140 executes the third condition determination after the procedure (C) is completed.
- the third condition determination is for determining whether CPF_A140 accepts the UE_A10 request, and the third condition determination is received from any device during the procedure of (C). It may be determined based on the information.
- CPF_A 140 determines whether the third condition is true or false.
- CPF_A140 sends the tracking area update acceptance (Tracking Area Update accept) message to UE_A10 via NR node_A122 if the third condition is true (S1706). If condition 3 is false, start the procedure (B) in this procedure.
- the tracking area update acceptance message may include an appropriate reason for acceptance.
- the tracking area update acceptance message may be a response message to the tracking area update request message, and is not limited to this, and may be a message for accepting a tracking area update request.
- the CPF_A140 may include at least one of the identification information items 41 to 47 in the tracking area update acceptance message, or the UE_A10 request is accepted by including these identification information items. You may show that it was done.
- each device transmits / receives the 43rd identification information and / or the 44th identification information, so that the network supports connection to the core network_A90 and / or switching of the EPS service, and / or It may indicate whether to allow or not. Furthermore, each device may indicate the service continuation mode when switching to the EPS service, which is supported and / or permitted by the network, by transmitting and receiving the 45th identification information and / or the 46th identification information. Good.
- each device may indicate the NSI that the network permits connection by transmitting and receiving the 47th identification information.
- each device may indicate the reason why the UE request is accepted by transmitting / receiving one or more pieces of identification information among the 41st to 47th identification information. Furthermore, each device may indicate processing to be performed by each device after this procedure based on the reason that the request of UE_A10 has been accepted, may perform this procedure again, or may have other conditions. You may carry out this procedure. For example, the UE_A 10 may perform connection to the core network_A 90 and / or switching of the EPS service based on processing to be performed by each device included in the reason why the tracking area update procedure is accepted.
- UE_A10 When receiving the tracking area update acceptance message, UE_A10 transmits a tracking area update completion (Tracking Area Update) message to CPF_A140 via NRnode_A122 (S1710). Each device completes the procedure (A) in this procedure based on the transmission / reception of the tracking area update completion message.
- Track Area Update Tracking Area Update
- the CPF_A 140 transmits a tracking area update rejection (Tracking Area Update reject) message to the UE_A10 via the NR node_A122. Furthermore, UE_A10 receives the tracking area update rejection message and recognizes that the request of UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission / reception of the tracking area update rejection message.
- the tracking area update rejection message may include an appropriate reason for rejection.
- the tracking area update rejection message may be a response message to the tracking area update request message, and is not limited to this, and may be a message rejecting the tracking area update request.
- the CPF_A140 may include one or more pieces of identification information among the 21st to 26th pieces of identification information in the tracking area update rejection message. By including these pieces of identification information, the UE_A10 request is rejected. You may show that
- each device may indicate the reason why the tracking area update procedure is rejected by transmitting / receiving the 21st identification information, or may indicate the processing to be performed by each device after the tracking area update procedure. Good.
- each device transmits / receives the 22nd identification information and / or the 23rd identification information, so that the network supports connection to the core network_A90 and / or switching of the EPS service, and / or It may indicate that permission is not allowed. Furthermore, each device may indicate the service continuation mode when switching to the EPS service, which is not supported and / or permitted by the network, by transmitting / receiving the 24th identification information and / or the 25th identification information. Good. Furthermore, each device may indicate a DCN that the network does not permit to connect by transmitting and receiving the 26th identification information.
- Each device completes this procedure based on the completion of the procedure (A) or (B) in this procedure.
- 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 each device transmits or receives one or more pieces of identification information among the 21st to 26th pieces of identification information, the device may indicate the reason why the request of UE_A10 is rejected. Furthermore, each device may indicate the processing to be performed by each device based on the reason that the UE_A10 request is rejected, may perform this procedure again, or may perform this procedure under different conditions. You may implement. For example, the UE_A 10 may perform connection to the core network_A 90 and / or switching of the EPS service based on processing to be performed by each device included in the reason why the tracking area update procedure is rejected.
- first and / or third and / or fourth condition determination is executed based on identification information and / or subscriber information and / or operator policy included in the tracking area update request message. May be. Further, the condition for determining the truth of the first and / or the third and / or the fourth condition may not be limited to the above-described conditions.
- the first condition and / or the third condition and / or the fourth condition may be true when the UE_A 10 requests a tracking area update and the network permits the request. Further, the first condition and / or the third condition and / or the fourth condition may be false when the UE_A 10 requests the tracking area update and the network does not permit the request. Furthermore, the first condition, and / or the second condition, and / or the third condition, supports a tracking area update requested by UE_A10 by a network to which UE_A10 is connected and / or a device in the network. If not, it can be false.
- the reconnection procedure is a procedure until the connection is temporarily disconnected and the connection is established again.
- a procedure for switching a PDU session connected to the core network_B190 to a PDN connection connected to the core network_A90 will be described.
- this procedure may be a procedure for making a transition from a state connected to the core network_A90 to a state connected to the core network_B190.
- two reconnection procedures will be described.
- the first reconnection procedure and the second reconnection procedure will be described.
- a first reconnection procedure in the present embodiment will be described with reference to FIG.
- this procedure refers to the first reconnection procedure, and each procedure includes a detach procedure, an attach procedure to the core network_A90, and a PDN connection procedure. Details of each procedure will be described later.
- each device transits to a first state connected to the core network_B190 (S1800).
- This procedure is for network-led transition from the state where UE_A10 is registered in core network_B190 to the state registered in core network_A90. This is a procedure for changing and / or switching connection service. Further, according to this procedure, the UE_A 10 may maintain the IP address even if the core network to be accessed or the connection service to be used is changed.
- the procedure for transitioning to the first state may be the initial procedure described in Chapter 1.3.
- each device executes a detach procedure (S1802), and makes a transition to a state in which UE_A10 is not connected to the core network_B190. Subsequently, each device executes a procedure for attaching to the core network_A90 (S1804), and transitions to a state in which the UE_A10 is connected to the core network_A90.
- the attach to the core network_A90 is an attach procedure to the core network_A90.
- each device may execute a PDN connection procedure (PDN Connectivity procedure) (S1806).
- PDN Connectivity procedure PDN connection procedure
- Each device may exchange various capability information and / or various request information of each device in the detach procedure and / or the attach procedure to the core network_A90 and / or the PDN connection procedure.
- UE_A10 may transmit at least one piece of identification information among at least the 51st to 57th pieces of identification information to core network_B190 in the detach procedure.
- each device When each device exchanges various information and / or negotiates various requests with the attach procedure to the core network_A90, it does not exchange various information and / or negotiates various requests with the PDN connection procedure. May be. Conversely, if each device does not exchange various information and / or negotiate various requests in the attach procedure to the core network_A90, it exchanges various information and / or negotiates various requests using the PDN connection procedure. You may implement. Not limited to this, each device exchanges various information and / or negotiates various requests with the procedure for attaching to the core network_A90, but also exchanges various information and / or negotiates various requests with the PDN connection procedure. May be implemented.
- UE_A10 may transmit one or more pieces of identification information among at least the 61st to 68th pieces of identification information to core network_B190, and core network_A90 may transmit from UE_A10.
- core network_A90 may transmit from UE_A10.
- at least one of the 61st to 68th identification information may be received, and at least one of the 19th and 26th identification information may be transmitted to UE_A10.
- UE_A10 may send at least one piece of identification information from among the 61st to 66th pieces of identification information to the core network_A90 by an attach procedure, and may not send it by a PDN connection procedure.
- the core network_A90 may transmit at least one or more of the 19th and 26th identification information to the UE_A10 by the attach procedure and not by the PDN connection procedure.
- UE_A 10 may transmit at least one piece of identification information from among the 61st to 66th pieces of identification information to core network_A 90 in the PDN connection procedure without transmitting it in the attach procedure.
- the core network_A90 may transmit at least the 19th and 26th identification information in the PDN connection procedure instead of transmitting in the attach procedure.
- UE_A10 may transmit identification information that has not been transmitted to the core network_A90 in the procedure for attaching to the core network_A90 among the 61st to 66th identification information by the PDN connection procedure.
- the core network_A90 may transmit, to the UE_A10, identification information that has not been transmitted in the attach procedure to the core network_A90 among the 19th and 26th identification information by the PDN connection procedure.
- Each device involved in this procedure transmits / receives one or more identification information included in each control message by transmitting / receiving each control message described in this procedure, and stores each transmitted / received identification information as a context. May be. Furthermore, each device may transition to an appropriate state based on the completion of this procedure.
- the core network_B190 is a procedure for cutting the connection between the UE_A10 and the network (access network and / or core network_B190, and / or PDN_A5). That is, if the UE_A10 is in the first state connected to the core network_B190, the core network_B190 can start this procedure at an arbitrary timing. In other words, if the UE_A10 is registered in the core network_B190 (EMM-REGISTERD), the core network_B190 may start this procedure at an arbitrary timing. Further, each device may transition to a state (UEM-DEREGISTERD) in which UE_A10 is not registered in the core network_B190 based on completion of the detachment procedure.
- EMM-REGISTERD a state in which UE_A10 is not registered in the core network_B190 based on completion of the detachment procedure.
- CPF_A 140 transmits a detach request message to UE_A 10 via NR node_A 122 (S1900), and starts a detach procedure.
- the trigger for the CPF_A140 to start the detach procedure is based on the fact that the device in the core network_B190 has determined that the UE_A10 cannot provide connectivity to the UE_A10 from the location information of the UE_A10. May be.
- the CPF_A 140 may start the detach procedure based on the change of the operator policy or the change of the subscriber information of the UE_A 10.
- the CPF_A 140 may start a detach procedure based on a request from an upper layer or an application server. Note that the trigger for the CPF_A 140 to start the detach procedure is not limited to these.
- CPF_A140 may include at least one piece of identification information among at least the 51st to 57th pieces of identification information in the detach request message. By including these pieces of identification information in the detach request message, CPF_A140 may indicate a request to UE_A10. In other words, the CPF_A 140 may indicate that the UE_A 10 is requested to have the characteristics or contents represented by each of the identification information described above by including these pieces of identification information.
- CPF_A140 is based on transmitting at least one or more of the 11th to 18th identification information to UE_A10 in the attach procedure to core network_B190 and / or the PDU session establishment procedure, at least.
- One or more pieces of identification information among the 51st to 57th pieces of identification information may be included in the detach request message.
- CPF_A140 identifies at least the 51st to 57th when permitting service continuation to continue communication through the attach procedure to the core network_A90 associated with the detach procedure and / or the PDN connection procedure associated with the detach procedure.
- One or more pieces of identification information may be included in the detach request message.
- this service continuation permission information may be managed as subscriber information for UE_A10. Therefore, CPF_A140 may include such identification information based on the subscriber information of UE_A10.
- the 52nd identification information is included in the detach request message. It may be determined that the information is not included in the detach request message.
- the 53rd identification information may be included in the detach request message. Otherwise, the 53rd identification information indicating NGC may be included in the detach request message, or it may be determined that the 53rd identification information is not included in the detach request message.
- CPF_A140 may request UE_A10 whether to start the attach procedure again by transmitting the 51st identification information. Further, UE_A10 may determine whether or not to start the attach procedure again based on the received 51st identification information.
- the CPF_A 140 may notify the UE_A 10 of the NSI identification information to be detached by the UE_A 10 by transmitting the 55th identification information. Further, UE_A10 may hold information for identifying the NSI to be detached by UE_A10 by receiving the 55th identification information.
- the CPF_A 140 may request the reattach procedure to the DCN and / or the PDN connection procedure indicated by the 56th identification information by transmitting the 56th identification information. Further, the UE_A 10 may determine to execute the reattach procedure to the DCN and / or the PDN connection procedure indicated by the 56th identification information by receiving the 56th identification information.
- the reattach procedure may be an attach procedure to the core network_A90 that starts based on completion of the detach procedure. Furthermore, reattaching may indicate that an attach procedure to the core network_A90 to be started is executed based on completion of the detach procedure.
- each device transmits / receives the 57th identification information, and after the completion of the detach procedure, the device is associated with the service that cannot be maintained and / or the service that cannot be maintained by the attach procedure and / or the PDN connection procedure that is executed again.
- NSI may be indicated.
- the CPF_A 140 may request that one or more services be continued by the reattach procedure and / or the PDN connection procedure by transmitting the 57th identification information. Further, the UE_A10 receives the 57th identification information, and decides to continue the one or more services indicated by the 57th identification information by executing the reattach procedure and / or the PDN connection procedure. May be.
- the service identification information and the DCN that performs the reattach procedure and / or the PDN connection procedure may be associated with each other and transmitted / received. Furthermore, when a plurality of service information is transmitted, different DCNs may be transmitted / received in association with each service. These one or more DCNs may be the 56th identification information described above.
- / or CPF_A140 may notify that one or more services cannot be continued by the reattach procedure and / or the PDN connection procedure by transmitting the 57th identification information. Further, UE_A10 may determine that one or more services cannot be continued by the reattach procedure and / or the PDN connection procedure by receiving the 57th identification information.
- each device may indicate whether or not to use a flag indicating handover during the attach procedure executed again after the completion of the detach procedure by transmitting and receiving the 52nd identification information.
- the CPF_A 140 transmits the 52nd identification information to start the core based on completion of the detachment procedure.
- the UE_A 10 may request to transmit a flag indicating handover.
- UE_A10 receives the 52nd identification information, and UE_A10 transmits a flag indicating handover in the attach procedure and / or PDN connection procedure to core network_A90 that starts based on the completion of the detachment procedure. You may decide that.
- the CPF_A 140 transmits the 52nd identification information, so that the core is executed based on the completion of the detachment procedure.
- the attach procedure to the network_A90 and / or the PDN connection procedure it may be notified that the flag indicating the handover by the UE_A10 does not need to be transmitted.
- UE_A10 does not transmit a flag indicating handover in the attach procedure and / or PDN connection procedure to core network_A90 that starts based on the completion of the detachment procedure by receiving the 52nd identification information. You may decide that.
- the information indicating the handover may be the 61st identification information or the identification information requesting the IP address reservation.
- the IP address preservation may be to establish connectivity with the same IP address as the IP address used before switching after performing the attach procedure and / or the PDN connection procedure again.
- IP address preservation may mean that the IP address used after re-executing the attach procedure and / or the PDN connection procedure is the same as the IP address used before the switching.
- each device may indicate the core network to which UE_A 10 should establish a connection after the completion of the detachment procedure by transmitting and receiving the 53rd identification information.
- the CPF_A 140 may notify the type of the core network to which the UE_A 10 should establish a connection after the completion of the detach procedure by transmitting the 53rd identification information.
- UE_A10 may determine the type of core network to which UE_A10 should establish a connection after the completion of the detachment procedure by receiving the 53rd identification information.
- each device may indicate the reason for executing the detach procedure (Cause) by transmitting and receiving the 54th identification information.
- CPF_A140 may include at least one or more pieces of identification information among the identification information items 51 to 57 in the session deletion request message.
- CPF_A140 may transmit a request to UE_A10 by including these pieces of identification information in the session deletion request message.
- each device transmits and receives the 51st identification information and / or the 52nd identification information and / or the 54th identification information, so that the IP corresponding to the PDU session is switched when the connection destination of the PDU session is switched. It may indicate that connectivity by address can be maintained or may be required to be maintained.
- each device transmits and receives the 51st identification information and / or the 52nd identification information and / or the 54th identification information, and after the detachment procedure is completed, the PDU session is disconnected. It may indicate that a PDN connection associated with the same IP address can be established or may require that it be established.
- the 51st to 57th identification information may be transmitted and received as a single identification information by combining two or more pieces of identification information.
- the combined identification information may be identification information having the meaning of each combination of identification information.
- CPF_A140 transmits a delete session request (Delete Session Request) message to UPGW_A130 (S1902), and starts the procedure (A) in this procedure.
- Delete Session Request Delete Session Request
- S1902 UPGW_A130
- each device may include one or more pieces of identification information among the 51st to 57th pieces of identification information in the session deletion request message.
- CPF_A140 may include at least one or more pieces of identification information among the identification information items 51 to 57 in the session deletion request message.
- CPF_A140 may transmit a request to UE_A10 by including these pieces of identification information in the session deletion request message.
- UPGW_A130 receives the session deletion request message. Based on the reception of the session deletion request message, UPGW_A 130 transmits a session deletion response message to CPF_A 140 (S1908). If UPGW_A130 is not connected to an external gateway (PGW_A30 or SCEF_A46) and / or is not configured as the same device, UPGW_A130 sends a session deletion request message to the external gateway based on the reception of the session deletion request message. The session deletion response message transmitted by the external gateway may be received. Each device completes the procedure (A) in this procedure based on the transmission / reception of the session deletion response message.
- UE_A10 may receive a detach request message and transmit a detach accept message to CPF_A 140 at an arbitrary timing (S1914).
- the UE_A 10 may include identification information such as a detach type for identifying the type of detachment in the detach acceptance message, or may indicate that the request is permitted by including these identification information.
- CPF_A140 receives a detach acceptance message from UE_A10.
- the CPF_A 140 may execute a procedure for deleting the signaling connection between the UE_A 10 and the CPF_A 140 based on the reception of the detach acceptance message and / or completion of the procedure (A) in this procedure (S1912).
- the connectivity between CPF_A140 and NRCnode_A122 may be released by deleting the context of UE_A10 stored in CPF_A140. Further, the NR node_A122 may release the RRC connection between the UE_A10 and the NR node_A122 by releasing the radio resource to the UE_A10 based on the release of the connection between the CPF_A140 and the NR node_A122.
- each device Upon completion of the above procedure, each device completes the detach procedure, and UE_A10 transitions to a state that is not registered in the core network_B190.
- Each device may execute the following procedure based on the completion of the detach procedure.
- the next procedure may be an attach procedure to the core network_A90 and / or a PDN connection procedure.
- each device is associated with the PDU session disconnected in this procedure based on transmission / reception of the 51st identification information and / or the 52nd identification information and / or the 54th identification information.
- each device may perform the following procedure to establish a PDN connection associated with the same IP address as the PDU session.
- UE_A10 may transmit the 61st identification information indicating the handover procedure to the core network_A90 in the next procedure, or the 62nd ID corresponding to the 57th identification information. Identification information may be transmitted.
- Each device uses the IP address associated with the PDU session disconnected in this procedure based on transmission / reception of the 51st identification information and / or the 52nd identification information and / or the 54th identification information.
- each device may execute the following procedure.
- UE_A10 may transmit the 61st identification information indicating the initial procedure to core network_A90 during the following procedure.
- each device receives information indicating handover based on transmission / reception of the 51st identification information and / or the 52nd identification information and / or the 53rd identification information and / or the 54th identification information.
- each device may execute the following procedure.
- UE_A10 may transmit the 61st identification information indicating the handover procedure, the 11th identification information, and / or the 16th identification to core network_A90 during the following procedure.
- the 63rd identification information corresponding to the identification information may be transmitted.
- UE_A10 may transmit the 18th identification information and / or the 64th identification information corresponding to the 46th identification information to core network_A90 in the following procedure, The identification information and / or the 65th identification information corresponding to the 45th identification information may be transmitted.
- each device may execute the following procedure after the detach procedure.
- UE_A10 may transmit the 61st identification information indicating the handover procedure, the 11th identification information, and / or the 16th identification to core network_A90 during the following procedure.
- the 63rd identification information corresponding to the identification information may be transmitted.
- each device may execute the following procedure after the detach procedure.
- the UE_A10 may transmit the 61st identification information indicating the initial procedure to the core network_A90 in the next procedure, the 11th identification information, and / or the 16th identification information.
- the 63rd identification information different from the identification information may be transmitted.
- each device attaches to the core network_A90, and / or PDN.
- a connection procedure may be performed.
- the use of the NGS service and the EPS service is determined for UE_A10. If the 54th identification information indicating that use of the NGS service is no longer permitted is sent / received in a state where it is permitted and / or supported, the procedure for attaching to each device and core network_A90 is not executed. In addition, the PDN connection procedure may be executed.
- UE_A10 transmits identification information corresponding to the identification information received from core network_B190 to core network_A90 during the next procedure. May be.
- the UE_A10 may transmit the 62nd identification information corresponding to the 57th identification information, the 11th identification information, and / or the 16th identification to the core network_A90 in the following procedure.
- the 63rd identification information corresponding to the identification information may be transmitted.
- UE_A10 may transmit the 18th identification information and / or the 64th identification information corresponding to the 46th identification information to core network_A90 in the following procedure,
- the identification information and / or the 65th identification information corresponding to the 45th identification information may be transmitted.
- UE_A10 may transmit the 68th identification information corresponding to the 56th identification information to core network_A90 in the following procedure, or the 69th identification corresponding to the 55th identification information Information may be transmitted.
- the attach procedure to the core network_A90 is a procedure for connecting to the network (access network and / or core network_A90 and / or PDN_A5) led by the UE_A10.
- UE_A10 may execute this procedure at any timing such as when the terminal is turned on, or it may be based on the detach procedure described in section 1.4.1.1. You may perform based on having decided to attach to network_B190. In other words, UE_A10 may start this procedure at an arbitrary timing as long as it is not registered in core network_A90 (EMM-DEREGISTERED). In addition, each device may transition to a registration state (EMM-REGISTERED) based on completion of the attach procedure to the core network_A90.
- EMM-DEREGISTERED EMM-DEREGISTERED
- UE_A10 may start this procedure based on receiving at least one piece of identification information among the 51st to 57th pieces of identification information in the detach procedure. Moreover, UE_A10 may start the attachment procedure to core network_A90 based on other triggers.
- This procedure is a procedure for each device to establish a PDN connection.
- Each device may execute this procedure in a state in which the procedure for attaching to the core network_A90 is completed, or may be executed in the procedure for attaching to the core network_A90.
- each device may start this procedure at an arbitrary timing after the procedure for attaching to the core network_A90.
- Each device may establish a PDN connection based on the completion of the PDN connection procedure.
- each device may establish a plurality of PDN connections by executing this procedure a plurality of times.
- UE_A10 transmits a PDN connection request (PDN Connectivity Request) message to MME_A40 via eNB_A45 (S2000), and starts a PDN connection procedure.
- PDN connection request PDN Connectivity Request
- UE_A10 may include at least one piece of identification information among at least the 61st to 66th pieces of identification information in the PDN connection request message.
- UE_A10 may show that UE_A10 requests
- UE_A10 receives at least one of the 61st to 66th identification information in the PDN connection request message based on the reception of at least one of the 51st to 57th identification information in the detach procedure. May be included.
- each device may indicate that this request is a request by handover from the core network_B190 by transmitting and receiving the 61st identification information.
- each device may indicate a session for requesting a handover by transmitting and receiving the 62nd identification information.
- each device may indicate the APN requested by UE_A 10 by transmitting and receiving the 63rd identification information.
- the APN may be the same as the APN acquired during the handover source PDU session establishment procedure.
- each device may indicate the UE identification information by transmitting and receiving the 64th identification information, or may indicate that this request is a reattach procedure.
- the UE identification information may be GUTI acquired during the handover source PDU session establishment procedure or TAU procedure, or may be IMSI.
- each device may indicate the connection destination DC requested by UE_A10 by transmitting / receiving the 65th identification information, or may indicate MME_A40 included in the DC.
- each device may indicate the NSI connected immediately before by transmitting and receiving the 66th identification information.
- each device may request establishment of a PDN connection for maintaining connectivity by an IP address associated with the PDU session before switching by transmitting / receiving the 61st identification information, or switching It may be required that the same IP address as that associated with the previous PDU session be assigned to the established PDN connection.
- the PDU session before switching may be a PDU session established for the NGS service and / or the core network_B190.
- MME_A40 receives the PDN connection request message and executes the first condition determination.
- the first condition determination is for determining whether the MME_A 40 accepts the UE_A 10 request. In the first condition determination, the MME_A 40 determines whether the first condition is true or false.
- MME_A40 may start the procedure (A) in the procedure if the first condition determination is true, and may start the procedure (B) in the procedure if the first condition determination is false. .
- MME_A40 executes the procedure (C) or (E) in this procedure, and starts the procedure (A) in this procedure.
- MME_A40 executes (C) in this procedure when PGW_A30 is selected as the external gateway, and executes (E) in this procedure when SCEF_A46 is selected as the GW for PDN connection.
- SCEF_A46 is selected as the GW for PDN connection.
- MME_A40 transmits a session creation request message to SGW_A35, and starts the procedure (C) in this procedure (S2002).
- the MME_A 40 may include at least one or more pieces of identification information among the pieces of identification information of the 61st to 66th in the session generation request message, or may include information indicating whether the request is an initial request.
- the UE_A10 request may be transmitted by including these pieces of identification information.
- SGW_A35 receives the session creation request message and transmits the session creation request message to PGW_A30 (S2004).
- SGW_A35 may include at least one piece of identification information from among the 61st to 66th pieces of identification information in the session generation request message, or may include information indicating whether the request is an initial request.
- the UE_A10 request may be transmitted by including these pieces of identification information.
- PGW_A30 receives the session generation request message and executes the second condition determination.
- the second condition determination is for determining whether or not the PGW_A 30 accepts the UE_A 10 request.
- the second condition is true when the UE_A10 request is accepted, and when the UE_A10 request is permitted. Further, the second condition is false when the UE_A10 request is rejected, and may be when the second condition is not determined to be true.
- the second condition determination may be performed not by PGW_A30 but by another device (for example, PCRF_A60).
- PGW_A30 performs an IP-CAN session establishment procedure with PCRF_A60. More specifically, the PGW_A 30 transmits a request message during the IP-CAN session establishment procedure to the PCRF_A 60. Further, the PCRF_A60 receives the request message during the IP-CAN session establishment procedure, determines the second condition, and transmits a response message during the IP-CAN session establishment procedure to the PGW_A30. Furthermore, PGW_A30 receives the response message during the IP-CAN session establishment procedure, and recognizes the result of the second condition determination.
- PGW_A30 may include at least one or more pieces of identification information of the 61st to 66th identification information in the request message during the IP-CAN session establishment procedure, or by including these identification information.
- UE_A10 request may be transmitted.
- the PCRF_A60 may include at least the second information determination result in the response message during the IP-CAN session establishment procedure, and by including this result, the second condition determination result is notified to the PGW_A30. Alternatively, the inclusion of this information may indicate that the UE_A10 request has been granted or rejected.
- PGW_A30 may perform the second condition determination based on the second condition determination result received from PCRF_A60. For example, when the PCRF_A60 accepts the UE_A10 request, the PCRF_A60 and the PGW_A30 may set the second condition to be true. When the PCRF_A60 rejects the UE_A10 request, the PCRF_A60 and the PGW_A30 may set the second condition to be false.
- PGW_A30 determines whether the second condition is true or false. When the second condition is true, PGW_A30 transmits a session generation response message to SGW_A35 (S2006). Furthermore, SGW_A35 receives the session creation response message.
- PGW_A30 may include an IP address in the session generation response message, or may indicate that the request of UE_A10 is permitted by including these identification information. Note that when the PGW_A 30 receives the 61st identification information and / or the 64th identification information in the session generation request, the IP address may be the same as the IP address to which the UE_A 10 is assigned in the previous connection.
- PGW_A30 sends a session creation rejection message to SGW_A35 (S2006).
- the session creation rejection message may be a session creation response message including a reason for rejection (Reject cause), or may indicate that the UE_A10 request has been rejected by including the reason for rejection.
- the SGW_A35 that has received the session generation response message or the session generation rejection message transmits a session generation response message or a session generation rejection message to the MME_A40 (S2008). Further, the MME_A 40 receives a session creation response message or a session creation rejection message.
- SGW_A35 includes at least one or more pieces of identification information included in the session generation response message or the session generation rejection message received from PGW_A30 in the session generation response message or the session generation rejection message received in the session generation response message. May be included.
- SGW_A35 may include the IP address in the session generation response message, or may indicate that the request of UE_A10 is permitted by including these identification information.
- the session creation rejection message may be a session creation response message including a reason for rejection (Rejectusecause), or may indicate that the request of UE_A10 has been rejected by including the reason for rejection.
- Each device completes the procedure (C) of this procedure based on the transmission / reception of the session generation response message and / or the session generation rejection message.
- MME_A40 transmits a session creation request message to SCEF_A46, and starts the procedure (E) in this procedure (S2010).
- SCEF_A 46 may include at least one piece of identification information among the pieces of identification information of the 61st to 66th in the session generation request message, or may include information indicating whether the request is an initial request. However, the UE_A10 request may be transmitted by including these pieces of identification information.
- SCEF_A46 receives the session generation request message and executes the third condition determination.
- the third condition determination is for determining whether the SCEF_A 46 accepts the UE_A 10 request.
- the third condition is true when the UE_A10 request is accepted, and when the UE_A10 request is permitted.
- the third condition is false when the UE_A10 request is rejected, and may be when the third condition is not determined to be true.
- SCEF_A46 determines whether the third condition is true or false. If the third condition is true, SCEF_A 46 transmits a session creation response message to MME_A 40 (S2012). Further, the MME_A 40 receives the session generation response message.
- SCEF_A46 may include the IP address in the session generation response message, or may indicate that the request of UE_A10 is permitted by including these identification information. Note that when the PGW_A 30 receives the 61st identification information and / or the 64th identification information in the session generation request, the IP address may be the same as the IP address to which the UE_A 10 is assigned in the previous connection.
- SCEF_A46 transmits a session creation rejection message to MME_A40 (S2012).
- the session creation rejection message may be a session creation response message including a reason for rejection (Reject cause), or may indicate that the UE_A10 request has been rejected by including the reason for rejection.
- Each device completes the procedure (E) of this procedure based on the transmission / reception of the session creation response message and / or the session creation rejection message.
- the MME_A40 sends a default EPS bearer context active message (ActivateCdefault EPS bearer context request) to the eNB_A45 based on reception of the session creation response message and / or upon completion of the procedure (C) or (E) in this procedure. ) And / or a PDN Connectivity Accept message is transmitted (S2014).
- the message transmitted from the MME_A 40 to the eNB_A 45 may be a response message to the PDN connection request message, and is not limited to this, and may be a message that accepts a request for establishing a PDN connection.
- eNB_A45 receives a default EPS bearer context active message and / or a PDN connection acceptance message, and receives an RRC message (for example, an RRC message such as an RRCConnection Reconfiguration message, an RRC Connection ⁇ ⁇ ⁇ ⁇ ⁇ Setup message, or an RRC Direct Transfer message), and UE_A10, and A default EPS bearer context active message or a PDN connection acceptance message and / or a PDN connection acceptance message is transmitted (S2016). Note that the PDN connection acceptance message may be included in the RRC message and transmitted / received.
- MME_A40 may include the IP address in the PDN connection acceptance message, or may indicate that the request of UE_A10 is permitted by including these identification information.
- UE_A10 When receiving the RRC message, UE_A10 transmits an RRC message (for example, an RRC message such as an RRC Connection Connection Reconfiguration Complete message, an RRC Connection Connection Setup message, or an RRC Direct Transfer message) to the eNB_A45 (S2018).
- the eNB_A45 receives the RRC message and transmits a bearer setting message to the MME_A40 (S2020). Furthermore, MME_A40 receives a bearer setting message.
- UE_A10 When receiving the default EPS bearer context activation message and / or the PDN connection acceptance message, UE_A10 sends the PDN Connectivity Complete message or the default EPS bearer context activation acceptance (ActivateEPSdefault EPS bearer context accept) to MME_A40 via eNB_A45. ) A message is transmitted (S2022) (S2024). Further, the MME_A 40 receives the PDN connection completion message and / or the default EPS bearer context activation acceptance message, and the MME_A 40 receives the PDN connection completion message and performs the fourth condition determination.
- the message transmitted from the UE_A10 to the eNB_A45 and the MME_A40 may be a response message to the PDN connection acceptance message or the default EPS bearer context active message, and is not limited to this, and may be a message indicating that the PDN connection procedure is completed. Good.
- the fourth condition determination is for determining whether or not the MME_A 40 requires the SGW_A 35 to change the bearer. If the fourth condition is true, MME_A40 starts the procedure (D) in this procedure. If the fourth condition determination is false, MME_A40 does not execute the procedure (D) in this procedure.
- the MME_A 40 transmits a bearer change request message to the SGW_A 35 (S2026), and starts the procedure (D) in this procedure. Furthermore, SGW_A35 receives the bearer change request message and transmits a bearer change response message to MME_A40 (S2028). Further, the MME_A 40 receives the bearer change response message and completes the procedure (D) of this procedure. Furthermore, each device completes the procedure (A) in this procedure based on the transmission / reception of the PDN connection completion message and / or the completion of the procedure (D) in this procedure.
- the MME_A 40 transmits a PDN connection rejection (PDN Connectivity reject) message to the UE_A 10 via the eNB_A45 (S2030), and starts the procedure (B) in this procedure. Further, UE_A10 receives the PDN connection rejection message and recognizes that the request of UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission / reception of the PDN connection rejection message.
- the PDN connection rejection message may include an appropriate rejection reason.
- the PDN connection rejection message may be a response message to the PDN connection request message, and is not limited thereto, and may be a message rejecting a request for establishing a PDN connection.
- the MME_A40 may include one or more pieces of identification information from among the 21st to 25th identification information in the PDU session establishment rejection message, and the UE_A10 request is rejected by including these identification information. You may show things.
- each device may indicate the reason why the PDN connection procedure is rejected by transmitting and receiving the 21st identification information, or may indicate the processing to be performed by each device after the attach procedure.
- each device transmits / receives the 22nd identification information and / or the 23rd identification information, so that the network supports connection to the core network_A90 and / or switching of the EPS service, and / or It may indicate that permission is not allowed. Furthermore, each device may indicate the service continuation mode when switching to the EPS service, which is not supported and / or permitted by the network, by transmitting / receiving the 24th identification information and / or the 25th identification information. Good.
- 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. The user may recognize that this procedure has been rejected, or may transition to a state where a PDU session is not established.
- 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 transmitting or receiving one or more pieces of identification information among the 21st to 25th pieces of identification information, each device may recognize the reason why the UE_A10 request is rejected. Furthermore, each apparatus may perform this procedure again based on the reason why the request of UE_A10 is rejected, or may perform this procedure under different conditions.
- first to fourth condition determinations described above may be performed based on identification information and / or subscriber information and / or operator policy included in the PDN connection request message. Further, the condition for determining whether the first to fourth conditions are true or false is not limited to the above-described conditions.
- the first to third conditions may be true when UE_A 10 requests session establishment and the network permits the request. Further, the first to third conditions may be false when the UE_A 10 requests session establishment and the network does not permit the request. Further, the first to third conditions may be false when the network to which UE_A 10 is connected and / or the device in the network does not support the establishment of the session requested by UE_A 10.
- UE_A10 transmits an attach request message to MME_A40 via eNB_A45 (S2100), and starts an attach procedure.
- UE_A10 may transmit the attach request message including the above-described PDN connection request message, or may include the PDN connection request message to request that the PDN connection procedure be performed during the attach procedure. .
- UE_A10 may include at least one piece of identification information from among the 61st to 66th pieces of identification information in the attach request message.
- UE_A10 may show that UE_A10 requests
- UE_A10 requests attachment and / or connection reflecting the characteristics represented by each identification information described above, or the contents represented by each identification information described above. May be indicated.
- UE_A10 requests establishment of a PDN connection having the characteristics represented by each identification information described above or a PDN connection reflecting the contents represented by each identification information by including these identification information. May be indicated.
- each device may indicate that this request is a handover from the core network_B190 by transmitting and receiving the 61st identification information.
- each device may indicate the UE identification information by transmitting and receiving the 64th identification information, or may indicate that this request is a reattach procedure.
- each device may indicate the connection destination DC requested by UE_A10 by transmitting / receiving the 65th identification information, or may indicate MME_A40 included in the DC.
- each device may indicate the NSI connected immediately before by transmitting and receiving the 66th identification information.
- each device may request establishment of a PDN connection for maintaining connectivity by an IP address associated with the PDU session before switching by transmitting / receiving the 61st identification information, or switching It may be required that the same IP address as that associated with the previous PDU session be assigned to the established PDN connection.
- UE_A 10 may transmit the identification information included in a control message different from the attach request message.
- MME_A40 receives the attach request message and / or a control message different from the attach request message, and executes the first condition determination.
- the first condition determination is for determining whether the MME_A 40 accepts the UE_A 10 request.
- MME_A40 starts the procedure (A) in the procedure when the first condition is true, and starts the procedure (B) in the procedure when the first condition is false. Details of the procedure (B) in this procedure will be described later.
- the MME_A 40 executes the second condition determination and starts the procedure (A) in this procedure.
- the second condition determination is for determining whether or not the MME_A 40 performs the PDU session establishment procedure.
- the MME_A 40 determines whether the second condition is true or false.
- the MME_A 40 starts the procedure (C) or (E) in the PDN connection procedure when the second condition is true, and omits the procedure when the second condition is false (S2104).
- the MME_A 40 transmits an attach accept message to the eNB_A 45 based on the reception of the attach request message and / or the session creation response message (S2106).
- MME_A40 may start the procedure (B) in this procedure without continuing the procedure (A) in this procedure.
- the eNB_A45 receives the attach acceptance message and transmits an RRC message (for example, an RRC message such as an RRCConnection Reconfiguration message, an RRC Connection Setup message, or an RRC Direct Transfer message) and / or an attach acceptance message to the UE_A10 (S2108).
- the attach acceptance message may be transmitted and received by being included in the RRC message.
- MME_A40 may transmit the attach acceptance message including the above-described PDN connection acceptance message, or the PDN connection procedure is accepted by including the PDN connection acceptance message. You may show that
- MME_A40 may include an IP address or may indicate that the request of UE_A10 has been accepted by including these identification information.
- the second condition determination is for determining whether or not the MME_A 40 performs the PDN connection procedure.
- the second condition is true when a PDN connection request message is received, and may be when the PDN connection procedure is also executed during this procedure. Also, the second condition is false when the PDN connection request message is not received, and the PDN connection procedure may not be executed during this procedure, or the second condition may not be determined to be true. .
- UE_A10 when UE_A10 receives an RRC message from eNB_A45, UE_A10 transmits an RRC connection message (e.g., an RRC message such as RRC Connection Reconfiguration Complete message, RRC Connection Setup Complete message, or RRCDirect Transfer message) to eNB_A45. (S2110).
- the eNB_A45 receives the RRC message and transmits a bearer setting message to the MME_A40 (S2112). Furthermore, MME_A40 receives a bearer setting message.
- UE_A10 When UE_A10 receives an attach acceptance message from MME_A40 via eNB_A45, UE_A10 transmits an attach complete message to MME_A40 via eNB_A45 (S2114) (S2116). Further, the MME_A 40 receives the attach completion message. Furthermore, when the second condition is true, the MME_A 40 starts the procedure (D) in the PDN connection procedure (S2118). If the second condition is false, the MME_A 40 does not execute the procedure (D) in the PDU session establishment procedure. Each device completes the procedure (A) in this procedure based on the transmission / reception of the attach completion message and / or the completion of the procedure (D) in the PDN connection procedure.
- UE_A10 When UE_A10 receives the PDN connection acceptance message, UE_A10 may transmit the attach completion message including the PDN connection completion message described above, or complete the PDN connection procedure by including the PDN connection completion message. You may show things.
- the MME_A40 transmits an attach rejection message to the UE_A10 via the eNB_A45, and starts the procedure (B) in this procedure (S2120). Further, UE_A10 receives the attach rejection message and recognizes that the request of UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission / reception of the attach rejection message. If the second condition is true, the MME_A40 may transmit the attach rejection message including the above-described PDN connection rejection message, or the PDN connection procedure is rejected by including the PDN connection rejection message. You may show that In that case, UE_A10 may further receive a PDN connection rejection message, or may authenticate that the PDN connection procedure is rejected.
- Each device completes this procedure based on the completion of the procedure (A) or (B) in this procedure.
- Each device may transition to a state in which UE_A10 is connected to the network and / or registered in the core network_A90 based on the completion of the procedure (A) in this procedure. Based on the completion of the procedure (B), it may be recognized that this procedure has been rejected, and it has entered a state where it cannot be connected to the network and / or cannot be registered in the core network_A90. Also good.
- the transition of each device to each state may be performed based on completion of this procedure, or may be performed based on establishment of a PDN connection.
- 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 transmitting or receiving one or more pieces of identification information among the 21st to 25th pieces of identification information, each device may recognize the reason why the UE_A10 request is rejected. Furthermore, each device may perform this procedure again based on the reason why the request of UE_A10 is rejected, or may perform the attach procedure for the core network_B190 or another cell.
- the second condition determination described above may be executed based on identification information and / or subscriber information and / or operator policy included in the attach request message. Further, the condition for determining whether the second condition is true or false is not limited to the above-described condition.
- This procedure is for moving the session led by the network and established by UE_A10 to the core network_B190 to the core network_A90.
- the core network that establishes the session and the connection service used in the session It is a procedure for changing. While the first reconnection procedure was a procedure for switching attached sessions all at once, this procedure provides a method for switching at least one session at a time.
- the attached state may be a state in which UE_A10 is connected to the network, and the unattached state may be a state in which UE_A10 is not connected to the network.
- each device transits to the first state connected to the core network_B190 (S2200).
- the procedure for transitioning to the first state may be the initial procedure described in Chapter 1.3.
- each device executes the procedure (A) in this procedure.
- the following describes each procedure included in the procedure (A) in this procedure.
- Each device executes the PDU session disconnection procedure (S2202) and starts the procedure (A) in this procedure.
- Each device releases at least one PDU session by executing a PDU session disconnection procedure.
- each device explicitly or implicitly enters a state where UE_A10 is not registered in core network_B190. You may make a transition.
- each device may execute the above-described detach procedure.
- each device executes a PDN connection procedure.
- UE_A10 may be in a state of being attached to core network_A90 and / or a state of being registered.
- each device executes the attach procedure to core network_A90 described above and transitions to the registered state.
- the PDN connection procedure may be executed.
- Each device completes the procedure (A) in this procedure by executing the PDN connection procedure. Furthermore, each device may execute the procedure (A) in this procedure again. That is, in the first state during this procedure, when a plurality of PDU sessions are established between UE_A10 and the core network_B190, each device performs (A) in this procedure for each PDU session. You may execute the procedure. Each device may execute the procedure (A) in this procedure at least once.
- the PDN connection procedure in this procedure may be the same as the PDN connection procedure in the first reconnection procedure.
- UE_A10 may continue to maintain a PDU session for one or a plurality of core networks_A90 excluding the PDU session disconnected based on the PDU session disconnection procedure, and may continue communication using these PDU sessions. .
- a network-led PDU session disconnection procedure in this embodiment will be described with reference to FIG.
- this procedure refers to the PDU session disconnection procedure.
- This procedure is a procedure for disconnecting and / or releasing a PDU session led by the network and established by UE_A10.
- Each device may release a plurality of PDU sessions by executing this procedure a plurality of times.
- each device executes the procedure (A) in the detach procedure (S2302).
- CPF_A140 transmits a PDU session disconnection request (PDU Session Disconnection Request) message to UE_A10 via NRnode_A122 (S2304). Furthermore, UE_A10 receives the PDU session disconnection request message.
- PDU Session Disconnection Request PDU Session Disconnection Request
- CPF_A140 may include at least the 71st to 76th identification information in the PDU session disconnection request message. By including these pieces of identification information in the PDU session disconnection request message, CPF_A140 may indicate a request to UE_A10. In other words, the CPF_A 140 may indicate that the UE_A 10 is requested to have the characteristics or contents represented by each of the identification information described above by including these pieces of identification information.
- CPF_A140 is based on transmitting at least one or more of the 11th to 18th identification information to UE_A10 in the attach procedure to core network_B190 and / or the PDU session establishment procedure, at least.
- One or more pieces of identification information among the 71st to 76th pieces of identification information may be included in the PDU session disconnection request message.
- CPF_A140 disconnects at least one of the identification information of the 71st to 76th PDU sessions when continuation of service is permitted by the PDN connection procedure accompanying the PDU session disconnection procedure. It may be included in the request message.
- the permission information for this service continuation may be managed as subscriber information for UE_A10. Therefore, CPF_A140 may include such identification information based on the subscriber information of UE_A10.
- the 74th identification information may be included in the PDU session disconnection request message. Otherwise, it may be determined that the 74th identification information is not included in the PDU session disconnection request message.
- the 73rd identification information indicating EPC may be included in the PDU session disconnection request message. Otherwise, the 73rd identification information indicating NGC may be included in the PDU session disconnection request message, or it may be determined that the 73rd identification information is not included in the PDU session disconnection request message.
- the CPF_A 140 requests the UE_A 10 to disconnect and / or switch and / or perform handover for the PDU session and / or bearer indicated by the 71st identification information by transmitting the 71st identification information. Also good. Further, the UE_A 10 may determine a PDU session and / or a bearer that performs disconnection and / or switching and / or handover by receiving the 71st identification information.
- each device may indicate the reason for this request by transmitting and receiving the 72nd identification information.
- the 72nd identification information may be information indicating a handover request, for example.
- CPF_A140 transmits the 73rd identification information to request that the system indicated by the 73rd identification information execute the PDN connection procedure and reactivate the session. Good. Also, UE_A10 receives the 73rd identification information, so that it performs the PDN connection procedure for the system indicated by the 73rd identification information and decides to reactivate the session. Good. The session reactivation may be to establish a PDN connection by executing a PDN connection procedure.
- each device may be information indicating whether transmission / reception of information indicating handover is necessary during session re-establishment by transmitting / receiving the 74th identification information.
- CPF_A140 is started based on the completion of the PDU session disconnection procedure by transmitting the 74th identification information.
- UE_A 10 may request that a flag indicating handover be transmitted.
- UE_A10 may determine that UE_A10 transmits a flag indicating handover in the PDN connection procedure that starts based on completion of the PDU session disconnection procedure by receiving the 74th identification information.
- the CPF_A 140 is executed based on completion of the PDU session disconnection procedure by transmitting the 74th identification information.
- a flag indicating handover by UE_A10 may be notified that transmission is not necessary.
- UE_A10 determines that UE_A10 does not transmit a flag indicating handover in the PDN connection procedure to core network_A90 that starts based on completion of the PDU session disconnection procedure by receiving the 74th identification information. May be.
- the information indicating the handover may be the 61st identification information or the identification information requesting the IP address reservation.
- the IP address preservation may be to establish connectivity by the same IP address as the IP address used before switching after executing the attach procedure and / or the PDN connection procedure again. In other words, IP address preservation may mean that the IP address used after re-executing the attach procedure and / or PDN connection procedure is the same as the IP address that was still used before switching.
- CPF_A140 may notify UE_A10 of the NSI in which the PDU session to be disconnected has been established by transmitting the 75th identification information. Further, by receiving the 75th identification information, the NSI in which the PDU session to be disconnected has been established may be received.
- the CPF_A 140 may request to execute the PDN connection procedure for the DCN indicated by the 76th identification information by transmitting the 76th identification information. Further, UE_A10 may determine to execute the PDN connection procedure for the DCN indicated by the 76th identification information by receiving the 76th identification information.
- the CPF_A 140 may request the DCN indicated by the 76th identification information to establish a PDN connection by transmitting the 76th identification information. Further, UE_A10 may determine to establish a PDN connection for the DCN indicated by the 76th identification information by receiving the 76th identification information.
- each device may indicate the NSI to be connected at the time of switching to the currently connected DCN and / or NGS connection service by transmitting and receiving the 75th and / or 76th identification information.
- each device maintains connectivity by the IP address corresponding to the PDU session when the connection destination of the PDU session is switched by transmitting and receiving the 72nd identification information and / or the 74th identification information. May indicate that it is possible, or may require that it be maintained.
- each device transmits / receives the 72nd identification information and / or the 74th identification information to the same IP address as the PDU session to be disconnected by the PDU session disconnection procedure after the PDU session disconnection procedure is completed. It may indicate that the associated PDN connection can be established or may require establishment.
- the 71st to 76th identification information may be transmitted and received as a single piece of identification information by combining two or more pieces of identification information.
- the combined identification information may be identification information having the meaning of each combination of identification information.
- the UE_A10 that has received the PDU session disconnection request message may transmit a PDU session disconnect acceptance (PDU Session DisconnectionAccept) message to the CPF_A140 via the NR_node_A122 (S2310). Further, CPF_A 140 may receive a PDU session disconnect acceptance message.
- PDU Session DisconnectionAccept PDU Session DisconnectionAccept
- Each device may complete this procedure based on transmission / reception of a PDU session acceptance message. Upon completion of the above procedure, each device completes the PDU session disconnection procedure and transitions to a state where the PDU session is disconnected.
- Each device may complete this procedure based on transmission / reception of a PDU session acceptance message. Upon completion of this procedure, each device may transition to a state in which the PDU session is disconnected.
- each device may execute the following procedure based on the completion of the PDU session disconnection procedure.
- the next procedure may be a PDN connection procedure.
- UE_A10 may start the PDN connection procedure based on the reception of at least one piece of identification information among the 71st to 76th pieces of identification information in the PDU session disconnection procedure.
- each device maintains connectivity based on the IP address associated with the PDU session disconnected in this procedure based on transmission / reception of the 72nd identification information and / or the 74th identification information.
- Each device may execute the following procedure in order to establish a PDN connection associated with the same IP address as the PDU session.
- UE_A10 may transmit to the core network_A90 the 61st identification information indicating the handover procedure to the core network_A90 in the next procedure, or to the 71st identification information.
- the corresponding 62nd identification information may be transmitted.
- each device does not maintain the connectivity by the IP address associated with the PDU session disconnected in this procedure based on the transmission / reception of the 72nd identification information and / or the 74th identification information.
- each device may execute the following procedure.
- UE_A10 may transmit the 61st identification information indicating the initial procedure to core network_A90 during the following procedure.
- each device uses the core network_B190 using the information indicating the handover based on transmission / reception of the 72nd identification information and / or the 73rd identification information and / or the 74th identification information to the core network.
- each device may execute the following procedure.
- UE_A10 may transmit the 61st identification information indicating the handover procedure, the 11th identification information, and / or the 16th identification to core network_A90 during the following procedure.
- the 63rd identification information corresponding to the identification information may be transmitted.
- UE_A10 may transmit the 18th identification information and / or the 64th identification information corresponding to the 46th identification information to core network_A90 in the following procedure, The identification information and / or the 65th identification information corresponding to the 45th identification information may be transmitted.
- each device may execute the following procedure after the detach procedure.
- UE_A10 may transmit the 61st identification information indicating the handover procedure, the 11th identification information, and / or the 16th identification to core network_A90 during the following procedure.
- the 63rd identification information corresponding to the identification information may be transmitted.
- each device may execute the following procedure after the detach procedure.
- the UE_A10 may transmit the 61st identification information indicating the initial procedure to the core network_A90 in the next procedure, the 11th identification information, and / or the 16th identification information.
- the 63rd identification information different from the identification information may be transmitted.
- UE_A10 When each device executes the next procedure after the PDU session disconnection procedure is completed, UE_A10 sends the identification information corresponding to the identification information received from core network_B190 to core network_A90 during the next procedure. You may send it. For example, the UE_A10 may transmit the 62nd identification information corresponding to the 71st identification information, the 11th identification information, and / or the 16th identification to the core network_A90 in the following procedure. The 63rd identification information corresponding to the identification information may be transmitted.
- UE_A10 may transmit the 18th identification information and / or the 64th identification information corresponding to the 46th identification information to core network_A90 in the following procedure, The identification information and / or the 65th identification information corresponding to the 45th identification information may be transmitted. Furthermore, UE_A10 may transmit the 68th identification information corresponding to the 76th identification information to core network_A90 in the following procedure, or the 69th identification corresponding to the 75th identification information Information may be transmitted.
- the PDN connection procedure in the second reconnection procedure may be the same as the PDN connection procedure example described in Chapter 1.4.1.3. Therefore, the detailed description here is omitted.
- Whether or not at least one of the 61st to 68th identification information is included in the PDN connection request message is determined by UE_A10 in the PDU session disconnection procedure among the 71st to 76th identification information. The determination may be made based on receiving at least one piece of identification information. In other words, the UE_A 10 receives at least one of the 61st to 68th identification information from the PDN based on the reception of at least one of the 71st to 76th identification information in the PDU session disconnection procedure. It may be included in the connection request message.
- 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 program recorded on the recording medium may be read by a computer system and executed.
- 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. Further, in the case where an integrated circuit technology that replaces the current integrated circuit appears due to progress in semiconductor technology, 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)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
[1.1.システム概要]
図1は、本実施形態における移動通信システムの概略を説明する為の図である。本図に示すように、移動通信システム1は、移動端末装置UE_A10とアクセスネットワーク_Aとアクセスネットワーク_Bとコアネットワーク_A90とコアネットワーク_B190とPDN(PacketData Network)_A5により構成されている。ここで、UE_A10は無線接続可能な端末装置であればよく、UE(User Equipment)、ME(Mobile Equipment)、MS(Mobile Station)、又はCIoT(Cellular Internetof Things)端末(CIoT UE)等でもよい。さらに、コアネットワークは、コアネットワーク_A90及び/又はコアネットワーク_B190であってもよく、アクセスネットワークは、アクセスネットワーク_A及び/又はアクセスネットワーク_Bであってもよい。
まず、各装置で記憶される識別情報について説明する。IMSI(International MobileSubscriber Identity)は、加入者(ユーザ)の永久的な識別情報であり、UEを使用するユーザに割り当てられる識別情報である。UE_A10及びMME_A40/CPF_A140及びSGW_A35が記憶するIMSIは、HSS_A50が記憶するIMSIと等しくてよい。
図4にUE_A10の装置構成を示す。図に示すように、UE_A10は、送受信部_A420と制御部_A400と記憶部_A440とで構成されている。送受信部_A420と記憶部_A440は、制御部_A400とバスを介して接続されている。
以下、eNB_A45、NR node_A122、及びWAG_A126の構成について説明する。図6にeNB_A45、NR node_A122、及びWAG_A126の装置構成を示す。図に示すように、eNB_A45、NR node_A122、及びWAG_A126は、ネットワーク接続部_B620と送受信部_B630と制御部_B600と記憶部_B640で構成されている。ネットワーク接続部_B620と送受信部_B630と記憶部_B640は、制御部_B600とバスを介して接続されている。
以下、MME_A40及びCPF_A140の構成について説明する。図7にMME_A40及びCPF_A140の装置構成を示す。図に示すように、MME_A40及びCPF_A140は、ネットワーク接続部_C720と制御部_C700と記憶部_C740で構成されている。ネットワーク接続部_C720と記憶部_C740は、制御部_C700とバスを介して接続されている。なお、これらの各部の機能は、物理的なハードウェア上で動作するものでもよいし、仮想的に汎用的なハードウェア上に構成された論理的なハードウェア上で動作するものでもよい。
図10にSGW_A35の装置構成を示す。図に示すように、SGW_A35はネットワーク接続部_D1020と制御部_D1000と記憶部_D1040とで構成されている。ネットワーク接続部_D1020と記憶部_D1040は、制御部_D1000とバスを介して接続されている。
図10にPGW_A30及びUPGW_A130の装置構成を示す。図に示すように、PGW_A30及びUPGW_A130はネットワーク接続部_D1020と制御部_D1000と記憶部_D1040とで構成されている。ネットワーク接続部_D1020と記憶部_D1040は、制御部_D1000とバスを介して接続されている。なお、これらの各部の機能は、物理的なハードウェア上で動作するものでもよいし、仮想的に汎用的なハードウェア上に構成された論理的なハードウェア上で動作するものでもよい。
図10にSCEF_A46の装置構成を示す。図に示すように、SCEF_A46は、ネットワーク接続部_D1020と制御部_D1000と記憶部_D1040で構成されている。ネットワーク接続部_D1020と記憶部_D1040は、制御部_D1000とバスを介して接続されている。
次に、本実施形態におけるコアネットワーク_B190に対する初期手続きの詳細手順を説明する前に、重複説明を避ける為、本実施形態特有の用語や、各手続きに用いる主要な識別情報を予め説明する。
まず、コアネットワーク_B190へのアタッチ手続きの概要について説明する。コアネットワーク_B190へのアタッチ手続きは、UE_A10が主導してネットワーク(アクセスネットワーク、及び/又はコアネットワーク_B190、及び/又はPDN_A5)へ接続する為の手続きである。UE_A10は、コアネットワーク_B190に接続していない状態であれば、端末電源投入時等の任意のタイミングで本手続きを実行する事ができる。言い換えると、UE_A10は、登録されていない状態(EMM-DEREGISTERED)であれば任意のタイミングで本手続きを開始してもよい。また、各装置は、コアネットワーク_B190へのアタッチ手続き完了に基づいて、登録状態(EMM-REGISTERED)に遷移してもよい。
次に、PDUセッション確立手続きの例について説明する。以下、本手続きはPDN接続手続きを指す。本手続きは、各装置がPDUセッションを確立する為の手続きである。なお、各装置は、本手続きを、コアネットワーク_B190へのアタッチ手続きを完了した状態で実行してもよいし、コアネットワーク_B190へのアタッチ手続きの中で実行してもよい。また、各装置は、コアネットワーク_B190へのアタッチ手続き後の任意のタイミングで本手続きを開始してもよい。また、各装置は、PDUセッション確立手続きの完了に基づいて、PDUセッションを確立してもよい。さらに、各装置は、本手続きを複数回実行する事で、複数のPDUセッションを確立してもよい。
図15を用いて、PDUセッション確立手続きを実行する手順の例を説明する。以下、本手続きの各ステップについて説明する。まず、UE_A10は、NR node_A122を介してCPF_A140にPDUセッション確立要求(PDU Session Establishment Request)メッセージを送信し(S1500)、PDUセッション確立手続きを開始する。なお、PDUセッションがPDNコネクション(PDN connection)である場合、PDUセッション確立要求メッセージはPDN接続要求(PDN connectivity request)メッセージでよい。また、PDUセッション確立要求メッセージは、これに限らず、PDUセッションの確立を要求するメッセージであればよい。
図16を用いて、コアネットワーク_B190へのアタッチ手続きを実行する手順の例を説明する。以下、本手続きとはコアネットワーク_B190へのアタッチ手続きを指す。本手続きは、UE_A10がコアネットワーク_B190に登録されるための手続きである。以下、本手続きの各ステップについて説明する。まず、UE_A10は、NR node_A122を介してCPF_A140にアタッチ要求(Attach request)メッセージを送信し(S1600)、コアネットワーク_B190へのアタッチ手続きを開始する。UE_A10は、アタッチ要求メッセージに、前述したPDUセッション確立要求メッセージを含めて送信してもよいし、PDUセッション確立要求メッセージを含める事で、コアネットワーク_B190へのアタッチ手続き中でPDUセッション確立手続きを実施する事を要求してもよい。
トラッキングエリア更新手続き(Tracking Area Update Procedure)の概要について説明する。以下、本手続きは、トラッキングエリア更新手続きを指す。本手続きは、ネットワーク(アクセスネットワーク、及び/又は、コアネットワーク_B190)におけるUE_A10の位置登録情報を更新する、及び/又は、UE_A10からネットワークへ定期的にUE_A10の状態を通知する、及び/又は、ネットワークにおけるUE_A10に関する特定のパラメータを更新する為の手続きである。UE_A10は、PDUセッションが確立された状態であれば、任意のタイミングで本手続きを実行する事ができる。また、UE_A10は、本手続きを定期的に実行する事ができる。
図17を用いて、トラッキングエリア更新手続きを実行する手順の例を説明する。以下、本手続きの各ステップについて説明する。まずUE_A10は、NR node_A122を介してCPF_A140にトラッキングエリア更新要求(Tracking Area Updaterequest)メッセージを送信し(S1700)、トラッキングエリア更新手続きを開始する。
次に、本実施形態における再接続手続きを説明する。ここで、再接続手続きとは、接続を一時切断し、再び接続を確立するまでの手続きである。本実施形態では、コアネットワーク_B190に接続するPDUセッションを、コアネットワーク_A90に接続するPDN接続に切り替える手続きを説明する。また、本手続きは、コアネットワーク_A90に接続する状態から、コアネットワーク_B190に接続する状態に遷移する手続きであってもよい。なお、本実施形態では、2つの再接続手続きについて説明する。以下、第1の再接続手続き及び第2の再接続手続きを説明する。
本実施形態における、第1の再接続手続きを、図18を用いて説明する。以下、本手続きとは、第1の再接続手続きを指し、各手続きには、デタッチ手続き、コアネットワーク_A90へのアタッチ手続き、PDN接続手続きがある。なお、各手続きの詳細は、後述する。まず、各装置は、コアネットワーク_B190へ接続する第1の状態に遷移(S1800)する。
まず、デタッチ手続きを、図19を用いて説明する。以下、本手続きとはデタッチ手続きを指す。本実施形態では、コアネットワーク_B190が主導して、UE_A10とネットワーク(アクセスネットワーク及び/又はコアネットワーク_B190、及び/又はPDN_A5)間の接続を切断するための手続きである。つまり、UE_A10がコアネットワーク_B190に接続している第1の状態であれば、コアネットワーク_B190は任意のタイミングで本手続きを開始する事ができる。言い換えれば、UE_A10がコアネットワーク_B190に登録されている状態(EMM-REGISTERD)であれば、コアネットワーク_B190は任意のタイミングで本手続きを開始してよい。また、各装置はデタッチ手続き完了に基づいて、UE_A10がコアネットワーク_B190に登録されていない状態(EMM-DEREGISTERD)に遷移してもよい。
次に、コアネットワーク_A90へのアタッチ手続きの概要について説明する。本実施形態において、コアネットワーク_A90へのアタッチ手続きは、UE_A10が主導してネットワーク(アクセスネットワーク、及び/又はコアネットワーク_A90、及び/又はPDN_A5)へ接続する為の手続きである。
次に、PDN接続手続きの例について説明する。以下、本手続きとはPDUセッション確立手続きを指す。本手続きは、各装置がPDN接続を確立する為の手続きである。なお、各装置は、本手続きを、コアネットワーク_A90へのアタッチ手続きを完了した状態で実行してもよいし、コアネットワーク_A90へのアタッチ手続きの中で実行してもよい。また、各装置は、コアネットワーク_A90へのアタッチ手続き後の任意のタイミングで本手続きを開始してもよい。また、各装置は、PDN接続手続きの完了に基づいて、PDN接続(PDN connection)を確立してもよい。さらに、各装置は、本手続きを複数回実行する事で、複数のPDN接続を確立してもよい。
図21を用いて、コアネットワーク_A90へのアタッチ手続きを実行する手順の例を説明する。以下、本手続きとはコアネットワーク_A90へのアタッチ手続きを指す。本手続きは、UE_A10がコアネットワーク_A90に登録されるための手続きである。以下、本手続きの各ステップについて説明する。まず、UE_A10は、eNB_A45を介してMME_A40にアタッチ要求メッセージを送信し(S2100)、アタッチ手続きを開始する。UE_A10は、アタッチ要求メッセージに、前述したPDN接続要求メッセージを含めて送信してもよいし、PDN接続要求メッセージを含める事で、アタッチ手続き中でPDN接続手続きを実施する事を要求してもよい。
次に、本実施形態における第2の再接続手続きを、図22を用いて説明する。以下、本手続きは、第2の再接続手続きを指し、各手続きには、PDUセッション切断手続き、及び/又はPDN接続手続きがある。なお、各手続きの詳細は、後術する。
本実施形態におけるネットワーク主導のPDUセッション切断手続きを、図23を用いて説明する。以下、本手続きとはPDUセッション切断手続きを指す。本手続きは、ネットワークが主導し、UE_A10が確立するPDUセッションを切断、及び/または解放する為の手続きである。なお、各装置は、本手続きを複数回実行する事で、複数のPDUセッションを解放してもよい。まず、各装置はデタッチ手続き中の(A)の手続きを実行する(S2302)。
第2の再接続手続きにおけるPDN接続手続きは、1.4.1.3章で述べたPDN接続手続き例と同様でよい。従って、ここでの詳細な説明は省略する。
本発明に関わる装置で動作するプログラムは、本発明に関わる実施形態の機能を実現するように、CentralProcessing Unit(CPU)等を制御してコンピュータを機能させるプログラムであっても良い。プログラムあるいはプログラムによって取り扱われる情報は、一時的にRandom Access Memory(RAM)等の揮発性メモリあるいはフラッシュメモリ等の不揮発性メモリやHard Disk Drive(HDD)、あるいはその他の記憶装置システムに格納される。
5 PDN_A
10 UE_A
20 UTRAN_A
22 NB_A
24 RNC_A
25 GERAN_A
26 BSS_A
30 PGW_A
35 SGW_A
40 MME_A
42 SGSN_A
45 eNB_A
46 SCEF_A
50 HSS_A
55 AAA_A
60 PCRF_A
65 ePDG_A
70 WLAN ANa
72 WLAN APa
74 TWAG_A
75 WLAN ANb
76 WLAN APb
80 E-UTRAN_A
90 コアネットワーク_A
120 NextGen RAN_A
122 NR node_A
125 WLAN ANc
126 WAG_A
130 UPGW_A
140 CPF_A
190 コアネットワーク_B
Claims (24)
- 端末装置であって、
前記端末装置は、
第1のコアネットワークに対してデタッチ手続きを実行し、
前記デタッチ手続きの後、第2のコアネットワークに対してアタッチ手続きを実行する、送受信部と、
前記デタッチ手続きの完了に基づいて、接続先を前記第1のコアネットワークから前記第2のコアネットワークに変更する、
制御部と、を備え、
前記送受信部は、
前記デタッチ手続きにおいて、デタッチ要求メッセージをCPF(Control Plane Function)から受信し、
前記アタッチ手続きにおいて、アタッチ要求メッセージをMME(Mobility ManagementEntity)に送信し、
前記デタッチ要求メッセージは、接続先を変更することを示す情報を含み、
前記アタッチ要求メッセージは、ハンドオーバーを示す情報を含む、
ことを特徴とする端末装置。 - 前記アタッチ要求メッセージは、さらに、前記MMEを識別する情報、及び/又はPDN接続要求メッセージを含む、
ことを特徴とする請求項1に記載の端末装置。 - 前記送受信部は、
前記デタッチ手続き前に、トラッキングエリア更新受諾メッセージを前記CPFから受信する、トラッキングエリア更新手続きを実行し、
前記トラッキングエリア更新受諾メッセージは、前記MMEを識別する情報を含む、
ことを特徴とする請求項2に記載の端末装置。 - 前記デタッチ手続きは、前記第1のコアネットワークにセッションを確立した状態で実行され、
前記制御部は、前記アタッチ手続きの完了に基づいて、前記セッションの接続先を前記第2のコアネットワークに切り替え、
前記PDN接続要求メッセージは、前記セッションを識別する情報、及び/又は前記セッションの接続先であるDN(Data Network)を識別する情報を示す情報を含む、
ことを特徴とする請求項2に記載の端末装置。 - 前記デタッチ要求メッセージは、さらに、前記セッションを識別する情報を含む、
ことを特徴とする請求項4に記載の端末装置。 - 前記送受信部は、
前記デタッチ手続き前に、PDUセッション確立受諾メッセージを前記CPFから受信する、PDUセッション確立手続きを実行し、
前記制御部は、前記PDUセッション確立手続きの完了に基づいて、前記セッションを確立し、
前記PDUセッション確立受諾メッセージは、前記DNを識別する情報を含む
ことを特徴とする請求項4に記載の端末装置。 - CPF(Control Plane Function)であって、
前記CPFは、
デタッチ手続きを実行する送受信部と、
前記デタッチ手続きの完了に基づいて、端末装置の接続先を、第1のコアネットワークから第2のコアネットワークに変更するために、前記端末装置との接続を切断する、制御部と、を備え、
前記送受信部は、
前記デタッチ手続きにおいて、デタッチ要求メッセージを前記端末装置に送信し、
前記デタッチ要求メッセージは、前記端末装置の接続先を変更することを示す情報を含む、
ことを特徴とするCPF。 - 前記デタッチ要求メッセージは、さらに、前記端末装置が再確立すべきセッションを識別する情報を含む、
ことを識別特徴とする請求項7に記載のCPF。 - 前記送受信部は、
前記デタッチ手続き前に、PDUセッション確立受諾メッセージを前記端末装置に送信する、PDUセッション確立手続きを実行し、
前記PDUセッション確立受諾メッセージは、前記セッションが接続するDN(Data Network)を識別する情報を含む
ことを特徴とする請求項8に記載のCPF。 - 前記送受信部は、
前記デタッチ手続き前に、トラッキングエリア更新受諾メッセージを前記端末装置に送信する、トラッキングエリア更新手続きを実行し、
前記トラッキングエリア更新受諾メッセージは、前記デタッチ手続きで、前記端末装置が接続すべきMME(MobilityManagement Entity)を識別するための情報を含む、
ことを特徴とする請求項7に記載のCPF。 - MME(Mobility Management Entity)であって、
前記MMEは、
アタッチ手続きを実行する、送受信部と、
前記アタッチ手続きの完了に基づいて、端末装置の接続先を、第1のコアネットワークから第2のコアネットワークに変更するために、前記端末装置と接続する、
制御部を備え、
前記送受信部は、
前記アタッチ手続きにおいて、アタッチ要求メッセージを前記端末装置から受信し、
前記アタッチ要求メッセージは、ハンドオーバーを示す情報を含む、
ことを特徴とするMME。 - 前記アタッチ要求メッセージは、さらに、PDN接続要求メッセージを含み、
前記PDN接続要求メッセージは、セッションを識別する情報、及び/又は前記セッションの接続先であるDN(Data Network)を識別する情報を示す情報を含む、
ことを特徴とする請求項11に記載のMME。 - 端末装置の通信制御方法であって、
第1のコアネットワークに対してデタッチ手続きを実行するステップと、
前記デタッチ手続きの後、第2のコアネットワークに対してアタッチ手続きを実行するステップと、
前記デタッチ手続きの完了に基づいて、接続先を前記第1のコアネットワークから前記第2のコアネットワークに変更する、
ステップとを有し、
前記デタッチ手続きにおいて、デタッチ要求メッセージをCPF(Control Plane Function)から受信するステップを、さらに、有し、
前記アタッチ手続きにおいて、アタッチ要求メッセージをMME(Mobility ManagementEntity)に送信するステップを、さらに、有し、
前記デタッチ要求メッセージは、接続先を変更することを示す情報を含み、
前記アタッチ要求メッセージは、ハンドオーバーを示す情報を含む、
ことを特徴とする端末装置の通信制御方法。 - 前記アタッチ要求メッセージは、さらに、前記MMEを識別する情報、及び/又はPDN接続要求メッセージを含む、
ことを特徴とする請求項13に記載の端末装置の通信制御方法。 - 前記デタッチ手続き前に、トラッキングエリア更新受諾メッセージを前記CPFから受信する、トラッキングエリア更新手続きを実行するステップを、さらに、有し、
前記トラッキングエリア更新受諾メッセージは、前記MMEを識別する情報を含む、
ことを特徴とする請求項14に記載の端末装置の通信制御方法。 - 前記デタッチ手続きは、前記第1のコアネットワークにセッションを確立した状態で実行され、
前記アタッチ手続きの完了に基づいて、前記セッションの接続先を前記第2のコアネットワークに切り替えるステップを、さらに、有し、
前記PDN接続要求メッセージは、前記セッションを識別する情報、及び/又は前記セッションの接続先であるDN(Data Network)を識別する情報を示す情報を含む、
ことを特徴とする請求項14に記載の端末装置の通信制御方法。 - 前記デタッチ要求メッセージは、さらに、前記セッションを識別する情報を含む、
ことを特徴とする請求項16に記載の端末装置の通信制御方法。 - 前記デタッチ手続き前に、PDUセッション確立受諾メッセージを前記CPFから受信する、PDUセッション確立手続きを実行するステップと、
前記PDUセッション確立手続きの完了に基づいて、前記セッションを確立するステップとを、さらに、有し、
前記PDUセッション確立受諾メッセージは、前記DNを識別する情報を含む
ことを特徴とする請求項16に記載の端末装置の通信制御方法。 - CPF(Control Plane Function)の通信制御方法であって、
デタッチ手続きを実行するステップと、
前記デタッチ手続きの完了に基づいて、端末装置の接続先を、第1のコアネットワークから第2のコアネットワークに変更するために、前記端末装置との接続を切断する、
ステップとを有し、
前記デタッチ手続きにおいて、デタッチ要求メッセージを前記端末装置に送信するステップを、さらに、有し、
前記デタッチ要求メッセージは、接続先を変更することを示す情報を含む、
ことを特徴とするCPFの通信制御方法。 - 前記デタッチ要求メッセージは、さらに、前記端末装置が再確立すべきセッションを識別する情報を含む、
ことを識別特徴とする請求項19に記載のCPFの通信制御方法。 - 前記デタッチ手続き前に、PDUセッション確立受諾メッセージを前記端末装置に送信する、PDUセッション確立手続きを実行するステップを、さらに、有し、
前記PDUセッション確立受諾メッセージは、前記セッションが接続するDN(Data Network)を識別する情報を含む
ことを特徴とする請求項20に記載のCPFの通信制御方法。 - 前記デタッチ手続き前に、トラッキングエリア更新受諾メッセージを前記端末装置に送信する、トラッキングエリア更新手続きを実行するステップを、さらに、有し、
前記トラッキングエリア更新受諾メッセージは、前記デタッチ手続きで、前記端末装置が接続すべきMME(MobilityManagement Entity)を識別するための情報を含む、
ことを特徴とする請求項19に記載のCPFの通信制御方法。 - MME(Mobility Management Entity)の通信制御方法であって、
アタッチ手続きを実行する、ステップと、
前記アタッチ手続きの完了に基づいて、端末装置の接続先を、第1のコアネットワークから第2のコアネットワークに変更するために、前記端末装置と接続する、
ステップとを有し、
前記アタッチ手続きにおいて、アタッチ要求メッセージを前記端末装置から受信するステップを、さらに、有し、
前記アタッチ要求メッセージは、ハンドオーバーを示す情報を含む、
ことを特徴とするMMEの通信制御方法。 - 前記アタッチ要求メッセージは、さらに、PDN接続要求メッセージを含み、
前記PDN接続要求メッセージは、セッションを識別する情報、及び/又は前記セッションの接続先であるDN(Data Network)を識別する情報を示す情報を含む、
ことを特徴とする請求項23に記載のMMEの通信制御方法。
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2017340216A AU2017340216B2 (en) | 2016-10-07 | 2017-08-14 | Terminal apparatus, mobility management entity (MME), control plane function (CPF), and communication control method |
CN201780061859.5A CN110140395B (zh) | 2016-10-07 | 2017-08-14 | 终端装置、移动性管理实体mme、控制平面功能cpf、以及通信控制方法 |
EP17858074.2A EP3525526A4 (en) | 2016-10-07 | 2017-08-14 | TERMINAL DEVICE, MOBILITY MANAGEMENT ENTITY (MME), CONTROL PLAN FUNCTION (CPF) AND COMMUNICATION CONTROL METHOD |
US16/339,651 US11140599B2 (en) | 2016-10-07 | 2017-08-14 | Terminal apparatus, mobility management entity (MME), control plane function (CPF), and communication control method |
NZ752976A NZ752976B2 (en) | 2016-10-07 | 2017-08-14 | Terminal apparatus, mobility management entity (mme), control plane function (cpf), and communication control method |
MX2019003991A MX2019003991A (es) | 2016-10-07 | 2017-08-14 | Aparato terminal, entidad de gestión de movilidad (mme), función del plano de control (cpf) y método de control de comunicación. |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016198806A JP2019208089A (ja) | 2016-10-07 | 2016-10-07 | 端末装置、MME(Mobility Management Entity)、CPF(Control Plane Function)、及び通信制御方法 |
JP2016-198806 | 2016-10-07 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018066234A1 true WO2018066234A1 (ja) | 2018-04-12 |
Family
ID=61830848
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2017/029303 WO2018066234A1 (ja) | 2016-10-07 | 2017-08-14 | 端末装置、MME(Mobility Management Entity)、CPF(Control Plane Function)、及び通信制御方法 |
Country Status (7)
Country | Link |
---|---|
US (1) | US11140599B2 (ja) |
EP (1) | EP3525526A4 (ja) |
JP (1) | JP2019208089A (ja) |
CN (1) | CN110140395B (ja) |
AU (1) | AU2017340216B2 (ja) |
MX (1) | MX2019003991A (ja) |
WO (1) | WO2018066234A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112154708A (zh) * | 2018-05-21 | 2020-12-29 | 夏普株式会社 | 用户装置、控制装置以及通信控制方法 |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2019145858A (ja) * | 2016-06-30 | 2019-08-29 | シャープ株式会社 | 端末装置、制御装置、及び通信制御方法 |
US10742522B2 (en) * | 2016-11-14 | 2020-08-11 | Huawei Technologies Co., Ltd. | Creation and modification of shareable slice instances |
US10716083B2 (en) * | 2016-12-15 | 2020-07-14 | Lg Electronics Inc. | Tracking area assignment method in wireless communication system and device therefor |
JP6961729B2 (ja) * | 2017-06-17 | 2021-11-05 | エルジー エレクトロニクス インコーポレイティドLg Electronics Inc. | 無線通信システムにおける端末の登録方法およびそのための装置 |
EP3534669B1 (en) * | 2017-08-14 | 2021-06-23 | HTC Corporation | Device and method of handling an interworking procedure |
US11503659B2 (en) * | 2021-01-15 | 2022-11-15 | T-Mobile Usa, Inc. | Routing optimization for service capability exposure |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010053066A1 (ja) * | 2008-11-06 | 2010-05-14 | シャープ株式会社 | 制御局、移動局、移動通信システム及び移動通信方法 |
US20160080981A1 (en) * | 2014-09-11 | 2016-03-17 | Telefonaktiebolaget L M Ericsson (Publ) | Fast wifi to lte handover |
US20160277985A1 (en) * | 2014-06-23 | 2016-09-22 | Huawel Technologies Co., Ltd. | Network handover method, and terminal |
JP2016198806A (ja) | 2015-04-13 | 2016-12-01 | 株式会社Hanaエンジニアリング | 半凝固合金の鍛造方法及びその鍛造装置 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2552845A (en) * | 2016-08-12 | 2018-02-14 | Nec Corp | Communication system |
-
2016
- 2016-10-07 JP JP2016198806A patent/JP2019208089A/ja active Pending
-
2017
- 2017-08-14 US US16/339,651 patent/US11140599B2/en active Active
- 2017-08-14 WO PCT/JP2017/029303 patent/WO2018066234A1/ja unknown
- 2017-08-14 EP EP17858074.2A patent/EP3525526A4/en active Pending
- 2017-08-14 AU AU2017340216A patent/AU2017340216B2/en active Active
- 2017-08-14 CN CN201780061859.5A patent/CN110140395B/zh active Active
- 2017-08-14 MX MX2019003991A patent/MX2019003991A/es unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010053066A1 (ja) * | 2008-11-06 | 2010-05-14 | シャープ株式会社 | 制御局、移動局、移動通信システム及び移動通信方法 |
US20160277985A1 (en) * | 2014-06-23 | 2016-09-22 | Huawel Technologies Co., Ltd. | Network handover method, and terminal |
US20160080981A1 (en) * | 2014-09-11 | 2016-03-17 | Telefonaktiebolaget L M Ericsson (Publ) | Fast wifi to lte handover |
JP2016198806A (ja) | 2015-04-13 | 2016-12-01 | 株式会社Hanaエンジニアリング | 半凝固合金の鍛造方法及びその鍛造装置 |
Non-Patent Citations (3)
Title |
---|
"Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System; (Release 14", 3GPP TR 23.799 |
SAMSUNG: "Solution for key issue 3: mobility support for interworking between the NextGen core and EPC", 3GPP TSG-SA WG2#115 S 2-162721, 23 May 2016 (2016-05-23), XP051109470 * |
See also references of EP3525526A4 |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112154708A (zh) * | 2018-05-21 | 2020-12-29 | 夏普株式会社 | 用户装置、控制装置以及通信控制方法 |
EP3799513A4 (en) * | 2018-05-21 | 2021-10-20 | Sharp Kabushiki Kaisha | USER DEVICE, CONTROL DEVICE AND COMMUNICATION CONTROL PROCESS |
US11576219B2 (en) | 2018-05-21 | 2023-02-07 | Sharp Kabushiki Kaisha | User equipment, control apparatus, and communication control method |
Also Published As
Publication number | Publication date |
---|---|
EP3525526A1 (en) | 2019-08-14 |
JP2019208089A (ja) | 2019-12-05 |
US11140599B2 (en) | 2021-10-05 |
MX2019003991A (es) | 2019-09-19 |
AU2017340216A1 (en) | 2019-05-23 |
EP3525526A4 (en) | 2020-05-27 |
NZ752976A (en) | 2021-10-29 |
AU2017340216B2 (en) | 2022-03-03 |
US20200053615A1 (en) | 2020-02-13 |
CN110140395B (zh) | 2022-01-14 |
CN110140395A (zh) | 2019-08-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018066234A1 (ja) | 端末装置、MME(Mobility Management Entity)、CPF(Control Plane Function)、及び通信制御方法 | |
WO2018030474A1 (ja) | 端末装置、ゲートウェイ、及び通信制御方法 | |
WO2018147220A1 (ja) | 端末装置、コアネットワーク装置、及び通信制御方法 | |
CN110892783B (zh) | 终端装置以及核心网内的装置 | |
JP6748220B2 (ja) | Ue、コアネットワーク装置、ueの通信方法及びコアネットワークの通信方法 | |
WO2019031433A1 (ja) | 端末装置、コアネットワーク内の装置、及び通信制御方法 | |
WO2018008603A1 (ja) | 端末装置、制御装置、ゲートウェイ、及び通信制御方法 | |
WO2017199957A1 (ja) | 端末装置、SME(Session Management Entity)、および通信制御方法 | |
WO2019031434A1 (ja) | 端末装置、コアネットワーク内の装置、及び通信制御方法 | |
WO2018128127A1 (ja) | 端末装置、コアネットワーク装置、及び通信制御方法 | |
CN110249663B (zh) | 终端装置、核心网装置、通信系统、以及通信控制方法 | |
WO2018128126A1 (ja) | 端末装置、ネットワーク機能部、基地局装置、通信システム、及び通信制御方法 | |
WO2012142889A1 (zh) | 一种网关的选择方法、实现设备及系统 | |
WO2017199955A1 (ja) | 端末装置、SME(Session Management Entity)、および通信制御方法 | |
WO2018147219A1 (ja) | 端末装置、コアネットワーク装置、及び通信制御方法 | |
WO2018066235A1 (ja) | 端末装置、MME(Mobility Management Entity)、CPF(Control Plane Function)、及び通信制御方法 | |
US11844015B2 (en) | UE and communication control method for establishing a PDU session in a public land mobile network | |
WO2017199954A1 (ja) | 端末装置、SME(Session Management Entity)、および通信制御方法 | |
WO2020100718A1 (ja) | Ue及び通信制御方法 | |
WO2021029381A1 (ja) | Ue、及び通信制御方法 | |
WO2020153126A1 (ja) | Ue | |
JP7216553B2 (ja) | Ue、コアネットワーク装置、及び通信制御方法 | |
WO2018128125A1 (ja) | 端末装置、ネットワーク機能部、基地局、通信システム、及び通信制御方法 | |
WO2021029383A1 (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: 17858074 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2017858074 Country of ref document: EP Effective date: 20190507 |
|
ENP | Entry into the national phase |
Ref document number: 2017340216 Country of ref document: AU Date of ref document: 20170814 Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: JP |