Wireless communication method, terminal device and network element

Abstract

The embodiments of the present application provide a wireless communication method, a terminal device, and a network element. The method includes: determining a first target mode corresponding to a first operation, wherein the first operation includes at least one of authorization, authentication, re-authorization, or re-authentication; and sending information for performing the first operation based on the first target mode. In the embodiments of the present application, by determining the first target mode corresponding to the first operation, the terminal device can send information for performing the first operation based on the first target mode; based on this, when the first operation is authorization / authentication, not only can the authorization / authentication process of the 3GPP network for the terminal device be optimized, but also unnecessary repeated authorization / authentication information can be provided to the 3GPP network. When the first operation is re-authorization / authentication, the terminal device can be re-authorized / authenticated, thereby improving system performance.

Description

[0001] This application is a divisional application of an application with an application date of December 14, 2020, application number 202080102003X (international application number PCT / CN2020 / 136203), and invention name “Wireless Communication Method, Terminal Equipment and Network Element”. Technical Field

[0002] The embodiments of the present application relate to the field of communications, and more specifically, to a wireless communication method, a terminal device, and a network element. Background Art

[0003] As of now, the 3rd Generation Partnership Project (3GPP) network can participate in the authorization / authentication process of drones in two ways. One way is that the drone provides information for authorization / authentication in the registration process of accessing the 3GPP network. The other way is that the drone provides information for authorization / authentication in the process of accessing the 3GPP network and establishing / modifying the Protocol Data Unit (PDU) session. In both ways, different network elements of the 3GPP network participate in the authorization / authentication process between the drone and the UTM / USS and obtain the authorization / authentication results.

[0004] In the specific implementation, the 3GPP network can choose any method to participate in the authorization / authentication process of the drone according to the operator configuration. However, since the drone does not know the configuration of the network, the information used for authorization / authentication will be provided in the registration process and the process of establishing / modifying the PDU session, which will cause the drone to provide unnecessary and repeated authorization / authentication information to the 3GPP network in different processes. In addition, when the drone needs to be re-authorized / authenticated, the drone cannot determine whether it should initiate the registration process or the PDU session-related process to re-provide the information used for authorization / authentication, resulting in the inability to re-authorize / authenticate the drone. Summary of the invention

[0005] The embodiments of the present application provide a wireless communication method, a terminal device, and a network element, which can not only optimize the authorization / authentication process of the 3GPP network for the terminal device, but also avoid providing the 3GPP network with unnecessary repeated authorization / authentication information, and can also realize re-authorization / authentication of the terminal device, thereby improving system performance.

[0006] In a first aspect, a wireless communication method is provided, the method being applicable to a terminal device, the method comprising:

[0007] Determining a first target mode corresponding to a first operation, wherein the first operation includes at least one of authorization, authentication, re-authorization, or re-authentication;

[0008] Information for performing the first operation is sent based on the first target mode.

[0009] In a second aspect, a wireless communication method is provided, the method being applicable to a terminal managing a network element, the method comprising:

[0010] receiving a second request, the second request being used to request at least one of the following operations to be performed on the terminal device: re-authorization, re-authentication, revocation of authorization, or revocation of authentication;

[0011] Determine the target network element;

[0012] Sending the second request to the target network element.

[0013] In a third aspect, a wireless communication method is provided, the method being applicable to a mobility management network element, the method comprising:

[0014] receiving a third request, the third request being used to request at least one of the following operations to be performed on the terminal device: re-authorization, re-authentication, revocation of authorization, or revocation of authentication;

[0015] The third request is sent to the terminal device.

[0016] In a fourth aspect, a wireless communication method is provided, the method being applicable to a policy control network element, the method comprising:

[0017] The policy information is sent to the terminal device through the mobility management network element, where the policy information includes parameters corresponding to the first mode and / or parameters corresponding to the second mode.

[0018] In a fifth aspect, a terminal device is provided, which is used to execute the method in the first aspect or its implementations. Specifically, the terminal device includes a functional module for executing the method in the first aspect or its implementations.

[0019] In a sixth aspect, a network element is provided for executing the method in any one of the second to fourth aspects or their respective implementations. Specifically, the network device includes a functional module for executing the method in any one of the second to fourth aspects or their respective implementations.

[0020] In a seventh aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or its implementation manners.

[0021] In an eighth aspect, a network element is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in any one of the second to fourth aspects or each implementation thereof.

[0022] In a ninth aspect, a chip is provided for implementing the method in any one of the first to fourth aspects or in each of its implementations. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method in any one of the first to fourth aspects or in each of its implementations.

[0023] In a tenth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method of any one of the first to fourth aspects or any of its implementations.

[0024] In an eleventh aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to fourth aspects or any of their implementations.

[0025] In a twelfth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to fourth aspects or in each of its implementations.

[0026] Based on the above technical solution, by determining the first target mode corresponding to the first operation, the terminal device can send information for executing the first operation based on the first target mode; based on this, when the first operation is authorization / authentication, it can not only optimize the authorization / authentication process of the 3GPP network for the terminal device, but also avoid providing the 3GPP network with unnecessary repeated authorization / authentication information. When the first operation is re-authorization / authentication, it can achieve re-authorization / authentication of the terminal device, thereby improving system performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 It is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

[0028] Figure 2 It is a schematic diagram of drone control provided according to an embodiment of the present application.

[0029] Figures 3 to 12 It is a schematic flowchart of the wireless communication method provided in an embodiment of the present application.

[0030] Fig.13 It is a schematic block diagram of a terminal device provided in an embodiment of the present application.

[0031] Fig.14 It is a schematic block diagram of a terminal management network element provided in an embodiment of the present application.

[0032] Fig.15 It is a schematic block diagram of a mobility management network element provided in an embodiment of the present application.

[0033] Fig.16 It is a schematic block diagram of a policy control network element provided in an embodiment of the present application.

[0034] Fig.17 It is a schematic block diagram of a communication device provided in an embodiment of the present application.

[0035] Fig.18 It is a schematic block diagram of the chip provided in the embodiment of the present application. DETAILED DESCRIPTION

[0036] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. For the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0037] The embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), next generation communication system or other communication systems, etc.

[0038] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), and vehicle to vehicle (Vehicle to Vehicle, V2V) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0039] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.

[0040] The embodiments of the present application do not limit the spectrum to which they are applied. For example, the embodiments of the present application can be applied to licensed spectrum or unlicensed spectrum.

[0041] Figure 1 A schematic diagram of a communication system 100 used in the present application is shown as an example. Figure 1 As shown, the communication system 100 mainly includes a terminal device (User Equipment, UE) 101, an access network (Access Network, AN) device 102, an access and mobility management function (Access and Mobility Management Function, AMF) entity 103, a session management function (Session Management Function, SMF) entity 104, a user plane function (User Plane Function, UPF) entity 105, a policy control function (Policy Control function, PCF) entity 106, a unified data management (Unified Data Management, UDM) entity 107, a data network (Data Network, DN) 108, an application function (Application Function, AF) entity 109, an authentication server function (Authentication Server Function, AUSF) entity 110, and a network slice selection function (Network Slice Selection Function, NSSF) entity 111.

[0042] Specifically, in the communication system 100, the UE 101 is connected to the AN device 102 through the Uu interface for access layer connection to exchange access layer messages and wireless data transmission, and the UE 101 is connected to the AMF entity 103 through the N1 interface for non-access layer (Non-Access Stratum, NAS) to exchange NAS messages; the AN device 102 is connected to the AMF entity 103 through the N2 interface, and the AN device 102 is connected to the UPF entity 105 through the N3 interface; multiple UPF entities 105 are connected through the N9 interface, and the UPF entity 105 is connected to the DN through the N6 interface. 108 is connected, and at the same time, the UPF entity 105 is connected to the SMF entity 104 through the N4 interface; the SMF entity 104 is connected to the PCF entity 106 through the N7 interface, the SMF entity 104 is connected to the UDM entity 107 through the N10 interface, the SMF entity 104 controls the UPF entity 105 through the N4 interface, and at the same time, the SMF entity 104 is connected to the AMF entity 103 through the N11 interface; multiple AMF entities 103 are connected through the N14 interface, the AMF entity 103 is connected to the UDM entity 107 through the N8 interface, the AMF entity 103 is connected to the AUSF entity 110 through the N12 interface, the AMF entity 103 is connected to the NSSF entity 111 through the N22 interface, and at the same time, the AMF entity 103 is connected to the PCF entity 106 through the N15 interface; the PCF entity 106 is connected to the AF entity 109 through the N5 interface; the AUSF entity 110 is connected to the UDM entity 107 through the N13 interface.

