User device, control device, and communication control method

Abstract

The present invention provides a communication method for realizing URLLC functions requiring high reliability and / or low latency communication in 5GS. A communication method for realizing URLLC functions even in 5GS supporting network-led setting update process and continuity of multiple session services is provided. A communication method for sharing which of the URLLC functions can be used between a user device and a network when multiple URLLC functions can be realized and appropriately managing the shared information is also provided.

Description

Technical Field

[0001] The present invention relates to a user device, a control device, and a communication control method. This application claims priority based on Japanese Patent Application No. 2018-97127 filed in Japan on May 21, 2018, and the contents thereof are hereby incorporated by reference. Background Art

[0002] In 3GPP (3rd Generation Partnership Project), research has begun on the system architecture of 5GS (5G System), which is the next generation, fifth generation (5G) mobile communication system, and discussions have been held on the support of new processes and new functions (see Non-Patent Documents 1 and 2). In addition, discussions have also begun on URLLC (Ultra-Reliable and Low Latency Communications) for supporting communications that require high reliability and / or low latency in 5GS (see Non-Patent Document 3).

[0003] Prior art literature

[0004] Non-patent literature

[0005] Non-patent document 1: 3GPP TS 23.501 v15.1.0 (2018-03); Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)

[0006] Non-patent document 2: 3GPP TS 23.502 v15.1.0 (2018-03); Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15)

[0007] Non-patent literature 3: 3GPP TR 23.725 v0.1.0(2018-04); Technical SpecificationGroup Services and System Aspects; Study on Study on enhancement of URLLCsupporting in 5GC(Release 16) Summary of the invention

[0008] Problem that the invention aims to solve

[0009] In 5GS (5G System), 5GC (5G Core Network) is being studied as a new core network to provide various services. In addition, research on functions for URLLC has also begun.

[0010] It should be noted that 5GS supports new processes such as network-led setting update process, multiple session service continuity, connection to LADN (Local Area Data Network), and other new functions. However, it is not clear how to use the new processes and new functions to implement URLLC functions in 5GS.

[0011] A solution of the present invention is completed in view of the above situation, and its purpose is to provide a method for implementing the functions used for URLLC in 5GS.

[0012] Technical Solution

[0013] A user device according to one embodiment of the present invention is characterized in that it comprises a control unit and a transceiver unit, wherein during a login process, the transceiver unit sends a login request message including information indicating support for Ultra-Reliable and Low Latency Communications (URLLC) to a control device, and receives a login request message including information indicating support for the URLLC from the control device, and the control unit establishes a PDU session supporting the URLLC during a Protocol Data Unit (PDU) session establishment process executed after the login process is completed.

[0014] A control device according to one embodiment of the present invention is characterized in that it comprises a control unit and a transceiver unit, wherein during a login process, the transceiver unit receives a login request message including information indicating support for Ultra-Reliable and Low Latency Communications (URLLC) from a user device, and sends the login request message including information indicating support for the URLLC to the user device, and the control unit establishes a PDU session supporting the URLLC during a Protocol Data Unit (PDU) session establishment process executed after the login process is completed.

[0015] A communication control method for a user device in one embodiment of the present invention is characterized in that it comprises the following steps: during a login process, sending a login request message including information indicating support for Ultra-Reliable and Low Latency Communications (URLLC) to a control device; receiving a login request message including information indicating support for the URLLC from the control device; and during a Protocol Data Unit (PDU) session establishment process executed after the login process is completed, establishing a PDU session supporting the URLLC.

[0016] A communication control method for a control device according to one embodiment of the present invention is characterized in that it comprises the following steps: during a login process, receiving a login request message including information indicating support for Ultra-Reliable and Low Latency Communications (URLLC) from a user device; sending a login request message including information indicating support for the URLLC to the user device; and during a Protocol Data Unit (PDU) session establishment process executed after the login process is completed, establishing a PDU session supporting the URLLC.

[0017] Beneficial Effects

[0018] According to one solution of the present invention, the functions for URLLC can be used in 5GS even when 5GS supports a network-led setting update process and continuity of multiple session services. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 This is a diagram illustrating an overview of a mobile communication system (EPS / 5GS).

[0020] Figure 2 This is a diagram illustrating the detailed structure of the mobile communication system (EPS / 5GS).

[0021] Figure 3 This is a diagram illustrating the device structure of UE.

[0022] Figure 4 This is a diagram illustrating the structure of the access network device (gNB) in 5GS.

[0023] Figure 5 This is a diagram illustrating the structure of the core network device (AMF / SMF / UPF) in 5GS.

[0024] Figure 6 is a diagram illustrating the login process.

[0025] Figure 7 It is a diagram illustrating the PDU session establishment process. DETAILED DESCRIPTION

[0026] The best mode for carrying out the present invention will be described with reference to the accompanying drawings.

[0027] [1. System Overview]

[0028] first, Figure 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment. Figure 2 It is a diagram for explaining the detailed structure of the mobile communication system 1.

[0029] exist Figure 1 It is recorded that the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network: packet data network)_A5, access network_B120, core network_B190 and DN (Data Network: data network)_A6.

[0030] In the following, symbols are sometimes omitted to record these devices and functions, for example, UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0031] In addition, Figure 2 It records devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, and interfaces that connect these devices and functions.

[0032] In the following, symbols are sometimes omitted to record these devices and functions, for example, UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, etc.

[0033] It should be noted that the EPS (Evolved Packet System) as a 4G system is composed of an access network_A and a core network_A, but may further include UE and / or PDN. In addition, the 5GS (5G System) as a 5G system is composed of a UE, an access network_B and a core network_B, but may further include a DN.

[0034] UE is a device that can connect to network services via 3GPP access (also known as 3GPP access network, 3GPP AN) and / or non-3GPP access (non-3GPP access, also known as non-3GPP access network, non-3GPP AN). UE can be a terminal device that can perform wireless communication, such as a portable phone or a smart phone, or a terminal device that can connect to EPS or 5GS. UE can have UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). It should be noted that UE can be expressed as a user device or as a terminal device.

[0035] In addition, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are configured in E-UTRAN. It should be noted that, in the following, the symbols for eNB45 are sometimes omitted, such as eNB. In addition, when there are multiple eNBs, each eNB is connected to each other, for example, via an X2 interface. In addition, one or more access points are configured in the wireless LAN access network.

[0036] In addition, access network_B corresponds to the 5G access network (5G AN). 5G AN is composed of NG-RAN (NG Radio Access Network: NG radio access network) and / or non-3GPP access network. One or more gNB (NRNodeB: NR node B) 122 are configured in NG-RAN. It should be noted that, below, the gNB122 is sometimes recorded with omitted symbols, such as eNB. The gNB is a node that provides the NR (New Radio: New Radio) user plane and control plane to the UE, and is a node connected to the 5GC via the NG interface (including the N2 interface or the N3 interface). That is, the gNB is a base station device newly designed for 5GS, and has different functions from the base station device (eNB) used in the EPS which is a 4G system. In addition, when there are multiple gNBs, the gNBs are connected to each other, for example, via the Xn interface.

[0037] In addition, below, E-UTRAN and NG-RAN are referred to as 3GPP access. In addition, wireless LAN access network and non-3GPP AN (non-3GPP AN) are referred to as non-3GPP access. In addition, nodes configured in access network_B are also collectively referred to as NG-RAN nodes.

[0038] In addition, below, access network_A and / or access network_B and / or the device included in access network_A and / or the device included in access network_B are sometimes referred to as access networks or access network devices.

[0039] In addition, the core network_A corresponds to EPC (Evolved Packet Core). In EPC, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc. are configured.

[0040] In addition, core network_B corresponds to 5GC (5G Core Network). In 5GC, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), UDM (Unified Data Management), etc. are configured. Here, 5GC can be expressed as 5GCN (5G Core Network).

[0041] In addition, below, core network_A and / or core network_B and / or the device included in core network_A and / or the device included in core network_B are sometimes referred to as core network or core network device.

[0042] The core network (core network_A and / or core network_B) can be an IP mobile communication network operated by a mobile communication operator (Mobile Network Operator; MNO) that connects the access network (access network_A and / or access network_B) and PDN and / or DN, or it can be a core network used by a mobile communication operator that operates and manages the mobile communication system 1, or it can be a core network used by virtual mobile communication operators and virtual mobile communication service providers such as MVNO (Mobile Virtual Network Operator) and MVNE (Mobile Virtual Network Enabler).

[0043] In addition, Figure 1 The case where PDN is the same as DN is recorded in the specification, but they can also be different. PDN can be a DN (Data Network) that provides communication services to UE. It should be noted that DN can be constructed as a packet data service network, and can also be constructed for each service. Moreover, PDN can include connected communication terminals. Therefore, connection with PDN can be connection with communication terminals and server devices configured for PDN. Moreover, sending and receiving user data with PDN can be sending and receiving user data with communication terminals and server devices configured for PDN. It should be noted that PDN can be expressed as DN, and DN can also be expressed as PDN.

[0044] In addition, hereinafter, at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN and / or one or more devices included therein are sometimes referred to as a network or a network device. That is, the network and / or network device sending and receiving messages and / or executing a process means that at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN and / or one or more devices included therein send and receive messages and / or execute a process.

[0045] In addition, the UE can be connected to the access network. In addition, the UE can be connected to the core network via the access network. Moreover, the UE can be connected to the PDN or DN via the access network and the core network. That is, the UE can send and receive (communicate) user data between the PDN or DN. When sending and receiving user data, not only IP (Internet Protocol) communication can be used, but also non-IP communication can be used.

[0046] Here, IP communication refers to data communication using IP, in which data is sent and received through IP packets. An IP packet consists of an IP header and a payload portion. The payload portion may include data sent and received by devices and functions included in EPS, and devices and functions included in 5GS. In addition, non-IP communication refers to data communication that does not use IP, in which data is sent and received in a form different from the structure of IP packets. For example, non-IP communication may be data communication achieved by sending and receiving application data that is not assigned an IP header, or may be assigned other headers such as a MAC header, Ethernet (registered trademark) frame header, etc. to send and receive user data sent and received by the UE.

[0047] [2. Configuration of each device]

[0048] Next, the configuration of each device (UE and / or access network device and / or core network device) used in each embodiment is described using the accompanying drawings. It should be noted that each device can be configured as physical hardware, as logical (virtual) hardware configured on general hardware, or as software. In addition, at least part (including all) of the functions of each device can also be configured as physical hardware, logical hardware, or software.

[0049] It should be noted that the storage units (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) in each device and function that appear below are composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each storage unit can not only store the information originally set at the factory stage, but also store various information sent and received between the device itself and devices and functions other than the function (such as UE and / or access network device and / or core network device and / or PDN and / or DN). In addition, each storage unit can store identification information, control information, flags, parameters, etc. included in the control messages sent and received in various communication processes described later. In addition, each storage unit can store this information in each UE. In addition, in the case of intercommunication between 5GS and EPS, each storage unit can store control messages and user data sent and received between the devices and functions included in 5GS and / or EPS. At this time, not only the data sent and received via the N26 interface can be stored, but also the data not sent and received via the N26 interface can be stored.

[0050] [2.1. UE device configuration]

[0051] First, use Figure 3An example of the configuration of a UE (User Equipment) is described. The UE is composed of a control unit_A300, an antenna 310, a transceiver_A320, and a storage unit_A340. The control unit_A300, the transceiver_A320, and the storage unit_A340 are connected via a bus. The transceiver_A320 is connected to the antenna 310.

[0052] The control unit_A300 is a functional unit that controls the overall actions and functions of the UE. The control unit_A300 implements various processes in the UE by reading and executing various programs stored in the storage unit_A340 as needed.

[0053] The transceiver_A320 is a functional unit for wirelessly communicating with a base station device (eNB or gNB) in the access network via an antenna. That is, the UE can use the transceiver_A320 to send and receive user data and / or control information between the access network device and / or the core network device and / or the PDN and / or the DN.

[0054] Reference Figure 2 To explain in detail, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver_A320. In addition, the UE can communicate with the base station device (gNB) in the 5G AN by using the transceiver_A320. In addition, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface by using the transceiver_A320. However, the N1 interface is a logical interface, so the communication between the UE and the AMF is actually carried out via the 5G AN.

[0055] The storage unit_A340 is a functional unit for storing programs, user data, control information, etc. required for various actions of the UE.

[0056] [2.2.gNB device configuration]

[0057] Next, use Figure 4 The following describes an example of the device configuration of a gNB. The gNB is composed of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, the network connection unit_B520, the transceiver unit_B530, and the storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0058] The control unit_B500 is a functional unit that controls the overall actions and functions of the gNB. The control unit_B500 implements various processes in the gNB by reading various programs stored in the storage unit_B540 as needed and executing them.

[0059] The network connection unit_B520 is a functional unit for gNB to communicate with AMF and / or UPF. That is, the gNB can use the network connection unit_B520 to send and receive user data and / or control information between the AMF and / or UPF.

[0060] The transceiver_B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can use the transceiver_B530 to send and receive user data and / or control information between the UE.

[0061] Reference Figure 2 To explain in detail, the gNB in ​​the 5G AN can communicate with the AMF via the N2 interface by using the network connection unit_B520, and can communicate with the UPF via the N3 interface. In addition, the gNB can communicate with the UE by using the transceiver unit_B530.

[0062] Storage unit_B540 is a functional unit used to store programs, user data, control information, etc. required for various actions of gNB.

[0063] [2.3.AMF device configuration]

[0064] Next, use Figure 5 The following describes an example of the device configuration of AMF. AMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. AMF may be a node that processes a control plane.

[0065] The control unit_B700 is a functional unit that controls the entire operation and function of the AMF. The control unit_B700 reads various programs stored in the storage unit_B740 as needed and executes them to realize various processes in the AMF.

