Terminal device

Abstract

To clarify the procedure for establishing a communication route for an A2X (Aircraft-to-anything) communication between a UAV (Uncrewed Aerial Vehicle) without a UICC (Universal Integrated Circuit Card), and to clarify behaviors of the UAV to a radio parameter.SOLUTION: A terminal device #1 does not have a UICC and directly sends a link establishment refusal message when use of an A2X communication is not authorized (S2200). Also, the terminal device #1 stops an A2X communication via a direct communication PC5 when an effective timer is finished.SELECTED DRAWING: Figure 11

Description

[Technical field]

[0001] The present invention relates to a terminal device. [Background technology]

[0002] The 3GPP (3rd Generation Partnership Project) is considering the system architecture of 5GS (5G System), which is a fifth generation (5G) mobile communication system, and is discussing how to support new procedures and new functions (see Non-Patent Documents 1 to 4). In recent years, there has been active discussion on functions for realizing A2X (Aircraft-to-anything) services. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 24.501 V18.2.0 (2023-03); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 18) [Non-Patent Document 2] 3GPP TS 23.256 V17.5.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 (Release 17) [Non-Patent Document 3] 3GPP TS 23.285 V17.1.0 (2022-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for V2X services (Release 17) [Non-Patent Document 4] 3GPP TS 24.587 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 (Release 18) Summary of the Invention [Problem to be solved by the invention]

[0004] In 5GS (5G System), a new core network, 5GCN (5G Core Network), is being considered to provide a wide variety of services. In addition, 5GS also considers functions to realize A2X (Aircraft-to-anything) services that provide communication between UAVs.

[0005] Specifically, the behavior of UAVs that do not have a UICC (Universal Integrated Circuit Card) and the information that wireless parameters constitute are being considered. On the other hand, the specific behavior of A2X communication between UAVs that do not have a UICC and the specific behavior of UAVs with respect to wireless parameters are not clear.

[0006] One aspect of the present invention has been made in consideration of the above circumstances. In the present invention, a procedure for establishing a communication path for A2X communication between UAVs that do not have a UICC is clarified. Also, the behavior of the UAV with respect to radio parameters is clarified. [Means for solving the problem]

[0007] A terminal device of one embodiment of the present invention is an Uncrewed Aerial Vehicle (UAV), and the terminal device is equipped with a transceiver unit and a memory unit, and the transceiver unit receives a direct link establishment request message from a different terminal device, and when the terminal device does not have a UICC and the memory unit does not have first identification information, the transceiver unit transmits a direct link establishment rejection message including second identification information to the different terminal device, and the first identification information is information indicating that the terminal device is authorized to use Aircraft-to-anything (A2X) communication via PC5 when the terminal device is ``not served by E-UTRA'' and ``not served by NR'', and the second identification information is a reason value indicating that the terminal device is not authorized to use A2X communication via PC5 when the terminal device is ``not served by E-UTRA'' and ``not served by NR''. Effect of the Invention

[0008] According to one aspect of the present invention, it is possible to clarify a procedure for establishing a communication path for A2X communication between UAVs that do not have a UICC. Also, it is possible to clarify the behavior of the UAV with respect to radio parameters. [Brief description of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an overview of a mobile communication system (EPS / 5GS). [Diagram 2] A diagram explaining the detailed configuration of a mobile communication system (EPS / 5GS). [Diagram 3]A diagram explaining the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Diagram 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 1 is a diagram illustrating a registration procedure. [Figure 7] A diagram explaining the PDU session establishment procedure. [Figure 8] A diagram explaining a network requested UE policy management procedure. [Figure 9] A diagram explaining a UE requested A2X policy provision procedure. [Figure 10] 13 is a diagram explaining the PC5 unicast link establishment procedure. [Figure 11] FIG. 1 is a diagram illustrating a first embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, a best mode for carrying out one aspect of the present invention will be described with reference to the drawings. In this embodiment, as an example, an embodiment of a mobile communication system to which one aspect of the present invention is applied will be described.

[0011] [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. As shown in FIG.

[0012] FIG. 1 shows that the mobile communication system 1 is composed of UE_A10, access network _A80, core network _A90, PDN (Packet Data Network) _A5, access network _B120, core network _B190, and DN (Data Network) _A6.

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

[0014] Figure 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 N3IWF170, as well as interfaces that connect these devices and functions to each other.

[0015] In the following, these devices and functions may be referred to by abbreviated symbols, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0016] In addition, the 4G system EPS (Evolved Packet System) is configured to include an access network _A and a core network _A, but may further include a UE and / or a PDN. In addition, the 5G system 5GS (5G System) is configured to include a UE, an access network _B, and a core network _B, but may further include a DN.

[0017] The UE is a device that can connect to a network service via 3GPP access (also referred to as a 3GPP access network, 3GPP AN) and / or non-3GPP access (also referred to as a non-3GPP access network, non-3GPP AN). 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 connect to both EPS and 5GS. The UE may include a Universal Integrated Circuit Card (UICC) or an Embedded UICC (eUICC). The UE may be expressed as a user device or a terminal device.

[0018] Moreover, the access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. In the E-UTRAN, one or more eNBs (evolved Node B) 45 are arranged. In the following, the eNB 45 may be written with the symbol omitted, such as eNB. In addition, when there are multiple eNBs, the eNBs are connected to each other, for example, by an X2 interface. In addition, one or more access points are arranged in the wireless LAN access network.

[0019] Moreover, the access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are arranged in the NG-RAN. In the following, the gNB 122 may be written with the symbol omitted, such as gNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node that connects to the 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 the 5GS, and has a different function from the base station device (eNB) used in the EPS, which is a 4G system. In addition, when there are multiple gNBs, each gNB is connected to each other, for example, by an Xn interface.

[0020] Furthermore, the non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network may be a non-3GPP access network that does not perform security management within the access network, such as a public wireless LAN. On the other hand, the trusted non-3GPP access network may be an access network defined by 3GPP, and may include a trusted non-3GPP access point (TNAP) and a trusted non-3GPP Gateway function (TNGF).

[0021] In the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. In addition, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. In addition, nodes arranged in the access network_B may be collectively referred to as NG-RAN nodes.

[0022] In addition, in the following, access network _A, and / or access network _B, and / or devices included in access network _A, and / or devices included in access network _B may be referred to as access networks or access network devices.

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

[0024] Moreover, the core network_B corresponds to a 5G Core Network (5GCN). For example, an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), and a Unified Data Management (UDM) are arranged in the 5GCN. Here, the 5GCN may be expressed as a 5GC.

[0025] In addition, in the following, core network _A and / or core network _B, devices included in core network _A, and / or devices included in core network _B may be referred to as core networks, core network devices, or devices within a core network.

[0026] The core network (core network _A and / or core network _B) may be an IP mobile communication network operated by a mobile network operator (MNO) that connects the access network (access network _A and / or access network _B) to the PDN and / or DN, or it may be a core network for a mobile network operator that operates and manages the mobile communication system 1, or it may be a core network for a virtual mobile communication operator such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler) or a virtual mobile communication service provider.

[0027] Also, in FIG. 1, 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. The DN may be configured as a packet data service network, or may be configured for each service. Furthermore, the PDN may include a communication terminal connected thereto. Therefore, connecting to the PDN may be connecting to a communication terminal or a server device arranged in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may be transmitting and receiving user data to and from a communication terminal or a server device arranged in the PDN. The PDN may be expressed as the DN, and the DN may be expressed as the PDN.

[0028] In addition, in the following, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device transmits or receives a message and / or executes a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein transmits or receives a message and / or executes a procedure.

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

[0030] Here, IP communication refers to data communication using IP, and data is transmitted and received by IP packets. The IP packet is composed of an IP header and a payload section. The payload section may include data transmitted and received by devices and functions included in EPS and devices and functions included in 5GS. In addition, non-IP communication refers to data communication that does not use IP, 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 transmitting and receiving application data to which an IP header is not attached, or may be user data transmitted and received by a UE with another header such as a MAC header or an Ethernet (registered trademark) frame header attached.

[0031] In addition, the access network_A, the core network_A, the access network_B, the core network_B, the PDN_A, and the DN_A may be configured with devices not shown in Fig. 2. For example, the core network_A and / or the core network_B may include an AUSF (Authentication Server Function) and an AAA (Authentication, authorization, and accounting) server (AAA-S).

[0032] Here, the AUSF is a core network device having an authentication function for 3GPP access and non-3GPP access, specifically, a network function unit that receives an authentication request for 3GPP access and / or non-3GPP access from a UE and executes an authentication procedure.

[0033] The AAA server is a device that is connected to the AUSF directly or indirectly via another network device and has authentication, authorization, and accounting functions. The AAA server may be a network device in the core network. The AAA server may not be included in the core network_A and / or the core network_B, but may be included in the PLMN. In other words, the AAA server may be a core network device or a device outside the core network. For example, the AAA server may be a server device in the PLMN managed by a third party.

[0034] 2, for the sake of simplicity, one of each device and function is shown, but a plurality of similar devices and functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may be configured with a plurality of devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150.

[0035] The UPF_A235 is connected to the DN, the SMF, other UPFs, and the access network. The UPF_A235 may perform roles such as an anchor for intra-RAT mobility or inter-RAT mobility, packet routing & forwarding, a UL CL (Uplink Classifier) ​​function supporting routing of multiple traffic flows for one DN, a branching point function supporting a multi-homed PDU session, QoS processing for the user plane, verification of uplink traffic, buffering of downlink packets, and a trigger function for downlink data notification. The UPF_A235 may also be a relay device that forwards user data as a gateway between the DN and the core network_B190. The UPF_A235 may also be a gateway for IP communication and / or non-IP communication. The UPF_A235 may also have a function of forwarding IP communication and a function of converting non-IP communication to IP communication. Furthermore, multiple gateways may be deployed, and may be gateways that connect the core network_B190 to a single DN. Note that UPF_A235 may have connectivity with other NFs and may be connected to each device via other NFs.

[0036] In addition, UPF_C239 (also called a branching point or uplink classifier), which is a UPF different from UPF_A235, may exist as a device or NF between UPF_A235 and the access network. When UPF_C239 exists, a PDU session between the UE and the DN is established via the access network, UPF_C239, and UPF_A235.

[0037] Moreover, the UPF 130 may be the same device as the UPF_A 235. Note that the UPF 130 and the UPF_A 235 may be described with the symbol omitted, such as UPF.

