WO2018128127A1 - 端末装置、コアネットワーク装置、及び通信制御方法 - Google Patents
端末装置、コアネットワーク装置、及び通信制御方法 Download PDFInfo
- Publication number
- WO2018128127A1 WO2018128127A1 PCT/JP2017/046638 JP2017046638W WO2018128127A1 WO 2018128127 A1 WO2018128127 A1 WO 2018128127A1 JP 2017046638 W JP2017046638 W JP 2017046638W WO 2018128127 A1 WO2018128127 A1 WO 2018128127A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- pdu session
- tracking area
- procedure
- identification information
- core network
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/005—Multiple registrations, e.g. multihoming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/25—Maintenance of established connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/38—Connection release triggered by timers
Definitions
- the present invention relates to a terminal device, a core network device, and a communication control method.
- This application claims the benefit of priority over Japanese Patent Application No. 2017-509 filed in Japan on January 5, 2017. By referring to it, all of its contents are It is included in the application.
- 3GPP (3rd Generation Partnership Project), which conducts standardization activities for mobile communication systems in recent years, is studying SAE (System Architecture Evolution), which is an LTE (Long Term Evolution) system architecture.
- SAE System Architecture Evolution
- LTE Long Term Evolution
- 3GPP has specified EPS (Evolved Packet System) as a communication system for realizing all IP (Internet Protocol).
- the core network that constitutes EPS is called EPC (Evolved-Packet-Core).
- next-generation communication technology and system architecture for 5G (5th Generation) mobile communication systems which are next-generation mobile communication systems.
- NextGen Architecture and Security for for Next Generation System
- NextGen extracts technical issues for connecting a wide variety of terminals to cellular networks, and specifies solutions.
- NextGen is studying to diversify session management in mobile communication services between terminals and network devices.
- the present invention has been made in view of such circumstances, and an object thereof is to provide means for establishing a session, communication control means for realizing various session continuity, and the like.
- the terminal device of the present invention executes a PDU session establishment procedure with a device included in the core network, and further moves a tracking area update procedure when moving from tracking area A to tracking area B. And a timer for establishing a PDU session based on completion of the PDU session establishment procedure, suspending the PDU session based on completion of the tracking area update procedure, and managing a state of the PDU session.
- the tracking area A is a tracking area included in a tracking area list held by the terminal device before execution of the tracking area update procedure
- the tracking area B is the tracking area B Tracking area different from tracking area A A is and, further, characterized in that a tracking area which is not included in the tracking area list.
- the gateway of the present invention included in the core network includes a transmitting / receiving unit that executes a PDU session establishment procedure and a tracking area update procedure with a terminal device, and the core network based on completion of the PDU session establishment procedure.
- a control unit that establishes a PDU session between the terminal device and the terminal device, suspends the PDU session based on completion of the tracking area update procedure, and further executes a timer for managing the state of the PDU session It is characterized by having.
- the communication control method for a terminal device includes a step of executing a PDU session establishment procedure with a device included in a core network, and a step of establishing a PDU session based on completion of the PDU session establishment procedure.
- a tracking area update procedure When moving from tracking area A to tracking area B, further executing a tracking area update procedure, suspending the PDU session based on completion of the tracking area update procedure, and A timer for managing a state, and the tracking area A is a tracking area included in a tracking area list held by the terminal device before execution of the tracking area update procedure,
- the tracking area B is the The tracking area is different from the tracking area A, and is a tracking area not included in the tracking area list.
- the gateway communication control method of the present invention included in the core network includes a step of executing a PDU session establishment procedure with a terminal device, and the core network and the terminal device based on completion of the PDU session establishment procedure. Establishing a PDU session with each other, executing a tracking area update procedure, suspending the PDU session based on completion of the tracking area update procedure, and managing a state of the PDU session And a step of executing a timer for performing the operation.
- each terminal device and each device in the core network can support a wide variety of session continuity, and further, by using a session that supports an appropriate type of session continuity, a wide variety can be obtained. Communication of user data can be realized.
- 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 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, and a PDN (PacketData Network) _A5.
- UE_A10 may be a terminal device that can be wirelessly connected, and may be a UE (User Equipment), an ME (Mobile Equipment), an MS (Mobile Station), a CIoT (Cellular Internet of Things) terminal (CIoT UE), or the like.
- the core network may be a core network_B190
- the access network may be an access network_B.
- the core network may be a core network device.
- 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.
- UE_A10 can be connected to the access network and / or the core network. Furthermore, UE_A10 can connect with PDN_A5 via an access network and / or a core network, and further transmits / receives user data to / from PDN_A5.
- the user data may be data transmitted / received between UE_A10 and PDN_A5. Further, transmission / reception (communication) of user data may be performed using a PDU (Protocol Data Unit or Packet Data Unit) session or may be performed using a PDN connection (Packet Data Network Connection). Further, user data communication is not limited to IP (Internet Protocol) communication but may be non-IP communication.
- a PDU session or a PDN connection (hereinafter also referred to as a PDN connection) is established between UE_A10 and PDN_A5 in order to provide a PDU connection service for transmitting and receiving user data between UE_A10 and PDN_A5.
- the PDU session or PDN connection may be connectivity established between UE_A 10 and the external gateway.
- the external gateway may be a device that connects the PDN_A5 and a core network such as PGW (Packet Data Network Gateway) _A30, UPGW (User Plane Gateway) _A130, and SCEF (Service Capability Exposure Function) _A46.
- PGW Packet Data Network Gateway
- UPGW User Plane Gateway
- SCEF Service Capability Exposure Function
- the PDU session or PDN connection may be a communication path established for transmitting / receiving user data between the UE_A 10 and the core network and / or PDN_A5, or may be a communication path for transmitting / receiving PDUs.
- the PDU session or the PDN connection may be a session established between the UE_A 10 and the core network and / or PDN_A5, and is configured by a transfer path such as one or a plurality of bearers between each device in the mobile communication system 1. It may be a logical communication path.
- the PDU session may be a connection established between the UE_A10 and the core network_B190 and / or the external gateway, a connection established between the UE_A10 and the UPGW_A130, or a PDN connection.
- a connection such as (Packet Data Network Connection) may be used.
- 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. Further, the PDN connection may be identified by a PDN connection ID, and the PDU session may be identified by a PDU session ID. Furthermore, the PDN connection and the PDU session may be identified by an EPS bearer ID.
- UE_A 10 can transmit and receive user data using a PDU session or a PDN connection with a device such as an application server arranged in PDN_A 5.
- the PDU session or the PDN connection can transfer user data transmitted and received between devices such as an application server arranged in the UE_A10 and the PDN_A5.
- each device UE_A10, a device in the access network, and / or a device in the core network
- identification information includes APN (AccessPoint Name), TFT (Traffic Flow Template), session type, application identification information, PDN_A5 identification information, NSI (Network Slice Instance) identification information, and DCN (Dedicated Core Core Network). At least one of the identification information and the access network identification information may be included, or other information may be further included. Further, when a plurality of PDU sessions or PDN connections are established, each piece of identification information associated with the PDU session or PDN connection may have the same contents or different contents. 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 may be a DN (Data Network) that provides a communication service to UE_A10.
- the DN may be configured as a packet data service network or may be configured for each service.
- PDN_A5 may include a connected communication terminal. Therefore, connecting to PDN_A5 may be connecting to a communication terminal or server device arranged in PDN_A5. Further, transmitting / receiving user data to / from PDN_A5 may be transmitting / receiving user data to / from a communication terminal or server device arranged in PDN_A5.
- PDN_A5 may be expressed as DN, or DN may be expressed as PDN_A5.
- the access network is a wireless network connected to UE_A10 and / or the core network.
- the access network may be a 3GPP access network or a non-3GPP access network.
- the 3GPP access 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. 3 shows an example of the configuration of the core network_B190.
- the core network_B190 in FIG. 3 (a) includes HSS_A50, PCRF_A60, UPGW (User (Plane Gateway) _A130, CPF (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 more devices arranged in the core network_B190, and may be a CP function for control information and / or control messages (hereinafter referred to as CPF (Control Plane Function) or Control Plane Network Function). Or a shared CP function shared between 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.
- 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 a device (for example, a base station device or an access point device) to which UE_A 10 is actually connected.
- a device used for connection a device adapted to a radio access network can be considered.
- 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 include NR node_A122 and NR node_B123. In this case, NR node_B123 may have the same configuration as 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.
- 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 for identifying the DN of the establishment destination of the PDU session.
- Assigned Session Type is information indicating the type of PDU session. Assigned Session Type may be Assigned PDN Type. The type of PDU session may be IP or non-IP. Furthermore, when the type of the PDU session is IP, information indicating the type of PDN allocated from the network may be further included. The Assigned Session Type may be IPv4, IPv6, or IPv4v6.
- IP Address is an IP address assigned to the UE.
- the IP address may be an IPv4 address, an IPv6 address, or an IPv6 prefix.
- Assigned Session Type indicates non-IP, the IP Address element does not have to be included.
- DN ID is identification information that identifies the core network_B190 and an external network such as DN. Furthermore, the DN ID can also be used as information for selecting a gateway such as UPGW_A130 connecting the core network_B190.
- the DN ID may be identification information for identifying such a gateway, or identification information for identifying an external network such as a DN.
- a plurality of gateways that connect the core network_B190 and the DN there may be a plurality of gateways that can be selected by the DN ID. Further, one gateway may be selected from the plurality of gateways by another method using identification information other than the DN ID.
- the DN ID may be the same information as the APN, or may be information different from the APN. If the DN ID and APN are different information, each device may manage information indicating the correspondence between the DN ID and APN, or perform a procedure for inquiring the APN using the DN ID. Alternatively, a procedure for inquiring about the DN ID using the APN may be performed.
- 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, or may be a communication path forming a PDN connection / PDU session. Further, the EPS bearer may be a default bearer or a dedicated bearer. Furthermore, the EPS bearer may be configured to include an RB established between the UE_A 10 and a base station and / or access point in the access network. Furthermore, RBs and EPS bearers may be associated one-to-one.
- the RB identification information may be associated with the EPS bearer identification information on a one-to-one basis, or may be the same identification information.
- RB may be SRB and / or CRB or DRB.
- 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.
- the default bearer is an EPS bearer that is first established during a PDN connection / PDU session, and is an EPS bearer that can be established only during one PDN connection / PDU session.
- the default bearer may be an EPS bearer that can be used for communication of user data not associated with the TFT.
- a dedicated bearer is an EPS bearer that is established after a default bearer is established in a PDN connection / PDU session, and a plurality of EPS bearers that can be established in one PDN connection / PDU session. is there.
- a dedicated bearer is an EPS bearer that can be used for communication of user data associated with a TFT.
- User Identity is information for identifying a subscriber. 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.
- FIG. 7 shows the device configuration of MME_A40 and CPF_140.
- the MME_A 40 and the CPF_140 are configured by a network connection unit_C720, a control unit_C700, and a storage unit_C740.
- the network connection unit_C720 and the storage unit_C740 are connected to the control unit_C700 via a bus.
- the functions of these units may operate on physical hardware, or may operate on logical hardware configured virtually on general-purpose hardware.
- Control unit_C700 is a functional unit for controlling MME_A40 and CPF_140.
- 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, MMEUE 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 the device configurations of PGW_A30 and UPGW_A130.
- the PGW_A30 and the UPGW_A130 are composed of a network connection unit_D1020, a control unit_D1000, and a storage unit_D1040.
- the network connection unit_D1020 and the storage unit_D1040 are connected to the control unit_D1000 via a bus.
- the functions of these units may operate on physical hardware, or may operate on logical hardware configured virtually on general-purpose hardware.
- Control unit_D1000 is a functional unit for controlling PGW_A30.
- the control unit_D1000 implements various processes by reading and executing various programs stored in the storage unit_D1040.
- the network connection unit_D1020 is a functional unit for connecting the PGW_A30 to the SGW_A35 and / or PCRF_A60 and / or ePDG_A65 and / or AAA_A55 and / or TWAG_A74 and / or PDN_A5.
- the network connection unit _D1020 allows the PGW_A30 to transmit and receive user data and / or control information from the SGW_A35 and / or PCRF_A60, and / or ePDG_A65, and / or AAA_A55, and / or TWAG_A74, and / or PDN_A5. It is a transmission / reception unit.
- the network connection unit_D1020 is a functional unit for UPGW_A130 to connect with PCRF_A60 and / or UPGW_A130 and / or PDN_A5.
- the network connection unit _D1020 allows the PGW_A30 to transmit and receive user data and / or control information from the SGW_A35 and / or PCRF_A60, and / or ePDG_A65, and / or AAA_A55, and / or TWAG_A74, and / or PDN_A5. It is a transmission / reception unit.
- Storage unit_D1040 is a functional unit that stores programs and data required for each operation of PGW_A30.
- the storage unit_D1040 is configured by, for example, a semiconductor memory, an HDD, or the like.
- the storage unit_D1040 may store at least identification information and / or control information and / or flags and / or parameters included in a control message transmitted and received in a communication procedure described later.
- the storage unit_D1040 stores the EPS bearer context 1042 as shown in the figure.
- the EPS bearer context 1042 includes one that is stored for each UE, one that is stored for each APN, one that is stored for each PDU session or PDN connection, and one that is stored for each bearer. May be stored separately. Further, the EPS bearer context may be a context stored in UPGW_A 130.
- FIG. 12 (b) shows information elements included in the EPS bearer context stored for each UE.
- the EPS bearer context stored for each UE includes IMSI, MEIdentity, MSISDN, and RAT type.
- Fig. 12 (c) shows the EPS bearer context stored for each APN.
- the EPS bearer context stored for each APN in the PGW storage unit includes APN in use.
- the EPS bearer context stored for each APN may be stored for each Data ⁇ ⁇ Network Identifier.
- Fig. 12 (d) shows the EPS bearer context for each PDU session or PDN connection stored for each PDU session or PDN connection.
- the EPS bearer context for each PDU session or PDN connection includes Assigned Session Type, IP Address (es), SGW F-TEID, PGW F-TEID, and Default Bearer.
- Fig. 12 (e) shows the EPS bearer context stored for each EPS bearer.
- the EPS bearer context includes EPS Bearer ID, TFT, SGWF-TEID, and PGW F-TEID.
- FIG. 10 shows the device configuration of SCEF_A46.
- the SCEF_A 46 includes a network connection unit_D1020, a control unit_D1000, and a storage unit_D1040.
- the network connection unit_D1020 and the storage unit_D1040 are connected to the control unit_D1000 via a bus.
- Control unit_D1000 is a functional unit for controlling SCEF_A46.
- the control unit_D1000 implements various processes by reading and executing various programs stored in the storage unit_D1040.
- the network connection unit_D1020 is a functional unit for the SCEF_A46 to connect to the core network_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 a procedure, it means that a device in the network performs message transmission / reception and / or a procedure.
- 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. Further, 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. Furthermore, the tracking area may be a routing area, a location area, or the like. Hereinafter, the tracking area may be TA (Tracking Area).
- the TA list is a list including one or more TAs assigned by the network to UE_A10.
- UE_A10 may be able to move without executing the tracking area update procedure while moving in one or more TAs included in the TA list.
- UE_A10 may be an information group in which the TA list indicates an area in which UE_A10 can move without executing the tracking area update procedure.
- the mobility across the TA of UE_A10 indicates that UE_A10 moves to a TA different from the currently connected TA.
- the mobility across the TA of the UE_A 10 may be that the UE_A 10 has entered a different TA from the currently connected TA.
- a TA different from the TA to which UE_A10 is currently connected may be a TA that is not included in the TA list currently held by UE_A10.
- the location information is re-registered and / or the established communication path is based on the fact that UE_A10 has entered a different TA from the currently connected TA. It may include performing session continuation (Session Continuity) and / or service continuation (Service Continuity) by switching.
- the first timer is a timer for indicating the expiration date of the suspended PDU session.
- Each device may disconnect a suspended PDU session based on the expiration of the first timer.
- timing of starting the first timer may be when the PDU session is suspended, or when UE_A10 enters a new TA, and is performed when UE_A10 enters a new TA. It may be when the tracking area update procedure is completed.
- the tracking area update procedure executed when UE_A10 returns to the previously connected TA or when UE_A10 returns to the previously connected TA If completed, the suspended PDU session may be resumed. In this case, the execution of the first timer may be stopped, and the first timer may be reset.
- the TA to which UE_A10 has previously connected may be a TA included in the TA list held by UE_A10 before the PDU session is suspended.
- the first type of PDU session in the present embodiment is a PDU session that is disconnected during mobility across the TA of UE_A10.
- the first type of PDU session may be a PDU session in which session continuation is not performed.
- the first type of PDU session may be configured with a bearer that is disconnected in the case of mobility across the TA of UE_A10.
- the disconnection of the first type of PDU session may be performed based on intrusion of UE_A10 into a different TA, or based on execution of a tracking area update procedure performed after UE_A10 enters into a different TA. It may be carried out or may be carried out based on execution of another procedure executed after the tracking area update procedure. Note that the timing at which the first type PDU session is disconnected is not limited to this.
- the PDU session disconnection may be performed individually by each device without transmitting / receiving a control message between the devices, or a procedure for disconnecting a PDU session and / or a bearer, and / or each You may implement
- the bearer associated with the PDU session when it is expressed that the PDU session is disconnected, it may mean that the bearer associated with the PDU session is disconnected, and further, associated with the PDU session and / or bearer. It may mean that the given context is released.
- the second type of PDU session in the present embodiment is a PDU session that is suspended or resumed during mobility across the TA of UE_A10.
- the second type of PDU session is a PDU session that does not perform session continuity (Session Continuity) but can return to the previous state under conditions such as returning to the original TA. It's okay.
- the second type of PDU session may be configured with a bearer that is suspended or resumed in the case of mobility across the TA of UE_A10.
- suspension and / or resume of the second type of PDU session may be performed based on intrusion of UE_A10 into a different TA, or a tracking area update procedure performed after UE_A10 intrudes into a different TA. May be executed based on the execution of the tracking area update procedure, or may be executed based on the execution of another procedure executed after the tracking area update procedure. Note that the timing at which the second type PDU session is suspended or resumed is not limited to this.
- the second type of PDU session may be disconnected based on the expiration of the first timer.
- each device may disconnect the suspended PDU session if the first timer expires in the state where the second type PDU session is suspended, and the context for the suspended PDU session. May be released.
- suspend and / or resume of the PDU session may be performed individually by each device without transmitting / receiving a control message between the devices, or a procedure for suspending the PDU session and / or bearer or You may implement
- the bearer associated with the PDU session when it is expressed that the PDU session is suspended, it may mean that the bearer associated with the PDU session is suspended, and further associated with the PDU session and / or bearer. It may mean transition to a state in which transmission / reception of user data using a PDU session and / or a bearer is not possible while maintaining a given context.
- the bearer associated with the PDU session when it is expressed that the PDU session is resumed, it may mean that the bearer associated with the PDU session is resumed, and the maintained PDU session and / or Alternatively, it may mean transition to a state in which user data can be transmitted and received using a PDU session and / or a bearer using a context associated with the bearer.
- the default type PDU session in the present embodiment is a PDU session established when each device does not transmit / receive identification information indicating the type of PDU session to be established in the PDU session establishment procedure.
- the type of the default type PDU session may be determined by a policy such as a UE policy or an operator policy, or may be set in UE_A10 in advance. Further, the default type PDU session may be the first PDU session, the second PDU session, or the third PDU session. The determination of the default type of PDU session is not limited to this.
- the default type of PDU session in this embodiment is a PDU session established when each device does not transmit or receive identification information indicating the type of PDU session to be established in the procedure for establishing the PDU session. is there.
- the type of the default type PDU session may be determined by a policy such as a UE policy or an operator policy, or may be set in UE_A10 in advance. Further, the default type PDU session may be the first PDU session, the second PDU session, or the third PDU session. The determination of the default type of PDU session is not limited to this.
- the first state in the present embodiment is a state in which the procedure for connecting and registering the UE_A10 to the core network_B190 has been completed and each device has established a PDU session.
- Each device may execute the procedure for registering UE_A10 in the core network_B190 and the procedure for establishing a PDU session at the same time or separately.
- the first state in the present embodiment may be a state in which each device has established a PDU session with respect to the core network_B190. More specifically, the first state may be a state in which each device establishes a PDU session between UE_A10 and UPGW_A130 via NRnode_A122.
- the first state may be a state in which mobility across the TA of UE_A10 is performed, and an established PDU session and / or bearer continues by the mobility across the TA of UE_A10. It may be a resumed state or a resumed state. Note that the first state is not limited to these states.
- the second state in the present embodiment may be a state in which the tracking area update procedure for updating the location registration information of UE_A10 is completed.
- the trigger for the tracking area update procedure may be an intrusion of UE_A10 into a different tracking area.
- the second state may be a state in which each device has established only an appropriate PDU session based on execution of the tracking area update procedure.
- the second state may be a state where mobility across the TA of UE_A10 is performed, and the established PDU session and / or bearer is disconnected due to the mobility across the TA of UE_A10. It may be a state or a suspended state. Note that the second state is not limited to this.
- the NSI Network Slice Instance
- the NSI in the present embodiment may be configured by a virtual NF (Network Function) generated using NST (Network Slice Template).
- NST is a logical expression of one or a plurality of NF (Network Function) associated with a resource request for providing a required communication service and capability.
- the NSI may be an aggregate in the core network_B190 composed of a plurality of NFs.
- the NSI may be a logical network configured to separate user data delivered by services or the like.
- At least one or more NFs may be configured in the network slice.
- the NF configured in the network slice may or may not be a device shared with other network slices.
- UE shall be assigned to one or more network slices based on registration information and / or APN such as UE usage type and / or one or more network slice type IDs and / or one or more NS IDs Can do.
- APN such as UE usage type and / or one or more network slice type IDs and / or one or more NS IDs Can do.
- the first identification information in the present embodiment is UE_A10 capability information indicating that the first type of PDU session is supported.
- the first identification information may be information indicating whether UE_A10 supports the first type of PDU session.
- the second identification information in this embodiment is UE_A10 capability information indicating that the second type of PDU session is supported.
- the second identification information may be information indicating whether UE_A10 supports the second type of PDU session.
- the third identification information in this embodiment is UE_A10 capability information indicating that the third type PDU session is supported.
- the third identification information may be information indicating whether the UE_A 10 supports the third type PDU session.
- the fourth identification information in the present embodiment is information indicating the type of PDU session that UE_A 10 requests to establish.
- Types of PDU sessions may include a first type PDU session, a second type PDU session, and a third type PDU session. Note that the type of PDU session is not limited to this. Further, the fourth identification information may be configured by one or more pieces of identification information of the fifth to seventh identification information, or may be configured as independent identification information, such as the fifth to seventh identification information. May be.
- / or the fourth identification information may be information requesting the network to transmit the 31st identification information and / or the 32nd identification information described later in the tracking area update procedure. Further, it may be information that requests the network to transmit any one of the 33rd to 36th identification information corresponding to the type of the PDU session indicated by the fourth identification information in the tracking area update procedure.
- the fourth identification information and the capability information indicating that the establishment and / or use of the type of PDU session indicated by the fourth identification information are supported may be single identification information.
- the fourth identification information may be single identification information including the meaning of each identification information, with any one of the first to third identification information. Therefore, in the present embodiment, the case where the fourth identification information indicates the type of the first type PDU session and further describes that the fourth identification information and the first identification information are transmitted or included in the control message.
- the fourth identification information and the first identification information may be transmitted as a single identification information having both meanings of the two identification information, or may be included in the control message.
- the fourth identification information indicates the type of the second type PDU session, and further describes that the fourth identification information and the second identification information are transmitted or included in the control message.
- the fourth identification information and the second identification information may be transmitted as a single identification information having both meanings of the two identification information, or may be included in the control message.
- the fourth identification information indicates the type of the third type PDU session, and further describes that the fourth identification information and the third identification information are transmitted or included in the control message.
- the fourth identification information and the third identification information may be transmitted as single identification information having both meanings of the two identification information or included in the control message.
- the fifth identification information in this embodiment is UE_A10 request information indicating that the establishment and / or use of the first type PDU session is requested.
- the fifth identification information may be information indicating whether the UE_A 10 requests establishment and / or use of the first type PDU session.
- And / or the fifth identification information may be information requesting the network to transmit the 31st identification information and / or the 32nd identification information described later in the tracking area update procedure. Furthermore, it may be information requesting the network to transmit the 33rd identification information in the tracking area update procedure.
- the fifth identification information and the first identification information may be single identification information including the meaning of each identification information. Therefore, in this embodiment, when it is described that the fifth identification information and the first 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 sixth identification information in this embodiment is UE_A10 request information indicating that the second type PDU session is requested to be established and / or used.
- the sixth identification information may be information indicating whether the UE_A 10 requests establishment and / or use of the second type PDU session.
- And / or the sixth identification information may be information requesting the network to transmit the 31st identification information and / or the 32nd identification information described later in the tracking area update procedure. Further, it may be information requesting the network to transmit the 34th identification information or the 35th identification information in the tracking area update procedure.
- the sixth identification information and the second identification information may be single identification information including the meaning of each identification information. Therefore, in the present embodiment, when it is described that the sixth identification information and the second identification information are transmitted or included in the control message, the two identification information is transmitted as a single identification information having both meanings. Or may be included in the control message.
- the seventh identification information in this embodiment is request information of UE_A10 indicating that the establishment and / or use of the third type PDU session is requested.
- the seventh identification information may be information indicating whether the UE_A 10 requests establishment and / or use of the third type PDU session.
- / or the seventh identification information may be information requesting the network to transmit the 31st identification information and / or the 32nd identification information described later in the tracking area update procedure.
- the 36th identification information may be information requesting the network to transmit in the tracking area update procedure.
- the seventh identification information and the third identification information may be single identification information including the meaning of each identification information. Therefore, in this embodiment, when it is described that the seventh identification information and the third 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 eleventh identification information in the present embodiment is network capability information indicating that the first type of PDU session is supported.
- the eleventh identification information may be information indicating whether the network supports the first type of PDU session. Note that UE_A10 may recognize that the establishment and / or use of the first type of PDU session has been accepted or recognized based on the reception of the eleventh identification information. May be.
- the twelfth identification information in this embodiment is network capability information indicating that the second type PDU session is supported.
- the twelfth identification information may be information indicating whether the network supports the second type of PDU session. Note that UE_A10 may recognize that the establishment and / or use of the second type PDU session has been accepted or recognized based on the reception of the twelfth identification information. May be.
- the thirteenth identification information in the present embodiment is network capability information indicating that the third type PDU session is supported.
- the thirteenth identification information may be information indicating whether the network supports the third type of PDU session. Note that the UE_A 10 may recognize that the establishment and / or use of the third type PDU session has been accepted or recognized based on the reception of the thirteenth identification information. May be.
- the 14th identification information in the present embodiment is information indicating the type of PDU session that the network has established and / or accepted and / or permitted to use.
- the fourteenth identification information may be information indicating that the network has accepted and / or permitted the establishment and / or use of the type of PDU session requested by UE_A10. Further, the fourteenth identification information may be information indicating that the network has accepted and / or permitted the UE_A10 request.
- the 14th identification information may be configured by one or more pieces of identification information of the 15th to 17th identification information, or may be configured as independent identification information, such as the 15th to 17th identification information. May be.
- / or the fourteenth identification information may be information indicating that thirty-first identification information and / or thirty-second identification information described later is transmitted by the network in the tracking area update procedure. Furthermore, it may be information indicating that any one of the 33rd to 36th identification information corresponding to the type of the PDU session indicated by the 14th identification information is transmitted by the network in the tracking area update procedure.
- the 14th identification information and the capability information indicating that the establishment and / or use of the type of PDU session indicated by the 14th identification information may be a single identification information.
- the fourteenth identification information may be single identification information including the meaning of each identification information, with any one of the eleventh to thirteenth identification information. Therefore, in the present embodiment, the 14th identification information indicates the type of the first type of PDU session, and it is further explained that the 14th identification information and the 11th identification information are transmitted or included in the control message.
- the fourteenth identification information and the eleventh identification information may be transmitted as single identification information having both meanings of the two identification information, or may be included in the control message.
- the 14th identification information indicates the type of the PDU session of the second type, and it is further explained that the 14th identification information and the 12th identification information are transmitted or included in the control message.
- the fourteenth identification information and the twelfth identification information may be transmitted as a single identification information having both meanings of the two identification information, or may be included in the control message.
- the 14th identification information indicates the type of the PDU session of the third type, and the 14th identification information and the 13th identification information are transmitted or included in the control message.
- the fourteenth identification information and the thirteenth identification information may be transmitted as single identification information having both meanings of the two identification information, or may be included in the control message.
- the fifteenth identification information in the present embodiment is information indicating that the network has accepted and / or permitted the request for establishment and / or use of the first type PDU session.
- the fifteenth identification information may be information indicating whether or not the network accepts the establishment and / or use of the first type of PDU session, or information indicating whether or not to allow the network. May be.
- / or the fifteenth identification information may be information indicating that the thirty-first identification information and / or the thirty-second identification information described later is transmitted by the network in the tracking area update procedure. Further, the fifteenth identification information may be information indicating that the thirty-third identification information is transmitted by the network in the tracking area update procedure.
- the fifteenth identification information and the eleventh identification information may be single identification information including the meaning of each identification information. Therefore, in this embodiment, when it is described that the fifteenth identification information and the eleventh identification information are transmitted or included in the control message, the two identification information are transmitted as a single identification information having both meanings. Or may be included in the control message.
- the sixteenth identification information in the present embodiment is information indicating that the network has accepted and / or permitted the request for establishment and / or use of the second type PDU session.
- the sixteenth identification information may be information indicating whether or not the network accepts establishment and / or use of the second type of PDU session, or information indicating whether or not to allow the network. May be.
- the 16th identification information may be information indicating that the 31st identification information and / or the 32nd identification information, which will be described later, is transmitted by the network in the tracking area update procedure. Further, the sixteenth identification information may be information indicating that the thirty-fourth identification information or the thirty-fifth identification information is transmitted by the network in the tracking area update procedure.
- the 16th identification information and the 12th identification information may be single identification information including the meaning of each identification information. Therefore, in this embodiment, when it is described that the 16th identification information and the 12th 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 seventeenth identification information in the present embodiment is information indicating that the network has accepted and / or authorized a request for establishment and / or use of the third type PDU session.
- the seventeenth identification information may be information indicating whether or not the network accepts the establishment and / or use of the third type PDU session, or information indicating whether or not to allow the network. May be.
- the 17th identification information may be information indicating that the 31st identification information and / or the 32nd identification information, which will be described later, is transmitted by the network in the tracking area update procedure. Further, the seventeenth identification information may be information indicating that the thirty-sixth identification information is transmitted by the network in the tracking area update procedure.
- the 17th identification information and the 13th identification information may be single identification information including the meaning of each identification information. Therefore, in this embodiment, when it is described that the 17th identification information and the 13th 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 18th identification information in this embodiment is reason information indicating that the request of UE_A10 is rejected.
- the eighteenth identification information may be information indicating that the request of UE_A10 is not accepted by the TA to which UE_A10 currently belongs, or reason information indicating that the request is not permitted.
- the request of UE_A10 may be the establishment and / or use of the first type of PDU session, the establishment and / or use of the second type of PDU session, There may be the establishment and / or use of three types of PDU sessions.
- the eighteenth identification information may be information indicating processing to be performed by UE_A 10 after receiving the rejection message.
- the eighteenth identification information may indicate, for example, that the same procedure should be re-executed using the same identification information with a different TA, or the same procedure may be re-executed with the same TA and using different identification information. It may indicate that it should do, or it may indicate that a different procedure should be performed.
- the procedure here may be an attach procedure, a PDU session establishment procedure, a tracking area update procedure, or a PDU session disconnection procedure. Detach procedure may be used.
- the eighteenth identification information may be information indicating the type of PDU session that the network has established and / or refused to use.
- the 21st identification information in the present embodiment is information for identifying the TA that UE_A10 was registered last.
- the 21st identification information may be information indicating the TA connected last. Further, the 21st identification information may be information indicating that the TA to which UE_A10 is currently connected and TA that has been connected in the past may be the same, or information indicating that they are different. Good.
- the 22nd identification information in the present embodiment is information indicating the state of the established PDU session.
- the state of the PDU session may be information indicating whether the PDU session is activated or information indicating whether the PDU session is suspended. Further, the 22nd identification information may be associated with information for identifying the PDU session and information for identifying the EPS bearer.
- the thirty-first identification information is information indicating a TA list assigned by the network to UE_A10.
- the thirty-first identification information may include a TA to which UE_A10 is registered, or may include a TA to which UE_A10 is currently connected.
- the 31st identification information may be associated with the 33rd to 36th identification information.
- the thirty-first identification information may be an information group indicating an area that can be moved without disconnecting and / or suspending and / or resuming the PDU session established by UE_A10.
- the established PDU session may be disconnected, suspended, or resumed. Good.
- the thirty-second identification information in this embodiment is information indicating the value of the first timer determined by the network.
- the thirty-second identification information may be information indicating that the first timer is started after this tracking area update, or the first timer is set based on suspension of the established PDU session. It may be information indicating.
- the value of the first timer may be a value indicating the time from the start of execution of the first timer to the expiration.
- the 33rd identification information in the present embodiment is information indicating a PDU session and / or an EPS bearer to be disconnected immediately before, during or immediately after the tracking area update procedure.
- the thirty-third identification information may be information indicating a PDU session and / or an EPS bearer that UE_A10 is disconnected based on intrusion into a TA other than the TA indicated by the thirty-first identification information.
- the 33rd identification information may be information indicating a PDU session and / or an EPS bearer that is disconnected based on mobility across the TA of UE_A10.
- the 33rd identification information may include information indicating one or a plurality of PDU sessions and / or EPS bearers.
- the information indicating the disconnected PDU session and / or EPS bearer may be information indicating a DN associated with the disconnected PDU session and / or EPS bearer, or a network slice. It may be information indicating the type.
- the information indicating the DN may be DNN (Data Network Name), and the information indicating the type of the network slice may be a network slice type.
- the 33rd identification information may be information indicating the DN associated with the PDU session to be disconnected at the TA into which UE_A10 has entered, or may be associated with the PDU session to be disconnected. Information indicating the type of slice may be used. In other words, the 33rd identification information may be information indicating a specific DN, or information indicating that the PDU session and / or EPS bearer associated with the specific DN is disconnected. May be. Further, the thirty-third identification information may be information indicating a specific slice type, or a PDU session and / or EPS bearer associated with information indicating a specific slice type may be disconnected. It may be information indicating.
- each device may disconnect the PDU session and / or EPS bearer associated with the DN indicated by the 33rd identification information, or the 33rd identification information may be disconnected.
- the PDU session and / or EPS bearer associated with the slice type indicated in the information may be disconnected.
- the thirty-fourth identification information in the present embodiment is information indicating a PDU session and / or an EPS bearer that is suspended immediately before, during, or immediately after the tracking area update procedure. Further, the thirty-fourth identification information may be information indicating a PDU session and / or an EPS bearer that is suspended by UE_A 10 based on an intrusion into a TA other than the TA indicated by the thirty-first identification information. In other words, the thirty-fourth identification information may be information indicating a PDU session and / or an EPS bearer that is suspended based on mobility across the TA of UE_A10. Note that the 34th identification information may include information indicating one or a plurality of PDU sessions and / or EPS bearers.
- the information indicating the suspended PDU session and / or EPS bearer may be information indicating the DN associated with the suspended PDU session and / or EPS bearer, or of the network slice. It may be information indicating the type.
- the information indicating the DN may be a DNN, and the information indicating the type of the network slice may be a network slice type.
- the thirty-fourth identification information may be information indicating the DN associated with the suspended PDU session at the TA into which UE_A10 has entered, or may be associated with the suspended PDU session. Information indicating the type of slice may be used. In other words, the thirty-fourth identification information may be information indicating a specific DN, or information indicating that a PDU session and / or an EPS bearer associated with the specific DN is suspended. May be. Further, the thirty-fourth identification information may be information indicating a specific slice type, or a PDU session and / or an EPS bearer associated with information indicating a specific slice type may be suspended. It may be information indicating.
- each device may suspend the PDU session and / or EPS bearer associated with the DN indicated by the thirty-fourth identification information.
- the PDU session and / or EPS bearer associated with the slice type indicated in the information may be suspended.
- the 35th identification information in this embodiment is information indicating a PDU session and / or an EPS bearer to be resumed immediately before, during, or immediately after the tracking area update procedure.
- the 35th identification information may be information indicating a PDU session and / or an EPS bearer that UE_A10 resumes based on an intrusion into a TA other than the TA indicated by the 31st identification information.
- the 35th identification information may be information indicating a PDU session resumed based on mobility across the TA of UE_A 10 and / or an EPS bearer.
- the 35th identification information may include information indicating one or a plurality of PDU sessions and / or EPS bearers.
- the information indicating the resumed PDU session and / or EPS bearer may be information indicating a DN associated with the resumed PDU session and / or EPS bearer, or may be a network slice. It may be information indicating the type.
- the information indicating the DN may be a DNN, and the information indicating the type of the network slice may be a network slice type.
- the 35th identification information may be information indicating the DN associated with the PDU session to be resumed in the TA to which UE_A10 has entered, or may be associated with the PDU session to be resumed. Information indicating the type of slice may be used. In other words, the 35th identification information may be information indicating a specific DN, or information indicating that a PDU session and / or EPS bearer associated with the specific DN is resumed. May be. Furthermore, the 35th identification information may be information indicating a specific slice type, or a PDU session and / or EPS bearer associated with information indicating a specific slice type may be resumed. It may be information indicating.
- each device may resume the PDU session and / or EPS bearer associated with the DN indicated by the 35th identification information.
- the PDU session and / or EPS bearer associated with the slice type indicated in the information may be resumed.
- the thirty-sixth identification information in the present embodiment is information indicating a PDU session and / or EPS bearer in which session continuation is performed immediately before, during or immediately after the tracking area update procedure.
- the 36th identification information may be information indicating a PDU session and / or an EPS bearer in which UE_A10 performs session continuation based on intrusion into a TA other than the TA indicated by the 31st identification information Good.
- the thirty-sixth identification information may be information indicating a PDU session in which session continuation is performed based on mobility across the TA of UE_A 10 and / or an EPS bearer.
- the 36th identification information may include information indicating one or a plurality of PDU sessions and / or EPS bearers.
- the information indicating the PDU session and / or EPS bearer in which session continuation is performed may be information indicating the DN associated with the PDU session and / or EPS bearer in which session continuation is performed. It may be information indicating the type of network slice.
- the information indicating the DN may be a DNN, and the information indicating the type of the network slice may be a network slice type.
- the 36th identification information may be information indicating a DN associated with a PDU session in which session continuation is performed in the TA into which UE_A 10 has entered, or a PDU in which session continuation is performed. It may be information indicating the type of slice associated with the session. In other words, the 36th identification information may be information indicating a specific DN, and session continuation is performed for a PDU session and / or EPS bearer associated with the specific DN. It may be information indicating. Further, the thirty-sixth identification information may be information indicating a specific slice type, or a PDU session associated with the information indicating the specific slice type and / or a session continuation for the EPS bearer May be information indicating that is implemented.
- each device may continue the session for the PDU session and / or EPS bearer associated with the DN indicated by the thirty-sixth identification information.
- the session continuation may be performed for the PDU session and / or EPS bearer associated with the slice type indicated by the 36th identification information.
- each device executes an initial procedure to transition to the first state, and UE_A10 establishes a session via the core network_B190.
- this procedure refers to the initial procedure, and each procedure includes an attach procedure and a PDN connection procedure. Details of each procedure will be described later.
- each device first executes the attach procedure (S1400), and transitions to a state in which UE_A 10 is connected to the network.
- each device executes a PDU session establishment procedure (S1402), and transitions to the first state (S1404).
- 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.
- 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.
- the UE_A10 and the core network_B190 may include one or more identification information of the first to seventh identification information and the twenty-first identification information, and / or the eleventh to seventeenth identification information and the thirty-first to thirty-second identification information.
- One or more pieces of identification information may be exchanged by an attach procedure and a PDU session establishment procedure.
- UE_A10 and core network_B190 may perform the above exchange only in the PDU session establishment procedure, not in the attach procedure, or only in the attach procedure, not in the PDU session establishment procedure.
- the UE_A10 and the core network_B190 may include one or more pieces of identification information among the first to seventh pieces of identification information and / or one piece or more of pieces of identification information among the eleventh to seventeenth pieces of identification information.
- each device may transmit and receive during the attach procedure.
- 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, or may transition to the first state.
- 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 the first state based on the completion of this procedure.
- the attach procedure is a procedure for connecting to a network (access network and / or core network_B190 and / or PDN_A5) led by UE_A10. If the UE_A10 is not connected to the network, the UE_A10 can execute this procedure at any timing such as when the terminal power is turned on. In other words, UE_A10 may start this procedure at an arbitrary timing as long as it is not registered (EMM-DEREGISTERED). Also, each device may transition to a registration state (EMM-REGISTERED) based on completion of the attach 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 in the registered state, or 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 may be a NAS (Non-Access-Stratum) 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 (Radio Resource Control) message including a PDU session establishment request message to NRnode_A122, and NRnode_A122 which has received an RRC message including a PDU session establishment request message transmits an PDU session establishment request message.
- CPF_A140 is selected as the routing destination NF or shared CP function, and a PDU session establishment 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 information included in the RRC message.
- the UE_A10 may include at least one piece of identification information of at least the first to seventh pieces of identification information in the RRC message including the PDU session establishment request message and / or the PDU session establishment request message.
- the request for UE_A10 may be indicated by including the identification information.
- UE_A10 may indicate the type of PDU session that UE_A10 requests and / or supports establishment by transmitting the first to seventh identification information. More specifically, the UE_A 10 transmits the first identification information and / or the fifth identification information and / or the fourth identification information indicating the first type of PDU session, thereby transmitting the first type. May indicate that UE_A10 requests and / or supports UE_A10.
- the UE_A10 transmits the second identification information and / or the sixth identification information and / or the fourth identification information indicating the second type of PDU session, whereby the second type PDU session is transmitted. May indicate that UE_A10 requires and / or supports UE_A10.
- the UE_A10 transmits the third identification information and / or the seventh identification information, and / or the fourth identification information indicating the third type PDU session, whereby the third type PDU session is transmitted. May indicate that UE_A10 requires and / or supports UE_A10.
- UE_A10 determines which identification information from among the first to seventh identification information is included in the PDU session establishment request message, UE_A10 capability information, and / or policy such as UE policy, and / or UE_A10 preference. You may decide based on. Note that determination by UE_A10 which identification information is included in the PDU session establishment request message is not limited to this.
- CPF_A140 receives the PDU session establishment request message and executes the first condition determination.
- the first condition determination is for the CPF_A 140 to determine whether to accept the UE_A10 request.
- the CPF_A 140 determines whether the first condition is true or false.
- CPF_A140 starts the procedure (A) in the procedure when the first condition is true, and starts the procedure (B) in the procedure when the first condition is false. The steps when the first condition is false will be described later.
- CPF_A140 executes the procedure (C) in this procedure and starts the procedure (A) in this procedure. Furthermore, each step of the procedure (C) in this procedure will be explained. CPF_A140 first selects NSI and / or UPGW_A130 to connect to, sends a session creation request message to the selected UPGW_A130 or UPGW_A130 associated with the selected NSI, and starts the procedure (C) in this procedure (S1502).
- CPF_A140 may include at least one piece of identification information among the first to seventh 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 seventh 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.
- the PCRF_A60 may include one or more pieces of identification information among the eleventh to seventeenth identification information in the response message during the IP-CAN session establishment procedure, and by including these identification information, the UE_A10 It may indicate that the request has been accepted and / or authorized.
- PCRF_A60 may include one or more pieces of identification information of the eighteenth identification information in the response message during the IP-CAN session establishment procedure, and by including these pieces of identification information, the request of UE_A10 It may indicate that it has been rejected.
- UPGW_A130 may perform the third condition determination based on the result of the third condition determination received from PCRF_A60. For example, when the PCRF_A60 accepts the UE_A10 request, the PCRF_A60 and UPGW_A130 may set the third condition to be true. When the PCRF_A60 rejects the UE_A10 request, the PCRF_A60 and the UPGW_A130 may set the third condition to be false.
- UPGW_A 130 determines whether the third condition is true or false. If the third condition is true, UPGW_A 130 transmits a session creation response message to CPF_A 140 (S1506). Furthermore, CPF_A140 receives the session creation response message.
- UPGW_A130 may include one or more pieces of identification information among the eleventh to seventeenth pieces of identification information, may include an IP address, or may include these pieces of identification information.
- UE_A10 request may be permitted.
- UPGW_A 130 transmits a session creation rejection message to CPF_A 140 (S1508).
- the session creation rejection message may be a session creation response message including a rejection reason (Reject cause).
- UPGW_A130 may include one or more pieces of identification information of the 18th identification information in the session generation rejection message, and indicates that the request of UE_A10 has been rejected by including these identification information. May be.
- 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 message may be a PDN connection acceptance (PDNPDConnectivity Accept) message or a default EPS bearer context activation request (Activate default EPSbearer context request) message.
- PDU session establishment acceptance message may be a NAS 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 more of the identification information of the eleventh to seventeenth identification information, the IP address, or the identification information in the PDU session establishment acceptance message. Including it may indicate that the request of UE_A10 has been accepted.
- CPF_A140 may indicate the type of PDU session that the network permits and / or supports to establish by transmitting the 11th to 17th identification information. More specifically, the CPF_A 140 transmits the first identification information by transmitting the 11th identification information and / or the 15th identification information and / or the 14th identification information indicating the first type of PDU session. May indicate that the establishment of the PDU session is accepted and / or supported by the network.
- the CPF_A 140 transmits the twelfth identification PDU session by transmitting the twelfth identification information and / or the sixteenth identification information and / or the fourteenth identification information indicating the second type PDU session. Establishment may be accepted and / or supported by the network.
- the CPF_A 140 transmits the third identification information and / or the seventh identification information and / or the fourth identification information indicating the third type PDU session, so that the third type PDU session is transmitted. Establishment may be accepted and / or supported by the network.
- 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.
- the CPF_A 140 determines which identification information among the 11th to 17th identification information is to be included in the PDU session establishment acceptance message, such as the received identification information and / or network capability information, and / or operator policy. It may be determined based on policies and / or network conditions. Note that the determination by CPF_A 140 which identification information is included in the PDU session establishment acceptance message is not limited to this.
- 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 NAS message.
- the PDU session establishment completion message may be a response message to the PDU session establishment acceptance message, and is not limited to this, and may be a message indicating that the PDU session establishment procedure is completed.
- the second condition determination is for CPF_A140 to determine whether or not it is necessary to request UPGW_A130 to change the bearer. If the second condition is true, CPF_A140 starts the procedure (D) in this procedure. When the second condition determination is false, CPF_A140 does not execute the procedure (D) in this procedure. Hereinafter, each step of the procedure (D) in this procedure will be described.
- the CPF_A 140 transmits a bearer change request message to the SGW_A 35 (S1526), and starts the procedure (D) in this procedure. Furthermore, SGW_A35 receives the bearer change request message and transmits a bearer change response message to CPF_A140 (S1528).
- CPF_A140 receives the bearer change response message and completes the procedure (D) of this procedure.
- each device is based on the transmission / reception of a PDU session establishment completion message when the second condition determination is false, and / or when the second condition determination is true, Based on this, complete the procedure (A) in this procedure.
- CPF_A140 transmits a PDU session establishment rejection (PDU session establishmentreject) message to UE_A10 via NR node_A122 (S1530), and starts the procedure (B) in this procedure. Furthermore, UE_A10 receives the PDU session establishment rejection message and recognizes that the request for UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission / reception of the PDU session establishment rejection message.
- the PDU session establishment rejection message may include an appropriate rejection reason. If the PDU session is a PDN connection, the PDU session establishment rejection message may be a PDN connection rejection (PDN Connectivity reject) message.
- PDN Connectivity reject PDN connection rejection
- the PDU session establishment rejection message may be a NAS 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.
- CPF_A140 may include the 18th identification information in the PDU session establishment rejection message, or may indicate that the request of UE_A10 has been rejected by including these identification information.
- the CPF_A 140 may indicate the reason why the PDU session establishment procedure is rejected by transmitting the 18th identification information, or may indicate processing to be performed by each device after the PDU session establishment procedure. .
- 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 one or more pieces of identification information among eleventh to seventeenth pieces of identification information, UE_A10 may establish the type of PDU session indicated by each piece of identification information, or the type of established PDU session May be recognized as the type indicated by the identification information. Note that UE_A 10 may establish a default type PDU session regardless of the received identification information.
- UE_A10 may recognize the reason why the request of UE_A10 is rejected. Furthermore, UE_A10 may execute this procedure again under different conditions based on the reason why the request of UE_A10 is rejected, or may execute another procedure such as a tracking area update procedure.
- the first to third condition determinations described above may be executed based on identification information and / or subscriber information and / or operator policy included in the PDU session establishment request message. Further, the condition for determining whether the first to third conditions are true or false is not limited to the above-described conditions.
- the first condition and / or the third condition may be true when the UE_A 10 requests establishment of a PDU session and the network permits the request.
- the first condition and / or the third condition may be false when the UE_A 10 requests establishment of a PDU session and the network does not permit the request.
- the first condition and / or the third condition is true if the network to which UE_A10 is connected and / or a device in the network supports the establishment of a PDU session required by UE_A10. Well, if you don't support it, you can false.
- Attaching procedure example An example of a procedure for executing the attach procedure will be described with reference to FIG. Hereinafter, this procedure refers to the attach procedure.
- This procedure is a procedure for registering UE_A10 in the network.
- 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 NR node_A122 that has received the RRC message including the attach request message is configured as CPF_A140 as the NF or shared CP function of the 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 information included in the RRC message.
- the attach request message may be a NAS message.
- the UEA 10 may transmit one or more attach request messages existing for each NSI requesting connection in one RRC message, or collectively refer to a plurality of attach request messages as an attach request message. Also good. 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 of the identification information of the first to seventh and the identification information of the 21st in the attach request message and / or the RRC message. Including it may indicate a request for UE_A10.
- UE_A10 may indicate the type of PDU session that UE_A10 requests and / or supports establishment by transmitting the first to seventh identification information. More specifically, the UE_A 10 transmits the first identification information and / or the fifth identification information and / or the fourth identification information indicating the first type of PDU session, thereby transmitting the first type. May indicate that UE_A10 requests and / or supports UE_A10.
- the UE_A10 transmits the second identification information and / or the sixth identification information and / or the fourth identification information indicating the second type of PDU session, whereby the second type PDU session is transmitted. May indicate that UE_A10 requires and / or supports UE_A10.
- the UE_A10 transmits the third identification information and / or the seventh identification information, and / or the fourth identification information indicating the third type PDU session, whereby the third type PDU session is transmitted. May indicate that UE_A10 requires and / or supports UE_A10.
- UE_A10 may indicate that the current TA is the same as the previously connected TA or a different TA by transmitting the 21st identification information. UE_A10 may transmit the first to seventh identification information in association with the twenty-first identification information.
- UE_A10 which identification information among the first to seventh identification information and the 21st identification information is to be included in the attach request message, UE_A10 capability information and / or policies such as UE policy, and / or It may be determined based on the preference of UE_A10. The determination by UE_A10 which identification information is included in the attach request message is not limited to this.
- UE_A10 may transmit the identification information included in a control message different from the attach request message.
- UE_A10 may transmit the ESM information response message (S1602), which is a response message to the ESM (EPS Session Management) information request message, including the identification information.
- S1602 ESM information response message
- ESM EPS Session Management
- the CPF_A 140 receives the control message different from the attach request message and / or the attach request message, and executes the first condition determination. CPF_A140 starts the procedure (A) in the procedure when the first condition is true, and starts the procedure (B) in the procedure when the first condition is false.
- CPF_A140 executes the fourth condition determination and starts the procedure (A) in this procedure.
- the CPF_A 140 determines whether the fourth condition is true or false.
- the CPF_A 140 executes the procedure (C) in the UE-initiated PDU session establishment procedure when the fourth condition is true, and omits the procedure when the fourth condition is false (S1604).
- the CPF_A 140 transmits an attach accept message to the NR node_A 122 based on reception of the attach request message and / or session creation response message and / or completion of the procedure (C) during the PDN connection procedure. (S1606).
- CPF_A140 may start the procedure (B) in this procedure without continuing the procedure (A) in this procedure.
- the 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 attach acceptance message may be a response message to the attach request 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 or more identification information among the 11th to 17th identification information and the 31st to 32nd identification information in the attach acceptance message, or may include an IP address. Including these pieces of identification information may indicate that the request of UE_A10 has been accepted.
- CPF_A140 may indicate the type of PDU session that the network permits and / or supports to establish by transmitting the 11th to 17th identification information. More specifically, the CPF_A 140 is authorized by the network by transmitting eleventh identification information and / or fifteenth identification information and / or fourteenth identification information indicating the first type of PDU session.
- the type of PDU session being supported and / or supported may indicate a first type of PDU session.
- CPF_A140 is authorized by the network by sending twelfth identification information and / or sixteenth identification information and / or fourteenth identification information indicating a second type of PDU session. And / or the type of PDU session supported may indicate a second type of PDU session.
- CPF_A140 is authorized by the network by transmitting thirteenth identification information and / or seventeenth identification information and / or fourteenth identification information indicating a third type of PDU session.
- / or the supported PDU session type may indicate a third type of PDU session.
- CPF_A140 may indicate one or more TAs that the network has allowed to connect to UE_A10 by transmitting the 31st identification information, and without executing the tracking area update procedure after completing this procedure, An area where UE_A 10 can move may be indicated.
- the CPF_A 140 may transmit the eleventh to seventeenth identification information and the thirty-first identification information in association with each other, or by transmitting these associated identification information, the eleventh to seventeenth identification information It may indicate that establishment of a PDU session of the type indicated by is permitted and / or supported within the TA indicated by the 31st identification information.
- CPF_A140 may further transmit the thirty-second identification information, By transmitting the thirty-second identification information, when the PDU session is suspended, the time during which the suspension of the PDU session is valid may be indicated.
- CPF_A140 indicates which identification information among the 11th to 17th identification information and the 31st to 32nd identification information is included in the attach acceptance message, the received identification information, and / or network capability information, and It may be determined based on a policy such as an operator policy and / or a network state. Note that the determination by CPF_A 140 which identification information is included in the attach acceptance message is not limited to this.
- 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 attach completion message may be a NAS message. Further, the attach completion message may be a response message to the attach response message.
- the CPF_A 140 transmits an attach rejection message to the UE_A 10 via the NR node_A 122 (S1620), and starts the procedure (B) in this procedure. 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.
- 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 be a NAS message.
- the attach rejection message may be a response message to the attach request message, and is not limited to this, and may be a message rejecting registration of UE_A10 to the network.
- CPF_A140 may include the 18th identification information in the attach rejection message, or may indicate that the request of UE_A10 has been rejected by including these identification information.
- each device may recognize the reason why the attach procedure is rejected by transmitting and receiving the 18th identification information, or may indicate the processing to be performed by each device after the attach procedure, This procedure may be performed again, or the procedure may be performed under different conditions.
- 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 one or more pieces of identification information among eleventh to seventeenth identification information and thirty-first to thirty-second identification information, the UE_A10 transmits the type of PDU session indicated by each of the eleventh to seventeenth identification information It may be recognized that the establishment is permitted and / or supported by the TA indicated by the 31st identification information.
- UE_A10 may recognize the reason why the request of UE_A10 is rejected. Further, the UE_A 10 may perform this procedure again based on the reason that the request of the UE_A 10 is rejected, or may perform the attach procedure for the core network_A 90 or another cell.
- first to fourth condition determinations described above may be executed based on identification information and / or subscriber information and / or operator policy included in the attach request message.
- condition for determining whether the first to fourth conditions are true or false is not limited to the above-described conditions.
- the first condition determination and / or the third condition determination may be the same as the above-described PDU session establishment procedure example.
- each device transitions to the first state or the second state by executing a procedure associated with UE mobility.
- this procedure refers to a procedure associated with UE mobility.
- this procedure may include a procedure associated with the mobility of the first UE and a procedure associated with the mobility of the second UE.
- the procedure accompanying the mobility of the first UE may be a procedure executed by each device in the first state
- the procedure accompanying the mobility of the second UE is a procedure executed by each device in the second state. It may be.
- the procedure associated with the mobility of the first UE is a procedure executed when the UE_A 10 performs mobility across the TA when each device is in the first state.
- this procedure refers to a procedure associated with the mobility of the first UE, and each procedure includes a tracking area update procedure.
- NRnode_B123 may be arranged in the TA into which UE_A10 has newly invaded, and the tracking area update executed in this procedure may be executed for NRnode_A122.
- NR node_B123 may perform transmission / reception and processing of each message performed by NR node_A122 during the tracking area update procedure. Further, this procedure may be a procedure that can be executed at an arbitrary timing as long as each device is in the first state.
- Each device first executes a tracking area update procedure (S1804) in the first state (S1802).
- the tracking area update procedure may be executed based on mobility across the TA of UE_A 10 or may be executed periodically.
- the tracking area update procedure is not limited to this, and may be executed at an arbitrary timing as long as the tracking area update procedure is in the state of transition to the first state.
- each device may exchange various request information in the tracking area update procedure.
- the UE_A 10 and the core network_B 190 may use one or more of the first to fourth identification information and the twenty-first identification information and / or the eleventh to fourteenth identification information and the thirty-first identification information. To one or more of the thirty-sixth pieces of identification information may be exchanged.
- each device may transition to the second state based on completion of the tracking area update procedure.
- the state in which each device transitions based on the completion of the tracking area update procedure is not limited to this.
- 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 from the first state to the second state (S1806) based on the completion of this procedure.
- each device may start the execution of the first timer based on the transition to the second state. In other words, each device may start executing the first timer based on the suspension of the established PDU session. In other words, each device may start executing the first timer based on the completion of the tracking area update procedure. Furthermore, each device may execute the first timer using the timer value transmitted and received in the tracking area update procedure as the first timer value.
- UE_A10 may start the procedure associated with the mobility of the second UE, Each device may resume the suspended PDU session and may further stop the execution of the first timer. Conversely, when the execution of the first timer expires, the UE_A 10 may start a procedure associated with the mobility of the second UE, and each device may disconnect the suspended PDU session.
- the tracking area that UE_A10 has previously connected may be a tracking area included in the TA list that UE_A10 has held before executing the tracking area update procedure.
- the procedure associated with the mobility of the second UE is a procedure executed when the UE_A 10 performs mobility across the TA when each device is in the second state.
- this procedure refers to a procedure associated with the mobility of the second UE, and each procedure includes a tracking area update procedure.
- NRnode_B122 may be arranged in the TA into which UE_A10 has newly invaded, and the tracking area update executed in this procedure may be executed for NRnode_A122. Further, this procedure may be a procedure that can be executed at an arbitrary timing as long as each device is in the second state.
- Each device first executes a tracking area update procedure (S204) in the second state (S202).
- the tracking area update procedure may be executed based on mobility across the TA of UE_A 10 or may be executed periodically.
- the tracking area update procedure is not limited to this, and may be executed at an arbitrary timing as long as the procedure transits to the second state.
- each device may exchange various request information in the tracking area update procedure.
- the UE_A 10 and the core network_B 190 may use one or more of the second to fourth identification information and the twenty-first identification information, and / or the twenty-first to fourteenth identification information and the thirty-first identification information. To one or more of the thirty-sixth pieces of identification information may be exchanged.
- each device may transition to the first state based on the completion of the tracking area update procedure.
- the state in which each device transitions based on the completion of the tracking area update procedure is not limited to this.
- 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 from the second state to the first state (S206) based on the completion of this procedure.
- 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 may start this procedure when performing mobility across TAs. In other words, the UE_A 10 may start this procedure when entering a TA different from the TA indicated in the held TA list. Furthermore, UE_A10 may start this procedure when the running timer expires. Further, UE_A 10 may start this procedure when the context of each device needs to be updated due to disconnection or invalidation of the PDU session and / or EPS bearer. Furthermore, UE_A10 may start this procedure, when the capability information regarding a PDU session establishment of UE_A10 and / or a preference change arise. Furthermore, UE_A10 may start this procedure periodically. Note that the UE_A 10 is not limited to these, and can execute this procedure at an arbitrary timing as long as the PDU session is established.
- UE_A10 may start this procedure in the first state or the second state, and may transition to the first state or the second state based on the completion of this procedure. More specifically, when UE_A10 starts this procedure in the state of the first state, whether each device transitions to the first state or the second state based on identification information transmitted / received And transition to the determined state. Furthermore, when UE_A10 starts this procedure in the second state, each device determines whether to transition to the first state or the second state based on identification information to be transmitted / received. The transition to the determined state may be made.
- 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 information included in the RRC message.
- the tracking area update request message may be a NAS message.
- the NR node_A 122 may be an access network device in the TA to which the UE_A 10 is currently connected. Therefore, NR node_A122 may be NR node_B123, and transmission / reception of each message performed by NR node_A122 during this procedure may be performed by NR node_B123 instead of NR node_A122.
- the UE_A10 may include at least one of identification information from the first to fourth identification information and the identification information from the 21st to 22nd in the tracking area update request message and / or the RRC message,
- the request of UE_A10 may be indicated by including these pieces of identification information.
- UE_A10 may indicate the type of PDU session supported by UE_A10 by transmitting the first to fourth identification information. More specifically, UE_A10 supports the first type of PDU session by transmitting first identification information and / or fourth identification information indicating the first type of PDU session. You may show that.
- UE_A10 indicates that UE_A10 supports the second type PDU session by transmitting the second identification information and / or the fourth identification information indicating the second type PDU session. May be.
- UE_A10 supports the establishment of the third type PDU session by transmitting the third identification information and / or the fourth identification information indicating the third type PDU session. May be indicated.
- UE_A10 may transmit the same identification information included in the tracking area update request message as the identification information exchanged in the attach procedure and / or the PDU session establishment procedure, or send different identification information in the tracking area update request message. May be included in the transmission.
- UE_A10 includes in the tracking area update procedure the identification information indicating the same type of PDU session as the type of PDU session established and / or used in the attach procedure and / or PDU session establishment procedure.
- the identification information indicating different types of PDU sessions may be included in the tracking area update procedure for transmission.
- UE_A10 may indicate that the current TA is the same as the previously connected TA or a different TA by transmitting the 21st identification information. UE_A10 may transmit the first to seventh identification information in association with the twenty-first identification information.
- UE_A10 may indicate that there is an activated PDU session or may indicate that there is a suspended PDU session by transmitting the 22nd identification information. Further, the UE_A 10 transmits the suspended PDU by transmitting the 21st identification information indicating the previously connected TA and / or the 22nd identification information indicating that there is a suspended PDU session. A session resume may be requested.
- UE_A10 determines which identification information is included in the tracking area update request message among the first to fourth identification information and the 21st to 22nd identification information, and the UE_A10 capability information and / or a policy such as a UE policy. And / or based on UE_A10 preferences. Note that the determination by UE_A10 which identification information is included in the tracking area update request message is not limited to this.
- CPF_A140 receives the tracking area update request message and executes the first condition determination. In the first condition determination, the CPF_A 140 determines whether the first condition is true or false. CPF_A140 starts the procedure (A) in the procedure when the first condition is true, and starts the procedure (B) in the procedure when the first condition is false. The steps when the first condition is false will be described later.
- CPF_A140 executes the fourth condition determination and starts the procedure (A) in this procedure.
- the CPF_A 140 determines whether the fourth condition is true or false.
- the CPF_A 140 starts the procedure (C) in this procedure when the fourth condition is true, and omits the procedure when the fourth condition is false (S1703).
- the first condition determination may be the same as the first condition determination during the attach procedure.
- the fourth condition determination is for determining whether or not a PDU session change and / or addition and / or deletion procedure is necessary.
- the procedure (C) in this procedure may be a procedure for transmitting / receiving a message between devices in the network, and may be a procedure for updating and / or sharing a context. Therefore, the details of the procedure are omitted.
- CPF_A140 may include at least one of the identification information from the first to the fourth identification information and the 21st identification information in the message during the procedure of (C) in this procedure, or these By including the identification information, UE_A10 request may be transmitted to each device.
- CPF_A140 includes at least one of identification information of 11th to 14th and identification information of 31st to 36th and / or 18th Identification information may be included, and by including these identification information, a determination regarding the request of the UE_A10 of the network may be transmitted to each device.
- CPF_A140 executes the third condition determination after the procedure (C) is completed.
- the third condition determination is for determining whether CPF_A140 accepts the UE_A10 request, and the third condition determination is received from any device during the procedure of (C). It may be determined based on the information. In the third condition determination, CPF_A 140 determines whether the third condition is true or false.
- CPF_A140 sends the tracking area update acceptance (Tracking Area Updateaccept) message to UE_A10 via NR node_A122 if the third condition is true (S1706). If the condition is false, the procedure (B) in this procedure is started.
- 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 included 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 tracking area update acceptance message may be a response message to the tracking area update request 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 or more of the 11th to 14th identification information and the 31st to 36th identification information in the tracking area update acceptance message, or include these identification information. Thus, it may indicate that the request of UE_A10 has been accepted, or may indicate the state of the PDU session after the completion of this procedure.
- CPF_A140 may indicate the type of PDU session supported by the network by transmitting the 11th to 14th identification information. More specifically, CPF_A140 is allowed and / or supported by the network by sending eleventh identification information and / or fourteenth identification information indicating a first type of PDU session. It may indicate that the type of the PDU session being used is the first type of PDU session.
- the CPF_A 140 transmits the twelfth identification information and / or the fourteenth identification information indicating the second type of PDU session, so that the PDU is permitted and / or supported by the network.
- the session type may indicate that it is a second type of PDU session.
- the CPF_A 140 transmits the thirteenth identification information and / or the fourteenth identification information indicating the third type of PDU session, so that the PDU is permitted and / or supported by the network.
- the session type may indicate that it is a third type PDU session.
- CPF_A140 may indicate one or more TAs that the network has allowed to connect to UE_A10 by transmitting the 31st identification information, and may execute a new tracking area update procedure after this procedure is completed. Alternatively, the area in which UE_A 10 can move may be indicated.
- the CPF_A 140 may transmit the 11th to 14th identification information and the 31st identification information in association with each other, or by transmitting these associated identification information, the 11th to 14th identification information It may indicate that establishment of a PDU session of the type indicated by is permitted and / or supported within the TA indicated by the 31st identification information.
- CPF_A140 may indicate the status of the PDU session after the completion of this procedure by transmitting the 33rd to 36th identification information. More specifically, the 33rd identification information may be transmitted to indicate that there is a PDU session and / or EPS bearer to be disconnected, and to identify the PDU session and / or EPS bearer to be disconnected. May be. Further, by transmitting the thirty-fourth identification information, it may be indicated that there is a PDU session and / or EPS bearer to be suspended, or a PDU session and / or EPS bearer to be suspended may be identified. Good.
- the 35th identification information may indicate that there is a resumed PDU session and / or EPS bearer, or the resumed PDU session and / or EPS bearer may be identified. Good. Further, the 36th identification information may be transmitted to indicate that there is a PDU session and / or EPS bearer for which the session is continued, and to identify the PDU session and / or EPS bearer for which the session is continued. May be.
- CPF_A140 may further transmit the 32nd identification information, By transmitting the thirty-second identification information, when the PDU session is suspended, the time during which the suspension of the PDU session is valid may be indicated. Further, when there is a suspended PDU session and / or EPS bearer, CPF_A140 may further transmit the 32nd identification information, or the PDU by transmitting the 32nd identification information. The session and / or EPS bearer suspend time may be indicated.
- the CPF_A 140 indicates which identification information among the 11th to 14th identification information and the 31st to 36th identification information is included in the tracking area update acceptance message, the received identification information, and / or network capability information. And / or based on policies such as operator policies and / or network conditions.
- the determination by CPF_A 140 which identification information is included in the tracking area update acceptance message is not limited to this.
- UE_A10 may transmit a tracking area update complete (Tracking Area Update) message to CPF_A140 via NR node_A122 (S1710).
- the tracking area update completion message may be a NAS message.
- the tracking area update completion message may be a response message to the tracking area update response message.
- Each device completes the procedure (A) in this procedure based on transmission / reception of a tracking area update completion message and / or transmission / reception of a tracking area update acceptance message.
- the CPF_A 140 transmits a tracking area update rejection (Tracking Area Update reject) message to the UE_A10 via the NR node_A122 (S1720), and starts the procedure (B) in this procedure. Furthermore, UE_A10 receives the tracking area update rejection message and recognizes that the request of UE_A10 has been rejected. Each device completes the procedure (B) in this procedure based on the transmission / reception of the tracking area update rejection message.
- the tracking area update rejection message may include an appropriate reason for rejection.
- the tracking area update rejection message may be a NAS message. Further, 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.
- CPF_A140 may include the 18th identification information in the tracking area update rejection message, or may indicate that the request of UE_A10 has been rejected by including these identification information.
- the CPF_A 140 may recognize the reason why the tracking area update procedure is rejected by transmitting and receiving the 18th identification information, or may indicate processing to be performed by each device after the tracking area update procedure. This procedure may be performed again under different conditions, or a procedure other than this procedure may be performed.
- 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 one or more pieces of identification information among eleventh to fourteenth identification information and thirty-first to thirty-sixth identification information, the type of PDU session indicated by each of the eleventh to fourteenth identification information is The TA indicated by the thirty-first identification information may recognize that it is permitted and / or supported.
- UE_A10 may recognize that a part or all of the PDU session and / or EPS bearer has been updated, It may be recognized that some or all of the EPS bearer needs to be updated.
- the UE_A10 may recognize that part or all of the PDU session and / or EPS bearer has been disconnected, or the disconnected PDU session, And / or the context related to the EPS bearer may be invalidated and / or released. Furthermore, when the UE_A 10 receives the thirty-fourth identification information, the UE_A 10 may recognize that part or all of the PDU session and / or EPS bearer has been suspended without being disconnected. Furthermore, when the UE_A 10 receives the 35th identification information, the UE_A 10 may recognize that part or all of the PDU session and / or the EPS bearer has returned from the suspended state.
- the UE_A 10 may recognize that part or all of the PDU session and / or EPS bearer has been continued without being disconnected. Further, when there is a suspended PDU session and / or EPS bearer, UE_A10 may start the execution of the first timer, and the value indicated by the 32nd identification information is the value of the first timer. May be set as
- each device may transition from the first state to the second state when transmitting and receiving the 35th identification information. Furthermore, each device may transition from the second state to the first state when transmitting and receiving the thirty-sixth identification information. Note that the condition for each device to transition to the first state or the second state is not limited to this.
- 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)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
図1は、本実施形態における移動通信システムの概略を説明する為の図である。本図に示すように、移動通信システム1は、移動端末装置UE_A10とアクセスネットワーク_Bとコアネットワーク_B190とPDN(PacketData Network)_A5により構成されている。ここで、UE_A10は無線接続可能な端末装置であればよく、UE(User Equipment)、ME(Mobile Equipment)、MS(Mobile Station)、又はCIoT(Cellular Internetof Things)端末(CIoT UE)等でもよい。さらに、コアネットワークは、コアネットワーク_B190であってもよく、アクセスネットワークは、アクセスネットワーク_Bであってもよい。さらに、コアネットワークは、コアネットワーク装置であってもよい。もしくは、本実施形態において、コアネットワーク装置とは、コアネットワーク_B190に含まれる各装置及び/又は各装置の処理又は機能の一部又は全てを実行する装置であってよい。アクセスネットワーク_Bは、NextGen RAN_A120及び/又は、E-UTRAN_A80及び/又は、WLAN ANc125であってよい。
まず、各装置で記憶される識別情報について説明する。IMSI(International MobileSubscriber Identity)は、加入者(ユーザ)の永久的な識別情報であり、UEを使用するユーザに割り当てられる識別情報である。UE_A10及びMME_A40/CPF_A140及びSGW_A35が記憶するIMSIは、HSS_A50が記憶するIMSIと等しくてよい。
図4にUE_A10の装置構成を示す。図に示すように、UE_A10は、送受信部_A420と制御部_A400と記憶部_A440とで構成されている。送受信部_A420と記憶部_A440は、制御部_A400とバスを介して接続されている。制御部_A400はUE_A10を制御する為の機能部である。制御部_A400は、記憶部_A440に記憶されている各種プログラムを読みだして実行する事により各種処理を実現する。
以下、eNB_A45、NR node_A122、及びWAG_A126の構成について説明する。図6にeNB_A45、NR node_A122、及びWAG_A126の装置構成を示す。図に示すように、eNB_A45、NR node_A122、及びWAG_A126は、ネットワーク接続部_B620と送受信部_B630と制御部_B600と記憶部_B640で構成されている。ネットワーク接続部_B620と送受信部_B630と記憶部_B640は、制御部_B600とバスを介して接続されている。
以下、MME_A40及びCPF_140の構成について説明する。図7にMME_A40及びCPF_140の装置構成を示す。図に示すように、MME_A40及びCPF_140は、ネットワーク接続部_C720と制御部_C700と記憶部_C740で構成されている。ネットワーク接続部_C720と記憶部_C740は、制御部_C700とバスを介して接続されている。なお、これらの各部の機能は、物理的なハードウェア上で動作するものでもよいし、仮想的に汎用的なハードウェア上に構成された論理的なハードウェア上で動作するものでもよい。
図10にSGW_A35の装置構成を示す。図に示すように、SGW_A35はネットワーク接続部_D1020と制御部_D1000と記憶部_D1040とで構成されている。ネットワーク接続部_D1020と記憶部_D1040は、制御部_D1000とバスを介して接続されている。
図10にPGW_A30及びUPGW_A130の装置構成を示す。図に示すように、PGW_A30及びUPGW_A130はネットワーク接続部_D1020と制御部_D1000と記憶部_D1040とで構成されている。ネットワーク接続部_D1020と記憶部_D1040は、制御部_D1000とバスを介して接続されている。なお、これらの各部の機能は、物理的なハードウェア上で動作するものでもよいし、仮想的に汎用的なハードウェア上に構成された論理的なハードウェア上で動作するものでもよい。
図10にSCEF_A46の装置構成を示す。図に示すように、SCEF_A46は、ネットワーク接続部_D1020と制御部_D1000と記憶部_D1040で構成されている。ネットワーク接続部_D1020と記憶部_D1040は、制御部_D1000とバスを介して接続されている。
次に、本実施形態における初期手続きの詳細手順を説明する前に、重複説明を避ける為、本実施形態特有の用語や、各手続きに用いる主要な識別情報を予め説明する。
まず、アタッチ手続きの概要について説明する。アタッチ手続きは、UE_A10が主導してネットワーク(アクセスネットワーク、及び/又はコアネットワーク_B190、及び/又はPDN_A5)へ接続する為の手続きである。UE_A10は、ネットワークに接続していない状態であれば、端末電源投入時等の任意のタイミングで本手続きを実行する事ができる。言い換えると、UE_A10は、登録されていない状態(EMM-DEREGISTERED)であれば任意のタイミングで本手続きを開始してもよい。また、各装置は、アタッチ手続き完了に基づいて、登録状態(EMM-REGISTERED)に遷移してもよい。
次に、PDUセッション確立手続きの例について説明する。以下、本手続きはPDUセッション確立手続きを指す。本手続きは、各装置がPDUセッションを確立する為の手続きである。なお、各装置は、本手続きを、アタッチ手続きを完了した状態で実行してもよいし、アタッチ手続きの中で実行してもよい。また、各装置は、登録状態で本手続きを開始してもよいし、アタッチ手続き後の任意のタイミングで本手続きを開始してもよい。また、各装置は、PDUセッション確立手続きの完了に基づいて、PDUセッションを確立してもよい。さらに、各装置は、本手続きを複数回実行する事で、複数のPDUセッションを確立してもよい。
図15を用いて、PDUセッション確立手続きを実行する手順の例を説明する。以下、本手続きの各ステップについて説明する。まず、UE_A10は、NR node_A122を介してCPF_A140にPDUセッション確立要求(PDU Session Establishment Request)メッセージを送信し(S1500)、PDUセッション確立手続きを開始する。なお、PDUセッションがPDNコネクション(PDN connection)である場合、PDUセッション確立要求メッセージはPDN接続要求(PDN connectivity request)メッセージでよい。さらに、PDUセッション確立要求メッセージは、NAS(Non-Access-Stratum)メッセージであってよい。また、PDUセッション確立要求メッセージは、これに限らず、PDUセッションの確立を要求するメッセージであればよい。
図16を用いて、アタッチ手続きを実行する手順の例を説明する。以下、本手続きとはアタッチ手続きを指す。本手続きは、UE_A10がネットワークに登録されるための手続きである。以下、本手続きの各ステップについて説明する。まず、UE_A10は、NR node_A122を介してCPF_A140にアタッチ要求(Attach request)メッセージを送信し(S1600)、アタッチ手続きを開始する。UE_A10は、アタッチ要求メッセージに、前述したPDUセッション確立要求メッセージを含めて送信してもよいし、PDUセッション確立要求メッセージを含める事で、アタッチ手続き中でPDUセッション確立手続きを実施する事を要求してもよい。
次に、UEのモビリティに伴う手続きを用いて説明する。本実施形態では、各装置は、UEのモビリティに伴う手続きを実行することで、第1の状態又は第2の状態に遷移する。以下、本手続きは、UEのモビリティに伴う手続きを指す。
次に、第1のUEのモビリティに伴う手続きを図18を用いて説明する。第1のUEのモビリティに伴う手続きは、各装置が第1の状態である場合において、UE_A10がTAを跨いだモビリティを行った際に実行される手続きである。以下、本手続きは、第1のUEのモビリティに伴う手続きを指し、各手続きには、トラッキングエリア更新手続きがある。さらに、UE_A10が新たに侵入したTAには、NRnode_B123が配置されていてもよく、本手続き中で実行されるトラッキングエリア更新は、NRnode_A122に対して実行されてよい。この場合、トラッキングエリア更新手続き中でNR node_A122が実施する各メッセージの送受信及び各処理は、NR node_B123が実施してもよい。さらに、本手続きは、各装置が第1の状態であれば、任意のタイミングで実行可能である手続きであってもよい。
次に、第2のUEのモビリティに伴う手続きを図2を用いて説明する。第2のUEのモビリティに伴う手続きは、各装置が第2の状態である場合において、UE_A10がTAを跨いだモビリティを行った際に実行される手続きである。以下、本手続きは、第2のUEのモビリティに伴う手続きを指し、各手続きには、トラッキングエリア更新手続きがある。さらに、UE_A10が新たに侵入したTAには、NRnode_B122が配置されていてもよく、本手続き中で実行されるトラッキングエリア更新は、NRnode_A122に対して実行されてよい。さらに、本手続きは、各装置が第2の状態であれば、任意のタイミングで実行可能である手続きであってもよい。
トラッキングエリア更新手続き(Tracking Area Update Procedure)の概要について説明する。以下、本手続きは、トラッキングエリア更新手続きを指す。本手続きは、ネットワーク(アクセスネットワーク、及び/又は、コアネットワーク_B190)におけるUE_A10の位置登録情報を更新する、及び/又は、UE_A10からネットワークへ定期的にUE_A10の状態を通知する、及び/又は、ネットワークにおけるUE_A10に関する特定のパラメータを更新する為の手続きである。
図17を用いて、トラッキングエリア更新手続きを実行する手順の例を説明する。以下、本手続きの各ステップについて説明する。まずUE_A10は、NR node_A122を介してCPF_A140にトラッキングエリア更新要求(Tracking Area Updaterequest)メッセージを送信し(S1700)、トラッキングエリア更新手続きを開始する。
本発明に関わる装置で動作するプログラムは、本発明に関わる実施形態の機能を実現するように、CentralProcessing Unit(CPU)等を制御してコンピュータを機能させるプログラムであっても良い。プログラムあるいはプログラムによって取り扱われる情報は、一時的にRandom Access Memory(RAM)等の揮発性メモリあるいはフラッシュメモリ等の不揮発性メモリやHard Disk Drive(HDD)、あるいはその他の記憶装置システムに格納される。
5 PDN_A
10 UE_A
30 PGW_A
35 SGW_A
40 MME_A
42 SGSN_A
45 eNB_A
46 SCEF_A
50 HSS_A
60 PCRF_A
80 E-UTRAN_A
120 NextGen RAN_A
122 NR node_A
123 NR node_B
125 WLAN ANc
126 WAG_A
130 UPGW_A
140 CPF_A
190 コアネットワーク_B
Claims (20)
- 端末装置であって、
前記端末装置は、コアネットワークに含まれる装置との間で、
PDUセッション確立手続きを実行し、
トラッキングエリアAからトラッキングエリアBに移動した際に、さらに、トラッキングエリア更新手続きを実行する
送受信部と、
前記PDUセッション確立手続きの完了に基づいて、PDUセッションを確立し、
前記トラッキングエリア更新手続きの完了に基づいて、前記PDUセッションをサスペンドし、さらに、前記PDUセッションの状態を管理するためのタイマーを実行する
制御部とを備え、
前記トラッキングエリアAは、前記トラッキングエリア更新手続きの実行前に前記端末装置が保持しているトラッキングエリアリストに含まれるトラッキングエリアであり、
前記トラッキングエリアBは、前記トラッキングエリアAとは異なるトラッキングエリアであり、さらに、前記トラッキングエリアリストに含まれないトラッキングエリアである
ことを特徴とする端末装置。 - 前記送受信は、前記PDUセッションがサスペンドされた状態で、前記端末装置が前記トラッキングエリアBから前記トラッキングエリアAに移動した場合は、
トラッキングエリア更新要求メッセージを、前記コアネットワークに含まれる装置に送信し、
情報Aを含むトラッキングエリア更新受諾メッセージを、前記コアネットワークに含まれる装置から受信し、
前記制御部は、
前記コアネットワークに含まれる装置から前記情報Aを受信した場合は、前記PDUセッションをレジュームし、
前記タイマーが満了した場合は、前記PDUセッションを切断し、
前記情報Aは、前記PDUセッションがレジュームされること示す情報である
ことを特徴とする請求項1に記載の端末装置。 - 前記送受信は、さらに、アタッチ手続きを実行し、
前記アタッチ手続きにおいて、
前記トラッキングエリアリストと、情報Bとを、前記コアネットワーク含まれる装置から受信し、
前記情報Bは、前記コアネットワークが前記PDUセッションをサポートすること示す情報である
ことを特徴とする請求項1又は請求項2に記載の端末装置。 - 前記送受信は、前記PDUセッション確立手続きにおいて、
情報Cを、前記コアネットワーク含まれる装置から受信し、
前記情報Cは、前記PDUセッションがサスペンド可能なPDUセッションであることを示す情報である
ことを特徴とする請求項1から請求項3の何れか一項に記載の端末装置。 - 前記送受信は、前記トラッキングエリア更新手続きにおいて、
前記トラッキングエリアリストとは異なるトラッキングエリアリストと、前記タイマーの値とを、前記コアネットワーク含まれる装置から受信する
ことを特徴とする請求項1から請求項4の何れか一項に記載の端末装置。 - コアネットワークに含まれる装置であって、
前記コアネットワークに含まれる装置は、端末装置との間で、
PDUセッション確立手続きと、トラッキングエリア更新手続きとを実行する
送受信部と、
前記PDUセッション確立手続きの完了に基づいて、前記コアネットワークと前記端末装置との間でPDUセッションを確立し、
前記トラッキングエリア更新手続きの完了に基づいて、前記PDUセッションをサスペンドし、さらに、前記PDUセッションの状態を管理するためのタイマーを実行する
制御部と、
を備えることを特徴とするコアネットワークに含まれる装置。 - 前記送受信は、前記PDUセッションがサスペンドされた状態で、トラッキングエリア更新要求メッセージを、前記端末装置から受信した場合は、情報Aを含むトラッキングエリア更新受諾メッセージを、前記端末装置に送信し、
前記制御部は、
前記PDUセッションがレジュームされること示す情報を、前記端末装置に送信した場合は、前記PDUセッションをレジュームし、
前記タイマーが満了した場合は、前記PDUセッションを切断し、
前記情報Aは、前記PDUセッションがレジュームされること示す情報である
ことを特徴とする請求項6に記載のコアネットワークに含まれる装置。 - 前記送受信は、さらに、アタッチ手続きを実行し、
前記アタッチ手続きにおいて、
トラッキングエリアリストと、情報Bとを、前記端末装置に送信し、
前記情報Bは、前記コアネットワークが前記PDUセッションをサポートすること示す情報である
ことを特徴とする請求項6又は請求項7に記載のコアネットワークに含まれる装置。 - 前記送受信は、前記PDUセッション確立手続きにおいて、
情報Cを、前記端末装置に送信し、
前記情報Cは、前記PDUセッションがサスペンド可能なPDUセッションであることを示す情報である
ことを特徴とする請求項6から請求項8の何れか一項に記載のコアネットワークに含まれる装置。 - 前記送受信は、前記トラッキングエリア更新手続きにおいて、
前記トラッキングエリアリストとは異なるトラッキングエリアリストと、前記タイマーの値とを、前記端末装置に送信する
ことを特徴とする請求項6から請求項9の何れか一項に記載のコアネットワークに含まれる装置。 - 端末装置の通信制御方法であって、コアネットワークに含まれる装置との間で、
PDUセッション確立手続きを実行するステップと、
前記PDUセッション確立手続きの完了に基づいて、PDUセッションを確立するステップと、
トラッキングエリアAからトラッキングエリアBに移動した際に、さらに、トラッキングエリア更新手続きを実行するステップと、
前記トラッキングエリア更新手続きの完了に基づいて、前記PDUセッションをサスペンドするステップと、
前記PDUセッションの状態を管理するためのタイマーを実行するステップとを有し、
前記トラッキングエリアAは、前記トラッキングエリア更新手続きの実行前に前記端末装置が保持しているトラッキングエリアリストに含まれるトラッキングエリアであり、
前記トラッキングエリアBは、前記トラッキングエリアAとは異なるトラッキングエリアであり、さらに、前記トラッキングエリアリストに含まれないトラッキングエリアである
ことを特徴とする端末装置の通信制御方法。 - 前記PDUセッションがサスペンドされた状態で、前記端末装置が前記トラッキングエリアBから前記トラッキングエリアAに移動した場合は、
トラッキングエリア更新要求メッセージを、前記コアネットワークに含まれる装置に送信するステップと、
情報Aを含むトラッキングエリア更新受諾メッセージを、前記コアネットワークに含まれる装置から受信するステップと、
前記PDUセッションをレジュームするステップとを有し、
前記タイマーが満了した場合は、前記PDUセッションを切断するステップを有し、
前記情報Aは、前記PDUセッションがレジュームされること示す情報である
ことを特徴とする請求項11に記載の端末装置の通信制御方法。 - アタッチ手続きを実行するステップをさらに有し、
前記アタッチ手続きにおいて、
前記トラッキングエリアリストと、情報Bとを、前記コアネットワーク含まれる装置から受信するステップを有し、
前記情報Bは、前記コアネットワークが前記PDUセッションをサポートすること示す情報である
ことを特徴とする請求項11又は請求項12に記載の端末装置の通信制御方法。 - 前記PDUセッション確立手続きにおいて、
情報Cを、前記コアネットワーク含まれる装置から受信するステップをさらに有し、
前記情報Cは、前記PDUセッションがサスペンド可能なPDUセッションであることを示す情報である
ことを特徴とする請求項11から請求項13の何れか一項に記載の端末装置の通信制御方法。 - 前記トラッキングエリア更新手続きにおいて、
前記トラッキングエリアリストとは異なるトラッキングエリアリストと、前記タイマーの値とを、前記コアネットワーク含まれる装置から受信するステップをさらに有す
ことを特徴とする請求項11から請求項14の何れか一項に記載の端末装置の通信制御方法。 - コアネットワークに含まれる装置の通信制御方法であって、端末装置との間で、
PDUセッション確立手続きを実行するステップと、
前記PDUセッション確立手続きの完了に基づいて、前記コアネットワークと前記端末装置との間でPDUセッションを確立するステップと、
トラッキングエリア更新手続きとを実行するステップと、
前記トラッキングエリア更新手続きの完了に基づいて、前記PDUセッションをサスペンドするステップと、
前記PDUセッションの状態を管理するためのタイマーを実行するステップとを有する
ことを特徴とするコアネットワークに含まれる装置の通信制御方法。 - 前記PDUセッションがサスペンドされた状態で、さらに、トラッキングエリア更新要求メッセージを、前記端末装置から受信した場合は、
前記PDUセッションがレジュームされること示す情報を、前記端末装置に送信するステップと、
前記PDUセッションをレジュームするステップを有し
前記タイマーが満了した場合は、前記PDUセッションを切断するステップを有する
ことを特徴とする請求項16に記載のコアネットワークに含まれる装置の通信制御方法。 - アタッチ手続きを実行するステップをさらに有し、
前記アタッチ手続きにおいて、
トラッキングエリアリストと、前記コアネットワークが前記PDUセッションをサポートすること示す情報とを、前記端末装置に送信するステップを有する
ことを特徴とする請求項16又は請求項17に記載のコアネットワークに含まれる装置の通信制御方法。 - 前記PDUセッション確立手続きにおいて、
前記PDUセッションがサスペンド可能なPDUセッションであることを示す情報を、前記端末装置に送信するステップをさらに有する
ことを特徴とする請求項16から請求項18の何れか一項に記載のコアネットワークに含まれる装置の通信制御方法。 - 前記トラッキングエリア更新手続きにおいて、
前記トラッキングエリアリストとは異なるトラッキングエリアリストと、前記タイマーの値とを、前記端末装置に送信するステップをさらに有する
ことを特徴とする請求項16から請求項19の何れか一項に記載のコアネットワークに含まれる装置の通信制御方法。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA3049321A CA3049321A1 (en) | 2017-01-05 | 2017-12-26 | Terminal apparatus, core network apparatus, and communication control method |
BR112019013919A BR112019013919A2 (pt) | 2017-01-05 | 2017-12-26 | aparelho terminal, aparelho de rede principal e método de controle de comunicação |
US16/476,095 US20190335413A1 (en) | 2017-01-05 | 2017-12-26 | Terminal apparatus, core network apparatus, and communication control method |
CN201780082211.6A CN110140394B (zh) | 2017-01-05 | 2017-12-26 | 终端装置、核心网装置以及通信控制方法 |
EP17889668.4A EP3567941A4 (en) | 2017-01-05 | 2017-12-26 | TERMINAL DEVICE, CENTRAL NETWORK DEVICE AND COMMUNICATION CONTROL PROCESS |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2017-000509 | 2017-01-05 | ||
JP2017000509A JP2020036055A (ja) | 2017-01-05 | 2017-01-05 | 端末装置、コアネットワーク装置、及び通信制御方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018128127A1 true WO2018128127A1 (ja) | 2018-07-12 |
Family
ID=62790935
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2017/046638 WO2018128127A1 (ja) | 2017-01-05 | 2017-12-26 | 端末装置、コアネットワーク装置、及び通信制御方法 |
Country Status (7)
Country | Link |
---|---|
US (1) | US20190335413A1 (ja) |
EP (1) | EP3567941A4 (ja) |
JP (1) | JP2020036055A (ja) |
CN (1) | CN110140394B (ja) |
BR (1) | BR112019013919A2 (ja) |
CA (1) | CA3049321A1 (ja) |
WO (1) | WO2018128127A1 (ja) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3534669B1 (en) * | 2017-08-14 | 2021-06-23 | HTC Corporation | Device and method of handling an interworking procedure |
US10757611B2 (en) * | 2017-09-22 | 2020-08-25 | Ofinno, Llc | SMF and AMF relocation during UE registration |
WO2020060007A1 (ko) * | 2018-09-17 | 2020-03-26 | 엘지전자 주식회사 | 5g 이동통신에서 pdu 세션을 핸들링하는 방법 및 무선 기기 |
CN112840732B (zh) * | 2018-10-10 | 2025-02-28 | 德国电信股份有限公司 | 控制对电信网络的用户面无线电通信资源的使用和/或接入 |
US12219646B2 (en) * | 2019-08-22 | 2025-02-04 | Lg Electronics Inc. | Operation method of relay UE for remote UE |
CN115412946A (zh) * | 2021-05-28 | 2022-11-29 | 展讯半导体(南京)有限公司 | 移动通信局域网建立方法及装置 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060087973A1 (en) * | 2004-10-22 | 2006-04-27 | Henry Huang | Delay timers for managing internal state changes and messages in user equipment for real-time multimedia applications |
JP2014512742A (ja) * | 2011-03-16 | 2014-05-22 | クアルコム,インコーポレイテッド | 無線アクセス技術間のサービス再試行中にセッションコンテキストを保存するための方法および装置 |
JP2017000509A (ja) | 2015-06-12 | 2017-01-05 | ダンロップスポーツ株式会社 | ゴルフボール用樹脂組成物およびゴルフボール |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8515465B2 (en) * | 2009-09-02 | 2013-08-20 | Telefonaktiebolaget L M Ericsson (Publ) | Solution for paging differentiation in communication network |
KR101422043B1 (ko) * | 2010-11-04 | 2014-07-30 | 엘지전자 주식회사 | 무선 통신 시스템에서 릴레이 노드가 기지국과의 연결을 재설정하는 방법 및 이를 위한 장치 |
WO2012100199A2 (en) * | 2011-01-21 | 2012-07-26 | Research In Motion Limted | Network apparatus and process to determine the connection context for connections used for (local) offloading |
US20120250601A1 (en) * | 2011-03-28 | 2012-10-04 | Hyung-Nam Choi | Communication terminal, method for exchanging data, communication device and method for establishing a communication connection |
CN103875283A (zh) * | 2011-09-30 | 2014-06-18 | 交互数字专利控股公司 | 用于启用被管理的远程接入的方法、设备和系统 |
WO2014025141A1 (en) * | 2012-08-06 | 2014-02-13 | Lg Electronics Inc. | A method for transferring a status report and a communication device thereof in a wireless communication system |
KR102040883B1 (ko) * | 2012-08-23 | 2019-11-05 | 인터디지탈 패튼 홀딩스, 인크 | 무선 시스템에서의 다중 스케줄러들을 이용한 동작 |
WO2014070321A1 (en) * | 2012-11-01 | 2014-05-08 | Maruti Gupta | Signaling qos requirements and ue power preference in lte-a networks |
US8989807B2 (en) * | 2013-02-28 | 2015-03-24 | Intel Mobile Communications GmbH | Communication terminal device, communication device, communication network server and method for controlling |
US9584988B2 (en) * | 2013-03-07 | 2017-02-28 | Intel Deutschland Gmbh | Communication terminal, communication device, method for processing a paging message and method for controlling a communication terminal |
EP2863702B1 (en) * | 2013-10-18 | 2019-03-06 | Vodafone GmbH | Use of mobile originating circuit-switched (mo-cs) signalling |
US10136407B2 (en) * | 2014-07-01 | 2018-11-20 | Sharp Kabushiki Kaisha | Base station device, first location management device, terminal device, communication control method, and communication system |
US10251097B2 (en) * | 2014-07-29 | 2019-04-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Technique for applying policy and charging rules to bearers |
US9749908B2 (en) * | 2015-07-29 | 2017-08-29 | Verizon Patent And Licensing Inc. | Local breakout service |
WO2017138769A1 (ko) * | 2016-02-11 | 2017-08-17 | 엘지전자(주) | 무선 통신 시스템에서 단말의 위치 갱신 방법 및 이를 지원하는 장치 |
US11166334B2 (en) * | 2016-07-01 | 2021-11-02 | Idac Holdings, Inc. | Methods for supporting session continuity on per-session basis |
EP3481101A4 (en) * | 2016-08-04 | 2019-07-31 | Huawei Technologies Co., Ltd. | COMMUNICATION PROCEDURE, USER DEVICE, BASE STATION, CONTROL CENTER NETWORK ELEMENT AND COMMUNICATION SYSTEM |
GB2552845A (en) * | 2016-08-12 | 2018-02-14 | Nec Corp | Communication system |
EP3490297B1 (en) * | 2016-08-22 | 2024-07-31 | Samsung Electronics Co., Ltd. | Method and apparatus for operating wireless communication system having separated mobility management and session management |
-
2017
- 2017-01-05 JP JP2017000509A patent/JP2020036055A/ja active Pending
- 2017-12-26 EP EP17889668.4A patent/EP3567941A4/en not_active Withdrawn
- 2017-12-26 CN CN201780082211.6A patent/CN110140394B/zh active Active
- 2017-12-26 US US16/476,095 patent/US20190335413A1/en not_active Abandoned
- 2017-12-26 CA CA3049321A patent/CA3049321A1/en active Pending
- 2017-12-26 WO PCT/JP2017/046638 patent/WO2018128127A1/ja unknown
- 2017-12-26 BR BR112019013919A patent/BR112019013919A2/pt not_active IP Right Cessation
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060087973A1 (en) * | 2004-10-22 | 2006-04-27 | Henry Huang | Delay timers for managing internal state changes and messages in user equipment for real-time multimedia applications |
JP2014512742A (ja) * | 2011-03-16 | 2014-05-22 | クアルコム,インコーポレイテッド | 無線アクセス技術間のサービス再試行中にセッションコンテキストを保存するための方法および装置 |
JP2017000509A (ja) | 2015-06-12 | 2017-01-05 | ダンロップスポーツ株式会社 | ゴルフボール用樹脂組成物およびゴルフボール |
Non-Patent Citations (3)
Title |
---|
LEE, J. SAMSUNG ELECTRONICS: "Local Area Data Network Discussion , Solution Update, Evaluation", 3GPP DRAFT; S2-166453 DISCUSSION, SOLUTION UPDATE, EVALUATION OF SOLUTION 4.25 - LOCAL AREA DATA NETWORK,, 8 November 2016 (2016-11-08), Reno, pages 1 - 13, XP051199433, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_118_Reno/Docs/> [retrieved on 20180117] * |
SAMSUNG: "Evaluation and Update to Solution 4. 25: Local Area Data Network", 3GPP SA WG2 MEETING #S2-118, S 2-166453, 8 November 2016 (2016-11-08), pages 1 - 6, XP051199434, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_118_Reno/Docs/S2-166453.zip> [retrieved on 20180117] * |
See also references of EP3567941A4 |
Also Published As
Publication number | Publication date |
---|---|
EP3567941A4 (en) | 2020-09-02 |
BR112019013919A2 (pt) | 2020-02-04 |
EP3567941A1 (en) | 2019-11-13 |
CA3049321A1 (en) | 2018-07-12 |
CN110140394B (zh) | 2022-01-14 |
CN110140394A (zh) | 2019-08-16 |
JP2020036055A (ja) | 2020-03-05 |
US20190335413A1 (en) | 2019-10-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110383867B (zh) | 终端装置、核心网装置以及通信控制方法 | |
WO2018030474A1 (ja) | 端末装置、ゲートウェイ、及び通信制御方法 | |
WO2018128127A1 (ja) | 端末装置、コアネットワーク装置、及び通信制御方法 | |
WO2018147220A1 (ja) | 端末装置、コアネットワーク装置、及び通信制御方法 | |
JP6748220B2 (ja) | Ue、コアネットワーク装置、ueの通信方法及びコアネットワークの通信方法 | |
WO2018207839A1 (ja) | 端末装置、amf、smf、コアネットワーク装置、及び通信制御方法 | |
WO2018066234A1 (ja) | 端末装置、MME(Mobility Management Entity)、CPF(Control Plane Function)、及び通信制御方法 | |
WO2019245004A1 (ja) | Ue、及びその通信方法 | |
WO2018084291A1 (ja) | 端末装置、コアネットワーク装置、通信システム、及び通信制御方法 | |
WO2018128126A1 (ja) | 端末装置、ネットワーク機能部、基地局装置、通信システム、及び通信制御方法 | |
WO2018147219A1 (ja) | 端末装置、コアネットワーク装置、及び通信制御方法 | |
WO2018066235A1 (ja) | 端末装置、MME(Mobility Management Entity)、CPF(Control Plane Function)、及び通信制御方法 | |
WO2021029381A1 (ja) | Ue、及び通信制御方法 | |
WO2018128125A1 (ja) | 端末装置、ネットワーク機能部、基地局、通信システム、及び通信制御方法 | |
JP7362344B2 (ja) | Ue、及び通信制御方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17889668 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 3049321 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112019013919 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 2017889668 Country of ref document: EP Effective date: 20190805 |
|
ENP | Entry into the national phase |
Ref document number: 112019013919 Country of ref document: BR Kind code of ref document: A2 Effective date: 20190704 |
|
NENP | Non-entry into the national phase |
Ref country code: JP |