WO2020004278A1 - User device, control device, and communication control method - Google Patents

Abstract

The present invention provides a communication means for realizing extension of a function for providing connectivity to a local area data network (LADN) in 5GS. The present invention provides a communication means for enabling extension of the function for providing connectivity to a local area data network (LADN) in 5GS. Further, the present invention provides a communication means for, when the function for providing connectivity to the LADN is extendable, enabling the extended function for providing connectivity to a LAND to be used between a user device and the network.

Description

User device, control device, and communication control method

The present disclosure relates to a user device, a control device, and a communication control method. Priority is claimed on Japanese Patent Application No. 2018-119582, filed on June 25, 2018, the content of which is incorporated herein by reference.

The 3GPP (3rd Generation Partnership Project) has begun studying the 5GS (5G System) system architecture, which is the next generation (5G) mobile communication system, and will support new procedures and new functions. Discussion has been made (see Non-Patent Documents 1 and 2).

For example, it is necessary to optimize and diversify communication procedures to support continuous mobile communication services in accordance with a wide variety of services, and to optimize system architecture in accordance with optimization and diversification of communication procedures. It is listed as a condition.

In 5GS (5G System), 5GCN (5G Core Network), which is a new core network, is being studied in order to provide various services. Note that 5GS supports new functions such as a function for providing connectivity to LADN (Local Area Data Network).

At 5GS, studies are underway to further expand new functions, such as functions for providing connectivity to LADN. However, it is unclear how new procedures and new features will be implemented in 5GS when implementing extensions to provide connectivity to LADN.

One aspect of the present invention has been made in view of the above circumstances, and an object of the present invention is to provide a method for realizing an extension of a function for providing connectivity to a LADN in 5GS.

The user device of one embodiment of the present invention includes a transmission / reception unit and a control unit, wherein the control unit transmits a registration request message to the control device in a registration procedure, and receives a registration acceptance message from the control device, The registration request message includes information A indicating whether the extension of the Local Area Data Network (LADN) service area is supported, and the registration acceptance message indicates whether the extension of the LADN service area is supported. Contains information B indicating, the control unit, if the information B indicates that does not support the extension of the LADN service area, an area configured by one or more tracking areas, as the LADN service area Setting, and if the information B indicates that the extension of the LADN service area is supported, the one or more tracking errors The user apparatus characterized by setting the different areas, as said LADN service area and the area formed by A.

The control device according to an embodiment of the present invention includes a transmission / reception unit and a control unit, wherein the control unit receives a registration request message from the user device in a registration procedure, and transmits a registration acceptance message to the user device, The registration request message includes information A indicating whether the extension of the Local Area Data Network (LADN) service area is supported, and the registration acceptance message indicates whether the extension of the LADN service area is supported. Including the information B indicating, the control unit, when the information A indicates that does not support the extension of the LADN service area, an area configured by one or more tracking areas, as the LADN service area Setting, if the information A indicates that the extension of the LADN service area is supported, the one or more tracking The different areas are to be composed area by the rear, it is set as the LADN service area, the registration acceptance message further comprising information C indicating the LADN service area.

A communication control method for a user apparatus according to an embodiment of the present invention includes a step of transmitting a registration request message to a control apparatus in a registration procedure, and a step of receiving a registration acceptance message from the control apparatus. The message includes information A indicating whether the extension of the Local Area Data Network (LADN) service area is supported, and the registration acceptance message includes information indicating whether the extension of the LADN service area is supported. B, the user equipment, if the information B indicates that does not support the extension of the LADN service area, an area configured by one or more tracking areas, set as the LADN service area, The information B indicates that the extension of the LADN service area is supported; The different areas are to be composed area by ring area, and sets as the LADN service area.

The communication control method of the control device according to an embodiment of the present invention includes a step of receiving a registration request message from a user device in a registration procedure, and a step of transmitting a registration acceptance message to the user device. The message includes information A indicating whether the extension of the Local Area Data Network (LADN) service area is supported, and the registration acceptance message includes information indicating whether the extension of the LADN service area is supported. B, the control device, if the information A indicates that the extension of the LADN service area is not supported, an area configured by one or more tracking areas, set as the LADN service area, If the information A indicates that the extension of the LADN service area is supported, the one or more The different areas are to be composed area by ring area, it is set as the LADN service area, the registration acceptance message further comprising information C indicating the LADN service area.

According to one aspect of the present invention, in 5GS, it is possible to realize an extension of a function for providing connectivity to a LADN, and furthermore, a function for providing connectivity to an extended LADN is provided. It can be used.

FIG. 2 is a diagram illustrating an outline of a mobile communication system (EPS / 5GS). FIG. 2 is a diagram illustrating a detailed configuration of a mobile communication system (EPS / 5GS). FIG. 3 is a diagram illustrating a device configuration of a UE. FIG. 3 is a diagram illustrating a configuration of an access network device (gNB) in 5GS. FIG. 3 is a diagram illustrating a configuration of a core network device (AMF / SMF / UPF) in 5GS. It is a figure explaining a registration procedure.

最 良 The best mode for carrying out the present invention will be described with reference to the drawings.

[1. System Overview]
First, FIG. 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment, and FIG. 2 is a diagram for explaining a detailed configuration of the mobile communication system 1.

In FIG. 1, the mobile communication system 1 includes UE_A10, access network_A80, core network_A90, PDN (Packet Data Network) _A5, access network _B120, core network _B190, and DN (Data Network) _A6. Is described.

In the following, these devices and functions may be described with symbols omitted, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc. .

FIG. 2 also shows 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 the like. An interface for connecting devices and functions to each other is described.

In the following, these devices and functions, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, etc. May be omitted.

Note that an EPS (Evolved Packet System), which is a 4G system, includes an access network_A and a core network_A, but may further include a UE and / or a PDN. Further, 5GS (5G @ System), which is a 5G system, includes a UE, an access network_B, and a core network_B, but may further include a DN.

UE is a device that can be connected to a network service through 3GPP access (3GPP access network, also referred to as 3GPP AN) and / or non-3GPP access (non-3GPP access network, also referred to as non-3GPP AN). is there. The UE may be a terminal device capable of wireless communication, such as a mobile phone or a smartphone, and may be a terminal device that can be connected to both EPS and 5GS. The UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Note that UE may be expressed as a user device or a terminal device.

The access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. One or more eNBs (evolved @ Node @ B) 45 are arranged in the E-UTRAN. In the following, eNB45 may be described by omitting a symbol like eNB. When there are a plurality of eNBs, the eNBs are connected to each other by, for example, an X2 interface. One or more access points are arranged in the wireless LAN access network.

ア ク セ ス The access network_B corresponds to a 5G access network (5G AN). The 5G AN is configured with an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeB) 122 are arranged in the NG-RAN. In the following, gNB122 may be described by omitting the symbol like eNB. The gNB is a node that provides an NR (New @ Radio) user plane and a control plane to the UE, and is a node that connects to 5GCN via an NG interface (including an N2 interface or an N3 interface). That is, the gNB is a base station device newly designed for 5GS, and has a function different from that of the base station device (eNB) used in EPS that is a 4G system. When there are a plurality of gNBs, the gNBs are connected to each other by, for example, an Xn interface.

In the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. Also, a wireless LAN access network or non-3GPP @ AN may be referred to as non-3GPP access. Also, the nodes arranged in the access network_B may be collectively referred to as NG-RAN nodes.

In the following, the access network_A, and / or the access network_B, and / or the device included in the access network_A, and / or the device included in the access network_B are the access network or the access network device. In some cases.

{Core network_A} corresponds to EPC (Evolved @ Packet @ Core). EPC, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway) -U, PGW-C, PCRF (Policy and Charging Rule Rules Function), HSS (Home Subscriber Server) and the like Be placed.

コ ア Also, the core network_B corresponds to 5GCN (5G Core Network). In the 5GCN, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), UDM (Unified Data Management) and the like are arranged. Here, 5GCN may be expressed as 5GC.

In the following, the core network _A, and / or the core network _B, the device included in the core network _A, and / or the device included in the core network _B may be referred to as a core network or a core network device. There is.

The core network (core network_A and / or core network_B) is a mobile communication carrier (Mobile Network) that connects an access network (access network_A and / or access network_B) with a PDN and / or DN. The network may be an IP mobile communication network operated by a Network Operator (MNO), a core network for a mobile communication carrier that operates and manages the mobile communication system 1, or an MVNO (Mobile Virtual Network Operator). ), A virtual network such as MVNE (Mobile Virtual Network Enabler) or a core network for a virtual mobile communication service provider.

Also, FIG. 1 describes a case where the PDN and the DN are the same, but they may be different. The PDN may be a DN (Data @ Network) that provides a communication service to the UE. Note that the DN may be configured as a packet data service network, or may be configured for each service. Further, the PDN may include a connected communication terminal. Therefore, connecting to a PDN may be connecting to a communication terminal or server device arranged in the PDN. Further, transmitting / receiving user data to / from the PDN may be transmitting / receiving user data to / from a communication terminal or server device arranged in the PDN. Note that PDN may be expressed as DN, or DN may be expressed as PDN.

In the following, an access network _A, a core network _A, a PDN, an access network _B, a core network _B, at least a part of a DN, and / or one or more devices included therein are referred to as a network or a network device. In some cases. That is, the fact that the network and / or the network device sends and receives messages and / or executes procedures means that the access network _A, the core network _A, the PDN, the access network _B, the core network _B, the DN At least some, and / or one or more devices included therein, may send and receive messages and / or perform procedures.

UE The UE can also connect to the access network. Further, the UE can be connected to the core network via the access network. Further, the UE can connect to the PDN or DN via the access network and the core network. That is, the UE can transmit / receive (communicate) user data to / from the PDN or DN. When transmitting and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication may be used.

IPHere, IP communication is data communication using IP, and data is transmitted and received by IP packets. An IP packet is composed of an IP header and a payload. The payload section may include devices / functions included in EPS and data transmitted / received by devices / functions included in 5GS. Non-IP communication is data communication without using IP, and data is transmitted and received in a format different from the structure of an IP packet. For example, non-IP communication may be data communication realized by transmission and reception of application data to which an IP header has not been added, or may have another header such as a Mac header or an Ethernet (registered trademark) frame header and be transmitted by the UE. User data to be transmitted and received may be transmitted and received.

[2. Configuration of each device]
Next, the configuration of each device (UE and / or access network device and / or core network device) used in each embodiment will be described with reference to the drawings. Each device may be configured as physical hardware, may be configured as logical (virtual) hardware configured on general-purpose hardware, or may be configured as software. May be. Further, at least a part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

Note that each storage unit (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) in each device / function appearing below is, for example, a semiconductor memory, an SSD ( It consists of Solid State Drive) and HDD (Hard Disk Drive). Further, each storage unit is not only information originally set from the shipping stage, but also devices and functions other than the own device and function (for example, UE, and / or access network device, and / or core network device, and / or Or PDN and / or DN) can store various information transmitted and received. Further, each storage unit can store identification information, control information, flags, parameters, and the like included in control messages transmitted and received in various communication procedures described below. Further, each storage unit may store such information for each UE. Also, when interworking between 5GS and EPS, each storage unit may store control messages and user data transmitted and received between devices and functions included in 5GS and / or EPS. it can. At this time, not only data transmitted / received via the N26 interface but also data transmitted / received without the N26 interface can be stored.

[2.1. UE configuration]
First, an example of a device configuration of a UE (User Equipment) will be described with reference to FIG. The UE includes a control unit_A300, an antenna 310, a transmission / reception unit_A320, and a storage unit_A340. The control unit_A300, the transmission / reception unit_A320, and the storage unit_A340 are connected via a bus. The transmission / reception unit_A320 is connected to the antenna 310.