[0066] The network connection unit_B720 is a functional unit for connecting the AMF with the base station device (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF in the 5G AN. That is, the AMF can use the network connection unit_B720 to send and receive user data and / or control information between the base station device (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF in the 5G AN.

[0067] Reference Figure 2To explain in detail, the AMF in the 5GC can communicate with the gNB via the N2 interface by using the network connection unit_A620, can communicate with the UDM via the N8 interface, can communicate with the SMF via the N11 interface, and can communicate with the PCF via the N15 interface. In addition, the AMF can send and receive NAS messages with the UE via the N1 interface by using the network connection unit_A620. However, the N1 interface is a logical interface, so the communication between the UE and the AMF is actually carried out via the 5G AN. In addition, the AMF can communicate with the MME via the N26 interface by using the network connection unit_A620 when the N26 interface is supported.

[0068] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of AMF.

[0069] It should be noted that AMF has the following functions: the function of exchanging control messages with RAN using N2 interface, the function of exchanging NAS messages with UE using N1 interface, the function of encrypting and integrity protecting NAS messages, the registration management (RM) function, the connection management (CM) function, the reachability management function, the mobility management (Mobility management) function of UE, etc., the function of transmitting SM (Session Management) messages between UE and SMF, the access authentication (Access Authentication, Access Authorization) function, the security anchor function (SEA; Security Anchor Functionality), the security context management (SCM; Security Context Management) function, the function of supporting the N2 interface for N3IWF (Non-3GPP Interworking Function: non-3GPP interworking function), the function of supporting the sending and receiving of NAS signals with UE via N3IWF, the function of authenticating UE connected via N3IWF, etc.

[0070] In addition, the RM state of each UE is managed in the login management. The RM state can be synchronized between the UE and the AMF. As the RM state, there are a non-logged-in state (RM-DEREGISTERED state) and a logged-in state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not logged in to the network. Therefore, the UE context in the AMF does not have valid location information and routing information for the UE, so the AMF is in a state where the UE cannot be reached. In addition, in the RM-REGISTERED state, the UE logs in to the network, so the UE can receive services that require logging in to the network. It should be noted that the RM state can also be expressed as a 5GMM state (5GMM state). In this case, the RM-DEREGISTERED state can also be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state can also be expressed as a 5GMM-REGISTERED state.

[0071] In other words, 5GMM-REGISTERED can be a state where each device has established a 5GMM context, or a state where a PDU session context has been established. It should be noted that when each device is in 5GMM-REGISTERED, UE_A10 can start sending and receiving user data and control messages, and can also respond to paging. Moreover, it should be noted that when each device is in 5GMM-REGISTERED, UE_A10 can perform login procedures and / or service request procedures other than the login procedure for initial login.

[0072] Moreover, 5GMM-DEREGISTERED can be a state where each device has not established a 5GMM context, a state where the network has not grasped the location information of UE_A10, or a state where the network cannot reach UE_A10. It should be noted that when each device is in 5GMM-DEREGISTERED, UE_A10 can start the login process or establish a 5GMM context by executing the login process.

[0073] In addition, the CM state of each UE is managed in the connection management. The CM state can be synchronized between the UE and the AMF. As CM states, there are a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the non-connected state, the UE is in a logged-in state, but does not have a NAS signaling connection (NASsignalling connection) established with the AMF via the N1 interface. In addition, in the non-connected state, the UE does not have a connection (N2connection) of the N2 interface and a connection (N3 connection) of the N3 interface. On the other hand, in the connected state, it has a NAS signaling connection (NAS signalling connection) established with the AMF via the N1 interface. In addition, in the connected state, the UE may also have a connection (N2 connection) of the N2 interface and / or a connection (N3 connection) of the N3 interface.

[0074] Moreover, in connection management, it can also be divided into CM state in 3GPP access and CM state in non-3GPP access for management. In this case, as the CM state in 3GPP access, there can be a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over3GPP access). Moreover, as the CM state in non-3GPP access, there can be a non-connected state in non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state in non-3GPP access (CM-CONNECTEDstate over non-3GPP access). It should be noted that the non-connected state can be expressed as an idle mode, and the connected state mode can be expressed as a connected mode.

[0075] It should be noted that the CM state can also be expressed as 5GMM mode (5GMM mode). In this case, the non-connected state can also be expressed as 5GMM non-connected mode (5GMM-IDLE mode), and the connected state can also be expressed as 5GMM connected mode (5GMM-CONNECTED mode). Moreover, the non-connected state in 3GPP access can also be expressed as 5GMM non-connected mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access can also be expressed as 5GMM connected mode in 3GPP access (5GMM-CONNECTED mode over 3GPP access). Moreover, the non-connected state in non-3GPP access can also be expressed as 5GMM non-connected mode in non-3GPP access (5GMM-IDLE modeover non-3GPP access), and the connected state in non-3GPP access can also be expressed as 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). It should be noted that the 5GMM non-connected mode can be expressed as an idle mode, and the 5GMM connected mode can be expressed as a connected mode.

[0076] In addition, more than one AMF can be configured in the core network_B. In addition, AMF can be an NF that manages more than one NSI (Network Slice Instance). In addition, AMF can also be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among multiple NSIs.

[0077] It should be noted that N3IWF is a device and / or function configured between non-3GPP access and 5GC when the UE is connected to 5GS via non-3GPP access.

[0078] [2.4. SMF device configuration]

[0079] Next, use Figure 5 An example of the device configuration of SMF is described. SMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. SMF can be a node that processes the control plane.

[0080] The control unit_B700 is a functional unit that controls the entire operation and function of the SMF. The control unit_B700 reads various programs stored in the storage unit_B740 as needed and executes them to realize various processes in the SMF.

[0081] The network connection unit_B720 is a functional unit for connecting the SMF with the AMF and / or UPF and / or PCF and / or UDM. That is, the SMF can use the network connection unit_B720 to send and receive user data and / or control information between the AMF and / or UPF and / or PCF and / or UDM.

[0082] Reference Figure 2 To explain in detail, the SMF in 5GC can communicate with AMF via the N11 interface by using the network connection part _A620, can communicate with UPF via the N4 interface, can communicate with PCF via the N7 interface, and can communicate with UDM via the N10 interface.

[0083] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of SMF.

