User equipment (UE)
By receiving PDU session change command messages in the 5G system through user equipment (UE), identifying and processing the authentication and authorization cancellation of the UAV, the clear behavior of the UAV and the effective release of the communication path are achieved, and the 5G system is solved. Issues of unclear management of direct C2 communication paths.
Patent Information
- Application Number
- CN202380036009.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-27
- Filing Date
- 2023-04-24
- Publication Date
- 2024-12-03
AI Technical Summary
In 5G systems, the methods for establishing, authenticating and authorizing the direct C2 communication path between the UAV and the UAV controller are unclear, and the behavior after canceling the authentication and authorization and the process of releasing the communication path are unclear.
The user equipment (UE) has a transmitting and receiving unit and a control unit. By receiving a PDU session change command message, it recognizes that the authentication and authorization of direct C2 communication is cancelled and the process of releasing the communication path is started.
The behavior of UAV when authentication and authorization is cancelled is clarified, and the release process and period of direct C2 communication path is clarified, solving the problem of unclear methods in the prior art.
Smart Images

Figure CN119073003A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a UE (User Equipment). Background Art
[0002] In 3GPP (3rd Generation Partnership Project), the system architecture of 5GS (5G System) as the fifth generation (5G) mobile communication system is studied, and discussions are made to support new processes and new functions (see non-patent documents 1 to 3). In Release 17 of the 5G standard, a mobile communication system for drones is discussed (see non-patent document 4). Prior art literature Non-patent literature
[0003] Non-patent document 1: 3GPP TS23.501V17.4.0 (2022-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Systemarchitecture for the 5G System (5GS); Stage 2 (Release 17) Non-patent document 2: 3GPP TS23.502V17.4.0 (2022-03); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17) Non-patent document 3: 3GPP TS24.501V17.6.1 (2022-03); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17) Non-patent document 4: 3GPP TS23.256V17.2.0 (2022-03); 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) Summary of the invention Problem that the invention aims to solve
[0004] In 5GS (5G System), 5GCN (5G Core Network) is being studied as a new core network to provide various services. In addition, a communication method using 5GS is also being studied as a communication method for operating UAV (Unmanned Aerial Vehicle).
[0005] Currently, in the communication method of UAV using 5GS, attempts are made to regulate direct communication (called direct C2 communication) between UAV and UAV controller (UAV controller) together with communication using 5GS.
[0006] On the other hand, regarding direct C2 communication, the method of establishing the communication path, the method of authentication and / or authorization are not yet clear. Moreover, the behavior when the authentication and / or authorization for direct C2 communication is cancelled is also unclear. In addition, the process for releasing the communication path for direct C2 communication and under what circumstances the communication path is released are not clear.
[0007] One solution of the present invention is completed in consideration of the above situation, and its purpose is to indicate and clarify the behavior of the UAV when the UAV receives the cancellation of the authentication and / or authorization of direct C2 communication from the network. In addition, the process of releasing direct C2 communication and the time to start the process are also clarified. Technical Solution
[0008] A user equipment (UE) according to one embodiment of the present invention is characterized in that the UE includes a transceiver and a control unit, wherein the UE establishes a communication path for a first direct C2 communication with a UAV-C, the transceiver receives a PDU session change command message including first identification information from a network, wherein the first identification information is information indicating cancellation of authentication and / or authorization of the communication path for the first direct C2 communication, and the control unit recognizes that authentication and / or authorization of the communication path for the first direct C2 communication is canceled based on reception of the PDU session change command message, and starts a process of releasing the communication path for the first direct C2 communication. Beneficial Effects
[0009] According to one aspect of the present invention, it is possible to clarify the behavior of the UAV when the authentication and / or authorization of the direct C2 communication is revoked, the process of releasing the direct C2 communication, and the time to start the process. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 This is a diagram illustrating the outline of a mobile communication system (EPS / 5GS). Figure 2 This is a diagram illustrating the detailed structure of the mobile communication system (EPS / 5GS). Figure 3 This is a diagram illustrating the device structure of UE. Figure 4 This is a diagram illustrating the structure of the access network device (gNB) in 5GS. Figure 5 This is a diagram that illustrates the structure of the core network device (AMF / SMF / UPF) in 5GS. Figure 6 This is a diagram for explaining the login process. Figure 7 It is a diagram illustrating the PDU session establishment process. Figure 8 is a diagram representing the network-led session management process. Fig. 9 It is a diagram showing the UE-led session management process. Fig.10 is a diagram illustrating a process for establishing direct C2 communication. Fig.11 It is a diagram for explaining the process for releasing direct C2 communication. Fig.12 This is a diagram illustrating the UUAA-MM process. Fig.13 This is a diagram illustrating the UUAA-SM process. Fig.14 This is a diagram illustrating the UUAA cancellation process. DETAILED DESCRIPTION
[0011] Hereinafter, the best mode for implementing one aspect of the present invention will be described with reference to the drawings. It should be noted that in this embodiment, an embodiment of a mobile communication system in which one aspect of the present invention is applied will be described as an example. [1. System Overview]
[0012] first, Figure 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment. Figure 2 It is a diagram for explaining the detailed structure of the mobile communication system 1.
[0013] exist Figure 1 It is recorded that the mobile communication system 1 is composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network: packet data network)_A5, access network_B120, core network_B190, and DN (Data Network: data network)_A6.
[0014] In the following, these devices / functions may be recorded with omitted symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.
[0015] In addition, Figure 2 The following devices / functions are recorded: UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170 and other devices / functions as well as interfaces connecting these devices / functions to each other.
[0016] In the following, for these devices / functions, symbols are sometimes omitted, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.
[0017] It should be noted that the EPS (Evolved Packet System) as a 4G system is composed of an access network_A and a core network_A, but may further include UE and / or PDN. In addition, the 5GS (5G System) as a 5G system is composed of a UE, an access network_B and a core network_B, but may further include a DN.
[0018] UE is a device that can connect to network services via 3GPP access (also known as 3GPP access network, 3GPP AN) and / or non-3GPP access (non-3GPP access, also known as non-3GPP access network, non-3GPP AN). UE can be a terminal device that can perform wireless communication, such as a portable phone or a smart phone, or a terminal device that can connect to EPS or 5GS. UE can have UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). It should be noted that UE can be expressed as a user device or as a terminal device.
[0019] In addition, access network_A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are configured in E-UTRAN. It should be noted that, in the following, eNB45 is sometimes recorded by omitting the symbol like eNB. In addition, when there are multiple eNBs, each eNB is connected to each other, for example, via an X2 interface. In addition, one or more access points are configured in the wireless LAN access network.
[0020] In addition, access network_B corresponds to the 5G access network (5G AN). 5G AN is composed of NG-RAN (NG Radio Access Network: NG wireless access network) and / or non-3GPP access network. One or more gNB (NRNodeB: NR Node B) 122 are configured in NG-RAN. It should be noted that, in the following, the symbol gNB122 is sometimes omitted like gNB. gNB is a node that provides NR (New Radio: New Radio) user plane and control plane to UE, and is a node connected to 5GCN via an NG interface (including N2 interface or N3 interface). That is, gNB is a base station device redesigned for 5GS, and has different functions from the base station device (eNB) used in EPS as a 4G system. In addition, when there are multiple gNBs, each gNB is connected to each other, for example, via an Xn interface.
[0021] In addition, the non-3GPP access network can be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network can be a non-3GPP access network such as a public wireless LAN that does not perform security management within the access network. On the other hand, the trusted non-3GPP access network can be an access network specified by 3GPP and can have TNAP (trusted non-3GPP access point) and TNGF (trusted non-3GPP Gateway function).
[0022] In addition, below, E-UTRAN and NG-RAN are sometimes referred to as 3GPP access. In addition, wireless LAN access network and non-3GPP AN are sometimes referred to as non-3GPP access. In addition, nodes configured in access network_B are sometimes collectively referred to as NG-RAN nodes.
[0023] In addition, in the following, access network_A and / or access network_B and / or the device included in access network_A and / or the device included in access network_B are sometimes referred to as access networks or access network devices.
[0024] In addition, the core network_A corresponds to EPC (Evolved Packet Core). In EPC, for example, MME (Mobility Management Entity), SGW (Serving Gateway), PGW (Packet Data Network Gateway)-U, PGW-C, PCRF (Policy and Charging Rules Function), HSS (Home Subscriber Server), etc. are configured.
[0025] In addition, core network_B corresponds to 5GCN (5G Core Network). In 5GCN, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), UDM (Unified Data Management), etc. are configured. Here, 5GCN can be expressed as 5GC.
[0026] In addition, below, core network_A and / or core network_B, devices included in core network_A and / or devices included in core network_B are sometimes referred to as core networks or core network devices or devices within the core network.
[0027] The core network (core network_A and / or core network_B) can be an IP mobile communication network operated by a mobile communication operator (Mobile Network Operator; MNO) that connects the access network (access network_A and / or access network_B) with the PDN and / or DN, or it can be a core network used by a mobile communication operator that operates and manages the mobile communication system 1, or it can be a core network used by virtual mobile communication operators and virtual mobile communication service providers such as MVNO (Mobile Virtual Network Operator) and MVNE (Mobile Virtual Network Enabler).
[0028] In addition, Figure 1The case where PDN and DN are the same is recorded in the text, but they can also be different. PDN can be a DN (Data Network) that provides communication services to UE. It should be noted that DN can be constructed as a packet data service network or for each service. Moreover, PDN can include connected communication terminals. Therefore, connection with PDN can be connection with communication terminals and server devices configured in PDN. Moreover, sending and receiving user data with PDN can also be sending and receiving user data with communication terminals and server devices configured in PDN. It should be noted that PDN can be expressed as DN, and DN can also be expressed as PDN.
[0029] In addition, hereinafter, at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN and / or one or more devices included therein are sometimes referred to as a network or a network device. That is, the network and / or network device sending and receiving messages and / or executing a process means that at least a part of access network_A, core network_A, PDN, access network_B, core network_B, DN and / or one or more devices included therein send and receive messages and / or execute a process.
[0030] In addition, the UE can be connected to the access network. In addition, the UE can be connected to the core network via the access network. Moreover, the UE can be connected to the PDN or DN via the access network and the core network. That is, the UE can send and receive (communicate) user data between the PDN or DN. When sending and receiving user data, not only IP (Internet Protocol) communication can be used, but also non-IP communication can be used.
[0031] Here, IP communication refers to data communication using IP, in which data is sent and received through IP packets. An IP packet consists of an IP header and a payload portion. The payload portion may include data sent and received by devices / functions included in EPS and devices / functions included in 5GS. In addition, non-IP communication refers to data communication that does not use IP, in which data is sent and received in a form different from the structure of IP packets. For example, non-IP communication may be data communication achieved by sending and receiving application data that is not assigned an IP header, or may be assigned other headers such as a MAC header, Ethernet (registered trademark) frame header, etc. to send and receive user data sent and received by the UE.
[0032] In addition, the access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may have configurations not recorded in Figure 2For example, an AUSF (Authentication Server Function) and an AAA (Authentication, authorization, and accounting) server (AAA-S) may be included in the core network_A and / or the core network_B.
[0033] Here, AUSF is a core network device having an authentication function for 3GPP access and non-3GPP access, and more specifically, is a network function unit that receives a request for authentication for 3GPP access and / or non-3GPP access from a UE and executes an authentication process.
[0034] In addition, the AAA server is a device that is directly connected to the AUSF or indirectly connected via other network devices and has authentication, authorization and billing functions. The AAA server can be a network device within the core network. It should be noted that the AAA server can be included in the PLMN but not included in the core network_A and / or core network_B. That is, the AAA server can be either a core network device or a device outside the core network. For example, the AAA server can be a server device within the PLMN managed by a third party (3rd Party).
[0035] It should be noted that in Figure 2 In the figure, for the sake of simplicity, each device / function is described as one, but multiple similar devices / functions may be configured in the mobile communication system 1. Specifically, multiple devices / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160 and / or UDM150 may be configured in the mobile communication system 1.
[0036] UPF_A235 is connected to DN, SMF, other UPFs, and access network. UPF_A235 can play the following roles: anchor for intra-RAT mobility or inter-RAT mobility, packet routing and forwarding, UL CL (Uplink Classifier) function to support routing of multiple service flows for one DN, branching point function to support multi-homed PDU session, QoS processing for user plane, verification of uplink service, buffering of downlink packets, triggering function of downlink data notification, etc. In addition, UPF_A235 can be a relay device that acts as a gateway between DN and core network_B190 to transmit user data. It should be noted that UPF_A235 can be a gateway for IP communication and / or non-IP communication. Moreover, UPF_A235 can have the function of transmitting IP communication and the function of converting non-IP communication and IP communication. Moreover, the configured multiple gateways can be gateways connecting the core network_B190 and a single DN. It should be noted that UPF_A235 can have connectivity with other NFs and can also be connected to each device via other NFs.
[0037] It should be noted that between UPF_A235 and the access network, there may be UPF_C239 (also called branching point or uplink classifier) as a UPF different from UPF_A235 as a device or NF. In the presence of UPF_C239, the PDU session between the UE and the DN is established via the access network, UPF_C239, and UPF_A235.
[0038] In addition, UPF130 may be the same device as UPF_A235. It should be noted that UPF130 and UPF_A235 may be described by omitting the reference numerals like UPF. [2. Configuration of each device]
[0039] Next, the configuration of each device (UE and / or access network device and / or core network device) used in each embodiment is described using the accompanying drawings. It should be noted that each device can be configured as physical hardware, as logical (virtual) hardware configured on general hardware, or as software. In addition, at least part (including all) of the functions of each device can also be configured as physical hardware, logical hardware, or software.
[0040] It should be noted that each storage unit (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) in each device and each function that appears below is composed of, for example, semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. In addition, each storage unit can not only store the information originally set from the factory stage, but also store various information sent and received between devices / functions other than its own device and its own function (for example, UE and / or access network device and / or core network device and / or PDN and / or DN). In addition, each storage unit can store identification information, control information, flags, parameters, etc. included in the control messages sent and received in various communication processes described later. In addition, each storage unit can also store this information for each UE. In addition, each storage unit can store control messages and user data sent and received between the devices / functions included in 5GS and / or EPS when intercommunication between 5GS and EPS is performed. At this time, not only the data sent and received via the N26 interface can be stored, but also the data not sent and received via the N26 interface can be stored. [2.1. UE device configuration]
[0041] First, use Figure 3 An example of the configuration of a UE (User Equipment) is described. The UE is composed of a control unit_A300, an antenna 310, a transceiver_A320, and a storage unit_A340. The control unit_A300, the transceiver_A320, and the storage unit_A340 are connected via a bus. The transceiver_A320 is connected to the antenna 310.
[0042] The control unit_A300 is a functional unit that controls the overall actions and functions of the UE. The control unit_A300 reads and executes various programs stored in the storage unit_A340 as needed, thereby realizing various processes in the UE.
[0043] The transceiver_A320 is a functional unit for wirelessly communicating with a base station device (eNB or gNB) in the access network via an antenna. That is, the UE can use the transceiver_A320 to send and receive user data and / or control information between the access network device and / or the core network device and / or the PDN and / or the DN.
[0044] Reference Figure 2 To explain in detail, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver_A320. In addition, the UE can communicate with the base station device (gNB) in the 5G AN by using the transceiver_A320. In addition, the UE can send and receive NAS (Non-Access-Stratum: non-access layer) messages with the AMF via the N1 interface by using the transceiver_A320. However, since the N1 interface is a logical interface, the communication between the UE and the AMF is actually carried out via the 5G AN.
[0045] The storage unit_A340 is a functional unit for storing programs, user data, control information, etc. required for various actions of the UE. [2.2.gNB device configuration]
[0046] Next, use Figure 4 The following describes an example of the gNB device configuration. The gNB is composed of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, the network connection unit_B520, the transceiver unit_B530, and the storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.
[0047] The control unit_B500 is a functional unit that controls the overall actions and functions of the gNB. The control unit_B500 reads and executes various programs stored in the storage unit_B540 as needed, thereby realizing various processes in the gNB.
[0048] The network connection unit_B520 is a functional unit for gNB to communicate with AMF and / or UPF. That is, the gNB can use the network connection unit_B520 to send and receive user data and / or control information between the AMF and / or UPF.
[0049] The transceiver_B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can use the transceiver_B530 to send and receive user data and / or control information between the UE.
[0050] Reference Figure 2To explain in detail, the gNB in the 5G AN can communicate with the AMF via the N2 interface by using the network connection unit_B520, and can communicate with the UPF via the N3 interface. In addition, the gNB can communicate with the UE by using the transceiver unit_B530.
[0051] Storage unit_B540 is a functional unit used to store programs, user data, control information, etc. required for various actions of gNB. [2.3.AMF device configuration]
[0052] Next, use Figure 5 The following describes an example of the device configuration of AMF. AMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. AMF can be a node that operates a control plane.
[0053] The control unit_B700 is a functional unit that controls the overall operation and functions of the AMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the AMF.
[0054] The network connection unit_B720 is a functional unit for connecting the AMF with the base station device (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF in the 5G AN. That is, the AMF can use the network connection unit_B720 to send and receive user data and / or control information between the base station device (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF in the 5G AN.
[0055] Reference Figure 2 To explain in detail, the AMF in 5GCN can communicate with gNB via the N2 interface, can communicate with UDM via the N8 interface, can communicate with SMF via the N11 interface, and can communicate with PCF via the N15 interface by using the network connection unit_A620. In addition, the AMF can send and receive NAS messages with the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is a logical interface, the communication between the UE and the AMF is actually carried out via the 5G AN. In addition, when the N26 interface is supported, the AMF can communicate with the MME via the N26 interface by using the network connection unit_A620.
[0056] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of AMF.
[0057] It should be noted that AMF has the following functions: the function of exchanging control messages with RAN using N2 interface, the function of exchanging NAS messages with UE using N1 interface, the function of encrypting and integrity protecting NAS messages, the registration management (RM) function, the connection management (CM) function, the reachability management function, the mobility management (Mobility management) function of UE, etc., the function of transmitting SM (Session Management) messages between UE and SMF, the access authentication (Access Authentication, Access Authorization) function, the security anchor function (SEA; Security Anchor Functionality), the security context management (SCM; Security Context Management) function, the function of supporting the N2 interface for N3IWF (Non-3GPP Interworking Function: non-3GPP interworking function), the function of supporting the sending and receiving of NAS signals with UE via N3IWF, the function of authenticating UE connected via N3IWF, etc.
[0058] In addition, the RM state of each UE is managed in the login management. The RM state can be synchronized between the UE and the AMF. As the RM state, there are a non-logged-in state (RM-DEREGISTERED state) and a logged-in state (RM-REGISTERED state). In the RM-DEREGISTERED state, since the UE has not logged in to the network, the UE context in the AMF does not have valid location information and routing information for the UE, so the AMF is in a state where the UE cannot be reached. In addition, in the RM-REGISTERED state, the UE has logged in to the network, so the UE can receive services that require login to the network. It should be noted that the RM state can be expressed as a 5GMM state (5GMM state). In this case, the RM-DEREGISTERED state can be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state can be expressed as a 5GMM-REGISTERED state.
[0059] In other words, 5GMM-REGISTERED can be a state where each device has established a 5GMM context, or a state where each device has established a PDU session context. It should be noted that when each device is 5GMM-REGISTERED, UE_A10 can start sending and receiving user data and control messages, and can also respond to paging. Moreover, it should be noted that when each device is 5GMM-REGISTERED, UE_A10 can perform login procedures and / or service request procedures other than the login procedure for initial login.
[0060] Moreover, 5GMM-DEREGISTERED can be a state where each device has not established a 5GMM context, a state where the location information of UE_A10 is not grasped by the network, or a state where the network cannot reach UE_A10. It should be noted that when each device is 5GMM-DEREGISTERED, UE_A10 can start the login process or establish a 5GMM context by executing the login process.
[0061] In addition, the CM state of each UE is managed in the connection management. The CM state can be synchronized between the UE and the AMF. As CM states, there are a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state, but does not have a NAS signaling connection (NAS signaling connection) established with the AMF via the N1 interface. In addition, in the CM-IDLE state, the UE does not have a connection (N2connection) of the N2 interface and a connection (N3connection) of the N3 interface. On the other hand, in the CM-CONNECTED state, it has a NAS signaling connection (NAS signaling connection) established with the AMF via the N1 interface. In addition, in the CM-CONNECTED state, the UE may also have a connection (N2connection) of the N2 interface and / or a connection (N3connection) of the N3 interface.
[0062] Moreover, in connection management, it can also be divided into CM state in 3GPP access and CM state in non-3GPP access for management. In this case, as the CM state in 3GPP access, there can be a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over3GPP access). Moreover, as the CM state in non-3GPP access, there can be a non-connected state in non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state in non-3GPP access (CM-CONNECTEDstate over non-3GPP access). It should be noted that the non-connected state can be expressed as an idle mode, and the connected state mode can be expressed as a connected mode.
[0063] It should be noted that the CM state can also be expressed as 5GMM mode. In this case, the non-connected state can also be expressed as 5GMM non-connected mode (5GMM-IDLE mode), and the connected state can also be expressed as 5GMM connected mode (5GMM-CONNECTED mode). Moreover, the non-connected state in 3GPP access can also be expressed as 5GMM non-connected mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access can also be expressed as 5GMM connected mode in 3GPP access (5GMM-CONNECTED mode over 3GPP access). Moreover, the non-connected state in non-3GPP access can also be expressed as 5GMM non-connected mode in non-3GPP access (5GMM-IDLE modeover non-3GPP access), and the connected state in non-3GPP access can also be expressed as 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). It should be noted that the 5GMM non-connected mode can be expressed as an idle mode, and the 5GMM connected mode can be expressed as a connected mode.
[0064] In addition, more than one AMF can be configured in the core network_B. In addition, AMF can be an NF (Network Function) that manages more than one NSI (Network Slice Instance). In addition, AMF can also be a shared CP function (CCNF; Common CPNF (Control Plane Network Function)) shared among multiple NSIs.
[0065] It should be noted that N3IWF is a device and / or function configured between non-3GPP access and 5GCN when the UE is connected to 5GS via non-3GPP access. [2.4.SMF device configuration]
[0066] Next, use Figure 5 An example of the device configuration of SMF is described. SMF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. SMF can be a node that operates a control plane.
[0067] The control unit_B700 is a functional unit that controls the entire operation and function of the SMF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the SMF.
[0068] The network connection unit_B720 is a functional unit for connecting the SMF with the AMF and / or UPF and / or PCF and / or UDM. That is, the SMF can use the network connection unit_B720 to send and receive user data and / or control information between the AMF and / or UPF and / or PCF and / or UDM.
[0069] Reference Figure 2 To explain in detail, the SMF in 5GCN can communicate with AMF via the N11 interface, communicate with UPF via the N4 interface, communicate with PCF via the N7 interface, and communicate with UDM via the N10 interface by using the network connection unit _A620.
[0070] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of SMF.
[0071] SMF has the following functions: session management functions such as establishment, modification, and release of PDU sessions, IP address allocation and management functions for UE, UPF selection and control functions, UPF setting functions for routing services to the appropriate destination (sending destination), functions for sending and receiving the SM part of NAS messages, functions for notifying that downlink data has arrived (Downlink Data Notification), functions for providing AN-specific (each AN's) SM information sent to AN via AMF and through the N2 interface, functions for determining the SSC mode (Session and Service Continuity mode) for the session, roaming functions, etc. [2.5. UPF device configuration]
[0072] Next, use Figure 5 The following describes an example of the device configuration of the UPF. The UPF is composed of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, the network connection unit_B720, and the storage unit_B740 are connected via a bus. The UPF may be a node that operates the control plane.
[0073] The control unit_B700 is a functional unit that controls the overall operation and functions of the UPF. The control unit_B700 reads and executes various programs stored in the storage unit_B740 as needed, thereby realizing various processes in the UPF.
[0074] The network connection unit_B720 is a functional unit for connecting the UPF to the base station device (gNB) and / or SMF and / or DN in the 5G AN. That is, the UPF can use the network connection unit_B720 to send and receive user data and / or control information between the base station device (gNB) and / or SMF and / or DN in the 5G AN.
[0075] Reference Figure 2 To explain in detail, the UPF in 5GCN can communicate with gNB via the N3 interface, communicate with SMF via the N4 interface, communicate with DN via the N6 interface, and communicate with other UPFs via the N9 interface by using the network connection unit _A620.
[0076] Storage unit_B740 is a functional unit for storing programs, user data, control information, etc. required for various actions of UPF.
[0077] UPF has the following functions: serving as an anchor point for intra-RAT mobility or inter-RAT mobility, serving as an external PDU session point for interconnecting with DN (that is, serving as a gateway between DN and core network_B to transmit user data), routing and transmission of packets, UL CL (Uplink Classifier) function that supports routing of multiple service flows for one DN, branching point function that supports multi-homed PDU sessions, QoS (Quality of Service) processing function for user plane, verification function of uplink services, triggering buffering of downlink packets, downlink data notification function, etc.
[0078] In addition, UPF can be a gateway for IP communication and / or non-IP communication. In addition, UPF can have the function of transmitting IP communication and can also have the function of converting non-IP communication and IP communication. Moreover, the configured multiple gateways can be gateways connecting the core network_B with a single DN. It should be noted that UPF can have connectivity with other NFs and can also be connected to each device via other NFs.
[0079] It should be noted that the user plane is user data sent and received between the UE and the network. The user plane can use a PDN connection or a PDU session for transmission and reception. Moreover, in the case of EPS, the user plane can also use the LTE-Uu interface and / or the S1-U interface and / or the S5 interface and / or the S8 interface and / or the SGi interface for transmission and reception. Moreover, in the case of 5GS, the user plane can also be transmitted and received via the interface between the UE and the NG RAN and / or the N3 interface and / or the N9 interface and / or the N6 interface. In the following, the user plane can also be expressed as U-Plane.
[0080] Moreover, the control plane is a control message sent and received for communication control of UE, etc. The control plane can use the NAS (Non-Access-Stratum) signaling connection between UE and MME for transmission and reception. Moreover, in the case of EPS, the control plane can also use the LTE-Uu interface and the S1-MME interface for transmission and reception. Moreover, in the case of 5GS, the control plane can also use the interface between UE and NG RAN and the N2 interface for transmission and reception. In the following, the control plane can be expressed as Control Plane or C-Plane.
[0081] Furthermore, the user plane (U-Plane, User Plane; UP) may be a communication path for sending and receiving user data, and may be composed of multiple bearers. Furthermore, the control plane (C-Plane, Control Plane; CP) may be a communication path for sending and receiving control messages, and may be composed of multiple bearers. [2.6. Description of other devices and / or functions]
[0082] Next, other devices and / or functions are described.
[0083] PCF has the function of providing policy rules, etc.
[0084] In addition, UDM has the following functions: authentication credential processing function, user identification processing function, access authentication function, login / mobility management function, subscriber information management (subscription management) function, etc.
[0085] In addition, the PCRF is connected to the PGW and / or PDN, and has the function of performing QoS management for data distribution, etc. For example, the PCRF manages the QoS of the communication path between the UE_A10 and the PDN. Moreover, the PCRF may be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used by each device when sending and receiving user data.
[0086] In addition, the HSS is connected to the MME and / or the SCEF, and has a function of managing subscriber information, etc. The subscriber information of the HSS is referenced, for example, when the MME performs access control. Furthermore, the HSS may be connected to a location management device different from the MME. [3. Description of terms, identification information, and processes used in each embodiment]
[0087] Next, at least one term, identification information, and process used in each embodiment will be described in advance. [3.1. Description of terms and identification information used in each embodiment]
[0088] First, highly specialized terms used in each embodiment and identification information used in the process will be described in advance.
[0089] The network refers to at least a part of the access network_B, the core network_B, and the DN. In addition, one or more devices included in at least a part of the access network_B, the core network_B, and the DN may also be referred to as a network or a network device. That is, the network executing the sending, receiving, and / or processing of messages may mean that a device (network device and / or control device) in the network executes the sending, receiving, and / or processing of messages. Conversely, the device in the network executing the sending, receiving, and / or processing of messages may mean that the network executes the sending, receiving, and / or processing of messages.
[0090] The SM (session management) message (also called NAS (Non-Access-Stratum) SM message) may be a NAS message used in the process of SM use, or may be a control message sent and received between UE_A10 and SMF_A230 via AMF_A240. In addition, the SM message may include: a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session change request message, a PDU session change command message, a PDU session change complete message, a PDU session change command reject message, a PDU session change reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, and the like. In addition, the SM process or SM process may include: PDU session establishment procedure (PDU session establishment procedure), PDU session modification procedure (PDU session modification procedure), PDU session release procedure (UE-requested PDUsession release procedure: UE-requested PDU session release procedure). It should be noted that each process can be a process initiated by the UE or a process initiated by the NW.
[0091] MM (Mobility management) message (or also called NAS MM message) can be a NAS message used for MM procedures, or it can be a control message sent and received between UE_A10 and AMF_A240. In addition, the MM message may include: Registration request message, Registration accept message, Registration reject message, De-registration request message, De-registration accept message, Configuration update command message, Configuration update complete message, Service request message, Service accept message, Service reject message, Notification message, Notification response message, etc. In addition, with regard to the procedures used for MM or MM procedures, it may include: registration procedure, deregistration procedure, generic UE configuration update procedure, authentication and / or authorization procedure, service request procedure, paging procedure, and notification procedure.
[0092] 5GS (5G System) service may be a connection service provided using the core network B190. Moreover, 5GS service may be a service different from EPS service or the same as EPS service.
[0093] Non-5GS services may be services other than 5GS services, and may also include EPS services and / or non-EPS services.
[0094] The PDN (Packet Data Network) type indicates the type of PDN connection, which includes IPv4, IPv6, IPv4v6, and non-IP. When IPv4 is specified, it indicates that IPv4 is used to send and receive data. When IPv6 is specified, it indicates that IPv6 is used to send and receive data. When IPv4v6 is specified, it indicates that IPv4 or IPv6 is used to send and receive data. When non-IP is specified, it indicates that communication is not using IP, but communication is carried out through a communication method other than IP.
[0095] A PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between a DN and a UE that provide a PDU connectivity service, but it can also be a connectivity established between a UE and an external gateway. The UE establishes a PDU session in 5GS via the access network_B and the core network_B, thereby being able to use the PDU session to send and receive user data with the DN. Here, the external gateway may refer to UPF, SCEF, etc. The UE can use the PDU session to send and receive user data with devices such as application servers configured in the DN. It should be noted that each device (UE and / or access network device and / or core network device) can also establish a correspondence between one or more identification information and the PDU session for management. It should be noted that these identification information may include one or more of DNN, QoS rules, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode (SSC mode), and may further include other information. Moreover, in the case of establishing multiple PDU sessions, each identification information corresponding to the PDU session establishment may be the same content or different content.
[0096] DNN (Data Network Name) can be identification information for identifying a core network and / or an external network such as a DN. Furthermore, DNN can also be used as information for selecting a gateway such as a PGW / UPF to which the core network B190 is connected. Furthermore, DNN can also be equivalent to APN (Access Point Name).
[0097] The PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, including IPv4, IPv6, Ethernet, and Unstructured. When IPv4 is specified, it means that IPv4 is used to send and receive data. When IPv6 is specified, it means that IPv6 is used to send and receive data. When Ethernet is specified, it means that Ethernet frames are sent and received. In addition, Ethernet can indicate that communication without using IP is performed. When Unstructured is specified, it means that Point-to-Point (P2P) tunnel technology is used to send and receive data to an application server in the DN. As a P2P tunnel technology, for example, UDP / IP encapsulation technology can also be used. It should be noted that in addition to the above, IP can also be included in the PDU session type. IP can be specified when the UE can use both IPv4 and IPv6.
[0098] PLMN (Public land mobile network) is a communication network that provides mobile wireless communication services. PLMN is a network managed by an operator as a communication operator, and the operator can be identified by the PLMN ID. The PLMN that is consistent with the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscriber Identity) can be a home PLMN (Home PLMN: HPLMN). Moreover, the UE can maintain an equivalent HPLMN list (Equivalent HPLMN list) for identifying one or more EHPLMNs (Equivalent HPLMN) in the USIM (Universal Subscriber Identity Module). A PLMN different from the HPLMN and / or EPLMN can be a VPLMN (Visited PLMN). The PLMN to which the UE has successfully logged in can be an RPLMN (Registered PLMN).
[0099] The tracking area is one or more ranges that can be represented as the location information of UE_A10 managed by the core network. It should be noted that the tracking area can be composed of multiple cells. Moreover, the tracking area can be either a range for broadcasting control messages such as paging, or a range where UE_A10 can move without performing a switching process. Moreover, the tracking area can be either a routing area or a positioning area, as long as it is the same area as these areas. Hereinafter, the tracking area may also be referred to as TA (Tracking Area). The tracking area can be identified by TAI (Tracking Area Identity) composed of TAC (Tracking area code) and PLMN.
[0100] The registration area (Registration area or login area) is a set of one or more TAs assigned to the UE by the AMF. It should be noted that it is better for UE_A10 to move without sending or receiving signals for tracking area update while moving within one or more TAs included in the registration area. In other words, the registration area can be an information group indicating the area where UE_A10 can move without performing the tracking area update process. The registration area can be identified by a TAI list (TAIlist) composed of one or more TAIs.
[0101] UE ID refers to information used to identify UE. For example, UE ID can be SUCI (SUbscription Concealed Identifier), or SUPI (Subscription Permanent Identifier), or GUTI (Globally Unique Temporary Identifier), or IMEI (International Mobile Subscriber Identity), or IMEISV (IMEI Software Version), or TMSI (Temporary Mobile Subscriber Identity). Alternatively, UE ID can also be other information configured in an application or network. Moreover, UE ID can also be information used to identify a user.
[0102] An always-on PDU session refers to a PDU session in which user plane resources must be activated whenever the UE transitions from the 5GMM-IDLE state to the 5GMM-CONNECTED state. The UE can request the core network and / or the core network device to establish a PDU session as an always-on PDU session based on instructions from the upper layer. The core network and / or the core network device determines whether the PDU session can be established as an always-on PDU session. Here, the establishment of an always-on PDU session may mean the establishment of a PDU session for C2 communication. Moreover, the establishment of an always-on PDU session may also mean the establishment of a PDU session for processing QoS flows for C2 communication. Here, the 5GMM-IDLE state may be the CM-IDLE state. Moreover, the 5GMM-CONNECTED state may be the CM-CONNECTED state. Moreover, the core network device that determines whether the PDU session can be established as an always-on PDU session may be the SMF.
[0103] The service-level-AA container information element (Service-level-AA container IE (Information Element)) is an information element used to transmit information used for authentication and authorization between the UE and the network to the upper layer. In addition, the service-level-AA container information element may include a service-level element ID and / or a service-level-AA server address and / or a service-level-AA payload and / or a service-level-AA response. Moreover, the service-level-AA container information element may include a C2 authorization result and / or a C2 session security information and / or identification information of a paired UAV-C and / or flight authorization information. Moreover, the service-level-AA container information element may include a service-level-AA pending indication. It should be noted that the service-level-AA container information element may also be referred to as a service-level-AA container.
[0104] The service-level device ID is an information element used to transmit the identification required for authentication and authorization implemented by the external DN. In addition, the service-level device ID can be included in the service-level AA container information element. In addition, the service-level device ID can also include a CAA-level UAV ID.
[0105] The service-level-AA server address is an information element used to transmit the address of the service-level authentication and authorization server. In addition, the service-level-AA server address may be included in the service-level-AA container information element. In addition, the service-level-AA server address may also include a USS address.
[0106] The Service-level-AA payload is an information element used to transmit the payload for authentication and authorization between the UE and the Service-level-AA server to the upper layer. In addition, the Service-level-AA payload may be included in the Service-level-AA container information element. In addition, the Service-level-AA payload may also include a UUAA aviation payload.
[0107] A Service-level-AA response is an information element that provides information related to a service-level authentication and authorization request. Specifically, a Service-level-AA response is an information element that indicates whether the authentication and authorization request to the service-level authentication server was successful or unsuccessful. In addition, a Service-level-AA response may be included in a Service-level-AA container information element.
[0108] UAV (Uncrewed Aerial Vehicle) refers to a flying drone. In addition, UAV can also be a UE. In addition, UAV can also be a 3GPP UE that supports UE functions.
[0109] In addition, the UAV can be managed by the USS. The UAV can establish a correspondence with the UAV controller. Moreover, the UAV can be managed by the core network device and / or UTM in correspondence with the UAV controller. Moreover, when the UAV is managed in correspondence with the UAV controller, it can be managed as a UAS by the core network device and / or UTM. The UAV can manage its own information (identification information, IP address, location information, etc.) by the core network device and / or UTM. In addition, the UE can be replaced by the UAV.
[0110] In addition, a UAV capable of utilizing UAS services may be a UAV capable of utilizing C2 communications and / or direct C2 communications. In addition, a UAV capable of utilizing C2 communications and / or direct C2 communications may be a UAV capable of utilizing UAS services.
[0111] The UAV controller (Uncrewed Aerial Vehicle controller) is a controller for operating the UAV. In addition, the UAV controller can also be a UE. In addition, the UAV controller can also be a 3GPP UE that supports UE functions.
[0112] The UAV controller can establish a correspondence with the UAV. Moreover, the UAV controller can establish a correspondence with the UAV and be managed by the core network device and / or UTM. Moreover, when the UAV controller is managed in correspondence with the UAV, it can be managed as a UAS by the core network device and / or UTM. The UAV controller can have its own information (identification information, IP address, location information, etc.) managed by the core network device and / or UTM. It should be noted that the UAV controller can be expressed as a UAC or as a UAV-C. In addition, the UE can also be replaced by a UAV-C.
[0113] Furthermore, a UAV-C capable of utilizing UAS services may be a UAV-C capable of utilizing C2 communication and / or direct C2 communication. Furthermore, a UAV-C capable of utilizing C2 communication and / or direct C2 communication may be a UAV-C capable of utilizing UAS services.
[0114] UAS (Uncrewed Aerial System) can be composed of UAV and associated functions. Here, the associated functions may include a C2 (command and control) link. Moreover, the C2 link can be a link between the UAV and the control station, or a link between the UAV and the network. Moreover, the C2 link can be a link for remote identification. In addition, the UAS can be composed of one or more UAVs and one or more UAV controllers. In addition, the UAS can be managed by a network device and / or a USS.
[0115] USS (Uncrewed Aerial System Service Supplier) is a device that has the function of managing UAV and / or UAV controller and / or UAS. USS can be a device of DN or a device within the core network. In addition, USS can be a device for autonomously manipulating UAV. In addition, USS can have the function of managing identification information, IP address, location information, etc. of UAV and / or UAV controller, and can also have the function of managing information of UAV and / or UAV controller other than the above. Moreover, USS can establish a correspondence between UAV and UAV controller and manage them as UAS. In addition, USS can send information for requesting network services to the core network device. In addition, USS can be a device that provides one or more functions and services for managing the scope of vehicle operation. In addition, USS can be a UAS application server.
[0116] In addition, USS may be a device having the function of UTM. In addition, USS may be a device in UTM. In addition, USS may be a device in UTM. It should be noted that USS may be expressed as USS / UTM or UTM / USS. In addition, USS may also be expressed as a network.
[0117] In addition, the USS can send information to the core network and / or UE via the UAS-NF (Uncrewed Aerial Systems Network Function). In addition, the information sent from the USS can be regarded as the information sent from the UAS-NF. In addition, the information received from the USS can be regarded as the information received from the UAS-NF.
[0118] UTM (Uncrewed Aerial System Traffic Management) may be a device including USS. UTM may be a device equipped with USS. In addition, UTM may be replaced by USS.
[0119] Command and Control (C2) communications may be user plane links used to transmit messages including commands and control information for operating the UAV from a UAV controller or UTM to the UAV.
[0120] In addition, C2 communication can be communication for transmitting messages including commands and control information for operating the UAV from the UAV controller or UTM to the UAV. In addition, C2 communication can also be a link between the UAV controller and the UAV. In addition, C2 communication can be a link between the USS and the UAV. In addition, C2 communication can be communication between the UAV controller and the UAV. In addition, C2 communication can be communication between the USS and the UAV.
[0121] Furthermore, C2 communication may be a link in the user plane for reporting telemetry data from the UAV to the UAV controller or the UTM. Furthermore, C2 communication may be a link in the user plane for transmitting messages including commands for operating the UAV and control information from the UAV controller to the UAV via the UTM. Here, C2 communication may be a link implemented through a PDU session. Furthermore, the PDU session for C2 communication may be implemented through an always-on PDU session. Furthermore, the establishment of a PDU session for C2 communication may mean the establishment of an always-on PDU session. Furthermore, the establishment of a PDU session for processing a QoS flow for C2 communication may mean the establishment of an always-on PDU session. Furthermore, a link may be a communication path or a transmission path. C2 communication may also be referred to as C2.
[0122] In addition, C2 communication can be replaced by a communication path for C2 communication. In addition, a communication path for C2 communication can also be replaced by C2 communication.
[0123] Direct C2 communication may be a link between a UAV and a UAV-C. In addition, direct C2 communication may also be communication between a UAV and a UAV-C.
[0124] Furthermore, direct C2 communication may be a direct link between the UAV and the UAV-C. Furthermore, direct C2 communication may be a direct C2 link between the UAV and the UAV-C. Furthermore, direct C2 communication may be a communication path on the PC5. Direct C2 communication may also be C2 communication.
[0125] Here, the UAV and / or UAV-C may be logged in the network. Furthermore, the link may be a communication path or a transmission path.
[0126] Furthermore, direct C2 communication may be replaced with a communication path for direct C2 communication. Furthermore, a communication path for direct C2 communication may be replaced with direct C2 communication.
[0127] The C2 authorization result may be a result of the C2 communication authorization, and specifically, may be information indicating the failure or success of the C2 communication authorization.
[0128] The result of the authorization of C2 communication can also be configured to include the authorization result of direct C2 communication. In this case, the C2 authorization result can be information indicating the success of the authorization of C2 communication using the PDU session, or the success of the authorization of the direct C2 communication, or the success of the authorization of both parties, or the failure of the authorization. Alternatively, the C2 authorization result indicates the success or failure of the authorization of C2 communication, and the network can notify the UE of the success or failure of the authorization of C2 communication using the PDU session and the direct C2 communication, and the UE can recognize the notification.
[0129] Alternatively, the service level AA container information element may include a direct C2 authorization result, which is an authorization result of direct C2 communication independent of the C2 authorization result. In this case, the direct C2 authorization result may be information indicating success or failure of authorization of direct C2 communication.
[0130] In addition, the C2 authorization result can be replaced by a direct C2 authorization result.
[0131] The direct C2 authorization result may be a result of authorization of the direct C2 communication, and specifically, may be information indicating failure or success of authorization of the direct C2 communication.
[0132] The result of the authorization of direct C2 communication may also be configured to include the authorization result of C2 communication. In this case, the direct C2 authorization result may be information indicating the success of the authorization of C2 communication using the PDU session, or the success of the authorization of the direct C2 communication, or the success of the authorization of both parties, or the failure of the authorization. Alternatively, the direct C2 authorization result indicates the success or failure of the authorization of the direct C2 communication, and the success or failure of the authorization of the direct C2 communication may be notified to the UE, and the UE may recognize the notification.
[0133] Authorization for C2 communication is an authorization and / or process requested to be performed when the UAV and / or UAV-C establishes a user plane connection for C2 operation. Here, the user plane connection for C2 operation can be C2 communication. In other words, authorization for C2 communication needs to be performed for the UAV and / or UAV-C to establish C2 communication.
[0134] In the authorization of C2 communication, the UAV and / or UAV-C may be authorized by the USS for the establishment of a PDN connection and / or a PDU session for C2 and / or the establishment of direct C2 communication. Moreover, the authorization of pairing of the UAV and the UAV-C and / or the flight authorization may be implemented in the authorization of C2 communication. The authorization of pairing of the UAV and the UAV-C and / or the flight authorization may be performed by the USS.
[0135] The authorization of C2 communication may be performed in the UUAA process or by other processes. Specifically, in the case where the UAV wants to split the C2 communication with the USS and the C2 communication with the UAV-C, the authorization of C2 communication may be performed in the process for the UAV to establish a new PDU session and / or PDN connection.
[0136] The case where the UAV wants to split the C2 communication with the USS and the C2 communication with the UAV-C may be, for example, a case where the UAV requests establishment of direct C2 communication.
[0137] In case the UAV and / or UAV-C requests establishment of direct C2 communication, authorization of C2 communication for direct C2 communication may be performed during a login procedure and / or a UUAA-MM procedure.
[0138] In addition, the authorization for C2 communication may also be referred to as authorization for direct C2 communication (Authorization for directC2).
[0139] The authorization of pairing of the UAV with the UAV-C may be the UAV authorization of pairing with the UAV-C and / or the UAV-C authorization of pairing with the UAV, which needs to be performed before the exchange of information between the UAV and the UAV-C implemented by the C2 communication.
[0140] Flight authorization is the authorization of the UAV to fly (flight). Flight authorization also needs to be performed before the UAV flies. Alternatively, flight authorization can be performed only in the case of UAV request, during the authorization process of C2 communication. In other words, by authorizing C2 communication, the pairing of the UAV with the UAV-C and / or the flight of the UAV can be authorized.
[0141] The CAA level UAV ID is information assigned to the UAV by functions in the aviation field such as USS. In addition, the CAA level UAV ID can be used for remote identification and tracking, and can also be used to identify the UAV. In addition, the CAA level UAV ID can be information provided by the UAV to the 3GPP system during the UUAA process.
[0142] In addition, the aviation community can assign new CAA-level UAV IDs to UAVs at any time. In addition, the new CAA-level UAV IDs can be provided to UAVs and 3GPP systems during the UAS association process.
[0143] The CAA level UAV ID may be referred to as identification information of the UAV, or may be referred to as information for identifying the UAV.
[0144] The 3GPP UAV ID is information associated with the UAV by the 3GPP system. In addition, the 3GPP UAV ID may be information used by the 3GPP system to identify the UAV. In addition, the USS may store an association between the CAA level UAV ID and the 3GPP UAV ID.
[0145] The 3GPP UAV ID may be referred to as identification information of the UAV, or may be referred to as information for identifying the UAV.
[0146] The UE may include an initiating UE and a target UE.
[0147] The initial UE may be a UE used in the communication between two UEs. In addition, the initial UE may send a message to the target UE. In addition, the initial UE may be used in the process for establishing direct C2 communication. In addition, the initial UE may be a UAV or a UAV-C.
[0148] The target UE may be a UE used in communication between two UEs. In addition, the target UE may send a message to the initial UE. In addition, the target UE may be used in a process for establishing direct C2 communication. In addition, the target UE may be a UAV or a UAV-C.
[0149] The first identification information may refer to information indicating whether the UE supports direct C2 communication. In addition, the first identification information may also be information indicating that the UE supports direct C2 communication. In addition, the first identification information may also be information indicating that the UE does not support direct C2 communication.
[0150] Furthermore, the first identification information may be information indicating authentication and / or authorization for requesting establishment of direct C2 communication. Furthermore, the first identification information may be information indicating authentication and / or authorization for requesting utilization of direct C2 communication.
[0151] In addition, the first identification information may also be a 5GMM capability. In addition, the first identification information may also be information included in the 5GMM capability.
[0152] The second identification information may refer to information indicating authentication and / or authorization for requesting direct C2 communication and / or establishment of C2 communication using a PDU session. In addition, the second identification information may also be information indicating authentication and / or authorization for requesting direct C2 communication and / or establishment of C2 communication.
[0153] In addition, the second identification information may also be information indicating a request to simultaneously establish direct C2 communication and authentication and / or authorization of C2 communication. In addition, the second identification information may also be information indicating a request to simultaneously utilize direct C2 communication and authentication and / or authorization of C2 communication.
[0154] In addition, the second identification information may also refer to information indicating whether the UE supports direct C2 communication and / or C2 communication. In addition, the second identification information may also refer to information indicating whether the UE supports direct C2 communication and / or C2 communication. In addition, the second identification information may also refer to information indicating that the UE does not support direct C2 communication and / or C2 communication.
[0155] In addition, the second identification information may be a 5GSM capability. In addition, the second identification information may also be information included in the 5GSM capability.
[0156] The first identification information and / or the second identification information may also be information included in a service level AA container.
[0157] Moreover, the first identification information and / or the second identification information may be information selected and determined based on the UE settings and / or the UE status and / or the user policy and / or the application request.
[0158] The third identification information may be source user information. In addition, the third identification information may also be the ID of the application layer of the initiating UE. In addition, the third identification information may also be the ID of the application layer of the UE on the message sending side. In addition, the third identification information may also be information received from an upper layer. In addition, the third identification information may also be source user information in which the ID of the application layer of the initiating UE received from the upper layer is set.
[0159] In addition, the third identification information may be information included in a message used in communication between two UEs.
[0160] The fourth identification information may refer to information for identifying an application of the UAS. In addition, the fourth identification information may also be information for an application for requesting the UAS. In addition, the fourth identification information may also be information for an application for utilizing the UAS. In addition, the fourth identification information may also be information used in an application of the UAS.
[0161] In addition, the fourth identification information may also be a ProSe identifier (ProSe identifier).
[0162] The fifth identification information may refer to target user information (target user info). In addition, the fifth identification information may also be the ID of the application layer of the target UE. In addition, the fifth identification information may also be the ID of the application layer of the UE on the message receiving side. In addition, the fifth identification information may also be information received from an upper layer. In addition, the fifth identification information may also be target user information in which the ID of the application layer of the target UE received from the upper layer is set.
[0163] In addition, the fifth identification information may be information included in a message used in communication between two UEs.
[0164] The sixth identification information refers to a reason value. The sixth identification information may be a reason value indicating a reason for releasing the communication path of the direct C2 communication.
[0165] Here, the reason value may indicate that direct C2 communication with the target UE is not allowed. In addition, the reason value may also indicate that direct C2 communication with the target UE is not required. In addition, the reason value may also indicate that direct C2 communication cannot be used. In addition, the reason value may also indicate insufficient resources for direct C2 communication. In addition, the reason value may also indicate a congestion condition. In addition, the reason value may also indicate a protocol error.
[0166] In addition, the reason value can be (#1direct communication to the target UE not allowed) or (#2direct communication to the target UE no longer needed) or (#4direct connection is not available anymore) or (#5lack of resources for 5G ProSe direct link) or (#13congestion situation) or (#111protocol error, unspecified).
[0167] In addition, the reason value may be selected and determined based on subscriber information and / or network status and / or user login information and / or context maintained by the UE to indicate whether the degree information in the above information is indicated. In addition, the reason value may also be selected and determined based on information indicated by the network and / or USS to indicate whether the degree information in the above information is indicated.
[0168] In addition, the reason value may also be indicated by the network and / or USS.
[0169] The tenth identification information may refer to information indicating whether the network authenticates and / or authorizes direct C2 communication. The tenth identification information may also refer to information indicating whether the network authenticates and / or authorizes direct C2 communication. The tenth identification information may also refer to information indicating that the network does not authenticate and / or authorize direct C2 communication.
[0170] The tenth identification information may be information indicating whether the network allows direct C2 communication. The tenth identification information may be information indicating that the network allows direct C2 communication. In addition, the tenth identification information may also be information indicating that the network does not allow direct C2 communication.
[0171] The eleventh identification information may refer to information indicating authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session. In addition, the eleventh identification information may also be information indicating authentication and / or authorization of direct C2 communication and / or C2 communication. In addition, the eleventh identification information may also be information indicating that authentication and / or authorization is not performed for direct C2 communication and / or C2 communication. In addition, the eleventh identification information may also be information indicating whether authentication and / or authorization is performed for direct C2 communication and / or C2 communication.
[0172] In addition, the eleventh identification information may also be information indicating that direct C2 communication and / or C2 communication is allowed. In addition, the eleventh identification information may also be information indicating that direct C2 communication and / or C2 communication is not allowed. In addition, the eleventh identification information may also be information indicating whether direct C2 communication and / or C2 communication is allowed.
[0173] The tenth identification information and / or the eleventh identification information may also be information included in the service level AA container. The tenth identification information and / or the eleventh identification information may also be a C2 authorization result and / or a service level AA response and / or a direct C2 authorization result included in the service level AA container, or may be information included in the C2 authorization result and / or a service level AA response and / or a direct C2 authorization result.
[0174] In addition, the tenth identification information and / or the eleventh identification information may also be information sent by the USS.
[0175] Moreover, the tenth identification information and / or the eleventh identification information may also be information selected and determined by the network based on the received identification information and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information, etc.
[0176] The twelfth identification information may refer to information for identifying a UAV. In addition, the twelfth identification information may also be information for identifying a UAV-C. In addition, the twelfth identification information may also be information for identifying a UAV that forms a UAV-C pair. In addition, the twelfth identification information may also be information for identifying a UAV-C that forms a UAV pair. In addition, the twelfth identification information may also be information used in direct C2 communication.
[0177] In addition, the twelfth identification information may also be information included in the service level AA container. In addition, the twelfth identification information may also be a service level (Service-level) element ID included in the service level AA container.
[0178] In addition, the twelfth identification information may be a CAA-level UAV ID or a 3GPP UAV ID.
[0179] The thirteenth identification information may refer to source user information. In addition, the thirteenth identification information may also be the ID of the application layer of the target UE. In addition, the thirteenth identification information may also be the ID of the application layer of the UE on the message sending side. In addition, the thirteenth identification information may also be information received from an upper layer. In addition, the thirteenth identification information may also be source user information in which the ID of the application layer of the target UE received from the upper layer is set.
[0180] In addition, the thirteenth identification information may be information included in a message used in communication between two UEs.
[0181] The fourteenth identification information may be information for identifying an application of the UAS. In addition, the fourteenth identification information may also be information for an application for requesting the UAS. In addition, the fourteenth identification information may also be information for an application for utilizing the UAS. In addition, the fourteenth identification information may also be information used in an application of the UAS.
[0182] In addition, the fourteenth identification information may be information for identifying an application of the UAS accepted by the target UE. In addition, the fourteenth identification information may also be information for requesting an application of the UAS accepted by the target UE. In addition, the fourteenth identification information may also be information for utilizing an application of the UAS accepted by the target UE. In addition, the fourteenth identification information may also be information used in an application of the UAS accepted by the target UE.
[0183] In addition, the fourteenth identification information may also be a response to the fifth identification information. In addition, the fourteenth identification information may also be the fifth identification information received by the target UE.
[0184] In addition, the fourteenth identification information may also be a ProSe identifier.
[0185] The fifteenth identification information may be information indicating cancellation of authentication and / or authorization of direct C2 communication. In addition, the fifteenth identification information may be information indicating whether to cancel authentication and / or authorization of direct C2 communication.
[0186] Furthermore, the fifteenth identification information may be information indicating cancellation of permission for direct C2 communication. Furthermore, the fifteenth identification information may be information indicating whether permission for direct C2 communication is cancelled.
[0187] The sixteenth identification information may be information indicating cancellation of authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session. In addition, the sixteenth identification information may also be information indicating whether to cancel authentication and / or authorization of direct C2 communication and / or C2 communication.
[0188] Furthermore, the sixteenth identification information may be information indicating cancellation of permission of direct C2 communication and / or C2 communication. Furthermore, the sixteenth identification information may be information indicating whether to cancel permission of direct C2 communication and / or C2 communication.
[0189] The fifteenth identification information and / or the sixteenth identification information may also be information included in the service level AA container. The fifteenth identification information and / or the sixteenth identification information may also be C2 authorization result and / or service level AA response and / or direct C2 authorization result included in the service level AA container, or may be information included in the C2 authorization result and / or service level AA response and / or direct C2 authorization result.
[0190] In addition, the fifteenth identification information and / or the sixteenth identification information may also be information sent by the USS.
[0191] Moreover, the fifteenth identification information and / or the sixteenth identification information may also be information selected and determined by the network based on the received sixth identification information and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information, etc.
[0192] The seventeenth identification information may refer to a reason value indicating the reason for rejecting the login process or the PDU session establishment process. In addition, the seventeenth identification information may also be a reason value indicating the reason for starting the PDU session change process. In addition, the seventeenth identification information may also be a reason value indicating the reason for starting the PDU session release process. The seventeenth identification information may be a 5GSM (5GS Session Management) reason value.
[0193] The seventeenth identification information may also refer to a reason value indicating the reason for canceling the authentication and / or authorization of the direct C2 communication and / or the C2 communication using the PDU session.
[0194] Furthermore, the seventeenth identification information may be a reason value indicating the reason for canceling permission of direct C2 communication and / or C2 communication.
[0195] The seventeenth identification information may also be information included in the service level AA container. The seventeenth identification information may also be information included in the C2 authorization result and / or the service level AA response and / or the direct C2 authorization result.
[0196] Moreover, the seventeenth identification information may also be information selected and determined by the network based on the received identification information and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information, etc.
[0197] The eighteenth identification information is a timer value. The eighteenth identification information may also be a timer value indicating a grace period until the direct C2 communication and / or the PDU session for C2 communication is released. In addition, the eighteenth identification information may also be a timer value indicating the time for releasing the direct C2 communication and / or the PDU session for C2 communication.
[0198] The eighteenth identification information may be a timer value specifying a start time and / or an end time.
[0199] In addition, the eighteenth identification information may also indicate that when the timer value is zero, the direct C2 communication and / or the PDU session for C2 communication must be released immediately after receiving the eighteenth identification information. In addition, the eighteenth identification information may also indicate that when the timer value is zero, the authentication and / or authorization of the direct C2 communication and / or the C2 communication using the PDU session is cancelled. In addition, the eighteenth identification information may also indicate that when the timer value is zero, the direct C2 communication and / or the C2 communication using the PDU session is not authenticated and / or authorized.
[0200] The eighteenth identification information may also be information included in the service level AA container. The eighteenth identification information may also be information included in the C2 authorization result and / or the service level AA response and / or the direct C2 authorization result.
[0201] Moreover, the eighteenth identification information may also be information selected and determined by the network based on the received identification information and / or information corresponding to the NSI and / or network capability information and / or operator policy and / or network status and / or user login information, etc. [3.2. Description of the process used in each embodiment]
[0202] Next, the procedures used in each embodiment are described. It should be noted that the procedures used in each embodiment include a registration procedure. Each procedure is described below.
[0203] It should be noted that, in each embodiment, Figure 2 As described above, the case where HSS and UDM, PCF and PCRF, SMF and PGW-C, UPF and PGW-U are respectively configured as the same device (that is, the same physical hardware or the same logical hardware or the same software) is used as an example for explanation. However, the content described in this embodiment can also be applied to the case where they are configured as different devices (that is, different physical hardware, or different logical hardware or different software). For example, data can be sent and received directly between them, data can be sent and received via the N26 interface between AMF and MME, and data can be sent and received via UE. [3.2.1. Login process]
[0204] First, use Figure 6 The registration procedure is explained. The registration procedure is a process in 5GS. Hereinafter, this process refers to the registration procedure. The registration procedure is a process for the UE to take the lead in logging into the access network_B and / or core network_B and / or DN. If the UE is not logged in to the network, this procedure can be performed at any time, such as when the power is turned on. In other words, if the UE is in a non-registered state (RM-DEREGISTERED state), this procedure can be started at any time. In addition, each device (especially UE and AMF) can transition to a registered state (RM-REGISTERED state) based on the completion of the registration procedure.
[0205] In addition, the registration process may be an initial registration initiated by the UE. In addition, the registration process may also be a mobility and periodic registration. In addition, the registration process may also be an MM process.
[0206] Moreover, the registration process may be a process for updating the location registration information of the UE in the network and / or periodically notifying the network of the status of the UE from the UE and / or updating specific parameters related to the UE in the network.
[0207] In addition, the login in this process can be a login for C2 communication or a login for direct C2 communication. In addition, the PDU session in this process can be a login for UAS service.
[0208] The UE can start the login process when moving across TAs. In other words, the UE can start the login process when it moves to a TA different from the TA shown in the maintained TA list. Moreover, the UE can also start this process when the executing timer expires. Moreover, the UE can also start the login process when the context of each device needs to be updated due to the disconnection or disabling of the PDU session. Moreover, the UE can also start the login process when the capability information and / or priority selection related to the establishment of the UE's PDU session changes. Moreover, the UE can also start the login process periodically. Moreover, the UE can start the login process based on the completion of the UE setting update process. It should be noted that the UE can perform the login process at any timing, and is not limited to this.
[0209] Moreover, even in the logged-in state, the UE may periodically start the login process. In other words, the UE may start the login process based on the expiration of the timer.
[0210] It should be noted that the login process performed based on the mobility of the UE and the login process performed periodically may also be expressed as a login process for mobility and login update. In other words, the login process for mobility and login update may be a login process performed based on the mobility of the UE or a login process performed periodically. Moreover, the login process for mobility and login update may also be a login process performed based on the setting update of the UE. Moreover, the login process for mobility and login update may also be a login process performed to establish a communication path for sending and receiving user data. Moreover, the login process for mobility and login update may also be a login process performed based on a request from the network. Moreover, in other words, the login process for mobility and login update may be a login process other than the initial login process. Below, the login process for mobility and login update may also be expressed as this process.
[0211] Next, each step of the login process is described. It should be noted that the login process described below can be an initial login process or a login process for mobility and login update.
[0212] First, the UE starts the registration process by sending a registration request message (S800)(S802)(S804) to the AMF. Specifically, the UE sends an RRC message including a registration request message to the 5G AN (or gNB) (S800). It should be noted that the registration request message is a NAS message. In addition, the RRC message can be a control message sent and received between the UE and the 5G AN (or gNB). In addition, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. It should be noted that the NAS layer is a higher layer than the RRC layer.
[0213] Here, the UE may include one or more of the first to second identification information in a login request message and / or an RRC message for transmission. In more detail, the UE may include one or more of the first to second identification information in a login request message and / or an RRC message for transmission, or may include it in a control message of a lower layer (e.g., MAC layer, RLC layer, PDCP layer) of the RRC layer different from these control messages for transmission.
[0214] It should be noted that the UE can indicate that the UE supports each function by sending these identification information, and can also indicate the UE's request. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information can constitute more than one identification information. It should be noted that the information indicating support for each function and the information indicating a request for use of each function can be sent and received as the same identification information, or can be sent and received as different identification information.
[0215] Here, the UE can indicate the content of each identification information to the network by sending a login request message.
[0216] In other words, in the case where the UE supports direct C2 communication and / or the UE requests authentication and / or authorization to establish direct C2 communication from the network and / or the UE requests authentication and / or authorization to utilize direct C2 communication from the network, the UE may include the first identification information in the login request message or send it together with the login request message.
[0217] In other words, in the case where the UE supports direct C2 communication and / or the UE requests authentication and / or authorization for establishment of direct C2 communication and / or C2 communication using PDU sessions from the network and / or the UE requests authentication and / or authorization for utilization of direct C2 communication and / or C2 communication using PDU sessions from the network, the UE may include the second identification information in the login request message or send it together with the login request message.
[0218] Furthermore, the UE may indicate the content indicated by the identification information included in the login request message to the network by including one or more of the first to second identification information in the login request message. Furthermore, the UE may request the network for the content indicated by the identification information included in the login request message by including one or more of the first to second identification information in the login request message.
[0219] It should be noted that the UE can select and determine whether to include one or more of the first to second identification information in the login request message based on the subscriber information and / or the network status and / or the user's login information and / or the context maintained by the UE.
[0220] It should be noted that the UE may also include identification information other than the first to second identification information in the login request message and send it. Specifically, the UE may include a service level AA container in the login request message. Alternatively, the UE may also use the service level AA container in sending the first to second identification information. Specifically, the UE may include one or more identification information from the first to second identification information in the service level AA container, and may also include the service level AA container in the login request message.
[0221] In addition, the UE may start the PDU session establishment process during the login process by including the SM message in the login request message or by sending the SM message together with the login request message. Here, the SM message may also be a PDU session establishment request message.
[0222] When receiving an RRC message including a login request message, the 5G AN (or gNB) selects an AMF to which the login request message is transmitted (S802). It should be noted that the 5G AN (or gNB) can select an AMF based on the information included in the login request message and / or the RRC message. The 5G AN (or gNB) extracts the login request message from the received RRC message and transmits the login request message to the selected AMF (S804).
[0223] The AMF can perform the first condition determination upon receiving the login request message. The first condition determination is used to determine whether the network (or AMF) accepts the UE's request. If the first condition determination is true, the AMF starts Figure 6 In contrast, when the first condition is false, the process starts Figure 6 (B) process.
[0224] It should be noted that the first conditional determination can be performed based on the reception of the login request message and / or the identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF, etc. For example, it can be that when the network allows the UE's request, the first conditional determination is true, and when the network does not allow the UE's request, the first conditional determination is false. In addition, it can also be that when the network of the UE's login destination and / or the device within the network supports the function requested by the UE, the first conditional determination is true, and when the function requested by the UE is not supported, the first conditional determination is false. Moreover, it can also be that when the identification information sent and received is allowed, the first conditional determination is true, and when the identification information sent and received is not allowed, the first conditional determination is false. It should be noted that the conditions for determining the truth or falsehood of the first conditional determination may not be limited to the above conditions.
[0225] First, the case where the first condition is true is explained. Figure 6 The fourth condition determination is first performed in the process (A). The fourth condition determination is used to determine whether the AMF implements the sending and receiving of SM messages between it and the SMF.
[0226] It should be noted that the fourth condition determination can be performed based on whether the AMF receives an SM message. In addition, the fourth condition determination can also be performed based on whether the login request message includes an SM message. For example, it may be that when the AMF receives an SM message and / or the login request message includes an SM message, the fourth condition is determined to be true, and when the AMF does not receive an SM and / or the login request message does not include an SM message, the fourth condition is determined to be false. It should be noted that the conditions for determining the truth or falsity of the fourth condition may not be limited to the above conditions.
[0227] Next, the AMF sends a Registration accept message to the UE via the 5G AN (or gNB) as a response message to the login request message based on the reception of the login request message and / or the completion of the transmission and reception of the SM message between the AMF and the SMF (S808). For example, when the fourth condition is judged to be false, the AMF can send a Registration accept message based on the reception of the login request message from the UE. In addition, when the fourth condition is judged to be true, the AMF can send a Registration accept message based on the completion of the transmission and reception of the SM message between it and the SMF. It should be noted that the Registration accept message is a NAS message sent and received on the N1 interface, but is included in the RRC message for transmission and reception between the UE and the 5G AN (gNB).
[0228] The AMF may include one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the login acceptance message and send it. It should be noted that the AMF can send these identification information to indicate that the network supports each function, and can also indicate that the UE's request is accepted. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information can constitute one or more identification information. It should be noted that the information indicating support for each function and the information indicating request for use of each function can be sent and received as the same identification information, and can also be sent and received as different identification information.
[0229] Furthermore, the network may indicate the content indicated by the identification information included in the login acceptance message to the UE by including one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the login acceptance message. Furthermore, the network may allow the content indicated by the identification information included in the login acceptance message to the UE by including one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the login acceptance message.
[0230] Here, the network may indicate the content of the above identification information to the UE by sending a login acceptance message.
[0231] It should be noted that AMF can select and determine whether to include one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the login acceptance message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by AMF.
[0232] It should be noted that the AMF may also include identification information other than the tenth to twelfth and fifteenth to eighteenth identification information in the login acceptance message and send it. Specifically, the AMF may include the service level AA container in the login acceptance message. Alternatively, the AMF may use the service level AA container in sending the tenth to twelfth and fifteenth to eighteenth identification information. Specifically, the AMF may include one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the service level AA container, and may also include the service level AA container in the login acceptance message. The UE may receive the login acceptance message including the service level AA container.
[0233] In addition, AMF can include the SM message in the login acceptance message to send or send the SM message together with the login acceptance message. Among them, the sending method can be executed when the SM message is included in the login request message and the fourth condition is judged to be true. In addition, the sending method can also be executed when the SM message is included with the login request message and the fourth condition is judged to be true. AMF can indicate that the process used for SM during the login process is accepted by performing such a sending method. Here, the SM message can be either a PDU session establishment request message or a PDU session establishment acceptance message.
[0234] In addition, based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by the AMF, the AMF can indicate that the UE's request is accepted by sending a login acceptance message.
[0235] Furthermore, the AMF may include information indicating that part of the UE's request is rejected in the login acceptance message, or may indicate the reason why part of the UE's request is rejected by sending information indicating that part of the UE's request is rejected. Furthermore, the UE may identify the reason why part of the UE's request is rejected by receiving information indicating that part of the UE's request is rejected. It should be noted that the reason for rejection may be information indicating that the content indicated by the identification information received by the AMF is not allowed.
[0236] The UE receives a login acceptance message from the AMF via the 5G AN (gNB) (S808). By receiving the login acceptance message, the UE can identify that the UE's request based on the login request message is accepted and the contents of various identification information included in the login acceptance message.
[0237] Moreover, the UE can send a login completion message to the AMF via the 5G AN (gNB) as a response message to the login acceptance message (S810). Here, the login completion message is a NAS message sent and received on the N1 interface, but is sent and received between the UE and the 5G AN (gNB) in an RRC message.
[0238] AMF receives the login completion message (S810) via 5G AN (gNB). In addition, each device completes the login based on the sending and receiving of the login acceptance message and / or the login completion message. Figure 6 (A) process.
[0239] Next, the case where the first condition is judged to be false is described. Figure 6In the process (B), the AMF sends a Registration reject message to the UE via the 5G AN (gNB) as a response message to the Registration Request message (S812). Here, the Registration reject message is a NAS message sent and received on the N1 interface, but is sent and received between the UE and the 5G AN (gNB) in an RRC message.
[0240] Here, the AMF may include one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the login rejection message and send it. Moreover, the AMF may indicate that the UE's request is rejected or indicate the reason why the UE's request is rejected by sending one or more of the tenth to twelfth and fifteenth to eighteenth identification information.
[0241] Furthermore, the network may indicate the content indicated by the identification information included in the login rejection message to the UE by including one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the login rejection message. Furthermore, the network may also not allow the content indicated by the identification information included in the login rejection message to the UE by including one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the login rejection message.
[0242] It should be noted that AMF can select and determine whether to include one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the login rejection message based on the received identification information and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by AMF.
[0243] Furthermore, the AMF may indicate that the request of the UE based on the login request message is rejected by sending a login rejection message. Furthermore, the AMF may include information indicating the reason for rejection in the login rejection message and send it, or may indicate the reason for rejection by sending the reason for rejection. Furthermore, the UE may identify the reason why the UE's request is rejected by receiving information indicating the reason why the UE's request is rejected. It should be noted that the reason for rejection may be information indicating that the content indicated by the identification information that the AMF is not allowed to receive.
[0244] The UE receives a login rejection message from the AMF via the 5G AN (gNB) (S812). By receiving the login rejection message, the UE can identify that the UE's request based on the login request message is rejected and the contents of various identification information included in the login rejection message. In addition, the UE can also identify that the UE's request is rejected when the login rejection message is not received after a specified period of time after sending the login request message. Each device completes the (B) process in this process based on the sending and receiving of the login rejection message.
[0245] It should be noted that sometimes it will be suspended Figure 6 (A) The process starts Figure 6 (B) process.
[0246] Each device is based on Figure 6 The login process is completed by completing the process (A) or (B). It should be noted that each device can be based on Figure 6 The completion of the (A) process changes to the state where the UE has logged in to the network (RM_REGISTERED state), which can also be based on Figure 6 The UE may maintain the state (RM_DEREGISTERED state) in which the UE is not logged in to the network by completing the process (B), and may also transition to the state in which the UE is not logged in to the network. In addition, the transition of each device to each state may be based on the completion of the login process or the establishment of a PDU session.
[0247] In addition, the UE may complete the login process based on receipt of the login accept message or the login reject message.
[0248] Furthermore, each device may perform processing based on information sent and received during the login process based on the completion of the login process. For example, the reason why the UE's request was rejected may be identified when information indicating that a part of the UE's request was rejected is sent and received. Furthermore, each device may perform this process again based on the reason why the UE's request was rejected, and may also perform the login process on the core network_B or other cells.
[0249] Furthermore, the UE may store the identification information received together with the registration accept message and / or the registration reject message based on the completion of the registration procedure, and may also identify the determination of the network.
[0250] Furthermore, the UE may, upon receiving one or more of the tenth to twelfth and fifteenth to eighteenth identification information, recognize the content indicated by the received identification information. Furthermore, the UE may, upon receiving one or more of the tenth to twelfth and fifteenth to eighteenth identification information, recognize that the content indicated by the identification information included in the login acceptance message or the login rejection message is permitted.
[0251] Here, the UE may start the establishment process of direct C2 communication upon receiving the tenth identification information. In other words, the UE may recognize that the direct C2 communication is authenticated and / or authorized upon receiving the tenth identification information, and start the establishment process of direct C2 communication.
[0252] In addition, when the UE receives the tenth identification information, it may not start the process of establishing direct C2 communication. In other words, when the UE receives the tenth identification information, it may recognize that direct C2 communication is not authenticated and / or authorized, and does not start the process of establishing direct C2 communication.
[0253] In addition, when the UE receives the eleventh identification information, it can start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication. In other words, when the UE receives the eleventh identification information, it can recognize that direct C2 communication and / or C2 communication using PDU session is authenticated and / or authorized, and start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication.
[0254] In addition, when the UE receives the eleventh identification information, it may not start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication. In other words, when the UE receives the eleventh identification information, it can recognize that direct C2 communication and / or C2 communication using PDU session is not authenticated and / or authorized, and does not start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication.
[0255] In addition, when the UE receives the twelfth identification information, it can also set the identification information of the UAV or UAV-C. In addition, when the UE receives the twelfth identification information, it can delete the stored identification information of the UAV or UAV-C and store the received identification information of the UAV or UAV-C.
[0256] In addition, when the UE receives the fifteenth identification information, it can also start the release process of the direct C2 communication. In other words, when the UE receives the fifteenth identification information, it can recognize that the authentication and / or authorization of the direct C2 communication is cancelled and start the release process of the direct C2 communication.
[0257] In addition, the UE may start a release process for direct C2 communication and / or a PDU session release process for C2 communication when receiving the sixteenth identification information. In other words, the UE may recognize that the authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session is canceled when receiving the sixteenth identification information, and may start a release process for direct C2 communication and / or a PDU session release process for C2 communication.
[0258] In addition, when the UE receives the eighteenth identification information, it can set the timer value indicated by the eighteenth identification information to the first timer. In addition, when the UE receives the eighteenth identification information, it can start the first timer using the timer value indicated by the eighteenth identification information. Moreover, when the first timer expires, the UE can start the release process of the communication path for direct C2 communication. In addition, during the period until the first timer expires, the UE can start the release process of the communication path for direct C2 communication.
[0259] Here, the first timer may be a timer for managing a grace time until the direct C2 communication and / or the PDU session for C2 communication is released. In addition, the first timer may also be a timer for managing the time of releasing the direct C2 communication and / or the PDU session for C2 communication. In addition, the first timer may be a timer for managing the timer value indicated by the eighteenth identification information.
[0260] It should be noted that the above UE behavior may be implemented after receiving a login acceptance message or a login rejection message. In addition, the above UE behavior may also be implemented after receiving one or more of the tenth to twelfth and fifteenth to eighteenth identification information.
[0261] The UE can identify the content of the above identification information by receiving a login acceptance message or a login rejection message.
[0262] It should be noted that the actions performed when each identification information is received can be performed based on the received identification information. [3.2.2.PDU session establishment process]
[0263] Next, use Figure 7 , the behavior of each device when the UE executes the PDU session establishment process is described. Hereinafter, the PDU session establishment process is sometimes referred to as this process. In addition, the PDU session establishment process can also be an SM process.
[0264] In addition, the PDU session in this process can be a PDU session for C2 communication or a PDU session for direct C2 communication. In addition, the PDU session in this process can also be a PDU session for UAS service.
[0265] It should be noted that this process can also be executed after executing the login process more than once.
[0266] First, the UE sends a PDU session establishment request message to the SMF (S1400)(S1402)(S1404) to start the PDU session establishment process. Then, the SMF receives the PDU session establishment request message from the UE.
[0267] Specifically, the UE starts the PDU session establishment process by sending a NAS message (S1400) including an N1 SM container containing a PDU session establishment request message to the AMF via the access network. The NAS message is, for example, a message sent via the N1 interface, and may be an uplink NAS transport (UL NAS TRANSPORT) message.
[0268] Here, the UE may include one or more of the first to second identification information in a PDU session establishment request message or a NAS message and send the message.
[0269] It should be noted that the UE can indicate that the UE supports each function by sending these identification information, and can also indicate the UE's request. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information can constitute more than one identification information. It should be noted that the information indicating support for each function and the information indicating a request for use of each function can be sent and received as the same identification information, or can be sent and received as different identification information.
[0270] Here, the UE instructs the network on the content of each identification information by sending a PDU session establishment request message or a NAS message.
[0271] In other words, in the case where the UE supports direct C2 communication and / or the UE requests authentication and / or authorization to establish direct C2 communication from the network and / or the UE requests authentication and / or authorization to utilize direct C2 communication from the network, the UE may include the first identification information in a PDU session establishment request message or include it in a NAS message together with the PDU session establishment request message and send it.
[0272] In other words, in the case where the UE supports direct C2 communication and / or the UE requests the network for authentication and / or authorization for establishment of direct C2 communication and / or C2 communication using a PDU session and / or the UE requests the network for authentication and / or authorization for utilization of direct C2 communication and / or C2 communication using a PDU session, the UE may include the second identification information in the PDU session establishment request message or include it in a NAS message together with the PDU session establishment request message and send it.
[0273] In addition, the access network can be a 3GPP access or a non-3GPP access, including a base station device. That is, the UE sends a NAS message to the AMF via the base station device.
[0274] In addition, the UE may request the establishment of a PDU session supporting C2 communication by sending a PDU session establishment request message. In other words, the UE may request the establishment of a PDU session supporting a QoS flow for C2 communication by sending a PDU session establishment request message.
[0275] In addition, when requesting the establishment of a PDU session supporting C2 communication, the UE may request the establishment of an always-on PDU session. In other words, when requesting the establishment of a PDU session supporting a QoS flow for C2 communication, the UE may request the establishment of an always-on PDU session.
[0276] It should be noted that the UE can select and determine whether to include one or more of the first to second identification information in the PDU session establishment request message based on the subscriber information and / or the network status and / or the user's login information and / or the context maintained by the UE.
[0277] It should be noted that the UE may also include identification information other than the first to second identification information in the PDU session establishment request message and send it. Specifically, the UE may include the service level AA container in the PDU session establishment request message. Alternatively, the UE may also use the service level AA container in sending the first to second identification information. Specifically, the UE may include one or more identification information from the first to second identification information in the service level AA container, and may also include the service level AA container information element in the PDU session establishment request message.
[0278] Then, when receiving a NAS message, the AMF can identify the content of the request made by the UE and / or the information included in the NAS message (message, container, information).
[0279] Next, the AMF selects the SMF as the transmission destination of at least a part of the information (message, container, information) included in the NAS message received from the UE (S1402). It should be noted that the AMF can select the SMF of the transmission destination based on the information (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 login information and / or context maintained by the AMF.
[0280] Next, the AMF sends at least a portion of the information (message, container, information) included in the NAS message received from the UE to the selected SMF via the N11 interface, for example (S1404).
[0281] Then, when receiving information (messages, containers, information) sent from AMF, SMF can identify the content of information (messages, containers, information) requested by UE and / or received from AMF.
[0282] Here, the SMF can perform a second condition determination. In addition, the second condition determination can be used to determine whether the network accepts the UE's request. The SMF can start the second condition determination if it is true. Figure 7 (A) process, when the second condition is judged to be false, starts Figure 7 (B) process.
[0283] It should be noted that the second condition determination can also be performed by a NF other than the SMF. The NF may be, for example, NSSF, NWDAF, PCF, or NRF. In the case where a NF other than the SMF performs the second condition determination, the SMF may provide the NF with the information required for the second condition determination, specifically, at least a portion of the information received from the UE (S1406). Moreover, in the case where the NF determines the truth or falsity of the second condition determination based on the information received from the SMF, information including the result of the second condition determination (that is, whether it is true or false) may be transmitted to the SMF. The SMF may determine the identification information and / or control message that should be sent to the UE based on the result of the second condition determination received from the NF.
[0284] It should be noted that the second condition judgment can be performed based on information received from AMF (messages, containers, information) and / or subscriber information (subscription information) and / or network capability information and / or UE policy and / or operator policy and / or network status and / or user login information and / or context maintained by SMF.
[0285] For example, the second condition may be determined to be true when the network allows the UE's request, and false when the network does not allow the UE's request. In addition, the second condition may be determined to be true when the network of the UE's connection destination and / or the device within the network supports the function requested by the UE, and false when the function requested by the UE is not supported. In addition, the second condition may be determined to be true when the identification information sent and received is allowed, and false when the identification information sent and received is not allowed.
[0286] It should be noted that the conditions for determining the truth or falsity of the second conditional determination may not be limited to the above conditions.
[0287] Next, Figure 7 Each step of the process (A) is described.
[0288] The SMF may select a UPF for the established PDU session, for example, by sending an N4 session establishment request message to the selected UPF via an N4 interface (S1408). The N4 session establishment request message may include at least a portion of the PCC rules received from the PCF.
[0289] SMF can determine whether to perform authorization for C2 communication in this process based on information (messages, containers, information) received from AMF and / or information such as PCC rules received from 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 login information and / or context maintained by SMF.
[0290] In the case where authorization of C2 communication is performed in the present process, the SMF may determine authorization for establishment of direct C2 communication and / or C2 communication using a PDU session based on at least one of the first to second identification information.
[0291] Here, the SMF may select one or more UPFs based on information (messages, containers, information) received from the AMF 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 login information and / or contexts maintained by the SMF. In addition, when multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF. Here, it is assumed that the UPF is selected.
[0292] Then, when receiving the N4 session establishment request message (S1408), the UPF can identify the content of the information received from the SMF. In addition, the UPF can send an N4 session establishment response message (S1410) to the SMF via the N4 interface based on the reception of the N4 session establishment request message.
[0293] Then, the SMF can identify the content of the information received from the UPF when receiving the N4 session establishment response message as a response message to the N4 session establishment request message.
[0294] Next, the SMF sends a PDU session establishment accept message to the UE based on the reception of the PDU session establishment request message and / or the selection of the UPF and / or the reception of the N4 session establishment response message, etc. Then, the UE receives the PDU session establishment accept message from the SMF (S1418)(S1420)(S1422).
[0295] Specifically, the SMF sends the N1 SM container and / or the N2 SM information and / or the PDU session ID to the AMF (S1412) based on the reception of the PDU session establishment request message and / or the selection of the UPF and / or the reception of the N4 session establishment response message, for example, via the N11 interface. Here, the N1 SM container may include the PDU session establishment acceptance message. Moreover, the PDU session ID may be included in the PDU session establishment acceptance message.
[0296] 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 (S1414) to the UE via the first base station device included in the access network (S1416). Here, the NAS message is sent, for example, via the N1 interface. In addition, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.
[0297] Specifically, when the AMF sends an N2 PDU session request message to the base station device included in the access network (S1414), the base station device that receives the N2 PDU session request message sends a NAS message to the UE (S1416). Here, the N2 PDU session request message may include a NAS message and / or N2 SM information. In addition, the NAS message may include a PDU session ID and / or an N1 SM container.
[0298] In addition, the PDU session establishment accept message may be a response message to the PDU session establishment request. In addition, the PDU session establishment accept message may indicate that the establishment of the PDU session is accepted.
[0299] Here, the SMF and / or AMF may indicate that at least part of the UE's request based on the PDU session establishment request message is accepted by sending a PDU session establishment accept message and / or an N1 SM container and / or a PDU session ID and / or a NAS message and / or an N2 SM information and / or an N2PDU session request message.
[0300] Here, the SMF and / or AMF may include one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the PDU session establishment accept message and / or N1SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message and send them.
[0301] It should be noted that, by sending these identification information and / or PDU session establishment acceptance messages, the SMF can indicate that the network supports each function, that the UE's request is accepted, that the request from the UE is not allowed, or a combination of these information. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information can constitute more than one identification information. It should be noted that the information indicating support for each function and the information indicating a request to use each function can be sent and received as the same identification information, or as different identification information.
[0302] Here, the network can indicate the content of the above identification information to the UE by sending a PDU session establishment accept message.
[0303] It should be noted that the network may also include identification information other than the tenth to twelfth and fifteenth to eighteenth identification information in the PDU session establishment accept message and send it. Specifically, the network may also include the service level AA container in the PDU session establishment accept message. Alternatively, the network may also use the service level AA container in the transmission of the tenth to twelfth and fifteenth to eighteenth identification information. Specifically, the network may also include one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the service level AA container, and may also include the service level AA container in the PDU session establishment accept message. The UE may receive the PDU session establishment accept message including the service level AA container.
[0304] It should be noted that SMF and / or AMF can determine which identification information to include in the PDU session establishment acceptance message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message based on the 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 login information and / or context maintained by SMF and / or AMF.
[0305] Next, when the UE receives the NAS message via the N1 interface (S1416), for example, it can recognize that the UE's request based on the PDU session establishment request message is accepted and / or the content of information (message, container, information) included in the NAS message.
[0306] Next, Figure 7 Each step of the process (B) is described.
[0307] First, based on the reception of the PDU session establishment request message, the SMF sends the N1 SM container and / or the PDU session ID to the AMF via the N11 interface (S1418). Here, the N1 SM container may include a PDU session establishment rejection message. Moreover, the PDU session ID may be included in the PDU session establishment rejection message.
[0308] Next, the AMF that receives the N1 SM container and / or the PDU session ID sends a NAS message (S1420) to the UE via a base station device included in the access network (S1422). Here, the NAS message is sent, for example, via the N1 interface. In addition, the NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. In addition, the NAS message may include the PDU session ID and / or the N1 SM container.
[0309] In addition, the PDU session establishment rejection message may be a response message to the PDU session establishment request. In addition, the PDU session establishment rejection message may indicate that the establishment of the PDU session is rejected.
[0310] Here, the SMF and / or AMF may indicate that the UE's request based on the PDU session establishment request message is rejected by sending a PDU session establishment reject message and / or an N1 SM container and / or a PDU session ID and / or a NAS message.
[0311] It should be noted that, by sending a PDU session establishment reject message, the SMF can indicate that the UE's request is rejected, that the request from the UE is not allowed, or a combination of these information.
[0312] Here, the SMF and / or AMF may include one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the PDU session establishment reject message and / or N1SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message and send them.
[0313] It should be noted that SMF and / or AMF can determine which identification information to include in the PDU session establishment reject message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message based on the 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 login information and / or context maintained by SMF and / or AMF.
[0314] Next, when the UE receives a NAS message via the N1 interface (S1422), for example, it can identify that the UE's request based on the PDU session establishment request message is rejected and / or the content of information (message, container, information) included in the NAS message.
[0315] Furthermore, the UE can recognize the content indicated by the received identification information when receiving one or more of the tenth to twelfth and fifteenth to eighteenth identification information. Furthermore, the UE can recognize that the content indicated by the identification information included in the NAS message or the PDU session establishment accept message or the PDU session establishment reject message is allowed when receiving one or more of the tenth to twelfth and fifteenth to eighteenth identification information.
[0316] Here, the UE may start the establishment process of direct C2 communication upon receiving the tenth identification information. In other words, the UE may recognize that the direct C2 communication is authenticated and / or authorized upon receiving the tenth identification information, and start the establishment process of direct C2 communication.
[0317] In addition, when the UE receives the tenth identification information, it may not start the process of establishing direct C2 communication. In other words, when the UE receives the tenth identification information, it may recognize that direct C2 communication is not authenticated and / or authorized, and does not start the process of establishing direct C2 communication.
[0318] In addition, when the UE receives the eleventh identification information, it can start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication. In other words, when the UE receives the eleventh identification information, it can recognize that direct C2 communication and / or C2 communication using PDU session is authenticated and / or authorized, and start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication.
[0319] In addition, when the UE receives the eleventh identification information, it may not start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication. In other words, when the UE receives the eleventh identification information, it can recognize that direct C2 communication and / or C2 communication using PDU session is not authenticated and / or authorized, and does not start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication.
[0320] In addition, when the UE receives the twelfth identification information, it can also set the identification information of the UAV or UAV-C. In addition, when the UE receives the twelfth identification information, it can delete the stored identification information of the UAV or UAV-C and store the received identification information of the UAV or UAV-C.
[0321] In addition, when the UE receives the fifteenth identification information, it can also start the release process of the direct C2 communication. In other words, when the UE receives the fifteenth identification information, it can recognize that the authentication and / or authorization of the direct C2 communication is cancelled and start the release process of the direct C2 communication.
[0322] In addition, the UE may start a release process for direct C2 communication and / or a PDU session release process for C2 communication when receiving the sixteenth identification information. In other words, the UE may recognize that the authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session is canceled when receiving the sixteenth identification information, and may start a release process for direct C2 communication and / or a PDU session release process for C2 communication.
[0323] In addition, when the UE receives the eighteenth identification information, it can set the timer value indicated by the eighteenth identification information to the first timer. In addition, when the UE receives the eighteenth identification information, it can start the first timer using the timer value indicated by the eighteenth identification information. Moreover, when the first timer expires, the UE can start the release process of the communication path for direct C2 communication. In addition, during the period until the first timer expires, the UE can start the release process of the communication path for direct C2 communication.
[0324] Here, the first timer may be a timer for managing a grace time until the direct C2 communication and / or the PDU session for C2 communication is released. In addition, the first timer may also be a timer for managing the time of releasing the direct C2 communication and / or the PDU session for C2 communication. In addition, the first timer may be a timer for managing the timer value indicated by the eighteenth identification information.
[0325] It should be noted that the above UE behavior may be implemented after receiving a PDU session accept message or a PDU session reject message. In addition, the above UE behavior may also be implemented after receiving one or more of the tenth to twelfth and fifteenth to eighteenth identification information.
[0326] The UE can identify the content of the above identification information by receiving a NAS message or a PDU session establishment accept message or a PDU session establishment reject message.
[0327] Each device can complete this process based on sending and receiving a PDU session establishment acceptance message. In addition, each device can establish a PDU session based on the completion of this process. At this time, each device can be transformed into a state where it can communicate with the DN using the established PDU session.
[0328] Each device can also complete this process based on the sending and receiving of the PDU session establishment acceptance message or the PDU session establishment rejection message. At this time, each device cannot establish a PDU session, and therefore, cannot communicate with the DN in the absence of a PDU session that has been established.
[0329] It should be noted that the various processes performed by the UE based on the reception of various identification information as described above can be performed in this process or after the completion of this process, or can be performed based on the completion of this process after the completion of this process. [3.2.3. Overview of the network-led session management process]
[0330] Next, the network-led session management process is described in general. Hereinafter, the network-led session management process is also referred to as this process. This process is a process for session management performed by the network for an established PDU session. In addition, the network-led session management process may be an SM process.
[0331] In addition, the PDU session in this process can be a PDU session for C2 communication or a PDU session for direct C2 communication. In addition, the PDU session in this process can also be a PDU session for UAS service.
[0332] It should be noted that this process can be a network-led PDU session modification process and / or a network-led PDU session release process, etc., and can also execute network-led session management processes not limited to these. It should be noted that each device can send and receive PDU session modification messages during the network-led PDU session modification process, and can also send and receive PDU session release messages during the network-led PDU session release process.
[0333] In addition, if the process is a network-led PDU session modification process, the session management request message in the process may be a PDU session modification command (PDU SESSION MODIFICATION COMMAND) message. In addition, if the process is a network-led PDU session release process, the session management request message in the process may be a PDU session release command (PDU SESSION RELEASE COMMAND) message.
[0334] In addition, if the process is a network-led PDU session modification process, the session management completion message in the process may be a PDU session modification completion (PDU SESSION MODIFICATION COMPLETE) message. In addition, if the process is a network-led PDU session release process, the session management completion message in the process may be a PDU session release completion (PDU SESSION RELEASE COMPLETE) message. [3.2.3.1. Example of network-led session management process]
[0335] Next, use Figure 8 , an example of a network-led session management process is described. Hereinafter, this process refers to a network-led session management process. Each step of this process is described.
[0336] Based on the completion of the login process and / or the PDU session establishment process, the UE and each device within the core network_B190 start the network-led session management process at an arbitrary timing.
[0337] Specifically, the device within the core network_B190 can start this process based on the reception of a PDU session change request message from the UE, or can start this process based on the reception of a PDU session release request message from the UE. It should be noted that, in the case where this process is started based on the reception of a PDU session change request message, this process can be a network-led PDU session change process. Moreover, in the case where this process is started based on the reception of a PDU session release request message, this process can be a network-led PDU session release process.
[0338] Moreover, the device within the core network_B190 can start this process based on a request from a device in the DN or other devices within the core network.
[0339] Here, the device in the core network_B 190 that starts this process may be SMF and / or AMF, and the UE may send and receive messages in this process via AMF and / or access network_B. Moreover, the device in the DN may be an AF (Application Function) in the DN.
[0340] The device in the core network_B190 sends a network-initiated session management request message to the UE (S1602) to start the network-initiated session management. In addition, the UE receives the network-initiated session management request message from the device in the core network_B190.
[0341] Here, the device in the core network_B190 may include at least one of the tenth to twelfth and fifteenth to eighteenth identification information in the network-led session management request message, or may indicate the request of the core network_B190 by including the identification information. Furthermore, the device in the core network_B190 may include the PDU session ID in the network-led session management request message, or may request to change the PDU session identified by the PDU session ID by including the PDU session ID.
[0342] It should be noted that the PDU session ID included in the PDU session change request message may be the PDU session ID of the established PDU session. Moreover, in the case where this process is performed based on the UE-led session management process, the PDU session ID included in the PDU session change request message may be the same as the PDU session ID included in the PDU session change request message or the PDU session release request message.
[0343] Here, the UE may start the establishment process of direct C2 communication upon receiving the tenth identification information. In other words, the UE may recognize that the direct C2 communication is authenticated and / or authorized upon receiving the tenth identification information, and start the establishment process of direct C2 communication.
[0344] In addition, when the UE receives the tenth identification information, it may not start the process of establishing direct C2 communication. In other words, when the UE receives the tenth identification information, it may recognize that direct C2 communication is not authenticated and / or authorized, and does not start the process of establishing direct C2 communication.
[0345] In addition, when the UE receives the eleventh identification information, it can start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication. In other words, when the UE receives the eleventh identification information, it can recognize that direct C2 communication and / or C2 communication using PDU session is authenticated and / or authorized, and start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication.
[0346] In addition, when the UE receives the eleventh identification information, it may not start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication. In other words, when the UE receives the eleventh identification information, it can recognize that direct C2 communication and / or C2 communication using PDU session is not authenticated and / or authorized, and does not start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication.
[0347] In addition, when the UE receives the twelfth identification information, it can also set the identification information of the UAV or UAV-C. In addition, when the UE receives the twelfth identification information, it can delete the stored identification information of the UAV or UAV-C and store the received identification information of the UAV or UAV-C.
[0348] In addition, when the UE receives the fifteenth identification information, it can also start the release process of the direct C2 communication. In other words, when the UE receives the fifteenth identification information, it can recognize that the authentication and / or authorization of the direct C2 communication is cancelled and start the release process of the direct C2 communication.
[0349] In addition, the UE may start a release process for direct C2 communication and / or a PDU session release process for C2 communication when receiving the sixteenth identification information. In other words, the UE may recognize that the authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session is canceled when receiving the sixteenth identification information, and may start a release process for direct C2 communication and / or a PDU session release process for C2 communication.
[0350] In addition, when the UE receives the eighteenth identification information, it can set the timer value indicated by the eighteenth identification information to the first timer. In addition, when the UE receives the eighteenth identification information, it can start the first timer using the timer value indicated by the eighteenth identification information. Moreover, when the first timer expires, the UE can start the release process of the communication path for direct C2 communication. In addition, during the period until the first timer expires, the UE can start the release process of the communication path for direct C2 communication.
[0351] Here, the first timer may be a timer for managing a grace time until the direct C2 communication and / or the PDU session for C2 communication is released. In addition, the first timer may also be a timer for managing the time of releasing the direct C2 communication and / or the PDU session for C2 communication. In addition, the first timer may be a timer for managing the timer value indicated by the eighteenth identification information.
[0352] It should be noted that the above UE behavior can be implemented after receiving the PDU session change command message or the PDU session release command message. In addition, the above UE behavior can also be implemented after receiving one or more of the tenth to twelfth and fifteenth to eighteenth identification information.
[0353] Then, the UE that receives the network-led session management request message sends a network-led session management completion message (S1604). Moreover, the UE may perform a first process (S1606) based on at least one of the tenth to twelfth and fifteenth to eighteenth identification information received from the core network_B190 to complete this process. In addition, the UE may implement the first process based on the completion of this process.
[0354] Here, the UE may include the PDU session ID in the network-initiated session management completion message. It should be noted that the PDU session ID included in the network-initiated session management completion message may be the same as the PDU session ID included in the network-initiated session management request message.
[0355] Hereinafter, an example of the first process will be described.
[0356] The first process may be a process in which the UE identifies a matter indicated by the core network_B190, or a process in which the UE identifies a request of the core network_B190. Furthermore, the first process may be a process in which the UE stores the received identification information as a context, or a process in which the received identification information is transmitted to an upper layer and / or a lower layer.
[0357] In addition, the UE performs the behavior of receiving each of the above-mentioned identification information as the first processing.
[0358] Furthermore, each device may perform processing based on the identification information sent and received in this process based on the completion of this process. In other words, the UE may perform the first processing based on the completion of this process, or may complete this process after the completion of the first processing.
[0359] Furthermore, each device completes the network-led session management process based on the completion of the above-mentioned processing and / or the sending and receiving of the network-led session management request message and / or the network-led session management completion message.
[0360] It should be noted that, based on the completion of the network-led session management process, each device can change the existing PDU session or release the existing PDU session. In other words, based on the completion of the PDU session change process, each device can change the existing PDU session. Similarly, in other words, based on the completion of the PDU session release process, each device can release the existing PDU session. [3.2.4. Overview of UE-led session management process]
[0361] Next, an overview of the UE-led session management process is described. Hereinafter, the UE-led session management process is also referred to as this process. This process is a process for session management performed by the UE for an established PDU session. In addition, the UE-led session management process may be an SM process.
[0362] In addition, the PDU session in this process can be a PDU session for C2 communication or a PDU session for direct C2 communication. In addition, the PDU session in this process can also be a PDU session for UAS service.
[0363] It should be noted that this process can be a UE-led PDU session change (PDU session modification) process and / or a UE-led PDU session release (PDU session release) process, etc., and can also execute UE-led session management processes not limited to these. It should be noted that each device can send and receive PDU session change request messages and / or PDU session change command messages and / or PDU session change completion messages and / or PDU session change rejection messages during the UE-led PDU session change process. In addition, each device can send and receive PDU session release request messages and / or PDU session release command messages and / or PDU session release completion messages and / or PDU session release rejection messages during the UE-led PDU session release process.
[0364] Moreover, each device completes the UE-led session management process based on the completion of the above-mentioned processing and / or the sending and receiving of the UE-led session management request message and / or the UE-led session management completion message. [3.2.4.1. Example of UE-led PDU session change process]
[0365] Next, use Fig. 9 , each step of this process is described. Hereinafter, this process refers to the PDU session change process led by the UE.
[0366] It should be noted that, based on the completion of the login process and / or the PDU session establishment process, the UE can start the UE-led PDU session change process at any timing. In other words, the UE can start the UE-led PDU session change process for the established PDU session at any timing. In other words, the UE can start the UE-led PDU session change process using the same PDU session ID as the established PDU session at any timing.
[0367] First, the UE starts the UE-led PDU session change process by sending a PDU session change request message to the SMF (S1802). Here, the UE can include the PDU session ID in the PDU session change request message, or request to change the PDU session identified by the PDU session ID by including the PDU session ID.
[0368] Here, the UE may include at least one of the first to second identification information in the PDU session change request message.
[0369] It should be noted that the PDU session ID included in the PDU session change request message may be the PDU session ID of the established PDU session.
[0370] Next, the SMF receives the PDU session change request message sent by the UE. If the SMF accepts the UE's request, it starts the network-led PDU session change process. On the contrary, if the SMF rejects the UE's request, it sends a PDU session change reject message to the UE. The following describes the situation where the SMF rejects the UE's request.
[0371] Based on the acceptance of the PDU session change request message, the SMF sends a PDU session change reject message to the UE (S1804).
[0372] Here, the SMF may include at least one of the tenth to twelfth and fifteenth to eighteenth identification information in the PDU session change reject message.
[0373] Here, the PDU session ID included in the PDU session change reject message may be the same as the PDU session ID included in the PDU session change request message. In other words, the PDU session ID included in the PDU session change reject message may be the same as the PDU session ID provided by the UE in this process.
[0374] The UE receives the PDU session change reject message. Moreover, each device completes this process based on the sending and receiving of the PDU session change reject message and / or the completion of the network-led PDU session change process.
[0375] Here, the UE may recognize that the UE's request is rejected based on the reception of the PDU session change reject message. Furthermore, the UE may implement the second process (S1806) based on the reception of the PDU session change reject message. It should be noted that the second process may be implemented based on the completion of this process.
[0376] Here, the second process may be a process in which the UE identifies the matter indicated by the SMF. Furthermore, the second process may be a process in which the UE stores the received identification information as a context, or may be a process in which the received identification information is transmitted to an upper layer and / or a lower layer. Furthermore, the second process may also be a process in which the UE identifies that the request for this process is rejected.
[0377] In addition, the PDU session change procedure and / or the PDU session release procedure for the same PDU session may be a PDU session change procedure and / or a PDU session release procedure using the same PDU session ID.
[0378] Moreover, each device completes the UE-led PDU session change process based on the completion of the above-mentioned processing and / or the sending and receiving of the UE-led PDU session change reject message. [3.2.4.2. Example of UE-led PDU session release process]
[0379] Next, each step of this process is described. Hereinafter, this process refers to the PDU session release process led by the UE.
[0380] The UE-led PDU session release process is the same as the above-mentioned PDU session change process.
[0381] Specifically, in the case where this process is a UE-led PDU session release process, the above-mentioned PDU session change request message can be replaced with a PDU session release request message. Moreover, in the case where this process is a UE-led PDU session release process, the above-mentioned PDU session change request message can be replaced with a PDU session release request message, and the above-mentioned PDU session change rejection message can be replaced with a PDU session release rejection message. In addition, the behavior of changing the PDU session can be replaced with the behavior of releasing the PDU session.
[0382] Moreover, in the case where this process is a UE-led PDU session release process, the behavior of the SMF based on the reception of the PDU session release request message can be the same as the behavior of the SMF based on the reception of the PDU session change request message described above. Moreover, in the case where this process is a UE-led PDU session release process, the behavior of the UE based on the reception of the PDU session release reject message can be the same as the behavior of the UE based on the reception of the PDU session change reject message described above.
[0383] Moreover, in the case where this process is a UE-led PDU session release process, the SMF can start a network-led PDU session release process based on the receipt of the PDU session release request message, or send a PDU session release reject message to the UE.
[0384] In addition, the UE may send a PDU session release request message including at least one of the first to second identification information to the network.
[0385] Moreover, each device completes the UE-led PDU session release process based on the completion of the above-mentioned processing and / or the sending and receiving of the UE-led PDU session release reject message. [3.2.5. Procedure for establishing direct C2 communications]
[0386] Next, use Fig.10 , the behavior of each device when the UE executes the process for establishing direct C2 communication is described. Hereinafter, the process for establishing direct C2 communication is sometimes referred to as this process. In addition, the process for establishing direct C2 communication may also be referred to as the establishment process of direct C2 communication.
[0387] It should be noted that this process can be performed after performing more than one login process and / or PDU session establishment process and / or network-led session management process and / or UE-led session management process. In addition, this process can also be performed during the login process or PDU session establishment process or network-led session management process or UE-led session management process.
[0388] This process may also be performed when the UE authenticates and / or authorizes direct C2 communication from the network during the login process and / or PDU session establishment process and / or network-led session management process and / or UE-led session management process. In other words, the UE may start this process when receiving the tenth to twelfth and fifteenth to eighteenth identification information. In addition, the UE may also start this process without authorization for direct C2 communication from the network.
[0389] It should be noted that in this process, the UE may include an initial UE and a target UE.
[0390] It should be noted that, in this process, the initial UE and the target UE can send and receive various control messages on PC5.
[0391] First, the initial UE sends a first control message to the target UE (S2000) to start this process.
[0392] Here, the first control message may be a message requesting establishment of direct C2 communication. In addition, the first control message may be a ProSe direct link establishment request message (ProSe direct link establishment request message). In addition, the first control message may be a direct communication request message (Direct Communication Request message).
[0393] Here, the initial UE may include one or more identification information in the third to fifth identification information and send it in the first control message. In addition, the initial UE may also send one or more identification information in the third to fifth identification information together with the first control message.
[0394] It should be noted that, by sending these identification information, the initial UE can indicate that the initial UE supports each function, and can also indicate the request of the initial UE. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information can constitute more than one identification information. It should be noted that the information indicating support for each function and the information indicating request for use of each function can be sent and received as the same identification information, and can also be sent and received as different identification information.
[0395] Here, the initial UE may indicate the content of each identification information to the network by sending the first control message. In addition, the initial UE may indicate the content of each identification information to the network by sending one or more identification information among the third to fifth identification information.
[0396] It should be noted that the initial UE can select and determine whether to include one or more of the third to fifth identification information in the first control message based on the subscriber information and / or the network status and / or the user's login information and / or the context maintained by the UE.
[0397] It should be noted that the UE may also include identification information other than the third to fifth identification information in the first control message and send it.
[0398] In addition, the initial UE may request the establishment of the direct C2 communication by sending the first control message. In addition, the initial UE may request the establishment of the direct C2 communication by sending one or more identification information among the third to fifth identification information.
[0399] Next, the target UE receives a first control message from the initial UE.
[0400] Upon receiving the first control message, the target UE may identify the content requested by the initial UE and / or the content of the information (message, container, identification information) included in the first control message.
[0401] Here, the target UE can perform the third condition determination. In addition, the third condition determination can be used to determine whether the target UE accepts the request of the initial UE. When the target UE determines that the third condition determination is true, it can start Fig.10 The process (A) of can start when the third condition is judged to be false. Fig.10 (B) process.
[0402] It should be noted that the third condition judgment can be performed based on information (messages, containers, information) received from the initial UE and / or subscriber information (subscription information) and / or network capability information and / or UE policy and / or operator policy and / or network status and / or user login information and / or context maintained by the target UE.
[0403] For example, when the target UE allows the request of the initial UE, the third conditional judgment can be determined to be true, and when the target UE does not allow the request of the initial UE, the third conditional judgment can be determined to be false. In addition, when the target UE and / or the device in the target UE, which is the connection destination of the initial UE, supports the function requested by the initial UE, the third conditional judgment can be determined to be true, and when it does not support the function requested by the initial UE, the third conditional judgment can be determined to be false. In addition, when the identification information is allowed to be sent and received, the third conditional judgment can be determined to be true, and when the identification information is not allowed to be sent and received, the third conditional judgment can be determined to be false.
[0404] It should be noted that the conditions for determining the truth or falsity of the third condition determination are not limited to the above conditions.
[0405] Next, Fig.10 Each step of the process of (A) is described.
[0406] Based on the reception of the first control message, the target UE sends a second control message to the initial UE (S2002).
[0407] Here, the second control message may be a message for accepting the establishment of direct C2 communication. In addition, the second control message may also be a ProSe direct link establishment accept message (ProSe direct link establishment accept message). In addition, the second control message may also be a direct communication accept message (Direct Communication Accept message).
[0408] In addition, the second control message may be a response message to the first control message. In addition, the second control message may indicate that the first control message is accepted.
[0409] Here, the target UE may include one or more of the thirteenth to fourteenth identification information in the second control message and send it.
[0410] Here, the target UE can indicate that at least a portion of the request of the initial UE based on the first control message is accepted by sending a second control message. In addition, the target UE can indicate that at least a portion of the request of the initial UE based on the first control message is accepted by sending one or more of the thirteenth to fourteenth identification information.
[0411] It should be noted that, by sending these identification information and / or the second control message, the target UE can indicate that the target UE supports each function, can indicate that the request of the initial UE is accepted, can indicate that the request from the initial UE is not allowed, or can indicate a combination of these information. Moreover, in the case of sending and receiving multiple identification information, two or more of these identification information can constitute more than one identification information. It should be noted that the information indicating support for each function and the information indicating a request to use each function can be sent and received as the same identification information, and can also be sent and received as different identification information.
[0412] It should be noted that the target UE can determine which identification information is included in the second control message based on the 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 login information and / or context maintained by the target UE.
[0413] Next, the original UE receives a second control message from the target UE.
[0414] When receiving the second control message, the initial UE can recognize that the request of the UE based on the first control message is accepted and / or the content of the information (message, container, identification information) included in the second control message.
[0415] Next, Fig.10 Each step of the process (B) is described.
[0416] First, the target UE sends a third control message to the initial UE based on reception of the first control message (S2004).
[0417] Here, the third control message may be a message for rejecting the establishment of direct C2 communication. In addition, the third control message may also be a ProSe direct link establishment reject message (ProSe direct link establishment reject message). In addition, the third control message may also be a direct communication reject message (Direct Communication Reject message).
[0418] In addition, the third control message may be a response message to the first control message. In addition, the third control message may indicate that the establishment of the direct C2 communication is rejected.
[0419] Here, the target UE may indicate that the request of the initial UE based on the first control message is rejected by sending a third control message.
[0420] It should be noted that, by sending the third control message, the target UE can indicate that the request of the initial UE is rejected, or that the request from the initial UE is not allowed, or a combination of these information.
[0421] Here, the target UE may include one or more of the thirteenth to fourteenth identification information in the third control message and send it.
[0422] It should be noted that the target UE can determine which identification information is included in the third control message based on the 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 login information and / or context maintained by the target UE.
[0423] Next, the initial UE receives the third control message (S2004). Upon receiving the third control message, the initial UE can identify that the initial UE's request based on the first control message is rejected and / or the content of information (message, container, identification information) included in the third control message.
[0424] Each device can complete this process based on the sending and receiving of the second control message. Each device can also establish a communication path for direct C2 communication based on the completion of this process. At this time, each device can use the established direct C2 communication to transform into a communicable state between the initial UE and the target UE.
[0425] In addition, each device can complete this process based on the sending and receiving of the third control message. At this time, each device cannot establish direct C2 communication, so in the absence of established direct C2 communication, communication cannot be performed between the initial UE and the target UE.
[0426] It should be noted that the various processes performed by the initial UE based on the reception of various identification information as described above can be performed in this process or after the completion of this process, or can be performed based on the completion of this process.
[0427] Upon completion of this process, the initial UE and the target UE that have established the direct C2 communication may start exchanging information using the direct C2 communication. [3.2.6. Procedure for releasing direct C2 communication]
[0428] Next, use Fig.11 , the behavior of each device when the UE executes the process for releasing the direct C2 communication is described. Hereinafter, the process for releasing the direct C2 communication is sometimes referred to as this process. In addition, the process for releasing the direct C2 communication may also be referred to as the release process of the direct C2 communication.
[0429] It should be noted that this process can be performed after performing more than one login process and / or PDU session establishment process and / or network-led session management process and / or UE-led session management process. In addition, this process can also be performed during the login process or PDU session establishment process or network-led session management process or UE-led session management process.
[0430] This process may also be performed when the UE cancels the authentication and / or authorization of direct C2 communication from the network during the login process and / or PDU session establishment process and / or the network-led session management process and / or the UE-led session management process. In other words, the UE may start this process when receiving the tenth to twelfth and fifteenth to eighteenth identification information. In addition, the UE may also start this process without canceling the direct C2 communication from the network.
[0431] It should be noted that in this process, the UE may include an initial UE and a target UE.
[0432] In addition, this process may also be performed when the UE receives an indication of failure of the radio link or an indication of release of the PC5-RRC connection from a lower layer.
[0433] In addition, this process can be performed when the initial UE receives a request from the upper layer to release the 5G ProSe direct link. In addition, this process can also be performed when the initial UE receives a request from the upper layer to release the communication path of the direct C2 communication.
[0434] In addition, this process can also be performed when the target UE is in an unresponsive state.
[0435] In addition, this process may also be performed when the initial UE reaches the maximum number of established 5G ProSe direct links and / or needs to establish a new 5G ProSe direct link. In addition, this process may also be performed when the initial UE reaches the maximum number of established direct C2 communication communication paths and / or needs to establish a new 5G ProSe direct link.
[0436] In addition, this process can also be performed when the initial UE acts as a 5G ProSe third layer UE to network relay UE (5G ProSe layer-3 UE-to-network relay UE) and / or when the PDU session is released by the initial UE or the network.
[0437] In addition, this process can also be performed when the initial UE acts as a 5G ProSe second layer remote UE (5GProSe layer-2remote UE) or a 5G ProSe third layer remote UE (5G ProSe layer-3remote UE) and / or the initial UE is in 5GMM-idle mode (IDLE mode).
[0438] In addition, this process can also be performed when the initial UE acts as a 5G ProSe second layer remote UE or a 5G ProSe third layer remote UE or a 5G ProSe second layer UE to network relay UE (5G ProSe layer-2UE-to-network relay UE) and / or the service authorization of the initial UE is revoked after receiving the set parameters.
[0439] In addition, this process can also be performed when the initial UE acts as a 5G ProSe third-layer UE to the network relay UE and / or the service authorization of the initial UE is revoked after receiving the set parameters.
[0440] It should be noted that the 5G ProSe second layer UE to network relay UE can be a UE that can utilize 5G ProSe or direct C2 communication and provides the function of supporting connectivity to the network for the 5G ProSe second layer remote UE via the second layer protocol.
[0441] In addition, the 5G ProSe third layer UE to network relay UE can be a UE capable of utilizing 5G ProSe or direct C2 communication, providing functionality supporting connectivity to the network for 5G ProSe third layer remote UEs via a third layer protocol.
[0442] In addition, the 5G ProSe second layer remote UE can be a UE that can utilize 5G ProSe or direct C2 communication and communicate with the DN via a 5G ProSe second layer UE to a network relay UE.
[0443] In addition, the 5G ProSe third layer remote UE can be a UE that communicates with the DN via a 5G ProSe third layer UE to a network relay UE and can utilize 5G ProSe or direct C2 communication.
[0444] It should be noted that, in this process, the initial UE and the target UE can send and receive various control messages on PC5.
[0445] First, the initial UE sends a first control message to the target UE (S2200) to start this process.
[0446] Here, the first control message may be a message requesting release of direct C2 communication. In addition, the first control message may also be a ProSe direct link release request message.
[0447] Here, the initial UE may include the sixth identification information in the first control message and send it. In addition, the initial UE may also send the sixth identification information together with the first control message.
[0448] Here, the initial UE can indicate the content of the identification information to the network by sending the first control message. In addition, the initial UE can indicate the content of the identification information to the network by sending the sixth identification information.
[0449] It should be noted that the initial UE can select and determine whether to include the sixth identification information in the first control message based on subscriber information and / or network status and / or user login information and / or context maintained by the UE.
[0450] It should be noted that the UE may also include identification information other than the sixth identification information in the first control message and send it.
[0451] In addition, the initial UE may request the release of the direct C2 communication with the target UE by sending the first control message. In addition, the initial UE may request the release of the direct C2 communication with the target UE by sending the sixth identification information.
[0452] Next, the target UE receives a first control message from the initial UE.
[0453] Upon receiving the first control message, the target UE may identify the content requested by the initial UE and / or the content of the information (message, container, identification information) included in the first control message.
[0454] Next, the target UE sends a second control message to the initial UE based on the reception of the first control message (S2202).
[0455] Here, the second control message may be a message for accepting the release of direct C2 communication. In addition, the second control message may also be a ProSe direct link release accept message.
[0456] In addition, the second control message may be a response message to the first control message. In addition, the second control message may indicate that the first control message is accepted.
[0457] Here, the target UE may indicate that at least a part of the request of the initial UE based on the first control message is accepted by sending the second control message.
[0458] It should be noted that, by sending the second control message, the target UE can indicate that the target UE supports various functions, or indicate that the request from the initial UE is accepted, or indicate that the request from the initial UE is not allowed, or indicate a combination of these information.
[0459] Next, the original UE receives a second control message from the target UE.
[0460] When receiving the second control message, the initial UE can recognize that the request of the UE based on the first control message is accepted and / or the content of the information (message, container, identification information) included in the second control message.
[0461] Each device may complete this process based on the sending and receiving of the second control message. Each device may also release the communication path for direct C2 communication based on the completion of this process. At this time, each device may be transformed into a state where communication between the initial UE and the target UE is not possible. [3.2.7.UUAA]
[0462] Next, the outline of the UUAA (USS UAV Authorization / Authentication) process is described. Hereinafter, the UUAA process may also be referred to as UUAA or this process.
[0463] This process is a process implemented by the USS for UE authentication and / or authorization. It should be noted that the authorization for C2 communication (Authorization for C2) can be performed in the UUAA process.
[0464] It should be noted that this process can be initiated by the network or by the UE.
[0465] In addition, UUAA may be a UUAA-MM process implemented when logging in to 5GS. In addition, UUAA may be a UUAA-SM process implemented in PDU session establishment. In addition, UUAA may be an MM process or an SM process. In addition, the process used in UUAA may be an MM process or an SM process.
[0466] In addition, UUAA-SM may be implemented without implementing UUAA-MM.
[0467] In addition, the PDU session for UAS services is established only after the UAV is authenticated and authorized by the USS. This behavior can be implemented between UUAA-MM or UUAA-SM.
[0468] It should be noted that the success of UUAA can be replaced by allowing the authentication and authorization of the UAV. In addition, the failure of UUAA can be replaced by not allowing the authentication and authorization of the UAV.
[0469] In addition, allowing the authentication and authorization of the UAV can be replaced by the UAV being authenticated and authorized. In addition, not allowing the authentication and authorization of the UAV can be replaced by the UAV not being authenticated and authorized.
[0470] In addition, the UAV authentication and authorization success can be replaced by the UAV being authenticated and authorized. In addition, the UAV authentication and authorization failure can be replaced by the UAV not being authenticated and authorized.
[0471] In addition, the authentication and authorization of the USS may be replaced by the UAV being authenticated and authorized. In addition, the authentication and authorization of the USS may not be replaced by the UAV not being authenticated and authorized. [3.2.7.1.UUAA-MM]
[0472] Next, use Fig.12 , the UUAA-MM process is explained. Hereinafter, the UUAA-MM process is also referred to as UUAA-MM or this process. This process can be a process implemented when logging in to 5GS.
[0473] The UUAA-MM process can be performed during the login process to 5GS or after the login process to 5GS. In other words, the first communication in the UUAA-MM process described below and the above-mentioned login process can be collectively referred to as the login process, and the first communication in the UUAA-MM process described below can be a process independent of the above-mentioned login process.
[0474] In addition, UUAA-MM can be implemented at the time of logging on to 5GS based on operator policy. In addition, UUAA-MM can also be implemented when requested from the operator and / or the UE has an aerial UE subscription in Access and Mobility SubscriptionData and provided by including CAA level UAVID in the Login Request message. In addition, without implementing UUAA-MM, the UE can be authenticated and / or authorized through PDU session establishment in UUAA-SM.
[0475] In addition, UUAA-MM may be an option. In addition, UUAA-MM may be implemented for UEs that request USS-based authentication and authorization of UAVs when logging into 5GS. In addition, UUAA-MM may be implemented by AMF. In addition, in the case where the UE has an over-the-air UE subscription through 5GS and the UE includes the CAA level UAV ID of the UAV in the login request message to provide, UUAA-MM may be implemented during UE login based on local network policy. In addition, UUAA-MM may also be implemented when the USS that authenticated the UAV performs re-authentication.
[0476] In addition, the UE may be authenticated and authorized by the USS using a certificate associated with the CAA level UAV ID and the CAA level UAV ID. In addition, during the implementation of UUAA-MM, the AMF may communicate with the USS via the UAS NF and may also transmit authentication messages between the UE and the UAS NF.
[0477] Next, each step of UUAA-MM is explained.
[0478] First, the UE performs a login procedure (S2400).
[0479] Next, a first communication is implemented between the UE, the AMF and the USS (S2402). In the first communication, messages used by the USS for authentication and authorization can be sent and received between the UE, the AMF and the USS.
[0480] Here, the UE and / or AMF can identify whether the UUAA-MM is successful through the message of the first communication. In other words, the UE and / or AMF can identify whether the authentication and authorization of the UAV is allowed through the message of the first communication.
[0481] Next, the AMF can perform the fifth condition determination. The fifth condition determination is used for the network (or AMF) to determine whether the UUAA-MM is successful. The AMF can start the fifth condition determination if it is true. Fig.12In addition, if the fifth condition is judged to be false, the AMF may start Fig.12 (B) non-login process (S2406).
[0482] It should be noted that the fifth condition judgment can be performed based on the reception of the message used in the first communication and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by AMF, etc.
[0483] For example, if UUAA-MM succeeds, the fifth condition may be true, and if UUAA-MM fails, the fifth condition may be false. Furthermore, if the identification information is allowed to be sent and received, the fifth condition may be true, and if the identification information is not allowed to be sent and received, the fifth condition may be false. It should be noted that the conditions for determining the truth or falsity of the fifth condition may not be limited to the above conditions.
[0484] In addition, the AMF can indicate the result of UUAA-MM to the UE through the process of implementing the truth or falsehood judgment based on the fifth condition.
[0485] In addition, each device can complete this process based on the implementation of the first communication and / or UE setting update process and / or non-login process.
[0486] In addition, the UE can Fig.12 In other words, the UE can identify the result of UUAA-MM by performing the (A) or (B) procedure in Fig.12 The UE may identify the result of the UUAA-MM based on the message received during the (A) or (B) process. In addition, the UE may identify the result of the UUAA-MM based on the completion of this process.
[0487] It should be noted that, in the case where authorization of C2 communication is performed during the UUAA-MM process, the UE may recognize that authorization of C2 communication and / or pairing of the UAV with the UAV-C and / or flight of the UAV are results of authorization.
[0488] The UE may prohibit the sending of MM messages and / or SM messages during the execution of the UUAA-MM procedure. In other words, the UE may control in the following manner: the sending of MM messages and / or SM messages is not performed until the first communication and / or UE setting update procedure and / or non-login procedure is completed. [3.2.7.2.UUAA-SM]
[0489] Next, use Fig.13, the UUAA-SM process is described. Hereinafter, the UUAA-SM process is also referred to as UUAA-SM or this process. This process may be a process implemented in PDU session establishment.
[0490] It should be noted that the messages sent and received in this process may be the same as the behaviors recorded in the chapter on the PDU session establishment process.
[0491] In addition, when the UE requests establishment of a PDU session, the PDU session may request UUAA authentication of the UAV.
[0492] In addition, when the UUAA is cancelled, all PDU sessions associated with the UAV can be released. In other words, when the authentication and authorization of the UAV are cancelled, all PDU sessions associated with the UAV can be released.
[0493] In addition, UUAA-SM can be implemented by SMF during PDU session establishment. In addition, UUAA-SM can be implemented based on SM subscription data from UDM and based on the service level element ID provided by the UE in the PDU session establishment request message.
[0494] Next, each step of UUAA-SM is explained.
[0495] First, the UE implements the PDU session establishment process. Specifically, the UE sends a PDU session establishment request message to the SMF (S2600).
[0496] Next, a second communication is implemented between the UE, the SMF and the USS (S2602). In the second communication, messages used by the USS for authentication and authorization may be sent and received between the UE, the SMF and the USS.
[0497] Here, the UE and / or SMF can identify whether the UUAA-SM is successful through the message of the second communication. In other words, the UE and / or SMF can identify whether the authentication and authorization of the UAV is allowed through the message of the second communication.
[0498] Next, SMF can perform the sixth condition determination. The sixth condition determination is used for the network (or SMF) to determine whether the UUAA-SM is successful. If the sixth condition determination is true, SMF sends Fig.13 (A) of the PDU session establishment acceptance message (S2604), on the contrary, when the sixth condition is judged to be false, send Fig.13 (B) PDU session establishment rejection message (S2606).
[0499] It should be noted that the sixth condition judgment can be performed based on the reception of the message used in the second communication and / or subscriber information and / or network capability information and / or operator policy and / or network status and / or user login information and / or context maintained by AMF, etc.
[0500] For example, if UUAA-SM succeeds, the sixth condition may be true, and if UUAA-SM fails, the sixth condition may be false. Furthermore, if the identification information is allowed to be sent and received, the sixth condition may be true, and if the identification information is not allowed to be sent and received, the sixth condition may be false. It should be noted that the conditions for determining the truth or falsity of the sixth condition may not be limited to the above conditions.
[0501] In addition, the SMF can indicate the result of UUAA-SM to the UE by sending a message based on the truth or falsity of the sixth condition.
[0502] In addition, each device can complete this process based on the implementation of the second communication and / or the sending and receiving of the PDU session acceptance message and / or the sending and receiving of the PDU session rejection message.
[0503] In addition, the UE can receive Fig.13 The UE may identify the result of UUAA-SM based on the completion of this process by sending a message (A) or (B).
[0504] It should be noted that, when authorization of C2 communication is performed during the UUAA-SM process, the UE can recognize that the authorization of C2 communication and / or the pairing of the UAV and the UAV-C and / or the flight of the UAV are the results of the authorization.
[0505] The UE may prohibit the sending of MM messages and / or SM messages during the execution of the UUAA-SM process. In other words, the UE may control in the following manner: not sending MM messages and / or SM messages until the second communication and / or PDU session establishment process is completed. [3.2.7.3.UUAA cancellation process]
[0506] Next, use Fig.14 , the UUAA revocation procedure is described. Hereinafter, the UUAA revocation procedure may also be referred to as the UUAA revocation (Revocation) or UAV authorization revocation (UAV authorization revocation) procedure or this procedure. This procedure may be a process implemented during the login process and / or the PDU session establishment.
[0507] In addition, this process may be a process initiated by the core network or USS. In addition, this process may be a process for the network or USS to cancel the authentication and authorization of the UAV for the UE.
[0508] Next, each step of this process is described.
[0509] First, a fourth communication is performed between the core network and the USS (S2800). In the fourth communication, a message for requesting cancellation of the UAV may be sent and received between the core network and the USS.
[0510] Next, the core network can start Fig.14 (A) process (S2802)(S2804), you can also start Fig.14 (B) process (S2806).
[0511] It should be noted that the core network can determine whether to implement the first communication based on the reception of the message used in the first communication and / or the subscriber information and / or the network capability information and / or the operator policy and / or the network status and / or the user's login information and / or the context maintained by the AMF. Fig.14 (A) process, or implementation Fig.14 (B) process.
[0512] For example, in the case of implementing UUAA-MM, it is possible to implement Fig.14 In addition, when implementing UUAA-SM, you can implement Fig.14 (B) process. It should be noted that the implementation Fig.14 The determination of which of (A) and (B) is to be selected may not be limited to the above-mentioned conditions.
[0513] In addition, the core network can Fig.14 The implementation of process (A) or (B) indicates to the UE the authentication of the UAV and the cancellation of the authorization.
[0514] In addition, each device may communicate based on the fourth and / or Fig.14 This process is completed by implementing process (A) or (B).
[0515] In addition, the UE may identify the authentication of the UAV and the revocation of authorization based on the completion of this procedure. [4. Implementation Method]
[0516] Next, each embodiment will be described. [4.1. First embodiment]
[0517] First, the first embodiment will be described. Hereinafter, the first embodiment may also be referred to as the present embodiment.
[0518] In this implementation, a PDU session change process or a PDU session release process may be implemented.
[0519] In this implementation, the first control message may be a PDU session change command message or a PDU session release command message.
[0520] In addition, in this embodiment, the UAV or UAV-C may be replaced by a UE. In addition, the UE may be replaced by a UAV or a UAV-C. In addition, each device may be a UAV and / or a UAV-C and / or a network.
[0521] In addition, in this embodiment, UAV can be replaced by UAV-C, and UAV-C can be replaced by UAV.
[0522] In addition, this embodiment may be supported in 5GS and / or EPS.
[0523] In addition, in this embodiment, UUAA-MM and / or UUAA-SM may be a state that has been implemented once. In addition, this embodiment may be implemented during the UUAA-MM or UUAA-SM or UUAA cancellation process.
[0524] In addition, in this embodiment, the UAV may be in a state where a PDU session for C2 communication is established between the UAV-C and / or the USS and / or the network, or may be in a state where a PDU session is not established.
[0525] In addition, in the present embodiment, the UAV is in a state where a communication path for direct C2 communication is established between the UAV and the UAV-C.
[0526] First, the network sends a first control message to the UAV. In addition, the network may send one or more of the tenth to twelfth and fifteenth to eighteenth identification information to the UAV. Here, the network may include one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the first control message.
[0527] Here, the network may indicate the content indicated by the identification information included in the first control message to the UAV by including one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the first control message. Furthermore, the network may allow the UAV to include the content indicated by the identification information included in the first control message by including one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the first control message. In addition, the network may indicate the content indicated by each identification information to the UAV by sending one or more of the tenth to twelfth and fifteenth to eighteenth identification information to the UAV.
[0528] Specifically, the network may instruct the UAV to cancel the authentication and / or authorization of direct C2 communication by sending the fifteenth identification information.
[0529] In addition, the network may indicate to the UAV to cancel the authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session by sending the sixteenth identification information. In addition, the network may include the fifteenth identification information and / or the sixteenth identification information in the service level AA container and send it to the UAV.
[0530] In addition, the network may indicate to the UAV the reason for canceling the authentication and / or authorization of direct C2 communication and / or C2 communication using the PDU session by sending the seventeenth identification information.
[0531] In addition, the network may indicate to the UAV a timer value of a grace time until the direct C2 communication and / or the PDU session for C2 communication is released by sending the eighteenth identification information.
[0532] In addition, the network may indicate to the UAV the content of each identification information included in the first control message by sending the first control message.
[0533] In addition, the network can indicate the content of each identification information to the UAV by sending each identification information.
[0534] It should be noted that the network can select and determine whether to include one or more of the tenth to twelfth and fifteenth to eighteenth identification information in the first control message based on the status of the UAV and / or the information received from the USS and / or the information received from the UAS-NF.
[0535] In addition, the network may determine whether to send the first control message and / or each identification information based on the state of the UAV and / or information received from the USS and / or information received from the UAS-NF, etc. In addition, the network may send the first control message and / or each identification information when receiving information indicating cancellation of authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session from the USS or UAS-NF.
[0536] Next, the UAV receives the first control message. In addition, the UAV may receive a first control message including one or more of the tenth to twelfth and fifteenth to eighteenth identification information from the network. In addition, the UAV may receive one or more of the tenth to twelfth and fifteenth to eighteenth identification information from the network.
[0537] Moreover, the UAV can store the identification information received together with the first control message based on the reception of the first control message, and can also identify the determination of the network.
[0538] Furthermore, when the UAV receives one or more of the tenth to twelfth and fifteenth to eighteenth identification information, it can identify the content indicated by the received identification information. Furthermore, when the UAV receives one or more of the tenth to twelfth and fifteenth to eighteenth identification information, it can identify that the content indicated by the identification information included in the first control message is allowed.
[0539] Here, the UAV may start the process of establishing direct C2 communication when receiving the tenth identification information. In other words, the UAV may recognize that the direct C2 communication is authenticated and / or authorized when receiving the tenth identification information, and start the process of establishing direct C2 communication.
[0540] In addition, the UAV may not start the process of establishing direct C2 communication when receiving the tenth identification information. In other words, the UAV may recognize that direct C2 communication is not authenticated and / or authorized when receiving the tenth identification information, and may not start the process of establishing direct C2 communication.
[0541] In addition, the UAV may start a direct C2 communication establishment process and / or a PDU session establishment process for C2 communication when receiving the eleventh identification information. In other words, the UAV may recognize that direct C2 communication and / or C2 communication using a PDU session is authenticated and / or authorized when receiving the eleventh identification information, and may start a direct C2 communication establishment process and / or a PDU session establishment process for C2 communication.
[0542] In addition, when the UAV receives the eleventh identification information, it may not start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication. In other words, when the UAV receives the eleventh identification information, it may recognize that direct C2 communication and / or C2 communication using PDU session is not authenticated and / or authorized, and does not start the establishment process of direct C2 communication and / or the PDU session establishment process for C2 communication.
[0543] In addition, when the UAV receives the twelfth identification information, it can also set the identification information of the UAV or UAV-C. In addition, when the UAV receives the twelfth identification information, it can delete the stored identification information of the UAV or UAV-C and store the received identification information of the UAV or UAV-C.
[0544] In addition, when the UAV receives the fifteenth identification information, it can recognize that the authentication and / or authorization of the direct C2 communication is cancelled. In addition, when the UAV receives the first control message, it can recognize that the authentication and / or authorization of the direct C2 communication is cancelled.
[0545] In addition, the UAV may also start the release process of the direct C2 communication when receiving the fifteenth identification information. In other words, the UAV may recognize that the authentication and / or authorization of the direct C2 communication is cancelled when receiving the fifteenth identification information, and start the release process of the direct C2 communication.
[0546] In addition, when the UAV receives the sixteenth identification information, it can recognize that the authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session is revoked. In addition, when the UAV receives the first control message, it can recognize that the authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session is revoked.
[0547] In addition, the UAV may start a release process of direct C2 communication and / or a PDU session release process for C2 communication when receiving the sixteenth identification information. In other words, the UAV may recognize that the authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session is canceled when receiving the sixteenth identification information, and start a release process of direct C2 communication and / or a PDU session release process for C2 communication.
[0548] In addition, when the UAV receives the seventeenth identification information, it can identify that the authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session is revoked. In addition, when the UAV receives the first control message, it can identify the reason why the authentication and / or authorization of direct C2 communication and / or C2 communication using PDU session is revoked.
[0549] In addition, the UAV, when receiving the eighteenth identification information, can identify a timer value indicating a grace period until the direct C2 communication and / or the PDU session for C2 communication is released. In addition, the UAV, when receiving the eighteenth identification information, can start the first timer using the timer value indicated by the eighteenth identification information. Moreover, when the first timer expires, the UAV can start a release process for the communication path for direct C2 communication. In addition, during the period until the first timer expires, the UAV can start a release process for the communication path for direct C2 communication.
[0550] Here, the first timer may be a timer for managing a grace time until the direct C2 communication and / or the PDU session for C2 communication is released. In addition, the first timer may also be a timer for managing the time of releasing the direct C2 communication and / or the PDU session for C2 communication. In addition, the first timer may be a timer for managing the timer value indicated by the eighteenth identification information.
[0551] In addition, when the UAV receives the first control message, it can identify that the authentication and / or authorization of the direct C2 communication is revoked. In addition, when the UAV receives the first control message, it can start the first timer using the timer value indicated by the eighteenth identification information. Moreover, when the first timer expires, the UAV can start the release process of the communication path for direct C2 communication. In addition, during the period until the first timer expires, the UAV can start the release process of the communication path for direct C2 communication. In addition, when the UAV receives the first control message, it can start the release process of the communication path for direct C2 communication. In addition, when the UAV receives the first control message, it can start the release process of the communication path for direct C2 communication, and identify that the authentication and / or authorization of the direct C2 communication is revoked.
[0552] It should be noted that the above-mentioned behavior of the UAV may be implemented after receiving the first control message. In addition, the above-mentioned behavior of the UAV may also be implemented after receiving one or more of the tenth to twelfth and fifteenth to eighteenth identification information.
[0553] In addition, when the UAV receives the first control message, it can identify the content of each identification information included in the first control message and implement the behavior when each identification information is received.
[0554] In addition, when the UAV receives each piece of identification information, it can identify the content of each piece of identification information. [4. Modifications]
[0555] The program that operates in the device according to one embodiment of the present invention may be a program that controls a central processing unit (CPU) or the like to enable a computer to function so as to implement the functions of the implementation method according to one embodiment of the present invention. The program or the information processed by the program is temporarily stored in a volatile memory such as a random access memory (RAM) or a non-volatile memory such as a flash memory, a hard disk drive (HDD) or other storage device system.
[0556] It should be noted that the program for realizing the functions of the implementation method involved in one scheme of the present invention may also be recorded in a computer-readable recording medium. This can be realized by reading the program recorded in the recording medium into a computer system and executing it. The "computer system" mentioned here refers to a computer system built into a device, and includes a computer system of hardware such as an operating system and peripherals. In addition, the "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or other computer-readable recording media.
[0557] In addition, each functional block or each feature of the device used in the above-mentioned embodiments can be installed or executed in a circuit, such as an integrated circuit or multiple integrated circuits. Circuits designed in a manner to perform the functions described in this specification may include: a general-purpose processor, a digital signal processor (DSP), an integrated circuit for a specific purpose (ASIC), a field programmable gate array (FPGA) or other programmable logic elements, discrete gates or transistor logic, discrete hardware parts, or a combination thereof. The general-purpose processor may be a microprocessor, or it may be a processor, controller, microcontroller, or state machine of the previous type. The aforementioned circuit may be composed of digital circuits or analog circuits. In addition, in the case where integrated circuit technology that replaces the current integrated circuit appears due to advances in semiconductor technology, one or more schemes of the present invention may also use new integrated circuits based on this technology.
[0558] It should be noted that the present invention is not limited to the above-mentioned embodiments. In the embodiments, an example of a device is described, but the present invention is not limited thereto and can be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning, washing equipment, air conditioning equipment, office equipment, vending machines, other life equipment, and other terminal devices or communication devices.
[0559] The embodiments of the present invention are described in detail with reference to the accompanying drawings, but the specific configuration is not limited to the present embodiment, and also includes design changes within the scope of the gist of the present invention. In addition, the present invention can be variously modified within the scope indicated by the claims, and the embodiments obtained by appropriately combining the technical solutions disclosed in different embodiments are also included in the technical scope of the present invention. In addition, it also includes a configuration obtained by replacing the elements that have the same effect as the elements recorded in the above-mentioned embodiments with each other. (Cross-reference of related applications) This application claims the benefit of priority to Japanese patent application No. 2022-072932 filed on April 27, 2022, the entire contents of which are incorporated herein by reference. Description of Reference Numerals 1: Mobile communication system 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 user equipment UE, characterized in that: The UE includes a transceiver unit and a control unit. The UE establishes a communication path for a first direct C2 communication with the UAV-C, The transceiver receives a PDU session change command message including first identification information from the network, The first identification information is information indicating cancellation of authentication and / or authorization of the communication path used for the first direct C2 communication, The control unit receives the PDU session change command message, identifying that authentication and / or authorization of the communication path for said first direct C2 communication is revoked, A release process of the communication path used for the first direct C2 communication is started.
2. The UE according to claim 1, characterized in that The transceiver receives a PDU session change command message including second identification information from the network, The second identification information is a timer value indicating a grace period until the communication path used for the first direct C2 communication is released, and the control unit receives the PDU session change command message, starting a timer using the timer value, When the timer expires, a release process of the communication path used for the first direct C2 communication is started.
Citation Information
Patent Citations
Lithium secondary battery
JP2022072932A