Control section_A300 is a functional section that controls the operation and functions of the entire UE. The control unit_A300 realizes various processes in the UE by reading and executing various programs stored in the storage unit_A340 as necessary.

Transceiving unit_A320 is a functional unit for performing wireless communication with a base station device (eNB or gNB) in an access network via an antenna. That is, the UE can use the transmitting / receiving unit _A320 to transmit / receive user data and / or control information to / from the access network device, and / or the core network device, and / or the PDN, and / or the DN. it can.

説明 Explaining in detail with reference to FIG. 2, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transmission / reception unit_A320. Further, the UE can communicate with the base station device (gNB) within 5G AN by using the transmission / reception unit_A320. Further, the UE can transmit and receive the AMF and the NAS (Non-Access-Stratum) message via the N1 interface by using the transmission / reception unit_A320. However, since the N1 interface is logical, communication between the UE and the AMF is actually performed via 5G AN.

Storage unit_A340 is a functional unit for storing programs, user data, control information, and the like necessary for each operation of the UE.

[2.2. GNB device configuration]
Next, an example of a device configuration of the gNB will be described with reference to FIG. The gNB includes a control unit_B500, an antenna 510, a network connection unit_B520, a transmission / reception unit_B530, and a storage unit_B540. The control unit_B500, the network connection unit_B520, the transmission / reception unit_B530, and the storage unit_B540 are connected via a bus. Transmission / reception section_B530 is connected to antenna 510.

Control unit_B500 is a functional unit that controls the operation and functions of the entire gNB. The control unit_B500 implements various processes in the gNB by reading and executing various programs stored in the storage unit_B540 as necessary.

Network connection unit_B520 is a functional unit for gNB to communicate with AMF and / or UPF. That is, the gNB can transmit / receive user data and / or control information to / from the AMF and / or the UPF using the network connection unit_B520.

Transceiving unit_B530 is a functional unit for performing wireless communication with UE via antenna 510. That is, the gNB can transmit / receive user data and / or control information to / from the UE using the transmission / reception unit_B530.

To be described in detail with reference to FIG. 2, the gNB in the 5G AN can communicate with the AMF via the N2 interface by using the network connection unit_B520, and the UPF via the N3 interface. Can communicate with Further, the gNB can communicate with the UE by using the transmission / reception unit_B530.

Storage unit_B540 is a functional unit for storing programs, user data, control information, and the like necessary for each operation of the gNB.

[2.3. AMF device configuration]
Next, an example of an AMF device configuration will be described with reference to FIG. The AMF includes 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. The AMF may be a node that handles a control plane.

Control unit_B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit_B700 implements various processes in the AMF by reading and executing various programs stored in the storage unit_B740 as necessary.

The network connection unit_B720 is a function unit for connecting the AMF to the base station device (gNB) and / or the SMF and / or the PCF and / or the UDM and / or the SCEF in the 5G AN. That is, the AMF, using the network connection unit_B720, between the base station device (gNB) in 5G AN, and / or SMF, and / or PCF, and / or UDM, and / or SCEF, Data and / or control information can be sent and received.

Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with the gNB through the N2 interface by using the network connection unit_A620, and communicate with the UDM through the N8 interface. It can communicate with the SMF via the N11 interface and can communicate with the PCF via the N15 interface. In addition, the AMF can transmit and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, communication between the UE and the AMF is actually performed via 5G AN. When the AMF supports the N26 interface, the AMF can communicate with the MME via the N26 interface by using the network connection unit_A620.

The storage unit_B740 is a functional unit for storing programs, user data, control information, and the like necessary for each operation of the AMF.

The AMF has a function of exchanging control messages with the RAN using the N2 interface, a function of exchanging NAS messages with the UE using the N1 interface, a function of encrypting and protecting the integrity of the NAS message, and a registration management function. (Registration management; RM) function, connection management (CM) function, reachability management (Reachability management) function, mobility management (Mobility management) function of UE, etc., SM (Session Management) between UE and SMF N2 for message transfer function, access authentication (Access Authentication, Access Authorization) function, security anchor function (SEA; Security Anchor Functionality), security context management (SCM; Security Context Management) function, N3IWF (Non-3GPP Interworking Function) Interface support function, NAS signal transmission / reception function via N3IWF, connection via N3IWF It has a function for authenticating the UE that.

登録 In the registration management, the RM state for each UE is managed. The RM state may be synchronized between the UE and the AMF. The RM state includes a non-registered state (RM-DEREGISTERED @ state) and a registered state (RM-REGISTERED @ state). In the RM-DEREGISTERED state, since the UE is not registered in the network, the AMF cannot reach the UE because the UE context in the AMF does not have valid location information or routing information for the UE. Further, in the RM-REGISTERED state, since the UE is registered in the network, the UE can receive a service that requires registration with the network. Note that the RM state may be expressed as a 5GMM state (5GMM @ state). In this case, the RM-DEREGISTERED state may be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as a 5GMM-REGISTERED state.

In other words, 5GMM-REGISTERED may be a state where each device has established a 5GMM context or a state where a PDU session context has been established. When each device is 5GMM-REGISTERED, UE_A10 may start transmitting and receiving user data and control messages, or may respond to paging. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may execute a registration procedure other than the registration procedure for initial registration and / or a service request procedure.

Furthermore, 5GMM-DEREGISTERED may be in a state where each device has not established a 5GMM context, may be in a state where the location information of UE_A10 is not grasped by the network, or the network may reach UE_A10. It may be in a state where it is impossible. When each device is 5GMM-DEREGISTERED, UE_A10 may start a registration procedure, or may establish a 5GMM context by executing the registration procedure.

接 続 In connection management, the CM status of each UE is managed. The CM state may be synchronized between the UE and the AMF. The CM state includes a non-connection state (CM-IDLE @ state) and a connection state (CM-CONNECTED @ state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection established with the AMF via the N1 interface. In the CM-IDLE state, the UE does not have the connection of the N2 interface (N2Nconnection) and the connection of the N3 interface (N3 connection). On the other hand, in the CM-CONNECTED state, it has a NAS signaling connection (NAS signaling connection) established with the AMF via the N1 interface. Further, in the CM-CONNECTED state, the UE may have a connection of the N2 interface (N2) connection) and / or a connection of the N3 interface (N3 connection).

Further, in connection management, the CM state in 3GPP access and the CM state in non-3GPP access may be managed separately. In this case, the CM state in 3GPP access may include a non-connection state in 3GPP access (CM-IDLE / state / over / 3GPP / access) and a connection state in 3GPP access (CM-CONNECTED / state / over / 3GPP / access). Furthermore, as the CM state in non-3GPP access, the non-connection state in non-3GPP access (CM-IDLE state over non-3GPP access) and the connection state in non-3GPP access (CM-CONNECTED state over non-3GPP access ). Note that the non-connection state may be expressed as an idle mode, and the connection state mode may be expressed as a connected mode.

Note that the CM state may be expressed as a 5GMM mode (5GMM mode). In this case, the non-connection state may be expressed as a 5GMM non-connection mode (5GMM-IDLE @ mode), and the connection state may be expressed as a 5GMM connection mode (5GMM-CONNECTED @ mode). Further, the non-connection state in 3GPP access may be expressed as a 5GMM non-connection mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connection state in 3GPP access is a 5GMM connection mode in 3GPP access (5GMM- CONNECTED mode over 3GPP access). Furthermore, the non-connection state in non-3GPP access may be expressed as a 5GMM non-connection mode in non-3GPP access (5GMM-IDLE mode over non-3GPP access), and the connection state in non-3GPP access is non- It may be expressed as a 5GMM connection mode in -3GPP access (5GMM-CONNECTED mode over non-3GPP access). Note that the 5GMM non-connection mode may be expressed as an idle mode, and the 5GMM connection mode may be expressed as a connected mode.

A Further, one or more AMFs may be arranged in the core network_B. The AMF may be an NF that manages one or more NSIs (Network \ Slice \ Instance). Further, the AMF may be a shared CP function (CCNF; \ Common \ CPNF (Control \ Plane \ Network \ Function)) shared by a plurality of NSIs.

Note that the N3IWF is a device and / or a function disposed between the non-3GPP access and the 5GCN when the UE connects to the 5GS via the non-3GPP access.

[2.4. SMF device configuration]
Next, an example of an SMF device configuration will be described with reference to FIG. The SMF includes 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. The SMF may be a node that handles the control plane.

Control unit_B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit_B700 implements various processes in the SMF by reading and executing various programs stored in the storage unit_B740 as necessary.

Network connection unit_B720 is a functional unit for connecting the SMF to the AMF, and / or the UPF, and / or the PCF, and / or the UDM. That is, the SMF can transmit and receive user data and / or control information to / from the AMF and / or the UPF and / or the PCF and / or the UDM using the network connection unit_B720.

Referring to FIG. 2 in detail, the SMF in the 5GCN can communicate with the AMF via the N11 interface by using the network connection unit_A620, and communicate with the UPF via the N4 interface. It can communicate, can communicate with PCF via N7 interface, and can communicate with UDM via N10 interface.

The storage unit_B740 is a functional unit for storing a program, user data, control information, and the like necessary for each operation of the SMF.

The SMF has a session management (Session management) function for establishing, modifying, and releasing PDU sessions, IP address allocation (IP address) for UEs and its management function, UPF selection and control function, appropriate destination (transmission destination). ), A function to send and receive the SM part of the NAS message, a function to notify that downlink data has arrived (Downlink Data Notification), and an AN via the N2 interface via AMF. Has a function of providing SM information specific to an AN (for each AN), a function of determining an SSC mode (Session / Service / Continuity / mode) for a session, a roaming function, and the like.

[2.5. Equipment configuration of UPF]
Next, an example of a device configuration of the UPF will be described with reference to FIG. The UPF includes 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. The UPF may be a node that handles the control plane.

Control unit_B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit_B700 realizes various processes in the UPF by reading and executing various programs stored in the storage unit_B740 as necessary.

Network connection unit_B720 is a functional unit for connecting the UPF to a base station device (gNB) and / or SMF and / or DN in 5G AN. That is, the UPF uses the network connection unit_B720 to transmit and receive user data and / or control information to and from the base station device (gNB) in 5G AN, and / or the SMF, and / or the DN. Can be.

Explaining in detail with reference to FIG. 2, the UPF in the 5GCN can communicate with the gNB through the N3 interface by using the network connection unit_A620, and communicate with the SMF through the N4 interface. It can communicate, can communicate with the DN via the N6 interface, and can communicate with other UPFs via the N9 interface.

The storage unit_B740 is a functional unit for storing programs, user data, control information, and the like necessary for each operation of the UPF.

UPF functions as an anchor point for intra-RAT mobility or inter-RAT mobility, and functions as an external PDU session point for interconnecting with the DN (that is, as a gateway between the DN and the core network_B, as a user, Data transfer function), packet routing and transfer function, UL CL (Uplink Classifier) function that supports the routing of multiple traffic flows for one DN, multi-homed PDU session It has a Branching point function, a QoS (Quality of Service) processing function for a user plane, a verification function of uplink traffic, buffering of downlink packets, a function of triggering downlink data notification (Downlink Data Notification), and the like.

UPUPF may be a gateway for IP communication and / or non-IP communication. In addition, the UPF may have a function of transferring IP communication, and may have a function of converting non-IP communication and IP communication. Further, a plurality of arranged gateways may be gateways connecting the core network_B and a single DN. Note that the UPF may have connectivity with another NF, and may be connected to each device via another NF.