[0038] [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. Furthermore, at least a part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

[0039] Each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) in each device / function described below is composed of, for example, a semiconductor memory, a solid state drive (SSD), a hard disk drive (HDD), etc. Each memory unit can store not only information that was originally set at the time of shipment, but also various information transmitted and received between the device / function other than the device / function itself (for example, UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Each memory unit can store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described later. Each memory unit may store this information for each UE. Each memory unit can store control messages and user data transmitted and received between the device / function included in the 5GS and / or EPS when interworking is performed between the 5GS and EPS. At this time, not only those transmitted and received via the N26 interface but also those transmitted and received without passing through the N26 interface can be stored.

[0040] [2.1. UE device configuration] First, an example of the device configuration of UE (User Equipment) will be described with reference to Fig. 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

[0041] The control unit _A300 is a functional unit that controls the operation and functions of the entire UE. The control unit _A300 realizes various processing in the UE by reading and executing various programs stored in the memory unit _A340 as necessary.

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

[0043] Explaining in detail with reference to FIG. 2, the UE can communicate with a base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver unit _A320. The UE can also communicate with a base station device (gNB) in the 5G AN by using the transceiver unit _A320. The UE can also transmit and receive AMF and NAS (Non-Access-Stratum) messages via the N1 interface by using the transceiver unit _A320. However, since the N1 interface is logical, in reality, communication between the UE and the AMF is performed via the 5G AN.

[0044] The memory unit _A340 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UE.

[0045] [2.2. gNB device configuration] Next, an example of the device configuration of the gNB will be described with reference to Fig. 4. The gNB is composed of a control unit _B500, an antenna 510, a network connection unit _B520, a transceiver unit _B530, and a memory unit _B540. The control unit _B500, the network connection unit _B520, the transceiver unit _B530, and the memory unit _B540 are connected via a bus. The transceiver unit _B530 is connected to the antenna 510.

[0046] The control unit _B500 is a functional unit that controls the operation and functions of the entire gNB. The control unit _B500 realizes various processes in the gNB by reading and executing various programs stored in the memory unit _B540 as necessary.

[0047] The network connection unit _B520 is a functional unit for the gNB to communicate with the AMF and / or UPF. That is, the gNB can transmit and receive user data and / or control information between the AMF and / or UPF using the network connection unit _B520.

[0048] The transceiver unit _B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information between the UE and the transceiver unit _B530.

[0049] 2, the gNB in ​​the 5G AN can communicate with the AMF via the N2 interface by using the network connection unit _B 520, and can communicate with the UPF via the N3 interface. The gNB can also communicate with the UE by using the transceiver unit _B 530.

[0050] The memory unit _B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB.

[0051] [2.3. AMF device configuration] Next, an example of the device configuration of the AMF will be described with reference to Figure 5. The AMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The AMF may be a node that handles the control plane.

[0052] The control unit _B700 is a functional unit that controls the operation and functions of the entire AMF. The control unit _B700 realizes various processing in the AMF by reading and executing various programs stored in the memory unit _B740 as necessary.

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

[0054] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with the gNB via the N2 interface by using the network connection unit_A620, can communicate with the UDM via the N8 interface, can communicate with the SMF via the N11 interface, and can communicate with the PCF via the N15 interface. In addition, the AMF can 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, in reality, communication between the UE and the AMF is performed via the 5G AN. In addition, if the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit_A620.

[0055] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of AMF.

[0056] In addition, 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 NAS messages, a registration management (RM) function, a connection management (CM) function, a reachability management function, a mobility management function for UEs, etc., a function of transferring SM (Session Management) messages between the UE and the SMF, an access authentication (access authorization) function, a security anchor functionality (SEA), a security context management (SCM) function, a function of supporting the N2 interface for the N3IWF (Non-3GPP Interworking Function), a function of supporting the transmission and reception of NAS signals with the UE via the N3IWF, and a function of authenticating UEs connected via the N3IWF.

[0057] In addition, in the registration management, the RM state of 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, the UE is not registered in the network, and therefore the UE context in the AMF does not have valid location information or routing information for the UE, and therefore the AMF cannot reach the UE. In the RM-REGISTERED state, the UE is registered in the network, and therefore the UE can receive services that require registration with the network. The RM state may be expressed as a 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.

[0058] In other words, 5GMM-REGISTERED may be a state in which each device has established a 5GMM context, or may be a state in which each device has established a PDU session context. 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.

[0059] Furthermore, 5GMM-DEREGISTERED may be a state in which each device has not established a 5GMM context, a state in which the location information of UE_A10 is not known to the network, or a state in which the network cannot reach UE_A10. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or establish a 5GMM context by executing the registration procedure.

[0060] In addition, in the connection management, the CM state of each UE is managed. The CM state may be synchronized between the UE and the AMF. The CM state includes a non-connected state (CM-IDLE state) and a connected 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 a connection (N2 connection) of the N2 interface and a connection (N3 connection) of the N3 interface. On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. In the CM-CONNECTED state, the UE may have a connection (N2 connection) of the N2 interface and / or a connection (N3 connection) of the N3 interface.

[0061] Furthermore, in connection management, a CM state in 3GPP access and a CM state in non-3GPP access may be managed separately. In this case, the CM state in 3GPP access may be a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over 3GPP access). Furthermore, the CM state in non-3GPP access may be a non-connected state in non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state in non-3GPP access (CM-CONNECTED state over non-3GPP access). The non-connected state may be expressed as an idle mode, and the connected state mode may be expressed as a connected mode.

[0062] The CM state may be expressed as a 5GMM mode. In this case, the unconnected state may be expressed as a 5GMM unconnected mode, and the connected state may be expressed as a 5GMM-CONNECTED mode. Furthermore, the unconnected state in 3GPP access may be expressed as a 5GMM unconnected mode in 3GPP access, and the connected state in 3GPP access may be expressed as a 5GMM-CONNECTED mode over 3GPP access. Furthermore, the unconnected state in non-3GPP access may be expressed as 5GMM unconnected mode in non-3GPP access (5GMM-IDLE mode over non-3GPP access), and the connected state in non-3GPP access may be expressed as 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). Note that the 5GMM unconnected mode may be expressed as idle mode, and the 5GMM connected mode may be expressed as connected mode.

[0063] In addition, one or more AMFs may be placed in the core network_B. In addition, the AMF may be a network function (NF) that manages one or more network slice instances (NSIs). In addition, the AMF may be a common control plane network function (CCNF) shared between multiple NSIs.

[0064] In addition, the N3IWF is a device and / or function located between the non-3GPP access and the 5GCN when the UE connects to the 5GS via the non-3GPP access.

[0065] [2.4. SMF device configuration] Next, an example of the device configuration of the SMF will be explained using Figure 5. The SMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The SMF may be a node that handles the control plane.

[0066] The control unit _B700 is a functional unit that controls the operation and functions of the entire SMF. The control unit _B700 realizes various processing in the SMF by reading and executing various programs stored in the memory unit _B740 as necessary.

[0067] The 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. In other words, the SMF can use the network connection unit _B720 to transmit and receive user data and / or control information between the AMF, and / or the UPF, and / or the PCF, and / or the UDM.

[0068] Explaining in detail with reference to Figure 2, the SMF in the 5GCN can communicate with the AMF via the N11 interface, can communicate with the UPF via the N4 interface, can communicate with the PCF via the N7 interface, and can communicate with the UDM via the N10 interface, by using the network connection unit _A620.

[0069] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the SMF.

[0070] The SMF has a session management function such as establishing, modifying, and releasing PDU sessions, an IP address allocation for UEs and its management function, a UPF selection and control function, a UPF setting function for routing traffic to the appropriate destination (destination), a function for sending and receiving the SM part of NAS messages, a function for notifying that downlink data has arrived (Downlink Data Notification), a function for providing AN-specific (for each AN) SM information to be sent to the AN via the N2 interface via the AMF, a function for determining the SSC mode (Session and Service Continuity mode) for the session, and a roaming function.

[0071] [2.5. UPF device configuration] Next, an example of the device configuration of the UPF will be described with reference to Fig. 5. The UPF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The UPF may be a node that handles the control plane.

[0072] The control unit _B700 is a functional unit that controls the operation and functions of the entire UPF. The control unit _B700 realizes various processing in the UPF by reading and executing various programs stored in the memory unit _B740 as necessary.

[0073] The network connection unit _B720 is a functional unit for the UPF to connect to a base station device (gNB), and / or SMF, and / or DN in the 5G AN. In other words, the UPF can transmit and receive user data and / or control information between the base station device (gNB), and / or SMF, and / or DN in the 5G AN using the network connection unit _B720.

[0074] Explaining in detail with reference to Figure 2, by using network connection unit _A620, the UPF in the 5GCN can communicate with a gNB via an N3 interface, can communicate with an SMF via an N4 interface, can communicate with a DN via an N6 interface, and can communicate with other UPFs via an N9 interface.

[0075] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UPF.

[0076] The UPF has functions such as an anchor point for intra-RAT mobility or inter-RAT mobility, an external PDU session point for interconnecting to DNs (i.e., a function for forwarding user data as a gateway between DN and core network_B), a packet routing and forwarding function, a UL CL (Uplink Classifier) ​​function that supports routing of multiple traffic flows for one DN, a branching point function that supports multi-homed PDU sessions, a QoS (Quality of Service) processing function for the user plane, an uplink traffic verification function, downlink packet buffering, and a function for triggering downlink data notification.

[0077] The UPF may also be a gateway for IP communication and / or non-IP communication. The UPF may also have a function for forwarding IP communication, and may also have a function for converting non-IP communication and IP communication. Furthermore, the multiple gateways may be gateways that connect the core network_B to a single DN. The UPF may also have connectivity with other NFs, and may be connected to each device via other NFs.

[0078] The user plane refers to 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. Furthermore, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface, and / or the S1-U interface, and / or the S5 interface, and / or the S8 interface, and / or the SGi interface. Furthermore, 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 the N3 interface, and / or the N9 interface, and / or the N6 interface. Hereinafter, the user plane may be expressed as U-Plane.

[0079] Furthermore, the control plane refers to a control message transmitted and received to control communication of the UE. The control plane may be transmitted and received using a Non-Access-Stratum (NAS) 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 the control plane or the C-Plane.

[0080] Furthermore, the U-Plane (User Plane; UP) may be a communication path for transmitting and receiving user data and may be composed of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may be a communication path for transmitting and receiving control messages and may be composed of multiple bearers.

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

[0082] First, the terminal device may be a mobile equipment (ME), and may or may not include a universal integrated circuit card (UICC) and / or a universal subscriber identity module (USIM).

[0083] In addition, the UE described in this specification may be read as a terminal device. Also, the terminal device may be read as a UE or a UAV.

[0084] In this specification, the terminal devices may include terminal device #1 and terminal device #2.

[0085] Next, a UAV (Uncrewed Aerial Vehicle) may be a flying drone. The UAV may be associated with a UAV controller. Furthermore, the UAV may be associated with the UAV controller and managed by a core network device and / or a UTM. Furthermore, when the UAV is associated with the UAV controller and managed, the UAV may be managed as a UAS by the core network device and / or a UTM. The UAV may have its own information (identification information, IP address, location information, etc.) managed by the core network device and / or the UTM. Furthermore, the UAV may be a UE.

[0086] Next, a UAV controller is a controller for operating a UAV. The UAV controller may be associated with a UAV. Furthermore, the UAV controller may be associated with a UAV and managed by a core network device and / or a UTM. Furthermore, when the UAV controller is associated with a UAV and managed, it may be managed by a core network device and / or a UTM as a UAS. The UAV controller may have its own information (identification information, IP address, location information, etc.) managed by the core network device and / or the UTM. The UAV controller may also be a UE. The UAV controller may be expressed as a UAC or a UAV-C. The UAV-C may also be a UE.

[0087] Next, a UAS (Uncrewed Aerial System) may be composed of a UAV and a UAV controller. The UAS may be managed by a core network device and / or a UTM. The UAS may be composed of one UAV and one UAV controller.