[0084] SMF has the following functions: session management (SessionManagement) functions such as establishment, modification, and release of PDU sessions, IP address allocation (IP address allocation) and its management functions for UE, UPF selection and control functions, UPF setting functions for routing services to the appropriate destination (sending destination), functions for sending and receiving the SM part of NAS messages, functions for notifying that downlink data has arrived (Downlink Data Notification), functions for providing AN-specific (each AN's) SM information sent to AN via AMF through the N2 interface, functions for determining the SSC mode (Session and Service Continuity mode) for the session, and roaming functions, etc.

[0085] [2.5. UPF device configuration]

[0086] Next, use Figure 5 An example of the device configuration of UPF is described. UPF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. UPF can be a node that processes the control plane.

[0087] The control unit_B700 is a functional unit that controls the overall operation and functions of the UPF. The control unit_B700 implements various processes in the UPF by reading various programs stored in the storage unit_B740 as needed and executing them.

[0088] The network connection unit_B720 is a functional unit for connecting the UPF to the base station device (gNB) and / or SMF and / or DN in the 5G AN. That is, the UPF can use the network connection unit_B720 to send and receive user data and / or control information between the base station device (gNB) and / or SMF and / or DN in the 5G AN.

[0089] Reference Figure 2 To explain in detail, the UPF in 5GC can communicate with gNB via the N3 interface by using the network connection part _A620, can communicate with SMF via the N4 interface, can communicate with DN via the N6 interface, and can communicate with other UPFs via the N9 interface.

[0090] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of UPF.

[0091] UPF has the following functions: serving as an anchor point for intra-RAT mobility or inter-RAT mobility, serving as an external PDU session point for interconnecting with DN (that is, serving as a gateway between DN and core network_B to transmit user data), routing and transmission of packets, UL CL (Uplink Classifier) ​​function that supports routing of multiple service flows for one DN, branching point function that supports multi-homed PDU sessions, QoS (Quality of Service) processing function for user plane, verification function of uplink services, triggering buffering of downlink packets, downlink data notification function, etc.

[0092] In addition, UPF can be a gateway for IP communication and / or non-IP communication. In addition, UPF can have the function of transmitting IP communication, and can also have the function of converting non-IP communication and IP communication. Moreover, the configured multiple gateways can be gateways connecting the core network_B and a single DN. It should be noted that UPF can have connectivity with other NFs, and can also be connected to each device via other NFs.

[0093] It should be noted that the user plane is user data sent and received between the UE and the network. The user plane can use a PDN connection or a PDU session for transmission and reception. Moreover, in the case of EPS, the user plane can also use the LTE-Uu interface and / or the S1-U interface and / or the S5 interface and / or the S8 interface and / or the SGi interface for transmission and reception. Moreover, in the case of 5GS, the user plane can also be transmitted and received via the interface between the UE and the NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. In the following, the user plane may also be expressed as U-Plane.

[0094] Moreover, the control plane is a control message sent and received for communication control of the UE, etc. The control plane can use the NAS (Non-Access-Stratum) signaling connection between the UE and the MME for transmission and reception. Moreover, in the case of EPS, the control plane can also use the LTE-Uu interface and the S1-MME interface for transmission and reception. Moreover, in the case of 5GS, the control plane can also use the interface between the UE and the NG RAN and the N2 interface for transmission and reception. In the following, the control plane can also be expressed as Control Plane, and can also be expressed as C-Plane.

[0095] Furthermore, the user plane (U-Plane, User Plane; UP) may be a communication path for sending and receiving user data, and may be composed of multiple bearers. Furthermore, the control plane (C-Plane, Control Plane; CP) may be a communication path for sending and receiving control messages, and may be composed of multiple bearers. [2.6. Description of other devices and / or functions]

[0096] Next, other devices and / or functions are described.

[0097] PCF has the function of providing policy rules, etc.

[0098] In addition, UDM has the following functions: authentication credential processing function, user identification processing function, access authentication function, login / mobility management function, subscriber information management (subscription management) function, etc.

[0099] In addition, PCRF has functions such as connecting with PGW and / or PDN to perform QoS management for data distribution. For example, it manages the QoS of the communication path between UE_A10 and PDN. Moreover, PCRF can be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used by each device when sending and receiving user data.

[0100] In addition, the HSS has functions such as connecting to the MME and / or SCEF and managing subscriber information. The subscriber information of the HSS is referenced, for example, during access control by the MME. Furthermore, the HSS can be connected to a location management device different from the MME.

[0101] In addition, the SCEF has the function of connecting with the DN and / or PDN, MME, and HSS, and serving as a relay device for connecting the DN and / or PDN and the gateway of the core network_A to transmit user data. It should be noted that the SCEF can be a gateway for non-IP communication. Moreover, the SCEF can have the function of converting non-IP communication and IP communication. In addition, multiple such gateways can be configured for the core network_A. The SCEF can be constructed on the outside of the core network, or on the inside.

[0102] [3. Description of terms, identification information, and processes used in each embodiment]

[0103] At least one term, identification information, and process used in each embodiment will be described in advance.

[0104] [3.1. Description of terms and identification information used in each embodiment]

[0105] First, highly specialized terms used in each embodiment and identification information used in the process will be described in advance.

[0106] The network refers to at least a part of the access network_B, the core network_B, and the DN. In addition, one or more devices included in at least a part of the access network_B, the core network_B, and the DN may also be referred to as a network or a network device. That is, the network performing the sending, receiving, and / or processing of messages may mean that a device (network device and / or control device) in the network performs the sending, receiving, and / or processing of messages. Conversely, the device in the network performing the sending, receiving, and / or processing of messages may mean that the network performs the sending, receiving, and / or processing of messages.

[0107] In addition, the SM (session management) message (also called NAS (Non-Access-Stratum) SM message) can be a NAS message used in the process of SM use, or a control message sent and received between UE_A10 and SMF_A230 via AMF_A240. Moreover, the SM message may include a PDU session establishment request message, a PDU session establishment acceptance message, a PDU session completion message, a PDU session rejection message, a PDU session change request message, a PDU session change acceptance message, a PDU session change response message, etc. In addition, the process of SM use may include a PDU session establishment process.

[0108] In addition, 5GS (5G System) service may be a connection service provided using core network B190. Moreover, 5GS service may be a service different from EPS service or the same as EPS service.

[0109] In addition, non-5GS services may be services other than 5GS services, and may also include EPS services and / or non-EPS services.

[0110] In addition, the single registration mode is a mode in which a common login state for the 5GMM state and the EMM state is maintained when UE_A10 can utilize the N1 mode and the S1 mode.

[0111] In addition, the single registration mode is a mode in which a common login state for the 5GMM state and the EMM state is maintained when UE_A10 can utilize the N1 mode and the S1 mode.

[0112] In addition, the S1 mode is a mode in which UE_A10 is allowed to access the EPC via the E-UTRAN. In other words, the S1 mode may also be a mode in which messages using the S1 interface are sent and received. It should be noted that the S1 interface may be composed of an S1-MME interface and an S1-U interface.

[0113] In addition, the N1 mode is a mode in which UE_A10 is allowed to access the 5GC via the 5G access network. In other words, the N1 mode may also be a mode in which messages using the N1 interface are sent and received.

[0114] In addition, APN (Access Point Name) can be identification information for identifying a core network and / or an external network such as a PDN, etc. Furthermore, APN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 connected to the core network A_90.

[0115] In addition, TFT (Traffic Flow Template) means that TFT represents all packet filters associated with the EPS bearer. TFT is information that identifies a part of the user data being sent and received, and UE_A10 uses the EPS bearer associated with TFT to send and receive user data identified by TFT. In other words, UE_A10 uses the RB (Radio Bearer) associated with TFT to send and receive user data identified by TFT. In addition, TFT can correspond user data such as application data sent and received to an appropriate transmission path, and can be identification information that identifies the application data. In addition, UE_A10 can use the default bearer to send and receive user data that cannot be identified by TFT. In addition, UE_A10 can pre-store the TFT associated with the default bearer.

[0116] In addition, the PDN (Packet Data Network) type indicates the type of PDN connection, which includes IPv4, IPv6, IPv4v6, and non-IP. When IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is sent and received using IPv6. When IPv4v6 is specified, it indicates that data is sent and received using IPv4 or IPv6. When non-IP is specified, it indicates that communication is performed not only by communication using IP, but also by communication methods other than IP.

[0117] In addition, the EPS bearer is a logical communication path established between the UE and the PGW, and is a communication path that constitutes a PDN connection. There are default bearers (also called default EPS bearers) and dedicated bearers (also called dedicated EPS bearers) in the EPS bearer.

[0118] In addition, the default bearer is an EPS bearer initially established in a PDN connection, and only one can be established in one PDN connection. The default bearer is an EPS bearer that can be used in the communication of user data that is not associated with a TFT (Traffic Flow Template).

[0119] In addition, a dedicated bearer is an EPS bearer established after a default bearer is established in a PDN connection, and more than one can be established in one PDN connection. A dedicated bearer is an EPS bearer that can be used in communication of user data corresponding to a TFT.

[0120] In addition, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between a DN and a UE that provides a PDU connectivity service, but can also be a connectivity established between a UE and an external gateway. The UE can use a PDU session to send and receive user data with the DN by establishing a PDU session via the access network_B and the core network_B in the 5GS. Here, the external gateway may refer to a UPF, a SCEF, etc. The UE can use a PDU session to send and receive user data with a device such as an application server configured in the DN.

[0121] It should be noted that each device (UE and / or access network device and / or core network device) may also manage one or more identification information corresponding to the establishment of a PDU session. It should be noted that these identification information may include one or more of DNN, TFT, PDU session type, application identification information, NSI identification information, access network identification information and SSC mode, and may further include other information. Moreover, in the case of establishing multiple PDU sessions, the identification information corresponding to the establishment of the PDU sessions may be the same content or different content.

[0122] In addition, DNN (Data Network Name) can be identification information for identifying a core network and / or an external network such as a DN. Furthermore, DNN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 connected to the core network B190. Furthermore, DNN can be equivalent to APN (Access Point Name).

[0123] In addition, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, which includes IPv4, IPv6, Ethernet, and Unstructured. When IPv4 is specified, it means that IPv4 is used to send and receive data. When IPv6 is specified, it means that IPv6 is used to send and receive data. When Ethernet is specified, it means that Ethernet frames are sent and received. In addition, Ethernet can indicate that communication without using IP is performed. When Unstructured is specified, it means that Point-to-Point (P2P) tunnel technology is used to send and receive data to an application server in the DN. As a P2P tunnel technology, for example, UDP / IP encapsulation technology can also be used. It should be noted that IP can be included in the above-mentioned others in the PDU session type. IP can be specified when the UE can use both IPv4 and IPv6.

[0124] In addition, a network slice (NS) refers to a logical network that provides specific network capabilities and network characteristics. UE and / or network can support network slicing (NW slicing; NS) in 5GS.

[0125] In addition, a network slice instance (NSI) refers to a network slice formed and configured by a collection of instances (entities) of network functions (NFs) and required resources. Here, NF refers to a processing function in a network, which is adopted or defined in 3GPP. NSI is an entity that constitutes one or more NSs in the core network_B. In addition, NSI can be composed of a virtual NF (Network Function) generated using NST (Network Slice Template). Here, NST refers to a logical expression of one or more NFs associated with a resource request for providing the requested communication service and capability. That is, NSI may refer to an aggregate within the core network_B190 composed of multiple NFs. In addition, NSI may be a logical network configured to divide the user data sent according to services, etc. More than one NF may be configured in the NS. The NF configured in the NS may be a device shared with other NSs, or may not be a device shared with other NSs. The UE and / or the device in the network can be assigned to one or more NSs based on the login information such as NSSAI and / or S-NSSAI and / or UE usage type (UE usage type) and / or one or more NSI IDs and / or APN. It should be noted that the UE usage type is a parameter value included in the login information of the UE for identifying the NSI. The UE usage type can be stored in the HSS. The AMF can select the SMF and UPF based on the UE usage type.

[0126] In addition, S-NSSAI (Single Network Slice Selection Assistance information) is information used to identify NS. S-NSSAI can be composed of only SST (Slice / Servicetype: slice / service type), or it can be composed of both SST and SD (Slice Differentiator: slice differentiator). Here, SST refers to information indicating the expected actions of NS in terms of functions and services. In addition, SD can be information that interpolates SST when selecting an NSI from multiple NSIs shown in SST. S-NSSAI can be information specific to each PLMN, or it can be standard information common among PLMNs. In addition, the network can store more than one S-NSSAI in the UE's login information as the default S-NSSAI. It should be noted that when the S-NSSAI is the default S-NSSAI, the network can provide NS related to the UE when the UE does not send a valid S-NSSAI to the network in the login request message.

[0127] In addition, NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Each S-NSSAI included in NSSAI is information for assisting the access network or core network to select NSI. The UE can store the NSSAI allowed by the network for each PLMN. In addition, NSSAI can be information for selecting AMF.

[0128] In addition, the SSC (Session and Service Continuity) mode represents the mode of session service continuity (Session and Service Continuity) supported by the system and / or each device in the 5G system (5GS). In more detail, it can be a mode that represents the type of session service continuity supported by the PDU session established between UE_A10 and UPF. It should be noted that the SSC mode (SSC mode) can also be a mode that represents the type of session service continuity set for each PDU session. Moreover, the SSC mode can be composed of three modes: SSC mode 1, SSC mode 2, and SSC mode 3. It should be noted that the SSC mode corresponding to the PDU session may not change during the duration of the PDU session.

[0129] In addition, SSC mode 1 is a mode in which the network maintains connectivity services provided to UE_A 10. It should be noted that, when the PDU session type corresponding to the PDU session is IPv4 or IPv6, the IP address can be maintained while the session service continues.

[0130] Moreover, regardless of the access technology used when UE_A10 is connected to the network, SSC mode 1 can be a session service continuity mode that continuously maintains the same UPF. More specifically, SSC mode 1 can be a mode that achieves session service continuity without changing the UPF used as the PDU session anchor of the established PDU session even if UE_A10 moves.

[0131] In addition, SSC mode 2 is a mode in which the network releases the connectivity service and the corresponding PDU session provided to UE_A10. It should be noted that in SSC mode 2, the IP address allocated to UE_A10 can also be released when the anchor of the PDU session is changed, when the PDU session type corresponding to the PDU session is IPv4, IPv6 or IPv4v6.

[0132] Furthermore, SSC mode 2 may be a session service continuity mode that continuously maintains the same UPF only within the service area of ​​the UPF. More specifically, SSC mode 2 may be a mode that implements session service continuity without changing the UPF used for the established PDU session as long as UE_A10 is within the service area of ​​the UPF. Furthermore, when UE_A10 moves, such as leaving the service area of ​​the UPF, SSC mode 2 may be a mode that implements session service continuity by changing the UPF used for the established PDU session.

[0133] Here, the service area of ​​the UPF may be an area where the UPF can provide session service continuity functions, or may be a subset of access networks such as RATs and cells used when the UE_A10 is connected to the network. Moreover, a subset of the access network may refer to a network consisting of one or more RATs and / or cells.

[0134] It should be noted that the change of the anchor point of the PDU session in SSC mode 2 can be achieved by each device executing the anchor point change process of the PDU session in SSC mode 2.

[0135] In addition, SSC mode 3 is a mode in which the network ensures that connectivity is not lost and makes UE_A10 aware of changes in the user plane. It should be noted that in the case of SSC mode 3, a PDU session through a new PDU session anchor point can be established before disconnecting the established PDU session to achieve better connectivity services. Moreover, in SSC mode 3, when the PDU session type corresponding to the PDU session is IPv4, IPv6 or IPv4v6, the IP address assigned to the UE is not maintained when the anchor of the PDU session is changed.

[0136] Furthermore, SSC mode 3 may also be a session service continuity mode that allows a new PDU session and / or communication path to be established via a new UPF for the same DN before disconnecting the PDU session and / or communication path established between UE_A10 and UPF. Furthermore, SSC mode 3 may also be a session service continuity mode that allows UE_A10 to be multi-homed. Furthermore, SSC mode 3 may also be a session service continuity mode that allows the use of multiple PDU sessions and / or UPFs corresponding to the PDU sessions. In other words, in the case of SSC mode 3, each device may use multiple PDU sessions to achieve session service continuity, and may also use multiple UPFs to achieve session service continuity.

[0137] Here, when each device establishes a new PDU session and / or communication path, the selection of a new UPF can be implemented by the network, and the new UPF can be the UPF that best suits the location where UE_A10 is connected to the network. In addition, when multiple PDU sessions and / or UPFs used by PDU sessions are valid, UE_A10 can immediately implement the correspondence between the communication of the application and / or flow and the newly established PDU session, or can implement it based on the completion of the communication.

[0138] It should be noted that the change of the anchor point of the PDU session in SSC mode 3 can be achieved by each device executing the anchor point change process of the PDU session in SSC mode 3.

[0139] In addition, in the case where a specific SSC mode is not determined, the default SSC mode is the SSC mode used by UE_A10 and / or the network. Specifically, in the case where there is no request for an SSC mode from an application and / or there is no policy of UE_A10 for determining an SSC mode for an application, the default SSC mode may be the SSC mode used by UE_A10. In addition, in the case where there is no request for an SSC mode from UE_A10, the default SSC mode may also be the SSC mode used by the network.

[0140] It should be noted that the default SSC mode can be set for each DN based on subscriber information and / or operator policy and / or UE_A10 policy, can be set for each PDN, can be set for each UE_A10 and / or subscriber. Moreover, the default SSC mode can be information indicating SSC mode 1, SSC mode 2, or SSC mode 3.

[0141] The anchor point change process of the PDU session is the process of switching the PDU session used for sending and receiving user data from the first PDU session to the second PDU session. The anchor point change process of the PDU session can include the anchor point change process of the PDU session of SSC mode 2 and the anchor point change process of the PDU session of SSC mode 3.

[0142] Here, the first PDU session may be a PDU session used for user data communication before the anchor point of the PDU session is changed. The second PDU session may be a PDU session used for user data communication after the anchor point of the PDU session is changed.

[0143] The anchor point change process of the PDU session of SSC mode 2 is a process of establishing a second PDU session after releasing the first PDU session. The anchor point change process of the PDU session of SSC mode 2 can be a network-led process.

[0144] Specifically, the anchor point change process of the PDU session in SSC mode 2 may be that when the first PDU session is established, the AMF and / or SMF sends a PDU session release command message to the UE, and then the UE that receives the PDU session release command message starts the PDU session establishment process, thereby performing the process of establishing the second PDU session.

[0145] It should be noted that information indicating the change of the anchor point of the PDU session may be added to the PDU session release command message. Moreover, the information indicating the change of the anchor point of the PDU session may be a reactivation request as the 39th 5GSM reason value (5GSMcause#39).

[0146] Moreover, in the PDU session establishment process for establishing the second PDU session, the PDU session establishment request message sent from the UE to the AMF and / or SMF and / or the NAS message sent and received for transmitting the PDU session establishment request message may include a PDU session ID identifying the first PDU session and a PDU session ID identifying the second PDU session. Moreover, the PDU session type, SSC mode, DNN and S-NSSAI sent and received in the PDU session establishment process for establishing the second PDU session may be the same as the PDU session type, SSC mode, DNN and S-NSSAI sent and received in the PDU session establishment process for establishing the first PDU session.

[0147] The anchor point change process of the PDU session of SSC mode 3 is a process of establishing a second PDU session before releasing the first PDU session. The anchor point change process of the PDU session of SSC mode 3 can be a network-led process.

[0148] Specifically, the anchor point change process of the PDU session in SSC mode 3 may be that when the first PDU session is established, the AMF and / or SMF sends a PDU session change command (PDU session modification command) message to the UE, and then the UE that receives the PDU session change command message starts the PDU session establishment process, thereby performing the process of establishing the second PDU session.

[0149] It should be noted that information indicating the change of the anchor point of the PDU session may be added to the PDU session change command message. Furthermore, the information indicating the change of the anchor point of the PDU session may be a reactivation request as the 39th 5GSM reason value (5GSMcause#39).

[0150] Moreover, in the PDU session establishment process for establishing the second PDU session, the PDU session establishment request message sent from the UE to the AMF and / or SMF and / or the NAS message sent and received for transmitting the PDU session establishment request message may include a PDU session ID identifying the first PDU session and a PDU session ID identifying the second PDU session. Moreover, the PDU session type, SSC mode, DNN and S-NSSAI sent and received in the PDU session establishment process for establishing the second PDU session may be the same as the PDU session type, SSC mode, DNN and S-NSSAI sent and received in the PDU session establishment process for establishing the first PDU session.

[0151] In addition, SSC mode 4 is an SSC mode different from SSC mode 1, SSC mode 2, and SSC mode 3, and is an SSC mode that can achieve session service continuity by changing the anchor point of the PDU session. It should be noted that in SSC mode 4, when the PDU session type corresponding to the PDU session is IPv4, IPv6, or IPv4v6, the IP address assigned to the UE can be maintained when the anchor of the PDU session is changed.

[0152] In other words, SSC mode 4 may be an SSC mode that maintains the IP address assigned to the UE even when the anchor point change procedure of the PDU session of SSC mode 2 is performed. In addition, SSC mode 4 may be an SSC mode that maintains the IP address assigned to the UE even when the anchor point change procedure of the PDU session of SSC mode 3 is performed.

[0153] It should be noted that SSC mode 4 is not limited to these, and any SSC mode may be used as long as it is different from SSC mode 1, SSC mode 2, and SSC mode 3.

[0154] The tracking area of ​​this embodiment is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. The tracking area can be composed of multiple cells. Moreover, the tracking area can be the range of control messages such as broadcast paging, or the range in which UE_A10 can move without performing a switching process. Moreover, the tracking area can be a routing area or a location area, as long as it is the same area as these areas. Below, the tracking area can also be TA (Tracking Area).

[0155] The TA list of this embodiment is a list of one or more TAs assigned to UE_A10 by the network. It should be noted that UE_A10 can move without performing a tracking area update procedure while moving within one or more TAs included in the TA list. In other words, in UE_A10, the TA list may be an information group indicating an area in which UE_A10 can move without performing a tracking area update procedure. It should be noted that the TA list may also be expressed as a TAI list consisting of one or more TAIs (Tracking area identities). Hereinafter, the TAI list may also refer to the TA list.

[0156] LADN (Local Area Data Network) refers to a DN that can connect to the UE only under specific circumstances, providing connectivity for a specific DNN (that is, LADN DNN).

[0157] LADN information is information associated with LADN. LADN information can be information indicating a specific LADN that the UE can utilize. LADN information can include LADN DNN and LADN service area information (LADN service area information). LADN DNN can be a type of DNN, or it can be a DNN used when establishing a PDU session for LADN. Moreover, LADN DNN can be information indicating LADN, or it can be information indicating a DN processed as LADN. Moreover, LADN service area information can be information indicating a LADN service area (LADN service area). Moreover, LADN service area information can be provided as a set of tracking areas, or it can be provided as a TAI (Tracking area identity) list (list). It should be noted that the LADN service area can be an area where a PDU session for LADN can be established, or it can be an area that can be connected to LADN.

[0158] The PDU session for LADN is a PDU session that establishes a corresponding PDU session with the DNN that has established an association with the LADN. The PDU session for LADN can be a PDU session established for the LADN. In other words, it can be a PDU session established between the UE and the LADN, or it can be a PDU session used for user data communication between the UE and the LADN. It should be noted that the PDU session for LADN can be a PDU session that can only be established in the LADN service area.

[0159] NB-IoT (Narrowband IoT) is a RAT (Radio Access Technology) with limited frequency band. NB-IoT can be a RAT for providing communication services to IoT terminals, or a RAT with some functions restricted. Moreover, NB-IoT can be a RAT constituting E-UTRAN. It should be noted that the RAT constituting E-UTRAN other than NB-IoT may be WB-E-UTRAN. Moreover, the mode of UE connected to the core network and / or DN using NB-IoT can be expressed as NB-N1 mode. Conversely, the mode of UE connected to the core network and / or DN using RAT other than NB-IoT can also be expressed as WB-N1 mode.

[0160] A multi-homed PDU Session is a PDU Session established using multiple UPFs connected to a DN. A multi-homed PDU Session can be a PDU Session established for a single DN or for different DNs. Moreover, a multi-homed PDU Session can be expressed as a multi-homed IPv6 PDU Session.

[0161] URLLC (Ultra-Reliable and Low Latency Communications) is a communication that achieves high reliability and / or low latency. URLLC may be one of the main communication services provided in 5GS. As functions constituting URLLC, there may be redundant communication and IP address maintenance. It should be noted that supporting URLLC may mean supporting redundant communication or supporting IP address maintenance. Moreover, supporting URLLC may mean continuing communication of user data using the same IP address even when the anchor point of the PDU session changes. Moreover, supporting URLLC may mean supporting the establishment of a corresponding QoS process with the 5QI (5G QoS Identifier) ​​for URLLC, or supporting the QoS rules corresponding to the QoS process, or establishing a PDU session corresponding to the QoS rules.

[0162] Redundant transmission is a communication in which the transmission and reception of user data are redundant. Redundant communication can be one of the technologies for implementing URLLC. Moreover, redundant communication can be a communication with higher reliability than that using a single user plane tunnel. It should be noted that the user plane tunnel can be a transmission path for transmitting and receiving user data between devices, or it can be a transmission path established on an interface for implementing the transmission and reception of user data.

[0163] Here, the redundant communication may include a first type of redundant communication, a second type of redundant communication, and a third type of redundant communication.

[0164] The first type of redundant communication is communication in which the transmission and reception of user data between the UE and the network is redundant by using multiple communication paths via different access networks. The UE can implement the first type of redundant communication by using multiple IP addresses.

[0165] Here, the first type of redundant communication can be implemented through multiple PDU sessions. In this case, the UE can implement the first type of redundant communication by using multiple PDU sessions established via different access networks. In other words, the UE can implement the first type of redundant communication by using multiple PDU session IDs.

[0166] In addition, the first type of redundant communication can be implemented through a single PDU session. In more detail, the first type of redundant communication can be implemented through a multi-access PDU session. In this case, the UE can implement the first type of redundant communication by using a single PDU session. In other words, the UE can implement the first type of redundant communication by using a single PDU session ID.

[0167] The second type of redundant communication is communication in which transmission and reception of user data between the UE and the network is redundant by using multiple communication paths via a single access network. The UE can implement the second type of redundant communication by using multiple IP addresses.

[0168] Here, the second type of redundant communication can be implemented through multiple PDU sessions. In this case, the UE can implement the second type of redundant communication by using multiple PDU sessions established via a single access network. In other words, the UE can implement the second type of redundant communication by using multiple PDU session IDs.

[0169] In addition, the second type of redundant communication can be implemented through a single PDU session. In more detail, the second type of redundant communication can be implemented through a multi-homing PDU session. In this case, the UE can implement the second type of redundant communication by using a single PDU session. In other words, the UE can implement the second type of redundant communication by using a single PDU session ID.

[0170] The third type of redundant communication is a communication in which the transmission and reception of user data between the access network or the core network and the network is redundant. The UE can implement the third type of redundant communication by using a single IP address.

[0171] Here, the third type of redundant communication can be implemented through a single PDU session. In this case, the UE can implement the third type of redundant communication by using a single PDU session. In other words, the UE can implement the third type of redundant communication by using a single PDU session ID.

[0172] IP address preservation is a technology that enables the continued use of the same IP address. When IP address preservation is supported, the UE can continue to use the same IP address for user data communications even when it moves outside the TA. In other words, when IP address preservation is supported, each device can continue to use the same IP address for user data communications even when the anchor point of the PDU session changes.

[0173] The first identification information is information indicating whether the UE supports URLLC. The first identification information may also be information represented by bits constituting a 5GMM capability information element representing the capabilities of the UE in 5G. Moreover, the first identification information may also be information selected and determined based on the UE settings and / or the UE status and / or the user policy and / or the application request.

[0174] Furthermore, the first identification information may be information including one or more meanings indicated by one or more identification information among the second to sixth identification information. In other words, the first identification information may be information composed of one or more identification information among the second to sixth identification information. Furthermore, the first to sixth identification information may be sent and received as different identification information or as one identification information.

[0175] The second identification information is information indicating whether the UE supports redundant communication. The second identification information may also be information represented by bits constituting a 5GMM capability information element representing the capability of the UE in 5G. Moreover, the second identification information may also be information selected and determined based on the UE setting and / or the UE status and / or the user policy and / or the request of the application.

[0176] Moreover, the second identification information may be information indicating which type of redundant communication is supported. For example, the second identification information may be information indicating support for the first type of redundant communication, information indicating support for the second type of redundant communication, or information indicating support for the third type of redundant communication.

[0177] Furthermore, the second identification information may be information including one or more meanings indicated by one or more identification information among the third to fifth identification information. In other words, the second identification information may be information composed of one or more identification information among the third to fifth identification information. Furthermore, the second to fifth identification information may be sent and received as different identification information or as one identification information.

[0178] The third identification information is information indicating whether the UE supports the first type of redundant communication. The third identification information may also be information represented by bits constituting a 5GMM capability information element representing the capability of the UE in 5G. Moreover, the third identification information may also be information selected and determined based on the UE setting and / or the UE status and / or the user policy and / or the request of the application.

[0179] The fourth identification information is information indicating whether the UE supports the second type of redundant communication. The fourth identification information may also be information represented by bits constituting a 5GMM capability information element representing the capability of the UE in 5G. Moreover, the fourth identification information may also be information selected and determined based on the UE setting and / or the UE status and / or the user policy and / or the request of the application.

[0180] The fifth identification information is information indicating whether the UE supports the third type of redundant communication. The fifth identification information may also be information represented by bits constituting a 5GMM capability information element representing the capability of the UE in 5G. Moreover, the fifth identification information may also be information selected and determined based on the UE setting and / or the UE status and / or the user policy and / or the request of the application.

[0181] The sixth identification information is information indicating whether the UE supports IP address maintenance. The sixth identification information may also be information represented by bits constituting a 5GMM capability information element representing the capabilities of the UE in 5G. Moreover, the sixth identification information may also be information selected and determined based on the UE settings and / or the UE status and / or the user policy and / or the application request.

[0182] The eleventh identification information is information indicating whether the network supports URLLC. The eleventh identification information may also be information represented by bits constituting a 5GS network feature support information element representing the capabilities of the network in 5G. Moreover, the eleventh identification information may also be information selected and determined by the network based on the received first identification information and / or information corresponding to the DN and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information, etc. Moreover, the eleventh identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0183] Furthermore, the eleventh identification information may be information including one or more meanings indicated by one or more identification information among the twelfth to sixteenth identification information. In other words, the eleventh identification information may be information composed of one or more identification information among the twelfth to sixteenth identification information. Furthermore, the eleventh to sixteenth identification information may be sent and received as different identification information or as one identification information.

[0184] The twelfth identification information is information indicating whether the network supports redundant communication. The twelfth identification information may also be information represented by bits constituting a 5GS network function support information element representing the capabilities of the network in 5G. Moreover, the twelfth identification information may also be information selected and determined by the network based on one or more of the identification information received from the second to fifth identification information and / or information corresponding to the DN and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information, etc. Moreover, the twelfth identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0185] Moreover, the twelfth identification information may be information indicating which type of redundant communication is supported. For example, the twelfth identification information may be information indicating support for the first type of redundant communication, or information indicating support for the second type of redundant communication, or information indicating support for the third type of redundant communication.

[0186] Furthermore, the twelfth identification information may be information including one or more meanings indicated by one or more identification information among the thirteenth to fifteenth identification information. In other words, the twelfth identification information may be information composed of one or more identification information among the thirteenth to fifteenth identification information. Furthermore, the twelfth to fifteenth identification information may be sent and received as different identification information or as one identification information.

[0187] The thirteenth identification information is information indicating whether the network supports the first type of redundant communication. The thirteenth identification information may also be information represented by bits constituting a 5GS network function support information element representing the capabilities of the network in 5G. Moreover, the thirteenth identification information may also be information selected and determined by the network based on one or more of the identification information received from the second to fifth identification information and / or information corresponding to the DN and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information, etc. Moreover, the thirteenth identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0188] The fourteenth identification information is information indicating whether the network supports the second type of redundant communication. The fourteenth identification information may also be information represented by bits constituting a 5GS network function support information element representing the capabilities of the network in 5G. Moreover, the fourteenth identification information may also be information selected and determined by the network based on one or more of the identification information received from the second to fifth identification information and / or information corresponding to the DN and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information. Moreover, the fourteenth identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0189] The fifteenth identification information is information indicating whether the network supports the third type of redundant communication. The fifteenth identification information may also be information represented by bits constituting a 5GS network function support information element representing the capabilities of the network in 5G. Moreover, the fifteenth identification information may also be information selected and determined by the network based on one or more of the identification information received from the second to fifth identification information and / or information corresponding to the DN and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information, etc. Moreover, the fifteenth identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0190] The sixteenth identification information is information indicating whether the network supports IP address maintenance. The sixteenth identification information may also be information represented by bits constituting a 5GS network function support information element representing the capabilities of the network in 5G. Moreover, the sixteenth identification information may also be information selected and determined by the network based on the received sixth identification information and / or information corresponding to the DN and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information, etc. Moreover, the sixteenth identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0191] The seventeenth identification information is LADN information. The seventeenth identification information may be LADN information permitted by the network or valid LADN information. Furthermore, the seventeenth identification information may be information sent and received when a LADN service area exists in the registration area to which the UE is connected.

