+

WO2018128125A1 - Dispositif terminal, unité de fonction réseau, station de base, système de communication et procédé de commande de communication - Google Patents

Dispositif terminal, unité de fonction réseau, station de base, système de communication et procédé de commande de communication Download PDF

Info

Publication number
WO2018128125A1
WO2018128125A1 PCT/JP2017/046626 JP2017046626W WO2018128125A1 WO 2018128125 A1 WO2018128125 A1 WO 2018128125A1 JP 2017046626 W JP2017046626 W JP 2017046626W WO 2018128125 A1 WO2018128125 A1 WO 2018128125A1
Authority
WO
WIPO (PCT)
Prior art keywords
identification information
network
terminal device
pdn
information
Prior art date
Application number
PCT/JP2017/046626
Other languages
English (en)
Japanese (ja)
Inventor
陽子 久下
真史 新本
Original Assignee
シャープ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by シャープ株式会社 filed Critical シャープ株式会社
Publication of WO2018128125A1 publication Critical patent/WO2018128125A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/06—Interfaces between hierarchically different network devices between gateways and public network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Definitions

  • the present invention relates to a terminal device, a network function unit, a base station, a communication system, and a communication control method.
  • 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 is being studied as a function that allows an operator to finely adjust a network in scenarios in various markets that require various requirements.
  • network slicing technology it is considered to configure one or a plurality of network slices in one PLMN.
  • each network slice is associated with a network slice type according to the requirements, the market, and the type of terminal connected to the network slice.
  • NextGen is studying a network slice technology that virtually divides the core network. Furthermore, in the network slice technology, it is considered that one or a plurality of network slices are configured in a core network, and each network slice is managed by being associated with at least one network slice type. In addition, it is considered that one network slice type can support connection to multiple PDNs or DNs.
  • the present invention has been made in view of such circumstances, and an object thereof is to provide communication control means for realizing management of each setting related to communication.
  • the terminal device transmits an attach request message including first identification information and second identification information to a network function unit configured in a core network.
  • a reception unit that receives an attach acceptance message including the identification information of 3 and a session between the terminal device and the PDN (Packet Data Network) indicated by the third identification information via the core network based on the third identification information
  • a control unit and a transmission unit and a reception unit start transmission / reception of PDN and user data using a session, wherein the first identification information is one or more PDNs requested by the terminal device
  • the second identification information is information indicating a PDN that the terminal device requests preferentially.
  • the first identification information and the second identification information are the connection destination of the terminal device by the network function unit.
  • PDN decision Is used to, third identification information is information indicating the PDN core network permits the connection to the terminal device, and wherein the.
  • the network function unit configured in the core network receives the attach request message including the first identification information and the second identification information from the terminal device, the reception unit, and the first identification Based on the reception of the information and the second identification information, determine the PDN (Packet DataNetwork) of the connection destination of the terminal device, establish a session with the gateway device of the determined PDN, to the control unit and the terminal device, the third A transmitting unit that transmits an attach acceptance message including the identification information of the first identification information, wherein the first identification information is information indicating one or more PDNs requested by the terminal device, and the second identification information is The terminal device is information indicating a PDN that is preferentially requested, and the third identification information is information indicating a PDN that the core network has permitted to connect to the terminal device.
  • the PDN Packet DataNetwork
  • the base station apparatus receives the RRC message including the attach request message including the first identification information and the second identification information, the receiving unit, the first identification information, and the second identification information
  • a control unit that determines a network function unit to which an attach request message is to be transferred, and a transmission / reception unit that transmits an attach request message to the network function unit.
  • the terminal device requests the first identification information. It is information indicating one or a plurality of PDNs, and the second identification information is information indicating PDNs requested by the terminal device preferentially.
  • the communication control method for a terminal device includes a step of transmitting an attach request message including first identification information and second identification information to a network function unit configured in a core network, and a network function unit From the step of receiving the attach acceptance message including the third identification information and the third identification information, a session between the PDN (Packet Data Network) and the terminal device indicated by the third identification information via the core network is performed.
  • PDN Packet Data Network
  • the step of starting transmission / reception of user data with a PDN using a session wherein the first identification information is information indicating one or more PDNs requested by the terminal device,
  • the identification information is information indicating the PDN that the terminal device requests preferentially, and the first identification information and the second identification information are stored in the P of the connection destination of the terminal device by the network function unit.
  • the third identification information is used to determine the DN, and the third identification information is information indicating a PDN that the core network has permitted to connect to the terminal device.
  • the communication control method of the network function unit configured in the core network includes a step of receiving an attach request message including first identification information and second identification information from the terminal device; Based on the reception of the identification information and the second identification information, determining the PDN (Packet DataNetwork) of the connection destination of the terminal device, establishing a session with the gateway device of the determined PDN, to the terminal device, Transmitting an attach acceptance message including the third identification information, wherein the first identification information is information indicating one or more PDNs requested by the terminal device, and the second identification information is The terminal device is information indicating a PDN that is preferentially requested, and the third identification information is information indicating a PDN that the core network has permitted to connect to the terminal device.
  • PDN Packet DataNetwork
  • the step of receiving from the terminal apparatus including the first identification information and the second identification information in the RRC message including the attach request message, and the first identification information And a step of determining a network function unit to which the attach request message is transferred based on the second identification information, and a step of transmitting the attach request message to the network function unit, wherein the first identification information is a terminal device. Is information indicating one or a plurality of PDNs requested, and the second identification information is information indicating PDNs requested preferentially by the terminal device.
  • the terminal device and each device in the core network can manage identifiers and / or parameters necessary for communication. Further, each device can execute communication control based on the set identifier and / or parameter.
  • FIG. 3 is a diagram for explaining an example of the configuration of a core network and an access network in a mobile communication system. It is a figure for demonstrating the detail of a mobile communication system. It is a figure for demonstrating the apparatus structure of UE. It is a figure for demonstrating the memory
  • 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_B, a core network_B190, a PDN (PacketData Network) _A5, and a PDN_B6.
  • UE_A10 only needs to be a wirelessly connectable terminal device, 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.
  • UE User Equipment
  • ME Mobile Equipment
  • MS Mobile Station
  • CIoT Cellular Internet of Things
  • the core network may be a core network_B190, and the access network may be an access network_B. Further, the core network may be a core network device. Alternatively, in the present embodiment, the core network device may be a device that executes part or all of each device and / or processing or function of each device included in the core network_B190.
  • the access network_B may be NextGen RAN_A120 and / or E-UTRAN_A80 and / or WLAN ANc125.
  • the core network_B190 includes NSI (NetworkSlice Instance) _A191 and NSI_B192.
  • the core network B190 is not limited to this, and may include one or a plurality of NSIs.
  • the NSI (Network Slice Instance) in this embodiment is an entity of a network slice (Network Slice) configured by one or more in the core network_B190. That is, the NSI may be a network slice. Further, the NSI in this embodiment may be configured by a virtual NF (Network Function: Network Function Unit) 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.
  • UE_A10 can be connected to the access network and / or the core network. Furthermore, UE_A10 can be connected to PDN_A5 and / or PDN_B6 via an access network and / or a core network, and further transmits / receives user data to / from PDN_A5 and / or PDN_B6.
  • 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.
  • PDN_A5 and PDN_B6 are described as having connectivity with the core network_B190 here, other PDNs may have connectivity with the core network_B190.
  • the PDU session or the PDN connection (hereinafter also referred to as a PDN connection) provides UE_A10 and PDN_A5 and / or PDN_A5 and / or PDN_A5 and / or PDN_A5 and / or PDN_B6 in order to provide a PDU connection service.
  • 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, UPGW_B131, 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 PDN connection may be a session established between UE_A10 and the core network and / or PDN_A5 and / or PDN_B6, such as one or more bearers between each device in the mobile communication system 1. It may be a logical communication path composed of transfer paths.
  • the PDU session may be a connection that UE_A10 establishes between the core network_B190 and the external gateway, a connection that establishes between UE_A10 and UPGW_A130 and / or UPGW_B131, or a PDN A connection such as a connection (Packet Data Network Connection) may be used.
  • a connection Packet Data Network Connection
  • the PDN connection may be connectivity and / or connection between UE_A10 and PGW_A30 via eNB (evolved) NodeB) _A45 and / or SGW (ServingGateway) _A35, or eNB_A45 and / or MME (Mobility) Management Entity) It may be connectivity and / or connection between UE_A 10 and SCEF_A 46 via _A40. Further, the PDU session may be connectivity and / or connection between UE_A 10 and UPGW_A 130 via NR node_A122.
  • the UE_A 10 can execute transmission / reception of user data using a PDU session or a PDN connection with a device such as an application server arranged in the PDN_A 5 and / or the PDN_B 6.
  • 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 identification information, access network identification information, DNN (Domain Network Name), service type, and network slice type 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. Further, the NSI identification information is information for identifying the NSI, and may be NSI ID or Slice Instance ID hereinafter.
  • 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 and PDN_B6 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 and PDN_B6 may include connected communication terminals. Therefore, connecting to PDN_A5 and / or PDN_B6 may be connecting to a communication terminal or server device arranged in PDN_A5 and / or PDN_B6. Furthermore, transmitting / receiving user data to / from PDN_A5 and / or PDN_B6 may be transmitting / receiving user data to / from a communication terminal or a server device arranged in PDN_A5 and / or PDN_B6. Note that PDN_A5 and / or PDN_B6 may be expressed as DN, and DN may be expressed as PDN_A5 and / or PDN_B6.
  • the access network is a wireless network connected to UE_A10 and / or the core network.
  • the access network may be a 3GPP access network or a non-3GPP access network.
  • the 3GPP access network may be E-UTRAN (Evolved Universal Terrestrial Radio Access Network) _A80, NextGen RAN (NextGeneration Radio Access Network) _A120, and the non-3GPP access network may be 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_B190 may be an EPC (Evolved Packet System Core) that configures EPS (Evolved Packet System) or an NGC (Next Generation (NextGen) Core) that configures NGS (NextGen System (Next Generation System)).
  • 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.
  • FIG. 2 shows an example of the configuration of the core network_B190.
  • the core network_B190 in FIG. 2 (a) includes HSS_A50, PCRF_A60, UPGW (User (Plane Gateway) _A130, CPF (ControlPlane 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-UTRAN80, 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.
  • 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. Note that UPGW_A130 may be SGW_A35 and / or PGW_A30.
  • PGW_A30 is connected to PDN_A5, SGW_A35, and PCRF_A60, and is a relay device that transfers user data as a gateway between PDN_A5 and / or DN and core network_B190. Note that 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_B190. Further, the plurality of gateways may be gateways connecting the core network_B190 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, and E-UTRAN_A80, and is a relay device that transfers user data as a gateway between the core network_B190 and the 3GPP access network (E-UTRAN_A80, NextGen RAN_A120).
  • 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.
  • CPF_A140 is a device connected to UPGW_A130, E-UTRAN_A80, NextGen RAN_A120, WLAN ANc125, HSS_A50 and SCEF_A46.
  • CPF_140 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_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. It may be a shared CP function (CCNF: Common CPNF (Control: PlaneNetwork Function))
  • CPF_A 140 may have connectivity with other NFs, and may be connected to each device via other NFs.
  • CPF_A140 may be MME_A40.
  • 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.
  • a plurality of such control devices may be arranged in the core network_B190, and 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 a plurality of core networks or DCN or NSI, or one or a plurality of 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_B190 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 a plurality of devices arranged in the core network_B190, and is also referred to as a CP function for control information and / or control messages (hereinafter referred to as CPF (Control Plane Function) or Control Plane Network Function). It may be a shared CP function shared among multiple NSIs.
  • 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.
  • SCEF_A46 is connected to PDN_A5 and CPF_A140 or 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_B190.
  • 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_B190. Further, a plurality of gateways connecting the core network_B190 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.
  • HSS_A50 is connected to MME_A40 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.
  • HSS_A50 may be a Subscriber Repository that stores subscriber information.
  • PCRF_A60 is connected to UPGW_A130 or PGW_A30 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.
  • 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.
  • NextGen RAN_A120 is a 5G access network and includes NR node (New RadioAccess 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 configured by E-UTRA and / or NextGen RA.
  • 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.
  • 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.
  • NSI_A191 is configured with UPGW_A130, UPGW_B131, and CPF_A140.
  • UPGW_C132 and CPF_B141 are configured in NSI_B192. Furthermore, CPF_A140 and CPF_B141 may have connectivity with HSS_A50. That is, one HSS may be shared by one or a plurality of NSIs.
  • UPGW_A130 is a GW device between PDN_A5 and NSI_A191 and core network_B190
  • UPGW_B131 is a GW device between PDN_B6, NSI_A191 and core network_B190.
  • UPGW_C132 is a GW device between PDN_C7, NSI_B192, and core network_B190.
  • UE_A10 has direct connectivity with UPGW_A130 and / or UPGW_B131 and / or UPGW_C132
  • a UPF User-PlaneFunction: UP function
  • UP function User-PlaneFunction: UP function
  • 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 the state in which UE_A10 is registered in EPC and the state in which NUE is registered in NGC.
  • 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 an ID of UE_A10 or ME, and may be, for example, IMEI (International Mobile Equipment Identity) or IMEISV (IMEI Software Version).
  • MSISDN represents the basic telephone number of UE_A10.
  • the MSISDN stored in 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_140.
  • 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. Further, the APN can also be used as information for selecting a gateway such as PGW_A30 / UPGW_A130 that connects the core network A_90.
  • 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.
  • UE Network Capability includes security algorithms and key derivation functions supported by UE_A10.
  • MS Network Capability is information including one or more pieces of information necessary for SGSN_A 42 for UE_A 10 having 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 identifying the DN of the establishment destination of the PDU session, DNN (Domain Network Name).
  • 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.
  • the 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_B190 and a UE context used when connecting to the core network_B190.
  • the UE context used when connecting to the core network_B190 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.
  • each device means MME_A40 and CPF_A140.
  • FIG. 7 shows the device configuration of each device. As illustrated, each device includes 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 each device.
  • 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_140 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_140.
  • 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_140 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, NRnode ID, 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 device configurations of PGW_A30, UPGW_A130, UPGW_B131, and UPGW_C132.
  • each device means PGW_A30, UPGW_A130, UPGW_B131, and UPGW_C132.
  • each device 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.
  • 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 the UPGW_A130 to connect with the PCRF_A60 and / or CPF_A140 and / or PDN_A5.
  • the network connection unit_D1020 is a functional unit for the UPGW_B131 to connect to the PCRF_A60 and / or CPF_A140 and / or PDN_B6.
  • the network connection unit_D1020 is a functional unit for the UPGW_C132 to connect with the PCRF_A60 and / or CPF_A140 and / or PDN_B6.
  • 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_B190.
  • 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 network is an access network and / or core network_B190 and / or PDN_A5. Further, the network may indicate any device included in the access network and / or the core network_B190 and / or the PDN_A5. That is, when the network performs message transmission / reception and / or procedures, it means that devices in the network perform message transmission / reception and / or procedures.
  • DNN Domain Network Name
  • the DNN may be associated with a service type. Further, the DNN may be an APN.
  • 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.
  • the tracking area may be TA (Tracking Area).
  • the TA (Tracking Area) list in this embodiment may be a group of information indicating a list of tracking areas in which the network can establish a PDU session with UE_A10.
  • the network slice type in the present embodiment is a type of network slice assigned to one or a plurality of NSIs that are classified based on the requirements, the market, or the type of UE connected to the NSI.
  • One or more NSI or network slices are associated with one network slice type.
  • the UE and each functional unit may store a network slice type and a service in association with each other.
  • the NSI type may be a network slice type.
  • the network slice type may be information for resolving one or a plurality of network slice instances associated with the network slice type.
  • the plurality of network slice instances associated with one network slice type may be network slices included in a single PLMN.
  • the network slice included in the PLMN may be a network slice associated with a single PLMN, or may be a network slice instance provided by a telecommunications carrier that manages or operates the PLMN.
  • the multi-parallel DN connection capability indicates that it has a function of simultaneously connecting to a plurality of DNs in the PLMN.
  • a UE having multi-concurrent DN connection capability may connect to a plurality of DNs by establishing a PDU session for each DN.
  • the UE performs an attach procedure and / or a PDU session establishment procedure for each DN to be connected, and establishes connectivity to a plurality of DNs.
  • a connection may be a multi-concurrent PDU session or a multi-concurrent PDN connection.
  • multi-concurrent DN connection capability is capability information that indicates that UE_A10 can establish connectivity to one or more DNs for a single network slice type that requires the establishment of connectivity. It may be.
  • connectivity to a plurality of DNs may be established by different PDU sessions for each DN. That is, for a single network slice type, the UE and network may establish multiple PDU sessions.
  • an IP address or an IPv6 network prefix may be assigned for each PDU session by a GW serving as an IP anchor point that connects to different DNs.
  • the connectivity to the plurality of DNs described above may be associated with a single network slice instance, or for each connectivity.
  • the network slice instances associated with can be different.
  • the term “connectivity is associated with a network instance” may mean that the connectivity is established via a communication path via one or more gateways configured in association with a network slice instance. In other words, connectivity being associated with a network instance may indicate that connectivity is established via the network instance.
  • the first identification information in the present embodiment is information for identifying the network slice type and / or service type. Furthermore, the first identification information may be NSSAI (Network Slice selectionAssistance Information).
  • NSSAI Network Slice selectionAssistance Information
  • the second identification information in this embodiment is an information group indicating a PDN or DN list.
  • the second identification information may include information that identifies one or more PDNs or DNs.
  • the second identification information may include one or a plurality of DNNs or APNs (Access (Point Name).
  • the second identification information may be managed for each network slice type. Therefore, if UE_A10 can establish connectivity to multiple network slice types, it may have a DNN list that can establish connectivity for each network slice type, and each DNN list has a different DNN. It may consist of groups. In other words, the second identification information may be information managed in association with the first identification information.
  • the third identification information is identification information indicating a PDN.
  • the third identification information may be information indicating any one of one or a plurality of PDNs indicated by the second identification information.
  • the third identification information may be DNN or APN.
  • the third identification information may be information indicating a DNN or APN that UE_A10 requests to connect with priority among one or a plurality of DNNs or APNs indicated by the second identification information.
  • the fourth identification information is identification information indicating that multi-home DN connection capability is provided. Further, the fourth identification information may be UE capability information. Further, the fourth identification information may be information obtained by combining the fourth identification information and the fifth identification information. In this case, the fourth identification information may be identification information having both the meanings of the fourth identification information and the fifth identification information.
  • the fifth identification information is identification information indicating that it has multi-parallel DN connection capability. Further, the fifth identification information may be UE capability information. Further, the fifth identification information may be information obtained by combining the fourth identification information and the fifth identification information. In this case, the fourth identification information may be identification information having both the meanings of the fourth identification information and the fifth identification information.
  • the sixth identification information may be identification information indicating a request for connection to a new DN.
  • the sixth identification information may be information indicating that a PDU session or a PDN connection has already been established in the same PLMN.
  • the sixth identification information may be information indicating an already established PDU session.
  • the sixth identification information may be an identification information group configured by information indicating one or a plurality of PDU sessions, or may indicate one or a plurality of PDU sessions by the sixth identification information. Good.
  • the sixth identification information may be information indicating that a multi-home DN connection or a multi-parallel DN connection is requested to request an additional connection to a new DN.
  • the sixth identification information may be identification information for identifying a PDU session already established for a multi-home DN connection or a multi-parallel DN connection.
  • the sixth identification information may be information for identifying a network slice type or a network slice type associated with an already established multi-home DN connection or multi-parallel DN connection.
  • the network has never been connected to a multi-home DN connection or a multi-concurrent DN connection.
  • the network may recognize that a new connection is required for either one or more DNs allowed for multi-home DN connections or multi-concurrent DN connections.
  • the network has never been connected to the multi-home DN connection or the multi-parallel DN connection, and UE_A10 is the network. May require a new connection to one or more DNs allowed for multi-homed DN connections or multi-concurrent DN connections.
  • the network is already connected to one or more DNs for a multi-homed DN connection or a multi-parallel DN connection. And the network may recognize that it is required to further connect to either one or more DNs allowed for multi-homed DN connections or multi-concurrent DN connections.
  • UE_A10 is already connected to the network with one or more DNs for multi-homed DN connections or multi-concurrent DN connections. In certain circumstances, it may be required to further connect to either one or more DNs allowed for multi-homed DN connections or multi-concurrent DN connections.
  • the tenth identification information is identification information indicating a network slice type permitted to be established.
  • the tenth identification information may be an information group including identification information indicating a plurality of network slice types. Further, the tenth identification information may be information indicating that the request from the UE is permitted.
  • the tenth identification information may be information indicating that the UE_A 10 has connected to the network slice instance corresponding to the network slice type requesting the connection and / or has permitted the connection.
  • the eleventh identification information is identification information indicating a DN to which the UE is connected through a PDU session permitted to be established.
  • the eleventh identification information may be a DNN or an APN.
  • the eleventh identification information may be identification information indicating a plurality of DNs or a set of identification information indicating a plurality of DNs. That is, the eleventh identification information may be composed of a plurality of DNNs and / or APNs. Further, the eleventh identification information may be information indicating that the request from the UE is permitted.
  • the DNN list indicated by the second identification information transmitted by the UE_A 10 may be information indicating a DN for which connectivity is established and / or connection is permitted.
  • it may be information indicating a DN for which connectivity is established and / or connection is permitted for the network slice type for which the UE_A 10 requests connectivity. Therefore, the eleventh identification information may be information managed in association with the network slice type.
  • the twelfth identification information is a list of network slice types.
  • the twelfth identification information is an identification information group indicating a list of NSI types that the network permits connection to the UE.
  • the twelfth identification information is an identification information group including identification information indicating network slice types to which the UE can connect.
  • the twelfth identification information may be configured by identification information indicating one or a plurality of NSI types.
  • the thirteenth identification information is identification information for identifying a DN that allows the network to connect to the UE.
  • the network may allow the UE to connect to a plurality of DNs, and the thirteenth identification information may be configured by one or a plurality of DNNs.
  • the connectable DNs may change according to the position of UE_A10.
  • connectable DNs may be managed according to the position of the tracking area or the like.
  • the thirteenth identification information may be identification information including a list of DNs permitted to be connected and a list of connectable DNs.
  • the thirteenth identification information may be information associated with a network slice type. Therefore, when UE_A10 establishes connectivity for multiple network slice types, it manages the list of DNs that are allowed to connect to each network slice and the list of connectable DNs to notify UE_A10. May be.
  • the 14th identification information is identification information indicating the multihome DN connection capability of the network. Further, the fourteenth identification information may be NW capability information.
  • the fifteenth identification information is information indicating permission of multihomed DN connection.
  • the fifteenth identification information may be information indicating non-permission of multi-DN connection.
  • the fourteenth identification information and the fifteenth identification information may be single identification information including the meaning of each identification information. Therefore, in this embodiment, when it is described that the 14th identification information and the 15th identification information are transmitted or included in the control message, the two identification information are transmitted as single identification information having both meanings. Or may be included in the control message.
  • the sixteenth identification information is information indicating that the UE is located in an area where the network restricts multihomed DN connection. Further, the sixteenth identification information may be information indicating an area where the network restricts multihomed DN connection.
  • the seventeenth identification information is information indicating that the UE is located in an area where the network permits multi-home DN connection. Further, the seventeenth identification information may be information indicating an area in which the network permits multihomed DN connection.
  • the eighteenth identification information is identification information indicating the multi-parallel DN connection capability of the network. Further, the fourteenth identification information may be NW capability information.
  • the 19th identification information is information indicating permission of multi-concurrent DN connection.
  • the nineteenth identification information may be information indicating non-permission of multi-concurrent DN connection.
  • the nineteenth identification information may be eighteenth identification information.
  • the eighteenth identification information and the nineteenth identification information may be single identification information including the meaning of each identification information. Therefore, in this embodiment, when it is described that the 18th identification information and the 19th identification information are transmitted or included in the control message, the two identification information are transmitted as single identification information having both meanings. Or may be included in the control message.
  • the 20th identification information is information indicating that the UE is located in an area where the network restricts multi-parallel DN connection. Further, the twentieth identification information may be information indicating an area where the network restricts multi-concurrent DN connection.
  • the 21st identification information is information indicating that the UE is located in an area where the network permits multi-parallel DN connection. Furthermore, the 21st identification information may be information indicating an area where the network permits multi-parallel DN connection.
  • the 22nd identification information may be information indicating that session switching has occurred.
  • the 22nd identification information may be an IP address updated by session switching.
  • the 22nd identification information may be associated with the 11th identification information.
  • the 30th identification information may be information indicating a reason for rejecting the UE_A10 request.
  • the 30th identification information may be rejectrecause value.
  • the thirtieth identification information may be information indicating that the network does not support connection to the NSI type and / or PDN requested by UE_A10.
  • the thirtieth identification information may be information indicating that the user is in an area that cannot be connected to the NSI specified by UE_A10.
  • each device executes an initial procedure, whereby UE_A10 establishes a PDU session via the core network_B190.
  • this procedure refers to an initial procedure, and each procedure includes an attach procedure to PDN_A5, a PDU session establishment procedure to PDN_A5, and a tracking area update procedure to PDN_A5. Details of each procedure will be described later.
  • each device first executes an attach procedure (S1400) to PDN_A5, and transitions to a state in which UE_A10 is connected to the network.
  • each device executes a PDU session establishment procedure (S1402) to PDN_A5 to establish a session to PDN_A5.
  • each device may execute an attach procedure to PDN_B6 and transition to a state in which UE_A10 is connected to the network.
  • each device may execute a PDU session establishment procedure to PDN_B6 to establish a session to PDN_B6.
  • the attach procedure to PDN_B6 and the PDU session establishment procedure to PDN_B6 can be described by using UPGW_B131 instead of UPGW_A130 in the attach procedure to PDN_A5 and the PDU session establishment procedure to PDN_A5.
  • the tracking area update procedure (S1408) to PDN_A5 may be executed.
  • the tracking area update procedure for PDN_B6 may be executed after the establishment of the PDU session to PDN_B6.
  • the attach procedure refers to the attach procedure to PDN_A5
  • the PDU session establishment procedure refers to the PDU session establishment procedure to PDN_A5
  • the tracking area update procedure refers to the tracking area update procedure to PDN_A5.
  • Each device may exchange various capability information and / or various request information of each device in the attach procedure 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 by the attach procedure, each device does not need to exchange various information and / or negotiate various requests by the PDU session establishment procedure. Conversely, if each device does not exchange various information and / or negotiate various requests in the attach procedure, it may exchange various information and / or negotiate various requests in the PDU session establishment procedure. . Not limited to this, each device may exchange various information and / or negotiate various requests in the attach procedure, or exchange various information and / or negotiate various requests in the PDU session establishment procedure. Good.
  • UE_A10 may transmit one or more pieces of identification information among the first to sixth pieces of identification information to core network_B190.
  • the core network_B190 receives one or more pieces of identification information from the first to sixth pieces of identification information from the UE_A10, and further sends one piece or more of pieces of identification information from the tenth piece of identification information to the UE_A10. May be.
  • UE_A10 may transmit one or more pieces of identification information from the first to sixth identification information to the core network_B190 by the attach procedure, and may not transmit by the PDU session establishment procedure.
  • the core network_B190 may transmit one or more pieces of identification information among the tenth to twenty-first pieces of identification information to the UE_A10 by the attach procedure and not by the PDU session establishment procedure.
  • each device may transmit UE_A10 to core network_B190 in the PDU session establishment procedure without transmitting one or more pieces of identification information from the first to sixth identification information in the attach procedure.
  • the core network_B190 may transmit one or more pieces of identification information among the first to sixth pieces of identification information to the UE_A10 by the PDU session establishment procedure without transmitting by the attach procedure.
  • UE_A10 may transmit the identification information not transmitted in the attach procedure among the core network_B190 and the first to sixth identification information in the PDU session establishment procedure.
  • the core network_B190 may transmit, to the UE_A10, identification information that has not been transmitted in the attach procedure among the 10th to 21st identification information in the PDU session establishment procedure.
  • each device may send and receive during the attach procedure.
  • each device When managing in association with a PDU session and / or EPS bearer, each device is in the process of establishing a PDU session. You may send and receive.
  • each device may execute the PDU session establishment procedure in the attach procedure or after the attach procedure is completed.
  • each device may establish a PDU session based on the completion of the attach procedure.
  • each device executes a tracking area update procedure (S1408).
  • the tracking area update procedure may be executed at an arbitrary timing after the PDU session is established.
  • Each device may exchange various request information in the tracking area update procedure. For example, in the tracking area update procedure for PDN_A5, UE_A10 may transmit one or more pieces of identification information among the first to sixth pieces of identification information to core network_B190. Further, the core network_B190 may transmit one or more pieces of identification information among the tenth to twenty-first 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 refers to an attach procedure to PDN_A5.
  • the attach procedure is a procedure for UE_A10 to lead and connect to a network (access network and / or core network_B190 and / or NSI and / or PDN). If the UE_A10 is not connected to the core network_B190 and / or NSI_A191, this procedure can be executed at any timing such as when the terminal is turned on. In other words, the UE_A 10 may start this procedure at an arbitrary timing as long as the UE_A 10 is not registered in the core network_B190 and / or NSI_A191 (EMM-DEREGISTERED). Also, each device may transition to a registration state (EMM-REGISTERED) based on completion of the attach procedure.
  • the attach procedure is executed at an arbitrary timing even if the UE_A10 is registered in the core network_B190 and / or NSI_A191. May be.
  • the PDU session establishment procedure refers to a PDU session establishment procedure for PDN_A5.
  • this procedure refers to the PDU session procedure.
  • This procedure is a procedure for each device to establish a PDU session. Each device may execute this procedure in a state where the attach procedure has been completed, or may be executed in the attach procedure. Each device may start this procedure at an arbitrary timing after the attach procedure.
  • each device may establish a PDU session based on completion of the PDU session establishment procedure.
  • each device may establish a plurality of PDU sessions by executing this procedure a plurality of times.
  • UE_A10 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 transmits an RRC (RadioResource Control) message including a NAS (Non-Access-Stratum) message including a PDU session establishment request message to NR node_A122, and includes a NAS message including a PDU session establishment request message.
  • RRC RadioResource Control
  • the NR node_A 122 that has received the RRC message selects CPF_A 140 as the NF or shared CP function of the NAS message routing destination including the PDU session establishment request message, and transmits the NAS message including the PDU session establishment request message to CPF_A 140.
  • the NR node_A 122 may select the routing destination NF or the shared CP function based on the first identification information and / or the second identification information and / or the third identification included in the RRC message. For example, the NR nod_A 122 may select an NSI that supports a network slice type or a service type indicated by the received first identification information, and may select an NF or a shared CP function included in the NSI. In addition, or NR nod_A122 selects a PDN to be connected from the PDN list indicated by the received second identification information, and selects an NF or shared CP function included in the NSI that supports connection to the selected PDN. Also good.
  • NR nod_A 122 may select an NF or a shared CP function included in the NSI that supports connection to the PDN indicated by the received second identification information.
  • NFNFnode_A122 may be selected according to the operator policy or the network policy without depending on these.
  • the NR node_A 122 may select an appropriate NF or CP function in consideration of the plurality of pieces of information.
  • the NRnode_A122 selects CPF_A140 as the routing destination NF or the shared CP function based on the first identification information. Also good.
  • the PDN indicated by the third identification information is PDN_C7
  • the NR node_A122 based on the third identification information, sends the CPF_B141 included in the NSI_B192 that is the NSI connected to the PDN_C7 to the routing destination NF or shared CP function You may choose as
  • NR node_A122 may select CPF_A140 included in NSI_A191 as a routing destination NF or shared CP function based on the operator policy.
  • routing destination NF or shared CP function may be performed not by NR node_A 122 but by a functional unit adjacent to or colocated with NR node_A 122.
  • NR node_A122 and / or NSSF (Network Slice Selection Function) adjacent to the access network may select a routing destination NF or a shared CP function.
  • the UE_A10 includes at least one piece of identification information among the first to sixth pieces of identification information in the NAS message including the PDU session establishment request message and / or the RRC message including the NAS message including the PDU session establishment request message.
  • the UE_A10 request may be indicated by including these pieces of identification information.
  • Each device may indicate the network slice type and / or service type requested by UE_A 10 by transmitting and receiving the first identification information. Alternatively, each device may send and receive first identification information to indicate that UE_A 10 requests a connection that supports a specific network slice type and / or service type. Each device may also indicate that UE_A 10 does not request connection to a specific network slice by emptying the first identification information.
  • each device may indicate the PDN for which UE_A 10 requests connection by transmitting and receiving the second identification information.
  • the second identification information may be a list of DNNs, and may be information indicating that it is required to connect to at least one of these DNNs.
  • Each device may indicate the DNN that UE_A 10 prefers to connect by transmitting and receiving the third identification information. Alternatively, each device transmits and receives the third identification information, so that UE_A10 prioritizes connection to at least one DN among one or more DNs indicated in the DNN list indicated in the second identification information. You may indicate that you are requesting to do. Furthermore, each device may indicate that UE_A10 does not prioritize connection of a specific PDN by emptying the third identification information.
  • each device may indicate that UE_A 10 has multi-home DN connection capability (Capability) by transmitting and receiving the fourth identification information. Furthermore, each device may indicate that UE_A 10 requests to establish a PDU session as a multihomed DN connection by transmitting and receiving the fourth identification information.
  • Capability multi-home DN connection capability
  • each device may indicate that UE_A 10 has multi-parallel DN connection capability (Capability) by transmitting and receiving the fifth identification information. Furthermore, each device may indicate that UE_A 10 requests to establish a PDU session as a multi-concurrent DN connection by transmitting / receiving the fifth identification information.
  • Capability multi-parallel DN connection capability
  • each device may indicate that UE_A 10 requests connectivity to a new PDN by transmitting and receiving sixth identification information.
  • Each device may request the execution of the PDU session establishment request procedure and / or the attach procedure by transmitting / receiving the sixth identification information even when UE_A 10 is registered in the core network_B190.
  • 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 selects the connected PDN and / or UPGW_A130 based on the received first identification information and / or second identification information and / or third identification information, and performs the procedure of (C) in this procedure. Execute and start the procedure (A) in this procedure. For example, when CPF_A 140 receives the third identification information, CPF_A 140 may select UPGW, which is a GW device to the PDN indicated by the third identification information. However, CPF_A 140 may select UPGW and PDN according to the location information of the UE and the network policy regardless of reception of the third identification information. Specifically, even when the second identification information indicating PDN_A5 is received, UPGW_B131 connected to PDN_B6 may be selected based on the network policy.
  • the CPF_A 140 transmits a session creation request message to the selected UPGW_A 130 or the UPGW_A 130 associated with the selected PDN, 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 sixth 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 sixth 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.
  • the PCRF_A60 may include at least the result of the third condition determination in the response message during the IP-CAN session establishment procedure. By including this result, the PCRF_A60 notifies the UPGW_A130 of the result of the third condition determination. May be.
  • 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 (S1508). Furthermore, CPF_A140 receives the session creation response message.
  • 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).
  • 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 EPS bearercontext 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 RRCConnection Setup 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 a plurality of identification information among the 10th to 21st identification information, an IP address, or these identifications in the PDU session establishment acceptance message. Including information may indicate that the request of UE_A10 has been accepted.
  • Each device may indicate the NSI type to which the PDU session established by this procedure is connected by transmitting and receiving the tenth identification information. Furthermore, each device may indicate information for identifying the PDN of the connection destination of the PDU session established by this procedure by transmitting and receiving the eleventh identification information. Each device may indicate that the request of UE_A10 is permitted by transmitting and receiving the eleventh identification information.
  • each device indicates the NSI type that UE_A10 is permitted to connect to in addition to the NSI type to which the PDU session established in this procedure is connected by transmitting and receiving the twelfth identification information.
  • each device indicates an NSI type to which UE_A 10 can be connected by transmitting and receiving the twelfth identification information.
  • the NSI type indicated by the twelfth identification information may be one or more NSI types.
  • each device indicates the PDN that UE_A10 is permitted to connect to in addition to the PDN to which the PDU session established in this procedure is connected by transmitting and receiving the thirteenth identification information.
  • each apparatus may show PDN which UE_A10 can connect by transmitting / receiving 13th identification information.
  • the thirteenth identification information may be associated with the twelfth identification information.
  • a plurality of thirteenth identification information may be associated with one twelfth identification information.
  • each device may indicate that the network has a multi-home DN connection capability (capability) in this procedure by transmitting and receiving the 14th identification information.
  • Each device may transmit and receive the fourteenth identification information based on the transmission and reception of the fourth identification information.
  • each device may indicate that the multi-home DN connection requested by UE_A10 is permitted by transmitting and receiving the fifteenth identification information. Further, each device may transmit and receive the fifteenth identification information to indicate that the network supports a multihomed DN connection.
  • the fifteenth identification information may be fourteenth identification information.
  • each device may indicate that multi-home DN connection is not permitted by transmitting / receiving the 15th identification information. Furthermore, each device may transmit and receive the fifteenth identification information to indicate that the network does not support multihomed DN connection.
  • each device may transmit and receive the 16th identification information to indicate that UE_A10 is located in an area where the network restricts multihomed DN connection. That is, each device may transmit and receive the 16th identification information to indicate that UE_A10 is not located in an area where the network permits multihomed DN connection. And / or each device may indicate an area where the multi-home DN connection is restricted by transmitting / receiving the sixteenth identification information.
  • the UE_A 10 that has received the information indicating the area where the multi-home DN connection is restricted may store this information. Furthermore, when UE_A10 has already memorized the area where the multihome DN connection is restricted by the network, it may be updated based on the reception of the 16th identification information.
  • each device may transmit and receive the 17th identification information to indicate that UE_A10 is located in an area where the network permits multihomed DN connection. And / or each device may indicate the area where the multi-home DN connection is permitted by transmitting and receiving the 17th identification information.
  • the UE_A 10 that has received the information indicating the area where the multi-home DN connection is permitted may store this information.
  • UE_A10 already stores an area where multi-home DN connection is permitted by the network, it may be updated based on reception of the 17th identification information.
  • each device may indicate that the network has multi-parallel DN connection capability (capability) in this procedure by transmitting and receiving the 18th identification information.
  • Each device may transmit / receive the eighteenth identification information based on the transmission / reception of the fifth identification information.
  • each device may indicate that the multi-parallel DN connection requested by UE_A10 is permitted by transmitting and receiving the 19th identification information. Further, each device may transmit and receive the 19th identification information to indicate that the network supports multi-parallel DN connection.
  • the nineteenth identification information may be eighteenth identification information.
  • each device may indicate that the multi-parallel DN connection is not permitted by transmitting and receiving the 19th identification information. Further, each device may transmit and receive the 19th identification information to indicate that the network does not support multi-parallel DN connection.
  • each device may transmit and receive the 20th identification information to indicate that UE_A10 is located in an area where the network restricts multi-parallel DN connection. That is, each device may transmit / receive the 20th identification information to indicate that UE_A10 is not located in an area where the network permits multi-parallel DN connection. And / or each device may indicate an area where multi-parallel DN connection is restricted by transmitting / receiving the 20th identification information.
  • limited may memorize
  • each device may transmit and receive the 21st identification information to indicate that UE_A10 is located in an area where the network permits multi-parallel DN connection. And / or each device may indicate the area where the multi-parallel DN connection is permitted by transmitting / receiving the 21st identification information.
  • UE_A10 which received the information which shows the area where the multi parallel DN connection was permitted may memorize
  • UE_A10 has already memorized the area where the multi-parallel DN connection is permitted by the network, it may be updated based on the reception of the 21st 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 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. If the second condition is true, the CPF_A 140 transmits a bearer change request message to the UPGW_A 130 (S1526), and starts the procedure (D) in this procedure. Further, UPGW_A 130 receives the bearer change request message and transmits a bearer change response message to CPF_A 140 (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 information indicating an appropriate reason for rejection. 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.
  • the information indicating an appropriate reason for refusal may be thirtieth identification information.
  • each device may indicate that it does not support connection to an NSI and / or PDN included in the NSI type requested by UE_A10 by transmitting and receiving thirtyth identification information.
  • the information may indicate that connection to the NSI and / or PDN included in the NSI type requested by the UE_A 10 is not permitted.
  • 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 UE_A10 receives the tenth identification information, UE_A10 determines that the connection to the requested PDN is established, and starts transmission / reception of user data between UE_A10 and PDN_A5 using the established PDU session.
  • the UE_A 10 when the UE_A 10 receives the 12th identification information and / or the 13th identification information, the UE_A 10 stores the received 12th identification information and / or 13th identification information in the storage unit. If the same information is already stored, the stored information is updated to the received information. Further, when the UE_A 10 performs the attach procedure and the PDU session establishment procedure, the requested NSI type and DNN may be selected from the stored 12th identification information and / or 13th identification information.
  • UE_A10 when UE_A10 receives the 14th identification information and / or UE_A10 receives the 15th identification information, and the 15th identification information indicates that the network supports a multihomed DN connection. If it is information, UE_A10 may continue to execute a procedure for adding a session to PDN_B6.
  • UE_A10 when UE_A10 receives the sixteenth identification information, UE_A10 stores the received sixteenth identification information, and when UE_A10 moves from the area indicated by the sixteenth identification information, the attach procedure or the tracking area again An update procedure may be performed.
  • UE_A10 when UE_A10 receives the 17th identification information, UE_A10 stores the received 17th identification information, and when UE_A10 moves from the area indicated by the 17th identification information, the attach procedure or the tracking area again An update procedure may be performed.
  • UE_A10 when UE_A10 receives the 18th identification information and / or UE_A10 receives the 19th identification information, and the 19th identification information indicates that the network supports multi-parallel DN connection. If it is information, UE_A 10 may continue to perform an attach procedure to PDN_B 6 and / or a PDU session establishment procedure.
  • the UE_A10 when the UE_A10 receives the 20th identification information, the UE_A10 stores the received 20th identification information, and when the UE_A10 moves from the area indicated by the 20th identification information, the attach procedure or the tracking area again. An update procedure may be performed.
  • the UE_A10 when the UE_A10 receives the 21st identification information, the UE_A10 stores the received 21st identification information, and when the UE_A10 moves from the area indicated by the 21st identification information, the attach procedure or the tracking area again An update procedure may be performed.
  • 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.
  • the first condition determination and the third condition determination may be performed regardless of the registration state of the UE in the network. 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.
  • Attaching procedure example An example of a procedure for executing the attach procedure will be described with reference to FIG.
  • this procedure refers to an attach procedure and refers to an attach procedure to PDN_A5.
  • This procedure is a procedure for registering UE_A10 in the core network_B190.
  • each step of this procedure will be described.
  • UE_A10 transmits an attach request message to CPF_A140 via NR node_A122 (S1600), and starts an attach procedure.
  • UE_A10 may send the attach request message including the PDU session establishment request message described above, or request that the PDU session establishment procedure be performed in the attach procedure by including the PDU session establishment request message. May be.
  • UE_A10 transmits an RRC message including an attach request message to NR node_A122 and receives an RRC message including an attach request message
  • NRnode_A122 is configured as CPF_A140 as an NF or a shared CP function as a routing destination of the attach request message. And sends an attach request message to CPF_A140.
  • the NR node_A 122 may select the routing destination NF or the shared CP function based on the tenth identification information included in the RRC message.
  • the attach request message may be a NAS message.
  • the method of selecting the NF or shared CP function of the routing destination by NR node_A122 may be the same as the method during the PDU session establishment procedure.
  • the UE_A 10 may transmit one or more attach request messages for each network slice requesting connection in one RRC message, or may collectively refer to a plurality of attach request messages as an attach request message. Alternatively, UE_A 10 may transmit an attach request message included in the RRC message for each NSI that requests connection.
  • the UE_A10 may include at least one or more pieces of identification information among the first to sixth pieces of identification information in the attach request message and / or the RRC message, and by including these pieces of identification information, the UE_A10 A request may be indicated.
  • Each device may indicate the network slice type and / or service type requested by UE_A 10 by transmitting and receiving the first identification information. Alternatively, each device may send and receive first identification information to indicate that UE_A 10 requests a connection that supports a specific network slice type and / or service type. Each device may also indicate that UE_A 10 does not request connection to a specific network slice by emptying the first identification information.
  • each device may indicate the PDN for which UE_A 10 requests connection by transmitting and receiving the second identification information.
  • the second identification information may be a list of DNNs, and may be information indicating that it is required to connect to at least one of these DNNs.
  • Each device may indicate the DNN that UE_A 10 prefers to connect by transmitting and receiving the third identification information. Alternatively, each device transmits and receives the third identification information, so that UE_A10 prioritizes connection to at least one DN among one or more DNs indicated in the DNN list indicated in the second identification information. You may indicate that you are requesting to do. Furthermore, each device may indicate that UE_A10 does not prioritize connection of a specific PDN by emptying the third identification information.
  • each device may indicate that UE_A 10 has multi-home DN connection capability (Capability) by transmitting and receiving the fourth identification information. Furthermore, each device may indicate that UE_A 10 requests to establish a PDU session as a multihomed DN connection by transmitting and receiving the fourth identification information.
  • Capability multi-home DN connection capability
  • each device may indicate that UE_A 10 has multi-parallel DN connection capability (Capability) by transmitting and receiving the fifth identification information. Furthermore, each device may indicate that UE_A 10 requests to establish a PDU session as a multi-concurrent DN connection by transmitting / receiving the fifth identification information.
  • Capability multi-parallel DN connection capability
  • each device may indicate that UE_A 10 requests connectivity to a new PDN by transmitting and receiving sixth identification information.
  • Each device may request the execution of the PDU session establishment request procedure and / or the attach procedure by transmitting / receiving the sixth identification information even when UE_A 10 is registered in the core network_B190.
  • 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. If the fourth condition is true, CPF_A140 selects NSI and / or UPGW_A130 to be connected based on the received first identification information and / or second identification information and / or third identification information. Then, the procedure (C) in the PDU session establishment procedure is executed, and when the fourth condition is false, these procedures are omitted (S1604).
  • CPF_A140 may select an NSI corresponding to the NSI type requested by UE_A10 based on the first identification information. Further, the CPF_A 140 may select UPGW_A 130 connected to the PDN indicated by the second identification information and the third identification information from the selected NSI based on the second identification information and the third identification information. Alternatively, the CPF_A 140 may comprehensively determine the first to third identification information and select an appropriate NSI and UPGW_A 130.
  • 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 CPF_A 140 may transmit the attach acceptance message to the NR node_A 122 by including it in an S1AP message (for example, Initial-context-setup-request or Downlink-NAS-Transport).
  • the attach acceptance message may be a NAS message.
  • 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.
  • CPF_A140 may include at least one of the identification information of the 10th to 21st identification information, the IP address, or these addresses in the attach acceptance message and / or the S1AP message. Including the identification information may indicate that the request of UE_A10 has been accepted. Further, the NR node_A122 may include one or more pieces of identification information from the 10th to 21st identification information in the RRC message, and by including these identification information, it indicates that the request of the UE_A10 has been accepted. May be.
  • Each device may indicate the NSI type to which the NSI to which the UE_A 10 is connected belongs by this procedure by transmitting and receiving the tenth identification information. Furthermore, each device may indicate information for identifying the connection-target PDN by transmitting and receiving the eleventh identification information. Each device may indicate that the request of UE_A10 is permitted by transmitting and receiving the eleventh identification information.
  • each device shows a list of NSI types that UE_A10 is allowed to connect to in addition to the NSI types that are connected in this procedure by transmitting and receiving the 12th identification information.
  • each device indicates an NSI type to which UE_A 10 can be connected by transmitting and receiving the twelfth identification information.
  • the NSI type indicated by the twelfth identification information may be configured by one or a plurality of NSI types.
  • each device indicates the PDN that UE_A10 is permitted to connect to in addition to the PDN connected in this procedure by transmitting and receiving the thirteenth identification information.
  • each apparatus may show PDN which UE_A10 can connect by transmitting / receiving 13th identification information.
  • the thirteenth identification information may be associated with the twelfth identification information.
  • a plurality of thirteenth identification information may be associated with one twelfth identification information.
  • each device may indicate that the network has multi-home DN connection capability by transmitting and receiving the 14th identification information. Furthermore, each device may indicate that the network supports establishment of a multi-parallel PDU session by transmitting and receiving the 14th identification information. Each device may indicate that the request of UE_A10 has been permitted by transmitting and receiving the 14th identification information.
  • each device may indicate that the multi-home DN connection requested by UE_A10 is permitted by transmitting and receiving the fifteenth identification information. Further, each device may transmit and receive the fifteenth identification information to indicate that the network supports a multihomed DN connection.
  • each device may indicate that multi-home DN connection is not permitted by transmitting / receiving the 15th identification information. Furthermore, each device may transmit and receive the fifteenth identification information to indicate that the network does not support multihomed DN connection.
  • each device may send and receive the 16th identification information to indicate that UE_A10 is located in an area where the network restricts multihomed DN connection. That is, each device may transmit and receive the 16th identification information to indicate that UE_A10 is not located in an area where the network permits multihomed DN connection. And / or each device may indicate an area where the multi-home DN connection is restricted by transmitting / receiving the sixteenth identification information.
  • the UE_A 10 that has received the information indicating the area where the multi-home DN connection is restricted may store this information. Furthermore, when UE_A10 has already memorized the area where the multihome DN connection is restricted by the network, it may be updated based on the reception of the 16th identification information.
  • each device may transmit and receive the 17th identification information to indicate that UE_A10 is located in an area where the network permits multihomed DN connection. And / or each device may indicate the area where the multi-home DN connection is permitted by transmitting and receiving the 17th identification information.
  • the UE_A 10 that has received the information indicating the area where the multi-home DN connection is permitted may store this information.
  • UE_A10 already stores an area where multi-home DN connection is permitted by the network, it may be updated based on reception of the 17th identification information.
  • each device may indicate that the network has multi-parallel DN connection capability (capability) in this procedure by transmitting and receiving the 18th identification information.
  • Each device may transmit / receive the eighteenth identification information based on the transmission / reception of the fifth identification information.
  • each device may indicate that the multi-parallel DN connection requested by UE_A10 is permitted by transmitting and receiving the 19th identification information. Further, each device may transmit and receive the 19th identification information to indicate that the network supports multi-parallel DN connection.
  • the nineteenth identification information may be eighteenth identification information.
  • each device may indicate that the multi-parallel DN connection is not permitted by transmitting and receiving the 19th identification information. Further, each device may transmit and receive the 19th identification information to indicate that the network does not support multi-parallel DN connection.
  • each device may transmit and receive the 20th identification information to indicate that UE_A10 is located in an area where the network restricts multi-parallel DN connection. That is, each device may transmit / receive the 20th identification information to indicate that UE_A10 is not located in an area where the network permits multi-parallel DN connection. And / or each device may indicate an area where multi-parallel DN connection is restricted by transmitting / receiving the 20th identification information.
  • limited may memorize
  • each device may transmit and receive the 21st identification information to indicate that UE_A10 is located in an area where the network permits multi-parallel DN connection. And / or each device may indicate the area where the multi-parallel DN connection is permitted by transmitting / receiving the 21st identification information.
  • UE_A10 which received the information which shows the area where the multi parallel DN connection was permitted may memorize
  • UE_A10 has already memorized the area where the multi-parallel DN connection is permitted by the network, it may be updated based on the reception of the 21st identification information.
  • 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 attach rejection message may include information indicating an appropriate reason for rejection.
  • the information indicating an appropriate reason for refusal may be thirtieth identification information.
  • each device may indicate that it does not support connection to an NSI and / or PDN included in the NSI type requested by UE_A10 by transmitting and receiving thirtyth identification information.
  • the information may indicate that connection to the NSI and / or PDN included in the NSI type requested by the UE_A 10 is not permitted.
  • 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 UE_A10 receives the tenth identification information, UE_A10 determines that the connection to the requested PDN is established, and starts transmission / reception of user data between UE_A10 and PDN_A5 using the established PDU session.
  • the UE_A 10 when the UE_A 10 receives the 12th identification information and / or the 13th identification information, the UE_A 10 stores the received 12th identification information and / or 13th identification information in the storage unit. If the same information is already stored, the stored information is updated to the received information. Further, when the UE_A 10 performs the attach procedure and the PDU session establishment procedure, the requested NSI type and DNN may be selected from the stored 12th identification information and / or 13th identification information.
  • UE_A10 when UE_A10 receives the 14th identification information and / or UE_A10 receives the 15th identification information, and the 15th identification information indicates that the network supports a multihomed DN connection. If it is information, UE_A10 may continue to execute a procedure for adding a session to PDN_B6.
  • UE_A10 when UE_A10 receives the sixteenth identification information, UE_A10 stores the received sixteenth identification information, and when UE_A10 moves from the area indicated by the sixteenth identification information, the attach procedure or the tracking area again An update procedure may be performed.
  • UE_A10 when UE_A10 receives the 17th identification information, UE_A10 stores the received 17th identification information, and when UE_A10 moves from the area indicated by the 17th identification information, the attach procedure or the tracking area again An update procedure may be performed.
  • UE_A10 when UE_A10 receives the 18th identification information and / or UE_A10 receives the 19th identification information, and the 19th identification information indicates that the network supports multi-parallel DN connection. If it is information, UE_A10 may continue to perform a first attach procedure to PDN_B6 and / or a PDU session establishment procedure.
  • the UE_A10 when the UE_A10 receives the 20th identification information, the UE_A10 stores the received 20th identification information, and when the UE_A10 moves from the area indicated by the 20th identification information, the attach procedure or the tracking area again. An update procedure may be performed.
  • the UE_A10 when the UE_A10 receives the 21st identification information, the UE_A10 stores the received 21st identification information, and when the UE_A10 moves from the area indicated by the 21st identification information, the attach procedure or the tracking area again An update procedure may be performed.
  • UE_A10 is not limited to this, and the tracking area update procedure may be started after the completion of this procedure.
  • UE_A10 may start the tracking area update procedure based on the expiration of the first timer.
  • 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.
  • the first condition determination and the third condition determination may be performed based on the sixth identification information included in the attach request message regardless of the registration state of the UE.
  • the 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 refers to the tracking area update procedure, and refers to the tracking area update procedure to PDN_A5.
  • 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 transmits the RRC message including the tracking area update request message to NR node_A122, and receives the RRC message including the tracking area update request message.
  • NR node_A122 is the NF to which the tracking area update request message is routed
  • CPF_A140 is selected as the shared CP function, and an attach request message is transmitted to CPF_A140.
  • the NR node_A 122 may select the routing destination NF or the shared CP function based on the tenth identification information included in the RRC message.
  • the tracking area update request message may be a NAS (Non-Access-Stratum) message.
  • UE_A10 may include at least one or more identification information of the second and third identification information in the tracking area update request message and / or the RRC message, or by including these identification information.
  • UE_A10 request may be indicated.
  • UE_A10 may include the identification information of the PDU session in the tracking area update request message and / or the RRC message.
  • Each device indicates a list of PDNs that UE_A 10 requests to connect by transmitting / receiving the second identification information.
  • the second identification information may be an identification information group including a plurality of DNNs.
  • the PDN list indicated by the second identification information may or may not include a PDN for which a session has already been established.
  • each device may transmit and receive by associating information identifying an already established PDN. Further, the second information may be associated with the third information.
  • each device indicates a PDU session in which UE_A 10 prioritizes connection by transmitting and receiving the third identification information.
  • the third identification information may indicate a PDN for which UE_A 10 requests connection.
  • 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.
  • CPF_A140 selects NSI and / or UPGW_A130 to be connected based on the received first identification information and / or tenth identification information, and (C) Or the procedure (D) in this procedure is started, and if the fourth condition is false, these procedures are omitted (S1703) (S1704).
  • the first condition determination may be the same as the first condition determination during the attach procedure.
  • the fourth condition determination is for determining whether or not a PDU session change and / or addition and / or deletion procedure is necessary.
  • the CPF_A 140 may determine session switching based on the second identification information and / or the third identification information. Specifically, when the PDN indicated by the second identification information and / or the third identification information is PDN_B6, it is possible to establish a session to PDN_B6 by moving UE_A10 and / or changing the operator policy. In some cases, the CPF_A 140 may decide to switch the session from the connection to the PDN_A5 to the connection to the PDN_B6.
  • CPF_A140 may decide to switch from the PDU session to PDN_A5 to the PDU session to PDN_B6 based on the network status, regardless of the message included in the tracking area update request message.
  • CPF_A140 may include at least one or more identification information of the second and third identification information in the message to UPGW_A130 in the procedure of (C) in this procedure, or these identifications By including the information, the request of UE_A10 may be transmitted to each device.
  • each device executes the procedure (D) in this procedure.
  • the CPF_A 140 may select UPGW_B 131 as the GW to which the session is switched. The selection of GW may be performed based on information acquired from HSS. Further, the CPF_A140 transmits to the selected UPGW_B131 a message including at least one or more of the second identification information and the third identification information, the identification information of the UPGW_A130, and the identification information of the PDU session. You can do it.
  • the UPGW_B 131 may approve the switching of the PDU session based on at least one of the received identification information, and may further execute a request procedure for information related to the session to the UPGW_A 130 which is the GW between the switching. In addition, each device may execute a procedure for switching the PDU session.
  • CPF_A140 executes the third condition determination after the procedure (C) or the procedure (D) is completed.
  • the third condition determination is for determining whether CPF_A140 accepts the request of UE_A10, and the third condition determination is either during the procedure of (C) or (D). It may be determined based on information received from the device. In the third condition determination, CPF_A 140 determines whether the third condition is true or false.
  • CPF_A140 sends a tracking area update acceptance (Tracking_Area Update accept) message to UE_A10 via NR node_A122 (S1706), and if the third condition is false, this procedure The procedure (B) in the middle starts.
  • 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.
  • CPF_A140 may include a tracking area update acceptance message in an S1AP message (for example, UEContext-Modification-Request or Downlink-NAS-Transport) and transmit it to NR-node_A122.
  • the tracking area update acceptance message may be a NAS message.
  • the NR node_A 122 may transmit the tracking area update acceptance message received by the UE_A 10 in the RRC message.
  • the CPF_A 140 may include at least one of the identification information of the 10th to 13th and 22nd identification information in the tracking area update acceptance message and / or the S1AP message, or include these identification information This may indicate that the UE_A10 request has been accepted.
  • the NR node_A122 may include one or more identification information of the 10th to 13th and 22nd identification information in the RRC message, and by including these identification information, the request of the UE_A10 is accepted. You may show things.
  • Each device may indicate the NSI type to which the PDU session established by this procedure is connected by transmitting and receiving the tenth identification information. Furthermore, each device may indicate information for identifying the PDN of the connection destination of the PDU session established by this procedure by transmitting and receiving the eleventh identification information. Each device may indicate that the request of UE_A10 is permitted by transmitting and receiving the eleventh identification information.
  • each device indicates the NSI type that is allowed to connect to UE_A10 in addition to the NSI type to which the PDU session established in this procedure is connected by transmitting and receiving the twelfth identification information.
  • each device indicates an NSI type to which UE_A 10 can be connected by transmitting and receiving the twelfth identification information.
  • the NSI type indicated by the twelfth identification information may be one or more NSI types.
  • each device indicates the PDN that is allowed to connect to UE_A10 in addition to the PDN to which the PDU session established in this procedure is connected by transmitting and receiving the thirteenth identification information.
  • each apparatus may show PDN which UE_A10 can connect by transmitting / receiving 13th identification information.
  • the thirteenth identification information may be associated with the twelfth identification information.
  • a plurality of thirteenth identification information may be associated with one twelfth identification information.
  • each device may instruct switching of sessions in this procedure by transmitting / receiving the 22nd identification information.
  • the 22nd identification information may be an IP address indicating a switching destination.
  • 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 information indicating 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 information indicating an appropriate reason for refusal may be thirtieth identification information.
  • each device may indicate that it does not support connection to an NSI and / or PDN included in the NSI type requested by UE_A10 by transmitting and receiving thirtyth identification information.
  • the information may indicate that connection to the NSI and / or PDN included in the NSI type requested by the UE_A 10 is not permitted.
  • 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 UE_A10 receives at least one of the tenth to thirteenth identification information, UE_A10 may store and / or update the received identification information and use it for the next tracking area update procedure. .
  • UE_A10 may authenticate session switching. Furthermore, when the 22nd identification information is an IP address, UE_A10 may memorize
  • UE_A10 may start the tracking area update procedure after this procedure is completed. For example, UE_A10 may start the tracking area update procedure based on the expiration of the first timer.
  • 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 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)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention concerne un procédé de commande de communication permettant de gérer de manière optimale, sur un réseau et un dispositif terminal, des informations de commande d'un dispositif terminal capable de se connecter à divers types de réseaux centraux, un moyen de commande de communication de dispositif d'un réseau capable de se connecter au dispositif terminal susmentionné, un moyen permettant de configurer des informations de commande relatives à la communication de chaque dispositif, un moyen de commande de communication permettant de mettre à jour les informations de configuration associées à la communication stockées par chaque dispositif, etc. Il devient ainsi possible de fournir un système de communication qui prend en charge les configurations de divers types de réseaux centraux, et un moyen de commande de communication favorable au dispositif terminal.
PCT/JP2017/046626 2017-01-05 2017-12-26 Dispositif terminal, unité de fonction réseau, station de base, système de communication et procédé de commande de communication WO2018128125A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2017000507A JP2020036053A (ja) 2017-01-05 2017-01-05 端末装置、ネットワーク機能部、基地局、通信システム、及び通信制御方法
JP2017-000507 2017-01-05

Publications (1)

Publication Number Publication Date
WO2018128125A1 true WO2018128125A1 (fr) 2018-07-12

Family

ID=62791161

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2017/046626 WO2018128125A1 (fr) 2017-01-05 2017-12-26 Dispositif terminal, unité de fonction réseau, station de base, système de communication et procédé de commande de communication

Country Status (2)

Country Link
JP (1) JP2020036053A (fr)
WO (1) WO2018128125A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020050138A1 (fr) * 2018-09-03 2020-03-12 日本電気株式会社 Dispositif de réseau central, dispositif de réseau d'accès, terminal de communication, système de communication et procédé de communication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090067436A1 (en) * 2007-09-07 2009-03-12 Trapeze Networks, Inc. Network assignment based on priority
US20160353281A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. Admission of a Session to a Virtual Network Service

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090067436A1 (en) * 2007-09-07 2009-03-12 Trapeze Networks, Inc. Network assignment based on priority
US20160353281A1 (en) * 2015-06-01 2016-12-01 Huawei Technologies Co., Ltd. Admission of a Session to a Virtual Network Service

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"111, Update to 6.1.3.1: Remove the signalling path between CCPF and UP functions", 3GPP TSG-SA WG2 MEETING #118, 8 November 2016 (2016-11-08), pages 1 - 4, XP051199605, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2-Arch/TSGS2_118_Reno/Docs/S2-166633.zip> [retrieved on 20180307] *
"Way forward on solutions for key issue 1 on network slicing", 3GPP TSG-SA WG2 MEETING #116BIS, 12 October 2016 (2016-10-12), pages 1 - 8, XP051169869, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_117_Kaohsiung_City/Docs/S2-165762.zip> [retrieved on 20180307] *
SAMSUNG: "Layer 2 aspects for supporting multiple services", 3GPP TSG-RAN WG2 MEETING #95BIS R2-166102, 30 September 2016 (2016-09-30), pages 1 - 4, XP051161571, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG2_RL2/TSGR2_95bis/Docs/R2-166102.zip> [retrieved on 20180307] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020050138A1 (fr) * 2018-09-03 2020-03-12 日本電気株式会社 Dispositif de réseau central, dispositif de réseau d'accès, terminal de communication, système de communication et procédé de communication
US12160740B2 (en) 2018-09-03 2024-12-03 Nec Corporation Core network device, access network device, communication terminal, communication system, and communication method

Also Published As

Publication number Publication date
JP2020036053A (ja) 2020-03-05

Similar Documents

Publication Publication Date Title
WO2018030474A1 (fr) Dispositif terminal, passerelle et procédé de commande de communications
WO2018168966A1 (fr) Dispositif terminal, dispositif de réseau central, et procédé de commande de communication
JP6748220B2 (ja) Ｕｅ、コアネットワーク装置、ｕｅの通信方法及びコアネットワークの通信方法
WO2018147220A1 (fr) Dispositif terminal, dispositif de réseau central et procédé de commande de communication
WO2020071502A1 (fr) Ue
EP3813478B1 (fr) Équipement utilisateur et son procédé de communication
EP3813477B1 (fr) Équipement utilisateur et son procédé de communication
WO2018207839A1 (fr) Dispositif terminal, amf, smf, dispositif de réseau central, et procédé de commande de communication
CN110140394B (zh) 终端装置、核心网装置以及通信控制方法
WO2018128126A1 (fr) Dispositif terminal, unité de fonction de réseau, dispositif de station de base, système de communication et procédé de commande de communication
CN110249663B (zh) 终端装置、核心网装置、通信系统、以及通信控制方法
WO2018147219A1 (fr) Dispositif terminal, dispositif de réseau central et procédé de commande de communication
WO2021029381A1 (fr) Équipement utilisateur et procédé de commande de communication
WO2018128125A1 (fr) Dispositif terminal, unité de fonction réseau, station de base, système de communication et procédé de commande de communication
JP7362344B2 (ja) Ｕｅ、及び通信制御方法

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17890055

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载