The user plane (user @ plane) is user data (user @ data) transmitted and received between the UE and the network. The user plane may be transmitted and received using a PDN connection or a PDU session. Further, in the case of EPS, the user plane may be transmitted and received using an LTE-Uu interface, and / or an S1-U interface, and / or an S5 interface, and / or an S8 interface, and / or an SGi interface. Further, in the case of 5GS, the user plane may be transmitted and received via an interface between the UE and the NG @ RAN, and / or an N3 interface, and / or an N9 interface, and / or an N6 interface. Hereinafter, the user plane may be expressed as U-Plane.

Furthermore, the control plane (control plane) is a control message transmitted and received to perform communication control and the like of the UE. The control plane may be transmitted / received using a NAS (Non-Access-Stratum) signaling connection between the UE and the MME. Furthermore, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Furthermore, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and the NG @ RAN, and the N2 interface. Hereinafter, the control plane may be expressed as a control plane or may be expressed as a C-Plane.

Furthermore, U-Plane (User Plane; 路 UP) may be a communication path for transmitting and receiving user data, or may be configured by a plurality of bearers. Further, C-Plane (Control @ Plane; $ CP) may be a communication channel for transmitting and receiving control messages, or may be configured with a plurality of bearers.

[2.6. Description of other devices and / or functions]
Next, other devices and / or functions will be described.

PCF has a function to provide policy rules.

UDM also has an authentication information processing (Authentication credential processing) function, a user identification processing function, an access authentication function, a registration / mobility management function, a subscriber information management (subscription management) function, and the like.

PCRThe PCRF is connected to the PGW and / or PDN, and has a function of performing QoS management for data delivery. For example, QoS of a communication path between UE_A10 and PDN is managed. Furthermore, the PCRF may be a device that creates and / or manages a PCC (Policy and Charging Control) rule and / or a routing rule used when each device transmits and receives user data.

HSThe HSS is connected to the MME and / or SCEF, and has a function of managing subscriber information. The subscriber information of the HSS is referred to, for example, at the time of MME access control. Further, the HSS may be connected to a location management device different from the MME.

The SCEF is connected to the DN and / or PDN, the MME, and the HSS, and has a function as a relay device that transfers user data as a gateway connecting the DN and / or the PDN and the core network _A. . Note that SCEF may be a gateway for non-IP communication. Further, SCEF may have a function of converting non-IP communication and IP communication. Also, a plurality of such gateways may be arranged in the core network_A. The SCEF may be configured outside or inside the core network.

[3. Explanation of terms / identification information and procedures used in each embodiment]
In each embodiment, at least one term / identification information and procedure used will be described in advance.

[3.1. Explanation of terms and identification information used in each embodiment]
First, highly specialized terms used in each embodiment and identification information used in procedures will be described in advance.

Network refers to at least a part of access network_B, core network_B, and DN. One or more devices included in at least a part of the access network_B, the core network_B, and the DN may be referred to as a network or a network device. That is, that the network performs transmission / reception and / or processing of the message may mean that a device in the network (network device and / or control device) performs transmission / reception and / or processing of the message. . Conversely, the fact that a device in the network performs transmission / reception and / or processing of a message may mean that the network performs transmission / reception and / or processing of a message.

Also, an SM (Session Management) message (also referred to as NAS (Non-Access-Stratum) SM message) may be a NAS message used in a procedure for SM, and transmitted and received between UE_A10 and SMF_A230 through AMF_A240. Control message. Further, the SM message includes 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, and the like. You may. Also, the procedure for the SM may include a PDU session establishment procedure.