[0043] In the communication system 100, the UDM entity 107 is a subscription database in the core network, which stores the subscription data of users in the 5G network. The AMF entity 103 is a mobility management function in the core network, and the SMF entity 104 is a session management function in the core network. In addition to the mobility management of the UE 101, the AMF entity 103 is also responsible for forwarding the session management related messages between the UE 101 and the SMF entity 104. The PCF entity 106 is a policy management function in the core network, which is responsible for formulating the mobility management, session management, charging and other related policies for the UE 101. The UPF entity 105 is a user plane function in the core network, which transmits data with the external data network through the N6 interface and transmits data with the AN device 102 through the N3 interface. After the UE 101 accesses the 5G network through the Uu port, a protocol data unit (PDU) session data connection is established from the UE 101 to the UPF entity 105 under the control of the SMF entity 104, so as to transmit data. The AMF entity 103 and the SMF entity 104 obtain user subscription data from the UDM entity 107 through the N8 and N10 interfaces respectively, and obtain policy data from the PCF entity 106 through the N15 and N7 interfaces.

[0044] In addition, there is also a network exposure function (NEF) entity in the communication system 100, which is used to interface with a third-party application server and transmit information between the core network node and the third-party application.

[0045] It should be noted that the above-mentioned communication system 100 is described by taking the 5G communication system as an example. Of course, the present application can also be applied to other 3GPP communication systems, such as 4G communication systems, or future 3GPP communication systems, and the present application is not limited to this.

[0046] It should be understood that a device having a communication function in a network / system in the embodiments of the present application may be referred to as a communication device.

[0047] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0048] The embodiments of the present application describe various embodiments in combination with terminal devices and network devices, wherein: the terminal device may also be referred to as user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a Wireless Local Loop (Wireless Local Loop, WLL) station, a Personal Digital Assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, and a next-generation communication system, for example, a terminal device in an NR network or a terminal device in a future evolved Public Land Mobile Network (Public Land Mobile Network, PLMN) network, etc.

[0049] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0050] The above-mentioned AN device 102 can be a device for communicating with a mobile device. The AN device 102 can be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a base station (gNB) in an NR network, or a network device in a future evolved PLMN network, etc.

[0051] In an embodiment of the present application, a network device provides services for a cell, and a terminal device communicates with the network device through transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell may be a cell corresponding to a network device (e.g., a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: a metro cell, a micro cell, a picocell, a femtocell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0052] With the development of mobile communication technology, the terminal devices that access the 3rd Generation Partnership Project (3GPP) mobile communication network are no longer limited to handheld terminal devices. More and more machines and equipment, such as drones, will also become widely used in wireless communication network scenarios. When drones and other devices access the 3GPP network, they are also accessed as terminal devices, such as Figure 2As shown in the figure, after the UAV (Unmanned Aerial Vehicle, UAV) accesses the 3GPP network, it can establish a connection with the UAV Management Center (Unmanned Aerial System Traffic Management, UTM) through the 3GPP network. UTM is responsible for the management functions such as registration and location tracking of the UAV, and can control the behavior of the UAV, such as flight routes. After the UAV accesses the 3GPP network, it can also establish a connection with the UAV controller through the 3GPP network to control the behavior of the UAV through the UAV controller.

[0053] The 3rd Generation Partnership Project (3GPP) network can participate in the authorization / authentication process of the drone in two ways. One way is that the drone provides information for authorization / authentication in the registration process of accessing the 3GPP network. The other way is that the drone provides information for authorization / authentication in the process of accessing the 3GPP network and establishing / modifying the Protocol Data Unit (PDU) session. In both ways, different network elements of the 3GPP network participate in the authorization / authentication process between the drone and the UTM / USS and obtain the authorization / authentication results.

[0054] In the specific implementation, the 3GPP network can choose any method to participate in the authorization / authentication process of the drone according to the operator configuration. However, since the drone does not know the configuration of the network, the information used for authorization / authentication will be provided in the registration process and the process of establishing / modifying the PDU session, which will cause the drone to provide unnecessary and repeated authorization / authentication information to the 3GPP network in different processes. In addition, when the drone needs to be re-authorized / authenticated, the drone cannot determine whether it should initiate the registration process or the PDU session-related process to re-provide the information used for authorization / authentication, resulting in the inability to re-authorize / authenticate the drone.

[0055] The embodiments of the present application provide a wireless communication method, a terminal device, and a network element, which can not only optimize the authorization / authentication process of the 3GPP network for the terminal device, but also avoid providing the 3GPP network with unnecessary repeated authorization / authentication information, and can also realize re-authorization / authentication of the terminal device, thereby improving system performance.

[0056] Figure 2 A schematic flow chart of a wireless communication method 210 according to an embodiment of the present application is shown, and the method 210 can be executed by a terminal device. Figure 2 The terminal device shown in FIG. 1 may be a terminal device such as Figure 1Optionally, the terminal device in the embodiment of the present application may be a drone device, or other types of terminal devices, including other types of machine devices or ordinary handheld terminal devices, which is not limited in the present application.

[0057] like Figure 2 As shown, the method 210 may include:

[0058] S211, determining a first target mode corresponding to a first operation, where the first operation includes at least one of authorization, authentication, re-authorization or re-authentication;

[0059] S212: Send information for performing the first operation based on the first target mode.

[0060] Based on the above technical solution, by determining the first target mode corresponding to the first operation, the terminal device can send information for executing the first operation based on the first target mode; based on this, when the first operation is authorization / authentication, it can not only optimize the authorization / authentication process of the 3GPP network for the terminal device, but also avoid providing the 3GPP network with unnecessary repeated authorization / authentication information. When the first operation is re-authorization / authentication, it can achieve re-authorization / authentication of the terminal device, thereby improving system performance.

[0061] It should be noted that the embodiment of the present application does not specifically limit the information used to perform the first operation. For example, the information used for authorization / authentication includes but is not limited to at least one of the following: drone identification, drone serial number, pilot information, manufacturer information, drone type or weight information, etc.

[0062] In some embodiments of the present application, the first target mode includes a first mode and / or a second mode, the first mode refers to the terminal device sending the information for performing the first operation through a registration process, and the second mode refers to the terminal device sending the information for performing the first operation through a session management process; S212 may include:

[0063] When the first target mode is the first mode, the information used to perform the first operation is sent through a mobility management network element; when the first target mode is the second mode, the information used to perform the first operation is sent through a session management network element.

[0064] It should be noted that the mobility management network element in the embodiment of the present application may be, for example, the access and mobility management function (AMF) in the 5G communication system, and of course, it may also be an entity with a mobility management function in other 3GPP communication systems, and the present application does not limit this. Similarly, the session management network element in the embodiment of the present application may be, for example, the session management function (SMF) in the 5G communication system, and of course, it may also be an entity with a session management function in other 3GPP communication systems, and the present application does not limit this.

[0065] In addition, in an embodiment of the present application, the first method and the second method can also express the corresponding process through other description methods. For example, the first method refers to the terminal device sending the information for performing the first operation through a mobility management network element or a mobility management message, and the second method refers to the terminal device sending the information for performing the first operation through a session management network element or a session management message. For another example, the first method refers to the terminal device performing the first operation through a mobility management network element, and the second method refers to the terminal device performing the first operation through a session management network element. The embodiment of the present application does not make specific limitations on this.

