Patent Application
20250185089
The present invention relates to a User Equipment (UE).
In the 3rd Generation Partnership Project (3GPP), system architecture of a 5G System (5GS), which is a fifth generation (5G) mobile communication system, has been studied, and discussions are underway to support new procedures and new functions (see NPLs 1 to 3). In Release 17 of the 5G standard, a mobile communication system for drones is discussed (see NPL 4).
For the 5G System (5GS), a 5G Core Network (5GCN) which is a new core network has been studied for the purpose of providing various services. Further, as a communication device for operating an Unmanned Aerial Vehicle (UAV), a communication device using a 5GS has also been studied.
At present, in the communication device of the UAV using the 5GS, the UAV is about to be specified not only for communication using the 5GS but also for direct communication with the UAV controller.
On the other hand, with respect to communication between the UAV and the UAV controller, a method for establishing a communication path and a method for authentication and/or authorization are not clear.
An aspect of the present invention has been made in view of the above circumstances, and an object thereof is to indicate and clarify information transmitted and/or received between a UAV and a UAV controller to and/or from a network, and behaviors of the UAV, the UAV controller, and the network in a case that the UAV and/or the UAV controller transmits and/or receives a message.
An aspect of the present invention provides a User Equipment (UE) including a controller, a transmission and/or reception unit, and a storage unit, wherein the transmission and/or reception unit transmits, to a core network, a registration request message including 1st identification information, and receives, from the core network, a registration accept message including 2nd identification information, the 1st identification information is information indicating whether direct C2 communication is supported, the 2nd identification information is information indicating that the direct C2 communication is authenticated and/or authorized, and the controller recognizes that the direct C2 communication is authenticated and/or authorized, based on reception of the registration accept message, and initiates an establishment procedure for the direct C2 communication.
An aspect of the present invention allows clarification of information transmitted and/or received to and/or from a network by a UAV and/or a UAV controller, and behaviors of the UAV, the UAV controller, and the network in a case that the UAV and/or the UAV controller transmits and/or receives a message.
A preferred embodiment for carrying out an aspect of the present invention will be described below with reference to the drawings. Note that an embodiment of a mobile communication system to which an aspect of the present invention is applied will be described as an example in the present embodiment.
First,
In the following description, the reference numerals of these apparatuses and functions may be omitted, as in UE, an access network_A, a core network_A, a PDN, an access network_B, a core network_B, a DN, and the like.
In addition,
In the following description, the reference numerals of these apparatuses and functions may be omitted as in UE, an E-UTRAN, an MME, an SGW, a PGW-U, a PGW-C, a PCRF, an HSS, a 5G AN, an AMF, a UPF, an SMF, a PCF, a UDM, an N3IWF, and the like.
Note that an Evolved Packet System (EPS) that is a 4G system includes an access network_A and a core network_A and may further include UE and/or a PDN. In addition, a 5G System (5GS) that is a 5G system includes UE, an access network_B, and a core network_B and may further include a DN.
The UE is an apparatus that can be connected to a network service over 3GPP access (also referred to as a 3GPP access network or a 3GPP AN) and/or non-3GPP access (also referred to as a non-3GPP access network or a non-3GPP AN). The UE may be a terminal apparatus capable of performing radio communication, such as a mobile phone or a smartphone, and may be a terminal apparatus that can be connected to both the EPS and the 5GS. The UE may include a Universal Integrated Circuit Card (UICC) and an Embedded UICC (eUICC). Note that the UE may be referred to as user equipment or a terminal apparatus.
In addition, the access network_A corresponds to an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and/or a wireless LAN access network. In the E-UTRAN, one or multiple evolved Node-B (eNBs) 45 are deployed. Note that, in the following description, the reference numeral of the eNB 45 may be omitted as in eNB. In addition, in a case that there are multiple eNBs, the eNBs are connected to each other via, for example, an X2 interface. In addition, one or multiple access points are deployed on the wireless LAN access network.
In addition, the access network_B corresponds to a 5G access network (5G AN). The 5G AN includes an NG Radio Access Network (NG-RAN) and/or a non-3GPP access network. One or multiple NR Node-Bs (gNBs) 122 are deployed on the NG-RAN. Note that in the following description, the symbol for the gNB 122 may be omitted as a gNB. The gNB is a node that provides a New Radio (NR) user plane and control plane to the UE, and is connected to a 5GCN via an NG interface (including an N2 interface or an N3 interface). In other words, the gNB is a base station apparatus newly designed for the 5GS and has functions different from those of the base station apparatus (eNB) used in the EPS that is a 4G system. In addition, in a case that there are multiple gNBs, the gNBs are connected to each other via, for example, an Xn interface.
In addition, a non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network may be a non-3GPP access network that does not manage security on the access network, for example, a public wireless LAN. On the other hand, the trusted non-3GPP access network may be an access network defined by the 3GPP and may include a trusted non-3GPP access point (TNAP) and a trusted non-3GPP Gateway function (TNGF).
In addition, in the following description, the E-UTRAN and the NG-RAN may be referred to as 3GPP access. In addition, the wireless LAN access network and the non-3GPP AN may be referred to as non-3GPP access. In addition, nodes deployed on the access network_B may also be collectively referred to as NG-RAN nodes.
In addition, in the following description, the access network_A, and/or the access network_B, and/or an apparatus included in the access network_A, and/or an apparatus included in the access network_B may be referred to as an access network or an access network apparatus.
The core network_A corresponds to an Evolved Packet Core (EPC). In the EPC, for example, a Mobility Management Entity (MME), a Serving Gateway (SGW), a Packet Data Network Gateway (PGW)-U, a PGW-C, a Policy and Charging Rules Function (PCRF), a Home Subscriber Server (HSS), and the like are deployed.
In addition, the core network_B corresponds to a 5G Core Network (5GCN). An Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), a Unified Data Management (UDM), and the like are deployed on the 5GCN. Here, the 5GCN may be referred to as a 5GC.
In addition, in the following description, the core network_A, and/or the core network_B, an apparatus included in the core network_A, and/or an apparatus included in the core network_B may be referred to as a core network, a core network apparatus, or an intra-core network apparatus.
The core network (the core network_A and/or the core network_B) may refer to an IP mobile communication network operated by a Mobile Network Operator (MNO) connecting the access network (the access network_A and/or the access network_B) and the PDN and/or the DN, a core network for a mobile network operator that operates and manages the mobile communication system 1, or a core network for a virtual mobile communication operator and a virtual mobile communication service provider such as a Mobile Virtual Network Operator (MVNO) and a Mobile Virtual Network Enabler (MVNE).
In addition, although
In addition, in the following, at least some of the access network_A, the core network_A, the PDN, the access network_B, the core network_B, and the DN, and/or one or multiple apparatuses included in these may be referred to as a network or a network apparatus. In other words, the expression that “the network and/or the network apparatus transmits and/or receives a message and/or performs a procedure” means that “at least some of the access network_A, the core network_A, the PDN, the access network_B, the core network_B, and the DN, and/or one or multiple apparatuses included in these transmit and/or receive a message and/or perform a procedure”.
In addition, the UE can be connected to the access network. In addition, the UE can be connected to the core network over the access network. Furthermore, the UE can be connected to the PDN or the DN over the access network and the core network. In other words, the UE can transmit and/or receive (communicate) user data to and/or from the PDN or the DN. In a case that user data is transmitted and/or received, not only Internet Protocol (IP) communication but also non-IP communication may be used.
Here, IP communication refers to data communication using an IP, and data is transmitted and/or received using IP packets. Each IP packet includes an IP header and a payload part. In the payload part, data transmitted and/or received by the apparatuses and functions included in the EPS and the apparatuses and functions included in the 5GS may be included. In addition, non-IP communication refers to data communication performed using no IP, in which data is transmitted and/or received in a form different from the structure of an IP packet. For example, non-IP communication may be data communication implemented through transmission and/or reception of application data to which an IP header is not added, or user data transmitted and/or received by the UE may be transmitted and/or received with another header such as a MAC header and an Ethernet (trade name) frame header added.
In addition, apparatuses which are not illustrated in
Here, the AUSF is a core network apparatus provided with an authentication function for 3GPP access and non-3GPP access. Specifically, the AUSF is a network function unit that receives an authentication request for 3GPP access and/or non-3GPP access from the UE and performs an authentication procedure.
The AAA server is an apparatus that is connected directly to the AUSF or indirectly to the AUSF via another network apparatus and has authentication, authorization, and billing functions. The AAA server may be a network apparatus within the core network. Note that the AAA server may not be included in the core network_A and/or the core network_B and may be included in the PLMN. In other words, the AAA server may be a core network apparatus or may be an apparatus outside the core network. For example, the AAA server may be a server apparatus within the PLMN managed by a 3rd party.
Note that, although each of the apparatuses and functions is illustrated one by one for simplicity in
A UPF_A 235 is connected to the DN, the SMF, other UPFs and the access network. The UPF_A 235 may play roles of an anchor to intra-RAT mobility or inter-RAT mobility, Packet routing & forwarding, an Uplink Classifier (UL CL) function to support routing of multiple traffic flows for one DN, a Branching point function to support a multi-homed PDU session, QoS processing for a user plane, verification of uplink traffic, buffering of downlink packets, a function of triggering Downlink Data Notification, and the like. Furthermore, the UPF_A 235 may be a relay apparatus that transfers the user data as a gateway between the DN and the core network_B 190. Note that the UPF_A 235 may serve as a gateway for IP communication and/or non-IP communication. Furthermore, the UPF_A 235 may have a function of transferring IP communication or a function to perform conversion between non-IP communication and IP communication. The multiple gateways deployed may serve as gateways for connecting the core network_B 190 with a single DN. Note that the UPF_A 235 may have connectivity with another NF or may be connected to each apparatus via another NF.
Note that, a UPF_C 239 (also referred to as a branching point or an uplink classifier), which is a UPF different from the UPF_A 235, may be present as an apparatus or NF between the UPF_A 235 and the access network. With the UPF_C 239 present, the PDU session between the UE and the DN is established via the access network, the UPF_C 239, and the UPF_A 235.
The UPF 130 may be an apparatus similar to the UPF_A 235. The UPF 130 and the UPF_A 235 may be described with the symbols thereof omitted, like the UPF.
Next, a configuration of each apparatus (the UE, and/or the access network apparatus, and/or the core network apparatus) used in each embodiment will be described with reference to the drawings. Note that each apparatus may be configured as physical hardware, may be configured as logical (virtual) hardware configured in general-purpose hardware, or may be configured as software. In addition, at least a part (including all) of the functions of each apparatus may be configured as physical hardware, logical hardware, or software.
Note that each storage unit (a storage unit_A 340, a storage unit_A 440, a storage unit_B 540, a storage unit_A 640, and a storage unit_B 740) in each apparatus and function to be described later includes, for example, a semiconductor memory, a Solid State Drive (SSD), a Hard Disk Drive (HDD), or the like. In addition, each storage unit can store not only information originally configured at the time of being shipped, but also various pieces of information transmitted and/or received to and/or from apparatuses and functions (for example, the UE, and/or the access network apparatus, and/or the core network apparatus, and/or the PDN, and/or the DN) other than the apparatus and functions of each storage unit. In addition, each storage unit can store identification information, control information, flags, parameters, and the like included in a control message transmitted and/or received in various communication procedures to be described later. In addition, each storage unit may store these pieces of information for each UE. In addition, in a case that each storage unit performs interworking between the 5GS and the EPS, each storage unit can store a control message and user data transmitted and/or received to and/or from the apparatuses and functions included in the 5GS and/or the EPS. In this case, not only data transmitted and/or received over the N26 interface but also data transmitted and/or received without using the N26 interface can be stored.
First, an apparatus configuration example of the User Equipment (UE) will be described with reference to
The controller_A 300 is a function unit that controls overall operations and functions of the UE. The controller_A 300 reads and performs various programs stored in the storage unit_A 340 as necessary, and thereby implements various types of processing in the UE.
The transmission and/or reception unit_A 320 is a function unit that performs radio communication with a base station apparatus (the eNB or the gNB) within the access network via the antenna. In other words, with the use of the transmission and/or reception unit_A 320, the UE can transmit and/or receive user data and/or control information to and/or from the access network apparatus, and/or the core network apparatus, and/or the PDN, and/or the DN.
To provide detailed description with reference to
The storage unit_A 340 is a function unit that stores programs, user data, control information, and the like necessary for each operation of the UE.
Next, an apparatus configuration example of the gNB will be described with reference to
The controller_B 500 is a function unit that controls overall operations and functions of the gNB. The controller_B 500 reads and performs various programs stored in the storage unit_B 540 as necessary, and thereby implements various types of processing in the gNB.
The network connection unit_B 520 is a function unit for the gNB to communicate with the AMF and/or the UPF. In other words, with the use of the network connection unit_B 520, the gNB can transmit and/or receive user data and/or control information to and/or from the AMF and/or the UPF.
The transmission and/or reception unit_B 530 is a function unit that performs radio communication with the UE via the antenna 510. In other words, with the use of the transmission and/or reception unit_B 530, the gNB can transmit and/or receive user data and/or control information to and/or from the UE.
To provide detailed description with reference to
Next, an apparatus configuration example of the AMF will be described with reference to
The controller_B 700 is a function unit that controls overall operations and functions of the AMF. The controller_B 700 reads and performs various programs stored in the storage unit_B 740 as necessary, and thereby implements various types of processing in the AMF.
The network connection unit_B 720 is a function unit for the AMF to connect to the base station apparatus (gNB) within the 5G AN, and/or the SMF, and/or the PCF, and/or the UDM, and/or an SCEF. In other words, with the use of the network connection unit_B 720, the AMF can transmit and/or receive user data and/or control information to and/or from the base station apparatus (gNB) in the 5G AN, and/or the SMF, and/or the PCF, and/or the UDM, and/or the SCEF.
To provide detailed description with reference to
The storage unit_B 740 is a function unit that stores programs, user data, control information, and the like necessary for each operation of the AMF.
Note that the AMF has a function of exchanging a control message with the RAN using the N2 interface, a function of exchanging a NAS message with the UE using the N1 interface, a function of performing encryption and integrity protection of a NAS message, a Registration management (RM) function, a Connection management (CM) function, a Reachability management function, a Mobility management function for the UE or the like, a function of transferring a Session Management (SM) message between the UE and the SMF, an Access Authentication (Access Authorization) function, a security anchor function (Security Anchor Functionality (SEA)), a Security Context Management (SCM) function, a function of supporting the N2 interface for a Non-3GPP Interworking Function (N3IWF), a function of supporting transmission and/or reception of a NAS signal to an/or from the UE via the N3IWF, a function of authenticating the UE connected via the N3IWF, and the like.
In addition, in registration management, an RM state for each piece of UE is managed. The RM state may be synchronized between the UE and the AMF. The RM state includes a deregistered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, because the UE is not registered with the network, the AMF is in a state of being unable to reach the UE, because a UE context in the AMF does not have location information and routing information that are valid for the UE. In addition, in the RM-REGISTERED state, because the UE is registered in the network, the UE can receive a service that requires registration with the network. Note that the RM state may be referred to as a 5GMM state. In this case, the RM-DEREGISTERED state may be referred to as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be referred to as a 5GMM-REGISTERED state.
In other words, 5GMM-REGISTERED may be a state in which each apparatus establishes a 5GMM context, or may be a state in which each apparatus establishes a PDU session context. Note that, in a case that each apparatus is in 5GMM-REGISTERED, the UE_A 10 may start transmission and/or reception of user data and a control message, or may respond to paging. Furthermore, in a case that each apparatus is in 5GMM-REGISTERED, the UE_A 10 may perform a registration procedure other than a registration procedure for initial registration, and/or a service request procedure.
In addition, 5GMM-DEREGISTERED may be a state in which each apparatus does not establish the 5GMM context, may be a state in which the location information of the UE_A 10 is not known to the network, or may be a state in which the network is unable to reach the UE_A 10. Note that, in a case that each apparatus is in 5GMM-DEREGISTERED, the UE_A 10 may initiate the registration procedure, or may perform the registration procedure to thereby establish the 5GMM context.
In addition, in connection management, a CM state for each UE is managed. The CM state may be synchronized between the UE and the AMF. The CM state includes a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state, but does not have NAS signalling connection established with the AMF via the N1 interface. In addition, in the CM-IDLE state, the UE has neither connection of the N2 interface (N2 connection) nor connection of the N3 interface (N3 connection). On the other hand, in the CM-CONNECTED state, the UE has NAS signalling connection established with the AMF via the N1 interface. In addition, in the CM-CONNECTED state, the UE may have connection of the N2 interface (N2 connection) and/or connection of the N3 interface (N3 connection).
Furthermore, in connection management, management may be performed separately for the CM state in 3GPP access and the CM state in non-3GPP access. In this case, the CM state in 3GPP access may include a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over 3GPP access). Furthermore, the CM state in non-3GPP access may include a non-connected state in non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state in non-3GPP access (CM-CONNECTED state over non-3GPP access). Note that the non-connected state may be referred to as an idle mode, and a connected state mode may be referred to as a connected mode.
Note that the CM state may be referred to as a 5GMM mode. In this case, the non-connected state may be referred to as a 5GMM non-connected mode (5GMM-IDLE mode), and the connected state may be referred to as a 5GMM connected mode (5GMM-CONNECTED mode). In addition, the non-connected state in 3GPP access may be referred to as a 5GMM non-connected mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access may be referred to as a 5GMM connected mode in 3GPP access (5GMM-CONNECTED mode over 3GPP access). In addition, the non-connected state in non-3GPP access may be referred to as a 5GMM non-connected mode in non-3GPP access (5GMM-IDLE mode over non-3GPP access), and the connected state in non-3GPP access may be referred to as a 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). Note that the 5GMM non-connected mode may be referred to as an idle mode, and the 5GMM connected mode may be referred to as a connected mode.
In addition, one or multiple AMFs may be deployed within the core network_B. The AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). In addition, the AMF may be a common CP function (Common Control Plane Network Function (CPNF) (CCNF)) shared among multiple NSIs.
Note that, in a case that the UE connects to the 5GS over non-3GPP access, the N3IWF is an apparatus and/or a function deployed between non-3GPP access and the 5GCN.
Next, an apparatus configuration example of the SMF will be described with reference to
The controller_B 700 is a function unit that controls overall operations and functions of the SMF. The controller_B 700 reads and performs various programs stored in the storage unit_B 740 as necessary, and thereby implements various types of processing in the SMF.
The network connection unit_B 720 is a function unit for the SMF to connect to the AMF, and/or the UPF, and/or the PCF, and/or the UDM. In other words, with the use of the network connection unit_B 720, the SMF can transmit and/or receive user data and/or control information to and/or from the AMF, and/or the UPF, and/or the PCF, and/or the UDM.
To provide detailed description with reference to
The storage unit_B 740 is a function unit that stores programs, user data, control information, and the like necessary for each operation of the SMF.
The SMF has a Session Management function for managing establishment, modification, and release of a PDU session, a function of IP address allocation to the UE and management thereof, a function of selection and control of the UPF, a function of configuring the UPF for routing traffic to an appropriate destination (transmission destination), a function of transmitting and/or receiving an SM part of a NAS message, a function of signalling arrival of downlink data (Downlink Data Notification), a function of providing SM information specific to an AN (for each AN) that is transmitted to the AN through the AMF over the N2 interface, a function of determining a Session and Service Continuity mode (SSC mode) for a session, a roaming function, and the like.
Next, an apparatus configuration example of the UPF will be described with reference to
The controller_B 700 is a function unit that controls overall operations and functions of the UPF. The controller_B 700 reads and performs various programs stored in the storage unit_B 740 as necessary, and thereby implements various types of processing in the UPF.
The network connection unit_B 720 is a function unit for the UPF to connect to the base station apparatus (gNB) within the 5G AN, and/or the SMF, and/or the DN. In other words, with the use of the network connection unit_B 720, the UPF can transmit and/or receive user data and/or control information to and/or from the base station apparatus (gNB) within the 5G AN, and/or the SMF, and/or the DN.
To provide detailed description with reference to
The storage unit_B 740 is a function unit that stores programs, user data, control information, and the like necessary for each operation of the UPF.
The UPF has a function as an anchor point for intra-RAT mobility or inter-RAT mobility, a function as an external PDU session point to be mutually connected with the DN (that is, a function of transferring user data as a gateway between the DN and the core network_B), a function of routing and transferring packets, an Uplink Classifier (UL CL) function of supporting routing of multiple traffic flows for one DN, a Branching point function of supporting a multi-homed PDU session, a Quality of Service (QOS) processing function for the user plane, a function of verifying uplink traffic, a function of triggering buffering of downlink packets and Downlink Data Notification, and the like.
In addition, the UPF may be a gateway for IP communication and/or non-IP communication. In addition, the UPF may have a function of transferring IP communication, or a function of conversion between non-IP communication and IP communication. Furthermore, multiple deployed gateways may be gateways for connecting the core network_B and a single DN. Note that the UPF may have connectivity with another NF, and may be connected to each apparatus via another NF.
Note that a user plane refers to user data that is transmitted and/or received between the UE and a network. The user plane may be transmitted and/or received using a PDN connection or a PDU session. Furthermore, in a case of the EPS, the user plane may be transmitted and/or received using an LTE-Uu interface, and/or an S1-U interface, and/or an S5 interface, and/or an S8 interface, and/or an SGi interface. Furthermore, in a case of the 5GS, the user plane may be transmitted and/or received over the interface between the UE and the NG RAN, and/or the N3 interface, and/or the N9 interface, and/or the N6 interface. The user plane may be hereinafter referred to as a U-Plane.
In addition, a control plane refers to a control message that is transmitted and/or received in order to perform communication control of the UE or the like. The control plane may be transmitted and/or received using Non-Access-Stratum (NAS) signalling connection between the UE and the MME. In addition, in a case of the EPS, the control plane may be transmitted and/or received using the LTE-Uu interface and an S1-MME interface.
Furthermore, in a case of the 5GS, the control plane may be transmitted and/or received using the interface between the UE and the NG RAN and the N2 interface. The control plane may be hereinafter referred to as a control plane, or may be hereinafter referred to as a C-Plane.
Furthermore, the U-Plane (User Plane (UP)) may be a communication path for transmitting and/or receiving user data, and may include multiple bearers. Furthermore, the C-Plane (Control Plane (CP)) may be a communication path for transmitting and/or receiving a control message, and may include multiple bearers.
Next, other apparatuses and/or functions will be described.
The PCF has a function such as a function of providing policy rules.
The UDM includes an authentication credential processing function, a user identification processing function, an access authentication function, a registration/mobility management function, a subscriber information management function, and the like.
The PCRF is connected to the PGW and/or the PDN and has a function such as a function of performing QoS management for data delivery. The PCRF performs, for example, QoS management for a communication path between the UE_A 10 and the PDN. The PCRF may also be an apparatus that creates and/or manages a Policy and Charging Control (PCC) rule and/or a routing rule that each apparatus uses in a case of transmitting and/or receiving user data.
The HSS is connected to the MME and/or the SCEF and has a function such as a function of managing subscriber information. The subscriber information of the HSS is referred to, for example, in a case of access control of the MME. The HSS may also be connected to a location management apparatus different from the MME.
Next, terms, identification information, and procedures, at least one of which will be used in the embodiments, will be described in advance.
First, highly technical terms and identification information used in procedures which will be used in the embodiments will be described in advance.
A network refers to at least some of the access network_B, the core network_B, and the DN. One or multiple apparatuses included in at least a part of the access network_B, the core network_B, and the DN may be referred to as a network or a network apparatus. In other words, “a network transmits and/or receives a message and/or performs processing” may mean “an apparatus (a network apparatus and/or a control apparatus) in the network transmits and/or receives the message and/or performs the processing”. Conversely, “an apparatus in a network transmits and/or receives a message and/or performs processing” may mean “the network transmits and/or receives the message and/or performs the processing”.
A session management (SM) message (also referred to as a Non-Access-Stratum (NAS) SM message) may be a NAS message used in a procedure for SM, or may be a control message transmitted and/or received between the UE_A 10 and the SMF_A 230 via the AMF_A 240. Furthermore, the SM message may include a PDU session establishment request message, a PDU session establishment accept message, a PDU session reject message (PDU session establishment reject message), a PDU session modification request message, a PDU session modification command message, a PDU session modification completion message (PDU session modification complete), a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release completion message, and the like. The procedure for SM or the SM procedure may include a PDU session establishment procedure, a PDU session modification procedure, and a PDU session release procedure (UE-requested PDU session release procedure). Note that each procedure may be a procedure initiated by the UE or may be a procedure initiated by the NW.
A Mobility management (MM) message (also referred to as a NAS MM message) may be a NAS message used in a procedure for MM, or may be a control message transmitted and/or received between the UE_A 10 and the AMF_A 240. Furthermore, the MM message may include a Registration request message, a Registration accept message, a Registration reject message, a De-registration request message, a De-registration accept message, a configuration update command message, a configuration update completion message, a Service request message, a Service accept message, a Service reject message, a Notification message, a Notification response message, and the like. The procedure for MM or the MM procedure may include a Registration procedure, a De-registration procedure, a Generic UE configuration update procedure, an authentication and/or authorization procedure, a Service request procedure, a Paging procedure, and a Notification procedure.
A 5G System (5GS) service may be a connection service provided using the core network_B 190. In addition, the 5GS service may be a service different from an EPS service, or may be a service similar to the EPS service.
A non 5GS service may be a service other than the 5GS service and may include an EPS service and/or a non EPS service.
A Packet Data Network (PDN) type indicates a type of PDN connection and includes IPv4, IPv6, IPv4v6, and non-IP. In a case that IPv4 is specified, it indicates that transmission and/or reception of data is performed using IPv4. In a case that IPv6 is specified, it indicates that transmission and/or reception of data is performed using IPv6. In a case that IPv4v6 is specified, it indicates that transmission and/or reception of data is performed using IPv4 or IPv6. In a case that non-IP is specified, it indicates that communication is performed using a communication method other than the IP, not communication using the IP.
Although a Protocol Data Unit/Packet Data Unit (PDU) session can be defined as a relationship between the DN that provides a PDU connectivity service and the UE, the PDU session may be connectivity established between the UE and an external gateway. In the 5GS, the UE establishes a PDU session via the access network_B and the core network_B, and can thereby perform transmission and/or reception of user data to and/or from the DN by using the PDU session. Here, the external gateway may be a UPF, an SCEF, or the like. The UE can perform transmission and/or reception of user data to and/or from an apparatus deployed in the DN, such as an application server, by using the PDU session. Note that each apparatus (the UE, and/or the access network apparatus, and/or the core network apparatus) may associate one or multiple pieces of identification information with a PDU session for management. Note that these pieces of identification information may include one or multiple of a DNN, a QoS rule, a PDU session type, application identification information, NSI identification information, access network identification information, and an SSC mode, and may further include other pieces of information. In addition, in a case that multiple PDU sessions are established, pieces of identification information associated with the PDU sessions may have the same or different contents.
The Data Network Name (DNN) may be identification information for identifying the core network and/or an external network such as the DN. Further, the DNN can also be used as information for selecting a gateway such as a PGW/UPF connecting the core network_B 190. In addition, the DNN may correspond to an Access Point Name (APN).
A Protocol Data Unit/Packet Data Unit (PDU) session type indicates a type of PDU session and includes IPv4, IPv6, Ethernet, and Unstructured. In a case that IPv4 is specified, it indicates that transmission and/or reception of data is performed using IPv4. In a case that IPv6 is specified, it indicates that transmission and/or reception of data is performed using IPv6. In a case that Ethernet is specified, it indicates that transmission and/or reception of an Ethernet frame is performed. Alternatively, Ethernet may indicate that communication using the IP is not performed. In a case that Unstructured is specified, it indicates that data is transmitted and/or received to and/or from an application server in the DN or the like by using a Point-to-Point (P2P) tunneling technique. For the P2P tunneling technique, for example, a UDP/IP encapsulation technique may be used. Note that the PDU session type may include the IP, in addition to the above. The IP can be specified in a case that the UE can use both of IPv4 and IPv6.
The Public land mobile network (PLMN) is a communication network that provides mobile radio communication services. The PLMN is a network managed by an operator who is a network operator, and the operator can be identified by a PLMN ID. A PLMN that matches a Mobile Network Code (MNC) and a Mobile Country Code (MCC) of an International Mobile Subscriber Identity (IMSI) of the UE may be a Home PLMN (HPLMN). Furthermore, the UE may hold, in the USIM, an Equivalent HPLMN list for identifying one or multiple Equivalent HPLMNs (EPLMNs). A PLMN different from the HPLMN and/or the EPLMN may be a VPLMN (Visited PLMN). A PLMN with which the UE has successfully registered may be a Registered PLMN (RPLMN).
A tracking area is a single or multiple ranges that can be expressed using location information of the UE_A 10 managed by the core network. Note that the tracking area may include multiple cells. Furthermore, the tracking area may be a range in which a control message such as paging is broadcast, or may be a range in which the UE_A 10 can move without performing a handover procedure. Furthermore, the tracking area may be a routing area, may be a location area, or may be any area similar to these. The tracking area may be hereinafter a TA. The tracking area may be identified by a Tracking Area Identity (TAI) including a Tracking area code (TAC) and a PLMN.
The Registration area is a set of one or multiple TAs allocated to the UE by the AMF. Note that, while moving within one or multiple TAs included in a registration area, the UE_A 10 may be able to move without transmitting and/or receiving a signal for updating the tracking area. In other words, the registration area may be an information group indicating an area in which the UE_A 10 can move without performing a tracking area update procedure. The registration area may be identified by a TAI list configured by one or multiple TAIs.
A UE ID is information for identifying the UE. The UE ID may be a Subscription Concealed Identifier (SUCI), or a Subscription Permanent Identifier (SUPI), or a Globally Unique Temporary Identifier (GUTI), or an International Mobile Subscriber Identity (IMEI), or an IMEI Software Version (IMEISV), or a Temporary Mobile Subscriber Identity (TMSI), for example. Alternatively, the UE ID may be other information configured by an application or within the network. Moreover, the UE ID may be information for identifying the user.
An Always-on PDU session is a PDU session for which user plane resources need to be activated each time a UE transitions from a 5GMM-IDLE state to a 5GMM-CONNECTED state. The UE can request a core network and/or a core network apparatus to establish a PDU session as an Always-on PDU session based on an indication from a higher layer. The core network and/or core network apparatus determines whether a PDU session can be established as an Always-on PDU session. Here, establishment of the Always-on PDU session may mean establishment of a PDU session for C2 communication. Further establishing an Always-on PDU session may mean establishing a PDU session that handles a QoS flow for the C2 communication. Here, the 5GMM-IDLE state may be a CM-IDLE state. The 5GMM-CONNECTED state may be a CM-CONNECTED state. The core network apparatus that determines whether a PDU session can be established as an Always-on PDU session may be an SMF.
A Service-level-AA container Information Element (IE) is an information element for transferring information for authentication and authorization between the UE and the network to the higher layer. The Service-level-AA container information element may include a Service-level device ID, and/or a Service-level-AA server address, and/or a Service-level-AA payload, and/or a Service-level-AA response. Further, the Service-level-AA container information element may include a C2 authorization result, and/or C2 session security information, and/or identification information of UAV-C to pair, and/or flight authorization information. Further, the Service-level-AA container information element may include a Service-level-AA pending indication. Note that the Service-level-AA container information element may be referred to as a Service-level-AA container.
The Service-level device ID is an information element for carrying an identity required for authentication and authorization by an external DN. The Service-level device ID may be included in the Service-level-AA container information element. The service-level device ID may include a CAA-level UAV ID.
The Service-level-AA server address is an information element for carrying an address of a service level authentication and authorization server. The Service-level-AA server address may also be included in the Service-level-AA container information element. The Service-level-AA server address may include a USS address.
Service-level-AA payload is an information element for carrying a payload for authentication and authorization between the UE and a service-level-AA server to the higher layer. The Service-level-AA payload may be included in the Service-level-AA container information element. The Service-level-AA payload may include a UUAA aviation payload.
The Service-level-AA response is an information element for providing information related to a service level authentication and authorization request. Specifically, the Service-level-AA response is an information element indicating that the authentication and authorization request to a service level authentication server has succeeded or not succeeded. The Service-level-AA response may also be included in the Service-level-AA container information element.
The C2 authorization result may be a result of authorization for the C2 communication. To be specific, the C2 authorization result may be information indicating a failure or a success in C2 communication authorization.
The result of the authorization for the C2 communication may include a result of the authorization for direct C2 communication. In this case, the C2 authorization result may be information indicating a success in the authorization for the C2 communication using the PDU session, a success in the authorization for the direct C2 communication, or a success in the authorization for both the C2 communication and the direct C2 communication, or a failure in authorization. Alternatively, the C2 authorization result indicates a success or a failure in the authorization for the C2 communication, and the network may notify the UE of a success or a failure in the authorization for the C2 communication using the PDU session and the direct C2 communication, or the UE may recognize the notification.
Alternatively, the Service-level-AA container information element may include a direct C2 authorization result that is an authorization result for the direct C2 communication and that is independent of the C2 authorization result. In this case, the direct C2 authorization result may be information indicating a success or a failure in authorization for the direct C2 communication.
An Unmanned Aerial Vehicle (UAV) is a flying drone. The UAV may be a UE. The UAV may be a 3GPP UE that supports UE functions.
The UAV may also be managed by a USS. The UAV may be associated with a UAV controller. Further, the UAV may be associated with the UAV controller and managed by a core network apparatus and/or a UTM. Further, in a case that the UAV is managed in association with the UAV controller, the UAV may be managed by the core network apparatus and/or the UTM as a UAS. The UAV may have its own information (identification information, IP address, location information, etc.) managed by the core network apparatus and/or the UTM. The UE may be read as the UAV.
The Unmanned Aerial Vehicle controller (UAV controller) is a controller for operating the UAV. The UAV controller may be a UE. The UAV controller may be a 3GPP UE supporting the UE functions.
The UAV controller may be associated with the UAV. Further, the UAV controller may be associated with the UAV and managed by the core network apparatus and/or the UTM. Further, in a case that the UAV controller is managed in association with the UAV, the UAV controller may be managed by the core network apparatus and/or the UTM as a UAS. The UAV controller may have its own information (identification information, IP address, location information, etc.) managed by the core network apparatus and/or the UTM. The UAV controller may be expressed as a UAC or a UAV-C. The UE may be read as the UAV-C.
The Unmanned Aerial System (UAS) may include a UAV and related functions. Here, the related functions may include a command and control (C2) link. Further, the C2 link may be a link between the UAV and the control station, or a link between the UAV and the network. Further, the C2 link may be a link for remote identification. The UAS may also include one or multiple UAVs and one or multiple UAV controllers. The UAS may also be managed by the network apparatus and/or the USS.
The Unmanned Aerial System Service Supplier (USS) is an apparatus having a function of managing the UAV and/or the UAV controller and/or the UAS. The USS may be an apparatus of the DN or an apparatus in the core network. The USS may also be an apparatus for autonomously navigating the UAV. The USS may include a function of managing identification information, an IP address, location information, and the like of the UAV and/or the UAV controller, or may include a function of managing information of the UAV and/or the UAV controller other than those pieces of information described above. Further, the USS may manage the UAV and the UAV controller in association with each other as a UAS. The USS may transmit information for requesting a network service from the core network apparatus. Further, the USS may be an apparatus that provides one or multiple functions or services for managing the range of motor vehicle operations. The USS may be a UAS application server.
The USS may be an apparatus including functions of the UTM. The USS may be an apparatus included in the UTM. The USS may be an apparatus in the UTM. The USS may be expressed as a USS/UTM or a UTM/USS. The USS may be expressed as a network.
The Unmanned Aerial System Traffic Management (UTM) may be an apparatus including the USS. The UTM may be an apparatus including the USS. The UTM may be read as the USS.
The Command and Control (C2) communication may be a user plane link for delivering, from the UAV controller or the UTM to the UAV, messages including commands and control information for operating the UAV.
The C2 communication may be communication for delivering, from the UAV controller or the UTM to the UAV, messages including commands and control information for operating the UAV. The C2 communication may be a link between the UAV controller and the UAV. The C2 communication may be a link between the USS and the UAV. The C2 communication may be communication between the UAV controller and the UAV. The C2 communication may be communication between the USS and the UAV.
Further, the C2 communication may be a user plane link for reporting telemetry data from the UAV to the UAV controller or UTM. Further, the C2 communication may be a user plane link for delivering, from the UAV controller to the UAV via the UTM, messages including commands and control information for operating the UAV. Here, the C2 communication may be a link realized by the PDU session. Further, the PDU session for the C2 communication may be realized by the Always-on PDU session. Establishing the PDU session for the C2 communication may also mean establishment of the Always-on PDU session. Further, establishment of a PDU session handling a QoS flow for the C2 communication may mean establishment of the Always-on PDU session. Further, the link may be a communication path or a transmission path. The C2 communication may be referred to as C2.
Direct C2 communication may be a link between the UAV and the UAV-C. The direct C2 communication may be communication between the UAV and the UAV-C.
The direct C2 communication may be a direct link between the UAV and the UAV-C. The direct C2 communication may be a direct C2 link between the UAV and the UAV-C. The direct C2 communication may be a communication path on a PC5. The direct C2 communication may be the C2 communication.
Here, the UAV and/or UAV-C may be registered with the network. Further, the link may be a communication path or a transmission path.
A CAA-Level UAV ID is information assigned to the UAV by a function of an aviation domain such as the USS. The CAA-Level UAV ID may be used for Remote Identification and tracking, or may be used to identify the UAV. The CAA-Level UAV ID may be information provided to the 3GPP system by the UAV during a UUAA procedure.
The aviation domain may assign a new CAA-Level UAV ID for the UAV at any timing. The new CAA-Level UAV ID may be provided to the UAV and the 3GPP system during a UAS-related procedure.
A 3GPP UAV ID is information associated with the UAV by the 3GPP system. The 3GPP UAV ID may be information used by the 3GPP system to identify the UAV. The USS may store an association between the CAA-level UAV ID and the 3GPP UAV ID.
The UE may act as an initiating UE or as a target UE.
The initiating UE may be a UE used in communication between two UEs. The initiating UE may transmit a message to the target UE. The initiating UE may be used in a procedure for establishing the direct C2 communication. The initiating UE may be a UAV or a UAV-C.
The target UE may be a UE used in communication between two UEs. The target UE may transmit a message to the initiating UE. The target UE may be used in a procedure for establishing the direct C2 communication. The target UE may be a UAV or may be a UAV-C.
Authorization for the C2 communication (Authorization for C2) is an authorization and/or procedure that is required to be performed in a case that the UAV and/or UAV-C establishes a user plane connection for a C2 operation. Here, the user plane connection for the C2 operation may be the C2 communication. In other words, in order for the UAV and/or the UAV-C to establish the C2 communication, the authorization for the C2 communication needs to be performed.
In the authorization for the C2 communication, the UAV and/or the UAV-C may authorize the USS to establish the PDN connection and/or PDU session for the C2 and/or to establish the direct C2 communication. Further, for authorization for the C2 communication, pairing between the UAV and the UAV-C may be authorized and/or Flight Authorization may be performed. The USS may perform the authorization of the pairing between the UAV and the UAV-C and/or the flight authorization.
The authorization of the pairing between the UAV and the UAV-C may be the UAV being authorized to be paired with the UAV-C and/or the UAV-C being authorized to be paired with the UAV, and may need to be performed before information is exchanged between the UAV and the UAV-C through the C2 communication.
The flight authorization is authorization for the UAV to fly (flight). The flight authorization may need to have been performed prior to the flight of the UAV. Alternatively, the flight authorization may be performed within the authorization procedure for the C2 communication only in a case that the UAV requests the authorization. In other words, in a case that the C2 communication is authorized, the pairing between the UAV and the UAV-C and/or the flight of the UAV may be authorized.
The authorization for the C2 communication may be performed during the UUAA procedure or may be performed by another procedure. In particular, in a case that the UAV desires to separate the C2 communication with the USS from the C2 communication with the UAV-C, the authorization for the C2 communication may be performed within the procedure for the UAV to establish a new PDU session and/or PDN connection.
The case that the UAV desires to separate the C2 communication with the USS from C2 communication with the UAV-C may be, for example, a case that the UAV requests establishment of the direct C2 communication.
In a case that the UAV and/or the UAV-C requests establishment of the direct C2 communication, the authorization for the C2 communication for the direct C2 communication may be performed during the registration procedure and/or during a UUAA-MM procedure.
1 st identification information may be information indicating whether the UE supports the direct C2 communication. The 1st identification information may be information indicating that the UE supports the direct C2 communication. The 1st identification information may be information indicating that the UE does not support the direct C2 communication.
The 1st identification information may be information indicating a request for authentication and/or authorization of establishment of the direct C2 communication. The 1st identification information may be information indicating a request for authentication and/or authorization of the use of the direct C2 communication.
The 1st identification information may be a 5GMM capability. The 1st identification information may be information included in the 5GMM capability.
2nd identification information may be information indicating a request for authentication and/or authorization of establishment of the direct C2 communication and/or the C2 communication using the PDU session. The 2nd identification information may be information indicating a request for authentication and/or authorization of establishment of the direct C2 communication and/or the C2 communication.
The 2nd identification information may be information indicating a request for authentication and/or authorization of simultaneous establishment of the direct C2 communication and the C2 communication. The 2nd identification information may be information indicating a request for authentication and/or authorization of simultaneous use of the direct C2 communication and the C2 communication.
The 2nd identification information may be information indicating whether the UE supports the direct C2 communication and/or the C2 communication. The 2nd identification information may be information indicating that the UE supports the direct C2 communication and/or the C2 communication. The 2nd identification information may be information indicating that the UE does not support the direct C2 communication and/or the C2 communication.
The 2nd identification information may be a 5GSM capability. The 2nd identification information may be information included in the 5GSM capability.
The 1st identification information and/or the 2nd identification information may be information included in the Service-level-AA container.
3rd identification information may be source user information (source user info). The 3rd identification information may be an application layer ID of the initiating UE. The 3rd identification information may be the application layer ID of the UE transmitting the message. The 3rd identification information received from the higher layer. The 3rd identification information may be source user information in which the application layer ID of the initiating UE received from the higher layer is set.
The 3rd identification information may be information included in a message used for communication between two UEs.
4th identification information may also be information identifying an application of the UAS. The 4th identification information may be information for requesting the application of the UAS. Further, the 4th identification information may be information for using the application of the UAS. Further, the 4th identification information may be information used for the application of the UAS.
Further, the 4th identification information may be a ProSe identifier.
The 5th identification information may be target user information (target user info). The 5th identification information may be the application layer ID of the target UE. The 5th identification information may be the application layer ID of the UE receiving a message. The 5th identification information may be information received from the higher layer. The 5th identification information may be target user information in which the application layer ID of the target UE received from the higher layer is set.
The 5th identification information may be information included in a message used for communication between two UEs.
10th identification information may be information indicating whether the network authenticates and/or authorizes the direct C2 communication. The 10th identification information may be information indicating that the network authenticates and/or authorizes the direct C2 communication. Further, the 10th identification information may be information indicating that the network does not authenticate and/or authorize the direct C2 communication.
The 10th identification information may be information indicating whether the network allows the direct C2 communication. The 10th identification information may be information indicating that the network allows the direct C2 communication. The 10th identification information may be information indicating that the network does not allow the direct C2 communication.
11th identification information may be information indicating that the direct C2 communication and/or the C2 communication using the PDU session is authenticated and/or authorized. The 11th identification information may be information indicating that the direct C2 communication and/or the C2 communication is authenticated and/or authorized. The 11th identification information may be information indicating that the direct C2 communication and/or the C2 communication is not authenticated and/or authorized. The 11th identification information may be information indicating whether to authenticate and/or authorize the direct C2 communication and/or the C2 communication.
The 11th identification information may be information indicating that the direct C2 communication and/or the C2 communication is allowed. The 11th identification information may be information indicating that the direct C2 communication and/or the C2 communication is not allowed. The 11th identification information may be information indicating whether to allow the direct C2 communication and/or the C2 communication.
The 10th identification information and/or the 11th identification information may be information included in a Service-level-AA container. The 10th identification information and/or the 11th identification information may 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 the Service-level-AA response and/or the direct C2 authorization result.
12th identification information may be information identifying the UAV. The 12th identification information may be information identifying the UAV-C. The 12th identification information may be information identifying a UAV to be paired with the UAV-C. The 12th identification information may be information identifying a UAV-C to be paired with the UAV. The 12th identification information may be information used in the direct C2 communication.
The 12th identification information may be information included in the Service-level-AA container. The 12th identification information may be a Service-level device ID included in the Service-level-AA container.
13th identification information may be source user information (source user info). The 13th identification information may be the application layer ID of the target UE. Alternatively, the 13th identification information may be the application layer ID of the UE transmitting a message. The 13th identification information may be information received from the higher layer. The 13th identification information may be source user information in which the application layer ID of the target UE received from the higher layer is set.
The 13th identification information may be information included in a message used for communication between two UEs.
14th identification information may be information identifying an application of the UAS. The 14th identification information may be information for requesting the application of the UAS. The 14th identification information may be information for using the application of the UAS. The 14th identification information may be information used for the application of the UAS.
The 14th identification information may be information for identifying the application of the UAS accepted by the target UE. The 14th identification information may be information for requesting the application of the UAS accepted by the target UE. The 14th identification information may be information for using the application of the UAS accepted by the target UE. The 14th identification information may be information used for the application of the UAS accepted by the target UE.
The 14th identification information may be a response to the 5th identification information. The 14th identification information may be the 5th identification information accepted by the target UE.
The 14th identification information may be a ProSe identifier.
Next, procedures used in each embodiment will be described. Note that the procedure used in each embodiment includes the Registration procedure. Each procedure will be described below.
Note that, in each embodiment, a case that each of the HSS and the UDM, the PCF and the PCRF, the SMF and the PGW-C, and the UPF and the PGW-U is configured as a single apparatus (that is, the same physical hardware, or the same logical hardware, or the same software) as illustrated in
First, the Registration procedure will be described with reference to
The registration procedure may be an initial registration initiated by the UE. The registration procedure may be mobility and periodic registration. The registration procedure may be the MM procedure.
Further, the registration procedure may be a procedure for updating position registration information of the UE on the network, and/or periodically signalling the state of the UE from the UE to the network, and/or updating a specific parameter related to the UE on the network.
The UE may also initiate a registration procedure in a case that the UE has performed mobility across a TA. In other words, the UE may initiate a registration procedure in a case that the UE has moved to a TA different from TAs indicated in a stored TA list. In addition, the UE may initiate the present procedure in a case that a running timer expires. In addition, the UE may initiate the registration procedure in a case that a context of each apparatus needs to be updated due to disconnection and/or invalidation of a PDU session. Furthermore, in a case that there is a change in capability information and/or a preference, related to PDU session establishment of the UE, the UE may initiate the registration procedure. In addition, the UE may periodically initiate the registration procedure. The UE may also initiate a registration procedure based on completion of a UE configuration update procedure. Note that the UE is not limited to this configuration, and can perform the registration procedure at any timing.
The UE may also initiate a registration procedure periodically even in a registered state. In other words, the UE may initiate a registration procedure based on expiration of a timer.
The registration procedure performed based on the mobility of the UE and the registration procedure performed periodically may also be expressed as a registration procedure for mobility and registration update. In other words, the registration procedure for mobility and registration update may be a registration procedure performed based on the mobility of the UE or may be a registration procedure performed periodically. The registration procedure for mobility and registration update may also be a registration procedure performed based on configuration update of the UE. The registration procedure for mobility and registration update may also be a registration procedure performed to establish a communication path for transmitting and/or receiving user data. The registration procedure for mobility and registration update may also be a registration procedure performed based on a request from the network. In other words, the registration procedure for mobility and registration update may be a registration procedure other than an initial registration procedure. Hereinafter, the registration procedure for mobility and registration update may be referred to as the present procedure.
Each step of the registration procedure will be described below. The registration procedure described below may be an initial registration procedure or a registration procedure for mobility and registration update.
First, the UE transmits a Registration request message to the AMF (S800) (S802) (S804) to initiate the registration procedure. Specifically, the UE transmits an RRC message including a registration request message to the 5G AN (or the gNB) (S800). The registration request message is a NAS message. The RRC message may be a control message transmitted and/or received between the UE and the 5G AN (or the gNB). In addition, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.
Here, the UE may transmit a registration request message and/or an RRC message including one or more pieces of identification information out of the 1st identification information and the 2nd identification information. More specifically, the UE can transmit a registration request message and/or an RRC message including one or more pieces of identification information out of the 1st identification information and the 2nd identification information and may also transmit a control message different from such messages, for example, a control message of a layer below the RRC layer (e.g., the MAC layer, the RLC layer, or the PDCP layer), including the one or more pieces of identification information.
By transmitting such identification information, the UE may indicate that the UE supports each function or may indicate the request of the UE. Furthermore, in a case that multiple pieces of identification information are transmitted and/or received, two or more pieces of identification information of these pieces of identification information may be configured as one or multiple pieces of identification information. Information indicating support for each function and information indicating a request to use each function may be transmitted and/or received with the same piece of identification information or may be transmitted and/or received as different pieces of identification information.
To be specific, by transmitting the 1st identification information, the UE may indicate to the network whether the UE supports the direct C2 communication. By transmitting the 1st identification information, the UE may indicate to the network that the UE supports the direct C2 communication. By transmitting the 1st identification information, the UE may indicate to the network that the UE does not support the direct C2 communication. By transmitting the 1 st identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize establishment of the direct C2 communication. By transmitting the 1st identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize the use of the direct C2 communication.
Here, by transmitting the 2nd identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication using the PDU session. By transmitting the 2nd identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize the simultaneous establishment of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize the simultaneous use of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UE may indicate to the network whether the UE supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UE may indicate to the network that the UE supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UE may indicate to the network that the UE does not support the direct C2 communication and/or the C2 communication.
Here, by transmitting the registration request message, the UE may indicate the content of the identification information to the network.
In other words, in a case that the UE supports the direct C2 communication, and/or in a case that the UE requests the network to authenticate and/or authorize establishment of the direct C2 communication, and/or in a case that the UE requests the network to authenticate and/or authorize the use of the direct C2 communication, the UE may transmit the 1st identification information included in the registration request message or transmit the 1st identification information along with the registration request message.
In other words, in a case that the UE supports the direct C2 communication, and/or in a case that the UE requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication using a PDU session, and/or in a case that the UE requests the network to authenticate and/or authorize utilization of the direct C2 communication and/or the C2 communication using a PDU session, the UE may transmit the 2nd identification information included in the registration request message or transmit the 2nd identification information along with the registration request message.
Further, by including, in the registration request message, one or more pieces of identification information out of the 1st identification information and the 2nd identification information, the UE may indicate, to the network, the content indicated by the identification information included in the registration request message. Further, by including, in the registration request message, one or more pieces of identification information out of the 1st identification information and the 2nd identification information, the UE may request, from the network, the content indicated by the identification information included in the registration request message.
Note that the UE may select or determine whether to include, in the registration request message, one or more pieces of identification information out of the 1st identification information and the 2nd identification information based on subscriber information, network status, user registration information, a context held by the UE, and/or the like.
Note that the UE may transmit the registration request message including identification information other than the 1st identification information and the 2nd identification information. Specifically, the UE may include the Service-level-AA container in the registration request message. Alternatively, the UE may use the Service-level-AA container to transmit the 1st identification information and the 2nd identification information. Specifically, the UE may include, in the Service-level-AA container, one or more pieces of identification information out of the 1st identification information and the 2nd identification information, and may further include the Service-level-AA container in the registration request message.
The UE may initiate the PDU session establishment procedure during the registration procedure by transmitting the registration request message including the SM message or by transmitting the SM message along with the registration request message. Here, the SM message may be a PDU session establishment request message.
Upon receiving the RRC message including the registration request message, the 5G AN (or the gNB) selects an AMF to which to transfer the registration request message (S802). The 5G AN (or the gNB) can select an AMF based on information included in the registration request message and/or the RRC message. The 5G AN (or the gNB) extracts the registration request message from the received RRC message and transfers the registration request message to the selected AMF (S804).
The AMF may make a first condition fulfillment determination in a case that the AMF has received a registration request message. The first condition fulfillment determination is used by the network (or AMF) to determine whether to accept the request of the UE. In a case that the first condition fulfillment determination is true, the AMF initiates the procedure of (A) of
Note that the first condition fulfillment determination may be performed based on reception of the registration request message, and/or each piece of identification information included in the registration request message, and/or subscriber information, and/or capability information of the network, and/or the operator policy, and/or a state of the network, and/or registration information of the user, and/or a context stored in the AMF, and/or the like. For example, the first condition fulfillment determination may be true in a case that the network allows the request from the UE, and the first condition fulfillment determination may be false in a case that the network does not allow the request from the UE. In addition, in a case that a network with which the UE is to be registered and/or an apparatus in the network supports the function requested by the UE, the first condition fulfillment determination may be true, whereas in a case that the network and/or the apparatus does not support the function requested by the UE, the first condition fulfillment determination may be false. Furthermore, in a case that the transmitted and/or received identification information is allowed, the first condition fulfillment determination may be true, whereas in a case that the transmitted and/or received identification information is not allowed, the first condition fulfillment determination may be false. The conditions for determining whether the first condition fulfillment determination is true or false may not be limited to the conditions described above.
First, the case that the first condition fulfillment determination is true will be described. In the procedure of (A) of
The fourth condition fulfillment determination may be made based on whether the AMF has received an SM message. The fourth condition fulfillment determination may be made based on whether an SM message is included in the registration request message. For example, the fourth condition fulfillment determination may be true in a case that the AMF has received an SM message and/or in a case that an SM message is included in the registration request message and false in a case that the AMF has received no SM message and/or in a case that no SM message is included in the registration request message. The conditions for determining whether the fourth condition fulfillment determination is true or false may not be limited to the conditions described above.
Next, based on reception of the registration request message and/or completion of transmission and/or reception of the SM message to and/or from the SMF, the AMF transmits a registration accept message to the UE via the 5G AN (or the gNB) as a response message to the registration request message (S808). For example, in a case that the fourth condition fulfillment determination is false, the AMF may transmit a registration accept message based on receiving the registration request message from the UE. In a case that the fourth condition fulfillment determination is true, the AMF may transmit a registration accept message based on completion of transmission and/or reception of an SM message to and/or from the SMF. The registration accept message is a NAS message transmitted and/or received over the N1 interface, but is incorporated into an RRC message and transmitted and/or received between the UE and the 5G AN (the gNB).
The AMF may transmit the registration accept message including one or more pieces of identification information out of the 10th identification information to the 12th identification information. By transmitting such identification information, the AMF may indicate that the network supports each function or may indicate that the request of the UE has been accepted. Furthermore, in a case that multiple pieces of identification information are transmitted and/or received, two or more pieces of identification information of these pieces of identification information may be configured as one or multiple pieces of identification information. Information indicating support for each function and information indicating a request to use each function may be transmitted and/or received with the same piece of identification information or may be transmitted and/or received as different pieces of identification information.
Further, by including, in the registration accept message, one or more pieces of identification information out of the 10th identification information to the 12th identification information, the network may indicate, to the UE, the content indicated by the identification information included in the registration accept message. Further, by including, in the registration accept message, one or more pieces of identification information out of the 10th identification information to the 12th identification information, the network may indicate, to the UE, the content indicated by the identification information included in the registration accept message.
To be specific, by transmitting the 10th identification information, the network may indicate to the UE whether to authenticate and/or authorize the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UE that the direct C2 communication is authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UE that the direct C2 communication is not authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UE whether to allow the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UE that the direct C2 communication is allowed. By transmitting the 10th identification information, the network may indicate to the UE that the direct C2 communication is not allowed.
Here, by transmitting the 11th identification information, the network may indicate to the UE that the direct C2 communication and/or the C2 communication using the PDU session is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UE that the direct C2 communication and/or the C2 communication is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UE that the direct C2 communication and/or the C2 communication is not authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UE whether to authenticate and/or authorize the direct C2 communication and/or the C2 communication. By transmitting the 11th identification information, the network may indicate to the UE that the direct C2 communication and/or the C2 communication is allowed. By transmitting the 11th identification information, the network may indicate to the UE that the direct C2 communication and/or the C2 communication is not allowed. By transmitting the 11th identification information, the network may indicate to the UE whether to allow the direct C2 communication and/or the C2 communication.
Here, by transmitting the 12th identification information, the network may indicate the UAV-C to be paired with the UAV or the UAV to be paired with the UAV-C. By transmitting the 12th identification information, the network may indicate the UAV-C to be paired with the UAV or the UAV to be paired with the UAV-C, which is used in the direct C2 communication.
Here, by transmitting the registration accept message, the network may indicate the content of the identification information to the UE.
Note that the AMF may select or determine whether to include, in the registration accept message, one or more pieces of identification information out of the 10th identification information to the 12th identification information based on each piece of received identification information, subscriber information, network capability information, an operator policy, network status, user registration information, a context held by the AMF, and/or the like.
The AMF may transmit the registration accept message including identification information other than the 10th identification information to 12th identification information. Specifically, the AMF may include the Service-level-AA container in the registration accept message. Alternatively, the AMF may use the Service-level-AA container to transmit the 10th identification information to the 12th identification information. Specifically, the AMF may include, in the Service-level-AA container, one or more pieces of identification information out of the 10th identification information to the 12th identification information, and may further include the Service-level-AA container in the registration accept message. The UE may receive the registration accept message including the Service-level-AA container.
The AMF can transmit the registration accept message including the SM message or transmit the SM message along with the registration accept message. However, this transmission method may be performed in a case that the SM message may be included in the registration request message and the fourth condition fulfillment determination is true. This transmission method may be performed in a case that the SM message is included with the registration request message and the fourth condition fulfillment determination is true. By performing such a transmission method as described above, the AMF can indicate that a procedure for SM has been accepted in the registration procedure. Here, the SM message may be a PDU session establishment request message or may be a PDU session establishment accept message.
The AMF may indicate that the request of the UE has been accepted by transmitting a registration accept message based on each piece of received identification information, subscriber information, network capability information, an operator policy, network status, user registration information, a context held by the AMF, and/or the like.
The AMF may also transmit a registration accept message including information indicating that a part of the request of the UE has been rejected or may transmit information indicating that a part of the request of the UE has been rejected to indicate a reason why a part of the request of the UE has been rejected. The UE may also recognize a reason why a part of the request of the UE has been rejected by receiving information indicating that a part of the request of the UE has been rejected. The reason for rejection may be information indicating that content indicated by the identification information received by the AMF is not allowed.
The UE receives the registration accept message from the AMF via the 5G AN (the gNB) (S808). By receiving the registration accept message, the UE can recognize that the request of the UE in the registration request message has been accepted and the content of various identification information included in the registration accept message.
Further, the UE can further transmit a registration complete message to the AMF via the 5G AN (the gNB) as a response message to the registration accept message (S810). Here, although the registration complete message is a NAS message transmitted and/or received over the N1 interface, the registration complete message is transmitted and/or received between the UE and the 5G AN (gNB) by being included in an RRC message.
The AMF receives the registration complete message via the 5G AN (the gNB) (S810). Each apparatus completes the procedure of (A) of
Next, the case that the first condition fulfillment determination is false will be described. In the procedure of (B) of
Here, the AMF may transmit the registration reject message including one or more pieces of identification information out of the 10th identification information to the 12th identification information. Here, by transmitting one or more pieces of identification information out of the 10th identification information to the 12th identification information, the AMF may indicate that the request of the UE has been rejected or indicate the reason why the request of the UE has been rejected.
Further, by including, in the registration reject message, one or more pieces of identification information out of the 10th identification information to the 12th identification information, the network may indicate, to the UE, the content indicated by the identification information included in the registration reject message. Further, by including, in the registration reject message, one or more pieces of identification information out of the 10th identification information to the 12th identification information, the network may not need to allow, for the UE, the content indicated by the identification information included in the registration reject message.
The AMF may select or determine whether to include, in the registration reject message, one or more pieces of identification information out of the 10th identification information to the 12th identification information, based on each piece of received identification information, subscriber information, network capability information, an operator policy, network status, user registration information, a context held by the AMF, and/or the like.
The AMF may also transmit a registration reject message to indicate that the request of the UE in the registration request message has been rejected. The AMF may also transmit a registration reject message including information indicating a reason for rejection or may transmit a reason for rejection to indicate the reason for rejection. The UE may also recognize a reason why the request of the UE has been rejected by receiving information indicating the reason why the request of the UE has been rejected. The reason for rejection may be information indicating that content indicated by the identification information received by the AMF is not allowed.
The UE receives the registration reject message from the AMF via the 5G AN (the gNB) (S812). By receiving the registration reject message, the UE can recognize that the request of the UE in the registration request message has been rejected and the content of various identification information included in the registration reject message. The UE may also recognize that the request of the UE has been rejected in a case that the UE does not receive a registration reject message even in a case that a prescribed period of time has elapsed after transmitting a registration request message. Each apparatus completes the procedure (B) in the present procedure based on transmission and/or reception of the registration reject message.
Note that the procedure of (B) of
Each apparatus completes the registration procedure, based on completion of the procedure of (A) or (B) of
The UE may complete the registration procedure based on reception of the registration accept message or the registration reject message.
Furthermore, each apparatus may perform processing based on information transmitted and/or received in the registration procedure, based on completion of the registration procedure. For example, in a case that information indicating that a part of the request from the UE has been rejected is transmitted and/or received, the reason for rejection of the request from the UE may be recognized. Each apparatus may also perform the present procedure again or may perform a registration procedure with the core network_B or another cell based on the reason why the request of the UE has been rejected.
Moreover, the UE may store the identification information received along with the registration accept message and/or the registration reject message or may recognize determination of the network based on the completion of the registration procedure.
Further, in a case of receiving one or more pieces of identification information out of the 10th identification information to the 12th identification information, the UE may recognize the content indicated by the received identification information. Further, in a case of receiving one or more pieces of identification information out of the 10th identification information to the 12th identification information, the UE may also recognize that the content indicated by the identification information included in the registration accept message or the registration reject message has been allowed.
Here, by receiving the 10th identification information, the UE may recognize whether the direct C2 communication has been authenticated and/or authorized. Further, by receiving the 10th identification information, the UE may recognize that the direct C2 communication has been authenticated and/or authorized. Further, by receiving the 10th identification information, the UE may recognize that the direct C2 communication has not been authenticated and/or authorized. By receiving the 10th identification information, the UE may recognize whether the direct C2 communication has been allowed. By receiving the 10th identification information, the UE may recognize that the direct C2 communication has been allowed. By receiving the 10th identification information, the UE may recognize that the direct C2 communication has not been allowed.
Here, by receiving the 11th identification information, the UE may recognize that the direct C2 communication and/or the C2 communication using the PDU session has been authenticated and/or authorized. By receiving the 11th identification information, the UE may recognize that the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UE may recognize that the direct C2 communication and/or the C2 communication has not been authenticated and/or authorized. By receiving the 11th identification information, the UE may recognize whether the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UE may recognize that the direct C2 communication and/or the C2 communication has been allowed. By receiving the 11th identification information, the UE may recognize that the direct C2 communication and/or the C2 communication has not been allowed. By receiving the 11th identification information, the UE may recognize whether the direct C2 communication and/or the C2 communication has been allowed.
Here, the UE may recognize the UAV or the UAV-C to be paired with the UE based on reception of the 12th identification information. The UE may recognize the UAV or the UAV-C to be paired with the UE, which is used in the direct C2 communication, based on reception of the 12th identification information.
By receiving the registration request message or the registration reject message, the UAV may recognize the content of the identification information.
A behavior to be performed in a case that each piece of identification information has been received may be performed based on the received identification information.
Next, the behavior of each apparatus in a case that the UE performs the PDU session establishment procedure will be described with reference to
Note that the present procedure may be performed after the registration procedure is performed one or more times.
First, the UE transmits the PDU session establishment request message to the SMF (S1400) (S1402) (S1404) and initiates the PDU session establishment procedure. Then, the SMF receives the PDU session establishment request message from the UE.
Specifically, by transmitting the NAS message including an N1 SM container including the PDU session establishment request message to the AMF via the access network (S1400), the UE initiates the PDU session establishment procedure. The NAS message may be, for example, a message transmitted via the N1 interface, and may be an uplink NAS transport (UL NAS TRANSPORT) message.
Here, the UE may transmit the PDU session establishment request message and/or the NAS message including one or more pieces of identification information out of at least the 1st identification information and the 2nd identification information.
By transmitting such identification information, the UE may indicate that the UE supports each function or may indicate the request of the UE. Furthermore, in a case that multiple pieces of identification information are transmitted and/or received, two or more pieces of identification information of these pieces of identification information may be configured as one or multiple pieces of identification information. Information indicating support for each function and information indicating a request to use each function may be transmitted and/or received with the same piece of identification information or may be transmitted and/or received as different pieces of identification information.
To be specific, by transmitting the 1st identification information, the UE may indicate to the network whether the UE supports the direct C2 communication. By transmitting the 1st identification information, the UE may indicate to the network that the UE supports the direct C2 communication. By transmitting the 1st identification information, the UE may indicate to the network that the UE does not support the direct C2 communication. By transmitting the 1 st identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize establishment of the direct C2 communication. By transmitting the 1st identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize the use of the direct C2 communication.
Here, by transmitting the 2nd identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication using the PDU session. By transmitting the 2nd identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize the simultaneous establishment of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UE may indicate to the network that the UE requests the network to authenticate and/or authorize the simultaneous use of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UE may indicate to the network whether the UE supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UE may indicate to the network that the UE supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UE may indicate to the network that the UE does not support the direct C2 communication and/or the C2 communication.
Here, by transmitting the PDU session establishment request message or the NAS message, the UE may indicate the content of the identification information to the network.
In other words, in a case that the UE supports the direct C2 communication, and/or in a case that the UE requests the network to authenticate and/or authorize establishment of the direct C2 communication, and/or in a case that the UE requests the network to authenticate and/or authorize utilization of the direct C2 communication, the UE may transmit the 1st identification information included in the PDU session establishment request message or included in the NAS message along with the PDU session establishment request message.
In other words, in a case that the UE supports the direct C2 communication, and/or in a case that the UE requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication using the PDU session, and/or in a case that the UE requests the network to authenticate and/or authorize utilization of the direct C2 communication and/or the C2 communication using the PDU session, the UE may transmit the 2nd identification information included in the PDU session establishment request message or included in the NAS message along with the PDU session establishment request message.
The access network may indicate the 3GPP access or the non-3GPP access, and include a base station apparatus. In other words, the UE transmits the NAS message to the AMF via the base station apparatus.
By transmitting the PDU session establishment request message, the UE may request establishment of a PDU session supporting the C2 communication. In other words, by transmitting the PDU session establishment request message, the UE may request establishment of a PDU session supporting a QoS flow for the C2 communication.
In a case of requesting establishment of the PDU session supporting the C2 communication, the UE may request establishment of the Always-on PDU session. In other words, in a case of requesting establishment of the PDU session supporting the QoS flow for the C2 communication, the UE may request establishment of the Always-on PDU session.
Note that the UE may include identification information other than the 1st identification information and the 2nd identification information in the PDU session establishment request message for transmission. Specifically, the UE may include the Service-level-AA container in the PDU session establishment request message. Alternatively, the UE may use the Service-level-AA container to transmit the 1st identification information and the 2nd identification information. Specifically, the UE may include, in the Service-level-AA container, one or more pieces of identification information out of the 1st identification information and the 2nd identification information, and may further include the Service-level-AA container information element in the PDU session establishment request message.
Next, in a case that the AMF receives the NAS message, the AMF can recognize what is requested by the UE, and/or the content of information and the like (a message, a container, information) included in the NAS message.
Next, the AMF selects the SMF as a transfer destination of at least a part of the information and the like (a message, a container, information) included in the NAS message received from the UE (S1402). Note that the AMF may select the SMF being a transfer destination, based on the information and the like (a message, a container, information) included in the NAS message, and/or the subscriber information, and/or the capability information of the network, and/or the UE policy, and/or the operator policy, and/or the state of the network, and/or the registration information of the user, and/or the context stored by the AMF, and/or the like.
Next, the AMF transmits at least a part of the information and the like (a message, a container, information) included in the NAS message received from the UE to the selected SMF via the N11 interface, for example (S1404).
Next, in a case that the SMF receives information and the like (a message, a container, information) transmitted from the AMF, the SMF can recognize what is requested by the UE, and/or the content of the information and the like (a message, a container, information) received from the AMF.
Here, the SMF may perform the second condition fulfillment determination. The second condition fulfillment determination may be used by the network to determine whether the request of the UE is accepted. In a case of determining the second condition fulfillment determination to be true, the SMF may initiate the procedure of (A) of
Note that the second condition fulfillment determination may be performed by the NF other than the SMF. The NF may be, for example, an NSSF, an NWDAF, a PCF, or an NRF. In a case that the NF other than the SMF performs the second condition fulfillment determination, the SMF may provide the NF with at least a part of information necessary for performing the second condition fulfillment determination, specifically, information received from the UE (S1406). Then, in a case that the NF determines true or false of the second condition fulfillment determination based on the information received from the SMF, the NF may notify the SMF of information including results (in other words, true or false) of the second condition fulfillment determination. The SMF may determine the identification information and/or the control message to be transmitted to the UE, based on the results of the second condition fulfillment determination received from the NF.
Note that the second condition fulfillment determination may be performed based on the information and the like (a message, a container, information) received from the AMF, and/or the subscriber information (subscription information), and/or the capability information of the network, and/or the UE policy, and/or the operator policy, and/or the state of the network, and/or the registration information of the user, and/or the context stored by the SMF, and/or the like.
For example, in a case that the network allows the request of the UE, the second condition fulfillment determination may be determined to be true, whereas in a case that the network does not allow the request of the UE, the second condition fulfillment determination may be determined to be false. In a case that a network as a connection destination of the UE and/or an apparatus in the network supports the function requested by the UE, the second condition fulfillment determination may be determined to be true, whereas in a case that the network and/or the apparatus does not support the function requested by the UE, the second condition fulfillment determination may be determined to be false. In a case that the transmitted and/or received identification information is allowed, the second condition fulfillment determination may be determined to be true, whereas in a case that the transmitted and/or received identification information is not allowed, the second condition fulfillment determination may be determined to be false.
Note that the condition for determining true or false of the second condition fulfillment determination need not necessarily be limited to the condition described above.
Next, each step of the procedure of (A) of
The SMF may select the UPF for a PDU session to be established, and transmit an N4 session establishment request message to the selected UPF via the N4 interface, for example (S1408). The N4 session establishment request message may include at least some of the PCC rules received from the PCF.
The SMF may determine whether to authorize the C2 communication during the present procedure based on the information and the like (a message, a container, information) received from the AMF, and/or the information such as the PCC rules received from the PCF, and/or the subscriber information, and/or the network capability information, and/or the UE policy, and/or the operator policy, and/or the network status, and/or the user registration information, and/or the context held by the SMF, and/or the like.
In a case that authorization for the C2 communication is performed during the present procedure, the SMF may determine to authorize establishment of the direct C2 communication and/or the C2 communication using the PDU session based on at least one piece of identification information out of the 1st identification information and the 2nd identification information.
Here, the SMF may select one or more UPFs, based on the information and the like (a message, a container, information) received from the AMF, and/or the information such as the PCC rules received from the PCF, and/or the subscriber information, and/or the network capability information, and/or the UE policy, and/or the operator policy, and/or the network status, and/or the user registration information, and/or the context held by the SMF, and/or the like. In a case that multiple UPFs are selected, the SMF may transmit the N4 session establishment request message to each UPF. Here, the UPF is assumed to have been selected.
Then, in a case of receiving the N4 session establishment request message (S1408), the UPF can recognize the content of the information received from the SMF. The UPF may transmit an N4 session establishment response message to the SMF via the N4 interface, for example, based on reception of the N4 session establishment request message (S1410).
Next, in a case that the SMF receives the N4 session establishment response message as a response message to the N4 session establishment request message, the SMF can recognize content of the information received from the UPF.
Then, the SMF transmits the PDU session establishment accept message to the UE based on reception of the PDU session establishment request message, and/or selection of the UPF, and/or reception of the N4 session establishment response message, and/or the like. The UE receives the PDU session establishment accept message from the SMF (S1418) (S1420) (S1422).
Specifically, the SMF transmits the N1 SM container, and/or N2 SM information, and/or the PDU session ID to the AMF via the N11 interface, for example, based on reception of the PDU session establishment request message, and/or selection of the UPF, and/or reception of the N4 session establishment response message, and/or the like (S1412). Here, the N1 SM container may include the PDU session establishment accept message. Further, the PDU session ID may be included in the PDU session establishment accept message.
Next, the AMF, having received the N1 SM container, and/or the N2 SM information, and/or the PDU session ID, transmits the NAS message to the UE via the first base station apparatus included in the access network (S1414) (S1416). Here, the NAS message is transmitted via the N1 interface, for example. The NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.
Specifically, in a case that the AMF transmits an N2 PDU session request message to the base station apparatus included in the access network (S1414), the base station apparatus receives the N2 PDU session request message and then transmits the NAS message to the UE (S1416). Here, the N2 PDU session request message may include the NAS message and/or the N2 SM information. The NAS message may include the PDU session ID and/or the N1 SM container.
The PDU session establishment accept message may be a response message to the PDU session establishment request. The PDU session establishment accept message may indicate that establishment of the PDU session has been accepted.
Here, by transmitting the PDU session establishment accept message, and/or the N1 SM container, and/or the PDU session ID, and/or the NAS message, and/or the N2 SM information, and/or the N2 PDU session request message, the SMF and/or the AMF may indicate that at least a part of the request of the UE by the PDU session establishment request message has been accepted.
Here, the SMF and/or the AMF may include at least one or more pieces of identification information out of the 10th identification information to the 12th identification information in the PDU session establishment accept message, and/or the N1 SM container, and/or the NAS message, and/or the N2 SM information, and/or the N2 PDU session request message for transmission.
Note that, by transmitting these pieces of identification information and/or the PDU session establishment accept message, the SMF may indicate that the network supports the functions, may indicate that the request of the UE has been accepted, may indicate that the request from the UE has not been allowed, or may indicate information obtained by combining the above-described pieces of information. Furthermore, in a case that multiple pieces of identification information are transmitted and/or received, two or more pieces of identification information of these pieces of identification information may be configured as one or multiple pieces of identification information. Note that information indicating support of each function and information indicating a request for use of each function may be transmitted and/or received as the same piece of identification information, or may be transmitted and/or received as different pieces of identification information.
To be specific, by transmitting the 10th identification information, the network may indicate to the UE whether to authenticate and/or authorize the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UE that the direct C2 communication is authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UE that the direct C2 communication is not authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UE whether to allow the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UE that the direct C2 communication is allowed. By transmitting the 10th identification information, the network may indicate to the UE that the direct C2 communication is not allowed.
Here, by transmitting the 11th identification information, the network may indicate to the UE that the direct C2 communication and/or the C2 communication using the PDU session is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UE that the direct C2 communication and/or the C2 communication is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UE that the direct C2 communication and/or the C2 communication is not authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UE whether to authenticate and/or authorize the direct C2 communication and/or the C2 communication. By transmitting the 11th identification information, the network may indicate to the UE that the direct C2 communication and/or the C2 communication is allowed. By transmitting the 11th identification information, the network may indicate to the UE that the direct C2 communication and/or the C2 communication is not allowed. By transmitting the 11th identification information, the network may indicate to the UE whether to allow the direct C2 communication and/or the C2 communication.
Here, by transmitting the 12th identification information, the network may indicate the UAV-C to be paired with the UAV or the UAV to be paired with the UAV-C. By transmitting the 12th identification information, the network may indicate the UAV-C to be paired with the UAV or the UAV to be paired with the UAV-C, which is used in the direct C2 communication.
Here, by transmitting the PDU session establishment accept message, the network may indicate the content of the identification information to the UE.
Note that the network may transmit the PDU session establishment accept message including identification information other than the 10th identification information to the 12th identification information. Specifically, the network may include the Service-level-AA container in the PDU session establishment accept message. Alternatively, the network may use the Service-level-AA container to transmit the 10th identification information to the 12th identification information. Specifically, the network may include, in the Service-level-AA container, one or more pieces of identification information out of the 10th identification information to the 12th identification information, and may further 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.
Note that the SMF and/or the AMF may determine which piece of identification information is to be included in the PDU session establishment accept message, and/or the N1 SM container, and/or the NAS message, and/or the N2 SM information, and/or the N2 PDU session request message, based on each piece of received identification information, and/or the subscriber information, and/or the network capability information, and/or the UE policy, and/or the operator policy, and/or the network status, and/or the user registration information, and/or the context held by the SMF and/or the AMF, and/or the like.
Then, in a case of receiving the NAS message via the N1 interface, for example (S1416), the UE can recognize that the request of the UE by the PDU session establishment request message has been accepted, and/or the content of the information and the like (a message, a container, information) included in the NAS message.
Next, each step of the procedure of (B) of
First, the SMF transmits the N1 SM container and/or the PDU session ID to the AMF via the N11 interface, for example, based on reception of the PDU session establishment request message (S1418). Here, the N1 SM container may include the PDU session establishment reject message. Further, the PDU session establishment reject message may include the PDU session ID.
Then, the AMF, having received the N1 SM container and/or the PDU session ID, transmits the NAS message to the UE via the base station apparatus included in the access network (S1420)(S1422). Here, the NAS message is transmitted via the N1 interface, for example. The NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. The NAS message may include the PDU session ID and/or the N1 SM container.
The PDU session establishment reject message may be a response message to the PDU session establishment request. The PDU session establishment reject message may indicate that establishment of the PDU session has been rejected.
Here, by transmitting the PDU session establishment reject message, and/or the N1 SM container, and/or the PDU session ID, and/or the NAS message, the SMF and/or the AMF may indicate that the request of the UE by the PDU session establishment request message has been rejected.
Note that, by transmitting the PDU session establishment reject message, the SMF may indicate that the request of the UE has been rejected, may indicate that the request from the UE has not been allowed, or may indicate information obtained by combining these.
Here, the SMF and/or the AMF may include at least one or more pieces of identification information out of the 10th identification information to the 12th identification information in the PDU session establishment reject message, and/or the N1 SM container, and/or the NAS message, and/or the N2 SM information, and/or the N2 PDU session request message for transmission.
Note that the SMF and/or the AMF may select and determine which piece of identification information is to be included in the PDU session establishment reject message, and/or the N1 SM container, and/or the NAS message, and/or the N2 SM information, and/or the N2 PDU session request message, based on each piece of received identification information, and/or the subscriber information, and/or the network capability information, and/or the UE policy, and/or the operator policy, and/or the network status, and/or the user registration information, and/or the context held by the SMF and/or the AMF, and/or the like.
Then, in a case of receiving the NAS message via the N1 interface, for example (S1422), the UE can recognize that the request of the UE by the PDU session establishment request message has been rejected, and/or the content of the information and the like (a message, a container, information) included in the NAS message.
Further, in a case of receiving one or more pieces of identification information out of the 10th identification information to the 12th identification information, the UE may recognize the content indicated by the received identification information. Further, in a case of receiving one or more pieces of identification information out of the 10th identification information to the 12th identification information, the UE may 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 has been allowed.
To be specific, by receiving the 10th identification information, the UE may recognize whether the direct C2 communication has been authenticated and/or authorized. Further, by receiving the 10th identification information, the UE may recognize that the direct C2 communication has been authenticated and/or authorized. Further, by receiving the 10th identification information, the UE may recognize that the direct C2 communication has not been authenticated and/or authorized. By receiving the 10th identification information, the UE may recognize whether the direct C2 communication has been allowed. By receiving the 10th identification information, the UE may recognize that the direct C2 communication has been allowed. By receiving the 10th identification information, the UE may recognize that the direct C2 communication has not been allowed.
Here, by receiving the 11th identification information, the UE may recognize that the direct C2 communication and/or the C2 communication using the PDU session has been authenticated and/or authorized. By receiving the 11th identification information, the UE may recognize that the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UE may recognize that the direct C2 communication and/or the C2 communication has not been authenticated and/or authorized. By receiving the 11th identification information, the UE may recognize whether the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UE may recognize that the direct C2 communication and/or the C2 communication has been allowed. By receiving the 11th identification information, the UE may recognize that the direct C2 communication and/or the C2 communication has not been allowed. By receiving the 11th identification information, the UE may recognize whether the direct C2 communication and/or the C2 communication has been allowed.
Here, the UE may recognize the UAV or the UAV-C to be paired with the UE based on reception of the 12th identification information. The UE may recognize the UAV or the UAV-C to be paired with the UE, which is used in the direct C2 communication, based on reception of the 12th identification information.
By receiving the NAS message or the PDU session establishment accept message or the PDU session establishment reject message, the UE may recognize the content of the identification information.
Each apparatus may complete the present procedure, based on transmission and/or reception of the PDU session establishment accept message. At this time, each apparatus may transition to a state in which the apparatus can communicate with the DN using the established PDU session.
Each apparatus may complete the present procedure, based on transmission and/or reception of the PDU session establishment accept message or the PDU session establishment reject message. At this time, each apparatus fails to establish a PDU session, and thus cannot communicate with the DN in a case that no PDU session has been established yet.
Each processing step shown above that the UE performs based on reception of each piece of identification information may be performed during the present procedure or after the present procedure is completed or may be performed based on completion of the present procedure after the present procedure is completed.
Next, the behavior of each apparatus in a case that the UE performs a procedure for establishing the direct C2 communication will be described with reference to
Note that the present procedure may be performed after the registration procedure is performed one or more times. The present procedure may be performed after the PDU session establishment procedure is performed one or more times. The present procedure may be performed after each of the registration procedure and the PDU session establishment procedure is performed one or more times.
The present procedure may be performed in a case that the network has authenticated and/or authorized, for the UE, establishment of the direct C2 communication in the registration procedure and/or the PDU session establishment procedure. In other words, based on reception of the 10th identification information to the 12th identification information, the UE may initiate the present procedure.
Alternatively, the UE may initiate the present procedure regardless of the authorization, by the network, of establishment of the direct C2 communication.
In the present procedure, the UE may act as an initiating UE or as a target UE.
First, the initiating UE transmits a first control message to the target UE (S1600) to initiate the procedure. Then, the target UE receives the first control message from the initiating UE.
Here, the first control message may be a message for requesting establishment of the direct C2 communication. The first control message may be a ProSe direct link establishment request message.
Here, the initiating UE may include, in the first control message, one or more pieces of identification information out of the 3rd identification information to the 5th identification information, and transmit the first control message.
By transmitting the first control message, the initiating UE may request establishment of the direct C2 communication.
Then, in a case of receiving the first control message, the target UE can recognize what is requested by the initiating UE, and/or the content of information and the like (a message, a container, identification information information) included in the first control message, or the like.
Here, the target UEF may perform a third condition fulfillment determination. The third condition fulfillment determination may be used by the target UE to determine whether the request of the UE is accepted. In a case of determining the third condition fulfillment determination to be true, the target UE may initiate the procedure of (A) of
Note that the third condition fulfillment determination may be performed based on the information and the like (a message, a container, information) received from the initiating UE, and/or the subscriber information (subscription information), and/or the network capability information, and/or the UE policy, and/or the operator policy, and/or the network status, and/or the user registration information, and/or the context stored by the target UE, and/or the like.
For example, in a case that the target UE allows the request of the initiating UE, the third condition fulfillment determination may be determined to be true, whereas in a case that the target UE does not allow the request of the initiating UE, the third condition fulfillment determination may be determined to be false. In a case that the target UE as a connection destination of the initiating UE and/or an apparatus in the target UE supports the function requested by the initiating UE, the third condition fulfillment determination may be determined to be true, whereas in a case that the target UE and/or the apparatus does not support the function requested by the initiating UE, the third condition fulfillment determination may be determined to be false. In a case that the transmitted and/or received identification information is allowed, the third condition fulfillment determination may be determined to be true, whereas in a case that the transmitted and/or received identification information is not allowed, the third condition fulfillment determination may be determined to be false.
Note that the condition for determining true or false of the third condition fulfillment determination need not necessarily be limited to the condition described above.
Next, each step of the procedure of (A) of
The target UE transmits a second control message to the initiating UE based on reception of the first control message. Then, the initiating UE receives the second control message from the target UE (S1602).
Here, the second control message may be a message for accepting establishment of the direct C2 communication. The second control message may be a ProSe direct link establishment accept message.
The second control message may be a response message to the first control message. The second control message may indicate that the first control message has been accepted.
Here, by transmitting the second control message, the target UE may indicate that at least a part of the request of the initiating UE by the first control message has been accepted.
Here, the target UE may include, in the second control message, one or more pieces of identification information out of the 13th identification information and the 14th identification information, and transmit the second control message.
Note that, by transmitting these pieces of identification information and/or the second control message, the target UE may indicate that the target UE supports the functions, may indicate that the request of the initiating UE has been accepted, may indicate that the request from the initiating UE has not been allowed, or may indicate information obtained by combining the above-described pieces of information. Furthermore, in a case that multiple pieces of identification information are transmitted and/or received, two or more pieces of identification information of these pieces of identification information may be configured as one or multiple pieces of identification information. Note that information indicating support of each function and information indicating a request for use of each function may be transmitted and/or received as the same piece of identification information, or may be transmitted and/or received as different pieces of identification information.
Note that the target UE may determine which identification information to be included in the second control message based on each piece of received identification information, and/or the subscriber information, and/or the network capability information, and/or the UE policy, and/or the operator policy, and/or the network status, and/or the user registration information, and/or the context held by the target UE, and/or the like.
Next, in a case of receiving the second control message via the PC5 interface, for example (S1602), the UE can recognize that the request of the UE by the first control message has been accepted, and/or the content of the information and the like (a message, a container, identification information) included in the second control message.
Next, each step of the procedure at (B) of
First, the target UE transmits a third control message to the initiating UE, e.g., via the PC5 interface, based on reception of the first control message (S1604).
Here, the third control message may be a message for rejecting establishment of the direct C2 communication. The third control message may be a ProSe direct link establishment reject message.
The third control message may be a response message to the first control message. The third control message may indicate that establishment of the direct C2 communication has been rejected.
Here, by transmitting the third control message, the target UE may indicate that the request of the UE by the first control message has been rejected.
Note that, by transmitting the third control message, the target UE may indicate that the request of the initiating UE has been rejected, may indicate that the request from the initiating UE has not been allowed, or may indicate information obtained by combining the above-described pieces of information.
Here, the target UE may include, in the third control message, one or more pieces of identification information out of the 13th identification information and the 14th identification information, and transmit the third control message.
Note that the target UE may determine which identification information is to be included in the third control message based on each piece of received identification information, and/or the subscriber information, and/or the network capability information, and/or the UE policy, and/or the operator policy, and/or the network status, and/or the user registration information, and/or the context held by the target UE, and/or the like.
Then, in a case of receiving the third control message via the PC5 interface, for example (S1604), the initiating UE can recognize that the request of the initiating UE by the first control message has been rejected, and/or the content of the information and the like (a message, a container, identification information) included in the third control message.
Each apparatus may complete the present procedure based on transmission and/or reception of the second control message. At this time, each apparatus may transition to a state in which communication can be performed between the initiating UE and the target UE using established the direct C2 communication.
Alternatively, each apparatus may complete the present procedure based on transmission and/or reception of the third control message. At this time, each apparatus fails to establish the direct C2 communication, and thus in a case that no direct C2 communication has been established yet, communication fails to be performed between the initiating UE and the target UE.
Each processing step shown above that the initiating UE performs based on reception of each piece of identification information may be performed during the present procedure or after the present procedure is completed or may be performed based on completion of the present procedure after the present procedure is completed.
After establishing the direct C2 communication based on completion of the present procedure, the initiating UE and the target UE initiate exchanging information using the direct C2 communication.
Next, an outline of a UUAA (USS UAV Authorization/Authentication) procedure will be described. Hereinafter, the UUAA procedure may be referred to as the UUAA or the present procedure.
The present procedure is a procedure for authentication and/or authorization of the UE by the USS. Note that Authorization for the C2 communication (Authorization for C2) may be performed during the UUAA procedure.
Note that the present procedure may be initiated by the network or by the UE.
The UUAA may be a UUAA-MM procedure performed at the time of registration with the 5GS. The UUAA may also be a UUAA-SM procedure performed during PDU session establishment. The UUAA may be an MM procedure or an SM procedure. The procedure used in the UUAA may be the MM procedure or the SM procedure.
In a case that the UUAA-MM is not performed, the UUAA-SM may be performed.
The PDU session for a UAS service may be established only after the UAV is authenticated and authorized by the USS. This behavior may be performed during the UUAA-MM or during the UUAA-SM.
Note that a success in the UUAA may be read as authentication and authorization of the UAV having been allowed. A failure in the UUAA may be read as authentication and authorization of the UAV not being allowed.
The fact that authentication and authorization of the UAV have been allowed may be read as the UAV having been authenticated and authorized. The fact that the authentication and authorization of the UAV have not been allowed may be read as the UAV having not been authenticated and authorized.
The fact that authentication and authorization of the UAV have succeeded may be read as the UAV having been authenticated and authorized. The fact that authentication and authorization of the UAV have failed may be read as the UAV having not been authenticated and authorized.
The fact that authentication and authorization of the USS have been allowed may be read as the UAV having been authenticated and authorized. The fact that authentication and authorization of the USS have not been allowed may be read as the UAV having not been authenticated and authorized.
Next, the UUAA-MM procedure will be described by using
The UUAA-MM procedure may be performed during or after the procedure of registration with the 5GS. In other words, the first communication during the UUAA-MM procedure described below and the registration procedure described above may be collectively referred to as the registration procedure, or the first communication during the UUAA-MM procedure described below may be a procedure independent of the registration procedure described above.
UUAA-MM may be performed in a case of registration with the 5GS based on the operator policy. UUAA-MM may be performed in a case that the UUAA-MM is requested by the operator and/or in a case that the UE has an aerial UE subscription in Access and Mobility Subscription Data and provides the CAA-Level UAV ID included in the Registration Request message. In a case that UUAA-MM is not performed, the UE may be authenticated and/or authorized by PDU session establishment in UUAA-SM.
UUAA-MM may be optional. UUAA-MM may be performed for the UE requesting authentication and authorization of the UAV by the USS in a case that the UE registers with the 5GS. UUAA-MM may be performed by the AMF. In a case that the UE has an airborne UE subscription in the 5GS and in a case that the UE provides the CAA-Level UAV ID of the UAV included in the registration request message, UUAA-MM may be performed while the UE is registered based on a local network policy. UUAA-MM may be performed in a case that the USS that has authenticated the UAV performs re-authentication.
The UE may also be authenticated and authorized by the USS using the CAA-Level UAV ID and a credential associated with the CAA-Level UAV ID. In a case that UUAA-MM is being performed, the AMF may communicate with the USS via the UAS NF and may transfer authentication messages between the UE and the UAS NF.
Next, each step of UUAA-MM will be described below.
First, the UE performs the registration procedure (S2000).
Then, first communication is performed between the UE and the AMF and the USS (S2002). In the first communication, messages for authentication and authorization used by the USS may be transmitted and/or received between the UE and the AMF and the USS.
Here, the UE and/or the AMF may recognize whether UUAA-MM has succeeded through a message for the first communication. In other words, the UE and/or the AMF may recognize, through the message for the first communication, whether the authentication and authorization of the UAV have been allowed.
Then, the AMF can perform a fifth condition fulfillment determination. The fifth condition fulfillment determination is used by the network (or AMF) to determine whether the UUAA-MM has succeeded. The AMF may initiate the UE configuration update procedure (S2004) in (A) of
Note that the fifth condition fulfillment determination may be performed based on 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 registration information, and/or the context held in the AMF, and/or the like.
For example, in a case that the UUAA-MM succeeds, the fifth condition fulfillment determination may be true, and in a case that the UUAA-MM fails, the fifth condition fulfillment determination may be false. Further, in a case that the transmitted and/or received identification information is allowed, the fifth condition fulfillment determination may be true, whereas in a case that the transmitted and/or received identification information is not allowed, the fifth condition fulfillment determination may be false. Note that conditions for determining whether the fifth condition fulfillment determination is true or false may not be limited to the above-described conditions.
The AMF may indicate the result of the UUAA-MM to the UE by a procedure performed according to whether the fifth condition fulfillment determination is true or false.
Each apparatus may also complete the present procedure based on the first communication and/or the UE configuration update procedure and/or performance of the deregistration procedure.
The UE may recognize the result of the UUAA-MM by the procedure in (A) or (B) of
In a case that the authorization for the C2 communication is performed during the UUAA-MM procedure, the UE may recognize the result of authorization for the C2 communication and/or authorization of the pairing between the UAV and the UAV-C and/or the flight of the UAV.
The UE may be prohibited from transmitting the MM message and/or the SM message while performing the UUAA-MM procedure. In other words, the UE may be controlled not to transmit the MM message and/or the SM message until the first communication and/or the UE configuration update procedure and/or the deregistration procedure is completed.
Next, the UUAA-SM procedure will be described by using
Note that the messages transmitted and/or received in the present procedure may have the same behavior as that described in the section of the PDU session establishment procedure.
In a case that the UE requests establishment of a PDU session, the PDU session may request UUAA authentication of the UAV.
In a case that UUAA is revoked, PDU sessions associated with all UAVs may be released. In other words, in a case that authentication and authorization of the UAV are revoked, PDU sessions associated with all UAVs may be released.
UUAA-SM may be performed by the SMF during the PDU session establishment procedure. UUAA-SM may be performed based on SM subscription data obtained from UDM and based on the service level device ID provided by the UE in the PDU session establishment request message.
Next, each step of UUAA-SM will be described below.
First, the UE performs the PDU session establishment procedure. Specifically, the UE transmits the PDU session establishment request message to the SMF (S2200).
Then, second communication is performed between the UE and the SMF and the USS (S2202). In the second communication, messages for authentication and authorization used by the USS may be transmitted and/or received between the UE and the SMF and the USS.
Here, the UE and/or the SMF may recognize whether the UUAA-SM has succeeded through a message for the second communication. In other words, the UE and/or the SMF may recognize, through the message for the second communication, whether authentication and authorization of the UAV have been allowed.
Then, the SMF can perform a sixth condition fulfillment determination. The sixth condition fulfillment determination is used by the network (or SMF) to determine whether the UUAA-SM has succeeded. In a case that the sixth condition fulfillment determination is true, the SMF transmits the PDU session establishment accept message in (A) of
Note that the sixth condition fulfillment determination may be performed based on reception of the message used in the second communication, and/or the subscriber information, and/or the capability information of the network, and/or the operator policy, and/or the network status, and/or the user registration information, and/or the context held in the AMF, and/or the like.
For example, in a case that the UUAA-SM succeeds, the sixth condition fulfillment determination may be true, whereas in a case that the UUAA-SM fails, the sixth condition fulfillment determination may be false. Further, in a case that the transmitted and/or received identification information is allowed, the sixth condition fulfillment determination may be true, whereas in a case that the transmitted and/or received identification information is not allowed, the sixth condition fulfillment determination may be false. The conditions for determining whether the sixth condition fulfillment determination is true or false need not be limited to the conditions described above.
The SMF may indicate the result of the UUAA-SM to the UE through a message transmitted according to whether the sixth condition fulfillment determination is true or false.
Each apparatus may complete the present procedure based on performance of the second communication, and/or transmission and/or reception of the PDU session accept message, and/or transmission and/or reception of the PDU session reject message.
The UE may recognize the result of the UUAA-SM by receiving the message in (A) or (B) of
Note that in a case that authorization for the C2 communication is performed during the UUAA-SM procedure, the UE may recognize the result of authorization for the C2 communication and/or authorization of the pairing between the UAV and the UAV-C and/or the flight of the UAV.
The UE may be prohibited from transmitting the MM message and/or the SM message while performing the UUAA-SM procedure. In other words, the UE may be controlled not to transmit the MM message and/or the SM message until the second communication and/or the PDU session establishment procedure is completed.
Next, each embodiment will be described.
First, a first embodiment will be described. Hereinafter, the first embodiment may be referred to as the present embodiment.
In the present embodiment, the registration procedure and/or UUAA-MM may be performed.
In the present embodiment, the UAV or the UAV-C may be read as the UE. The UE may be read as the UAV or the UAV-C. Each apparatus may be the UAV and/or the UAV-C and/or the network.
In the present embodiment, the UAV may be read as the UAV-C, and the UA-C may be read as the UAV.
The present embodiment may be supported in the 5GS and/or the EPS.
First, the UAV transmits the registration request message to the network. Here, the UAV may include, in the registration request message, at least one or more pieces of identification information out of the 1st identification information and the 2nd identification information.
Here, by transmitting the 1st identification information, the UAV may indicate to the network whether the UAV supports the direct C2 communication. By transmitting the 1st identification information, the UAV may indicate to the network that the UAV supports the direct C2 communication. By transmitting the 1st identification information, the UAV may indicate to the network that the UAV does not support the direct C2 communication. By transmitting the 1st identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize establishment of the direct C2 communication. By transmitting the 1st identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize use of the direct C2 communication.
Here, by transmitting the 2nd identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication using the PDU session. By transmitting the 2nd identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize simultaneous establishment of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize simultaneous use of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UAV may indicate to the network whether the UAV supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV may indicate to the network that the UAV supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV may indicate to the network that the UAV does not support the direct C2 communication and/or the C2 communication.
Here, by transmitting the registration request message, the UAV may indicate the content of the identification information to the network.
Then, the network receives the registration request message from the UAV.
The network can perform the first condition fulfillment determination in a case of receiving the registration request message. The first condition fulfillment determination is used by the network (or AMF) to determine whether to accept the request of the UE. In a case that the first condition fulfillment determination is true, the network initiates the procedure of (A) of
First, the case that the first condition fulfillment determination is true will be described. The network transmits the registration accept message to the UAV. Here, the network may include, in the registration accept message, one or more pieces of identification information out of the 10th identification information to the 12th identification information.
Here, by transmitting the 10th identification information, the network may indicate to the UAV whether to authenticate and/or authorize the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is not authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV whether to allow the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is allowed. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is not allowed.
Here, by transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication using the PDU session is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is not authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV whether to authenticate and/or authorize the direct C2 communication and/or the C2 communication. By transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is allowed. By transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is not allowed. By transmitting the 11th identification information, the network may indicate to the UAV whether to allow the direct C2 communication and/or the C2 communication.
Here, by transmitting the 12th identification information, the network may indicate the UAV-C to be paired with the UAV. By transmitting the 12th identification information, the network may indicate the UAV-C to be paired with the UAV, which is used in the direct C2 communication.
Here, by transmitting the registration accept message, the network may indicate the content of the identification information to the UAV.
Then, the UAV receives the registration accept message. The UAV may receive, from the network, the registration accept message including one or more pieces of identification information out of the 10th identification information to the 12th identification information.
Here, by receiving the 10th identification information, the UAV may recognize whether the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has not been authenticated and/or authorized. By receiving the 10th identification information, the UAV may recognize whether the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has not been allowed.
Here, by receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication using the PDU session has been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication has not been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize whether the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication has been allowed. By receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication has not been allowed. By receiving the 11th identification information, the UAV may recognize whether the direct C2 communication and/or the C2 communication has been allowed.
Here, the UAV may recognize the UAV-C to be paired with the UAV based on reception of the 12th identification information. The UAV may recognize the UAV-C to be paired with the UAV, which is used in the direct C2 communication, based on reception of the 12th identification information.
By receiving the registration accept message, the UAV may recognize the content of the identification information.
Then, each apparatus may perform UUAA-MM.
Next, the case that the first condition fulfillment determination is false will be described. The network transmits the registration reject message to the UAV. Here, the network may include, in the registration reject message, one or more pieces of identification information out of the 10th identification information and the 11th identification information.
Here, by transmitting the 10th identification information, the network may indicate to the UAV whether to authenticate and/or authorize the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is not authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV whether to allow the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is not allowed.
Here again, by transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is not authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV whether to authenticate and/or authorize the direct C2 communication and/or the C2 communication. By transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is not allowed. By transmitting the 11th identification information, the network may indicate to the UAV whether to allow the direct C2 communication and/or the C2 communication.
Here, by transmitting the registration accept message, the network may indicate the content of the identification information to the UAV.
Then, the UAV receives the registration reject message. The UAV may receive, from the network, the registration reject message including one or more pieces of identification information out of the 10th identification information and the 11th identification information.
Here, by receiving the 10th identification information, the UAV may recognize whether the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has not been authenticated and/or authorized. By receiving the 10th identification information, the UAV may recognize whether the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has not been allowed.
Here, by receiving the 11th identification information, the UAV may recognize that the direct the C2 communication and/or the C2 communication has not been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize whether the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication has not been allowed. By receiving the 11th identification information, the UAV may recognize whether the direct C2 communication and/or the C2 communication has been allowed.
By receiving the registration request message, the UAV may recognize the content of the identification information.
The subsequent behavior may or may not be performed regardless of whether the first condition fulfillment determination is true or false.
Then, the UAV-C may transmit the registration request message to the network. Here, the UAV-C may include, in the registration request message, one or more pieces of identification information out of the 1st identification information and the 2nd identification information.
Here, by transmitting the 1st identification information, the UAV-C may indicate to the network whether the UAV-C supports the direct C2 communication. By transmitting the 1 st identification information, the UAV-C may indicate to the network that the UAV-C supports the direct C2 communication. By transmitting the 1st identification information, the UAV-C may indicate to the network that the UAV-C does not support the direct C2 communication. By transmitting the 1st identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize establishment of the direct C2 communication. By transmitting the 1st identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize the use of the direct C2 communication.
Here, by transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication using the PDU session. By transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize the simultaneous establishment of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize the simultaneous use of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UAV-C may indicate to the network whether the UAV-C supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C does not support the direct C2 communication and/or the C2 communication.
Here, by transmitting the registration request message, the UAV-C may indicate the content of the identification information to the network.
Then, the network may receive the registration request message from the UAV-C.
The network can perform the first condition fulfillment determination in a case of receiving the registration request message. The first condition fulfillment determination is used by the network (or AMF) to determine whether to accept the request of the UE. In a case that the first condition fulfillment determination is true, the network initiates the procedure of (A) of
First, the case that the first condition fulfillment determination is true will be described. The network may transmit the registration accept message to the UAV-C. Here, the network may include, in the registration accept message, one or more pieces of identification information out of the 10th identification information to the 12th identification information.
Here, by transmitting the 10th identification information, the network may indicate to the UAV-C whether to authenticate and/or authorize the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is not authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV-C whether to allow the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is allowed. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is not allowed.
Here, by transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication using the PDU session is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is not authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV-C whether to authenticate and/or authorize the direct C2 communication and/or the C2 communication. By transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is allowed. By transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is not allowed. By transmitting the 11th identification information, the network may indicate to the UAV-C whether to allow the direct C2 communication and/or the C2 communication.
Here, by transmitting the 12th identification information, the network may indicate the UAV to be paired with the UAV-C. By transmitting the 12th identification information, the network may indicate the UAV to be paired with the UAV-C, which is used in the direct C2 communication.
Here, by transmitting the registration accept message, the network may indicate the content of the identification information to the UAV-C.
Then, the UAV-C may receive the registration accept message. The UAV-C may receive, from the network, the registration accept message including one or more pieces of identification information out of the 10th identification information to the 12th identification information.
Here, by receiving the 10th identification information, the UAV-C may recognize whether the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has not been authenticated and/or authorized. By receiving the 10th identification information, the UAV-C may recognize whether the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has not been allowed.
Here, by receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication using the PDU session has been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has not been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize whether the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has been allowed. By receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has not been allowed. By receiving the 11th identification information, the UAV-C may recognize whether the direct C2 communication and/or the C2 communication has been allowed.
Here, the UAV-C may recognize the UAV to be paired with the UAV—C based on reception of the 12th identification information. The UAV-C may recognize the UAV to be paired with the UAV-C, which is used in the direct C2 communication, based on reception of the 12th identification information.
By receiving the registration accept message, the UAV-C may recognize the content of the identification information.
Then, each apparatus may perform UUAA-MM.
Next, the case that the first condition fulfillment determination is false will be described. The network may transmit the registration reject message to the UAV-C. Here, the network may include, in the registration reject message, one or more pieces of identification information out of the 10th identification information and the 11th identification information.
Here, by transmitting the 10th identification information, the network may indicate to the UAV-C whether to authenticate and/or authorize the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is not authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV-C whether to allow the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is not allowed.
Here, by transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is not authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV-C whether to authenticate and/or authorize the direct C2 communication and/or the C2 communication. By transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is not allowed. By transmitting the 11th identification information, the network may indicate to the UAV-C whether to allow the direct C2 communication and/or the C2 communication.
Here, by transmitting the registration accept message, the network may indicate the content of the identification information to the UAV-C.
Then, the UAV-C may receive the registration reject message. The UAV-C may receive, from the network, the registration reject message including one or more pieces of identification information out of the 10th identification information and the 11th identification information.
Here, by receiving the 10th identification information, the UAV-C may recognize whether the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has not been authenticated and/or authorized. By receiving the 10th identification information, the UAV-C may recognize whether the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has not been allowed.
Here, by receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has not been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize whether the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has not been allowed. By receiving the 11th identification information, the UAV-C may recognize whether the direct C2 communication and/or the C2 communication has been allowed.
By receiving the registration request message, the UAV-C may recognize the content of the identification information.
The subsequent behavior may or may not be performed regardless of whether the first condition fulfillment determination is true or false.
Then, the UAV may transmit the PDU session establishment request message to the network. Here, the UAV may include, in the PDU session establishment request message, one or more pieces of identification information out of the 1st identification information and the 2nd identification information.
Here, by transmitting the 1st identification information, the UAV may indicate to the network whether the UAV supports the direct C2 communication. By transmitting the 1st identification information, the UAV may indicate to the network that the UAV supports the direct C2 communication. By transmitting the 1st identification information, the UAV may indicate to the network that the UAV does not support the direct C2 communication. By transmitting the 1st identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize establishment of the direct C2 communication. By transmitting the 1st identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize use of the direct C2 communication.
Here, by transmitting the 2nd identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication using the PDU session. By transmitting the 2nd identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize simultaneous establishment of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UAV may indicate to the network that the UAV requests the network to authenticate and/or authorize simultaneous use of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UAV may indicate to the network whether the UAV supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV may indicate to the network that the UAV supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV may indicate to the network that the UAV does not support the direct C2 communication and/or the C2 communication.
Here, by transmitting the PDU session establishment request message, the UAV may indicate the content of the identification information to the network.
Then, the network may receive the PDU session establishment request message from the UAV.
Here, the network may perform the second condition fulfillment determination. The second condition fulfillment determination may be used by the network to determine whether the request of the UE is accepted. In a case of determining that the second condition fulfillment determination is true, the network may initiate the procedure of (A) of
First, the case that the second condition fulfillment determination is true will be described. Each apparatus may perform UUAA-SM.
Next, the network may transmit the PDU session establishment accept message to the UAV. The network may include, in the PDU session establishment accept message, one or more pieces of identification information out of the 10th identification information to the 12th identification information.
Here, by transmitting the 10th identification information, the network may indicate to the UAV whether to authenticate and/or authorize the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is not authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV whether to allow the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is allowed. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is not allowed.
Here, by transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication using the PDU session is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is not authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV whether to authenticate and/or authorize the direct C2 communication and/or the C2 communication. By transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is allowed. By transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is not allowed. By transmitting the 11th identification information, the network may indicate to the UAV whether to allow the direct C2 communication and/or the C2 communication.
Here, by transmitting the 12th identification information, the network may indicate the UAV-C to be paired with the UAV. By transmitting the 12th identification information, the network may indicate the UAV-C to be paired with the UAV, which is used in the direct C2 communication.
Here, by transmitting the PDU session establishment accept message, the network may indicate the content of the identification information to the UAV.
The UAV may receive the PDU session establishment accept message. The UAV may receive, from the network, the PDU session establishment accept message including one or more pieces of identification information out of the 10th identification information to 12th identification information.
Here, by receiving the 10th identification information, the UAV may recognize whether the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has not been authenticated and/or authorized. By receiving the 10th identification information, the UAV may recognize whether the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has not been allowed.
Here, by receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication using the PDU session has been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication has not been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize whether the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication has been allowed. By receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication has not been allowed. By receiving the 11th identification information, the UAV may recognize whether the direct C2 communication and/or the C2 communication has been allowed.
Here, the UAV may recognize the UAV-C to be paired with the UAV based on reception of the 12th identification information. The UAV may recognize the UAV-C to be paired with the UAV, which is used in the direct C2 communication, based on reception of the 12th identification information.
By receiving the PDU session establishment accept message, the UAV may recognize the content of the identification information.
Next, the case that the second condition fulfillment determination is false will be described. Each apparatus need not perform UUAA-SM.
Next, the network may transmit the PDU session establishment reject message to the UAV. Here, the network may include, in the PDU session establishment reject message, one or more pieces of identification information out of the 10th identification information and the 11th identification information.
Here, by transmitting the 10th identification information, the network may indicate to the UAV whether to authenticate and/or authorize the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is not authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV whether to allow the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV that the direct C2 communication is not allowed.
Here again, by transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is not authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV whether to authenticate and/or authorize the direct C2 communication and/or the C2 communication. By transmitting the 11th identification information, the network may indicate to the UAV that the direct C2 communication and/or the C2 communication is not allowed. By transmitting the 11th identification information, the network may indicate to the UAV whether to allow the direct C2 communication and/or the C2 communication.
Here, by transmitting the PDU session establishment reject message, the network may indicate the content of the identification information to the UAV.
Then, the UAV may receive the PDU session establishment reject message. The UAV may receive, from the network, the PDU session establishment reject message including one or more pieces of identification information out of the 10th identification information and the 11th identification information.
Here, by receiving the 10th identification information, the UAV may recognize whether the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has not been authenticated and/or authorized. By receiving the 10th identification information, the UAV may recognize whether the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV may recognize that the direct C2 communication has not been allowed.
Here, by receiving the 11th identification information, the UAV may recognize that the direct the C2 communication and/or the C2 communication has not been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize whether the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV may recognize that the direct C2 communication and/or the C2 communication has not been allowed. By receiving the 11th identification information, the UAV may recognize whether the direct C2 communication and/or the C2 communication has been allowed.
By receiving the PDU session establishment reject message, the UAV may recognize the content of the identification information.
The subsequent behavior may or may not be performed regardless of whether the second condition fulfillment determination is true or false.
Then, UAV-C may transmit the PDU session establishment request message to the network. Here, the UAV-C may include, in the PDU session establishment request message, one or more pieces of identification information out of the 1st identification information and the 2nd identification information.
Here, by transmitting the 1st identification information, the UAV-C may indicate to the network whether the UAV-C supports the direct C2 communication. By transmitting the 1st identification information, the UAV-C may indicate to the network that the UAV-C supports the direct C2 communication. By transmitting the 1st identification information, the UAV-C may indicate to the network that the UAV-C does not support the direct C2 communication. By transmitting the 1st identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize establishment of the direct C2 communication. By transmitting the 1st identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize the use of the direct C2 communication.
Here, by transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication using the PDU session. By transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize establishment of the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize the simultaneous establishment of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C requests the network to authenticate and/or authorize the simultaneous use of the direct C2 communication and the C2 communication. By transmitting the 2nd identification information, the UAV-C may indicate to the network whether the UAV-C supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C supports the direct C2 communication and/or the C2 communication. By transmitting the 2nd identification information, the UAV-C may indicate to the network that the UAV-C does not support the direct C2 communication and/or the C2 communication.
Here, by transmitting the PDU session establishment request message, the UAV-C may indicate the content of the identification information to the network.
Then, the network may receive the PDU session establishment request message from the UAV-C.
Here, the network may perform the second condition fulfillment determination. The second condition fulfillment determination may be used by the network to determine whether the request of the UE is accepted. In a case of determining that the second condition fulfillment determination is true, the network may initiate the procedure of (A) of
First, the case that the second condition fulfillment determination is true will be described. Each apparatus may perform UUAA-SM.
Then, the network may transmit the PDU session establishment accept message to the UAV-C. The network may include, in the PDU session establishment accept message, one or more pieces of identification information out of the 10th identification information to the 12th identification information.
Here, by transmitting the 10th identification information, the network may indicate to the UAV-C whether to authenticate and/or authorize the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is not authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV-C whether to allow the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is allowed. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is not allowed.
Here, by transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication using the PDU session is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is not authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV-C whether to authenticate and/or authorize the direct C2 communication and/or the C2 communication. By transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is allowed. By transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is not allowed. By transmitting the 11th identification information, the network may indicate to the UAV-C whether to allow the direct C2 communication and/or the C2 communication.
Here, by transmitting the 12th identification information, the network may indicate the UAV to be paired with the UAV-C. By transmitting the 12th identification information, the network may indicate the UAV to be paired with the UAV-C, which is used in the direct C2 communication.
Here, by transmitting the PDU session establishment accept message, the network may indicate the content of the identification information to the UAV-C.
Then, the UAV-C may receive the PDU session establishment accept message. The UAV-C may receive, from the network, the PDU session establishment accept message including one or more pieces of identification information out of the 10th identification information to the 12th identification information.
Here, by receiving the 10th identification information, the UAV-C may recognize whether the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has not been authenticated and/or authorized. By receiving the 10th identification information, the UAV-C may recognize whether the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has not been allowed.
Here, by receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication using the PDU session has been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has not been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize whether the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has been allowed. By receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has not been allowed. By receiving the 11th identification information, the UAV-C may recognize whether the direct C2 communication and/or the C2 communication has been allowed.
Here, the UAV-C may recognize the UAV to be paired with the UAV—C based on reception of the 12th identification information. The UAV-C may recognize the UAV to be paired with the UAV-C, which is used in the direct C2 communication, based on reception of the 12th identification information.
By receiving the PDU session establishment accept message, the UAV-C may recognize the content of the identification information.
Next, the case that the second condition fulfillment determination is false will be described. Each apparatus need not perform UUAA-SM.
Then, the network may transmit the PDU session establishment reject message to the UAV-C. Here, the network may include, in the PDU session establishment reject message, one or more pieces of identification information out of the 10th identification information and the 11th identification information.
Here, by transmitting the 10th identification information, the network may indicate to the UAV-C whether to authenticate and/or authorize the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is not authenticated and/or authorized. By transmitting the 10th identification information, the network may indicate to the UAV-C whether to allow the direct C2 communication. By transmitting the 10th identification information, the network may indicate to the UAV-C that the direct C2 communication is not allowed.
Here, by transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is not authenticated and/or authorized. By transmitting the 11th identification information, the network may indicate to the UAV-C whether to authenticate and/or authorize the direct C2 communication and/or the C2 communication. By transmitting the 11th identification information, the network may indicate to the UAV-C that the direct C2 communication and/or the C2 communication is not allowed. By transmitting the 11th identification information, the network may indicate to the UAV-C whether to allow the direct C2 communication and/or the C2 communication.
Here, by transmitting the PDU session establishment reject message, the network may indicate the content of the identification information to the UAV-C.
Then, the UAV-C may receive the PDU session establishment reject message. The UAV-C may receive, from the network, the PDU session establishment reject message including one or more pieces of identification information out of the 10th identification information and the 11th identification information.
Here, by receiving the 10th identification information, the UAV-C may recognize whether the direct C2 communication has been authenticated and/or authorized. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has not been authenticated and/or authorized. By receiving the 10th identification information, the UAV-C may recognize whether the direct C2 communication has been allowed. By receiving the 10th identification information, the UAV-C may recognize that the direct C2 communication has not been allowed.
Here, by receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has not been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize whether the direct C2 communication and/or the C2 communication has been authenticated and/or authorized. By receiving the 11th identification information, the UAV-C may recognize that the direct C2 communication and/or the C2 communication has not been allowed. By receiving the 11th identification information, the UAV-C may recognize whether the direct C2 communication and/or the C2 communication has been allowed.
By receiving the PDU session establishment reject message, the UAV-C may recognize the content of the identification information.
The subsequent behavior may or may not be performed regardless of whether the second condition fulfillment determination is true or false.
Then, the UAV and the UAV-C may perform a procedure for establishing the direct C2 communication.
Here, the procedure for establishing the direct C2 communication may be performed in a case that the UAV and the UAV-C support the direct C2 communication.
The procedure for establishing the direct C2 communication may be performed in a case that the direct C2 communication is authenticated and/or authorized.
The procedure for establishing the direct C2 communication may be performed in a case that the UE receives the registration accept message. In other words, the procedure for establishing the direct C2 communication may be performed in a case that the UE receives the 10th identification information and the 11th identification information. In still other words, the procedure for establishing the direct C2 communication may be performed based on completion of the registration procedure.
The procedure for establishing the direct C2 communication may be performed in a case that the UE receives the PDU session establishment accept message.
The procedure for establishing the direct C2 communication may be performed in a case that UUAA-MM is completed.
The procedure for establishing the direct C2 communication may be performed in a case that the UE receives the PDU session establishment accept message. In other words, the procedure for establishing the direct C2 communication may be performed based on completion of the PDU session establishment procedure.
The procedure for establishing the direct C2 communication may be performed in a case that UUAA-SM is completed.
A program running on an apparatus according to an aspect of the present invention may serve as a program that controls a Central Processing Unit (CPU) and the like to cause a computer to function in such a manner as to realize the functions of the embodiment according to the aspect of the present invention. Programs or information handled by the programs are temporarily stored in a volatile memory such as a Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or another storage apparatus system.
Note that a program for realizing such the functions of the embodiment according to an aspect of the present invention may be recorded on a computer-readable recording medium. The functions may be realized by causing a computer system to read the program recorded on the recording medium for execution. It is assumed that the “computer system” refers to a computer system built into the apparatuses, and the computer system includes an operating system and hardware components such as a peripheral device. In addition, the “computer-readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium dynamically retaining the program for a short time, or any other computer-readable recording medium.
In addition, each functional block or various features of the apparatuses used in the aforementioned embodiments may be implemented or performed on an electric circuit, for example, an integrated circuit or multiple integrated circuits. An electric circuit designed to perform the functions described in the present specification may include a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or may be a processor of a known type, a controller, a micro-controller, or a state machine instead. The aforementioned electric circuit may include a digital circuit or may include an analog circuit. In addition, in a case that a circuit integration technology that replaces the present integrated circuits appears with advances in semiconductor technologies, one or multiple aspects of the present invention can also use a new integrated circuit based on the technology.
Note that the invention of the present application is not limited to the above-described embodiments. Although apparatuses have been described as an example in the embodiments, the invention of the present application is not limited to these apparatuses, and is applicable to a terminal apparatus or a communication apparatus of a fixed-type or a non-stationary electronic apparatus installed indoors or outdoors, for example, an AV apparatus, a kitchen apparatus, a cleaning or washing machine, an air-conditioning apparatus, office equipment, a vending machine, and other household apparatuses.
Although, the embodiments of the present invention have been described in detail above referring to the drawings, the specific configuration is not limited to the embodiments and includes, for example, design changes within the scope that do not depart from the gist of the present invention. Furthermore, in the present invention, various modifications are possible within the scope of claims, and embodiments that are made by suitably combining technical means disclosed according to the different embodiments are also included in the technical scope of the present invention. In addition, a configuration in which elements described in the respective embodiments and having mutually similar effects are substituted for one another is also included.
The present application claims priority of JP 2022-035962, filed on Mar. 9, 2022, and all the contents thereof are included herein by the reference.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2022-035962 | Mar 2022 | JP | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/JP2023/001828 | 1/23/2023 | WO |