[0088] Furthermore, the UAS (Uncrewed Aerial System) may be composed of a UAV and related functions. Here, the related functions may include a C2 (command and control) link. Furthermore, the C2 link may be a link between the UAV and a control device, or a link between the UAV and a network. Furthermore, the C2 link may be a link for remote identification.

[0089] Next, the network refers to at least a part of the access network _B, the core network _B, and the DN. In addition, one or more devices included in at least a part of the access network _B, the core network _B, and the DN may be referred to as a network or a network device.

[0090] That is, when a network transmits, receives, and / or processes messages, it may mean that devices in the network (network devices and / or control devices) transmit, receive, and / or process messages. Conversely, when a device in the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, and / or processes messages.

[0091] Furthermore, the network may refer to a Public Land Mobile Network (PLMN) or a Non-Public Network (NPN).

[0092] The network may also be referred to as NW.

[0093] Next, a PLMN (Public Land Mobile Network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by an operator, which is a communication carrier, and the operator can be identified by a PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscription Identity) may be a Home PLMN (HPLMN). Furthermore, the UE may hold an Equivalent PLMN list in the USIM to identify one or more EPLMNs (Equivalent PLMNs). A PLMN different from the HPLMN and / or EPLMN may be a Visited PLMN (VPLMN). A PLMN to which the UE has successfully registered may be a Registered PLMN (RPLMN).

[0094] Next, PLMN selection may be a procedure for a UE to select a PLMN.

[0095] Next, a PCF (Policy Control Function) may be an NF having a function of determining a policy for controlling the behavior of a network.

[0096] Next, the SM (Session Management) message may be a NAS message used in a procedure for SM. The SM message may be referred to as a NAS (Non-Access-Stratum) SM message. The SM message may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240.

[0097] Next, an SM procedure may be a procedure for an SM.

[0098] Next, the MM (Mobility management) message may be a NAS message used in a procedure for MM. The MM message may be a control message transmitted and received between the UE_A10 and the AMF_A240. The MM message may be referred to as a NAS MM message.

[0099] Next, an MM procedure may be a procedure for MM.

[0100] Next, 5GS (5G System) service may be a connection service provided using Core Network_B190.

[0101] Next, a non-5GS service may be a service other than a 5GS service.

[0102] Next, a PDU (Protocol Data Unit) session can be defined as an association between a DN providing a PDU connectivity service and a UE, but may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data between a DN and a DN by establishing a PDU session via an access network_B and a core network_B. Here, the external gateway may be a UPF, a SCEF, or the like. A UE can transmit and receive user data to and from a device such as an application server located in a DN by using a PDU session. Each device (UE, and / or an access network device, and / or a core network device) may manage one or more pieces of identification information in association with a PDU session. These pieces of identification information may include one or more of a DNN, a QoS rule, a PDU session type, an application identification information, an NSI identification information, an access network identification information, and an SSC mode, or may further include other information. Furthermore, when a plurality of PDU sessions are established, each piece of identification information associated with a PDU session may be the same or different.

[0103] Next, the PDU (Protocol Data Unit) session type indicates the type of the PDU session, and includes IPv4, IPv6, Ethernet, and Unstructured. When IPv4 is specified, it indicates that data is transmitted and received using IPv4. When IPv6 is specified, it indicates that data is transmitted and received using IPv6. When Ethernet is specified, it indicates that Ethernet frames are transmitted and received. Ethernet may also indicate that communication using IP is not performed. When Unstructured is specified, it indicates that data is transmitted and received to an application server or the like in a DN using a Point-to-Point (P2P) tunneling technique. As the P2P tunneling technique, for example, a UDP / IP encapsulation technique may be used. In addition to the above, the PDU session type may also include IP. IP can be specified when the UE is capable of using both IPv4 and IPv6.

[0104] Next, the 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 a PGW / UPF that connects the core network B190.

[0105] Next, PC5 is a reference point. Also, PC5 may be a reference point between ProSe-enabled UEs, or a reference point between UAS-enabled UEs, or a reference point between A2X-enabled UEs, or a reference point between UEs, or a reference point between terminal devices.

[0106] Next, the PC5 path may be a communication path on the PC5. Also, the PC5 path may be a communication path between ProSe-enabled UEs, a communication path between UAS-enabled UEs, a communication path between A2X-enabled UEs, a communication path between UEs, or a communication path between terminal devices. The PC5 path may be referred to as a PC5 interface.

[0107] Next, Uu may be a radio interface, and Uu may be a radio interface between the 5G AN and the UE.

[0108] Next, the Uu path may be a communication path on Uu. Also, the Uu path may be a communication path between the 5G AN and the UE. In addition, the Uu path may be referred to as a Uu interface.

[0109] Next, the initiating UE may be a UE that transmits and receives messages to and from the target UE.

[0110] Next, the target UE may be a UE that transmits and receives messages to and from the initiating UE.

[0111] Next, A2X (Aircraft-to-anything) communication is communication for supporting A2X services utilizing the PC5 reference point. Here, the A2X service may be realized by various types of A2X applications such as BRID (Broadcast Remote ID) and DAA (Detect And Avoid). A2X communication may be communication on PC5.

[0112] Next, A2X services are A2X applications and data services provided by A2X application servers. An A2X service may belong to one A2X service type. An A2X service may be associated with one or more A2X applications, and an A2X application may be associated with one or more A2X services.

[0113] Next, DAA (Detect And Avoid) is the ability to see, sense, or detect colliding traffic or other hazards and take appropriate action.

[0114] Next, DDAA (Direct Detect And Avoid) is a DAA that utilizes communications on the PC5 reference point.

[0115] Next, when a terminal device is "not served by E-UTRA" and / or "not served by NR", it may mean that the terminal device cannot communicate with the network, or it may mean that the terminal device is only available for communication over PC5.

[0116] Next, when a terminal device is "served by E-UTRA" and / or "served by NR", it may mean that the terminal device can communicate with the network, or that the terminal device can use communication on PC5 and / or communication on Uu.

[0117] Additionally, a terminal device being "not served by E-UTRA" may mean that the terminal device is not able to communicate with a base station or network using E-UTRA technology.

[0118] Additionally, a terminal device being "not served by NR" may mean that the terminal device is not able to communicate with a base station or network using NR technology.

[0119] [2.7. Description of Identification Information in the Present Embodiment] Next, the identification information transmitted, received, stored, and / or managed by each device in this embodiment will be described.

[0120] First, the first identification information may be information indicating whether the terminal device is authorized to use A2X communication via PC5 when the terminal device is "not served by E-UTRA" and / or "not served by NR". The first identification information may be information indicating that the terminal device is authorized or not authorized to use A2X communication via PC5 when the terminal device is "not served by E-UTRA" and / or "not served by NR". The first identification information may be included in the 20th identification information.

[0121] Furthermore, the first identification information may be information indicating whether the terminal device #1 is authorized to use A2X communication via PC5 when the terminal device #1 is "not served by E-UTRA" and / or "not served by NR". The first identification information may be information indicating that the terminal device #1 is authorized or not authorized to use A2X communication via PC5 when the terminal device #1 is "not served by E-UTRA" and / or "not served by NR". The first identification information may be included in the 20th identification information.

[0122] Next, the second identification information may be information indicating whether the terminal device has a UICC. The second identification information may be information indicating whether the terminal device has a UICC or not. The second identification information may be included in the twentieth identification information.

[0123] Furthermore, the second identification information may be information indicating whether the terminal device #1 has a UICC. The second identification information may be information indicating whether the terminal device #1 has a UICC or not. The second identification information may be included in the twentieth identification information.

[0124] Next, the tenth identification information is a reason value or a rejection reason value. The tenth identification information is a reason value indicating #1 (direct communication to the target UE not allowed) or a rejection reason value. The tenth identification information may be a reason value indicating that direct communication to the terminal device is not allowed.

[0125] Furthermore, the tenth identification information may be a reason value indicating that direct communication with terminal device #2 is not permitted.

[0126] The tenth identification information may be #3 (conflict of layer-2 ID for unicast communication is detected), #5 (lack of resources for PC5 unicast link), or #111 (protocol error, unspecified).

[0127] Next, the eleventh identification information is a reason value or a rejection reason value. The eleventh identification information may be a reason value indicating that the terminal device is not equipped with a UICC. The eleventh identification information may be a reason value indicating that the terminal device is not authorized to use A2X communication via PC5 when the terminal device is "not served by E-UTRA" and / or "not served by NR".

[0128] The 11th identification information may be a reason value indicating that direct communication to the terminal device is not permitted because (a) the terminal device is not equipped with a UICC and / or (b) the terminal device is not authorized to use A2X communication via PC5 when the terminal device is “not served by E-UTRA” and / or “not served by NR”.

[0129] The eleventh identification information may be a reason value indicating that the terminal device #2 does not have a UICC. The eleventh identification information may be a reason value indicating that the terminal device #2 is not authorized to use A2X communication via PC5 when the terminal device #2 is “not served by E-UTRA” and / or “not served by NR”.

[0130] The 11th identification information may be a reason value indicating that direct communication with terminal device #2 is not permitted because (a) terminal device #2 does not have a UICC and / or (b) terminal device #2 is not authorized to use A2X communication via PC5 when terminal device #2 is “not served by E-UTRA” and / or “not served by NR”.

[0131] Next, the twelfth identification information may be information indicating whether the terminal device is authorized to use A2X communication via PC5 when the terminal device is "not served by E-UTRA" and / or "not served by NR". The twelfth identification information may be information indicating that the terminal device is authorized or not authorized to use A2X communication via PC5 when the terminal device is "not served by E-UTRA" and / or "not served by NR". The twelfth identification information may be included in the twentieth identification information.

[0132] Furthermore, the 12th identification information may be information indicating whether the terminal device #2 is authorized to use A2X communication via PC5 when the terminal device #2 is "not served by E-UTRA" and / or "not served by NR". The 12th identification information may be information indicating that the terminal device #2 is authorized or not authorized to use A2X communication via PC5 when the terminal device #2 is "not served by E-UTRA" and / or "not served by NR". The 12th identification information may be included in the 20th identification information.

[0133] Next, the thirteenth identification information may be information indicating whether the terminal device has a UICC. The thirteenth identification information may be information indicating whether the terminal device has a UICC or not. The thirteenth identification information may be included in the twentieth identification information.

[0134] Furthermore, the 13th identification information may be information indicating whether the terminal device #2 has a UICC. The 13th identification information may be information indicating whether the terminal device #2 has a UICC or not. The 13th identification information may be included in the 20th identification information.

[0135] Next, the twentieth identification information may be an A2X setting parameter. The twentieth identification information may be information for controlling A2X communication. The twentieth identification information may be a setting parameter for A2X communication via PC5 and / or a setting parameter for A2X communication via Uu.

[0136] The 20th identification information may be preset in the terminal device. The 20th identification information may be set in the USIM. The 20th identification information may be provided as an A2X policy. The 20th identification information may be provided by an A2X application server.

[0137] The twentieth identification information may include the first, and / or the second, and / or the twelfth, and / or the thirteenth identification information.

[0138] [3. Description of procedures used in each embodiment] Next, the procedures used in each embodiment will be described.