[0066] In some embodiments of the present application, the S211 may include:

[0067] A first request is received, where the first request is used to request re-authorization and / or re-authentication for the terminal device; and the first target method is determined based on a method for obtaining the first request.

[0068] In other words, when the UTM / USS needs to perform a first operation on the UAV, the UAV provides information for performing the first operation through a corresponding 3GPP process according to a manner of obtaining a first request from the 3GPP network.

[0069] Optionally, when the first request is received from the mobility management network element, the first mode is determined as the first target mode; when the first request is received from the session management network element, the second mode is determined as the first target mode.

[0070] In some embodiments of the present application, the method 210 may further include:

[0071] First indication information sent by a mobility management network element is received, where the first indication information is used to determine the first target mode.

[0072] In other words, when the UTM / USS needs to perform a first operation on the UAV, the UAV provides information for performing the first operation through a corresponding 3GPP process according to the first indication information in the first request obtained from the 3GPP network.

[0073] Optionally, the first indication information is used to instruct the terminal device to use the first mode or the second mode; S211 may include: determining the first mode or the second mode indicated by the first indication information as the first target mode.

[0074] Optionally, the first indication information is used to indicate whether the first method is supported or not, and / or the first indication information is used to indicate whether the second method is supported or not; S211 may include: determining the first target method according to the supported method indicated by the first indication information.

[0075] Optionally, a first request sent by the mobility management network element is received, where the first request is used to request the re-authorization and / or re-authentication, and the first request includes the first indication information.

[0076] In some embodiments of the present application, the method 210 may further include:

[0077] Receive a first request sent by the mobility management network element, wherein the first request is used to request the re-authorization and / or re-authentication; S211 may include: when the first request does not include information for indicating the first target mode, determining the second mode as the first target mode.

[0078] In other words, when the UTM / USS needs to perform a first operation on the UAV, the UAV determines the second mode as the first target mode by default if the first request obtained from the 3GPP network does not include information for indicating the first target mode.

[0079] In some embodiments of the present application, the S211 may include:

[0080] Receive policy information, where the policy information includes parameters corresponding to the first mode and / or parameters corresponding to the second mode; and determine the first target mode based on the policy information.

[0081] Optionally, the policy information sent by the policy control network element is received through the mobility management network element.

[0082] Optionally, when the parameters of the terminal device match the parameters corresponding to the first mode, the first mode is determined as the first target mode; when the parameters of the terminal device match the parameters corresponding to the second mode, the second mode is determined as the first target mode.

[0083] Optionally, the parameter belongs to at least one of the following information: area information, public land mobile network PLMN information or time information.

[0084] Optionally, the policy information also includes an identifier of the terminal device.

[0085] In some embodiments of the present application, the method 210 may further include:

[0086] Second indication information is received, where the second indication information is used to indicate the withdrawal of authorization and / or authentication.

[0087] Optionally, the second indication information forwarded by the session management network element is received through the mobility management network element.

[0088] Optionally, the second indication information forwarded by the terminal management network element is received through the mobility management network element.

[0089] Optionally, the second indication information forwarded by the terminal management network element is received through the session management network element.

[0090] Figure 4 A schematic flow chart of a wireless communication method 220 according to an embodiment of the present application is shown, and the method 220 can be performed by a terminal management network element. Optionally, the terminal management network element can be used to manage terminal devices, and the terminal devices can be drone devices or other types of terminal devices, including other types of machine devices or ordinary handheld terminal devices, which are not limited in the present application. For example, the terminal management network element can be an unmanned aerial vehicle function (UAVF) or an entity with a drone function.

[0091] like Figure 4 As shown, the method 220 may include:

[0092] S221, receiving a second request, where the second request is used to request to perform at least one of the following operations on the terminal device: re-authorization, re-authentication, revocation of authorization, or revocation of authentication;

[0093] S222, determining a target network element;

[0094] S223: Send the second request to the target network element.

[0095] In some embodiments of the present application, the S222 may include:

[0096] A session management network element is determined as the target network element.

[0097] In some embodiments of the present application, the S222 may include:

[0098] Determine a second target mode corresponding to a second operation, wherein the second operation includes at least one of authorization, authentication, re-authorization or re-authentication, and revoking authorization or revoking authentication; and determine the target network element based on the second target mode.

[0099] In some embodiments of the present application, the second target mode includes the first mode and / or the second mode, the first mode refers to the terminal device sending the information for performing the second operation through a registration process, and the second mode refers to the terminal device sending the information for performing the second operation through a session management process; based on this, when the second target mode is the first mode, the mobility management network element is determined as the target network element; when the second target mode is the second mode, the session management network element is determined as the target network element.

[0100] In some embodiments of the present application, the second target mode is determined based on a first mapping relationship, where the first mapping relationship includes parameters corresponding to the first mode and / or parameters corresponding to the second mode.

[0101] Optionally, when the parameters of the terminal device match the parameters corresponding to the first mode, the first mode is determined as the second target mode; when the parameters of the terminal device match the parameters corresponding to the second mode, the second mode is determined as the second target mode.

[0102] Optionally, the parameter belongs to at least one of the following information:

[0103] Area information, Public Land Mobile Network PLMN information or time information.

[0104] Optionally, the first mapping relationship information is pre-configured.

[0105] In some embodiments of the present application, query information is obtained through a unified data storage UDR or a unified data management UDM, and the query information is used to indicate information of a mobility management network element and / or a session management network element serving the terminal device, and / or the query information is used to indicate whether the mobility management network element and / or the session management network element supports the second operation; based on the query information, the second target mode is determined.

[0106] Figure 5A schematic flow chart of a wireless communication method 230 according to an embodiment of the present application is shown, and the method 230 can be performed by a mobility management network element. The mobility management network element in the embodiment of the present application can be, for example, an access and mobility management function (AMF) in a 5G communication system, and of course, it can also be an entity with a mobility management function in other 3GPP communication systems, and the present application does not limit this.

[0107] like Figure 5 As shown, the method 230 may include:

[0108] S231, receiving a third request, wherein the third request is used to request to perform at least one of the following operations on the terminal device: re-authorization, re-authentication, revocation of authorization, or revocation of authentication;

[0109] S232: Send the third request to the terminal device.

[0110] In some embodiments of the present application, the S231 may include:

[0111] The third request sent by the receiving terminal management network element.

[0112] In some embodiments of the present application, the S231 may include:

[0113] The third request sent by the session management network element is received.

[0114] In some embodiments of the present application, the third request includes first indication information, and the first indication information is used to determine a first target mode corresponding to a first operation, and the first operation includes at least one of authorization, authentication, re-authorization or re-authentication.

[0115] In some embodiments of the present application, the first target method includes a first method and / or a second method, the first method refers to the terminal device sending the information used to perform the first operation through a registration process, and the second method refers to the terminal device sending the information used to perform the first operation through a session management process.

[0116] In some embodiments of the present application, the first indication information is used to instruct the terminal device to use the first method or the second method.

[0117] In some embodiments of the present application, the first indication information is used to indicate whether the first method is supported or not, and / or the first indication information is used to indicate whether the second method is supported or not.

[0118] In some embodiments of the present application, when the third request does not include information for indicating a first target mode corresponding to the first operation, the first target mode is a second mode, the first operation includes at least one of authorization, authentication, re-authorization or re-authentication, and the second mode refers to the terminal device sending the information for performing the first operation through a session management process.

[0119] Figure 6 A schematic flow chart of a wireless communication method 240 according to an embodiment of the present application is shown, and the method 240 can be executed by a policy control network element. The policy control network element in the embodiment of the present application can be, for example, a policy control function (PCF) in a 5G communication system, and of course, it can also be an entity with a policy control function in other 3GPP communication systems, and the present application does not limit this.

[0120] like Figure 6 As shown, the method 240 may include:

[0121] S241, sending policy information to the terminal device through the mobility management network element, where the policy information includes parameters corresponding to the first method and / or parameters corresponding to the second method.