[0192] Furthermore, the seventeenth identification information may also be information selected and determined by the network based on one or more of the received first to sixth identification information and / or information corresponding to the DN and / or network capability information and / or operator policy and / or network status and / or user login information, etc. Furthermore, the seventeenth identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0193] Moreover, the LADN DNN included in the seventeenth identification information may be information for identifying a DN supporting URLLC, information for identifying a DN supporting redundant communication, or information for identifying a DN supporting IP address maintenance. In more detail, the LADN DNN included in the seventeenth identification information may be information for identifying a DN supporting the first type of redundant communication, information for identifying a DN supporting the second type of redundant communication, or information for identifying a DN supporting the third type of redundant communication.

[0194] The twenty-first identification information is information indicating whether URLLC is supported in the PDU session established in this process. The twenty-first identification information may also be information indicating a request to establish a PDU session that supports URLLC. Moreover, the twenty-first identification information may also be information selected and determined based on one or more identification information among the eleventh to seventeenth identification information that have been sent and received and / or the setting of the UE and / or the status of the UE and / or the user policy and / or the request of the application. Moreover, the twenty-first identification information may be information including one or more meanings indicated by one or more identification information among the twenty-second to twenty-fourth identification information. In other words, the twenty-first identification information may be information composed of one or more identification information among the twenty-second to twenty-fourth identification information. In addition, the twenty-second to twenty-fourth identification information may be sent and received as different identification information, or may be sent and received as one identification information.

[0195] The twenty-second identification information is information indicating whether redundant communication is supported in the PDU session established in this process. The twenty-second identification information may also be information indicating a request to establish a PDU session that supports redundant communication. Moreover, the twenty-second identification information may also be information selected and determined based on one or more of the identification information from the eleventh to seventeenth identification information that has been sent and received and / or the setting of the UE and / or the status of the UE and / or the user policy and / or the request of the application.

[0196] The twenty-third identification information is information indicating the type of redundant communication. The twenty-third identification information may also be information indicating the type of redundant communication requested by the UE. In more detail, the twenty-third identification information may also be information indicating the type of redundant communication requested by the UE corresponding to the PDU session established in this process. It should be noted that the twenty-third identification information may be information indicating the first type of redundant communication, information indicating the second type of redundant communication, or information indicating the third type of redundant communication. Moreover, the twenty-second identification information may also be information selected and determined based on one or more of the identification information among the eleventh to seventeenth identification information that have been sent and received and / or the UE settings and / or the UE status and / or the user policy and / or the request of the application.

[0197] The twenty-fourth identification information is information indicating whether IP address maintenance is supported in the PDU session established in this process. The twenty-fourth identification information may also be information indicating a request to establish a PDU session that supports IP address maintenance. Moreover, the twenty-fourth identification information may also be information selected and determined based on one or more of the identification information from the eleventh to seventeenth identification information that has been sent and received and / or the UE's settings and / or the UE's status and / or the user policy and / or the request of the application.

[0198] The twenty-fifth identification information is information indicating the SSC mode. The twenty-fifth identification information may also be information indicating the SSC mode requested by the UE. In more detail, the twenty-fifth identification information may also be information indicating the SSC mode requested by the UE corresponding to the PDU session established in this process. It should be noted that the twenty-fifth identification information may be information indicating SSC mode 1, information indicating SSC mode 2, or information indicating SSC mode 3. Moreover, the twenty-fifth identification information may also be information selected and determined based on one or more of the identification information among the eleventh to seventeenth identification information that have been sent and received and / or the UE settings and / or the UE status and / or the user policy and / or the request of the application.