[0139] In each embodiment, as shown in FIG. 2, the case where the HSS and UDM, the PCF and PCRF, the SMF and PGW-C, and the UPF and PGW-U are configured as the same device (i.e., the same physical hardware, or the same logical hardware, or the same software) will be described as an example. However, the contents described in this embodiment are also applicable to the case where these are configured as different devices (i.e., different physical hardware, or different logical hardware, or different software). For example, data may be transmitted and received directly between these, or data may be transmitted and received via the N26 interface between the AMF and MME, or data may be transmitted and received via the UE.

[0140] [3.1. Registration Procedure] First, the registration procedure will be described with reference to FIG. 6. The registration procedure is a procedure in 5GS. In this chapter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to take the initiative in registering to the access network_B, and / or the core network_B, and / or the DN. If the UE is not registered to the network, it can execute this procedure at any timing, such as when the power is turned on. In other words, if the UE is in a deregistered state (RM-DEREGISTERED state), it can start this procedure at any timing. Furthermore, each device (particularly the UE and the AMF) can transition to a registered state (RM-REGISTERED state) based on the completion of the registration procedure. Note that the registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state (registered state or deregistered state) for 3GPP access and the registration state for non-3GPP access.

[0141] The registration procedure may also be a registration procedure for initial registration. The registration procedure may also be a registration procedure for mobility and periodic registration update. The registration procedure may also be referred to as registration.

[0142] Furthermore, the registration procedure may be a procedure for updating the location registration information of the UE in the network and / or for the UE to periodically notify the network of the status of the UE and / or for updating certain parameters related to the UE in the network.

[0143] In addition, the UE may perform a registration procedure after performing SNPN selection or PLMN selection.

[0144] The UE may start the registration procedure when mobility across TAs is performed. In other words, the UE may start the registration procedure when the UE moves to a TA different from the TA indicated in the TA list held by the UE. Furthermore, the UE may start the registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may start the registration procedure when a change occurs in capability information and / or preferences regarding the establishment of a PDU session of the UE. Furthermore, the UE may start the registration procedure periodically. Furthermore, the UE may start the registration procedure based on the completion of a UE setting update procedure. It should be noted that the UE can execute the registration procedure at any timing, not limited to the above.

[0145] Additionally, the UE may initiate a registration procedure periodically even when in a registered state.

[0146] In addition, the registration procedure executed based on the mobility of the UE and the registration procedure executed periodically may be expressed as a registration procedure for mobility and registration update. In other words, the registration procedure for mobility and registration update may be a registration procedure executed based on the mobility of the UE, or may be a registration procedure executed periodically. Furthermore, the registration procedure for mobility and registration update may be a registration procedure executed based on a setting update of the UE. Furthermore, the registration procedure for mobility and registration update may be a registration procedure executed to establish a communication path for transmitting and receiving user data. Furthermore, the registration procedure for mobility and registration update may be a registration procedure executed based on a request from the network. Furthermore, in other words, the registration procedure for mobility and registration update may be a registration procedure other than the registration procedure for initial registration.

[0147] Next, each step of the registration procedure will be described. Note that the registration procedure described below may be a registration procedure for initial registration, or a registration procedure for mobility and registration update.

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

[0149] In addition, the UE may send a registration request message to indicate to the network that the UE supports each function or to indicate the UE's request.

[0150] When the 5G AN (or gNB) receives an RRC message including a registration request message, it selects an AMF to which the registration request message is to be transferred (S802). The 5G AN (or gNB) can select an AMF based on information included in the registration request message and / or the RRC message. The 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).

[0151] When the AMF receives the registration request message, the AMF can execute a first condition determination. The first condition determination is for determining whether the network (or the AMF) accepts the request of the UE. When the first condition determination is true, the AMF starts the procedure of (A) in Fig. 6, whereas when the first condition determination is false, the AMF starts the procedure of (B) in Fig. 6.

[0152] The first condition determination may be performed based on the reception of a registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or a context held by the AMF. For example, when the network permits the request of the UE, the first condition determination may be true, and when the network does not permit the request of the UE, the first condition determination may be false. In addition, when the network to which the UE is registered and / or a device in the network supports a function requested by the UE, the first condition determination may be true, and when the network does not support the function requested by the UE, the first condition determination may be false. Furthermore, when the identification information to be transmitted and received is permitted, the first condition determination may be true, and when the identification information to be transmitted and received is not permitted, the first condition determination may be false. In addition, the conditions for determining whether the first condition determination is true or false may not be limited to the above-mentioned conditions.

[0153] First, a case where the first condition determination is true will be described. In the procedure of (A) in Fig. 6, the AMF transmits a registration accept message to the UE via the 5G AN (or gNB) as a response message to the registration request message (S806). Note that the registration accept message is a NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) in the form of an RRC message.

[0154] In addition, the AMF may send a registration accept message including the 20th identification information. In addition, the AMF may send this identification information to indicate that the network supports each function, or to indicate that the UE's request has been accepted.

[0155] Furthermore, the AMF may indicate to the UE what the 20th identification information indicates by sending the identification information in a registration accept message.

[0156] Furthermore, the AMF may select and decide whether to include the 20th identification information in the registration acceptance message based on each 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 context held by the AMF, etc.

[0157] The AMF may also indicate that the UE's request has been accepted by sending a registration acceptance message based on the received identification information, and / or subscription information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0158] Furthermore, the AMF may include information indicating that some of the UE's requests have been rejected in the registration acceptance message and transmit it, or may indicate the reason why some of the UE's requests have been rejected by transmitting information indicating that some of the UE's requests have been rejected. Furthermore, the UE may recognize the reason why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. In addition, the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0159] Next, the UE receives a registration accept message from the AMF via the 5G AN (gNB) (S806). The UE may also receive a registration accept message including the 20th identity from the AMF.

[0160] Here, by receiving the registration accept message, the UE may recognize that the UE's request via the registration request message has been accepted, and the contents of various identification information included in the registration accept message.

[0161] Next, the UE may or may not transmit a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S808). Here, the registration completion message is a NAS message transmitted and received on the N1 interface, but is included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

[0162] Next, the AMF may or may not receive a registration completion message via the 5G AN (gNB) (S808).

[0163] Each device completes the procedure of FIG. 6(A) based on the transmission and reception of the registration acceptance message and / or the registration completion message.

[0164] The UE may also perform SNPN selection or PLMN selection based on receiving the registration accept message, and may also perform SNPN selection or PLMN selection based on sending the registration complete message.

[0165] Next, a case where the first condition determination is false will be described. In the procedure of (B) of Fig. 6, the AMF transmits a registration reject message to the UE via the 5G AN (gNB) as a response message to the registration request message (S810). Here, the registration reject message is a NAS message transmitted and received on the N1 interface, but is included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

[0166] In addition, the AMF may send a registration rejection message including the 20th identity information. In addition, the AMF may send this identity information to indicate that the UE request has been rejected, and may indicate the reason why the UE request has been rejected.

[0167] Furthermore, the AMF may indicate to the UE the contents indicated by the identification information included in the registration rejection message by including the 20th identification information in the registration rejection message and sending it.

[0168] Furthermore, the AMF may select and decide whether to include the 20th identification information in the registration rejection message based on each 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 context held by the AMF, etc.

[0169] Furthermore, the AMF may indicate that the UE's request by the registration request message has been rejected by sending a registration rejection message. Furthermore, the AMF may include information indicating the reason for the rejection in the registration rejection message and transmit it, or may indicate the reason for the rejection by sending the reason for the rejection. Furthermore, the UE may recognize the reason for the rejection of the UE's request by receiving information indicating the reason for the rejection of the UE's request. In addition, the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0170] Next, the UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S810). The UE may also receive a registration rejection message including the 20th identification information from the AMF. By receiving the registration rejection message, the UE may recognize that the UE's request by the registration request message has been rejected and the contents of various identification information included in the registration rejection message.

[0171] Here, if the UE receives the registration rejection message, it may perform SNPN selection or PLMN selection.

[0172] Furthermore, if the UE does not receive a registration rejection message even after a predetermined period of time has elapsed after sending the registration request message, the UE may recognize that the UE's request has been rejected.

[0173] Each device completes procedure (B) of this procedure based on the sending and receiving of the registration rejection message.

[0174] The procedure in FIG. 6(B) may be started when the procedure in FIG. 6(A) is stopped.

[0175] Each device completes the registration procedure based on the completion of the procedure of (A) or (B) in Fig. 6. Each device may transition to a state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure of (A) in Fig. 6. Also, each device may maintain a state in which the UE is not registered in the network (RM_DEREGISTERED state) based on the completion of the procedure of (B) in Fig. 6, or may transition to a state in which the UE is not registered in the network.

[0176] Furthermore, each device may perform processing based on the information transmitted and received in the registration procedure based on the completion of the registration procedure. For example, when transmitting and receiving information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's request has been rejected, or may perform the registration procedure for the core network_B or another cell.

[0177] Further, the UE may store the identification information received with the registration accept message or the registration reject message and may recognize the network's decision based on the completion of the registration procedure.

[0178] Further, the UE may perform SNPN selection or PLMN selection based on the completion of a registration procedure.

[0179] [3.2. PDU Session Establishment Procedure] Next, the PDU session establishment procedure will be described with reference to Fig. 7. Hereinafter, the PDU session establishment procedure may be referred to as this procedure. The PDU session establishment procedure may also be an SM procedure.

[0180] Note that the registration procedure may have been performed one or more times prior to this procedure.

[0181] Next, each step of the PDU session establishment procedure is described.

[0182] First, the UE transmits a PDU session establishment request message to the SMF (S1200, S1202, S1204) to start a PDU session establishment procedure. Then, the SMF receives the PDU session establishment request message from the UE.

[0183] Specifically, the UE initiates the PDU session establishment procedure by sending a NAS message including an N1 SM container including a PDU session establishment request message to the AMF via the access network (S1200). The NAS message is, for example, a message sent via the N1 interface and may be an uplink NAS transport (UL NAS TRANSPORT) message.

[0184] In addition, the UE may indicate that the UE supports each function or may indicate a request from the UE by sending a PDU session establishment request message or a NAS message.

[0185] Next, when the AMF receives the NAS message, it can recognize what the UE is requesting and / or the contents of the information, etc. (message, container, information) contained in the NAS message.

[0186] Next, the AMF selects an SMF as a transfer destination of at least a part of the information, etc. (message, container, information) included in the NAS message received from the UE (S1202). The AMF may select the transfer destination SMF based on the information, etc. (message, container, information) included in the NAS message, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0187] Next, the AMF sends at least a portion of the information (message, container, information) contained in the NAS message received from the UE to the selected SMF, for example via the N11 interface (S1204).

[0188] Next, when the SMF receives information etc. (message, container, information) sent from the AMF, it can recognize what the UE is requesting and / or the content of the information etc. (message, container, information) received from the AMF.

[0189] Here, the SMF may perform a second condition determination. Also, the second condition determination may be for determining whether the network accepts the request of the UE. If the SMF determines that the second condition determination is true, it may start the procedure of (A) in Figure 7, and if the SMF determines that the second condition determination is false, it may start the procedure of (B) in Figure 7.