[0122] Optionally, the parameter belongs to at least one of the following information:

[0123] Area information, Public Land Mobile Network PLMN information or time information.

[0124] Optionally, the policy information also includes an identifier of the terminal device.

[0125] Optionally, the first method refers to the terminal device sending the information used to perform the first operation through a registration process, and the second method refers to the terminal device sending the information used to perform the first operation through a session management process, and the first operation includes at least one of authorization, authentication, re-authorization or re-authentication.

[0126] It should be understood that the method flow executed by each network element and the method flow executed by the terminal device can refer to each other. For example, the steps in the above methods 220 / 230 / 240 can refer to the corresponding steps in method 210, and for the sake of brevity, they are not repeated here.

[0127] The method provided in the embodiments of the present application is described below in conjunction with specific examples.

[0128] In some embodiments of the present application, when the UTM / USS needs to re-authorize / authenticate the UAV, a re-authorization / authentication request is sent to the UAVF in the 3GPP network, and the UAVF obtains a re-authorization / authentication method for the UAV, and sends the re-authorization / authentication request to the corresponding network element according to the obtained re-authorization / authentication method, and the corresponding network element further sends the re-authorization / authentication request to the UAV. The UAV provides re-authorization / authentication information through the corresponding 3GPP process according to the method of obtaining the re-authorization / authentication request from the 3GPP network.

[0129] Figure 7 It is a schematic interactive flow chart of the wireless communication method 310 provided in an embodiment of the present application. The method 310 can be interactively executed by an Unmanned Aerial Vehicle (UAV), an AMF, an SMF, a UAVF, and a Unified Threat Management (UTM) / UAS Service Supplier (USS). Optionally, the UAV in the embodiment of the present application may also be referred to as an unmanned aerial vehicle device, and may also be replaced by other types of terminal devices, including other types of machine devices or ordinary handheld terminal devices, which are not limited in the present application. Similarly, AMF may be replaced by other mobility management network elements, SMF may be replaced by other session management network elements, and UAVF may be replaced by other terminal management network elements. In addition, optionally, UTM / USS may be any server with data processing capabilities.

[0130] like Figure 7 As shown, the method 310 may include some or all of the following:

[0131] S311, UTM / USS needs to re-authorize / authenticate the UAV and sends a re-authorization / authentication request to the UAVF in the 3GPP network.

[0132] S312: UAVF determines the re-authorization / authentication method.

[0133] Optionally, method one is to re-authorize / authenticate the UAV through a mobility management network element, such as AMF, and method two is to re-authorize / authenticate the UAV through a session management network element, such as SMF.

[0134] Optionally, the UAVF determines the re-authorization / authentication method by methods including but not limited to the following:

[0135] Method 1:

[0136] The UAVF is configured with the re-authorization / authentication method of the UAV. For example, the re-authorization / authentication method of the UAV corresponding to the Public Land Mobile Network (PLMN) or regional information. The UAVF can determine the corresponding re-authorization / authentication method according to the PLMN or regional information where the UAV is located.

[0137] Method 2:

[0138] The UAVF obtains the re-authorization / authentication method for the UAV by querying the UDM and / or UDR. For example, the UDM is queried to obtain the AMF and / or SMF information serving the UAV, and the UDR is queried to obtain whether the AMF and / or SMF supports the re-authorization / authentication of the UAV.

[0139] If it is determined that the re-authorization / authentication method for the UAV is method 1, the following steps are performed:

[0140] S313a, UAVF sends a re-authorization / authentication request to the mobility management network element (eg AMF).

[0141] S314a, the mobility management network element (eg AMF) sends a re-authorization / authentication request to the UAV.

[0142] S315a, send the information for re-authorization / authentication to the mobility management network element (eg AMF) through the registration process.

[0143] S316a, the mobility management network element (eg, AMF) sends information for re-authorization / authentication to the UAVF.

[0144] S317, UAVF sends re-authorization / authentication information to UTM / USS.

[0145] If it is determined that the re-authorization / authentication method for the UAV is method 2, perform the following steps:

[0146] S313b, UAVF sends a re-authorization / authentication request to the session management network element (eg, SMF).

[0147] S314 b, the session management network element (eg, SMF) sends a re-authorization / authentication request to the UAV.

[0148] S315b, sending the information for re-authorization / authentication to the session management network element (eg, SMF) through the session management process.

[0149] S316 b, the session management network element (eg, SMF) sends information for re-authorization / authentication to the UAVF.

[0150] For S313a~S316a and S313 b~S316 b, the UAV determines the 3GPP process for providing information for re-authorization / authentication according to the manner in which the re-authorization / authentication request is obtained from the 3GPP network. If the re-authorization / authentication request is obtained from a mobility management message, the information for re-authorization / authentication is sent to a mobility management network element, such as AMF, through a registration process (e.g., a mobility management message). If the re-authorization / authentication request is obtained from a session management message, the information for re-authorization / authentication is sent to a session management network element, such as SMF, through a session management process (e.g., a session management message).

[0151] In some embodiments of the present application, when the UTM / USS needs to revoke the authorization / authentication of the UAV, an instruction to revoke the authorization / authentication is sent to the UAVF in the 3GPP network, the UAVF obtains a method for revoking the authorization / authentication of the UAV, and sends the instruction to revoke the authorization / authentication to the corresponding network element according to the obtained method for revoking the authorization / authentication, and the corresponding network element further sends the instruction to revoke the authorization / authentication to the UAV.

[0152] Figure 8 It is a schematic interactive flow chart of the wireless communication method 320 provided in an embodiment of the present application. The method 320 can be interactively executed by an Unmanned Aerial Vehicle (UAV), an AMF, an SMF, a UAVF, and a Unified Threat Management (UTM) / UAS Service Supplier (USS). Optionally, the UAV in the embodiment of the present application may also be referred to as a drone device, and may be replaced by other types of terminal devices, including other types of machine devices or ordinary handheld terminal devices, which are not limited in the present application. Similarly, AMF may be replaced by other mobility management network elements, SMF may be replaced by other session management network elements, and UAVF may be replaced by other terminal management network elements. In addition, optionally, UTM / USS may be any server with data processing capabilities.

[0153] like Figure 8 As shown, the method 320 may include some or all of the following:

[0154] S321, UTM / USS needs to revoke the authorization / authentication of the UAV, and sends a revocation authorization / authentication indication to the UAVF in the 3GPP network.

[0155] S322, UAVF determines the authorization / authentication revocation method. It should be understood that the specific implementation of the UAVF determining the authorization / authentication revocation method can refer to S312 in method 310, that is, the UAVF determines the re-authorization / authentication method, which will not be repeated here to avoid repetition.

[0156] If it is determined that the authorization / authentication method for the UAV is method 1, perform the following steps:

[0157] S323a, UAVF sends the authorization / authentication revocation indication to the mobility management network element, such as AMF.

[0158] S324a, the mobility management network element sends a revocation authorization / authentication indication to the UAV. For example, the AMF sends a revocation authorization / authentication indication to the UAV.

[0159] If it is determined that the authorization / authentication method for the UAV is method 2, perform the following steps:

[0160] S323b, UAVF sends the authorization / authentication revocation indication to the session management network element, such as SMF.

[0161] S324b, the session management network element sends a revocation authorization / authentication indication to the UAV. For example, the SMF sends a revocation authorization / authentication indication to the UAV.

[0162] In some embodiments of the present application, when the UTM / USS needs to re-authorize / authenticate the UAV, the re-authorization / authentication request is sent to the UAVF in the 3GPP network, the UAVF sends the re-authorization / authentication request to the SMF, the SMF sends the re-authorization / authentication request to the AMF, the AMF sends the re-authorization / authentication request to the UAV, and the AMF also sends the information used to determine the re-authorization / authentication method to the UAV. The UAV provides information for re-authorization / authentication through the corresponding 3GPP process based on the information for determining the re-authorization / authentication method obtained from the AMF.