{The 5GS (5G @ System) service may be a connection service provided using the core network_B190. Further, the 5GS service may be a service different from the EPS service or a service similar to the EPS service.

The non-5GS service may be a service other than the 5GS service, and may include an EPS service and / or a non-EPS service.

The single registration mode is a mode in which the UE_A10 maintains a common registration state for the 5GMM state and the EMM state when the N1 mode and the S1 mode are available.

The dual registration mode is a mode in which the UE_A10 maintains the registration state independently of the 5GMM state and the EMM state when the N1 mode and the S1 mode are available. Note that, in the case of the dual registration mode, UE_A10 may be registered in the network only in the N1 mode (that is, registered in only 5GC) or may be registered in the network only in the S1 mode (registered only in the EPC). Alternatively, it may be registered in the network in both N1 mode and S1 mode (registered in both 5GC and EPC).

UEs that support both 5GC and EPC NAS for interworking between 5GS and EPC can operate in single registration mode or dual registration mode.

The S1 mode is a mode in which UE_A10 is permitted to access the EPC via E-UTRAN. In other words, the S1 mode may be a mode in which transmission and reception of a message using the S1 interface is performed. Note that the S1 interface may be composed of an S1-MME interface and an S1-U interface.

NThe N1 mode is a mode in which UE_A10 is permitted to access 5GC via a 5G access network. In other words, the N1 mode may be a mode in which transmission and reception of messages using the N1 interface are performed.

APN (Access @ Point @ Name) may be identification information for identifying an external network such as a core network and / or a PDN. Further, the APN can be used as information for selecting a gateway such as PGW_A30 / UPF_A235 that connects the core network A_90.

PD Also, the PDN (Packet Data Network) type indicates the type of PDN connection, and includes IPv4, IPv6, IPv4v6, and non-IP. If IPv4 is specified, it indicates that data is sent and received using IPv4. When IPv6 is specified, it indicates that data is transmitted and received using IPv6. When IPv4v6 is specified, it indicates that data transmission / reception is performed using IPv4 or IPv6. When non-IP is specified, it indicates that communication is to be performed by a communication method other than IP instead of communication using IP.

Also, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between the DN providing the PDU connectivity service and the UE, but is established between the UE and an external gateway. Connectivity. By establishing a PDU session via the access network_B and the core network_B in the 5GS, the UE can transmit and receive user data to and from the DN using the PDU session. Here, the external gateway may be UPF, SCEF, or the like. The UE can transmit and receive user data to and from a device such as an application server arranged in the DN using the PDU session.

Each device (UE and / or access network device and / or core network device) may manage one or more pieces of identification information in association with a PDU session. Incidentally, these identification information may include one or more of DNN, QoS rule, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and other information may be included. Further, it may be included. Further, when a plurality of PDU sessions are established, each piece of identification information associated with the PDU session may have the same content or different content.

{DNN (Data \ Network \ Name) may be identification information for identifying a core network and / or an external network such as a DN. Furthermore, the DNN can also be used as information for selecting a gateway such as PGW_A30 / UPF_A235 that connects the core network B190. Further, the DNN may be equivalent to an APN (Access @ Point @ Name).

The PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and includes IPv4, IPv6, Ethernet, and Unstructured. If IPv4 is specified, it indicates that data transmission and reception will be performed using IPv4. When IPv6 is specified, it indicates that data is transmitted and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Further, Ethernet may indicate that communication using IP is not performed. When Unstructured is specified, it indicates that data is transmitted / received to / from an application server in the DN using the point-to-point (P2P) tunneling technology. As the P2P tunneling technology, for example, a UDP / IP encapsulation technology may be used. The PDU session type may include IP in addition to the above. IP can be specified if the UE can use both IPv4 and IPv6.

Network slices (NS) are logical networks that provide specific network capabilities and network characteristics. The UE and / or the network can support a network slice (NW slice; NS) in 5GS.

A network slice instance (NSI) is composed of an instance (entity) of a network function (NF) and a set of necessary resources, and forms a network slice to be arranged. Here, the NF is a processing function in a network, which is adopted or defined in 3GPP. The NSI is an entity of the NS, which is composed of one or more core networks_B. Also, the NSI may be configured by a virtual NF (Network Function) generated using NST (Network Slice Template). Here, the NST is a logical expression of one or more NFs associated with a resource request for providing a required communication service or capability. That is, the NSI may be an aggregate in the core network_B190 configured by a plurality of NFs. The NSI may be a logical network configured to separate user data delivered by a service or the like. One or more NFs may be configured in the NS. The NF configured in the NS may or may not be a device shared with another NS. The UE and / or the devices in the network may have one or more NSSAI and / or S-NSSAI and / or UE usage type and / or one or more NSINID based registration information and / or APN. NS can be assigned. Note that UE usage type is a parameter value included in UE registration information used for identifying NSI. The UE usage type may be stored in the HSS. AMF may select SMF and UPF based on UE usage type.

S-NSSAI (Single Network Slice Selection Assistance Information) is information for identifying the NS. S-NSSAI may be configured only with SST (Slice / Service type), or may be configured with both SST and SD (Slice Differentiator). Here, the SST is information indicating the expected NS operation in terms of functions and services. The SD may be information for interpolating the SST when one NSI is selected from a plurality of NSIs indicated by the SST. The S-NSSAI may be information unique to each PLMN or standard information shared between PLMNs. Also, the network may store one or more S-NSSAIs in the registration information of the UE as the default S-NSSAI. If the UE does not send a valid S-NSSAI to the network in the registration request message when the S-NSSAI is the default S-NSSAI, the network may provide an NS related to the UE.

NNSSAI (Network (Slice Selection Assistance Information) is a group of S-NSSAI. Each S-NSSAI included in the NSSAI is information that assists the access network or the core network in selecting the NSI. The UE may store the NSSAI granted from the network for each PLMN. Also, NSSAI may be information used to select an AMF.

{SSC (Session \ Service \ Continuity)} mode indicates a mode of session service continuity (Session \ Service \ Continuity) supported by the system and / or each device in the 5G system (5GS). More specifically, the mode may indicate the type of session service continuation supported by the PDU session established between UE_A10 and the UPF. Note that SSC @ mode may be a mode indicating the type of session service continuation set for each PDU session. Furthermore, SSC @ mode may be composed of three modes, SSC @ mode @ 1, SSC @ mode @ 2, and SSC @ mode # 3. Note that the SSC @ mode associated with the PDU session does not need to be changed while the PDU session exists.

{5GMM-CONNECTED} mode with RRC inactive indication is a state indicating that the state of the NAS layer is in a connected state despite the inactive state of the RRC layer. In other words, 5GMM-CONNECTED mode with RRC inactive indication is a state where the radio bearer is released while maintaining the context of the NAS signaling connection and / or the NAS signaling connection.

The support of 5GMM-CONNECTED mode with RRC inactive indication means that the state of the NAS layer is maintained in the connected state even when a notification indicating that the RRC layer has been disabled is received from the lower layer. It may mean that it is supported. Furthermore, the use of 5GMM-CONNECTED mode with RRC inactive indication means that the state of the NAS layer is maintained in a connected state even when a notification indicating that the RRC layer has been disabled is received from a lower layer. It may mean.

The tracking area is one or more ranges that can be represented by the location information of UE_A10 managed by the core network. The tracking area may be composed of a plurality of cells. Further, the tracking area may be a range in which a control message such as paging is broadcast, or may be a range in which UE_A10 can move without performing a handover procedure. Further, the tracking area may be a routing area, a location area, or any similar area. Hereinafter, the tracking area may be a TA (Tracking @ Area).

The TA list is a list including one or a plurality of TAs assigned to UE_A10 by the network. Note that UE_A10 may be able to move without executing the tracking area update procedure while moving within one or more TAs included in the TA list. In other words, UE_A10 may be a group of information indicating the area where UE_A10 can move without executing the tracking area update procedure. Note that the TA list may be expressed as a TAI list composed of one or more TAIs {(Tracking {area} identity)}. Hereinafter, the TAI list may refer to the TA list.

{LADN} (Local Area Data Network) is a DN to which the UE can connect only at a specific place, and provides connectivity to a specific DNN (that is, LADN DNN). The LADN may be a DN that can be connected at a specific location by using a PDU session associated with a specific DNN. Further, the LADN may be a DN that can be connected at a specific location by using a PDU session associated with a combination of a specific DNN and a specific S-NSSAI.

LADN information is information related to LADN. The LADN information may be information indicating a specific LADN available to the UE. The LADN information may include LADN @ DNN and LADN service area information. More specifically, the LADN information may include one or more pieces of information existing for each LADN (hereinafter, referred to as information indicating the LADN). Further, the information indicating the LADN may include LADN @ DNN and LADN service area information. Here, LADN DNN may be information for identifying a LADN, information for identifying a DN treated as an LADN, or a DNN used when establishing a PDU session for the LADN. .

Note that when the LADN information is conventional LADN information, the LADN information may be information having the configuration described above. Specifically, when the LADN information is conventional LADN information, the LADN service area may be a conventional LADN service area.

Conversely, when the LADN information is extended LADN information, the LADN information may be information in which a part of the configuration described above is extended. Specifically, when the LADN information is extended LADN information, the LADN service area may be an extended LADN service area. Further, when the LADN information is extended LADN information, the information indicating the LADN may further include information indicating a period during which the LADN service area is valid and / or information indicating a granularity of the LADN service area. Further, when the LADN information is extended LADN information, the information indicating the LADN may further include S-NSSAI.

The {LADN service area} is an area where a PDU session for the LADN can be established. The LADN service area may be an area where connection to the LADN is possible. Further, the LADN service area may be an area indicated by the LADN service area information. Here, the LADN service area information may be information for identifying the LADN service area, and may be provided as a set of tracking areas or may be provided as a TAI (Tracking area identity) list.

Note that if the LADN service area is a conventional LADN service area, the LADN service area may be an area configured by a tracking area belonging to a registration area to which the UE is currently connected. In other words, when the LADN service area is a conventional LADN service area, the LADN service area may be an area configured by one or a plurality of tracking areas. Conversely, if the LADN service area is an extended LADN service area, the LADN service area may be an area configured by the tracking area, or may be covered by some base stations in the tracking area. Area. Further, when the LADN service area is an extended LADN service area, the LADN service area may be an area having a size other than the area configured by the tracking area, or may be an area that does not depend on the tracking area. Is also good. In other words, if the LADN service area is an extended LADN service area, the LADN service area may be an area configured by one or more tracking areas, or may be configured by one or more tracking areas. The area may be different from the area.

{Furthermore, when the LADN service area is an area constituted by one or a plurality of tracking areas, the LADN service area information may be a tracking area ID list constituted by one or a plurality of tracking area IDs. Conversely, if the LADN service area is an area different from the area configured by one or more tracking areas, the LADN service area information may be information that requires assistance from RAN (Radio Access Network). Alternatively, the information may not require the assistance of the RAN. Here, the information requiring RAN assistance may be cell information or base station information. Further, the information requiring RAN assistance may be a cell ID or a base station ID. Further, the information that requires RAN assistance is not limited to these, and may be information defined by RAN. Further, the information that does not require the assistance of the RAN may be physical position information or position information that can be obtained by an application. Further, the information that does not require the assistance of the RAN is not limited thereto, and may be information that can be acquired by other than the RAN. Here, the RAN may be expressed as an access network. Conversely, an access network may be referred to as a RAN.

The extension of the LADN service area may mean using a LADN service area having a different granularity from the conventional LADN service area. Further, the extension of the LADN service area may mean that extended LADN information different from conventional LADN information is used. Further, extending the LADN service area may mean connecting to an extended LADN different from the conventional LADN.

In other words, when each device supports expansion of the LADN service area, in addition to the conventional LADN service area, an extended LADN service area different from the conventional LADN service area may be adaptable. Furthermore, when each device supports the extension of the LADN service area, in addition to the conventional LADN information, extended LADN information different from the conventional LADN information may be usable. Further, when each device supports expansion of the LADN service area, it may be possible to connect to an extended LADN different from the conventional LADN in addition to the conventional LADN.

Conversely, if some of the devices do not support the extension of the LADN service area, adaptation of the extended LADN service area is not possible, and only the conventional LADN service area may be adaptable. Furthermore, if some of the devices do not support the extension of the LADN service area, the use of the extended LADN information may not be possible, and only the conventional LADN information may be available. Furthermore, if some of the devices do not support expansion of the LADN service area, connection to the expanded LADN may not be possible, but only connection to the conventional LADN may be possible.

Also, if each device supports the use restriction of the extension of the LADN service area, adaptation of the extended LADN service area is not possible, and only the conventional LADN service area may be adaptable. Further, when each device supports the use restriction of the extension of the LADN service area, the extended LADN information may not be used, and only the conventional LADN information may be used. Further, when each device supports the use restriction of the extension of the LADN service area, the connection to the extended LADN may not be possible, and only the connection to the conventional LADN may be possible.

Conversely, if each device does not support the use restriction of the extension of the LADN service area, the extended LADN service area may be adaptable. Further, if each device does not support the use restriction of the extension of the LADN service area, the extended LADN information may be available. Further, when each device does not support the use restriction of the extension of the LADN service area, it may be possible to connect to the extended LADN.

The {PDU session for LADN (PDU {session} for {LADN)} is a PDU session associated with the DNN associated with the LADN. The PDU session for the LADN may be a PDU session established for the LADN. In other words, it may be a PDU session established between the UE and the LADN, or a PDU session used for user data communication between the UE and the LADN. The PDU session for LADN may be a PDU session that can be established only in the LADN service area. In other words, the UE may be able to establish a PDU session for LADN by using a specific DNN at a specific location. Further, in other words, the UE may be able to establish a PDU session for a LADN by using a combination of a specific DNN and a specific S-NSSAI at a specific location.

The first identification information is information indicating whether or not the UE supports expansion of the LADN service area. The first identification information may be a bit indicating that the extension of the LADN service area is supported, or a bit indicating that the extension of the LADN service area is not supported.

{Circle around (1)} The first identification information may be information indicating whether or not the UE supports the use restriction of the extension of the LADN service area. Furthermore, the first identification information may be a bit indicating that the usage restriction of the extension of the LADN service area is supported, or a bit indicating that the usage restriction of the extension of the LADN service area is not supported. Good.

{Further, the first identification information may be a bit constituting a 5GMM capability information element {(5GMM capability information element)} indicating the capability of the UE in 5G. Furthermore, the first identification information is information selected and determined based on UE capability information, and / or UE settings, and / or UE status, and / or user policies, and / or application requirements. It may be.

Eleventh identification information is information indicating whether or not the network supports expansion of the LADN service area. The eleventh identification information may be a bit indicating that the extension of the LADN service area is supported, or a bit indicating that the extension of the LADN service area is not supported.

{Circle around (11)} The eleventh identification information may be information indicating whether or not the network supports the use restriction of extension of the LADN service area. Further, the eleventh identification information may be a bit indicating that the usage restriction of the extension of the LADN service area is supported, or a bit indicating that the usage restriction of the extension of the LADN service area is not supported. Good.

{Furthermore, the eleventh identification information may be a bit constituting a 5GS network function support information element {5GS network function support information element} that indicates the capability of the network in 5G. Further, the eleventh identification information may be the first identification information received by the network, and / or the information associated with the DN, and / or the information associated with the NSI, and / or the capability information of the network. And / or information determined and / or determined based on an operator policy, and / or network status, and / or user registration information, and the like. Furthermore, the eleventh identification information may be information that is selected and determined based on other identification information selected by the network in this procedure.

12Twelfth identification information is LADN information. The twelfth identification information may be LADN information permitted by the network, or may be valid LADN information. Further, the twelfth identification information may be information transmitted and received when a LADN service area exists in a registration area to which the UE is connected.

Further, when the first identification information and / or the eleventh identification information is information indicating that the extension of the LADN service area is supported, the twelfth identification information is different from the conventional LADN information and is extended. May be LADN information. Conversely, if the first identification information and / or the eleventh identification information is information indicating that the extension of the LADN service area is not supported, the twelfth identification information may be conventional LADN information.

Further, when the first identification information and / or the eleventh identification information is information indicating that the usage limitation of the extension of the LADN service area is supported, the twelfth identification information is the conventional LADN information. Good. Conversely, if the first identification information and / or the eleventh identification information is information indicating that the usage restriction of the extension of the LADN service area is not supported, the twelfth identification information is different from the conventional LADN information. It may be different, extended LADN information.

Further, the twelfth identification information is the first identification information received by the network, and / or the information associated with the DN, and / or the information associated with the NSI, and / or the capability information of the network, And / or information determined and / or determined based on an operator policy, and / or network status, and / or user registration information, and the like. Further, the twelfth identification information may be information that is selected and determined based on other identification information selected by the network in this procedure.

13The thirteenth identification information is information indicating the granularity of the LADN service area. The thirteenth identification information may be information indicating the size of the LADN service area. Further, the thirteenth identification information may be transmitted / received in association with the twelfth identification information, or information existing for each LADN included in the twelfth identification information (hereinafter, referred to as information indicating the LADN). ) May be transmitted and received. Further, the thirteenth identification information may be transmitted and received for each piece of information indicating the LADN. In this case, the thirteenth identification information may be different for each piece of information indicating a LADN, or may be the same between pieces of information indicating a plurality of LADNs.

When the thirteenth identification information is transmitted and received in association with the information indicating the LADN, the thirteenth identification information is the LADN service area information included in the information indicating the LADN (hereinafter, the LADN service area information and the ) May be information indicating the granularity.

For example, the thirteenth identification information may be information indicating that an area constituted by one or more tracking areas is used as the LADN service area. In this case, a tracking area ID list composed of one or more tracking area IDs may be set in the LADN service area information.

Furthermore, the thirteenth identification information may be information indicating that an area different from an area constituted by one or more tracking areas is used as the LADN service area. In this case, information that requires RAN assistance or information that does not require RAN assistance may be set in the LADN service area information.

Furthermore, the thirteenth identification information may be information indicating that an area covered by some base stations in the tracking area is used as the LADN service area. In this case, a cell ID and / or a cell ID list including one or more cell IDs may be set in the LADN service area information.

Furthermore, the thirteenth identification information may be information indicating that an area set independent of the tracking area is used as the LADN service area. In this case, physical location information may be set in the LADN service area information.

Here, if the thirteenth identification information is not transmitted / received and / or the thirteenth identification information is invalid information, an area configured by one or more tracking areas may be used as the LADN service area. . Further, a tracking area ID list including one or a plurality of tracking area IDs may be set in the LADN service area information. Note that the granularity and / or the LADN service area information indicated by the thirteenth identification information need not be limited to these.

Further, the thirteenth identification information is the first identification information received by the network, and / or the information associated with the DN, and / or the information associated with the NSI, and / or the capability information of the network, And / or information determined and / or determined based on an operator policy, and / or network status, and / or user registration information, and the like. Furthermore, the thirteenth identification information may be information that is selected and determined based on other identification information selected by the network in this procedure.

14The fourteenth identification information is information indicating a period during which the LADN service area is valid. The fourteenth identification information may be information indicating whether or not the LADN service area is currently valid. Further, the fourteenth identification information may be transmitted / received in association with the twelfth identification information, or information existing for each LADN included in the twelfth identification information (hereinafter, referred to as information indicating the LADN). ) May be transmitted and received. Further, the fourteenth identification information may be transmitted and received for each piece of information indicating the LADN. In this case, the fourteenth identification information may be different for each piece of information indicating a LADN, or may be the same between pieces of information indicating a plurality of LADNs.

Here, the information indicating the period during which the LADN service area is valid may be information indicating the time during which the LADN service area is valid, or information indicating the period indicated by a specific date and time. Is also good. Further, the information indicating the period during which the LADN service area is valid may be information indicating a specific time zone or information indicating a specific day of the week. Further, the information indicating the period during which the LADN service area is valid may be information indicating a specific day or information indicating a specific week. Further, the information indicating the period during which the LADN service area is valid may be information indicating a specific month or information indicating a specific year.

Here, if the fourteenth identification information is not transmitted / received and / or the fourteenth identification information is invalid information, the LADN information and / or the information indicating the LADN are updated during a period in which the LADN service area is valid. It may be until it is done. Note that the information indicating the period during which the LADN service area is valid is not limited to these.

Further, the fourteenth identification information may be the first identification information received by the network, and / or the information associated with the DN, and / or the information associated with the NSI, and / or the capability information of the network. And / or information determined and / or determined based on an operator policy, and / or network status, and / or user registration information, and the like. Further, the fourteenth identification information may be information selected and determined based on other identification information selected by the network in this procedure.

[3.2. Explanation of procedures used in each embodiment]
Next, a procedure used in each embodiment will be described. The procedures used in each embodiment include a registration procedure, a PDU session establishment procedure, and a UE configuration update procedure. Hereinafter, each procedure will be described.

In each embodiment, as shown in FIG. 2, HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are respectively the same device (that is, the same physical device). Hardware, or the same logical hardware, or the same software) will be described as an example. However, the contents described in the present embodiment can also be applied to a case where these are configured as different devices (that is, different physical hardware, different logical hardware, or different software). For example, data transmission / reception may be performed directly between them, data may be transmitted / received via the N26 interface between the AMF and the MME, or data may be transmitted / received via the UE.

[3.2.1. Registration procedure]
First, the registration procedure will be described with reference to FIG. The registration procedure is a procedure in 5GS. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to register with the access network_B and / or the core network_B and / or the DN under the initiative of the UE. If the UE has not been registered in the network, the UE can execute this procedure at an arbitrary timing such as when power is turned on. In other words, the UE can start this procedure at an arbitrary timing in a non-registered state (RM-DEREGISTERED state). Also, each device (especially UE and AMF) can transition to the registered state (RM-REGISTERED state) based on the completion of the registration procedure.

Further, the registration procedure updates the location registration information of the UE in the network, and / or notifies the status of the UE from the UE to the network periodically, and / or updates specific parameters related to the UE in the network. Procedure may be used.

The UE may start the registration procedure when mobility across TAs is performed. In other words, the UE may start the registration procedure when moving to a TA different from the TA indicated in the retained TA list. Further, the UE may start this procedure when the running timer expires. Further, the UE may start the registration procedure when the context of each device needs to be updated due to disconnection or invalidation of the PDU session. Further, the UE may initiate a registration procedure when a change occurs in capability information and / or preferences regarding UE PDU session establishment. Further, the UE may periodically initiate a registration procedure. Further, the UE may start the registration procedure based on the completion of the UE setting update procedure. Note that the UE is not limited to these, and can execute the registration procedure at any timing.

First, the UE starts a registration procedure by transmitting a registration request (Registration @ request) message to the AMF (S800) (S802) (S804). Specifically, the UE transmits an RRC message including a registration request message to 5G @ AN (or gNB) (S800). The registration request message is a NAS message. Further, the RRC message may be a control message transmitted and received between the UE and the 5G @ AN (or gNB). Further, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. Note that the NAS layer is a higher layer than the RRC layer.

Here, the UE can transmit at least the first identification information included in the registration request message and / or the RRC message, but control messages different from these, for example, a layer lower than the RRC layer (for example, , MAC layer, RLC layer, PDCP layer). The UE may transmit the identification information to indicate that the UE supports each function, or may indicate a request from the UE. Further, when a plurality of pieces of identification information are transmitted and received, two or more pieces of identification information of these pieces of identification information may be configured as one or more pieces of identification information. The information indicating the support of each function and the information indicating a request to use each function may be transmitted and received with the same identification information or may be transmitted and received as different identification information.

If the UE supports the extension of the LADN service area, the information indicating the support of the extension of the LADN service area may be set to the first identification information, or the first indicating the support of the extension of the LADN service area. May be included in the registration request message and transmitted. Conversely, if the UE does not support the extension of the LADN service area, the UE may set information indicating that the extension of the LADN service area is not supported as the first identification information, or the extension of the LADN service area. May be included in the registration request message and transmitted, or the first identification information may not be transmitted.

Further, when the UE supports the use restriction of the extension of the LADN service area, the information indicating the support of the use restriction of the extension of the LADN service area may be set as the first identification information, or the LADN service area. The first identification information indicating the support of the use restriction of the extension may be included in the registration request message and transmitted. Conversely, if the UE does not support the use restriction of the extension of the LADN service area, the UE may set information indicating that the use restriction of the extension of the LADN service area is not supported in the first identification information. Alternatively, the first identification information indicating that the usage restriction of the extension of the LADN service area is not supported may be included in the registration request message and transmitted, or the first identification information may not be transmitted.

Furthermore, the UE may transmit the first identification information to indicate that the UE supports extension of the LADN service area. In this case, the first identification information may be information indicating support for extension of the LADN service area.

Conversely, the UE may transmit the first identification information to indicate that the UE supports the use restriction of the extension of the LADN service area. In this case, the first identification information may be information indicating support for use restriction of extension of the LADN service area.

Also, the UE, by transmitting the registration request message including an SM message (for example, a PDU session establishment request message), or by transmitting an SM message with the registration request message (for example, a PDU session establishment request message), The PDU session establishment procedure may be started during the registration procedure.

Upon receiving the RRC message including the registration request message, the {5G} AN (or gNB) selects an AMF to which the registration request message is transferred (S802). Note that the 5G @ AN (or gNB) can select the AMF based on information included in the registration request message and / or the RRC message. 5G @ AN (or gNB) extracts the registration request message from the received RRC message, and transfers the registration request message to the selected AMF (S804).

When the AMF receives the registration request message, it can execute the first condition determination. The first condition determination is for determining whether the network (or AMF) accepts the request of the UE. The AMF starts the procedure of FIG. 6 (A) when the first condition determination is true, and starts the procedure of FIG. 6 (B) when the first condition determination is false.

Note that the first condition determination is to receive a registration request message, and / or each identification information included in the registration request message, and / or subscriber information, and / or network capability information, and / or an operator policy, and It may be executed based on network status, and / or user registration information, and / or the context held by the AMF, and the like. For example, if the network grants the UE request, the first condition determination may be true, and if the network does not grant the UE request, the first condition determination may be false. Further, the network of the registration destination of the UE, and / or a device in the network, if the function requested by the UE is supported, the first condition determination is true, does not support the function requested by the UE In this case, the first condition determination may be false. Further, when transmitted and received identification information is permitted, the first condition determination may be true, and when transmitted and received identification information is not permitted, the first condition determination may be false. Note that the condition for determining whether the first condition is true or false is not limited to the above-described condition.

First, the case where the first condition determination is true will be described. The AMF can first execute the fourth condition determination in the procedure of FIG. 6A. The fourth condition determination is for determining whether or not the AMF transmits / receives an SM message to / from the SMF.

Note that the fourth condition determination may be performed based on whether the AMF has received the SM message. Further, the fourth condition determination may be executed based on whether the registration request message includes the SM message. For example, if the AMF receives the SM message, and / or if the SM message was included in the registration request message, the fourth condition determination may be true, if the AMF did not receive the SM message, If the registration request message does not include the SM message, the fourth condition determination may be false. The condition for determining whether the fourth condition is true or false is not limited to the above-described condition.

The AMF selects the SMF when the fourth condition determination is true, and performs transmission / reception of the SM message with the selected SMF, whereas when the fourth condition determination is false, Are not executed (S806). In addition, even when the fourth condition determination is true, the AMF may stop the procedure of FIG. 6A when receiving the SM message indicating rejection from the SMF. At this time, the AMF can start the procedure of FIG. 6 (B).

Note that the AMF can notify the SMF of the identification information received in the registration request message when transmitting and receiving the SM message with the SMF in S806. The SMF can acquire the identification information received from the AMF by transmitting / receiving the SM message to / from the AMF.

Next, the AMF receives the registration request message, and / or based on the completion of transmission and reception of the SM message between the SMF, as a response message to the registration request message, via 5GAN (or gNB), to the UE A registration acceptance (Registration @ accept) message is transmitted (S808). For example, if the fourth condition determination is true, the AMF may send a registration acceptance message based on receiving a registration request message from the UE. When the fourth condition determination is false, the AMF may transmit a registration acceptance message based on the completion of transmission and reception of the SM message with the SMF. Note that the registration acceptance message is a NAS message transmitted and received on the N1 interface, and is transmitted and received between the UE and 5G @ AN (gNB) by being included in the RRC message.

The AMF may transmit the registration acceptance message including at least one of the eleventh to fourteenth identification information. The AMF may indicate that the network supports each function by transmitting these identification information, or may indicate that the request of the UE has been accepted. Further, when a plurality of pieces of identification information are transmitted and received, two or more pieces of identification information of these pieces of identification information may be configured as one or more pieces of identification information. The information indicating the support of each function and the information indicating a request to use each function may be transmitted and received with the same identification information or may be transmitted and received as different identification information.

When the AMF supports the extension of the LADN service area, the information indicating the support of the extension of the LADN service area may be set to the eleventh identification information, or the eleventh information indicating the support of the extension of the LADN service area may be set. May be included in the registration acceptance message and transmitted. Conversely, if the AMF does not support the extension of the LADN service area, the AMF may set information indicating that the extension of the LADN service area is not supported in the eleventh identification information, or the extension of the LADN service area. May be included in the registration acceptance message and transmitted, or the eleventh identification information may not be transmitted.

Further, when the AMF supports the use restriction of the extension of the LADN service area, the AMF may set information indicating the support of the use restriction of the extension of the LADN service area in the eleventh identification information, Eleventh identification information indicating support for the use restriction of the extension may be included in the registration acceptance message and transmitted. Conversely, if the AMF does not support the use restriction of the extension of the LADN service area, the AMF may set information indicating that the use restriction of the extension of the LADN service area is not supported in the eleventh identification information. Alternatively, the eleventh identification information indicating that the usage restriction of the extension of the LADN service area is not supported may be included in the registration acceptance message and transmitted, or the eleventh identification information may not be transmitted.

Furthermore, the AMF may indicate that the network supports extension of the LADN service area by transmitting the eleventh identification information. Further, the AMF may indicate that extension of the LADN service area is available by transmitting the eleventh identification information. Further, the AMF may indicate that the network has authorized the use of the extension of the LADN service area by transmitting the eleventh identification information. In this case, the eleventh identification information may be information indicating support for extension of the LADN service area.

Conversely, the AMF sends the eleventh identification indicating that it does not support the extension of the LADN service area, or the network does not support the extension of the LADN service area by not sending the eleventh identification. May be indicated. Further, the AMF indicates that the extension of the LADN service area is not available by sending an eleventh identification indicating that the extension of the LADN service area is not supported, or not transmitting the eleventh identification. You may. In addition, the AMF sends the eleventh identity indicating that it does not support the extension of the LADN service area, or does not send the eleventh identity to allow the network to use the extension of the LADN service area. May be indicated.

Furthermore, the AMF may indicate that the network supports the use restriction of the extension of the LADN service area by transmitting the eleventh identification information. Further, the AMF may indicate that the use of the extension of the LADN service area is restricted by transmitting the eleventh identification information. In this case, the eleventh identification information may be information indicating support for use restriction of extension of the LADN service area.

Conversely, the AMF sends the eleventh identification information indicating that it does not support the use restriction of the extension of the LADN service area, or does not send the eleventh identification information, so that the network can It may indicate that usage restrictions are not supported. In addition, the AMF restricts the use of the extension of the LADN service area by transmitting the eleventh identification information indicating that it does not support the use restriction of the extension of the LADN service area, or by not transmitting the eleventh identification information. May be indicated.

Here, the AMF may transmit the eleventh identification information based on the first identification information. Specifically, when the first identification information is information indicating support for extension of the LADN service area, the AMF may transmit, to the UE, eleventh identification information indicating support for extension of the LADN service area. . Conversely, if the first identification information is information indicating that the extension of the LADN service area is not supported, the AMF transmits to the UE the eleventh identification information indicating that the extension of the LADN service area is not supported. Is also good.

Further, the AMF is information indicating that the first identification information supports the use restriction of the extension of the LADN service area, and further, if the AMF decides to restrict the use of the extension of the LADN service area, the LADN service area May be set to the eleventh identification information, or the eleventh identification information indicating the usage restriction of the extension of the LADN service area may be transmitted to the UE. Conversely, if the first identification information is information indicating that the extension of the LADN service area is not supported, the AMF does not have to transmit the eleventh identification information.

Furthermore, the AMF may indicate that the network supports LADN or indicate that connection to the LADN is permitted by transmitting the twelfth identification information. Further, the AMF notifies the UE of the list of DNNs available for connection to the LADN and / or the LADN service area which is an area where the connection to the LADN is possible by transmitting the twelfth identification information. May be. Further, the AMF may notify the UE of one or more S-NSSAIs available for connection to the LADN by transmitting the twelfth identification information. Note that the S-NSSAI that can be used for connecting to the LADN may be associated with the DNN and / or the LADN service area that can be used for connecting to the LADN.

Here, the AMF may transmit the twelfth identification information based on the first identification information. Specifically, when the first identification information is information indicating support for extension of the LADN service area, the AMF may set the extended LADN service area as the LADN service area, or The information may be set as LADN information, or the set LADN information may be transmitted to the UE as twelfth identification information. Conversely, if the first identification information is information indicating that the extension of the LADN service area is not supported, the AMF may set the conventional LADN service area as the LADN service area, or It may be set as LADN information, or the set LADN information may be transmitted to the UE as twelfth identification information.

AMF may further indicate the granularity of the LADN service area by transmitting the thirteenth identification information. More specifically, the AMF transmits the thirteenth identification information together with the twelfth identification information, so that the granularity of the LADN service area indicated by the LADN service area information included in the LADN information indicated by the twelfth identification information May be indicated, or an area that can be used as the LADN service area may be notified. Specifically, the AMF transmits the thirteenth identification information together with the twelfth identification information, so that the LADN service area indicated by the LADN service area information included in the twelfth identification information has one or more tracking information. It may indicate that the area is constituted by an area, or may indicate that the area is different from an area constituted by one or more tracking areas. Further, the AMF may transmit the thirteenth identification information together with the twelfth identification information to indicate that the tracking area ID list is included as the LADN service area information. It may indicate that necessary information is included, or may indicate that information that does not require RAN assistance is included.

Here, the AMF may determine whether to transmit the thirteenth identification information based on the first identification information. Specifically, the AMF may transmit the thirteenth identification information to the UE when the first identification information is information indicating support for extension of the LADN service area. Conversely, if the first identification information is information indicating that the extension of the LADN service area is not supported, the AMF may not need to transmit the thirteenth identification information to the UE.

Furthermore, the AMF may indicate the period during which the LADN service area is valid by transmitting the fourteenth identification information. More specifically, the AMF transmits the fourteenth identification information together with the twelfth identification information, so that the LADN service area indicated by the LADN service area information included in the LADN information indicated by the twelfth identification information is valid. May be indicated.

Here, the AMF may determine whether to transmit the fourteenth identification information based on the first identification information. Specifically, the AMF may transmit the fourteenth identification information to the UE when the first identification information is information indicating support for extension of the LADN service area. Conversely, if the first identification information is information indicating that the extension of the LADN service area is not supported, the AMF may not need to transmit the fourteenth identification information to the UE.

Further, the AMF transmits the eleventh identification information, together with the twelfth identification information, and / or the thirteenth identification information, and / or the fourteenth identification information, so that the extended LADN information, and / or It may indicate that the extended LADN service area can be used, and may notify the available LADN information and / or the LADN service area information. In this case, the eleventh identification information may be information indicating support for extension of the LADN service area, and the twelfth identification information may be extended LADN information.

Conversely, the AMF transmits the eleventh identification information, and / or the twelfth identification information, and does not transmit the thirteenth identification information, and / or the fourteenth identification information. And / or may indicate that use of the extended LADN service area is not possible. In other words, the AMF transmits the eleventh identification information, and / or the twelfth identification information, and does not transmit the thirteenth identification information, and / or the fourteenth identification information, so that the conventional LADN information, and It may indicate that a conventional LADN service area can be used, and may notify the available LADN information and / or LADN service area information. In this case, the eleventh identification information may be information indicating that expansion of the LADN service area is not supported, and the twelfth identification information may be conventional LADN information.

Further, the AMF transmits the twelfth identification information, the eleventh identification information, and / or the thirteenth identification information, and / or does not transmit the fourteenth identification information, thereby expanding the LADN information, and It may indicate that the use of the extended LADN service area is not possible. In other words, the AMF transmits the twelfth identification information, the eleventh identification information, and / or the thirteenth identification information, and / or by not transmitting the fourteenth identification information, the conventional LADN information, and It may indicate that a conventional LADN service area can be used, and may notify the available LADN information and / or LADN service area information. In this case, the twelfth identification information may be conventional LADN information.

The AMF determines which identification information among the identification information of the eleventh to fourteenth to be included in the registration acceptance message by each received identification information and / or subscriber information, and / or network capability information, and / or Alternatively, the selection and the determination may be made based on an operator policy, and / or network status, and / or user registration information, and / or a context held by the AMF.

The AMF can also transmit an SM message (for example, a PDU session establishment acceptance message) in the registration acceptance message, or send an SM message (for example, a PDU session establishment acceptance message) together with the registration acceptance message. However, this transmission method may be executed when an SM message (for example, a PDU session establishment request message) is included in the registration request message and the fourth condition determination is true. Further, this transmission method may be executed when the SM message (for example, the PDU session establishment request message) is included together with the registration request message and the fourth condition determination is true. By performing such a transmission method, the AMF can indicate that the procedure for the SM has been accepted in the registration procedure.

In addition, the AMF receives the received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or The registration acceptance message may be transmitted based on the context or the like held by the AMF to indicate that the request from the UE has been accepted.

Further, the AMF may transmit the registration acceptance message including information indicating that some requests of the UE have been rejected, or may transmit information indicating that some requests of the UE have been rejected. Doing so may indicate why some of the UE's requests were rejected. Further, the UE may recognize why some of the UE's requests were rejected by receiving information indicating that some of the UE's requests were rejected. Note that the reason for rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

The UE receives the registration acceptance message via the 5G AN (gNB) (S808). By receiving the registration acceptance message, the UE can recognize that the request of the UE by the registration request message has been accepted and the contents of various kinds of identification information included in the registration acceptance message.

The UE can further transmit a registration completion message to the AMF via 5G @ AN (gNB) as a response message to the registration acceptance message (S810). Note that, when the UE receives the SM message such as the PDU session establishment acceptance message, the registration completion message may be transmitted including the SM message such as the PDU session establishment completion message, or by including the SM message. , SM may be completed. Here, the registration completion message is a NAS message transmitted and received on the N1 interface, and is transmitted and received between the UE and the 5G @ AN (gNB) by being included in the RRC message.

The AMF receives the registration completion message via the 5G AN (gNB) (S810). In addition, each device completes the procedure of FIG. 6A based on transmission / reception of the registration acceptance message and / or the registration completion message.

Next, the case where the first condition determination is false will be described. In the procedure of FIG. 6B, the AMF transmits a registration rejection (Registration @ reject) message to the UE via 5G @ AN (gNB) as a response message to the registration request message (S812). Here, the registration rejection message is a NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and 5G @ AN (gNB) by being included in the RRC message.

Note that the AMF may transmit the registration reject message to indicate that the UE request by the registration request message has been rejected. Further, the AMF may transmit the registration rejection message with information indicating the reason for the rejection, or may indicate the reason for the rejection by transmitting the reason for the rejection. Further, the UE may recognize the reason why the request of the UE was rejected by receiving information indicating the reason why the request of the UE was rejected. Note that the reason for rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

The UE receives the registration reject message via the 5G AN (gNB) (S812). By receiving the registration rejection message, the UE can recognize that the request of the UE by the registration request message has been rejected and the contents of various identification information included in the registration rejection message. Further, the UE may recognize that the request of the UE has been rejected if the UE does not receive the registration rejection message even after a predetermined period has elapsed after transmitting the registration request message. Each device completes the procedure (B) in this procedure based on the transmission and reception of the registration rejection message.

Note that the procedure shown in FIG. 6B may be started when the procedure shown in FIG. 6A is stopped. In the procedure of FIG. 6A, if the fourth condition determination is true, the AMF may transmit a registration rejection message including an SM message indicating rejection such as a PDU session establishment rejection message. Including a SM message indicating rejection may indicate that the procedure for SM has been rejected. In that case, the UE may further receive an SM message indicating rejection, such as a PDU session establishment rejection message, or recognize that the procedure for SM has been rejected.

Each device completes the registration procedure based on the completion of the procedure of (A) or (B) in FIG. Note that each device may transition to a state where the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure of (A) in FIG. 6, or may complete the procedure of (B) in FIG. , The UE may maintain a state in which the UE is not registered in the network (RM_DEREGISTERED @ state), or may transition to a state in which the UE is not registered in the network. The transition of each device to each state may be performed based on completion of a registration procedure, or may be performed based on establishment of a PDU session.

Further, each device may execute a process based on information transmitted and received in the registration procedure based on completion of the registration procedure. For example, when information indicating that some requests of the UE are rejected is transmitted and received, the reason why the request of the UE was rejected may be recognized. Furthermore, each device may perform this procedure again based on the reason that the request of the UE has been rejected, or may perform the registration procedure for the core network_B or another cell.

Furthermore, based on the completion of the registration procedure, the UE may store the identification information received together with the registration acceptance message and / or the registration rejection message, or may recognize the network decision.

For example, when receiving the eleventh identification information, the UE may recognize that the network supports the extension of the LADN service area. Further, when receiving the eleventh identification information, the UE may recognize that the use of the extension of the LADN service area is permitted. In other words, when the UE receives the eleventh identification information, not only the area configured by one or more tracking areas, but also the area different from the area configured by one or more tracking areas, the LADN service It may be recognized that it can be set as an area, or that it can be used as a LADN service area. When receiving the eleventh identification information, the UE may recognize that it is possible to change the LADN service area depending on time. In these cases, the eleventh identification information may be information indicating support for extension of the LADN service area. Further, in these cases, the UE may use the extended LADN information, and / or the extended LADN service area to establish a PDU session for the LADN or to communicate with the LADN. Is also good.

Conversely, if the UE receives the eleventh identification information indicating that it does not support the extension of the LADN service area, or does not receive the eleventh identification information, the network supports the extension of the LADN service area. You may recognize that it is not. Further, when the UE receives the eleventh identification information indicating that it does not support the extension of the LADN service area, or does not receive the eleventh identification information, the use of the extension of the LADN service area is permitted. You may recognize that there is not. In other words, when the UE receives the eleventh identification information indicating that the extension of the LADN service area is not supported, or does not receive the eleventh identification information, the UE is configured by one or more tracking areas. It may be recognized that only the area can be set as the LADN service area, or that it can be used as the LADN service area. When the UE receives the eleventh identification information indicating that the extension of the LADN service area is not supported or does not receive the eleventh identification information, it is not possible to change the LADN service area by time. May be recognized. In these cases, the UE may use the conventional LADN information and / or the conventional LADN service area to establish a PDU session for the LADN or to communicate with the LADN.

Furthermore, when the UE receives the eleventh identification information, the UE may recognize that the network supports the use restriction of the extension of the LADN service area. Furthermore, when receiving the eleventh identification information, the UE may recognize that the use of the extension of the LADN service area is restricted. In this case, the eleventh identification information may be information indicating support for use restriction of extension of the LADN service area.

Conversely, when the UE receives the eleventh identification information indicating that it does not support the use restriction of the extension of the LADN service area, or when the network does not receive the eleventh identification information, the network extends the LADN service area. It may recognize that it does not support the use restriction of. Further, if the UE receives the eleventh identification information indicating that it does not support the use restriction of the extension of the LADN service area, or if the UE does not receive the eleventh identification information, the use of the extension of the LADN service area is not performed. You may recognize that you are not restricted. When the use of the extension of the LADN service area is restricted, the UE may be prohibited from using the extended LADN service area.

Further, when receiving the twelfth identification information, the UE may recognize that the network supports LADN, or may recognize that connection to the LADN has been permitted. Furthermore, the UE, when receiving the twelfth identification information, may recognize a list of DNNs available for connection to the LADN, and / or a LADN service area that is an area where connection to the LADN is possible. And may be stored in context. Further, when the UE receives the twelfth identification information, the UE may recognize or store one or more S-NSSAIs available for connection to the LADN in the context. Further, the UE may recognize that the S-NSSAI available for connection to the LADN and the DNN available for connection to the LADN, and / or the LADN service area are associated, May be stored in the context in association with the S-NSSAI available in the connection to the DDN and / or the LADN service area available in the connection to the LADN.

In other words, when receiving the twelfth identification information, the UE may recognize that a PDU session for the LADN associated with the received LADNLADNN can be established, or the received LADN S- It may recognize that a PDU session for the LADN associated with NSSAI can be established. Furthermore, when the UE receives the twelfth identification information, the UE may recognize that a PDU session for the LADN associated with the received combination of LADN DNN and LADN S-NSSAI can be established. .

Further, in other words, when the UE receives the twelfth identification information, the UE may recognize that the LADN service area is an area in which a PDU session for the LADN associated with LADN DNN can be established. However, it may recognize that the PDU session for the LADN associated with the LADN @ S-NSSAI can be established. Furthermore, when the UE receives the twelfth identification information, the received LADN service area is an area where a PDU session for the LADN associated with the combination of LADN DNN and LADN S-NSSAI can be established. You may recognize that.

Furthermore, upon receiving the thirteenth identification information, the UE may recognize the granularity of the LADN service area. More specifically, the UE, together with the twelfth identification information, when receiving the thirteenth identification information, may recognize the granularity of the LADN service area indicated by the LADN service area information included in the twelfth identification information, Alternatively, it may be stored in the context in association with the LADN service area information. Specifically, the UE, together with the twelfth identification information, when receiving the thirteenth identification information, as the granularity of the LADN service area, the LADN service area indicated by the LADN service area information, by one or more tracking areas It may be recognized that the area is an area configured by the user or may be recognized as an area different from an area configured by one or more tracking areas. Furthermore, the UE, together with the twelfth identification information, when receiving the thirteenth identification information, may recognize that the tracking area ID list is included as the LADN service area information, or RAN assists It may recognize that necessary information is included, or may recognize that information that does not require RAN assistance is included.

Conversely, if the UE has not received the thirteenth identification information, the UE may use the default granularity as the granularity of the LADN service area. Further, even if the UE receives the thirteenth identification information, if the thirteenth identification information is invalid information, and / or if the UE does not support the extension of the LADN service area, The 13th identification information may be ignored, or the default granularity may be used as the granularity of the LADN service area. Here, the default granularity may be a granularity preset in the UE or a granularity indicated by information previously received from the network. Furthermore, in the case of the default granularity, the LADN service area may be an area configured by one or more tracking areas, and the LADN service area information may be a tracking area ID list.

When the twelfth identification information includes information indicating a plurality of LADNs, the UE stores the granularity of the LADN service area in the context in association with the information indicating the LADN for each information indicating the LADN. May be. Furthermore, when a plurality of LADN service area information is included in the twelfth identification information, the UE stores the granularity of the LADN service area in the context in association with the LADN service area information for each of the LADN service area information. May be.

Furthermore, upon receiving the fourteenth identification information, the UE may recognize a period during which the LADN service area is valid. More specifically, when the UE receives the fourteenth identification information together with the twelfth identification information, the UE recognizes the period during which the LADN service area indicated by the LADN service area information included in the twelfth identification information is valid. May be stored in the context in association with the LADN service area information.

Conversely, the UE may use the default period as a period during which the LADN service area is valid when the UE does not receive the fourteenth identification information. Further, even if the UE receives the fourteenth identification information, if the fourteenth identification information is invalid information, and / or if the UE does not support the extension of the LADN service area, The fourteenth identification information may be ignored, or a default period may be used as a period during which the LADN service area is valid. Here, the default period may be a period preset in the UE or a period indicated by information previously received from the network. Further, the default period may be a period until the LADN information is updated.

Note that, when the twelfth identification information includes information indicating a plurality of LADNs, the UE associates the period during which the LADN service area is valid with the information indicating the LADN for each information indicating the LADN. It may be stored in the context. Further, when the plurality of LADN service area information is included in the twelfth identification information, the UE associates the period during which the LADN service area is valid with the LADN service area information for each of the LADN service area information. It may be stored in the context.

Furthermore, the UE, together with the twelfth identification information, when receiving the eleventh identification information, and / or the thirteenth identification information, and / or the fourteenth identification information, extended LADN information, and / or extended It may recognize that the used LADN service area can be used, and may store the available LADN information and / or the LADN service area information in the context. Further, in this case, the UE may recognize that the received LADN information is the extended LADN information, or may store the received LADN information in the context as the extended LADN information. Further, in this case, the UE may recognize that the LADN service area indicated by the received LADN service area information is an extended LADN service area, or the received LADN service area information, It may be stored in the context as LADN service area information indicating the area. In this case, the eleventh identification information may be information indicating support for extension of the LADN service area, and the twelfth identification information may be extended LADN information.

Conversely, the UE receives the eleventh identification information, and / or the twelfth identification information, and does not receive the thirteenth identification information, and / or the fourteenth identification information, and / or the twelfth identification information. Received the identification information of the eleventh identification information, and / or the thirteenth identification information, and / or did not receive the fourteenth identification information, the extended LADN information, and / or the extended LADN It may be recognized that use of the service area is not possible. Further, the UE, in this case, may recognize that it is possible to use the conventional LADN information, and / or the conventional LADN service area, and may use the available LADN information, and / or the LADN service area. Information may be stored in context. Further, in this case, the UE may recognize that the received LADN information is conventional LADN information, or may store the received LADN information in the context as conventional LADN information. Further, in this case, the UE may recognize that the LADN service area indicated by the received LADN service area information is the conventional LADN service area, or the received LADN service area information may be used to identify the conventional LADN service area. It may be stored in the context as the indicated LADN service area information. In this case, the eleventh identification information may be information indicating that extension of the LADN service area is not supported, and the twelfth identification information may be conventional LADN information.

Further, if the UE receives the twelfth identification information in a state where the UE does not support the extension of the LADN service area, the extended LADN information, and / or the use of the extended LADN service area is not possible You may recognize that. Further, the UE, in this case, may recognize that it is possible to use the conventional LADN information, and / or the conventional LADN service area, and may use the available LADN information, and / or the LADN service area. Information may be stored in context. Further, in this case, the UE may recognize that the received LADN information is conventional LADN information, or may store the received LADN information in the context as conventional LADN information. Further, in this case, the UE may recognize that the LADN service area indicated by the received LADN service area information is the conventional LADN service area, or the received LADN service area information may be used to identify the conventional LADN service area. It may be stored in the context as the indicated LADN service area information. In this case, the twelfth identification information may be conventional LADN information.

Further, the UE receives at least the twelfth identification information, and may recognize that it is possible to establish a PDU session for the LADN if the UE is located in the LADN service area indicated by the received information. Alternatively, a PDU session establishment procedure for establishing a PDU session for the LADN may be started. In other words, the UE receives at least the twelfth identification information, and recognizes that it is not possible to establish a PDU session for the LADN when located outside the LADN service area indicated by the received information. Alternatively, a PDU session establishment procedure for establishing a PDU session for LADN may be prohibited.

Further, the UE initiates a PDU session establishment procedure for establishing a PDU session for the LADN based on the update of the LADN information and / or the determination of whether or not the UE is located in the LADN service area. Is also good. Specifically, the UE may initiate a PDU session establishment procedure for establishing a PDU session for a LADN based on a determination that the UE is located within a LADN service area. Conversely, each device may release or be associated with a PDU session for LADN based on the determination that the UE is located outside the LADN service area. User plane resources may be released.

Here, the determination whether the UE is located in the LADN service area may be performed based on the extended LADN service area, or may be performed based on the conventional LADN service area. . In other words, when each device stores the extended LADN service area, each device performs a determination as to whether the UE is in the LADN service area based on the extended LADN service area. Is also good. Conversely, if each device stores a conventional LADN service area, each device may perform a determination whether the UE is in the LADN service area based on the conventional LADN service area. .

Furthermore, when the stored LADN service area is a tracking area ID list, the LADN service area information stored by the UE and the tracking area ID acquired from the RAN are compared, and the LADN service area May be determined. Specifically, the UE recognizes that the UE is located in the LADN service area when the tracking area ID acquired from the RAN is included in the LADN service area information stored by the UE, and stores the UE. May be. Conversely, if the tracking area ID obtained from the RAN is not included in the LADN service area information stored by the UE, the UE recognizes that the UE is located outside the LADN service area, and stores the UE. Is also good.

Furthermore, if the stored LADN service area is information that requires RAN assistance, the LADN service area information stored by the UE and the information obtained from the RAN, based on a comparison of the LADN service area, You may judge whether it is located inside. Specifically, the UE recognizes that the UE is located in the LADN service area when the information obtained from the RAN is included in the LADN service area information stored by the UE, and stores the information. Is also good. Conversely, if the information obtained from the RAN is not included in the LADN service area information stored by the UE, the UE may recognize and store that the UE is located outside the LADN service area. .

Further, if the stored LADN service area is information that does not require RAN assistance, the LADN service area information stored by the UE is compared with information obtained from a source other than the RAN. It may be determined whether or not it is located in the area. Specifically, the UE recognizes and stores that the UE is located in the LADN service area when the information obtained from other than the RAN is included in the LADN service area information stored by the UE. May be. Conversely, the UE recognizes that the UE is located outside the LADN service area when the information acquired from other than the RAN is not included in the LADN service area information stored by the UE, and may store the information. Good.

The determination whether the UE is located in the LADN service area may be performed based on transmission / reception of a control message transmitted from the network to the UE. Specifically, the UE may recognize and store that the UE is located in the LADN service area based on receiving a control message from the network. Conversely, the UE may recognize and store that the UE is located outside the LADN service area based on receiving a control message from the network. Here, the control message transmitted from the network to the UE may be, for example, a control message for LCS (Location @ Services). Note that the determination of whether the UE is located in the LADN service area is not limited to these.

Further, the UE may recognize that it is possible to establish a PDU session for the LADN within a period in which the LADN service area is valid, or a PDU session for establishing a PDU session for the LADN. The establishment procedure may be started. In other words, the UE may recognize that it is not possible to establish a PDU session for the LADN outside the period in which the LADN service area is valid, or may configure the PDU to establish a PDU session for the LADN. The session establishment procedure may be prohibited.

Furthermore, the UE may start a PDU session establishment procedure for establishing a PDU session for the LADN based on the update of the LADN information and / or the determination of the activation of the LADN service area. Specifically, the UE may start a PDU session establishment procedure for establishing a PDU session for LADN based on the activation of the LADN service area. Conversely, each device may release a PDU session for the LADN established in association with the invalidated LADN service area based on the invalidation of the LADN service area, The user plane resources associated with the PDU session may be released.

Here, the determination of the activation of the LADN service area may be performed based on information indicating a period during which the LADN service area is valid. Specifically, the UE, the period during which the LADN service area is valid, and the current time are compared. If the current time is within the period during which the LADN service area is valid, the LADN service area is valid. May be determined. Conversely, the UE and the period during which the LADN service area is valid are compared with the current time. If the current time is outside the period during which the LADN service area is valid, it is determined that the LADN service area is invalid. May be. Further, the UE may activate the associated LADN service area based on the start of a period during which the LADN service area indicated by the received information is valid. Conversely, the UE may invalidate the associated LADN service area based on the end of the period during which the LADN service area indicated by the received information is valid.

判断 Also, the decision to activate the LADN service area may be made based on the reception of a control message from the network. Specifically, when receiving the control message from the network, the UE may determine that the LADN service area is valid. Further, the UE may determine that the LADN service area is not valid when it is not possible to receive a control message from the network. Conversely, the UE may determine that the LADN service area is not valid when receiving the reception of the control message from the network. Further, the UE may determine that the LADN service area is valid when it is not possible to receive a control message from the network. Further, the UE may activate the LADN service area based on receiving a control message from the network. Conversely, the UE may invalidate the LADN service area based on receiving a control message from the network. Note that the determination of the activation of the LADN service area is not limited to these.

[3.2.2. PDU session establishment procedure]
Next, an outline of a PDU session establishment procedure performed to establish a PDU session with the DN will be described. The PDU session establishment procedure is a procedure in 5GS. Note that each device can start the PDU session establishment procedure at an arbitrary timing when the registration procedure is completed and the apparatus enters the registration state. Also, each device may be able to execute a PDU session establishment procedure in a registration procedure. Further, each device may establish a PDU session based on the completion of the PDU session establishment procedure. Note that the PDU session establishment procedure may be a procedure initiated by the UE or a procedure initiated by the UE. Each device can establish a plurality of PDU sessions by executing the PDU session establishment procedure a plurality of times. Hereinafter, each step of the PDU session establishment procedure will be briefly described.

First, the UE starts a PDU session establishment procedure by transmitting a PDU session establishment request (PDU @ session @ establishment @ request) message to the SMF via the AMF. Further, the UE receives a PDU session establishment acceptance (PDU @ session @ establishment @ accept) message from the SMF via the AMF. Further, the UE may transmit a PDU session establishment completion (PDU @ session @ establishment @ complete) message based on the reception of the PDU session establishment acceptance message. Further, the UE may complete the PDU session establishment procedure by receiving a PDU session establishment acceptance message and / or transmitting a PDU session establishment completion message. Further, each device may establish a PDU session based on completion of the PDU session establishment procedure. Here, the PDU session establishment acceptance message may be a response message to the PDU session establishment request message. Further, the PDU session establishment completion message may be a response message to the PDU session establishment acceptance message.

Here, if the PDU session establishment procedure is a PDU session establishment procedure for establishing a PDU session for a LADN, the UE includes, in the PDU session establishment request message, a LADN that is a DNN available for connection to the LADN. You may transmit including DNN. Further, if the PDU session establishment procedure is a PDU session establishment procedure for establishing a PDU session for a LADN, the UE is an S-NSSAI available in the connection to the LADN in the PDU session establishment request message. LADN @ S-NSSAI may be transmitted, or S-NSSAI associated with LADN @ DNN may be transmitted.

In these cases, the UE may select LADN DNN to be included in the PDU session establishment request message from the LADN DNN included in the LADN information received before the execution of the PDU session establishment procedure, or the UE may store the The LADN @ DNN to be included in the PDU session establishment request message may be selected from the existing LADN @ DNNs. Further, the UE may select LADN S-NSSAI to be included in the PDU session establishment request message from the LADN S-NSSAI included in the LADN information received before the execution of the PDU session establishment procedure, or the UE may store the The LADN @ S-NSSAI to be included in the PDU session establishment request message may be selected from the available LADN @ S-NSSAIs. Further, the UE may select the S-NSSAI associated with the LADN DNN to be included in the PDU session establishment request message, and include the selected S-NSSAI in the PDU session establishment request message.

Further, if a plurality of LADN DNN is included in the LADN information received before the execution of the PDU session establishment procedure, and / or if a plurality of LADN DNNs are stored, the UE performs the LADN service area information, And / or LADN @ DNN may be selected based on the information indicating the period during which the LADN service area is valid, and the selected LADN @ DNN may be included in the PDU session establishment request message and transmitted. Further, if a plurality of LADN 以前 S-NSSAI are included in the LADN information received before the execution of the PDU session establishment procedure, and / or if a plurality of LADN S-NSSAIs are stored, the UE Based on the service area information and / or the information indicating the period during which the LADN service area is valid, LADN S-NSSAI may be selected, and the selected LADN S-NSSAI may be included in the PDU session establishment request message and transmitted. . In more detail, when the information indicating a plurality of LADN is included in the LADN information received before the execution of the PDU session establishment procedure, and / or when storing information indicating a plurality of LADN, UE Selects the information indicating the LADN based on the LADN service area information and / or the information indicating the period during which the LADN service area is valid, and selects the LADN DNN and / or the LADN S included in the information indicating the selected LADN. -NSSAI may be included in the PDU session establishment request message and transmitted. Further, when the PDU session establishment procedure is a PDU session establishment procedure for establishing a PDU session for a LADN, each device establishes a PDU session for an LADN based on completion of the PDU session establishment procedure. You may.

[4. First Embodiment]
Next, a first embodiment will be described. Hereinafter, the first embodiment will be referred to as the present embodiment. In the communication procedure according to the present embodiment, first, each device performs a registration procedure started by the UE. Next, each device establishes a PDU session by performing the UE-initiated PDU session establishment procedure, and transitions to a state in which communication using the PDU session can be performed between the UE and the DN. Next, each device transmits and receives user data using the PDU session. Thus, the procedure of the present embodiment is completed.

In the procedure of the present embodiment, each device may exchange support information for extending the LADN service area and / or LADN information between the UE and the network in the registration procedure.

Further, in the PDU session establishment procedure, each device may establish a PDU session for the LADN between the UE and the network based on the information exchanged in the registration procedure. The PDU session for the LADN may be a PDU session that can be established only when the UE is located in a specific area. Here, the specific area may be, for example, a LADN service area.

Furthermore, each device may execute user data communication with the LADN by using the established PDU session. Further, each device may release the established PDU session based on the update of the LADN information and / or a change in the state of the LADN service area, or may release the user plane associated with the established PDU session. Resources may be released.

[5. Modifications]
The program that operates on the device according to the present invention may be a program that controls a Central Processing Unit (CPU) and the like to cause a computer to function so as to realize the functions of the embodiment according to the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a random access memory (RAM), a nonvolatile memory such as a flash memory, a hard disk drive (HDD), or another storage device system.

Note that a program for realizing the functions of the embodiment according to the present invention may be recorded on a computer-readable recording medium. The program may be realized by causing a computer system to read and execute the program recorded on the recording medium. Here, the “computer system” is a computer system built in the device, and includes an operating system and hardware such as peripheral devices. Further, the “computer-readable recording medium” refers to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another computer-readable recording medium. Is also good.

Each functional block or various features of the apparatus used in the above-described embodiments may be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other Logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. A general purpose processor may be a microprocessor, or may be a conventional processor, controller, microcontroller, or state machine. The above-mentioned electric circuit may be constituted by a digital circuit or an analog circuit. In addition, in the case where a technology for forming an integrated circuit that substitutes for a current integrated circuit appears due to an advance in semiconductor technology, one or more aspects of the present invention can use a new integrated circuit based on the technology.

発 明 Note that the present invention is not limited to the above embodiment. In the embodiment, an example of the device is described, but the present invention is not limited to this, and stationary or non-movable electronic devices installed indoors and outdoors, for example, AV devices, kitchen devices It can be applied to terminal devices or communication devices such as cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to the embodiments, and may include a design change or the like without departing from the gist of the present invention. Further, the present invention can be variously modified within the scope shown in the claims, and an embodiment obtained by appropriately combining technical means disclosed in different embodiments is also included in the technical scope of the present invention. It is. The elements described in the above embodiments also include a configuration in which elements having the same effects are replaced.

Claims (6)

1. A user device,
   The user device includes a transmission / reception unit and a control unit,
   The control unit, in the registration procedure,
   Send a registration request message to the control unit,
   Receiving a registration acceptance message from the control device;
   The registration request message includes information A indicating whether or not expansion of a Local Area Data Network (LADN) service area is supported,
   The registration acceptance message includes information B indicating whether or not the extension of the LADN service area is supported,
   The control unit includes:
   When the information B indicates that the extension of the LADN service area is not supported, an area configured by one or more tracking areas is set as the LADN service area,
   When the information B indicates that the extension of the LADN service area is supported, an area different from the area constituted by the one or more tracking areas is set as the LADN service area. User equipment.
2. The registration acceptance message further includes information C indicating a period during which the LADN service area is valid,
   The transmitting and receiving unit, when the information B is information indicating that the extension of the LADN service area is supported, within a period indicated by the information C, a PDU for establishing a PDU session for the LADN. The user apparatus according to claim 1, wherein the user apparatus starts a session establishment procedure.
3. A control device,
   The control device includes a transmitting and receiving unit and a control unit,
   The control unit, in the registration procedure,
   Receiving a registration request message from the user equipment,
   Sending a registration acceptance message to the user device;
   The registration request message includes information A indicating whether or not expansion of a Local Area Data Network (LADN) service area is supported,
   The registration acceptance message includes information B indicating whether or not the extension of the LADN service area is supported,
   The control unit includes:
   When the information A indicates that the extension of the LADN service area is not supported, an area configured by one or more tracking areas is set as the LADN service area,
   When the information A indicates that the extension of the LADN service area is supported, an area different from the area configured by the one or more tracking areas is set as the LADN service area,
   The control device, wherein the registration acceptance message further includes information C indicating the LADN service area.
4. A communication control method for a user device,
   In the registration procedure,
   Transmitting a registration request message to the control device;
   Receiving a registration acceptance message from the control device,
   The registration request message includes information A indicating whether or not expansion of a Local Area Data Network (LADN) service area is supported,
   The registration acceptance message includes information B indicating whether or not the extension of the LADN service area is supported,
   The user device,
   When the information B indicates that the extension of the LADN service area is not supported, an area configured by one or more tracking areas is set as the LADN service area,
   When the information B indicates that the extension of the LADN service area is supported, an area different from the area constituted by the one or more tracking areas is set as the LADN service area. A communication control method for a user device.
5. The registration acceptance message further includes information C indicating a period during which the LADN service area is valid,
   The user apparatus, when the information B is information indicating that the extension of the LADN service area is supported, within a period indicated by the information C, a PDU for establishing a PDU session for the LADN. 5. The communication control method for a user device according to claim 4, wherein a session establishment procedure is started.
6. A communication control method for a control device,
   In the registration procedure,
   Receiving a registration request message from the user equipment;
   Transmitting a registration acceptance message to the user device;
   The registration request message includes information A indicating whether or not expansion of a Local Area Data Network (LADN) service area is supported,
   The registration acceptance message includes information B indicating whether or not the extension of the LADN service area is supported,
   The control device includes:
   When the information A indicates that the extension of the LADN service area is not supported, an area configured by one or more tracking areas is set as the LADN service area,
   When the information A indicates that the extension of the LADN service area is supported, an area different from the area configured by the one or more tracking areas is set as the LADN service area,
   The communication control method of a control device, wherein the registration acceptance message further includes information C indicating the LADN service area.

Images