[0199] Furthermore, the twenty-fifth identification information may be information indicating a type of session service continuity different from SSC mode 1, SSC mode 2, and SSC mode 3. For example, the twenty-fifth identification information may be information indicating SSC mode 4.

[0200] The twenty-sixth identification information is information indicating the DNN. The twenty-sixth identification information may also be information indicating the DNN requested by the UE. In more detail, the twenty-sixth identification information may also be information indicating the DNN requested by the UE to establish the corresponding PDU session established in this process. Moreover, the twenty-sixth identification information may also be information selected and determined based on one or more of the identification information among the eleventh to seventeenth identification information sent and received and / or the UE settings and / or the UE status and / or the user policy and / or the request of the application.

[0201] The thirty-first identification information is information indicating whether URLLC is supported in the PDU session established in this process. The thirty-first identification information may also be information indicating the establishment of a PDU session supporting URLLC. Moreover, the thirty-first identification information may also be information indicating that the establishment request of a PDU session supporting URLLC has been delegated.

[0202] Moreover, the thirty-first identification information may also be information selected and determined by the network based on the received twenty-first identification information and / or information corresponding to the DN and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information. Moreover, the thirty-first identification information may also be information selected and determined based on other identification information selected by the network in this process. Moreover, the thirty-first identification information may be information including one or more meanings indicated by one or more identification information in the thirty-second to thirty-fourth identification information. In other words, the thirty-first identification information may be information composed of one or more identification information in the thirty-second to thirty-fourth identification information. In addition, the thirty-second to thirty-fourth identification information may be sent and received as different identification information, or may be sent and received as one identification information.

[0203] The thirty-second identification information is information indicating whether redundant communication is supported in the PDU session established in this process. The thirty-second identification information may also be information indicating that a PDU session supporting redundant communication is established. Furthermore, the thirty-second identification information may also be information indicating that a request to establish a PDU session supporting redundant communication has been delegated.

[0204] Furthermore, the thirty-second identification information may also be information selected and determined by the network based on the received twenty-second identification information and / or the twenty-third identification information and / or the information corresponding to the DN and / or the information corresponding to the NSI and / or the network capability information and / or the operator policy and / or the network status and / or the user login information, etc. Furthermore, the thirty-second identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0205] The thirty-third identification information is information indicating the type of redundant communication. The thirty-third identification information may also be information indicating the type of redundant communication selected by the network. In more detail, the thirty-third identification information may also be information indicating the type of redundant communication selected by the network corresponding to the PDU session established in this process. It should be noted that the thirty-third identification information may be information indicating the first type of redundant communication, may be information indicating the second type of redundant communication, or may be information indicating the third type of redundant communication.

[0206] Furthermore, the thirty-third identification information may also be information selected and determined by the network based on the received twenty-second identification information and / or the twenty-third identification information and / or the information corresponding to the DN and / or the information corresponding to the NSI and / or the network capability information and / or the operator policy and / or the network status and / or the user login information, etc. Furthermore, the thirty-third identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0207] The thirty-fourth identification information is information indicating whether the PDU session established in this process supports IP address maintenance. The thirty-fourth identification information may also be information indicating that a PDU session supporting IP address maintenance is established. Moreover, the thirty-fourth identification information may also be information indicating that a request to establish a PDU session supporting IP address maintenance has been delegated.

[0208] Furthermore, the thirty-fourth identification information may also be information selected and determined by the network based on the received twenty-fourth identification information and / or the twenty-fifth identification information and / or the information corresponding to the DN and / or the information corresponding to the NSI and / or the network capability information and / or the operator policy and / or the network status and / or the user login information, etc. Furthermore, the thirty-fourth identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0209] In addition, the thirty-fifth identification information is information indicating an SSC mode. The thirty-fifth identification information may also be information indicating an SSC mode selected by the network. In more detail, the thirty-fifth identification information may also be information indicating an SSC mode selected by the network corresponding to the PDU session established in this process. It should be noted that the selected SSC mode may be SSC mode 1, SSC mode 2, or SSC mode 3.

[0210] Furthermore, the thirty-fifth identification information may also be information selected and determined by the network based on the received twenty-fourth identification information and / or the twenty-fifth identification information and / or the information corresponding to the DN and / or the information corresponding to the NSI and / or the network capability information and / or the operator policy and / or the network status and / or the user login information, etc. Furthermore, the thirty-fifth identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0211] Furthermore, the thirty-fifth identification information may be information indicating a type of session service continuity different from SSC mode 1, SSC mode 2, and SSC mode 3. For example, the thirty-fifth identification information may be information indicating SSC mode 4.

[0212] In addition, the thirty-sixth identification information is information indicating the DNN. The thirty-sixth identification information may also be information indicating the DNN selected by the network. In more detail, the thirty-sixth identification information may also be information indicating the DNN selected by the network to establish the corresponding PDU session established in this process.

[0213] Furthermore, the thirty-sixth identification information may also be information selected and determined by the network based on the received thirty-sixth identification information and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information, etc. Furthermore, the thirty-sixth identification information may also be information selected and determined based on other identification information selected by the network in this process.

[0214] [3.2. Description of the process used in each embodiment]

[0215] Next, the procedures used in each embodiment are described. It should be noted that the procedures used in each embodiment include a registration procedure, a PDU session establishment procedure, and a Generic UE configuration update procedure. Each procedure is described below.

[0216] It should be noted that, in each embodiment, Figure 2As described in the , the case where HSS and UDM, PCF and PCRF, SMF and PGW-C, UPF and PGW-U are respectively configured as the same device (that is, the same physical hardware, the same logical hardware, or the same software) is used as an example for explanation. However, the content described in this embodiment can also be applied to the case where they are configured as different devices (that is, different physical hardware, different logical hardware, or different software). For example, data can be sent and received directly between them, data can be sent and received via the N26 interface between AMF and MME, and data can be sent and received via UE.

[0217] [3.2.1. Login process]

[0218] First, use Figure 6 The registration procedure is described. The registration procedure is a process in 5GS. Hereinafter, this process refers to the registration procedure. The registration procedure is a process led by the UE to log in to the access network_B and / or the core network_B and / or the DN. If it is not logged in to the network, the UE can perform this procedure at any timing, such as when the power is turned on. In other words, if it is in a non-registered state (RM-DEREGISTERED state), the UE can start this procedure at any timing. In addition, each device (especially the UE and AMF) can transition to the registered state (RM-REGISTERED) based on the completion of the registration procedure.

[0219] Moreover, the registration process may be a process for updating location registration information of the UE in the network and / or periodically notifying the network of the status of the UE from the UE and / or updating specific parameters related to the UE in the network.

[0220] The UE can start the login process when moving across TAs. In other words, the UE can start the login process when it moves to a TA that is different from the TA shown in the maintained TA list. Moreover, the UE can also start this process when the executing timer expires. Moreover, the UE can also start the login process when the context of each device needs to be updated because the PDU session is disconnected or disabled. Moreover, the UE can also start the login process when the capability information and / or preference selection related to the UE's PDU session establishment changes. Moreover, the UE can also start the login process periodically. Moreover, the UE can start the login process based on the completion of the UE setting update process. It should be noted that the UE can perform the login process at any timing, and is not limited to this.

[0221] First, the UE starts the registration process by sending a registration request message (S800)(S802)(S804) to the AMF via the 5G AN (or gNB). Specifically, the UE sends an RRC message including a registration request message to the 5G AN (or gNB) (S800). It should be noted that the registration request message is a NAS message. In addition, the RRC message may be a control message sent and received between the UE and the 5G AN (or gNB). In addition, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. It should be noted that the NAS layer is a higher layer than the RRC layer.

[0222] Here, the UE can include at least one or more of the first to sixth identification information in the login request message and / or RRC message for transmission, but can also include it in a control message different from these, such as a control message of a lower layer of the RRC layer (such as the MAC layer, the RLC layer, the PDCP layer) for transmission. It should be noted that the UE can indicate that the UE supports each function by sending these identification information, and can also indicate the UE's request. Moreover, two or more of these identification information can constitute one or more identification information. It should be noted that the information indicating support for each function and the information indicating a request to use each function can be sent and received as the same identification information, and can also be sent and received as different identification information.

[0223] The UE can indicate that the UE supports URLLC by sending the first identification information. In this case, the first identification information can also be information indicating support for URLLC.

[0224] Moreover, the UE may indicate that the UE supports redundant communication by sending one or more of the second to fifth identification information. In this case, the second identification information may be information indicating support for redundant communication, and the third to fifth identification information may be information indicating support for various types of redundant communication.

[0225] Specifically, the UE may indicate that the UE supports the first type of redundant communication by sending the second identification information and / or the third identification information. In this case, the second identification information may be information indicating the first type of redundant communication, and the third identification information may be information indicating support for the first type of redundant communication.

[0226] Moreover, the UE may indicate that the UE supports the second type of redundant communication by sending the second identification information and / or the fourth identification information. In this case, the second identification information may be information indicating the second type of redundant communication, and the fourth identification information may be information indicating support for the second type of redundant communication.

[0227] Moreover, the UE may indicate that the UE supports the third type of redundant communication by sending the second identification information and / or the fifth identification information. In this case, the second identification information may be information indicating the third type of redundant communication, and the fifth identification information may be information indicating support for the third type of redundant communication.

[0228] Moreover, the UE may indicate that the UE supports IP address maintenance by sending the sixth identification information. In this case, the sixth identification information may be information indicating support for IP address maintenance.

[0229] In addition, the UE can start the PDU session establishment process during the login process by including an SM message (such as a PDU session establishment request message) in the login request message, or sending an SM message (such as a PDU session establishment request message) together with the login request message.

[0230] When receiving an RRC message including a login request message, the 5G AN (or gNB) selects an AMF to which the login request message is transmitted (S802). It should be noted that the 5G AN (or gNB) can select an AMF based on the information included in the login request message and / or the RRC message. The 5G AN (or gNB) extracts the login request message from the received RRC message and transmits the login request message to the selected AMF (S804).

[0231] The AMF can perform the first condition determination upon receiving the login request message. The first condition determination is used to determine whether the network (or AMF) accepts the UE's request. If the first condition determination is true, the AMF starts Figure 6 (A) process, when the first condition is judged to be false, starts Figure 6 (B) process.

[0232] It should be noted that the first conditional determination can be performed based on the reception of the login request message and / or the identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF, etc. For example, it may be that when the network allows the UE's request, the first conditional determination is true, and when the network does not allow the UE's request, the first conditional determination is false. In addition, it may also be that when the network of the UE's login destination and / or the device within the network supports the function requested by the UE, the first conditional determination is true, and when the function requested by the UE is not supported, the first conditional determination is false. Moreover, it may also be that when the identification information is allowed to be sent and received, the first conditional determination is true, and when the identification information is not allowed to be sent and received, the first conditional determination is false. It should be noted that the conditions for determining the truth or falsehood of the first conditional determination may not be limited to the above conditions.

[0233] First, the case where the first condition is true is explained. Figure 6 The fourth condition determination is first performed in the process (A). The fourth condition determination is used to determine whether the AMF implements the sending and receiving of SM messages with the SMF.

[0234] It should be noted that the fourth condition determination can be performed based on whether the AMF receives an SM message. In addition, the fourth condition determination can also be performed based on whether the login request message includes an SM message. For example, it may be that when the AMF receives an SM message and / or the login request message includes an SM message, the fourth condition is determined to be true, and when the AMF does not receive an SM and / or the login request message does not include an SM message, the fourth condition is determined to be false. It should be noted that the conditions for determining the truth or falsity of the fourth condition may not be limited to the above conditions.

[0235] If the fourth condition is true, the AMF selects an SMF and performs SM message transmission and reception between the AMF and the selected SMF, and does not perform those steps (S806) if the fourth condition is false. In addition, even if the fourth condition is true, if an SM message indicating rejection is received from the SMF, the AMF may terminate the communication. Figure 6 (A) process. At this point, AMF can start Figure 6 (B) process.

[0236] It should be noted that in S806, AMF can notify SMF of the identification information received in the login request message when sending and receiving SM messages with SMF. SMF can obtain the identification information received from AMF by sending and receiving SM messages with AMF.

[0237] Next, the AMF sends a Registration accept message to the UE via the 5G AN (or gNB) as a response message to the login request message based on the reception of the login request message and / or the completion of the transmission and reception of the SM message between the AMF and the SMF (S808). For example, when the fourth condition is judged to be true, the AMF may send a Registration accept message based on the reception of the login request message from the UE. In addition, when the fourth condition is judged to be false, the AMF may send a Registration accept message based on the completion of the transmission and reception of the SM message between the AMF and the SMF. It should be noted that the Registration accept message is a NAS message transmitted and received on the N1 interface, but is included in the RRC message for transmission and reception between the UE and the 5G AN (gNB).

[0238] AMF may include at least one of the eleventh to seventeenth identification information in the login acceptance message. It should be noted that AMF can send these identification information to indicate that the network supports each function, and can also indicate that the UE's request is accepted. Moreover, two or more of these identification information can constitute one or more identification information. It should be noted that the information indicating support for each function and the information indicating a request to use each function can be sent and received as the same identification information, and can also be sent and received as different identification information.

[0239] AMF can indicate that the network supports URLLC by sending the eleventh identification information. In this case, the eleventh identification information can also be information indicating support for URLLC.

[0240] Moreover, the AMF can indicate that the network supports redundant communication by sending one or more of the identification information from the twelfth to fifteenth identification information, or can indicate which type of redundant communication is supported. In this case, the twelfth identification information can be information indicating support for redundant communication, and the thirteenth to fifteenth identification information can be information indicating support for each type of redundant communication.

[0241] Specifically, the AMF may indicate that the network supports the first type of redundant communication by sending the twelfth identification information and / or the thirteenth identification information. In this case, the twelfth identification information may be information indicating the first type of redundant communication, and the thirteenth identification information may be information indicating support for the first type of redundant communication.