[0163] Fig. 9It is a schematic interactive flow chart of the wireless communication method 330 provided in an embodiment of the present application. The method 330 can be interactively executed by an Unmanned Aerial Vehicle (UAV), an AMF, an SMF, a UAVF, and a Unified Threat Management (UTM) / UAS Service Supplier (USS). Optionally, the UAV in the embodiment of the present application may also be referred to as a drone device, and may be replaced by other types of terminal devices, including other types of machine devices or ordinary handheld terminal devices, which are not limited in the present application. Similarly, AMF may be replaced by other mobility management network elements, SMF may be replaced by other session management network elements, and UAVF may be replaced by other terminal management network elements. In addition, optionally, UTM / USS may be any server with data processing capabilities.

[0164] like Fig. 9 As shown, the method 330 may include some or all of the following:

[0165] S331, UTM / USS needs to re-authorize / authenticate the UAV and sends a re-authorization / authentication request to the UAVF in the 3GPP network.

[0166] S332, UAVF sends a re-authorization / authentication request to the session management network element (eg, SMF).

[0167] S333, the session management network element (eg, SMF) sends a re-authorization / authentication request to the mobility management network element (eg, AMF).

[0168] S334, the mobility management network element (such as AMF) determines the re-authorization / authentication method.

[0169] S335, the mobility management network element (such as AMF) sends a re-authorization / authentication request to the UAV. The mobility management network element (such as AMF) will also send information used to determine the re-authorization / authentication method to the UAV. Method 1 is to re-authorize / authenticate the UAV through the mobility management network element (such as AMF), and method 2 is to authorize / authenticate the UAV through the session management network element (such as SMF). The information sent by AMF to the UAV for determining the re-authorization / authentication method includes but is not limited to the following:

[0170] a) Directly instruct the UAV to use method 1 or method 2.

[0171] b) Indicates whether the network side supports method 1 or method 2.

[0172] c), no instructions.

[0173] Based on this, the UAV determines the 3GPP procedure used to provide the re-authorization / authentication information based on the information obtained from the AMF for determining the re-authorization / authentication method. If the UAV determines from the AMF that the re-authorization / authentication method is method 1, the following steps are performed:

[0174] S336a, UAV sends information for re-authorization / authentication to the mobility management network element (e.g. AMF).

[0175] S337a, the mobility management network element (eg AMF) sends information for re-authorization / authentication to the UAVF.

[0176] If the UAV determines from the AMF that the re-authorization / authentication mode is mode 2, the following steps are performed:

[0177] S336b, UAV sends information for re-authorization / authentication to the session management network element (such as SMF).

[0178] S337b, the session management network element (eg, SMF) sends information for re-authorization / authentication to the UAVF.

[0179] For S336a~S337a and S336 b~S337 b, if AMF directly instructs UAV to use method 1 or method 2, method 1 sends the re-authorization / authentication information to the mobility management network element, such as AMF, through the registration process (e.g., mobility management message), and method 2 sends the re-authorization / authentication information to the session management network element, such as SMF, through the session management process (e.g., session management message). If AMF indicates that the network side does not support method 1, the re-authorization / authentication information is sent to the session management network element, such as SMF, through the session management process (e.g., session management message). If AMF indicates that the network side supports method 1, the re-authorization / authentication information is sent to the mobility management network element, such as AMF, through the registration process (e.g., mobility management message). If there is no indication, method 2 is used by default, and the re-authorization / authentication information is sent to the session management network element, such as SMF, through the session management process (e.g., session management message).

[0180] S338, UAVF sends re-authorization / authentication information to UTM / USS

[0181] In some embodiments of the present application, when the UTM / USS needs to revoke the authorization / authentication of the UAV, an indication of revoking the authorization / authentication is sent to the UAVF in the 3GPP network, the UAVF sends the indication of revoking the authorization / authentication to the SMF, the SMF sends the indication of revoking the authorization / authentication to the AMF, and the AMF sends the indication of revoking the authorization / authentication to the UAV.

[0182] Fig.10 It is a schematic interactive flow chart of the wireless communication method 340 provided in an embodiment of the present application. The method 340 can be interactively executed by an Unmanned Aerial Vehicle (UAV), an AMF, an SMF, a UAVF, and a Unified Threat Management (UTM) / UAS Service Supplier (USS). Optionally, the UAV in the embodiment of the present application may also be referred to as an unmanned aerial vehicle device, and may also be replaced by other types of terminal devices, including other types of machine devices or ordinary handheld terminal devices, which is not limited in the present application. Similarly, AMF may be replaced by other mobility management network elements, SMF may be replaced by other session management network elements, and UAVF may be replaced by other terminal management network elements. In addition, optionally, UTM / USS may be any server with data processing capabilities.

[0183] like Fig.10 As shown, the method 340 may include some or all of the following:

[0184] S341, UTM / USS needs to revoke the authorization / authentication of the UAV, and sends a revocation authorization / authentication indication to the UAVF in the 3GPP network.

[0185] S342, UAVF sends the authorization / authentication revocation indication to the session management network element (eg, SMF).

[0186] S343, the session management network element (eg, SMF) sends a revocation authorization / authentication indication to the mobility management network element (eg, AMF).

[0187] S344, the mobility management network element (eg AMF) sends a revocation authorization / authentication indication to the UAV.

[0188] In some embodiments of the present application, policy information is configured on the UAV, and the UAV provides authorization / authentication information through a corresponding 3GPP process according to the configured policy information.

[0189] Fig.11It is a schematic interactive flow chart of the wireless communication method 350 provided in an embodiment of the present application. The method 340 can be interactively executed by an unmanned aerial vehicle (UAV), an AMF, an SMF, a UAVF, a PCF, and a unified threat management (UTM) / UAS service supplier (USS). Optionally, the UAV in the embodiment of the present application can also be referred to as an unmanned aerial vehicle device, and can also be replaced by other types of terminal devices, including other types of machine devices or ordinary handheld terminal devices, which are not limited in the present application. Similarly, AMF can be replaced by other mobility management network elements, SMF can also be replaced by other session management network elements, UAVF can be replaced by other terminal management network elements, and PCF can also be replaced by other policy control network elements. In addition, optionally, UTM / USS can be any server with data processing capabilities.

[0190] like Fig.11 As shown, the method 350 may include some or all of the following:

[0191] S351, the policy control network element (eg, PCF) sends policy information to the mobility management network element (eg, AMF).

[0192] Optionally, policy information includes:

[0193] Parameters: area information, PLMN information, time information, etc.

[0194] Select the authorization / authentication method corresponding to the parameters: Method 1 is to authorize / authenticate UAV through a mobility management network element (such as AMF), and / or Method 2 is to authorize / authenticate UAV through a session management network element (such as SMF).

[0195] Optionally, the policy information may also include: UAV identification.

[0196] S352, the mobility management network element (eg, AMF) sends the policy information to the UAV.

[0197] If the UAV determines that the authorization / authentication method is method 1 according to the policy information, the following steps are performed:

[0198] S353a, UAV sends information for authorization / authentication to the mobility management network element (eg AMF).

[0199] S354a, the mobility management network element (eg, AMF) sends information for authorization / authentication to the UAVF.

[0200] If the UAV determines that the authorization / authentication method is method 2 according to the policy information, the following steps are performed:

[0201] S353b, UAV sends information for authorization / authentication to the session management network element (eg, SMF).

[0202] S354b, the session management network element (eg, SMF) sends information for authorization / authentication to the UAVF.

[0203] For S353a~S354a and S353 b~S354 b, the UAV determines the 3GPP process used for the information for authorization / authentication based on the policy information. For example, the 3GPP process used for the information for authorization / authentication is determined based on the match between the network information, location information, time information, etc., where the UAV is currently located, and the information in the policy information. If it is method 1, the information used for authorization / authentication is sent to the mobility management network element (such as AMF) through the registration process (such as mobility management message). If it is method 2, the information used for authorization / authentication is sent to the session management network element (such as SMF) through the session management process (such as session management message).