[0190] The second condition determination may be performed by an NF other than the SMF. When an NF other than the SMF performs the second condition determination, the SMF may provide the NF with information necessary for performing the second condition determination, specifically, at least a part of the information received from the UE (S1206). Then, when the NF determines whether the second condition determination is true or false based on the information received from the SMF, it may convey information including the result of the second condition determination (i.e., true or false) to the SMF. The SMF may determine the identification information and / or the control message to be transmitted to the UE based on the result of the second condition determination received from the NF.

[0191] Furthermore, the second condition determination may be performed based on information received from the AMF (message, container, information), and / or subscription information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc.

[0192] For example, if the network permits the request of the UE, the second condition determination may be determined as true, and if the network does not permit the request of the UE, the second condition determination may be determined as false. Also, if the network to which the UE is connected and / or a device in the network supports the function requested by the UE, the second condition determination may be determined as true, and if the network does not support the function requested by the UE, the second condition determination may be determined as false. Also, if the transmitted and received identification information is permitted, the second condition determination may be determined as true, and if the transmitted and received identification information is not permitted, the second condition determination may be determined as false.

[0193] The conditions for determining whether the second condition determination is true or false are not limited to the above-mentioned conditions.

[0194] Next, each step of the procedure in FIG.

[0195] The SMF may select a UPF for the PDU session to be established and may transmit an N4 session establishment request message to the selected UPF, for example, via the N4 interface (S1208). The N4 session establishment request message may include at least a portion of the PCC rules received from the PCF.

[0196] Here, the SMF may select one or more UPFs based on information received from the AMF (message, container, information), and / or information such as PCC rules received from the PCF, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc. In addition, if multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF. Here, it is assumed that a UPF is selected.

[0197] Next, when the UPF receives the N4 session establishment request message (S1208), the UPF can recognize the contents of the information received from the SMF. In addition, the UPF may send an N4 session establishment response message to the SMF, for example, via the N4 interface, based on the reception of the N4 session establishment request message (S1210).

[0198] Next, when the SMF receives an N4 session establishment response message as a response message to the N4 session establishment request message, it can recognize the contents of the information received from the UPF.

[0199] Next, the SMF sends a PDU session establishment accept message to the UE based on receipt of a PDU session establishment request message, and / or selection of a UPF, and / or receipt of an N4 session establishment response message (S1212) (S1214) (S1216).

[0200] Specifically, the SMF sends an N1 SM container and / or N2 SM information and / or a PDU session ID to the AMF, for example via an N11 interface, based on receiving a PDU session establishment request message and / or selecting a UPF and / or receiving an N4 session establishment response message (S1212). Here, the N1 SM container may include a PDU session establishment accept message. Furthermore, the PDU session ID may be included in the PDU session establishment accept message.

[0201] Next, the AMF that receives the N1 SM container, and / or the N2 SM information, and / or the PDU session ID, sends a NAS message to the UE via the access network (S1214) (S1216). Here, the NAS message is sent, for example, via the N1 interface. Also, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

[0202] Specifically, the AMF sends an N2 PDU session request message to the access network (S1214), and the access network that receives the N2 PDU session request message sends a NAS message to the UE (S1216). Here, the N2 PDU session request message may include a NAS message and / or N2 SM information. The NAS message may also include a PDU session ID and / or an N1 SM container.

[0203] The PDU session establishment acceptance message may be a response message to a PDU session establishment request, and may indicate that the establishment of the PDU session has been accepted.

[0204] Here, the SMF and / or AMF may indicate that at least a portion of the UE's request in the PDU session establishment request message has been accepted by sending a PDU session establishment acceptance message, and / or an N1 SM container, and / or a PDU session ID, and / or a NAS message, and / or N2 SM information, and / or an N2 PDU session request message.

[0205] Here, the SMF and / or AMF may include the 20th identification information in and send the PDU session establishment acceptance message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message.

[0206] Furthermore, by sending this identification information and / or a PDU session establishment acceptance message, the SMF may indicate that the network supports each function, may indicate that the UE request has been accepted, may indicate that the request from the UE is not allowed, or may indicate a combination of these.

[0207] Furthermore, the SMF and / or AMF may determine which identification information to include in the PDU session establishment acceptance message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF and / or AMF, etc.

[0208] Next, the UE receives a PDU session establishment acceptance message and / or a NAS message from the SMF (S1212) (S1214) (S1216). The UE may also receive a PDU session establishment acceptance message and / or a NAS message including the 20th identification information from the SMF. When the UE receives the PDU session establishment acceptance message and / or the NAS message, the UE may recognize that the UE's request via the PDU session establishment request message has been accepted and / or the contents of the information, etc. (message, container, information) included in the NAS message.

[0209] In addition, when the UE receives a PDU session establishment acceptance message and / or a NAS message, it may implement behavior upon receiving each identification information included in the PDU session establishment acceptance message and / or the NAS message.

[0210] Next, each step of the procedure in FIG.

[0211] First, the SMF sends a PDU session establishment reject message to the UE (S1218) (S1220) (S1222).

[0212] Specifically, based on receiving the PDU session establishment request message, the SMF sends an N1 SM container and / or a PDU session ID to the AMF, for example via the N11 interface (S1218). Here, the N1 SM container may include a PDU session establishment rejection message. Further, the PDU session ID may be included in the PDU session establishment rejection message.

[0213] Next, the AMF that receives the N1 SM container and / or the PDU session ID sends a NAS message to the UE via the access network (S1220) (S1222). Here, the NAS message is sent, for example, via the N1 interface. The NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. The NAS message may include the PDU session ID and / or the N1 SM container.

[0214] The PDU session establishment rejection message may be a response message to a PDU session establishment request, and may indicate that the establishment of the PDU session has been rejected.

[0215] Here, the SMF and / or AMF may indicate that the UE's request for the PDU session establishment request message has been rejected by sending a PDU session establishment rejection message, and / or an N1 SM container, and / or a PDU session ID, and / or a NAS message.

[0216] In addition, the SMF may indicate that the UE request has been rejected, or that the request from the UE has not been authorized, by sending a PDU session establishment rejection message, or may indicate a combination of these.

[0217] Here, the SMF and / or AMF may send the 20th identification information including in the PDU session establishment rejection message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message.

[0218] Furthermore, the SMF and / or AMF may determine which identification information to include in the PDU session establishment rejection message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF and / or AMF, etc.

[0219] Furthermore, the SMF and / or AMF may include information indicating that the UE request has been rejected in the PDU session establishment rejection message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message, and may indicate the reason why the UE request has been rejected by transmitting the information indicating that the UE request has been rejected. Furthermore, the UE may recognize the reason why the UE request has been rejected by receiving the information indicating that the UE request has been rejected. The reason for the rejection may be information indicating that the content indicated by the identification information received by the SMF and / or AMF is not permitted and / or unavailable.

[0220] Next, the UE receives a NAS message and / or a PDU session establishment rejection message (S1218) (S1220) (S1222). The UE may also receive a PDU session establishment rejection message and / or a NAS message including the 20th identification information from the SMF. When the UE receives the PDU session establishment rejection message and / or the NAS message, the UE may recognize that the UE's request via the PDU session establishment request message has been rejected and / or the contents of the information, etc. (message, container, information) included in the NAS message.

[0221] In addition, when the UE receives a PDU session establishment rejection message and / or a NAS message, it may implement behavior upon receiving the PDU session establishment rejection message and / or each identification information included in the NAS message.

[0222] Each device may complete this procedure based on the transmission and reception of the PDU session establishment acceptance message. Also, each device may establish a PDU session based on the completion of this procedure. At this time, each device may transition to a state in which it can communicate with the DN using the established PDU session.

[0223] In addition, each device may complete this procedure based on sending and receiving a PDU session establishment rejection message. At this time, each device cannot establish a PDU session, so it cannot communicate with the DN if there is no already established PDU session.

[0224] In addition, each process that the UE performs based on the reception of each identification information shown above may be performed during this procedure or after completion of this procedure, or may be performed after completion of this procedure based on the completion of this procedure.

[0225] [3.3. Network-requested UE policy management procedures] Next, a network-requested UE policy management procedure will be described with reference to Fig. 8. Hereinafter, the network-requested UE policy management procedure may be referred to as this procedure.

[0226] This procedure may be initiated when the PCF wants to update the UE policy.

[0227] Furthermore, prior to this procedure, the registration procedure and / or PDU session establishment procedure may or may not have been performed one or more times.

[0228] Next, each step of the procedure will be described.

[0229] First, the PCF sends a manage UE policy command message to the UE via the AMF (S1400). The PCF may also send the manage UE policy command message including the 20th identification information to the UE.

[0230] Here, the PCF may transmit the 20th identification information to indicate to the UE the contents indicated by the 20th identification information.

[0231] Furthermore, the PCF may determine whether to send a management UE policy command message and / or the 20th identification information based on the state of the UE, and / or information received from the A2X application server, and / or information received from other NFs, etc.

[0232] Then, the UE receives a manage UE policy command message from the PCF via the AMF. The UE may also receive a manage UE policy command message from the PCF, the manage UE policy command message including the twentieth identity.

[0233] Further, the UE may recognize or store the received identification information and may recognize the network's decision based on receiving the Manage UE Policy Command message.

[0234] When the UE receives the management UE policy command message, the UE can execute a third condition determination. The third condition determination is for determining whether the UE accepts the network request. When the third condition determination is true, the UE starts the procedure of Fig. 8 (A), whereas when the third condition determination is false, the UE starts the procedure of Fig. 8 (B).

[0235] The third condition determination may be performed based on the reception of a management UE policy command message, and / or each identification information included in the management UE policy command message, and / or subscriber information, and / or UE capability information, and / or UE policy, and / or UE state, and / or context held by the UE, etc. For example, when the UE permits a request from the network, the third condition determination may be true, and when the UE does not permit a request from the network, the third condition determination may be false. Also, when the UE supports a function requested by the network, the third condition determination may be true, and when the UE does not support a function requested by the network, the third condition determination may be false. Furthermore, when the identification information to be transmitted and received is permitted, the third condition determination may be true, and when the identification information to be transmitted and received is not permitted, the third condition determination may be false. The conditions for determining whether the third condition determination is true or false may not be limited to the above-mentioned conditions.

[0236] First, the case where the third condition is true will be described.

[0237] In the procedure of (A) of FIG. 8, the UE sends a manage UE policy complete message to the PCF via the AMF as a response message to the manage UE policy command message (S1402).

[0238] The PCF then receives a manage UE policy complete message from the UE via the AMF.

[0239] Further, the PCF may recognize the UE's decision based on receipt of a manage UE policy complete message.

[0240] Each device may complete the procedure of FIG. 8(A) based on sending and receiving a manage UE policy command message and / or a manage UE policy complete message.

[0241] Next, a case where the third condition is false will be described.

[0242] In the procedure of (B) of Figure 8, the UE sends a manage UE policy command reject message to the PCF via the AMF as a response message to the manage UE policy command message (S1404).

[0243] The PCF then receives a management UE policy command reject message from the UE via the AMF.

[0244] Further, the PCF may recognize the UE's decision based on receipt of a manage UE policy command reject message.

[0245] Each device may complete the procedure of FIG. 8(B) based on sending and receiving the manage UE policy command message and / or the manage UE policy command reject message.