[0242] Moreover, the AMF may indicate that the network supports the second type of redundant communication by sending the twelfth identification information and / or the fourteenth identification information. In this case, the twelfth identification information may be information indicating the second type of redundant communication, and the fourteenth identification information may be information indicating support for the second type of redundant communication.

[0243] Moreover, the AMF may indicate that the network supports the third type of redundant communication by sending the twelfth identification information and / or the fifteenth identification information. In this case, the twelfth identification information may be information indicating the third type of redundant communication, and the fifteenth identification information may be information indicating support for the third type of redundant communication.

[0244] Moreover, AMF can indicate that the network supports IP address maintenance by sending the sixteenth identification information. In this case, the sixteenth identification information can be information indicating support for IP address maintenance.

[0245] Furthermore, the AMF may indicate that the network supports LADN or that connection to LADN is allowed by sending the seventeenth identification information. Furthermore, the AMF may notify the UE of a list of DNNs that can be used when connected to LADN and / or an area that can be connected to LADN by sending the seventeenth identification information.

[0246] Furthermore, the AMF may indicate that the LADN DNN included in the seventeenth identification information can be utilized when establishing a PDU session supporting URLLC by sending the eleventh identification information together with the seventeenth identification information. Furthermore, the AMF may indicate that the LADN DNN included in the seventeenth identification information can be utilized when establishing a PDU session supporting redundant communication by sending one or more of the twelfth to fifteenth identification information together with the seventeenth identification information.

[0247] In more detail, the AMF may indicate that the LADN DNN included in the seventeenth identification information can be utilized when establishing a PDU session supporting the first type of redundant communication by sending the twelfth identification information and / or the thirteenth identification information together with the seventeenth identification information. Furthermore, the AMF may indicate that the LADN DNN included in the seventeenth identification information can be utilized when establishing a PDU session supporting the second type of redundant communication by sending the twelfth identification information and / or the fourteenth identification information together with the seventeenth identification information. Furthermore, the AMF may indicate that the LADN DNN included in the seventeenth identification information can be utilized when establishing a PDU session supporting the third type of redundant communication by sending the twelfth identification information and / or the fifteenth identification information together with the seventeenth identification information.

[0248] Moreover, the AMF can indicate that the LADN DNN included in the seventeenth identification information can be utilized when establishing a PDU session supporting IP address maintenance by sending the sixteenth identification information together with the seventeenth identification information.

[0249] It should be noted that the AMF can select and determine which of the eleventh to seventeenth identification information to include in the login acceptance message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF.

[0250] In addition, the AMF can include an SM message (such as a PDU session establishment accept message) in the login accept message and send it, or send an SM message (such as a PDU session establishment accept message) together with the login accept message. However, the sending method can also be performed when the SM message (such as a PDU session establishment request message) is included in the login request message and the fourth condition is judged to be true. In addition, in the sending method, an SM message (such as a PDU session establishment request message) can also be included together with the login request message, and it can be performed when the fourth condition is judged to be true. The AMF can indicate that the process used by the SM during the login process is accepted by performing such a sending method.

[0251] In addition, the AMF can indicate that the UE's request is accepted by sending a login acceptance message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF.

[0252] Furthermore, the AMF may include information indicating that a part of the UE's request is rejected in the login acceptance message, and may also indicate the reason why a part of the UE's request is rejected by sending information indicating that a part of the UE's request is rejected. Furthermore, the UE may identify the reason why a part of the UE's request is rejected by receiving information indicating that a part of the UE's request is rejected. It should be noted that the reason for rejection may be information indicating that the content indicated by the identification information received by the AMF is not allowed.

[0253] The UE receives a login acceptance message (S808) via the 5G AN (gNB). By receiving the login acceptance message, the UE can identify that the UE's request based on the login request message is accepted and the contents of various identification information included in the login acceptance message.

[0254] The UE can further send a login completion message to the AMF via the 5G AN (gNB) as a response message to the login acceptance message (S810). It should be noted that the UE can include an SM message such as a PDU session establishment completion message in the login completion message when receiving an SM message such as a PDU session establishment acceptance message, or it can include an SM message to indicate that the SM process is complete. Here, the login completion message is a NAS message sent and received on the N1 interface, but is included in the RRC message for sending and receiving between the UE and the 5G AN (gNB).

[0255] AMF receives a login completion message via 5G AN (gNB) (S810). In addition, each device completes the login based on the sending and receiving of the login acceptance message and / or the login completion message. Figure 6 (A) process.

[0256] Next, the case where the first condition is judged to be false is described. Figure 6 In the process (B), the AMF sends a Registration reject message to the UE via the 5G AN (gNB) as a response message to the Registration Request message (S812). Here, the Registration reject message is a NAS message sent and received on the N1 interface, but is sent and received between the UE and the 5G AN (gNB) in an RRC message.

[0257] It should be noted that the AMF may also indicate that the UE's request based on the login request message is rejected by sending a login rejection message. Moreover, the AMF may include information indicating the reason for rejection in the login rejection message and send it, or may indicate the reason for rejection by sending the reason for rejection. Furthermore, the UE may identify the reason why the UE's request is rejected by receiving information indicating the reason why the UE's request is rejected. It should be noted that the reason for rejection may be information indicating that the content indicated by the identification information that the AMF is not allowed to receive.

[0258] The UE receives a login rejection message via the 5G AN (gNB) (S812). By receiving the login rejection message, the UE can identify that the UE's request based on the login request message is rejected and the contents of various identification information included in the login rejection message. In addition, the UE can also identify that the UE's request is rejected when the login rejection message is not received after a specified period of time after sending the login request message. Each device completes the (B) process in this process based on the sending and receiving of the login rejection message.

[0259] It should be noted that sometimes it will be suspended Figure 6 (A) The process starts Figure 6 (B) process. Figure 6 In the process (A), if the fourth condition is true, the AMF may include a SM message indicating rejection, such as a PDU session establishment reject message, in the login reject message and send it, or may include a SM message indicating rejection to indicate that the process for SM is rejected. In this case, the UE may further receive a SM message indicating rejection, such as a PDU session establishment reject message, and may also recognize that the process for SM is rejected.

[0260] Each device is based on Figure 6 The login process is completed by completing the process (A) or (B). It should be noted that each device can be based on Figure 6 The completion of the (A) process transitions to the state where the UE logs into the network (RM_REGISTERED state), which can also be based on Figure 6The completion of the (B) process can maintain the state where the UE is not logged into the network (RM_DEREGISTERED state), and can also transition to the state where the UE is not logged into the network. In addition, the transition of each device to each state can be based on the completion of the login process or the establishment of a PDU session.

[0261] Furthermore, each device may perform processing based on information sent and received during the login process based on the completion of the login process. For example, the reason why the UE's request was rejected may be identified when information indicating that a part of the UE's request was rejected is sent and received. Furthermore, each device may perform this process again based on the reason why the UE's request was rejected, and may also perform the login process on the core network_B or other cells.

[0262] Furthermore, the UE may store the identification information received together with the login accept message and / or the login reject message based on the completion of the login process, and may also identify the determination of the network.

[0263] For example, the UE can identify whether the network supports URLLC when receiving the eleventh identification information. In addition, the UE can identify that a PDU session supporting URLLC can be established when the first identification information is sent and / or the eleventh identification information is received, and can also start a PDU session establishment process for establishing a PDU session supporting URLLC after this process is completed. In this case, the first identification information and the eleventh identification information may also be information indicating support for URLLC.

[0264] Moreover, the UE can identify whether the network supports redundant communication when receiving one or more of the identification information from the twelfth to fifteenth identification information, and can also identify which type of redundant communication is supported. Moreover, the UE can identify that a PDU session supporting redundant communication can be established when one or more of the identification information from the second to fifth identification information is sent and / or one or more of the identification information from the twelfth to fifteenth identification information is received, and can also start the PDU session establishment process for establishing a PDU session supporting redundant communication after this process is completed. In this case, the second identification information and the twelfth identification information can be information indicating support for redundant communication, and the third to fifth identification information and the thirteenth to fifteenth identification information can be information indicating support for various types of redundant communication.

[0265] Specifically, the UE can identify that a PDU session supporting the first type of redundant communication can be established when the second identification information and / or the third identification information is sent and / or the twelfth identification information and / or the thirteenth identification information is received, and can also start the PDU session establishment process for establishing the PDU session supporting the first type of redundant communication after the present process is completed. In this case, the second identification information and the twelfth identification information may be information indicating support for the first type of redundant communication, and the third identification information and the thirteenth identification information may be information indicating support for the first type of redundant communication.

[0266] Moreover, the UE may identify that a PDU session supporting the second type of redundant communication can be established when the second identification information and / or the fourth identification information is sent and / or the twelfth identification information and / or the fourteenth identification information is received, and may also start a PDU session establishment process for establishing a PDU session supporting the second type of redundant communication after this process is completed. In this case, the second identification information and the twelfth identification information may be information indicating support for the second type of redundant communication, and the fourth identification information and the fourteenth identification information may be information indicating support for the second type of redundant communication.

[0267] Moreover, the UE may identify that a PDU session supporting the third type of redundant communication can be established when the second identification information and / or the fifth identification information is sent and / or the twelfth identification information and / or the fifteenth identification information is received, and may also start a PDU session establishment process for establishing a PDU session supporting the third type of redundant communication after this process is completed. In this case, the second identification information and the twelfth identification information may be information indicating support for the third type of redundant communication, and the fifth identification information and the fifteenth identification information may be information indicating support for the third type of redundant communication.

[0268] Moreover, the UE can identify whether the network supports IP address maintenance when receiving the sixteenth identification information. Moreover, the UE can identify that a PDU session supporting IP address maintenance can be established when the sixth identification information is sent and / or the sixteenth identification information is received, and can also start a PDU session establishment process for establishing a PDU session supporting IP address maintenance after this process is completed. In this case, the sixth identification information and the sixteenth identification information can be information indicating support for IP address maintenance.

[0269] Furthermore, the UE can recognize that the network supports LADN when receiving the seventeenth identification information, and can also recognize that connection to LADN is allowed. Furthermore, the UE can recognize that a PDU session for LADN can be established when receiving the seventeenth identification information, and can also start a PDU session establishment process for establishing a PDU session for LADN after this process is completed. Furthermore, the UE can recognize an overview of DNNs that can be used when connecting to LADN and / or an area that can be connected to LADN when receiving the seventeenth identification information, and can also store it in the context.

[0270] Furthermore, the UE can recognize that the LADN DNN included in the seventeenth identification information can be used when establishing a PDU session supporting URLLC when the eleventh identification information is received together with the seventeenth identification information. Furthermore, the UE can recognize that the LADN DNN included in the seventeenth identification information can be used when establishing a PDU session supporting redundant communication when one or more of the twelfth to fifteenth identification information is received together with the seventeenth identification information.

[0271] In more detail, the UE can recognize that the LADN DNN included in the seventeenth identification information can be used when establishing a PDU session supporting the first type of redundant communication when the twelfth identification information and / or the thirteenth identification information are received together with the seventeenth identification information. Moreover, the UE can recognize that the LADN DNN included in the seventeenth identification information can be used when establishing a PDU session supporting the second type of redundant communication when the twelfth identification information and / or the fourteenth identification information are received together with the seventeenth identification information. Moreover, the UE can recognize that the LADN DNN included in the seventeenth identification information can be used when establishing a PDU session supporting the third type of redundant communication when the twelfth identification information and / or the fifteenth identification information are received together with the seventeenth identification information.

[0272] Moreover, when the UE receives the sixteenth identification information together with the seventeenth identification information, it can recognize that the LADN DNN included in the seventeenth identification information can be used when establishing a PDU session supporting IP address maintenance.

[0273] [3.2.2.PDU session establishment process]

[0274] Next, use Figure 7An overview of the PDU session establishment procedure for establishing a PDU session for a DN is described. The PDU session establishment procedure is a process in 5GS. Hereinafter, this process refers to the PDU session establishment procedure. The PDU session establishment procedure is a process for each device to establish a PDU session. It should be noted that each device can start the PDU session establishment procedure at any timing when the login process is completed and the device is in a logged-in state. In addition, each device may also execute the PDU session establishment procedure during the login process. In addition, each device may establish a PDU session based on the completion of the PDU session establishment procedure. It should be noted that the PDU session establishment procedure may be a process initiated by the UE or a process initiated by the UE request. Each device can establish multiple PDU sessions by executing the PDU session establishment procedure multiple times.

[0275] Furthermore, the UE may start a PDU session establishment process based on the identification information received during the login process. For example, the UE may start a PDU session establishment process to establish a PDU session supporting URLLC when URLLC is supported. Furthermore, the UE may start a PDU session establishment process to establish a PDU session supporting redundant communication when redundant communication is supported. Furthermore, the UE may start a PDU session establishment process to establish a PDU session supporting IP address maintenance when IP address maintenance is supported.

[0276] Moreover, the UE may start the PDU session establishment procedure to establish a PDU session for LADN when it is located in an area that can be connected to the LADN and / or when it is located in a LADN service area. In other words, the UE may prohibit the execution of the PDU session establishment procedure for establishing a PDU session for LADN when it is located outside the LADN service area.

[0277] First, the UE starts the PDU session establishment process by sending a NAS message (S900)(S902)(S904) including a PDU session establishment request message to the SMF via the 5G AN (gNB) and AMF.

[0278] Specifically, the UE sends a NAS message (S900) including a PDU session establishment request message to the AMF via the N1 interface and the 5G AN (gNB).

[0279] Here, the UE can include at least one of the identification information 21 to 26 in the PDU session establishment request message and / or NAS message for transmission, but can also include it in a control message different from these, such as a control message of a lower layer of the RRC layer (e.g., MAC layer, RLC layer, PDCP layer) for transmission. The UE's request can also be expressed by including these identification information in these messages. In addition, two or more of these identification information can also constitute one or more identification information.

[0280] The UE may indicate a request to establish a PDU session supporting URLLC by sending the twenty-first identification information. In this case, the twenty-first identification information may also be information indicating support for URLLC.

[0281] Furthermore, the UE may indicate a request to establish a PDU session supporting redundant communication by sending the twenty-second identification information and / or the twenty-third identification information. Furthermore, the UE may indicate the type of redundant communication requested by the UE by sending the twenty-second identification information and / or the twenty-third identification information. In this case, the twenty-second identification information may be information indicating support for redundant communication. Furthermore, the twenty-third identification information may be information indicating the first type of redundant communication, information indicating the second type of redundant communication, or information indicating the third type of redundant communication.