[0204] S355, UAVF sends the information used for authorization / authentication to UTM / USS.

[0205] In some embodiments of the present application, when the UTM / USS needs to re-authorize / authenticate the UAV, the re-authorization / authentication request is sent to the UAVF in the 3GPP network, the UAVF sends the re-authorization / authentication request to the SMF, the SMF sends the re-authorization / authentication request to the AMF, the AMF sends the re-authorization / authentication request to the UAV, the UAV determines the re-authorization / authentication method according to the configured policy information, and provides information for re-authorization / authentication through the corresponding 3GPP process.

[0206] Fig.12It is a schematic interactive flow chart of the wireless communication method 360 provided in an embodiment of the present application. The method 360 can be interactively executed by an Unmanned Aerial Vehicle (UAV), an AMF, an SMF, a UAVF, and a Unified Threat Management (UTM) / UAS Service Supplier (USS). Optionally, the UAV in the embodiment of the present application may also be referred to as a drone device, and may be replaced by other types of terminal devices, including other types of machine devices or ordinary handheld terminal devices, which are not limited in the present application. Similarly, AMF may be replaced by other mobility management network elements, SMF may be replaced by other session management network elements, and UAVF may be replaced by other terminal management network elements. In addition, optionally, UTM / USS may be any server with data processing capabilities.

[0207] like Fig.12 As shown, the method 360 may include some or all of the following:

[0208] S361, UTM / USS needs to re-authorize / authenticate the UAV and sends a re-authorization / authentication request to the UAVF in the 3GPP network.

[0209] S362, UAVF sends a re-authorization / authentication request to the session management network element (eg, SMF).

[0210] S363, the session management network element (eg, SMF) sends a re-authorization / authentication request to the mobility management network element (eg, AMF).

[0211] S364, the mobility management network element (eg, AMF) sends a re-authorization / authentication request to the UAV.

[0212] Based on this, the UAV may determine the re-authorization / authentication method based on the policy information. It should be understood that the UAV determines the re-authorization / authentication method based on the policy information, which is similar to the UAV determining the authorization / authentication method based on the policy information in method 350, and is not repeated here to avoid repetition.

[0213] If the UAV determines that the authorization / authentication method is method 1 according to the policy information, the following steps are performed:

[0214] S365a, UAV sends information for re-authorization / authentication to the mobility management network element (e.g. AMF).

[0215] S366a, the mobility management network element (eg AMF) sends information for re-authorization / authentication to the UAVF.

[0216] If the UAV determines that the authorization / authentication method is method 2 according to the policy information, the following steps are performed:

[0217] S365b, UAV sends information for re-authorization / authentication to the session management network element (eg, SMF).

[0218] S366b, the session management network element (eg, SMF) sends information for re-authorization / authentication to the UAVF.

[0219] For S365a~S366a and S365 b~S366 b, the UAV determines the 3GPP process used for the information for re-authorization / authentication based on the policy information. For example, the 3GPP process used for the information for re-authorization / authentication is determined based on the match between the network information, location information, time information, etc., where the UAV is currently located, and the information in the policy information. If it is method 1, the information for re-authorization / authentication is sent to the mobility management network element (such as AMF) through the registration process (such as mobility management message). If it is method 2, the information for re-authorization / authentication is sent to the session management network element (such as SMF) through the session management process (such as session management message).

[0220] S367, UAVF sends information for re-authorization / authentication to UTM / USS.

[0221] It should be understood that Figures 1 to 12 This is only an example of the present application and should not be construed as a limitation of the present application.

[0222] For example, in other embodiments of the present application, the process of re-authorizing / authenticating the UAV by methods 310 and 330 can also be applied to the process of authorizing / authenticating the UAV, which is equivalent to that the UAV does not need to be authorized / authenticated as soon as it is turned on, and can only perform the authorization / authentication process after the network receives an indication of the authorization / authentication method.

[0223] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple variations, and these simple variations all belong to the protection scope of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will not further describe various possible combinations. For another example, the various different embodiments of the present application can also be combined arbitrarily, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. It should also be understood that in the various method embodiments of the present application, the size of the sequence number of the above processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the term "and / or" is only a description of the association relationship of the associated objects, indicating that there can be three relationships. Specifically, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character “ / ” in this article generally indicates that the previous and next associated objects are in an “or” relationship.

[0224] Combination of the above Figures 1 to 12 , a method embodiment of the present application is described in detail, and an apparatus embodiment of the present application is described in detail below.

[0225] Fig.13 It is a schematic block diagram of a terminal device 410 according to an embodiment of the present application.

[0226] like Fig.13 As shown, the terminal device 410 may include:

[0227] A determining unit 411 is configured to determine a first target mode corresponding to a first operation, wherein the first operation includes at least one of authorization, authentication, re-authorization or re-authentication;

[0228] The sending unit 412 is configured to send information for performing the first operation based on the first target mode.

[0229] In some embodiments of the present application, the first target mode includes a first mode and / or a second mode, the first mode refers to the terminal device sending the information for performing the first operation through a registration process, and the second mode refers to the terminal device sending the information for performing the first operation through a session management process; the sending unit 412 is specifically used to:

[0230] When the first target mode is the first mode, the information used to perform the first operation is sent through a mobility management network element; when the first target mode is the second mode, the information used to perform the first operation is sent through a session management network element.

[0231] In some embodiments of the present application, the determining unit 411 is specifically configured to:

[0232] receiving a first request, wherein the first request is used to request re-authorization and / or re-authentication for the terminal device;

[0233] The first target mode is determined based on the mode of obtaining the first request.

[0234] In some embodiments of the present application, the determining unit 411 is specifically configured to:

[0235] In a case where the first request is received from the mobility management network element, determining the first mode as the first target mode;

[0236] When the first request is received from the session management network element, the second mode is determined as the first target mode.

[0237] In some embodiments of the present application, the sending unit 412 is further configured to:

[0238] First indication information sent by a mobility management network element is received, where the first indication information is used to determine the first target mode.

[0239] In some embodiments of the present application, the first indication information is used to instruct the terminal device to use the first mode or the second mode; the determining unit 411 is specifically used to:

[0240] The first mode or the second mode indicated by the first indication information is determined as the first target mode.

[0241] In some embodiments of the present application, the first indication information is used to indicate whether the first mode is supported or not supported, and / or the first indication information is used to indicate whether the second mode is supported or not supported; the determining unit 411 is specifically used to:

[0242] The first target mode is determined by using the supported modes indicated by the first indication information.

[0243] In some embodiments of the present application, the sending unit 412 is specifically used to:

[0244] A first request sent by the mobility management network element is received, where the first request is used to request the re-authorization and / or re-authentication, and the first request includes the first indication information.

[0245] In some embodiments of the present application, the sending unit 412 is further configured to:

[0246] receiving a first request sent by the mobility management network element, where the first request is used to request the re-authorization and / or re-authentication; the determining unit 411 is specifically used to:

[0247] In a case where the first request does not include information indicating the first target mode, the second mode is determined as the first target mode.

[0248] In some embodiments of the present application, the sending unit 412 is further configured to:

[0249] receiving policy information, where the policy information includes parameters corresponding to the first mode and / or parameters corresponding to the second mode; and the determining unit 411 is specifically configured to:

[0250] The first target mode is determined based on the policy information.

[0251] In some embodiments of the present application, the sending unit 412 is specifically used to:

[0252] The policy information sent by the policy control network element is received through the mobility management network element.

[0253] In some embodiments of the present application, the determining unit 411 is specifically configured to:

[0254] When the parameters of the terminal device match the parameters corresponding to the first mode, the first mode is determined as the first target mode; when the parameters of the terminal device match the parameters corresponding to the second mode, the second mode is determined as the first target mode.

[0255] In some embodiments of the present application, the parameter belongs to at least one of the following information:

[0256] Area information, Public Land Mobile Network PLMN information or time information.

[0257] In some embodiments of the present application, the policy information also includes an identifier of the terminal device.