[0246] Further, each device may complete the procedure based on completion of the above-mentioned processing, and / or sending and receiving a management UE policy command message, and / or sending and receiving a management UE policy complete message, and / or sending and receiving a management UE policy command reject message.

[0247] Furthermore, each device may perform processing based on the identification information transmitted and received in this procedure upon completion of this procedure.

[0248] In addition, the UE may add a new UE policy, modify a UE policy stored in the UE, or delete a UE policy stored in the UE based on the completion of the network requested UE policy management procedure.

[0249] [3.4. UE Request A2X Policy Provisioning Procedure] Next, a UE-requested A2X policy provisioning procedure will be described with reference to Fig. 9. Hereinafter, the UE-requested A2X policy provisioning procedure may be referred to as this procedure.

[0250] This procedure may be initiated when the UE requests a UE policy or an A2X policy.

[0251] Furthermore, prior to this procedure, the registration procedure and / or PDU session establishment procedure may or may not have been performed one or more times.

[0252] Next, each step of the procedure will be described.

[0253] First, the UE sends a UE policy provisioning request message to the PCF via the AMF (S1600).

[0254] Next, the PCF receives a UE policy provision request message from the UE via the AMF.

[0255] Further, the PCF may recognize the UE's decision based on receiving the UE Policy Provisioning Request message.

[0256] When the PCF receives the UE policy provision request message, the PCF can execute a fourth condition determination. The fourth condition determination is for determining whether the network accepts the UE request. When the fourth condition determination is true, the PCF starts the procedure of (A) in Fig. 9, whereas when the fourth condition determination is false, the PCF starts the procedure of (B) in Fig. 9.

[0257] The fourth condition determination may be performed based on the reception of a UE policy provision request message, and / or each identification information included in the UE policy provision request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or a context held by the PCF. For example, when the network permits the request of the UE, the fourth condition determination may be true, and when the network does not permit the request of the UE, the fourth condition determination may be false. Furthermore, when the network to which the UE is registered and / or a device in the network supports a function requested by the UE, the fourth condition determination may be true, and when the network does not support the function requested by the UE, the fourth condition determination may be false. Furthermore, when the identification information to be transmitted and received is permitted, the fourth condition determination may be true, and when the identification information to be transmitted and received is not permitted, the fourth condition determination may be false. The conditions for determining whether the fourth condition determination is true or false may not be limited to the above-mentioned conditions.

[0258] First, the case where the fourth condition is true will be described.

[0259] In the procedure of (A) of Fig. 9, the PCF may perform a network request policy management procedure (S1602). Here, the network request policy management procedure may be the procedure described in the above-mentioned Chapter 3.3.

[0260] Each device may complete the procedure of FIG. 9(A) based on sending and receiving a UE policy provision request message and / or completing a network requested policy management procedure.

[0261] Next, a case where the fourth condition is false will be described.

[0262] In the procedure of (B) of Figure 9, the PCF transmits a UE policy provisioning reject message to the UE via the AMF as a response message to the UE policy provision request message (S1604). In addition, the PCF may transmit the UE policy provisioning reject message including the 20th identification information to the UE.

[0263] Here, the PCF may indicate to the UE the contents indicated by each identification information by transmitting the 20th identification information.

[0264] The PCF may also determine whether to send a UE policy provision rejection message and / or the 20th identification information based on the state of the UE, and / or information received from the A2X application server, and / or information received from other NFs, etc.

[0265] Then, the UE receives a UE policy provision rejection message from the PCF via the AMF. The UE may also receive a UE policy provision rejection message from the PCF, the UE including the twentieth identity information.

[0266] Further, the UE may be aware of the network's decision based on receiving a UE policy provision rejection message.

[0267] In addition, when the UE receives a UE policy provision rejection message, the UE may implement the behavior when it receives the 20th identification information included in the UE policy provision rejection message.

[0268] Each device may complete the procedure of (B) in FIG. 9 based on sending and receiving a UE policy provision request message and / or a UE policy provision rejection message.

[0269] Further, each device may complete the procedure based on completion of the above-mentioned processing, and / or sending and receiving a UE policy provision request message, and / or completing a network requested policy management procedure, and / or sending and receiving a UE policy provision rejection message.

[0270] Furthermore, each device may perform processing based on the identification information transmitted and received in this procedure upon completion of this procedure.

[0271] Furthermore, based on the completion of this procedure, the UE may add a new UE policy, change a UE policy stored in the UE, or delete a UE policy stored in the UE.

[0272] [3.5 PC5 unicast link establishment procedure] Next, the PC5 unicast link establishment procedure will be described with reference to FIG. 10. Hereinafter, the PC5 unicast link establishment procedure may be referred to as this procedure. This procedure may be an A2X procedure or a procedure for A2X communication. This procedure may be an A2X procedure for DAA or a procedure for unicast mode A2X communication on NR-PC5. This procedure may be a procedure for direct C2 communication.

[0273] In addition, prior to this procedure, the registration procedure, and / or the PDU session establishment procedure, and / or the service approval and provision may or may not have been performed one or more times.

[0274] In addition, in this procedure, there may be an initiating UE and a target UE.

[0275] In this procedure, the initiating UE and the target UE may transmit and receive control messages on the PC5. Each UE may be in a unicast mode. Each UE may have a UE policy for BRID and / or DAA.

[0276] Next, each step of the procedure will be described.

[0277] First, the initiating UE transmits a direct link establishment request message to the target UE (S2000). The initiating UE may transmit the direct link establishment request message including one or more pieces of identification information among the first and second pieces of identification information.

[0278] By transmitting these pieces of identification information, the initiating UE may indicate that the initiating UE supports each function, or may indicate a request of the initiating UE. Furthermore, when a plurality of pieces of identification information are transmitted and received, two or more pieces of identification information may be configured as one or more pieces of identification information. Furthermore, the information indicating support of each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0279] Here, the initiating UE may indicate the contents of each piece of identification information to the target UE by transmitting a direct link establishment request message, or may indicate the contents of each piece of identification information to the target UE by transmitting one or more pieces of identification information among the first and second identification information.

[0280] In addition, the initiating UE may select and decide whether to include one or more of the first and second identification information in the direct link establishment request message based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0281] The initiating UE may also request establishment of a direct link by sending a direct link establishment request message.

[0282] Next, the target UE receives a direct link establishment request message from the initiating UE, and may receive the direct link establishment request message including one or more of the first and second identification information from the initiating UE.

[0283] When the target UE receives the direct link establishment request message, it may recognize the content requested by the initiating UE and / or the content of the information (message, container, identification information) included in the direct link establishment request message.

[0284] Here, the target UE may perform a fifth condition determination. The fifth condition determination may be for the target UE to determine whether or not to accept the request of the initiating UE. If the target UE determines that the fifth condition determination is true, the target UE may start the procedure of (A) in Fig. 10, and if the target UE determines that the fifth condition determination is false, the target UE may start the procedure of (B) in Fig. 10.

[0285] In addition, the fifth condition determination may be performed based on information (message, container, information) received from the initiating UE, and / or subscription information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the target UE, etc.

[0286] For example, if the target UE permits the request of the initiating UE, the fifth condition determination may be determined as true, and if the target UE does not permit the request of the initiating UE, the fifth condition determination may be determined as false. If the target UE supports the function requested by the initiating UE, the fifth condition determination may be determined as true, and if the target UE does not support the function requested by the initiating UE, the fifth condition determination may be determined as false. If the transmitted and received identification information is permitted, the fifth condition determination may be determined as true, and if the transmitted and received identification information is not permitted, the fifth condition determination may be determined as false.

[0287] The conditions for determining whether the fifth condition determination is true or false are not limited to the above-mentioned conditions.

[0288] Next, each step of the procedure in FIG. 10(A) will be described.

[0289] Based on receiving the direct link establishment request message, the target UE sends a direct link establishment accept message to the initiating UE (S2002). In addition, the target UE may send the direct link establishment accept message including one or more identification information among the tenth to thirteenth identification information to the initiating UE.

[0290] Here, the target UE may indicate that at least a part of the request of the initiating UE is accepted by sending a direct link establishment acceptance message, and may indicate that at least a part of the request of the initiating UE is accepted by sending one or more identification information of the tenth to thirteenth identification information.

[0291] By transmitting these identification information and / or the direct link establishment acceptance message, the target UE may indicate that the target UE supports each function, may indicate that the request from the initiating UE has been accepted, may indicate that the request from the initiating UE is not permitted, or may indicate a combination of these. Furthermore, when multiple pieces of identification information are transmitted and received, two or more pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0292] Furthermore, the target UE may determine which identification information to include in the direct link establishment acceptance message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the target UE, etc.

[0293] The direct link establishment acceptance message may be a response message to the direct link establishment request message, and may indicate that the direct link establishment request message has been accepted.

[0294] Next, the initiating UE receives a direct link establishment acceptance message from the target UE.

[0295] When the initiating UE receives the direct link establishment acceptance message, it can recognize that the initiating UE's request has been accepted and / or the contents of the information, etc. (message, container, identification information) included in the direct link establishment acceptance message.

[0296] Each device may complete the procedure of FIG. 10A based on the transmission and reception of the direct link establishment request message and / or the direct link establishment acceptance message. Each device may establish a PC5 unicast link based on the completion of this procedure. At this time, each device may transition to a state in which communication using the PC5 unicast link is possible.

[0297] Next, each step of the procedure in FIG. 10(B) will be described.

[0298] First, the target UE transmits a direct link establishment reject message to the initiating UE based on receiving the direct link establishment request message (S2004). The target UE may also transmit the direct link establishment reject message including one or more of the tenth to thirteenth identification information to the initiating UE.

[0299] The direct link establishment rejection message may be a response message to the direct link establishment request message, and may indicate that the direct link establishment request message has been rejected.

[0300] In addition, the target UE may indicate that the initiating UE's request has been rejected by sending a direct link establishment rejection message.

[0301] In addition, the target UE may determine which identification information to include in the direct link establishment rejection message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the target UE, etc.

[0302] Next, the initiating UE receives a direct link establishment rejection message from the target UE, and may receive a direct link establishment rejection message from the target UE, the direct link establishment rejection message including one or more of the tenth to thirteenth identities.

[0303] When the initiating UE receives a direct link establishment rejection message, it may recognize that the initiating UE's request has been rejected and / or the contents of the information, etc. (message, container, identification information) included in the direct link establishment rejection message.

[0304] Each device may complete the procedure of FIG. 10B based on the transmission and reception of the direct link establishment request message and / or the direct link establishment rejection message. At this time, each device may not be able to establish a PC5 unicast link. Also, each device may not be able to communicate using the PC5 unicast link.

[0305] Each device may complete this procedure based on sending and receiving a direct link establishment request message, and / or a direct link establishment acceptance message, and / or a direct link establishment rejection message.

[0306] Furthermore, the behavior of each UE based on receiving the above identification information may be executed after completion of this procedure.

[0307] [4. Embodiment] Next, each embodiment will be described.

[0308] [4.1. First embodiment] First, the first embodiment will be described with reference to Fig. 11. In this chapter, the first embodiment may be referred to as the present embodiment.

