Terminal device, AMF, SMF, core network device, and communication control method
阅读说明：本技术 终端装置、amf、smf、核心网装置以及通信控制方法 (Terminal device, AMF, SMF, core network device, and communication control method ) 是由 久下阳子 新本真史 于 2018-05-09 设计创作，主要内容包括：本发明对通信系统中所包括的控制装置、终端装置提供：用于会话管理的适当的单元、用于建立与会话连续模式对应的会话的适当的通信控制单元以及用于控制会话的适当的通信控制单元。由此,对通信系统中所包括的控制装置、终端装置提供：与关于适当的会话的连续的模式对应的会话锚重新定位过程、通信控制单元以及管理单元。(The present invention provides a control device and a terminal device included in a communication system, the control device including: an appropriate unit for session management, an appropriate communication control unit for establishing a session corresponding to the session continuation mode, and an appropriate communication control unit for controlling the session. Thereby, the control device and the terminal device included in the communication system are provided with: a session anchor relocation procedure corresponding to a continuous mode with respect to an appropriate session, a communication control unit and a management unit.)
1. A terminal device, characterized in that,
in a PDU session anchor relocation procedure to relocate the anchor of a session and a packet data unit PDU session serving continuous SSC mode 2,
the first identification information is information indicating that a PDU session needs to be re-established,
the second identification information is PDU session identification information corresponding to the PDU session establishment of the SSC pattern 2,
the terminal device includes a transmission/reception unit that receives a PDU session release command including the first identification information and the second identification information from a core network,
the terminal device includes a control unit that transmits a PDU session establishment request message including the first identification information to the core network based on reception of the PDU session release command, thereby starting a PDU session establishment procedure.
2. A terminal device according to claim 1,
in a PDU session anchor relocation procedure for relocating an anchor device of a PDU session of SSC mode 3,
the transmitting/receiving part is provided with a transmitting/receiving part,
transmitting a PDU session establishment request message including information indicating a request to transmit routing preference to the core network,
receiving a Router Advertisement (RA) message or a Protocol Data Unit (PDU) session establishment acceptance message including an IPv6 network prefix and identification information of routing preferences corresponding to the IPv6 network prefix from the core network.
3. An access and mobility management function, AMF,
in a PDU session anchor relocation procedure to relocate the anchor of a session and a packet data unit PDU session serving continuous SSC mode 2,
the first identification information is information indicating that a PDU session needs to be re-established,
the second identification information is PDU session identification information corresponding to the PDU session establishment of the SSC pattern 2,
the AMF includes a transmission/reception unit that transmits a PDU session release command including the first identification information and the second identification information to a terminal device,
the AMF includes a control unit that stores the second identification information and counts an effective time of the second identification information using a timer.
4. A session management function, SMF,
in a PDU session anchor relocation procedure to relocate the anchor of a session and a packet data unit PDU session serving continuous SSC mode 2,
the first identification information is information indicating that a PDU session needs to be re-established,
the second identification information is PDU session identification information corresponding to the PDU session establishment of the SSC pattern 2,
the SMF has a transmitting/receiving section that transmits a PDU session release command including the first identification information and the second identification information to a terminal device via an access and mobility management function (AMF),
the SMF includes a control unit that stores the second identification information and counts an effective time of the second identification information using a timer.
5. The SMF of claim 4,
in a PDU session anchor relocation procedure for relocating an anchor device of a PDU session of SSC mode 3,
the transmitting/receiving part is provided with a transmitting/receiving part,
receiving a PDU session setup request message including information indicating a request to send routing preferences from the terminal device via the access and mobility management function AMF,
and sending a Router Advertisement (RA) message or a Protocol Data Unit (PDU) session establishment acceptance message, which comprises an IPv6 network prefix and identification information of routing preference corresponding to the IPv6 network prefix, to the terminal device through the AMF.
6. A communication control method of a terminal device,
in a PDU session anchor relocation procedure to relocate the anchor of a session and a packet data unit PDU session serving continuous SSC mode 2,
the first identification information is information indicating that a PDU session needs to be re-established,
the second identification information is PDU session identification information corresponding to the PDU session establishment of the SSC pattern 2,
the communication control method includes the steps of:
receiving a PDU session release command including the first identification information and the second identification information from a core network; and
and sending a PDU session establishment request message comprising the first identification information to the core network based on the receiving of the PDU session release command so as to start a PDU session establishment process.
7. The communication control method of a terminal device according to claim 6,
in a PDU session anchor relocation procedure for relocating an anchor device of a PDU session of SSC mode 3,
comprises the following steps:
transmitting a PDU session establishment request message including information indicating a request for transmitting a routing preference to the core network; and
receiving a Router Advertisement (RA) message or a Protocol Data Unit (PDU) session establishment acceptance message including an IPv6 network prefix and identification information of routing preferences corresponding to the IPv6 network prefix from the core network.
8. A communication control method of an access and mobility management function, AMF,
in a PDU session anchor relocation procedure to relocate the anchor of a session and a packet data unit PDU session serving continuous SSC mode 2,
the first identification information is information indicating that a PDU session needs to be re-established,
the second identification information is PDU session identification information corresponding to the PDU session establishment of the SSC pattern 2,
the communication control method includes the steps of:
transmitting a PDU session release command including the first identification information and the second identification information to a terminal apparatus; and
and storing the second identification information, and timing the effective time of the second identification information by using a timer.
9. A communication control method of a Session Management Function (SMF),
in a PDU session anchor relocation procedure to relocate the anchor of a session and a packet data unit PDU session serving continuous SSC mode 2,
the first identification information is information indicating that a PDU session needs to be re-established,
the second identification information is PDU session identification information corresponding to the PDU session establishment of the SSC pattern 2,
the communication control method includes the steps of:
transmitting a PDU session release command including the first identification information and the second identification information to a terminal device via an access and mobility management function, AMF; and
and storing the second identification information, and timing the effective time of the second identification information by using a timer.
10. The SMF communication control method according to claim 9,
in a PDU session anchor relocation procedure for relocating an anchor device of a PDU session of SSC mode 3,
comprises the following steps:
receiving a PDU session setup request message including information indicating a request to send routing preferences from a terminal device via an access and mobility management function AMF; and
and sending a Router Advertisement (RA) message or a Protocol Data Unit (PDU) session establishment acceptance message, which comprises an IPv6 network prefix and identification information of routing preference corresponding to the IPv6 network prefix, to the terminal device through the AMF.
11. A communication control method of a core network is characterized in that,
in a PDU session anchor relocation procedure to relocate the anchor of a session and a packet data unit PDU session serving continuous SSC mode 2,
the first identification information is information indicating that a PDU session needs to be re-established,
the second identification information is PDU session identification information corresponding to the PDU session establishment of the SSC pattern 2,
the communication control method includes the steps of:
transmitting a PDU session release command including the first identification information and the second identification information to a terminal apparatus; and
and storing the second identification information, and timing the effective time of the second identification information by using a timer.
12. The communication control method of a core network according to claim 11,
in a PDU session anchor relocation procedure for relocating an anchor device of a PDU session of SSC mode 3,
comprises the following steps:
receiving a PDU session setup request message including information indicating a request to transmit a routing preference from a terminal apparatus; and
and sending a Router Advertisement (RA) message or a Protocol Data Unit (PDU) session establishment acceptance message, which comprises an IPv6 network prefix and identification information of routing preference corresponding to the IPv6 network prefix, to the terminal device.
13. A core network apparatus, characterized in that,
in a PDU session anchor relocation procedure to relocate the anchor of a session and a packet data unit PDU session serving continuous SSC mode 2,
the first identification information is information indicating that a PDU session needs to be re-established,
the second identification information is PDU session identification information corresponding to the PDU session establishment of the SSC pattern 2,
transmitting a PDU session release command including the first identification information and the second identification information to a terminal device,
and storing the second identification information, and timing the effective time of the second identification information by using a timer.
14. Core network arrangement according to claim 13,
in a PDU session anchor relocation procedure for relocating an anchor device of a PDU session of SSC mode 3,
receiving a PDU session establishment request message including information indicating a request to send a routing preference from a terminal device,
and sending a Router Advertisement (RA) message or a Protocol Data Unit (PDU) session establishment acceptance message, which comprises an IPv6 network prefix and identification information of routing preference corresponding to the IPv6 network prefix, to the terminal device.
Technical Field
The invention relates to a terminal device, AMF, SMF, core network device and communication control method. The present application claims priority based on japanese patent application 2017-92902 filed in japan on 5, 9, 2017, which is incorporated herein by reference in its entirety.
Background
In 3GPP (3rd generation partnership Project) which has performed standardization activities of mobile communication systems in recent years, SAE (System Architecture Evolution), which is a System framework of LTE (Long Term Evolution), has been studied. As a communication System for realizing all ip (internet protocol), 3GPP standardized EPS (Evolved Packet System). It should be noted that the core network constituting the EPS is referred to as EPC (Evolved packet core).
In recent years, 3GPP has also studied Next-Generation communication technology and System Architecture of a 5G (5th Generation: fifth Generation) mobile communication System as a Next-Generation mobile communication System, and Next-Generation communication technology has also studied Next-Generation gen (Architecture and Security for Next Generation System: Next-Generation System Architecture and Security). In 3GPP, as a system for implementing a 5G mobile communication system, standardization of 5GS (5G system: 5G system) is performed. In 5GS, the technical problem for connecting various terminals to the cellular network is extracted, and the solution is standardized.
Examples of the request conditions include: optimization and diversification of communication procedures for supporting continuous mobile communication services corresponding to terminals supporting various access networks, optimization of a system framework matching the optimization and diversification of communication procedures, and the like.
Disclosure of Invention
Problems to be solved by the invention
In 5GS, session management in a mobile communication service between a terminal and a network device is being studied. More specifically, in order to achieve continuity of a session, a PDU session anchor relocation process for switching a class of DN (Data Network: Data Network) as an anchor point to a gateway of the DN, a process for establishing a connection with a plurality of anchor points without changing the class of the DN as a connection destination of the session is being studied.
However, the detailed manner of the procedure for implementing session continuity and the procedure for switching anchor points has not been clarified yet.
The present invention has been made in view of the above circumstances, and an object thereof is to provide means for realizing various session continuations, means for communication procedures, and the like.
Technical scheme
In a PDU Session anchor relocation process for relocating an anchor device of a PDU (PcketDataUnit) Session of SSC (Session and Service Continuity mode) mode 2(mode 2), the first identification information is information indicating that a PDU session needs to be re-established, the second identification information is PDU session identification information corresponding to the PDU session establishment of SSC mode 2, the terminal device includes a transmission/reception unit that receives a PDU session release command including the first identification information and the second identification information from a core network, the terminal device includes a control unit that transmits a PDU session establishment request message including the first identification information to the core network based on reception of the PDU session release command, thereby starting a PDU session establishment procedure.
In addition, in a PDU session anchor relocation procedure for relocating an anchor device of a PDU session in SSC mode 3(mode 3), the terminal device of the present invention transmits a PDU session establishment request message including information indicating a request to transmit a routing preference to the core network, and receives an RA (Router advertisement) message or a PDU session establishment acceptance message including an IPv6 network prefix and identification information of a routing preference associated with the IPv6 network prefix, from the core network.
In addition, in a PDU session anchor relocation process for relocating an anchor device of a PDU (pckey Data unit) session of an SSC (session and Service continuity) mode 2, first identification information is information indicating that a PDU session needs to be reestablished, second identification information is PDU session identification information corresponding to the PDU session of the SSC mode 2, the AMF includes a transmitting and receiving unit that transmits a PDU session release command including the first identification information and the second identification information to a terminal device, and the AMF includes a control unit that stores the second identification information and that counts an effective time of the second identification information using a timer.
In addition, in a PDU Session anchor relocation process for relocating an anchor device of an SSC (Session and Service continuity) mode 2 PDU (pckey Data unit) Session, the SMF (Session Management Function) according to the present invention includes a transmission/reception unit that transmits a PDU Session release command including the first identification information and the second identification information to a terminal device via an amf (access and Mobility Management Function), wherein the transmission/reception unit stores the second identification information, and a timer is used to count an effective time of the second identification information.
In addition, in a PDU session anchor relocation process of relocating an anchor device of a PDU session in SSC mode 3, the SMF according to the present invention receives, from a terminal device, a PDU session establishment request message including information indicating a request to transmit a routing preference via the AMF (access and Mobility management function), and transmits, to the terminal device, an ra (routeradditionality) message or a PDU session establishment acceptance message including an IPv6 network prefix and identification information of a routing preference associated with the IPv6 network prefix, via the AMF.
In addition, a communication control method of a terminal device according to the present invention is a PDU session anchor relocation process for relocating an anchor device of an SSC (session and servicecontinuity) mode 2 PDU (pckey Data unit) session, wherein first identification information is information indicating that a PDU session needs to be reestablished, and second identification information is PDU session identification information corresponding to the PDU session establishment of the SSC mode 2, the communication control method including the steps of: receiving a PDU session release command including the first identification information and the second identification information from a core network; and sending a PDU session establishment request message including the first identification information to the core network based on the reception of the PDU session release command so as to start a PDU session establishment process.
Further, a communication control method of a terminal device according to the present invention is a communication control method of a terminal device, in a PDU session anchor relocation process for relocating an anchor device of a PDU session in SSC mode 3, comprising the steps of: transmitting a PDU session establishment request message including information indicating a request for transmitting a routing preference to the core network; and receiving an ra (router advertisement) message or a PDU session establishment accept message including an IPv6 network prefix and identification information establishing a routing preference corresponding to the IPv6 network prefix from the core network.
In addition, in a PDU session anchor relocation process for relocating an anchor device of a PDU (pcket Data unit) session in SSC (session and Service continuity) mode 2, first identification information is information indicating that a PDU session needs to be reestablished, and second identification information is PDU session identification information corresponding to the PDU session establishment in SSC mode 2, the communication control method of the present invention includes the steps of: transmitting a PDU session release command including the first identification information and the second identification information to a terminal apparatus; and storing the second identification information, and timing the effective time of the second identification information by using a timer.
In addition, in a PDU session anchor relocation process for relocating an anchor device of a PDU (pckey Data unit) session in an SSC (session and Service continuity) mode 2, first identification information is information indicating that a PDU session needs to be reestablished, and second identification information is PDU session identification information corresponding to the PDU session in the SSC mode 2, the communication control method of the present invention includes the steps of: transmitting a PDU session release command including the first identification information and the second identification information to a terminal device via an amf (access and Mobility Management function); and storing the second identification information, and timing the effective time of the second identification information by using a timer.
In addition, the communication control method of SMF of the present invention has the following steps in a PDU session anchor relocation process for relocating an anchor device of a PDU session of SSC mode 3: receiving a PDU session setup request message including information indicating a request to transmit a routing preference from a terminal device via an amf (access and mobility Management function); and transmitting an ra (router advertisement) message or a PDU session establishment accept message including an IPv6 network prefix and identification information of a routing preference corresponding to the IPv6 network prefix, to the terminal apparatus via the AMF.
In addition, in a PDU session anchor relocation process for relocating an anchor device of a PDU (pcket Data unit) session in SSC (session and servicecontinuity) mode 2, a first identification information is information indicating that a PDU session needs to be reestablished, and a second identification information is a PDU session identification information corresponding to the PDU session in SSC mode 2, the communication control method of the present invention includes the steps of: transmitting a PDU session release command including the first identification information and the second identification information to a terminal apparatus; and storing the second identification information, and timing the effective time of the second identification information by using a timer.
In addition, the communication control method of the core network of the present invention has the following steps in a PDU session anchor relocation process for relocating an anchor device of a PDU session in SSC mode 3: receiving a PDU session setup request message including information indicating a request to transmit a routing preference from a terminal apparatus; and sending an ra (router advertisement) message or a PDU session establishment accept message including an IPv6 network prefix and identification information of a routing preference corresponding to the IPv6 network prefix, to the terminal apparatus.
In addition, in a PDU session anchor relocation process for relocating an anchor device of an SSC (session and Service continuity) mode 2 PDU (pckey Data unit) session, a core network device of the present invention is configured such that first identification information is information indicating that a PDU session needs to be reestablished, and second identification information is PDU session identification information corresponding to the PDU session of the SSC mode 2, transmits a PDU session release command including the first identification information and the second identification information to a terminal device, stores the second identification information, and counts an effective time of the second identification information using a timer.
In addition, the core network apparatus of the present invention receives a PDU session establishment request message including information indicating a request to send a routing preference from a terminal apparatus in a PDU session anchor relocation process of relocating an anchor apparatus of a PDU session in SSC mode 3, and transmits an ra (router advertisement) message or a PDU session establishment acceptance message including an IPv6 network prefix and identification information of a routing preference corresponding to the IPv6 network prefix, to the terminal apparatus.
Advantageous effects
According to the present invention, the terminal device and each device in the core network can support various session continuation modes, and can realize a communication control procedure corresponding to the session continuation mode.
Drawings
Fig. 1 is a diagram for explaining a mobile communication system in outline.
Fig. 2 is a diagram for explaining an example of the configuration of a core network and an access network in a mobile communication system.
Fig. 3 is a diagram for explaining an outline of the mobile communication system at the time of PDU session anchor relocation.
Fig. 4 is a diagram illustrating an apparatus configuration of a UE.
Fig. 5 is a diagram for explaining a storage unit of the UE.
Fig. 6 is a diagram illustrating AN apparatus configuration of AN eNB/AN node.
Fig. 7 is a diagram illustrating the configuration of the AMF/MME/CPF device.
Fig. 8 is a diagram illustrating the storage unit of AMF/MME/CPF.
Fig. 9 is a diagram for explaining the storage unit of the AMF/MME/CPF.
FIG. 10 is a diagram illustrating the configuration of a UPF/SGW/PGW device.
Fig. 11 is a diagram for explaining a storage unit of the SGW.
FIG. 12 is a diagram for explaining a storage unit of UPF/PGW.
Fig. 13 is a diagram for explaining an initial process.
Fig. 14 is a diagram for explaining a PDU session change procedure.
Fig. 15 is a diagram for explaining a PDU session setup procedure.
Fig. 16 is a diagram for explaining a first PDU session anchor relocation setup procedure.
Fig. 17 is a diagram for explaining a first PDU session release procedure.
Fig. 18 is a diagram for explaining a second PDU session anchor relocation setup procedure.
Fig. 19 is a diagram for explaining a second PDU session release procedure.
Detailed Description
Hereinafter, preferred embodiments for carrying out the present invention will be described with reference to the drawings. In the present embodiment, an embodiment of a mobile communication system in a case where the present invention is applied will be described as an example.
[1. System outline ]
Fig. 1 is a diagram for explaining the outline of a mobile communication system according to the present embodiment. As shown in fig. 1, the
Further, the UE _ a10 can connect with an access network and/or a core network. Also, the UE _ a10 can connect with the DN _ a5 via an access network and/or a core network, and in turn transceive user data with the DN _ a 5. Note that the user data may be data transceived between the UE _ a10 and the DN _ a 5. 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). The communication of the user data is not limited to IP (Internet Protocol) communication, but may be non-IP communication.
Here, the PDU session or PDN connection (hereinafter, also referred to as PDN connection) is connectivity established between the UE _ a10 and the DN _ a5 in order to provide a PDU connection service for transmitting and receiving user data between the UE _ a10 and the DN _ a 5. More specifically, the PDU session or PDN connection may be the connectivity established between the UE _ a10 and the external gateway. Here, the external Gateway may be a device such as UPF (User Plane Function) _ a235, PGW (Packet Data Network Gateway), UPGW (User Plane Gateway), SCEF (Service capability exposure Function), etc. that connects the core Network and DN _ a 5.
Further, the PDU session or PDN connection may be a communication path established for transceiving user data between the UE _ a10 and the core network and/or DN _ a5, and may also be a communication path for transceiving PDUs. The PDU session or PDN connection may be a session established between the UE _ a10 and the core network and/or DN _ a5, or may be a logical communication path including one or more transport paths such as bearers between the respective devices in the
It should be noted that the PDN connection may be connectivity and/or connection between UE _ a10 and PGW _ a30 via eNB (evolved Node b) _ a45 and/or SGW (serving gateway), or may be connectivity and/or connection between UE _ a10 and SCEF via eNB _ a45 and/or MME (Mobility Management Entity). Also, the PDU session may be connectivity and/or connection between the UE _ a10 and the UPGW or UPF _ a235 via the AN node _ a 122. It should be noted that the connectivity between the UE _ a10 and the UPF _ a235 may constitute more than one UPF. Also, a PDN connection may be identified by a PDN connection ID, and a PDU session may also be identified by a PDU session ID. Also, PDN connections and PDU sessions can be identified by EPS bearer IDs.
The UE _ a10 can perform transmission and reception of user data with an apparatus such as an application server assigned to the DN _ a5 using a PDU session or PDN connection. In other words, the PDU session or PDN connection can transfer user data transmitted and received between the UE _ a10 and an application server or the like configured to the DN _ a 5. Furthermore, each device (UE _ a10, a device within the access network, and/or a device within the core network) may manage one or more pieces of identification information in association with a PDU session or PDN connection establishment. It should be noted that the identification information may include at least one of DNN (Data Network Name: Data Network Name), APN (Access Point Name: Access Point Name), TFT (Traffic Flow Template), session type, application identification information, DN a5 identification information, NSI (Network Slice Instance) identification information, DCN (differentiated Core Network) identification information, and Access Network identification information, and may further include other information. In addition, when a plurality of PDU sessions or PDN connections are established, the content of each piece of identification information corresponding to the PDU sessions or PDN connections may be the same or different. The NSI identification information is information for identifying an NSI, and may be the following NSI ID or Slice Instance ID, or may be NSSAI (Network Slice Selection Assistance information), or may be S-NSSAI (Single Network Slice Selection Assistance information).
The IP communication is data communication using IP, and is data communication realized by transmitting and receiving an IP packet to which an IP header is added. The payload constituting the IP packet may include user data transmitted and received by the UE _ a 10. Note that non-IP communication is data communication not using IP, and is data communication realized by transmitting and receiving data to which an IP header is not added. For example, the non-IP communication may be data communication realized by transmitting and receiving application data to which an IP packet is not assigned, or may be other headers such as a MAC header and an Ethernet (registered trademark) frame header to transmit and receive user data transmitted and received by the UE _ a 10.
Also, DN _ A5 can be a DN (Data Network: Data Network) that provides communication services for UE _ A10. The DN may be configured as a packet data service network or may be configured for each service. Also, DN a5 may include a connected communication terminal. Therefore, the connection with the DN _ a5 may refer to connection with a communication terminal or a server apparatus assigned to the DN _ a 5. Furthermore, the transmission and reception of user data to and from DN _ a5 may be referred to as transmission and reception of user data to and from a communication terminal or a server apparatus assigned to DN _ a 5.
Also, the access network is a radio network connected with the UE _ a10 and/or the core network. The access network may be a 3GPP access network or a non-3GPP access network. It should be noted that the 3GPP Access Network may be E-UTRAN (Evolved Universal terrestrial Radio Access Network) _ A80, 5GRAN (NextGenationRadioactive Access Network) _ A120, and the non-3GPP Access Network may be
Also, the core network is an IP Mobile communication network operated by a Mobile communication operator (Mobile network operator) connected to the access network and/or DN a 5. The core Network may be a core Network for a Mobile communications carrier that operates and manages the
Next, a configuration example of the core network _ B190 will be described. An example of the configuration of the core network _ B190 will be described. Fig. 2 shows an example of the configuration of the core network _ B190. The core network _ B190 in fig. 2 (a) is composed of UDM _ a50, PCF _ a60, SMF (Session Management Function) _ a230, UPF _ a235, and AMF (Access and Mobility Management Function) _ a 240.
It should be noted that the SMF _ A230 and/or the AMF _ A240 may be a CPF (Control Plane Function) and the UPF _ A235 may be a PGW (User Plane Gateway).
Furthermore, the core network _ B190 can be connected to a plurality of radio access networks (E-UTRAN _ a80, 5G RAN _ a120, wlan ac 125). 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 of the access networks. Also, the UE _ a10 can be wirelessly connected to the radio access network.
Also, an access network capable of connection through the 3GPP access system may be composed of E-UTRAN _ a80 and 5G RAN _ a 120. Also, an access network capable of connection through the WLAN access system may be composed of a WLAN access network c (WLAN ANc125) connected with the CPF or AMF _ a240 and UPF _ a 235. Hereinafter, each device will be briefly described.
The UPF _ a235 is a device connected to the DN _ a5, the SMF _ a230, the E-UTRAN80, the 5G RAN _ a120, and the WLAN ANc125, and is a relay device that serves as a gateway between the DN _ a5 and the core network _ B190 and transmits user data. In other words, the UPF _ a235 is an anchor point or anchor means for the PDU session established by the UE _ a10 for communicating user data. It should be noted that the UPF _ a235 may be a gateway for IP communications and/or non-IP communications. Further, the UPF _ a235 may have a function of transmitting IP communication, and may also have a function of converting non-IP communication and IP communication. Note that a plurality of such gateways may be configured in the core network _ B190. And the configured plurality of gateways may be gateways connecting the core network B190 and a single DN. The UPF _ a235 may have connectivity to other NFs, and may be connected to each device via other NFs. It should be noted that the UPF _ a235 may be an SGW and/or a PGW and/or a UPGW.
The PGW is a relay device connected to DN _ a5, SGW, and PCF _ a60, and serving as a gateway between DN _ a5 and core network _ B190 to transmit user data. It should be noted that the PGW may be a gateway for IP communication and/or non-IP communication.
Also, the PGW may have a function of transmitting IP communication, and may also have a function of converting non-IP communication and IP communication. Note that a plurality of such gateways may be configured in the core network _ B190. And the configured plurality of gateways may be gateways connecting the core network B190 and a single DN.
It should be noted that a U-Plane (User Plane) may be a communication path for transceiving User data, and may be composed of a plurality of bearers. Also, a C-Plane (Control Plane) may refer to a communication path for transceiving a Control message, and may be composed of a plurality of bearers.
Also, the PGW may be connected to the UP function and Policy function, and may also be connected to the UE _ a10 via the U-Plane. Also, the PGW may be constructed together with the UPF _ a 235.
The SGW is a relay device connected to the PGW, MME and E-UTRAN _ a80, and serving as a core network _ B190 for transferring user data to and from gateways of 3GPP access networks (E-UTRAN _ a80 and 5G RAN _ a 120).
The SGW may be an UP function having a connection point with the access network for transmitting user data, or may be an upgw (user Plane gateway) serving as a gateway for transmitting user data between the access network and the core network.
Also, the CPF is a device connected with the UPF _ a235, the E-UTRAN _ a80, the 5G RAN _ a120, the WLAN ANc125, and the UDM _ a 50. The CPF may be an NF that functions as mobility management for the UE _ a10 or the like, may be an NF that functions as session management for PDU sessions or the like, and may be an NF that manages one or more NSIs. In addition, the CPF may also be an NF that serves one or more of the above-mentioned functions. It should be noted that the NF may be one or more devices configured in the core Network _ B190, may also be a CP Function (Control Plane Function or Control Plane Network Function) for controlling information and/or Control messages, and may also be a shared CP Function (CCNF, Common CP Function) shared among multiple NSIs. The CPF may have connectivity to another NF, and may be connected to each device via another NF. It should be noted that the CPF may be an MME, an NF having functions of the AMF _ a240 and the SMF _ a230, the AMF _ a240, or the SMF _ a 230.
Also, the AMF _ a240 is a device connected to the SMF _ a230, the E-UTRAN _ a80, the 5G RAN _ a120, the
The SMF _ a230 is a device connected to the AMF _ a240, the UPF _ a235, the UDM _ a50, and the PCF _ a 60. The SMF _ a230 may be an NF that functions as session management for a PDU session or the like. It should be noted that the NF may be one or more devices configured in the core Network _ B190, may also be a CP Function (Control Plane Function or Control Plane Network Function) for controlling information and/or Control messages, and may also be a shared CP Function (CCNF, Common CP Function) shared among multiple NSIs. The SMF _ a230 may have connectivity to another NF, and may be connected to each device via another NF. It is noted that the SMF _ a230 may be an NF having a partial function of the functions of the CPF.
The MME is a control device that is connected to the SGW, the access network, the HSS, and the SCEF, and performs location information management including mobility management of the UE _ a10 and access control via the access network. Also, the MME may include a function as a session management device that manages the session established by the UE _ a 10.
A plurality of such control devices may be disposed in the core network _ B190, and may be configured by a location management device different from the MME, for example. The location management device different from the MME can be connected to the SGW, the access network, the SCEF, and the HSS in the same manner as the MME.
Further, in the case where a plurality of MMEs are included within the core network _ B190, the MMEs may be connected to each other. This enables the UE _ a10 to transmit and receive contexts between MMEs. As described above, the MME may be a management device that transmits and receives Control information related to mobility management and session management to and from the UE _ a10, in other words, a Control device of a Control Plane (C-Plane; CP).
Further, although the MME has been described as being included in the core network _ B190, the MME may be a management apparatus configured with one or more core networks, DCNs, or NSIs, or may be a management apparatus connected to one or more core networks, DCNs, or NSIs. Here, a plurality of DCNs or NSIs may be used by a single carrier or may be used by different carriers.
Further, the MME may be a relay device that performs transmission of user data as a gateway between the core network _ B190 and the access network. The user data transmitted and received by using the MME as a gateway may be small data.
The MME may be an NF that functions as mobility management for the UE _ a10 or the like, may be an NF that functions as session management for PDU sessions or the like, or may be an NF that manages one or more NSIs. In addition, the MME may also be an NF that serves one or more of the above-mentioned functions. The NF may be one or more devices configured in the core Network _ B190, may be a Control information and/or a CP Function (hereinafter, also referred to as a CPF (Control Plane Function) or a Control Plane Network Function) for controlling messages, and may be a shared CP Function shared among multiple NSIs.
Herein, NF refers to a processing function formed in the network. That is, the NF may be a functional device such as MME, SGW, PGW, CPF, UPGW, AMF _ a240, UPF _ a235, SMF _ a230, PCF _ a60, or may be function and capability information such as MM (mobility Management) and SM (Session Management). Further, the NF may be a functional device for realizing a single function or may be a functional device for realizing a plurality of functions. For example, there may be a NF for implementing the MM function and a NF for implementing the SM function, or there may be a NF for implementing both the MM function and the SM function.
The SCEF is a relay device that is connected to DN _ a5, CPF or AMF _ a240, or MME, and UDM _ a50, and serves as a gateway connecting DN _ a5 and/or DN to core network _ B190 to transmit user data. It should be noted that the SCEF may be a gateway for non-IP communication. Also, the SCEF may have a function of converting non-IP communication and IP communication. Further, a plurality of such gateways may be configured in the core network _ B190. Also, multiple gateways connecting the core network _ B190 with a single DN _ a5 and/or DN may be configured. The SCEF may be configured outside or inside the core network.
The UDM _ a50 is a management node that is connected to the MME, the AMF _ a240, the SMF _ a230, and the SCEF to manage subscriber information. UDM _ a50 subscriber information is referred to, for example, at access control of the MME. Also, UDM _ a50 may be connected with a location management device other than an MME. For example, the UDM _ a50 may be connected with the CPF or AMF _ a240 or SMF _ a 230.
The PCF _ a60 is connected to the UPGW, the SMF _ a230, the PGW, and the DN _ a5, and performs QoS management for data transmission. For example, management of QoS of the communication path between the UE _ a10 and the DN _ a5 is performed. Also, PCF _ A60 may be a device that formulates and/or manages PCC (Policy and Charging Control) rules and/or routing rules for use by devices in transceiving user data.
In addition, PCF _ a60 may also be a Policy function that formulates and/or manages policies. In more detail, PCF _ a60 may be connected with an UP function.
As shown in fig. 2 (b), each radio access network includes a device (e.g., a base station device, an access point device) to which the UE _ a10 is actually connected, and the like. The means for connecting may take into account means adapted to the radio access network.
In the present embodiment, the E-UTRAN-A80 is an LTE (Long Term Evolution) access network and is configured to include an eNB-A45. The eNB _ a45 is a Radio base station for the UE _ a10 to connect to via E-utra (evolved universal Radio access), and may be configured to include one or more eNB _ a45 in E-UTRAN _ a 80. In addition, a plurality of enbs may be connected to each other.
Also, the 5G RAN _ a120 is a 5G access network, and is configured to include AN node (New Radio access technology node) _ a 122. The AN node _ a122 is a Radio base station to which the UE _ a10 connects via a Next Generation Radio Access (NextGen RA), and may be configured to include one or more AN nodes _ a122 in the 5G RAN _ a 120. It should be noted that, in the case where a plurality of AN nodes _ a122 are included in the 5G RAN _ a120, the AN node _ a122 and the AN node _ B123 may be included in the 5G RAN _ a 120. In this case, the AN node _ B123 may be the same configuration as the AN node _ a 122.
Also, the 5G RAN _ A120 may be an access network composed of E-UTRA and/or NextGen RA. In other words, the 5GRAN _ a120 may include the eNB _ a45, the AN node _ a122, and both. In this case, the eNB _ a45 and the AN node _ a122 may be the same device. Thus, the AN node _ a122 can be replaced with the eNB _ a 45.
It should be noted that the 5G RAN _ a120 may be a 5G-RAN (5G Radio Access Network: 5G Radio Access Network) or a 5G-AN (5G Access Network: 5G Access Network). In other words, the 5G RAN _ A120 may be represented as NextGen RAN and/or 5G-AN, and the NextGen RAN and/or 5GN-AN may also be represented as 5G RAN _ A120.
The WLAN ANc125 is a wireless LAN access network and includes a WAG _ a 126. A WAG (WLAN access gateway) _ a126 is a wireless base station to which the UE _ a10 connects through wireless LAN access, and may be configured to include one or more WAG _ a126 in the
In this specification, the UE _ a10 being connected to each radio access network means being connected to a base station apparatus, an access point, and the like included in each radio access network, and means that data, signals, and the like to be transmitted and received also pass through the base station apparatus, the access point, and the like. It should be noted that, regardless of the kind of the access network, the control message transmitted and received between the UE _ a10 and the core network _ B190 may be the same control message. Thus, messaging by the UE _ a10 and the core network _ B190 via the AN node _ a122 may be the same as messaging by the UE _ a10 and the core network _ B190 via the eNB _ a45 and/or the WAG _ a 126.
Next, an outline of a system when the PDU session anchor is relocated in the present embodiment will be described with reference to fig. 3. The core network _ B190 includes at least two UPFs (UPF _ a235, UPF _ B236), SMF _ a230, and AMF _ a 240. At this time, the DNs to which UPF _ A235 and UPF _ B236 are connected are equal. Also, the UPF _ a235 and the UPF _ B236 are gateway devices managed by the SMF _ a 230.
The UE _ a10 can transmit and receive the UPF _ a235 and/or the UPF _ B236 and user data via the access network _ B.
[1.2. constitution of device ]
First, identification information stored in each device will be described. SUPI (Subscriber permanent identifier) is permanent identification information allocated to a Subscriber of 5G in 5GS, permanent identification information of the Subscriber (user), and identification information allocated to a user using UE. The SUPI may be an IMSI (International Mobile Subscriber Identity) or a NAI (Network Access Identifier). The SUPI stored in UDM _ a50 and the IMSI stored in HSS may be equal, or an association between the SUPI stored in UDM _ a50 and the IMSI stored in HSS may be stored in at least any NF. The IMSI stored by the UE _ a10 and the AMF _ a240 may be equal to the IMSI stored by the UDM _ a50 or HSS.
The IMSI is permanent identification information of a subscriber (user), and is identification information allocated to a user using the UE. The IMSIs stored by UE _ A10, MME/CPF/AMF _ A240, and SGW may be equal to the IMSIs stored by UDM _ A50 or HSS.
The RM State/MM State indicates a Mobility management (Mobility management) State of the UE _ A10 or AMF _ A240. For example, the RM State/MM State may be an RM-REGISTERED State (REGISTERED State) in which the UE _ A10 is REGISTERED with the network and/or an RM-DEREGISTERD State (unregistered State) in which the UE _ A10 is not REGISTERED with the network. Further, the RMState/MM State may be an ECM-CONNECTED State to maintain a connection between the UE _ a10 and the core network and/or an ECM-IDLE State to release the connection. Note that the RM State/MM State may be information capable of distinguishing a State in which the UE _ a10 is registered with the EPC from a State in which it is registered with the 5 GC.
GUTI (Global Unique temporal Identity) is the Temporary identification information of UE _ A10. The GUTI is composed of identification information of the MME/CPF/AMF _ A240 (GUMMEI (Global Unique MMEIdenifier: Globally Unique MME identifier)) and identification information of UE _ A10 within a specific MME/CPF/AMF _ A240 (M-TMSI (M-temporal Mobile Subscriber Identity: M-Temporary Mobile Subscriber Identity)). The MEIdentity is the ID of the UE _ a10 or ME, and may be, for example, PEI (Permanent Equipment Identifier), IMEI (International Mobile Equipment Identity), IMEISV (IMEI Software Version). The MSISDN represents the basic phone number of UE _ a 10. The MSISDN stored by the MME/CPF/AMF _ a240 may be the information indicated by the storage of UDM _ a 50. Note that, the GUTI may include information for identifying the CPF.
The MME F-TEID is information identifying the MME/CPF/AMF _ A240. The MME F-TEID may include an IP address of the MME/CPF/AMF _ a240, may also include a TEID (Tunnel Endpoint Identifier) of the MME/CPF/AMF _ a240, and may also include both parties. In addition, the IP address of the MME/CPF/AMF _ A240 and the TEID of the MME/CPF/AMF _ A240 may be stored independently. The MME F-TEID may be identification information for user data or identification information for control information. The MME F-TEID may also be an AMF ID.
The SGW F-TEID is identifying SGW information. The SGW F-TEID may include the IP address of the SGW, may also include the TEID of the SGW, and may also include both parties. Further, the IP address of the SGW and the TEID of the SGW may be stored independently. The sgwf-TEID may be identification information for user data or identification information for control information. The SGW F-TEID may also be a UPG ID.
The PGW F-TEID is information identifying the PGW/UPGW/SMF _ A230/UPF _ A235. The PGW F-TEID may include the IP address of PGW/UPGW/SMF _ a230/UPF _ a235, may also include the TEID of PGW/UPGW/SMF _ a230/UPF _ a235, and may also include both. In addition, the IP addresses of the PGW/UPGW/SMF _ A230/UPF _ A235 and the TEIDs of the PGW/UPGW/SMF _ A230/UPF _ A235 may be stored separately. The PGW F-TEID may be identification information for user data or identification information for control information. The PGW F-TEID may also be UPGW ID.
The eNB F-TEID is information identifying eNB _ a 45. The eNB F-TEID may include the IP address of the eNB _ A45, may include the TEID of the eNB _ A45, and may include both. Further, the IP address of eNB _ a45 and the TEID of the SGW may be stored independently. The eNBF-TEID may be identification information for user data or identification information for control information.
The DNN (Data Network Name) may be identification information for identifying an external Network such as a core Network and DN. The DNN can also be used as information for selecting a gateway such as PGW/UPGW/UPF _ a235 connected to the core network. It should be noted that DNN may be apn (access Point name). Therefore, the APN may be expressed as a DNN, and the DNN may also be expressed as an APN.
The DNN may be identification information for identifying such a gateway, or may be identification information for identifying an external network such as a DN. When a plurality of gateways connecting the core network and the DN are arranged, a plurality of gateways that can be selected by the DNN may be present. Further, one gateway may be selected from such a plurality of gateways by another method using identification information other than DNN.
The DNN may be identification information for identifying such a gateway, or may be identification information for identifying an external network such as a DN. When a plurality of gateways connecting the core network _ B190 and the DN are arranged, a plurality of gateways that can be selected by the DNN may be present. Alternatively, one gateway may be selected from such a plurality of gateways by another method using identification information other than the DN ID.
The DNN may be information equivalent to the APN or information different from the APN. When the DNN and the APN are different information, each device may manage information indicating a correspondence relationship between the DNN and the APN, may perform a procedure of inquiring about the APN using the DNN, or may perform a procedure of inquiring about the DNN using the APN.
The UE Radio Access Capability is identification information indicating the Radio Access Capability of the UE _ a 10. The UE Network Capability includes algorithms and key derivation functions for security supported by UE _ a 10. MS Network Capability is information including one or more pieces of information required for the SGSN _ a42 for a UE _ a10 having GERAN _ a25 and/or UTRAN _ a20 functionality. Access restriction is registration information of access restriction. The eNB Address is the IP Address of eNB _ a 45. The MME UE S1AP ID is information identifying the UE _ A10 within the MME/CPF/AMF _ A240. The eNB UE S1AP ID is information identifying UE _ A10 within eNB _ A45.
APN in Use (APN being used) is the most recently used APN. The APN in Use may be a DataNetwork Identifier. The APN may be composed of identification information of a network, identification information of a default operator. Also, the APN in Use may be information identifying a DN of an establishment destination of the PDU session.
The Assigned Session Type is information indicating the Type of PDU Session. The Assigned Session Type may also be an Assigned PDN Type (specified PDN Type). The type of the PDU session may be IP or non-IP. Also, in case that the type of the PDU session is IP, information indicating the type of PDN allocated by the network may be further included. It should be noted that the Assigned Session Type may be IPv4, IPv6, or IPv4v 6.
In addition, if not specifically described, the 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. When the Assigned SessionType indicates non-IP, the element of IP Address may not be included.
The EPS Bearer ID (EPS Bearer ID) is identification information of the EPS Bearer. In addition, the EPS Bearer ID may be identification information for identifying an SRB (signaling Radio Bearer) and/or a CRB (Control-plane Radio Bearer), or may be identification information for identifying a DRB (Data Radio Bearer). TI (Transaction Identifier) is identification information for identifying a bidirectional message flow (Transaction). Note that the epsipearer ID may be EPS bearer identification information that identifies a dedicated bearer (dedicatedbearer). Thus, it may be identification information identifying an EPS bearer different from the default bearer. The TFT represents all packet filters that have established an association with the EPS bearer. The TFT is information identifying a part of the user data to be transmitted and received, and the UE _ a10 transmits and receives the user data identified by the TFT using the EPS bearer associated with the TFT. In other words, the UE _ A10 transmits and receives user data identified by the TFT using an RB (Radio Bearer) associated with the TFT. The TFT may associate user data such as application data to be transmitted and received with an appropriate transmission path, and may be identification information for identifying the application data. Further, the UE _ a10 may use a default bearer to transceive user data that cannot be recognized by the TFT. Further, the UE _ a10 may pre-store the TFT with which the default bearer is associated. The EPS Bearer ID may be a route ID.
The Default Bearer is EPS Bearer identification information identifying a Default Bearer established corresponding to the PDN session. It should be noted that the EPS bearer may refer to a logical communication path established between the UE _ a10 and the PGW/UPGW/UPF _ a235, or may refer to a communication path constituting a PDU connection/PDU session. Furthermore, the EPS bearer may be either a default bearer or a dedicated bearer. Also, the EPS bearer may be configured to include RBs established between the UE _ a10 and a base station and/or access point within the access network. Also, RBs may be in one-to-one correspondence with EPS bearers. Therefore, the identification information of the RB may correspond to the identification information of the EPS bearer one-to-one, or may be the same identification information. Note that the RB may be an SRB and/or a CRB, or a DRB. In addition, the Default Bearer may be information acquired by the UE _ a10 and/or the SGW and/or the PGW/UPGW/SMF _ a230/UPF _ a235 from the core network at the time of PDU session setup. It should be noted that the default bearer is an EPS bearer initially established in a PDN connection/PDU session, and is an EPS bearer that can only be established in one PDN connection/PDU session. The default bearer may be an EPS bearer that can be used in communication of user data for which no correspondence is established with the TFT. In addition, the dedicated bearer is an EPS bearer established after a default bearer is established in a PDN connection/PDU session, and is an EPS bearer that can establish a plurality of bearers in one PDN connection/PDU session. The dedicated bearer is an EPS bearer that can be used in communication of user data for which correspondence is established with the TFT. DefaultBearer may be a default route ID or may be information indicating one or more default routes.
User Identity is information identifying a subscriber. The User Identity may be SUPI, IMSI, or MSISDN. Further, the User Identity may be identification information other than SUPI, IMSI, MSISDN. The Serving Node Information is Information for identifying the MME/CPF/AMF _ a240 used in the PDU session, and may be an IP address of the MME/CPF/AMF _ a 240.
The eNB Address is the IP Address of eNB _ a 45. The eNB ID is information identifying the UE within eNB _ a 45. MME Address is the IP Address of MME/CPF/AMF _ A240. The MME ID is information identifying the MME/CPF/AMF _ A240. AN node Address is AN IP Address of AN node a 122. The AN node ID is information identifying the AN node _ a 122. The WAG Address is the IP Address of WAG _ a 126. The WAG ID is information identifying the WAG _ a 126.
The structure of each apparatus will be described below. The following devices and some or all of the functions of each part of each device may be executed on physical hardware or may be executed on logical hardware virtually configured by general-purpose hardware.
[1.2.1. constitution of UE ]
Fig. 4 shows an apparatus configuration of UE _ a 10. As shown in fig. 4, the UE _ a10 includes a transmission/reception unit _ a420, a control unit _ a400, and a storage unit _ a 440. The transmitting/receiving unit _ a420 and the storage unit _ a440 are connected to the control unit _ a400 via a bus. The control section _ a400 is a functional section for controlling the UE _ a 10. The control unit _ a400 reads and executes various programs stored in the storage unit _ a440 to realize various processes.
The transceiving section _ a420 is a functional section for the UE _ a10 to connect with a base station and/or an access point within an access network and connect to the access network. Further, an external antenna _ a410 is connected to the transmission/reception unit _ a 420. In other words, the transceiver section _ a420 is a functional section for the UE _ a10 to connect with a base station and/or an access point within the access network. The transceiver unit _ a420 is a transceiver function unit for the UE _ a10 to transmit and receive user data and/or control information from a base station and/or an access point in the access network.
The storage unit _ a440 is a functional unit that stores programs, data, and the like necessary for the operations of the UE _ a 10. 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 control messages transmitted and received in a communication process described later. The storage unit _ a440 stores a
First, information elements included in a UE context stored per UE are shown in (b) of fig. 5. As shown in fig. 5 (b), the UE context stored per UE includes SUPI, RM State, GUTI, and ME Identity. Next, a UE context per PDU session or PDN connection stored per PDU session or PDN connection is shown in fig. 5 (c). As shown in fig. 5 (c), the UE context of each PDU Session includes DNN, Assigned Session Type, ipaddress (es), Default Bearer.
Fig. 5 (d) shows a UE context for each bearer stored in the storage unit of the UE. As shown in fig. 5 (d), the UE context of each Bearer includes EPS Bearer ID, TI, TFT. [1.2.2. construction of eNB/AN node/WAG ]
The following describes the configuration of eNB _ a45, AN node _ a122, and WAG _ a 126. Fig. 6 shows AN apparatus configuration of eNB _ a45, AN node AN 122, and WAG _ a 126. As shown in fig. 6, the eNB _ a45, the AN node _ a122, and the WAG _ a126 are composed of 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.
The control section _ B600 is a functional section for controlling the eNB _ a 45. The control unit _ B600 reads and executes various programs stored in the storage unit _ B640 to realize various processes.
The network connection _ B620 is a functional part for connecting the eNB _ a45, the AN node _ a122, and the WAG _ a126 with the MME and/or the SGW. The network connection unit _ B620 is a transmission/reception unit for the eNB _ a45, the AN node _ a122, and the WAG _ a126 to transmit/receive user data and/or control information from the MME and/or the SGW.
The transceiving section _ B630 is a functional section for connecting the eNB _ a45, the AN node _ a122, and the WAG _ a126 with the UE _ a 10. The transceiver unit _ B630 is a transceiver function unit that transmits and receives user data and/or control information from the UE _ a 10. The external antenna _ B610 is connected to the transmission/reception unit _ B630.
The storage unit _ B640 is a functional unit that stores programs, data, and the like necessary for the operations of the eNB _ a45, the AN node _ a122, and the WAG _ a 126. The storage unit _ B640 is formed of, 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 control messages transmitted and received in a communication process described later. The storage section _ B640 may store these pieces of information as a context for each UE _ a 10.
[1.2.3. constitution of MME/CPF/AMF ]
The following describes the configurations of the MME, CPF, and AMF _ a 240. Fig. 7 shows the device configuration of the MME, CPF, and AMF _ a 240. As shown in fig. 7, the MME, the CPF, and the AMF _ a240 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 be executed on physical hardware or logical hardware virtually configured by general-purpose hardware.
The control unit _ C700 is a functional unit for controlling the MME, the CPF, and the AMF _ a 240. The control unit _ C700 reads and executes various programs stored in the storage unit _ C740 to realize various processes.
The network connection _ C720 is a functional part for the MME to connect with a base station within the access network and/or an access point within the access network and/or SCEF and/or UDM _ a50 and/or SGW. The network connection unit _ C720 is a transmission/reception unit for the MME to transmit/receive user data and/or control information to/from a base station in the access network and/or an access point in the access network and/or SCEF and/or UDM _ a50 and/or SGW.
The network connection unit _ C720 is a functional unit for connecting the CPF to a base station in the access network and/or an access point in the access network and/or the SCEF and/or the UDM _ a50 and/or the UPGW and/or the UPF _ a235 and/or the SMF _ a 230. The network connection unit _ C720 is a transmission/reception unit for the MME to transmit/receive user data and/or control information to/from a base station in the access network and/or an access point in the access network and/or SCEF and/or UDM _ a50 and/or UPGW and/or UPF _ a 235.
The storage unit _ C740 is a functional unit that stores programs, data, and the like necessary for the operations of the MME, the CPF, and the AMF _ a 240. 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 control messages transmitted and received in a communication procedure described later.
The storage unit _ C740 stores an MME context 742 as shown in fig. 7. The information element stored in the storage unit _ C740 will be described below. Note that in the MME context, the CPF may be a storage context. First, information elements included in a UE context stored per UE are shown in (b) of fig. 8. As shown in fig. 8 (b), the MME context stored for each UE includes one or more of SUPI, MSISDN, RM State, GUTI, ME Identity, UE Radio Access Capability, UE Network Capability, MS Network Capability, Access response, MMEF-TEID, SGW F-TEID, eNB Address, MME UE S1AP ID, eNB UE S1AP ID, AN node Address, AN node ID, WAG Address, and WAG ID.
Next, an MME context per PDU session or PDN connection stored per PDU session or PDN connection is shown in fig. 9 (c). As shown in fig. 9 (c), the MME context of each PDU session includes DNN, AssignedSession Type, IP Address (es), PGW F-TEID, and Default bearer.
Fig. 9 (d) shows an MME context per bearer stored per bearer. As shown in fig. 9 (d), the MME context stored per Bearer includes one or more of EPS Bearer ID, TI, TFT, SGW F-TEID, PGW F-TEID, MME F-TEID, eNB Address, AN node Address, WAG Address, eNB ID, AN node ID, and WAGID. Here, the information elements included in the MME context illustrated in fig. 8 and 9 may be included in either the MM context or the EPS bearer context for storage.
[1.2.4.SGW/UPF constitution ]
Fig. 10 shows the device configuration of the SGW/UPF _ a 235. As shown in fig. 10, the SGW/UPF _ a235 includes a network connection unit _ D1020, a control unit _ D1000, and a storage unit _ D1040. The network connection unit _ D1020 and the storage unit _ D1040 are connected to the control unit _ D1000 via a bus.
The control unit _ D1000 is a functional unit for controlling the SGW/UPF _ a 235. The control unit _ D1000 reads and executes various programs stored in the storage unit _ D1040 to realize various processes.
The network connection _ D1020 is a functional part for the SGW/UPF _ a235 to connect with a base station and/or access point and/or MME and/or PGW and/or SGSN _ a42 within the access network. The network connection unit _ D1020 is a transmission/reception unit for the SGW/UPF _ a235 to transmit/receive user data and/or control information from a base station and/or access point and/or MME and/or PGW and/or SGSN _ a42 in the access network.
The storage unit _ D1040 is a functional unit that stores programs, data, and the like necessary for each operation of the SGW/UPF _ a 235. The storage unit _ D1040 is formed of, 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 a flag and/or a parameter included in a control message transmitted and received in a communication procedure described later.
The storage section _ D1040 stores the
First, fig. 11 (b) shows information elements of an EPS bearer context stored per UE. As shown in fig. 11 (b), the EPS bearer context stored per UE includes SUPI, ME Identity, 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. The EPS bearer context per PDU session is shown in fig. 11 (c). As shown in fig. 11 (c), the EPS bearer context of each PDU Session includes DNN, Assigned Session Type, SGW F-TEID, PGW F-TEID, defaultbefore, and IP Address (es).
Also, the EPS bearer context includes an EPS bearer context for each bearer. An EPS bearer context for each bearer is shown in fig. 11 (d). As shown in fig. 11 (d), the EPS Bearer context of each Bearer includes one or more of EPS Bearer ID, TFT, PGW F-TEID, SGW F-TEID, eNB F-TEID, MME Address, AN node Address, WAG Address, MME ID, AN node ID, and WAG ID.
[1.2.5. constitution of PGW/UPGW/SMF/UPF ]
Fig. 10 shows the device configuration of the PGW, UPGW, SMF _ a230, and UPF _ a 235. As shown in fig. 10, the PGW, UPGW, SMF _ a230, and UPF _ a235 are configured by 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 be executed on physical hardware or logical hardware virtually configured by general-purpose hardware.
The control unit _ D1000 is a functional unit for controlling the PGW. The control unit _ D1000 reads and executes various programs stored in the storage unit _ D1040 to realize various processes.
The network connection _ D1020 is a functional part for connecting the PGW with the SGW and/or PCF _ a60 and/or ePDG _ a65 and/or AAA _ a55 and/or TWAG _ a74 and/or DN _ a 5. The network connection _ D1020 is a transmission/reception unit for the PGW to transmit/receive user data and/or control information from the SGW and/or PCF _ a60 and/or ePDG _ a65 and/or AAA _ a55 and/or TWAG _ a74 and/or DN _ a 5.
Also, the network connection part _ D1020 is a functional part for the UPGW to connect with the PCF _ a60 and/or the AN node _ a122 and/or the DN _ a 5. The network connection _ D1020 is a transmission/reception unit for the PGW to transmit/receive user data and/or control information from the SGW and/or PCF _ a60 and/or ePDG _ a65 and/or AAA _ a55 and/or TWAG _ a74 and/or DN _ a 5.
Further, the network connection part _ D1020 is a functional part for connecting the SMF _ a230 with the AMF _ a240 and/or the UPF _ a235 and/or the UDM _ a50 and/or the PCF _ a 60. The network connection unit _ D1020 is a transmission/reception unit for the SMF _ a230 to transmit/receive control information to/from the AMF _ a240, the UPF _ a235, and/or the UDM _ a 50.
Further, the network connection part _ D1020 is a functional part for connecting the UPF _ a235 with the AN node _ a122 and/or the SMF _ a230 and/or the PDN _ a5 and/or the DN _ B105. The network connection unit _ D1020 is a transmission/reception unit through which the UPF _ a235 transmits/receives user data and/or control information to/from the AN node _ a122, the SMF _ a230, the DN _ a5, and/or the DN _ B105.
The storage unit _ D1040 is a functional unit that stores programs, data, and the like necessary for each operation of the PGW. The storage unit _ D1040 is formed of, 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 a flag and/or a parameter included in a control message transmitted and received in a communication procedure described later.
The storage section _ D1040 stores the
Information elements included in the EPS bearer context stored per UE are shown in fig. 12 (b). As shown in fig. 12 (b), the EPS bearer context stored per UE includes SUPI, ME Identity, MSISDN, RAT type (RAT type).
Next, fig. 12 (c) shows an EPS bearer context stored per APN. As shown in fig. 12 (c), the EPS bearer context stored for each APN in the PGW storage unit includes an APN in use. It should be noted that the EPS bearer context stored for each APN may also be stored for each Data Network Identifier (Data Network Identifier).
Further, an EPS bearer context per PDU session or PDN connection stored per PDU session or PDN connection is shown in (d) of fig. 12. As shown in fig. 12 (d), the EPS Bearer context of each PDU Session or PDN connection includes Assigned Session Type, IP Address (es), SGW F-TEID, PGW F-TEID, Default Bearer.
An EPS bearer context stored per EPS bearer is further shown in fig. 12 (e). As shown in fig. 12 (e), the EPS Bearer context includes EPS Bearer ID, TFT, SGW F-TEID, PGW F-TEID.
[1.3 description of initial Process ]
Next, terms specific to the present embodiment and main identification information used in each process will be described in advance to avoid overlapping description before describing the detailed steps of the initial process of the present embodiment.
SUPI (Subscriber Permanent Identifier) is identification information allocated to a registrar. The SUPI may be an IMSI (International Mobile Subscriber Identity) or a NAI (Network Access Identifier).
The CM state refers to information for managing the state of the connection of NAS signals between the UE and the AMF. The CM state includes a CM-IDLE state in which there is no connection between the UE and the AMF and a CM-CONNECTED state in which a connection between the UE and the AMF is established.
The CM-IDLE state UE is a state in which there is no connection of the AMF with the NAS signal and a state in which the connection with the access network is released. In case the CM-IDLE UE transmits an uplink signal or user data, a service request procedure may also be started requesting a transition to CM-CONNECTED. The AMF in the CM-IDLE state may also initiate the transition to the CM-IDLE state by initiating a service request procedure by sending a page to the UE.
On the other hand, the UE in the CM-CONNECTED state may be in a state in which connection to NAS signals of the AMF is established and in a state in which connection to the access network is established.
Dnn (data Network name) is information identifying dn (data Network). The DNN may also be an APN (Access Point name).
The first PDU session is a PDU session constituting a route with the UPF _ a235 as an anchor point. In other words, the anchor point for the first PDU session is UPF _ A235.
The second PDU session is a PDU session constituting a route with the UPF _ B236 as an anchor point. In other words, the anchor point for the first PDU session is the UPF _ B236.
The first state refers to a state in which the first PDU session is established and the second PDU session is not established. Also, the first state is the REGISTERD state.
Here, the REGISTERD state is a state in which the UE is registered in the network, and may be a state in which the AMF stores a context for the UE.
The second state refers to a state in which the first PDU session is not established and the second PDU session is not established. Also, in the second state, the network may be a state in which information on the first PDU session is stored. In other words, the second state may be a state in which the AMF _ a240 stores an SMF ID identifying a selected SMF in the first PDU session and/or a state in which the SMF _ a230 stores a UPF ID identifying a selected UPF in the first PDU session. The second state may be the REGISTERD state.
It should be noted that the SMF _ a230 may store the UPF ID identifying the selected UPF in the first PDU session as the UPF prohibited during the PDU session re-establishment procedure, or may select the relocated UPF to store instead.
The third state refers to a state in which the first PDU session is not established and the second PDU session is established. In other words, the third state refers to a state in which the first PDU session is released and the second PDU session is established. Also, the third state is the REGISTERD state.
The fourth state refers to a state in which the first PDU session is established and the second PDU session is established. In other words, the fourth state is a state in which the first PDU session and the second PDU session are simultaneously established. The fourth state may be the REGISTERD state.
The ssc (Session and Service Continuity) mode indicates a mode in which Service sessions (sessions and Service Continuity) supported by the system and/or each device are continuous in 5 GC. In more detail, it may be a mode indicating a kind of service session continuity supported by the PDU session established between the UE _ a10 and the anchor point. Here, the anchor point may be a UPGW or a UPF _ a 235. The SSC pattern may be a pattern indicating a type of service session continuity set for each PDU session. The SSC pattern may include three patterns, i.e.,
In addition, the
Further, the SSC pattern 2 in the present embodiment is a service session continuation pattern in which, when one anchor point associated with the SSC pattern 2 is included in a PDU session, the PDU session is released first and then the PDU session is continuously established. In detail, the SSC pattern 2 is a pattern for deleting a PDU session once and then reestablishing the PDU session when anchor relocation occurs.
Further, the SSC pattern 2 is a pattern in which a service session that continuously maintains the same UPF as an anchor point is continued only in the service area of the UPF. In more detail, the SSC pattern 2 may be a pattern that enables service session continuity without changing the UPF used by the established PDU session as long as the UE _ a10 is within the service area of the UPF. Furthermore, when the UE _ a10 moves as if it leaves the service area of the UPF, the SSC pattern 2 may be a pattern in which service session continuity is achieved by changing the UPF used for the established PDU session.
Here, the service area of the TUPF may be an area where one UPF can provide a service session continuity function, or may be a subset of an access network such as a RAT or a cell used when the UE _ a10 connects to a network. Also, the subset of access networks may be either a network comprising one or more cells or a TA.
Further, SSC mode 3 in the present embodiment is a mode in which a service session continuation can be established between a new anchor and the UE on the same DN without releasing a PDU session between the UE and the anchor.
Also, the SSC mode 3 is a service session continuation mode that allows a new PDU session and/or communication path via a new UPF to be established for the same DN before the PDU session and/or communication path established between the UE _ a10 and the UPF is disconnected. Also, the SSC pattern 3 may be a pattern that allows the UE _ a10 to become a multi-homed service session continuation.
And/or SSC pattern 3 may also be a pattern that allows a service session using a plurality of PDU sessions and/or UPFs corresponding to the PDU sessions to be continuous. In other words, in the SSC mode 3, each device may use a plurality of PDU sessions to continue a service session, or may use a plurality of TUPFs to continue a service session.
Here, in the case where each device establishes a new PDU session and/or communication path, the selection of a new UPF may be implemented by the network, and the new UPF may be the one most suitable for the location where the UE _ a10 is connected to the network. Further, when a plurality of PDU sessions and/or the UPFs used for the PDU sessions are valid, the UE _ a10 may perform the correspondence between the newly established PDU sessions of the communication of the application and/or the flow at once or may perform the correspondence based on the completion of the communication.
The multi home PDU session means that a plurality of IPv6 prefixes establish an associated PDU session. In other words, a multimedia PDU session provides access to the DN, routing, user data paths via more than one normal anchor point.
The PDU session Type refers to information provided in the PDU session, indicating the kind of connection, showing IPv4, IPv6, Ethernet Type, or non-IP Type.
A default route refers to a communication path that is selectable without a route corresponding to a particular service. More specifically, the path is a default router that transmits user data to the UE without a route corresponding to a specific service. Note that, in the case where a plurality of PDU sessions or a PDU session including a plurality of routes is established between the UE and the DN, a route used by default or a route included in the PDU session is indicated. The default route may be one per PDU session or may be distributed in plural.
In addition, the UE may establish multiple PDU sessions, or may establish a default route per PDU session.
In this way, the UE may establish multiple default routes. The UE may also store a default router for each default route. Thus, the UE may also store multiple default routers. Alternatively, only one default router having a high priority may be managed. At this point, other default routers may be deleted and/or default routes corresponding to the default routers may be established.
The nsi (Network Slice entity) of the present embodiment is an entity in which one or more Network slices (Network slices) are arranged in the core Network _ B190. The NSI according to the present embodiment may be configured by a virtual nf (Network function) generated using NST (Network Slice Template). Here, NST refers to a logical representation of one or more nfs (network functions) associated with a resource request for providing a requested communication service, capability.
That is, the NSI may refer to an aggregate within the core network _ B190 composed of a plurality of NFs. The NSI may be a logical network configured to divide distributed user data according to services and the like. At least one more NF may be constructed in the network slice. The NFs that make up a network slice may or may not be devices that are shared with other network slices.
The UE can be assigned to one or more network slices based on APNs and/or registration information such as UE usage type (UE usage type) and/or one or more network slice type IDs and/or one or more NS IDs.
Next, the identification information in the present embodiment will be described.
The first identification information in the present embodiment is information indicating whether the network notifies the UE of Preference information of a route. Specifically, the first identification information is information indicating Preference information indicating whether or not an RTR (router) or an SMF constituting a UPF serving as an anchor point and/or a UPF serving as an anchor point notifies the UE of a route. The first identification information may be information indicating that the UE determines a default route. Alternatively, the first identification information may be Capability information indicating that the UE has a function of determining a default route.
Also, the first identification information may be information indicating an SSC pattern requested by the UE. Specifically, in case that the SSC pattern requested by the UE is SSC pattern 2 and/or SSC pattern 3, the network may inform the UE of the Preference information. On the other hand, in case that the SSC pattern requested by the UE is
The first identification information may be DNN. Specifically, in the case where the DNN is information representing the DN of the MEC, the network may notify the UE of the Preference information.
Further, the first identification information may also be information indicating whether the UE supports establishment of a multi-homed PDU session. Specifically, in case the UE supports the establishment of a multi homed PDU session or requests the establishment of a multi homed PDU session, the network may notify the UE of the Preference information. The first identification information may be the third identification information.
When the network notifies the UE of the Preference information, the UPF and/or the RTR or the SMF may include the Preference information in an ra (router advertisement) and transmit the same, or the SMF may include the Preference information in a NAS message and transmit the same.
The second identification information in the present embodiment is information indicating an SSC pattern requested by the UE. The second information may be information indicating
In the case where the second identification information is information indicating SSC pattern 3, the first identification information and the second identification information may be configured as one identification information having their respective meanings. In the present embodiment, when the first identification information and the second identification information indicating the SSC pattern 3 are transmitted and received in a single control message, the identification information may be transmitted and received as one piece of identification information having their meanings.
The third identification information in the present embodiment is information indicating that establishment of a multi-homed PDU session is requested. The third identification information may be Capability information indicating that the UE supports a setup function of a multi-homed PDU session. In other words, the third identification information may be information indicating that the UE supports establishment of a multi-homed PDU session.
The first identification information and the third identification information may be configured as one identification information having respective meanings. In the present embodiment, when the first identification information and the third identification information are included in a single control message and transmitted and received, the identification information configured as one identification information having each meaning may be transmitted and received.
The fourth identification information in the present embodiment is information for identifying a network slice. The fourth identification information may be S-nssai (single Network Slice Selection Assistance information). The fourth identification information may be information associated with the fifth identification information. The fourth identification information may be information indicating a type of a network slice requested by the UE, a type of an application program.
The fifth identification information in the present embodiment is information indicating a DN requested by the UE. The fifth identification information may be dnn (data Network name).
The sixth identification information in the present embodiment is information indicating a PDU session to which a connection is requested. The sixth identification information may be a PDU session ID. The sixth identification information may be information managed by the UE. The sixth identification information may be information indicating that the established PDU session is a new PDU session. The sixth identification information may be information indicating a PDU session released once.
The seventh identification information in the present embodiment is information indicating the type of the request. The seventh identification information may be a Request type (Request type). The seventh identification information may be information indicating that a PDU session identified by the PDU session ID indicated by the sixth identification information has been established in non-3GPP, or information indicating correspondence to the PDN connection established in 3GPP, in association with the sixth identification information.
The eleventh identification information in the present embodiment is Preference information (Route Preference: Prf) of a Route included in an established PDU session. The eleventh identification information may be information indicating the priority level of the route, and may be represented by "High", "Medium", or "Low", for example. Alternatively, "high", "medium", and "low" may be used to indicate the same three phases. Note that "Medium" or "middle" may be used as information indicating default. Alternatively, it can be represented with a higher granularity. Alternatively, it can be expressed in a lower granularity. The eleventh identification information may be determined based on operator policy, location information of the UE, congestion status of RAT type, S-NSSAI, or UPF, or may also be determined based on two or more of these pieces of information.
Also, the eleventh identification information may be information for selecting a default route. More specifically, it may be information for selecting a default router. For example, in the case where the default router and the reference information are stored for each PDU session, a default router corresponding to the reference information having a high priority level may be selected to transmit data. In this way, a default route may be selected that facilitates selection of a default router.
It should be noted that the preference information may be information corresponding to the default router and/or default route and/or IPv6 network prefix. Thus, different priorities may be set per default router and/or per default route and/or per IPv6 network prefix.
The twelfth identification information in the present embodiment is an SSC pattern supported by an anchor point of an established PDU session. The twelfth identification information may be information selected and determined by the SMF. The twelfth identification information may be determined based on registration information of the UE.
The thirteenth identification information in the present embodiment is capability information indicating that establishment of a multi-homed PDU session is supported. In other words, the thirteenth information may be information indicating that the network supports establishment of a multi-homed PDU session, or may be information indicating that the network allows establishment of a multi-homed PDU session.
The fourteenth identification information in the present embodiment is information indicating a PDU session type. The fourteenth identification information may be information indicating an address. And more particularly, may be an IPv6 network prefix. The fourteenth identification information may include information indicating that the PDU session type of the PDU session established or changed by the procedure has become the PDU session type indicated by the identification information, or may include information indicating that an address corresponding to the PDU session established or changed by the procedure has become the address indicated by the identification information and/or the address of the PDU session type indicated in the present embodiment.
The fourteenth identification information may be information indicating that the PDU session type used for the user data communication to the DN has become the PDU session type indicated by the present identification information, or may be information indicating that the address used for the user data communication to the DN has become the address indicated by the present identification information and/or the address of the PDU session type shown in the present embodiment.
The fourteenth identification information may include a plurality of pieces of information indicating the PDU session type and/or address, information indicating whether each PDU session type is a PDU session type used for user data communication to the DN, and information indicating whether each address is an address used for user data communication to the DN.
The fourteenth identification information may be information indicating that a PDU session connected to the DN has been established, information indicating that the connection destination of the PDU session has been changed to the DN, or information indicating that a PDU session established or changed by the present procedure is changed to a PDU session used for user data communication to the DN.
The fifteenth identification information in the present embodiment is information indicating a reason (cause). The fifteenth identification information may be information indicating that the setup of the PDU session is rejected.
The fifteenth identification information may be information indicating that a PDU session constituting an anchor supporting the SSC pattern requested by the UE cannot be established. In other words, it may be information indicating that the network does not support the SSC pattern requested by the UE.
The fifteenth identification information may be information indicating that the establishment of a multi homed PDU session is not supported. In other words, the fifteenth identification information may be information indicating that the network does not support establishment of a multi home PDU session, or may be information indicating that the network does not allow establishment of a multi home PDU session.
The fifteenth identification information may be information indicating a plurality of reasons, or may be processed as information that is independent for each reason.
The twenty-first identification information in the present embodiment is information indicating that the network temporarily maintains the storage of information on the released PDU session. Also, the twenty-first information may also be Temporary information that is associated with information on a PDU session temporarily stored by the network. In other words, the temporarily stored information on the PDU session may be associated with the twenty-first identification information, stored by the AMF and/or the SMF. The Temporary information may be a PDU Session ID identifying the PDU session being released.
Further, the twenty-first information may be information indicating that the network requests re-establishment of a PDU session for the same DN as the released PDU session. In other words, the twenty-first identification information may be information used for the UE to start a re-establishment procedure of the PUD session.
Here, the network may temporarily store the information on the PDU session in such a manner that the AMF stores an SMF ID identifying an SMF corresponding to a PDU session ID identifying the released PDU session and/or the SMF stores a UPF ID identifying an UPF corresponding to the PDU session.
The SMF may manage the UPF associated with the PDU session as the UPF prohibited when the PDU session is reestablished, and store the UPF ID. Alternatively, the SMF may determine the UPF of the relocation target in advance and store the UPF identifying the relocation destination.
The twenty-first information may be information indicating an SSC pattern. Specifically, when the twenty-first identification information is information indicating the SSC pattern 2, it may indicate that the network temporarily maintains and stores information on the released PDU session. Alternatively, the twenty-first identification information may be twenty-second identification information.
The twenty-second identification information in the present embodiment may be information indicating that the network requests re-establishment of a PDU session for the same DN as the deleted or released PDU session. Alternatively, the twenty-second identification information in the present embodiment may be information indicating that the network needs to establish a PDU session again for the same DN as the deleted or released PDU session. In other words, the twenty-second identification information may be information for the UE to start a re-establishment procedure of the PDU session. The twenty-second identification information may be information indicating a reason.
The thirty-first identification information in the present embodiment is information indicating that establishment of a PDU session is requested based on a request from the network. In other words, the thirty-first identification information may indicate that the UE requests and starts the setup procedure of the PDU session based on a request from the network. Also, the thirty-first identification information may indicate that the UE requests and starts the establishment of a PDU session for the purpose of relocation of the anchor point.
The thirty-second identification information in the present embodiment is information indicating information on a PDU session requested to be established. The thirty-second identification information may be the same as the twenty-first identification information. In other words, the thirty-second identification information may be information that is associated with information on the PDU session temporarily stored by the network. The thirty-second identification information may be information for the AMF to select the SMF, and may also be information for the SMF to select the UPF.
The thirty-second identification information may also be thirty-third identification information.
The thirty-third identification information in the present embodiment is PDU session identification information that identifies a PDU session released before, that is, a past PDU session (old PDU session). The thirty-third identification information may indicate that the UE requests and starts an establishment procedure of the PDU session based on a request from the network. Also, the thirty-first identification information may indicate that the UE requests and starts the establishment of a PDU session for the purpose of relocation of the anchor point.
The fortieth identification information in the present embodiment is information indicating that the release of the PDU session is requested based on the reference information. In other words, the fortieth identification information is information indicating that the UE determines the released PDU session based on the Preference information, starts or requests to start the release procedure of the PDU session. The fortieth identification information may be information indicating a reason.
The fortieth identification information may be information indicating that the release of the PDU session is requested.
The fifty-first identification information in the present embodiment is information indicating a reason (cause). The fifty-first identification information may be information indicating that the reference information is updated. The fifty-first identification information may also be information indicating that the request of the UE does not coincide with the reference information.
Specifically, in the case where the network confirms that the reference information of each route managed by the network is different as a result of the reception of the fortieth identification information, the network transmits the fifty-th identification information to the UE. In other words, the fifty-first identification information may be information indicating that the reference information stored by the UE is different from the information stored by the network or the reference information is updated.
The sixtieth identification information in the present embodiment is information indicating a reason (cause). The sixteenth identification information may be information indicating that a change of a default route of the PDU session is requested. The sixteenth identification information may be information that requests update of the reference information in order to request change of the default route. In other words, the sixty-first identification information may be information that requests the update of the reference information from the network and notifies the updated reference information.
The sixteenth identification information may be information indicating a type of change of the PDU session, or may be a PDU session change type (PDU session modification type).
The sixteenth identification information in the present embodiment is information for identifying a route for requesting update or change of the reference information. The sixty-second identification information may be a route ID for identifying a route, a UPF ID for identifying an anchor point, or an IP address. Also, the sixty-second identification information may be information indicating a default route. In other words, the sixty-second identification information may indicate a route that the UE wants to change to the default route. Alternatively, the sixty-second identification information may be information indicating a route for which the UE wants to update the Preference information.
The seventy-first identification information in the present embodiment is information indicating a reason (cause). The seventy-first identification information may be information indicating update or change of the Preference information. In other words, the seventy-first identification information may be information indicating that the network is updated and the Preference information is changed. The seventy-first identification information may be information indicating an update or change of a PDU session due to movement of the UE. In other words, the seventy-first identification information may be information indicating that the network updated information on the PDU session along with the update of the UE location information.
The seventy-second identification information in the present embodiment is information indicating updated and changed Preference information. The seventy-second information may be information informing, by the network, an update or change of Preference information of a route or an anchor included in the PDU session. The seventy-second identification information may also be the same as the eleventh identification information.
The eighty-first identification information in the present embodiment is information indicating a reason. The eighty-first identification information may be information indicating that updating of the reference information is not supported. The eighty-first identification information may be information indicating that the update of the Preference information does not satisfy the request of the UE.
Next, in the present embodiment, an initial process will be described with reference to fig. 13. In the present embodiment, each device transits to the first state by performing an initial procedure, and the UE _ a10 establishes a first PDU session via the core network _ B190. Hereinafter, the present process is referred to as an initial process, and each process includes a registration process and a PDU session establishment process. Details of each process are described later.
In this procedure, each device first executes a registration procedure (S1300), and transitions to a state in which UE _ a10 is connected to the network. Next, each device executes a PDU session setup procedure (S1302) to transition to a first state (S1304). It should be noted that the devices may exchange various capability information and/or various request information of the devices during the registration process and/or the PDU session establishment process.
It should be noted that, in the case where the exchange of various information and/or the negotiation of various requests have been performed during the registration process, the devices may not perform the exchange of various information and/or the negotiation of various requests during the PDU session establishment process. Conversely, the devices may perform the exchange of various information and/or the negotiation of various requests during the PDU session setup without performing the exchange of various information and/or the negotiation of various requests during the registration process. But not limited thereto, the devices may also perform the exchange of various information and/or the negotiation of various requests in the PDU session setup procedure, in case the exchange of various information and/or the negotiation of various requests has already been performed in the registration procedure.
In addition, each device may perform the PDU session establishment procedure during the registration procedure, or may perform the PDU session establishment procedure after the registration procedure is completed. In the case where the PDU session setup procedure is performed in the registration procedure, the PDU session setup request message may be included in the registration request message for transceiving, the PDU session setup accept message may be included in the registration accept message for transceiving, the PDU session setup complete message may be included in the registration complete message for transceiving, and the PDU session setup reject message may be included in the registration reject message for transceiving. Also, in the case where the PDU session establishment procedure is performed during the registration procedure, each device may establish the PDU session based on completion of the registration procedure, or may transition to the first state.
Each apparatus completes the process through the above process. Each device related to this process can transmit and receive one or more pieces of identification information included in each control message by transmitting and receiving each control message described in this process, and store each piece of identification information transmitted and received as a context. Also, each device may transition to the first state upon completion of the present process.
[1.3.1. overview of registration procedure ]
First, an outline of the registration process will be described. The registration procedure is a procedure that is dominated by the UE _ a10 for connecting to the network (access and/or core network _ B190 and/or DN _ a 5). When in a state of not being connected to the network, the UE _ a10 may perform the present process at an arbitrary timing such as when the terminal is powered on. In other words, the UE _ a10 can start the present procedure at an arbitrary timing when in the unregistered state (RM-registered). Further, each device may transition to a REGISTERED state (RM-REGISTERED) based on completion of the registration process.
Also, the present procedure may be a procedure of updating location registration information of the UE _ a10 in the network and/or periodically informing the network of the status of the UE _ a10 from the UE _ a10 and/or updating specific parameters about the UE _ a10 in the network.
UE _ a10 may begin the process when moving across TAs. In other words, UE _ a10 may begin the process upon entering a TA other than the TA shown in the maintained TA list. Also, the UE _ a10 may begin the process upon expiration of the executed timer. Also, the UE _ a10 may start the process when the context of each device needs to be updated due to the PDU session and/or EPS bearer being switched off, disabled. Also, the UE _ a10 may start the present procedure in case capability information and/or preferences regarding PDU session setup of the UE _ a10 changes. Also, the UE _ a10 may start the process periodically. Note that the UE _ a10 is not limited to this, and the present procedure can be executed at an arbitrary timing as long as the PDU session is established.
[1.3.2. overview of PDU Session setup procedure and registration procedure ]
Hereinafter, a case where the PDU session setup procedure is performed in the registration procedure will be described.
Hereinafter, the present procedure refers to a PDU session setup procedure and a registration procedure. This procedure is performed by each device to establish a PDU session. It should be noted that each device may perform the PDU session establishment procedure in a state where the registration procedure is completed. Further, each device may start the PDU session establishment procedure in the registration state, or may start the PDU session establishment procedure at an arbitrary timing after the registration procedure. Further, each device may establish a PDU session based on completion of the present process. Also, each device may establish a plurality of PDU sessions by performing a PDU session establishment procedure, which is not included in the registration procedure, a plurality of times.
[1.3.2.1.PDU Session setup procedure example ]
An example of the steps of performing the PDU session setup procedure will be described using fig. 15. Hereinafter, each step of the present process will be described. First, the UE _ a10 transmits a PDU session setup request (PDU session setup request) message to the SMF _ a230 via the AN node _ a122 and the AMF _ a240 (S1500), (S1502), and (S1504), and starts a PDU session setup procedure.
It should be noted that the PDU session establishment request message may be included in a registration request (registration request) message for transmission. For example, the registration request message may include a PDU session setup request message as an SM message, or may include a PDU session setup request message as an NAS message.
Specifically, the UE _ a10 transmits a PDU session setup request message to the AMF _ a240 using the N1 interface (S1500), the AMF _ a240 having received the PDU session setup request message selects the SMF _ a230 as the NF of the routing destination of the PDU session setup request message (S1502), and transmits the PDU session setup request message to the selected SMF _ a230 using the N11 interface (S1504). Here, the AMF _ a240 may select the SMF _ a230 of the routing destination based on information included in the PDU session setup request message. In more detail, the AMF _ a240 may select the SMF _ a230 of the routing destination according to various identification information and/or subscriber information and/or capability information of the network and/or operator policy and/or network status and/or context that the AMF _ a240 has maintained, which are acquired based on the reception of the PDU session setup request message.
It should be noted that, in the case that the PDU session is PDN connection (PDN connection), the PDU session establishment request message may be a PDN connection request (PDN connection request) message. The PDU session establishment request message may be a NAS message transmitted and received over the N1 interface and the N11 interface, or may be included in a NAS message. Further, the PDU session establishment request message is not limited thereto, and may be a message requesting establishment of a PDU session.
Here, the UE _ a10 may include at least one or more identification information of the first to seventh identification information in the PDU session setup request message and/or the registration request message and/or the NAS message, or may indicate the request of the UE _ a10 by including the identification information.
Also, the UE _ a10 may request establishment of a PDU session connected with the DN _ a5 by transmitting one or more identification information among the first to seventh identification information. In more detail, the UE _ a10 may request establishment of a PDU session connected to the DN _ a5 by transmitting the fifth identification information and/or associating the fourth identification information with the fifth identification information.
Also, the UE _ a10 may request establishment of a PDU session identified by the PDU session ID indicated by the sixth identification information by transmitting the sixth identification information and/or associating the fifth identification information with the sixth identification information, or may request setting of a connection destination of the established PDU session to DN _ a 5.
Also, the UE _ a10 may indicate that the PDU session identified by the PDU session ID identified by the sixth identification information is the request type indicated by the seventh identification information by transmitting the seventh identification information and/or associating the sixth identification information with the seventh identification information.
Also, the UE _ a10 may request transmission of the preference information from the anchor point in or after the PDU session indicated by the sixth identification information is established by transmitting the first identification information and/or transmitting the sixth identification information in correspondence with the first identification information.
Also, the UE _ a10 may request the SSC pattern of the PDU session identified by the PDU session ID identified by the sixth identification information by transmitting and/or establishing correspondence with the sixth identification information to the second transmission second identification information.
Further, the UE _ a10 may request establishment of a multi-homed PDU session by transmitting the third identification information and/or transmitting the third identification information in association with the sixth identification information, may request addition or deletion of a route caused by addition or deletion of an anchor point for a PDU session identified by the PDU session ID identified by the sixth identification information, may request support of a procedure for a multi-homed PDU session, or may request connection with an anchor point that supports a procedure for a multi-homed PDU session.
It should be noted that the UE _ a10 may determine which of the first to 7 th identification information to add to the PDU session setup request message and/or the registration request message and/or the NAS message based on the capability information of the UE _ a10 and/or the policy such as the UE policy and/or the preference of the UE _ a 10. It should be noted that the determination of which identification information to add to the PDU session setup request message and/or the registration request message and/or the NAS message by the UE _ a10 is not limited thereto.
For example, the UE _ a10 may transmit the first identification information included in the PDU session setup request message and/or the registration request message and/or the NAS message in case of transmitting the second identification information indicating SSC mode 3 and/or in case of requesting to establish a PDU of SSC mode 3 and/or in case of transmitting the third identification information and/or in case of requesting to establish a multiple PDU session.
Also, the UE _ a10 may transmit information indicating whether the information indicating the reference of the PDU session is received by the ra (router advertisement) message or the PDU session accept message. The information may be information indicating any one of the above-described reception methods. It should be noted that the receiving method may be determined by the policy of the UE. Thus, the UE _ a10 may request a receiving method of information representing a reference of the PDU session. Hereinafter, the identification information will be described using the name of reception method request information. It should be noted that the UE _10 may include the reception method request information in its control message to transmit in a case where the first identification information and/or the second identification information and/or the third identification information indicating the SSC pattern 3 are included in the PDU session setup request message and/or the registration request message and/or the NAS message.
The SMF _ a230 receives the PDU session setup request message and performs a first conditional discrimination. The first condition is determined to determine whether the SMF _ a230 accepts the request of UE _ a 10. In the first condition discrimination, the SMF _ a230 determines whether the first condition discrimination is true or false. The SMF _ a230 starts the process (a) in this process when the first condition is determined to be true, and starts the process (B) in this process when the first condition is determined to be false. Note that, the procedure of the case where the first condition is judged to be false will be described later.
Hereinafter, the steps in the case where the first condition is determined to be true, that is, the steps in the process (a) in the present process will be described. The SMF _ a230 selects the UPF _ a235 of the PDU Session Establishment destination (S1505), transmits a Session Establishment request (Session Establishment request) message to the selected UPF _ a235 (S1506), and starts the process (a) in this procedure.
Here, the SMF _ a230 may select one or more UPF _ as 235 according to the respective identification information and/or capability information of the network and/or subscriber information and/or operator policy and/or network status and/or context that the SMF _ a230 has maintained, which are acquired based on the reception of the PDU session setup request message. It should be noted that, in the case that multiple UPF _ as 235 are selected, the SMF _ a230 may send a session establishment request message to each UPF _ a 235.
The UPF _ a235 receives the session establishment request message and formulates a context for the PDU session. Also, the UPF _ a235 transmits a Session Establishment response (Session Establishment response) message to the SMF _ a230 based on receiving the Session Establishment request message and/or formulating a context for the PDU Session (S1508). Further, the SMF _ a230 receives the session establishment response message. It should be noted that the session establishment request message and the session establishment response message may be control messages sent and received over the N4 interface. Also, the session establishment response message may be a response message to the session establishment request message.
Also, the SMF _ a230 may perform address assignment of an address assigned to the UE _ a10 based on the reception of a PDU session setup request message and/or the selection of the UPF _ a235 and/or the reception of a session setup response message. Also, the SMF _ a230 may associate an address assigned to the UE _ a10 with information indicating that the address is an address used in communication with the DN _ a 5. It should be noted that the SMF _ a230 may perform address assignment of an address assigned to the UE _ a10 during the PDU session setup procedure, or after the PDU session setup procedure is completed.
Specifically, the SMF _ a230 may allocate an address in the PDU session establishment process without using the DHCPv4 to allocate an IPv4 address, or may transmit the allocated address to the UE _ a 10. Furthermore, the SMF _ a230 may allocate an Address after the PDU session establishment procedure when allocating an IPv4 Address and/or an IPv6 Address and/or an IPv6prefix using DHCPv4, DHCPv6, or slaac (stateless Address autoconfiguration), or may include the allocated Address in an RA message and send the RA message to the UE _ a 10. Note that the address allocation performed by the SMF _ a230 is not limited to this.
The SMF _ a230 may transmit the allocated address to the UE _ a10 in the fourteenth identification information upon completion of address allocation to the address allocated to the UE _ a10, or may transmit information indicating the allocated address and information indicating whether the allocated address is an address usable for user data communication with the DN _ a5 in association with each other to the UE _ a10 without being included in the fourteenth identification information. In this case, the UE _ a10 may receive the fourteenth identification information and/or information indicating an allocated address and/or information indicating whether the allocated address is an address that can be used in user data communication with the DN _ a5, which is transmitted by the SMF _ a 230.
The SMF _ a230 transmits a PDU session setup accept (PDU session setup accept) message to the UE _ a10 via the AMF _ a240 based on the reception of the PDU session setup request message and/or the selection of the UPF _ a235 and/or the completion of the address assignment of the address assigned to the UE _ a10 (S1510) (S1512).
Note that, in the case where the PDU session establishment request message is included in the Registration request (Registration request) message and transmitted, the PDU session establishment accept message may be included in the Registration accept (Registration accept) message and transmitted. For example, the registration accept message may include a PDU session setup accept message as an SM message, or may include a PDU session setup accept message as an NAS message.
Specifically, the SMF _ a230 transmits a PDU session setup accept message to the AMF _ a240 using the N11 interface (S1510), and the AMF _ a240 having received the PDU session setup request message transmits a PDU session setup accept message to the UE _ a10 using the N1 interface (S1512).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session establishment accept message may be a PDN connection accept (PDN connectivity accept) message. The PDU session establishment accept message may be a NAS message transmitted and received over the N11 interface and the N1 interface, or may be transmitted in a NAS message. Further, the PDU session establishment accept message is not limited thereto, and may be a message indicating that the establishment of the PDU session is accepted.
Here, the SMF _ a230 and/or the AMF _ a240 may include one or more identification information of at least eleventh to fourteenth identification information in the PDU session setup accept message and/or the registration accept message and/or the NAS message, and may indicate that the request of the UE _ a10 is accepted by including the identification information.
Also, the SMF _ a230 may indicate that the network accepts the establishment request of the PDU session connected to DN _ a5 by transmitting more than one of the eleventh to fourteenth identification information, and may also indicate that the network allows the establishment of the PDU session connected to DN _ a 5.
In more detail, the SMF _ a230 and/or the AMF _ a240 may notify the established PDU session and/or the preference information of the route included in the PDU session by transmitting the eleventh identification information and/or by transmitting the eleventh identification information in association with the fourteenth identification information, and may also notify the preference information of the route obtained by the address indicated by the fourteenth identification information.
Also, the SMF _ a230 and/or the AMF _ a240 may inform the established PDU session and/or the SSC pattern of the route included in the PDU session by transmitting the twelfth identification information, and may also indicate that the SSC pattern requested by the UE _ a10 is allowed.
Also, the SMF _ a230 and/or the AMF _ a240 may indicate that the established PDU session is a multi-homed PDU session by transmitting thirteenth identification information, may also indicate that an anchor point may be added or deleted from the established PDU session, and may also indicate that the request of the UE _ a10 is allowed.
Also, the SMF _ a230 and/or the AMF _ a240 may indicate that a PDU session connected to the DN _ a5 is established by transmitting fourteenth identification information, and may also indicate that an address used in user data communication to the DN _ a5 using the established PDU session is an address of a PDU session type indicated by the fourteenth identification information and/or an address indicated by the fourteenth identification information.
It should be noted that the SMF _ a230 and/or the AMF _ a240 may determine which of the eleventh to fourteenth identification information to add to the PDU session establishment accept message and/or the registration accept message and/or the NAS message based on the received identification information and/or the network capability information and/or policies such as operator policy and/or the status of the network. It should be noted that the determination of which identification information to add to the PDU session setup accept message and/or the registration accept message and/or the NAS message by the SMF _ a230 and/or the AMF _ a240 is not limited thereto.
UE _ a10 receives the PDU session setup accept message, and further transmits a PDU session setup complete (PDU session setup complete) message to SMF _ a230 via AMF _ a240 (S1514) (S1516). Further, the SMF _ a230 receives the PDU session setup complete message and performs a second conditional discrimination.
Specifically, the UE _ a10 transmits a PDU session setup complete message to the AMF _ a240 using the N1 interface (S1514), and the AMF _ a240 having received the PDU session setup complete message transmits the PDU session setup complete message to the SMF _ a230 using the N11 interface (S1516).
It should be noted that, when the PDU session is a PDN connection, the PDU session establishment completion message may be a PDN connection completion (PDN Connectivity complete) message, or may be a default EPS bearer context activation accept (active default EPS bearer context accept) message. Also, the PDU session setup complete message may be a NAS message transceived over the N1 interface and the N11 interface. Further, the PDU session setup complete message may be a response message to the PDU session setup accept message, but is not limited thereto, and may also be a message indicating that the PDU session setup procedure is complete.
The second condition discriminates the kind of message on the N4 interface used for determining transceiving. If the second condition is determined to be true, the SMF _ a230 transmits a Session Modification request message (Session Modification request) to the UPF _ a235 (S1518), and receives a Session Modification response message (Session Modification response) transmitted by the UPF _ a235 that received the Session Modification request message (S1520). When the second condition is determined to be false, the SMF _ a230 transmits a session establishment request message to the UPF _ a235 (S1518), and further receives a session change response message transmitted by the UPF _ a235 that received the session establishment request message (S1520). Each device completes the (a) process of the present process based on the transmission and reception of the PDU session setup complete message and/or the transmission and reception of the session change response message and/or the transmission and reception of the session setup response message.
In the process (a) of this procedure, if the address assigned to the UE _ a10 is not notified to the UE _ a10, the SMF _ a230 may transmit an RA via the UPF _ a235 serving as an anchor point (S1524). Here, the RA may include an IPv6prefix corresponding to the PDU session, and a default router address for transmission. Note that the default router address may be the address of the UPF _ a 235. Also, the UE _ a10 that received the RA may generate an IPv6 address using the IPv6 network prefix included in the RA.
Also, the SMF _ a230 and/or the UPF _ a235 may notify that a PDU session has been established for the DN _ a5 by transmitting one or more of the eleventh identification information and the fourteenth identification information to the RA, and may also notify that an address is allocated to the UE _ a 10. Here, the eleventh identification information may indicate information indicating a priority level of a Medium, and may be, for example, information indicating "Medium". Thus, when the PDU session established later and/or the IPv6prefix corresponding to the PDU session have a high priority, the UE _ a10 can transmit user data using the PDU session having a high priority and/or the IPv6prefix corresponding to the PDU session.
It should be noted that the SMF _ a230 may send the eleventh identification information to the UE _ a10 based on the condition. For example, the eleventh identification information may be transmitted to the UE _ a10 in case the first identification information is received and/or in case the second identification information representing the SSC pattern 3 is received and/or in case the third identification information is received.
In addition, when the above condition is not satisfied, the SMF _ a230 may not transmit the eleventh identification information. Alternatively, when the above condition is not satisfied, eleventh identification information indicating default may be transmitted. The information indicating the default may be information indicating "medium". For example, it may be set not to transmit the eleventh identification information in a case where the second identification information indicating the
Further, the SMF _ a230 may select whether to include the eleventh identification information in the RA or the PDU session accept message for transmission. It should be noted that the SMF _ a230 may select the method indicated by the reception method request information based on the reception method request information sent by the UE _ a 10.
Next, each step of the process (B) in this process will be described. The SMF _ a230 transmits a PDU session establishment rejection message (S1526) to the UE _ a10 via the AMF _ a240 (S1528), and starts the (B) process in this procedure.
Specifically, the SMF _ a230 transmits a PDU session setup reject message to the AMF _ a240 using the N11 interface (S1526), and the AMF _ a240 having received the PDU session setup request message transmits a PDU session setup reject message to the UE _ a10 using the N1 interface (S1528).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session establishment reject message may be a PDN connection reject (PDN connectivity reject) message. The PDU session establishment reject message may be a NAS message transmitted and received over the N11 interface and the N1 interface, or may be transmitted in a NAS message. The PDU session establishment reject message is not limited to this, and may be a message indicating that the establishment of the PDU session is rejected.
Here, the SMF _ a230 and/or the AMF _ a240 may include at least fifteenth identification information in the PDU session setup reject message and/or the NAS message, or may include these identification information to indicate that the request of the UE _ a10 is rejected.
Also, the SMF _ a230 and/or the AMF _ a240 may indicate that the network has rejected the request for the setup of the PDU session connected to DN _ a5 by transmitting fifteenth identification information, and may also indicate that the setup of the PDU session connected to DN _ a5 is not allowed. Also, the SMF _ a230 may indicate that a PDU session connected to the DN _ a5 is not established by transmitting fifteenth identification information.
For example, SMF _ a230 and/or AMF _ a240 may indicate that a connection with DN _ a5 is rejected by sending fifteenth identification information, may indicate a reason for rejection, may indicate that a request for UE _ a10 is rejected, may indicate that a connection supporting the requested SSC mode cannot be established, or may indicate that establishment of a multi home PDU session is not supported.
Each device completes the procedure based on completion of the procedure (a) or (B) in this procedure or transmission/reception of S1524. It should be noted that each device may transition to a state in which a PDU session is established based on completion of the procedure (a) in this procedure, may know that this procedure is rejected based on completion of the procedure (B) in this procedure, and may also transition to a state in which a PDU session is not established.
Each device may perform processing based on the identification information transmitted and received in the present procedure, based on the completion of the present procedure.
For example, in case of receiving more than one of the eleventh to thirteenth identification information, the UE _ a10 may perform a procedure of adding or deleting an anchor point to the established PDU session. Specifically, based on the reception of the eleventh identification information, the UE _ a10 may compare with preference information of other routes included in the PDU session, and start a deletion process of an anchor point. Alternatively, the anchor point addition process may be started based on the reception of the eleventh identification information. Alternatively, the UE _ a10 may start and/or perform a process of adding or deleting an anchor to the PDU session based on the SSC pattern shown by the twelfth identification information being SSC pattern 2 or SSC pattern 3 and further based on the reception of the thirteenth identification information.
Also, the UE _ a10 may store the preference information indicated by the eleventh identification information in the storage section, upon receiving the eleventh identification information. In this case, in the case where preference information has already been stored for another route, the preference information indicated by the eleventh identification information may be additionally stored, and in the case where preference information for the same route is stored, the preference information may be updated to the information indicated by the eleventh identification information.
Also, the UE _ a10, upon receiving the twelfth identification information, may control the execution of the relocation of the anchor point based on the SSC pattern indicated by the twelfth identification information. Specifically, in the case where the SSC pattern indicated by the twelfth identification information is
Also, the SMF _ a230 and/or the AMF _ a240 may perform a process of adding or deleting an anchor point to the established PDU session in case of receiving more than one of the first to third identification information. Specifically, in the case where the first identification information is information requesting notification of preference information and/or in the case where the SSC pattern shown by the second identification information is SSC pattern 2 or SSC pattern 3 and/or the third identification information is a request to establish a multi home PDU session, the SMF _ a230 and/or AMF _ a240 may perform a process of adding or deleting an anchor point to the PDU session.
Further, the AMF _ a240 and/or the SMF _ a230 may transition the state in which the UE _ a10 is established to the state in which the PDU session is not established or to the abnormal state based on the transmission of the PDU session establishment reject message and/or the transmission of each piece of identification information included in the PDU session establishment reject message. Note that the state in which the state corresponding to the UE _ a10 is established transitions upon completion of the present procedure is not limited to this.
Further, the first condition discrimination may be performed based on identification information included in the PDU session setup request message and/or the registration request message and/or the NAS message and/or subscriber information and/or operator policy obtained from the UDM _ a 50. For example, the first conditional discrimination may be true if the network allows the request of the UE _ a 10. Further, the first conditional discrimination may be false in the case where the network does not allow the request of the UE _ a 10. The first condition discriminates that the UE _ a10 may be true if the network and/or the device in the network to which the UE _ a10 is connected supports the requested function, and may be false if the UE _ a10 does not support the requested function. The condition for determining whether the first condition is true or false may not be limited to the above condition. Further, the second conditional discrimination may be performed based on whether a session on the N4 interface for the PDU session is established. For example, the second condition discriminates that it may be true in case a session on the N4 interface for a PDU session is established and false in case it is not established. The condition for determining whether the second condition is true or false may not be limited to the above condition.
[1.4. overview of PDU Session Anchor relocation procedure ]
In this chapter, an outline of the PDU session anchor relocation procedure is explained.
[1.4.1. description of first PDU Session Anchor relocation procedure ]
First, the first PDU session anchor relocation will be described with reference to fig. 16. In the present embodiment, each device starts from the state of transition to the first state (S1600). Hereinafter, the present process refers to a first PDU session anchor relocation process, and there are a first PDU session release process and a first PDU session establishment process in each process. The details of each process will be described later.
Here, PDU session anchor relocation refers to a procedure for changing an anchor point of an established session.
Note that, in the case of performing the first PDU session anchor relocation, the UPF _ a235 may be in a state where a PDU session is established in correspondence with the SSC pattern 2 establishment. In other words, in the initial process for transitioning to the first state, each device may be in a state where the PDU session is established with the SSC pattern 2 being associated with the UPF _ a235, and each device may also be in a state where the SSC pattern 2 is stored with the UPF _ a235 being associated. Specifically, the twelfth identification information may be received from the network by the UE _ a10 in the initial procedure, and the twelfth identification information may be information indicating the SSC pattern 2.
In this process, each device first executes a first PDU session release procedure (S1602) to transition to a second state (S1604). Next, each device executes the first PDU session setup procedure (S1606) to transition to the third state (S1608).
It should be noted that the devices may exchange capability information and/or master request information of the devices in the first PDU session release procedure and/or the first PDU session establishment procedure.
Each apparatus completes the process through the above process. Each device related to this process can transmit and receive one or more pieces of identification information included in each control message by transmitting and receiving each control message described in this process, and store each piece of identification information transmitted and received as a context. Also, each device may transition to the third state based on completing the process.
[1.4.1.1 example first PDU Session Release procedure ]
First, an outline of a first PDU session release procedure (PDU session release procedure) will be described. Hereinafter, the present procedure refers to a first PDU session release procedure. This procedure is a procedure for each device to release a PDU session to perform PDU session anchor relocation for a PDU session using an anchor (UPF _ a235) corresponding to SSC pattern 2. It should be noted that one or more routes may be included in a PDU session. In other words, one or more anchor points may be assigned to a PDU session.
Further, each device may start the PDU session release procedure at an arbitrary timing after transitioning to the first state.
Hereinafter, an example of the order of performing the first PDU session setup procedure will be described using fig. 17. Hereinafter, each step of the present process will be described. First, the SMF _ a230 determines to start performing anchor (UPF) relocation (S1702). The SMF _ a230 may also determine that anchor relocation is required.
The SMF _ a230 may determine relocation of the anchor based on the UPF _ a235 being in an overflow state and/or based on the UE _ a10 moving and/or based on changes in network policy and/or based on requests from other NFs. It should be noted that the primary factor in determining the relocation of the anchor is not limited thereto.
The SMF _ a230 then sends a Session release request message (S1704) to the relocated source UPF _ a235 to begin the release process of the Session between the SMF _ a230 and the UPF _ a 235. Here, the SMF _ a230 may select one or more UPFs based on a determination of a UPF relocation and/or based on a context that the SMF _ a230 has maintained. It should be noted that, in the case that a plurality of UPF _ as 235 are selected, the SMF _ a230 may send a session release request message to each UPF _ a 235.
The UPF _ a235 receives the session release request message and deletes the context for the PDU session. Also, the UPF _ a235 transmits a Session release response (Session release response) message to the SMF _ a230 based on receiving the Session release request message and/or deleting the context for the PDU Session. Also, the SMF _ a230 receives the session release response message. It should be noted that the session release request message and the session release response message may be control messages sent and received over the N4 interface. Also, the session release response message may be a response message to the session release request message.
Next, the SMF _ a230 transmits a PDU session release command message to the UE _ a10 via the AMF _ a240 based on the reception of the PDU session release response message and/or the determination of the PDU session anchor relocation (S1708).
Specifically, the SMF _ a230 transmits a PDU session release command message to the AMF _ a240 (S1708), and the AMF _ a240 having received the PDU session release command message transmits the PDU session release command message to the UE _ a10 (S1710).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session release command message may be an EPS bearer disable request (deactivating EPS bearer context request) message. The PDU session release command message may be a NAS message transmitted and received over the N11 interface and the N1 interface, or may be transmitted in a NAS message. The PDU session release command message is not limited to this, and may be any message that indicates that the network requests the release of the PDU session and/or that the network determines the release of the PDU session.
Here, the SMF _ a230 and/or the AMF _ a240 may include at least one or more identification information of twenty-first to twenty-second identification information in the PDU session release command message and/or the NAS message, or may indicate a request for release of the PDU session by including the identification information.
Also, the SMF _ a230 and/or the AMF _ a240 may indicate that the network accepts the request for the establishment of the PDU session connected to DN _ a5 by transmitting one or more of the twenty-first to twenty-second identification information, and may also indicate that the network allows the establishment of the PDU session connected to DN _ a 5.
In more detail, the SMF _ a230 and/or the AMF _ a240 may indicate to maintain information about the PDU session released a certain period of time after the PDU session is released by transmitting the twenty-first identification information. Specifically, the SMF _ a230 may store information related to the UPF _ a235 in which the PDU session is associated with the twenty-first identification information, and the AMF _ a240 may store information identifying the SMF _ a230, for example, an SMF ID, in association with the twenty-first identification information.
Also, by transmitting the twenty-second identification information, the SMF _ a230 and/or the AMF _ a240 may indicate that the release of the PDU session is performed for PDU session anchor relocation.
It should be noted that the SMF _ a230 and/or the AMF _ a240 may determine which identification information of the twenty-first to twenty-second identification information to add to the PDU session release command message and/or the NAS message based on the received identification information and/or the capability information of the network and/or the policy such as the operator policy and/or the status of the network. It should be noted that the determination of which identification information to add to the PDU session release command message and/or the NAS message by the SMF _ a230 and/or the AMF _ a240 is not limited thereto.
UE _ a10 receives the PDU session release command message, and further sends a PDU session release accept message to SMF _ a230 via AMF _ a240 (S1712) (S1714).
Specifically, the UE _ a10 transmits a PDU session release accept message to the AMF _ a240 using the N1 interface (S1712), and the AMF _ a240 having received the PDU session release accept message transmits a PDU session release accept message to the SMF _ a230 using the N11 interface (S1714).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session release accept message may be an EPS bearer context disable accept (deactivating EPS bearer context accept) message.
The PDU session release accept message may be a NAS message transmitted and received over the N1 interface and the N11 interface, or may be transmitted and received by including the NAS message. The PDU session release accept message is not limited to this as long as it is a response message to the PDU session release command message, and it is only required to be a message indicating that the PDU session release process is completed.
Next, the SMF _ a230 transmits a PDU session release notification (PDU session release) message to the AMF _ a240 (S1716). The SMF _ a230 may notify completion of the release of the PDU session by transmitting a PDU session release notification message, or may notify that the PDU session is released but in a state of maintaining information of storing a part for relocation. The PDU session release notification message is not limited to this, and may be any message that notifies the release of the PDU session.
It should be noted that the AMF _ a240 may start the timing of the timer using the timer managing the storage of the information on the PDU session based on the reception of the PDU session release accept message and/or the reception of the PDU session release notify message and/or the transmission of the PDU session release command message. Also, the AMF _ a240 may start storing the twenty-first identification information in association with information on the PDU session, for example, an SMF ID identifying the SMF _ 230.
Alternatively, the AMF _ A240 may begin storing the above information based on more detailed conditions. For example, in case of receiving a PDU session release notification message including twenty-first identification information and/or twenty-second identification information and/or in case of releasing the PDU session of the SSC mode 2, the above information may be stored based on the reception of the PDU session release accept message and/or the reception of the PDU session release notification message and/or the transmission of the PDU session release command message. It should be noted that such detailed conditions may be determined by the system, the policy of the operator, and the like. If such a condition is not met, AMF _ a240 may not start storing the information and counting the timer. In addition, the timer managing the storage of the information on the PDU session may be stored by the AMF _ a240 through pre-configuration, or may be determined based on the received identification information and/or policies such as capability information of the network and/or operator policies and/or states of the network.
Also, the AMF _ a240 may release the information and/or context on the PDU session in case of expiration of a timer (expire) using a timer managing storage of information on the PDU session.
The SMF _ a230 may start timing of a timer using a timer managing storage of information on the PDU session based on reception of the PDU session release accept message and/or transmission of the PDU session release notify message and/or reception of the PDU session release command message. Also, the SMF _ a230 may start to store the twenty-first identification information in association with information on the PDU session.
Alternatively, the SMF _ a230 may start storing the above information based on a more detailed condition. For example, in the case of receiving a PDU session release accept message including the twenty-first identification information and/or the twenty-second identification information and/or in the case of transmitting a PDU session release notification message including the twenty-first identification information and/or the twenty-second identification information and/or in the case of releasing the PDU session of the SSC mode 2, it is possible to start the counting of the above-mentioned timer and to store the twenty-first identification information in association with information on the PDU session based on the reception of the PDU session release accept message and/or on the transmission of the PDU session release notification message and/or on the reception of the PDU session release command message.
It should be noted that such detailed conditions may be determined by the system, the policy of the operator, and the like. If such a condition is not met, the SMF _ a230 may not start storing the information and counting the timer. Here, the information on the PDU session may refer to a UPF ID of the UPF _ a235 identifying the relocation source, in which case the SMF _ a230 selects the UFP _ B236 of the relocation destination in the first PDU session setup procedure.
Alternatively, the information about the PDU session may be a UPF ID of the UPF _ B236 identifying the relocation destination, in which case the SMF _ a230 may select the UPF _ B236 of the relocation destination based on the receipt of the PDU session release response message and/or the determination of the PDU session anchor relocation.
Here, the timer managing the storage of the information on the PDU session may be stored by the SMF _ a230 through pre-configuration, or may be determined based on a policy such as the received identification information and/or capability information of the network and/or operator policy and/or the state of the network.
Also, the SMF _ a230 may release the information and/or context on the PDU session in case of expiration of a timer (expire) using a timer managing storage of the information on the PDU session.
Each device completes the process based on the transmission and reception in S1716. It should be noted that each device may transition to a state in which the first PDU session is released upon completion of the present procedure. Each device may perform processing based on the identification information transmitted and received in the present procedure, based on the completion of the present procedure.
For example, in the case where the UE _ a10 receives more than one of the twenty-first to twenty-second identification information, the first PDU session setup procedure may be started immediately.
When the UE _ a10 receives one or more pieces of identification information out of the twenty-first to twenty-second identification information, the information on the PDU session may not be released temporarily, or may be released immediately.
In this process example, the process of releasing the PDU session by the SMF _ a230 is described based on fig. 17, but the process is not limited to this and may be another process. For example, the SMF _ a230 transmits a NAS message including the twenty-first identification information and/or the twenty-second identification information to the UE _ a10 via the AMF _ a240 after performing the process of determining the UPF relocation in S1702. The NAS message may be a control message including the released PDU session ID, or may be control information indicating a request to the UE _ a10 to start the UE-initiated PDU session release procedure or a notification of the start of the UE-initiated PDU session release procedure.
Upon receipt of the NAS message described above, the UE _ a10 may send a PDU session release request message to the AMF _ a 240. Also, the AMF _ a240 may transmit the received PDU session release request message to the SMF _ a 230. Here, the UE _ a10 may include the PDU session ID and/or the twenty-first identification information received based on the above-described NAS message in the PDU session release request message. Note that the procedure after the SMF _ a230 receives the PDU session release request message may be the procedure after S1704 described with reference to fig. 17.
[1.4.1.2 description of first PDU Session setup procedure ]
Hereinafter, the present procedure refers to a first PDU session setup procedure. This procedure is a procedure for each device in the second state to establish the second PDU session. It should be noted that, each device may perform the first PDU session setup procedure in a state that the first PDU session release procedure is completed. Further, each device may start the first PDU session setup procedure in the registered state. Further, the apparatuses may establish the second PDU session based on completion of the present procedure.
The first PDU session establishment procedure will be described with reference to fig. 15. Hereinafter, each step of the present process will be described. First, the UE _ a10 transmits a PDU session setup request message to the SMF _ a230 via the AN node _ a122 and the AMF _ a240 (S1500) (S1502) (S1504), starting a PDU session setup procedure.
Specifically, the UE _ a10 transmits a PDU session setup request message to the AMF _ a240 using the N1 interface (S1500), the AMF _ a240 having received the PDU session setup request message selects the SMF _ a230 as the NF of the routing destination of the PDU session setup request message (S1502), and transmits the PDU session setup request message to the selected SMF _ a230 using the N11 interface (S1504).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session establishment request message may be a PDN connection request message. The PDU session establishment request message may be a NAS message transmitted and received over the N1 interface and the N11 interface, or may be included in a NAS message. Further, the PDU session setup request message is not limited thereto as long as it is a message that re-locates the setup of the PDU session requested from the network through the PDU session anchor.
Here, the UE _ a10 may include at least one or more pieces of identification information of the first to seventh identification information, one or more pieces of identification information of the thirty-first to thirty-third identification information in the PDU session establishment request message and/or the NAS message, or may indicate the request of the UE _ a10 by including these pieces of identification information.
Also, the UE _ a10 may request establishment of a PDU session connected with the DN _ a5 by transmitting one or more identification information of thirty-first to thirty-third identification information.
Specifically, the UE _ a10 may indicate a request to establish a PDU session based on a request from the network by transmitting the thirty-first identification information, and may also indicate a request to establish a PDU session by PDU session anchor relocation.
Also, the UE _ a10 may indicate a PDU session requested to be established by the UE _ a10 by transmitting thirty-second identification information, and may also indicate information on the PDU session temporarily stored by the network.
Also, the UE _ a10 may instruct the PDU session anchor to relocate the PDU session of the source by sending a thirty-third identification information.
It should be noted that the UE _ a10 may determine which of the thirty-first to thirty-third identification information to add to the PDU session setup request message and/or the NAS message based on the capability information of the UE _ a10 and/or the policy such as the UE policy and/or the preference of the UE _ a 10. It should be noted that the determination of which identification information to add to the PDU session setup request message and/or the NAS message by the UE _ a10 is not limited thereto.
It should be noted that, when the timer for managing storage of information on the PDU session started in the first PDU session release procedure is in execution, the AMF _ a240 and/or the SMF _ a230 may stop the timer for managing storage of information on the PDU session.
It should be noted that the AMF _ a240 may select the SMF _ a230 that transmits the PDU session setup request message based on information included in the PDU session setup request message. In more detail, the AMF _ a240 may select the SMF _ a230 of the routing destination according to various identification information acquired based on the reception of the PDU session setup request message, for example, thirty-one identification information and/or subscriber information and/or capability information of the network and/or operator policy and/or network status and/or context that the AMF _ a240 has maintained.
More specifically, the AMF _ a240 may select the SMF _ a230 from information stored when the PDU session is released based on one or more of thirty-first to thirty-third identification information. More specifically, the SMF _ a230 may be selected by determining a PDU session ID to be released in advance based on one or more pieces of identification information among the thirty-first to thirty-third pieces of identification information, and determining an SMF ID from stored information corresponding to the determined PDU session ID.
It should be noted that, in the case where the timer for managing storage of information on the PDU session started in the first PDU session release procedure is in execution, the AMF _ a240 may execute deletion of information on the PDU session and stop of the timer for managing storage of information on the PDU session based on reception of the PDU session establishment request message and/or transmission of any one or more PDU session establishment accept messages described later and/or transmission of PDU session establishment complete messages described later and/or completion of selection of the SMF _ a230 described above and/or transmission of PDU session establishment request described later, which include the thirty-first to thirty-third identification information in the PDU session establishment request message and/or transmission of PDU session establishment complete messages described later.
The SMF _ a230 receives the PDU session setup request message and performs a first conditional discrimination. The first condition is determined to determine whether the SMF _ a230 accepts the request of UE _ a 10. In the first condition discrimination, the SMF _ a230 determines whether the first condition discrimination is true or false. The SMF _ a230 starts the process (a) in this process when the first condition is determined to be true, and starts the process (B) in this process when the first condition is determined to be false. Note that, the procedure of the case where the first condition is judged to be false will be described later.
Hereinafter, the steps in the case where the first condition is determined to be true, that is, the steps in the process (a) in the present process will be described. The SMF _ a230 selects the UPF _ B236 of the PDU Session Establishment destination (S1505), and transmits a Session Establishment request (Session Establishment request) message to the selected UPF _ B236 (S1506), starting the procedure of (a) in this procedure.
Here, the SMF _ a230 may select one or more UPFs according to respective identification information acquired based on the reception of the PDU session setup request message, for example, thirty-one identification information and/or capability information of the network and/or subscriber information and/or operator policy and/or network status and/or context that the SMF _ a230 has maintained. It should be noted that, in the case that multiple UPFs are selected, the SMF _ a230 may send a session establishment request message to each UPF.
Hereinafter, a case where the SMF _ a230 selects the UPF _ B236 by the UPF selection process will be described. Note that, in the case where another UPF is selected, the PDU session can be established by performing a procedure to replace the UPF _ B236 with the selected UPF, which will be described later.
It should be noted that as a specific method for the SMF _ a230 to select the UPF _ B236 through the UPF selection process, the SMF _ a230 may select the UPF _ B236 from information stored when the PDU session is released based on one or more identification information of the thirty-first to thirty-third identification information. More specifically, the PDU session ID released in advance may be determined based on one or more pieces of identification information among the thirty-first to thirty-third pieces of identification information, and the UPF _ B236 may be selected by determining the UPF of the relocation destination from the stored information corresponding to the determined PDU session ID.
It should be noted that, in the case where the timer for managing storage of information on a PDU session started in the first PDU session release procedure is in execution, the SMF _ a230 may execute deletion of information on a PDU session including information on a relocation destination and stop of the timer for managing storage of information based on reception of a PDU session establishment request message and/or transmission of a PDU session establishment accept message described later and/or reception of a PDU session establishment complete message described later and/or completion of selection of the above-mentioned UPF _ B236 and/or transmission of a session establishment request described later, and/or more than one of thirty-first to thirty-third identification information included in the PDU session establishment request message and/or transmission of a PDU session establishment accept message described later.
The UPF _ B236 receives the session establishment request message and formulates a context for the PDU session. Also, the UPF _ B236 transmits a Session Establishment response (Session Establishment response) message to the SMF _ a230 based on receiving the Session Establishment request message and/or formulating a context for the PDU Session (S1508). Further, the SMF _ a230 receives the session establishment response message. It should be noted that the session establishment request message and the session establishment response message may be control messages sent and received over the N4 interface. Also, the session establishment response message may be a response message to the session establishment request message.
Also, the SMF _ a230 may perform address assignment of an address assigned to the UE _ a10 based on the reception of a PDU session setup request message and/or the selection of the UPF _ B236 and/or the reception of a session setup response message. Also, the SMF _ a230 may associate an address assigned to the UE _ a10 with information indicating that the address is an address used in communication with the DN _ a 5. It should be noted that the SMF _ a230 may perform address assignment of an address assigned to the UE _ a10 during the PDU session setup procedure, or after the PDU session setup procedure is completed.
Specifically, the SMF _ a230 may allocate an address in the PDU session establishment process without using the DHCPv4 to allocate an IPv4 address, or may transmit the allocated address to the UE _ a 10. Furthermore, the SMF _ a230 may allocate an Address after the PDU session establishment process when allocating an IPv4 Address and/or an IPv6 Address and/or an IPv6prefix using DHCPv4, DHCPv6, or slaac (stateless Address autoconfiguration), or may send the allocated Address to the UE _ a10 using RA. Note that the address allocation performed by the SMF _ a230 is not limited to this.
The SMF _ a230 may transmit the allocated address to the UE _ a10 in the fourteenth identification information upon completion of address allocation to the address allocated to the UE _ a10, or may transmit information indicating the allocated address and information indicating whether the allocated address is an address usable for user data communication with the DN _ a5 in association with each other to the UE _ a10 without being included in the fourteenth identification information. In this case, the UE _ a10 may receive the fourteenth identification information and/or information indicating an allocated address and/or information indicating whether the allocated address is an address that can be used in user data communication with the DN _ a5, which is transmitted by the SMF _ a 230.
The SMF _ a230 transmits a PDU session setup accept (PDU session setup accept) message to the UE _ a10 via the AMF _ a240 based on the reception of the PDU session setup request message and/or the selection of the UPF _ B236 and/or the reception of the session setup response message and/or the completion of the address assignment of the address assigned to the UE _ a10 (S1610) (S1612).
Note that, in the case where the PDU session establishment request message is included in the Registration request (Registration request) message and transmitted, the PDU session establishment accept message may be included in the Registration accept (Registration accept) message and transmitted. For example, the registration accept message may include a PDU session setup accept message as an SM message, or may include a PDU session setup accept message as an NAS message.
Specifically, the SMF _ a230 transmits a PDU session setup accept message to the AMF _ a240 using the N11 interface (S1510), and the AMF _ a240 having received the PDU session setup request message transmits a PDU session setup accept message to the UE _ a10 using the N1 interface (S1512).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session establishment accept message may be a PDN connection accept (PDN connectivity accept) message. The PDU session establishment accept message may be a NAS message transmitted and received over the N11 interface and the N1 interface, or may be transmitted in a NAS message. Further, the PDU session establishment accept message is not limited thereto, and may be a message indicating that the establishment of the PDU session is accepted.
Here, the SMF _ a230 and/or the AMF _ a240 may include one or more identification information of at least eleventh to fourteenth identification information in the PDU session setup accept message and/or the registration accept message and/or the NAS message, and may indicate that the request of the UE _ a10 is accepted by including the identification information.
Also, the SMF _ a230 may indicate that the network accepts the establishment request of the PDU session connected to DN _ a5 by transmitting more than one of the eleventh to fourteenth identification information, and may also indicate that the network allows the establishment of the PDU session connected to DN _ a 5.
It should be noted that the SMF _ a230 and/or the AMF _ a240 may determine which of the eleventh to fourteenth identification information to add to the PDU session establishment accept message and/or the registration accept message and/or the NAS message based on the received identification information and/or the network capability information and/or policies such as operator policy and/or the status of the network. It should be noted that the determination of which identification information to add to the PDU session setup accept message and/or the registration accept message and/or the NAS message by the SMF _ a230 and/or the AMF _ a240 is not limited thereto.
UE _ a10 receives the PDU session setup accept message, and further transmits a PDU session setup complete (PDU session setup complete) message to SMF _ a230 via AMF _ a240 (S1514) (S1516). Further, the SMF _ a230 receives the PDU session setup complete message and performs a second conditional discrimination.
Specifically, the UE _ a10 transmits a PDU session setup complete message to the AMF _ a240 using the N1 interface (S1514), and the AMF _ a240 having received the PDU session setup complete message transmits the PDU session setup complete message to the SMF _ a230 using the N11 interface (S1516).
It should be noted that, when the PDU session is a PDN connection, the PDU session establishment completion message may be a PDN connection completion (PDN Connectivity complete) message, or may be a default EPS bearer context activation accept (active default EPS bearer context accept) message. Also, the PDU session setup complete message may be a NAS message transceived over the N1 interface and the N11 interface. Further, the PDU session setup complete message may be a response message to the PDU session setup accept message, but is not limited thereto, and may also be a message indicating that the PDU session setup procedure is complete.
The second condition discriminates the kind of message on the N4 interface used for determining transceiving. If the second condition is determined to be true, the SMF _ a230 transmits a Session modification request message (Session modification request) to the UPF _ B236 (S1518), and receives a Session modification response message (Session modification response) transmitted by the UPF _ B236 that received the Session modification request message (S1520). When the second condition is determined to be false, the SMF _ a230 transmits a session establishment request message to the UPF _ B236 (S1518), and further receives a session change response message transmitted by the UPF _ B236 that received the session establishment request message (S1520). Each device completes the (a) process of the present process based on the transmission and reception of the PDU session setup complete message and/or the transmission and reception of the session change response message and/or the transmission and reception of the session setup response message.
In the process (a) of this procedure, if the address assigned to the UE _ a10 is not notified to the UE _ a10, the SMF _ a230 may transmit an RA via the UPF _ B236 that becomes an anchor point (S1524).
The SMF _ a230 and/or UPF _ B236 may notify that a PDU session has been established for the DN _ a5 by transmitting one or more of the eleventh identification information and the fourteenth identification information to the RA, and may also notify that an address has been allocated to the UE _ a 10.
Next, each step of the process (B) in this process will be described. The SMF _ a230 transmits a PDU session establishment rejection message (S1526) to the UE _ a10 via the AMF _ a240 (S1528), and starts the (B) process in this procedure.
Specifically, the SMF _ a230 transmits a PDU session setup reject message to the AMF _ a240 using the N11 interface (S1526), and the AMF _ a240 having received the PDU session setup request message transmits a PDU session setup reject message to the UE _ a10 using the N1 interface (S1528).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session establishment reject message may be a PDN connection reject (PDN connectivity reject) message. The PDU session establishment reject message may be a NAS message transmitted and received over the N11 interface and the N1 interface, or may be transmitted in a NAS message. The PDU session establishment reject message is not limited to this, and may be a message indicating that the establishment of the PDU session is rejected.
Here, the SMF _ a230 and/or the AMF _ a240 may include at least fifteenth identification information in the PDU session setup reject message and/or the NAS message, or may include these identification information to indicate that the request of the UE _ a10 is rejected.
Also, the SMF _ a230 and/or the AMF _ a240 may indicate that the network has rejected the request for the setup of the PDU session connected to DN _ a5 by transmitting fifteenth identification information, and may also indicate that the setup of the PDU session connected to DN _ a5 is not allowed. Also, the SMF _ a230 may indicate that a PDU session connected to the DN _ a5 is not established by transmitting fifteenth identification information.
For example, SMF _ a230 and/or AMF _ a240 may indicate that a connection with DN _ a5 is rejected by sending fifteenth identification information, may indicate a reason for rejection, may indicate that a request for UE _ a10 is rejected, may indicate that a connection supporting the requested SSC mode cannot be established, or may indicate that establishment of a multi home PDU session is not supported.
Each device completes the procedure based on completion of the procedure (a) or (B) in this procedure or transmission/reception of S1524. It should be noted that each device may transition to a state in which a PDU session is established based on completion of the procedure (a) in this procedure, may know that this procedure is rejected based on completion of the procedure (B) in this procedure, and may also transition to a state in which a PDU session is not established.
Each device may perform processing based on the identification information transmitted and received in the present procedure, based on the completion of the present procedure.
Further, the first condition discrimination may be performed based on identification information included in the PDU session setup request message and/or the registration request message and/or the NAS message and/or subscriber information and/or operator policy obtained from the UDM _ a 50. For example, the first conditional discrimination may be true if the network allows the request of the UE _ a 10. Further, the first conditional discrimination may be false in the case where the network does not allow the request of the UE _ a 10. The first condition discriminates that the UE _ a10 may be true if the network and/or the device in the network to which the UE _ a10 is connected supports the requested function, and may be false if the UE _ a10 does not support the requested function. The condition for determining whether the first condition is true or false may not be limited to the above condition. Further, the second conditional discrimination may be performed based on whether a session on the N4 interface for the PDU session is established. For example, the second condition discriminates that it may be true in case a session on the N4 interface for a PDU session is established and false in case it is not established. The condition for determining whether the second condition is true or false may not be limited to the above condition.
[1.4.2. description of second PDU Session Anchor relocation procedure ]
Next, the second PDU session anchor relocation will be described with reference to fig. 18. In the present embodiment, each device starts from the state of transition to the first state (S1800), similarly to the first PDU session anchor relocation procedure described in chapter 1.4.1. Hereinafter, the present process refers to a second PDU session anchor relocation process, and there are a second PDU session release process and a second PDU session establishment process in each process. The details of each process will be described later.
Here, PDU session anchor relocation refers to a procedure for changing an anchor point of an established session.
Note that, in the case of performing the second PDU session anchor relocation, the UPF _ a235 may be in a state where a PDU session is established in correspondence with the SSC pattern 3 establishment. In other words, in the initial process for transitioning to the first state, each device may be in a state where the PDU session is established with the SSC pattern 3 being associated with the UPF _ a235, and each device may also be in a state where the SSC pattern 3 is stored with the UPF _ a235 being associated. Specifically, the twelfth identification information may be received from the network by the UE _ a10 in the initial procedure, and the twelfth identification information may be information indicating the SSC pattern 3.
In this process, each device first executes a second PDU session establishment procedure (S1802), and transitions to a fourth state (S1804). Next, each device executes a second PDU session release procedure (S1806), and transitions to a third state (S1808).
It should be noted that the devices may exchange various capability information and/or various request information of the devices in the second PDU session release procedure and/or the first PDU session establishment procedure.
Each apparatus completes the process through the above process. Each device related to this process can transmit and receive one or more pieces of identification information included in each control message by transmitting and receiving each control message described in this process, and store each piece of identification information transmitted and received as a context. Also, each device may transition to the third state based on completing the process.
[1.4.2.1. description of second PDU Session setup procedure ]
Hereinafter, the present procedure refers to a second PDU session setup procedure. This procedure is a procedure for each device in the first state to establish a second PDU session. It should be noted that, unlike the first PDU session anchor relocation procedure described in chapter 1.4.1, each device may start the second PDU session setup procedure without performing the PDU session release procedure. Further, the devices may begin a second PDU session establishment procedure in the registered state.
It should be noted that the UE _ a10 may start the second PDU session establishment procedure at an arbitrary timing. Alternatively, the second PDU session setup procedure may be started by a change in TA or area within the mobile service range accompanying the UE _ a10, a detection of entry into a TA or area in which the second PDU session setup procedure can be performed, a reception of a notification from the core network indicating that the second PDU session setup procedure can be performed, or the like.
More specifically, in the first state, a PDU session is established between UE _ a10 and UFP _ a235, the established PDU session being managed by SMF _ a 230. In this state, the SMF _ a230 may determine the relocation of the UPF. The specific process in the determination may be the same as the UPF relocation process described in S1702 in chapter 1.4.1.1. The SMF _ a230 may send a NAS message to the UE _ a10 via the AMF _ a240 after determining the relocation.
The SMF _ a230 may inform that the PDU session is released after a certain time elapses through the NAS message. Also, the UE-initiated PDU session setup procedure may be requested to be started for UE _ a 10. Here, the SMF _ a230 may include information indicating a time until the PDU session is released in the NAS message. Also, identification information of the released PDU session may be included. It should be noted that the DN for the PDU session requested to be established to UE _ a10 may be the same as the DN to which the released PDU session is connected. That is, the establishment of a PDU session may also be requested for the DN to which the released PDU session is connected. Accordingly, the SMF _ a230 may transmit including a DNN identifying the DN requesting the connection in a NAS message.
In this way, UE _ a10 may begin the UE-initiated PDU session establishment procedure by receiving the NAS message sent by SMF _ a 230.
It should be noted that the SMF _ a230 may determine to change the anchor device to the UPF _ B236 in the process of determining the relocation of the UPF, and store the identification information of the UPF _ B236 in association with the identification information of the PDU session.
Hereinafter, as the UE-dominated PDU session establishment procedure, the second PDU session establishment procedure will be described with reference to fig. 15. Hereinafter, each step of the present process will be described. First, the UE _ a10 transmits a PDU session setup request message to the SMF _ a230 via the AN node _ a122 and the AMF _ a240 (S1500) (S1502) (S1504), starting a PDU session setup procedure.
Specifically, the UE _ a10 transmits a PDU session setup request message to the AMF _ a240 using the N1 interface (S1500), the AMF _ a240 having received the PDU session setup request message selects the SMF _ a230 as the NF of the routing destination of the PDU session setup request message (S1502), and transmits the PDU session setup request message to the selected SMF _ a230 using the N11 interface (S1504).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session establishment request message may be a PDN connection request message. The PDU session establishment request message may be a NAS message transmitted and received over the N1 interface and the N11 interface, or may be included in a NAS message. Further, the PDU session setup request message is not limited thereto as long as it is a message that re-locates the setup of the PDU session requested from the network through the PDU session anchor.
Here, the UE _ a10 may include at least one or more pieces of identification information of the first to seventh identification information, one or more pieces of identification information of the thirty-first to thirty-third identification information in the PDU session establishment request message and/or the NAS message, or may indicate the request of the UE _ a10 by including these pieces of identification information.
Also, the UE _ a10 may request establishment of a PDU session connected with the DN _ a5 by transmitting one or more identification information of thirty-first to thirty-third identification information.
Specifically, the UE _ a10 may indicate a request to establish a PDU session based on a request from the network by transmitting the thirty-first identification information, and may also indicate a request to establish a PDU session by PDU session anchor relocation.
Also, the UE _ a10 may indicate a PDU session requested to be established by the UE _ a10 by transmitting thirty-second identification information, and may also indicate information on the PDU session temporarily stored by the network.
Also, the UE _ a10 may instruct the PDU session anchor to relocate the PDU session of the source by sending a thirty-third identification information.
It should be noted that the UE _ a10 may determine which of the thirty-first to thirty-third identification information to add to the PDU session setup request message and/or the NAS message based on the capability information of the UE _ a10 and/or the policy such as the UE policy and/or the preference of the UE _ a 10. It should be noted that the determination of which identification information to add to the PDU session setup request message and/or the NAS message by the UE _ a10 is not limited thereto.
It should be noted that the AMF _ a240 may select the SMF _ a230 that transmits the PDU session setup request message based on information included in the PDU session setup request message. In more detail, the AMF _ a240 may select the SMF _ a230 of the routing destination according to various identification information acquired based on the reception of the PDU session setup request message, for example, thirty-one identification information and/or subscriber information and/or capability information of the network and/or operator policy and/or network status and/or context that the AMF _ a240 has maintained.
More specifically, the AMF _ a240 may select the SMF _ a230 from information stored when the PDU session is released based on one or more of thirty-first to thirty-third identification information. More specifically, the SMF _ a230 may be selected by determining a PDU session ID to be released in advance based on one or more pieces of identification information among the thirty-first to thirty-third pieces of identification information, and determining an SMF ID from stored information corresponding to the determined PDU session ID.
The SMF _ a230 receives the PDU session setup request message and performs a first conditional discrimination. The first condition is determined to determine whether the SMF _ a230 accepts the request of UE _ a 10. In the first condition discrimination, the SMF _ a230 determines whether the first condition discrimination is true or false. The SMF _ a230 starts the process (a) in this process when the first condition is determined to be true, and starts the process (B) in this process when the first condition is determined to be false. Note that, the procedure of the case where the first condition is judged to be false will be described later.
Hereinafter, the steps in the case where the first condition is determined to be true, that is, the steps in the process (a) in the present process will be described. The SMF _ a230 selects the UPF _ B236 of the PDU Session Establishment destination (S1505), transmits a Session Establishment request (Session Establishment request) message to the selected UPF _ B236 (S1506), and starts the procedure of (a) in this procedure.
Here, the SMF _ a230 may select one or more UPFs according to respective identification information acquired based on the reception of the PDU session setup request message, for example, thirty-one identification information and/or capability information of the network and/or subscriber information and/or operator policy and/or network status and/or context that the SMF _ a230 has maintained. It should be noted that, in the case that multiple UPFs are selected, the SMF _ a230 may send a session establishment request message to each UPF.
Alternatively, the SMF _ a230 at the beginning of the process may select the UPF _ B236 based on information that determines that the identification information of the UPF _ B236 stored in a colorful manner for changing the anchor device to the UPF _ B236 corresponds to the identification information of the PDU session in the process of determining the relocation of the UPF.
Hereinafter, a case where the SMF _ a230 selects the UPF _ B236 by the UPF selection process will be described. Note that, in the case where another UPF is selected, the PDU session can be established by performing a procedure to replace the UPF _ B236 with the selected UPF, which will be described later.
The UPF _ B236 receives the session establishment request message and formulates a context for the PDU session. Also, the UPF _ B236 transmits a Session Establishment response (Session Establishment response) message to the SMF _ a230 based on receiving the Session Establishment request message and/or formulating a context for the PDU Session (S1508). Further, the SMF _ a230 receives the session establishment response message. It should be noted that the session establishment request message and the session establishment response message may be control messages sent and received over the N4 interface. Also, the session establishment response message may be a response message to the session establishment request message.
Also, the SMF _ a230 may perform address assignment of an address assigned to the UE _ a10 based on the reception of a PDU session setup request message and/or the selection of the UPF _ B236 and/or the reception of a session setup response message. Also, the SMF _ a230 may associate an address assigned to the UE _ a10 with information indicating that the address is an address used in communication with the DN _ a 5. It should be noted that the SMF _ a230 may perform address assignment of an address assigned to the UE _ a10 during the PDU session setup procedure, or after the PDU session setup procedure is completed.
Specifically, the SMF _ a230 may allocate an address in the PDU session establishment process without using the DHCPv4 to allocate an IPv4 address, and may also transmit the allocated address to the UE _ a 10. Furthermore, the SMF _ a230 may allocate an Address after the PDU session establishment procedure when allocating an IPv4 Address and/or an IPv6 Address and/or an IPv6prefix using DHCPv4, DHCPv6, or slaac (stateless Address autoconfiguration), or may send the allocated Address to the UE _ a10 using RA. Note that the address allocation performed by the SMF _ a230 is not limited to this.
The SMF _ a230 may transmit the allocated address to the UE _ a10 in the fourteenth identification information upon completion of address allocation to the address allocated to the UE _ a10, or may transmit information indicating the allocated address and information indicating whether the allocated address is an address usable for user data communication with the DN _ a5 in association with each other to the UE _ a10 without being included in the fourteenth identification information. In this case, the UE _ a10 may receive the fourteenth identification information and/or information indicating an allocated address and/or information indicating whether the allocated address is an address that can be used in user data communication with the DN _ a5, which is transmitted by the SMF _ a 230.
The SMF _ a230 transmits a PDU session setup accept (PDU session setup accept) message to the UE _ a10 via the AMF _ a240 based on the reception of the PDU session setup request message and/or the selection of the UPF _ B236 and/or the reception of the session setup response message and/or the completion of the address assignment of the address assigned to the UE _ a10 (S1610) (S1612).
Note that, in the case where the PDU session establishment request message is included in the Registration request (Registration request) message and transmitted, the PDU session establishment accept message may be included in the Registration accept (Registration accept) message and transmitted. For example, the registration accept message may include a PDU session setup accept message as an SM message, or may include a PDU session setup accept message as an NAS message.
Specifically, the SMF _ a230 transmits a PDU session setup accept message to the AMF _ a240 using the N11 interface (S1510), and the AMF _ a240 having received the PDU session setup request message transmits a PDU session setup accept message to the UE _ a10 using the N1 interface (S1512).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session establishment accept message may be a PDN connection accept (PDN connectivity accept) message. The PDU session establishment accept message may be a NAS message transmitted and received over the N11 interface and the N1 interface, or may be transmitted in a NAS message. Further, the PDU session establishment accept message is not limited thereto, and may be a message indicating that the establishment of the PDU session is accepted.
Here, the SMF _ a230 and/or the AMF _ a240 may include one or more identification information of at least eleventh to fourteenth identification information in the PDU session setup accept message and/or the registration accept message and/or the NAS message, and may indicate that the request of the UE _ a10 is accepted by including the identification information.
Also, the SMF _ a230 may indicate that the network accepts the establishment request of the PDU session connected to DN _ a5 by transmitting more than one of the eleventh to fourteenth identification information, and may also indicate that the network allows the establishment of the PDU session connected to DN _ a 5.
It should be noted that the SMF _ a230 and/or the AMF _ a240 may determine which of the eleventh to fourteenth identification information to add to the PDU session establishment accept message and/or the registration accept message and/or the NAS message based on the received identification information and/or the network capability information and/or policies such as operator policy and/or the status of the network. It should be noted that the determination of which identification information to add to the PDU session setup accept message and/or the registration accept message and/or the NAS message by the SMF _ a230 and/or the AMF _ a240 is not limited thereto.
It should be noted that the SMF _ a230 may determine whether the eleventh identification information and/or the fourteenth identification information is included in the PDU session accept message based on a request of the UE _ a 10. In other words, the UE _ a10 may transmit information indicating that the SMF _ a230 includes the eleventh identification information in the PDU session accept message for transmission and/or information indicating that the SMF _ a230 includes the fourteenth identification information in the PDU session accept message for transmission to the SMF _ a230 via the AMF _ a 240. It should be noted that such request information may also be included in the PDU session establishment request message when the second PDU session is established, the PDU session establishment request message when the first PDU session is established, and/or the registration request message for transmission.
Also, the SMF _ a230 may transmit the eleventh identification information in case of receiving the first identification information and/or the second identification information and/or the third identification information representing the SSC pattern 3 through a PDU session setup request message at the time of establishing the second PDU session, a PDU session setup request message at the time of establishing the first PDU session, and/or a registration request message.
Further, the SMF _ a230 may include the default router address in the PDU session accept message for transmission based on the same condition as the condition of including the eleventh identification information and/or the fourteenth identification information. Note that the default router address may be an address or identification information indicating the UPF _ B236.
Here, the eleventh identification information may indicate information indicating a High priority level, and may be, for example, "High (High)" information. Thus, the UE _ a10 may be notified that the IPv6prefix corresponding to the first PDU session and/or the IPv6prefix corresponding to the second PDU session is high in priority with respect to the first PDU session and/or the IPv 3578 prefix corresponding to the first PDU session.
UE _ a10 receives the PDU session setup accept message, and further transmits a PDU session setup complete (PDU session setup complete) message to SMF _ a230 via AMF _ a240 (S1514) (S1516). Further, the SMF _ a230 receives the PDU session setup complete message and performs a second conditional discrimination.
Specifically, the UE _ a10 transmits a PDU session setup complete message to the AMF _ a240 using the N1 interface (S1514), and the AMF _ a240 having received the PDU session setup complete message transmits the PDU session setup complete message to the SMF _ a230 using the N11 interface (S1516).
It should be noted that, when the PDU session is a PDN connection, the PDU session establishment completion message may be a PDN connection completion (PDN Connectivity complete) message, or may be a default EPS bearer context activation accept (active default EPS bearer context accept) message. Also, the PDU session setup complete message may be a NAS message transceived over the N1 interface and the N11 interface. Further, the PDU session setup complete message may be a response message to the PDU session setup accept message, but is not limited thereto, and may also be a message indicating that the PDU session setup procedure is complete.
The second condition discriminates the kind of message on the N4 interface used for determining transceiving. If the second condition is determined to be true, the SMF _ a230 transmits a Session Modification request message (Session Modification request) to the UPF _ B236 (S1518), and receives a Session Modification response message (Session Modification response) transmitted by the UPF _ B236 that received the Session Modification request message (S1520). When the second condition is determined to be false, the SMF _ a230 transmits a session establishment request message to the UPF _ B236 (S1518), and further receives a session change response message transmitted by the UPF _ B236 that received the session establishment request message (S1520). Each device completes the (a) process of the present process based on the transmission and reception of the PDU session setup complete message and/or the transmission and reception of the session change response message and/or the transmission and reception of the session setup response message.
In the process (a) of this procedure, if the address assigned to the UE _ a10 is not notified to the UE _ a10, the SMF _ a230 may transmit an RA via the UPF _ B236 that becomes an anchor point (S1524). Here, the RA may include an IPv6prefix corresponding to the PDU session, and a default router address for transmission. Note that the default router address may be the address of the UPF _ B236. Also, the UE _ a10 that received the RA may generate an IPv6 address using the IPv6 network prefix included in the RA. Here, the IPv6 network prefix may be information different from information that a correspondence is established with the first PDU session.
The SMF _ a230 and/or the UPF _ B236 may notify that a PDU session has been established for the DN _ a5 by transmitting one or more of the eleventh identification information and the fourteenth identification information to the RA, and may also notify that an address is allocated to the UE _ a 10.
It should be noted that the SMF _ a230 may determine whether the eleventh identification information and/or the fourteenth identification information is included in the RA message based on a request of the UE _ a 10. In other words, the UE _ a10 may transmit information indicating that the SMF _ a230 includes the eleventh identification information in the PDU session accept message for transmission and/or information indicating that the SMF _ a230 includes the fourteenth identification information in the PDU session accept message for transmission to the SMF _ a230 via the AMF _ a 240. It should be noted that such request information may also be included in the PDU session establishment request message when the second PDU session is established, the PDU session establishment request message when the first PDU session is established, and/or the registration request message for transmission.
Also, the SMF _ a230 may transmit the eleventh identification information in case of receiving the first identification information and/or the second identification information and/or the third identification information representing the SSC pattern 3 through a PDU session setup request message at the time of establishing the second PDU session, a PDU session setup request message at the time of establishing the first PDU session, and/or a registration request message.
Further, the SMF _ a230 may include the default router address in the RA message for transmission based on the same condition as the condition for including the eleventh identification information and/or the fourteenth identification information. Note that the default router address may be an address or identification information indicating the UPF _ B236.
Here, the eleventh identification information may indicate information indicating a High priority level, and may be, for example, "High (High)" information. Thus, the UE _ a10 may be notified that the IPv6prefix corresponding to the first PDU session and/or the IPv6prefix corresponding to the second PDU session is high in priority with respect to the first PDU session and/or the IPv 3578 prefix corresponding to the first PDU session.
Next, each step of the process (B) in this process will be described. The SMF _ a230 transmits a PDU session establishment rejection message (S1526) to the UE _ a10 via the AMF _ a240 (S1528), and starts the (B) process in this procedure.
Specifically, the SMF _ a230 transmits a PDU session setup reject message to the AMF _ a240 using the N11 interface (S1526), and the AMF _ a240 having received the PDU session setup request message transmits a PDU session setup reject message to the UE _ a10 using the N1 interface (S1528).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session establishment reject message may be a PDN connection reject (PDN connectivity reject) message. The PDU session establishment reject message may be a NAS message transmitted and received over the N11 interface and the N1 interface, or may be transmitted in a NAS message. The PDU session establishment reject message is not limited to this, and may be a message indicating that the establishment of the PDU session is rejected.
Here, the SMF _ a230 and/or the AMF _ a240 may include at least fifteenth identification information in the PDU session setup reject message and/or the NAS message, or may include these identification information to indicate that the request of the UE _ a10 is rejected.
Also, the SMF _ a230 and/or the AMF _ a240 may indicate that the network has rejected the request for the setup of the PDU session connected to DN _ a5 by transmitting fifteenth identification information, and may also indicate that the setup of the PDU session connected to DN _ a5 is not allowed. Also, the SMF _ a230 may indicate that a PDU session connected to the DN _ a5 is not established by transmitting fifteenth identification information.
For example, SMF _ a230 and/or AMF _ a240 may indicate that a connection with DN _ a5 is rejected by sending fifteenth identification information, may indicate a reason for rejection, may indicate that a request for UE _ a10 is rejected, may indicate that a connection supporting the requested SSC mode cannot be established, or may indicate that establishment of a multi home PDU session is not supported.
Each device completes the procedure based on completion of the procedure (a) or (B) in this procedure or transmission/reception of S1524. It should be noted that each device may transition to a state in which a PDU session is established based on completion of the procedure (a) in this procedure, may know that this procedure is rejected based on completion of the procedure (B) in this procedure, and may also transition to a state in which a PDU session is not established.
Each device may perform processing based on the identification information transmitted and received in the present procedure, based on the completion of the present procedure.
Furthermore, the first condition discrimination may be performed based on identification information included in the PDU session setup request message and/or the registration request message and/or the NAS message and/or subscriber information and/or operator policy obtained from the UDM _ a 50. For example, the first conditional discrimination may be true if the network allows the request of the UE _ a 10. Further, the first conditional discrimination may be false in the case where the network does not allow the request of the UE _ a 10. The first condition discriminates that the UE _ a10 may be true if the network and/or the device in the network to which the UE _ a10 is connected supports the requested function, and may be false if the UE _ a10 does not support the requested function. The condition for determining whether the first condition is true or false may not be limited to the above condition. Further, the second conditional discrimination may be performed based on whether a session on the N4 interface for the PDU session is established. For example, the second condition discriminates that it may be true in case a session on the N4 interface for a PDU session is established and false in case it is not established. The condition for determining whether the second condition is true or false may not be limited to the above condition.
Thus, the UE _ a10 establishes a PDU session with the UPF _ B236 as the anchor point. As a result, the UE _ a10 becomes a state in which the PDU session with the UPF _ a235 as the security point and the PDU session with the UPF _ B236 as the anchor point are simultaneously established. It should be noted that these PDU sessions may be PDU sessions established for the same DN.
Thereby, the UE _ a10 enters a state of holding a plurality of communication paths. When transceiving user data, the UE _ a10 may select a route based on route preference information corresponding to each PDU session established. That is, the PDU session with high preference can be used for transceiving user data. At this time, an IPv6prefix and/or a default route and/or a default router corresponding to the PDU session with high preference may also be selected to transmit the user data.
[1.4.2.2 description of the second PDU Session Release procedure ]
The UE _ a10 may perform the second PDU session release procedure after completing the second PDU session establishment procedure. It should be noted that the second PDU session release procedure is a procedure for releasing a PDU session with the UPF _ a235 as an anchor point.
Hereinafter, an example of the order of performing the first PDU session setup procedure will be described using fig. 19. Hereinafter, each step of the present process will be described.
First, the UE _ a10 transmits a release request message for PDU session release to the AMF _ a240, and starts a release procedure for PDU session release (S1900). The UE _ a10 sends information identifying the PDU session with the UPF _ a235 as anchor and/or information indicating that the UPF _ a235 is an anchor and/or DNN included in the release request message for PDU session release.
The information identifying the PDU session with the UPF _ a235 as an anchor point may be, for example, a PDU session ID identifying the first PDU session, in a case where the PDU session ID identifying the first PDU session is different from a PDU session ID identifying the second PDU session established based on the procedure described in chapter 1.4.2.1.
Alternatively, the information identifying the PDU session with the UPF _ a235 as an anchor point may be information indicating an old PDU session and/or information indicating a PDU session with low routing preference. By including it, the UE _ a10 may request the release of the old PDU session and/or the release of a PDU session with low routing preference.
Alternatively, the information identifying the PDU session with the UPF _ a235 as an anchor may be information indicating the SSC pattern 3. By including it, the UE _ a10 may request the release of the old PDU session and/or the release of a PDU session with low routing preference.
Alternatively, the information identifying the PDU session with the UPF _ a235 as an anchor may be information indicating the SSC pattern 3. By including it, the UE _ a10 may request the release of the old PDU session and/or the release of a PDU session with low routing preference.
Alternatively, the information identifying the PDU session with the UPF _ a235 as an anchor point may be information representing the prefix of IPv 6. By including it, the UE _ a10 can request release of a PDU session corresponding to the IPv6 prefix.
Alternatively, the information may be a group of information in which one or more of the above-described information is combined.
Next, the AMF _ a240 receives the PDU session release request, and transmits the received PDU session release request to the SMF _ a230 (S1902).
The SMF _ a230 receives the PDU session release request, detects the UPF _ a235 as an anchor for the released PDU session and/or the released PDU session based on the PDU session release request.
The SMF _ a230 may previously store the information regarding the PDU session established by the UE _10 in correspondence with the anchor establishment of the PDU session, and select the UPF _ a235 as the anchor of the PDU session based on the PDU session release request included in the PDU session release request message. Here, the information on the PDU session may refer to a PDU session ID and/or DNN and/or preference information of the PDU session and/or IPv6prefix and/or information indicating SSC mode 3.
Alternatively, in the process of determining the relocation of the UPF at the beginning of the second PDU session setup procedure described in chapter 1.4.2.1, the SMF _ a230 may store information of the released PDU session and/or information of the anchor point of the released PDU session. The SMF _ a230 may select the UPF _ a235 as an anchor for the PDU session to be released based on such information.
Next, the SMF _ a230 transmits a Session release request (Session release request) message to the UPF _ a235 (S1906) to start a release process of the Session between the SMF _ a230 and the UPF _ a 235.
The UPF _ a235 receives the session release request message and deletes the context for the PDU session. Also, the UPF _ a235 transmits a Session release response (Session release response) message to the SMF _ a230 based on receiving the Session release request message and/or deleting the context for the PDU Session (S1908). Also, the SMF _ a230 receives the session release response message. It should be noted that the session release request message and the session release response message may be control messages sent and received over the N4 interface. Also, the session release response message may be a response message to the session release request message.
Next, the SMF _ a230 transmits a PDU session release command message (PDU session release command) to the UE _ a10 via the AMF _ a240 based on the reception of the PDU session release response message and/or the determination of the PDU session anchor relocation (S1910).
Specifically, the SMF _ a230 transmits a PDU session release command message to the AMF _ a240 (S1910), and the AMF _ a240 having received the PDU session release command message transmits the PDU session release command message to the UE _ a10 (S1912).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session release command message may be an EPS bearer disable request (deactivating EPS bearer context request) message. The PDU session release command message may be a NAS message transmitted and received over the N11 interface and the N1 interface, or may be transmitted in a NAS message. The PDU session release command message is not limited to this, and may be any message that indicates that the network requests the release of the PDU session and/or that the network determines the release of the PDU session.
Here, the SMF _ a230 and/or the AMF _ a240 may include at least one or more identification information of twenty-first to twenty-second identification information in the PDU session release command message and/or the NAS message, or may indicate a request for release of the PDU session by including the identification information.
Also, the SMF _ a230 and/or the AMF _ a240 may indicate that the network accepts the request for the establishment of the PDU session connected to DN _ a5 by transmitting one or more of the twenty-first to twenty-second identification information, and may also indicate that the network allows the establishment of the PDU session connected to DN _ a 5.
In more detail, the SMF _ a230 and/or the AMF _ a240 may indicate to maintain information about the PDU session released a certain period of time after the PDU session is released by transmitting the twenty-first identification information. Specifically, the SMF _ a230 may store information related to the UPF _ a235 in which the PDU session is associated with the twenty-first identification information, and the AMF _ a240 may store information identifying the SMF _ a230, for example, an SMF ID, in association with the twenty-first identification information.
Also, by transmitting the twenty-second identification information, the SMF _ a230 and/or the AMF _ a240 may indicate that the release of the PDU session is performed for PDU session anchor relocation.
It should be noted that the SMF _ a230 and/or the AMF _ a240 may determine which identification information of the twenty-first to twenty-second identification information to add to the PDU session release command message and/or the NAS message based on the received identification information and/or the capability information of the network and/or the policy such as the operator policy and/or the status of the network. It should be noted that the determination of which identification information to add to the PDU session release command message and/or the NAS message by the SMF _ a230 and/or the AMF _ a240 is not limited thereto.
UE _ a10 receives the PDU session release command message, and further sends a PDU session release accept message to SMF _ a230 via AMF _ a240 (S1914) (S1916).
Specifically, the UE _ a10 transmits a PDU session release accept message to the AMF _ a240 using the N1 interface (S1914), and the AMF _ a240 having received the PDU session release accept message transmits a PDU session release accept message to the SMF _ a230 using the N11 interface (S1916).
It should be noted that, in the case that the PDU session is a PDN connection, the PDU session release accept message may be an EPS bearer context disable accept (deactivating EPS bearer context accept) message. The PDU session release accept message may be a NAS message transmitted and received over the N1 interface and the N11 interface, or may be transmitted and received by including the NAS message. The PDU session release accept message is not limited to this as long as it is a response message to the PDU session release command message, and it is only required to be a message indicating that the PDU session release process is completed.
Next, the SMF _ a230 transmits a PDU session release notification (PDU session release) message to the AMF _ a240 (S1918). The SMF _ a230 may notify completion of the release of the PDU session by transmitting a PDU session release notification message, or may notify that the PDU session is released but in a state of maintaining storage of information for storing a part of relocation. The PDU session release notification message is not limited to this, and may be any message that notifies the release of the PDU session.
It should be noted that the AMF _ a240 may start the timing of the timer using the timer managing the storage of the information on the PDU session based on the reception of the PDU session release accept message and/or the reception of the PDU session release notify message and/or the transmission of the PDU session release command message. Also, the AMF _ a240 may start storing the twenty-first identification information in association with information on the PDU session, for example, an SMF ID identifying the SMF _ 230.
Alternatively, the AMF _ A240 may begin storing the above information based on more detailed conditions. For example, in case of receiving a PDU session release notification message including twenty-first identification information and/or twenty-second identification information and/or in case of releasing a PDU session of the SSC mode 2, the above information may be stored starting based on the reception of a PDU session release accept message and/or the reception of a PDU session release notification message and/or the transmission of a PDU session release command message. It should be noted that such detailed conditions may be determined by the system, the policy of the operator, and the like. If such a condition is not met, AMF _ a240 may not start storing the information and counting the timer. In addition, the timer managing the storage of the information on the PDU session may be stored by the AMF _ a240 through pre-configuration, or may be determined based on the received identification information and/or policies such as capability information of the network and/or operator policies and/or states of the network.
Also, the AMF _ a240 may release the information and/or context on the PDU session in case of expiration of a timer (expire) using a timer managing storage of information on the PDU session.
The SMF _ a230 may start timing of a timer using a timer managing storage of information on the PDU session based on reception of the PDU session release accept message and/or transmission of the PDU session release notify message and/or reception of the PDU session release command message. Also, the SMF _ a230 may start to store the twenty-first identification information in association with information on the PDU session.
Alternatively, the SMF _ a230 may start storing the above information based on a more detailed condition. For example, in the case of receiving a PDU session release accept message including the twenty-first identification information and/or the twenty-second identification information and/or in the case of transmitting a PDU session release notification message including the twenty-first identification information and/or the twenty-second identification information and/or in the case of releasing the PDU session of the SSC mode 2, the timing of the above-described timer may be started and the twenty-first identification information may be stored in association with information on the PDU session based on the reception of the PDU session release accept message and/or based on the transmission of the PDU session release notification message and/or based on the reception of the PDU session release command message.
It should be noted that such detailed conditions may be determined by the system, the policy of the operator, and the like. If such a condition is not met, the SMF _ a230 may not start storing the information and counting the timer. Here, the information on the PDU session may refer to a UPF ID of the UPF _ a235 identifying the relocation source, in which case the SMF _ a230 selects the UFP _ B236 of the relocation destination in the first PDU session setup procedure.
Alternatively, the information about the PDU session may be a UPF ID of the UPF _ B236 identifying the relocation destination, in which case the SMF _ a230 may select the UPF _ B236 of the relocation destination based on the receipt of the PDU session release response message and/or the determination of the PDU session anchor relocation.
Here, the timer managing the storage of the information on the PDU session may be stored by the SMF _ a230 through pre-configuration, or may be determined based on a policy such as the received identification information and/or capability information of the network and/or operator policy and/or the state of the network. Also, the SMF _ a230 may release the information and/or context on the PDU session in case of expiration of a timer (expire) using a timer managing storage of the information on the PDU session.
Each device completes the process based on the transmission and reception in S1716. It should be noted that each device may transition to a state in which the first PDU session is released upon completion of the present procedure.
In this process example, the procedure of releasing the PDU session by being dominated by the SMF _ a230 is described based on fig. 19, but the procedure is not limited to this, and other procedures may be used. For example, a procedure may also be implemented where the network dominates to release the PDU session. In this case, the procedure of S1900 and S1902, which corresponds to a part where the UE _ a10 starts the procedure in the PDU session release procedure described so far, may be omitted. Thereby, the PDU session release procedure initiated by the SMF _ a230 can be performed.
[1.5. overview of PDU Session Change procedure ]
Next, an outline of the PDU session change procedure will be described. Hereinafter, the present procedure refers to a PDU session change procedure. This procedure is performed to update the status of the PDU session by each device. It should be noted that each device may execute the PDU session establishment procedure in a state of having completed the PDU session establishment procedure, or may execute the PDU session establishment procedure in the PDU session establishment procedure. In addition, each device may start the procedure in the registration state, or may start the procedure at an arbitrary timing after the PDU session establishment procedure. Further, each device may update the status of the PDU session based on completion of the PDU session change procedure. Also, in the case where a plurality of PDU sessions are established, each device can update the status of each PDU session by performing the present procedure a plurality of times.
[1.5.1.PDU Session Change procedure example ]
An example of the order in which the PDU session change procedure is performed will be described with reference to fig. 14. Hereinafter, each step of the present process will be described. First, the UE _ a10 transmits a PDU session modification request (PDU session modification request) message to the SMF _ a230 via the AMF _ a240 (S1400) (S1402). Specifically, the UE _ a10 transmits a PDU session change request message to the AMF _ a240 using the N1 interface (S1400), and the AMF _ a240 having received the PDU session change request message transmits the PDU session change request message to the SMF _ a230 using the N11 interface (S1402).
The trigger of the UE _ a10 sending the PDU session change request message may be that the UE _ a10 has moved, that a default route has changed, or that the policy of the UE _ a10 has changed.
Here, the UE _ a10 may include at least one of sixteenth to sixteenth identification information in the PDU session change request message, or may include the identification information to indicate a request of the UE _ a 10.
Further, the UE _ a10 may request a change of the connection destination of the PDU session by transmitting one or more pieces of identification information among sixty-first to sixty-second identification information, or may request a change of information on the connection.
In more detail, the UE _ a10 may request updating of preference information including a route indicated by sixty-second identification information or updating of information on a PDU session of the route indicated by sixty-second identification information by transmitting sixty-first identification information and/or transmitting sixty-first identification information in correspondence with sixty-second identification information, and may also request changing of the route to a default route.
Also, the UE _ a10 may indicate a route for requesting update of preference information by transmitting sixty-second identification information.
Next, the SMF _ a230 determines a change of the PDU session (S1406). The SMF _ a230 may determine the change of the PDU session based on the reception of the PUD session change request message, or may determine the change of the PDU session based on operator policy, network policy, mobility of the UE _ a10, subscriber information.
That is, the SMF _ a230 may start the PDU session change procedure without receiving a PDU session change request from the UE _ a 10. In other words, the PDU session change procedure may be a procedure started by the UE or a procedure started by the network.
In the case where the SMF _ a230 receives the PDU session change request message, the SMF _ a230 performs the first conditional discrimination. The first condition is determined to determine whether the SMF _ a230 accepts the request of UE _ a 10. In the first condition discrimination, the SMF _ a230 determines whether the first condition discrimination is true or false. The SMF _ a230 starts the process (a) in this process when the first condition is determined to be true, and starts the process (B) in this process when the first condition is determined to be false. Note that, the procedure of the case where the first condition is judged to be false will be described later.
It should be noted that, when the SMF _ a230 does not receive the PDU session change request message, the SMF _ a230 may start the process (a) in this procedure without performing the first condition determination.
Hereinafter, each step of the process (a) in the present process will be described. The SMF _ a230 transmits a PDU session modification command message (S1408) to the UE _ a10 via the AMF _ a240 (S1410). Specifically, the SMF _ a230 transmits a PDU session change command message to the AMF _ a240 using the N11 interface (S1408), and the AMF _ a240 having received the PDU session change command message transmits the PDU session change command message to the UE _ a10 using the N1 interface (S1410).
It should be noted that the trigger of the SMF _ a230 sending the PDU session change command message may be receiving a state change notification message sent from the AMF _ a240, receiving a request message from the AF, or detecting a state change of the SMF _ a230 itself.
The PDU session change command message may be a NAS message transmitted and received over the N11 interface and the N1 interface, or may be transmitted and received in a NAS message. The PDU session change command message is not limited to this, and may be any message indicating that the change of the PDU session is determined.
The state change notification message may be a message transmitted from the AMF _ a240 to the SMF _ a230 using the N11 interface, or information indicating that the state of the UE _ a10 changes according to the mobility of the UE _ a10, or the like. Also, the state change notification message may also be information indicating that a state of the UE _ a10 and/or the network device has changed due to a change in subscriber information and/or operator policy and/or policy of the UE _ a 10. The request message from the AF may be a request message sent from the AF or a request message sent by another network device agent.
Here, the SMF _ a230 may include at least one or more identification information of the seventeenth to seventeenth identification information in the PDU session change command message, or may include these identification information to indicate a request of the SMF _ a 230.
Also, the SMF _ a230 may request a connection target of the PDU session, a change of information on the PDU session, by transmitting one or more identification information of the seventy-first to seventy-second identification information. In more detail, the SMF _ a230 may request updating of the preference information by transmitting the seventy-first identification information and/or transmitting the seventy-first identification information in association with the seventy-second identification information, may request a change of the default route, and may notify a change of mobility.
Also, the SMF _ a230 may notify updating of the preference information by transmitting the seventy-second identification information, and may also notify updated preference information.
It should be noted that the SMF _ a230 may determine which identification information of the seventy-first to seventy-second identification information is to be added to the PDU session change request message based on the network status and/or policies such as the capability information of the network and/or the operator policy. It should be noted that the determination of which identification information is to be added to the PDU session change request message by the SMF _ a230 is not limited thereto.
The UE _ a10 that received the PDU session change command message transmits a PDU session change response (PDU session update accept) message to the SMF _ a230 via the AMF _ a240 (S1412) (S1414).
Specifically, the UE _ a10 transmits a PDU session change response message to the AMF _ a240 using the N1 interface (S1412), and the AMF _ a240 having received the PDU session change request message transmits the PDU session change response message to the SMF _ a230 using the N11 interface (S1414).
The PDU session change response message may be a NAS message transmitted and received over the N1 interface and the N11 interface, or may be transmitted and received in a NAS message. The PDU session change response message is not limited to this, and may be a message indicating that the PDU session establishment is accepted.
The SMF _ a230 receives the PDU Session change response message and transmits a Session Modification request message (Session Modification request) to the UPF _ a235 (S1416), and further receives a Session Modification response message (Session Modification response) transmitted by the UPF _ a235 having received the Session Modification request message (S1418). Each device completes the process (a) in this process based on the transmission and reception of the PDU session change response message and/or the transmission and reception of the session change response message.
In the process (a) of this procedure, if the address allocated to the UE _ a10 is not notified to the UE _ a10, the SMF _ a230 may transmit an RA via the UPF _ a235 or the UEPF _ B236 that becomes an anchor point (S1420).
The SMF _ a230 and/or UPF _ a235 may notify the change preference information by sending the seventy-second identification information to the RA, and may also change the notification address to the UE _ a 10.
Next, each step of the process (B) in this process will be described. The SMF _ a230 starts the (B) process in this process by transmitting a PDU session initiation reject (reject) message (S1422) via the AMF _ a240 (S1424).
Specifically, the SMF _ a230 transmits a PDU session change reject message to the AMF _ a240 using the N11 interface (S1422), and the AMF _ a240 having received the PDU session change reject message transmits a PDU session change reject message to the UE _ a10 using the N1 interface (S1424).
The PDU session change rejection message may be a NAS message transmitted and received over the N11 interface and the N1 interface, or may be transmitted and received in a NAS message. The PDU session change rejection message is not limited to this, and may be any message indicating that the change of the PDU session is rejected.
Here, the SMF _ a230 may include at least eighty-th identification information in the PDU session change reject message, or may notify rejection of the request by including the identification information.
Also, the SMF _ a230 may reject the change of the information on the PDU session by transmitting the eighty-first identification information. Specifically, the SMF _ a230 may indicate that the request of the UE _ a10 is rejected by transmitting the eighty-first identification information, may indicate that the preference information cannot be changed, or may indicate that the preference information does not satisfy the request.
Further, the state in which the PDU session is not established may be shifted to the state in which the PDU session is not established or to the abnormal state based on the transmission of the AMF _ a240 and/or the SMF _ a230 and/or the PDU session change reject message and/or the transmission of each piece of identification information included in the PDU session change reject message.
Likewise, the UE _ a10 may transition to a state where a PDU session is not established or may transition to an abnormal state based on the reception of the PDU session change reject message and/or the reception of each identification information included in the PDU session change reject message. Note that the state in which the state corresponding to the UE _ a10 is established transitions upon completion of the present procedure is not limited to this.
Further, the first conditional discrimination may be performed based on identification information included in the PDU session change request message and/or preferences of the UE _ a10 and/or policies of the UE _ a10 and/or context maintained by the UE _ a 10. The condition for determining whether the first condition is true or false may not be limited to the above condition.
[2. modified examples ]
The program that operates in the apparatus according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like to realize the functions of the embodiments according to the present invention and cause a computer to function. The program or information processed 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 other storage device system.
Note that a program for realizing the functions of the embodiments of the present invention may be recorded in a computer-readable recording medium. This can be realized by reading the program recorded in the recording medium into a computer system and executing it. The term "computer system" as used herein refers to a computer system built in the apparatus and includes hardware such as an operating system and peripheral devices. Further, the "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short time, or another recording medium that is readable by a computer.
Further, each functional block or each feature of the apparatus used in the above-described embodiments may be mounted on or executed by an electronic circuit, for example, an integrated circuit or a plurality of integrated circuits. A circuit designed in a manner to perform the functions described herein may include: general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic elements, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor, but in the alternative, the processor may be a conventional processor, controller, microcontroller, or state machine. The electronic circuit may be a digital circuit or an analog circuit. Further, in the case where an integrated circuit technology that replaces a current integrated circuit appears due to the advancement of semiconductor technology, one or more aspects of the present invention can also use a new integrated circuit based on the technology.
The present invention is not limited to the above-described embodiments. In the embodiments, although an example of the device is described, the present invention is not limited to this, and can be applied to fixed or non-movable electronic devices installed indoors and outdoors, for example, terminal devices or communication devices such as AV equipment, kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.
While the embodiments of the present invention have been described in detail with reference to the drawings, the specific configurations are not limited to the embodiments, and design changes and the like are included without departing from the scope of the present invention. The present invention can be variously modified within the scope shown in the claims, and embodiments obtained by appropriately combining the claims disclosed in the respective different embodiments are also included in the technical scope of the present invention. The present invention also includes a configuration in which elements having the same effects as those described in the above embodiments are replaced with each other.
Description of the reference numerals
1 mobile communication system
5 DN_A
10 UE_A
45 eNB_A
50 UDM_A
60 PCF_A
80 E-UTRAN_A
120 5G RAN_A
122 AN node _ A
123 AN node _ B
125 WLAN ANc
126 WAG_A
190 core network _ B
230 SMF_A
235 UPF_A
236 UPF_B
240 AMF_A
- 上一篇：一种医用注射器针头装配设备
- 下一篇：切换状态的方法、网络设备和终端设备