[0258] In some embodiments of the present application, the sending unit 412 is specifically used to:

[0259] Second indication information is received, where the second indication information is used to indicate the withdrawal of authorization and / or authentication.

[0260] In some embodiments of the present application, the sending unit 412 is specifically used to:

[0261] receiving, through the mobility management network element, the second indication information forwarded by the session management network element;

[0262] Receiving, through the mobility management network element, the second indication information forwarded by the terminal management network element; or

[0263] The second indication information forwarded by the terminal management network element is received through the session management network element.

[0264] Fig.14 It is a schematic block diagram of the terminal management network element 420 provided in an embodiment of the present application.

[0265] like Fig.14 As shown, the terminal management network element 420 may include:

[0266] The receiving unit 421 is configured to receive a second request, wherein the second request is configured to request that at least one of the following operations be performed on the terminal device: re-authorization, re-authentication, revocation of authorization, or revocation of authentication;

[0267] A determination unit 422, configured to determine a target network element;

[0268] The sending unit 423 is configured to send the second request to the target network element.

[0269] In some embodiments of the present application, the determining unit 422 is specifically configured to:

[0270] A session management network element is determined as the target network element.

[0271] In some embodiments of the present application, the determining unit 422 is specifically configured to:

[0272] Determining a second target mode corresponding to a second operation, wherein the second operation includes at least one of authorization, authentication, re-authorization or re-authentication, and revoking authorization or revoking authentication;

[0273] The target network element is determined based on the second target mode.

[0274] In some embodiments of the present application, the second target mode includes a first mode and / or a second mode, the first mode refers to the terminal device sending the information for performing the second operation through a registration process, and the second mode refers to the terminal device sending the information for performing the second operation through a session management process; the determining unit 422 is specifically used to:

[0275] When the second target mode is the first mode, a mobility management network element is determined as the target network element; when the second target mode is the second mode, a session management network element is determined as the target network element.

[0276] In some embodiments of the present application, the determining unit 422 is further configured to:

[0277] The second target mode is determined based on a first mapping relationship, where the first mapping relationship includes parameters corresponding to the first mode and / or parameters corresponding to the second mode.

[0278] In some embodiments of the present application, the determining unit 422 is specifically configured to:

[0279] When the parameters of the terminal device match the parameters corresponding to the first mode, the first mode is determined as the second target mode; when the parameters of the terminal device match the parameters corresponding to the second mode, the second mode is determined as the second target mode.

[0280] In some embodiments of the present application, the parameter belongs to at least one of the following information:

[0281] Area information, Public Land Mobile Network PLMN information or time information.

[0282] In some embodiments of the present application, the first mapping relationship information is preconfigured.

[0283] In some embodiments of the present application, the determining unit 422 is specifically configured to:

[0284] Obtaining query information through a unified data storage UDR or a unified data management UDM, where the query information is used to indicate information of a mobility management network element and / or a session management network element serving the terminal device, and / or, the query information is used to indicate whether the mobility management network element and / or the session management network element supports the second operation;

[0285] Based on the query information, the second target mode is determined.

[0286] Fig.15 It is a schematic block diagram of the mobility management network element 430 provided in an embodiment of the present application.

[0287] like Fig.15 As shown, the mobility management network element 430 may include:

[0288] The receiving unit 431 is used to receive a third request, where the third request is used to request to perform at least one of the following operations on the terminal device: re-authorization, re-authentication, revocation of authorization, or revocation of authentication;

[0289] The sending unit 432 is configured to send the third request to the terminal device.

[0290] In some embodiments of the present application, the receiving unit 431 is specifically used to:

[0291] The third request sent by the receiving terminal management network element.

[0292] In some embodiments of the present application, the receiving unit 431 is specifically used to:

[0293] The third request sent by the session management network element is received.

[0294] In some embodiments of the present application, the third request includes first indication information, and the first indication information is used to determine a first target mode corresponding to a first operation, and the first operation includes at least one of authorization, authentication, re-authorization or re-authentication.

[0295] In some embodiments of the present application, the first target method includes a first method and / or a second method, the first method refers to the terminal device sending the information used to perform the first operation through a registration process, and the second method refers to the terminal device sending the information used to perform the first operation through a session management process.

[0296] In some embodiments of the present application, the first indication information is used to instruct the terminal device to use the first method or the second method.

[0297] In some embodiments of the present application, the first indication information is used to indicate whether the first method is supported or not, and / or the first indication information is used to indicate whether the second method is supported or not.

[0298] In some embodiments of the present application, when the third request does not include information for indicating a first target mode corresponding to the first operation, the first target mode is a second mode, the first operation includes at least one of authorization, authentication, re-authorization or re-authentication, and the second mode refers to the terminal device sending the information for performing the first operation through a session management process.

[0299] Fig.16 It is a schematic block diagram of the policy control network element 440 provided in an embodiment of the present application.

[0300] like Fig.16 As shown, the policy control network element 440 may include:

[0301] The sending unit 441 is used to send policy information to the terminal device through the mobility management network element, where the policy information includes parameters corresponding to the first mode and / or parameters corresponding to the second mode.

[0302] In some embodiments of the present application, the parameter belongs to at least one of the following information:

[0303] Area information, Public Land Mobile Network PLMN information or time information.

[0304] In some embodiments of the present application, the policy information also includes an identifier of the terminal device.

[0305] In some embodiments of the present application, the first method refers to the terminal device sending the information used to perform the first operation through a registration process, and the second method refers to the terminal device sending the information used to perform the first operation through a session management process, and the first operation includes at least one of authorization, authentication, re-authorization or re-authentication.

[0306] It should be understood that in the present application, the device embodiments and the method embodiments may correspond to each other, and similar descriptions may refer to the method embodiments. Specifically, Fig.13 The terminal device 410 shown, Fig.14 The terminal management network element 420 shown, Fig.15 The mobility management network element shown and Fig.16 The policy control network elements shown may correspond to the corresponding subjects in the method for executing the embodiment of the present application, and Fig.13 The terminal device 410 shown, Fig.14 The terminal management network element 420 shown, Fig.15 The mobility management network element shown and Fig.16 The aforementioned and other operations and / or functions of each unit in the policy control network element shown are for implementing the corresponding processes in each method, and for the sake of brevity, they are not described again here.

[0307] The communication device of the embodiment of the present application is described above from the perspective of the functional module in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or a combination of hardware and software modules in the decoding processor to perform. Optionally, the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory, and completes the steps in the above method embodiment in conjunction with its hardware. For example, the determination unit and the communication unit involved above can be implemented by a processor and a transceiver, respectively.

[0308] Fig.17 It is a schematic structural diagram of a communication device 500 according to an embodiment of the present application.

[0309] like Fig.17 As shown, the communication device 500 may include a processor 510 .

[0310] The processor 510 may call and run a computer program from the memory to implement the method in the embodiment of the present application.

[0311] Please continue to see Fig.17 , the communication device 500 may further include a memory 520 .

[0312] The memory 520 may be used to store indication information, and may also be used to store codes, instructions, etc. executed by the processor 510. The processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application. The memory 520 may be a separate device independent of the processor 510, or may be integrated in the processor 510.

[0313] Please continue to see Fig.17 , the communication device 500 may further include a transceiver 530 .

[0314] The processor 510 may control the transceiver 530 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include an antenna, and the number of antennas may be one or more.

[0315] It should be understood that the various components in the communication device 500 are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0316] It should also be understood that the communication device 500 may be a terminal device of an embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. That is to say, the communication device 500 of the embodiment of the present application may correspond to the terminal device 410 in the embodiment of the present application, and may correspond to the execution of the corresponding subject in the method 200 according to the embodiment of the present application. For the sake of brevity, it will not be repeated here. Similarly, the communication device 500 may be various network elements of the embodiments of the present application, and the communication device 500 may implement the corresponding processes implemented by the corresponding network elements in the various methods of the embodiments of the present application. That is to say, the communication device 500 of the embodiment of the present application may correspond to the terminal device 410 in the embodiment of the present application. Fig.13 The terminal device 410 shown in FIG. Fig.14 The terminal management network element 420 shown in FIG. Fig.15 The mobility management network element shown or Fig.16 The policy control network element shown may correspond to the corresponding subject in the method according to the embodiment of the present application, and for the sake of brevity, it will not be repeated here.