[0282] Specifically, the UE may indicate a request to establish a PDU session supporting the first type of redundant communication by sending the twenty-second identification information and / or the twenty-third identification information. In this case, the twenty-third identification information may be information indicating the first type of redundant communication.

[0283] In addition, the UE may indicate a request to establish a PDU session supporting the second type of redundant communication by sending the twenty-second identification information and / or the twenty-third identification information. In this case, the twenty-third identification information may be information indicating the second type of redundant communication.

[0284] In addition, the UE may indicate a request to establish a PDU session supporting the third type of redundant communication by sending the twenty-second identification information and / or the twenty-third identification information. In this case, the twenty-third identification information may be information indicating the third type of redundant communication.

[0285] The UE may indicate a request to establish a PDU session supporting IP address maintenance by sending the twenty-fourth identification information. In this case, the twenty-fourth identification information may be information indicating support for IP address maintenance.

[0286] Moreover, the UE may indicate a request to establish a PDU session of the SSC mode indicated by the twenty-fifth identification information by sending the twenty-fifth identification information, or may indicate the SSC mode requested by the UE. In this case, the information SSC mode indicated by the twenty-fifth identification information may be any one of "SSC mode 1", "SSC mode 2" or "SSC mode 3".

[0287] Furthermore, the UE may send the 25th identification information together with the 24th identification information to indicate a request to establish a PDU session that maintains the IP address even when the anchor point change procedure of the PDU session of SSC mode 2 is performed. In this case, the 24th identification information may be information indicating support for IP address maintenance, and the 25th identification information may be information indicating SSC mode 2.

[0288] Furthermore, the UE may send the 25th identification information together with the 24th identification information to indicate a request to establish a PDU session that maintains the IP address even when the anchor point change procedure of the PDU session of SSC mode 3 is performed. In this case, the 24th identification information may be information indicating support for IP address maintenance, and the 25th identification information may be information indicating SSC mode 3.

[0289] Moreover, the UE may indicate a request to establish a PDU session that maintains the IP address even when the anchor point change procedure of the PDU session is performed by sending the twenty-fourth identification information and / or the twenty-fifth identification information. In this case, the twenty-fourth identification information may be information indicating support for IP address maintenance, and the twenty-fifth identification information may be information indicating SSC mode 4. It should be noted that, when the twenty-fifth identification information is information indicating SSC mode 4, the UE may not send the twenty-fourth identification information.

[0290] Moreover, the UE may indicate a request to establish a PDU session corresponding to the DNN indicated by the twenty-sixth identification information by sending the twenty-sixth identification information, or may indicate the DNN requested by the UE. It should be noted that the twenty-sixth identification information may be a DNN that identifies a DN that supports one or more functions indicated by the identification information sent and received together with the twenty-sixth identification information. Moreover, the twenty-sixth identification information may be a DNN received during the login process, or may be a LADN.

[0291] When receiving a NAS message including a PDU session establishment request message (S900), the AMF obtains the PDU session establishment request message from the NAS message, and selects the SMF as the transmission destination of the PDU session establishment request message (S902). It should be noted that the AMF can select the SMF of the transmission destination based on the identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF, etc. included in the PDU session establishment request message and / or the NAS message.

[0292] The AMF transmits a PDU session establishment request message to the selected SMF via the N11 interface (S904).

[0293] When receiving the PDU session establishment request message (S904), the SMF identifies various identification information included in the PDU session establishment request message. Then, the SMF performs the third condition determination. The third condition determination is used to determine whether the SMF accepts the UE's request. In the third condition determination, the SMF determines whether the third condition determination is true or false. If the third condition determination is true, the SMF starts Figure 7 (A) process, when the third condition is judged to be false, starts Figure 7 (B) process.

[0294] It should be noted that the third condition determination can be performed based on the PDU session establishment request message and / or the identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the SMF included in the PDU session establishment request message. For example, the third condition determination may be true when the network allows the UE's request. In addition, the third condition determination may be false when the network does not allow the UE's request. Moreover, it may also be that the third condition determination is true when the network of the UE's connection destination and / or the device within the network supports the function requested by the UE, and the third condition determination is false when the function requested by the UE is not supported. Moreover, it may also be that the third condition determination is true when the identification information that is allowed to be sent and received is allowed, and the third condition determination is false when the identification information that is not allowed to be sent and received is allowed. It should be noted that the conditions for determining the truth or falsity of the third condition may not be limited to the above conditions.

[0295] Next, the step of judging whether the third condition is true is Figure 7 The SMF selects the UPF of the destination for establishing the PDU session, sends a session establishment request message to the selected UPF via the N4 interface (S906), and starts Figure 7 (A) process.

[0296] Here, the SMF can select one or more UPFs based on the identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the SMF, etc., obtained based on the reception of the PDU session establishment request message. It should be noted that, when multiple UPFs are selected, the SMF can send a session establishment request message to each UPF.

[0297] The UPF receives a session establishment request message from the SMF via the N4 interface (S906) and generates a context for the PDU session. Moreover, the UPF sends a session establishment response message to the SMF via the N4 interface based on the reception of the session establishment request message and / or the generation of the context for the PDU session (S908).

[0298] The SMF receives a session establishment response message from the UPF via the N4 interface as a response message to the session establishment request message (S908). The SMF may perform address allocation of the address allocated to the UE based on the reception of the PDU session establishment request message and / or the selection of the UPF and / or the reception of the session establishment response message.

[0299] Based on the reception of the PDU session establishment request message and / or the selection of the UPF and / or the reception of the session establishment response message and / or the completion of the address allocation of the address allocated to the UE, the SMF sends a PDU session establishment accept message (S910)(S912) to the UE via the AMF.

[0300] Specifically, when the SMF sends a PDU session establishment acceptance message to the AMF via the N11 interface (S910), the AMF that receives the PDU session establishment request message sends a NAS message including a PDU session establishment acceptance message to the UE via the N1 interface (S912). It should be noted that the PDU session establishment acceptance message can be a NAS message or a response message to the PDU session establishment request. In addition, the PDU session establishment acceptance message can indicate that the establishment of the PDU session is accepted.

[0301] Here, the SMF and AMF can indicate that the UE's request based on the PDU session establishment request is accepted by sending a PDU session establishment accept message.

[0302] SMF and AMF may include at least one of the thirty-first to thirty-sixth identification information in the PDU session establishment acceptance message. It should be noted that SMF and AMF can send these identification information to indicate that the network supports each function, and can also indicate that the UE's request is accepted. Moreover, two or more of these identification information can constitute one or more identification information. It should be noted that the information indicating support for each function and the information indicating a request to use each function can be sent and received as the same identification information, and can also be sent and received as different identification information.

[0303] SMF and AMF can indicate acceptance of a request to establish a PDU session supporting URLLC by sending the thirty-first identification information, or can indicate establishment of the PDU session. In this case, the thirty-first identification information can be information indicating support for URLLC.

[0304] Furthermore, the SMF and the AMF may indicate acceptance of a request to establish a PDU session supporting redundant communication by sending the thirty-second identification information and / or the thirty-third identification information, or may indicate establishment of the PDU session. Furthermore, the SMF and the AMF may indicate the type of redundant communication selected and determined by the network by sending the thirty-second identification information and / or the thirty-third identification information. In this case, the thirty-second identification information may be information indicating support for redundant communication. Furthermore, the thirty-third identification information may be information indicating the first type of redundant communication, or information indicating the third type of redundant communication, or information indicating the third type of redundant communication.

[0305] Specifically, SMF and AMF can indicate acceptance of a request to establish a PDU session supporting the first type of redundant communication by sending the thirty-second identification information and / or the thirty-third identification information, or can indicate establishment of the PDU session. In this case, the thirty-third identification information can be information indicating the first type of redundant communication.

[0306] In addition, SMF and AMF can indicate acceptance of a request to establish a PDU session supporting the third type of redundant communication by sending the thirty-second identification information and / or the thirty-third identification information, or can indicate establishment of the PDU session. In this case, the thirty-third identification information can be information indicating the third type of redundant communication.

[0307] In addition, SMF and AMF can indicate acceptance of a request to establish a PDU session supporting the third type of redundant communication by sending the thirty-second identification information and / or the thirty-third identification information, or can indicate establishment of the PDU session. In this case, the thirty-third identification information can be information indicating the third type of redundant communication.

[0308] SMF and AMF can indicate acceptance of the establishment request of the PDU session supporting IP address maintenance by sending the thirty-fourth identification information, or can indicate establishment of the PDU session. In this case, the thirty-fourth identification information can be information indicating support for IP address maintenance.

[0309] Moreover, SMF and AMF can indicate acceptance of a request to establish a PDU session of the SSC mode indicated by the thirty-fifth identification information by sending the thirty-fifth identification information, or can indicate establishment of the PDU session. Moreover, SMF and AMF can indicate an SSC mode selected and determined by the network by sending the thirty-fifth identification information. In this case, the information SSC mode indicated by the thirty-fifth identification information can be any one of "SSC mode 1", "SSC mode 2" or "SSC mode 3".

[0310] Furthermore, the SMF and the AMF may indicate acceptance of a request to establish a PDU session that maintains an IP address even when the anchor point change process of the PDU session in SSC mode 2 is performed, or may indicate establishment of a PDU session, by sending the 35th identification information together with the 34th identification information. In this case, the 34th identification information may be information indicating support for IP address maintenance, and the 35th identification information may be information indicating SSC mode 2.

[0311] Furthermore, the SMF and the AMF may indicate acceptance of a request to establish a PDU session that maintains an IP address even when the anchor point change process of the PDU session in SSC mode 3 is performed, or may indicate establishment of a PDU session, by sending the 35th identification information together with the 34th identification information. In this case, the 34th identification information may be information indicating support for IP address maintenance, and the 35th identification information may be information indicating SSC mode 3.

[0312] Moreover, the SMF and the AMF may indicate acceptance of a request to establish a PDU session that maintains an IP address even when the anchor point change process of the PDU session is executed by sending the thirty-fourth identification information and / or the thirty-fifth identification information, or may indicate establishment of a PDU session. In this case, the thirty-fourth identification information may be information indicating support for IP address maintenance, and the thirty-fifth identification information may be information indicating SSC mode 4. It should be noted that, in the case where the thirty-fifth identification information is information indicating SSC mode 4, the SMF and the AMF may not send the thirty-fourth identification information.

[0313] Moreover, SMF and AMF can indicate acceptance of a request to establish a PDU session corresponding to the DNN indicated by the thirty-sixth identification information by sending the thirty-sixth identification information, or can indicate establishment of the PDU session. Moreover, SMF and AMF can indicate sending the thirty-sixth identification information, the DNN selected and determined by the network. It should be noted that the thirty-sixth identification information can be a DNN that identifies a DN that supports one or more functions indicated by the identification information sent and received together with the thirty-sixth identification information. Moreover, the thirty-sixth identification information can be a DNN sent during the login process, or it can be a LADN.

[0314] It should be noted that SMF and AMF can select and determine whether to include which of the thirty-first to thirty-sixth identification information in the PDU session establishment acceptance message based at least on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by AMF.

[0315] In addition, the SMF and the AMF can include the selected and / or allowed PDU session ID in the PDU session establishment accept message. In addition, the SMF and the AMF can specify a PDU session type representing the type of the selected and / or allowed PDU session. As the PDU session type, any one of IPv4, IPv6, IP, Ethernet, and unstructured can be specified as described above. In addition, the SMF and the AMF can include the SSC mode of the selected and / or allowed PDU session in the PDU session establishment accept message.

[0316] Moreover, the SMF and AMF can include the permitted QoS rule group in the PDU session establishment accept message. It should be noted that one or more QoS rules can be included in the permitted QoS rule group. Moreover, in the present process, when multiple QoS flows and / or user plane radio bearers are established, multiple QoS rules can be included in the permitted QoS rule group. Conversely, in the present process, when only one QoS flow and / or user plane radio bearer is established, one QoS rule can be included in the permitted QoS rule group.

[0317] Furthermore, the SMF may include information indicating that part of the UE's request is rejected in the PDU session establishment acceptance message, and may also indicate the reason why part of the UE's request is rejected by sending information indicating that part of the UE's request is rejected. Furthermore, the UE may identify the reason why part of the UE's request is rejected by receiving the information indicating that part of the UE's request is rejected. It should be noted that the reason for rejection may be information indicating that the content indicated by the identification information that the SMF is not allowed to receive.

[0318] When the UE receives a NAS message including a PDU session establishment accept message from the AMF via the N1 interface (S912), it sends a PDU session establishment complete message (S914) to the SMF via the AMF (S916). The UE can detect that the UE's request based on the PDU session establishment request is accepted by receiving the PDU session establishment accept message.

[0319] Specifically, the UE sends a PDU session establishment completion message to the AMF via the N1 interface (S914). When the AMF receives the PDU session establishment completion message from the UE, it sends a PDU session establishment completion message to the SMF via the N11 interface (S916).

[0320] It should be noted that the PDU session establishment completion message sent by AMF to SMF may be a response message to the PDU session establishment acceptance message sent from SMF to AMF in S910. In addition, the PDU session establishment completion message may also be a NAS message. In addition, the PDU session establishment completion message may be any message indicating that the PDU session establishment process is completed.

[0321] The SMF can perform the second conditional judgment when receiving the PDU session establishment completion message from the AMF via the N11 interface (S916). The second conditional judgment is used to determine the type of messages sent and received on the N4 interface. When the second conditional judgment is true, the SMF receives the session change acceptance message sent from the UPF as the response message (S920) when sending a session change request message to the UPF via the N4 interface (S918). When the second conditional judgment is false, the SMF receives the session change acceptance message sent from the UPF as the response message (S920) when sending a session establishment request message to the UPF via the N4 interface (S918).

[0322] It should be noted that the second conditional determination can be performed based on whether a session on the N4 interface for the PDU session is established. For example, the second conditional determination is true when a session on the N4 interface for the PDU session is established, and false when a session on the N4 interface for the PDU session is not established. It should be noted that the conditions for determining whether the second condition is true or false are not limited to the above conditions.