[0309] In this embodiment, a registration procedure, and / or a PDU session establishment procedure, and / or a network-requested UE policy management procedure, and / or a UE-requested A2X policy provisioning procedure, and / or a PC5 unicast link establishment procedure may be performed. Also, these procedures may be performed before this embodiment.

[0310] In this embodiment, the first control message may be a direct link establishment request message, the second control message may be a direct link establishment accept message or a direct link establishment reject message, and the first and / or second control message may be a message used in the A2X procedure or a message used in the DAA.

[0311] In this embodiment, there may be a terminal device #1 and a terminal device #2. Each terminal device may be a UAV. The terminal device #1 may be an initiating UE. The terminal device #2 may be a target UE. Each terminal device may be in a unicast mode. Each terminal device may have a UE policy for BRID and / or DAA.

[0312] Furthermore, terminal device #1 and / or terminal device #2 may hold a twentieth identification information.

[0313] Each step of this embodiment will now be described.

[0314] First, terminal device #1 may transmit a first control message to terminal device #2 (S2200). Terminal device #1 may also transmit a first control message including one or more pieces of identification information from the first to second identification information to terminal device #2.

[0315] Here, terminal device #1 may transmit one or more pieces of identification information from the first and second identification information, thereby indicating to terminal device #2 the contents indicated by each piece of identification information.

[0316] Specifically, by transmitting the first identification information, terminal device #1 may indicate to terminal device #2 whether terminal device #1 is authorized to use A2X communication via PC5 when terminal device #1 is "not served by E-UTRA" and / or "not served by NR". Also, by transmitting the first identification information, terminal device #1 may indicate to terminal device #2 whether terminal device #1 is authorized or not authorized to use A2X communication via PC5 when terminal device #1 is "not served by E-UTRA" and / or "not served by NR".

[0317] Furthermore, terminal device #1 may indicate to terminal device #2 whether terminal device #1 has a UICC by transmitting the second identification information. Furthermore, terminal device #1 may indicate to terminal device #2 whether terminal device #1 has a UICC or not by transmitting the second identification information.

[0318] In addition, terminal device #1 does not need to transmit the first and / or second identification information, does not need to include the first and / or second identification information in the first control message, and does not need to transmit the first control message if (a) terminal device #1 does not have a UICC and / or (b) when terminal device #1 is "not served by E-UTRA" and / or "not served by NR" and terminal device #1 is not authorized to use A2X communication via PC5.

[0319] Furthermore, if (a) terminal device #1 does not have a UICC and / or (b) terminal device #1 does not have the first and / or 20th identification information, terminal device #1 does not need to transmit the first and / or second identification information, does not need to include the first and / or second identification information in the first control message, and does not need to transmit the first control message.

[0320] Furthermore, if (a) terminal device #1 does not have a UICC and / or (b) terminal device #1 has the first and / or 20th identification information, terminal device #1 does not need to transmit the first and / or second identification information, does not need to include the first and / or second identification information in the first control message, and does not need to transmit the first control message.

[0321] In addition, based on the 20th identification information, terminal device #1 may recognize (a) whether terminal device #2 is equipped with a UICC and / or (b) whether terminal device #2 is authorized to use A2X communication via PC5 when terminal device #2 is “not served by E-UTRA” and / or “not served by NR”.

[0322] In addition, terminal device #1 does not need to transmit the first and / or second identification information, does not need to include the first and / or second identification information in the first control message, and does not need to transmit the first control message if (a) terminal device #2 does not have a UICC and / or (b) when terminal device #2 is "not served by E-UTRA" and / or "not served by NR" and terminal device #2 is not authorized to use A2X communication via PC5.

[0323] Terminal device #1 may determine whether to transmit the first control message and / or each piece of identification information based on the state of terminal device #1 and / or information received from the network.

[0324] Next, terminal device #2 may receive a first control message from terminal device #1 (S2200). Furthermore, terminal device #2 may receive a first control message from terminal device #1 that includes one or more pieces of identification information from the first and second identification information.

[0325] Furthermore, terminal device #2 may recognize or store the received identification information based on the reception of the first control message, or may recognize the decision of terminal device #1. Furthermore, when terminal device #2 receives the first control message, it may perform the behavior when receiving each identification information.

[0326] Specifically, when terminal device #2 receives the first identification information, it may recognize whether terminal device #1 is authorized to use A2X communication via PC5 when terminal device #1 is "not served by E-UTRA" and / or "not served by NR." Also, when terminal device #2 receives the first identification information, it may recognize whether terminal device #1 is authorized or not authorized to use A2X communication via PC5 when terminal device #1 is "not served by E-UTRA" and / or "not served by NR."

[0327] Furthermore, when terminal device #2 receives the second identification information, it may recognize whether terminal device #1 has a UICC. Furthermore, when terminal device #2 receives the second identification information, it may recognize whether terminal device #1 has a UICC or not.

[0328] Furthermore, when terminal device #2 receives the first and / or second identification information, it may store the status of terminal device #1 and / or information related to terminal device #1. In other words, when terminal device #2 receives the first and / or second identification information, it may store (a) whether terminal device #1 is equipped with a UICC and / or (b) whether terminal device #1 is authorized to use A2X communication via PC5 when terminal device #1 is "not served by E-UTRA" and / or "not served by NR".

[0329] In addition, based on the 20th identification information, terminal device #2 may recognize (a) whether terminal device #1 is equipped with a UICC and / or (b) whether terminal device #1 is authorized to use A2X communication via PC5 when terminal device #1 is “not served by E-UTRA” and / or “not served by NR”.

[0330] Also, if (a) terminal device #1 is not equipped with a UICC and / or (b) terminal device #1 is not authorized to use A2X communication via PC5 when terminal device #1 is "not served by E-UTRA" and / or "not served by NR", terminal device #2 does not need to perform a new PC5 unicast link establishment procedure with terminal device #1, and does not need to perform a PC5 unicast link establishment procedure for DAA and / or DDAA and / or BRID.

[0331] Next, terminal device #2 may transmit a second control message to terminal device #1 (S2202). Terminal device #2 may also transmit a second control message including one or more of the tenth to thirteenth identification information to terminal device #1.

[0332] Here, terminal device #2 may transmit one or more pieces of identification information among the tenth to thirteenth identification information, thereby indicating to terminal device #1 the contents indicated by each piece of identification information.

[0333] Specifically, terminal device #2 may indicate a reason value indicating #1 (direct communication to the target UE not allowed) to terminal device #1 by transmitting the tenth identification information. Furthermore, terminal device #2 may indicate to terminal device #1 that direct communication with terminal device #2 is not allowed by transmitting the tenth identification information.

[0334] In addition, terminal device #2 may transmit the tenth and / or eleventh identification information, may include the tenth and / or eleventh identification information in the second control message, or may transmit the second control message when (a) terminal device #2 does not have a UICC and / or (b) when terminal device #2 is “not served by E-UTRA” and / or “not served by NR” and terminal device #2 is not authorized to use A2X communication via PC5.

[0335] In addition, terminal device #2 may transmit the tenth and / or eleventh identification information, may include the tenth and / or eleventh identification information in the second control message, or may transmit the second control message if (a) terminal device #2 does not have a UICC and / or (b) terminal device #2 does not have the twelfth and / or eleventh identification information.

[0336] In addition, terminal device #2 may transmit the 10th and / or 11th identification information, may include the 10th and / or 11th identification information in the second control message, or may transmit the second control message if (a) terminal device #2 does not have a UICC and / or (b) terminal device #2 has the 12th and / or 20th identification information.

[0337] Furthermore, the terminal device #2 may determine whether to transmit the tenth identification information or include the tenth identification information in the second control message based on the first and / or second identification information. Furthermore, the terminal device #2 may transmit the tenth and / or eleventh identification information, may include the tenth and / or eleventh identification information in the second control message, or may transmit the second control message when (a) the terminal device #1 does not have a UICC and / or (b) the terminal device #1 is “not served by E-UTRA” and / or “not served by NR” and the terminal device #1 is not authorized to use A2X communication via PC5.

[0338] Furthermore, the terminal device #2 may indicate to the terminal device #1 that the terminal device #2 does not have a UICC by transmitting the eleventh identification information. Furthermore, the terminal device #2 may indicate to the terminal device #1 that the terminal device #2 is not authorized to use A2X communication via PC5 when the terminal device #2 is "not served by E-UTRA" and / or "not served by NR" by transmitting the eleventh identification information.

[0339] In addition, by transmitting the 11th identification information, terminal device #2 may indicate to terminal device #1 that direct communication with terminal device #2 is not permitted because (a) terminal device #2 does not have a UICC and / or (b) when terminal device #2 is “not served by E-UTRA” and / or “not served by NR”, terminal device #2 is not authorized to use A2X communication via PC5.

[0340] Furthermore, by transmitting the 12th identification information, terminal device #2 may indicate to terminal device #1 whether terminal device #2 is authorized to use A2X communication via PC5 when terminal device #2 is "not served by E-UTRA" and / or "not served by NR". Furthermore, by transmitting the 12th identification information, terminal device #2 may indicate to terminal device #1 whether terminal device #2 is authorized or not authorized to use A2X communication via PC5 when terminal device #2 is "not served by E-UTRA" and / or "not served by NR".

[0341] Moreover, terminal device #2 may indicate to terminal device #1 whether terminal device #2 has a UICC or not by transmitting the thirteenth identification information. Moreover, terminal device #2 may indicate to terminal device #1 whether terminal device #2 has a UICC or not by transmitting the thirteenth identification information.

[0342] Terminal device #2 may determine whether or not to transmit the second control message and / or each piece of identification information based on the state of terminal device #2 and / or information received from the network.

[0343] Next, terminal device #1 receives a second control message from terminal device #2 (S2202). Terminal device #1 may also receive a second control message from terminal device #2 that includes one or more of the tenth to thirteenth identification information.

[0344] Furthermore, terminal device #1 may recognize or store the received identification information based on the reception of the second control message, or may recognize the decision of terminal device #2. Furthermore, when terminal device #1 receives the second control message, it may perform the behavior when receiving each identification information.

[0345] Specifically, when terminal device #1 receives the tenth identification information, it may recognize the reason value indicating #1 (direct communication to the target UE not allowed). Also, when terminal device #1 receives the tenth identification information, it may recognize that direct communication with terminal device #2 is not allowed.

[0346] Furthermore, when terminal device #1 receives the eleventh identification information, it may recognize that terminal device #2 does not have a UICC. Furthermore, when terminal device #1 receives the eleventh identification information, it may recognize that terminal device #2 is not authorized to use A2X communication via PC5 when terminal device #2 is "not served by E-UTRA" and / or "not served by NR".

[0347] Furthermore, when terminal device #1 receives the 11th identification information, it may recognize that direct communication with terminal device #2 is not permitted because (a) terminal device #2 does not have a UICC and / or (b) when terminal device #2 is "not served by E-UTRA" and / or "not served by NR", terminal device #2 is not authorized to use A2X communication via PC5.

[0348] Furthermore, when terminal device #1 receives the 10th and / or 11th identification information, it may not attempt to initiate a PC5 unicast link establishment procedure with terminal device #2. Furthermore, when terminal device #1 receives the 10th and / or 11th identification information, it may not attempt to initiate a PC5 unicast link establishment procedure with terminal device #2 for at least time T.