[0317] In addition, a chip is also provided in an embodiment of the present application.

[0318] For example, the chip may be an integrated circuit chip with signal processing capabilities, and can implement or execute the methods, steps, and logic diagrams disclosed in the embodiments of the present application. The chip may also be called a system-level chip, a system chip, a chip system, or a system-on-chip chip, etc. Optionally, the chip can be applied to various communication devices, so that the communication device equipped with the chip can execute the methods, steps, and logic diagrams disclosed in the embodiments of the present application.

[0319] Fig.18 is a schematic structural diagram of a chip 600 according to an embodiment of the present application.

[0320] like Fig.18 As shown, the chip 600 includes a processor 610 .

[0321] The processor 610 may call and run a computer program from the memory to implement the method in the embodiment of the present application.

[0322] Please continue to see Fig.18 , the chip 600 may further include a memory 620 .

[0323] The processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application. The memory 620 may be used to store indication information, and may also be used to store codes, instructions, etc. executed by the processor 610. The memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.

[0324] Please continue to see Fig.18 , the chip 600 may further include an input interface 630 .

[0325] The processor 610 may control the input interface 630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0326] Please continue to see Fig.18 , the chip 600 may further include an output interface 640 .

[0327] The processor 610 may control the output interface 640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0328] It should be understood that the chip 600 can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present application, and can also implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of the present application. For the sake of brevity, it will not be repeated here.

[0329] It should also be understood that the various components in the chip 600 are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0330] The processors mentioned above may include but are not limited to:

[0331] General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.

[0332] The processor can be used to implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor, or a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0333] The memory mentioned above includes but is not limited to:

[0334] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus random access memory (DR RAM).

[0335] It should be noted that the memory described herein is intended to include these and any other suitable types of memory.

[0336] In an embodiment of the present application, a computer-readable storage medium is further provided for storing a computer program. The computer-readable storage medium stores one or more programs, wherein the one or more programs include instructions, which, when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to perform the method of the method embodiment.

[0337] Optionally, the computer-readable storage medium can be applied to each network element in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the corresponding network elements in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0338] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0339] A computer program product is also provided in an embodiment of the present application, including a computer program.

[0340] Optionally, the computer program product can be applied to each network element in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the corresponding network elements in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0341] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0342] The embodiment of the present application further provides a computer program. When the computer program is executed by a computer, the computer can execute the method of the method embodiment.

[0343] Optionally, the computer program can be applied to each network element in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the corresponding network elements in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0344] In addition, the embodiment of the present application also provides a communication system, which may include the terminal device and each network element involved above to form a communication system as follows: Figure 1 The communication system 100 shown is not described in detail for the sake of brevity. It should be noted that the term "system" and the like in this document may also be referred to as "network management architecture" or "network system" and the like.

[0345] It should also be understood that the terms used in the embodiments of the present application and the appended claims are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present application.

[0346] For example, as used in the embodiments of the present application and the appended claims, the singular forms "a," "said," "above," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

[0347] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

[0348] If implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk.

[0349] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0350] In several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways.

[0351] For example, the division of units or modules or components in the device embodiment described above is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or modules or components can be combined or integrated into another system, or some units or modules or components can be ignored or not executed.

[0352] For another example, the units / modules / components described above as separation / display components may or may not be physically separated, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units / modules / components may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

[0353] Finally, it should be noted that the mutual coupling or direct coupling or communication connection shown or discussed above may be an indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.

[0354] The above contents are only specific implementation methods of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be based on the protection scope of the claims.

Claims

1. A wireless communication method, characterized in that: The method is applicable to a terminal management network element, and the method comprises: receiving a second request, the second request being used to request at least one of the following operations to be performed on the terminal device: re-authorization, re-authentication, revocation of authorization, or revocation of authentication; Determine the target network element; sending the second request to the target network element, The determining of the target network element includes: determining a second target mode corresponding to a second operation, wherein the second operation includes at least one of authorization, authentication, re-authorization or re-authentication, revoking authorization or revoking authentication; and determining the target network element based on the second target mode. The second target mode includes the first mode and / or the second mode, the first mode refers to the terminal device sending information for performing the second operation through a registration process, and the second mode refers to the terminal device sending the information for performing the second operation through a session management process; and determining the target network element based on the second target mode includes: When the second target mode is the first mode, a mobility management network element is determined as the target network element; when the second target mode is the second mode, a session management network element is determined as the target network element.

2. The method according to claim 1, characterized in that: The determining the second target mode corresponding to the second operation includes: The second target mode is determined based on a first mapping relationship, where the first mapping relationship includes parameters corresponding to the first mode and / or parameters corresponding to the second mode.

3. The method according to claim 2, characterized in that The determining the second target mode based on the first mapping relationship includes: When the parameters of the terminal device match the parameters corresponding to the first mode, the first mode is determined as the second target mode; when the parameters of the terminal device match the parameters corresponding to the second mode, the second mode is determined as the second target mode.

4. The method according to claim 2, characterized in that: The parameter belongs to at least one of the following information: Area information, Public Land Mobile Network PLMN information or time information.

5. The method according to claim 2, characterized in that: The first mapping relationship is preconfigured.

6. The method according to claim 1, characterized in that The determining the second target mode corresponding to the second operation includes: Obtaining query information through a unified data storage UDR or a unified data management UDM, where the query information is used to indicate information of a mobility management network element and / or a session management network element serving the terminal device, and / or, the query information is used to indicate whether the mobility management network element and / or the session management network element supports the second operation; Based on the query information, the second target mode is determined.

7. A terminal management network element, characterized in that: include: A receiving unit, configured to receive a second request, wherein the second request is used to request at least one of the following operations to be performed on the terminal device: re-authorization, re-authentication, revocation of authorization, or revocation of authentication; A determination unit, used for determining a target network element; a sending unit, configured to send the second request to the target network element, The determining unit is further used to: determine a second target mode corresponding to a second operation, the second operation including at least one of authorization, authentication, re-authorization or re-authentication, revocation of authorization or revocation of authentication; determine the target network element based on the second target mode, The second target mode includes the first mode and / or the second mode, the first mode refers to the terminal device sending information for performing the second operation through a registration process, and the second mode refers to the terminal device sending the information for performing the second operation through a session management process; the determining unit is further used to: When the second target mode is the first mode, a mobility management network element is determined as the target network element; when the second target mode is the second mode, a session management network element is determined as the target network element.

8. The terminal management network element according to claim 7, characterized in that: The determining unit is further configured to: The second target mode is determined based on a first mapping relationship, where the first mapping relationship includes parameters corresponding to the first mode and / or parameters corresponding to the second mode.

9. The terminal management network element according to claim 8, characterized in that: The determining unit is further configured to: When the parameters of the terminal device match the parameters corresponding to the first mode, the first mode is determined as the second target mode; when the parameters of the terminal device match the parameters corresponding to the second mode, the second mode is determined as the second target mode.

10. The terminal management network element according to claim 8, characterized in that: The parameter belongs to at least one of the following information: Area information, Public Land Mobile Network PLMN information or time information.

11. The terminal management network element according to claim 8, characterized in that: The first mapping relationship is preconfigured.

12. The terminal management network element according to claim 7, characterized in that: The determining unit is further configured to: Obtaining query information through a unified data storage UDR or a unified data management UDM, where the query information is used to indicate information of a mobility management network element and / or a session management network element serving the terminal device, and / or, the query information is used to indicate whether the mobility management network element and / or the session management network element supports the second operation; Based on the query information, the second target mode is determined.

13. A terminal management network element, characterized in that: include: A processor and a memory, the memory being used to store a computer program, and the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 6.

Images