[0323] Each device completes process (A) in the PDU session establishment process based on the sending and receiving of the PDU session establishment completion message and / or the sending and receiving of the session change response message and / or the sending and receiving of the session establishment response message. When completing process (A) in this process, the UE is in a state of establishing a PDU session for the DN.

[0324] Next, the steps of process (B) in the PDU session establishment process are described. SMF sends a PDU session establishment reject message (PDU session establishment reject) to UE via AMF (S922)(S924). Specifically, SM sends a PDU session establishment reject message (S922) to AMF via the N11 interface. When AMF receives a PDU session establishment request message from SMF via the N11 interface (S922), it sends a PDU session establishment reject message (S924) to UE using the N1 interface.

[0325] It should be noted that the PDU session establishment rejection message may also be a NAS message. In addition, the PDU session establishment rejection message may be any message indicating that the establishment of the PDU session is rejected.

[0326] Here, the SMF can indicate that the UE's request based on the PDU session establishment request is rejected by sending a PDU session establishment reject message. Moreover, the SMF can include information indicating the reason for rejection in the PDU session establishment reject message and send it, or can indicate the reason for rejection by sending the reason for rejection. Furthermore, the UE can identify the reason why the UE's request is rejected by receiving information indicating the reason why the UE's request is rejected. It should be noted that the reason for rejection can be information indicating that the content indicated by the identification information that the SMF is not allowed to receive.

[0327] The UE can recognize, by receiving the PDU session establishment reject message, that the UE's request based on the PDU session establishment request is rejected and the contents of various identification information included in the PDU session establishment reject message.

[0328] Each device is based on Figure 7 The PDU session establishment process is completed by completing the process (A) or (B). It should be noted that each device can be based on Figure 7 The completion of the (A) process can be used to transition to the established PDU session state, or based on Figure 7 The UE can recognize that the PDU session establishment process is rejected by completing the (B) process, and can also switch to a state where the PDU session is not established. Figure 7 The (A) process is completed to communicate with the DN using the established PDU session.

[0329] Furthermore, each device may implement processing based on identification information sent and received during the PDU session establishment process based on the completion of the PDU session establishment process. For example, each device may identify the reason why the UE's request was rejected when sending and receiving information indicating that a part of the UE's request was rejected. Furthermore, each device may implement this process again based on the reason why the UE's request was rejected, or implement the PDU session establishment process for other cells.

[0330] Moreover, the UE may store the identification information received together with the PDU session establishment accept message and / or the PDU session establishment reject message based on the completion of the PDU session establishment process, and may also identify the determination of the network.

[0331] For example, the UE can identify whether URLLC is supported in an established PDU session when receiving the thirty-first identification information. Moreover, each device can establish a PDU session supporting URLLC when sending and receiving the twenty-first identification information and / or the thirty-first identification information. Moreover, the UE can identify that a PDU session supporting URLLC is established when the twenty-first identification information is sent and / or the thirty-first identification information is received. In this case, the twenty-first identification information and / or the thirty-first identification information may also be information indicating support for URLLC.

[0332] Moreover, the UE can identify whether redundant communication is supported in the established PDU session when receiving the thirty-second identification information and / or the thirty-third identification information. Moreover, each device can establish a PDU session supporting redundant communication when sending and receiving the twenty-second identification information and / or the twenty-third identification information and / or the thirty-second identification information and / or the thirty-third identification information. Moreover, the UE can identify that a PDU session supporting redundant communication has been established when the twenty-second identification information and / or the twenty-third identification information is sent and / or the thirty-second identification information and / or the thirty-third identification information is received. In this case, the twenty-second identification information and the thirty-second identification information may also be information indicating support for redundant communication. Moreover, the twenty-third identification information and / or the thirty-third identification information may be information indicating the first type of redundant communication, may be information indicating the third type of redundant communication, or may be information indicating the third type of redundant communication.

[0333] Specifically, each device may establish a PDU session supporting the first type of redundant communication when the twenty-second identification information and / or the twenty-third identification information and / or the thirty-second identification information and / or the thirty-third identification information are sent and received. Moreover, the UE may identify the establishment of a PDU session supporting the first type of redundant communication when the twenty-second identification information and / or the twenty-third identification information are sent and / or the thirty-second identification information and / or the thirty-third identification information are received. In this case, the thirty-third identification information may be information indicating the first type of redundant communication.

[0334] In addition, each device may establish a PDU session supporting the second type of redundant communication when the twenty-second identification information and / or the twenty-third identification information and / or the thirty-second identification information and / or the thirty-third identification information are sent and received. Moreover, the UE may identify the establishment of a PDU session supporting the second type of redundant communication when the twenty-second identification information and / or the twenty-third identification information are sent and / or the thirty-second identification information and / or the thirty-third identification information are received. In this case, the thirty-third identification information may be information indicating the second type of redundant communication.

[0335] In addition, each device may establish a PDU session supporting the third type of redundant communication when the twenty-second identification information and / or the twenty-third identification information and / or the thirty-second identification information and / or the thirty-third identification information are sent and received. Moreover, the UE may identify the establishment of a PDU session supporting the third type of redundant communication when the twenty-second identification information and / or the twenty-third identification information are sent and / or the thirty-second identification information and / or the thirty-third identification information are received. In this case, the thirty-third identification information may be information indicating the third type of redundant communication.

[0336] The UE can identify whether IP address maintenance is supported in an established PDU session when the thirty-fourth identification information is received. Moreover, each device can establish a PDU session that supports IP address maintenance when the twenty-fourth identification information and / or the thirty-fourth identification information are sent and received. Moreover, the UE can identify that a PDU session that supports IP address maintenance has been established when the twenty-fourth identification information is sent and / or the thirty-fourth identification information is received. In this case, the twenty-fourth identification information and / or the thirty-fourth identification information can be information indicating support for IP address maintenance.

[0337] Moreover, the UE can recognize that a PDU session of the SSC mode indicated by the thirty-fifth identification information is established when the thirty-fifth identification information is received, and can also recognize that a corresponding SSC mode is established with the established PDU session. Moreover, each device can recognize that a PDU session of the SSC mode indicated by the thirty-fifth identification information is established when the thirty-fifth identification information is sent and received. Moreover, the UE can store the SSC mode indicated by the thirty-fifth identification information in the context of the established PDU session when the thirty-fifth identification information is received. Moreover, the UE can recognize that the establishment request of the PDU session of the SSC mode indicated by the twenty-fifth identification information is accepted when the thirty-fifth identification information is received. In this case, the information SSC mode indicated by the thirty-fifth identification information can be any one of "SSC mode 1", "SSC mode 2" or "SSC mode 3".

[0338] Furthermore, each device may establish a PDU session that maintains an IP address even when the anchor point change process of the PDU session in SSC mode 2 is performed when the thirty-fifth identification information is sent and received together with the thirty-fourth identification information. Furthermore, the UE may recognize that a PDU session that maintains an IP address even when the anchor point change process of the PDU session in SSC mode 2 is performed is established when the thirty-fifth identification information is received together with the thirty-fourth identification information. In this case, the thirty-fourth identification information may be information indicating support for IP address maintenance, and the thirty-fifth identification information may be information indicating SSC mode 2.

[0339] Furthermore, each device may establish a PDU session that maintains an IP address even when the anchor point change process of the PDU session in SSC mode 3 is performed when the thirty-fifth identification information is sent and received together with the thirty-fourth identification information. Furthermore, the UE may recognize that a PDU session that maintains an IP address even when the anchor point change process of the PDU session in SSC mode 3 is performed is established when the thirty-fifth identification information is received together with the thirty-fourth identification information. In this case, the thirty-fourth identification information may be information indicating support for IP address maintenance, and the thirty-fifth identification information may be information indicating SSC mode 3.

[0340] Moreover, each device may establish a PDU session that maintains the IP address even when the anchor point change process of the PDU session is executed, when the thirty-fourth identification information and / or the thirty-fifth identification information are sent and received. Moreover, the UE may identify the establishment of a PDU session that maintains the IP address even when the anchor point change process of the PDU session is executed, when the thirty-fourth identification information and / or the thirty-fifth identification information are received. In this case, the thirty-fourth identification information may be information indicating support for IP address maintenance, and the thirty-fifth identification information may be information indicating SSC mode 4. It should be noted that, in the case where the thirty-fifth identification information is information indicating SSC mode 4, the UE may not send the thirty-fourth identification information.

[0341] Moreover, each device can establish a PDU session corresponding to the DNN indicated by the thirty-sixth identification information when the thirty-sixth identification information is sent and received. Moreover, the UE can identify the establishment of a PDU session corresponding to the DNN indicated by the thirty-sixth identification information when receiving the thirty-sixth identification information. Moreover, the UE can identify the DNN selected and determined by the network when receiving the thirty-sixth identification information. It should be noted that the thirty-sixth identification information can be a DNN that identifies a DN that supports one or more functions indicated by the identification information sent and received together with the thirty-sixth identification information. Moreover, the thirty-sixth identification information can be a DNN received during the login process, or it can be a LADN.

[0342] [4. First embodiment]

[0343] Next, the first embodiment is described. Hereinafter, the first embodiment is referred to as the present embodiment. In the communication process of the present embodiment, first, each device performs the login process initiated by the UE. Then, each device establishes a PDU session by performing the PDU session establishment process initiated by the UE, and transitions to a state in which communication using the PDU session can be performed between the UE and the DN. Next, each device uses the PDU session to send and receive user data. Through the above steps, the process of the present embodiment is completed.

[0344] It should be noted that during the process of this implementation, each device can exchange URLLC support information, redundant communication support information and / or IP address maintenance support information between the UE and the network during the login process.

[0345] Moreover, each device can establish a PDU session supporting URLLC between the UE and the network based on the information exchanged during the login process during the PDU session establishment process, and can also establish a PDU session supporting redundant communication, and can also establish a PDU session supporting IP address maintenance. It should be noted that the PDU session supporting URLLC, the PDU session supporting redundant communication, and the PDU session supporting IP address maintenance can be PDU sessions that can only be established for a specific DN. Here, the specific DN may refer to LADN, for example.

[0346] Moreover, each device can perform communication of user data supporting URLLC by using an established PDU session, can perform redundant communication, and can also perform communication of user data supporting IP address maintenance.

[0347] [5. Improvement example]

[0348] The program running in the device involved in the present invention can be a program that controls a central processing unit (CPU) or the like to enable a computer to function in order to realize the functions of the embodiments involved in the present invention. The program or the information processed by the program is temporarily stored in a volatile memory such as a random access memory (RAM) or a non-volatile memory such as a flash memory, a hard disk drive (HDD) or other storage device system.

[0349] It should be noted that the program for realizing the functions of the embodiments involved in the present invention may also 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 "computer system" mentioned here refers to a computer system built into a device, and includes a computer system of hardware such as an operating system and peripherals. In addition, 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 other computer-readable recording media.

[0350] In addition, each functional block or each feature of the device used in the above-mentioned embodiments can be installed or executed by an electronic circuit such as an integrated circuit or multiple integrated circuits. Circuits designed in a manner to perform the functions described in this specification may include: a general-purpose processor, a digital signal processor (DSP), an integrated circuit for a specific purpose (ASIC), a field programmable gate array (FPGA) or other programmable logic elements, discrete gates or transistor logic, discrete hardware parts, or a combination thereof. The general-purpose processor may be a microprocessor, or it may be a processor, controller, microcontroller, or state machine of the previous type. The above-mentioned electronic circuit may be composed of a digital circuit or an analog circuit. In addition, in the case where an integrated circuit technology that replaces the current integrated circuit appears due to advances in semiconductor technology, one or more schemes of the present invention may also use a new integrated circuit based on the technology.

[0351] It should be noted that the present invention is not limited to the above-mentioned embodiments. In the embodiments, an example of a device is described, but the present invention is not limited thereto and can be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, other life equipment, and other terminal devices or communication devices.

[0352] Above, the embodiments of the present invention are described in detail with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiments, and also includes design changes within the scope of the gist of the present invention. In addition, the present invention can be variously modified within the scope shown in the technical solution, and the embodiments obtained by appropriately combining the technical solutions disclosed in different embodiments are also included in the technical scope of the present invention. In addition, it also includes a configuration obtained by replacing the elements that have the same effect as the elements recorded in the above-mentioned embodiments with each other.

Claims

1. A user equipment UE, characterized in that: The UE includes a control unit and a transceiver unit, wherein: During the protocol data unit (PDU) session establishment process, the transceiver is configured to receive a PDU session establishment acceptance message from the core network device, In the case where the transceiver receives information indicating characteristics of the PDU session included in the PDU session establishment acceptance message, the control unit considers that the established PDU session can be used for highly reliable low latency communication (URLLC), In the case where the transceiver does not receive the information indicating the characteristics of the PDU session included in the PDU session establishment accept message, the control unit considers that it is unknown whether the established PDU session can be used for the URLLC, The established PDU session available for the URLLC is associated with a Quality of Service (QoS) rule.

2. A core network device, characterized in that: The core network device comprises a control unit and a transceiver unit, wherein: In the protocol data unit PDU session establishment process, the transceiver is configured to send a PDU session establishment acceptance message to the user equipment UE, In the case where the transceiver sends information indicating characteristics of the PDU session included in the PDU session establishment acceptance message, the control unit considers that the established PDU session can be used for highly reliable low latency communication URLLC, In the case where the transceiver does not send information indicating the characteristics of the PDU session included in the PDU session establishment accept message, the control unit considers that it is unknown whether the established PDU session can be used for the URLLC, and The established PDU session available for the URLLC is associated with a Quality of Service (QoS) rule.

3. A communication control method performed by a user equipment UE, characterized in that: The communication control method comprises the following steps: During the PDU session establishment process, a PDU session establishment acceptance message is received from the core network device. upon receiving information indicating characteristics of the PDU session contained in said PDU SESSION ESTABLISHMENT ACCEPT message, considering that the established PDU session can be used for High Reliability Low Latency Communication (URLLC), In the absence of receiving information indicating the characteristics of the PDU session contained in the PDU SESSION ESTABLISHMENT ACCEPT message, it is considered unknown whether the established PDU session is usable for the URLLC, wherein The established PDU session available for the URLLC is associated with a Quality of Service (QoS) rule.

Images