[0349] Furthermore, when terminal device #1 receives the 12th identification information, it may recognize whether terminal device #2 is authorized to use A2X communication via PC5 when terminal device #2 is "not served by E-UTRA" and / or "not served by NR". Furthermore, when terminal device #1 receives the 12th identification information, it may recognize whether terminal device #2 is authorized or not authorized to use A2X communication via PC5 when terminal device #2 is "not served by E-UTRA" and / or "not served by NR".

[0350] Furthermore, when terminal device #1 receives the thirteenth identification information, it may recognize whether terminal device #2 has a UICC. Furthermore, when terminal device #1 receives the thirteenth identification information, it may recognize whether terminal device #2 has a UICC or not.

[0351] Furthermore, when terminal device #1 receives the 12th and / or 13th identification information, it may store the status of terminal device #2 and / or information related to terminal device #2. In other words, when terminal device #1 receives the 12th and / or 13th identification information, it may store (a) whether terminal device #2 is equipped with a UICC and / or (b) whether terminal device #2 is authorized to use A2X communication via PC5 when terminal device #2 is "not served by E-UTRA" and / or "not served by NR".

[0352] Furthermore, when terminal device #1 receives the tenth and / or eleventh identification information, it may delete the status of terminal device #2 and / or information related to terminal device #2. In other words, when terminal device #1 receives the tenth and / or eleventh identification information, it may delete information regarding (a) whether terminal device #2 is equipped with a UICC and / or (b) whether terminal device #2 is authorized to use A2X communication via PC5 when terminal device #2 is "not served by E-UTRA" and / or "not served by NR".

[0353] Also, if (a) terminal device #2 is not equipped with a UICC and / or (b) terminal device #2 is not authorized to use A2X communication via PC5 when terminal device #2 is "not served by E-UTRA" and / or "not served by NR", terminal device #1 does not need to perform a new PC5 unicast link establishment procedure with terminal device #2, and does not need to perform a PC5 unicast link establishment procedure for DAA and / or DDAA and / or BRID.

[0354] [4.2. Second embodiment] First, the second embodiment will be described. In this chapter, the second embodiment may be referred to as the present embodiment.

[0355] In this embodiment, a registration procedure, and / or a PDU session establishment procedure, and / or a network requested UE policy management procedure, and / or a UE requested A2X policy provision procedure, and / or a PC5 unicast link establishment procedure may be performed. Also, these procedures may be performed before this embodiment.

[0356] In addition, in this embodiment, A2X communication via PC5 in broadcast mode may be implemented. In this embodiment, A2X procedure may be implemented. In this embodiment, A2X procedure for DAA and / or A2X procedure for BRID may be implemented. In this embodiment, broadcast mode A2X communication on PC5 may be implemented.

[0357] The terminal device may also hold a twentieth identity. The terminal device may also be in a broadcast mode. The terminal device may also be provided with a UE policy for BRID and / or DAA.

[0358] The behavior of the terminal device in this embodiment will be described below.

[0359] The terminal device may be performing A2X communication via PC5.

[0360] The terminal device may be equipped with radio parameters.

[0361] Here, the radio parameters may be associated with a geographical area, and / or an altitude range, and / or a validity timer, and the radio parameters may be configured with a geographical area, and / or an altitude range, and / or a validity timer.

[0362] In addition, radio parameters may be set for each PC5 RAT (i.e., LTE PC5, NR PC5).

[0363] In this embodiment, the timer may be a valid timer, a timer using a valid timer, a timer using radio parameters, a timer using radio parameters associated with the valid timer, or a timer using a valid timer associated with the radio parameters. Also, the valid timer may be read as a timer.

[0364] In addition, when the terminal device is provided with the radio parameters, it may start the validity timer, or it may start the timer using the radio parameters related to the validity timer, or it may start the timer using the validity timer.

[0365] In addition, the terminal device may start a validity timer when provided with the radio parameters, may start a timer using the radio parameters associated with the validity timer, or may start a timer using the validity timer.

[0366] In addition, when starting A2X communication, the terminal device may start a validity timer, may start a timer using radio parameters related to the validity timer, or may start a timer using the validity timer.

[0367] In addition, when starting A2X communication, the terminal device may start a validity timer, may start a timer using radio parameters related to the validity timer, or may start a timer using the validity timer.

[0368] Here, the validity timer or radio parameters related to the validity timer may be set for each PC5 RAT (i.e., LTE PC5, NR PC5). In addition, when there are multiple validity timers or radio parameters related to the validity timers set for each PC5 RAT, the terminal device may select or use the validity timer set for the longest time. For example, when the validity timer set for LTE PC5 is 10 seconds and the validity timer set for NR PC5 is 50 seconds, the terminal device may select or use the validity timer set for NR PC5.

[0369] Also, the terminal device may start a validity timer for each PC5 RAT, may start a timer using radio parameters related to the validity timer, or may start a timer using the validity timer. For example, if the terminal device receives radio parameters in LTE, the terminal device may select or use the validity timer set for LTE PC5.

[0370] Furthermore, if the terminal device (a) starts a timer when the radio parameters are provided, and / or (b) the validity timer, or the timer using the validity timer, or the timer using the radio parameters associated with the validity timer, expires, the terminal device may select or use a validity timer set for another PC5 RAT that is different from the timer set for the active PC5 RAT. For example, if the terminal device starts a timer when the radio parameters are provided, and the timer using the validity timer set for LTE PC5 expires, the terminal device may start a timer using the validity timer set for NR PC5.

[0371] Furthermore, if the terminal device (a) starts a timer when starting A2X communication, and / or (b) the validity timer, or the timer using the validity timer, or the timer using the radio parameters associated with the validity timer expires, the terminal device may not select or use a validity timer set for another PC5 RAT different from the timer set for the active PC5 RAT. For example, if the terminal device starts a timer when starting A2X communication and the timer using the validity timer set for LTE PC5 expires, the terminal device may not start a timer using the validity timer set for NR PC5.

[0372] When a terminal device is performing A2X communication on PC5 using radio parameters associated with a geographical area and / or altitude range and moves out of the geographical area and / or altitude range, the terminal device may stop A2X communication on PC5 and may stop the validity timer.

[0373] Furthermore, if the terminal device is "not served by NR" and "not served by E-UTRA" for A2X communication via PC5 and / or if the terminal device intends to use radio resources other than those operated by the serving cell for A2X communication on PC5, the terminal device may select appropriate radio parameters for the new geographical area.

[0374] Furthermore, if the terminal device is "served by NR" and / or "served by E-UTRA" for A2X communication on PC5 and / or if the terminal device intends to use radio resources for A2X communication on PC5 operated by the serving cell, the terminal device may perform a procedure to initiate A2X communication on PC5 when it is "served by NR" and / or "served by E-UTRA" on PC5.

[0375] When a terminal device is performing A2X communication on PC5 using radio parameters associated with the validity timer and the validity timer expires, the terminal device may stop A2X communication on PC5 and may perform a procedure to start A2X communication on Uu.

[0376] Furthermore, if the terminal device is "not served by NR" and "not served by E-UTRA" for A2X communication via PC5 and / or if the terminal device intends to use radio resources other than those operated by the serving cell for A2X communication on PC5, the terminal device may select appropriate radio parameters for the new geographical area.

[0377] Furthermore, when the terminal device is "served by NR" and / or "served by E-UTRA" for A2X communication on PC5, and / or when the terminal device intends to use radio resources for A2X communication on PC5 operated by the serving cell, the terminal device may perform a procedure for initiating A2X communication on PC5 when it is "served by NR" and / or "served by E-UTRA" on PC5, and may perform a procedure for initiating A2X communication on Uu.

[0378] In addition, when a terminal device is performing A2X communication on PC5 using radio parameters associated with a validity timer and the validity timer expires, the terminal device may request a new validity timer or radio parameters from the 5G AN (or gNB) and / or the network.

[0379] In addition, the terminal device may be performing A2X communication on PC5 using radio parameters associated with the validity timer, and before the validity timer expires, the terminal device may request a new validity timer or radio parameters from the 5G AN (or gNB) and / or the network.

[0380] In addition, when the terminal device is performing A2X communication on PC5 using radio parameters related to the validity timer and the validity timer expires, the terminal device may update the validity timer or the radio parameters.

[0381] In addition, the terminal device may be performing A2X communication on PC5 using radio parameters related to the validity timer, and before the validity timer expires, the terminal device may update the validity timer or the radio parameters.

[0382] In addition, when the terminal device receives a new valid timer or radio parameters from the 5G AN (or gNB) and / or the network, it may stop a running timer, start a timer using the received valid timer, or start a timer using the received radio parameters.

[0383] In addition, the terminal device may stop a running timer or stop A2X communication during an emergency call or emergency service, and may request a valid timer or radio parameters from the network or update the valid timer or radio parameters during an emergency call or emergency service.

[0384] In addition, in the case of an emergency call or emergency services, the terminal device may initiate A2X communication using radio parameters associated with the timer, even if the timer has already expired.

[0385] 5. Variations A program that operates on an apparatus according to an aspect of the present invention may be a program that controls a Central Processing Unit (CPU) or the like to cause a computer to function so as to realize the functions of an embodiment according to an aspect of 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 non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or other storage device system.

[0386] A program for implementing the functions of the embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. The program may be implemented by loading the program recorded on the recording medium into a computer system and executing it. The term "computer system" as used herein refers to a computer system built into an apparatus, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other recording medium that can be read by a computer.

[0387] In addition, each functional block or feature of the device used in the above-mentioned embodiment may be implemented or performed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. The electric circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. In addition, when a technology for integrated circuitization that replaces current integrated circuits appears due to the progress of semiconductor technology, one or more aspects of the present invention may use a new integrated circuit based on that technology.

[0388] The present invention is not limited to the above-mentioned embodiment. In the embodiment, one example of the device is described, but the present invention is not limited to this and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices of AV equipment, kitchen equipment, cleaning / washing equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0389] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within the scope of the gist of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are replaced with elements that have the same effect are also included. [Explanation of symbols]

[0390] 1 Mobile communication systems 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access Network_A (E-UTRAN) 90 Core Network_A 120 Access Network_B (5G AN) 122 gNB 130 UPF 132 SMF 140 AMF 150 UDM 160 PCF 190 Core Network_B 235 UPF_A 239 UPF_C

Claims

1. A terminal device comprising a transmitting / receiving unit and a control unit, The aforementioned terminal device is an Uncrewed Aerial Vehicle (UAV), When the transmitting / receiving unit receives first control information related to Aircraft-to-anything (A2X) communication on PC5 from the core network, the control unit starts a first timer using the timer value included in the first control information. When the first timer expires, the control unit requests second control information related to A2X communication from the core network. Terminal device.

2. When the transmitting / receiving unit receives third control information relating to the A2X communication on the PC5 from the core network, the control unit stops the first timer that is running and starts the first timer using the timer value included in the third control information. The terminal device according to claim 1.

3. A method used in terminal devices, The aforementioned terminal device is an Uncrewed Aerial Vehicle (UAV), When first control information regarding Aircraft-to-anything (A2X) communication on PC5 is received from the core network, the first timer is started using the timer value included in the first control information. When the first timer expires, a request for second control information regarding A2X communication is sent to the core network. method.

Images